| View previous topic :: View next topic |
| Author |
Message |
tranquilcool
Veteran
Joined: 25 Mar 2005
Posts: 1179
|
 Posted: Fri Mar 06, 2009 8:50 pm Post subject: |
 |
|
| cheater1034 wrote: | | tranquilcool wrote: | sysctl table check failed: /debug/hid_mousepoll_interval .6.77 Unknown sysctl binary path
Pid: 1, comm: swapper Not tainted 2.6.28-zen12 #1
Call Trace:
[<8013c867>] set_fail+0x45/0x47
[<8013cbcf>] sysctl_check_table+0x366/0x6b7
[<8012c8c2>] sysctl_head_finish+0x11/0x37
[<8013cbeb>] sysctl_check_table+0x382/0x6b7
[<80647d37>] sysctl_init+0x0/0x25
[<80647d59>] sysctl_init+0x22/0x25
[<80101114>] do_one_initcall+0x24/0x16e
[<8011de2b>] finish_task_switch+0x1f/0x79
[<804c7458>] schedule+0x23a/0x697
[<8015c94f>] __alloc_pages_internal+0x9a/0x470
[<804c7bee>] schedule_timeout+0x7d/0xaf
[<804c7ae6>] wait_for_common+0xed/0x10c
[<8011d27a>] enqueue_task_fair+0x12a/0x18f
[<801121fd>] xapic_wait_icr_idle+0x11/0x17
[<80120e68>] resched_task+0x56/0x63
[<8011f4ec>] try_to_wake_up+0xaf/0x171
[<80134cea>] __create_workqueue_key+0x9f/0x162
[<8063636b>] kernel_init+0x159/0x225
[<80636212>] kernel_init+0x0/0x225
[<801040f7>] kernel_thread_helper+0x7/0x10
this shows up in dmesg both in 28-zen12 an 29-rc7-zen2
any ideas? |
.config would be beneficial, i can't answer bug reports when people don't give me any other information besides what the problem is. |
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_SET_CUSTOM_SCHED_LATENCY=y
CONFIG_CUSTOM_SCHED_LATENCY=20
CONFIG_SET_CUSTOM_SCHED_MIN_GRANULARITY=y
CONFIG_CUSTOM_SCHED_MIN_GRANULARITY=4000
CONFIG_SET_CUSTOM_SCHED_WAKEUP_GRANULARITY=y
CONFIG_CUSTOM_SCHED_WAKEUP_GRANULARITY=10
CONFIG_SET_CUSTOM_VM_SWAPPINESS=y
CONFIG_CUSTOM_VM_SWAPPINESS=66
CONFIG_SET_CUSTOM_VM_DIRTY_RATIO=y
CONFIG_CUSTOM_VM_DIRTY_RATIO=10
CONFIG_BOOST_PRIVILEGED_TASKS=y
CONFIG_BOOST_RENICE_SETTING=-10
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_KERNEL_LZMA=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_TASKSTATS=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
CONFIG_PREEMPT_RCU=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_NAMESPACES=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs"
CONFIG_INITRAMFS_ROOT_UID=0
CONFIG_INITRAMFS_ROOT_GID=0
CONFIG_RD_LZMA=y
CONFIG_CUSTOM_CFLAGS=""
CONFIG_CUSTOM_MAKEFLAGS="-j5"
CONFIG_SYSCTL=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
CONFIG_SLUB=y
CONFIG_XVMALLOC=y
CONFIG_HAVE_OPROFILE=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_FIFO=y
CONFIG_IOSCHED_BFQ=y
CONFIG_DEFAULT_BFQ=y
CONFIG_DEFAULT_IOSCHED="bfq"
CONFIG_FREEZER=y
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_MPENTIUM4=y
CONFIG_X86_MARCH_NATIVE=y
CONFIG_X86_CPU=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_PROCESSOR_SELECT=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_NR_CPUS=2
CONFIG_SCHED_SMT=y
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_HIGHMEM4G=y
CONFIG_VMSPLIT_2G=y
CONFIG_PAGE_OFFSET=0x80000000
CONFIG_HIGHMEM=y
CONFIG_NEED_NODE_MEMMAP_SIZE=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
CONFIG_HIGHPTE=y
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_SECCOMP=y
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_PM=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_X86_P4_CLOCKMOD=y
CONFIG_X86_SPEEDSTEP_LIB=y
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_BINFMT_ELF=y
CONFIG_HAVE_AOUT=y
CONFIG_BINFMT_MISC=m
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_NET=y
CONFIG_COMPAT_NET_DEV_OPS=y
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_INET=y
CONFIG_IP_FIB_HASH=y
CONFIG_NET_IPIP=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_LRO=m
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NF_DEFRAG_IPV4=m
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_BT=y
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE=""
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_COMPCACHE=y
CONFIG_BLK_DEV_COMPCACHE_DEBUG=y
CONFIG_SWAP_DISCARD_SUPPORTED=y
CONFIG_BLK_DEV_COMPCACHE_STATS=y
CONFIG_HAVE_IDE=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_WAIT_SCAN=m
CONFIG_ATA=y
CONFIG_ATA_ACPI=y
CONFIG_ATA_SFF=y
CONFIG_ATA_PIIX=y
CONFIG_MD=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=m
CONFIG_IEEE1394=y
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_RAWIO=y
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_PCI=y
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
CONFIG_INPUT=y
CONFIG_INPUT_POLLDEV=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_LIBPS2=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_NR_TTY_DEVICES=63
CONFIG_VT_CKO=y
CONFIG_VT_PRINTK_EMERG_COLOR=0x01
CONFIG_VT_PRINTK_ALERT_COLOR=0x04
CONFIG_VT_PRINTK_CRIT_COLOR=0x05
CONFIG_VT_PRINTK_ERR_COLOR=0x0B
CONFIG_VT_PRINTK_WARNING_COLOR=0x09
CONFIG_VT_PRINTK_NOTICE_COLOR=0x07
CONFIG_VT_PRINTK_INFO_COLOR=0x0F
CONFIG_VT_PRINTK_DEBUG_COLOR=0x03
CONFIG_HW_CONSOLE=y
CONFIG_DEVKMEM=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_PPDEV=y
CONFIG_HW_RANDOM=y
CONFIG_RTC=y
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_I801=y
CONFIG_I2C_PIIX4=y
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_POWER_SUPPLY=y
CONFIG_HWMON=y
CONFIG_HWMON_VID=y
CONFIG_SENSORS_W83627HF=y
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_SSB_POSSIBLE=y
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_DVB_CORE=y
CONFIG_VIDEO_MEDIA=y
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=y
CONFIG_MEDIA_TUNER_SIMPLE=y
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA9887=y
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_IR_I2C=m
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_BT848=m
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_DVB_CAPTURE_DRIVERS=y
CONFIG_DVB_BT8XX=m
CONFIG_DVB_CX24110=y
CONFIG_DVB_SP887X=y
CONFIG_DVB_NXT6000=y
CONFIG_DVB_MT352=y
CONFIG_DVB_ZL10353=y
CONFIG_DVB_OR51211=y
CONFIG_DVB_LGDT330X=y
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_UVESA=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FB_CON_DECOR=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_ZEN_CLUT224=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_HRTIMER=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_RTCTIMER=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_VMASTER=y
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_DRIVERS=y
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_PCI=y
CONFIG_SND_BT87X=m
CONFIG_SND_EMU10K1=y
CONFIG_SND_INTEL8X0=m
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
CONFIG_AC97_BUS=y
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
CONFIG_USB_HID=y
CONFIG_USB_HID_MOUSE_POLLING=y
CONFIG_USB_HID_MOUSE_POLLING_INTERVAL=10
CONFIG_USB_HIDDEV=y
CONFIG_HID_COMPAT=y
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_EZKEY=y
CONFIG_HID_GYRATION=y
CONFIG_HID_LOGITECH=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_NTRIG=y
CONFIG_HID_PANTHERLORD=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
CONFIG_HID_TOPSEED=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_SUSPEND=y
CONFIG_USB_MON=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_BERRY_CHARGE=y
CONFIG_EDAC=y
CONFIG_EDAC_MM_EDAC=y
CONFIG_EDAC_I82875P=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I82860=m
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_REISERFS_FS=y
CONFIG_REISER4_FS=y
CONFIG_JFS_FS=y
CONFIG_FILE_LOCKING=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_TREE=y
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_AUTOFS4_FS=y
CONFIG_FUSE_FS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=y
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFSD=y
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_CODA_FS=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_UTF8=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_DOUBLEFAULT=y
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_UDELAY=y
CONFIG_DEFAULT_IO_DELAY_TYPE=2
CONFIG_OPTIMIZE_INLINING=y
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_LZF=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y
CONFIG_HAVE_KVM=y
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
CONFIG_CRC7=y
CONFIG_LIBCRC32C=y
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
sorry i didn't give .config
@Gentree
thanks!
_________________
this is a strange strange world.
Last edited by tranquilcool on Fri Mar 06, 2009 11:01 pm; edited 2 times in total |
|
| Back to top |
|
 |
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Fri Mar 06, 2009 10:46 pm Post subject: |
|
|
| Code: | | grep -e ^[^#] .config |
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
cheater1034
Veteran
Joined: 09 Sep 2004
Posts: 1558
|
| Posted: Mon Mar 09, 2009 6:34 pm Post subject: |
|
|
| Gentree wrote: | | kernelOfTruth wrote: | I haven't kept track of all those changes but I suppose
2.6.28-zen12 and 2.6.29-rc7-zen1 contain the latest reiser4 with fixes ?
thanks for your continued work on this kernel(patchset)  |
huh? what fixes? I just started using 2.6.28-zen10 recently and had 70% of my R4 portage partition disappear on me after a power out.  Was the R4 patch in this release unstable? |
No, like the other filesystems in zen, reiser4 is always the latest upstream. There is nothing there to make it unstable like that. But, generally speaking, reiser4 is pretty infamous about corrupting data.
| Quote: | | I have been using 2.6.20-nicus for nearly 2 years and have most of my system on R4 since R4 was in beta. This is the first time I have lost ANYTHING on an R4 partition despite frequent browns on power glitches. Very disappointing. |
It seems to have happened to all of us. I've used reiser4 for atleast 2 years, the first time i lost data was back in mid-2008 some time. I got sick of reiser4 anyway since it becomes un-usably slow when using compression after the disk gets to about 50% full. I suppose the allocation in btrfs is much better so on a btrfs partition with zlib compression, it won't bog down at 50% full like reiser4, but rather more like ~90%.
| Quote: | Can this still be regarded as reliable? Whatever happened to atomic writes? Atomic as in nuked partition?
I've seen some murmurings about kernel ppl hacking about in R4 and making a mess of it.
 |
Reiser4 has a lot of problems, I've heard it regarded to as many things but I don't think one of those things was ever reliable. I'd say it's pretty doubtful it will get into linus' tree even if everything on the to-do list is ever gets done.
Anyway, corrupt data sucks and seems to be more frequent of an occurence on reiser4 then other filesystems (i havent had any corruption on xfs, ext4, or btrfs in the time that I have used them).
So anyway, it's the latest reiser4 upstream with no gimmicks or anything, so it's nothing zen-specific that broke it.
_________________
IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
--
Lost in android development land. |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Thu Mar 12, 2009 12:53 pm Post subject: |
|
|
| cheater1034 wrote: | | Gentree wrote: | | kernelOfTruth wrote: | I haven't kept track of all those changes but I suppose
2.6.28-zen12 and 2.6.29-rc7-zen1 contain the latest reiser4 with fixes ?
thanks for your continued work on this kernel(patchset) |
huh? what fixes? I just started using 2.6.28-zen10 recently and had 70% of my R4 portage partition disappear on me after a power out. Was the R4 patch in this release unstable? |
No, like the other filesystems in zen, reiser4 is always the latest upstream. There is nothing there to make it unstable like that. But, generally speaking, reiser4 is pretty infamous about corrupting data.
| Quote: | | I have been using 2.6.20-nicus for nearly 2 years and have most of my system on R4 since R4 was in beta. This is the first time I have lost ANYTHING on an R4 partition despite frequent browns on power glitches. Very disappointing. |
It seems to have happened to all of us. I've used reiser4 for atleast 2 years, the first time i lost data was back in mid-2008 some time.
|
Reiser4 got a lot of bad press while it was in beta. A lot of ppl used it without sufficient precaution (backup) and then got all flamey and cursed the fs for their own fuckups. They have been flaming ever since. IIRC there were some issues that lingered a bit longer on 64bit systems - which were pretty new at that time.
Linus' principal objection seems to be the idea of plugins and the security implications of having something in the kernel that opens a door in having a plugin interface.
Since Hans decided to get a job breaking rocks he has been out of the loop. This clearly has been detrimental to progress on R4. Your experience with recent breakage starting last year would coincide with my experience and with the rumours that someone(s) who doesn't understand the code has been poking where they should not.
For me the main interest in R4 was it's resistance to power failure which is pretty common here. Uptil now it has saved me from needing to buy a UPS. That was a big plus. Looks like someone has fsck all the hard work that went into making this outstanding fs. 
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
cheater1034
Veteran
Joined: 09 Sep 2004
Posts: 1558
|
| Posted: Fri Mar 13, 2009 2:18 am Post subject: |
|
|
| Gentree wrote: | | cheater1034 wrote: | | Gentree wrote: | | kernelOfTruth wrote: | I haven't kept track of all those changes but I suppose
2.6.28-zen12 and 2.6.29-rc7-zen1 contain the latest reiser4 with fixes ?
thanks for your continued work on this kernel(patchset) |
huh? what fixes? I just started using 2.6.28-zen10 recently and had 70% of my R4 portage partition disappear on me after a power out. Was the R4 patch in this release unstable? |
No, like the other filesystems in zen, reiser4 is always the latest upstream. There is nothing there to make it unstable like that. But, generally speaking, reiser4 is pretty infamous about corrupting data.
| Quote: | | I have been using 2.6.20-nicus for nearly 2 years and have most of my system on R4 since R4 was in beta. This is the first time I have lost ANYTHING on an R4 partition despite frequent browns on power glitches. Very disappointing. |
It seems to have happened to all of us. I've used reiser4 for atleast 2 years, the first time i lost data was back in mid-2008 some time.
|
Reiser4 got a lot of bad press while it was in beta. A lot of ppl used it without sufficient precaution (backup) and then got all flamey and cursed the fs for their own fuckups. They have been flaming ever since. IIRC there were some issues that lingered a bit longer on 64bit systems - which were pretty new at that time.
Linus' principal objection seems to be the idea of plugins and the security implications of having something in the kernel that opens a door in having a plugin interface.
Since Hans decided to get a job breaking rocks he has been out of the loop. This clearly has been detrimental to progress on R4. Your experience with recent breakage starting last year would coincide with my experience and with the rumours that someone(s) who doesn't understand the code has been poking where they should not.
For me the main interest in R4 was it's resistance to power failure which is pretty common here. Uptil now it has saved me from needing to buy a UPS. That was a big plus. Looks like someone has fsck all the hard work that went into making this outstanding fs. |
Switch to btrfs
It doesn't bog down like reiser4, and it has more features (has compression too), and from what I can tell it's the fastest FS i've ever used 
_________________
IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
--
Lost in android development land. |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
gimpel
Advocate
Joined: 15 Oct 2004
Posts: 2720
Location: Munich, Bavaria
|
| Posted: Fri Mar 13, 2009 3:59 pm Post subject: |
|
|
| kernelOfTruth wrote: | | cheater1034 wrote: |
Switch to btrfs
It doesn't bog down like reiser4, and it has more features (has compression too), and from what I can tell it's the fastest FS i've ever used |
how's space efficiency with btrfs ?
is it better than ext3 ? comparable to jfs ? (jfs is a little worse in terms of space efficiency compared to reiserfs)
thanks |
Depends on if you use compression or don't. BTRFS has optional transparent compression too.
Speaking of which.. anyone knows how to boot a root partition on a multidevice BTRFS subvol?
My current GRUB command looks like:
| Code: | | /kernel-2.6.29-rc7-git3 root=/dev/sdb7 rootfstype=btrfs rootflags=subvol=archroot,device=/dev/sdb7,device=/dev/sda1 vga=0x317 |
but that gives a "sdb7 not found or bad block" error
_________________
http://proaudio.tuxfamily.org/wiki - pro-audio software overlay
|
|
| Back to top |
|
|
broch
Tux's lil' helper
Joined: 09 Jul 2005
Posts: 94
|
| Posted: Fri Mar 20, 2009 12:51 pm Post subject: old bug reappeared in zen |
|
|
this kills touchpad every few minutes:
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
the above is not present in 2.6.28.8 or 2.6.29-rc8-git4
This problem was firs present in kernels from 2007 I believe.
edit:
hmm actually I see it in 2.6.28.8 now
so I will run longer 2.6.29-rc8-git4 see what will happen |
|
| Back to top |
|
|
dodo1122
Guru
Joined: 02 Sep 2006
Posts: 347
Location: York, England
|
| Posted: Sat Mar 21, 2009 2:01 am Post subject: Re: old bug reappeared in zen |
|
|
| broch wrote: | this kills touchpad every few minutes:
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
the above is not present in 2.6.28.8 or 2.6.29-rc8-git4
This problem was firs present in kernels from 2007 I believe.
edit:
hmm actually I see it in 2.6.28.8 now
so I will run longer 2.6.29-rc8-git4 see what will happen |
And i thought i was the only one who was getting this :/
Started happening with 2.6.28 tbh, and isn't frequent, but damn annoying when it happens.
I have a thinkpad T61p.
_________________
#zen-sources on irc.rizon.net |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sat Mar 21, 2009 2:35 am Post subject: Re: old bug reappeared in zen |
|
|
| dodo1122 wrote: | | broch wrote: | this kills touchpad every few minutes:
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
the above is not present in 2.6.28.8 or 2.6.29-rc8-git4
This problem was firs present in kernels from 2007 I believe.
edit:
hmm actually I see it in 2.6.28.8 now
so I will run longer 2.6.29-rc8-git4 see what will happen |
And i thought i was the only one who was getting this :/
Started happening with 2.6.28 tbh, and isn't frequent, but damn annoying when it happens.
I have a thinkpad T61p. |
thinkpad ftl!
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
tranquilcool
Veteran
Joined: 25 Mar 2005
Posts: 1179
|
| Posted: Sat Mar 21, 2009 6:35 am Post subject: |
|
|
i don't have a thinkpad but the mouse thing happens frequently
and it's very annoying.
_________________
this is a strange strange world. |
|
| Back to top |
|
|
ponciarello
Apprentice
Joined: 22 Jul 2008
Posts: 223
Location: beach of slack
|
| Posted: Sat Mar 21, 2009 2:07 pm Post subject: |
|
|
| Code: | Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c012de0d>] do_group_exit+0x2d/0x90
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c0137b6f>] dequeue_signal+0x2f/0x1b0
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kerne
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c01381e0>] get_signal_to_deliver+0x230/0x3c0
l: [<c012de0d>] do_group_exit+0x2d/0x90
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c01025d1>] do_notify_resume+0xc1/0x830
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c01381e0>] get_signal_to_deliver+0x230/0x3c0
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c01025d1>] do_notify_resume+0xc1/0x830
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c0192f90>] filldir64+0x0/0x100
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c0192f90>] filldir64+0x0/0x100
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c01afc06>] inotify_inode_queue_event+0x46/0x100
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c01afc06>] inotify_inode_queue_event+0x46/0x100
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c0142b38>] ktime_get+0x18/0x40
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c0142b38>] ktime_get+0x18/0x40
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c014dad3>] sys_futex+0xa3/0x130
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c014dad3>] sys_futex+0xa3/0x130
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c010342a>] work_notifysig+0x13/0x19
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c010342a>] work_notifysig+0x13/0x19
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c014dad3>] sys_futex+0xa3/0x130
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: [<c010342a>] work_notifysig+0x13/0x19
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: Code: 0c e9 74 bf 2a 00 8d 74 26 00 83 ec 10 89 5c 24 04 89 74 24 08 89 7c 24 0c 89 c3 89 d6 8b 40 14 85 c0 74 4a 8b 43 10 85 c0 74 3f <8b> 48 34 85 c9 74 38 89 d8 ff d1 89 c7 89 f2 89 d8 e8 79 bc 02
Message from syslogd@toscibo at Sat Mar 21 15:05:17 2009 ...
toscibo kernel: EIP: [<c01835d1>] filp_close+0x21/0x80 SS:ESP 0068:ec8e5e14 |
latest pull
_________________
look for monty python channel on youtube |
|
| Back to top |
|
|
gaelic
Tux's lil' helper
Joined: 30 Dec 2003
Posts: 119
Location: Vienna, Austria, Europe, World, Solar System, Milky Way, Universe
|
| Posted: Sat Mar 21, 2009 7:13 pm Post subject: |
|
|
| Gentree wrote: | | cheater1034 wrote: | | Gentree wrote: | | kernelOfTruth wrote: | I haven't kept track of all those changes but I suppose
2.6.28-zen12 and 2.6.29-rc7-zen1 contain the latest reiser4 with fixes ?
thanks for your continued work on this kernel(patchset) |
huh? what fixes? I just started using 2.6.28-zen10 recently and had 70% of my R4 portage partition disappear on me after a power out. Was the R4 patch in this release unstable? |
No, like the other filesystems in zen, reiser4 is always the latest upstream. There is nothing there to make it unstable like that. But, generally speaking, reiser4 is pretty infamous about corrupting data.
| Quote: | | I have been using 2.6.20-nicus for nearly 2 years and have most of my system on R4 since R4 was in beta. This is the first time I have lost ANYTHING on an R4 partition despite frequent browns on power glitches. Very disappointing. |
It seems to have happened to all of us. I've used reiser4 for atleast 2 years, the first time i lost data was back in mid-2008 some time.
|
Reiser4 got a lot of bad press while it was in beta. A lot of ppl used it without sufficient precaution (backup) and then got all flamey and cursed the fs for their own fuckups. They have been flaming ever since. IIRC there were some issues that lingered a bit longer on 64bit systems - which were pretty new at that time.
Linus' principal objection seems to be the idea of plugins and the security implications of having something in the kernel that opens a door in having a plugin interface.
Since Hans decided to get a job breaking rocks he has been out of the loop. This clearly has been detrimental to progress on R4. Your experience with recent breakage starting last year would coincide with my experience and with the rumours that someone(s) who doesn't understand the code has been poking where they should not.
For me the main interest in R4 was it's resistance to power failure which is pretty common here. Uptil now it has saved me from needing to buy a UPS. That was a big plus. Looks like someone has fsck all the hard work that went into making this outstanding fs. |
thanks for your words, exactly whats on my mind too.  |
|
| Back to top |
|
|
gaelic
Tux's lil' helper
Joined: 30 Dec 2003
Posts: 119
Location: Vienna, Austria, Europe, World, Solar System, Milky Way, Universe
|
| Posted: Sat Mar 21, 2009 7:19 pm Post subject: |
|
|
| cheater1034 wrote: | | Gentree wrote: | | cheater1034 wrote: | | Gentree wrote: | | kernelOfTruth wrote: | I haven't kept track of all those changes but I suppose
2.6.28-zen12 and 2.6.29-rc7-zen1 contain the latest reiser4 with fixes ?
thanks for your continued work on this kernel(patchset) |
huh? what fixes? I just started using 2.6.28-zen10 recently and had 70% of my R4 portage partition disappear on me after a power out. Was the R4 patch in this release unstable? |
No, like the other filesystems in zen, reiser4 is always the latest upstream. There is nothing there to make it unstable like that. But, generally speaking, reiser4 is pretty infamous about corrupting data.
| Quote: | | I have been using 2.6.20-nicus for nearly 2 years and have most of my system on R4 since R4 was in beta. This is the first time I have lost ANYTHING on an R4 partition despite frequent browns on power glitches. Very disappointing. |
It seems to have happened to all of us. I've used reiser4 for atleast 2 years, the first time i lost data was back in mid-2008 some time.
|
Reiser4 got a lot of bad press while it was in beta. A lot of ppl used it without sufficient precaution (backup) and then got all flamey and cursed the fs for their own fuckups. They have been flaming ever since. IIRC there were some issues that lingered a bit longer on 64bit systems - which were pretty new at that time.
Linus' principal objection seems to be the idea of plugins and the security implications of having something in the kernel that opens a door in having a plugin interface.
Since Hans decided to get a job breaking rocks he has been out of the loop. This clearly has been detrimental to progress on R4. Your experience with recent breakage starting last year would coincide with my experience and with the rumours that someone(s) who doesn't understand the code has been poking where they should not.
For me the main interest in R4 was it's resistance to power failure which is pretty common here. Uptil now it has saved me from needing to buy a UPS. That was a big plus. Looks like someone has fsck all the hard work that went into making this outstanding fs. |
Switch to btrfs
It doesn't bog down like reiser4, and it has more features (has compression too), and from what I can tell it's the fastest FS i've ever used |
hehe. btrfs isn't even beta. its more than alpha at the moment. an big changes are underway (new version of btrfs will not be able to read old versions of btrfs and so on) |
|
| Back to top |
|
|
broch
Tux's lil' helper
Joined: 09 Jul 2005
Posts: 94
|
| Posted: Sun Mar 22, 2009 12:48 am Post subject: Re: old bug reappeared in zen |
|
|
| broch wrote: | this kills touchpad every few minutes:
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1
psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched.
the above is not present in 2.6.28.8 or 2.6.29-rc8-git4
This problem was firs present in kernels from 2007 I believe.
edit:
hmm actually I see it in 2.6.28.8 now
so I will run longer 2.6.29-rc8-git4 see what will happen |
o.k. so it seems after whole day of running 2.6.29-rc8-git4 that the bug is gone. Hopefully for good this time. |
|
| Back to top |
|
|
ponciarello
Apprentice
Joined: 22 Jul 2008
Posts: 223
Location: beach of slack
|
| Posted: Tue Mar 24, 2009 11:07 am Post subject: |
|
|
I'm running It
| Code: | $ uname -r
2.6.29zen0 |
(sorry, can't resist to say It )
_________________
look for monty python channel on youtube |
|
| Back to top |
|
|
jisakiel
n00b
Joined: 31 May 2003
Posts: 30
|
| Posted: Tue Mar 24, 2009 10:24 pm Post subject: |
|
|
| ponciarello wrote: | | yes, but I think it doesn't make much sense fixing a thing that will be merged with pulls from linus' tree |
Still having that problem as of 2.6.29zen0, I guess the bug might still be in the released 2.6.29?
(just for the record, cross compiling using make-kpkg in an amd64 machine for my eeepc, which is 32 bits... line is DEB_HOST_ARCH=i386 CONCURRENCY_LEVEL=3 make-kpkg --rootcmd fakeroot --arch i386 --cross_compile - --append-to-version=-eee901 linux-image . Haven't yet checked if an amd64 build has the same problems. ). |
|
| Back to top |
|
|
jisakiel
n00b
Joined: 31 May 2003
Posts: 30
|
| Posted: Sat Mar 28, 2009 3:13 am Post subject: |
|
|
| jisakiel wrote: | | ponciarello wrote: | | yes, but I think it doesn't make much sense fixing a thing that will be merged with pulls from linus' tree |
Still having that problem as of 2.6.29zen0, I guess the bug might still be in the released 2.6.29?
(just for the record, cross compiling using make-kpkg in an amd64 machine for my eeepc, which is 32 bits... line is DEB_HOST_ARCH=i386 CONCURRENCY_LEVEL=3 make-kpkg --rootcmd fakeroot --arch i386 --cross_compile - --append-to-version=-eee901 linux-image . Haven't yet checked if an amd64 build has the same problems. ). |
May I be missing something in my config? Still having the problem as of zen1. Both AMD64 and x86 builds (different configs) nevertheless..
Any clues on when is this gonna be patched upstream? I can't compile zen without drivers for my intels! |
|
| Back to top |
|
|
Phlogiston
Veteran
Joined: 27 Jan 2004
Posts: 1925
Location: Europe, Swizerland
|
| Posted: Sat Mar 28, 2009 2:53 pm Post subject: |
|
|
Anyone got fglrx working with latest zen-sources?
_________________
Workstation: 5.1 SurroundSound, LIRC remote control; Laptop [IBM-T43]: patched sources, s2disk/ram, fingerprint sensor |
|
| Back to top |
|
|
unK
l33t
Joined: 06 Feb 2007
Posts: 769
|
| Posted: Sat Mar 28, 2009 3:30 pm Post subject: |
|
|
| Phlogiston wrote: | | Anyone got fglrx working with latest zen-sources? |
By that you mean to compile or to work? I used ati-drivers-8.600 from here, but all I get is black screen after X startup. It works with gentoo-sources-2.6.29 though.
_________________
ncmpcpp - featureful ncurses based MPD client inspired by ncmpc |
|
| Back to top |
|
|
Phlogiston
Veteran
Joined: 27 Jan 2004
Posts: 1925
Location: Europe, Swizerland
|
| Posted: Sat Mar 28, 2009 9:16 pm Post subject: |
|
|
| unK wrote: | | Phlogiston wrote: | | Anyone got fglrx working with latest zen-sources? |
By that you mean to compile or to work? I used ati-drivers-8.600 from here, but all I get is black screen after X startup. It works with gentoo-sources-2.6.29 though. |
worked here with a patch I found on the net... but not 8.600, the version before
_________________
Workstation: 5.1 SurroundSound, LIRC remote control; Laptop [IBM-T43]: patched sources, s2disk/ram, fingerprint sensor |
|
| Back to top |
|
|
rahulthewall
Veteran
Joined: 01 Nov 2007
Posts: 1264
Location: Zürich
|
| Posted: Mon Mar 30, 2009 10:06 pm Post subject: |
|
|
Anyone got their laptop to resume from sleep (all I get is a black screen) on Intel 945GM with 2.6.29 (KMS enabled/disabled and zen-sources) ?
_________________
Who shall guard the guards? |
|
| Back to top |
|
|
hephooey
n00b
Joined: 24 Feb 2003
Posts: 74
|
| Posted: Tue Mar 31, 2009 2:33 am Post subject: |
|
|
| rahulthewall wrote: | | Anyone got their laptop to resume from sleep (all I get is a black screen) on Intel 945GM with 2.6.29 (KMS enabled/disabled and zen-sources) ? |
I also got a black screen with 965GM, no matter if KMS is enabled or not. Everything else works fine though |
|
| Back to top |
|
|
Phlogiston
Veteran
Joined: 27 Jan 2004
Posts: 1925
Location: Europe, Swizerland
|
| Posted: Tue Mar 31, 2009 8:18 am Post subject: |
|
|
I tried switching to readeon driver. Now I can't s2ram anymore, the system freezes on resume, I would say when it wants to switch back to running X.
I'm using the drm and readon module from inside 2.6.29-zen1 and x11-base/xorg-server-1.5.3-r5, x11-drivers/xf86-video-ati-6.12.1. Compositing is not enabled.
_________________
Workstation: 5.1 SurroundSound, LIRC remote control; Laptop [IBM-T43]: patched sources, s2disk/ram, fingerprint sensor |
|
| Back to top |
|
|
manwe_
l33t
Joined: 01 Feb 2006
Posts: 632
Location: Kraków/Cracow, Poland
|
| Posted: Tue Mar 31, 2009 9:18 am Post subject: |
|
|
| Same problem here, system doesn't wake up - black screen, no response on keyboard (even sysrq) or through network. Everything in the newest versions: zen-2.6.29-r1, xorg-server-1.5.3-r5, nvidia-drivers-180.41 and according to post by this guy ( http://www.nvnews.net/vbulletin/showthread.php?t=130796 ) problem is not nvidia-related. |
|
| Back to top |
|
|
|
Unsupported Software
