Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Bernd Schmidt wrote: > One of these appears in my system as well (ASUS P5W-DH Deluxe > mainboard). Here's the hdparm output: Yup, same mainboard here. > Since about 2.6.17 or 2.6.18, it has been causing long delays while > booting: > ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata2.00: qc timeout (cmd 0xec) > ata2.00: failed to IDENTIFY (I/O error, err_mask=0x5) > ata2: port is slow to respond, please be patient (Status 0x80) > ata2: COMRESET failed (errno=-16) > ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133 > ata2.00: 640 sectors, multi 1: LBA > ata2.00: configured for UDMA/133 And yup, same problem with the painful boot delays since 2.6.18. Tejun indicated that a fix would get merged with 2.6.23, but that didn't happen. Here's hoping something makes it into .24! Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote:
> Would it also be possible for you to send along 'hdparm --Istdout'
> output for your config disk thingy, /dev/sdd ?
Sure, just don't ask me what it is! (I've generally assumed that
writing to it would be a bad idea.)
Berck
/dev/sdd:
0040 3fff c837 0010 003f
3030 3030 3030 315f 5f5f 5f5f
5f5f 5f5f 5f30 5f45 0003 3e00 0004 5247
4c31 3033 3634 436f 6e66 6967 2020 4469
736b 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8001
2f00 4000 0200 0007 3fff 0010
003f fc10 00fb 0101 0280 0407
0003 0078 0078 0078 0078
0201
007e 001b 0068 5060 4000 1000 4000
407f fffe c0fe
0002
0001
0017 2040
b4a5
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote:
Would it also be possible for you to send along 'hdparm --Istdout'
output for your config disk thingy, /dev/sdd ?
Sure, just don't ask me what it is! (I've generally assumed that
writing to it would be a bad idea.)
Berck
/dev/sdd:
0040 3fff c837 0010 003f
3030 3030 3030 315f 5f5f 5f5f
5f5f 5f5f 5f30 5f45 0003 3e00 0004 5247
4c31 3033 3634 436f 6e66 6967 2020 4469
736b 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8001
2f00 4000 0200 0007 3fff 0010
003f fc10 00fb 0101 0280 0407
0003 0078 0078 0078 0078
0201
007e 001b 0068 5060 4000 1000 4000
407f fffe c0fe
0002
0001
0017 2040
b4a5
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Bernd Schmidt wrote: One of these appears in my system as well (ASUS P5W-DH Deluxe mainboard). Here's the hdparm output: Yup, same mainboard here. Since about 2.6.17 or 2.6.18, it has been causing long delays while booting: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x5) ata2: port is slow to respond, please be patient (Status 0x80) ata2: COMRESET failed (errno=-16) ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133 ata2.00: 640 sectors, multi 1: LBA ata2.00: configured for UDMA/133 And yup, same problem with the painful boot delays since 2.6.18. Tejun indicated that a fix would get merged with 2.6.23, but that didn't happen. Here's hoping something makes it into .24! Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Berck E. Nash wrote:
> hdparm output attached.
Whoops, it really is this time.
/dev/sde:
427a 3fff 0010 e100 0258 003f
000e 5744 2d57 4d41 4b48 3131 3235
3131 3700 0003 4000 004a 3331
2e30 3846 3331 5744 4320 5744 3336 3047
442d 3030 464c 4132 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
2f00 4001 0280 0007 3fff 0010
003f fc10 00fb 0110 44e0 044f 0007
0003 0078 0078 0078 0078
001f 0202
007e 74eb 7f63 4003 74e9 3e43 4003
407f 80fe
44e0 044f
0001 0141 0746
0002 0001
001f
001f
8da5
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote: > Can you tell me something about this device? > > [ 49.045635] ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133 > [ 49.051677] ata2.00: 640 sectors, multi 1: LBA > [ 49.056321] ata2.00: configured for UDMA/133 > > It seems like it does not support the 'check power mode' command. > > Can you post a text file attachment, containing the output of 'hdparm > --Istdout' ? No problem. The device in question is a Western Digital Raptor WD360GD 36.7GB 10,000 RPM Serial ATA150 Hard Drive. hdparm output attached. Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote: > Once the blame has been squared fixed upon me :) you can use git-bisect > to locate the precise change that broke your setup. Okay, here's the problem: 268fe6f9f15551be9abedd44a237392675d529d5 is first bad commit commit 268fe6f9f15551be9abedd44a237392675d529d5 Author: Jeff Garzik <[EMAIL PROTECTED]> Date: Fri Sep 21 07:09:36 2007 -0400 [libata] SCSI: simple TEST UNIT READY simulation It's trivial to ping the device, and that's a much more sane behavior than no-op. Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]> :04 04 44d34cdad073bd623545b8239aca9a113652c6d0 df6d21f7ce56a4e796f8f856c1f647b0395ab4df M drivers Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jens Axboe wrote: > On Tue, Sep 25 2007, Berck E. Nash wrote: >> Jeff Garzik wrote: >> >>> The first step would be to clone the "upstream" branch of >>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git >>> >>> and see if the problem is reproducible there. If yes, then you have >>> narrowed down the problem to something my ATA devel tree has introduced >>> into -mm. >> Nope, you're off the hook. The libata tree works great, so it must be >> something else in -mm conflicting. Whoops, sorry! I just lied. I'm a git newbie, and failed to actually get the "upstream" branch the first time, so rc8 is clean, but it fails when I actually pull the upstream branch. I'll git bisect and get back to you. BErck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote: > The first step would be to clone the "upstream" branch of > git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git > > and see if the problem is reproducible there. If yes, then you have > narrowed down the problem to something my ATA devel tree has introduced > into -mm. Nope, you're off the hook. The libata tree works great, so it must be something else in -mm conflicting. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote: The first step would be to clone the upstream branch of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git and see if the problem is reproducible there. If yes, then you have narrowed down the problem to something my ATA devel tree has introduced into -mm. Nope, you're off the hook. The libata tree works great, so it must be something else in -mm conflicting. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jens Axboe wrote: On Tue, Sep 25 2007, Berck E. Nash wrote: Jeff Garzik wrote: The first step would be to clone the upstream branch of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git and see if the problem is reproducible there. If yes, then you have narrowed down the problem to something my ATA devel tree has introduced into -mm. Nope, you're off the hook. The libata tree works great, so it must be something else in -mm conflicting. Whoops, sorry! I just lied. I'm a git newbie, and failed to actually get the upstream branch the first time, so rc8 is clean, but it fails when I actually pull the upstream branch. I'll git bisect and get back to you. BErck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote: Once the blame has been squared fixed upon me :) you can use git-bisect to locate the precise change that broke your setup. Okay, here's the problem: 268fe6f9f15551be9abedd44a237392675d529d5 is first bad commit commit 268fe6f9f15551be9abedd44a237392675d529d5 Author: Jeff Garzik [EMAIL PROTECTED] Date: Fri Sep 21 07:09:36 2007 -0400 [libata] SCSI: simple TEST UNIT READY simulation It's trivial to ping the device, and that's a much more sane behavior than no-op. Signed-off-by: Jeff Garzik [EMAIL PROTECTED] :04 04 44d34cdad073bd623545b8239aca9a113652c6d0 df6d21f7ce56a4e796f8f856c1f647b0395ab4df M drivers Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Jeff Garzik wrote: Can you tell me something about this device? [ 49.045635] ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133 [ 49.051677] ata2.00: 640 sectors, multi 1: LBA [ 49.056321] ata2.00: configured for UDMA/133 It seems like it does not support the 'check power mode' command. Can you post a text file attachment, containing the output of 'hdparm --Istdout' ? No problem. The device in question is a Western Digital Raptor WD360GD 36.7GB 10,000 RPM Serial ATA150 Hard Drive. hdparm output attached. Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Berck E. Nash wrote:
hdparm output attached.
Whoops, it really is this time.
/dev/sde:
427a 3fff 0010 e100 0258 003f
000e 5744 2d57 4d41 4b48 3131 3235
3131 3700 0003 4000 004a 3331
2e30 3846 3331 5744 4320 5744 3336 3047
442d 3030 464c 4132 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
2f00 4001 0280 0007 3fff 0010
003f fc10 00fb 0110 44e0 044f 0007
0003 0078 0078 0078 0078
001f 0202
007e 74eb 7f63 4003 74e9 3e43 4003
407f 80fe
44e0 044f
0001 0141 0746
0002 0001
001f
001f
8da5
cpufreq scaling appears not to work on overclocked systems
This is not new, but exists as far back as 2.6.17. I haven't reported it before because I figured that surely someone else had noticed it, but since it's still unfixed and I cannot find any mention of it on LKML, here we go. I'm running a Core2 Duo 1.86GHz overclocked to 2.56GHz. Everything is normal with cpufreq scaling disabled. With cpufreq scaling enabled in the kernel, using any governor, /proc/cpuinfo indicates a maximum of the rated frequency rather than the actual frequency. Here it is under 100% utilization, with userspace governor and powernowd: [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping: 6 cpu MHz : 1862.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5134.39 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping: 6 cpu MHz : 1862.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5131.64 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: At idle it drops down to 1596.000 MHz reported. At boot the kernel doest report the correct frequency (2564.907), which agrees with the bogomips reported by /proc/cpuinfo as well. I haven't done any benchmarking to try to determine if perhaps freq scaling works as it should and just the reported frequency is incorrect. Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.23-rc1-mm1 compile error in function `acpi_pci_choose_state':
drivers/built-in.o: In function `acpi_pci_choose_state': pci-acpi.c:(.text+0xdccf): undefined reference to `acpi_pm_device_sleep_state' drivers/built-in.o: In function `pnpacpi_suspend': core.c:(.text+0x35a7c): undefined reference to `acpi_pm_device_sleep_state' Config file attached. # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc1-mm1 # Sun Jul 29 09:14:48 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_NR_QUICK=2 CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set CONFIG_AUDIT=y # CONFIG_AUDITSYSCALL is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 # CONFIG_CONTAINERS is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_CONTAINER_NS is not set # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=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_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_BLK_DEV_BSG=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y # CONFIG_IOSCHED_AS is not set # CONFIG_IOSCHED_DEADLINE is not set CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # # CONFIG_TICK_ONESHOT is not set CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set # CONFIG_MK8 is not set # CONFIG_MPSC is not set CONFIG_MCORE2=y # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_HT=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_NR_CPUS=2 CONFIG_PHYSICAL_ALIGN=0x20 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y # CONFIG_X86_MCE_AMD is not set # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_START=0x20 # CONFIG_SECCOMP is not set # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set CONFIG_HZ_300=y # CONFIG_HZ_1000 is not set CONFIG_HZ=300 CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y CONFIG_PM_LEGACY=y # CONFIG_PM_DEBUG is not set CONFIG_ACPI=y CONFIG_ACPI_PROCFS=y # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y # CONFIG_ACPI_FAN is not set # CONFIG_ACPI_DOCK is not set
2.6.23-rc1-mm1 compile error in function `acpi_pci_choose_state':
drivers/built-in.o: In function `acpi_pci_choose_state': pci-acpi.c:(.text+0xdccf): undefined reference to `acpi_pm_device_sleep_state' drivers/built-in.o: In function `pnpacpi_suspend': core.c:(.text+0x35a7c): undefined reference to `acpi_pm_device_sleep_state' Config file attached. # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc1-mm1 # Sun Jul 29 09:14:48 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_NR_QUICK=2 CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set CONFIG_AUDIT=y # CONFIG_AUDITSYSCALL is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 # CONFIG_CONTAINERS is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_CONTAINER_NS is not set # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=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_VM_EVENT_COUNTERS=y CONFIG_SLAB=y # CONFIG_SLUB is not set # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_BLK_DEV_BSG=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y # CONFIG_IOSCHED_AS is not set # CONFIG_IOSCHED_DEADLINE is not set CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq # # Processor type and features # # CONFIG_TICK_ONESHOT is not set CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set # CONFIG_MK8 is not set # CONFIG_MPSC is not set CONFIG_MCORE2=y # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_HT=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_NR_CPUS=2 CONFIG_PHYSICAL_ALIGN=0x20 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y # CONFIG_X86_MCE_AMD is not set # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_START=0x20 # CONFIG_SECCOMP is not set # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set CONFIG_HZ_300=y # CONFIG_HZ_1000 is not set CONFIG_HZ=300 CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y CONFIG_PM_LEGACY=y # CONFIG_PM_DEBUG is not set CONFIG_ACPI=y CONFIG_ACPI_PROCFS=y # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y # CONFIG_ACPI_FAN is not set # CONFIG_ACPI_DOCK is not set CONFIG_ACPI_PROCESSOR=y
cpufreq scaling appears not to work on overclocked systems
This is not new, but exists as far back as 2.6.17. I haven't reported it before because I figured that surely someone else had noticed it, but since it's still unfixed and I cannot find any mention of it on LKML, here we go. I'm running a Core2 Duo 1.86GHz overclocked to 2.56GHz. Everything is normal with cpufreq scaling disabled. With cpufreq scaling enabled in the kernel, using any governor, /proc/cpuinfo indicates a maximum of the rated frequency rather than the actual frequency. Here it is under 100% utilization, with userspace governor and powernowd: [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping: 6 cpu MHz : 1862.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5134.39 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping: 6 cpu MHz : 1862.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5131.64 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: At idle it drops down to 1596.000 MHz reported. At boot the kernel doest report the correct frequency (2564.907), which agrees with the bogomips reported by /proc/cpuinfo as well. I haven't done any benchmarking to try to determine if perhaps freq scaling works as it should and just the reported frequency is incorrect. Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Linux 2.6.21.3] CDRW drive not recognised by PATA (ata_piix)
I complained about this very problem months ago. Tejun Heo responded
with the attached patch which does indeed fix the problem for me.
Unfortunately, this patch hasn't made it into the kernel yet. I have no
idea why.
diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
index dc42ba1..6e7775a 100644
--- a/drivers/ata/ata_piix.c
+++ b/drivers/ata/ata_piix.c
@@ -105,7 +105,8 @@ enum {
PIIX_FLAG_AHCI = (1 << 27), /* AHCI possible */
PIIX_FLAG_CHECKINTR = (1 << 28), /* make sure PCI INTx enabled */
- PIIX_PATA_FLAGS = ATA_FLAG_SLAVE_POSS,
+ PIIX_PATA_FLAGS = ATA_FLAG_SLAVE_POSS |
+ ATA_FLAG_SETXFER_POLLING,
PIIX_SATA_FLAGS = ATA_FLAG_SATA | PIIX_FLAG_CHECKINTR,
/* combined mode. if set, PATA is channel 0.
Re: [Linux 2.6.21.3] CDRW drive not recognised by PATA (ata_piix)
I complained about this very problem months ago. Tejun Heo responded
with the attached patch which does indeed fix the problem for me.
Unfortunately, this patch hasn't made it into the kernel yet. I have no
idea why.
diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
index dc42ba1..6e7775a 100644
--- a/drivers/ata/ata_piix.c
+++ b/drivers/ata/ata_piix.c
@@ -105,7 +105,8 @@ enum {
PIIX_FLAG_AHCI = (1 27), /* AHCI possible */
PIIX_FLAG_CHECKINTR = (1 28), /* make sure PCI INTx enabled */
- PIIX_PATA_FLAGS = ATA_FLAG_SLAVE_POSS,
+ PIIX_PATA_FLAGS = ATA_FLAG_SLAVE_POSS |
+ ATA_FLAG_SETXFER_POLLING,
PIIX_SATA_FLAGS = ATA_FLAG_SATA | PIIX_FLAG_CHECKINTR,
/* combined mode. if set, PATA is channel 0.
2.6.22-rc3-mm1 reiser4 bug
All appears to work fine, until I try to boot a kernel with a Reiser4 / partition. Then I get endless errors of the sort: [ 206.349450] sd 1:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK (See attached dmesg for more, I only sent the first 1,000 lines, it goes on until a hard reboot.) The same partition and the same kernel work great as long as that partition isn't the current system root. The same kernel and the same hard drive works fine as long as the partition is formatted ReiserFS. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.22-rc3-mm1 reiser4 bug
All appears to work fine, until I try to boot a kernel with a Reiser4 / partition. Then I get endless errors of the sort: [ 206.349450] sd 1:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK (See attached dmesg for more, I only sent the first 1,000 lines, it goes on until a hard reboot.) The same partition and the same kernel work great as long as that partition isn't the current system root. The same kernel and the same hard drive works fine as long as the partition is formatted ReiserFS. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Tejun Heo wrote: > Hmmm... Once properly initialized, ahci is highly unlikely to cause > runaway IRQs which results in nobody cared. It has proper IRQ mask and > pending bits allowing the driver to reliably detect when and why the > controller is raising interrupt and disable it if necessary. Can you > try without the NVIDIA module? I'm beginning to think it was a one-time hardware error of some sort. I've been running 2.6.21-rc7-mm2 for awhile now and the problem hasn't reoccurred, so I think you can consider the matter settled... Thanks, Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Tejun Heo wrote: Hmmm... Once properly initialized, ahci is highly unlikely to cause runaway IRQs which results in nobody cared. It has proper IRQ mask and pending bits allowing the driver to reliably detect when and why the controller is raising interrupt and disable it if necessary. Can you try without the NVIDIA module? I'm beginning to think it was a one-time hardware error of some sort. I've been running 2.6.21-rc7-mm2 for awhile now and the problem hasn't reoccurred, so I think you can consider the matter settled... Thanks, Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Tejun Heo wrote: > Please test this one instead. Thanks. Yup, the second patch fixes it. -Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Tejun Heo wrote: Please test this one instead. Thanks. Yup, the second patch fixes it. -Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Kernel panic on boot, console output attached. [14316256.221707] Linux version 2.6.21-rc7-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Apr 24 12:09:02 MDT 2007 [14316256.221707] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [14316256.221707] BIOS-provided physical RAM map: [14316256.221707] BIOS-e820: - 0009fc00 (usable) [14316256.221707] BIOS-e820: 0009fc00 - 000a (reserved) [14316256.221707] BIOS-e820: 000e4000 - 0010 (reserved) [14316256.221707] BIOS-e820: 0010 - 3ff8 (usable) [14316256.221707] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [14316256.221707] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [14316256.221707] BIOS-e820: 3ffe - 4000 (reserved) [14316256.221707] BIOS-e820: ffb0 - 0001 (reserved) [14316256.221707] end_pfn_map = 1048576 [14316256.221707] DMI 2.4 present. [14316256.221707] ACPI: RSDP 000FAF20, 0024 (r2 ACPIAM) [14316256.221707] ACPI: XSDT 3FF80100, 0064 (r1 NEC 1000724 MSFT 97) [14316256.221707] ACPI: FACP 3FF80290, 00F4 (r3 A_M_I_ OEMFACP 1000724 MSFT 97) [14316256.221707] ACPI: DSDT 3FF80590, 9560 (r1 A0543 A05430000 INTL 20060113) [14316256.221707] ACPI: FACS 3FF8E000, 0040 [14316256.221707] ACPI: APIC 3FF80390, 0080 (r1 A_M_I_ OEMAPIC 1000724 MSFT 97) [14316256.221707] ACPI: SLIC 3FF80410, 0176 (r1 NEC 1000724 MSFT 97) [14316256.221707] ACPI: OEMB 3FF8E040, 0066 (r1 A_M_I_ AMI_OEM 1000724 MSFT 97) [14316256.221707] ACPI: HPET 3FF89AF0, 0038 (r1 A_M_I_ OEMHPET 1000724 MSFT 97) [14316256.221707] ACPI: MCFG 3FF89B30, 003C (r1 A_M_I_ OEMMCFG 1000724 MSFT 97) [14316256.221707] ACPI: SSDT 3FF8E0B0, 01C6 (r1AMI CPU1PM1 INTL 20060113) [14316256.221707] ACPI: SSDT 3FF8E280, 013A (r1AMI CPU2PM1 INTL 20060113) [14316256.221707] Zone PFN ranges: [14316256.221707] DMA 0 -> 4096 [14316256.221707] DMA324096 -> 1048576 [14316256.221707] Normal1048576 -> 1048576 [14316256.221707] Movable zone start PFN for each node [14316256.221707] early_node_map[2] active PFN ranges [14316256.221707] 0:0 -> 159 [14316256.221707] 0: 256 -> 262016 [14316256.221707] ACPI: PM-Timer IO Port: 0x808 [14316256.221707] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [14316256.221707] Processor #0 (Bootup-CPU) [14316256.221707] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [14316256.221707] Processor #1 [14316256.221707] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [14316256.221707] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [14316256.221707] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [14316256.221707] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [14316256.221707] Setting APIC routing to flat [14316256.221707] ACPI: HPET id: 0x8086a201 base: 0xfed0 [14316256.221707] Using ACPI (MADT) for SMP configuration information [14316256.221707] Allocating PCI resources starting at 5000 (gap: 4000:bfb0) [14316256.221707] PERCPU: Allocating 32896 bytes of per cpu data [14316256.221707] Built 1 zonelists, mobility grouping on. Total pages: 257236 [14316256.221707] Kernel command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [14316256.221707] Initializing CPU#0 [14316256.221707] PID hash table entries: 4096 (order: 12, 32768 bytes) [14316256.221707] time.c: Detected 2564.902 MHz processor. [14316256.231707] Console: colour VGA+ 80x25 [14316256.235040] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [14316256.235040] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [14316256.235040] Checking aperture... [14316256.241707] Memory: 1026888k/1048064k available (2355k kernel code, 20620k reserved, 1490k data, 212k init) [14316256.325040] Calibrating delay using timer specific routine.. 5134.38 BogoMIPS (lpj=8554219) [14316256.325040] Mount-cache hash table entries: 256 [14316256.325040] CPU: L1 I cache: 32K, L1 D cache: 32K [14316256.325040] CPU: L2 cache: 2048K [14316256.325040] using mwait in idle threads. [14316256.325040] CPU: Physical Processor ID: 0 [14316256.325040] CPU: Processor Core ID: 0 [14316256.325040] CPU0: Thermal monitoring enabled (TM2) [14316256.325040] Freeing SMP alternatives: 26k freed [14316256.325040] ACPI: Core revision 20070126 [14316256.361707] Using local APIC timer interrupts. [14316256.361707] result 22900897 [14316256.361707]
2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Kernel panic on boot, console output attached. [14316256.221707] Linux version 2.6.21-rc7-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Apr 24 12:09:02 MDT 2007 [14316256.221707] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [14316256.221707] BIOS-provided physical RAM map: [14316256.221707] BIOS-e820: - 0009fc00 (usable) [14316256.221707] BIOS-e820: 0009fc00 - 000a (reserved) [14316256.221707] BIOS-e820: 000e4000 - 0010 (reserved) [14316256.221707] BIOS-e820: 0010 - 3ff8 (usable) [14316256.221707] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [14316256.221707] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [14316256.221707] BIOS-e820: 3ffe - 4000 (reserved) [14316256.221707] BIOS-e820: ffb0 - 0001 (reserved) [14316256.221707] end_pfn_map = 1048576 [14316256.221707] DMI 2.4 present. [14316256.221707] ACPI: RSDP 000FAF20, 0024 (r2 ACPIAM) [14316256.221707] ACPI: XSDT 3FF80100, 0064 (r1 NEC 1000724 MSFT 97) [14316256.221707] ACPI: FACP 3FF80290, 00F4 (r3 A_M_I_ OEMFACP 1000724 MSFT 97) [14316256.221707] ACPI: DSDT 3FF80590, 9560 (r1 A0543 A05430000 INTL 20060113) [14316256.221707] ACPI: FACS 3FF8E000, 0040 [14316256.221707] ACPI: APIC 3FF80390, 0080 (r1 A_M_I_ OEMAPIC 1000724 MSFT 97) [14316256.221707] ACPI: SLIC 3FF80410, 0176 (r1 NEC 1000724 MSFT 97) [14316256.221707] ACPI: OEMB 3FF8E040, 0066 (r1 A_M_I_ AMI_OEM 1000724 MSFT 97) [14316256.221707] ACPI: HPET 3FF89AF0, 0038 (r1 A_M_I_ OEMHPET 1000724 MSFT 97) [14316256.221707] ACPI: MCFG 3FF89B30, 003C (r1 A_M_I_ OEMMCFG 1000724 MSFT 97) [14316256.221707] ACPI: SSDT 3FF8E0B0, 01C6 (r1AMI CPU1PM1 INTL 20060113) [14316256.221707] ACPI: SSDT 3FF8E280, 013A (r1AMI CPU2PM1 INTL 20060113) [14316256.221707] Zone PFN ranges: [14316256.221707] DMA 0 - 4096 [14316256.221707] DMA324096 - 1048576 [14316256.221707] Normal1048576 - 1048576 [14316256.221707] Movable zone start PFN for each node [14316256.221707] early_node_map[2] active PFN ranges [14316256.221707] 0:0 - 159 [14316256.221707] 0: 256 - 262016 [14316256.221707] ACPI: PM-Timer IO Port: 0x808 [14316256.221707] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [14316256.221707] Processor #0 (Bootup-CPU) [14316256.221707] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [14316256.221707] Processor #1 [14316256.221707] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [14316256.221707] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [14316256.221707] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [14316256.221707] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [14316256.221707] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [14316256.221707] Setting APIC routing to flat [14316256.221707] ACPI: HPET id: 0x8086a201 base: 0xfed0 [14316256.221707] Using ACPI (MADT) for SMP configuration information [14316256.221707] Allocating PCI resources starting at 5000 (gap: 4000:bfb0) [14316256.221707] PERCPU: Allocating 32896 bytes of per cpu data [14316256.221707] Built 1 zonelists, mobility grouping on. Total pages: 257236 [14316256.221707] Kernel command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [14316256.221707] Initializing CPU#0 [14316256.221707] PID hash table entries: 4096 (order: 12, 32768 bytes) [14316256.221707] time.c: Detected 2564.902 MHz processor. [14316256.231707] Console: colour VGA+ 80x25 [14316256.235040] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [14316256.235040] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [14316256.235040] Checking aperture... [14316256.241707] Memory: 1026888k/1048064k available (2355k kernel code, 20620k reserved, 1490k data, 212k init) [14316256.325040] Calibrating delay using timer specific routine.. 5134.38 BogoMIPS (lpj=8554219) [14316256.325040] Mount-cache hash table entries: 256 [14316256.325040] CPU: L1 I cache: 32K, L1 D cache: 32K [14316256.325040] CPU: L2 cache: 2048K [14316256.325040] using mwait in idle threads. [14316256.325040] CPU: Physical Processor ID: 0 [14316256.325040] CPU: Processor Core ID: 0 [14316256.325040] CPU0: Thermal monitoring enabled (TM2) [14316256.325040] Freeing SMP alternatives: 26k freed [14316256.325040] ACPI: Core revision 20070126 [14316256.361707] Using local APIC timer interrupts. [14316256.361707] result 22900897 [14316256.361707] Detected
2.6.20-mm1 USB-related OOPS
I get the following OOPS on boot, presumably connected with USB driver loading. I've attached the entire log. Please CC on replies as I'm not subscribed. [ 149.525742] Unable to handle kernel NULL pointer dereference at 0008 RIP: [ 149.531302] [] :cdc_acm:acm_probe+0x1dd/0x741 [ 149.539958] PGD 3d248067 PUD 3d23c067 PMD 0 [ 149.544431] Oops: [1] PREEMPT SMP [ 149.548475] last sysfs file: /class/net/lo/operstate [ 149.553510] CPU 0 [ 149.555618] Modules linked in: cdc_acm snd_rtctimer w83627ehf eeprom i2c_isa nvidia(P) usb_storage usbhid 8139cp snd_hda_intel snd_hda_codec snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_timer snd_seq_device snd 8139too uhci_hcd mii soundcore snd_page_alloc i2c_i801 evdev usbcore i2c_core floppy [ 149.587337] Pid: 1620, comm: modprobe Tainted: P 2.6.20-mm1 #3 [ 149.593785] RIP: 0010:[] [] :cdc_acm:acm_probe+0x1dd/0x741 [ 149.602650] RSP: 0018:81003df29c98 EFLAGS: 00010246 [ 149.608045] RAX: 81003eb14800 RBX: 81003eb14820 RCX: 81003eb21008 [ 149.615278] RDX: 81003eb14800 RSI: RDI: [ 149.622507] RBP: R08: 0001 R09: 0d80 [ 149.629730] R10: R11: c219a7f8 R12: 0d80 [ 149.636960] R13: 81003f555800 R14: R15: 81003eb14800 [ 149.644183] FS: 2abc668716d0() GS:80544000() knlGS: [ 149.652393] CS: 0010 DS: ES: CR0: 8005003b [ 149.658217] CR2: 0008 CR3: 3d25d000 CR4: 06e0 [ 149.665458] Process modprobe (pid: 1620, threadinfo 81003df28000, task 81003eeb0950) [ 149.674014] Stack: 81003d21af20 81003eb14800 81003edf3418 81003d21af20 [ 149.682317] fff4 81003d4e3820 00ff804db922 0001 [ 149.689981] 00100db0 81003d21af20 8801cbe5 81003eb14820 [ 149.697455] Call Trace: [ 149.700194] [] :usbcore:usb_match_one_id+0x26/0x84 [ 149.706742] [] :usbcore:usb_probe_interface+0x7d/0xa5 [ 149.713544] [] driver_probe_device+0xf6/0x17f [ 149.719654] [] __driver_attach+0x0/0x93 [ 149.725230] [] __driver_attach+0x5a/0x93 [ 149.730893] [] bus_for_each_dev+0x43/0x6e [ 149.736644] [] bus_add_driver+0x6b/0x18d [ 149.742310] [] :usbcore:usb_register_driver+0x85/0xeb [ 149.749113] [] :cdc_acm:acm_init+0xcc/0x105 [ 149.755037] [] sys_init_module+0x1572/0x16d2 [ 149.761058] [] system_call+0x7e/0x83 [ 149.766361] [ 149.767898] [ 149.767898] Code: 49 8b 46 08 80 78 05 0a 74 17 49 8b 47 08 80 78 05 0a 0f 85 [ 149.777661] RIP [] :cdc_acm:acm_probe+0x1dd/0x741 [ 149.784146] RSP [ 149.787694] CR2: 0008 [0.00] Linux version 2.6.20-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 SMP PREEMPT Fri Feb 16 17:31:24 MST 2007 [0.00] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ff8 (usable) [0.00] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [0.00] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [0.00] BIOS-e820: 3ffe - 4000 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.4 present. [0.00] ACPI: RSDP 000FAF20, 0024 (r2 ACPIAM) [0.00] ACPI: XSDT 3FF80100, 0064 (r1 NEC 1000724 MSFT 97) [0.00] ACPI: FACP 3FF80290, 00F4 (r3 A_M_I_ OEMFACP 1000724 MSFT 97) [0.00] ACPI: DSDT 3FF80590, 9560 (r1 A0543 A05430000 INTL 20060113) [0.00] ACPI: FACS 3FF8E000, 0040 [0.00] ACPI: APIC 3FF80390, 0080 (r1 A_M_I_ OEMAPIC 1000724 MSFT 97) [0.00] ACPI: SLIC 3FF80410, 0176 (r1 NEC 1000724 MSFT 97) [0.00] ACPI: OEMB 3FF8E040, 0066 (r1 A_M_I_ AMI_OEM 1000724 MSFT 97) [0.00] ACPI: HPET 3FF89AF0, 0038 (r1 A_M_I_ OEMHPET 1000724 MSFT 97) [0.00] ACPI: MCFG 3FF89B30, 003C (r1 A_M_I_ OEMMCFG 1000724 MSFT 97) [0.00] ACPI: SSDT 3FF8E0B0, 01C6 (r1AMI CPU1PM1 INTL 20060113) [0.00] ACPI: SSDT 3FF8E280, 013A (r1AMI CPU2PM1 INTL 20060113) [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00]
2.6.20-mm1 USB-related OOPS
I get the following OOPS on boot, presumably connected with USB driver loading. I've attached the entire log. Please CC on replies as I'm not subscribed. [ 149.525742] Unable to handle kernel NULL pointer dereference at 0008 RIP: [ 149.531302] [8887eec3] :cdc_acm:acm_probe+0x1dd/0x741 [ 149.539958] PGD 3d248067 PUD 3d23c067 PMD 0 [ 149.544431] Oops: [1] PREEMPT SMP [ 149.548475] last sysfs file: /class/net/lo/operstate [ 149.553510] CPU 0 [ 149.555618] Modules linked in: cdc_acm snd_rtctimer w83627ehf eeprom i2c_isa nvidia(P) usb_storage usbhid 8139cp snd_hda_intel snd_hda_codec snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_timer snd_seq_device snd 8139too uhci_hcd mii soundcore snd_page_alloc i2c_i801 evdev usbcore i2c_core floppy [ 149.587337] Pid: 1620, comm: modprobe Tainted: P 2.6.20-mm1 #3 [ 149.593785] RIP: 0010:[8887eec3] [8887eec3] :cdc_acm:acm_probe+0x1dd/0x741 [ 149.602650] RSP: 0018:81003df29c98 EFLAGS: 00010246 [ 149.608045] RAX: 81003eb14800 RBX: 81003eb14820 RCX: 81003eb21008 [ 149.615278] RDX: 81003eb14800 RSI: RDI: [ 149.622507] RBP: R08: 0001 R09: 0d80 [ 149.629730] R10: R11: c219a7f8 R12: 0d80 [ 149.636960] R13: 81003f555800 R14: R15: 81003eb14800 [ 149.644183] FS: 2abc668716d0() GS:80544000() knlGS: [ 149.652393] CS: 0010 DS: ES: CR0: 8005003b [ 149.658217] CR2: 0008 CR3: 3d25d000 CR4: 06e0 [ 149.665458] Process modprobe (pid: 1620, threadinfo 81003df28000, task 81003eeb0950) [ 149.674014] Stack: 81003d21af20 81003eb14800 81003edf3418 81003d21af20 [ 149.682317] fff4 81003d4e3820 00ff804db922 0001 [ 149.689981] 00100db0 81003d21af20 8801cbe5 81003eb14820 [ 149.697455] Call Trace: [ 149.700194] [8801cbe5] :usbcore:usb_match_one_id+0x26/0x84 [ 149.706742] [8801d78e] :usbcore:usb_probe_interface+0x7d/0xa5 [ 149.713544] [8039ac88] driver_probe_device+0xf6/0x17f [ 149.719654] [8039ad94] __driver_attach+0x0/0x93 [ 149.725230] [8039adee] __driver_attach+0x5a/0x93 [ 149.730893] [8039a14e] bus_for_each_dev+0x43/0x6e [ 149.736644] [8039a48e] bus_add_driver+0x6b/0x18d [ 149.742310] [8801d2b0] :usbcore:usb_register_driver+0x85/0xeb [ 149.749113] [880560cc] :cdc_acm:acm_init+0xcc/0x105 [ 149.755037] [8028dd0b] sys_init_module+0x1572/0x16d2 [ 149.761058] [802561ce] system_call+0x7e/0x83 [ 149.766361] [ 149.767898] [ 149.767898] Code: 49 8b 46 08 80 78 05 0a 74 17 49 8b 47 08 80 78 05 0a 0f 85 [ 149.777661] RIP [8887eec3] :cdc_acm:acm_probe+0x1dd/0x741 [ 149.784146] RSP 81003df29c98 [ 149.787694] CR2: 0008 [0.00] Linux version 2.6.20-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 SMP PREEMPT Fri Feb 16 17:31:24 MST 2007 [0.00] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ff8 (usable) [0.00] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [0.00] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [0.00] BIOS-e820: 3ffe - 4000 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.4 present. [0.00] ACPI: RSDP 000FAF20, 0024 (r2 ACPIAM) [0.00] ACPI: XSDT 3FF80100, 0064 (r1 NEC 1000724 MSFT 97) [0.00] ACPI: FACP 3FF80290, 00F4 (r3 A_M_I_ OEMFACP 1000724 MSFT 97) [0.00] ACPI: DSDT 3FF80590, 9560 (r1 A0543 A05430000 INTL 20060113) [0.00] ACPI: FACS 3FF8E000, 0040 [0.00] ACPI: APIC 3FF80390, 0080 (r1 A_M_I_ OEMAPIC 1000724 MSFT 97) [0.00] ACPI: SLIC 3FF80410, 0176 (r1 NEC 1000724 MSFT 97) [0.00] ACPI: OEMB 3FF8E040, 0066 (r1 A_M_I_ AMI_OEM 1000724 MSFT 97) [0.00] ACPI: HPET 3FF89AF0, 0038 (r1 A_M_I_ OEMHPET 1000724 MSFT 97) [0.00] ACPI: MCFG 3FF89B30, 003C (r1 A_M_I_ OEMMCFG 1000724 MSFT 97) [0.00] ACPI: SSDT 3FF8E0B0, 01C6 (r1AMI CPU1PM1 INTL 20060113) [0.00] ACPI: SSDT 3FF8E280, 013A (r1AMI CPU2PM1 INTL 20060113) [0.00] Zone PFN
Re: 2.6.18 - AHCI detection pauses excessively
Tejun Heo wrote: > Berck E. Nash wrote: >> [ 68.242305] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> [ 98.221334] ata2.00: qc timeout (cmd 0xec) >> [ 98.225467] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) >> [ 108.063137] ata2: port is slow to respond, please be patient (Status 0x80) >> [ 131.003980] ata2: port failed to respond (30 secs, Status 0x80) >> [ 131.009930] ata2: COMRESET failed (device not ready) >> [ 131.014926] ata2: hardreset failed, retrying in 5 secs >> [ 138.308717] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >> [ 138.319554] ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA >> [ 138.325157] ata2.00: ata2: dev 0 multi count 1 >> [ 138.334245] ata2.00: configured for UDMA/133 > [--snip--] >> [ 143.191590] scsi 2:0:0:0: Direct-Access ATA Config Disk >> RGL1 PQ: 0 ANSI: 5 >> [ 143.199761] SCSI device sdd: 640 512-byte hdwr sectors (0 MB) >> [ 143.205550] sdd: Write Protect is off >> [ 143.209257] SCSI device sdd: write cache: disabled, read cache: enabled, >> doesn't support DPO or FUA >> [ 143.218356] SCSI device sdd: 640 512-byte hdwr sectors (0 MB) >> [ 143.224143] sdd: Write Protect is off >> [ 143.227847] SCSI device sdd: write cache: disabled, read cache: enabled, >> doesn't support DPO or FUA >> [ 143.236927] sdd: unknown partition table >> [ 143.241194] sd 2:0:0:0: Attached scsi disk sdd >> [ 143.245707] sd 2:0:0:0: Attached scsi generic sg3 type 0 > > Ahh.. I can't believe I missed this again. A Port Multiplier is > attached to your ata2 which is probably a sil3726 or 4726. Why this > device fails initial reset is unknown yet. Anyways, with proper PMP > support, this problem will go away. So, this isn't really a ahci issue > and there's nothing wrong with your disks either. I'll ask SIMG why > this happens with the PMP. Hrm. It's not a Silicon Image chip, or at least doesn't claim to be: 00:1f.2 SATA controller: Intel Corporation 82801GR/GH (ICH7 Family) Serial ATA Storage Controller AHCI (rev 01) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 2606 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.18 - AHCI detection pauses excessively
Tejun Heo wrote: Berck E. Nash wrote: [ 68.242305] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 98.221334] ata2.00: qc timeout (cmd 0xec) [ 98.225467] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104) [ 108.063137] ata2: port is slow to respond, please be patient (Status 0x80) [ 131.003980] ata2: port failed to respond (30 secs, Status 0x80) [ 131.009930] ata2: COMRESET failed (device not ready) [ 131.014926] ata2: hardreset failed, retrying in 5 secs [ 138.308717] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 138.319554] ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA [ 138.325157] ata2.00: ata2: dev 0 multi count 1 [ 138.334245] ata2.00: configured for UDMA/133 [--snip--] [ 143.191590] scsi 2:0:0:0: Direct-Access ATA Config Disk RGL1 PQ: 0 ANSI: 5 [ 143.199761] SCSI device sdd: 640 512-byte hdwr sectors (0 MB) [ 143.205550] sdd: Write Protect is off [ 143.209257] SCSI device sdd: write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 143.218356] SCSI device sdd: 640 512-byte hdwr sectors (0 MB) [ 143.224143] sdd: Write Protect is off [ 143.227847] SCSI device sdd: write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 143.236927] sdd: unknown partition table [ 143.241194] sd 2:0:0:0: Attached scsi disk sdd [ 143.245707] sd 2:0:0:0: Attached scsi generic sg3 type 0 Ahh.. I can't believe I missed this again. A Port Multiplier is attached to your ata2 which is probably a sil3726 or 4726. Why this device fails initial reset is unknown yet. Anyways, with proper PMP support, this problem will go away. So, this isn't really a ahci issue and there's nothing wrong with your disks either. I'll ask SIMG why this happens with the PMP. Hrm. It's not a Silicon Image chip, or at least doesn't claim to be: 00:1f.2 SATA controller: Intel Corporation 82801GR/GH (ICH7 Family) Serial ATA Storage Controller AHCI (rev 01) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 2606 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 316 Region 0: I/O ports at e400 [size=8] Region 1: I/O ports at e080 [size=4] Region 2: I/O ports at e000 [size=8] Region 3: I/O ports at dc00 [size=4] Region 4: I/O ports at d880 [size=16] Region 5: Memory at febfb800 (32-bit, non-prefetchable) [size=1K] Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Address: fee0300c Data: 4179 Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- And, remember, this behavior started in 2.6.18 and didn't exist in 2.6.17. Would it help if I narrowed down which patch caused it? Berck - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.18 - AHCI detection pauses excessively
Tejun Heo wrote: Hmm... this is difficult. The problem is that everything looks normal until command is issued. My primary suspect still is ahci powering down phy during initialization. Can you please test the attached patch again? No significant difference that I can tell. I've attached the whole log from boot to power-down. That's with both this patch and the previous patch. If you want just one, I can do that as well... Then, a series of obsolete STANDBY failures. Who's issuing these commands? It's not libata, libata uses STANDBY (0xe2). Is it some kind of gentoo thing? Nope, Debian/Unstable. Berck [0.00] Linux version 2.6.19-rc6-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #4 SMP PREEMPT Wed Nov 29 09:40:25 MST 2006 [0.00] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ff8 (usable) [0.00] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [0.00] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [0.00] BIOS-e820: 3ffe - 4000 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.4 present. [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 262016 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] Setting APIC routing to flat [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Nosave address range: 0009f000 - 000a [0.00] Nosave address range: 000a - 000e4000 [0.00] Nosave address range: 000e4000 - 0010 [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bfb0) [0.00] PERCPU: Allocating 32512 bytes of per cpu data [0.00] Built 1 zonelists. Total pages: 257375 [0.00] Kernel command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 57.051783] Console: colour VGA+ 80x25 [ 57.314953] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 57.322333] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 57.329293] Checking aperture... [ 57.340073] Memory: 1027700k/1048064k available (2281k kernel code, 19860k reserved, 999k data, 196k init) [ 57.409313] Calibrating delay using timer specific routine.. 5800.15 BogoMIPS (lpj=2900076) [ 57.417779] Mount-cache hash table entries: 256 [ 57.422423] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.427211] CPU: L2 cache: 2048K [ 57.430763] using mwait in idle threads. [ 57.434721] CPU: Physical Processor ID: 0 [ 57.438764] CPU: Processor Core ID: 0 [ 57.442465] CPU0: Thermal monitoring enabled (TM2) [ 57.447302] Freeing SMP alternatives: 24k freed [ 57.451874] ACPI: Core revision 20060707 [ 57.480782] Using local APIC timer interrupts. [ 57.519735] result 25877174 [ 57.522568] Detected 25.877 MHz APIC timer. [ 57.527253] Booting processor 1/2 APIC 0x1 [ 57.541734] Initializing CPU#1 [ 57.602132] Calibrating delay using timer specific routine.. 5796.48 BogoMIPS (lpj=2898240) [ 57.602137] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.602138] CPU: L2 cache: 2048K [ 57.602139] CPU: Physical Processor ID: 0 [ 57.602140] CPU: Processor Core ID: 1 [ 57.602144] CPU1: Thermal monitoring enabled (TM2) [ 57.602335] Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Re: 2.6.18 - AHCI detection pauses excessively
Tejun Heo wrote: Hmm... this is difficult. The problem is that everything looks normal until command is issued. My primary suspect still is ahci powering down phy during initialization. Can you please test the attached patch again? No significant difference that I can tell. I've attached the whole log from boot to power-down. That's with both this patch and the previous patch. If you want just one, I can do that as well... Then, a series of obsolete STANDBY failures. Who's issuing these commands? It's not libata, libata uses STANDBY (0xe2). Is it some kind of gentoo thing? Nope, Debian/Unstable. Berck [0.00] Linux version 2.6.19-rc6-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #4 SMP PREEMPT Wed Nov 29 09:40:25 MST 2006 [0.00] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ff8 (usable) [0.00] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [0.00] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [0.00] BIOS-e820: 3ffe - 4000 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.4 present. [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] DMA324096 - 1048576 [0.00] Normal1048576 - 1048576 [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 - 159 [0.00] 0: 256 - 262016 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] Setting APIC routing to flat [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Nosave address range: 0009f000 - 000a [0.00] Nosave address range: 000a - 000e4000 [0.00] Nosave address range: 000e4000 - 0010 [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bfb0) [0.00] PERCPU: Allocating 32512 bytes of per cpu data [0.00] Built 1 zonelists. Total pages: 257375 [0.00] Kernel command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 57.051783] Console: colour VGA+ 80x25 [ 57.314953] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 57.322333] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 57.329293] Checking aperture... [ 57.340073] Memory: 1027700k/1048064k available (2281k kernel code, 19860k reserved, 999k data, 196k init) [ 57.409313] Calibrating delay using timer specific routine.. 5800.15 BogoMIPS (lpj=2900076) [ 57.417779] Mount-cache hash table entries: 256 [ 57.422423] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.427211] CPU: L2 cache: 2048K [ 57.430763] using mwait in idle threads. [ 57.434721] CPU: Physical Processor ID: 0 [ 57.438764] CPU: Processor Core ID: 0 [ 57.442465] CPU0: Thermal monitoring enabled (TM2) [ 57.447302] Freeing SMP alternatives: 24k freed [ 57.451874] ACPI: Core revision 20060707 [ 57.480782] Using local APIC timer interrupts. [ 57.519735] result 25877174 [ 57.522568] Detected 25.877 MHz APIC timer. [ 57.527253] Booting processor 1/2 APIC 0x1 [ 57.541734] Initializing CPU#1 [ 57.602132] Calibrating delay using timer specific routine.. 5796.48 BogoMIPS (lpj=2898240) [ 57.602137] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.602138] CPU: L2 cache: 2048K [ 57.602139] CPU: Physical Processor ID: 0 [ 57.602140] CPU: Processor Core ID: 1 [ 57.602144] CPU1: Thermal monitoring enabled (TM2) [ 57.602335] Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping
Re: 2.6.18 - AHCI detection pauses excessively
Tejun Heo wrote: Yeah, I did and forgot about this thread too. Sorry. This is on the top of my to-do list now. I'm attaching the patch. TIA. That didn't fix the problem, but did change the messages. I've attached the entire log, including the weird errors on power-off from the same device that gives problems on boot, which I suspect are related. Berck [0.00] Linux version 2.6.19-rc6-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #3 SMP PREEMPT Sun Nov 26 21:25:59 MST 2006 [0.00] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ff8 (usable) [0.00] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [0.00] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [0.00] BIOS-e820: 3ffe - 4000 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.4 present. [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 262016 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] Setting APIC routing to flat [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Nosave address range: 0009f000 - 000a [0.00] Nosave address range: 000a - 000e4000 [0.00] Nosave address range: 000e4000 - 0010 [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bfb0) [0.00] PERCPU: Allocating 32512 bytes of per cpu data [0.00] Built 1 zonelists. Total pages: 257375 [0.00] Kernel command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 57.369381] Console: colour VGA+ 80x25 [ 57.632610] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 57.639997] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 57.646956] Checking aperture... [ 57.657752] Memory: 1027700k/1048064k available (2281k kernel code, 19860k reserved, 999k data, 196k init) [ 57.726521] Calibrating delay using timer specific routine.. 5800.15 BogoMIPS (lpj=2900075) [ 57.734992] Mount-cache hash table entries: 256 [ 57.739636] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.744433] CPU: L2 cache: 2048K [ 57.747699] using mwait in idle threads. [ 57.751657] CPU: Physical Processor ID: 0 [ 57.755701] CPU: Processor Core ID: 0 [ 57.759400] CPU0: Thermal monitoring enabled (TM2) [ 57.764238] Freeing SMP alternatives: 24k freed [ 57.768811] ACPI: Core revision 20060707 [ 57.797724] Using local APIC timer interrupts. [ 57.836680] result 25877185 [ 57.839512] Detected 25.877 MHz APIC timer. [ 57.844463] Booting processor 1/2 APIC 0x1 [ 57.858937] Initializing CPU#1 [ 57.919341] Calibrating delay using timer specific routine.. 5796.44 BogoMIPS (lpj=2898222) [ 57.919345] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.919346] CPU: L2 cache: 2048K [ 57.919348] CPU: Physical Processor ID: 0 [ 57.919348] CPU: Processor Core ID: 1 [ 57.919352] CPU1: Thermal monitoring enabled (TM2) [ 57.919543] Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping 06 [ 57.920346] Brought up 2 CPUs [ 57.962055] testing NMI watchdog ... OK. [ 57.996481] time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer. [ 58.003041] time.c: Detected 2898.247 MHz processor. [ 58.095698] migration_cost=22 [ 58.099005]
Re: 2.6.18 - AHCI detection pauses excessively
Tejun Heo wrote: Yeah, I did and forgot about this thread too. Sorry. This is on the top of my to-do list now. I'm attaching the patch. TIA. That didn't fix the problem, but did change the messages. I've attached the entire log, including the weird errors on power-off from the same device that gives problems on boot, which I suspect are related. Berck [0.00] Linux version 2.6.19-rc6-mm1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #3 SMP PREEMPT Sun Nov 26 21:25:59 MST 2006 [0.00] Command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ff8 (usable) [0.00] BIOS-e820: 3ff8 - 3ff8e000 (ACPI data) [0.00] BIOS-e820: 3ff8e000 - 3ffe (ACPI NVS) [0.00] BIOS-e820: 3ffe - 4000 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.4 present. [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] DMA324096 - 1048576 [0.00] Normal1048576 - 1048576 [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 - 159 [0.00] 0: 256 - 262016 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] Setting APIC routing to flat [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Nosave address range: 0009f000 - 000a [0.00] Nosave address range: 000a - 000e4000 [0.00] Nosave address range: 000e4000 - 0010 [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bfb0) [0.00] PERCPU: Allocating 32512 bytes of per cpu data [0.00] Built 1 zonelists. Total pages: 257375 [0.00] Kernel command line: root=/dev/sdc1 ro console=tty0 console=ttyS0,115200n8 BOOT_IMAGE=vmlinuz [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 57.369381] Console: colour VGA+ 80x25 [ 57.632610] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 57.639997] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 57.646956] Checking aperture... [ 57.657752] Memory: 1027700k/1048064k available (2281k kernel code, 19860k reserved, 999k data, 196k init) [ 57.726521] Calibrating delay using timer specific routine.. 5800.15 BogoMIPS (lpj=2900075) [ 57.734992] Mount-cache hash table entries: 256 [ 57.739636] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.744433] CPU: L2 cache: 2048K [ 57.747699] using mwait in idle threads. [ 57.751657] CPU: Physical Processor ID: 0 [ 57.755701] CPU: Processor Core ID: 0 [ 57.759400] CPU0: Thermal monitoring enabled (TM2) [ 57.764238] Freeing SMP alternatives: 24k freed [ 57.768811] ACPI: Core revision 20060707 [ 57.797724] Using local APIC timer interrupts. [ 57.836680] result 25877185 [ 57.839512] Detected 25.877 MHz APIC timer. [ 57.844463] Booting processor 1/2 APIC 0x1 [ 57.858937] Initializing CPU#1 [ 57.919341] Calibrating delay using timer specific routine.. 5796.44 BogoMIPS (lpj=2898222) [ 57.919345] CPU: L1 I cache: 32K, L1 D cache: 32K [ 57.919346] CPU: L2 cache: 2048K [ 57.919348] CPU: Physical Processor ID: 0 [ 57.919348] CPU: Processor Core ID: 1 [ 57.919352] CPU1: Thermal monitoring enabled (TM2) [ 57.919543] Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz stepping 06 [ 57.920346] Brought up 2 CPUs [ 57.962055] testing NMI watchdog ... OK. [ 57.996481] time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer. [ 58.003041] time.c: Detected 2898.247 MHz processor. [ 58.095698] migration_cost=22 [ 58.099005] NET:
2.6.12-rc2-mm1 compile error in mmx.c
2.6.12-rc2-mm1 fails to build for me with the following error: arch/i386/lib/mmx.c:374: error: conflicting types for `mmx_clear_page' include/asm/mmx.h:11: error: previous declaration of `mmx_clear_page' make[1]: *** [arch/i386/lib/mmx.o] Error 1 make: *** [arch/i386/lib] Error 2 I hope this is useful-- I apologize if it is not. (I browsed the archives, and no one seems to be complaining of the same thing so far.) I'm not subscribed to the list, but I'll gladly provide more information if you CC me on a response. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.12-rc2-mm1 compile error in mmx.c
2.6.12-rc2-mm1 fails to build for me with the following error: arch/i386/lib/mmx.c:374: error: conflicting types for `mmx_clear_page' include/asm/mmx.h:11: error: previous declaration of `mmx_clear_page' make[1]: *** [arch/i386/lib/mmx.o] Error 1 make: *** [arch/i386/lib] Error 2 I hope this is useful-- I apologize if it is not. (I browsed the archives, and no one seems to be complaining of the same thing so far.) I'm not subscribed to the list, but I'll gladly provide more information if you CC me on a response. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
