Linux 2.6.21-rc2

Linux 2.6.21-rc2

[Linus Torvalds]

Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way 
more changes than I really like.

And yeah, it's largely my fault, because I simply missed a V4L/DVB merge 
that came in before the merge window closed, but since I didn't notice it 
didn't make -rc1, and as such it got merged late and is in -rc2 instead.

But because I'll flail around wildly and rather blame anything else than 
my own incompetence, I'll just claim that all the other kernel developers 
have been irresponsible, and caused -rc2 to be bigger than needed. In some 
areas (you know who you are) it may even be true..

Apart from the V4L/DVB merge, we've got a late PARISC update, and a number 
of driver updates (ata, networking, usb) changes. Along with the normal 
smattering of random stuff (core networking, selinux, infiniband, agp, 
mips, arm).

Anyway, I really hope the thing starts calming down now, and everybody 
should take a hard look at the regressions lists that Adrian has started 
sending out. We already fixed some of them, but there is more to go..

Thanks,

		Linus

Re: Linux 2.6.21-rc2

[Gabriel C]

Linus Torvalds wrote:
> Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way 
> more changes than I really like.
>
>   


I got this warning so far :)

drivers/video/Kconfig:1622:warning: 'select' used by config symbol 
'FB_PS3' refer to undefined symbol 'PS3_PS3AV'


Regards,

Gabriel

[PATCH] affinity is not defined in non-smp kernels - i386

[Fernando Luis Vázquez Cao]

Initialize affinity only when building SMP kernels.

Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
---

--- linux-2.6.21-rc2-dtt/arch/i386/kernel/io_apic.c	2007-03-06 15:20:14.000000000 +0900
+++ linux-2.6.21-rc2-kdump/arch/i386/kernel/io_apic.c	2007-03-06 15:51:45.000000000 +0900
@@ -1354,7 +1354,9 @@ static void __init setup_IO_APIC_irqs(vo
 		}
 		spin_lock_irqsave(&ioapic_lock, flags);
 		__ioapic_write_entry(apic, pin, entry);
+#ifdef CONFIG_SMP
 		irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 		spin_unlock_irqrestore(&ioapic_lock, flags);
 	}
 	}

[PATCH] affinity is not defined in non-smp kernels - i386 (v2)

[Fernando Luis Vázquez Cao]

Initialize affinity only when building SMP kernels.

Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
---

--- linux-2.6.21-rc2-dtt/arch/i386/kernel/io_apic.c	2007-03-06 15:20:14.000000000 +0900
+++ linux-2.6.21-rc2-kdump/arch/i386/kernel/io_apic.c	2007-03-06 15:51:45.000000000 +0900
@@ -1354,7 +1354,9 @@ static void __init setup_IO_APIC_irqs(vo
 		}
 		spin_lock_irqsave(&ioapic_lock, flags);
 		__ioapic_write_entry(apic, pin, entry);
+#ifdef CONFIG_SMP
 		irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 		spin_unlock_irqrestore(&ioapic_lock, flags);
 	}
 	}
@@ -2875,7 +2877,9 @@ int io_apic_set_pci_routing (int ioapic,
 
 	spin_lock_irqsave(&ioapic_lock, flags);
 	__ioapic_write_entry(ioapic, pin, entry);
+#ifdef CONFIG_SMP
 	irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 	spin_unlock_irqrestore(&ioapic_lock, flags);
 
 	return 0;

Re: [PATCH] affinity is not defined in non-smp kernels - i386

[Eric W. Biederman]

Fernando Luis Vázquez Cao <fernando@oss.ntt.co.jp> writes:

> Initialize affinity only when building SMP kernels.

Reasonable.  I goofed here.

However I would prefer my patch that just deletes these problem lines.
These lines don't really contribute anything and are harmless to
remove.

Eric

Re: [PATCH] affinity is not defined in non-smp kernels - i386

[Bill Davidsen]

Eric W. Biederman wrote:
> Fernando Luis Vázquez Cao <fernando@oss.ntt.co.jp> writes:
> 
>> Initialize affinity only when building SMP kernels.
> 
> Reasonable.  I goofed here.
> 
> However I would prefer my patch that just deletes these problem lines.
> These lines don't really contribute anything and are harmless to
> remove.

Where is the initialization performed, then?

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

Re: [PATCH] affinity is not defined in non-smp kernels - i386

[Eric W. Biederman]

Bill Davidsen <davidsen@tmr.com> writes:

> Eric W. Biederman wrote:
>> Fernando Luis Vázquez Cao <fernando@oss.ntt.co.jp> writes:
>>
>>> Initialize affinity only when building SMP kernels.
>>
>> Reasonable.  I goofed here.
>>
>> However I would prefer my patch that just deletes these problem lines.
>> These lines don't really contribute anything and are harmless to
>> remove.
>
> Where is the initialization performed, then?

The field is initialized statically.   We also never use it internally it the
kernel except for reporting back to the user what where we were told we could
route the interrupt to.

Eric

Re: [PATCH] affinity is not defined in non-smp kernels - i386

[Linus Torvalds]

On Wed, 28 Feb 2007, Bill Davidsen wrote:
> 
> Where is the initialization performed, then?

Here's the commit with the patch from Eric that I pushed out (I had 
thought I'd already applied it for rc2, but I obviously hadn't. Blush. 
It's there now in -git, but obviously not in the -rc2 release).

It's got the explanation too.

		Linus

---
commit 2ff7354fe888f46f6629b57e463b0a1eb956c02b
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Tue Feb 27 00:27:41 2007 -0700

    [PATCH] x86_64/i386 irq: Fix !CONFIG_SMP compilation
    
    When removing set_native_irq I missed the fact that it was
    called in a couple of places that were compiled even when
    SMP support is disabled.  And since the irq_desc[].affinity
    field only exists in SMP things broke.
    
    Thanks to Simon Arlott <simon@arlott.org> for spotting this.
    
    There are a couple of ways to fix this but the simplest one
    is to just remove the assignments.  The affinity field is only
    used to display a value to the user, and nothing on either i386
    or x86_64 reads it or depends on it being any particlua value,
    so skipping the assignment is safe.  The assignment that
    is being removed is just for the initial affinity value before
    the user explicitly sets it.  The irq_desc array initializes
    this field to CPU_MASK_ALL so the field is initialized to
    a reasonable value in the SMP case without being set.
    
    Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

diff --git a/arch/i386/kernel/io_apic.c b/arch/i386/kernel/io_apic.c
index 6fec4da..e4408ff 100644
--- a/arch/i386/kernel/io_apic.c
+++ b/arch/i386/kernel/io_apic.c
@@ -1354,7 +1354,6 @@ static void __init setup_IO_APIC_irqs(void)
 		}
 		spin_lock_irqsave(&ioapic_lock, flags);
 		__ioapic_write_entry(apic, pin, entry);
-		irq_desc[irq].affinity = TARGET_CPUS;
 		spin_unlock_irqrestore(&ioapic_lock, flags);
 	}
 	}
@@ -2875,7 +2874,6 @@ int io_apic_set_pci_routing (int ioapic, int pin, int irq, int edge_level, int a
 
 	spin_lock_irqsave(&ioapic_lock, flags);
 	__ioapic_write_entry(ioapic, pin, entry);
-	irq_desc[irq].affinity = TARGET_CPUS;
 	spin_unlock_irqrestore(&ioapic_lock, flags);
 
 	return 0;
diff --git a/arch/x86_64/kernel/io_apic.c b/arch/x86_64/kernel/io_apic.c
index 48593f6..0a91368 100644
--- a/arch/x86_64/kernel/io_apic.c
+++ b/arch/x86_64/kernel/io_apic.c
@@ -830,10 +830,6 @@ static void setup_IO_APIC_irq(int apic, int pin, unsigned int irq,
 		disable_8259A_irq(irq);
 
 	ioapic_write_entry(apic, pin, entry);
-
-	spin_lock_irqsave(&ioapic_lock, flags);
-	irq_desc[irq].affinity = TARGET_CPUS;
-	spin_unlock_irqrestore(&ioapic_lock, flags);
 }
 
 static void __init setup_IO_APIC_irqs(void)

[PATCH] affinity is not defined in non-smp kernels - i386 (v2)

[Fernando Luis Vázquez Cao]

Initialize affinity only when building SMP kernels.

Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
---

--- linux-2.6.21-rc2-dtt/arch/i386/kernel/io_apic.c	2007-03-06 15:20:14.000000000 +0900
+++ linux-2.6.21-rc2-kdump/arch/i386/kernel/io_apic.c	2007-03-06 15:51:45.000000000 +0900
@@ -1354,7 +1354,9 @@ static void __init setup_IO_APIC_irqs(vo
 		}
 		spin_lock_irqsave(&ioapic_lock, flags);
 		__ioapic_write_entry(apic, pin, entry);
+#ifdef CONFIG_SMP
 		irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 		spin_unlock_irqrestore(&ioapic_lock, flags);
 	}
 	}
@@ -2875,7 +2877,9 @@ int io_apic_set_pci_routing (int ioapic,
 
 	spin_lock_irqsave(&ioapic_lock, flags);
 	__ioapic_write_entry(ioapic, pin, entry);
+#ifdef CONFIG_SMP
 	irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 	spin_unlock_irqrestore(&ioapic_lock, flags);
 
 	return 0;

[PATCH] affinity is not defined in non-smp kernels - x86_64

[Fernando Luis Vázquez Cao]

Initialize affinity only when building SMP kernels.

Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
---

--- linux-2.6.21-rc2-dtt/arch/x86_64/kernel/io_apic.c	2007-03-06 15:20:14.000000000 +0900
+++ linux-2.6.21-rc2-kdump/arch/x86_64/kernel/io_apic.c	2007-03-06 15:48:52.000000000 +0900
@@ -832,7 +832,9 @@ static void setup_IO_APIC_irq(int apic, 
 	ioapic_write_entry(apic, pin, entry);
 
 	spin_lock_irqsave(&ioapic_lock, flags);
+#ifdef CONFIG_SMP
 	irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 	spin_unlock_irqrestore(&ioapic_lock, flags);
 }
 

Re: Linux 2.6.21-rc2

[David Brown]

On 2/27/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way
> more changes than I really like.
>
> And yeah, it's largely my fault, because I simply missed a V4L/DVB merge
> that came in before the merge window closed, but since I didn't notice it
> didn't make -rc1, and as such it got merged late and is in -rc2 instead.
>
> But because I'll flail around wildly and rather blame anything else than
> my own incompetence, I'll just claim that all the other kernel developers
> have been irresponsible, and caused -rc2 to be bigger than needed. In some
> areas (you know who you are) it may even be true..
>
> Apart from the V4L/DVB merge, we've got a late PARISC update, and a number
> of driver updates (ata, networking, usb) changes. Along with the normal
> smattering of random stuff (core networking, selinux, infiniband, agp,
> mips, arm).
>
> Anyway, I really hope the thing starts calming down now, and everybody
> should take a hard look at the regressions lists that Adrian has started
> sending out. We already fixed some of them, but there is more to go..
>
> Thanks,
>
>                 Linus

I got this compile error:

  CC      arch/i386/kernel/io_apic.o
arch/i386/kernel/io_apic.c: In function 'setup_IO_APIC_irqs':
arch/i386/kernel/io_apic.c:1357: error: 'struct irq_desc' has no
member named 'affinity'
arch/i386/kernel/io_apic.c: In function 'io_apic_set_pci_routing':
arch/i386/kernel/io_apic.c:2878: error: 'struct irq_desc' has no
member named 'affinity'
make[1]: *** [arch/i386/kernel/io_apic.o] Error 1
make: *** [arch/i386/kernel] Error 2

didn't happen with rc1

- David Brown

Re: Linux 2.6.21-rc2

[Brice Goglin]

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

Linus Torvalds wrote:
> Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way 
> more changes than I really like.
>   

Hi Linus,

rc2 fails to build on my thinkpad t43:

  CC      arch/i386/kernel/io_apic.o
arch/i386/kernel/io_apic.c: In function 'setup_IO_APIC_irqs':
arch/i386/kernel/io_apic.c:1357: error: 'struct irq_desc' has no member
named 'affinity'
arch/i386/kernel/io_apic.c: In function 'io_apic_set_pci_routing':
arch/i386/kernel/io_apic.c:2878: error: 'struct irq_desc' has no member
named 'affinity'
make[1]: *** [arch/i386/kernel/io_apic.o] Error 1
make: *** [arch/i386/kernel] Error 2

The problem is caused by affinity being within #ifdef SMP in struct
irq_desc in irq.h:
#ifdef CONFIG_SMP
        cpumask_t               affinity;
        unsigned int            cpu;
#endif

I don't know whether the whole functions or just a single line should be
placed under #ifdef CONFIG_SMP. Eric (in CC) will know better than I do.

My config is attached.

Brice


[-- Attachment #2: config --]
[-- Type: text/plain, Size: 47682 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.21-rc2
# Wed Feb 28 08:09:48 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=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_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION="=panpancucul"
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
# CONFIG_TASK_XACCT is not set
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
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_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Block layer
#
CONFIG_BLOCK=y
# CONFIG_LBD is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_PARAVIRT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MCORE2 is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=m
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=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=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_KEXEC=y
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_COMPAT_VDSO=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SYSFS_DEPRECATED=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/sda6"

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
# CONFIG_ACPI_DOCK is not set
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
CONFIG_ACPI_IBM=m
# CONFIG_ACPI_IBM_DOCK is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
# CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE is not set
CONFIG_X86_SPEEDSTEP_ICH=m
CONFIG_X86_SPEEDSTEP_SMI=m
CONFIG_X86_P4_CLOCKMOD=m
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=m
# CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=m

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=m
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set

#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set

#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
# CONFIG_DONGLE is not set

#
# Old SIR device drivers
#
CONFIG_IRPORT_SIR=m

#
# Old Serial dongle support
#
# CONFIG_DONGLE_OLD is not set

#
# FIR device drivers
#
# CONFIG_USB_IRDA is not set
# CONFIG_SIGMATEL_FIR is not set
CONFIG_NSC_FIR=m
# CONFIG_WINBOND_FIR is not set
# CONFIG_TOSHIBA_FIR is not set
# CONFIG_SMC_IRCC_FIR is not set
# CONFIG_ALI_FIR is not set
# CONFIG_VLSI_FIR is not set
# CONFIG_VIA_FIR is not set
# CONFIG_MCS_FIR is not set
# CONFIG_BT is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
CONFIG_WIRELESS_EXT=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y
CONFIG_PNPACPI=y

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set

#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set

#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
CONFIG_SATA_ACPI=y
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_WINBOND_VLB is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#
# CONFIG_MAC_EMUMOUSEBTN is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#

#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
CONFIG_TIGON3=m
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
CONFIG_MYRI10GE=m
# CONFIG_NETXEN_NIC is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
# CONFIG_NET_WIRELESS_RTNETLINK is not set

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
# CONFIG_ARLAN is not set
# CONFIG_WAVELAN is not set
# CONFIG_PCMCIA_WAVELAN is not set
# CONFIG_PCMCIA_NETWAVE is not set

#
# Wireless 802.11 Frequency Hopping cards support
#
# CONFIG_PCMCIA_RAYCS is not set

#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_IPW2100 is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set

#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_HOSTAP is not set
# CONFIG_BCM43XX is not set
# CONFIG_ZD1211RW is not set
CONFIG_NET_WIRELESS=y

#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_UINPUT is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=y
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_GEODE is not set
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_NVRAM=m
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
CONFIG_I2C_I801=m
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PASEMI is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Hardware Monitoring support
#
CONFIG_HWMON=m
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
CONFIG_SENSORS_HDAPS=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y

#
# Video Capture Adapters
#

#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_CAFE_CCIC is not set

#
# V4L USB devices
#
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_W9968CF is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set

#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set
# CONFIG_USB_DSBR is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_BACKLIGHT_PROGEAR is not set
CONFIG_FB=m
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=m
CONFIG_FB_CFB_COPYAREA=m
CONFIG_FB_CFB_IMAGEBLIT=m
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

#
# Frambuffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_ADLIB is not set
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_MIRO is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set

#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AC97_POWER_SAVE is not set

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set

#
# SoC audio support
#
# CONFIG_SND_SOC is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m

#
# HID Devices
#
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_EHCI_BIG_ENDIAN_MMIO is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
CONFIG_USB_LIBUSUAL=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_TOUCHSCREEN is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_ATI_REMOTE2 is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set
# CONFIG_USB_GTCO is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET_MII is not set
# CONFIG_USB_USBNET is not set
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_AIRPRIME is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_FUNSOFT is not set
CONFIG_USB_SERIAL_VISOR=m
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_DEBUG is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# LED devices
#
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
CONFIG_EDAC=m

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
# CONFIG_EDAC_AMD76X is not set
# CONFIG_EDAC_E7XXX is not set
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82875P is not set
# CONFIG_EDAC_I82860 is not set
# CONFIG_EDAC_R82600 is not set
CONFIG_EDAC_POLL=y

#
# Real Time Clock
#
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set

#
# RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_TEST is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m

#
# Auxiliary Display support
#

#
# Virtualization
#
# CONFIG_KVM is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
CONFIG_NFS_DIRECTIO=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp850"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Distributed Lock Manager
#
# CONFIG_DLM is not set

#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Page alloc debug is incompatible with Software Suspend on i386
#
CONFIG_DEBUG_RODATA=y
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_MANAGER=m
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
CONFIG_CRYPTO_SHA1=m
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=m
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=m
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_MICHAEL_MIC=m
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
CONFIG_CRYPTO_DEV_GEODE=m

#
# Library routines
#
CONFIG_BITREVERSE=m
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
CONFIG_CRC32=m
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y

Re: Linux 2.6.21-rc2

[Eric W. Biederman]

Brice Goglin <Brice.Goglin@ens-lyon.org> writes:

> Linus Torvalds wrote:
>> Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way 
>> more changes than I really like.
>>   
>
> Hi Linus,
>
> rc2 fails to build on my thinkpad t43:
>
>   CC      arch/i386/kernel/io_apic.o
> arch/i386/kernel/io_apic.c: In function 'setup_IO_APIC_irqs':
> arch/i386/kernel/io_apic.c:1357: error: 'struct irq_desc' has no member
> named 'affinity'
> arch/i386/kernel/io_apic.c: In function 'io_apic_set_pci_routing':
> arch/i386/kernel/io_apic.c:2878: error: 'struct irq_desc' has no member
> named 'affinity'
> make[1]: *** [arch/i386/kernel/io_apic.o] Error 1
> make: *** [arch/i386/kernel] Error 2
>
> The problem is caused by affinity being within #ifdef SMP in struct
> irq_desc in irq.h:
> #ifdef CONFIG_SMP
>         cpumask_t               affinity;
>         unsigned int            cpu;
> #endif
>
> I don't know whether the whole functions or just a single line should be
> placed under #ifdef CONFIG_SMP. Eric (in CC) will know better than I do.

Yes. I goofed, and missed that stupid case.  The offending lines
should just die.  Patch already sent to Linus.  

Eric

Re: Linux 2.6.21-rc2

[David Brown]

> Yes. I goofed, and missed that stupid case.  The offending lines
> should just die.  Patch already sent to Linus.

Could the patch be posted? or could I see a git commit so I can get it myself?

Thanks,
David Brown

Re: Linux 2.6.21-rc2

[Randy Dunlap]

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

On Wed, 28 Feb 2007 08:44:45 -0800 David Brown wrote:

> > Yes. I goofed, and missed that stupid case.  The offending lines
> > should just die.  Patch already sent to Linus.
> 
> Could the patch be posted? or could I see a git commit so I can get it myself?

I'm attaching it below.  It hit the git commits mailing list
just a few minutes ago.

---
~Randy


[-- Attachment #2: irq-desc-affinity.patch --]
[-- Type: text/x-patch, Size: 2503 bytes --]


When removing set_native_irq I missed the fact that it was
called in a couple of places that were compiled even when
SMP support is disabled.  And since the irq_desc[].affinity
field only exists in SMP things broke.

Thanks to Simon Arlott <simon@arlott.org> for spotting this.

There are a couple of ways to fix this but the simplest one
is to just remove the assignments.  The affinity field is only
used to display a value to the user, and nothing on either i386
or x86_64 reads it or depends on it being any particlua value,
so skipping the assignment is safe.  The assignment that
is being removed is just for the initial affinity value before
the user explicitly sets it.  The irq_desc array initializes
this field to CPU_MASK_ALL so the field is initialized to
a reasonable value in the SMP case without being set.

Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
---
 arch/i386/kernel/io_apic.c   |    2 --
 arch/x86_64/kernel/io_apic.c |    4 ----
 2 files changed, 0 insertions(+), 6 deletions(-)

diff --git a/arch/i386/kernel/io_apic.c b/arch/i386/kernel/io_apic.c
index 6fec4da..e4408ff 100644
--- a/arch/i386/kernel/io_apic.c
+++ b/arch/i386/kernel/io_apic.c
@@ -1354,7 +1354,6 @@ static void __init setup_IO_APIC_irqs(void)
 		}
 		spin_lock_irqsave(&ioapic_lock, flags);
 		__ioapic_write_entry(apic, pin, entry);
-		irq_desc[irq].affinity = TARGET_CPUS;
 		spin_unlock_irqrestore(&ioapic_lock, flags);
 	}
 	}
@@ -2875,7 +2874,6 @@ int io_apic_set_pci_routing (int ioapic, int pin, int irq, int edge_level, int a
 
 	spin_lock_irqsave(&ioapic_lock, flags);
 	__ioapic_write_entry(ioapic, pin, entry);
-	irq_desc[irq].affinity = TARGET_CPUS;
 	spin_unlock_irqrestore(&ioapic_lock, flags);
 
 	return 0;
diff --git a/arch/x86_64/kernel/io_apic.c b/arch/x86_64/kernel/io_apic.c
index 48593f6..0a91368 100644
--- a/arch/x86_64/kernel/io_apic.c
+++ b/arch/x86_64/kernel/io_apic.c
@@ -830,10 +830,6 @@ static void setup_IO_APIC_irq(int apic, int pin, unsigned int irq,
 		disable_8259A_irq(irq);
 
 	ioapic_write_entry(apic, pin, entry);
-
-	spin_lock_irqsave(&ioapic_lock, flags);
-	irq_desc[irq].affinity = TARGET_CPUS;
-	spin_unlock_irqrestore(&ioapic_lock, flags);
 }
 
 static void __init setup_IO_APIC_irqs(void)
-- 
1.5.0.g53756

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] affinity is not defined in non-smp kernels - x86_64

[Fernando Luis Vázquez Cao]

Initialize affinity only when building SMP kernels.

Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
---

--- linux-2.6.21-rc2-dtt/arch/x86_64/kernel/io_apic.c	2007-03-06 15:20:14.000000000 +0900
+++ linux-2.6.21-rc2-kdump/arch/x86_64/kernel/io_apic.c	2007-03-06 15:48:52.000000000 +0900
@@ -832,7 +832,9 @@ static void setup_IO_APIC_irq(int apic, 
 	ioapic_write_entry(apic, pin, entry);
 
 	spin_lock_irqsave(&ioapic_lock, flags);
+#ifdef CONFIG_SMP
 	irq_desc[irq].affinity = TARGET_CPUS;
+#endif
 	spin_unlock_irqrestore(&ioapic_lock, flags);
 }
 

Re: Linux 2.6.21-rc2

[Damien Wyart]

* Linus Torvalds <torvalds@linux-foundation.org> [070228 06:16]:
> Anyway, I really hope the thing starts calming down now, and everybody
> should take a hard look at the regressions lists that Adrian has
> started sending out. We already fixed some of them, but there is more
> to go..

Ingo's patch correcting a bug in the SMT scheduler
(http://lkml.org/lkml/2007/2/26/103) seems to have been missed. It is
quite important when using dynticks.

-- 
Damien Wyart

[1/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way 
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : kwin dies silently
References : http://lkml.org/lkml/2007/2/28/112
Submitter  : Sid Boyce <g3vbv@blueyonder.co.uk>
Status     : unknown


Subject    : resume: slab error in verify_redzone_free(): cache `size-512':
                     memory outside object was overwritten
References : http://lkml.org/lkml/2007/2/24/41
Submitter  : Pavel Machek <pavel@ucw.cz>
Handled-By : Marcel Holtmann <marcel@holtmann.org>
Status     : unknown


Subject    : bluetooth hardlocks
References : http://lkml.org/lkml/2007/3/2/85
Submitter  : Pavel Machek <pavel@ucw.cz>
Status     : unknown


Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
References : http://lkml.org/lkml/2007/3/4/64
Submitter  : Mark Lord <lkml@rtr.ca>
Caused-By  : Marcel Holtmann <marcel@holtmann.org>
             commit c1a3313698895d8ad4760f98642007bf236af2e8
Status     : unknown


Subject    : kref refcounting breakage
References : http://lkml.org/lkml/2007/3/2/67
Submitter  : Andrew Morton <akpm@linux-foundation.org>
Handled-By : Greg KH <greg@kroah.com>
Status     : unknown


Subject    : wireless breakage (ipw2200, iwconfig, NetworkManager)
References : http://lkml.org/lkml/2007/3/4/135
Submitter  : Matt Mackall <mpm@selenic.com>
Caused-By  : Greg Kroah-Hartman <gregkh@suse.de> (?)
             commit 43cb76d91ee85f579a69d42bc8efc08bac560278 (?)
Handled-By : Johannes Berg <johannes@sipsolutions.net>
Status     : unknown


Subject    : forcedeth: skb_over_panic
References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
Submitter  : Albert Hopkins <kernel@marduk.letterboxes.org>
Status     : unknown

[1/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way 
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : kwin dies silently
References : http://lkml.org/lkml/2007/2/28/112
Submitter  : Sid Boyce <g3vbv@blueyonder.co.uk>
Status     : unknown


Subject    : resume: slab error in verify_redzone_free(): cache `size-512':
                     memory outside object was overwritten
References : http://lkml.org/lkml/2007/2/24/41
Submitter  : Pavel Machek <pavel@ucw.cz>
Handled-By : Marcel Holtmann <marcel@holtmann.org>
Status     : unknown


Subject    : bluetooth hardlocks
References : http://lkml.org/lkml/2007/3/2/85
Submitter  : Pavel Machek <pavel@ucw.cz>
Status     : unknown


Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
References : http://lkml.org/lkml/2007/3/4/64
Submitter  : Mark Lord <lkml@rtr.ca>
Caused-By  : Marcel Holtmann <marcel@holtmann.org>
             commit c1a3313698895d8ad4760f98642007bf236af2e8
Status     : unknown


Subject    : kref refcounting breakage
References : http://lkml.org/lkml/2007/3/2/67
Submitter  : Andrew Morton <akpm@linux-foundation.org>
Handled-By : Greg KH <greg@kroah.com>
Status     : unknown


Subject    : wireless breakage (ipw2200, iwconfig, NetworkManager)
References : http://lkml.org/lkml/2007/3/4/135
Submitter  : Matt Mackall <mpm@selenic.com>
Caused-By  : Greg Kroah-Hartman <gregkh@suse.de> (?)
             commit 43cb76d91ee85f579a69d42bc8efc08bac560278 (?)
Handled-By : Johannes Berg <johannes@sipsolutions.net>
Status     : unknown


Subject    : forcedeth: skb_over_panic
References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
Submitter  : Albert Hopkins <kernel@marduk.letterboxes.org>
Status     : unknown

Re: [1/6] 2.6.21-rc2: known regressions

[Andrew Morton]

On Mon, 5 Mar 2007 02:50:31 +0100 Adrian Bunk <bunk@stusta.de> wrote:

> This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> that are not yet fixed in Linus' tree.


We seem to have broken an unusually large amount of stuff this time.

partial post-mortem:

- The ACPICA merge landed in -mm super-late: basically it was in mainline
  a week afterwards and saw only a single -mm release.

  Part of the reason for this short period in -mm was that ACPICA had its
  paws all over x86_64 code and conflicted badly with significant changes
  in the x86_64 tree.

  That happens sometimes.  But when it does, the mess lands in my lap
  rather than in the laps of the perpetrators.

  Lesson: keep the code well-factored so that different subsystems don't
  soil each others' kennels.

- The hrtimers/dynticks stuff is simply hard: timekeeping, low-level x86,
  even APICs.  These are areas in which things break a lot, so churning it
  was inevitably going to cause problems.

  Lesson: none, I think.  Low-level x86 support is just hard, and
  changing it breaks things.


So that accounts for _some_ of the damage, but I wonder if there's more to
it than that.

Re: [1/6] 2.6.21-rc2: known regressions

[Andrew Morton]

On Mon, 5 Mar 2007 02:50:31 +0100 Adrian Bunk <bunk@stusta.de> wrote:

> This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> that are not yet fixed in Linus' tree.


We seem to have broken an unusually large amount of stuff this time.

partial post-mortem:

- The ACPICA merge landed in -mm super-late: basically it was in mainline
  a week afterwards and saw only a single -mm release.

  Part of the reason for this short period in -mm was that ACPICA had its
  paws all over x86_64 code and conflicted badly with significant changes
  in the x86_64 tree.

  That happens sometimes.  But when it does, the mess lands in my lap
  rather than in the laps of the perpetrators.

  Lesson: keep the code well-factored so that different subsystems don't
  soil each others' kennels.

- The hrtimers/dynticks stuff is simply hard: timekeeping, low-level x86,
  even APICs.  These are areas in which things break a lot, so churning it
  was inevitably going to cause problems.

  Lesson: none, I think.  Low-level x86 support is just hard, and
  changing it breaks things.


So that accounts for _some_ of the damage, but I wonder if there's more to
it than that.

Re: [1/6] 2.6.21-rc2: known regressions

[Greg KH]

On Mon, Mar 05, 2007 at 02:50:31AM +0100, Adrian Bunk wrote:
> Subject    : kref refcounting breakage
> References : http://lkml.org/lkml/2007/3/2/67
> Submitter  : Andrew Morton <akpm@linux-foundation.org>
> Handled-By : Greg KH <greg@kroah.com>
> Status     : unknown

I'm working on tracking this down still...

> Subject    : wireless breakage (ipw2200, iwconfig, NetworkManager)
> References : http://lkml.org/lkml/2007/3/4/135
> Submitter  : Matt Mackall <mpm@selenic.com>
> Caused-By  : Greg Kroah-Hartman <gregkh@suse.de> (?)
>              commit 43cb76d91ee85f579a69d42bc8efc08bac560278 (?)
> Handled-By : Johannes Berg <johannes@sipsolutions.net>
> Status     : unknown

I really think this is a CONFIG_SYSFS_DEPRECATED issue (not being set),
but want to get Matt confirm either way before saying this is a real
issue or not.

thanks,

greg k-h

Re: [1/6] 2.6.21-rc2: known regressions

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On Sun, 2007-03-04 at 19:35 -0800, Greg KH wrote:

> > Subject    : wireless breakage (ipw2200, iwconfig, NetworkManager)
> > References : http://lkml.org/lkml/2007/3/4/135
> > Submitter  : Matt Mackall <mpm@selenic.com>
> > Caused-By  : Greg Kroah-Hartman <gregkh@suse.de> (?)
> >              commit 43cb76d91ee85f579a69d42bc8efc08bac560278 (?)
> > Handled-By : Johannes Berg <johannes@sipsolutions.net>
> > Status     : unknown
> 
> I really think this is a CONFIG_SYSFS_DEPRECATED issue (not being set),
> but want to get Matt confirm either way before saying this is a real
> issue or not.

I just tested on my quad powermac that also runs a stock Debian/unstable
and changing that option makes all the difference. Nevermind that it
defaults to yes and one needs to turn it off explicitly...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: [1/6] 2.6.21-rc2: known regressions

[Johannes Berg]

[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

On Sun, 2007-03-04 at 19:35 -0800, Greg KH wrote:

> > Subject    : wireless breakage (ipw2200, iwconfig, NetworkManager)
> > References : http://lkml.org/lkml/2007/3/4/135
> > Submitter  : Matt Mackall <mpm@selenic.com>
> > Caused-By  : Greg Kroah-Hartman <gregkh@suse.de> (?)
> >              commit 43cb76d91ee85f579a69d42bc8efc08bac560278 (?)
> > Handled-By : Johannes Berg <johannes@sipsolutions.net>
> > Status     : unknown
> 
> I really think this is a CONFIG_SYSFS_DEPRECATED issue (not being set),
> but want to get Matt confirm either way before saying this is a real
> issue or not.

I just tested on my quad powermac that also runs a stock Debian/unstable
and changing that option makes all the difference. Nevermind that it
defaults to yes and one needs to turn it off explicitly...

johannes

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: [1/6] 2.6.21-rc2: known regressions

[Mark Lord]

Adrian Bunk wrote:
>
> Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
> References : http://lkml.org/lkml/2007/3/4/64
> Submitter  : Mark Lord <lkml@rtr.ca>
> Caused-By  : Marcel Holtmann <marcel@holtmann.org>
>              commit c1a3313698895d8ad4760f98642007bf236af2e8
> Status     : unknown

A 2-line patch exists for fs/sysfs/dir.c to address this.
Waiting on Greg to apply it or substitute something prettier.  ;)

Cheers

Re: [1/6] 2.6.21-rc2: known regressions

[Mark Lord]

Adrian Bunk wrote:
>
> Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
> References : http://lkml.org/lkml/2007/3/4/64
> Submitter  : Mark Lord <lkml@rtr.ca>
> Caused-By  : Marcel Holtmann <marcel@holtmann.org>
>              commit c1a3313698895d8ad4760f98642007bf236af2e8
> Status     : unknown

A 2-line patch exists for fs/sysfs/dir.c to address this.
Waiting on Greg to apply it or substitute something prettier.  ;)

Cheers

Re: [1/6] 2.6.21-rc2: known regressions

[Greg KH]

On Sun, Mar 04, 2007 at 11:01:33PM -0500, Mark Lord wrote:
> Adrian Bunk wrote:
> >
> >Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
> >References : http://lkml.org/lkml/2007/3/4/64
> >Submitter  : Mark Lord <lkml@rtr.ca>
> >Caused-By  : Marcel Holtmann <marcel@holtmann.org>
> >             commit c1a3313698895d8ad4760f98642007bf236af2e8
> >Status     : unknown
> 
> A 2-line patch exists for fs/sysfs/dir.c to address this.
> Waiting on Greg to apply it or substitute something prettier.  ;)

I want to see if Marcel agrees with it, as he did the original patch in
that area.

thanks,

greg k-h

Re: [1/6] 2.6.21-rc2: known regressions

[Marcel Holtmann]

Hi Greg,

> > >Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
> > >References : http://lkml.org/lkml/2007/3/4/64
> > >Submitter  : Mark Lord <lkml@rtr.ca>
> > >Caused-By  : Marcel Holtmann <marcel@holtmann.org>
> > >             commit c1a3313698895d8ad4760f98642007bf236af2e8
> > >Status     : unknown
> > 
> > A 2-line patch exists for fs/sysfs/dir.c to address this.
> > Waiting on Greg to apply it or substitute something prettier.  ;)
> 
> I want to see if Marcel agrees with it, as he did the original patch in
> that area.

I am not deep enough in the sysfs code to tell you if Mark's change it
correct or not. It looks however fully reasonable to me. From the higher
level perspective of the device_move() usage the RFCOMM code looks
correct and has been tested before I submitted it for inclusion.

Regards

Marcel

Re: [1/6] 2.6.21-rc2: known regressions

[Marcel Holtmann]

Hi Greg,

> > >Subject    : Bluetooth RFComm locks up the machine  (device_move() related)
> > >References : http://lkml.org/lkml/2007/3/4/64
> > >Submitter  : Mark Lord <lkml@rtr.ca>
> > >Caused-By  : Marcel Holtmann <marcel@holtmann.org>
> > >             commit c1a3313698895d8ad4760f98642007bf236af2e8
> > >Status     : unknown
> > 
> > A 2-line patch exists for fs/sysfs/dir.c to address this.
> > Waiting on Greg to apply it or substitute something prettier.  ;)
> 
> I want to see if Marcel agrees with it, as he did the original patch in
> that area.

I am not deep enough in the sysfs code to tell you if Mark's change it
correct or not. It looks however fully reasonable to me. From the higher
level perspective of the device_move() usage the RFCOMM code looks
correct and has been tested before I submitted it for inclusion.

Regards

Marcel

[BUG} usb regression in 2.6.21-rc2-git3

[Mark Lord]

Adrian Bunk wrote:
> This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> that are not yet fixed in Linus' tree.


Here's another one for Greg:

I have a Targus USB 1.1 "dock", basically a hub with built-in
serial, parallel, PS/2 KB, PS/2 Mouse, and extra USB ports.

Simply connecting, and then disconnecting it causes an oops with 2.6.21-rc2:

Mar  4 23:29:51 silvy kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2
Mar  4 23:29:51 silvy kernel: usb 4-2: configuration #1 chosen from 1 choice
Mar  4 23:29:51 silvy kernel: hub 4-2:1.0: USB hub found
Mar  4 23:29:51 silvy kernel: hub 4-2:1.0: 5 ports detected
Mar  4 23:29:52 silvy kernel: usb 4-2.3: new full speed USB device using uhci_hcd and address 3
Mar  4 23:29:52 silvy kernel: usb 4-2.3: configuration #1 chosen from 1 choice
Mar  4 23:29:52 silvy kernel: input: MTC PS/2 to USB converter as /class/input/input9
Mar  4 23:29:52 silvy kernel: input: USB HID v1.10 Keyboard [MTC PS/2 to USB converter] on usb-0000:00:1d.3-2.3
Mar  4 23:29:52 silvy kernel: input: MTC PS/2 to USB converter as /class/input/input10
Mar  4 23:29:52 silvy kernel: input: USB HID v1.10 Mouse [MTC PS/2 to USB converter] on usb-0000:00:1d.3-2.3
Mar  4 23:29:52 silvy kernel: usb 4-2.5: new full speed USB device using uhci_hcd and address 4
Mar  4 23:29:52 silvy kernel: usb 4-2.5: configuration #1 chosen from 1 choice
Mar  4 23:29:52 silvy kernel: usb 4-2.4: new full speed USB device using uhci_hcd and address 5
Mar  4 23:29:52 silvy kernel: usb 4-2.4: configuration #1 chosen from 1 choice
Mar  4 23:29:52 silvy kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 1 proto 2 vid 0x0711 pid 0x0300
Mar  4 23:29:52 silvy kernel: usbcore: registered new interface driver usblp
Mar  4 23:29:52 silvy kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Mar  4 23:29:52 silvy kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for MCT U232
Mar  4 23:29:52 silvy kernel: mct_u232 4-2.4:1.0: MCT U232 converter detected
Mar  4 23:29:52 silvy kernel: usb-serial ttyUSB0: Error registering port device, continuing
Mar  4 23:29:52 silvy kernel: usbcore: registered new interface driver mct_u232
Mar  4 23:29:52 silvy kernel: drivers/usb/serial/mct_u232.c: Magic Control Technology USB-RS232 converter driver z2.0
Mar  4 23:29:57 silvy kernel: usb 4-2: USB disconnect, address 2
Mar  4 23:29:57 silvy kernel: usb 4-2.3: USB disconnect, address 3
Mar  4 23:29:57 silvy kernel: usb 4-2.4: USB disconnect, address 5
Mar  4 23:29:57 silvy kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 0000000c
Mar  4 23:29:57 silvy kernel:  printing eip:
Mar  4 23:29:57 silvy kernel: c027c251
Mar  4 23:29:57 silvy kernel: *pde = 00000000
Mar  4 23:29:57 silvy kernel: Oops: 0000 [#1]
Mar  4 23:29:57 silvy kernel: PREEMPT 
Mar  4 23:29:57 silvy kernel: Modules linked in: mct_u232 usblp radeon drm nfsd exportfs lockd nfs_acl sunrpc acpi_cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_stats freq_table cpufreq_conservative ac fan button thermal video battery container processor rfcomm l2cap bluetooth cfq_iosched deflate zlib_deflate twofish twofish_common serpent blowfish des cbc ecb blkcipher aes xcbc sha256 sha1 crypto_null af_key af_packet sbp2 usbhid hid pl2303 usbserial mousedev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss pcmcia snd_pcm snd_timer snd ipw2200 soundcore ieee80211 ieee80211_crypt pcspkr psmouse serio_raw b44 ahci ohci1394 ieee1394 snd_page_alloc sdhci mmc_core firmware_class yenta_socket rsrc_nonstatic pcmcia_core mii intel_agp ehci_hcd uhci_hcd usbcore agpgart sg sr_mod cdrom unix
Mar  4 23:29:57 silvy kernel: CPU:    0
Mar  4 23:29:57 silvy kernel: EIP:    0060:[klist_del+6/69]    Not tainted VLI
Mar  4 23:29:57 silvy kernel: EFLAGS: 00010286   (2.6.21-rc2-git3 #5)
Mar  4 23:29:57 silvy kernel: EIP is at klist_del+0x6/0x45
Mar  4 23:29:57 silvy kernel: eax: 00000000   ebx: f619f278   ecx: 00000001   edx: f66873c8
Mar  4 23:29:57 silvy kernel: esi: f619f288   edi: f66873c0   ebp: f619f618   esp: f742fe24
Mar  4 23:29:57 silvy kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Mar  4 23:29:57 silvy kernel: Process khubd (pid: 1970, ti=f742e000 task=f7c20070 task.ti=f742e000)
Mar  4 23:29:57 silvy kernel: Stack: f619f278 00000001 c01fb571 f619f278 00000001 f66873c0 00000000 c01fb6f2 
Mar  4 23:29:57 silvy kernel:        f66873c0 f8a05d0e fffffffe f6146340 f66873c0 f66873c0 f66873f4 f8a05c8e 
Mar  4 23:29:57 silvy kernel:        f66873c0 f619f618 c01aafd5 00000202 00000000 f619f200 f66873c0 f619f200 
Mar  4 23:29:57 silvy kernel: Call Trace:
Mar  4 23:29:57 silvy kernel:  [device_del+21/398] device_del+0x15/0x18e
Mar  4 23:29:57 silvy kernel:  [device_unregister+8/16] device_unregister+0x8/0x10
Mar  4 23:29:57 silvy kernel:  [<f8a05d0e>] destroy_serial+0x80/0xcc [usbserial]
Mar  4 23:29:57 silvy kernel:  [<f8a05c8e>] destroy_serial+0x0/0xcc [usbserial]
Mar  4 23:29:57 silvy kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
Mar  4 23:29:57 silvy kernel:  [<f8a057f7>] usb_serial_disconnect+0x81/0xaa [usbserial]
Mar  4 23:29:57 silvy kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
Mar  4 23:29:57 silvy kernel:  [<f887fcc8>] usb_unbind_interface+0x2a/0x59 [usbcore]
Mar  4 23:29:57 silvy kernel:  [__device_release_driver+110/139] __device_release_driver+0x6e/0x8b
Mar  4 23:29:57 silvy kernel:  [device_release_driver+29/50] device_release_driver+0x1d/0x32
Mar  4 23:29:57 silvy kernel:  [bus_remove_device+113/129] bus_remove_device+0x71/0x81
Mar  4 23:29:57 silvy kernel:  [device_del+308/398] device_del+0x134/0x18e
Mar  4 23:29:57 silvy kernel:  [<f887e54c>] usb_disable_device+0x5c/0xbb [usbcore]
Mar  4 23:29:57 silvy kernel:  [<f887afdb>] usb_disconnect+0x82/0x104 [usbcore]
Mar  4 23:29:57 silvy kernel:  [<f887afc9>] usb_disconnect+0x70/0x104 [usbcore]
Mar  4 23:29:57 silvy kernel:  [<f887b9c8>] hub_thread+0x30b/0x9db [usbcore]
Mar  4 23:29:57 silvy kernel:  [__activate_task+28/40] __activate_task+0x1c/0x28
Mar  4 23:29:57 silvy kernel:  [autoremove_wake_function+0/51] autoremove_wake_function+0x0/0x33
Mar  4 23:29:57 silvy kernel:  [<f887b6bd>] hub_thread+0x0/0x9db [usbcore]
Mar  4 23:29:57 silvy kernel:  [kthread+155/191] kthread+0x9b/0xbf
Mar  4 23:29:57 silvy kernel:  [kthread+0/191] kthread+0x0/0xbf
Mar  4 23:29:57 silvy kernel:  [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10
Mar  4 23:29:57 silvy kernel:  =======================
Mar  4 23:29:57 silvy kernel: Code: 8b 4b 04 8d 46 04 89 43 04 89 5e 04 89 48 04 89 01 ff 4a 14 8b 42 08 a8 08 74 07 5b 5e e9 83 09 00 00 5b 5e c3 56 89 c6 53 8b 00 <8b> 58 0c 89 e0 25 00 e0 ff ff ff 40 14 89 f0 e8 f5 fe ff ff 85 
Mar  4 23:29:57 silvy kernel: EIP: [klist_del+6/69] klist_del+0x6/0x45 SS:ESP 0068:f742fe24

[BUG] sdhci regression in 2.6.21-rc2

[Mark Lord]

Another regression, for Pierre Ossman this time.

My syslog gets spammed like this (below) on suspend/resume (to RAM) cycles.
Worked fine, without all of the noise, in all previous kernels up to 2.6.20+.


Mar  4 23:28:45 silvy logger: suspending
Mar  4 23:29:09 silvy kernel: Stopping tasks ... done.
Mar  4 23:29:09 silvy kernel: Suspending console(s)
Mar  4 23:29:09 silvy kernel: pl2303 5-1.3:1.0: no suspend for driver pl2303?
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:03:01.2 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1f.2 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1e.2 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1d.7 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1d.3 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled
Mar  4 23:29:09 silvy kernel: ACPI: PCI interrupt for device 0000:00:1d.0 disabled
Mar  4 23:29:09 silvy kernel: Intel machine check architecture supported.
Mar  4 23:29:09 silvy kernel: Intel machine check reporting enabled on CPU#0.
Mar  4 23:29:09 silvy kernel: Back to C!
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:01.0 at offset 7 (was 2000d0d0, writing d0d0)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:01.0 at offset 3 (was 10000, writing 10010)
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
Mar  4 23:29:09 silvy kernel: usb usb1: root hub lost power or was reset
Mar  4 23:29:09 silvy kernel: PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 18
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20a)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 8 (was 1, writing bf61)
Mar  4 23:29:09 silvy kernel: usb usb2: root hub lost power or was reset
Mar  4 23:29:09 silvy kernel: PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 19
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 309)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 8 (was 1, writing bf41)
Mar  4 23:29:09 silvy kernel: usb usb3: root hub lost power or was reset
Mar  4 23:29:09 silvy kernel: PCI: Enabling device 0000:00:1d.3 (0000 -> 0001)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 17
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1d.3 to 64
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 407)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1d.3 at offset 8 (was 1, writing bf21)
Mar  4 23:29:09 silvy kernel: usb usb4: root hub lost power or was reset
Mar  4 23:29:09 silvy kernel: mmc0: Got command interrupt even though no command operation was in progress.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Card is consuming too much power!
Mar  4 23:29:09 silvy kernel: mmc0: Unexpected interrupt 0x00800000.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 16 (level, low) -> IRQ 16
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1d.7 to 64
Mar  4 23:29:09 silvy kernel: usb usb5: root hub lost power or was reset
Mar  4 23:29:09 silvy kernel: ehci_hcd 0000:00:1d.7: debug port 1
Mar  4 23:29:09 silvy kernel: PCI: cache line size of 32 is not supported by device 0000:00:1d.7
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 9 (was 10001, writing 8bf18801)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 8 (was 0, writing dfc0dfc0)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 7 (was 2280e0f0, writing 22802020)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 6 (was 20030300, writing 20070300)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 1 (was 100005, writing 100107)
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.2 at offset f (was 100, writing 10b)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 7 (was 0, writing dffffd00)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 6 (was 0, writing dffffe00)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 5 (was 1, writing ec41)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 4 (was 1, writing ed01)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 1 (was 2900000, writing 2900003)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 16 (level, low) -> IRQ 16
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1e.2 to 64
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Controller never released inhibit bit(s).
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x2 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x4 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: mmc0: Reset 0x1 never completed.
Mar  4 23:29:09 silvy kernel: sdhci: ============== REGISTER DUMP ==============
Mar  4 23:29:09 silvy kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Mar  4 23:29:09 silvy kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Mar  4 23:29:09 silvy kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Mar  4 23:29:09 silvy kernel: sdhci: ===========================================
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1f.0 at offset 1 (was 2000007, writing 2000107)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1f.2 at offset f (was 200, writing 20a)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1f.2 at offset 9 (was d0000, writing 0)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 18
Mar  4 23:29:09 silvy kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1f.3 at offset f (was 200, writing 20a)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:00:1f.3 at offset 1 (was 2800001, writing 2800101)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:01:00.0 at offset f (was 1ff, writing 10b)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:01:00.0 at offset c (was 0, writing dfe00000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:01:00.0 at offset 3 (was 0, writing 10)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:00.0 at offset f (was 100, writing 109)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:00.0 at offset 4 (was 0, writing dfcfe000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:00.0 at offset 3 (was 0, writing 4000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 100000, writing 100106)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 19
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset f (was 7800100, writing 58001ff)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset e (was 0, writing 24fc)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset d (was 0, writing 2400)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset c (was 0, writing 20fc)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset b (was 0, writing 2000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset a (was 0, writing 8ffff000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset 9 (was 0, writing 8c000000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset 8 (was 0, writing 8bfff000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset 7 (was 0, writing 88000000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset 6 (was 0, writing b0070403)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset 4 (was 0, writing dfc00000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.0 at offset 3 (was 820000, writing 82a800)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.1 at offset 4 (was 0, writing dfcfc800)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.1 at offset 3 (was 800000, writing 804000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.1 at offset 1 (was 2100000, writing 2100106)
Mar  4 23:29:09 silvy kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19]  MMIO=[dfcfc800-dfcfcfff]  Max Packet=[2048]  IR/IT contexts=[4/4]
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.2 at offset 4 (was 0, writing dfcfc700)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.2 at offset 3 (was 800000, writing 804000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:01.2 at offset 1 (was 2100000, writing 2100106)
Mar  4 23:29:09 silvy kernel: ACPI: PCI Interrupt 0000:03:01.2[C] -> GSI 17 (level, low) -> IRQ 18
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:03.0 at offset f (was 18030100, writing 1803010a)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:03.0 at offset 4 (was 0, writing dfcfd000)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:03.0 at offset 3 (was 0, writing 4010)
Mar  4 23:29:09 silvy kernel: PM: Writing back config space on device 0000:03:03.0 at offset 1 (was 2900000, writing 2900112)
Mar  4 23:29:09 silvy kernel: pnp: Device 00:04 does not support activation.
Mar  4 23:29:09 silvy kernel: pnp: Device 00:05 does not support activation.
Mar  4 23:29:09 silvy kernel:  usbdev5.2_ep00: PM: resume from 0, parent 5-1 still 2
Mar  4 23:29:09 silvy kernel: hub 5-1:1.0: PM: resume from 2, parent 5-1 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.2_ep81: PM: resume from 0, parent 5-1:1.0 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.2: PM: resume from 0, parent 5-1 still 2
Mar  4 23:29:09 silvy kernel: usb 5-1.3: PM: resume from 2, parent 5-1 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.3_ep00: PM: resume from 0, parent 5-1.3 still 2
Mar  4 23:29:09 silvy kernel: pl2303 5-1.3:1.0: PM: resume from 2, parent 5-1.3 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.3_ep81: PM: resume from 0, parent 5-1.3:1.0 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.3_ep02: PM: resume from 0, parent 5-1.3:1.0 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.3_ep83: PM: resume from 0, parent 5-1.3:1.0 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.3: PM: resume from 0, parent 5-1.3 still 2
Mar  4 23:29:09 silvy kernel: usb 5-1.4: PM: resume from 2, parent 5-1 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.4_ep00: PM: resume from 0, parent 5-1.4 still 2
Mar  4 23:29:09 silvy kernel: usbhid 5-1.4:1.0: PM: resume from 2, parent 5-1.4 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.4_ep81: PM: resume from 0, parent 5-1.4:1.0 still 2
Mar  4 23:29:09 silvy kernel:  usbdev5.4: PM: resume from 0, parent 5-1.4 still 2
Mar  4 23:29:09 silvy kernel: pl2303 ttyUSB0: PM: resume from 0, parent 5-1.3:1.0 still 2
Mar  4 23:29:09 silvy kernel: Restarting tasks ... done.
Mar  4 23:29:09 silvy NetworkManager: <information>^ISWITCH: terminating current connection 'eth0' because it's no longer valid. 
Mar  4 23:29:09 silvy NetworkManager: <information>^IDeactivating device eth0. 
Mar  4 23:29:09 silvy kernel: usb 5-1: USB disconnect, address 2
Mar  4 23:29:09 silvy kernel: usb 5-1.3: USB disconnect, address 3
Mar  4 23:29:09 silvy kernel: pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
Mar  4 23:29:09 silvy kernel: pl2303 5-1.3:1.0: device disconnected
Mar  4 23:29:09 silvy kernel: usb 5-1.4: USB disconnect, address 4
Mar  4 23:29:09 silvy kernel: ata1.00: configured for UDMA/100
Mar  4 23:29:09 silvy kernel: SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
Mar  4 23:29:09 silvy kernel: sda: Write Protect is off
Mar  4 23:29:09 silvy kernel: sda: Mode Sense: 00 3a 00 00
Mar  4 23:29:09 silvy kernel: SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  4 23:29:09 silvy dhclient: DHCPRELEASE on eth0 to 10.0.0.2 port 67
Mar  4 23:29:09 silvy kernel: usb 5-1: new high speed USB device using ehci_hcd and address 5
Mar  4 23:29:09 silvy dhcdbd: dhco_value_from_text: Non ascii char outside valid hex string:  0 
Mar  4 23:29:09 silvy dhcdbd: dhco_input_option: Value silvy cannot be converted to type X 
Mar  4 23:29:09 silvy dhcdbd: dhco_parse_option_settings: bad option setting: old_host_name = silvy 
Mar  4 23:29:10 silvy kernel: usb 5-1: configuration #1 chosen from 1 choice
Mar  4 23:29:10 silvy kernel: hub 5-1:1.0: USB hub found
Mar  4 23:29:10 silvy kernel: hub 5-1:1.0: 4 ports detected
Mar  4 23:29:10 silvy kernel: ata2.00: configured for UDMA/33
Mar  4 23:29:10 silvy kernel: [drm] Loading R300 Microcode
Mar  4 23:29:10 silvy kernel: usb 5-1.3: new full speed USB device using ehci_hcd and address 6
Mar  4 23:29:10 silvy kernel: usb 5-1.3: configuration #1 chosen from 1 choice
Mar  4 23:29:10 silvy kernel: pl2303 5-1.3:1.0: pl2303 converter detected
Mar  4 23:29:10 silvy kernel: usb 5-1.3: pl2303 converter now attached to ttyUSB0
Mar  4 23:29:10 silvy NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
Mar  4 23:29:10 silvy NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
Mar  4 23:29:10 silvy NetworkManager: <information>^Imatch 
Mar  4 23:29:10 silvy NetworkManager: <information>^Imatch 
Mar  4 23:29:10 silvy kernel: usb 5-1.4: new low speed USB device using ehci_hcd and address 7
Mar  4 23:29:10 silvy kernel: usb 5-1.4: configuration #1 chosen from 1 choice
Mar  4 23:29:10 silvy kernel: input: Logitech Optical USB Mouse as /class/input/input8
Mar  4 23:29:10 silvy kernel: input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:1d.7-1.4
Mar  4 23:29:11 silvy kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
Mar  4 23:29:11 silvy kernel: b44: eth0: Flow control is off for TX and off for RX.
Mar  4 23:29:11 silvy NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link. 
Mar  4 23:29:11 silvy NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'. 
Mar  4 23:29:11 silvy NetworkManager: <information>^IWill activate connection 'eth0'. 
Mar  4 23:29:11 silvy NetworkManager: <information>^IDevice eth0 activation scheduled... 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) started... 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started... 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete. 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting... 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful. 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete. 
Mar  4 23:29:11 silvy NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started... 
Mar  4 23:29:11 silvy NetworkManager: <information>^Imatch 
Mar  4 23:29:12 silvy NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction. 
Mar  4 23:29:12 silvy NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
Mar  4 23:29:12 silvy NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0 
Mar  4 23:29:13 silvy NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0 
Mar  4 23:29:15 silvy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Mar  4 23:29:15 silvy dhclient: DHCPOFFER from 10.0.0.2
Mar  4 23:29:15 silvy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar  4 23:29:15 silvy dhclient: DHCPACK from 10.0.0.2
Mar  4 23:29:15 silvy dhcdbd: dhco_value_from_text: Non ascii char outside valid hex string:  0 
Mar  4 23:29:15 silvy dhcdbd: dhco_input_option: Value silvy cannot be converted to type X 
Mar  4 23:29:15 silvy dhcdbd: dhco_parse_option_settings: bad option setting: new_host_name = silvy 
Mar  4 23:29:15 silvy dhcdbd: dhco_value_from_text: Non ascii char outside valid hex string:  0 
Mar  4 23:29:15 silvy dhcdbd: dhco_input_option: Value silvy cannot be converted to type X 
Mar  4 23:29:15 silvy dhcdbd: dhco_parse_option_settings: bad option setting: old_host_name = silvy 
Mar  4 23:29:15 silvy NetworkManager: <information>^IDHCP daemon state is now 2 (bound) for interface eth0 
Mar  4 23:29:15 silvy NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... 
Mar  4 23:29:15 silvy NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) started... 
Mar  4 23:29:15 silvy dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Mar  4 23:29:15 silvy dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Mar  4 23:29:15 silvy dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Mar  4 23:29:15 silvy NetworkManager: <information>^IRetrieved the following IP4 configuration from the DHCP daemon: 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  address 10.0.0.14 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  netmask 255.255.255.0 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  broadcast 10.0.0.255 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  gateway 10.0.0.2 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  nameserver 10.0.0.2 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  nameserver 206.191.0.140 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  nameserver 206.191.0.210 
Mar  4 23:29:15 silvy NetworkManager: <information>^I  domain name 'localnet.' 
Mar  4 23:29:15 silvy NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... 
Mar  4 23:29:15 silvy NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) complete. 
Mar  4 23:29:15 silvy NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) started... 
Mar  4 23:29:15 silvy dhclient: bound to 10.0.0.14 -- renewal in 37786 seconds.
Mar  4 23:29:16 silvy NetworkManager: <information>^IDHCP returned name servers but system has disabled dynamic modification! 
Mar  4 23:29:16 silvy NetworkManager: <information>^IActivation (eth0) successful, device activated. 
Mar  4 23:29:16 silvy NetworkManager: <information>^Imatch 
Mar  4 23:29:16 silvy NetworkManager: <information>^IActivation (eth0) Finish handler scheduled. 
Mar  4 23:29:16 silvy NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) complete. 

Re: [BUG] sdhci regression in 2.6.21-rc2

[Pierre Ossman]

Mark Lord wrote:
> Another regression, for Pierre Ossman this time.
> 
> My syslog gets spammed like this (below) on suspend/resume (to RAM) cycles.
> Worked fine, without all of the noise, in all previous kernels up to
> 2.6.20+.
> 

This looks like a PCI configuration issue. Can you bisect which commit caused
the issue? And what's the PCI address of the device?

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

Re: [BUG] sdhci regression in 2.6.21-rc2

[Mark Lord]

Pierre Ossman wrote:
> Mark Lord wrote:
>> Another regression, for Pierre Ossman this time.
>>
>> My syslog gets spammed like this (below) on suspend/resume (to RAM) cycles.
>> Worked fine, without all of the noise, in all previous kernels up to
>> 2.6.20+.
>>
> 
> This looks like a PCI configuration issue.

To me, it looks like a buggy driver "resume" sequence.
The low-level SDHCI driver is trying to use the device
before the PM/PCI stuff has restored the pre-suspend state.

> Can you bisect which commit caused the issue?

Nope.  I don't have time to run around that (huge) treadmill, thanks.

>And what's the PCI address of the device?

0000:03:01.2 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17)

So, from the syslog, we see that the machine suspends (to RAM):

>kernel: Stopping tasks ... done.
>kernel: Suspending console(s)
>kernel: pl2303 1-1.3:1.0: no suspend for driver pl2303?
>kernel: ACPI: PCI interrupt for device 0000:03:01.2 disabled
>kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1f.2 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1e.2 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1d.7 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1d.3 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled
>kernel: ACPI: PCI interrupt for device 0000:00:1d.0 disabled
>kernel: Intel machine check architecture supported.
>kernel: Intel machine check reporting enabled on CPU#0.

A few seconds later, I manually wake-up the machine.
It resumes (from RAM), and the PM code begins restoring PCI config
space for various device:

>kernel: Back to C!
>kernel: PM: Writing back config space on device 0000:00:01.0 at offset 7 (was 2000d0d0, writing d0d0)
>kernel: PM: Writing back config space on device 0000:00:01.0 at offset 3 (was 10000, writing 10010)
>kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
>kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
>kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
>kernel: usb usb2: root hub lost power or was reset
>kernel: PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
>kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 18
>kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64
>kernel: PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20a)
>kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 8 (was 1, writing bf61)
>kernel: usb usb3: root hub lost power or was reset
>kernel: PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
>kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 19
>kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64
>kernel: PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 309)
>kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 8 (was 1, writing bf41)
>kernel: usb usb4: root hub lost power or was reset
>kernel: PCI: Enabling device 0000:00:1d.3 (0000 -> 0001)
>kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 17
>kernel: PCI: Setting latency timer of device 0000:00:1d.3 to 64
>kernel: PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 407)
>kernel: PM: Writing back config space on device 0000:00:1d.3 at offset 8 (was 1, writing bf21)
>kernel: usb usb5: root hub lost power or was reset

But.. in the middle of all of this, we now see the SHDCI code
trying to talk to its as-yet-not-restored device, and being rather
noisy about it all:

>kernel: sdhci: ============== REGISTER DUMP ==============
>kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
>kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
>kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
>kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
>kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
>kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
>kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
>kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
>kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
>kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
>kernel: sdhci: ===========================================
>kernel: mmc0: Card is consuming too much power!
>kernel: mmc0: Unexpected interrupt 0x00800000.
>kernel: sdhci: ============== REGISTER DUMP ==============
>kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
>kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
>kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
>kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
>kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
>kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
>kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
>kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
>kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
>kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
>kernel: sdhci: ===========================================

Meanwhile, the PM code is also continuing to bring up devices:

>kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 16 (level, low) -> IRQ 16
>kernel: PCI: Setting latency timer of device 0000:00:1d.7 to 64
>kernel: usb usb1: root hub lost power or was reset
>kernel: ehci_hcd 0000:00:1d.7: debug port 1
>kernel: PCI: cache line size of 32 is not supported by device 0000:00:1d.7
>kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 9 (was 10001, writing 8bf18801)
>kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 8 (was 0, writing dfc0dfc0)
>kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 7 (was 2280e0f0, writing 22802020)
>kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 6 (was 20030300, writing 20070300)
>kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 1 (was 100005, writing 100107)
>kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64
>kernel: PM: Writing back config space on device 0000:00:1e.2 at offset f (was 100, writing 10b)
>kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 7 (was 0, writing dffffd00)
>kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 6 (was 0, writing dffffe00)
>kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 5 (was 1, writing ec41)
>kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 4 (was 1, writing ed01)
>kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 1 (was 2900000, writing 2900003)
>kernel: ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 16 (level, low) -> IRQ 16
>kernel: PCI: Setting latency timer of device 0000:00:1e.2 to 64

And the SDHCI continues to spam the syslog:

>kernel: mmc0: Controller never released inhibit bit(s).
>kernel: sdhci: ============== REGISTER DUMP ==============
>kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
>kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
>kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
>kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
>kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
>kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
>kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
>kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
>kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
>kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
>kernel: sdhci: ===========================================
>kernel: mmc0: Reset 0x2 never completed.
>kernel: sdhci: ============== REGISTER DUMP ==============
>kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
>kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
>kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
>kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
>kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
>kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
>kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
>kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
>kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
>kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
>kernel: sdhci: ===========================================
>kernel: mmc0: Reset 0x4 never completed.
>kernel: sdhci: ============== REGISTER DUMP ==============
>kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
>kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
>kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
>kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
>kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
>kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
>kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
>kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
>kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
>kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
>kernel: sdhci: ===========================================
...
<snip>

And eventually we see more PM recovery messages:

>kernel: PM: Writing back config space on device 0000:00:1f.0 at offset 1 (was 2000007, writing 2000107)
>kernel: PM: Writing back config space on device 0000:00:1f.2 at offset f (was 200, writing 20a)
>kernel: PM: Writing back config space on device 0000:00:1f.2 at offset 9 (was d0000, writing 0)
>kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 18
>kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
>kernel: PM: Writing back config space on device 0000:00:1f.3 at offset f (was 200, writing 20a)
>kernel: PM: Writing back config space on device 0000:00:1f.3 at offset 1 (was 2800001, writing 2800101)
>kernel: PM: Writing back config space on device 0000:01:00.0 at offset f (was 1ff, writing 10b)
>kernel: PM: Writing back config space on device 0000:01:00.0 at offset c (was 0, writing dfe00000)
>kernel: PM: Writing back config space on device 0000:01:00.0 at offset 3 (was 0, writing 10)
>kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
>kernel: PM: Writing back config space on device 0000:03:00.0 at offset f (was 100, writing 109)
>kernel: PM: Writing back config space on device 0000:03:00.0 at offset 4 (was 0, writing dfcfe000)
>kernel: PM: Writing back config space on device 0000:03:00.0 at offset 3 (was 0, writing 4000)
>kernel: PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 100000, writing 100106)
>kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 19

And here, finally, we see the PM code restoring state for the SDHCI controller:

>kernel: PM: Writing back config space on device 0000:03:01.0 at offset f (was 7800100, writing 58001ff)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset e (was 0, writing 24fc)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset d (was 0, writing 2400)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset c (was 0, writing 20fc)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset b (was 0, writing 2000)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset a (was 0, writing 8ffff000)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset 9 (was 0, writing 8c000000)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset 8 (was 0, writing 8bfff000)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset 7 (was 0, writing 88000000)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset 6 (was 0, writing b0070403)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset 4 (was 0, writing dfc00000)
>kernel: PM: Writing back config space on device 0000:03:01.0 at offset 3 (was 820000, writing 82a800)
>kernel: PM: Writing back config space on device 0000:03:01.1 at offset 4 (was 0, writing dfcfc800)
>kernel: PM: Writing back config space on device 0000:03:01.1 at offset 3 (was 800000, writing 804000)
>kernel: PM: Writing back config space on device 0000:03:01.1 at offset 1 (was 2100000, writing 2100106)
>kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19]  MMIO=[dfcfc800-dfcfcfff]  Max Packet=[2048]  IR/IT contexts=[4/4]
>kernel: PM: Writing back config space on device 0000:03:01.2 at offset 4 (was 0, writing dfcfc700)
>kernel: PM: Writing back config space on device 0000:03:01.2 at offset 3 (was 800000, writing 804000)
>kernel: PM: Writing back config space on device 0000:03:01.2 at offset 1 (was 2100000, writing 2100106)
>kernel: ACPI: PCI Interrupt 0000:03:01.2[C] -> GSI 17 (level, low) -> IRQ 18
>kernel: PM: Writing back config space on device 0000:03:03.0 at offset f (was 18030100, writing 1803010a)
>kernel: PM: Writing back config space on device 0000:03:03.0 at offset 4 (was 0, writing dfcfd000)
>kernel: PM: Writing back config space on device 0000:03:03.0 at offset 3 (was 0, writing 4010)
>kernel: PM: Writing back config space on device 0000:03:03.0 at offset 1 (was 2900000, writing 2900112)

So, somewhere, the SDHCI drivers need to be told to stay dormant until their
device has been recovered, just like most other device drivers do.

Cheers

Mark

Re: [BUG] sdhci regression in 2.6.21-rc2

[Mark Lord]

Mark Lord wrote:
> Pierre Ossman wrote:
>> Mark Lord wrote:
>>> Another regression, for Pierre Ossman this time.
>>>
>>> My syslog gets spammed like this (below) on suspend/resume (to RAM) 
>>> cycles.
>>> Worked fine, without all of the noise, in all previous kernels up to
>>> 2.6.20+.
>>>
>>
>> This looks like a PCI configuration issue.
> 
> To me, it looks like a buggy driver "resume" sequence.
> The low-level SDHCI driver is trying to use the device
> before the PM/PCI stuff has restored the pre-suspend state.
...

I've dug a bit deeper, instrumenting the driver,
and found/fixed the problem.

The interrupt is shared with another device, which resumes
earlier than the sdhci controller, and generates an interrupt.

The sdhci interrupt handler runs, sees 0xffffffff in its own
device's interrupt status, and tries to handle it..
The reason for the 0xffffffff is that the device is still
suspended, and *all* regs are reading back 0xffffffff.

So.. the suspend routine should de-register the irq handler,
and the resume routine should re-register it again.

Or perhaps a simpler kludge like this one, which fixes it for me:

Signed-off-by:  Mark Lord <mlord@pobox.com>
---
--- linux/drivers/mmc/sdhci.c.orig	2007-03-02 15:06:31.000000000 -0500
+++ linux/drivers/mmc/sdhci.c	2007-03-05 10:13:51.000000000 -0500
@@ -994,7 +994,7 @@
 
 	intmask = readl(host->ioaddr + SDHCI_INT_STATUS);
 
-	if (!intmask) {
+	if (!intmask || intmask == 0xffffffff) {
 		result = IRQ_NONE;
 		goto out;
 	}

Re: [BUG] sdhci regression in 2.6.21-rc2

[Andrew Morton]

On Mon, 05 Mar 2007 10:19:55 -0500 Mark Lord <lkml@rtr.ca> wrote:

> The interrupt is shared with another device, which resumes
> earlier than the sdhci controller, and generates an interrupt.
> 
> The sdhci interrupt handler runs, sees 0xffffffff in its own
> device's interrupt status, and tries to handle it..
> The reason for the 0xffffffff is that the device is still
> suspended, and *all* regs are reading back 0xffffffff.
> 
> So.. the suspend routine should de-register the irq handler,
> and the resume routine should re-register it again.
> 
> Or perhaps a simpler kludge like this one, which fixes it for me:
> 
> Signed-off-by:  Mark Lord <mlord@pobox.com>
> ---
> --- linux/drivers/mmc/sdhci.c.orig	2007-03-02 15:06:31.000000000 -0500
> +++ linux/drivers/mmc/sdhci.c	2007-03-05 10:13:51.000000000 -0500
> @@ -994,7 +994,7 @@
>  
>  	intmask = readl(host->ioaddr + SDHCI_INT_STATUS);
>  
> -	if (!intmask) {
> +	if (!intmask || intmask == 0xffffffff) {
>  		result = IRQ_NONE;
>  		goto out;
>  	}

This is actually pretty standard handling for a lot of drivers: any
device which can appear on a cardbus or other hot-unpluggable bus and which
shares interupts needs such treatment.

I don't know whether anything which this driver drives could ever appear on
such a bus, but I'm inclined to just apply it into 2.6.21.

(I'm also inclined to drop the darned mmc tree - am getting rather tired of
people moving their files all over the tree all the time).

Re: [BUG] sdhci regression in 2.6.21-rc2

[Pierre Ossman]

Andrew Morton wrote:
>
> (I'm also inclined to drop the darned mmc tree - am getting rather tired of
> people moving their files all over the tree all the time).
>
>   

Fine, I can stop bothering with putting up a test tree and just push the
stuff to Linus directly if that is what you prefer. Or is moving files
around barred from the kernel?

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

Re: [BUG] sdhci regression in 2.6.21-rc2

[Andrew Morton]

On Tue, 06 Mar 2007 06:47:32 +0100 Pierre Ossman <drzeus-list@drzeus.cx> wrote:

> Andrew Morton wrote:
> >
> > (I'm also inclined to drop the darned mmc tree - am getting rather tired of
> > people moving their files all over the tree all the time).
> >
> >   
> 
> Fine, I can stop bothering with putting up a test tree and just push the
> stuff to Linus directly if that is what you prefer. Or is moving files
> around barred from the kernel?

Oh, it's just a pain in the ass.  Please don't do it lightly - if there's a
really good reason then OK.

Plus it helps if the massive file move isn't left sitting in some external
tree for months.  I mean, it's usually a trivial thing, so do it just a
week before the pull is due.  

But whatever.  What are we going to do about $SUBJECT?

Re: [BUG] sdhci regression in 2.6.21-rc2

[Pierre Ossman]

Andrew Morton wrote:
> Oh, it's just a pain in the ass.  Please don't do it lightly - if there's a
> really good reason then OK.
>   

The mmc code is a mess (mostly my fault for the addition of SD support)
and I'm trying to break things apart to clear the code up. That
unfortunately meant moving files around.

> Plus it helps if the massive file move isn't left sitting in some external
> tree for months.  I mean, it's usually a trivial thing, so do it just a
> week before the pull is due.  
>
>   

My goal with putting it in -mm was to give people a chance to cry bloody
murder before I merged the stuff (which I intend to do immediately post
2.6.21). The changes are all over the place, so to ease my mind I prefer
to have it simmer for a while.

As to making your life easier, send patches to the mmc layer my way and
I'll handle the conflicts. I made the mess so it's only fair that I have
to clean it up.

> But whatever.  What are we going to do about $SUBJECT?
>   

It should go in now, along with a fix to unregister the interrupt. I
have a bunch of fixes I intend to push to Linus today and I'll include
this in that group.

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

Re: [BUG] sdhci regression in 2.6.21-rc2

[Pierre Ossman]

Mark Lord wrote:
>
> But.. in the middle of all of this, we now see the SHDCI code
> trying to talk to its as-yet-not-restored device, and being rather
> noisy about it all:
>

Not quite. I'd say it's the kernel calling the interrupt handler of a
currently sleeping device. Since we're seeing this problem I assume the
kernel's interrupt code isn't aware of PM states?

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

Re: [BUG] sdhci regression in 2.6.21-rc2

[Pierre Ossman]

Pierre Ossman wrote:
> Mark Lord wrote:
>> But.. in the middle of all of this, we now see the SHDCI code
>> trying to talk to its as-yet-not-restored device, and being rather
>> noisy about it all:
>>
> 
> Not quite. I'd say it's the kernel calling the interrupt handler of a
> currently sleeping device. Since we're seeing this problem I assume the
> kernel's interrupt code isn't aware of PM states?
> 

Hmm... I guess it can't be as the interrupt handler isn't associated with a
device, just a random pointer.

So either release the interrupt (which seems a bit unsafe as then we might not
get it back), or handle states at the start of the isr.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

Re: [BUG] sdhci regression in 2.6.21-rc2

[Mark Lord]

Pierre Ossman wrote:
> Pierre Ossman wrote:
>> I'd say it's the kernel calling the interrupt handler of a
>> currently sleeping device. Since we're seeing this problem I assume the
>> kernel's interrupt code isn't aware of PM states?
>
> Hmm... I guess it can't be as the interrupt handler isn't associated with a
> device, just a random pointer.
> 
> So either release the interrupt (which seems a bit unsafe as then we might not
> get it back), or handle states at the start of the isr.

>From linux/Documentation/power/pci.txt:

> A reference implementation
> -------------------------
> .suspend()
> {
>         /* driver specific operations */
> 
>         /* Disable IRQ */
>         free_irq();
>         /* If using MSI */
>         pci_disable_msi();
> 
>         pci_save_state();
>         pci_enable_wake();
>         /* Disable IO/bus master/irq router */
>         pci_disable_device();
>         pci_set_power_state(pci_choose_state());
> }
> 
> .resume()
> {
>         pci_set_power_state(PCI_D0);
>         pci_restore_state();
>         /* device's irq possibly is changed, driver should take care */
>         pci_enable_device();
>         pci_set_master();
> 
>         /* if using MSI, device's vector possibly is changed */
>         pci_enable_msi();
> 
>         request_irq();
>         /* driver specific operations; */
> }

Re: [BUG] sdhci regression in 2.6.21-rc2

[Pierre Ossman]

Mark Lord wrote:
> Pierre Ossman wrote:
>>
>> Hmm... I guess it can't be as the interrupt handler isn't associated
>> with a
>> device, just a random pointer.
>>
>> So either release the interrupt (which seems a bit unsafe as then we
>> might not
>> get it back), or handle states at the start of the isr.
>
> From linux/Documentation/power/pci.txt:
>

That conveniently leaves out the part of how to handle when we're not
getting our stuff back. ;)

But it seems to be the easier route anyway... I'll whip up a patch.

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

Re: [BUG] sdhci regression in 2.6.21-rc2

[Mark Lord]

Pierre Ossman wrote:
> Mark Lord wrote:
>
>> From linux/Documentation/power/pci.txt:
>>
> That conveniently leaves out the part of how to handle when we're not
> getting our stuff back. ;)
> 
> But it seems to be the easier route anyway... I'll whip up a patch.

It's probably best all-round.

But another simpler way is to just set a global "am_suspended" bool
in the _suspend() code, and clear it again in the _resume() code,
and check it in the irq handler() code.

And the test for 0xffffffff (my simple patch) is probably good
to have regardless inside the irq handler().

Cheers

Re: [BUG} usb regression in 2.6.21-rc2-git3

[Mark Lord]

Mark Lord wrote:
>
> Here's another one for Greg:
> 
> I have a Targus USB 1.1 "dock", basically a hub with built-in
> serial, parallel, PS/2 KB, PS/2 Mouse, and extra USB ports.
> 
> Simply connecting, and then disconnecting it causes an oops with 
> 2.6.21-rc2:
..

Same behaviour with a second, different USB 1.1 "dock" here as well:

Mar  4 23:40:16 silvy kernel: usb 5-8: new high speed USB device using ehci_hcd and address 5
Mar  4 23:40:16 silvy kernel: usb 5-8: configuration #1 chosen from 1 choice
Mar  4 23:40:16 silvy kernel: hub 5-8:1.0: USB hub found
Mar  4 23:40:16 silvy kernel: hub 5-8:1.0: 4 ports detected
Mar  4 23:40:16 silvy kernel: usb 5-8.4: new full speed USB device using ehci_hcd and address 6
Mar  4 23:40:17 silvy kernel: usb 5-8.4: configuration #1 chosen from 1 choice
Mar  4 23:40:17 silvy kernel: hub 5-8.4:1.0: USB hub found
Mar  4 23:40:17 silvy kernel: hub 5-8.4:1.0: 4 ports detected
Mar  4 23:40:17 silvy kernel: usb 5-8.4.1: new full speed USB device using ehci_hcd and address 7
Mar  4 23:40:17 silvy kernel: usb 5-8.4.1: configuration #1 chosen from 1 choice
Mar  4 23:40:17 silvy kernel: usb 5-8.4.3: new low speed USB device using ehci_hcd and address 8
Mar  4 23:40:17 silvy kernel: usb 5-8.4.3: configuration #1 chosen from 1 choice
Mar  4 23:40:17 silvy kernel: input: Composite USB PS2 Converter USB to PS2 Adaptor  v1.12 as /class/input/input8
Mar  4 23:40:17 silvy kernel: input: USB HID v1.10 Keyboard [Composite USB PS2 Converter USB to PS2 Adaptor  v1.12] on usb-0000:00:1d.7-8.4.3
Mar  4 23:40:17 silvy kernel: input: Composite USB PS2 Converter USB to PS2 Adaptor  v1.12 as /class/input/input9
Mar  4 23:40:17 silvy kernel: input: USB HID v1.10 Mouse [Composite USB PS2 Converter USB to PS2 Adaptor  v1.12] on usb-0000:00:1d.7-8.4.3
Mar  4 23:40:17 silvy kernel: usb 5-8.4.4: new full speed USB device using ehci_hcd and address 9
Mar  4 23:40:17 silvy kernel: usb 5-8.4.4: configuration #1 chosen from 1 choice
Mar  4 23:40:17 silvy kernel: pl2303 5-8.4.4:1.0: pl2303 converter detected
Mar  4 23:40:17 silvy kernel: usb-serial ttyUSB0: Error registering port device, continuing
Mar  4 23:40:17 silvy kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 7 if 0 alt 1 proto 2 vid 0x0B39 pid 0x0801
Mar  4 23:40:17 silvy kernel: usbcore: registered new interface driver usblp
Mar  4 23:40:17 silvy kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Mar  4 23:41:05 silvy kernel: usb 5-8: USB disconnect, address 5
Mar  4 23:41:05 silvy kernel: usb 5-8.4: USB disconnect, address 6
Mar  4 23:41:05 silvy kernel: usb 5-8.4.1: USB disconnect, address 7
Mar  4 23:41:05 silvy kernel: drivers/usb/class/usblp.c: usblp0: removed
Mar  4 23:41:05 silvy kernel: usb 5-8.4.3: USB disconnect, address 8
Mar  4 23:41:05 silvy kernel: usb 5-8.4.4: USB disconnect, address 9
Mar  4 23:41:05 silvy kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 0000000c
Mar  4 23:41:05 silvy kernel:  printing eip:
Mar  4 23:41:05 silvy kernel: c027c251
Mar  4 23:41:05 silvy kernel: *pde = 00000000
Mar  4 23:41:05 silvy kernel: Oops: 0000 [#1]
Mar  4 23:41:05 silvy kernel: PREEMPT 
Mar  4 23:41:05 silvy kernel: Modules linked in: usblp radeon drm nfsd exportfs lockd nfs_acl sunrpc acpi_cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_stats freq_table cpufreq_conservative ac fan button thermal video battery container processor rfcomm l2cap bluetooth cfq_iosched deflate zlib_deflate twofish twofish_common serpent blowfish des cbc ecb blkcipher aes xcbc sha256 sha1 crypto_null af_key af_packet sbp2 usbhid hid pl2303 usbserial mousedev pcmcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore ipw2200 ahci psmouse serio_raw pcspkr ieee80211 ieee80211_crypt sdhci mmc_core snd_page_alloc yenta_socket rsrc_nonstatic firmware_class ohci1394 ieee1394 b44 mii pcmcia_core intel_agp ehci_hcd uhci_hcd usbcore agpgart sg sr_mod cdrom unix
Mar  4 23:41:05 silvy kernel: CPU:    0
Mar  4 23:41:05 silvy kernel: EIP:    0060:[klist_del+6/69]    Not tainted VLI
Mar  4 23:41:05 silvy kernel: EFLAGS: 00010286   (2.6.21-rc2-git3 #5)
Mar  4 23:41:05 silvy kernel: EIP is at klist_del+0x6/0x45
Mar  4 23:41:05 silvy kernel: eax: 00000000   ebx: f6730a78   ecx: 00000001   edx: f63f5248
Mar  4 23:41:05 silvy kernel: esi: f6730a88   edi: f63f5240   ebp: f6706618   esp: f7ba7e00
Mar  4 23:41:05 silvy kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Mar  4 23:41:05 silvy kernel: Process khubd (pid: 1925, ti=f7ba6000 task=f7c275e0 task.ti=f7ba6000)
Mar  4 23:41:05 silvy kernel: Stack: f6730a78 00000001 c01fb571 f6730a78 00000001 f63f5240 00000000 c01fb6f2 
Mar  4 23:41:05 silvy kernel:        f63f5240 f89ffd0e fffffffe f6c62a40 f63f5240 f63f5240 f63f5274 f89ffc8e 
Mar  4 23:41:05 silvy kernel:        f63f5240 f6706618 c01aafd5 00000202 00000000 f6730a00 f63f5240 f6730a00 
Mar  4 23:41:05 silvy kernel: Call Trace:
Mar  4 23:41:05 silvy kernel:  [device_del+21/398] device_del+0x15/0x18e
Mar  4 23:41:05 silvy kernel:  [device_unregister+8/16] device_unregister+0x8/0x10
Mar  4 23:41:05 silvy kernel:  [<f89ffd0e>] destroy_serial+0x80/0xcc [usbserial]
Mar  4 23:41:05 silvy kernel:  [<f89ffc8e>] destroy_serial+0x0/0xcc [usbserial]
Mar  4 23:41:05 silvy kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
Mar  4 23:41:05 silvy kernel:  [<f89ff7f7>] usb_serial_disconnect+0x81/0xaa [usbserial]
Mar  4 23:41:05 silvy kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
Mar  4 23:41:05 silvy kernel:  [<f887fcc8>] usb_unbind_interface+0x2a/0x59 [usbcore]
Mar  4 23:41:05 silvy kernel:  [__device_release_driver+110/139] __device_release_driver+0x6e/0x8b
Mar  4 23:41:05 silvy kernel:  [device_release_driver+29/50] device_release_driver+0x1d/0x32
Mar  4 23:41:05 silvy kernel:  [bus_remove_device+113/129] bus_remove_device+0x71/0x81
Mar  4 23:41:05 silvy kernel:  [device_del+308/398] device_del+0x134/0x18e
Mar  4 23:41:05 silvy kernel:  [<f887e54c>] usb_disable_device+0x5c/0xbb [usbcore]
Mar  4 23:41:05 silvy kernel:  [<f887afdb>] usb_disconnect+0x82/0x104 [usbcore]
Mar  4 23:41:05 silvy kernel:  [<f887afc9>] usb_disconnect+0x70/0x104 [usbcore]
Mar  4 23:41:05 silvy kernel:  [<f887afc9>] usb_disconnect+0x70/0x104 [usbcore]
Mar  4 23:41:05 silvy kernel:  [<f887b9c8>] hub_thread+0x30b/0x9db [usbcore]
Mar  4 23:41:05 silvy kernel:  [__activate_task+28/40] __activate_task+0x1c/0x28
Mar  4 23:41:05 silvy kernel:  [autoremove_wake_function+0/51] autoremove_wake_function+0x0/0x33
Mar  4 23:41:05 silvy kernel:  [<f887b6bd>] hub_thread+0x0/0x9db [usbcore]
Mar  4 23:41:05 silvy kernel:  [kthread+155/191] kthread+0x9b/0xbf
Mar  4 23:41:05 silvy kernel:  [kthread+0/191] kthread+0x0/0xbf
Mar  4 23:41:05 silvy kernel:  [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10
Mar  4 23:41:05 silvy kernel:  =======================
Mar  4 23:41:05 silvy kernel: Code: 8b 4b 04 8d 46 04 89 43 04 89 5e 04 89 48 04 89 01 ff 4a 14 8b 42 08 a8 08 74 07 5b 5e e9 83 09 00 00 5b 5e c3 56 89 c6 53 8b 00 <8b> 58 0c 89 e0 25 00 e0 ff ff ff 40 14 89 f0 e8 f5 fe ff ff 85 
Mar  4 23:41:05 silvy kernel: EIP: [klist_del+6/69] klist_del+0x6/0x45 SS:ESP 0068:f7ba7e00

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Still no improvement on the b0rken usb-serial resume support in -rc*.

Today I got this ooops on resume from RAM.
Slightly tainted kernel this time (vmware), but not previously
on similar crashes.  I cannot yet get it to "crash on demaind",
so you'll just have to live with it this time.

All USB was dead until after a reboot this time.

pl2303 5-6.3:1.0: PM: resume from 2, parent 5-6.3 still 2
 usbdev5.23_ep81: PM: resume from 0, parent 5-6.3:1.0 still 2
 usbdev5.23_ep02: PM: resume from 0, parent 5-6.3:1.0 still 2
 usbdev5.23_ep83: PM: resume from 0, parent 5-6.3:1.0 still 2
 usbdev5.23: PM: resume from 0, parent 5-6.3 still 2
usb 5-6.4: PM: resume from 2, parent 5-6 still 2
 usbdev5.24_ep00: PM: resume from 0, parent 5-6.4 still 2
usbhid 5-6.4:1.0: PM: resume from 2, parent 5-6.4 still 2
 usbdev5.24_ep81: PM: resume from 0, parent 5-6.4:1.0 still 2
 usbdev5.24: PM: resume from 0, parent 5-6.4 still 2
Restarting tasks ... done.
ata1.00: configured for UDMA/100
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
usb 5-6: USB disconnect, address 22
usb 5-6.3: USB disconnect, address 23
BUG: unable to handle kernel paging request at virtual address fffffffb
 printing eip:
c01823cb
*pde = 00002067
*pte = 00000000
Oops: 0000 [#1]
PREEMPT 
Modules linked in: hci_usb radeon drm vmnet(P) vmmon(P) nfsd exportfs lockd nfs_acl sunrpc acpi_cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_stats freq_table cpufreq_conservative ac fan button thermal video battery container processor rfcomm l2cap bluetooth cfq_iosched deflate zlib_deflate twofish twofish_common serpent blowfish des cbc ecb blkcipher aes xcbc sha256 sha1 crypto_null af_key af_packet sbp2 usbhid hid pl2303 usbserial pcmcia mousedev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss ipw2200 snd_pcm ieee80211 ieee80211_crypt snd_timer ohci1394 psmouse firmware_class sdhci mmc_core yenta_socket rsrc_nonstatic ieee1394 serio_raw b44 mii pcmcia_core snd pcspkr soundcore ehci_hcd snd_page_alloc uhci_hcd ahci usbcore intel_agp agpgart sg sr_mod cdrom unix
CPU:    0
EIP:    0060:[<c01823cb>]    Tainted: P       VLI
EFLAGS: 00010286   (2.6.21-rc3-git4 #5)
EIP is at sysfs_hash_and_remove+0x18/0x111
eax: fffffff3   ebx: c030b3d4   ecx: 00000000   edx: fffffff3
esi: fffffff3   edi: fffffff3   ebp: f62af618   esp: f74e5dec
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process khubd (pid: 1955, ti=f74e4000 task=f74d6a50 task.ti=f74e4000)
Stack: c02d15d8 fffffff3 c0158595 c030b3d4 fffffff3 fffffff3 f62af618 c01843d9 
       c030b3c8 f411f8e0 c0184422 f411f878 00000001 f2ca4880 c02005ca f411f8e0 
       c01fba1f f411f878 00000001 f2ca4880 00000000 c01fba4e f2ca4880 f8a15d0e 
Call Trace:
 [<c0158595>] lookup_one_len+0x4d/0x5c
 [<c01843d9>] remove_files+0x15/0x1e
 [<c0184422>] sysfs_remove_group+0x40/0x56
 [<c02005ca>] device_pm_remove+0x1d/0x5a
 [<c01fba1f>] device_del+0x167/0x18e
 [<c01fba4e>] device_unregister+0x8/0x10
 [<f8a15d0e>] destroy_serial+0x80/0xcc [usbserial]
 [<f8a15c8e>] destroy_serial+0x0/0xcc [usbserial]
 [<c01ab1bd>] kref_put+0x5f/0x6e
 [<f8a157f7>] usb_serial_disconnect+0x81/0xaa [usbserial]
 [<c01ab1bd>] kref_put+0x5f/0x6e
 [<f88c7cc8>] usb_unbind_interface+0x2a/0x59 [usbcore]
 [<c01fd1a2>] __device_release_driver+0x6e/0x8b
 [<c01fd444>] device_release_driver+0x1d/0x32
 [<c01fcbd2>] bus_remove_device+0x71/0x81
 [<c01fb9ec>] device_del+0x134/0x18e
 [<f88c654c>] usb_disable_device+0x5c/0xbb [usbcore]
 [<f88c2fdb>] usb_disconnect+0x82/0x104 [usbcore]
 [<f88c2fc9>] usb_disconnect+0x70/0x104 [usbcore]
 [<f88c39c8>] hub_thread+0x30b/0x9db [usbcore]
 [<c027ce7a>] schedule+0x47c/0x51f
 [<c0126a84>] autoremove_wake_function+0x0/0x33
 [<f88c36bd>] hub_thread+0x0/0x9db [usbcore]
 [<c01269ba>] kthread+0x9b/0xbf
 [<c012691f>] kthread+0x0/0xbf
 [<c0104733>] kernel_thread_helper+0x7/0x10
 =======================
Code: 8b 40 08 a8 08 74 08 5b 5e 5f e9 6c ac 0f 00 5b 5e 5f c3 55 57 56 53 83 ec 0c 85 c0 89 44 24 04 89 14 24 0f 84 ed 00 00 00 89 c2 <8b> 40 08 85 c0 0f 84 e0 00 00 00 8b 52 50 83 c0 68 89 54 24 08 
EIP: [<c01823cb>] sysfs_hash_and_remove+0x18/0x111 SS:ESP 0068:f74e5dec

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Oliver Neukum]

Am Montag, 12. März 2007 15:56 schrieb Mark Lord:
> Still no improvement on the b0rken usb-serial resume support in -rc*.

Have you applied the fixes in Greg's current tree?

	Regards
		Oliver

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Oliver Neukum wrote:
> Am Montag, 12. März 2007 15:56 schrieb Mark Lord:
>> Still no improvement on the b0rken usb-serial resume support in -rc*.
> 
> Have you applied the fixes in Greg's current tree?

I don't know anything about any "current tree"
other than the 2.6.21-rc3-git* on kernel.org.

Greg hasn't suggested anything for this yet,
mostly because he's been busy keeping the 2.6.20.xx
point releases sane.

Cheers

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Oliver Neukum]

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

Am Montag, 12. März 2007 16:13 schrieb Mark Lord:
> Oliver Neukum wrote:
> > Am Montag, 12. März 2007 15:56 schrieb Mark Lord:
> >> Still no improvement on the b0rken usb-serial resume support in -rc*.
> > 
> > Have you applied the fixes in Greg's current tree?
> 
> I don't know anything about any "current tree"
> other than the 2.6.21-rc3-git* on kernel.org.
> 
> Greg hasn't suggested anything for this yet,
> mostly because he's been busy keeping the 2.6.20.xx
> point releases sane.

Sorry, try these in the chronological order the names imply.
If it still happens, let me know.

	Regards
		Oliver

[-- Attachment #2: serial20070305.patch --]
[-- Type: text/x-diff, Size: 1056 bytes --]

--- a/drivers/usb/serial/usb-serial.c	2007-03-05 14:43:20.000000000 +0100
+++ b/drivers/usb/serial/usb-serial.c	2007-03-05 15:18:53.000000000 +0100
@@ -99,9 +99,12 @@
 			continue;
 
 		*minor = i;
+		j = 0;
 		dbg("%s - minor base = %d", __FUNCTION__, *minor);
-		for (i = *minor; (i < (*minor + num_ports)) && (i < SERIAL_TTY_MINORS); ++i)
+		for (i = *minor; (i < (*minor + num_ports)) && (i < SERIAL_TTY_MINORS); ++i) {
 			serial_table[i] = serial;
+			serial->port[j++]->number = i;
+		}
 		spin_unlock(&table_lock);
 		return serial;
 	}
@@ -848,7 +851,6 @@
 		port = kzalloc(sizeof(struct usb_serial_port), GFP_KERNEL);
 		if (!port)
 			goto probe_error;
-		port->number = i + serial->minor;
 		port->serial = serial;
 		spin_lock_init(&port->lock);
 		mutex_init(&port->mutex);
@@ -1035,9 +1037,6 @@
 		kfree(port->interrupt_out_buffer);
 	}
 
-	/* return the minor range that this device had */
-	return_serial (serial);
-
 	/* free up any memory that we allocated */
 	for (i = 0; i < serial->num_port_pointers; ++i)
 		kfree(serial->port[i]);

[-- Attachment #3: usbserial20070227.patch --]
[-- Type: text/x-diff, Size: 611 bytes --]

--- linux-2.6.21-rc1/drivers/usb/serial/usb-serial.c.alt	2007-02-21 05:32:30.000000000 +0100
+++ linux-2.6.21-rc1/drivers/usb/serial/usb-serial.c	2007-02-26 15:32:50.000000000 +0100
@@ -826,7 +826,6 @@
 			num_ports = type->num_ports;
 	}
 
-	serial->minor = minor;
 	serial->num_ports = num_ports;
 	serial->num_bulk_in = num_bulk_in;
 	serial->num_bulk_out = num_bulk_out;
@@ -980,6 +979,7 @@
 		dev_err(&interface->dev, "No more free serial devices\n");
 		goto probe_error;
 	}
+	serial->minor = minor;
 
 	/* register all of the individual ports with the driver core */
 	for (i = 0; i < num_ports; ++i) {

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Greg KH]

On Mon, Mar 12, 2007 at 11:13:59AM -0400, Mark Lord wrote:
> Oliver Neukum wrote:
> >Am Montag, 12. M??rz 2007 15:56 schrieb Mark Lord:
> >>Still no improvement on the b0rken usb-serial resume support in -rc*.
> >
> >Have you applied the fixes in Greg's current tree?
> 
> I don't know anything about any "current tree"
> other than the 2.6.21-rc3-git* on kernel.org.

And all of those fixes Oliver is referring to should be in anything
older than 2.6.21-rc3-git6.  So we have a different problem here than
what people were seeing before.

> Greg hasn't suggested anything for this yet,
> mostly because he's been busy keeping the 2.6.20.xx
> point releases sane.

No, I didn't suggest anything because I thought it was going to be fixed
with Oliver's patches :(

thanks,

greg k-h

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Oliver Neukum]

Am Montag, 12. März 2007 16:29 schrieb Greg KH:
> On Mon, Mar 12, 2007 at 11:13:59AM -0400, Mark Lord wrote:
> > Oliver Neukum wrote:
> > >Am Montag, 12. M??rz 2007 15:56 schrieb Mark Lord:
> > >>Still no improvement on the b0rken usb-serial resume support in -rc*.
> > >
> > >Have you applied the fixes in Greg's current tree?
> > 
> > I don't know anything about any "current tree"
> > other than the 2.6.21-rc3-git* on kernel.org.
> 
> And all of those fixes Oliver is referring to should be in anything
> older than 2.6.21-rc3-git6.  So we have a different problem here than
> what people were seeing before.

Older than 2.6.21-rc3-git6? Did you throw them out? Why?

	Regards
		Oliver

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Greg KH wrote:
> ..
> And all of those fixes Oliver is referring to should be in anything
> older than 2.6.21-rc3-git6.

Did you mean, "anything *newer* than -git6" ??

This last crash was with -git4.  I'm building -git7 now.

>Does userspace have it open when you suspend/resume?

For the ooops I just posted, yes, I may have left Linux ckermit
running on the serial port before the suspend.

We shouldn't be oopsing regardless, but perhaps that could help
narrow things down a bit.

I'll also retest the simple plug-unplug-oops crash reported earlier,
once I have rc3-git7 up and running.

Cheers

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Greg KH]

On Mon, Mar 12, 2007 at 12:03:27PM -0400, Mark Lord wrote:
> Greg KH wrote:
> >..
> >And all of those fixes Oliver is referring to should be in anything
> >older than 2.6.21-rc3-git6.
> 
> Did you mean, "anything *newer* than -git6" ??

Oops, yes, I ment "newer", sorry.

> This last crash was with -git4.  I'm building -git7 now.

Ah, ok, there's still hope, Oliver's patches didn't go into -git4.

> >Does userspace have it open when you suspend/resume?
> 
> For the ooops I just posted, yes, I may have left Linux ckermit
> running on the serial port before the suspend.
> 
> We shouldn't be oopsing regardless, but perhaps that could help
> narrow things down a bit.
> 
> I'll also retest the simple plug-unplug-oops crash reported earlier,
> once I have rc3-git7 up and running.

thanks, but again, which usb-serial device do you have running here?

greg k-h

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Greg KH wrote:
>
> thanks, but again, which usb-serial device do you have running here?

That's in the oops log:  pl2303 for the ckermit test.

For the other oops (plug/wait/unplug a multi-func hub), one of the hubs
also has a pl2303, the other has an mct_u232.

Cheers

-ml

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Mark Lord wrote:
> Greg KH wrote:
>> Does userspace have it open when you suspend/resume?
> 
> For the ooops I just posted, yes, I may have left Linux ckermit
> running on the serial port before the suspend.

Here's a retest under linux-2.6.21-rc3-git7,
doing suspend/resume (RAM) with ckermit open on the serial port.

(LONG, Ooops at the bottom).

12:06:54 kernel: Stopping tasks ... done.
12:06:54 kernel: Suspending console(s)
12:06:54 kernel: pl2303 5-5.3:1.0: no suspend for driver pl2303?
12:06:54 kernel: ACPI: PCI interrupt for device 0000:03:01.2 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1f.2 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1e.2 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1d.7 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1d.3 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled
12:06:54 kernel: ACPI: PCI interrupt for device 0000:00:1d.0 disabled
12:06:54 kernel: Intel machine check architecture supported.
12:06:54 kernel: Intel machine check reporting enabled on CPU#0.
12:06:54 kernel: Back to C!
12:06:54 kernel: PM: Writing back config space on device 0000:00:01.0 at offset 7 (was 2000d0d0, writing d0d0)
12:06:54 kernel: PM: Writing back config space on device 0000:00:01.0 at offset 3 (was 10000, writing 10010)
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
12:06:54 kernel: usb usb1: root hub lost power or was reset
12:06:54 kernel: PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 18
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64
12:06:54 kernel: PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20a)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 8 (was 1, writing bf61)
12:06:54 kernel: usb usb2: root hub lost power or was reset
12:06:54 kernel: PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 19
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64
12:06:54 kernel: PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 309)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 8 (was 1, writing bf41)
12:06:54 kernel: usb usb3: root hub lost power or was reset
12:06:54 kernel: PCI: Enabling device 0000:00:1d.3 (0000 -> 0001)
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 17
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1d.3 to 64
12:06:54 kernel: PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 407)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1d.3 at offset 8 (was 1, writing bf21)
12:06:54 kernel: usb usb4: root hub lost power or was reset
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 16 (level, low) -> IRQ 16
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1d.7 to 64
12:06:54 kernel: usb usb5: root hub lost power or was reset
12:06:54 kernel: ehci_hcd 0000:00:1d.7: debug port 1
12:06:54 kernel: PCI: cache line size of 32 is not supported by device 0000:00:1d.7
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 9 (was 10001, writing 8bf18801)
12:06:54 NetworkManager: <information>^ISWITCH: terminating current connection 'eth0' because it's no longer valid. 
12:06:54 NetworkManager: <information>^IDeactivating device eth0. 
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 8 (was 0, writing dfc0dfc0)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 7 (was 2280e0f0, writing 22802020)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 6 (was 20030300, writing 20070300)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 1 (was 100005, writing 100107)
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.2 at offset f (was 100, writing 10b)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 7 (was 0, writing dffffd00)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 6 (was 0, writing dffffe00)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 5 (was 1, writing ec41)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 4 (was 1, writing ed01)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1e.2 at offset 1 (was 2900000, writing 2900003)
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 16 (level, low) -> IRQ 16
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1e.2 to 64
12:06:54 kernel: PM: Writing back config space on device 0000:00:1f.0 at offset 1 (was 2000007, writing 2000107)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1f.2 at offset f (was 200, writing 20a)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1f.2 at offset 9 (was d0000, writing 0)
12:06:54 kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 18
12:06:54 kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
12:06:54 kernel: PM: Writing back config space on device 0000:00:1f.3 at offset f (was 200, writing 20a)
12:06:54 kernel: PM: Writing back config space on device 0000:00:1f.3 at offset 1 (was 2800001, writing 2800101)
12:06:54 kernel: PM: Writing back config space on device 0000:01:00.0 at offset f (was 1ff, writing 10b)
12:06:54 kernel: PM: Writing back config space on device 0000:01:00.0 at offset c (was 0, writing dfe00000)
12:06:54 kernel: PM: Writing back config space on device 0000:01:00.0 at offset 3 (was 0, writing 10)
12:06:54 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
12:06:54 kernel: PM: Writing back config space on device 0000:03:00.0 at offset f (was 100, writing 109)
12:06:54 kernel: PM: Writing back config space on device 0000:03:00.0 at offset 4 (was 0, writing dfcfe000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:00.0 at offset 3 (was 0, writing 4000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:00.0 at offset 1 (was 100000, writing 100106)
12:06:54 kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 19
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset f (was 7800100, writing 58001ff)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset e (was 0, writing 24fc)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset d (was 0, writing 2400)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset c (was 0, writing 20fc)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset b (was 0, writing 2000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset a (was 0, writing 8ffff000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset 9 (was 0, writing 8c000000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset 8 (was 0, writing 8bfff000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset 7 (was 0, writing 88000000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset 6 (was 0, writing b0070403)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset 4 (was 0, writing dfc00000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.0 at offset 3 (was 820000, writing 82a800)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.1 at offset 4 (was 0, writing dfcfc800)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.1 at offset 3 (was 800000, writing 804000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.1 at offset 1 (was 2100000, writing 2100106)
12:06:54 kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19]  MMIO=[dfcfc800-dfcfcfff]  Max Packet=[2048]  IR/IT contexts=[4/4]
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.2 at offset 4 (was 0, writing dfcfc700)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.2 at offset 3 (was 800000, writing 804000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:01.2 at offset 1 (was 2100000, writing 2100106)
12:06:54 kernel: ACPI: PCI Interrupt 0000:03:01.2[C] -> GSI 17 (level, low) -> IRQ 18
12:06:54 kernel: PM: Writing back config space on device 0000:03:03.0 at offset f (was 18030100, writing 1803010a)
12:06:54 kernel: PM: Writing back config space on device 0000:03:03.0 at offset 4 (was 0, writing dfcfd000)
12:06:54 kernel: PM: Writing back config space on device 0000:03:03.0 at offset 3 (was 0, writing 4010)
12:06:54 kernel: PM: Writing back config space on device 0000:03:03.0 at offset 1 (was 2900000, writing 2900112)
12:06:54 kernel: pnp: Device 00:04 does not support activation.
12:06:54 kernel: pnp: Device 00:05 does not support activation.
12:06:54 kernel:  usbdev5.2_ep00: PM: resume from 0, parent 5-5 still 2
12:06:54 kernel: hub 5-5:1.0: PM: resume from 2, parent 5-5 still 2
12:06:54 kernel:  usbdev5.2_ep81: PM: resume from 0, parent 5-5:1.0 still 2
12:06:54 kernel:  usbdev5.2: PM: resume from 0, parent 5-5 still 2
12:06:54 kernel: usb 5-5.3: PM: resume from 2, parent 5-5 still 2
12:06:54 kernel:  usbdev5.3_ep00: PM: resume from 0, parent 5-5.3 still 2
12:06:54 kernel: pl2303 5-5.3:1.0: PM: resume from 2, parent 5-5.3 still 2
12:06:54 kernel:  usbdev5.3_ep81: PM: resume from 0, parent 5-5.3:1.0 still 2
12:06:54 kernel:  usbdev5.3_ep02: PM: resume from 0, parent 5-5.3:1.0 still 2
12:06:54 kernel:  usbdev5.3_ep83: PM: resume from 0, parent 5-5.3:1.0 still 2
12:06:54 kernel:  usbdev5.3: PM: resume from 0, parent 5-5.3 still 2
12:06:54 kernel: usb 5-5.4: PM: resume from 2, parent 5-5 still 2
12:06:54 kernel:  usbdev5.4_ep00: PM: resume from 0, parent 5-5.4 still 2
12:06:54 kernel: usbhid 5-5.4:1.0: PM: resume from 2, parent 5-5.4 still 2
12:06:54 kernel:  usbdev5.4_ep81: PM: resume from 0, parent 5-5.4:1.0 still 2
12:06:54 kernel:  usbdev5.4: PM: resume from 0, parent 5-5.4 still 2
12:06:54 kernel: pl2303 ttyUSB0: PM: resume from 0, parent 5-5.3:1.0 still 2
12:06:54 kernel: Restarting tasks ... done.
12:06:54 kernel: usb 5-5: USB disconnect, address 2
12:06:54 kernel: usb 5-5.3: USB disconnect, address 3
12:06:54 kernel: pl2303 5-5.3:1.0: device disconnected
12:06:54 kernel: usb 5-5.4: USB disconnect, address 4
12:06:54 kernel: ata1.00: configured for UDMA/100
12:06:54 kernel: SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
12:06:54 kernel: sda: Write Protect is off
12:06:54 kernel: sda: Mode Sense: 00 3a 00 00
12:06:54 dhclient: DHCPRELEASE on eth0 to 10.0.0.2 port 67
12:06:54 kernel: SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
12:06:54 dhcdbd: dhco_value_from_text: Non ascii char outside valid hex string:  0 
12:06:54 dhcdbd: dhco_input_option: Value silvy cannot be converted to type X 
12:06:54 dhcdbd: dhco_parse_option_settings: bad option setting: old_host_name = silvy 
12:06:54 kernel: usb 5-5: new high speed USB device using ehci_hcd and address 5
12:06:54 kernel: usb 5-5: configuration #1 chosen from 1 choice
12:06:55 kernel: hub 5-5:1.0: USB hub found
12:06:55 kernel: hub 5-5:1.0: 4 ports detected
12:06:55 kernel: ata2.00: configured for UDMA/33
12:06:55 kernel: [drm] Loading R300 Microcode
12:06:55 kernel: usb 5-5.3: new full speed USB device using ehci_hcd and address 6
12:06:55 kernel: usb 5-5.3: configuration #1 chosen from 1 choice
12:06:55 kernel: pl2303 5-5.3:1.0: pl2303 converter detected
12:06:55 kernel: usb 5-5.3: pl2303 converter now attached to ttyUSB1
12:06:55 NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
12:06:55 NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
12:06:55 NetworkManager: <information>^Imatch 
12:06:55 NetworkManager: <information>^Imatch 
12:06:55 kernel: usb 5-5.4: new low speed USB device using ehci_hcd and address 7
12:06:55 kernel: usb 5-5.4: configuration #1 chosen from 1 choice
12:06:55 kernel: input: Logitech Optical USB Mouse as /class/input/input8
12:06:55 kernel: input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:1d.7-5.4
12:06:56 kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
12:06:56 kernel: b44: eth0: Flow control is off for TX and off for RX.
12:06:56 NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link. 
12:06:56 NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'. 
12:06:56 NetworkManager: <information>^IWill activate connection 'eth0'. 
12:06:56 NetworkManager: <information>^IDevice eth0 activation scheduled... 
12:06:56 NetworkManager: <information>^IActivation (eth0) started... 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started... 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete. 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting... 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful. 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete. 
12:06:56 NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started... 
12:06:56 NetworkManager: <information>^Imatch 
12:06:57 NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction. 
12:06:57 NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
12:06:57 NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0 
12:06:58 NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0 
12:06:59 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
12:06:59 dhclient: DHCPOFFER from 10.0.0.2
12:06:59 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
12:06:59 dhclient: DHCPACK from 10.0.0.2
12:06:59 dhclient: bound to 10.0.0.14 -- renewal in 34884 seconds.
12:06:59 kernel: pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
12:06:59 kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000168
12:06:59 kernel:  printing eip:
12:06:59 kernel: f89fe1f6
12:06:59 kernel: *pde = 00000000
12:06:59 kernel: Oops: 0000 [#1]
12:06:59 kernel: PREEMPT 
12:06:59 kernel: Modules linked in: radeon drm nfsd exportfs lockd nfs_acl sunrpc acpi_cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_stats freq_table cpufreq_conservative ac fan button thermal video battery container processor rfcomm l2cap bluetooth cfq_iosched deflate zlib_deflate twofish twofish_common serpent blowfish des cbc ecb blkcipher aes xcbc sha256 sha1 crypto_null af_key af_packet sbp2 usbhid hid pl2303 usbserial mousedev pcmcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ipw2200 snd ieee80211 ieee80211_crypt ohci1394 serio_raw psmouse soundcore snd_page_alloc pcspkr sdhci firmware_class ahci ieee1394 yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd mmc_core b44 mii uhci_hcd usbcore intel_agp agpgart sg sr_mod cdrom unix
12:06:59 kernel: CPU:    0
12:06:59 kernel: EIP:    0060:[<f89fe1f6>]    Not tainted VLI
12:06:59 kernel: EFLAGS: 00010297   (2.6.21-rc3-git7 #7)
12:06:59 kernel: EIP is at pl2303_shutdown+0x37/0x70 [pl2303]
12:06:59 kernel: eax: 00000000   ebx: f7560d80   ecx: c20df5c0   edx: f89fe1bf
12:06:59 kernel: esi: f7560d80   edi: 00000000   ebp: f7560d80   esp: f5d45e78
12:06:59 kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
12:06:59 kernel: Process kermit (pid: 4403, ti=f5d44000 task=f5cdb0b0 task.ti=f5d44000)
12:06:59 kernel: Stack: c01ab1b5 f7b39a78 00000000 f7560d80 00000001 00000000 00000000 f8a29ca1 
12:06:59 kernel:        00200200 f7b39a00 f7b39a08 f5f71bc0 f7560db4 f8a29c18 c01ab1b5 c01e5b0c 
12:06:59 kernel:        f5f634cc f5f63400 f5f63400 f5f63400 f5f71bc0 c01e7758 f6c4bc40 c0138a0a 
12:06:59 kernel: Call Trace:
12:06:59 kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
12:06:59 kernel:  [<f8a29ca1>] destroy_serial+0x89/0x122 [usbserial]
12:06:59 kernel:  [<f8a29c18>] destroy_serial+0x0/0x122 [usbserial]
12:06:59 kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
12:06:59 kernel:  [tty_fasync+60/180] tty_fasync+0x3c/0xb4
12:06:59 kernel:  [release_dev+484/1496] release_dev+0x1e4/0x5d8
12:06:59 kernel:  [find_get_page+21/69] find_get_page+0x15/0x45
12:06:59 kernel:  [filemap_nopage+385/726] filemap_nopage+0x181/0x2d6
12:06:59 kernel:  [pty_write+43/53] pty_write+0x2b/0x35
12:06:59 kernel:  [getnstimeofday+48/216] getnstimeofday+0x30/0xd8
12:06:59 kernel:  [enqueue_hrtimer+256/268] enqueue_hrtimer+0x100/0x10c
12:06:59 kernel:  [tty_release+15/24] tty_release+0xf/0x18
12:06:59 kernel:  [__fput+150/336] __fput+0x96/0x150
12:06:59 kernel:  [filp_close+79/86] filp_close+0x4f/0x56
12:06:59 kernel:  [sys_close+117/183] sys_close+0x75/0xb7
12:06:59 kernel:  [sysenter_past_esp+95/133] sysenter_past_esp+0x5f/0x85
12:06:59 kernel:  =======================
12:06:59 kernel: Code: 2c a0 f8 00 74 1c c7 44 24 08 2f 04 a0 f8 c7 44 24 04 33 05 a0 f8 c7 04 24 09 06 a0 f8 e8 8f 9e 71 c7 89 ee 31 ff eb 2c 8b 46 14 <8b> 98 68 01 00 00 85 db 74 1b 8b 03 e8 f9 fd ff ff 89 d8 e8 95 
12:06:59 kernel: EIP: [<f89fe1f6>] pl2303_shutdown+0x37/0x70 [pl2303] SS:ESP 0068:f5d45e78

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

..and here is a retest with linux-2.6.21-rc3-git7
of simply plug/wait/unplug a USB hub/serial/parallel/PS2 gizmo.

I have two of these, with different serial port hardware in each,
and doing this with either of them produces an ooops.

12:12:02 kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2
12:12:02 kernel: usb 4-2: configuration #1 chosen from 1 choice
12:12:02 kernel: hub 4-2:1.0: USB hub found
12:12:02 kernel: hub 4-2:1.0: 5 ports detected
12:12:02 kernel: usb 4-2.3: new full speed USB device using uhci_hcd and address 3
12:12:02 kernel: usb 4-2.3: configuration #1 chosen from 1 choice
12:12:02 kernel: input: MTC PS/2 to USB converter as /class/input/input9
12:12:02 kernel: input: USB HID v1.10 Keyboard [MTC PS/2 to USB converter] on usb-0000:00:1d.3-2.3
12:12:02 kernel: input: MTC PS/2 to USB converter as /class/input/input10
12:12:02 kernel: input: USB HID v1.10 Mouse [MTC PS/2 to USB converter] on usb-0000:00:1d.3-2.3
12:12:02 kernel: usb 4-2.4: new full speed USB device using uhci_hcd and address 4
12:12:03 kernel: usb 4-2.4: configuration #1 chosen from 1 choice
12:12:03 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for MCT U232
12:12:03 kernel: usb 4-2.5: new full speed USB device using uhci_hcd and address 5
12:12:03 kernel: usb 4-2.5: configuration #1 chosen from 1 choice
12:12:03 kernel: mct_u232 4-2.4:1.0: MCT U232 converter detected
12:12:03 kernel: usb 4-2.4: MCT U232 converter now attached to ttyUSB2
12:12:03 kernel: usbcore: registered new interface driver mct_u232
12:12:03 kernel: drivers/usb/serial/mct_u232.c: Magic Control Technology USB-RS232 converter driver z2.0
12:12:03 kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 1 proto 2 vid 0x0711 pid 0x0300
12:12:03 kernel: usbcore: registered new interface driver usblp
12:12:03 kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
12:12:06 kernel: usb 4-2: USB disconnect, address 2
12:12:06 kernel: usb 4-2.3: USB disconnect, address 3
12:12:06 kernel: usb 4-2.4: USB disconnect, address 4
12:12:06 kernel: mct_u232 ttyUSB2: MCT U232 converter now disconnected from ttyUSB2
12:12:06 kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000168
12:12:06 kernel:  printing eip:
12:12:06 kernel: f8ca6542
12:12:06 kernel: *pde = 00000000
12:12:06 kernel: Oops: 0000 [#2]
12:12:06 kernel: PREEMPT 
12:12:06 kernel: Modules linked in: usblp mct_u232 radeon drm nfsd exportfs lockd nfs_acl sunrpc acpi_cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_userspace cpufreq_stats freq_table cpufreq_conservative ac fan button thermal video battery container processor rfcomm l2cap bluetooth cfq_iosched deflate zlib_deflate twofish twofish_common serpent blowfish des cbc ecb blkcipher aes xcbc sha256 sha1 crypto_null af_key af_packet sbp2 usbhid hid pl2303 usbserial mousedev pcmcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ipw2200 snd ieee80211 ieee80211_crypt ohci1394 serio_raw psmouse soundcore snd_page_alloc pcspkr sdhci firmware_class ahci ieee1394 yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd mmc_core b44 mii uhci_hcd usbcore intel_agp agpgart sg sr_mod cdrom unix
12:12:06 kernel: CPU:    0
12:12:06 kernel: EIP:    0060:[<f8ca6542>]    Not tainted VLI
12:12:06 kernel: EFLAGS: 00010206   (2.6.21-rc3-git7 #7)
12:12:06 kernel: EIP is at mct_u232_shutdown+0x39/0x65 [mct_u232]
12:12:06 kernel: eax: 00000001   ebx: f7649cc0   ecx: c20df5c0   edx: 00000078
12:12:06 kernel: esi: 00000000   edi: f7649cc0   ebp: f5c45c18   esp: f7437e38
12:12:06 kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
12:12:06 kernel: Process khubd (pid: 1949, ti=f7436000 task=f7d8da10 task.ti=f7436000)
12:12:06 kernel: Stack: f6c2c478 00000000 f6c2c478 f7649cc0 00000001 f7649cc0 f8a29ca1 f7649cc0 
12:12:06 kernel:        f7649cc0 f5c45c18 f88c5a43 f7649cf4 f8a29c18 c01ab1b5 00000202 00000000 
12:12:06 kernel:        f6c2c400 f7649cc0 f6c2c400 f7649cc4 f8a297f7 c01ab1b5 00000001 f5abec67 
12:12:06 kernel: Call Trace:
12:12:06 kernel:  [<f8a29ca1>] destroy_serial+0x89/0x122 [usbserial]
12:12:06 kernel:  [<f88c5a43>] usb_kill_urb+0x4e/0xcb [usbcore]
12:12:06 kernel:  [<f8a29c18>] destroy_serial+0x0/0x122 [usbserial]
12:12:06 kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
12:12:06 kernel:  [<f8a297f7>] usb_serial_disconnect+0x81/0xaa [usbserial]
12:12:06 kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
12:12:06 kernel:  [<f88c7ca8>] usb_unbind_interface+0x2a/0x59 [usbcore]
12:12:06 kernel:  [__device_release_driver+110/139] __device_release_driver+0x6e/0x8b
12:12:06 kernel:  [device_release_driver+29/50] device_release_driver+0x1d/0x32
12:12:06 kernel:  [bus_remove_device+113/129] bus_remove_device+0x71/0x81
12:12:06 kernel:  [device_del+308/405] device_del+0x134/0x195
12:12:06 kernel:  [<f88c652d>] usb_disable_device+0x5c/0xbb [usbcore]
12:12:06 kernel:  [<f88c2f8d>] usb_disconnect+0x82/0x104 [usbcore]
12:12:06 kernel:  [<f88c2f7b>] usb_disconnect+0x70/0x104 [usbcore]
12:12:06 kernel:  [<f88c397a>] hub_thread+0x30b/0x9ed [usbcore]
12:12:06 kernel:  [activate_task+153/172] activate_task+0x99/0xac
12:12:06 kernel:  [schedule+1148/1311] schedule+0x47c/0x51f
12:12:06 kernel:  [autoremove_wake_function+0/51] autoremove_wake_function+0x0/0x33
12:12:06 kernel:  [<f88c366f>] hub_thread+0x0/0x9ed [usbcore]
12:12:06 kernel:  [kthread+155/191] kthread+0x9b/0xbf
12:12:06 kernel:  [kthread+0/191] kthread+0x0/0xbf
12:12:06 kernel:  [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10
12:12:06 kernel:  =======================
12:12:06 kernel: Code: 00 74 1c c7 44 24 08 35 6e ca f8 c7 44 24 04 ca 6e ca f8 c7 04 24 47 71 ca f8 e8 46 1b 47 c7 89 fb 31 f6 eb 23 8b 53 14 83 c2 78 <8b> 82 f0 00 00 00 85 c0 74 0f c7 82 f0 00 00 00 00 00 00 00 e8 
12:12:06 kernel: EIP: [<f8ca6542>] mct_u232_shutdown+0x39/0x65 [mct_u232] SS:ESP 0068:f7437e38

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Mark Lord wrote:
> ..and here is a retest with linux-2.6.21-rc3-git7
> of simply plug/wait/unplug a USB hub/serial/parallel/PS2 gizmo.
> 
> I have two of these, with different serial port hardware in each,
> and doing this with either of them produces an ooops.
> 
...
> 12:12:06 kernel: mct_u232 ttyUSB2: MCT U232 converter now disconnected 
> from ttyUSB2
> 12:12:06 kernel: BUG: unable to handle kernel NULL pointer dereference 
> at virtual address 00000168
> 12:12:06 kernel:  printing eip:
> 12:12:06 kernel: f8ca6542
> 12:12:06 kernel: *pde = 00000000
> 12:12:06 kernel: Oops: 0000 [#2]

Okay, from that part (above), the problem is obvious:
in that the "MCT U232 converter now disconnected" appears,
and then we continue to try and call the driver's method.. Oops!

The hack patch below "fixes" this, but it really just hides whatever
the real problem underneath was:

Signed-off-by:  Mark Lord <mlord@pobox.com>
---
--- linux/include/linux/usb/serial.h.orig	2007-03-12 12:18:48.000000000 -0400
+++ linux/include/linux/usb/serial.h	2007-03-12 12:18:23.000000000 -0400
@@ -99,11 +99,19 @@
 /* get and set the port private data pointer helper functions */
 static inline void *usb_get_serial_port_data (struct usb_serial_port *port)
 {
+	if (!port) {
+		WARN_ON(1);
+		return NULL;
+	}
 	return dev_get_drvdata(&port->dev);
 }
 
 static inline void usb_set_serial_port_data (struct usb_serial_port *port, void *data)
 {
+	if (!port) {
+		WARN_ON(1);
+		return;
+	}
 	dev_set_drvdata(&port->dev, data);
 }
 

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Mark Lord]

Mark Lord wrote:
>
> Okay, from that part (above), the problem is obvious:
> in that the "MCT U232 converter now disconnected" appears,
> and then we continue to try and call the driver's method.. Oops!
> 
> The hack patch below "fixes" this, but it really just hides whatever
> the real problem underneath was:
> 
> Signed-off-by:  Mark Lord <mlord@pobox.com>
> ---
> --- linux/include/linux/usb/serial.h.orig    2007-03-12 
> 12:18:48.000000000 -0400
> +++ linux/include/linux/usb/serial.h    2007-03-12 12:18:23.000000000 -0400
> @@ -99,11 +99,19 @@
> /* get and set the port private data pointer helper functions */
> static inline void *usb_get_serial_port_data (struct usb_serial_port *port)
> {
> +    if (!port) {
> +        WARN_ON(1);
> +        return NULL;
> +    }
>     return dev_get_drvdata(&port->dev);
> }
> 
> static inline void usb_set_serial_port_data (struct usb_serial_port 
> *port, void *data)
> {
> +    if (!port) {
> +        WARN_ON(1);
> +        return;
> +    }
>     dev_set_drvdata(&port->dev, data);
> }
> 

Mmmm.. and that same hack also prevents the Oops seen
when I leave ckermit running during suspend/resume(RAM),
giving me this BUG() report now instead:

12:29:51 kernel: pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
12:29:51 kernel: BUG: at include/linux/usb/serial.h:103 usb_get_serial_port_data()
12:29:51 kernel:  [<f8a03254>] pl2303_shutdown+0x95/0xb5 [pl2303]
12:29:51 kernel:  [<f8a23ca1>] destroy_serial+0x89/0x122 [usbserial]
12:29:51 kernel:  [<f8a23c18>] destroy_serial+0x0/0x122 [usbserial]
12:29:51 kernel:  [kref_put+95/110] kref_put+0x5f/0x6e
12:29:51 kernel:  [tty_fasync+60/180] tty_fasync+0x3c/0xb4
12:29:51 kernel:  [release_dev+484/1496] release_dev+0x1e4/0x5d8
12:29:51 kernel:  [find_get_page+21/69] find_get_page+0x15/0x45
12:29:51 kernel:  [filemap_nopage+385/726] filemap_nopage+0x181/0x2d6
12:29:51 kernel:  [pty_write+43/53] pty_write+0x2b/0x35
12:29:51 kernel:  [getnstimeofday+48/216] getnstimeofday+0x30/0xd8
12:29:51 kernel:  [rb_insert_color+74/173] rb_insert_color+0x4a/0xad
12:29:51 kernel:  [enqueue_hrtimer+256/268] enqueue_hrtimer+0x100/0x10c
12:29:51 kernel:  [tty_release+15/24] tty_release+0xf/0x18
12:29:51 kernel:  [__fput+150/336] __fput+0x96/0x150
12:29:51 kernel:  [filp_close+79/86] filp_close+0x4f/0x56
12:29:51 kernel:  [sys_close+117/183] sys_close+0x75/0xb7
12:29:51 kernel:  [sysenter_past_esp+95/133] sysenter_past_esp+0x5f/0x85
12:29:51 kernel:  =======================

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Oliver Neukum]

Am Montag, 12. März 2007 17:50 schrieb Mark Lord:
> Mark Lord wrote:
> >
> > Okay, from that part (above), the problem is obvious:
> > in that the "MCT U232 converter now disconnected" appears,
> > and then we continue to try and call the driver's method.. Oops!
> > 
> > The hack patch below "fixes" this, but it really just hides whatever
> > the real problem underneath was:

static void destroy_serial(struct kref *kref):

	/* the ports are cleaned up and released in port_release() */
	for (i = 0; i < serial->num_ports; ++i)
		if (serial->port[i]->dev.parent != NULL) {
			device_unregister(&serial->port[i]->dev);
			serial->port[i] = NULL;
		}

	if (serial->type->shutdown)
		serial->type->shutdown(serial);

IMHO shutdown() is using serial->port[] and bombs.
Could you reverse the order here?

	Regards
		Oliver

[PATCH] usb-serial regression (Oops) in 2.6.21-rc*

[Mark Lord]

Oliver Neukum wrote:
>> Mark Lord wrote:
>>> Okay, from that part (above), the problem is obvious:
>>> in that the "MCT U232 converter now disconnected" appears,
>>> and then we continue to try and call the driver's method.. Oops!
..
> IMHO shutdown() is using serial->port[] and bombs.
> Could you reverse the order here?

Yup.  Fixed.  Tested.  Works.

This patch fixes the Oops that otherwise occurs whenever
a USB serial adapter is unplugged from a system, as well
the Oops seen when one is in use before resume (to RAM).

GregKH:  This needs to go into 2.6.21-rc*.

Signed-off-by:  Mark Lord <mlord@pobox.com>
---
--- 2.6.21-rc3/drivers/usb/serial/usb-serial.c	2007-03-12 11:22:43.000000000 -0400
+++ linux/drivers/usb/serial/usb-serial.c	2007-03-12 16:12:53.000000000 -0400
@@ -141,6 +141,9 @@
 	for (i = 0; i < serial->num_ports; ++i)
 		serial->port[i]->open_count = 0;
 
+	if (serial->type->shutdown)
+		serial->type->shutdown(serial);
+
 	/* the ports are cleaned up and released in port_release() */
 	for (i = 0; i < serial->num_ports; ++i)
 		if (serial->port[i]->dev.parent != NULL) {
@@ -148,9 +151,6 @@
 			serial->port[i] = NULL;
 		}
 
-	if (serial->type->shutdown)
-		serial->type->shutdown(serial);
-
 	/* return the minor range that this device had */
 	return_serial(serial);
 

Re: [PATCH] usb-serial regression (Oops) in 2.6.21-rc*

[Greg KH]

On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
> Oliver Neukum wrote:
> >>Mark Lord wrote:
> >>>Okay, from that part (above), the problem is obvious:
> >>>in that the "MCT U232 converter now disconnected" appears,
> >>>and then we continue to try and call the driver's method.. Oops!
> ..
> >IMHO shutdown() is using serial->port[] and bombs.
> >Could you reverse the order here?
> 
> Yup.  Fixed.  Tested.  Works.
> 
> This patch fixes the Oops that otherwise occurs whenever
> a USB serial adapter is unplugged from a system, as well
> the Oops seen when one is in use before resume (to RAM).
> 
> GregKH:  This needs to go into 2.6.21-rc*.
> 
> Signed-off-by:  Mark Lord <mlord@pobox.com>
> ---
> --- 2.6.21-rc3/drivers/usb/serial/usb-serial.c	2007-03-12 
> 11:22:43.000000000 -0400
> +++ linux/drivers/usb/serial/usb-serial.c	2007-03-12 
> 16:12:53.000000000 -0400
> @@ -141,6 +141,9 @@
> 	for (i = 0; i < serial->num_ports; ++i)
> 		serial->port[i]->open_count = 0;
> 
> +	if (serial->type->shutdown)
> +		serial->type->shutdown(serial);
> +
> 	/* the ports are cleaned up and released in port_release() */
> 	for (i = 0; i < serial->num_ports; ++i)
> 		if (serial->port[i]->dev.parent != NULL) {
> @@ -148,9 +151,6 @@
> 			serial->port[i] = NULL;
> 		}
> 
> -	if (serial->type->shutdown)
> -		serial->type->shutdown(serial);
> -


Argh, no, this change was done to help the ftdi drivers out.

Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
tree from Jim Radford:
	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a

It makes this change because the usb-serial drivers need the port
devices when the port_remove() callbacks happen.  Otherwise you get an
oops that way.

Jim, can you take a look at this and see if you can figure something
out?

thanks,

greg k-h

Re: [PATCH] usb-serial regression (Oops) in 2.6.21-rc*

[Mark Lord]

Greg KH wrote:
>>>> Mark Lord wrote:
>> This patch fixes the Oops that otherwise occurs whenever
>> a USB serial adapter is unplugged from a system, as well
>> the Oops seen when one is in use before resume (to RAM).
>>
>> GregKH:  This needs to go into 2.6.21-rc*.
>>
>> Signed-off-by:  Mark Lord <mlord@pobox.com>
>> ---
>> --- 2.6.21-rc3/drivers/usb/serial/usb-serial.c	2007-03-12 
>> 11:22:43.000000000 -0400
>> +++ linux/drivers/usb/serial/usb-serial.c	2007-03-12 
>> 16:12:53.000000000 -0400
>> @@ -141,6 +141,9 @@
>> 	for (i = 0; i < serial->num_ports; ++i)
>> 		serial->port[i]->open_count = 0;
>>
>> +	if (serial->type->shutdown)
>> +		serial->type->shutdown(serial);
>> +
>> 	/* the ports are cleaned up and released in port_release() */
>> 	for (i = 0; i < serial->num_ports; ++i)
>> 		if (serial->port[i]->dev.parent != NULL) {
>> @@ -148,9 +151,6 @@
>> 			serial->port[i] = NULL;
>> 		}
>>
>> -	if (serial->type->shutdown)
>> -		serial->type->shutdown(serial);
>> -
>
> Argh, no, this change was done to help the ftdi drivers out.
> 
> Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> tree from Jim Radford:
> 	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a
> 
> It makes this change because the usb-serial drivers need the port
> devices when the port_remove() callbacks happen.  Otherwise you get an
> oops that way.

Oh, good. Now we know the exact changeset that caused the regression, thanks.
That patch should either get reverted, or an alternative fix be posted.

Such as.. this one, from earlier, except perhaps minus the WARN_ON()s:

Signed-off-by:  Mark Lord <mlord@pobox.com>
---
--- linux/include/linux/usb/serial.h.orig	2007-03-12 12:18:48.000000000 -0400
+++ linux/include/linux/usb/serial.h	2007-03-12 12:18:23.000000000 -0400
@@ -99,11 +99,19 @@
 /* get and set the port private data pointer helper functions */
 static inline void *usb_get_serial_port_data (struct usb_serial_port *port)
 {
+	if (!port) {
+		/* WARN_ON(1);*/
+		return NULL;
+	}
 	return dev_get_drvdata(&port->dev);
 }
 
 static inline void usb_set_serial_port_data (struct usb_serial_port *port, void *data)
 {
+	if (!port) {
+		/* WARN_ON(1); */
+		return;
+	}
 	dev_set_drvdata(&port->dev, data);
 }
 

Re: [PATCH] usb-serial regression (Oops) in 2.6.21-rc*

[Jim Radford]

On Mon, Mar 12, 2007 at 01:33:31PM -0700, Greg KH wrote:
> On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
> > Oliver Neukum wrote:
> > >>Mark Lord wrote:
> > >>>Okay, from that part (above), the problem is obvious:
> > >>>in that the "MCT U232 converter now disconnected" appears,
> > >>>and then we continue to try and call the driver's method.. Oops!

> > >IMHO shutdown() is using serial->port[] and bombs.
> > >Could you reverse the order here?

> > Yup.  Fixed.  Tested.  Works.

> > This patch fixes the Oops that otherwise occurs whenever
> > a USB serial adapter is unplugged from a system, as well
> > the Oops seen when one is in use before resume (to RAM).

> Argh, no, this change was done to help the ftdi drivers out.

> Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> tree from Jim Radford:
> 	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a
> 
> It makes this change because the usb-serial drivers need the port
> devices when the port_remove() callbacks happen.  Otherwise you get an
> oops that way.

> Jim, can you take a look at this and see if you can figure something
> out?

The problem is really the

   serial->port[i] = NULL;

line after device_unregister() which is used to flag "fake" devices
that don't need legacy cleanup later in the destrol_serial.  That
flagging should be done using a *real* flag, and not by overloading
the ->port[i] pointer since we require it to be non-NULL in
->shutdown() in all drivers that are not converted to new
->port_probe()/->port_remove() framework (currently all except ftdi).

I'll work on a patch to do that, but for now, I think you should apply
Mark's patch to revert the order change since the FTDI driver no
longer requires the correct ordering of device_unregister() and
->shutdown().

-Jim

[PATCH] usb-serial regression fix

[Jim Radford]

On Mon, Mar 12, 2007 at 03:42:35PM -0700, Jim Radford wrote:
> On Mon, Mar 12, 2007 at 01:33:31PM -0700, Greg KH wrote:
> > On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
> > > Oliver Neukum wrote:
> > > >>Mark Lord wrote:
> > > >>>Okay, from that part (above), the problem is obvious:
> > > >>>in that the "MCT U232 converter now disconnected" appears,
> > > >>>and then we continue to try and call the driver's method.. Oops!
> 
> > > >IMHO shutdown() is using serial->port[] and bombs.
> > > >Could you reverse the order here?
> 
> > > Yup.  Fixed.  Tested.  Works.
> 
> > > This patch fixes the Oops that otherwise occurs whenever
> > > a USB serial adapter is unplugged from a system, as well
> > > the Oops seen when one is in use before resume (to RAM).
> 
> > Argh, no, this change was done to help the ftdi drivers out.
> 
> > Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> > tree from Jim Radford:
> > 	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a
> > 
> > It makes this change because the usb-serial drivers need the port
> > devices when the port_remove() callbacks happen.  Otherwise you get an
> > oops that way.
> 
> > Jim, can you take a look at this and see if you can figure something
> > out?
> 
> The problem is really the
> 
>    serial->port[i] = NULL;
> 
> line after device_unregister() which is used to flag "fake" devices
> that don't need legacy cleanup later in the destrol_serial.  That
> flagging should be done using a *real* flag, and not by overloading
> the ->port[i] pointer since we require it to be non-NULL in
> ->shutdown() in all drivers that are not converted to new
> ->port_probe()/->port_remove() framework (currently all except ftdi).

> I'll work on a patch to do that, but for now, I think you should apply
> Mark's patch to revert the order change since the FTDI driver no
> longer requires the correct ordering of device_unregister() and
> ->shutdown().

Do not NULL serial->port[i] since it is used in ->shutdown().  This
wasn't an issue until the order or ->shutdown() and device_unregister
was corrected.

Signed-Off: Jim Radford <radford@blackbean.org>

diff --git a/drivers/usb/serial/usb-serial.c b/drivers/usb/serial/usb-serial.c
index 8511352..871c9a8 100644
--- a/drivers/usb/serial/usb-serial.c
+++ b/drivers/usb/serial/usb-serial.c
@@ -145,7 +145,6 @@ static void destroy_serial(struct kref *kref)
        for (i = 0; i < serial->num_ports; ++i)
                if (serial->port[i]->dev.parent != NULL) {
                        device_unregister(&serial->port[i]->dev);
-                       serial->port[i] = NULL;
                }

        if (serial->type->shutdown)

Re: [PATCH] usb-serial regression fix

[Greg KH]

On Mon, Mar 12, 2007 at 03:59:22PM -0700, Jim Radford wrote:
> On Mon, Mar 12, 2007 at 03:42:35PM -0700, Jim Radford wrote:
> > On Mon, Mar 12, 2007 at 01:33:31PM -0700, Greg KH wrote:
> > > On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
> > > > Oliver Neukum wrote:
> > > > >>Mark Lord wrote:
> > > > >>>Okay, from that part (above), the problem is obvious:
> > > > >>>in that the "MCT U232 converter now disconnected" appears,
> > > > >>>and then we continue to try and call the driver's method.. Oops!
> > 
> > > > >IMHO shutdown() is using serial->port[] and bombs.
> > > > >Could you reverse the order here?
> > 
> > > > Yup.  Fixed.  Tested.  Works.
> > 
> > > > This patch fixes the Oops that otherwise occurs whenever
> > > > a USB serial adapter is unplugged from a system, as well
> > > > the Oops seen when one is in use before resume (to RAM).
> > 
> > > Argh, no, this change was done to help the ftdi drivers out.
> > 
> > > Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> > > tree from Jim Radford:
> > > 	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a
> > > 
> > > It makes this change because the usb-serial drivers need the port
> > > devices when the port_remove() callbacks happen.  Otherwise you get an
> > > oops that way.
> > 
> > > Jim, can you take a look at this and see if you can figure something
> > > out?
> > 
> > The problem is really the
> > 
> >    serial->port[i] = NULL;
> > 
> > line after device_unregister() which is used to flag "fake" devices
> > that don't need legacy cleanup later in the destrol_serial.  That
> > flagging should be done using a *real* flag, and not by overloading
> > the ->port[i] pointer since we require it to be non-NULL in
> > ->shutdown() in all drivers that are not converted to new
> > ->port_probe()/->port_remove() framework (currently all except ftdi).
> 
> > I'll work on a patch to do that, but for now, I think you should apply
> > Mark's patch to revert the order change since the FTDI driver no
> > longer requires the correct ordering of device_unregister() and
> > ->shutdown().
> 
> Do not NULL serial->port[i] since it is used in ->shutdown().  This
> wasn't an issue until the order or ->shutdown() and device_unregister
> was corrected.
> 
> Signed-Off: Jim Radford <radford@blackbean.org>
> 
> diff --git a/drivers/usb/serial/usb-serial.c b/drivers/usb/serial/usb-serial.c
> index 8511352..871c9a8 100644
> --- a/drivers/usb/serial/usb-serial.c
> +++ b/drivers/usb/serial/usb-serial.c
> @@ -145,7 +145,6 @@ static void destroy_serial(struct kref *kref)
>         for (i = 0; i < serial->num_ports; ++i)
>                 if (serial->port[i]->dev.parent != NULL) {
>                         device_unregister(&serial->port[i]->dev);
> -                       serial->port[i] = NULL;
>                 }

But shouldn't you null it out somewhere?  It will be an "empty" pointer
at some point in time...

Mark, does this solve your oops (after you revert your previous patch)?

thanks,

greg k-h

Re: [PATCH] usb-serial regression fix

[Jim Radford]

On Mon, Mar 12, 2007 at 05:18:19PM -0700, Greg KH wrote:
> On Mon, Mar 12, 2007 at 03:59:22PM -0700, Jim Radford wrote:
> > On Mon, Mar 12, 2007 at 03:42:35PM -0700, Jim Radford wrote:
> > > On Mon, Mar 12, 2007 at 01:33:31PM -0700, Greg KH wrote:
> > > > On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
> > > > > Oliver Neukum wrote:
> > > > > > >Mark Lord wrote:
> > > > > > > >Okay, from that part (above), the problem is obvious:
> > > > > > > >in that the "MCT U232 converter now disconnected"
> > > > > > > >appears, and then we continue to try and call the
> > > > > > > >driver's method.. Oops!

> > > > > >IMHO shutdown() is using serial->port[] and bombs.
> > > > > >Could you reverse the order here?

> > Do not NULL serial->port[i] since it is used in ->shutdown().
> > This wasn't an issue until the order or ->shutdown() and
> > device_unregister was corrected.

> >         for (i = 0; i < serial->num_ports; ++i)
> >                 if (serial->port[i]->dev.parent != NULL) {
> >                         device_unregister(&serial->port[i]->dev);
> > -                       serial->port[i] = NULL;
> >                 }

> But shouldn't you null it out somewhere?  It will be an "empty"
> pointer at some point in time...

Not as far as I can see. The serial structure that ->port[i] is in
gets kfree()ed soon after, in the same function, and nothing in
between, other than ->shutdown(), uses ->port[].  I assume it was
someone being overly cautious.

-Jim

Re: [PATCH] usb-serial regression fix

[Mark Lord]

Jim Radford wrote:
> On Mon, Mar 12, 2007 at 05:18:19PM -0700, Greg KH wrote:
>> On Mon, Mar 12, 2007 at 03:59:22PM -0700, Jim Radford wrote:
>>> On Mon, Mar 12, 2007 at 03:42:35PM -0700, Jim Radford wrote:
>>>> On Mon, Mar 12, 2007 at 01:33:31PM -0700, Greg KH wrote:
>>>>> On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
>>>>>> Oliver Neukum wrote:
>>>>>>>> Mark Lord wrote:
>>>>>>>>> Okay, from that part (above), the problem is obvious:
>>>>>>>>> in that the "MCT U232 converter now disconnected"
>>>>>>>>> appears, and then we continue to try and call the
>>>>>>>>> driver's method.. Oops!
> 
>>>>>>> IMHO shutdown() is using serial->port[] and bombs.
>>>>>>> Could you reverse the order here?
> 
>>> Do not NULL serial->port[i] since it is used in ->shutdown().
>>> This wasn't an issue until the order or ->shutdown() and
>>> device_unregister was corrected.
> 
>>>         for (i = 0; i < serial->num_ports; ++i)
>>>                 if (serial->port[i]->dev.parent != NULL) {
>>>                         device_unregister(&serial->port[i]->dev);
>>> -                       serial->port[i] = NULL;
>>>                 }
> 
>> But shouldn't you null it out somewhere?  It will be an "empty"
>> pointer at some point in time...
> 
> Not as far as I can see. The serial structure that ->port[i] is in
> gets kfree()ed soon after, in the same function, and nothing in
> between, other than ->shutdown(), uses ->port[].  I assume it was
> someone being overly cautious.

So where does the memory get freed -- the structure pointed at
by the serial->port[i] thingie ?  It's not a leak, is it?

???

Re: [PATCH] usb-serial regression fix

[Jim Radford]

On Mon, Mar 12, 2007 at 09:55:14PM -0400, Mark Lord wrote:
> Jim Radford wrote:
> >On Mon, Mar 12, 2007 at 05:18:19PM -0700, Greg KH wrote:
> >>On Mon, Mar 12, 2007 at 03:59:22PM -0700, Jim Radford wrote:
> >>>On Mon, Mar 12, 2007 at 03:42:35PM -0700, Jim Radford wrote:
> >>>>On Mon, Mar 12, 2007 at 01:33:31PM -0700, Greg KH wrote:
> >>>>>On Mon, Mar 12, 2007 at 04:22:22PM -0400, Mark Lord wrote:
> >>>>>>Oliver Neukum wrote:
> >>>>>>>>Mark Lord wrote:
> >>>>>>>>>Okay, from that part (above), the problem is obvious:
> >>>>>>>>>in that the "MCT U232 converter now disconnected"
> >>>>>>>>>appears, and then we continue to try and call the
> >>>>>>>>>driver's method.. Oops!

> >>>>>>>IMHO shutdown() is using serial->port[] and bombs.
> >>>>>>>Could you reverse the order here?

> >>>Do not NULL serial->port[i] since it is used in ->shutdown().
> >>>This wasn't an issue until the order or ->shutdown() and
> >>>device_unregister was corrected.

> >>>        for (i = 0; i < serial->num_ports; ++i)
> >>>                if (serial->port[i]->dev.parent != NULL) {
> >>>                        device_unregister(&serial->port[i]->dev);
> >>>-                       serial->port[i] = NULL;
> >>>                }

> >>But shouldn't you null it out somewhere?  It will be an "empty"
> >>pointer at some point in time...

> >Not as far as I can see. The serial structure that ->port[i] is in
> >gets kfree()ed soon after, in the same function, and nothing in
> >between, other than ->shutdown(), uses ->port[].  I assume it was
> >someone being overly cautious.

> So where does the memory get freed -- the structure pointed at
> by the serial->port[i] thingie ?  It's not a leak, is it?

It gets free'd through device_unregister

    for (i = 0; i < num_ports; ++i) {
       ...
       port->dev.release = &port_release;
       ...
       retval = device_register(&port->dev);

which means that until all the drivers get converted to use
->port_probe() and ->port_remove() (which gets called by
device_unregister) and stop using the ->port[] array in ->shutdown()
we need to have ->shutdown() called before device_unregister.

> > > > Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> > > > tree from Jim Radford:

> > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a

So, this patch should be reverted for now.

-Jim

Re: [PATCH] usb-serial regression fix

[Oliver Neukum]

Am Dienstag, 13. März 2007 10:14 schrieb Jim Radford:

> > So where does the memory get freed -- the structure pointed at
> > by the serial->port[i] thingie ?  It's not a leak, is it?
> 
> It gets free'd through device_unregister
> 
>     for (i = 0; i < num_ports; ++i) {
>        ...
>        port->dev.release = &port_release;
>        ...
>        retval = device_register(&port->dev);
> 
> which means that until all the drivers get converted to use
> ->port_probe() and ->port_remove() (which gets called by
> device_unregister) and stop using the ->port[] array in ->shutdown()
> we need to have ->shutdown() called before device_unregister.
> 
> > > > > Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> > > > > tree from Jim Radford:
> 
> > > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a
> 
> So, this patch should be reverted for now.

While we are at it, is there a reason we call return_serial() late in the
sequence? Making sure the device is not reopened should be the
first measure. Are we protected by hanging up the tty?

Secondly, what is this code supposed to do:

	for (i = 0; i < serial->num_ports; ++i)
		serial->port[i]->open_count = 0;

If we get to destroy_serial(), how can ports still be open?

	Regards
		Oliver

Re: [PATCH] usb-serial regression fix

[Mark Lord]

Oliver Neukum wrote:
>
> If we get to destroy_serial(), how can ports still be open?

(1) open up a ckermit session on /dev/usb_serial_port_0.
(2) suspend the machine (to RAM).
(3) the suspend logic "removes" all USB devices.

Cheers

Re: [PATCH] usb-serial regression fix

[Oliver Neukum]

Am Dienstag, 13. März 2007 14:39 schrieb Mark Lord:
> Oliver Neukum wrote:
> >
> > If we get to destroy_serial(), how can ports still be open?
> 
> (1) open up a ckermit session on /dev/usb_serial_port_0.
> (2) suspend the machine (to RAM).
> (3) the suspend logic "removes" all USB devices.

No,

any open port has taken a reference in serial_open():
	serial = usb_serial_get_by_index(tty->index);

destroy_serial() can be called only when the refcount goes to zero. How
can there be open ports?

	Regards
		Oliver

Re: [PATCH] usb-serial regression fix

[Mark Lord]

Jim Radford wrote:
> On Mon, Mar 12, 2007 at 09:55:14PM -0400, Mark Lord wrote:
>
>> So where does the memory get freed -- the structure pointed at
>> by the serial->port[i] thingie ?  It's not a leak, is it?
> 
> It gets free'd through device_unregister
> 
>     for (i = 0; i < num_ports; ++i) {
>        ...
>        port->dev.release = &port_release;
>        ...
>        retval = device_register(&port->dev);
> 
> which means that until all the drivers get converted to use
> ->port_probe() and ->port_remove() (which gets called by
> device_unregister) and stop using the ->port[] array in ->shutdown()
> we need to have ->shutdown() called before device_unregister.
> 
>>>>> Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
>>>>> tree from Jim Radford:
> 
>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a
> 
> So, this patch should be reverted for now.

Okay, so.. Jim, could you spell it out for us now?

I'm confused.

Based on the current 2.6.21-rc3-git*,
tell us *exactly* what (if any) needs to be reverted,
and *exactly* which (if any) of my suggested patches to apply ?

Thanks

Re: [PATCH] usb-serial regression fix

[Jim Radford]

On Tue, Mar 13, 2007 at 09:55:41AM -0400, Mark Lord wrote:
> Jim Radford wrote:
> >On Mon, Mar 12, 2007 at 09:55:14PM -0400, Mark Lord wrote:
> >
> >>So where does the memory get freed -- the structure pointed at
> >>by the serial->port[i] thingie ?  It's not a leak, is it?
> >
> >It gets free'd through device_unregister
> >
> >    for (i = 0; i < num_ports; ++i) {
> >       ...
> >       port->dev.release = &port_release;
> >       ...
> >       retval = device_register(&port->dev);
> >
> >which means that until all the drivers get converted to use
> >->port_probe() and ->port_remove() (which gets called by
> >device_unregister) and stop using the ->port[] array in ->shutdown()
> >we need to have ->shutdown() called before device_unregister.
> >
> >>>>>Look at changeset d9a7ecacac5f8274d2afce09aadcf37bdb42b93a in Linus's
> >>>>>tree from Jim Radford:
> >
> >>>>>http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9a7ecacac5f8274d2afce09aadcf37bdb42b93a

> >So, this patch should be reverted for now.

> Okay, so.. Jim, could you spell it out for us now?

> I'm confused.

> Based on the current 2.6.21-rc3-git*, tell us *exactly* what (if
> any) needs to be reverted, and *exactly* which (if any) of my
> suggested patches to apply ?

The simple change to not NULL the ->port[] array after unregister was
not quite enough, as ->shutdown() would, as hinted at by Mark, then
access kfree'd memory.

The best thing to do is to just revert
d9a7ecacac5f8274d2afce09aadcf37bdb42b93a and work out a better fix for
the next release.  My patches to fix ftdi_sio no longer require this
patch, so it is pointless at this late state if it breaks *anything*,
and it does.


This patch reverts d9a7ecacac5f8274d2afce09aadcf37bdb42b93a since it
breaks drivers that need to access the ->port[] array in shutdown
(most of them).

Signed-Off: Jim Radford <radford@blackbean.org>

--- b/drivers/usb/serial/usb-serial.c
+++ a/drivers/usb/serial/usb-serial.c
@@ -137,6 +135,11 @@
 
 	dbg("%s - %s", __FUNCTION__, serial->type->description);
 
+	serial->type->shutdown(serial);
+
+	/* return the minor range that this device had */
+	return_serial(serial);
+
 	for (i = 0; i < serial->num_ports; ++i)
 		serial->port[i]->open_count = 0;
 
@@ -147,12 +150,6 @@
 			serial->port[i] = NULL;
 		}
 
-	if (serial->type->shutdown)
-		serial->type->shutdown(serial);
-
-	/* return the minor range that this device had */
-	return_serial(serial);
-
 	/* If this is a "fake" port, we have to clean it up here, as it will
 	 * not get cleaned up in port_release() as it was never registered with
 	 * the driver core */

Re: [PATCH] usb-serial regression fix

[Mark Lord]

Jim Radford wrote:
> ...
> This patch reverts d9a7ecacac5f8274d2afce09aadcf37bdb42b93a since it
> breaks drivers that need to access the ->port[] array in shutdown
> (most of them).

Patch applied, tested, works for me.
 
Signed-Off: Jim Radford <radford@blackbean.org>
Acked-by: Mark Lord <mlord@pobox.com>

--- b/drivers/usb/serial/usb-serial.c
+++ a/drivers/usb/serial/usb-serial.c
@@ -137,6 +135,11 @@
 
 	dbg("%s - %s", __FUNCTION__, serial->type->description);
 
+	serial->type->shutdown(serial);
+
+	/* return the minor range that this device had */
+	return_serial(serial);
+
 	for (i = 0; i < serial->num_ports; ++i)
 		serial->port[i]->open_count = 0;
 
@@ -147,12 +150,6 @@
 			serial->port[i] = NULL;
 		}
 
-	if (serial->type->shutdown)
-		serial->type->shutdown(serial);
-
-	/* return the minor range that this device had */
-	return_serial(serial);
-
 	/* If this is a "fake" port, we have to clean it up here, as it will
 	 * not get cleaned up in port_release() as it was never registered with
 	 * the driver core */

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Oliver Neukum]

Am Montag, 12. März 2007 17:11 schrieb Mark Lord:
> Mark Lord wrote:
> > Greg KH wrote:
> >> Does userspace have it open when you suspend/resume?
> > 
> > For the ooops I just posted, yes, I may have left Linux ckermit
> > running on the serial port before the suspend.
> 
> Here's a retest under linux-2.6.21-rc3-git7,
> doing suspend/resume (RAM) with ckermit open on the serial port.

I am looking at it.

	Regards
		Oliver

Re: [BUG} usb-serial regression in 2.6.21-rc2-git3

[Greg KH]

On Mon, Mar 12, 2007 at 10:56:45AM -0400, Mark Lord wrote:
> Still no improvement on the b0rken usb-serial resume support in -rc*.
> 
> Today I got this ooops on resume from RAM.
> Slightly tainted kernel this time (vmware), but not previously
> on similar crashes.  I cannot yet get it to "crash on demaind",
> so you'll just have to live with it this time.
> 
> All USB was dead until after a reboot this time.

What type of usb-serial device do you have plugged in?
Does userspace have it open when you suspend/resume?
Is vmware accessing the device?

thanks,

greg k-h

Re: [1/6] 2.6.21-rc2: known regressions

[Jeff Garzik]

Adrian Bunk wrote:
> Subject    : forcedeth: skb_over_panic
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
> Submitter  : Albert Hopkins <kernel@marduk.letterboxes.org>
> Status     : unknown


I think this is fixed by the recent forcedeth 3-patch patchset?  Can 
Albert or others confirm?

	Jeff

Re: [1/6] 2.6.21-rc2: known regressions

[Jeff Garzik]

Adrian Bunk wrote:
> Subject    : forcedeth: skb_over_panic
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
> Submitter  : Albert Hopkins <kernel@marduk.letterboxes.org>
> Status     : unknown


I think this is fixed by the recent forcedeth 3-patch patchset?  Can 
Albert or others confirm?

	Jeff

Re: [1/6] 2.6.21-rc2: known regressions

[Albert Hopkins]

On Wed, 2007-03-07 at 06:06 -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
> > Subject    : forcedeth: skb_over_panic
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
> > Submitter  : Albert Hopkins <kernel@marduk.letterboxes.org>
> > Status     : unknown
> 
> 
> I think this is fixed by the recent forcedeth 3-patch patchset?  Can 
> Albert or others confirm?
> 
> 	Jeff
> 

I'll reflect this in th bug report, but I recently tried the forcedeth
driver in 2.6.21-rc3 and still get an oops.

--
Albert W. Hopkins

Re: [1/6] 2.6.21-rc2: known regressions

[Albert Hopkins]

On Wed, 2007-03-07 at 06:06 -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
> > Subject    : forcedeth: skb_over_panic
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=8058
> > Submitter  : Albert Hopkins <kernel@marduk.letterboxes.org>
> > Status     : unknown
> 
> 
> I think this is fixed by the recent forcedeth 3-patch patchset?  Can 
> Albert or others confirm?
> 
> 	Jeff
> 

I'll reflect this in th bug report, but I recently tried the forcedeth
driver in 2.6.21-rc3 and still get an oops.

--
Albert W. Hopkins

[2/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : ThinkPad doesn't resume from suspend to RAM
References : http://lkml.org/lkml/2007/2/27/80
             http://lkml.org/lkml/2007/2/28/348
Submitter  : Jens Axboe <jens.axboe@oracle.com>
             Jeff Chua <jeff.chua.linux@gmail.com>
Status     : unknown


Subject    : beeps get longer after suspend
References : http://lkml.org/lkml/2007/2/26/276
Submitter  : Pavel Machek <pavel@ucw.cz>
Status     : unknown


Subject    : ThinkPad T60: no screen after suspend to RAM
References : http://lkml.org/lkml/2007/2/22/391
Submitter  : Michael S. Tsirkin <mst@mellanox.co.il>
Status     : unknown


Subject    : ThinkPad Z60m: usb mouse stops working after suspend to ram
References : http://lkml.org/lkml/2007/2/21/413
             http://lkml.org/lkml/2007/2/28/172
Submitter  : Arkadiusz Miskiewicz <arekm@maven.pl>
Caused-By  : Konstantin Karasyov <konstantin.a.karasyov@intel.com>
             commit 0a6139027f3986162233adc17285151e78b39cac
Handled-By : Konstantin Karasyov <konstantin.a.karasyov@intel.com>
Status     : problem is being debugged


Subject    : AE_NOT_FOUND ACPI messages
References : http://bugzilla.kernel.org/show_bug.cgi?id=8066
             http://lkml.org/lkml/2007/2/27/263
Submitter  : Thomas Meyer <thomas.mey@web.de>
             Meelis Roos <mroos@linux.ee>
Handled-By : Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Patch      : http://bugzilla.kernel.org/show_bug.cgi?id=8066
Status     : patch available


Subject    : Asus M6Ne notebook: ACPI: First battery is not detected
References : http://bugzilla.kernel.org/show_bug.cgi?id=8080
Submitter  : Janosch Machowinski <jmachowinski@gmx.de>
Status     : unknown


Subject    : AT keyboard only works with pci=noacpi
References : http://lkml.org/lkml/2007/3/3/68
Submitter  : Ash Milsted <thatistosayiseenem@gawab.com>
Status     : unknown

Re: [2/6] 2.6.21-rc2: known regressions

[Jeff Garzik]

Adrian Bunk wrote:
> Subject    : AT keyboard only works with pci=noacpi
> References : http://lkml.org/lkml/2007/3/3/68
> Submitter  : Ash Milsted <thatistosayiseenem@gawab.com>
> Status     : unknown


sounds like a BIOS bug, even though it appears to be a regression?

Re: [2/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Wed, 7 Mar 2007, Jeff Garzik wrote:
>
> Adrian Bunk wrote:
> > Subject    : AT keyboard only works with pci=noacpi
> > References : http://lkml.org/lkml/2007/3/3/68
> > Submitter  : Ash Milsted <thatistosayiseenem@gawab.com>
> > Status     : unknown
> 
> sounds like a BIOS bug, even though it appears to be a regression?

So?

BIOS bugs are not bugs we can fix, they are things we have to work around. 
They are like hardware bugs in a network chip: a "driver" that doesn't 
work around a BIOS bug is simply a *buggy* driver, exactly the same way a 
network driver has to work around errata in the hardware.

So it doesn't really matter if something is a BIOS bug or not. It's not 
reasonable to expect people to upgrade their BIOS'es - even if such an 
upgrade were to exist (which is fairly rare in itself). 

If it used to work, that just makes it (a) doubly important to try to fix 
it, since regressions are BAD BAD BAD and (b) a fair amount *easier* to 
fix, since we can hopefully get an idea of what broke it.

Ash, can you try to use "git bisect" to figure where it started? But 
perhaps just try -rc3 first to see if it's been fixed?

The working setups (whether with irqfixup or with pci=noacpi seem to both 
have a nice

	input: AT Translated Set 2 keyboard as /class/input/inputX

but the nonworking one does not. But even the nonworking one actually 
*found* the controller:

	PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
	PNP: PS/2 controller doesn't have AUX irq; using default 12
	serio: i8042 KBD port at 0x60,0x64 irq 1
	serio: i8042 AUX port at 0x60,0x64 irq 12
	mice: PS/2 mouse device common for all mice

which probably means that the "atkbd_probe()" function fails (probably 
because it never gets a reply, which in turn is probably because the 
interrupt routing is broken).

If you use "atkbd.reset=1" on the kernel command line, you would probably 
get a message like "keyboard reset failed"..

Now, the most likely cause is obviously just the ACPI changes that mess up 
irq routing somehow, but it would be important to figure out *what* makes 
it happen, which is why "git bisect" would be wonderful to try.

So Ash, if you get the git tree, just start with

	git bisect start
	git bisect good v2.6.20
	git bisect bad v2.6.21-rc1

and off you go.. git isn't really that hard to use any more.

		Linus

Re: [2/6] 2.6.21-rc2: known regressions

[Ash Milsted]

On Wed, 07 Mar 2007 06:09:06 -0500
Jeff Garzik <jeff@garzik.org> wrote:

> Adrian Bunk wrote:
> > Subject    : AT keyboard only works with pci=noacpi
> > References : http://lkml.org/lkml/2007/3/3/68
> > Submitter  : Ash Milsted <thatistosayiseenem@gawab.com>
> > Status     : unknown
> 
> 
> sounds like a BIOS bug, even though it appears to be a regression?
> 

Resolved here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=117332735404395&w=2

Was a bug in the i8042 driver it seems.

Ash

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

> Quoting Adrian Bunk <bunk@stusta.de>:
> Subject: [2/6] 2.6.21-rc2: known regressions
> 
> Subject    : ThinkPad T60: no screen after suspend to RAM
> References : http://lkml.org/lkml/2007/2/22/391
> Submitter  : Michael S. Tsirkin <mst@mellanox.co.il>
> Status     : unknown

Here's the status with -rc3: better, but still does not work as well as 2.6.20.

1. Switching to console VT, and running s2ram, I am able to resume to console
   (I have not tested with echo mem > /sys/power/state yet, both work OK
    with 2.6.20)
   This seems to take about as long as with 2.6.20.
   During this time, I see some messages on console (see attached log)

2. First disk access after resume takes a couple of minutes
   (seemed instant with 2.6.20) during this time no new messages show on console

3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
   after waiting for some 10 min, I rebooted.
   no new messages showed up in /var/log/messages

log attached
   
-- 
MST


[-- Attachment #2: newlog --]
[-- Type: text/plain, Size: 20275 bytes --]

Mar  8 08:47:20 localhost kernel: Inspecting /boot/System.map-2.6.21-rc3-work
Mar  8 08:47:20 localhost kernel: Loaded 31265 symbols from /boot/System.map-2.6.21-rc3-work.
Mar  8 08:47:20 localhost kernel: Symbols match kernel version 2.6.21.
Mar  8 08:47:20 localhost kernel: No module symbols loaded - kernel modules not enabled. 
Mar  8 08:47:20 localhost kernel: 1
Mar  8 08:47:20 localhost kernel: [   15.317823] ata2: SATA link down (SStatus 0 SControl 0)
Mar  8 08:47:20 localhost kernel: [   15.317897] scsi2 : ahci
Mar  8 08:47:20 localhost kernel: [   15.379836] ata3: SATA link down (SStatus 0 SControl 0)
Mar  8 08:47:20 localhost kernel: [   15.379909] scsi3 : ahci
Mar  8 08:47:20 localhost kernel: [   15.441854] ata4: SATA link down (SStatus 0 SControl 0)
Mar  8 08:47:20 localhost kernel: [   15.441999] scsi 0:0:0:0: Direct-Access     ATA      HTS541080G9SA00  MB4I PQ: 0 ANSI: 5
Mar  8 08:47:20 localhost kernel: [   15.442216] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Mar  8 08:47:20 localhost kernel: [   15.442292] sda: Write Protect is off
Mar  8 08:47:20 localhost kernel: [   15.443138] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  8 08:47:20 localhost kernel: [   15.443256] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Mar  8 08:47:20 localhost kernel: [   15.443330] sda: Write Protect is off
Mar  8 08:47:20 localhost kernel: [   15.443406] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  8 08:47:20 localhost kernel: [   15.443490]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
Mar  8 08:47:20 localhost kernel: [   15.845145] sd 0:0:0:0: Attached scsi disk sda
Mar  8 08:47:20 localhost kernel: [   15.845290] sd 0:0:0:0: Attached scsi generic sg0 type 0
Mar  8 08:47:20 localhost kernel: [   15.845797] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 21
Mar  8 08:47:20 localhost kernel: [   15.845946] ehci_hcd 0000:00:1d.7: EHCI Host Controller
Mar  8 08:47:20 localhost kernel: [   15.846106] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
Mar  8 08:47:20 localhost kernel: [   15.846229] ehci_hcd 0000:00:1d.7: debug port 1
Mar  8 08:47:20 localhost kernel: [   15.846315] ehci_hcd 0000:00:1d.7: irq 21, io mem 0xee444000
Mar  8 08:47:20 localhost kernel: [   15.850269] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Mar  8 08:47:20 localhost kernel: [   15.850508] usb usb1: configuration #1 chosen from 1 choice
Mar  8 08:47:20 localhost kernel: [   15.850630] hub 1-0:1.0: USB hub found
Mar  8 08:47:20 localhost kernel: [   15.850697] hub 1-0:1.0: 8 ports detected
Mar  8 08:47:20 localhost kernel: [   15.862005] USB Universal Host Controller Interface driver v3.0
Mar  8 08:47:20 localhost kernel: [   15.862135] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:47:20 localhost kernel: [   15.862268] uhci_hcd 0000:00:1d.0: UHCI Host Controller
Mar  8 08:47:20 localhost kernel: [   15.862381] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Mar  8 08:47:20 localhost kernel: [   15.862484] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001820
Mar  8 08:47:20 localhost kernel: [   15.862702] usb usb2: configuration #1 chosen from 1 choice
Mar  8 08:47:20 localhost kernel: [   15.862821] hub 2-0:1.0: USB hub found
Mar  8 08:47:20 localhost kernel: [   15.862887] hub 2-0:1.0: 2 ports detected
Mar  8 08:47:20 localhost kernel: [   15.892543] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 22
Mar  8 08:47:20 localhost kernel: [   15.892676] uhci_hcd 0000:00:1d.1: UHCI Host Controller
Mar  8 08:47:20 localhost kernel: [   15.892789] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Mar  8 08:47:20 localhost kernel: [   15.892894] uhci_hcd 0000:00:1d.1: irq 22, io base 0x00001840
Mar  8 08:47:20 localhost kernel: [   15.893113] usb usb3: configuration #1 chosen from 1 choice
Mar  8 08:47:20 localhost kernel: [   15.893229] hub 3-0:1.0: USB hub found
Mar  8 08:47:20 localhost kernel: [   15.893296] hub 3-0:1.0: 2 ports detected
Mar  8 08:47:20 localhost kernel: [   15.933182] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 23
Mar  8 08:47:20 localhost kernel: [   15.933314] uhci_hcd 0000:00:1d.2: UHCI Host Controller
Mar  8 08:47:20 localhost kernel: [   15.933427] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Mar  8 08:47:20 localhost kernel: [   15.933577] uhci_hcd 0000:00:1d.2: irq 23, io base 0x00001860
Mar  8 08:47:20 localhost kernel: [   15.933797] usb usb4: configuration #1 chosen from 1 choice
Mar  8 08:47:20 localhost kernel: [   15.933915] hub 4-0:1.0: USB hub found
Mar  8 08:47:20 localhost kernel: [   15.933981] hub 4-0:1.0: 2 ports detected
Mar  8 08:47:20 localhost kernel: [   15.976494] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 21
Mar  8 08:47:20 localhost kernel: [   15.976627] uhci_hcd 0000:00:1d.3: UHCI Host Controller
Mar  8 08:47:20 localhost kernel: [   15.976740] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
Mar  8 08:47:20 localhost kernel: [   15.976843] uhci_hcd 0000:00:1d.3: irq 21, io base 0x00001880
Mar  8 08:47:20 localhost kernel: [   15.977060] usb usb5: configuration #1 chosen from 1 choice
Mar  8 08:47:20 localhost kernel: [   15.977196] hub 5-0:1.0: USB hub found
Mar  8 08:47:20 localhost kernel: [   15.977263] hub 5-0:1.0: 2 ports detected
Mar  8 08:47:20 localhost kernel: [   16.040824] Initializing USB Mass Storage driver...
Mar  8 08:47:20 localhost kernel: [   16.157808] usb 5-2: new full speed USB device using uhci_hcd and address 2
Mar  8 08:47:20 localhost kernel: [   16.221329] usb 5-2: configuration #1 chosen from 1 choice
Mar  8 08:47:20 localhost kernel: [   16.224625] usbcore: registered new interface driver usb-storage
Mar  8 08:47:20 localhost kernel: [   16.224692] USB Mass Storage support registered.
Mar  8 08:47:20 localhost kernel: [   16.224886] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
Mar  8 08:47:20 localhost kernel: [   16.233142] serio: i8042 KBD port at 0x60,0x64 irq 1
Mar  8 08:47:20 localhost kernel: [   16.233211] serio: i8042 AUX port at 0x60,0x64 irq 12
Mar  8 08:47:20 localhost kernel: [   16.233366] mice: PS/2 mouse device common for all mice
Mar  8 08:47:20 localhost kernel: [   16.233716] Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Tue Mar 06 13:10:00 2007 UTC).
Mar  8 08:47:20 localhost kernel: [   16.234221] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 22
Mar  8 08:47:20 localhost kernel: [   16.236937] input: AT Translated Set 2 keyboard as /class/input/input3
Mar  8 08:47:20 localhost kernel: [   16.444361] ALSA device list:
Mar  8 08:47:20 localhost kernel: [   16.444428]   #0: HDA Intel at 0xee240000 irq 22
Mar  8 08:47:20 localhost kernel: [   16.444525] nf_conntrack version 0.5.0 (7168 buckets, 57344 max)
Mar  8 08:47:20 localhost kernel: [   16.444736] ip_tables: (C) 2000-2006 Netfilter Core Team
Mar  8 08:47:20 localhost kernel: [   16.444809] TCP cubic registered
Mar  8 08:47:20 localhost kernel: [   16.444887] NET: Registered protocol family 1
Mar  8 08:47:20 localhost kernel: [   16.444953] NET: Registered protocol family 17
Mar  8 08:47:20 localhost kernel: [   16.445019] ieee80211: 802.11 data/management/control stack, git-1.1.13
Mar  8 08:47:20 localhost kernel: [   16.445087] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Mar  8 08:47:20 localhost kernel: [   16.445185] Starting balanced_irq
Mar  8 08:47:20 localhost kernel: [   16.445254] Using IPI No-Shortcut mode
Mar  8 08:47:20 localhost kernel: [   16.472663] kjournald starting.  Commit interval 5 seconds
Mar  8 08:47:20 localhost kernel: [   16.472735] EXT3-fs: mounted filesystem with ordered data mode.
Mar  8 08:47:20 localhost kernel: [   16.472864] VFS: Mounted root (ext3 filesystem) readonly.
Mar  8 08:47:20 localhost kernel: [   16.473029] Freeing unused kernel memory: 184k freed
Mar  8 08:47:20 localhost kernel: [   16.473122] Write protecting the kernel read-only data: 902k
Mar  8 08:47:20 localhost kernel: [   24.658491] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
Mar  8 08:47:20 localhost kernel: [   24.658576] Copyright (c) 1999-2006 Intel Corporation.
Mar  8 08:47:20 localhost kernel: [   24.658761] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:47:20 localhost kernel: [   24.733801] e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:16:41:54:6c:47
Mar  8 08:47:20 localhost kernel: [   24.815441] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Mar  8 08:47:20 localhost kernel: [   25.282292] Adding 1951824k swap on /dev/sda6.  Priority:-1 extents:1 across:1951824k
Mar  8 08:47:20 localhost kernel: [   25.343370] EXT3 FS on sda3, internal journal
Mar  8 08:47:20 localhost kernel: [   25.697608] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04793/0x300000
Mar  8 08:47:20 localhost kernel: [   25.697710] serio: Synaptics pass-through port at isa0060/serio1/input0
Mar  8 08:47:20 localhost kernel: [   25.742946] input: SynPS/2 Synaptics TouchPad as /class/input/input4
Mar  8 08:47:20 localhost kernel: [   30.419349] NTFS volume version 3.1.
Mar  8 08:47:20 localhost kernel: [   31.156204] IBM TrackPoint firmware: 0x0e, buttons: 3/3
Mar  8 08:47:20 localhost kernel: [   31.426442] input: TPPS/2 IBM TrackPoint as /class/input/input5
Mar  8 08:47:22 localhost hpiod: 0.9.7 accepting connections at 50899... 
Mar  8 08:47:26 localhost kernel: [   39.389386] [drm] Initialized i915 1.6.0 20060119 on minor 0
Mar  8 08:48:07 localhost kernel: <1] pcieport-driver 0000:00:1c.3: LATE suspend
Mar  8 08:48:07 localhost kernel: [    2.183443] Intel machine check architecture supported.
Mar  8 08:48:07 localhost kernel: [    2.183451] Intel machine check reporting enabled on CPU#0.
Mar  8 08:48:07 localhost kernel: [    2.183982] Enabling non-boot CPUs ...
Mar  8 08:48:07 localhost kernel: [    2.321035] SMP alternatives: switching to SMP code
Mar  8 08:48:07 localhost kernel: [    2.321241] Booting processor 1/1 eip 3000
Mar  8 08:48:07 localhost kernel: [    2.332199] Initializing CPU#1
Mar  8 08:48:07 localhost kernel: [    3.143727] Calibrating delay using timer specific routine.. 20089.15 BogoMIPS (lpj=100445793)
Mar  8 08:48:07 localhost kernel: [    3.143746] monitor/mwait feature present.
Mar  8 08:48:07 localhost kernel: [    3.143751] CPU: L1 I cache: 32K, L1 D cache: 32K
Mar  8 08:48:07 localhost kernel: [    3.143755] CPU: L2 cache: 2048K
Mar  8 08:48:07 localhost kernel: [    3.143759] CPU: Physical Processor ID: 0
Mar  8 08:48:07 localhost kernel: [    3.143761] CPU: Processor Core ID: 1
Mar  8 08:48:07 localhost kernel: [    3.143774] Intel machine check architecture supported.
Mar  8 08:48:07 localhost kernel: [    3.143783] Intel machine check reporting enabled on CPU#1.
Mar  8 08:48:07 localhost kernel: [    3.144104] CPU1: Intel Genuine Intel(R) CPU           T2400  @ 1.83GHz stepping 08
Mar  8 08:48:07 localhost kernel: [    3.144892] speedstep-centrino with X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated.
Mar  8 08:48:07 localhost kernel: [    3.144896]  Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead.
Mar  8 08:48:07 localhost kernel: [    3.144936] CPU1 is up
Mar  8 08:48:07 localhost kernel: [    3.440273] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:07 localhost kernel: [    3.527272] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 22
Mar  8 08:48:07 localhost kernel: [    3.912917] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:07 localhost kernel: [    3.912966] usb usb2: root hub lost power or was reset
Mar  8 08:48:07 localhost kernel: [    3.912988] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 22
Mar  8 08:48:07 localhost kernel: [    3.913036] usb usb3: root hub lost power or was reset
Mar  8 08:48:07 localhost kernel: [    3.913055] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 23
Mar  8 08:48:07 localhost kernel: [    3.913102] usb usb4: root hub lost power or was reset
Mar  8 08:48:07 localhost kernel: [    3.913120] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 21
Mar  8 08:48:07 localhost kernel: [    3.913168] usb usb5: root hub lost power or was reset
Mar  8 08:48:07 localhost kernel: [    3.914015] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 21
Mar  8 08:48:07 localhost kernel: [    3.914205] ACPI: PCI Interrupt 0000:00:1f.1[C] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:07 localhost kernel: [    3.914407] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:07 localhost kernel: [    3.922880] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:07 localhost kernel: [    3.928614] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:07 localhost kernel: [    3.928638] pnp: Device 00:08 does not support activation.
Mar  8 08:48:07 localhost kernel: [    3.928641] pnp: Device 00:09 does not support activation.
Mar  8 08:48:07 localhost kernel: [    4.209165] ata2: SATA link down (SStatus 0 SControl 0)
Mar  8 08:48:07 localhost kernel: [    4.209179] ata3: SATA link down (SStatus 0 SControl 0)
Mar  8 08:48:07 localhost kernel: [    4.209191] ata4: SATA link down (SStatus 0 SControl 0)
Mar  8 08:48:07 localhost kernel: [    4.849894] atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
Mar  8 08:48:07 localhost kernel: [    4.849896] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
Mar  8 08:48:07 localhost kernel: [    4.850297] atkbd.c: Unknown key pressed (translated set 2, code 0x63 on isa0060/serio0).
Mar  8 08:48:07 localhost kernel: [    4.850300] atkbd.c: Use 'setkeycodes 63 <keycode>' to make it known.
Mar  8 08:48:07 localhost kernel: [    5.826771] Restarting tasks ... <6>usb 5-2: USB disconnect, address 2
Mar  8 08:48:07 localhost kernel: [    5.839206] done.
Mar  8 08:48:07 localhost kernel: [    6.702776] ata1: waiting for device to spin up (7 secs)
Mar  8 08:48:07 localhost kernel: [    6.775788] usb 5-2: new full speed USB device using uhci_hcd and address 3
Mar  8 08:48:07 localhost kernel: [    6.866806] usb 5-2: configuration #1 chosen from 1 choice
Mar  8 08:48:07 localhost kernel: [   11.334773] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar  8 08:48:07 localhost kernel: [   11.673734] ata1.00: configured for UDMA/100
Mar  8 08:48:07 localhost kernel: [   11.696311] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Mar  8 08:48:07 localhost kernel: [   11.697691] sda: Write Protect is off
Mar  8 08:48:07 localhost kernel: [   11.708467] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  8 08:48:16 localhost kernel: <>[   19.841599] button button_power:00: suspend
Mar  8 08:48:16 localhost kernel: [   19.841607] Disabling non-boot CPUs ...
Mar  8 08:48:16 localhost kernel: [   19.847811] Breaking affinity for irq 12
Mar  8 08:48:16 localhost kernel: [   20.444974] CPU 1 is now offline
Mar  8 08:48:16 localhost kernel: [   20.444980] SMP alternatives: switching to UP code
Mar  8 08:48:16 localhost kernel: [   20.445823] CPU1 is down
Mar  8 08:48:16 localhost kernel: [    2.423903] Intel machine check architecture supported.
Mar  8 08:48:16 localhost kernel: [    2.423911] Intel machine check reporting enabled on CPU#0.
Mar  8 08:48:16 localhost kernel: [    2.424444] Enabling non-boot CPUs ...
Mar  8 08:48:16 localhost kernel: [    2.534642] SMP alternatives: switching to SMP code
Mar  8 08:48:16 localhost kernel: [    2.534847] Booting processor 1/1 eip 3000
Mar  8 08:48:16 localhost kernel: [    2.545805] Initializing CPU#1
Mar  8 08:48:16 localhost kernel: [    3.357337] Calibrating delay using timer specific routine.. 20089.13 BogoMIPS (lpj=100445659)
Mar  8 08:48:16 localhost kernel: [    3.357357] monitor/mwait feature present.
Mar  8 08:48:16 localhost kernel: [    3.357362] CPU: L1 I cache: 32K, L1 D cache: 32K
Mar  8 08:48:16 localhost kernel: [    3.357365] CPU: L2 cache: 2048K
Mar  8 08:48:16 localhost kernel: [    3.357369] CPU: Physical Processor ID: 0
Mar  8 08:48:16 localhost kernel: [    3.357372] CPU: Processor Core ID: 1
Mar  8 08:48:16 localhost kernel: [    3.357384] Intel machine check architecture supported.
Mar  8 08:48:16 localhost kernel: [    3.357394] Intel machine check reporting enabled on CPU#1.
Mar  8 08:48:16 localhost kernel: [    3.357711] CPU1: Intel Genuine Intel(R) CPU           T2400  @ 1.83GHz stepping 08
Mar  8 08:48:16 localhost kernel: [    3.358503] speedstep-centrino with X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated.
Mar  8 08:48:16 localhost kernel: [    3.358507]  Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead.
Mar  8 08:48:16 localhost kernel: [    3.358548] CPU1 is up
Mar  8 08:48:16 localhost kernel: [    3.653795] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:16 localhost kernel: [    3.740900] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 22
Mar  8 08:48:16 localhost kernel: [    4.126569] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:16 localhost kernel: [    4.126619] usb usb2: root hub lost power or was reset
Mar  8 08:48:16 localhost kernel: [    4.126639] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 22
Mar  8 08:48:16 localhost kernel: [    4.126686] usb usb3: root hub lost power or was reset
Mar  8 08:48:16 localhost kernel: [    4.126705] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 23
Mar  8 08:48:16 localhost kernel: [    4.126752] usb usb4: root hub lost power or was reset
Mar  8 08:48:16 localhost kernel: [    4.126772] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 21
Mar  8 08:48:16 localhost kernel: [    4.126819] usb usb5: root hub lost power or was reset
Mar  8 08:48:16 localhost kernel: [    4.127659] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 21
Mar  8 08:48:16 localhost kernel: [    4.127848] ACPI: PCI Interrupt 0000:00:1f.1[C] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:16 localhost kernel: [    4.128049] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:16 localhost kernel: [    4.136510] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:16 localhost kernel: [    4.142247] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
Mar  8 08:48:16 localhost kernel: [    4.142271] pnp: Device 00:08 does not support activation.
Mar  8 08:48:16 localhost kernel: [    4.142274] pnp: Device 00:09 does not support activation.
Mar  8 08:48:16 localhost kernel: [    4.421975] ata2: SATA link down (SStatus 0 SControl 0)
Mar  8 08:48:16 localhost kernel: [    4.421989] ata3: SATA link down (SStatus 0 SControl 0)
Mar  8 08:48:16 localhost kernel: [    4.422001] ata4: SATA link down (SStatus 0 SControl 0)
Mar  8 08:48:16 localhost kernel: [    5.971047] Restarting tasks ... done.
Mar  8 08:48:16 localhost kernel: [    6.012513] usb 5-2: USB disconnect, address 3
Mar  8 08:48:16 localhost kernel: [    6.891677] ata1: waiting for device to spin up (7 secs)
Mar  8 08:48:16 localhost kernel: [    6.958587] usb 5-2: new full speed USB device using uhci_hcd and address 4
Mar  8 08:48:16 localhost kernel: [    7.049506] usb 5-2: configuration #1 chosen from 1 choice
Mar  8 08:48:16 localhost kernel: [   11.547844] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar  8 08:48:16 localhost kernel: [   11.885459] ata1.00: configured for UDMA/100
Mar  8 08:48:16 localhost kernel: [   11.913910] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Mar  8 08:48:16 localhost kernel: [   11.914575] sda: Write Protect is off
Mar  8 08:48:16 localhost kernel: [   11.914868] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar  8 08:48:16 localhost shutdown[4092]: shutting down for system halt

Re: [2/6] 2.6.21-rc2: known regressions

[Jeff Chua]

On 3/8/07, Michael S. Tsirkin <mst@mellanox.co.il> wrote:
> > Quoting Adrian Bunk <bunk@stusta.de>:
> > Subject: [2/6] 2.6.21-rc2: known regressions
> >
> > Subject    : ThinkPad T60: no screen after suspend to RAM
> > References : http://lkml.org/lkml/2007/2/22/391
> > Submitter  : Michael S. Tsirkin <mst@mellanox.co.il>
> > Status     : unknown
>
> Here's the status with -rc3: better, but still does not work as well as 2.6.20.

> 3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
>    after waiting for some 10 min, I rebooted.
>    no new messages showed up in /var/log/messages

In my case, I can "suspend" and "resume", but seems the clock died
after resume. "date" always returns the same time! I had to disable
CONFIG_NO_HZ and CONFIG_SYSFS_DEPRECATED in order to suspend.

Try to execute "date" and see if it changes after resume.

Thanks,
Jeff.

Re: [2/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

[ Eric, Ingo, can you double-check the timer initialization after resume? 
  We appear to have several reports of date not advancing, and while this 
  could be some SATA issue, it could easily be a timer tick issue too ]

On Thu, 8 Mar 2007, Michael S. Tsirkin wrote:
> 
> Here's the status with -rc3: better, but still does not work as well as 2.6.20.

Ok. I think we mostly solved the irq-related stuff, but you might want to 
check whether you have CONFIG_NOHZ on or off and whether that makes a 
difference.

> 2. First disk access after resume takes a couple of minutes
>    (seemed instant with 2.6.20) during this time no new messages show on console

Yeah, there is some problem with SATA resume. It would be beautiful if the 
people who actually see this could narrow it down with bisection. "It 
works for me" is clearly the case for many people, but not all.

But before blaming SATA, check if you have NO_HZ enabled and whether 
disabling that makes it work ok. If timeouts don't work right (or are 
*extremely* slow) things that should be instant won't be.

> 3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
>    after waiting for some 10 min, I rebooted.
>    no new messages showed up in /var/log/messages

I think this is likely just more of the disk being buggered, but it could 
again be related to NO_HZ (people report time not advancing, and that 
would make any X timeout taking forever, and you'd see exactly your 
behaviour).

		Linus

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> > 3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
> >    after waiting for some 10 min, I rebooted. no new messages showed 
> >    up in /var/log/messages
> 
> I think this is likely just more of the disk being buggered, but it 
> could again be related to NO_HZ (people report time not advancing, and 
> that would make any X timeout taking forever, and you'd see exactly 
> your behaviour).

Michael - does your 'date' output advance after resume? If not then i'd 
say it's a NO_HZ related problem. If yes then i'd guess it's the SATA 
problem.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> Michael - does your 'date' output advance after resume? If not then 
> i'd say it's a NO_HZ related problem. [...]

in that case please do this on such a 'frozen date' system:

	echo q > /proc/sysrq-trigger

and then send us the hw-timers info.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> Michael - does your 'date' output advance after resume? If not then 
> i'd say it's a NO_HZ related problem. [...]

in that case please do this on such a 'frozen date' system:

	echo q > /proc/sysrq-trigger

and then send us the hw-timers info.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [2/6] 2.6.21-rc2: known regressions
> 
> 
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > > 3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
> > >    after waiting for some 10 min, I rebooted. no new messages showed 
> > >    up in /var/log/messages
> > 
> > I think this is likely just more of the disk being buggered, but it 
> > could again be related to NO_HZ (people report time not advancing, and 
> > that would make any X timeout taking forever, and you'd see exactly 
> > your behaviour).
> 
> Michael - does your 'date' output advance after resume? If not then i'd 
> say it's a NO_HZ related problem. If yes then i'd guess it's the SATA 
> problem.

I'll test, but I have NO_HZ off for now.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [2/6] 2.6.21-rc2: known regressions
> 
> 
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > > 3. When I switch to X (CTRL-ALT-F7), X hangs after drawing a couple of windows
> > >    after waiting for some 10 min, I rebooted. no new messages showed 
> > >    up in /var/log/messages
> > 
> > I think this is likely just more of the disk being buggered, but it 
> > could again be related to NO_HZ (people report time not advancing, and 
> > that would make any X timeout taking forever, and you'd see exactly 
> > your behaviour).
> 
> Michael - does your 'date' output advance after resume? If not then i'd 
> say it's a NO_HZ related problem. If yes then i'd guess it's the SATA 
> problem.

I'll test, but I have NO_HZ off for now.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Michael S. Tsirkin <mst@mellanox.co.il> wrote:

> > Michael - does your 'date' output advance after resume? If not then 
> > i'd say it's a NO_HZ related problem. If yes then i'd guess it's the 
> > SATA problem.
> 
> I'll test, but I have NO_HZ off for now.

there can still be effects of it (the regression we fixed in -rc3 was 
such an effect too), so please test it.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> > 2. First disk access after resume takes a couple of minutes
> >    (seemed instant with 2.6.20) during this time no new messages 
> >    show on console
> 
> Yeah, there is some problem with SATA resume. It would be beautiful if 
> the people who actually see this could narrow it down with bisection. 
> "It works for me" is clearly the case for many people, but not all.

Thomas found a new twist to this today: applying the patch below (which 
turns on ATA_DEBUG) made the SATA problem go away on his laptop. 
Michael, could you try this patch, does it change the behavior of your 
laptop in any way?

	Ingo

---
 include/linux/libata.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux/include/linux/libata.h
===================================================================
--- linux.orig/include/linux/libata.h
+++ linux/include/linux/libata.h
@@ -51,7 +51,7 @@
  * compile-time options: to be removed as soon as all the drivers are
  * converted to the new debugging mechanism
  */
-#undef ATA_DEBUG		/* debugging output */
+#define ATA_DEBUG 1		/* debugging output */
 #undef ATA_VERBOSE_DEBUG	/* yet more debugging output */
 #undef ATA_IRQ_TRAP		/* define to ack screaming irqs */
 #undef ATA_NDEBUG		/* define to disable quick runtime checks */

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> Thomas found a new twist to this today: applying the patch below 
> (which turns on ATA_DEBUG) made the SATA problem go away on his 
> laptop. Michael, could you try this patch, does it change the behavior 
> of your laptop in any way?

Here's another suspend/resume artifact: one of my boxes wouldnt resume, 
it hangs at:

[    1.456633] pci 0000:00:18.2: resuming
[    1.456641] pci 0000:00:18.3: resuming
[    1.456648] 8139too 0000:05:07.0: resuming
[    1.456667] radeonfb 0000:01:00.0: resuming

the box is pingable but otherwise no console and it's hung as well. [I 
got the log above via netconsole]

disabling the following radeonfb options in the .config made resume work 
again:

 CONFIG_FB_RADEON=y
 CONFIG_FB_RADEON_I2C=y
 CONFIG_FB_RADEON_BACKLIGHT=y

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> Here's another suspend/resume artifact: one of my boxes wouldnt 
> resume, it hangs at:
> 
> [    1.456633] pci 0000:00:18.2: resuming
> [    1.456641] pci 0000:00:18.3: resuming
> [    1.456648] 8139too 0000:05:07.0: resuming
> [    1.456667] radeonfb 0000:01:00.0: resuming
> 
> the box is pingable but otherwise no console and it's hung as well. [I 
> got the log above via netconsole]

unfortunately there's no way to get any backtrace out of the system at 
this point - the timer interrupts are not active yet here, so i cannot 
use the softlockup_tick patch to sample the lockup. Since it's pingable 
i'll try to hack a dump_stack() into icmp_reply() ;-)

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> > Here's another suspend/resume artifact: one of my boxes wouldnt 
> > resume, it hangs at:
> > 
> > [    1.456633] pci 0000:00:18.2: resuming
> > [    1.456641] pci 0000:00:18.3: resuming
> > [    1.456648] 8139too 0000:05:07.0: resuming
> > [    1.456667] radeonfb 0000:01:00.0: resuming
> > 
> > the box is pingable but otherwise no console and it's hung as well. [I 
> > got the log above via netconsole]
> 
> unfortunately there's no way to get any backtrace out of the system at 
> this point - the timer interrupts are not active yet here, so i cannot 
> use the softlockup_tick patch to sample the lockup. Since it's 
> pingable i'll try to hack a dump_stack() into icmp_reply() ;-)

didnt succeed at that - no netconsole output during the hang. But the 
RADEON_FB .config options definitely make the difference. The video card 
in question is:

01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Fri, 9 Mar 2007, Ingo Molnar wrote:
> 
> disabling the following radeonfb options in the .config made resume work 
> again:

In general, don't even *try* to use radeonfb for suspend/resume.

I don't think it has ever worked, except on some very rare laptops 
(largely PPC Macs) where people had enough information to set up the 
PLL's.

I don't think the other framebuffer drivers are much better.

You're better off using the VGA console, and lettign X re-initialize the 
graphics device. That generally at least has a reasonably good chance of 
working.

Re-initializing graphics modes really is very hard. You can try with the 
BIOS video hack (I forget the kernel command line to turn it on), but we 
really do end up depending on X doing it better.

Some day we may have modesetting support in the kernel for some graphics 
hw, right now it's pretty damn spotty.

		Linus

Re: [2/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Fri, 9 Mar 2007, Ingo Molnar wrote:
> 
> disabling the following radeonfb options in the .config made resume work 
> again:

In general, don't even *try* to use radeonfb for suspend/resume.

I don't think it has ever worked, except on some very rare laptops 
(largely PPC Macs) where people had enough information to set up the 
PLL's.

I don't think the other framebuffer drivers are much better.

You're better off using the VGA console, and lettign X re-initialize the 
graphics device. That generally at least has a reasonably good chance of 
working.

Re-initializing graphics modes really is very hard. You can try with the 
BIOS video hack (I forget the kernel command line to turn it on), but we 
really do end up depending on X doing it better.

Some day we may have modesetting support in the kernel for some graphics 
hw, right now it's pretty damn spotty.

		Linus

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> > disabling the following radeonfb options in the .config made resume 
> > work again:
> 
> In general, don't even *try* to use radeonfb for suspend/resume.
> 
> I don't think it has ever worked, except on some very rare laptops 
> (largely PPC Macs) where people had enough information to set up the 
> PLL's.
> 
> I don't think the other framebuffer drivers are much better.
> 
> You're better off using the VGA console, and lettign X re-initialize 
> the graphics device. That generally at least has a reasonably good 
> chance of working.
> 
> Re-initializing graphics modes really is very hard. You can try with 
> the BIOS video hack (I forget the kernel command line to turn it on), 
> but we really do end up depending on X doing it better.

it's the s3_sleep boot option and /proc/sys/kernel/acpi_video_mode, but 
that didnt make a difference.

> Some day we may have modesetting support in the kernel for some 
> graphics hw, right now it's pretty damn spotty.

having no video is what i'd have expected - but getting a /hang/ is not 
what i'd have expected.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Fri, 9 Mar 2007, Ingo Molnar wrote:
> > Some day we may have modesetting support in the kernel for some 
> > graphics hw, right now it's pretty damn spotty.
> 
> having no video is what i'd have expected - but getting a /hang/ is not 
> what i'd have expected.

I debugged a case exactly like this (with the TRACE_RESUME() thing) back 
last November on my laptop.

The problem is that radeonfb actually *tries* to re-initialize the 
graphics chips, but because it doesn't know all the details, it does it 
wrong, and hangs the whole chip.

I forget exactly where it happened, and it might well be different for 
you. But this is exactly what TRACE_RESUME can be used to pinpoint if you 
want to try to debug it. 

			Linus

Re: [2/6] 2.6.21-rc2: known regressions

[Pavel Machek]

Hi!

> > disabling the following radeonfb options in the .config made resume work 
> > again:
> 
> In general, don't even *try* to use radeonfb for suspend/resume.
> 
> I don't think it has ever worked, except on some very rare laptops 
> (largely PPC Macs) where people had enough information to set up the 
> PLL's.

It worked ok on thinkpad x32. BIOS did the setup in resume case (with
acpi_sleep=..., anyway), and radeonfb could pick the card up from there.

> I don't think the other framebuffer drivers are much better.
> 
> You're better off using the VGA console, and lettign X re-initialize the 
> graphics device. That generally at least has a reasonably good chance of 
> working.

suspend.sf.net, s2ram there has a long list of tricks. If you invent
new one, please add it there.

> Re-initializing graphics modes really is very hard. You can try with the 
> BIOS video hack (I forget the kernel command line to turn it on), but we 
> really do end up depending on X doing it better.

...or you can try vbetool; it is similar hack to acpi_sleep=... , but
it works for more people.

> Some day we may have modesetting support in the kernel for some graphics 
> hw, right now it's pretty damn spotty.

Yep, that's the way to go.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Pavel Machek <pavel@ucw.cz> wrote:

> > Some day we may have modesetting support in the kernel for some 
> > graphics hw, right now it's pretty damn spotty.
> 
> Yep, that's the way to go.

hey, i wildly supported this approach ever since 1996, when GGI came up
:-/

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Pavel Machek <pavel@ucw.cz> wrote:

> > Some day we may have modesetting support in the kernel for some 
> > graphics hw, right now it's pretty damn spotty.
> 
> Yep, that's the way to go.

hey, i wildly supported this approach ever since 1996, when GGI came up
:-/

	Ingo

Re: [linux-pm] [2/6] 2.6.21-rc2: known regressions

[Jim Gettys]

On Sun, 2007-03-18 at 17:07 +0100, Ingo Molnar wrote:
> * Pavel Machek <pavel@ucw.cz> wrote:
> 
> > > Some day we may have modesetting support in the kernel for some 
> > > graphics hw, right now it's pretty damn spotty.
> > 
> > Yep, that's the way to go.
> 
> hey, i wildly supported this approach ever since 1996, when GGI came up
> :-/
> 

So wildly you wrote tons of code.... ;-).

More seriously, at the time, XFree86 would have spat in your face for
any such thing.  Thankfully, times are changing.

Also more seriously, a somewhat hybrid approach is in order for mode
setting: simple mode setting isn't much code and is required for sane
behavior on crash (it is nice to get oopses onto a screen); but the full
blown mode setting/configuration problem is so large that on some
hardware, it is likely left best left to a helper process (not the X
server).

Also key to get sane behavior out of the scheduler is to get the X
server to yield (sleep in the kernel) rather than busy waiting when the
GPU is busy; a standardized interface for this for both fbdev and dri is
in order.  Right now, X is a misbehaving compute bound process rather
than the properly interactive process it can/should/will be, releasing
the CPU whenever the hardware is busy. Needless to say, this wastes
cycles and hurts interactivity with just about any scheduler you can
devise. It isn't as if this is hard; on UNIX systems we did it in 1984
or thereabouts.

Of course, in 1996, XFree86 would have ignored any such interfaces, in
its insane quest for operating system independent user space drivers
requiring no standard kernel interfaces.... (it is the second part of
this where the true insanity lay).
                                  - Jim

-- 
Jim Gettys
One Laptop Per Child

BSOD (was: [2/6] 2.6.21-rc2: known regressions)

[Pete Zaitcev]

On Sun, 18 Mar 2007 12:40:45 -0400, Jim Gettys <jg@laptop.org> wrote:

> Also more seriously, a somewhat hybrid approach is in order for mode
> setting: simple mode setting isn't much code and is required for sane
> behavior on crash (it is nice to get oopses onto a screen); but the full
> blown mode setting/configuration problem is so large that on some
> hardware, it is likely left best left to a helper process (not the X
> server).

Jim, I doubt that a mode switch on oops is a good idea. Maybe I'm unlucky,
but in my experience, it often is the case that systems fail to switch
to text mode for shutdown. What is amazing, the very same systems switch
to text mode on <Alt>F1 just fine, and then back to <Alt>F7!
I would hazard a guess that this happens because nobody cares
about shutdown modes to fix them. But then the same is true for
crashes.

I understand that you have your own experience, but thought to note
this all the same.

>From the constructive angle, I think that a crash should render into
existing mode, into the currently mapped frame buffer. This is the
only way how it can be made to work reliably.

Yours,
-- Pete

Re: BSOD

[David Miller]

From: Pete Zaitcev <zaitcev@redhat.com>
Date: Mon, 19 Mar 2007 12:08:07 -0700

> On Sun, 18 Mar 2007 12:40:45 -0400, Jim Gettys <jg@laptop.org> wrote:
> 
> > Also more seriously, a somewhat hybrid approach is in order for mode
> > setting: simple mode setting isn't much code and is required for sane
> > behavior on crash (it is nice to get oopses onto a screen); but the full
> > blown mode setting/configuration problem is so large that on some
> > hardware, it is likely left best left to a helper process (not the X
> > server).
> 
> Jim, I doubt that a mode switch on oops is a good idea. Maybe I'm unlucky,
> but in my experience, it often is the case that systems fail to switch
> to text mode for shutdown. What is amazing, the very same systems switch
> to text mode on <Alt>F1 just fine, and then back to <Alt>F7!
> I would hazard a guess that this happens because nobody cares
> about shutdown modes to fix them. But then the same is true for
> crashes.
> 
> I understand that you have your own experience, but thought to note
> this all the same.
> 
> From the constructive angle, I think that a crash should render into
> existing mode, into the currently mapped frame buffer. This is the
> only way how it can be made to work reliably.

All of this talk makes me appreciate what happens on Sparc machines
even though it has more often than not been ridiculed.

There the firmware sets the resolution and that's basically what
the kernel and X uses, no mode changes are performed.

With that kind of setup even the system firmware (such as OFW) can
render error messages onto the console while X is active.

The disadvantage of course is that you're stuck with whatever video
mode you configured the firmware to use.  The advantage is that you
always get crash messages and neither X nor the kernel framebuffer
driver need to know how to switch modes.

Back to the main discussion, when we get an OOPS you can basically
assume that nothing works.  So I definitely agree with Peter.
There is no way we should try to execute something so non-trivial
as a mode switch when the kernel is on it's last legs.

There are four pieces of information the kernel needs from the X
server when it switches modes in order to do this:

1) pixel resolution
2) frame buffer base, should be specified in an extremely
   portable a manner (this means NOT using physical addresses
   or just PCI addresses), perhaps a PCI device specifier,
   BAR index, and offset from that BAR.
3) frame buffer w-skip (ie. how many bytes to get to the next
   scanline)
4) depth/bpp

This is also what the most minimal kernel framebuffer driver needs in
order to support a chip.

I understand that there are chips that can only be rendered into using
DMA or indirect accesses, that's a very real and tough problem to fix.
There is also the issue of making sure the graphics card accelerator
is not rendering anything (ie. it's pipeline FIFO has emptied) when
we try to render a panic message.

Re: BSOD

[Jesse Barnes]

On Monday, March 19, 2007 12:38 pm David Miller wrote:
> All of this talk makes me appreciate what happens on Sparc machines
> even though it has more often than not been ridiculed.
>
> There the firmware sets the resolution and that's basically what
> the kernel and X uses, no mode changes are performed.
>
> With that kind of setup even the system firmware (such as OFW) can
> render error messages onto the console while X is active.
>
> The disadvantage of course is that you're stuck with whatever video
> mode you configured the firmware to use.  The advantage is that you
> always get crash messages and neither X nor the kernel framebuffer
> driver need to know how to switch modes.

That certainly keeps things simple, but most machines force us into a 
more flexible approach. :)

> Back to the main discussion, when we get an OOPS you can basically
> assume that nothing works.  So I definitely agree with Peter.
> There is no way we should try to execute something so non-trivial
> as a mode switch when the kernel is on it's last legs.
>
> There are four pieces of information the kernel needs from the X
> server when it switches modes in order to do this:
>
> 1) pixel resolution
> 2) frame buffer base, should be specified in an extremely
>    portable a manner (this means NOT using physical addresses
>    or just PCI addresses), perhaps a PCI device specifier,
>    BAR index, and offset from that BAR.
> 3) frame buffer w-skip (ie. how many bytes to get to the next
>    scanline)
> 4) depth/bpp
>
> This is also what the most minimal kernel framebuffer driver needs in
> order to support a chip.
>
> I understand that there are chips that can only be rendered into
> using DMA or indirect accesses, that's a very real and tough problem
> to fix. There is also the issue of making sure the graphics card
> accelerator is not rendering anything (ie. it's pipeline FIFO has
> emptied) when we try to render a panic message.

I'm working on an approach that will teach the DRM layer about 
modesetting, which should address all the problems above, and also 
allow flexible uses like multihead and (I hope, though this is far 
fetched) things like a separate head for a kernel level debugger.

As for what happens at panic time, if the kernel knows how to modeset we 
can do whatever we want:  conservatively clear an appropriate scanout 
buffer and render our panic there, switch into a better mode to dump 
the panic if we think that's possible, or just hang without any output 
like we do today.

Kernel based modesetting should get us a lot of things:
  o robust suspend/resume support
  o some more independence from X for complex gfx setups
  o a good mode at early boot time
and several others I'm leaving out at the moment.  On the downside, the 
modesetting layer will be a chunk of new code, and require enhanced 
chip specific mode setting code to be added to the drm/fb drivers.

Jesse

Re: BSOD

[David Miller]

From: Jesse Barnes <jesse.barnes@intel.com>
Date: Mon, 19 Mar 2007 12:54:36 -0700

> Kernel based modesetting should get us a lot of things:

But for panics you're ignoring what Peter and I are saying.

Mode setting is complex and it is not going to work exactly when you
need the kernel crash message the most.

After debugging the kernel for 10+ years I can tell you one thing, for
a bad crash what's going to happen is you'll get the printk but that's
about all that will work at that point, and the kernel is going to
hang next.  Sometimes you won't get the whole panic message, just
the beginning, even with the most simplistic printk implementation.

You will not, I repeat, will not be able to mode switch or anything
non-trivial like that when the kernel is in this state.

Mode switching on panic, just say no. :-)

Re: BSOD

[Jesse Barnes]

On Monday, March 19, 2007 1:05 pm David Miller wrote:
> From: Jesse Barnes <jesse.barnes@intel.com>
> Date: Mon, 19 Mar 2007 12:54:36 -0700
>
> > Kernel based modesetting should get us a lot of things:
>
> But for panics you're ignoring what Peter and I are saying.
>
> Mode setting is complex and it is not going to work exactly when you
> need the kernel crash message the most.
>
> After debugging the kernel for 10+ years I can tell you one thing,
> for a bad crash what's going to happen is you'll get the printk but
> that's about all that will work at that point, and the kernel is
> going to hang next.  Sometimes you won't get the whole panic message,
> just the beginning, even with the most simplistic printk
> implementation.
>
> You will not, I repeat, will not be able to mode switch or anything
> non-trivial like that when the kernel is in this state.
>
> Mode switching on panic, just say no. :-)

You must have missed this part:

"As for what happens at panic time, if the kernel knows how to modeset 
we can do whatever we want:  conservatively clear an appropriate 
scanout buffer and render our panic there, switch into a better mode to 
dump the panic if we think that's possible, or just hang without any 
output like we do today."

Where "an appropriate" might mean "currently active" which would give us 
what you and Peter are saying.  The point is, with the modesetting code 
in the kernel, we'll actually *have* all the information you outlined 
in your previous mail so we'll have a chance to dtrt when the panic 
occurs (which is to tell the user about it).

So don't worry, I'm not ignoring that point at all, doing much of 
anything after panic/oops is a crapshoot. :)

Jesse

Re: BSOD

[Jim Gettys]

I agree with David and Jessie.

All the kernel needs to know for oopses is frame buffer depth, start,
stride, and how to get the GPU to "stop" (or it may very well overwrite
the screen).  Trying to get back to a default mode setting first in the
middle of oopsing is very unlikely to succeed.

The time you want mode switching (or lack othereof) is at suspend/resume
time, not at oopses.

This presumes the frame buffer is accessible in the address space of the
kernel.  There have been display devices where this is not true; but not
many.
                               - Jim




On Mon, 2007-03-19 at 13:05 -0700, David Miller wrote:
> From: Jesse Barnes <jesse.barnes@intel.com>
> Date: Mon, 19 Mar 2007 12:54:36 -0700
> 
> > Kernel based modesetting should get us a lot of things:
> 
> But for panics you're ignoring what Peter and I are saying.
> 
> Mode setting is complex and it is not going to work exactly when you
> need the kernel crash message the most.
> 
> After debugging the kernel for 10+ years I can tell you one thing, for
> a bad crash what's going to happen is you'll get the printk but that's
> about all that will work at that point, and the kernel is going to
> hang next.  Sometimes you won't get the whole panic message, just
> the beginning, even with the most simplistic printk implementation.
> 
> You will not, I repeat, will not be able to mode switch or anything
> non-trivial like that when the kernel is in this state.
> 
> Mode switching on panic, just say no. :-)
> 
-- 
Jim Gettys
One Laptop Per Child

Re: BSOD

[Paul Mackerras]

David Miller writes:

> Mode setting is complex and it is not going to work exactly when you
> need the kernel crash message the most.

It's a matter of writing maybe a dozen MMIO registers on the ATI
chips, for instance, with some delays.  Provided we have interrupts
disabled and udelay still works, there's not a lot of the kernel that
we need to rely on to do that.

> After debugging the kernel for 10+ years I can tell you one thing, for
> a bad crash what's going to happen is you'll get the printk but that's
> about all that will work at that point, and the kernel is going to
> hang next.  Sometimes you won't get the whole panic message, just
> the beginning, even with the most simplistic printk implementation.
> 
> You will not, I repeat, will not be able to mode switch or anything
> non-trivial like that when the kernel is in this state.
> 
> Mode switching on panic, just say no. :-)

Anything is better than nothing.  At the moment we get nothing if you
are in X when the panic occurs, even for the nicest, most well-behaved
panics. :)  If we can change that to getting something sometimes,
that's a win.

Paul.

Re: BSOD

[Jim Gettys]

On Tue, 2007-03-20 at 20:19 +1100, Paul Mackerras wrote:

> Anything is better than nothing.  At the moment we get nothing if you
> are in X when the panic occurs, even for the nicest, most well-behaved
> panics. :)  If we can change that to getting something sometimes,
> that's a win.

Treating the display as a frame buffer if at all possible is more likely
to work than anything else.  All the kernel needs to know is beginning
address, stride (# bytes/line; not necessarily the same as the number of
pixels on a row), number of rows, and depth of the display.  Thereafter,
it's just a SMOP as they say (and the sometimes maligned fbdev driver of
course already has all this code, and usually oops messages do ok on
fbdev).  

The other interesting headache that comes up sometimes is when the oops
message is more than a screen-full long.

One may also need to reset lookup tables to some sane value, and halt
the GPU, and maybe worry about video overlays.
                                 - Jim


-- 
Jim Gettys
One Laptop Per Child

Re: [linux-pm] [2/6] 2.6.21-rc2: known regressions

[Bill Davidsen]

Jim Gettys wrote:
> On Sun, 2007-03-18 at 17:07 +0100, Ingo Molnar wrote:
>> * Pavel Machek <pavel@ucw.cz> wrote:
>>
>>>> Some day we may have modesetting support in the kernel for some 
>>>> graphics hw, right now it's pretty damn spotty.
>>> Yep, that's the way to go.
>> hey, i wildly supported this approach ever since 1996, when GGI came up
>> :-/
>>
> 
> So wildly you wrote tons of code.... ;-).
> 
> More seriously, at the time, XFree86 would have spat in your face for
> any such thing.  Thankfully, times are changing.
> 
> Also more seriously, a somewhat hybrid approach is in order for mode
> setting: simple mode setting isn't much code and is required for sane
> behavior on crash (it is nice to get oopses onto a screen); but the full
> blown mode setting/configuration problem is so large that on some
> hardware, it is likely left best left to a helper process (not the X
> server).
> 
> Also key to get sane behavior out of the scheduler is to get the X
> server to yield (sleep in the kernel) rather than busy waiting when the
> GPU is busy; a standardized interface for this for both fbdev and dri is
> in order.  Right now, X is a misbehaving compute bound process rather
> than the properly interactive process it can/should/will be, releasing
> the CPU whenever the hardware is busy. Needless to say, this wastes
> cycles and hurts interactivity with just about any scheduler you can
> devise. It isn't as if this is hard; on UNIX systems we did it in 1984
> or thereabouts.

What you say sounds good, assuming that the cost of a sleep is less than 
the cost of the busy wait. But this may be hardware, the waits may be 
very small and frequent, and if it's hitting a small hardware window 
like retrace, delays in response will cause the time period to be missed 
completely. This probably less critical with very smart cards, many of 
us don't run them.
> 
> Of course, in 1996, XFree86 would have ignored any such interfaces, in
> its insane quest for operating system independent user space drivers
> requiring no standard kernel interfaces.... (it is the second part of
> this where the true insanity lay).
>                                   - Jim
> 


-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

Re: [linux-pm] [2/6] 2.6.21-rc2: known regressions

[Bill Davidsen]

Jim Gettys wrote:
> On Sun, 2007-03-18 at 17:07 +0100, Ingo Molnar wrote:
>> * Pavel Machek <pavel@ucw.cz> wrote:
>>
>>>> Some day we may have modesetting support in the kernel for some 
>>>> graphics hw, right now it's pretty damn spotty.
>>> Yep, that's the way to go.
>> hey, i wildly supported this approach ever since 1996, when GGI came up
>> :-/
>>
> 
> So wildly you wrote tons of code.... ;-).
> 
> More seriously, at the time, XFree86 would have spat in your face for
> any such thing.  Thankfully, times are changing.
> 
> Also more seriously, a somewhat hybrid approach is in order for mode
> setting: simple mode setting isn't much code and is required for sane
> behavior on crash (it is nice to get oopses onto a screen); but the full
> blown mode setting/configuration problem is so large that on some
> hardware, it is likely left best left to a helper process (not the X
> server).
> 
> Also key to get sane behavior out of the scheduler is to get the X
> server to yield (sleep in the kernel) rather than busy waiting when the
> GPU is busy; a standardized interface for this for both fbdev and dri is
> in order.  Right now, X is a misbehaving compute bound process rather
> than the properly interactive process it can/should/will be, releasing
> the CPU whenever the hardware is busy. Needless to say, this wastes
> cycles and hurts interactivity with just about any scheduler you can
> devise. It isn't as if this is hard; on UNIX systems we did it in 1984
> or thereabouts.

What you say sounds good, assuming that the cost of a sleep is less than 
the cost of the busy wait. But this may be hardware, the waits may be 
very small and frequent, and if it's hitting a small hardware window 
like retrace, delays in response will cause the time period to be missed 
completely. This probably less critical with very smart cards, many of 
us don't run them.
> 
> Of course, in 1996, XFree86 would have ignored any such interfaces, in
> its insane quest for operating system independent user space drivers
> requiring no standard kernel interfaces.... (it is the second part of
> this where the true insanity lay).
>                                   - Jim
> 


-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

Re: [linux-pm] [2/6] 2.6.21-rc2: known regressions

[Jim Gettys]

On Mon, 2007-03-19 at 16:33 -0400, Bill Davidsen wrote:

> 
> What you say sounds good, assuming that the cost of a sleep is less than 
> the cost of the busy wait. But this may be hardware, the waits may be 
> very small and frequent, and if it's hitting a small hardware window 
> like retrace, delays in response will cause the time period to be missed 
> completely. This probably less critical with very smart cards, many of 
> us don't run them.
> > 

Actually, various strategies involving short busy waiting, or looking at
DMA address registers before sleeping were commonplace.  But a
syscall/sleep/wakeup is/was pretty fast.  If you have an operation
blitting the screen (e.g. scrolling), it takes a bit of time for the GPU
to execute the command.  I see this right now on OLPC, where a wonderful
music application needs to scroll (most of) the screen left),
periodically, and we're losing samples sometimes at those operation.

Remember also, that being nice to everyone else by sleeping, there are
more cycles to go around, and the scheduler can nicely boost the X
server's priority as it will for "interactive" processes that are being
cooperative.
                                - Jim

-- 
Jim Gettys
One Laptop Per Child

Re: [linux-pm] [2/6] 2.6.21-rc2: known regressions

[Bill Davidsen]

Jim Gettys wrote:
> On Mon, 2007-03-19 at 16:33 -0400, Bill Davidsen wrote:
>
>   
>> What you say sounds good, assuming that the cost of a sleep is less than 
>> the cost of the busy wait. But this may be hardware, the waits may be 
>> very small and frequent, and if it's hitting a small hardware window 
>> like retrace, delays in response will cause the time period to be missed 
>> completely. This probably less critical with very smart cards, many of 
>> us don't run them.
>>     
>
> Actually, various strategies involving short busy waiting, or looking at
> DMA address registers before sleeping were commonplace.  But a
> syscall/sleep/wakeup is/was pretty fast.  If you have an operation
> blitting the screen (e.g. scrolling), it takes a bit of time for the GPU
> to execute the command.  I see this right now on OLPC, where a wonderful
> music application needs to scroll (most of) the screen left),
> periodically, and we're losing samples sometimes at those operation.
>   
None of that conflicts with what I said, but what works on an LCD may 
not be appropriate for a CRT. With even moderate 1024x768@70 timing the 
horizontal retrace happens ~50k/sec, and that's not an appropriate 
syscall rate. I'm just pointing out that some things a video interface 
does with simple hardware involve lots of very small windows. Don't read 
that as "don't do it," just "be careful HOW you do it."
> Remember also, that being nice to everyone else by sleeping, there are
> more cycles to go around, and the scheduler can nicely boost the X
> server's priority as it will for "interactive" processes that are being
> cooperative.
I'm going to cautiously guess that the problem might be not "how much" 
but "how soon." That is, latency might be more important than giving the 
server a lot of CPU.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

Re: [2/6] 2.6.21-rc2: known regressions

[Johannes Stezenbach]

On Thu, Mar 08, 2007, Linus Torvalds wrote:
> On Fri, 9 Mar 2007, Ingo Molnar wrote:
> > 
> > disabling the following radeonfb options in the .config made resume work 
> > again:
> 
> In general, don't even *try* to use radeonfb for suspend/resume.
> 
> I don't think it has ever worked, except on some very rare laptops 
> (largely PPC Macs) where people had enough information to set up the 
> PLL's.
> 
> I don't think the other framebuffer drivers are much better.
> 
> You're better off using the VGA console, and lettign X re-initialize the 
> graphics device. That generally at least has a reasonably good chance of 
> working.
> 
> Re-initializing graphics modes really is very hard. You can try with the 
> BIOS video hack (I forget the kernel command line to turn it on), but we 
> really do end up depending on X doing it better.

acpi_sleep=s3_bios has always worked for me on my ThinkPad T42p.

Even if one doesn't use the fb console at all, radeonfb apparently
is still required on some ThinkPad models to work around BIOS bugs:

http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off


Johannes

Re: [2/6] 2.6.21-rc2: known regressions

[Johannes Stezenbach]

On Thu, Mar 08, 2007, Linus Torvalds wrote:
> On Fri, 9 Mar 2007, Ingo Molnar wrote:
> > 
> > disabling the following radeonfb options in the .config made resume work 
> > again:
> 
> In general, don't even *try* to use radeonfb for suspend/resume.
> 
> I don't think it has ever worked, except on some very rare laptops 
> (largely PPC Macs) where people had enough information to set up the 
> PLL's.
> 
> I don't think the other framebuffer drivers are much better.
> 
> You're better off using the VGA console, and lettign X re-initialize the 
> graphics device. That generally at least has a reasonably good chance of 
> working.
> 
> Re-initializing graphics modes really is very hard. You can try with the 
> BIOS video hack (I forget the kernel command line to turn it on), but we 
> really do end up depending on X doing it better.

acpi_sleep=s3_bios has always worked for me on my ThinkPad T42p.

Even if one doesn't use the fb console at all, radeonfb apparently
is still required on some ThinkPad models to work around BIOS bugs:

http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off


Johannes

Re: [2/6] 2.6.21-rc2: known regressions

[Pavel Machek]

Hi!

> > You're better off using the VGA console, and lettign X re-initialize the 
> > graphics device. That generally at least has a reasonably good chance of 
> > working.
> > 
> > Re-initializing graphics modes really is very hard. You can try with the 
> > BIOS video hack (I forget the kernel command line to turn it on), but we 
> > really do end up depending on X doing it better.
> 
> acpi_sleep=s3_bios has always worked for me on my ThinkPad T42p.
> 
> Even if one doesn't use the fb console at all, radeonfb apparently
> is still required on some ThinkPad models to work around BIOS bugs:
> 
> http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off


s2ram should be able to work around this, it has parts from
radeontool. (suspend.sf.net).


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [2/6] 2.6.21-rc2: known regressions

[Pavel Machek]

Hi!

> > You're better off using the VGA console, and lettign X re-initialize the 
> > graphics device. That generally at least has a reasonably good chance of 
> > working.
> > 
> > Re-initializing graphics modes really is very hard. You can try with the 
> > BIOS video hack (I forget the kernel command line to turn it on), but we 
> > really do end up depending on X doing it better.
> 
> acpi_sleep=s3_bios has always worked for me on my ThinkPad T42p.
> 
> Even if one doesn't use the fb console at all, radeonfb apparently
> is still required on some ThinkPad models to work around BIOS bugs:
> 
> http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off


s2ram should be able to work around this, it has parts from
radeontool. (suspend.sf.net).


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Pavel Machek <pavel@suse.cz> wrote:

> > Even if one doesn't use the fb console at all, radeonfb apparently 
> > is still required on some ThinkPad models to work around BIOS bugs:
> > 
> > http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
> 
> 
> s2ram should be able to work around this, it has parts from 
> radeontool. (suspend.sf.net).

i'm wondering, do you have any idea how Windows handles the 
suspend/resume quirks problem area? Do they "curse BIOS vendors and 
maintain a large DB of DMI-driven exceptions", or do they perhaps have 
some fundamentally better approach than us? If it's the former, then we 
might as well try to bring more automatism (and more of your database) 
into the kernel itself.

btw., the s2ram database seems quite a bit spotty:

 $ ./s2ram -n
 Machine is unknown.
 This machine can be identified by:
     sys_vendor   = "System manufacturer"
     sys_product  = "System Product Name"
     sys_version  = "System Version"
     bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"

 $ ./s2ram -n
 Machine is unknown.
 This machine can be identified by:
    sys_vendor   = "Hewlett-Packard "
    sys_product  = "compaq nx9030 (PG630ET#ABD)       "
    sys_version  = "Rev 1           "
    bios_version = "F.15    "
 See http://en.opensuse.org/S2ram for details.

even at the link above i didnt find any clear algorithm about how to 
extend the quirks-list and the white-list - while i expect that most 
people experience what i did: that s2ram doesnt know their boxes. 
(otherwise they would not visit that URL at all i suspect)

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Pavel Machek <pavel@suse.cz> wrote:

> > Even if one doesn't use the fb console at all, radeonfb apparently 
> > is still required on some ThinkPad models to work around BIOS bugs:
> > 
> > http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
> 
> 
> s2ram should be able to work around this, it has parts from 
> radeontool. (suspend.sf.net).

i'm wondering, do you have any idea how Windows handles the 
suspend/resume quirks problem area? Do they "curse BIOS vendors and 
maintain a large DB of DMI-driven exceptions", or do they perhaps have 
some fundamentally better approach than us? If it's the former, then we 
might as well try to bring more automatism (and more of your database) 
into the kernel itself.

btw., the s2ram database seems quite a bit spotty:

 $ ./s2ram -n
 Machine is unknown.
 This machine can be identified by:
     sys_vendor   = "System manufacturer"
     sys_product  = "System Product Name"
     sys_version  = "System Version"
     bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"

 $ ./s2ram -n
 Machine is unknown.
 This machine can be identified by:
    sys_vendor   = "Hewlett-Packard "
    sys_product  = "compaq nx9030 (PG630ET#ABD)       "
    sys_version  = "Rev 1           "
    bios_version = "F.15    "
 See http://en.opensuse.org/S2ram for details.

even at the link above i didnt find any clear algorithm about how to 
extend the quirks-list and the white-list - while i expect that most 
people experience what i did: that s2ram doesnt know their boxes. 
(otherwise they would not visit that URL at all i suspect)

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Stefan Seyfried]

On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
> 
> * Pavel Machek <pavel@suse.cz> wrote:
> > s2ram should be able to work around this, it has parts from 
> > radeontool. (suspend.sf.net).
> 
> i'm wondering, do you have any idea how Windows handles the 
> suspend/resume quirks problem area? Do they "curse BIOS vendors and 
> maintain a large DB of DMI-driven exceptions", or do they perhaps have 
> some fundamentally better approach than us? If it's the former, then we 
> might as well try to bring more automatism (and more of your database) 
> into the kernel itself.

I think that in windows, you simply install the "HP nx$FOOBAR intel graphics
driver" on a nx$FOOBAR machine, and the "ASUS $FOOBAR ATI graphics driver"
on an ASUS $FOOBAR machine etc. Those drivers are mostly stock intel/ATI/
whoever drivers, but with the little bit of extra knowledge on how to wake
up the graphics chip.

And there is no console mode in Windows. If you restrict yourself to
"it works from X", many machines do not need workarounds.
 
> btw., the s2ram database seems quite a bit spotty:
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>      sys_vendor   = "System manufacturer"
>      sys_product  = "System Product Name"
>      sys_version  = "System Version"
>      bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>     sys_vendor   = "Hewlett-Packard "
>     sys_product  = "compaq nx9030 (PG630ET#ABD)       "
>     sys_version  = "Rev 1           "
>     bios_version = "F.15    "
>  See http://en.opensuse.org/S2ram for details.
> 
> even at the link above i didnt find any clear algorithm about how to 
> extend the quirks-list and the white-list - while i expect that most 
> people experience what i did: that s2ram doesnt know their boxes. 
> (otherwise they would not visit that URL at all i suspect)

Ok. To be honest, you are the first reporter that seems to have read the
documentation above, but not understood what to do.

So i'll put it into even simpler steps:

 - get the current version of s2ram
 - boot your system with init=/bin/bash, mount /proc and /sys
 - try the s2ram options in the combinations listed on the above page
 - as soon as you find an option that works, please retry it from a
   full booted system (including X)
 - if it still works, please report the options used and the output of
   "s2ram -n" to the suspend-devel mailinglist.

i might consider reworking the documentation if there are more reports
about problems with the procedure.
-- 
Stefan Seyfried

"Any ideas, John?"
"Well, surrounding them's out." 

Re: [2/6] 2.6.21-rc2: known regressions

[Stefan Seyfried]

On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
> 
> * Pavel Machek <pavel@suse.cz> wrote:
> > s2ram should be able to work around this, it has parts from 
> > radeontool. (suspend.sf.net).
> 
> i'm wondering, do you have any idea how Windows handles the 
> suspend/resume quirks problem area? Do they "curse BIOS vendors and 
> maintain a large DB of DMI-driven exceptions", or do they perhaps have 
> some fundamentally better approach than us? If it's the former, then we 
> might as well try to bring more automatism (and more of your database) 
> into the kernel itself.

I think that in windows, you simply install the "HP nx$FOOBAR intel graphics
driver" on a nx$FOOBAR machine, and the "ASUS $FOOBAR ATI graphics driver"
on an ASUS $FOOBAR machine etc. Those drivers are mostly stock intel/ATI/
whoever drivers, but with the little bit of extra knowledge on how to wake
up the graphics chip.

And there is no console mode in Windows. If you restrict yourself to
"it works from X", many machines do not need workarounds.
 
> btw., the s2ram database seems quite a bit spotty:
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>      sys_vendor   = "System manufacturer"
>      sys_product  = "System Product Name"
>      sys_version  = "System Version"
>      bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>     sys_vendor   = "Hewlett-Packard "
>     sys_product  = "compaq nx9030 (PG630ET#ABD)       "
>     sys_version  = "Rev 1           "
>     bios_version = "F.15    "
>  See http://en.opensuse.org/S2ram for details.
> 
> even at the link above i didnt find any clear algorithm about how to 
> extend the quirks-list and the white-list - while i expect that most 
> people experience what i did: that s2ram doesnt know their boxes. 
> (otherwise they would not visit that URL at all i suspect)

Ok. To be honest, you are the first reporter that seems to have read the
documentation above, but not understood what to do.

So i'll put it into even simpler steps:

 - get the current version of s2ram
 - boot your system with init=/bin/bash, mount /proc and /sys
 - try the s2ram options in the combinations listed on the above page
 - as soon as you find an option that works, please retry it from a
   full booted system (including X)
 - if it still works, please report the options used and the output of
   "s2ram -n" to the suspend-devel mailinglist.

i might consider reworking the documentation if there are more reports
about problems with the procedure.
-- 
Stefan Seyfried

"Any ideas, John?"
"Well, surrounding them's out." 

Re: [2/6] 2.6.21-rc2: known regressions

[Johannes Stezenbach]

On Sat, Mar 10, 2007 at 12:43:01PM +0100, Stefan Seyfried wrote:
> On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
> > 
> > i'm wondering, do you have any idea how Windows handles the 
> > suspend/resume quirks problem area? Do they "curse BIOS vendors and 
> > maintain a large DB of DMI-driven exceptions", or do they perhaps have 
> > some fundamentally better approach than us? If it's the former, then we 
> > might as well try to bring more automatism (and more of your database) 
> > into the kernel itself.
> 
> I think that in windows, you simply install the "HP nx$FOOBAR intel graphics
> driver" on a nx$FOOBAR machine, and the "ASUS $FOOBAR ATI graphics driver"
> on an ASUS $FOOBAR machine etc. Those drivers are mostly stock intel/ATI/
> whoever drivers, but with the little bit of extra knowledge on how to wake
> up the graphics chip.

That's also what the thinkwiki page suggests. It says:

"Affected Operating Systems:
  * Linux, all flavours.
  * Windows, for some models as well (only when using non-IBM drivers).
  * FreeBSD (on the A22M)"


Johannes

Re: [2/6] 2.6.21-rc2: known regressions

[Johannes Stezenbach]

On Sat, Mar 10, 2007 at 12:43:01PM +0100, Stefan Seyfried wrote:
> On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
> > 
> > i'm wondering, do you have any idea how Windows handles the 
> > suspend/resume quirks problem area? Do they "curse BIOS vendors and 
> > maintain a large DB of DMI-driven exceptions", or do they perhaps have 
> > some fundamentally better approach than us? If it's the former, then we 
> > might as well try to bring more automatism (and more of your database) 
> > into the kernel itself.
> 
> I think that in windows, you simply install the "HP nx$FOOBAR intel graphics
> driver" on a nx$FOOBAR machine, and the "ASUS $FOOBAR ATI graphics driver"
> on an ASUS $FOOBAR machine etc. Those drivers are mostly stock intel/ATI/
> whoever drivers, but with the little bit of extra knowledge on how to wake
> up the graphics chip.

That's also what the thinkwiki page suggests. It says:

"Affected Operating Systems:
  * Linux, all flavours.
  * Windows, for some models as well (only when using non-IBM drivers).
  * FreeBSD (on the A22M)"


Johannes

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Stefan Seyfried <seife@suse.de> wrote:

> > btw., the s2ram database seems quite a bit spotty:
> > 
> >  $ ./s2ram -n
> >  Machine is unknown.
> >  This machine can be identified by:
> >      sys_vendor   = "System manufacturer"
> >      sys_product  = "System Product Name"
> >      sys_version  = "System Version"
> >      bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
> > 
> >  $ ./s2ram -n
> >  Machine is unknown.
> >  This machine can be identified by:
> >     sys_vendor   = "Hewlett-Packard "
> >     sys_product  = "compaq nx9030 (PG630ET#ABD)       "
> >     sys_version  = "Rev 1           "
> >     bios_version = "F.15    "
> >  See http://en.opensuse.org/S2ram for details.
> > 
> > even at the link above i didnt find any clear algorithm about how to 
> > extend the quirks-list and the white-list - while i expect that most 
> > people experience what i did: that s2ram doesnt know their boxes. 
> > (otherwise they would not visit that URL at all i suspect)
> 
> Ok. To be honest, you are the first reporter that seems to have read 
> the documentation above, but not understood what to do.

thanks for the compliment ;-) _I_ very much know what to do (i mailed 
the right person after all ;), but i dont really count and on the 6 
systems i tried s2ram said on 5 that it's 'unknown', i assumed it could 
possibly be due to the visible lack of clear instructions on that 
webpage ;-)

> i might consider reworking the documentation if there are more reports 
> about problems with the procedure.

Probably tweaking the webpage doesnt help because people dont get there 
- as the results plainly show it. Maybe some more automation would be 
useful too, a tool that detects failed resume and tries all those 
options that makes sense on that box or something? It's not like that 
people dont _try_ suspend/resume on Linux, it's just that they find it 
doesnt work and there is no clear mortal-usable (end-user-) way of 
fixing it and submitting the result of that fixing.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Stefan Seyfried <seife@suse.de> wrote:

> > btw., the s2ram database seems quite a bit spotty:
> > 
> >  $ ./s2ram -n
> >  Machine is unknown.
> >  This machine can be identified by:
> >      sys_vendor   = "System manufacturer"
> >      sys_product  = "System Product Name"
> >      sys_version  = "System Version"
> >      bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
> > 
> >  $ ./s2ram -n
> >  Machine is unknown.
> >  This machine can be identified by:
> >     sys_vendor   = "Hewlett-Packard "
> >     sys_product  = "compaq nx9030 (PG630ET#ABD)       "
> >     sys_version  = "Rev 1           "
> >     bios_version = "F.15    "
> >  See http://en.opensuse.org/S2ram for details.
> > 
> > even at the link above i didnt find any clear algorithm about how to 
> > extend the quirks-list and the white-list - while i expect that most 
> > people experience what i did: that s2ram doesnt know their boxes. 
> > (otherwise they would not visit that URL at all i suspect)
> 
> Ok. To be honest, you are the first reporter that seems to have read 
> the documentation above, but not understood what to do.

thanks for the compliment ;-) _I_ very much know what to do (i mailed 
the right person after all ;), but i dont really count and on the 6 
systems i tried s2ram said on 5 that it's 'unknown', i assumed it could 
possibly be due to the visible lack of clear instructions on that 
webpage ;-)

> i might consider reworking the documentation if there are more reports 
> about problems with the procedure.

Probably tweaking the webpage doesnt help because people dont get there 
- as the results plainly show it. Maybe some more automation would be 
useful too, a tool that detects failed resume and tries all those 
options that makes sense on that box or something? It's not like that 
people dont _try_ suspend/resume on Linux, it's just that they find it 
doesnt work and there is no clear mortal-usable (end-user-) way of 
fixing it and submitting the result of that fixing.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Pavel Machek]

Hi!

> > Ok. To be honest, you are the first reporter that seems to have read 
> > the documentation above, but not understood what to do.
> 
> thanks for the compliment ;-) _I_ very much know what to do (i mailed 
> the right person after all ;), but i dont really count and on the 6 

(Can we get the whitelist entries?)

> > i might consider reworking the documentation if there are more reports 
> > about problems with the procedure.
> 
> Probably tweaking the webpage doesnt help because people dont get there 
> - as the results plainly show it. Maybe some more automation would be 
> useful too, a tool that detects failed resume and tries all those 
> options that makes sense on that box or something? It's not like
> that 

Unfortunately, these tend to crash the box when you pass wrong
options, and I do not see easy way to test "can user see whats on
display" automatically.

Feel free to send patches, but I do not think it is easy/possible.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [2/6] 2.6.21-rc2: known regressions

[Pavel Machek]

Hi!

> > Ok. To be honest, you are the first reporter that seems to have read 
> > the documentation above, but not understood what to do.
> 
> thanks for the compliment ;-) _I_ very much know what to do (i mailed 
> the right person after all ;), but i dont really count and on the 6 

(Can we get the whitelist entries?)

> > i might consider reworking the documentation if there are more reports 
> > about problems with the procedure.
> 
> Probably tweaking the webpage doesnt help because people dont get there 
> - as the results plainly show it. Maybe some more automation would be 
> useful too, a tool that detects failed resume and tries all those 
> options that makes sense on that box or something? It's not like
> that 

Unfortunately, these tend to crash the box when you pass wrong
options, and I do not see easy way to test "can user see whats on
display" automatically.

Feel free to send patches, but I do not think it is easy/possible.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Pavel Machek <pavel@suse.cz> wrote:

> > Probably tweaking the webpage doesnt help because people dont get 
> > there - as the results plainly show it. Maybe some more automation 
> > would be useful too, a tool that detects failed resume and tries all 
> > those options that makes sense on that box or something? It's not 
> > like that
> 
> Unfortunately, these tend to crash the box when you pass wrong 
> options, and I do not see easy way to test "can user see whats on 
> display" automatically.

you could perhaps try what X's modesetting utility does: display a 
dialog box that times out if it does not get clicked on, and reboot if 
it did not get clicked on. Likewise, detect upon the next bootup that a 
suspend-test was in progress (and didnt get back via normal resume), via 
some temporary file. That way both the 'did not resume and i had to 
power-cycle' and the 'resume did not restore my X' problems can be 
handled.

Finally, when the correct options have been established (worse-case with 
a small number of reboots and "yes, indeed the resume did not work fine" 
clicks done upon bootup by the user), automatically fill in a webform in 
firefox and ask the user to do a single click to submit that form.

techniques like that have more chance i think to get Linux 
suspend/resume anywhere near to working. The current 'rely on the 
developer' technique apparently does not work.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Pavel Machek <pavel@suse.cz> wrote:

> > Probably tweaking the webpage doesnt help because people dont get 
> > there - as the results plainly show it. Maybe some more automation 
> > would be useful too, a tool that detects failed resume and tries all 
> > those options that makes sense on that box or something? It's not 
> > like that
> 
> Unfortunately, these tend to crash the box when you pass wrong 
> options, and I do not see easy way to test "can user see whats on 
> display" automatically.

you could perhaps try what X's modesetting utility does: display a 
dialog box that times out if it does not get clicked on, and reboot if 
it did not get clicked on. Likewise, detect upon the next bootup that a 
suspend-test was in progress (and didnt get back via normal resume), via 
some temporary file. That way both the 'did not resume and i had to 
power-cycle' and the 'resume did not restore my X' problems can be 
handled.

Finally, when the correct options have been established (worse-case with 
a small number of reboots and "yes, indeed the resume did not work fine" 
clicks done upon bootup by the user), automatically fill in a webform in 
firefox and ask the user to do a single click to submit that form.

techniques like that have more chance i think to get Linux 
suspend/resume anywhere near to working. The current 'rely on the 
developer' technique apparently does not work.

	Ingo

Re: [2/6] 2.6.21-rc2: known regressions

[Stefan Seyfried]

On Sun, Mar 11, 2007 at 09:20:02AM +0100, Ingo Molnar wrote:
> 
> * Pavel Machek <pavel@suse.cz> wrote:
> > Unfortunately, these tend to crash the box when you pass wrong 
> > options, and I do not see easy way to test "can user see whats on 
> > display" automatically.
> 
> you could perhaps try what X's modesetting utility does: display a 
> dialog box that times out if it does not get clicked on, and reboot if 
> it did not get clicked on. Likewise, detect upon the next bootup that a 
> suspend-test was in progress (and didnt get back via normal resume), via 
> some temporary file. That way both the 'did not resume and i had to 
> power-cycle' and the 'resume did not restore my X' problems can be 
> handled.
> 
> Finally, when the correct options have been established (worse-case with 
> a small number of reboots and "yes, indeed the resume did not work fine" 
> clicks done upon bootup by the user), automatically fill in a webform in 
> firefox and ask the user to do a single click to submit that form.

There is ongoing work to make something like this happen, but it will
take some time (very probably the whitelist will end up in a HAL fdi-file
which gives the additional advantage that interested vendors can supply a
linux-"driver" for their notebooks which makes suspend "just work" (the
"driver" simply being a .fdi-file that lists the workaround for this
particular machine)

> techniques like that have more chance i think to get Linux 
> suspend/resume anywhere near to working. The current 'rely on the 
> developer' technique apparently does not work.

It is not too bad actually, i seem to be getting lots of whitelist
entries from people that are first time shell users, and i usually
walk them through the process in just one or two mails. But yes, it
does not scale well ;-)

I was already thinking about some more sophisticated "wildcard" matching,
something like "if it is a HP and it has an ATI gfx chip, and we do
not have an exact match, then do VBE_POST|VBE_MODE" or similar, which
would probably get many machines working fine (it turns out that almost
all new machines from a vendor with similar hardware need similar
workarounds, but for example the hp's with ATI need different quirks
than the hp's with intel. Only thinkpads seem to almost universally work
with s3_bios,s3_mode, with some x86_64 models being the exception).
Something like that should be pretty easy once the whitelist is kept
in HAL.
-- 
Stefan Seyfried

"Any ideas, John?"
"Well, surrounding them's out." 

Re: [2/6] 2.6.21-rc2: known regressions

[Stefan Seyfried]

On Sun, Mar 11, 2007 at 09:20:02AM +0100, Ingo Molnar wrote:
> 
> * Pavel Machek <pavel@suse.cz> wrote:
> > Unfortunately, these tend to crash the box when you pass wrong 
> > options, and I do not see easy way to test "can user see whats on 
> > display" automatically.
> 
> you could perhaps try what X's modesetting utility does: display a 
> dialog box that times out if it does not get clicked on, and reboot if 
> it did not get clicked on. Likewise, detect upon the next bootup that a 
> suspend-test was in progress (and didnt get back via normal resume), via 
> some temporary file. That way both the 'did not resume and i had to 
> power-cycle' and the 'resume did not restore my X' problems can be 
> handled.
> 
> Finally, when the correct options have been established (worse-case with 
> a small number of reboots and "yes, indeed the resume did not work fine" 
> clicks done upon bootup by the user), automatically fill in a webform in 
> firefox and ask the user to do a single click to submit that form.

There is ongoing work to make something like this happen, but it will
take some time (very probably the whitelist will end up in a HAL fdi-file
which gives the additional advantage that interested vendors can supply a
linux-"driver" for their notebooks which makes suspend "just work" (the
"driver" simply being a .fdi-file that lists the workaround for this
particular machine)

> techniques like that have more chance i think to get Linux 
> suspend/resume anywhere near to working. The current 'rely on the 
> developer' technique apparently does not work.

It is not too bad actually, i seem to be getting lots of whitelist
entries from people that are first time shell users, and i usually
walk them through the process in just one or two mails. But yes, it
does not scale well ;-)

I was already thinking about some more sophisticated "wildcard" matching,
something like "if it is a HP and it has an ATI gfx chip, and we do
not have an exact match, then do VBE_POST|VBE_MODE" or similar, which
would probably get many machines working fine (it turns out that almost
all new machines from a vendor with similar hardware need similar
workarounds, but for example the hp's with ATI need different quirks
than the hp's with intel. Only thinkpads seem to almost universally work
with s3_bios,s3_mode, with some x86_64 models being the exception).
Something like that should be pretty easy once the whitelist is kept
in HAL.
-- 
Stefan Seyfried

"Any ideas, John?"
"Well, surrounding them's out." 

s2ram (was Re: [2/6] 2.6.21-rc2: known regressions)

[Pavel Machek]

Hi!

> > > Even if one doesn't use the fb console at all, radeonfb apparently 
> > > is still required on some ThinkPad models to work around BIOS bugs:
> > > 
> > > http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
> > 
> > 
> > s2ram should be able to work around this, it has parts from 
> > radeontool. (suspend.sf.net).
> 
> i'm wondering, do you have any idea how Windows handles the 
> suspend/resume quirks problem area? Do they "curse BIOS vendors and 

Windows actually have (kernel) graphics drivers that know how to
resume the video. If you boot save mode, they go w/o graphics drivers,
and have similar problems to us.

> btw., the s2ram database seems quite a bit spotty:
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>      sys_vendor   = "System manufacturer"
>      sys_product  = "System Product Name"
>      sys_version  = "System Version"
>      bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>     sys_vendor   = "Hewlett-Packard "
>     sys_product  = "compaq nx9030 (PG630ET#ABD)       "
>     sys_version  = "Rev 1           "
>     bios_version = "F.15    "
>  See http://en.opensuse.org/S2ram for details.

Desktops are the problem; but that nx9030 should be reasonably easy to
add.

> even at the link above i didnt find any clear algorithm about how to 
> extend the quirks-list and the white-list - while i expect that most 
> people experience what i did: that s2ram doesnt know their boxes. 
> (otherwise they would not visit that URL at all i suspect)

Did you get options for s2ram that work on your systems? Mail them to
seife@suse.de, and he'll extend the whitelist ;-). In the meantime,
just use -f <whatever>
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

s2ram (was Re: [2/6] 2.6.21-rc2: known regressions)

[Pavel Machek]

Hi!

> > > Even if one doesn't use the fb console at all, radeonfb apparently 
> > > is still required on some ThinkPad models to work around BIOS bugs:
> > > 
> > > http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
> > 
> > 
> > s2ram should be able to work around this, it has parts from 
> > radeontool. (suspend.sf.net).
> 
> i'm wondering, do you have any idea how Windows handles the 
> suspend/resume quirks problem area? Do they "curse BIOS vendors and 

Windows actually have (kernel) graphics drivers that know how to
resume the video. If you boot save mode, they go w/o graphics drivers,
and have similar problems to us.

> btw., the s2ram database seems quite a bit spotty:
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>      sys_vendor   = "System manufacturer"
>      sys_product  = "System Product Name"
>      sys_version  = "System Version"
>      bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
> 
>  $ ./s2ram -n
>  Machine is unknown.
>  This machine can be identified by:
>     sys_vendor   = "Hewlett-Packard "
>     sys_product  = "compaq nx9030 (PG630ET#ABD)       "
>     sys_version  = "Rev 1           "
>     bios_version = "F.15    "
>  See http://en.opensuse.org/S2ram for details.

Desktops are the problem; but that nx9030 should be reasonably easy to
add.

> even at the link above i didnt find any clear algorithm about how to 
> extend the quirks-list and the white-list - while i expect that most 
> people experience what i did: that s2ram doesnt know their boxes. 
> (otherwise they would not visit that URL at all i suspect)

Did you get options for s2ram that work on your systems? Mail them to
seife@suse.de, and he'll extend the whitelist ;-). In the meantime,
just use -f <whatever>
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Linus Torvalds <torvalds@linux-foundation.org>:
> > 
> > Here's the status with -rc3: better, but still does not work as well as 2.6.20.
> 
> Ok. I think we mostly solved the irq-related stuff, but you might want to 
> check whether you have CONFIG_NOHZ on or off and whether that makes a 
> difference.

This testing was done without NO_HZ.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> > 2. First disk access after resume takes a couple of minutes
> >    (seemed instant with 2.6.20) during this time no new messages show on console
> 
> Yeah, there is some problem with SATA resume. It would be beautiful if the 
> people who actually see this could narrow it down with bisection. "It 
> works for me" is clearly the case for many people, but not all.

Problem is, there seem to be multiple problems some of which got
fixed between rc2 and rc3.
With rc2 I didn't get as far as getting to console.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> > 2. First disk access after resume takes a couple of minutes
> >    (seemed instant with 2.6.20) during this time no new messages show on console
> 
> Yeah, there is some problem with SATA resume. It would be beautiful if the 
> people who actually see this could narrow it down with bisection. "It 
> works for me" is clearly the case for many people, but not all.

Problem is, there seem to be multiple problems some of which got
fixed between rc2 and rc3.
With rc2 I didn't get as far as getting to console.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [2/6] 2.6.21-rc2: known regressions
> 
> 
> Michael,
> 
> * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
> 
> > > > 2. First disk access after resume takes a couple of minutes
> > > >    (seemed instant with 2.6.20) during this time no new messages show on console
> > > 
> > > Yeah, there is some problem with SATA resume. It would be beautiful if the 
> > > people who actually see this could narrow it down with bisection. "It 
> > > works for me" is clearly the case for many people, but not all.
> > 
> > Problem is, there seem to be multiple problems some of which got fixed 
> > between rc2 and rc3. With rc2 I didn't get as far as getting to 
> > console.
> 
> a quick ping: on your box that doesnt resume - if you can log in over 
> the network after resume (or somehow run shell commands), does 'date' 
> advance properly or not? (or do you not get that far to be able to 
> tell?)
> 
> 	Ingo

I just retested - 'date' does not advance after resume for me.
This is with NO_HZ *not* set.
Sorry it took so long.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Michael S. Tsirkin <mst@dev.mellanox.co.il>:
> Subject: Re: [2/6] 2.6.21-rc2: known regressions
> 
> > Quoting Ingo Molnar <mingo@elte.hu>:
> > Subject: Re: [2/6] 2.6.21-rc2: known regressions
> > 
> > 
> > Michael,
> > 
> > * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
> > 
> > > > > 2. First disk access after resume takes a couple of minutes
> > > > >    (seemed instant with 2.6.20) during this time no new messages show on console
> > > > 
> > > > Yeah, there is some problem with SATA resume. It would be beautiful if the 
> > > > people who actually see this could narrow it down with bisection. "It 
> > > > works for me" is clearly the case for many people, but not all.
> > > 
> > > Problem is, there seem to be multiple problems some of which got fixed 
> > > between rc2 and rc3. With rc2 I didn't get as far as getting to 
> > > console.
> > 
> > a quick ping: on your box that doesnt resume - if you can log in over 
> > the network after resume (or somehow run shell commands), does 'date' 
> > advance properly or not? (or do you not get that far to be able to 
> > tell?)
> > 
> > 	Ingo
> 
> I just retested - 'date' does not advance after resume for me.
> This is with NO_HZ *not* set.
> Sorry it took so long.

Update: just re-tested with 2.6.21-rc4, same behaviour: date
does not advance after resume from ram.

-- 
MST

Re: [2/6] 2.6.21-rc2: known regressions

[Thomas Gleixner]

On Sat, 2007-03-17 at 23:41 +0200, Michael S. Tsirkin wrote:
> > > a quick ping: on your box that doesnt resume - if you can log in over 
> > > the network after resume (or somehow run shell commands), does 'date' 
> > > advance properly or not? (or do you not get that far to be able to 
> > > tell?)
> > > 
> > > 	Ingo
> > 
> > I just retested - 'date' does not advance after resume for me.
> > This is with NO_HZ *not* set.
> > Sorry it took so long.
> 
> Update: just re-tested with 2.6.21-rc4, same behaviour: date
> does not advance after resume from ram.

Can you get a full dmesg from boot to resume out of the box ?

	tglx

Re: [2/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

> Quoting Thomas Gleixner <tglx@linutronix.de>:
> Subject: Re: [2/6] 2.6.21-rc2: known regressions
> 
> On Sat, 2007-03-17 at 23:41 +0200, Michael S. Tsirkin wrote:
> > > > a quick ping: on your box that doesnt resume - if you can log in over 
> > > > the network after resume (or somehow run shell commands), does 'date' 
> > > > advance properly or not? (or do you not get that far to be able to 
> > > > tell?)
> > > > 
> > > > 	Ingo
> > > 
> > > I just retested - 'date' does not advance after resume for me.
> > > This is with NO_HZ *not* set.
> > > Sorry it took so long.
> > 
> > Update: just re-tested with 2.6.21-rc4, same behaviour: date
> > does not advance after resume from ram.
> 
> Can you get a full dmesg from boot to resume out of the box ?
> 
> 	tglx

Here it is.
Symptoms:
1. after resume, takes up to 1 min to enable disk
2. date does not advance after resume

-- 
MST

[-- Attachment #2: bootlog2 --]
[-- Type: text/plain, Size: 97933 bytes --]

[    0.000000] Linux version 2.6.21-rc4-work (mst@mst-lt) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #5 SMP Wed Mar 21 18:13:10 IST 2007
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] sanitize start
[    0.000000] sanitize end
[    0.000000] copy_e820_map() start: 0000000000000000 size: 000000000009f000 end: 000000000009f000 type: 1
[    0.000000] copy_e820_map() type is E820_RAM
[    0.000000] copy_e820_map() start: 000000000009f000 size: 0000000000001000 end: 00000000000a0000 type: 2
[    0.000000] copy_e820_map() start: 00000000000d2000 size: 0000000000002000 end: 00000000000d4000 type: 2
[    0.000000] copy_e820_map() start: 00000000000dc000 size: 0000000000024000 end: 0000000000100000 type: 2
[    0.000000] copy_e820_map() start: 0000000000100000 size: 000000003f5e0000 end: 000000003f6e0000 type: 1
[    0.000000] copy_e820_map() type is E820_RAM
[    0.000000] copy_e820_map() start: 000000003f6e0000 size: 0000000000013000 end: 000000003f6f3000 type: 3
[    0.000000] copy_e820_map() start: 000000003f6f3000 size: 000000000000d000 end: 000000003f700000 type: 4
[    0.000000] copy_e820_map() start: 000000003f700000 size: 0000000000900000 end: 0000000040000000 type: 2
[    0.000000] copy_e820_map() start: 00000000f0000000 size: 0000000004000000 end: 00000000f4000000 type: 2
[    0.000000] copy_e820_map() start: 00000000fec00000 size: 0000000000010000 end: 00000000fec10000 type: 2
[    0.000000] copy_e820_map() start: 00000000fed00000 size: 0000000000000400 end: 00000000fed00400 type: 2
[    0.000000] copy_e820_map() start: 00000000fed14000 size: 0000000000006000 end: 00000000fed1a000 type: 2
[    0.000000] copy_e820_map() start: 00000000fed1c000 size: 0000000000074000 end: 00000000fed90000 type: 2
[    0.000000] copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2
[    0.000000] copy_e820_map() start: 00000000ff800000 size: 0000000000800000 end: 0000000100000000 type: 2
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[    0.000000]  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
[    0.000000]  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003f6e0000 (usable)
[    0.000000]  BIOS-e820: 000000003f6e0000 - 000000003f6f3000 (ACPI data)
[    0.000000]  BIOS-e820: 000000003f6f3000 - 000000003f700000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
[    0.000000]  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
[    0.000000]  BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
[    0.000000] Warning only 896MB will be used.
[    0.000000] Use a HIGHMEM enabled kernel.
[    0.000000] 896MB LOWMEM available.
[    0.000000] found SMP MP-table at 000f68e0
[    0.000000] Entering add_active_range(0, 0, 229376) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   229376
[    0.000000] On node 0 totalpages: 229376
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 1760 pages used for memmap
[    0.000000]   Normal zone: 223520 pages, LIFO batch:31
[    0.000000] DMI present.
[    0.000000] ACPI: RSDP 000F68A0, 0024 (r2 LENOVO)
[    0.000000] ACPI: XSDT 3F6E63A2, 0074 (r1 LENOVO TP-79        1051  LTP        0)
[    0.000000] ACPI: FACP 3F6E6500, 00F4 (r3 LENOVO TP-79        1051 LNVO        1)
[    0.000000] ACPI Warning (tbfadt-0420): Optional field "Gpe1Block" has zero address or length: 000000000000102C/0 [20070126]
[    0.000000] ACPI: DSDT 3F6E66E7, C6E2 (r1 LENOVO TP-79        1051 MSFT  100000E)
[    0.000000] ACPI: FACS 3F6F4000, 0040
[    0.000000] ACPI: SSDT 3F6E66B4, 0033 (r1 LENOVO TP-79        1051 MSFT  100000E)
[    0.000000] ACPI: ECDT 3F6F2DC9, 0052 (r1 LENOVO TP-79        1051 LNVO        1)
[    0.000000] ACPI: TCPA 3F6F2E1B, 0032 (r2 LENOVO TP-79        1051 LNVO        1)
[    0.000000] ACPI: APIC 3F6F2E4D, 0068 (r1 LENOVO TP-79        1051 LNVO        1)
[    0.000000] ACPI: MCFG 3F6F2EB5, 003E (r1 LENOVO TP-79        1051 LNVO        1)
[    0.000000] ACPI: HPET 3F6F2EF3, 0038 (r1 LENOVO TP-79        1051 LNVO        1)
[    0.000000] ACPI: BOOT 3F6F2FD8, 0028 (r1 LENOVO TP-79        1051  LTP        1)
[    0.000000] ACPI: SSDT 3F6E595D, 0507 (r1 LENOVO TP-79        1051 INTL 20050513)
[    0.000000] ACPI: SSDT 3F6E5785, 01D8 (r1 LENOVO TP-79        1051 INTL 20050513)
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:14 APIC version 20
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] Processor #1 6:14 APIC version 20
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:b0000000)
[    0.000000] Built 1 zonelists.  Total pages: 227584
[    0.000000] Kernel command line: root=/dev/sda3 ro splash
[    0.000000] mapped APIC to ffffd000 (fee00000)
[    0.000000] mapped IOAPIC to ffffc000 (fec00000)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 1828.761 MHz processor.
[   11.745696] Console: colour VGA+ 80x25
[   11.751844] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[   11.752430] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[   11.777663] Memory: 904220k/917504k available (2935k kernel code, 12876k reserved, 1333k data, 184k init, 0k highmem)
[   11.777766] virtual kernel memory layout:
[   11.777768]     fixmap  : 0xfffb7000 - 0xfffff000   ( 288 kB)
[   11.777770]     vmalloc : 0xf8800000 - 0xfffb5000   ( 119 MB)
[   11.777773]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   11.777775]       .init : 0xc0532000 - 0xc0560000   ( 184 kB)
[   11.777777]       .data : 0xc03ddc81 - 0xc052b190   (1333 kB)
[   11.777779]       .text : 0xc0100000 - 0xc03ddc81   (2935 kB)
[   11.778246] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[   11.928280] Calibrating delay using timer specific routine.. 3661.21 BogoMIPS (lpj=18306090)
[   11.928482] Mount-cache hash table entries: 512
[   11.928687] CPU: After generic identify, caps: bfe9fbff 00000000 00000000 00000000 0000c1a9 00000000 00000000
[   11.928698] monitor/mwait feature present.
[   11.928766] using mwait in idle threads.
[   11.928837] CPU: L1 I cache: 32K, L1 D cache: 32K
[   11.928950] CPU: L2 cache: 2048K
[   11.929016] CPU: Physical Processor ID: 0
[   11.929083] CPU: Processor Core ID: 0
[   11.929149] CPU: After all inits, caps: bfe9fbff 00000000 00000000 00002940 0000c1a9 00000000 00000000
[   11.929159] Intel machine check architecture supported.
[   11.929235] Intel machine check reporting enabled on CPU#0.
[   11.929307] Compat vDSO mapped to ffffe000.
[   11.929386] Checking 'hlt' instruction... OK.
[   11.968411] SMP alternatives: switching to UP code
[   11.968822] ACPI: Core revision 20070126
[   12.001702] CPU0: Intel Genuine Intel(R) CPU           T2400  @ 1.83GHz stepping 08
[   12.001945] SMP alternatives: switching to SMP code
[   12.002065] Booting processor 1/1 eip 3000
[   12.013090] Initializing CPU#1
[   12.158203] Calibrating delay using timer specific routine.. 3657.59 BogoMIPS (lpj=18287992)
[   12.158212] CPU: After generic identify, caps: bfe9fbff 00000000 00000000 00000000 0000c1a9 00000000 00000000
[   12.158221] monitor/mwait feature present.
[   12.158226] CPU: L1 I cache: 32K, L1 D cache: 32K
[   12.158229] CPU: L2 cache: 2048K
[   12.158233] CPU: Physical Processor ID: 0
[   12.158235] CPU: Processor Core ID: 1
[   12.158238] CPU: After all inits, caps: bfe9fbff 00000000 00000000 00002940 0000c1a9 00000000 00000000
[   12.158247] Intel machine check architecture supported.
[   12.158256] Intel machine check reporting enabled on CPU#1.
[   12.158528] CPU1: Intel Genuine Intel(R) CPU           T2400  @ 1.83GHz stepping 08
[   12.159377] Total of 2 processors activated (7318.81 BogoMIPS).
[   12.159644] ENABLING IO-APIC IRQs
[   12.159938] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[   12.497483] checking TSC synchronization [CPU#0 -> CPU#1]:
[   12.517575] Measured 578974 cycles TSC warp between CPUs, turning off TSC clock.
[   12.517674] Brought up 2 CPUs
[   12.823444] migration_cost=78
[   12.823392] PM: Adding info for No Bus:platform
[   12.823577] NET: Registered protocol family 16
[   12.823836] PM: Adding info for platform:dock.0
[   12.824223] ACPI: ACPI Dock Station Driver 
[   12.824311] PM: Adding info for No Bus:vtcon0
[   12.824360] ACPI: bus type pci registered
[   12.824439] PCI: Using MMCONFIG
[   12.825412] Setting up standard PCI resources
[   12.844565] ACPI: Interpreter enabled
[   12.844634] ACPI: (supports S0 S3 S4 S5)
[   12.844952] ACPI: Using IOAPIC for interrupt routing
[   12.845158] PM: Adding info for acpi:acpi_system:00
[   12.845224] PM: Adding info for acpi:button_power:00
[   12.845289] PM: Adding info for acpi:ACPI0007:00
[   12.845352] PM: Adding info for acpi:ACPI0007:01
[   12.845429] PM: Adding info for acpi:device:00
[   12.845991] PM: Adding info for acpi:PNP0C0F:00
[   12.846542] PM: Adding info for acpi:PNP0C0F:01
[   12.847114] PM: Adding info for acpi:PNP0C0F:02
[   12.847654] PM: Adding info for acpi:PNP0C0F:03
[   12.848197] PM: Adding info for acpi:PNP0C0F:04
[   12.848739] PM: Adding info for acpi:PNP0C0F:05
[   12.849284] PM: Adding info for acpi:PNP0C0F:06
[   12.849824] PM: Adding info for acpi:PNP0C0F:07
[   12.849903] PM: Adding info for acpi:PNP0C01:00
[   12.850104] PM: Adding info for acpi:PNP0C0D:00
[   12.850294] PM: Adding info for acpi:PNP0C0E:00
[   12.850375] PM: Adding info for acpi:PNP0A08:00
[   12.850468] PM: Adding info for acpi:device:01
[   12.850549] PM: Adding info for acpi:PNP0C02:00
[   12.850640] PM: Adding info for acpi:PNP0000:00
[   12.850712] PM: Adding info for acpi:PNP0100:00
[   12.851021] PM: Adding info for acpi:PNP0103:00
[   12.851098] PM: Adding info for acpi:PNP0200:00
[   12.851172] PM: Adding info for acpi:PNP0800:00
[   12.851254] PM: Adding info for acpi:PNP0C04:00
[   12.851331] PM: Adding info for acpi:PNP0B00:00
[   12.851407] PM: Adding info for acpi:PNP0303:00
[   12.851484] PM: Adding info for acpi:IBM0057:00
[   12.853544] PM: Adding info for acpi:IBM0071:00
[   12.853773] PM: Adding info for acpi:PNP0C09:00
[   12.853884] PM: Adding info for acpi:power_resource:00
[   12.854416] PM: Adding info for acpi:PNP0C0A:00
[   12.854901] PM: Adding info for acpi:ACPI0003:00
[   12.855162] PM: Adding info for acpi:IBM0068:00
[   12.855296] PM: Adding info for acpi:video:00
[   12.855375] PM: Adding info for acpi:device:02
[   12.855449] PM: Adding info for acpi:device:03
[   12.855537] PM: Adding info for acpi:device:04
[   12.855623] PM: Adding info for acpi:device:05
[   12.855708] PM: Adding info for acpi:video:01
[   12.855787] PM: Adding info for acpi:device:06
[   12.855862] PM: Adding info for acpi:device:07
[   12.855939] PM: Adding info for acpi:device:08
[   12.856030] PM: Adding info for acpi:device:09
[   12.856119] PM: Adding info for acpi:device:0a
[   12.856205] PM: Adding info for acpi:device:0b
[   12.856286] PM: Adding info for acpi:device:0c
[   12.856369] PM: Adding info for acpi:device:0d
[   12.856448] PM: Adding info for acpi:device:0e
[   12.856532] PM: Adding info for acpi:device:0f
[   12.856718] PM: Adding info for acpi:device:10
[   12.856803] PM: Adding info for acpi:device:11
[   12.856899] PM: Adding info for acpi:device:12
[   12.857626] PM: Adding info for acpi:bay:00
[   12.857729] PM: Adding info for acpi:device:13
[   12.857827] PM: Adding info for acpi:device:14
[   12.857908] PM: Adding info for acpi:device:15
[   12.858022] PM: Adding info for acpi:device:16
[   12.858120] PM: Adding info for acpi:device:17
[   12.858198] PM: Adding info for acpi:device:18
[   12.858271] PM: Adding info for acpi:device:19
[   12.858382] PM: Adding info for acpi:device:1a
[   12.858462] PM: Adding info for acpi:device:1b
[   12.858543] PM: Adding info for acpi:device:1c
[   12.858624] PM: Adding info for acpi:device:1d
[   12.858733] PM: Adding info for acpi:device:1e
[   12.858814] PM: Adding info for acpi:device:1f
[   12.858890] PM: Adding info for acpi:device:20
[   12.858972] PM: Adding info for acpi:device:21
[   12.859057] PM: Adding info for acpi:device:22
[   12.859834] PM: Adding info for acpi:thermal:00
[   12.859899] PM: Adding info for acpi:thermal:01
[   12.859962] PM: Adding info for acpi:thermal:02
[   12.860597] ACPI: PCI Root Bridge [PCI0] (0000:00)
[   12.860676] PCI: Probing PCI hardware (bus 00)
[   12.860689] PM: Adding info for No Bus:pci0000:00
[   12.860786] Boot video device is 0000:00:02.0
[   12.861391] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[   12.861465] PCI quirk: region 1180-11bf claimed by ICH6 GPIO
[   12.861585] 0000:00:1f.1: trying to change BAR0 from 0000 to 01F0
[   12.861658] 0000:00:1f.1: trying to change BAR1 from 0000 to 03F4
[   12.861730] 0000:00:1f.1: trying to change BAR2 from 0000 to 0170
[   12.861803] 0000:00:1f.1: trying to change BAR3 from 0000 to 0374
[   12.863027] PCI: Transparent bridge - 0000:00:1e.0
[   12.863250] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[   12.863563] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT]
[   12.863784] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
[   12.864005] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
[   12.864233] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
[   12.864458] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
[   12.864916] PM: Adding info for pci:0000:00:00.0
[   12.865159] PM: Adding info for pci:0000:00:02.0
[   12.865392] PM: Adding info for pci:0000:00:02.1
[   12.865625] PM: Adding info for pci:0000:00:1b.0
[   12.865865] PM: Adding info for pci:0000:00:1c.0
[   12.866100] PM: Adding info for pci:0000:00:1c.1
[   12.866332] PM: Adding info for pci:0000:00:1c.2
[   12.866564] PM: Adding info for pci:0000:00:1c.3
[   12.866829] PM: Adding info for pci:0000:00:1d.0
[   12.867063] PM: Adding info for pci:0000:00:1d.1
[   12.867295] PM: Adding info for pci:0000:00:1d.2
[   12.867532] PM: Adding info for pci:0000:00:1d.3
[   12.867764] PM: Adding info for pci:0000:00:1d.7
[   12.867995] PM: Adding info for pci:0000:00:1e.0
[   12.868231] PM: Adding info for pci:0000:00:1f.0
[   12.868464] PM: Adding info for pci:0000:00:1f.1
[   12.868696] PM: Adding info for pci:0000:00:1f.2
[   12.868936] PM: Adding info for pci:0000:00:1f.3
[   12.869003] PM: Adding info for pci:0000:02:00.0
[   12.869070] PM: Adding info for pci:0000:03:00.0
[   12.869244] PM: Adding info for pci:0000:15:00.0
[   12.869647] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
[   12.870534] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11)
[   12.871418] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11)
[   12.872300] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11)
[   12.873181] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11)
[   12.874062] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11)
[   12.874946] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11)
[   12.875829] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
[   12.876843] ACPI: Power Resource [PUBS] (on)
[   12.876943] Linux Plug and Play Support v0.97 (c) Adam Belay
[   12.877022] pnp: PnP ACPI init
[   12.877099] PM: Adding info for No Bus:pnp0
[   12.879323] PM: Adding info for pnp:00:00
[   12.879416] PM: Adding info for pnp:00:01
[   12.879496] PM: Adding info for pnp:00:02
[   12.879690] PM: Adding info for pnp:00:03
[   12.879756] PM: Adding info for pnp:00:04
[   12.879817] PM: Adding info for pnp:00:05
[   12.879891] PM: Adding info for pnp:00:06
[   12.879959] PM: Adding info for pnp:00:07
[   12.880027] PM: Adding info for pnp:00:08
[   12.880094] PM: Adding info for pnp:00:09
[   12.881965] PM: Adding info for pnp:00:0a
[   12.883808] pnp: PnP ACPI: found 11 devices
[   12.884882] SCSI subsystem initialized
[   12.884999] libata version 2.20 loaded.
[   12.885078] usbcore: registered new interface driver usbfs
[   12.885198] usbcore: registered new interface driver hub
[   12.885322] usbcore: registered new device driver usb
[   12.885493] PCI: Using ACPI for IRQ routing
[   12.885561] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[   12.886025] pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved
[   12.886098] pnp: 00:00: iomem range 0xc0000-0xc3fff could not be reserved
[   12.886172] pnp: 00:00: iomem range 0xc4000-0xc7fff could not be reserved
[   12.886246] pnp: 00:00: iomem range 0xc8000-0xcbfff has been reserved
[   12.886325] pnp: 00:02: iomem range 0xf0000000-0xf3ffffff could not be reserved
[   12.886412] pnp: 00:02: iomem range 0xfed1c000-0xfed1ffff could not be reserved
[   12.886500] pnp: 00:02: iomem range 0xfed14000-0xfed17fff could not be reserved
[   12.886588] pnp: 00:02: iomem range 0xfed18000-0xfed18fff could not be reserved
[   12.886676] Time: hpet clocksource has been installed.
[   12.886796] PM: Adding info for No Bus:mem
[   12.886840] PM: Adding info for No Bus:kmem
[   12.886881] PM: Adding info for No Bus:null
[   12.886923] PM: Adding info for No Bus:port
[   12.886963] PM: Adding info for No Bus:zero
[   12.887010] PM: Adding info for No Bus:full
[   12.887051] PM: Adding info for No Bus:random
[   12.887092] PM: Adding info for No Bus:urandom
[   12.887133] PM: Adding info for No Bus:kmsg
[   12.917175] PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
[   12.917250] PCI: Bridge: 0000:00:1c.0
[   12.917318]   IO window: 2000-2fff
[   12.917388]   MEM window: ee000000-ee0fffff
[   12.917457]   PREFETCH window: disabled.
[   12.917527] PCI: Bridge: 0000:00:1c.1
[   12.917595]   IO window: 3000-4fff
[   12.917664]   MEM window: ec000000-edffffff
[   12.917735]   PREFETCH window: e4000000-e40fffff
[   12.917806] PCI: Bridge: 0000:00:1c.2
[   12.917873]   IO window: 5000-6fff
[   12.917943]   MEM window: e8000000-e9ffffff
[   12.918013]   PREFETCH window: e4100000-e41fffff
[   12.918084] PCI: Bridge: 0000:00:1c.3
[   12.918151]   IO window: 7000-8fff
[   12.918221]   MEM window: ea000000-ebffffff
[   12.918290]   PREFETCH window: e4200000-e42fffff
[   12.918366] PCI: Bus 22, cardbus bridge: 0000:15:00.0
[   12.918435]   IO window: 00009000-000090ff
[   12.918506]   IO window: 00009400-000094ff
[   12.918577]   PREFETCH window: e0000000-e3ffffff
[   12.918648]   MEM window: 50000000-53ffffff
[   12.918719] PCI: Bridge: 0000:00:1e.0
[   12.918786]   IO window: 9000-cfff
[   12.918855]   MEM window: e4300000-e7ffffff
[   12.918926]   PREFETCH window: e0000000-e3ffffff
[   12.919022] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 20 (level, low) -> IRQ 16
[   12.919158] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[   12.919182] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 21 (level, low) -> IRQ 17
[   12.919317] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[   12.919340] ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 22 (level, low) -> IRQ 18
[   12.919475] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[   12.919498] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 23 (level, low) -> IRQ 19
[   12.919633] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[   12.919645] PCI: Enabling device 0000:00:1e.0 (0005 -> 0007)
[   12.919720] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[   12.919740] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[   12.919912] NET: Registered protocol family 2
[   13.016480] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[   13.016657] TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
[   13.018505] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   13.019198] TCP: Hash tables configured (established 131072 bind 65536)
[   13.019270] TCP reno registered
[   13.046541] Simple Boot Flag at 0x35 set to 0x1
[   13.047398] PM: Adding info for platform:pcspkr
[   13.047625] PM: Adding info for No Bus:snapshot
[   13.048056] NTFS driver 2.1.28 [Flags: R/W].
[   13.048161] fuse init (API version 7.8)
[   13.048254] PM: Adding info for No Bus:fuse
[   13.048388] io scheduler noop registered
[   13.048517] io scheduler cfq registered (default)
[   13.048989] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[   13.049043] assign_interrupt_mode Found MSI capability
[   13.049114] Allocate Port Service[0000:00:1c.0:pcie00]
[   13.049123] PM: Adding info for pci_express:0000:00:1c.0:pcie00
[   13.049170] Allocate Port Service[0000:00:1c.0:pcie02]
[   13.049179] PM: Adding info for pci_express:0000:00:1c.0:pcie02
[   13.049225] Allocate Port Service[0000:00:1c.0:pcie03]
[   13.049234] PM: Adding info for pci_express:0000:00:1c.0:pcie03
[   13.049340] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[   13.049393] assign_interrupt_mode Found MSI capability
[   13.049464] Allocate Port Service[0000:00:1c.1:pcie00]
[   13.049473] PM: Adding info for pci_express:0000:00:1c.1:pcie00
[   13.049518] Allocate Port Service[0000:00:1c.1:pcie02]
[   13.049527] PM: Adding info for pci_express:0000:00:1c.1:pcie02
[   13.049572] Allocate Port Service[0000:00:1c.1:pcie03]
[   13.049586] PM: Adding info for pci_express:0000:00:1c.1:pcie03
[   13.049689] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[   13.049742] assign_interrupt_mode Found MSI capability
[   13.049812] Allocate Port Service[0000:00:1c.2:pcie00]
[   13.049821] PM: Adding info for pci_express:0000:00:1c.2:pcie00
[   13.049867] Allocate Port Service[0000:00:1c.2:pcie02]
[   13.049875] PM: Adding info for pci_express:0000:00:1c.2:pcie02
[   13.049920] Allocate Port Service[0000:00:1c.2:pcie03]
[   13.049929] PM: Adding info for pci_express:0000:00:1c.2:pcie03
[   13.050032] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[   13.050085] assign_interrupt_mode Found MSI capability
[   13.050155] Allocate Port Service[0000:00:1c.3:pcie00]
[   13.050163] PM: Adding info for pci_express:0000:00:1c.3:pcie00
[   13.050215] Allocate Port Service[0000:00:1c.3:pcie02]
[   13.050224] PM: Adding info for pci_express:0000:00:1c.3:pcie02
[   13.050272] Allocate Port Service[0000:00:1c.3:pcie03]
[   13.050280] PM: Adding info for pci_express:0000:00:1c.3:pcie03
[   13.050441] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   13.050512] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[   13.058733] acpiphp_ibm: ibm_find_acpi_device:  Failed to get device information<3>acpiphp_ibm: ibm_find_acpi_device:  Failed to get device information<3>acpiphp_ibm: ibm_find_acpi_device:  Failed to get device information<3>acpiphp_ibm: ibm_find_acpi_device:  Failed to get device information<3>acpiphp_ibm: ibm_find_acpi_device:  Failed to get device information<3>acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
[   13.063910] PM: Adding info for platform:vesafb.0
[   13.064266] ACPI: AC Adapter [AC] (off-line)
[   13.072884] ACPI: Battery Slot [BAT0] (battery present)
[   13.073123] input: Power Button (FF) as /class/input/input0
[   13.073194] ACPI: Power Button (FF) [PWRF]
[   13.073359] input: Lid Switch as /class/input/input1
[   13.073432] ACPI: Lid Switch [LID]
[   13.073584] input: Sleep Button (CM) as /class/input/input2
[   13.073659] ACPI: Sleep Button (CM) [SLPB]
[   13.074248] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   13.074607] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   13.075207] ACPI: SSDT 3F6E6121, 01ED (r1  PmRef  Cpu0Ist      100 INTL 20050513)
[   13.075894] ACPI: SSDT 3F6E5E64, 0238 (r1  PmRef  Cpu0Cst      100 INTL 20050513)
[   13.077471] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[   13.077727] ACPI: Processor [CPU0] (supports 8 throttling states)
[   13.078288] ACPI: SSDT 3F6E630E, 0094 (r1  PmRef  Cpu1Ist      100 INTL 20050513)
[   13.078953] ACPI: SSDT 3F6E609C, 0085 (r1  PmRef  Cpu1Cst      100 INTL 20050513)
[   13.080482] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[   13.080736] ACPI: Processor [CPU1] (supports 8 throttling states)
[   13.089078] ACPI: Thermal Zone [THM0] (47 C)
[   13.091466] ACPI: Thermal Zone [THM1] (47 C)
[   13.091612] ibm_acpi: IBM ThinkPad ACPI Extras v0.13
[   13.091680] ibm_acpi: http://ibm-acpi.sf.net/
[   13.091747] ibm_acpi: ThinkPad EC firmware 79HT43WW-1.02
[   13.092843] PM: Adding info for No Bus:tty
[   13.092891] PM: Adding info for No Bus:console
[   13.092939] PM: Adding info for No Bus:ptmx
[   13.092982] PM: Adding info for No Bus:tty0
[   13.093030] PM: Adding info for No Bus:vcs
[   13.093073] PM: Adding info for No Bus:vcsa
[   13.093119] PM: Adding info for No Bus:tty1
[   13.093160] PM: Adding info for No Bus:tty2
[   13.093208] PM: Adding info for No Bus:tty3
[   13.093251] PM: Adding info for No Bus:tty4
[   13.093293] PM: Adding info for No Bus:tty5
[   13.093335] PM: Adding info for No Bus:tty6
[   13.093376] PM: Adding info for No Bus:tty7
[   13.093418] PM: Adding info for No Bus:tty8
[   13.093464] PM: Adding info for No Bus:tty9
[   13.093513] PM: Adding info for No Bus:tty10
[   13.093559] PM: Adding info for No Bus:tty11
[   13.093604] PM: Adding info for No Bus:tty12
[   13.093653] PM: Adding info for No Bus:tty13
[   13.093697] PM: Adding info for No Bus:tty14
[   13.093741] PM: Adding info for No Bus:tty15
[   13.093791] PM: Adding info for No Bus:tty16
[   13.093835] PM: Adding info for No Bus:tty17
[   13.093880] PM: Adding info for No Bus:tty18
[   13.093927] PM: Adding info for No Bus:tty19
[   13.093972] PM: Adding info for No Bus:tty20
[   13.094016] PM: Adding info for No Bus:tty21
[   13.094061] PM: Adding info for No Bus:tty22
[   13.094116] PM: Adding info for No Bus:tty23
[   13.094163] PM: Adding info for No Bus:tty24
[   13.094213] PM: Adding info for No Bus:tty25
[   13.094258] PM: Adding info for No Bus:tty26
[   13.094305] PM: Adding info for No Bus:tty27
[   13.094351] PM: Adding info for No Bus:tty28
[   13.094403] PM: Adding info for No Bus:tty29
[   13.094448] PM: Adding info for No Bus:tty30
[   13.094494] PM: Adding info for No Bus:tty31
[   13.094540] PM: Adding info for No Bus:tty32
[   13.094589] PM: Adding info for No Bus:tty33
[   13.094636] PM: Adding info for No Bus:tty34
[   13.094683] PM: Adding info for No Bus:tty35
[   13.094736] PM: Adding info for No Bus:tty36
[   13.094790] PM: Adding info for No Bus:tty37
[   13.094837] PM: Adding info for No Bus:tty38
[   13.094884] PM: Adding info for No Bus:tty39
[   13.094933] PM: Adding info for No Bus:tty40
[   13.094980] PM: Adding info for No Bus:tty41
[   13.095032] PM: Adding info for No Bus:tty42
[   13.095082] PM: Adding info for No Bus:tty43
[   13.095130] PM: Adding info for No Bus:tty44
[   13.095178] PM: Adding info for No Bus:tty45
[   13.095226] PM: Adding info for No Bus:tty46
[   13.095274] PM: Adding info for No Bus:tty47
[   13.095322] PM: Adding info for No Bus:tty48
[   13.095375] PM: Adding info for No Bus:tty49
[   13.095422] PM: Adding info for No Bus:tty50
[   13.095474] PM: Adding info for No Bus:tty51
[   13.095522] PM: Adding info for No Bus:tty52
[   13.095572] PM: Adding info for No Bus:tty53
[   13.095623] PM: Adding info for No Bus:tty54
[   13.095677] PM: Adding info for No Bus:tty55
[   13.095725] PM: Adding info for No Bus:tty56
[   13.095774] PM: Adding info for No Bus:tty57
[   13.095823] PM: Adding info for No Bus:tty58
[   13.095874] PM: Adding info for No Bus:tty59
[   13.095923] PM: Adding info for No Bus:tty60
[   13.095973] PM: Adding info for No Bus:tty61
[   13.096028] PM: Adding info for No Bus:tty62
[   13.096080] PM: Adding info for No Bus:tty63
[   13.096198] PM: Adding info for No Bus:ptyp0
[   13.096251] PM: Adding info for No Bus:ptyp1
[   13.096300] PM: Adding info for No Bus:ptyp2
[   13.096348] PM: Adding info for No Bus:ptyp3
[   13.096402] PM: Adding info for No Bus:ptyp4
[   13.096453] PM: Adding info for No Bus:ptyp5
[   13.096502] PM: Adding info for No Bus:ptyp6
[   13.096552] PM: Adding info for No Bus:ptyp7
[   13.096601] PM: Adding info for No Bus:ptyp8
[   13.096653] PM: Adding info for No Bus:ptyp9
[   13.096701] PM: Adding info for No Bus:ptypa
[   13.096755] PM: Adding info for No Bus:ptypb
[   13.096804] PM: Adding info for No Bus:ptypc
[   13.096854] PM: Adding info for No Bus:ptypd
[   13.096904] PM: Adding info for No Bus:ptype
[   13.096956] PM: Adding info for No Bus:ptypf
[   13.097006] PM: Adding info for No Bus:ptyq0
[   13.097063] PM: Adding info for No Bus:ptyq1
[   13.097113] PM: Adding info for No Bus:ptyq2
[   13.097165] PM: Adding info for No Bus:ptyq3
[   13.097214] PM: Adding info for No Bus:ptyq4
[   13.097266] PM: Adding info for No Bus:ptyq5
[   13.097316] PM: Adding info for No Bus:ptyq6
[   13.097366] PM: Adding info for No Bus:ptyq7
[   13.097421] PM: Adding info for No Bus:ptyq8
[   13.097508] PM: Adding info for No Bus:ptyq9
[   13.097557] PM: Adding info for No Bus:ptyqa
[   13.097605] PM: Adding info for No Bus:ptyqb
[   13.097653] PM: Adding info for No Bus:ptyqc
[   13.097706] PM: Adding info for No Bus:ptyqd
[   13.097761] PM: Adding info for No Bus:ptyqe
[   13.097810] PM: Adding info for No Bus:ptyqf
[   13.097859] PM: Adding info for No Bus:ptyr0
[   13.097908] PM: Adding info for No Bus:ptyr1
[   13.097963] PM: Adding info for No Bus:ptyr2
[   13.098014] PM: Adding info for No Bus:ptyr3
[   13.098063] PM: Adding info for No Bus:ptyr4
[   13.098119] PM: Adding info for No Bus:ptyr5
[   13.098168] PM: Adding info for No Bus:ptyr6
[   13.098221] PM: Adding info for No Bus:ptyr7
[   13.098273] PM: Adding info for No Bus:ptyr8
[   13.098325] PM: Adding info for No Bus:ptyr9
[   13.098377] PM: Adding info for No Bus:ptyra
[   13.098436] PM: Adding info for No Bus:ptyrb
[   13.098491] PM: Adding info for No Bus:ptyrc
[   13.098545] PM: Adding info for No Bus:ptyrd
[   13.098596] PM: Adding info for No Bus:ptyre
[   13.098648] PM: Adding info for No Bus:ptyrf
[   13.098700] PM: Adding info for No Bus:ptys0
[   13.098756] PM: Adding info for No Bus:ptys1
[   13.098813] PM: Adding info for No Bus:ptys2
[   13.098866] PM: Adding info for No Bus:ptys3
[   13.098919] PM: Adding info for No Bus:ptys4
[   13.098974] PM: Adding info for No Bus:ptys5
[   13.099028] PM: Adding info for No Bus:ptys6
[   13.099081] PM: Adding info for No Bus:ptys7
[   13.099140] PM: Adding info for No Bus:ptys8
[   13.099196] PM: Adding info for No Bus:ptys9
[   13.099249] PM: Adding info for No Bus:ptysa
[   13.099303] PM: Adding info for No Bus:ptysb
[   13.099357] PM: Adding info for No Bus:ptysc
[   13.099413] PM: Adding info for No Bus:ptysd
[   13.099469] PM: Adding info for No Bus:ptyse
[   13.099529] PM: Adding info for No Bus:ptysf
[   13.099586] PM: Adding info for No Bus:ptyt0
[   13.099640] PM: Adding info for No Bus:ptyt1
[   13.099694] PM: Adding info for No Bus:ptyt2
[   13.099749] PM: Adding info for No Bus:ptyt3
[   13.099804] PM: Adding info for No Bus:ptyt4
[   13.099864] PM: Adding info for No Bus:ptyt5
[   13.099920] PM: Adding info for No Bus:ptyt6
[   13.099978] PM: Adding info for No Bus:ptyt7
[   13.100032] PM: Adding info for No Bus:ptyt8
[   13.100087] PM: Adding info for No Bus:ptyt9
[   13.100145] PM: Adding info for No Bus:ptyta
[   13.100201] PM: Adding info for No Bus:ptytb
[   13.100263] PM: Adding info for No Bus:ptytc
[   13.100329] PM: Adding info for No Bus:ptytd
[   13.100384] PM: Adding info for No Bus:ptyte
[   13.100439] PM: Adding info for No Bus:ptytf
[   13.100495] PM: Adding info for No Bus:ptyu0
[   13.100553] PM: Adding info for No Bus:ptyu1
[   13.100613] PM: Adding info for No Bus:ptyu2
[   13.100669] PM: Adding info for No Bus:ptyu3
[   13.100727] PM: Adding info for No Bus:ptyu4
[   13.100787] PM: Adding info for No Bus:ptyu5
[   13.100844] PM: Adding info for No Bus:ptyu6
[   13.100900] PM: Adding info for No Bus:ptyu7
[   13.100957] PM: Adding info for No Bus:ptyu8
[   13.101020] PM: Adding info for No Bus:ptyu9
[   13.101076] PM: Adding info for No Bus:ptyua
[   13.101133] PM: Adding info for No Bus:ptyub
[   13.101192] PM: Adding info for No Bus:ptyuc
[   13.101250] PM: Adding info for No Bus:ptyud
[   13.101308] PM: Adding info for No Bus:ptyue
[   13.101373] PM: Adding info for No Bus:ptyuf
[   13.101431] PM: Adding info for No Bus:ptyv0
[   13.101487] PM: Adding info for No Bus:ptyv1
[   13.101545] PM: Adding info for No Bus:ptyv2
[   13.101605] PM: Adding info for No Bus:ptyv3
[   13.101662] PM: Adding info for No Bus:ptyv4
[   13.101721] PM: Adding info for No Bus:ptyv5
[   13.101783] PM: Adding info for No Bus:ptyv6
[   13.101843] PM: Adding info for No Bus:ptyv7
[   13.101904] PM: Adding info for No Bus:ptyv8
[   13.101962] PM: Adding info for No Bus:ptyv9
[   13.102024] PM: Adding info for No Bus:ptyva
[   13.102083] PM: Adding info for No Bus:ptyvb
[   13.102147] PM: Adding info for No Bus:ptyvc
[   13.102207] PM: Adding info for No Bus:ptyvd
[   13.102269] PM: Adding info for No Bus:ptyve
[   13.102327] PM: Adding info for No Bus:ptyvf
[   13.102385] PM: Adding info for No Bus:ptyw0
[   13.102448] PM: Adding info for No Bus:ptyw1
[   13.102508] PM: Adding info for No Bus:ptyw2
[   13.102571] PM: Adding info for No Bus:ptyw3
[   13.102631] PM: Adding info for No Bus:ptyw4
[   13.102690] PM: Adding info for No Bus:ptyw5
[   13.102748] PM: Adding info for No Bus:ptyw6
[   13.102809] PM: Adding info for No Bus:ptyw7
[   13.102869] PM: Adding info for No Bus:ptyw8
[   13.102936] PM: Adding info for No Bus:ptyw9
[   13.102996] PM: Adding info for No Bus:ptywa
[   13.103056] PM: Adding info for No Bus:ptywb
[   13.103116] PM: Adding info for No Bus:ptywc
[   13.103177] PM: Adding info for No Bus:ptywd
[   13.103236] PM: Adding info for No Bus:ptywe
[   13.103298] PM: Adding info for No Bus:ptywf
[   13.103365] PM: Adding info for No Bus:ptyx0
[   13.103426] PM: Adding info for No Bus:ptyx1
[   13.103485] PM: Adding info for No Bus:ptyx2
[   13.103547] PM: Adding info for No Bus:ptyx3
[   13.103607] PM: Adding info for No Bus:ptyx4
[   13.103667] PM: Adding info for No Bus:ptyx5
[   13.103738] PM: Adding info for No Bus:ptyx6
[   13.103799] PM: Adding info for No Bus:ptyx7
[   13.103861] PM: Adding info for No Bus:ptyx8
[   13.103923] PM: Adding info for No Bus:ptyx9
[   13.103983] PM: Adding info for No Bus:ptyxa
[   13.104043] PM: Adding info for No Bus:ptyxb
[   13.104105] PM: Adding info for No Bus:ptyxc
[   13.104175] PM: Adding info for No Bus:ptyxd
[   13.104235] PM: Adding info for No Bus:ptyxe
[   13.104296] PM: Adding info for No Bus:ptyxf
[   13.104362] PM: Adding info for No Bus:ptyy0
[   13.104423] PM: Adding info for No Bus:ptyy1
[   13.104484] PM: Adding info for No Bus:ptyy2
[   13.104549] PM: Adding info for No Bus:ptyy3
[   13.104612] PM: Adding info for No Bus:ptyy4
[   13.104676] PM: Adding info for No Bus:ptyy5
[   13.104738] PM: Adding info for No Bus:ptyy6
[   13.104801] PM: Adding info for No Bus:ptyy7
[   13.104863] PM: Adding info for No Bus:ptyy8
[   13.104924] PM: Adding info for No Bus:ptyy9
[   13.104992] PM: Adding info for No Bus:ptyya
[   13.105058] PM: Adding info for No Bus:ptyyb
[   13.105119] PM: Adding info for No Bus:ptyyc
[   13.105181] PM: Adding info for No Bus:ptyyd
[   13.105245] PM: Adding info for No Bus:ptyye
[   13.105307] PM: Adding info for No Bus:ptyyf
[   13.105374] PM: Adding info for No Bus:ptyz0
[   13.105438] PM: Adding info for No Bus:ptyz1
[   13.105504] PM: Adding info for No Bus:ptyz2
[   13.105566] PM: Adding info for No Bus:ptyz3
[   13.105632] PM: Adding info for No Bus:ptyz4
[   13.105696] PM: Adding info for No Bus:ptyz5
[   13.105761] PM: Adding info for No Bus:ptyz6
[   13.105829] PM: Adding info for No Bus:ptyz7
[   13.105894] PM: Adding info for No Bus:ptyz8
[   13.105959] PM: Adding info for No Bus:ptyz9
[   13.106023] PM: Adding info for No Bus:ptyza
[   13.106085] PM: Adding info for No Bus:ptyzb
[   13.106148] PM: Adding info for No Bus:ptyzc
[   13.106219] PM: Adding info for No Bus:ptyzd
[   13.106284] PM: Adding info for No Bus:ptyze
[   13.106346] PM: Adding info for No Bus:ptyzf
[   13.106411] PM: Adding info for No Bus:ptya0
[   13.106475] PM: Adding info for No Bus:ptya1
[   13.106538] PM: Adding info for No Bus:ptya2
[   13.106606] PM: Adding info for No Bus:ptya3
[   13.106674] PM: Adding info for No Bus:ptya4
[   13.106740] PM: Adding info for No Bus:ptya5
[   13.106806] PM: Adding info for No Bus:ptya6
[   13.106873] PM: Adding info for No Bus:ptya7
[   13.106939] PM: Adding info for No Bus:ptya8
[   13.107005] PM: Adding info for No Bus:ptya9
[   13.107073] PM: Adding info for No Bus:ptyaa
[   13.107137] PM: Adding info for No Bus:ptyab
[   13.107203] PM: Adding info for No Bus:ptyac
[   13.107268] PM: Adding info for No Bus:ptyad
[   13.107339] PM: Adding info for No Bus:ptyae
[   13.107404] PM: Adding info for No Bus:ptyaf
[   13.107483] PM: Adding info for No Bus:ptyb0
[   13.107554] PM: Adding info for No Bus:ptyb1
[   13.107621] PM: Adding info for No Bus:ptyb2
[   13.107686] PM: Adding info for No Bus:ptyb3
[   13.107751] PM: Adding info for No Bus:ptyb4
[   13.107821] PM: Adding info for No Bus:ptyb5
[   13.107886] PM: Adding info for No Bus:ptyb6
[   13.107956] PM: Adding info for No Bus:ptyb7
[   13.108022] PM: Adding info for No Bus:ptyb8
[   13.108087] PM: Adding info for No Bus:ptyb9
[   13.108152] PM: Adding info for No Bus:ptyba
[   13.108218] PM: Adding info for No Bus:ptybb
[   13.108288] PM: Adding info for No Bus:ptybc
[   13.108356] PM: Adding info for No Bus:ptybd
[   13.108428] PM: Adding info for No Bus:ptybe
[   13.108494] PM: Adding info for No Bus:ptybf
[   13.108562] PM: Adding info for No Bus:ptyc0
[   13.108629] PM: Adding info for No Bus:ptyc1
[   13.108695] PM: Adding info for No Bus:ptyc2
[   13.108768] PM: Adding info for No Bus:ptyc3
[   13.108840] PM: Adding info for No Bus:ptyc4
[   13.108908] PM: Adding info for No Bus:ptyc5
[   13.108976] PM: Adding info for No Bus:ptyc6
[   13.109043] PM: Adding info for No Bus:ptyc7
[   13.109109] PM: Adding info for No Bus:ptyc8
[   13.109175] PM: Adding info for No Bus:ptyc9
[   13.109242] PM: Adding info for No Bus:ptyca
[   13.109318] PM: Adding info for No Bus:ptycb
[   13.109385] PM: Adding info for No Bus:ptycc
[   13.109454] PM: Adding info for No Bus:ptycd
[   13.109522] PM: Adding info for No Bus:ptyce
[   13.109588] PM: Adding info for No Bus:ptycf
[   13.109658] PM: Adding info for No Bus:ptyd0
[   13.109733] PM: Adding info for No Bus:ptyd1
[   13.109803] PM: Adding info for No Bus:ptyd2
[   13.109871] PM: Adding info for No Bus:ptyd3
[   13.109939] PM: Adding info for No Bus:ptyd4
[   13.110011] PM: Adding info for No Bus:ptyd5
[   13.110079] PM: Adding info for No Bus:ptyd6
[   13.110146] PM: Adding info for No Bus:ptyd7
[   13.110219] PM: Adding info for No Bus:ptyd8
[   13.110288] PM: Adding info for No Bus:ptyd9
[   13.110359] PM: Adding info for No Bus:ptyda
[   13.110427] PM: Adding info for No Bus:ptydb
[   13.110496] PM: Adding info for No Bus:ptydc
[   13.110566] PM: Adding info for No Bus:ptydd
[   13.110639] PM: Adding info for No Bus:ptyde
[   13.110712] PM: Adding info for No Bus:ptydf
[   13.110780] PM: Adding info for No Bus:ptye0
[   13.110850] PM: Adding info for No Bus:ptye1
[   13.110923] PM: Adding info for No Bus:ptye2
[   13.110992] PM: Adding info for No Bus:ptye3
[   13.111063] PM: Adding info for No Bus:ptye4
[   13.111139] PM: Adding info for No Bus:ptye5
[   13.111209] PM: Adding info for No Bus:ptye6
[   13.111281] PM: Adding info for No Bus:ptye7
[   13.111353] PM: Adding info for No Bus:ptye8
[   13.111423] PM: Adding info for No Bus:ptye9
[   13.111492] PM: Adding info for No Bus:ptyea
[   13.111568] PM: Adding info for No Bus:ptyeb
[   13.111637] PM: Adding info for No Bus:ptyec
[   13.111710] PM: Adding info for No Bus:ptyed
[   13.111783] PM: Adding info for No Bus:ptyee
[   13.111852] PM: Adding info for No Bus:ptyef
[   13.111922] PM: Adding info for No Bus:ttyp0
[   13.111989] PM: Adding info for No Bus:ttyp1
[   13.112060] PM: Adding info for No Bus:ttyp2
[   13.112124] PM: Adding info for No Bus:ttyp3
[   13.112191] PM: Adding info for No Bus:ttyp4
[   13.112259] PM: Adding info for No Bus:ttyp5
[   13.112325] PM: Adding info for No Bus:ttyp6
[   13.112391] PM: Adding info for No Bus:ttyp7
[   13.112465] PM: Adding info for No Bus:ttyp8
[   13.112531] PM: Adding info for No Bus:ttyp9
[   13.112598] PM: Adding info for No Bus:ttypa
[   13.112666] PM: Adding info for No Bus:ttypb
[   13.112733] PM: Adding info for No Bus:ttypc
[   13.112801] PM: Adding info for No Bus:ttypd
[   13.112867] PM: Adding info for No Bus:ttype
[   13.112939] PM: Adding info for No Bus:ttypf
[   13.113006] PM: Adding info for No Bus:ttyq0
[   13.113072] PM: Adding info for No Bus:ttyq1
[   13.113144] PM: Adding info for No Bus:ttyq2
[   13.113215] PM: Adding info for No Bus:ttyq3
[   13.113283] PM: Adding info for No Bus:ttyq4
[   13.113356] PM: Adding info for No Bus:ttyq5
[   13.113425] PM: Adding info for No Bus:ttyq6
[   13.113492] PM: Adding info for No Bus:ttyq7
[   13.113558] PM: Adding info for No Bus:ttyq8
[   13.113628] PM: Adding info for No Bus:ttyq9
[   13.113695] PM: Adding info for No Bus:ttyqa
[   13.113762] PM: Adding info for No Bus:ttyqb
[   13.113837] PM: Adding info for No Bus:ttyqc
[   13.113905] PM: Adding info for No Bus:ttyqd
[   13.113974] PM: Adding info for No Bus:ttyqe
[   13.114041] PM: Adding info for No Bus:ttyqf
[   13.114110] PM: Adding info for No Bus:ttyr0
[   13.114178] PM: Adding info for No Bus:ttyr1
[   13.114253] PM: Adding info for No Bus:ttyr2
[   13.114321] PM: Adding info for No Bus:ttyr3
[   13.114388] PM: Adding info for No Bus:ttyr4
[   13.114459] PM: Adding info for No Bus:ttyr5
[   13.114530] PM: Adding info for No Bus:ttyr6
[   13.114601] PM: Adding info for No Bus:ttyr7
[   13.114670] PM: Adding info for No Bus:ttyr8
[   13.114742] PM: Adding info for No Bus:ttyr9
[   13.114810] PM: Adding info for No Bus:ttyra
[   13.114879] PM: Adding info for No Bus:ttyrb
[   13.114947] PM: Adding info for No Bus:ttyrc
[   13.115018] PM: Adding info for No Bus:ttyrd
[   13.115087] PM: Adding info for No Bus:ttyre
[   13.115165] PM: Adding info for No Bus:ttyrf
[   13.115236] PM: Adding info for No Bus:ttys0
[   13.115313] PM: Adding info for No Bus:ttys1
[   13.115382] PM: Adding info for No Bus:ttys2
[   13.115450] PM: Adding info for No Bus:ttys3
[   13.115522] PM: Adding info for No Bus:ttys4
[   13.115596] PM: Adding info for No Bus:ttys5
[   13.115671] PM: Adding info for No Bus:ttys6
[   13.115742] PM: Adding info for No Bus:ttys7
[   13.115811] PM: Adding info for No Bus:ttys8
[   13.115881] PM: Adding info for No Bus:ttys9
[   13.115954] PM: Adding info for No Bus:ttysa
[   13.116024] PM: Adding info for No Bus:ttysb
[   13.116101] PM: Adding info for No Bus:ttysc
[   13.116173] PM: Adding info for No Bus:ttysd
[   13.116244] PM: Adding info for No Bus:ttyse
[   13.116315] PM: Adding info for No Bus:ttysf
[   13.116386] PM: Adding info for No Bus:ttyt0
[   13.116455] PM: Adding info for No Bus:ttyt1
[   13.116525] PM: Adding info for No Bus:ttyt2
[   13.116605] PM: Adding info for No Bus:ttyt3
[   13.116677] PM: Adding info for No Bus:ttyt4
[   13.116749] PM: Adding info for No Bus:ttyt5
[   13.116820] PM: Adding info for No Bus:ttyt6
[   13.116890] PM: Adding info for No Bus:ttyt7
[   13.116962] PM: Adding info for No Bus:ttyt8
[   13.117039] PM: Adding info for No Bus:ttyt9
[   13.117110] PM: Adding info for No Bus:ttyta
[   13.117186] PM: Adding info for No Bus:ttytb
[   13.117258] PM: Adding info for No Bus:ttytc
[   13.117332] PM: Adding info for No Bus:ttytd
[   13.117417] PM: Adding info for No Bus:ttyte
[   13.117491] PM: Adding info for No Bus:ttytf
[   13.117567] PM: Adding info for No Bus:ttyu0
[   13.117642] PM: Adding info for No Bus:ttyu1
[   13.117718] PM: Adding info for No Bus:ttyu2
[   13.117791] PM: Adding info for No Bus:ttyu3
[   13.117862] PM: Adding info for No Bus:ttyu4
[   13.117936] PM: Adding info for No Bus:ttyu5
[   13.118013] PM: Adding info for No Bus:ttyu6
[   13.118084] PM: Adding info for No Bus:ttyu7
[   13.118159] PM: Adding info for No Bus:ttyu8
[   13.118232] PM: Adding info for No Bus:ttyu9
[   13.118307] PM: Adding info for No Bus:ttyua
[   13.118380] PM: Adding info for No Bus:ttyub
[   13.118454] PM: Adding info for No Bus:ttyuc
[   13.118532] PM: Adding info for No Bus:ttyud
[   13.118606] PM: Adding info for No Bus:ttyue
[   13.118681] PM: Adding info for No Bus:ttyuf
[   13.118753] PM: Adding info for No Bus:ttyv0
[   13.118826] PM: Adding info for No Bus:ttyv1
[   13.118902] PM: Adding info for No Bus:ttyv2
[   13.118980] PM: Adding info for No Bus:ttyv3
[   13.119053] PM: Adding info for No Bus:ttyv4
[   13.119128] PM: Adding info for No Bus:ttyv5
[   13.119200] PM: Adding info for No Bus:ttyv6
[   13.119279] PM: Adding info for No Bus:ttyv7
[   13.119353] PM: Adding info for No Bus:ttyv8
[   13.119428] PM: Adding info for No Bus:ttyv9
[   13.119508] PM: Adding info for No Bus:ttyva
[   13.119582] PM: Adding info for No Bus:ttyvb
[   13.119659] PM: Adding info for No Bus:ttyvc
[   13.119740] PM: Adding info for No Bus:ttyvd
[   13.119813] PM: Adding info for No Bus:ttyve
[   13.119887] PM: Adding info for No Bus:ttyvf
[   13.119968] PM: Adding info for No Bus:ttyw0
[   13.120042] PM: Adding info for No Bus:ttyw1
[   13.120115] PM: Adding info for No Bus:ttyw2
[   13.120191] PM: Adding info for No Bus:ttyw3
[   13.120266] PM: Adding info for No Bus:ttyw4
[   13.120346] PM: Adding info for No Bus:ttyw5
[   13.120425] PM: Adding info for No Bus:ttyw6
[   13.120505] PM: Adding info for No Bus:ttyw7
[   13.120582] PM: Adding info for No Bus:ttyw8
[   13.120659] PM: Adding info for No Bus:ttyw9
[   13.120733] PM: Adding info for No Bus:ttywa
[   13.120811] PM: Adding info for No Bus:ttywb
[   13.120887] PM: Adding info for No Bus:ttywc
[   13.120969] PM: Adding info for No Bus:ttywd
[   13.121044] PM: Adding info for No Bus:ttywe
[   13.121121] PM: Adding info for No Bus:ttywf
[   13.121198] PM: Adding info for No Bus:ttyx0
[   13.121273] PM: Adding info for No Bus:ttyx1
[   13.121350] PM: Adding info for No Bus:ttyx2
[   13.121426] PM: Adding info for No Bus:ttyx3
[   13.121512] PM: Adding info for No Bus:ttyx4
[   13.121590] PM: Adding info for No Bus:ttyx5
[   13.121666] PM: Adding info for No Bus:ttyx6
[   13.121744] PM: Adding info for No Bus:ttyx7
[   13.121822] PM: Adding info for No Bus:ttyx8
[   13.121901] PM: Adding info for No Bus:ttyx9
[   13.121984] PM: Adding info for No Bus:ttyxa
[   13.122062] PM: Adding info for No Bus:ttyxb
[   13.122138] PM: Adding info for No Bus:ttyxc
[   13.122215] PM: Adding info for No Bus:ttyxd
[   13.122293] PM: Adding info for No Bus:ttyxe
[   13.122369] PM: Adding info for No Bus:ttyxf
[   13.122445] PM: Adding info for No Bus:ttyy0
[   13.122528] PM: Adding info for No Bus:ttyy1
[   13.122605] PM: Adding info for No Bus:ttyy2
[   13.122684] PM: Adding info for No Bus:ttyy3
[   13.122766] PM: Adding info for No Bus:ttyy4
[   13.122844] PM: Adding info for No Bus:ttyy5
[   13.122929] PM: Adding info for No Bus:ttyy6
[   13.123015] PM: Adding info for No Bus:ttyy7
[   13.123095] PM: Adding info for No Bus:ttyy8
[   13.123172] PM: Adding info for No Bus:ttyy9
[   13.123251] PM: Adding info for No Bus:ttyya
[   13.123328] PM: Adding info for No Bus:ttyyb
[   13.123406] PM: Adding info for No Bus:ttyyc
[   13.123487] PM: Adding info for No Bus:ttyyd
[   13.123571] PM: Adding info for No Bus:ttyye
[   13.123650] PM: Adding info for No Bus:ttyyf
[   13.123734] PM: Adding info for No Bus:ttyz0
[   13.123812] PM: Adding info for No Bus:ttyz1
[   13.123890] PM: Adding info for No Bus:ttyz2
[   13.123969] PM: Adding info for No Bus:ttyz3
[   13.124053] PM: Adding info for No Bus:ttyz4
[   13.124136] PM: Adding info for No Bus:ttyz5
[   13.124216] PM: Adding info for No Bus:ttyz6
[   13.124294] PM: Adding info for No Bus:ttyz7
[   13.124375] PM: Adding info for No Bus:ttyz8
[   13.124454] PM: Adding info for No Bus:ttyz9
[   13.124533] PM: Adding info for No Bus:ttyza
[   13.124618] PM: Adding info for No Bus:ttyzb
[   13.124700] PM: Adding info for No Bus:ttyzc
[   13.124781] PM: Adding info for No Bus:ttyzd
[   13.124859] PM: Adding info for No Bus:ttyze
[   13.124942] PM: Adding info for No Bus:ttyzf
[   13.125022] PM: Adding info for No Bus:ttya0
[   13.125106] PM: Adding info for No Bus:ttya1
[   13.125188] PM: Adding info for No Bus:ttya2
[   13.125271] PM: Adding info for No Bus:ttya3
[   13.125352] PM: Adding info for No Bus:ttya4
[   13.125437] PM: Adding info for No Bus:ttya5
[   13.125517] PM: Adding info for No Bus:ttya6
[   13.125598] PM: Adding info for No Bus:ttya7
[   13.125685] PM: Adding info for No Bus:ttya8
[   13.125765] PM: Adding info for No Bus:ttya9
[   13.125845] PM: Adding info for No Bus:ttyaa
[   13.125927] PM: Adding info for No Bus:ttyab
[   13.126012] PM: Adding info for No Bus:ttyac
[   13.126094] PM: Adding info for No Bus:ttyad
[   13.126181] PM: Adding info for No Bus:ttyae
[   13.126262] PM: Adding info for No Bus:ttyaf
[   13.126345] PM: Adding info for No Bus:ttyb0
[   13.126431] PM: Adding info for No Bus:ttyb1
[   13.126511] PM: Adding info for No Bus:ttyb2
[   13.126593] PM: Adding info for No Bus:ttyb3
[   13.126675] PM: Adding info for No Bus:ttyb4
[   13.126764] PM: Adding info for No Bus:ttyb5
[   13.126848] PM: Adding info for No Bus:ttyb6
[   13.126931] PM: Adding info for No Bus:ttyb7
[   13.127013] PM: Adding info for No Bus:ttyb8
[   13.127094] PM: Adding info for No Bus:ttyb9
[   13.127178] PM: Adding info for No Bus:ttyba
[   13.127267] PM: Adding info for No Bus:ttybb
[   13.127349] PM: Adding info for No Bus:ttybc
[   13.127625] PM: Adding info for No Bus:ttybd
[   13.127710] PM: Adding info for No Bus:ttybe
[   13.127794] PM: Adding info for No Bus:ttybf
[   13.127874] PM: Adding info for No Bus:ttyc0
[   13.127954] PM: Adding info for No Bus:ttyc1
[   13.128040] PM: Adding info for No Bus:ttyc2
[   13.128122] PM: Adding info for No Bus:ttyc3
[   13.128202] PM: Adding info for No Bus:ttyc4
[   13.128286] PM: Adding info for No Bus:ttyc5
[   13.128366] PM: Adding info for No Bus:ttyc6
[   13.128448] PM: Adding info for No Bus:ttyc7
[   13.128535] PM: Adding info for No Bus:ttyc8
[   13.128617] PM: Adding info for No Bus:ttyc9
[   13.128698] PM: Adding info for No Bus:ttyca
[   13.128780] PM: Adding info for No Bus:ttycb
[   13.128864] PM: Adding info for No Bus:ttycc
[   13.128951] PM: Adding info for No Bus:ttycd
[   13.129034] PM: Adding info for No Bus:ttyce
[   13.129123] PM: Adding info for No Bus:ttycf
[   13.129206] PM: Adding info for No Bus:ttyd0
[   13.129290] PM: Adding info for No Bus:ttyd1
[   13.129372] PM: Adding info for No Bus:ttyd2
[   13.129455] PM: Adding info for No Bus:ttyd3
[   13.129538] PM: Adding info for No Bus:ttyd4
[   13.129631] PM: Adding info for No Bus:ttyd5
[   13.129715] PM: Adding info for No Bus:ttyd6
[   13.129799] PM: Adding info for No Bus:ttyd7
[   13.129883] PM: Adding info for No Bus:ttyd8
[   13.129967] PM: Adding info for No Bus:ttyd9
[   13.130052] PM: Adding info for No Bus:ttyda
[   13.130139] PM: Adding info for No Bus:ttydb
[   13.130228] PM: Adding info for No Bus:ttydc
[   13.130313] PM: Adding info for No Bus:ttydd
[   13.130398] PM: Adding info for No Bus:ttyde
[   13.130482] PM: Adding info for No Bus:ttydf
[   13.130567] PM: Adding info for No Bus:ttye0
[   13.130658] PM: Adding info for No Bus:ttye1
[   13.130749] PM: Adding info for No Bus:ttye2
[   13.130834] PM: Adding info for No Bus:ttye3
[   13.130918] PM: Adding info for No Bus:ttye4
[   13.131006] PM: Adding info for No Bus:ttye5
[   13.131092] PM: Adding info for No Bus:ttye6
[   13.131176] PM: Adding info for No Bus:ttye7
[   13.131261] PM: Adding info for No Bus:ttye8
[   13.131355] PM: Adding info for No Bus:ttye9
[   13.131440] PM: Adding info for No Bus:ttyea
[   13.131527] PM: Adding info for No Bus:ttyeb
[   13.131612] PM: Adding info for No Bus:ttyec
[   13.131698] PM: Adding info for No Bus:ttyed
[   13.131784] PM: Adding info for No Bus:ttyee
[   13.131874] PM: Adding info for No Bus:ttyef
[   13.131980] lp: driver loaded but no devices found
[   13.132076] PM: Adding info for No Bus:rtc
[   13.132122] Real Time Clock Driver v1.12ac
[   13.132196] PM: Adding info for No Bus:nvram
[   13.132237] Non-volatile memory driver v1.2
[   13.132305] Linux agpgart interface v0.102 (c) Dave Jones
[   13.132489] agpgart: Detected an Intel 945GM Chipset.
[   13.133619] agpgart: Detected 7932K stolen memory.
[   13.151130] PM: Adding info for No Bus:agpgart
[   13.151212] agpgart: AGP aperture is 256M @ 0xd0000000
[   13.151395] [drm] Initialized drm 1.1.0 20060810
[   13.151464] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
[   13.151554] intelfb: Version 0.9.4
[   13.151823] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
[   13.151964] intelfb: 00:02.0: Intel(R) 945GM, aperture size 256MB, stolen memory 7932kB
[   13.153998] intelfb: Non-CRT device is enabled ( LVDS port ).  Disabling mode switching.
[   13.154181] intelfb: Video mode must be programmed at boot time.
[   13.155845] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[   13.155960] PM: Adding info for platform:serial8250
[   13.156223] PM: Adding info for No Bus:ttyS0
[   13.156358] PM: Adding info for No Bus:ttyS1
[   13.156485] PM: Adding info for No Bus:ttyS2
[   13.156612] PM: Adding info for No Bus:ttyS3
[   13.157682] loop: loaded (max 8 devices)
[   13.157752] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
[   13.157822] e100: Copyright(c) 1999-2006 Intel Corporation
[   13.157996] PM: Adding info for No Bus:lo
[   13.158157] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[   13.158229] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[   13.158371] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0k
[   13.158444] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[   13.158573] Linux video capture interface: v2.00
[   13.158687] saa7130/34: v4l2 driver version 0.2.14 loaded
[   13.158889] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[   13.158962] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[   13.159078] ICH7: IDE controller at PCI slot 0000:00:1f.1
[   13.159157] ACPI: PCI Interrupt 0000:00:1f.1[C] -> GSI 16 (level, low) -> IRQ 20
[   13.159296] ICH7: chipset revision 2
[   13.159362] ICH7: not 100% native mode: will probe irqs later
[   13.159442]     ide0: BM-DMA at 0x1810-0x1817, BIOS settings: hda:DMA, hdb:pio
[   13.159629] Probing IDE interface ide0...
[   13.180600] Clocksource tsc unstable (delta = -226791774 ns)
[   13.188109] hda: HL-DT-STCD-RW/DVD DRIVE GCC-4246N, ATAPI CD/DVD-ROM drive
[   13.188354] PM: Adding info for No Bus:ide0
[   13.195090] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[   13.195238] PM: Adding info for ide:0.0
[   13.195851] hda: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
[   13.196251] Uniform CD-ROM driver Revision: 3.20
[   13.198085] ahci 0000:00:1f.2: version 2.1
[   13.198115] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
[   13.211322] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[   13.211335] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x1 impl SATA mode
[   13.211428] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
[   13.211627] ata1: SATA max UDMA/133 cmd 0xf8844500 ctl 0x00000000 bmdma 0x00000000 irq 20
[   13.211798] ata2: SATA max UDMA/133 cmd 0xf8844580 ctl 0x00000000 bmdma 0x00000000 irq 20
[   13.211961] ata3: SATA max UDMA/133 cmd 0xf8844600 ctl 0x00000000 bmdma 0x00000000 irq 20
[   13.212144] ata4: SATA max UDMA/133 cmd 0xf8844680 ctl 0x00000000 bmdma 0x00000000 irq 20
[   13.212249] scsi0 : ahci
[   13.212335] PM: Adding info for No Bus:host0
[   13.263765] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   13.275332] ata1.00: ATA-7: HTS541080G9SA00, MB4IC60H, max UDMA/100
[   13.275409] ata1.00: 156301488 sectors, multi 16: LBA48 
[   13.278283] ata1.00: configured for UDMA/100
[   13.278367] scsi1 : ahci
[   13.278453] PM: Adding info for No Bus:host1
[   13.282997] ata2: SATA link down (SStatus 0 SControl 0)
[   13.283087] scsi2 : ahci
[   13.283172] PM: Adding info for No Bus:host2
[   13.287592] ata3: SATA link down (SStatus 0 SControl 0)
[   13.287680] scsi3 : ahci
[   13.287764] PM: Adding info for No Bus:host3
[   13.292180] ata4: SATA link down (SStatus 0 SControl 0)
[   13.292290] PM: Adding info for No Bus:target0:0:0
[   13.292418] scsi 0:0:0:0: Direct-Access     ATA      HTS541080G9SA00  MB4I PQ: 0 ANSI: 5
[   13.292514] PM: Adding info for scsi:0:0:0:0
[   13.292695] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[   13.292784] sda: Write Protect is off
[   13.293651] sda: Mode Sense: 00 3a 00 00
[   13.293677] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   13.293825] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[   13.293910] sda: Write Protect is off
[   13.293978] sda: Mode Sense: 00 3a 00 00
[   13.294002] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   13.294093]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[   13.677351] sd 0:0:0:0: Attached scsi disk sda
[   13.677531] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   13.678160] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 21
[   13.678308] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[   13.678314] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[   13.678465] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[   13.678591] ehci_hcd 0000:00:1d.7: debug port 1
[   13.678664] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[   13.678679] ehci_hcd 0000:00:1d.7: irq 21, io mem 0xee444000
[   13.682644] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[   13.682766] PM: Adding info for usb:usb1
[   13.682868] PM: Adding info for No Bus:usbdev1.1_ep00
[   13.682923] usb usb1: configuration #1 chosen from 1 choice
[   13.683006] PM: Adding info for usb:1-0:1.0
[   13.683063] hub 1-0:1.0: USB hub found
[   13.683137] hub 1-0:1.0: 8 ports detected
[   13.684895] PM: Adding info for No Bus:usbdev1.1_ep81
[   13.685006] PM: Adding info for No Bus:usbdev1.1
[   13.685098] USB Universal Host Controller Interface driver v3.0
[   13.685314] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
[   13.685457] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[   13.685463] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[   13.685594] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[   13.685710] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001820
[   13.685842] PM: Adding info for usb:usb2
[   13.685932] PM: Adding info for No Bus:usbdev2.1_ep00
[   13.685985] usb usb2: configuration #1 chosen from 1 choice
[   13.686068] PM: Adding info for usb:2-0:1.0
[   13.686124] hub 2-0:1.0: USB hub found
[   13.686199] hub 2-0:1.0: 2 ports detected
[   13.694955] PM: Adding info for No Bus:usbdev2.1_ep81
[   13.695056] PM: Adding info for No Bus:usbdev2.1
[   13.695152] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 22
[   13.695297] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[   13.695303] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[   13.695436] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[   13.695557] uhci_hcd 0000:00:1d.1: irq 22, io base 0x00001840
[   13.695691] PM: Adding info for usb:usb3
[   13.695784] PM: Adding info for No Bus:usbdev3.1_ep00
[   13.695835] usb usb3: configuration #1 chosen from 1 choice
[   13.695918] PM: Adding info for usb:3-0:1.0
[   13.695974] hub 3-0:1.0: USB hub found
[   13.696048] hub 3-0:1.0: 2 ports detected
[   13.712888] PM: Adding info for No Bus:usbdev3.1_ep81
[   13.712987] PM: Adding info for No Bus:usbdev3.1
[   13.713083] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 23
[   13.713227] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[   13.713233] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[   13.713366] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[   13.713489] uhci_hcd 0000:00:1d.2: irq 23, io base 0x00001860
[   13.713622] PM: Adding info for usb:usb4
[   13.713717] PM: Adding info for No Bus:usbdev4.1_ep00
[   13.713775] usb usb4: configuration #1 chosen from 1 choice
[   13.713858] PM: Adding info for usb:4-0:1.0
[   13.713916] hub 4-0:1.0: USB hub found
[   13.713990] hub 4-0:1.0: 2 ports detected
[   13.736126] PM: Adding info for No Bus:usbdev4.1_ep81
[   13.736233] PM: Adding info for No Bus:usbdev4.1
[   13.736328] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 21
[   13.736474] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[   13.736479] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[   13.736630] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[   13.736748] uhci_hcd 0000:00:1d.3: irq 21, io base 0x00001880
[   13.736880] PM: Adding info for usb:usb5
[   13.736974] PM: Adding info for No Bus:usbdev5.1_ep00
[   13.737028] usb usb5: configuration #1 chosen from 1 choice
[   13.737110] PM: Adding info for usb:5-0:1.0
[   13.737168] hub 5-0:1.0: USB hub found
[   13.737242] hub 5-0:1.0: 2 ports detected
[   13.761788] PM: Adding info for No Bus:usbdev5.1_ep81
[   13.761892] PM: Adding info for No Bus:usbdev5.1
[   13.762004] Initializing USB Mass Storage driver...
[   13.825063] usb 5-2: new full speed USB device using uhci_hcd and address 2
[   13.867336] PM: Adding info for usb:5-2
[   13.867469] PM: Adding info for No Bus:usbdev5.2_ep00
[   13.867526] usb 5-2: configuration #1 chosen from 1 choice
[   13.868024] PM: Adding info for usb:5-2:1.0
[   13.868141] PM: Adding info for No Bus:usbdev5.2_ep81
[   13.868207] PM: Adding info for No Bus:usbdev5.2_ep02
[   13.868273] PM: Adding info for No Bus:usbdev5.2_ep83
[   13.868349] PM: Adding info for No Bus:usbdev5.2
[   13.868433] usbcore: registered new interface driver usb-storage
[   13.868508] USB Mass Storage support registered.
[   13.868704] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[   13.868855] PM: Adding info for platform:i8042
[   13.876701] serio: i8042 KBD port at 0x60,0x64 irq 1
[   13.876775] serio: i8042 AUX port at 0x60,0x64 irq 12
[   13.876879] PM: Adding info for serio:serio0
[   13.876948] PM: Adding info for No Bus:psaux
[   13.877001] PM: Adding info for serio:serio1
[   13.877047] mice: PS/2 mouse device common for all mice
[   13.877319] PM: Adding info for No Bus:i2c-9191
[   13.877447] Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Tue Mar 06 13:10:00 2007 UTC).
[   13.877548] PM: Adding info for No Bus:timer
[   13.877608] PM: Adding info for No Bus:sequencer
[   13.877655] PM: Adding info for No Bus:sequencer2
[   13.877796] PM: Adding info for No Bus:seq
[   13.877997] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 22
[   13.878148] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[   13.880151] input: AT Translated Set 2 keyboard as /class/input/input3
[   13.986993] PM: Adding info for No Bus:pcmC0D1p
[   13.987092] PM: Adding info for No Bus:adsp
[   13.987154] PM: Adding info for No Bus:pcmC0D0p
[   13.987216] PM: Adding info for No Bus:pcmC0D0c
[   13.987275] PM: Adding info for No Bus:dsp
[   13.987338] PM: Adding info for No Bus:audio
[   13.987406] PM: Adding info for No Bus:controlC0
[   13.987469] PM: Adding info for No Bus:mixer
[   13.992479] ALSA device list:
[   13.992551]   #0: HDA Intel at 0xee240000 irq 22
[   13.992660] nf_conntrack version 0.5.0 (7168 buckets, 57344 max)
[   13.992935] ip_tables: (C) 2000-2006 Netfilter Core Team
[   13.993016] TCP cubic registered
[   13.993104] NET: Registered protocol family 1
[   13.993174] NET: Registered protocol family 17
[   13.993246] ieee80211: 802.11 data/management/control stack, git-1.1.13
[   13.993320] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
[   13.993410] ieee80211_crypt: registered algorithm 'NULL'
[   13.993415] ieee80211_crypt: registered algorithm 'WEP'
[   13.993419] ieee80211_crypt: registered algorithm 'CCMP'
[   13.993422] ieee80211_crypt: registered algorithm 'TKIP'
[   13.993431] Starting balanced_irq
[   13.993511] Using IPI No-Shortcut mode
[   13.993717] swsusp: Resume From Partition /dev/sda6
[   13.993721] PM: Checking swsusp image.
[   13.993918] PM: Resume from disk failed.
[   14.017423] EXT3-fs: INFO: recovery required on readonly filesystem.
[   14.017501] EXT3-fs: write access will be enabled during recovery.
[   17.727159] kjournald starting.  Commit interval 5 seconds
[   17.727250] EXT3-fs: recovery complete.
[   17.728176] EXT3-fs: mounted filesystem with ordered data mode.
[   17.728350] VFS: Mounted root (ext3 filesystem) readonly.
[   17.728560] Freeing unused kernel memory: 184k freed
[   17.728683] Write protecting the kernel read-only data: 902k
[   17.970740] PM: Adding info for No Bus:vcs1
[   17.992460] PM: Adding info for No Bus:vcsa1
[   18.179032] PM: Removing info for No Bus:vcs1
[   18.179128] PM: Removing info for No Bus:vcsa1
[   18.179209] PM: Adding info for No Bus:vcs1
[   18.179261] PM: Adding info for No Bus:vcsa1
[   18.179333] PM: Removing info for No Bus:vcs1
[   18.179383] PM: Removing info for No Bus:vcsa1
[   18.225405] PM: Adding info for No Bus:vcs1
[   18.225711] PM: Adding info for No Bus:vcsa1
[   23.400049] PM: Adding info for No Bus:vcs2
[   23.400132] PM: Adding info for No Bus:vcsa2
[   23.400548] PM: Removing info for No Bus:vcs2
[   23.400609] PM: Removing info for No Bus:vcsa2
[   23.401050] PM: Adding info for No Bus:vcs3
[   23.401146] PM: Adding info for No Bus:vcsa3
[   23.402118] PM: Removing info for No Bus:vcs3
[   23.402181] PM: Removing info for No Bus:vcsa3
[   23.402642] PM: Adding info for No Bus:vcs4
[   23.402714] PM: Adding info for No Bus:vcsa4
[   23.403375] PM: Removing info for No Bus:vcs4
[   23.403455] PM: Removing info for No Bus:vcsa4
[   23.411722] PM: Adding info for No Bus:vcs5
[   23.411824] PM: Adding info for No Bus:vcsa5
[   23.412264] PM: Removing info for No Bus:vcs5
[   23.412320] PM: Removing info for No Bus:vcsa5
[   23.412819] PM: Adding info for No Bus:vcs6
[   23.412918] PM: Adding info for No Bus:vcsa6
[   23.413895] PM: Removing info for No Bus:vcs6
[   23.413965] PM: Removing info for No Bus:vcsa6
[   26.832471] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
[   26.832551] Copyright (c) 1999-2006 Intel Corporation.
[   26.832761] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[   26.832976] PCI: Setting latency timer of device 0000:02:00.0 to 64
[   26.913367] e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:16:41:54:6c:47
[   26.992675] PM: Adding info for No Bus:eth0
[   26.992799] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[   27.310074] Adding 1951824k swap on /dev/sda6.  Priority:-1 extents:1 across:1951824k
[   27.370807] EXT3 FS on sda3, internal journal
[   27.655673] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04793/0x300000
[   27.655784] serio: Synaptics pass-through port at isa0060/serio1/input0
[   27.698500] input: SynPS/2 Synaptics TouchPad as /class/input/input4
[   27.702092] PM: Adding info for serio:serio2
[   28.875095] NTFS volume version 3.1.
[   28.875172] NTFS-fs warning (device sda1): load_system_files(): Unsupported volume flags 0x4000 encountered.
[   28.875267] NTFS-fs error (device sda1): load_system_files(): Volume has unsupported flags set.  Mounting read-only.  Run chkdsk and mount in Windows.
[   31.166984] PM: Adding info for No Bus:vcs2
[   31.167020] PM: Adding info for No Bus:vcsa2
[   31.172935] PM: Removing info for No Bus:vcs2
[   31.172964] PM: Removing info for No Bus:vcsa2
[   31.176248] PM: Adding info for No Bus:vcs3
[   31.176274] PM: Adding info for No Bus:vcsa3
[   31.185974] PM: Removing info for No Bus:vcs3
[   31.186001] PM: Removing info for No Bus:vcsa3
[   31.188943] PM: Adding info for No Bus:vcs4
[   31.188971] PM: Adding info for No Bus:vcsa4
[   31.195018] PM: Removing info for No Bus:vcs4
[   31.195045] PM: Removing info for No Bus:vcsa4
[   31.196385] PM: Adding info for No Bus:vcs5
[   31.196413] PM: Adding info for No Bus:vcsa5
[   31.202363] PM: Removing info for No Bus:vcs5
[   31.202392] PM: Removing info for No Bus:vcsa5
[   31.203990] PM: Adding info for No Bus:vcs6
[   31.204018] PM: Adding info for No Bus:vcsa6
[   31.209574] PM: Removing info for No Bus:vcs6
[   31.209602] PM: Removing info for No Bus:vcsa6
[   31.232924] PM: Adding info for No Bus:vcs2
[   31.232957] PM: Adding info for No Bus:vcsa2
[   31.238956] PM: Removing info for No Bus:vcs2
[   31.238986] PM: Removing info for No Bus:vcsa2
[   31.246877] PM: Adding info for No Bus:vcs3
[   31.246907] PM: Adding info for No Bus:vcsa3
[   31.252421] PM: Removing info for No Bus:vcs3
[   31.252450] PM: Removing info for No Bus:vcsa3
[   31.260613] PM: Adding info for No Bus:vcs4
[   31.260642] PM: Adding info for No Bus:vcsa4
[   31.266175] PM: Removing info for No Bus:vcs4
[   31.266204] PM: Removing info for No Bus:vcsa4
[   31.272902] PM: Adding info for No Bus:vcs5
[   31.272932] PM: Adding info for No Bus:vcsa5
[   31.283083] PM: Removing info for No Bus:vcs5
[   31.283111] PM: Removing info for No Bus:vcsa5
[   31.289866] PM: Adding info for No Bus:vcs6
[   31.289896] PM: Adding info for No Bus:vcsa6
[   31.295994] PM: Removing info for No Bus:vcs6
[   31.296024] PM: Removing info for No Bus:vcsa6
[   31.466596] PM: Adding info for No Bus:vcs2
[   31.466629] PM: Adding info for No Bus:vcsa2
[   31.467270] PM: Removing info for No Bus:vcs2
[   31.467295] PM: Removing info for No Bus:vcsa2
[   31.467736] PM: Adding info for No Bus:vcs3
[   31.467760] PM: Adding info for No Bus:vcsa3
[   31.468390] PM: Removing info for No Bus:vcs3
[   31.468414] PM: Removing info for No Bus:vcsa3
[   31.468858] PM: Adding info for No Bus:vcs4
[   31.468882] PM: Adding info for No Bus:vcsa4
[   31.469507] PM: Removing info for No Bus:vcs4
[   31.469529] PM: Removing info for No Bus:vcsa4
[   31.469966] PM: Adding info for No Bus:vcs5
[   31.469988] PM: Adding info for No Bus:vcsa5
[   31.470621] PM: Removing info for No Bus:vcs5
[   31.470644] PM: Removing info for No Bus:vcsa5
[   31.471081] PM: Adding info for No Bus:vcs6
[   31.471101] PM: Adding info for No Bus:vcsa6
[   31.471742] PM: Removing info for No Bus:vcs6
[   31.471768] PM: Removing info for No Bus:vcsa6
[   31.496053] PM: Removing info for No Bus:vcs1
[   31.496128] PM: Removing info for No Bus:vcsa1
[   31.532098] PM: Adding info for No Bus:vcs1
[   31.532132] PM: Adding info for No Bus:vcsa1
[   31.532977] PM: Removing info for No Bus:vcs1
[   31.533006] PM: Removing info for No Bus:vcsa1
[   31.533315] PM: Adding info for No Bus:vcs1
[   31.533335] PM: Adding info for No Bus:vcsa1
[   31.533661] PM: Removing info for No Bus:vcs1
[   31.533681] PM: Removing info for No Bus:vcsa1
[   31.533960] PM: Adding info for No Bus:vcs1
[   31.533980] PM: Adding info for No Bus:vcsa1
[   31.534340] PM: Removing info for No Bus:vcs1
[   31.534360] PM: Removing info for No Bus:vcsa1
[   31.534885] PM: Adding info for No Bus:vcs1
[   31.534905] PM: Adding info for No Bus:vcsa1
[   32.416823] speedstep-centrino with X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated.
[   32.416827]  Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead.
[   32.417502] speedstep-centrino with X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated.
[   32.417506]  Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead.
[   32.875260] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[   33.137905] input: TPPS/2 IBM TrackPoint as /class/input/input5
[   38.584256] PM: Adding info for No Bus:vcs7
[   38.584286] PM: Adding info for No Bus:vcsa7
[   38.750942] PM: Removing info for No Bus:vcs1
[   38.750976] PM: Removing info for No Bus:vcsa1
[   38.847994] PM: Adding info for No Bus:vcs1
[   38.848020] PM: Adding info for No Bus:vcsa1
[   38.848054] PM: Adding info for No Bus:vcs2
[   38.848072] PM: Adding info for No Bus:vcsa2
[   38.848450] PM: Adding info for No Bus:vcs3
[   38.848469] PM: Adding info for No Bus:vcsa3
[   38.851444] PM: Adding info for No Bus:vcs4
[   38.851472] PM: Adding info for No Bus:vcsa4
[   38.853065] PM: Adding info for No Bus:vcs5
[   38.853088] PM: Adding info for No Bus:vcsa5
[   38.854591] PM: Adding info for No Bus:vcs6
[   38.854611] PM: Adding info for No Bus:vcsa6
[   39.933577] [drm] Initialized i915 1.6.0 20060119 on minor 0
[   55.358317] PM: Preparing system for mem sleep
[   55.359372] Stopping tasks ... done.
[   55.379164] Suspending console(s)
[   55.379239] psmouse serio2: suspend
[   55.408772] psmouse serio1: suspend
[   55.445047] atkbd serio0: suspend
[   55.496382] i8042 i8042: suspend
[   55.496562] usb 5-2:1.0: suspend
[   55.496567] usb 5-2: suspend, may wakeup
[   55.496573] hub 5-0:1.0: suspend
[   55.496577] usb usb5: suspend, may wakeup
[   55.496602] hub 4-0:1.0: suspend
[   55.496606] usb usb4: suspend, may wakeup
[   55.496614] hub 3-0:1.0: suspend
[   55.496618] usb usb3: suspend, may wakeup
[   55.496625] hub 2-0:1.0: suspend
[   55.496629] usb usb2: suspend, may wakeup
[   55.496635] hub 1-0:1.0: suspend
[   55.496639] usb usb1: suspend, may wakeup
[   55.496674] sd 0:0:0:0: suspend
[   55.936052] ide-cdrom 0.0: suspend
[   55.936080] serial8250 serial8250: suspend
[   55.936419] platform vesafb.0: suspend
[   55.936424] pci_express 0000:00:1c.3:pcie03: suspend
[   55.936428] pci_express 0000:00:1c.3:pcie02: suspend
[   55.936432] pci_express 0000:00:1c.3:pcie00: suspend
[   55.936436] pci_express 0000:00:1c.2:pcie03: suspend
[   55.936439] pci_express 0000:00:1c.2:pcie02: suspend
[   55.936443] pci_express 0000:00:1c.2:pcie00: suspend
[   55.936447] pci_express 0000:00:1c.1:pcie03: suspend
[   55.936450] pci_express 0000:00:1c.1:pcie02: suspend
[   55.936454] pci_express 0000:00:1c.1:pcie00: suspend
[   55.936458] pci_express 0000:00:1c.0:pcie03: suspend
[   55.936462] pci_express 0000:00:1c.0:pcie02: suspend
[   55.936466] pci_express 0000:00:1c.0:pcie00: suspend
[   55.936471] platform pcspkr: suspend
[   55.936481] pnp 00:0a: suspend
[   55.936485] i8042 aux 00:09: suspend
[   55.936488] i8042 kbd 00:08: suspend
[   55.936492] pnp 00:07: suspend
[   55.936495] pnp 00:06: suspend
[   55.936498] pnp 00:05: suspend
[   55.936501] pnp 00:04: suspend
[   55.936504] pnp 00:03: suspend
[   55.936507] system 00:02: suspend
[   55.936510] pnp 00:01: suspend
[   55.936513] system 00:00: suspend
[   55.936518] pci 0000:15:00.0: suspend
[   55.936570] pci 0000:03:00.0: suspend
[   55.936799] e1000 0000:02:00.0: suspend
[   55.937811] ACPI: PCI interrupt for device 0000:02:00.0 disabled
[   55.938078] pci 0000:00:1f.3: suspend
[   55.938117] ahci 0000:00:1f.2: suspend
[   55.938276] ACPI: PCI interrupt for device 0000:00:1f.2 disabled
[   55.938602] PIIX_IDE 0000:00:1f.1: suspend
[   55.938636] pci 0000:00:1f.0: suspend
[   55.938683] pci 0000:00:1e.0: suspend
[   55.938719] ehci_hcd 0000:00:1d.7: suspend, may wakeup
[   55.938770] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
[   55.939800] uhci_hcd 0000:00:1d.3: suspend
[   55.939837] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
[   55.939842] uhci_hcd 0000:00:1d.2: suspend
[   55.939874] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
[   55.939878] uhci_hcd 0000:00:1d.1: suspend
[   55.939911] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
[   55.939915] uhci_hcd 0000:00:1d.0: suspend
[   55.939947] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
[   55.939951] pcieport-driver 0000:00:1c.3: suspend
[   55.940002] pcieport-driver 0000:00:1c.2: suspend
[   55.940050] pcieport-driver 0000:00:1c.1: suspend
[   55.940100] pcieport-driver 0000:00:1c.0: suspend
[   55.940151] HDA Intel 0000:00:1b.0: suspend
[   55.949178] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
[   55.949537] pci 0000:00:02.1: suspend
[   55.949557] pci 0000:00:02.0: suspend
[   55.949573] agpgart-intel 0000:00:00.0: suspend
[   55.949588] thermal thermal:02: suspend
[   55.949592] thermal thermal:01: suspend
[   55.949595] acpi thermal:00: suspend
[   55.949599] acpi device:22: suspend
[   55.949602] acpi device:21: suspend
[   55.949606] acpi device:20: suspend
[   55.949609] acpi device:1f: suspend
[   55.949612] acpi device:1e: suspend
[   55.949615] acpi device:1d: suspend
[   55.949619] acpi device:1c: suspend
[   55.949623] acpi device:1b: suspend
[   55.949626] acpi device:1a: suspend
[   55.949629] acpi device:19: suspend
[   55.949632] acpi device:18: suspend
[   55.949636] acpi device:17: suspend
[   55.949639] acpi device:16: suspend
[   55.949642] acpi device:15: suspend
[   55.949646] acpi device:14: suspend
[   55.949649] acpi device:13: suspend
[   55.949652] acpi bay:00: suspend
[   55.949656] acpi device:12: suspend
[   55.949659] acpi device:11: suspend
[   55.949662] acpi device:10: suspend
[   55.949666] acpi device:0f: suspend
[   55.949669] acpi device:0e: suspend
[   55.949673] acpi device:0d: suspend
[   55.949676] acpi device:0c: suspend
[   55.949679] acpi device:0b: suspend
[   55.949683] acpi device:0a: suspend
[   55.949686] acpi device:09: suspend
[   55.949689] acpi device:08: suspend
[   55.949693] acpi device:07: suspend
[   55.949696] acpi device:06: suspend
[   55.949700] video video:01: suspend
[   55.949703] acpi device:05: suspend
[   55.949707] acpi device:04: suspend
[   55.949710] acpi device:03: suspend
[   55.949713] acpi device:02: suspend
[   55.949716] video video:00: suspend
[   55.949720] ibm_hotkey IBM0068:00: suspend
[   55.949724] ac ACPI0003:00: suspend
[   55.949728] battery PNP0C0A:00: suspend
[   55.949732] power power_resource:00: suspend
[   55.949735] ec PNP0C09:00: suspend
[   55.949739] acpi IBM0071:00: suspend
[   55.949742] acpi IBM0057:00: suspend
[   55.949746] acpi PNP0303:00: suspend
[   55.949749] acpi PNP0B00:00: suspend
[   55.949752] acpi PNP0C04:00: suspend
[   55.949756] acpi PNP0800:00: suspend
[   55.949759] acpi PNP0200:00: suspend
[   55.949763] acpi PNP0103:00: suspend
[   55.949766] acpi PNP0100:00: suspend
[   55.949769] acpi PNP0000:00: suspend
[   55.949773] acpi PNP0C02:00: suspend
[   55.949776] acpi device:01: suspend
[   55.949779] pci_root PNP0A08:00: suspend
[   55.949783] button PNP0C0E:00: suspend
[   55.949787] button PNP0C0D:00: suspend
[   55.949790] acpi PNP0C01:00: suspend
[   55.949795] pci_link PNP0C0F:07: suspend
[   55.949798] pci_link PNP0C0F:06: suspend
[   55.949802] pci_link PNP0C0F:05: suspend
[   55.949806] pci_link PNP0C0F:04: suspend
[   55.949809] pci_link PNP0C0F:03: suspend
[   55.949812] pci_link PNP0C0F:02: suspend
[   55.949816] pci_link PNP0C0F:01: suspend
[   55.949820] pci_link PNP0C0F:00: suspend
[   55.949823] acpi device:00: suspend
[   55.949827] processor ACPI0007:01: suspend
[   55.949830] processor ACPI0007:00: suspend
[   55.949834] button button_power:00: suspend
[   55.949837] acpi acpi_system:00: suspend
[   55.949843] platform dock.0: suspend
[   55.949847] Disabling non-boot CPUs ...
[   55.951806] Breaking affinity for irq 20
[   56.059979] CPU 1 is now offline
[   56.059984] SMP alternatives: switching to UP code
[   56.060782] CPU1 is down
[   56.060786] PM: Entering mem sleep
[   56.060804] serial8250 serial8250: LATE suspend
[   56.060898] platform vesafb.0: LATE suspend
[   56.060904] platform pcspkr: LATE suspend
[   56.060911] pci 0000:15:00.0: LATE suspend
[   56.060914] pci 0000:03:00.0: LATE suspend
[   56.060917] e1000 0000:02:00.0: LATE suspend
[   56.060920] pci 0000:00:1f.3: LATE suspend
[   56.060923] PIIX_IDE 0000:00:1f.1: LATE suspend
[   56.060927] pci 0000:00:1f.0: LATE suspend
[   56.060930] pci 0000:00:1e.0: LATE suspend
[   56.060934] pcieport-driver 0000:00:1c.3: LATE suspend
[   56.060937] pcieport-driver 0000:00:1c.2: LATE suspend
[   56.060941] pcieport-driver 0000:00:1c.1: LATE suspend
[   56.060944] pcieport-driver 0000:00:1c.0: LATE suspend
[   56.060948] HDA Intel 0000:00:1b.0: LATE suspend
[   56.060951] pci 0000:00:02.1: LATE suspend
[   56.060954] pci 0000:00:02.0: LATE suspend
[   56.060957] agpgart-intel 0000:00:00.0: LATE suspend
[   56.060972] platform dock.0: LATE suspend
[    2.134505] Intel machine check architecture supported.
[    2.134518] Intel machine check reporting enabled on CPU#0.
[    2.134529] Back to C!
[    2.134873] platform dock.0: EARLY resume
[    2.134887] agpgart-intel 0000:00:00.0: EARLY resume
[    2.134892] pci 0000:00:02.0: EARLY resume
[    2.134895] pci 0000:00:02.1: EARLY resume
[    2.134899] HDA Intel 0000:00:1b.0: EARLY resume
[    2.134902] pcieport-driver 0000:00:1c.0: EARLY resume
[    2.134906] pcieport-driver 0000:00:1c.1: EARLY resume
[    2.134910] pcieport-driver 0000:00:1c.2: EARLY resume
[    2.134913] pcieport-driver 0000:00:1c.3: EARLY resume
[    2.134917] uhci_hcd 0000:00:1d.0: EARLY resume
[    2.134920] uhci_hcd 0000:00:1d.1: EARLY resume
[    2.134923] uhci_hcd 0000:00:1d.2: EARLY resume
[    2.134927] uhci_hcd 0000:00:1d.3: EARLY resume
[    2.134930] ehci_hcd 0000:00:1d.7: EARLY resume
[    2.134933] pci 0000:00:1e.0: EARLY resume
[    2.134937] pci 0000:00:1f.0: EARLY resume
[    2.134940] PIIX_IDE 0000:00:1f.1: EARLY resume
[    2.134944] ahci 0000:00:1f.2: EARLY resume
[    2.134947] pci 0000:00:1f.3: EARLY resume
[    2.134950] e1000 0000:02:00.0: EARLY resume
[    2.134953] pci 0000:03:00.0: EARLY resume
[    2.134956] pci 0000:15:00.0: EARLY resume
[    2.134967] platform pcspkr: EARLY resume
[    2.134972] platform vesafb.0: EARLY resume
[    2.135061] serial8250 serial8250: EARLY resume
[    2.135071] i8042 i8042: EARLY resume
[    2.135129] PM: Finishing wakeup.
[    2.135132] Enabling non-boot CPUs ...
[    2.136537] SMP alternatives: switching to SMP code
[    2.136740] Booting processor 1/1 eip 3000
[    2.147701] Initializing CPU#1
[    2.959150] Calibrating delay using timer specific routine.. 20089.12 BogoMIPS (lpj=100445639)
[    2.959161] CPU: After generic identify, caps: bfe9fbff 00000000 00000000 00000000 0000c1a9 00000000 00000000
[    2.959170] monitor/mwait feature present.
[    2.959175] CPU: L1 I cache: 32K, L1 D cache: 32K
[    2.959179] CPU: L2 cache: 2048K
[    2.959183] CPU: Physical Processor ID: 0
[    2.959185] CPU: Processor Core ID: 1
[    2.959189] CPU: After all inits, caps: bfe9fbff 00000000 00000000 00002940 0000c1a9 00000000 00000000
[    2.959198] Intel machine check architecture supported.
[    2.959208] Intel machine check reporting enabled on CPU#1.
[    2.959508] CPU1: Intel Genuine Intel(R) CPU           T2400  @ 1.83GHz stepping 08
[    2.960293] speedstep-centrino with X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated.
[    2.960296]  Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead.
[    2.960336] CPU1 is up
[    3.239195] platform dock.0: resuming
[    3.239200] acpi acpi_system:00: resuming
[    3.239202] button button_power:00: resuming
[    3.239204] processor ACPI0007:00: resuming
[    3.239206] processor ACPI0007:01: resuming
[    3.239208] acpi device:00: resuming
[    3.239210] pci_link PNP0C0F:00: resuming
[    3.239212] pci_link PNP0C0F:01: resuming
[    3.239214] pci_link PNP0C0F:02: resuming
[    3.239216] pci_link PNP0C0F:03: resuming
[    3.239218] pci_link PNP0C0F:04: resuming
[    3.239220] pci_link PNP0C0F:05: resuming
[    3.239222] pci_link PNP0C0F:06: resuming
[    3.239224] pci_link PNP0C0F:07: resuming
[    3.239226] acpi PNP0C01:00: resuming
[    3.239228] button PNP0C0D:00: resuming
[    3.239230] button PNP0C0E:00: resuming
[    3.239232] pci_root PNP0A08:00: resuming
[    3.239234] acpi device:01: resuming
[    3.239236] acpi PNP0C02:00: resuming
[    3.239237] acpi PNP0000:00: resuming
[    3.239239] acpi PNP0100:00: resuming
[    3.239241] acpi PNP0103:00: resuming
[    3.239243] acpi PNP0200:00: resuming
[    3.239246] acpi PNP0800:00: resuming
[    3.239247] acpi PNP0C04:00: resuming
[    3.239249] acpi PNP0B00:00: resuming
[    3.239251] acpi PNP0303:00: resuming
[    3.239253] acpi IBM0057:00: resuming
[    3.239255] acpi IBM0071:00: resuming
[    3.239257] ec PNP0C09:00: resuming
[    3.239259] power power_resource:00: resuming
[    3.239440] battery PNP0C0A:00: resuming
[    3.239617] ac ACPI0003:00: resuming
[    3.239621] ibm_hotkey IBM0068:00: resuming
[    3.239623] video video:00: resuming
[    3.239625] acpi device:02: resuming
[    3.239627] acpi device:03: resuming
[    3.239629] acpi device:04: resuming
[    3.239631] acpi device:05: resuming
[    3.239632] video video:01: resuming
[    3.239634] acpi device:06: resuming
[    3.239636] acpi device:07: resuming
[    3.239638] acpi device:08: resuming
[    3.239639] acpi device:09: resuming
[    3.239641] acpi device:0a: resuming
[    3.239643] acpi device:0b: resuming
[    3.239645] acpi device:0c: resuming
[    3.239646] acpi device:0d: resuming
[    3.239648] acpi device:0e: resuming
[    3.239650] acpi device:0f: resuming
[    3.239652] acpi device:10: resuming
[    3.239654] acpi device:11: resuming
[    3.239656] acpi device:12: resuming
[    3.239657] acpi bay:00: resuming
[    3.239659] acpi device:13: resuming
[    3.239661] acpi device:14: resuming
[    3.239663] acpi device:15: resuming
[    3.239665] acpi device:16: resuming
[    3.239666] acpi device:17: resuming
[    3.239668] acpi device:18: resuming
[    3.239670] acpi device:19: resuming
[    3.239672] acpi device:1a: resuming
[    3.239673] acpi device:1b: resuming
[    3.239675] acpi device:1c: resuming
[    3.239677] acpi device:1d: resuming
[    3.239679] acpi device:1e: resuming
[    3.239681] acpi device:1f: resuming
[    3.239683] acpi device:20: resuming
[    3.239684] acpi device:21: resuming
[    3.239686] acpi device:22: resuming
[    3.239688] acpi thermal:00: resuming
[    3.239690] thermal thermal:01: resuming
[    3.240184] thermal thermal:02: resuming
[    3.240756] agpgart-intel 0000:00:00.0: resuming
[    3.255490] pci 0000:00:02.0: resuming
[    3.255586] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
[    3.255590] pci 0000:00:02.1: resuming
[    3.255598] PM: Writing back config space on device 0000:00:02.1 at offset 1 (was 900000, writing 900003)
[    3.255603] HDA Intel 0000:00:1b.0: resuming
[    3.342657] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100106, writing 100102)
[    3.342673] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 22
[    3.342680] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[    3.836421] pcieport-driver 0000:00:1c.0: resuming
[    3.836453] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 180107, writing 100107)
[    3.836475] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    3.836484] pcieport-driver 0000:00:1c.1: resuming
[    3.836528] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    3.836535] pcieport-driver 0000:00:1c.2: resuming
[    3.836556] PM: Writing back config space on device 0000:00:1c.2 at offset 7 (was 20006050, writing 6050)
[    3.836586] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[    3.836592] pcieport-driver 0000:00:1c.3: resuming
[    3.836602] PM: Writing back config space on device 0000:00:1c.3 at offset f (was 40400, writing 4040b)
[    3.836616] PM: Writing back config space on device 0000:00:1c.3 at offset 9 (was 10001, writing e421e421)
[    3.836624] PM: Writing back config space on device 0000:00:1c.3 at offset 8 (was 0, writing ebf0ea00)
[    3.836632] PM: Writing back config space on device 0000:00:1c.3 at offset 7 (was 20000000, writing 8070)
[    3.836643] PM: Writing back config space on device 0000:00:1c.3 at offset 3 (was 810000, writing 810010)
[    3.836652] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100000, writing 100107)
[    3.836674] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    3.836682] uhci_hcd 0000:00:1d.0: resuming
[    3.836688] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
[    3.836696] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[    3.836745] usb usb2: root hub lost power or was reset
[    3.836764] uhci_hcd 0000:00:1d.1: resuming
[    3.836769] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 22
[    3.836777] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[    3.836834] usb usb3: root hub lost power or was reset
[    3.836849] uhci_hcd 0000:00:1d.2: resuming
[    3.836852] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 23
[    3.836857] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[    3.836899] usb usb4: root hub lost power or was reset
[    3.836914] uhci_hcd 0000:00:1d.3: resuming
[    3.836917] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 21
[    3.836922] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[    3.836964] usb usb5: root hub lost power or was reset
[    3.836995] ehci_hcd 0000:00:1d.7: resuming
[    3.837808] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 21
[    3.837813] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[    3.837868] pci 0000:00:1e.0: resuming
[    3.837893] PM: Writing back config space on device 0000:00:1e.0 at offset 1 (was 100005, writing 100007)
[    3.837911] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[    3.837914] pci 0000:00:1f.0: resuming
[    3.837955] PIIX_IDE 0000:00:1f.1: resuming
[    3.837969] PM: Writing back config space on device 0000:00:1f.1 at offset 7 (was 1, writing 375)
[    3.837974] PM: Writing back config space on device 0000:00:1f.1 at offset 6 (was 1, writing 171)
[    3.837978] PM: Writing back config space on device 0000:00:1f.1 at offset 5 (was 1, writing 3f5)
[    3.837983] PM: Writing back config space on device 0000:00:1f.1 at offset 4 (was 1, writing 1f1)
[    3.837995] ACPI: PCI Interrupt 0000:00:1f.1[C] -> GSI 16 (level, low) -> IRQ 20
[    3.837998] ahci 0000:00:1f.2: resuming
[    3.838212] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
[    3.838220] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[    3.847115] pci 0000:00:1f.3: resuming
[    3.847151] e1000 0000:02:00.0: resuming
[    3.847598] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    3.847609] PCI: Setting latency timer of device 0000:02:00.0 to 64
[    3.853394] pci 0000:03:00.0: resuming
[    3.853592] pci 0000:15:00.0: resuming
[    3.853604] PM: Writing back config space on device 0000:15:00.0 at offset f (was 34001ff, writing 3c0010b)
[    3.853610] PM: Writing back config space on device 0000:15:00.0 at offset e (was 0, writing 94fc)
[    3.853616] PM: Writing back config space on device 0000:15:00.0 at offset d (was 0, writing 9400)
[    3.853622] PM: Writing back config space on device 0000:15:00.0 at offset c (was 0, writing 90fc)
[    3.853628] PM: Writing back config space on device 0000:15:00.0 at offset b (was 0, writing 9000)
[    3.853634] PM: Writing back config space on device 0000:15:00.0 at offset a (was 0, writing 53fff000)
[    3.853640] PM: Writing back config space on device 0000:15:00.0 at offset 9 (was 0, writing 50000000)
[    3.853646] PM: Writing back config space on device 0000:15:00.0 at offset 8 (was 0, writing e3fff000)
[    3.853652] PM: Writing back config space on device 0000:15:00.0 at offset 7 (was 0, writing e0000000)
[    3.853658] PM: Writing back config space on device 0000:15:00.0 at offset 6 (was 0, writing b0171615)
[    3.853666] PM: Writing back config space on device 0000:15:00.0 at offset 4 (was 0, writing e4300000)
[    3.853672] PM: Writing back config space on device 0000:15:00.0 at offset 3 (was 20000, writing 2a808)
[    3.853679] PM: Writing back config space on device 0000:15:00.0 at offset 1 (was 2100000, writing 2100007)
[    3.853705] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    3.853713] system 00:00: resuming
[    3.853715] pnp 00:01: resuming
[    3.853716] system 00:02: resuming
[    3.853718] pnp 00:03: resuming
[    3.853720] pnp 00:04: resuming
[    3.853722] pnp 00:05: resuming
[    3.853723] pnp 00:06: resuming
[    3.853725] pnp 00:07: resuming
[    3.853727] i8042 kbd 00:08: resuming
[    3.853729] i8042 aux 00:09: resuming
[    3.853731] pnp 00:0a: resuming
[    3.853738] platform pcspkr: resuming
[    3.853741] pci_express 0000:00:1c.0:pcie00: resuming
[    3.853743] pci_express 0000:00:1c.0:pcie02: resuming
[    3.853745] pci_express 0000:00:1c.0:pcie03: resuming
[    3.853747] pci_express 0000:00:1c.1:pcie00: resuming
[    3.853749] pci_express 0000:00:1c.1:pcie02: resuming
[    3.853751] pci_express 0000:00:1c.1:pcie03: resuming
[    3.853753] pci_express 0000:00:1c.2:pcie00: resuming
[    3.853755] pci_express 0000:00:1c.2:pcie02: resuming
[    3.853757] pci_express 0000:00:1c.2:pcie03: resuming
[    3.853759] pci_express 0000:00:1c.3:pcie00: resuming
[    3.853761] pci_express 0000:00:1c.3:pcie02: resuming
[    3.853763] pci_express 0000:00:1c.3:pcie03: resuming
[    3.853765] platform vesafb.0: resuming
[    3.853990] serial8250 serial8250: resuming
[    3.853996] ide-cdrom 0.0: resuming
[    3.857029] sd 0:0:0:0: resuming
[    3.857036] usb usb1: resuming
[    3.877215] hub 1-0:1.0: resuming
[    3.877220] usb usb2: resuming
[    3.885545] hub 2-0:1.0: resuming
[    3.885549] usb usb3: resuming
[    3.913863] hub 3-0:1.0: resuming
[    3.913867] usb usb4: resuming
[    3.962189] hub 4-0:1.0: resuming
[    3.962194] usb usb5: resuming
[    4.034294] hub 5-0:1.0: resuming
[    4.034299] usb 5-2: resuming
[    4.034304]  usbdev5.2_ep00: PM: resume from 0, parent 5-2 still 2
[    4.034309] usb 5-2:1.0: PM: resume from 2, parent 5-2 still 2
[    4.034312] usb 5-2:1.0: resuming
[    4.034316]  usbdev5.2_ep81: PM: resume from 0, parent 5-2:1.0 still 2
[    4.034320]  usbdev5.2_ep02: PM: resume from 0, parent 5-2:1.0 still 2
[    4.034325]  usbdev5.2_ep83: PM: resume from 0, parent 5-2:1.0 still 2
[    4.034329]  usbdev5.2: PM: resume from 0, parent 5-2 still 2
[    4.034333] i8042 i8042: resuming
[    4.036208] atkbd serio0: resuming
[    4.039572] psmouse serio1: resuming
[    4.055718] ata2: SATA link down (SStatus 0 SControl 0)
[    4.055736] ata3: SATA link down (SStatus 0 SControl 0)
[    4.055750] ata4: SATA link down (SStatus 0 SControl 0)
[    4.241724] psmouse serio2: resuming
[    5.273802] Restarting tasks ... <6>usb 5-2: USB disconnect, address 2
[    5.274002] PM: Removing info for No Bus:usbdev5.2_ep81
[    5.274048] PM: Removing info for No Bus:usbdev5.2_ep02
[    5.274081] PM: Removing info for No Bus:usbdev5.2_ep83
[    5.274115] PM: Removing info for usb:5-2:1.0
[    5.274156] PM: Removing info for No Bus:usbdev5.2
[    5.274192] PM: Removing info for No Bus:usbdev5.2_ep00
[    5.274234] PM: Removing info for usb:5-2
[    5.285419] done.
[    5.953244] ata1: waiting for device to spin up (7 secs)
[    5.994839] usb 5-2: new full speed USB device using uhci_hcd and address 3
[    6.056673] PM: Adding info for usb:5-2
[    6.056753] PM: Adding info for No Bus:usbdev5.3_ep00
[    6.056782] usb 5-2: configuration #1 chosen from 1 choice
[    6.059645] PM: Adding info for usb:5-2:1.0
[    6.059690] PM: Adding info for No Bus:usbdev5.3_ep81
[    6.059713] PM: Adding info for No Bus:usbdev5.3_ep02
[    6.059738] PM: Adding info for No Bus:usbdev5.3_ep83
[    6.059762] PM: Adding info for No Bus:usbdev5.3
[    9.372331] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    9.706492] ata1.00: configured for UDMA/100
[    9.737686] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    9.739158] sda: Write Protect is off
[    9.739225] sda: Mode Sense: 00 3a 00 00
[    9.756091] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[3/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : NCQ problem with ahci and Hitachi drive
References : http://lkml.org/lkml/2007/3/4/178
Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
Status     : unknown


Subject    : kernels fail to boot with drives on ATIIXP controller
References : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229621
Submitter  : Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
Status     : unknown


Subject    : libata: PATA UDMA/100 configured as UDMA/33
References : http://lkml.org/lkml/2007/2/20/294
             http://www.mail-archive.com/linux-ide@vger.kernel.org/msg04115.html
Submitter  : Fabio Comolli <fabio.comolli@gmail.com>
Handled-By : Tejun Heo <htejun@gmail.com>
Status     : problem is being discussed


Subject    : SATA_ACPI errors during kernel boot
References : http://bugzilla.kernel.org/show_bug.cgi?id=8080
             http://bugzilla.kernel.org/show_bug.cgi?id=8046
             http://bugzilla.kernel.org/show_bug.cgi?id=8095
             http://lkml.org/lkml/2007/2/22/159
Submitter  : Janosch Machowinski <jmachowinski@gmx.de>
             Lukas Hejtmanek <xhejtman@fi.muni.cz>
             Meelis Roos <mroos@linux.ee>
             Olivier Mondoloni <darkcore71@yahoo.fr>
Handled-By : Thomas Renninger <trenn@suse.de>
             Tejun Heo <htejun@gmail.com>
             Robert Moore <robert.moore@intel.com>
Status     : problem is being debugged

Re: [3/6] 2.6.21-rc2: known regressions

[Michal Jaegermann]

On Mon, Mar 05, 2007 at 02:50:36AM +0100, Adrian Bunk wrote:
> This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> that are not yet fixed in Linus' tree.
....
> Subject    : kernels fail to boot with drives on ATIIXP controller
> References : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229621
> Submitter  : Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
> Status     : unknown

Alan added comment to my posting that my problems are caused by
messed up IRQ routing on that box I tried.  Indeed, I can boot
kernel 2.6.20-1.2962.fc7, which really is 2.6.21-rc2, provided
I will use 'acpi=off irqpoll'.  Anything else and a boot silently
dies if 'acpi=off' is skipped or is not finding disk if 'irqpoll'
is missing.

Somehow 2.6.19 is booting on the same hardware without "valliant
efforts"; OTOH 'ahci' driver was not used there.

    Michal

Re: [3/6] 2.6.21-rc2: known regressions

[Alan Cox]

> Subject    : libata: PATA UDMA/100 configured as UDMA/33
> References : http://lkml.org/lkml/2007/2/20/294
>              http://www.mail-archive.com/linux-ide@vger.kernel.org/msg04115.html
> Submitter  : Fabio Comolli <fabio.comolli@gmail.com>
> Handled-By : Tejun Heo <htejun@gmail.com>
> Status     : problem is being discussed

Patch went to Jeff, hopefully it is now fixed. Bigger rework is heading
into -mm but not appropriate or neccessary for 2.6.21

Re: [3/6] 2.6.21-rc2: known regressions

[Jeff Garzik]

Adrian Bunk wrote:
> Subject    : NCQ problem with ahci and Hitachi drive
> References : http://lkml.org/lkml/2007/3/4/178
> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
> Status     : unknown

according to the last message in that thread, it sounds like ACPI and 
interrupt problems


> Subject    : SATA_ACPI errors during kernel boot
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8080
>              http://bugzilla.kernel.org/show_bug.cgi?id=8046
>              http://bugzilla.kernel.org/show_bug.cgi?id=8095
>              http://lkml.org/lkml/2007/2/22/159
> Submitter  : Janosch Machowinski <jmachowinski@gmx.de>
>              Lukas Hejtmanek <xhejtman@fi.muni.cz>
>              Meelis Roos <mroos@linux.ee>
>              Olivier Mondoloni <darkcore71@yahoo.fr>
> Handled-By : Thomas Renninger <trenn@suse.de>
>              Tejun Heo <htejun@gmail.com>
>              Robert Moore <robert.moore@intel.com>
> Status     : problem is being debugged

Note that there WILL be an increase in ACPI diagnostic output.  The key 
difference is whether the users are seeing scary printks, or whether the 
boot is actually breaking.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [3/6] 2.6.21-rc2: known regressions

[Jeff Garzik]

Adrian Bunk wrote:
> Subject    : NCQ problem with ahci and Hitachi drive
> References : http://lkml.org/lkml/2007/3/4/178
> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
> Status     : unknown

according to the last message in that thread, it sounds like ACPI and 
interrupt problems


> Subject    : SATA_ACPI errors during kernel boot
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8080
>              http://bugzilla.kernel.org/show_bug.cgi?id=8046
>              http://bugzilla.kernel.org/show_bug.cgi?id=8095
>              http://lkml.org/lkml/2007/2/22/159
> Submitter  : Janosch Machowinski <jmachowinski@gmx.de>
>              Lukas Hejtmanek <xhejtman@fi.muni.cz>
>              Meelis Roos <mroos@linux.ee>
>              Olivier Mondoloni <darkcore71@yahoo.fr>
> Handled-By : Thomas Renninger <trenn@suse.de>
>              Tejun Heo <htejun@gmail.com>
>              Robert Moore <robert.moore@intel.com>
> Status     : problem is being debugged

Note that there WILL be an increase in ACPI diagnostic output.  The key 
difference is whether the users are seeing scary printks, or whether the 
boot is actually breaking.

	Jeff

Re: [3/6] 2.6.21-rc2: known regressions

[Mathieu Bérard]

Jeff Garzik a écrit :
> Adrian Bunk wrote:
>> Subject    : NCQ problem with ahci and Hitachi drive
>> References : http://lkml.org/lkml/2007/3/4/178
>> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
>> Status     : unknown
>
> according to the last message in that thread, it sounds like ACPI and
> interrupt problems
>
Hi,
after more testing with a 2.6.21-rc3, it appears that after several ata
errors the boot process
somehow continued as normal, after a "NCQ disabled due to excessive
errors" message.
"pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
does nothing.

lspci:
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML
Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI
Express Root Port (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
SMBus Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc M24 [Radeon
Mobility X600]
06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
06:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG
Network Connection (rev 05)
06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394
Host Controller
06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated
FlashMedia Controller
06:04.4 Generic system peripheral [0805]: Texas Instruments
PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller


/proc/interrupts:
        CPU0      
  0:       3242   IO-APIC-edge      timer
  1:        863   IO-APIC-edge      i8042
  8:          3   IO-APIC-edge      rtc
  9:          1   IO-APIC-fasteoi   acpi
 12:        116   IO-APIC-edge      i8042
 14:        128   IO-APIC-edge      libata
 15:          0   IO-APIC-edge      libata
 16:          1   IO-APIC-fasteoi   uhci_hcd:usb4, yenta
 17:          0   IO-APIC-fasteoi   tifm_7xx1, Intel ICH6
 18:        249   IO-APIC-fasteoi   eth0
 19:       2712   IO-APIC-fasteoi   libata, uhci_hcd:usb2, sdhci:slot0,
sdhci:slot1, sdhci:slot2
 20:         47   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5
 21:          3   IO-APIC-fasteoi   uhci_hcd:usb3, ohci1394
 22:          1   IO-APIC-fasteoi   ipw2200
NMI:          0
LOC:      15767
ERR:          0
MIS:          0


/proc/interrupts with pci=noacpi:
    CPU0      
  0:       2886    XT-PIC-XT        timer
  1:         79    XT-PIC-XT        i8042
  2:          0    XT-PIC-XT        cascade
  8:          3    XT-PIC-XT        rtc
  9:          1    XT-PIC-XT        acpi
 10:          1    XT-PIC-XT        uhci_hcd:usb4, tifm_7xx1, yenta,
sdhci:slot0, sdhci:slot1, sdhci:slot2, Intel ICH6
 11:       3415    XT-PIC-XT        eth0, libata, uhci_hcd:usb1,
uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb5, ohci1394, ipw2200
 12:        116    XT-PIC-XT        i8042
 14:        129    XT-PIC-XT        libata
 15:          0    XT-PIC-XT        libata
NMI:          0
LOC:       6594
ERR:          0
MIS:          0

Full 2.6.21-rc3 boot log:
[    0.000000] Linux version 2.6.21-rc3 (root@manwe) (gcc version 4.1.2
(Ubuntu 4.1.2-0ubuntu4)) #1 PREEMPT Fri Mar 9 01:54:11 CET 2007
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] sanitize start
[    0.000000] sanitize end
[    0.000000] copy_e820_map() start: 0000000000000000 size:
000000000009f800 end: 000000000009f800 type: 1
[    0.000000] copy_e820_map() type is E820_RAM
[    0.000000] copy_e820_map() start: 000000000009f800 size:
0000000000000800 end: 00000000000a0000 type: 2
[    0.000000] copy_e820_map() start: 00000000000d2000 size:
0000000000002000 end: 00000000000d4000 type: 2
[    0.000000] copy_e820_map() start: 00000000000dc000 size:
0000000000024000 end: 0000000000100000 type: 2
[    0.000000] copy_e820_map() start: 0000000000100000 size:
000000003fde0000 end: 000000003fee0000 type: 1
[    0.000000] copy_e820_map() type is E820_RAM
[    0.000000] copy_e820_map() start: 000000003fee0000 size:
000000000000a000 end: 000000003feea000 type: 3
[    0.000000] copy_e820_map() start: 000000003feea000 size:
0000000000016000 end: 000000003ff00000 type: 4
[    0.000000] copy_e820_map() start: 000000003ff00000 size:
0000000000100000 end: 0000000040000000 type: 2
[    0.000000] copy_e820_map() start: 00000000e0000000 size:
0000000010006000 end: 00000000f0006000 type: 2
[    0.000000] copy_e820_map() start: 00000000f0008000 size:
0000000000004000 end: 00000000f000c000 type: 2
[    0.000000] copy_e820_map() start: 00000000fed20000 size:
0000000000070000 end: 00000000fed90000 type: 2
[    0.000000] copy_e820_map() start: 00000000ff000000 size:
0000000001000000 end: 0000000100000000 type: 2
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
[    0.000000]  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003fee0000 (usable)
[    0.000000]  BIOS-e820: 000000003fee0000 - 000000003feea000 (ACPI data)
[    0.000000]  BIOS-e820: 000000003feea000 - 000000003ff00000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003ff00000 - 0000000040000000 (reserved)
[    0.000000]  BIOS-e820: 00000000e0000000 - 00000000f0006000 (reserved)
[    0.000000]  BIOS-e820: 00000000f0008000 - 00000000f000c000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
[    0.000000]  BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
[    0.000000] 126MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   261856
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   261856
[    0.000000] DMI present.
[    0.000000] ACPI: RSDP 000F6980, 0014 (r0 TOSCPL)
[    0.000000] ACPI: RSDT 3FEE276F, 0044 (r1 TOSCPL   RSDT    6040000 
LTP        0)
[    0.000000] ACPI: APIC 3FEE9E88, 0068 (r1 INTEL  ALVISO    6040000
LOHR       5F)
[    0.000000] ACPI: FACP 3FEE9EF0, 0074 (r1 TOSCPL ALVISO    6040000
LOHR       32)
[    0.000000] ACPI: DSDT 3FEE3217, 6C71 (r1 TOSCPL ALVISO    6040000
MSFT  100000E)
[    0.000000] ACPI: FACS 3FEFAFC0, 0040
[    0.000000] ACPI: BOOT 3FEE9FD8, 0028 (r1 PTLTD  $SBFTBL$  6040000 
LTP        1)
[    0.000000] ACPI: MCFG 3FEE9F9C, 003C (r1 INTEL  ALVISO    6040000
LOHR       5F)
[    0.000000] ACPI: SSDT 3FEE2FE5, 022E (r1 SataRe SataAhci     1000
INTL 20030224)
[    0.000000] ACPI: SSDT 3FEE2BAA, 022B (r1  PmRef  Cpu0Ist     3000
INTL 20030224)
[    0.000000] ACPI: SSDT 3FEE29CC, 01DE (r1  PmRef  Cpu0Cst     3001
INTL 20030224)
[    0.000000] ACPI: SSDT 3FEE27B3, 0219 (r1  PmRef    CpuPm     3000
INTL 20030224)
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:13 APIC version 20
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI
0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at 50000000 (gap:
40000000:a0000000)
[    0.000000] Built 1 zonelists.  Total pages: 259811
[    0.000000] Kernel command line: root=/dev/mapper/Base-Root ro single
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] CPU 0 irqstacks, hard=c034f000 soft=c034e000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 1729.086 MHz processor.
[   82.100659] Console: colour VGA+ 80x25
[   82.104287] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[   82.104813] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[   82.128315] Memory: 1031112k/1047424k available (1606k kernel code,
15544k reserved, 544k data, 184k init, 129920k highmem)
[   82.128378] virtual kernel memory layout:
[   82.128379]     fixmap  : 0xfffaa000 - 0xfffff000   ( 340 kB)
[   82.128381]     pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
[   82.128383]     vmalloc : 0xf8800000 - 0xffbfe000   ( 115 MB)
[   82.128385]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   82.128386]       .init : 0xc031b000 - 0xc0349000   ( 184 kB)
[   82.128388]       .data : 0xc029183b - 0xc0319bb4   ( 544 kB)
[   82.128390]       .text : 0xc0100000 - 0xc029183b   (1606 kB)
[   82.128741] Checking if this processor honours the WP bit even in
supervisor mode... Ok.
[   82.188878] Calibrating delay using timer specific routine.. 3460.07
BogoMIPS (lpj=1730037)
[   82.188995] Security Framework v1.0.0 initialized
[   82.189054] Mount-cache hash table entries: 512
[   82.189191] CPU: L1 I cache: 32K, L1 D cache: 32K
[   82.189271] CPU: L2 cache: 2048K
[   82.189321] Intel machine check architecture supported.
[   82.189367] Intel machine check reporting enabled on CPU#0.
[   82.189422] CPU: Intel(R) Pentium(R) M processor 1.73GHz stepping 08
[   82.189539] Checking 'hlt' instruction... OK.
[   82.192970] ACPI: Core revision 20070126
[   82.193084] ACPI: Table DSDT replaced by host OS
[   82.193197] ACPI: DSDT 00000000, 6305 (r1 TOSCPL ALVISO    6040000
INTL 20051117)
[   82.202965] ENABLING IO-APIC IRQs
[   82.203196] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[   82.416878] NET: Registered protocol family 16
[   82.416994] ACPI: bus type pci registered
[   82.417047] PCI: Using MMCONFIG
[   82.417737] Setting up standard PCI resources
[   82.422950] ACPI: Interpreter enabled
[   82.422996] ACPI: (supports S0 S3 S4 S5)
[   82.423228] ACPI: Using IOAPIC for interrupt routing
[   82.468401] ACPI: PCI Root Bridge [PCI0] (0000:00)
[   82.468914] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[   82.468962] PCI quirk: region 1180-11bf claimed by ICH6 GPIO
[   82.469042] 0000:00:1f.1: trying to change BAR0 from 0000 to 01F0
[   82.469090] 0000:00:1f.1: trying to change BAR1 from 0000 to 03F4
[   82.469137] 0000:00:1f.1: trying to change BAR2 from 0000 to 0170
[   82.469184] 0000:00:1f.1: trying to change BAR3 from 0000 to 0374
[   82.469927] PCI: Transparent bridge - 0000:00:1e.0
[   82.470019] PCI: Bus #07 (-#0a) is hidden behind transparent bridge
#06 (-#07) (try 'pci=assign-busses')
[   82.470074] Please report the result to linux-kernel to fix this
permanently
[   82.477076] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 12
14 15)
[   82.477633] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12
14 15) *10
[   82.478229] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12
14 15) *11
[   82.478831] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12
14 15)
[   82.479384] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12
14 15) *11
[   82.479979] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12
14 15)
[   82.480532] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12
14 15) *11
[   82.481129] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12
14 15)
[   82.481670] Linux Plug and Play Support v0.97 (c) Adam Belay
[   82.481721] pnp: PnP ACPI init
[   82.503859] pnp: PnP ACPI: found 9 devices
[   82.503925] PCI: Using ACPI for IRQ routing
[   82.503970] PCI: If a device doesn't work, try "pci=routeirq".  If it
helps, post a report
[   82.504135] pnp: 00:01: ioport range 0xfe00-0xfe7f has been reserved
[   82.504182] pnp: 00:01: ioport range 0xfe80-0xfeff has been reserved
[   82.504229] pnp: 00:01: ioport range 0xff00-0xff7f has been reserved
[   82.504277] pnp: 00:01: iomem range 0xe0000000-0xefffffff has been
reserved
[   82.504324] pnp: 00:01: iomem range 0xf0000000-0xf0003fff has been
reserved
[   82.504372] pnp: 00:01: iomem range 0xf0004000-0xf0004fff has been
reserved
[   82.504420] pnp: 00:01: iomem range 0xf0005000-0xf0005fff has been
reserved
[   82.504712] Time: tsc clocksource has been installed.
[   82.534686] PCI: Bridge: 0000:00:01.0
[   82.534732]   IO window: 3000-3fff
[   82.534777]   MEM window: b8100000-b81fffff
[   82.534822]   PREFETCH window: c8000000-cfffffff
[   82.534868] PCI: Bridge: 0000:00:1c.0
[   82.534913]   IO window: 4000-4fff
[   82.534959]   MEM window: bc000000-bfffffff
[   82.535006]   PREFETCH window: d0000000-d3ffffff
[   82.535053] PCI: Bridge: 0000:00:1c.1
[   82.535098]   IO window: 5000-5fff
[   82.535144]   MEM window: c0000000-c3ffffff
[   82.535191]   PREFETCH window: d4000000-d7ffffff
[   82.535241] PCI: Bus 7, cardbus bridge: 0000:06:04.0
[   82.535287]   IO window: 00006400-000064ff
[   82.535334]   IO window: 00006800-000068ff
[   82.535381]   PREFETCH window: 50000000-53ffffff
[   82.535428]   MEM window: 54000000-57ffffff
[   82.535475] PCI: Bridge: 0000:00:1e.0
[   82.535520]   IO window: 6000-6fff
[   82.535567]   MEM window: c4000000-c40fffff
[   82.535614]   PREFETCH window: 50000000-53ffffff
[   82.535668] ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level,
low) -> IRQ 16
[   82.536458] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level,
low) -> IRQ 17
[   82.536562] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level,
low) -> IRQ 16
[   82.536674] ACPI: PCI Interrupt 0000:06:04.0[A] -> GSI 16 (level,
low) -> IRQ 16
[   82.536778] NET: Registered protocol family 2
[   82.546708] IP route cache hash table entries: 32768 (order: 5,
131072 bytes)
[   82.546828] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[   82.547737] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[   82.548053] TCP: Hash tables configured (established 131072 bind 65536)
[   82.548103] TCP reno registered
[   82.550814] checking if image is initramfs... it is
[   82.926145] Freeing initrd memory: 3943k freed
[   82.926322] Simple Boot Flag at 0x36 set to 0x1
[   82.926670] highmem bounce pool size: 64 pages
[   82.926717] Total HugeTLB memory allocated, 0
[   82.926848] io scheduler noop registered
[   82.926934] io scheduler cfq registered (default)
[   82.927311] assign_interrupt_mode Found MSI capability
[   82.927524] assign_interrupt_mode Found MSI capability
[   82.927748] assign_interrupt_mode Found MSI capability
[   82.929989] RAMDISK driver initialized: 16 RAM disks of 65536K size
1024 blocksize
[   82.930197] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at
0x60,0x64 irq 1,12
[   82.930435] i8042.c: Detected active multiplexing controller, rev 1.1.
[   82.930548] serio: i8042 KBD port at 0x60,0x64 irq 1
[   82.930624] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[   82.930694] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[   82.930762] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[   82.930830] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[   82.930924] mice: PS/2 mouse device common for all mice
[   82.931061] TCP cubic registered
[   82.931110] NET: Registered protocol family 1
[   82.931162] Using IPI Shortcut mode
[   82.931366] Freeing unused kernel memory: 184k freed
[   82.933520] input: AT Translated Set 2 keyboard as /class/input/input0
[   83.034411] Switched to high resolution mode on CPU 0
[   83.038869] 8139too Fast Ethernet driver 0.9.28
[   83.038971] ACPI: PCI Interrupt 0000:06:01.0[A] -> GSI 21 (level,
low) -> IRQ 18
[   83.039529] eth0: RealTek RTL8139 at 0xf8820000, 00:0f:b0:a5:9a:81,
IRQ 18
[   83.041859] netconsole: local port 5000
[   83.041905] netconsole: local IP 192.168.0.20
[   83.041950] netconsole: interface eth0
[   83.041994] netconsole: remote port 5000
[   83.042039] netconsole: remote IP 192.168.0.1
[   83.042084] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[   83.042131] netconsole: device eth0 not up yet, forcing it
[   83.042210] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   83.042967] netconsole: carrier detect appears untrustworthy, waiting
4 seconds
[   87.059120] netconsole: network logging started
[   87.064954] SCSI subsystem initialized
[   87.070057] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level,
low) -> IRQ 19
[   88.070489] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5
Gbps 0x5 impl IDE mode
[   88.070546] ahci 0000:00:1f.2: flags: 64bit ncq pm led slum part
[   88.070671] ata1: SATA max UDMA/133 cmd 0xf8824d00 ctl 0x00000000
bmdma 0x00000000 irq 19
[   88.070789] ata2: SATA max UDMA/133 cmd 0xf8824d80 ctl 0x00000000
bmdma 0x00000000 irq 19
[   88.070910] ata3: SATA max UDMA/133 cmd 0xf8824e00 ctl 0x00000000
bmdma 0x00000000 irq 19
[   88.071027] ata4: SATA max UDMA/133 cmd 0xf8824e80 ctl 0x00000000
bmdma 0x00000000 irq 19
[   88.071091] scsi0 : ahci
[   88.528373] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   88.573162] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100
[   88.573212] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   88.575453] ata1.00: configured for UDMA/100
[   88.575503] scsi1 : ahci
[   88.878284] ata2: SATA link down (SStatus 0 SControl 0)
[   88.878338] scsi2 : ahci
[   89.181217] ata3: SATA link down (SStatus 0 SControl 300)
[   89.181270] scsi3 : ahci
[   89.484151] ata4: SATA link down (SStatus 0 SControl 0)
[   89.484277] scsi 0:0:0:0: Direct-Access     ATA      HTS541010G9SA00 
MBZO PQ: 0 ANSI: 5
[   89.488409] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12)
initialised: dm-devel@redhat.com
[   89.601570] usbcore: registered new interface driver usbfs
[   89.601649] usbcore: registered new interface driver hub
[   89.601716] usbcore: registered new device driver usb
[   89.602398] USB Universal Host Controller Interface driver v3.0
[   89.602495] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level,
low) -> IRQ 20
[   89.602607] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[   89.602735] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 1
[   89.602821] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001800
[   89.602958] usb usb1: configuration #1 chosen from 1 choice
[   89.603026] hub 1-0:1.0: USB hub found
[   89.603077] hub 1-0:1.0: 2 ports detected
[   89.705230] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level,
low) -> IRQ 19
[   89.705354] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[   89.705423] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned
bus number 2
[   89.705506] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001820
[   89.705633] usb usb2: configuration #1 chosen from 1 choice
[   89.705702] hub 2-0:1.0: USB hub found
[   89.705752] hub 2-0:1.0: 2 ports detected
[   89.806175] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level,
low) -> IRQ 21
[   89.806300] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[   89.806370] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned
bus number 3
[   89.806455] uhci_hcd 0000:00:1d.2: irq 21, io base 0x00001840
[   89.806582] usb usb3: configuration #1 chosen from 1 choice
[   89.806652] hub 3-0:1.0: USB hub found
[   89.806703] hub 3-0:1.0: 2 ports detected
[   89.907109] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level,
low) -> IRQ 16
[   89.907217] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[   89.907288] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned
bus number 4
[   89.907370] uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001860
[   89.907488] usb usb4: configuration #1 chosen from 1 choice
[   89.907556] hub 4-0:1.0: USB hub found
[   89.907606] hub 4-0:1.0: 2 ports detected
[   89.911054] usb 1-1: new low speed USB device using uhci_hcd and
address 2
[   90.008647] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level,
low) -> IRQ 20
[   90.008762] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[   90.008827] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 5
[   90.008912] ehci_hcd 0000:00:1d.7: debug port 1
[   90.008969] ehci_hcd 0000:00:1d.7: irq 20, io mem 0xb8000000
[   90.012903] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[   90.013011] usb usb5: configuration #1 chosen from 1 choice
[   90.013084] hub 5-0:1.0: USB hub found
[   90.013135] hub 5-0:1.0: 8 ports detected
[   90.114194] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level,
low) -> IRQ 21
[   90.114347] ata5: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6
bmdma 0x000118c0 irq 14
[   90.114430] ata6: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376
bmdma 0x000118c8 irq 15
[   90.114511] scsi4 : ata_piix
[   90.419698] ata5.00: ATAPI, max UDMA/33
[   90.426941] usb 1-1: device not accepting address 2, error -71
[   90.574569] ata5.00: configured for UDMA/33
[   90.574624] scsi5 : ata_piix
[   90.574727] ata6: port disabled. ignoring.
[   90.576634] scsi 4:0:0:0: CD-ROM            MATSHITA DVD-RAM UJ-841S 
1.50 PQ: 0 ANSI: 5
[   90.576836] ACPI: PCI Interrupt 0000:06:04.2[C] -> GSI 18 (level,
low) -> IRQ 21
[   90.627288] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] 
MMIO=[c4006800-c4006fff]  Max Packet=[2048]  IR/IT contexts=[4/8]
[   90.636552] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[   90.636620] sda: Write Protect is off
[   90.636689] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[   90.636787] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[   90.636842] sda: Write Protect is off
[   90.636913] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[   90.636970]  sda:<6>usb 1-1: new low speed USB device using uhci_hcd
and address 4
[   91.072397] usb 1-1: configuration #1 chosen from 1 choice
[   91.098889] input: Logitech USB Receiver as /class/input/input1
[   91.099036] input: USB HID v1.10 Mouse [Logitech USB Receiver] on
usb-0000:00:1d.0-1
[   91.099185] usbcore: registered new interface driver usbhid
[   91.099239] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[  120.630313] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2
frozen
[  120.630373] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
cdb 0x0 data 4096 in
[  120.630375]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  120.933235] ata1: soft resetting port
[  121.088217] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  121.093545] ata1.00: configured for UDMA/100
[  121.093600] ata1: EH complete
[  121.093682] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[  121.093739] sda: Write Protect is off
[  121.093805] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[  151.086611] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2
frozen
[  151.086665] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
cdb 0x0 data 4096 in
[  151.086667]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  151.389541] ata1: soft resetting port
[  151.544521] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  151.549801] ata1.00: configured for UDMA/100
[  151.549852] ata1: EH complete
[  151.549921] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[  151.549976] sda: Write Protect is off
[  151.550042] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[  181.542915] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2
frozen
[  181.542970] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
cdb 0x0 data 4096 in
[  181.542971]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  181.845846] ata1: soft resetting port
[  182.000827] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  182.006151] ata1.00: configured for UDMA/100
[  182.006202] ata1: EH complete
[  182.006271] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[  182.006325] sda: Write Protect is off
[  182.006391] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[  211.999220] ata1.00: NCQ disabled due to excessive errors
[  211.999271] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2
frozen
[  211.999329] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
cdb 0x0 data 4096 in
[  211.999331]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  212.302152] ata1: soft resetting port
[  212.457132] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  212.462428] ata1.00: configured for UDMA/100
[  212.462479] ata1: EH complete
[  212.462547] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[  212.462602] sda: Write Protect is off
[  212.462668] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[  212.477303]  sda1 sda2 < sda5 sda6 > sda3
[  212.521233] sd 0:0:0:0: Attached scsi disk sda
[  212.524556] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  212.524782] sr 4:0:0:0: Attached scsi generic sg1 type 5
[  212.530683] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
xa/form2 cdda tray
[  212.530745] Uniform CD-ROM driver Revision: 3.20
[  212.855075] Attempting manual resume
[  212.923490] SGI XFS with ACLs, realtime, no debug enabled
[  212.982545] Filesystem "dm-0": Disabling barriers, not supported by
the underlying device
[  212.982815] XFS mounting filesystem dm-0
[  216.458088] input: PC Speaker as /class/input/input2
[  216.869753] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
[  216.874226] input: PS/2 Mouse as /class/input/input3
[  216.891684] Real Time Clock Driver v1.12ac
[  216.893113] input: AlpsPS/2 ALPS GlidePoint as /class/input/input4
[  216.896321] iTCO_wdt: Found a ICH6-M TCO device (Version=2,
TCOBASE=0x1060)
[  216.896402] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[  217.001241] Linux agpgart interface v0.102 (c) Dave Jones
[  217.007834] agpgart: Detected an Intel 915GM Chipset.
[  217.024646] agpgart: AGP aperture is 256M @ 0x0
[  217.044332] ACPI: PCI Interrupt 0000:06:04.3[B] -> GSI 17 (level,
low) -> IRQ 17
[  217.058492] sdhci: Secure Digital Host Controller Interface driver
[  217.058545] sdhci: Copyright(c) Pierre Ossman
[  217.058620] sdhci: SDHCI controller found at 0000:06:04.4 [104c:8034]
(rev 0)
[  217.058684] ACPI: PCI Interrupt 0000:06:04.4[D] -> GSI 19 (level,
low) -> IRQ 19
[  217.058832] mmc0: SDHCI at 0xc4009400 irq 19 DMA
[  217.058910] mmc1: SDHCI at 0xc4009000 irq 19 DMA
[  217.058988] mmc2: SDHCI at 0xc4006400 irq 19 DMA
[  217.590753] ieee80211: 802.11 data/management/control stack, git-1.1.13
[  217.590810] ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.intel.com>
[  217.622453] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.2.0kmprq
[  217.622511] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[  217.622637] ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 22 (level,
low) -> IRQ 22
[  217.622770] ipw2200: Detected Intel PRO/Wireless 2200BG Network
Connection
[  218.194017] ipw2200: Radio Frequency Kill Switch is On:
[  218.194020] Kill switch must be turned off for wireless networking to
work.
[  218.194193] ipw2200: Detected geography ZZM (11 802.11bg channels, 0
802.11a channels)
[  218.194287] Yenta: CardBus bridge found at 0000:06:04.0 [1179:ff00]
[  218.194356] Yenta: Enabling burst memory read transactions
[  218.194407] Yenta: Using CSCINT to route CSC interrupts to PCI
[  218.194460] Yenta: Routing CardBus interrupts to PCI
[  218.194515] Yenta TI: socket 0000:06:04.0, mfunc 0x10aa1b22, devctl 0x66
[  218.417563] Yenta: ISA IRQ mask 0x0cf8, PCI irq 16
[  218.417622] Socket status: 30000006
[  218.417675] Yenta: Raising subordinate bus# of parent bus (#06) from
#07 to #0a
[  218.417739] pcmcia: parent PCI bridge I/O window: 0x6000 - 0x6fff
[  218.417794] pcmcia: parent PCI bridge Memory window: 0xc4000000 -
0xc40fffff
[  218.417850] pcmcia: parent PCI bridge Memory window: 0x50000000 -
0x53ffffff
[  218.419219] ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level,
low) -> IRQ 17
[  219.231630] intel8x0_measure_ac97_clock: measured 50495 usecs
[  219.231686] intel8x0: clocking to 48000
[  219.357519] Capability LSM initialized
[  219.432905] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3])
[  219.468590] Time: acpi_pm clocksource has been installed.
[  219.481281] Non-volatile memory driver v1.2
[  219.493925] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
[  219.530293] IA-32 Microcode Update Driver: v1.14a
<tigran@aivazian.fsnet.co.uk>
[  219.542486] Machine check exception polling timer started.
[  219.592529] fuse init (API version 7.8)

Full 2.6.21-rc3 boot log with pci=noacpi:
[    0.000000] Linux version 2.6.21-rc3 (root@manwe) (gcc version 4.1.2
(Ubuntu 4.1.2-0ubuntu4)) #1 PREEMPT Fri Mar 9 01:54:11 CET 2007
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] sanitize start
[    0.000000] sanitize end
[    0.000000] copy_e820_map() start: 0000000000000000 size:
000000000009f800 end: 000000000009f800 type: 1
[    0.000000] copy_e820_map() type is E820_RAM
[    0.000000] copy_e820_map() start: 000000000009f800 size:
0000000000000800 end: 00000000000a0000 type: 2
[    0.000000] copy_e820_map() start: 00000000000d2000 size:
0000000000002000 end: 00000000000d4000 type: 2
[    0.000000] copy_e820_map() start: 00000000000dc000 size:
0000000000024000 end: 0000000000100000 type: 2
[    0.000000] copy_e820_map() start: 0000000000100000 size:
000000003fde0000 end: 000000003fee0000 type: 1
[    0.000000] copy_e820_map() type is E820_RAM
[    0.000000] copy_e820_map() start: 000000003fee0000 size:
000000000000a000 end: 000000003feea000 type: 3
[    0.000000] copy_e820_map() start: 000000003feea000 size:
0000000000016000 end: 000000003ff00000 type: 4
[    0.000000] copy_e820_map() start: 000000003ff00000 size:
0000000000100000 end: 0000000040000000 type: 2
[    0.000000] copy_e820_map() start: 00000000e0000000 size:
0000000010006000 end: 00000000f0006000 type: 2
[    0.000000] copy_e820_map() start: 00000000f0008000 size:
0000000000004000 end: 00000000f000c000 type: 2
[    0.000000] copy_e820_map() start: 00000000fed20000 size:
0000000000070000 end: 00000000fed90000 type: 2
[    0.000000] copy_e820_map() start: 00000000ff000000 size:
0000000001000000 end: 0000000100000000 type: 2
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
[    0.000000]  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003fee0000 (usable)
[    0.000000]  BIOS-e820: 000000003fee0000 - 000000003feea000 (ACPI data)
[    0.000000]  BIOS-e820: 000000003feea000 - 000000003ff00000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003ff00000 - 0000000040000000 (reserved)
[    0.000000]  BIOS-e820: 00000000e0000000 - 00000000f0006000 (reserved)
[    0.000000]  BIOS-e820: 00000000f0008000 - 00000000f000c000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
[    0.000000]  BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
[    0.000000] 126MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   261856
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   261856
[    0.000000] DMI present.
[    0.000000] ACPI: RSDP 000F6980, 0014 (r0 TOSCPL)
[    0.000000] ACPI: RSDT 3FEE276F, 0044 (r1 TOSCPL   RSDT    6040000 
LTP        0)
[    0.000000] ACPI: APIC 3FEE9E88, 0068 (r1 INTEL  ALVISO    6040000
LOHR       5F)
[    0.000000] ACPI: FACP 3FEE9EF0, 0074 (r1 TOSCPL ALVISO    6040000
LOHR       32)
[    0.000000] ACPI: DSDT 3FEE3217, 6C71 (r1 TOSCPL ALVISO    6040000
MSFT  100000E)
[    0.000000] ACPI: FACS 3FEFAFC0, 0040
[    0.000000] ACPI: BOOT 3FEE9FD8, 0028 (r1 PTLTD  $SBFTBL$  6040000 
LTP        1)
[    0.000000] ACPI: MCFG 3FEE9F9C, 003C (r1 INTEL  ALVISO    6040000
LOHR       5F)
[    0.000000] ACPI: SSDT 3FEE2FE5, 022E (r1 SataRe SataAhci     1000
INTL 20030224)
[    0.000000] ACPI: SSDT 3FEE2BAA, 022B (r1  PmRef  Cpu0Ist     3000
INTL 20030224)
[    0.000000] ACPI: SSDT 3FEE29CC, 01DE (r1  PmRef  Cpu0Cst     3001
INTL 20030224)
[    0.000000] ACPI: SSDT 3FEE27B3, 0219 (r1  PmRef    CpuPm     3000
INTL 20030224)
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:13 APIC version 20
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] Allocating PCI resources starting at 50000000 (gap:
40000000:a0000000)
[    0.000000] Built 1 zonelists.  Total pages: 259811
[    0.000000] Kernel command line: root=/dev/mapper/Base-Root ro single
pci=noacpi
[    0.000000] Found and enabled local APIC!
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] CPU 0 irqstacks, hard=c034f000 soft=c034e000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 1729.052 MHz processor.
[   28.094814] Console: colour VGA+ 80x25
[   28.098208] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[   28.098736] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[   28.122214] Memory: 1031112k/1047424k available (1606k kernel code,
15544k reserved, 544k data, 184k init, 129920k highmem)
[   28.122277] virtual kernel memory layout:
[   28.122279]     fixmap  : 0xfffaa000 - 0xfffff000   ( 340 kB)
[   28.122281]     pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
[   28.122282]     vmalloc : 0xf8800000 - 0xffbfe000   ( 115 MB)
[   28.122284]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   28.122286]       .init : 0xc031b000 - 0xc0349000   ( 184 kB)
[   28.122287]       .data : 0xc029183b - 0xc0319bb4   ( 544 kB)
[   28.122289]       .text : 0xc0100000 - 0xc029183b   (1606 kB)
[   28.122640] Checking if this processor honours the WP bit even in
supervisor mode... Ok.
[   28.182778] Calibrating delay using timer specific routine.. 3460.10
BogoMIPS (lpj=1730052)
[   28.182893] Security Framework v1.0.0 initialized
[   28.182952] Mount-cache hash table entries: 512
[   28.183089] CPU: L1 I cache: 32K, L1 D cache: 32K
[   28.183169] CPU: L2 cache: 2048K
[   28.183217] Intel machine check architecture supported.
[   28.183264] Intel machine check reporting enabled on CPU#0.
[   28.183318] CPU: Intel(R) Pentium(R) M processor 1.73GHz stepping 08
[   28.183435] Checking 'hlt' instruction... OK.
[   28.186871] ACPI: Core revision 20070126
[   28.186986] ACPI: Table DSDT replaced by host OS
[   28.187101] ACPI: DSDT 00000000, 6305 (r1 TOSCPL ALVISO    6040000
INTL 20051117)
[   28.189974] ACPI: setting ELCR to 0e00 (from 0c00)
[   28.400789] NET: Registered protocol family 16
[   28.400904] ACPI: bus type pci registered
[   28.400957] PCI: Using MMCONFIG
[   28.401645] Setting up standard PCI resources
[   28.406853] ACPI: Interpreter enabled
[   28.406900] ACPI: (supports S0 S3 S4 S5)
[   28.407132] ACPI: Using PIC for interrupt routing
[   28.452326] Linux Plug and Play Support v0.97 (c) Adam Belay
[   28.452378] pnp: PnP ACPI init
[   28.474767] pnp: PnP ACPI: found 9 devices
[   28.474837] PCI: Probing PCI hardware
[   28.475352] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[   28.475400] PCI quirk: region 1180-11bf claimed by ICH6 GPIO
[   28.475480] 0000:00:1f.1: trying to change BAR0 from 0000 to 01F0
[   28.475527] 0000:00:1f.1: trying to change BAR1 from 0000 to 03F4
[   28.475574] 0000:00:1f.1: trying to change BAR2 from 0000 to 0170
[   28.475621] 0000:00:1f.1: trying to change BAR3 from 0000 to 0374
[   28.476362] PCI: Transparent bridge - 0000:00:1e.0
[   28.476455] PCI: Bus #07 (-#0a) is hidden behind transparent bridge
#06 (-#07) (try 'pci=assign-busses')
[   28.476509] Please report the result to linux-kernel to fix this
permanently
[   28.477400] pnp: 00:01: ioport range 0xfe00-0xfe7f has been reserved
[   28.477448] pnp: 00:01: ioport range 0xfe80-0xfeff has been reserved
[   28.477496] pnp: 00:01: ioport range 0xff00-0xff7f has been reserved
[   28.477543] pnp: 00:01: iomem range 0xe0000000-0xefffffff has been
reserved
[   28.477591] pnp: 00:01: iomem range 0xf0000000-0xf0003fff has been
reserved
[   28.477638] Time: tsc clocksource has been installed.
[   28.477687] pnp: 00:01: iomem range 0xf0004000-0xf0004fff has been
reserved
[   28.477735] pnp: 00:01: iomem range 0xf0005000-0xf0005fff has been
reserved
[   28.508000] PCI: Bridge: 0000:00:01.0
[   28.508045]   IO window: 3000-3fff
[   28.508090]   MEM window: b8100000-b81fffff
[   28.508135]   PREFETCH window: c8000000-cfffffff
[   28.508181] PCI: Bridge: 0000:00:1c.0
[   28.508226]   IO window: 4000-4fff
[   28.508273]   MEM window: bc000000-bfffffff
[   28.508319]   PREFETCH window: d0000000-d3ffffff
[   28.508367] PCI: Bridge: 0000:00:1c.1
[   28.508412]   IO window: 5000-5fff
[   28.508458]   MEM window: c0000000-c3ffffff
[   28.508504]   PREFETCH window: d4000000-d7ffffff
[   28.508555] PCI: Bus 7, cardbus bridge: 0000:06:04.0
[   28.508600]   IO window: 00006400-000064ff
[   28.508648]   IO window: 00006800-000068ff
[   28.508695]   PREFETCH window: 50000000-53ffffff
[   28.508742]   MEM window: 54000000-57ffffff
[   28.508789] PCI: Bridge: 0000:00:1e.0
[   28.508834]   IO window: 6000-6fff
[   28.508881]   MEM window: c4000000-c40fffff
[   28.508927]   PREFETCH window: 50000000-53ffffff
[   28.509056] NET: Registered protocol family 2
[   28.517623] IP route cache hash table entries: 32768 (order: 5,
131072 bytes)
[   28.517744] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[   28.518638] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[   28.518950] TCP: Hash tables configured (established 131072 bind 65536)
[   28.518999] TCP reno registered
[   28.521728] checking if image is initramfs... it is
[   28.897082] Freeing initrd memory: 3943k freed
[   28.897258] Simple Boot Flag at 0x36 set to 0x1
[   28.897591] highmem bounce pool size: 64 pages
[   28.897638] Total HugeTLB memory allocated, 0
[   28.897770] io scheduler noop registered
[   28.897855] io scheduler cfq registered (default)
[   28.898234] assign_interrupt_mode Found MSI capability
[   28.898443] assign_interrupt_mode Found MSI capability
[   28.898670] assign_interrupt_mode Found MSI capability
[   28.900923] RAMDISK driver initialized: 16 RAM disks of 65536K size
1024 blocksize
[   28.901109] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at
0x60,0x64 irq 1,12
[   28.902057] i8042.c: Detected active multiplexing controller, rev 1.1.
[   28.902162] serio: i8042 KBD port at 0x60,0x64 irq 1
[   28.902241] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[   28.902314] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[   28.902401] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[   28.902470] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[   28.902560] mice: PS/2 mouse device common for all mice
[   28.902702] TCP cubic registered
[   28.902750] NET: Registered protocol family 1
[   28.902803] Using IPI Shortcut mode
[   28.903006] Freeing unused kernel memory: 184k freed
[   28.905169] input: AT Translated Set 2 keyboard as /class/input/input0
[   29.008326] Switched to high resolution mode on CPU 0
[   29.010655] 8139too Fast Ethernet driver 0.9.28
[   29.011221] eth0: RealTek RTL8139 at 0xf8820000, 00:0f:b0:a5:9a:81,
IRQ 11
[   29.013527] netconsole: local port 5000
[   29.013573] netconsole: local IP 192.168.0.20
[   29.013618] netconsole: interface eth0
[   29.013663] netconsole: remote port 5000
[   29.013708] netconsole: remote IP 192.168.0.1
[   29.013753] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[   29.013801] netconsole: device eth0 not up yet, forcing it
[   29.013879] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   29.014630] netconsole: carrier detect appears untrustworthy, waiting
4 seconds
[   33.029671] netconsole: network logging started
[   33.035522] SCSI subsystem initialized
[   34.041305] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5
Gbps 0x5 impl IDE mode
[   34.041363] ahci 0000:00:1f.2: flags: 64bit ncq pm led slum part
[   34.041503] ata1: SATA max UDMA/133 cmd 0xf8824d00 ctl 0x00000000
bmdma 0x00000000 irq 11
[   34.041628] ata2: SATA max UDMA/133 cmd 0xf8824d80 ctl 0x00000000
bmdma 0x00000000 irq 11
[   34.041754] ata3: SATA max UDMA/133 cmd 0xf8824e00 ctl 0x00000000
bmdma 0x00000000 irq 11
[   34.041881] ata4: SATA max UDMA/133 cmd 0xf8824e80 ctl 0x00000000
bmdma 0x00000000 irq 11
[   34.041942] scsi0 : ahci
[   34.499179] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   34.500247] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100
[   34.500297] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   34.501605] ata1.00: configured for UDMA/100
[   34.501655] scsi1 : ahci
[   34.804094] ata2: SATA link down (SStatus 0 SControl 0)
[   34.804147] scsi2 : ahci
[   35.107022] ata3: SATA link down (SStatus 0 SControl 300)
[   35.107075] scsi3 : ahci
[   35.409949] ata4: SATA link down (SStatus 0 SControl 0)
[   35.410086] scsi 0:0:0:0: Direct-Access     ATA      HTS541010G9SA00 
MBZO PQ: 0 ANSI: 5
[   35.414197] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12)
initialised: dm-devel@redhat.com
[   35.525666] usbcore: registered new interface driver usbfs
[   35.525759] usbcore: registered new interface driver hub
[   35.525834] usbcore: registered new device driver usb
[   35.526522] USB Universal Host Controller Interface driver v3.0
[   35.526634] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[   35.526769] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 1
[   35.526860] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00001800
[   35.527012] usb usb1: configuration #1 chosen from 1 choice
[   35.527090] hub 1-0:1.0: USB hub found
[   35.527140] hub 1-0:1.0: 2 ports detected
[   35.628035] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[   35.628131] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned
bus number 2
[   35.628224] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00001820
[   35.628362] usb usb2: configuration #1 chosen from 1 choice
[   35.628442] hub 2-0:1.0: USB hub found
[   35.628492] hub 2-0:1.0: 2 ports detected
[   35.728979] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[   35.729070] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned
bus number 3
[   35.729164] uhci_hcd 0000:00:1d.2: irq 11, io base 0x00001840
[   35.729308] usb usb3: configuration #1 chosen from 1 choice
[   35.729391] hub 3-0:1.0: USB hub found
[   35.729442] hub 3-0:1.0: 2 ports detected
[   35.829912] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[   35.829972] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned
bus number 4
[   35.830083] uhci_hcd 0000:00:1d.3: irq 10, io base 0x00001860
[   35.830216] usb usb4: configuration #1 chosen from 1 choice
[   35.830297] hub 4-0:1.0: USB hub found
[   35.830347] hub 4-0:1.0: 2 ports detected
[   35.833845] usb 1-1: new low speed USB device using uhci_hcd and
address 2
[   35.931272] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[   35.931352] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 5
[   35.931449] ehci_hcd 0000:00:1d.7: debug port 1
[   35.931505] ehci_hcd 0000:00:1d.7: irq 11, io mem 0xb8000000
[   35.935482] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[   35.935607] usb usb5: configuration #1 chosen from 1 choice
[   35.935689] hub 5-0:1.0: USB hub found
[   35.935740] hub 5-0:1.0: 8 ports detected
[   36.092619] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] 
MMIO=[c4006800-c4006fff]  Max Packet=[2048]  IR/IT contexts=[4/8]
[   36.092998] ata5: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6
bmdma 0x000118c0 irq 14
[   36.093093] ata6: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376
bmdma 0x000118c8 irq 15
[   36.093188] scsi4 : ata_piix
[   36.350721] usb 1-1: device not accepting address 2, error -71
[   36.398196] ata5.00: ATAPI, max UDMA/33
[   36.553176] ata5.00: configured for UDMA/33
[   36.553230] scsi5 : ata_piix
[   36.553348] ata6: port disabled. ignoring.
[   36.555292] scsi 4:0:0:0: CD-ROM            MATSHITA DVD-RAM UJ-841S 
1.50 PQ: 0 ANSI: 5
[   36.564056] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[   36.564122] sda: Write Protect is off
[   36.564221] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[   36.564332] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[   36.564386] sda: Write Protect is off
[   36.564478] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[   36.564535]  sda:<6>usb 1-1: new low speed USB device using uhci_hcd
and address 4
[   36.995244]  sda1 sda2 <<6>usb 1-1: configuration #1 chosen from 1 choice
[   37.009405]  sda5 sda6 > sda3
[   37.016674] sd 0:0:0:0: Attached scsi disk sda
[   37.019316] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   37.019376] scsi 4:0:0:0: Attached scsi generic sg1 type 5
[   37.024809] input: Logitech USB Receiver as /class/input/input1
[   37.025012] input: USB HID v1.10 Mouse [Logitech USB Receiver] on
usb-0000:00:1d.0-1
[   37.025333] usbcore: registered new interface driver usbhid
[   37.025382] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[   37.026312] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
xa/form2 cdda tray
[   37.026370] Uniform CD-ROM driver Revision: 3.20
[   37.362728] Attempting manual resume
[   37.419339] SGI XFS with ACLs, realtime, no debug enabled
[   37.472334] Filesystem "dm-0": Disabling barriers, not supported by
the underlying device
[   37.472746] XFS mounting filesystem dm-0
[   37.662579] Starting XFS recovery on filesystem: dm-0 (logdev: internal)
[   38.461059] Ending XFS recovery on filesystem: dm-0 (logdev: internal)
[   41.585513] Linux agpgart interface v0.102 (c) Dave Jones
[   41.724841] agpgart: Detected an Intel 915GM Chipset.
[   41.741921] agpgart: AGP aperture is 256M @ 0x0
[   41.757296] input: PS/2 Mouse as /class/input/input2
[   41.776092] input: AlpsPS/2 ALPS GlidePoint as /class/input/input3
[   41.804732] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
[   41.804867] iTCO_wdt: Found a ICH6-M TCO device (Version=2,
TCOBASE=0x1060)
[   41.804960] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   41.851929] Real Time Clock Driver v1.12ac
[   41.879265] input: PC Speaker as /class/input/input4
[   42.130778] ieee80211: 802.11 data/management/control stack, git-1.1.13
[   42.130835] ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.intel.com>
[   42.140470] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.2.0kmprq
[   42.140528] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[   42.140732] ipw2200: Detected Intel PRO/Wireless 2200BG Network
Connection
[   42.195824] sdhci: Secure Digital Host Controller Interface driver
[   42.195881] sdhci: Copyright(c) Pierre Ossman
[   43.540318] ipw2200: Radio Frequency Kill Switch is On:
[   43.540320] Kill switch must be turned off for wireless networking to
work.
[   43.540528] ipw2200: Detected geography ZZM (11 802.11bg channels, 0
802.11a channels)
[   43.540731] Yenta: CardBus bridge found at 0000:06:04.0 [1179:ff00]
[   43.540817] Yenta: Enabling burst memory read transactions
[   43.540869] Yenta: Using CSCINT to route CSC interrupts to PCI
[   43.540957] Yenta: Routing CardBus interrupts to PCI
[   43.541011] Yenta TI: socket 0000:06:04.0, mfunc 0x10aa1b22, devctl 0x66
[   43.764493] Yenta: ISA IRQ mask 0x00f8, PCI irq 10
[   43.764551] Socket status: 30000006
[   43.764641] Yenta: Raising subordinate bus# of parent bus (#06) from
#07 to #0a
[   43.764699] pcmcia: parent PCI bridge I/O window: 0x6000 - 0x6fff
[   43.764789] pcmcia: parent PCI bridge Memory window: 0xc4000000 -
0xc40fffff
[   43.764839] pcmcia: parent PCI bridge Memory window: 0x50000000 -
0x53ffffff
[   43.766222] sdhci: SDHCI controller found at 0000:06:04.4 [104c:8034]
(rev 0)
[   43.766360] mmc0: SDHCI at 0xc4009400 irq 10 DMA
[   43.766457] mmc1: SDHCI at 0xc4009000 irq 10 DMA
[   43.766552] mmc2: SDHCI at 0xc4006400 irq 10 DMA
[   44.580756] intel8x0_measure_ac97_clock: measured 50508 usecs
[   44.580812] intel8x0: clocking to 48000
[   44.704886] Capability LSM initialized
[   44.780120] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3])
[   44.801715] Time: acpi_pm clocksource has been installed.
[   44.828491] Non-volatile memory driver v1.2
[   44.841139] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
[   44.877491] IA-32 Microcode Update Driver: v1.14a
<tigran@aivazian.fsnet.co.uk>
[   44.889690] Machine check exception polling timer started.
[   44.939740] fuse init (API version 7.8)
[   67.168309] Restarting system.

Thanks
-- 
Mathieu

and try remove another quirk on this computers Re: [3/6] 2.6.21-rc2: known regressions

[Sergio Monteiro Basto]

[-- Attachment #1: Type: text/plain, Size: 7924 bytes --]

On Sat, 2007-03-10 at 02:09 +0100, Mathieu Bérard wrote:
> Jeff Garzik a écrit :
> > Adrian Bunk wrote:
> >> Subject    : NCQ problem with ahci and Hitachi drive
> >> References : http://lkml.org/lkml/2007/3/4/178
> >> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
> >> Status     : unknown
> >
> > according to the last message in that thread, it sounds like ACPI and
> > interrupt problems
> >
> Hi,
> after more testing with a 2.6.21-rc3, it appears that after several ata
> errors the boot process
> somehow continued as normal, after a "NCQ disabled due to excessive
> errors" message.
> "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
> does nothing.


Hi, I have a laptop quite similar to this report, but still running
2.4.20.
With /usr/bin/hal-device-manager on (00:1f.1) 82801FB/FBM/FR/FW/FRW
(ICH6 Family) IDE Controller (rev 03
I found that I have an Hitachi Travelstar 80GN. 

And your initial report point that you have an Hitachi Travelstar 5K100
and the patch http://lkml.org/lkml/2007/2/22/8 blacklist your HD ,
correct ? 

I will try 20-rc3 to see if I have any problem.
but blacklist it is not a good solution ... 

well I recently found a quirk that is apply on laptop that I mention
here. which I remove from my kernel because I don't have a Assus and my
laptop is quirked too. 

--- linux-2.6.20.i686/drivers/pci/quirks.c.orig 2007-03-04 04:52:21.000000000 +0000
+++ linux-2.6.20.i686/drivers/pci/quirks.c      2007-03-04 04:52:41.000000000 +0000
@@ -1121,8 +1121,8 @@ static void asus_hides_smbus_lpc_ich6(st
        iounmap(base);
        printk(KERN_INFO "PCI: Enabled ICH6/i801 SMBus device\n");
 }
-DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL,  PCI_DEVICE_ID_INTEL_ICH6_1,     asus_hides_smbus_lpc_ich6 );
-DECLARE_PCI_FIXUP_RESUME(PCI_VENDOR_ID_INTEL,  PCI_DEVICE_ID_INTEL_ICH6_1,     asus_hides_smbus_lpc_ich6 );
+/* DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL,       PCI_DEVICE_ID_INTEL_ICH6_1,     asus_hides_smbus_lpc_ich6 ); */
+/* DECLARE_PCI_FIXUP_RESUME(PCI_VENDOR_ID_INTEL,       PCI_DEVICE_ID_INTEL_ICH6_1,     asus_hides_smbus_lpc_ich6 ); */

 /*
  * SiS 96x south bridge: BIOS typically hides SMBus device...


With this quirk I got this oops on hibernate (but computer still
working) 

Suspending console(s)
eth1: Going into suspend...
ACPI: PCI interrupt for device 0000:02:04.0 disabled
ACPI: PCI interrupt for device 0000:00:1e.3 disabled
ACPI: PCI interrupt for device 0000:00:1e.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.7 disabled
ACPI: PCI interrupt for device 0000:00:1d.3 disabled
ACPI: PCI interrupt for device 0000:00:1d.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.1 disabled
ACPI: PCI interrupt for device 0000:00:1d.0 disabled
ipw2200: Unable to load ucode: -22
ipw2200: Unable to load firmware: -22
ipw2200: Failed to up device
swsusp: critical section:
swsusp: Need to copy 57480 pages
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
BUG: sleeping function called from invalid context at mm/slab.c:3035
in_atomic():0, irqs_disabled():1
no locks held by pm-hibernate/22979.
irq event stamp: 0
hardirqs last  enabled at (0): [<00000000>] 0x0
hardirqs last disabled at (0): [<c042580c>] copy_process+0x311/0x1249
softirqs last  enabled at (0): [<c042580c>] copy_process+0x311/0x1249
softirqs last disabled at (0): [<00000000>] 0x0
 [<c04051c9>] show_trace_log_lvl+0x1a/0x2f
 [<c040576e>] show_trace+0x12/0x14
 [<c04057f2>] dump_stack+0x16/0x18
 [<c0421266>] __might_sleep+0xc9/0xcf
 [<c0474cb1>] kmem_cache_alloc+0x28/0xc4
 [<c046bb50>] __get_vm_area_node+0x87/0x16f
 [<c046bcae>] __get_vm_area+0x22/0x28
 [<c046bcf3>] get_vm_area+0x3f/0x43
 [<c041f0ed>] __ioremap+0xa0/0xe6
 [<c041f147>] ioremap_nocache+0x14/0x79
 [<c04f070a>] asus_hides_smbus_lpc_ich6+0x37/0x61
 [<c04ef384>] pci_fixup_device+0x70/0x7c
 [<c04f0a70>] pci_device_resume_early+0x17/0x2e
 [<c0550779>] dpm_power_up+0x41/0x53
 [<c0550798>] device_power_up+0xd/0xf
 [<c0448bc4>] swsusp_suspend+0x55/0x62
 [<c044929c>] pm_suspend_disk+0xd5/0x181
 [<c04480a7>] enter_state+0x51/0x172
 [<c044824e>] state_store+0x86/0x9c
 [<c04b0a58>] subsys_attr_store+0x20/0x25
 [<c04b0b69>] sysfs_write_file+0xb8/0xe0
 [<c0478c68>] vfs_write+0xaf/0x163
 [<c04792b6>] sys_write+0x3d/0x61
 [<c0404058>] syscall_call+0x7/0xb
 =======================
PCI: Enabled ICH6/i801 SMBus device

removing quirk resolve the oops.

BTW I have an HP Compaq nx6110 , what laptop is yours ? 

ah! and WTF I don't attach your dmesg in a file ? 
 
> 
> lspci:
> 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML
> Express Processor to DRAM Controller (rev 03)
> 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI
> Express Root Port (rev 03)
> 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) PCI Express Port 1 (rev 03)
> 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) PCI Express Port 2 (rev 03)
> 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) USB UHCI #1 (rev 03)
> 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) USB UHCI #2 (rev 03)
> 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) USB UHCI #3 (rev 03)
> 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) USB UHCI #4 (rev 03)
> 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) USB2 EHCI Controller (rev 03)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
> 00:1e.2 Multimedia audio controller: Intel Corporation
> 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
> 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
> AC'97 Modem Controller (rev 03)
> 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface
> Bridge (rev 03)
> 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) IDE Controller (rev 03)
> 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA
> Controller (rev 03)
> 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
> SMBus Controller (rev 03)
> 01:00.0 VGA compatible controller: ATI Technologies Inc M24 [Radeon
> Mobility X600]
> 06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> 06:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG
> Network Connection (rev 05)
> 06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
> 06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394
> Host Controller
> 06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated
> FlashMedia Controller
> 06:04.4 Generic system peripheral [0805]: Texas Instruments
> PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
> 
> 
> /proc/interrupts:
>         CPU0      
>   0:       3242   IO-APIC-edge      timer
>   1:        863   IO-APIC-edge      i8042
>   8:          3   IO-APIC-edge      rtc
>   9:          1   IO-APIC-fasteoi   acpi
>  12:        116   IO-APIC-edge      i8042
>  14:        128   IO-APIC-edge      libata
>  15:          0   IO-APIC-edge      libata
>  16:          1   IO-APIC-fasteoi   uhci_hcd:usb4, yenta
>  17:          0   IO-APIC-fasteoi   tifm_7xx1, Intel ICH6
>  18:        249   IO-APIC-fasteoi   eth0
>  19:       2712   IO-APIC-fasteoi   libata, uhci_hcd:usb2, sdhci:slot0,
> sdhci:slot1, sdhci:slot2
>  20:         47   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5
>  21:          3   IO-APIC-fasteoi   uhci_hcd:usb3, ohci1394
>  22:          1   IO-APIC-fasteoi   ipw2200
> NMI:          0
> LOC:      15767
> ERR:          0
> MIS:          0


-- 
Sérgio M. B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]

Re: and try remove another quirk on this computers Re: [3/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Sat, 10 Mar 2007, Sergio Monteiro Basto wrote:
> 
> With this quirk I got this oops on hibernate (but computer still
> working) 

Well, strictly speaking it's a warning, not an oops per se. 

What happens is that the quirk wants to do an "ioremap_nocache()", which 
allocates memory, and that happens very early during initialization when 
interrupts are disabled.

And you're really not supposed to allocate memory, except using 
GFP_ATOMIC. But we've always been lax about that during early boot, so we 
have stuff that does. And resume ends up doing a lot of the same things 
early boot does, and shows issues like this.

So the quirk is probably still a good idea, and the warning message is 
just that - a very scary warning message, but not an indicator that 
anything is seriously screwed up for you.

(It is an indication of a real bug, though, even though it's harmless in 
practice in this case)

		Linus

Re: and try remove another quirk on this computers Re: [3/6] 2.6.21-rc2: known regressions

[Sergio Monteiro Basto]

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On Fri, 2007-03-09 at 21:41 -0800, Linus Torvalds wrote:
> 
> On Sat, 10 Mar 2007, Sergio Monteiro Basto wrote:
> > 
> > With this quirk I got this oops on hibernate (but computer still
> > working) 
> 
> Well, strictly speaking it's a warning, not an oops per se. 
> 
> What happens is that the quirk wants to do an "ioremap_nocache()", which 
> allocates memory, and that happens very early during initialization when 
> interrupts are disabled.
> 
> And you're really not supposed to allocate memory, except using 
> GFP_ATOMIC. But we've always been lax about that during early boot, so we 
> have stuff that does. And resume ends up doing a lot of the same things 
> early boot does, and shows issues like this.
> 
> So the quirk is probably still a good idea, and the warning message is 
> just that - a very scary warning message, but not an indicator that 
> anything is seriously screwed up for you.
> 
> (It is an indication of a real bug, though, even though it's harmless in 
> practice in this case)

Hi, thanks 
Just to write, I test last fedora kernel(2.6.20-1.2981.fc7) which is
based on 2.6.21-rc3-git5, without any problem, less than the scary
warning, talked in this email :)

Best regards,
-- 
Sérgio M. B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]

Re: [3/6] 2.6.21-rc2: known regressions

[Tejun Heo]

Mathieu Bérard wrote:
> Jeff Garzik a écrit :
>> Adrian Bunk wrote:
>>> Subject    : NCQ problem with ahci and Hitachi drive
>>> References : http://lkml.org/lkml/2007/3/4/178
>>> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
>>> Status     : unknown
>> according to the last message in that thread, it sounds like ACPI and
>> interrupt problems
>>
> Hi,
> after more testing with a 2.6.21-rc3, it appears that after several ata
> errors the boot process
> somehow continued as normal, after a "NCQ disabled due to excessive
> errors" message.
> "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
> does nothing.

I was mistaken.  It can't be IRQ routing problem.  I somehow thought the
port was a ata_piix one.  Considering the reported broken NCQ feature on
the device GTF might be mangling with the drive to disable NCQ or
something.  Does giving "libata.noacpi=1" make any difference?

Thanks.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [3/6] 2.6.21-rc2: known regressions

[Tejun Heo]

Mathieu Bérard wrote:
> Jeff Garzik a écrit :
>> Adrian Bunk wrote:
>>> Subject    : NCQ problem with ahci and Hitachi drive
>>> References : http://lkml.org/lkml/2007/3/4/178
>>> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
>>> Status     : unknown
>> according to the last message in that thread, it sounds like ACPI and
>> interrupt problems
>>
> Hi,
> after more testing with a 2.6.21-rc3, it appears that after several ata
> errors the boot process
> somehow continued as normal, after a "NCQ disabled due to excessive
> errors" message.
> "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
> does nothing.

I was mistaken.  It can't be IRQ routing problem.  I somehow thought the
port was a ata_piix one.  Considering the reported broken NCQ feature on
the device GTF might be mangling with the drive to disable NCQ or
something.  Does giving "libata.noacpi=1" make any difference?

Thanks.

-- 
tejun

Re: [3/6] 2.6.21-rc2: known regressions

[Mathieu Bérard]

Tejun Heo a écrit :
> > Mathieu Bérard wrote:
>> >> Jeff Garzik a écrit :
>>> >>> Adrian Bunk wrote:
>>>> >>>> Subject    : NCQ problem with ahci and Hitachi drive
>>>> >>>> References : http://lkml.org/lkml/2007/3/4/178
>>>> >>>> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
>>>> >>>> Status     : unknown
>>> >>> according to the last message in that thread, it sounds like
ACPI and
>>> >>> interrupt problems
>>> >>>
>> >> Hi,
>> >> after more testing with a 2.6.21-rc3, it appears that after
several ata
>> >> errors the boot process
>> >> somehow continued as normal, after a "NCQ disabled due to excessive
>> >> errors" message.
>> >> "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
>> >> does nothing.
> >
> > I was mistaken.  It can't be IRQ routing problem.  I somehow thought the
> > port was a ata_piix one.  Considering the reported broken NCQ feature on
> > the device GTF might be mangling with the drive to disable NCQ or
> > something.  Does giving "libata.noacpi=1" make any difference?
> >

Hi,
libata.noacpi=1 worked. The drive is up and running with NCQ on.
Here is the PATA/SATA related part of my DSDT table with the _GTF methods:

Device (PATA)
{
    Name (_ADR, 0x001F0001)
    OperationRegion (PACS, PCI_Config, 0x40, 0xC0)
    Field (PACS, DWordAcc, NoLock, Preserve)
    {
        PRIT,   16,
        Offset (0x04),
        PSIT,   4,
        Offset (0x08),
        SYNC,   4,
        Offset (0x0A),
        SDT0,   2,
            ,   2,
        SDT1,   2,
        Offset (0x14),
        ICR0,   4,
        ICR1,   4,
        ICR2,   4,
        ICR3,   4,
        ICR4,   4,
        ICR5,   4
    }

    Device (PRID)
    {
        Name (_ADR, 0x00)
        Method (_GTM, 0, NotSerialized)
        {
            Name (PBUF, Buffer (0x14)
            {
                0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                0x00, 0x00, 0x00, 0x00
            })
            CreateDWordField (PBUF, 0x00, PIO0)
            CreateDWordField (PBUF, 0x04, DMA0)
            CreateDWordField (PBUF, 0x08, PIO1)
            CreateDWordField (PBUF, 0x0C, DMA1)
            CreateDWordField (PBUF, 0x10, FLAG)
            Store (GETP (PRIT), PIO0)
            Store (GDMA (And (SYNC, 0x01), And (ICR3, 0x01), And (ICR0,
0x01), SDT0, And (ICR1, 0x01)), DMA0)
            If (LEqual (DMA0, 0xFFFFFFFF))
            {
                Store (PIO0, DMA0)
            }

            If (And (PRIT, 0x4000))
            {
                If (LEqual (And (PRIT, 0x90), 0x80))
                {
                    Store (0x0384, PIO1)
                }
                Else
                {
                    Store (GETT (PSIT), PIO1)
                }
            }
            Else
            {
                Store (0xFFFFFFFF, PIO1)
            }

            Store (GDMA (And (SYNC, 0x02), And (ICR3, 0x02), And (ICR0,
0x02), SDT1, And (ICR1, 0x02)), DMA1)
            If (LEqual (DMA1, 0xFFFFFFFF))
            {
                Store (PIO1, DMA1)
            }

            Store (GETF (And (SYNC, 0x01), And (SYNC, 0x02), PRIT), FLAG)
            If (And (LEqual (PIO0, 0xFFFFFFFF), LEqual (DMA0, 0xFFFFFFFF)))
            {
                Store (0x78, PIO0)
                Store (0x14, DMA0)
                Store (0x03, FLAG)
            }

            Return (PBUF)
        }

        Method (_STM, 3, NotSerialized)
        {
            CreateDWordField (Arg0, 0x00, PIO0)
            CreateDWordField (Arg0, 0x04, DMA0)
            CreateDWordField (Arg0, 0x08, PIO1)
            CreateDWordField (Arg0, 0x0C, DMA1)
            CreateDWordField (Arg0, 0x10, FLAG)
            If (LEqual (SizeOf (Arg1), 0x0200))
            {
                And (PRIT, 0x40F0, PRIT)
                And (SYNC, 0x02, SYNC)
                Store (0x00, SDT0)
                And (ICR0, 0x02, ICR0)
                And (ICR1, 0x02, ICR1)
                And (ICR3, 0x02, ICR3)
                And (ICR5, 0x02, ICR5)
                CreateWordField (Arg1, 0x62, W490)
                CreateWordField (Arg1, 0x6A, W530)
                CreateWordField (Arg1, 0x7E, W630)
                CreateWordField (Arg1, 0x80, W640)
                CreateWordField (Arg1, 0xB0, W880)
                CreateWordField (Arg1, 0xBA, W930)
                Or (PRIT, 0x8004, PRIT)
                If (LAnd (And (FLAG, 0x02), And (W490, 0x0800)))
                {
                    Or (PRIT, 0x02, PRIT)
                }

                Or (PRIT, SETP (PIO0, W530, W640), PRIT)
                If (And (FLAG, 0x01))
                {
                    Or (SYNC, 0x01, SYNC)
                    Store (SDMA (DMA0), SDT0)
                    If (LLess (DMA0, 0x1E))
                    {
                        Or (ICR3, 0x01, ICR3)
                    }

                    If (LLess (DMA0, 0x3C))
                    {
                        Or (ICR0, 0x01, ICR0)
                    }

                    If (And (W930, 0x2000))
                    {
                        Or (ICR1, 0x01, ICR1)
                    }
                }
            }

            If (LEqual (SizeOf (Arg2), 0x0200))
            {
                And (PRIT, 0x3F0F, PRIT)
                Store (0x00, PSIT)
                And (SYNC, 0x01, SYNC)
                Store (0x00, SDT1)
                And (ICR0, 0x01, ICR0)
                And (ICR1, 0x01, ICR1)
                And (ICR3, 0x01, ICR3)
                And (ICR5, 0x01, ICR5)
                CreateWordField (Arg2, 0x62, W491)
                CreateWordField (Arg2, 0x6A, W531)
                CreateWordField (Arg2, 0x7E, W631)
                CreateWordField (Arg2, 0x80, W641)
                CreateWordField (Arg2, 0xB0, W881)
                CreateWordField (Arg2, 0xBA, W931)
                Or (PRIT, 0x8040, PRIT)
                If (LAnd (And (FLAG, 0x08), And (W491, 0x0800)))
                {
                    Or (PRIT, 0x20, PRIT)
                }

                If (And (FLAG, 0x10))
                {
                    Or (PRIT, 0x4000, PRIT)
                    If (LGreater (PIO1, 0xF0))
                    {
                        Or (PRIT, 0x80, PRIT)
                    }
                    Else
                    {
                        Or (PRIT, 0x10, PRIT)
                        Store (SETT (PIO1, W531, W641), PSIT)
                    }
                }

                If (And (FLAG, 0x04))
                {
                    Or (SYNC, 0x02, SYNC)
                    Store (SDMA (DMA1), SDT1)
                    If (LLess (DMA1, 0x1E))
                    {
                        Or (ICR3, 0x02, ICR3)
                    }

                    If (LLess (DMA1, 0x3C))
                    {
                        Or (ICR0, 0x02, ICR0)
                    }

                    If (And (W931, 0x2000))
                    {
                        Or (ICR1, 0x02, ICR1)
                    }
                }
            }
        }

        Device (P_D0)
        {
            Name (_ADR, 0x00)
            Method (_GTF, 0, NotSerialized)
            {
                Name (PIB0, Buffer (0x0E)
                {
                    0x03, 0x00, 0x00, 0x00, 0x00, 0xA0, 0xEF, 0x03,
                    0x00, 0x00, 0x00, 0x00, 0xA0, 0xEF
                })
                CreateByteField (PIB0, 0x01, PMD0)
                CreateByteField (PIB0, 0x08, DMD0)
                If (And (PRIT, 0x02))
                {
                    If (LEqual (And (PRIT, 0x09), 0x08))
                    {
                        Store (0x08, PMD0)
                    }
                    Else
                    {
                        Store (0x0A, PMD0)
                        ShiftRight (And (PRIT, 0x0300), 0x08, Local0)
                        ShiftRight (And (PRIT, 0x3000), 0x0C, Local1)
                        Add (Local0, Local1, Local2)
                        If (LEqual (0x03, Local2))
                        {
                            Store (0x0B, PMD0)
                        }

                        If (LEqual (0x05, Local2))
                        {
                            Store (0x0C, PMD0)
                        }
                    }
                }
                Else
                {
                    Store (0x01, PMD0)
                }

                If (And (SYNC, 0x01))
                {
                    Store (Or (SDT0, 0x40), DMD0)
                    If (And (ICR1, 0x01))
                    {
                        If (And (ICR0, 0x01))
                        {
                            Add (DMD0, 0x02, DMD0)
                        }

                        If (And (ICR3, 0x01))
                        {
                            Store (0x45, DMD0)
                        }
                    }
                }
                Else
                {
                    Or (Subtract (And (PMD0, 0x07), 0x02), 0x20, DMD0)
                }

                Return (PIB0)
            }
        }

        Device (P_D1)
        {
            Name (_ADR, 0x01)
            Method (_GTF, 0, NotSerialized)
            {
                Name (PIB1, Buffer (0x0E)
                {
                    0x03, 0x00, 0x00, 0x00, 0x00, 0xB0, 0xEF, 0x03,
                    0x00, 0x00, 0x00, 0x00, 0xB0, 0xEF
                })
                CreateByteField (PIB1, 0x01, PMD1)
                CreateByteField (PIB1, 0x08, DMD1)
                If (And (PRIT, 0x20))
                {
                    If (LEqual (And (PRIT, 0x90), 0x80))
                    {
                        Store (0x08, PMD1)
                    }
                    Else
                    {
                        Add (And (PSIT, 0x03), ShiftRight (And (PSIT,
0x0C), 0x02), Local0)
                        If (LEqual (0x05, Local0))
                        {
                            Store (0x0C, PMD1)
                        }
                        Else
                        {
                            If (LEqual (0x03, Local0))
                            {
                                Store (0x0B, PMD1)
                            }
                            Else
                            {
                                Store (0x0A, PMD1)
                            }
                        }
                    }
                }
                Else
                {
                    Store (0x01, PMD1)
                }

                If (And (SYNC, 0x02))
                {
                    Store (Or (SDT1, 0x40), DMD1)
                    If (And (ICR1, 0x02))
                    {
                        If (And (ICR0, 0x02))
                        {
                            Add (DMD1, 0x02, DMD1)
                        }

                        If (And (ICR3, 0x02))
                        {
                            Store (0x45, DMD1)
                        }
                    }
                }
                Else
                {
                    Or (Subtract (And (PMD1, 0x07), 0x02), 0x20, DMD1)
                }

                Return (PIB1)
            }
        }
    }
}

Device (SATA)
{
    Name (_ADR, 0x001F0002)
    OperationRegion (SACS, PCI_Config, 0x40, 0xC0)
    Field (SACS, DWordAcc, NoLock, Preserve)
    {
        PRIT,   16,
        SECT,   16,
        PSIT,   4,
        SSIT,   4,
        Offset (0x08),
        SYNC,   4,
        Offset (0x0A),
        SDT0,   2,
            ,   2,
        SDT1,   2,
        Offset (0x0B),
        SDT2,   2,
            ,   2,
        SDT3,   2,
        Offset (0x14),
        ICR0,   4,
        ICR1,   4,
        ICR2,   4,
        ICR3,   4,
        ICR4,   4,
        ICR5,   4,
        Offset (0x50),
        MAPV,   2,
            ,   5,
        USCC,   1,
        Offset (0x52),
        PCSR,   8
    }
}

-- 
Mathieu
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [3/6] 2.6.21-rc2: known regressions

[Mathieu Bérard]

Tejun Heo a écrit :
> > Mathieu Bérard wrote:
>> >> Jeff Garzik a écrit :
>>> >>> Adrian Bunk wrote:
>>>> >>>> Subject    : NCQ problem with ahci and Hitachi drive
>>>> >>>> References : http://lkml.org/lkml/2007/3/4/178
>>>> >>>> Submitter  : Mathieu Bérard <Mathieu.Berard@crans.org>
>>>> >>>> Status     : unknown
>>> >>> according to the last message in that thread, it sounds like
ACPI and
>>> >>> interrupt problems
>>> >>>
>> >> Hi,
>> >> after more testing with a 2.6.21-rc3, it appears that after
several ata
>> >> errors the boot process
>> >> somehow continued as normal, after a "NCQ disabled due to excessive
>> >> errors" message.
>> >> "pci=noacpi" or "noacpi" parameters workarounds the problem "irqpoll"
>> >> does nothing.
> >
> > I was mistaken.  It can't be IRQ routing problem.  I somehow thought the
> > port was a ata_piix one.  Considering the reported broken NCQ feature on
> > the device GTF might be mangling with the drive to disable NCQ or
> > something.  Does giving "libata.noacpi=1" make any difference?
> >

Hi,
libata.noacpi=1 worked. The drive is up and running with NCQ on.
Here is the PATA/SATA related part of my DSDT table with the _GTF methods:

Device (PATA)
{
    Name (_ADR, 0x001F0001)
    OperationRegion (PACS, PCI_Config, 0x40, 0xC0)
    Field (PACS, DWordAcc, NoLock, Preserve)
    {
        PRIT,   16,
        Offset (0x04),
        PSIT,   4,
        Offset (0x08),
        SYNC,   4,
        Offset (0x0A),
        SDT0,   2,
            ,   2,
        SDT1,   2,
        Offset (0x14),
        ICR0,   4,
        ICR1,   4,
        ICR2,   4,
        ICR3,   4,
        ICR4,   4,
        ICR5,   4
    }

    Device (PRID)
    {
        Name (_ADR, 0x00)
        Method (_GTM, 0, NotSerialized)
        {
            Name (PBUF, Buffer (0x14)
            {
                0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
                0x00, 0x00, 0x00, 0x00
            })
            CreateDWordField (PBUF, 0x00, PIO0)
            CreateDWordField (PBUF, 0x04, DMA0)
            CreateDWordField (PBUF, 0x08, PIO1)
            CreateDWordField (PBUF, 0x0C, DMA1)
            CreateDWordField (PBUF, 0x10, FLAG)
            Store (GETP (PRIT), PIO0)
            Store (GDMA (And (SYNC, 0x01), And (ICR3, 0x01), And (ICR0,
0x01), SDT0, And (ICR1, 0x01)), DMA0)
            If (LEqual (DMA0, 0xFFFFFFFF))
            {
                Store (PIO0, DMA0)
            }

            If (And (PRIT, 0x4000))
            {
                If (LEqual (And (PRIT, 0x90), 0x80))
                {
                    Store (0x0384, PIO1)
                }
                Else
                {
                    Store (GETT (PSIT), PIO1)
                }
            }
            Else
            {
                Store (0xFFFFFFFF, PIO1)
            }

            Store (GDMA (And (SYNC, 0x02), And (ICR3, 0x02), And (ICR0,
0x02), SDT1, And (ICR1, 0x02)), DMA1)
            If (LEqual (DMA1, 0xFFFFFFFF))
            {
                Store (PIO1, DMA1)
            }

            Store (GETF (And (SYNC, 0x01), And (SYNC, 0x02), PRIT), FLAG)
            If (And (LEqual (PIO0, 0xFFFFFFFF), LEqual (DMA0, 0xFFFFFFFF)))
            {
                Store (0x78, PIO0)
                Store (0x14, DMA0)
                Store (0x03, FLAG)
            }

            Return (PBUF)
        }

        Method (_STM, 3, NotSerialized)
        {
            CreateDWordField (Arg0, 0x00, PIO0)
            CreateDWordField (Arg0, 0x04, DMA0)
            CreateDWordField (Arg0, 0x08, PIO1)
            CreateDWordField (Arg0, 0x0C, DMA1)
            CreateDWordField (Arg0, 0x10, FLAG)
            If (LEqual (SizeOf (Arg1), 0x0200))
            {
                And (PRIT, 0x40F0, PRIT)
                And (SYNC, 0x02, SYNC)
                Store (0x00, SDT0)
                And (ICR0, 0x02, ICR0)
                And (ICR1, 0x02, ICR1)
                And (ICR3, 0x02, ICR3)
                And (ICR5, 0x02, ICR5)
                CreateWordField (Arg1, 0x62, W490)
                CreateWordField (Arg1, 0x6A, W530)
                CreateWordField (Arg1, 0x7E, W630)
                CreateWordField (Arg1, 0x80, W640)
                CreateWordField (Arg1, 0xB0, W880)
                CreateWordField (Arg1, 0xBA, W930)
                Or (PRIT, 0x8004, PRIT)
                If (LAnd (And (FLAG, 0x02), And (W490, 0x0800)))
                {
                    Or (PRIT, 0x02, PRIT)
                }

                Or (PRIT, SETP (PIO0, W530, W640), PRIT)
                If (And (FLAG, 0x01))
                {
                    Or (SYNC, 0x01, SYNC)
                    Store (SDMA (DMA0), SDT0)
                    If (LLess (DMA0, 0x1E))
                    {
                        Or (ICR3, 0x01, ICR3)
                    }

                    If (LLess (DMA0, 0x3C))
                    {
                        Or (ICR0, 0x01, ICR0)
                    }

                    If (And (W930, 0x2000))
                    {
                        Or (ICR1, 0x01, ICR1)
                    }
                }
            }

            If (LEqual (SizeOf (Arg2), 0x0200))
            {
                And (PRIT, 0x3F0F, PRIT)
                Store (0x00, PSIT)
                And (SYNC, 0x01, SYNC)
                Store (0x00, SDT1)
                And (ICR0, 0x01, ICR0)
                And (ICR1, 0x01, ICR1)
                And (ICR3, 0x01, ICR3)
                And (ICR5, 0x01, ICR5)
                CreateWordField (Arg2, 0x62, W491)
                CreateWordField (Arg2, 0x6A, W531)
                CreateWordField (Arg2, 0x7E, W631)
                CreateWordField (Arg2, 0x80, W641)
                CreateWordField (Arg2, 0xB0, W881)
                CreateWordField (Arg2, 0xBA, W931)
                Or (PRIT, 0x8040, PRIT)
                If (LAnd (And (FLAG, 0x08), And (W491, 0x0800)))
                {
                    Or (PRIT, 0x20, PRIT)
                }

                If (And (FLAG, 0x10))
                {
                    Or (PRIT, 0x4000, PRIT)
                    If (LGreater (PIO1, 0xF0))
                    {
                        Or (PRIT, 0x80, PRIT)
                    }
                    Else
                    {
                        Or (PRIT, 0x10, PRIT)
                        Store (SETT (PIO1, W531, W641), PSIT)
                    }
                }

                If (And (FLAG, 0x04))
                {
                    Or (SYNC, 0x02, SYNC)
                    Store (SDMA (DMA1), SDT1)
                    If (LLess (DMA1, 0x1E))
                    {
                        Or (ICR3, 0x02, ICR3)
                    }

                    If (LLess (DMA1, 0x3C))
                    {
                        Or (ICR0, 0x02, ICR0)
                    }

                    If (And (W931, 0x2000))
                    {
                        Or (ICR1, 0x02, ICR1)
                    }
                }
            }
        }

        Device (P_D0)
        {
            Name (_ADR, 0x00)
            Method (_GTF, 0, NotSerialized)
            {
                Name (PIB0, Buffer (0x0E)
                {
                    0x03, 0x00, 0x00, 0x00, 0x00, 0xA0, 0xEF, 0x03,
                    0x00, 0x00, 0x00, 0x00, 0xA0, 0xEF
                })
                CreateByteField (PIB0, 0x01, PMD0)
                CreateByteField (PIB0, 0x08, DMD0)
                If (And (PRIT, 0x02))
                {
                    If (LEqual (And (PRIT, 0x09), 0x08))
                    {
                        Store (0x08, PMD0)
                    }
                    Else
                    {
                        Store (0x0A, PMD0)
                        ShiftRight (And (PRIT, 0x0300), 0x08, Local0)
                        ShiftRight (And (PRIT, 0x3000), 0x0C, Local1)
                        Add (Local0, Local1, Local2)
                        If (LEqual (0x03, Local2))
                        {
                            Store (0x0B, PMD0)
                        }

                        If (LEqual (0x05, Local2))
                        {
                            Store (0x0C, PMD0)
                        }
                    }
                }
                Else
                {
                    Store (0x01, PMD0)
                }

                If (And (SYNC, 0x01))
                {
                    Store (Or (SDT0, 0x40), DMD0)
                    If (And (ICR1, 0x01))
                    {
                        If (And (ICR0, 0x01))
                        {
                            Add (DMD0, 0x02, DMD0)
                        }

                        If (And (ICR3, 0x01))
                        {
                            Store (0x45, DMD0)
                        }
                    }
                }
                Else
                {
                    Or (Subtract (And (PMD0, 0x07), 0x02), 0x20, DMD0)
                }

                Return (PIB0)
            }
        }

        Device (P_D1)
        {
            Name (_ADR, 0x01)
            Method (_GTF, 0, NotSerialized)
            {
                Name (PIB1, Buffer (0x0E)
                {
                    0x03, 0x00, 0x00, 0x00, 0x00, 0xB0, 0xEF, 0x03,
                    0x00, 0x00, 0x00, 0x00, 0xB0, 0xEF
                })
                CreateByteField (PIB1, 0x01, PMD1)
                CreateByteField (PIB1, 0x08, DMD1)
                If (And (PRIT, 0x20))
                {
                    If (LEqual (And (PRIT, 0x90), 0x80))
                    {
                        Store (0x08, PMD1)
                    }
                    Else
                    {
                        Add (And (PSIT, 0x03), ShiftRight (And (PSIT,
0x0C), 0x02), Local0)
                        If (LEqual (0x05, Local0))
                        {
                            Store (0x0C, PMD1)
                        }
                        Else
                        {
                            If (LEqual (0x03, Local0))
                            {
                                Store (0x0B, PMD1)
                            }
                            Else
                            {
                                Store (0x0A, PMD1)
                            }
                        }
                    }
                }
                Else
                {
                    Store (0x01, PMD1)
                }

                If (And (SYNC, 0x02))
                {
                    Store (Or (SDT1, 0x40), DMD1)
                    If (And (ICR1, 0x02))
                    {
                        If (And (ICR0, 0x02))
                        {
                            Add (DMD1, 0x02, DMD1)
                        }

                        If (And (ICR3, 0x02))
                        {
                            Store (0x45, DMD1)
                        }
                    }
                }
                Else
                {
                    Or (Subtract (And (PMD1, 0x07), 0x02), 0x20, DMD1)
                }

                Return (PIB1)
            }
        }
    }
}

Device (SATA)
{
    Name (_ADR, 0x001F0002)
    OperationRegion (SACS, PCI_Config, 0x40, 0xC0)
    Field (SACS, DWordAcc, NoLock, Preserve)
    {
        PRIT,   16,
        SECT,   16,
        PSIT,   4,
        SSIT,   4,
        Offset (0x08),
        SYNC,   4,
        Offset (0x0A),
        SDT0,   2,
            ,   2,
        SDT1,   2,
        Offset (0x0B),
        SDT2,   2,
            ,   2,
        SDT3,   2,
        Offset (0x14),
        ICR0,   4,
        ICR1,   4,
        ICR2,   4,
        ICR3,   4,
        ICR4,   4,
        ICR5,   4,
        Offset (0x50),
        MAPV,   2,
            ,   5,
        USCC,   1,
        Offset (0x52),
        PCSR,   8
    }
}

-- 
Mathieu

Re: [3/6] 2.6.21-rc2: known regressions

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 97 bytes --]

Can you apply the attached patch and report what the kernel says with
ACPI turned on?

-- 
tejun

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 565 bytes --]

diff --git a/drivers/ata/libata-acpi.c b/drivers/ata/libata-acpi.c
index 019d8ff..6a27a7f 100644
--- a/drivers/ata/libata-acpi.c
+++ b/drivers/ata/libata-acpi.c
@@ -473,8 +473,8 @@ static void taskfile_load_raw(struct ata_port *ap,
 	struct ata_taskfile tf;
 	unsigned int err;
 
-	if (ata_msg_probe(ap))
-		ata_dev_printk(atadev, KERN_DEBUG, "%s: (0x1f1-1f7): hex: "
+	if (1 || ata_msg_probe(ap))
+		ata_dev_printk(atadev, KERN_INFO, "%s: (0x1f1-1f7): hex: "
 			"%02x %02x %02x %02x %02x %02x %02x\n",
 			__FUNCTION__,
 			gtf->tfa[0], gtf->tfa[1], gtf->tfa[2],

Re: [3/6] 2.6.21-rc2: known regressions

[Mathieu Bérard]

Tejun Heo a écrit :
> Can you apply the attached patch and report what the kernel says with
> ACPI turned on?
>
>   
Hi,
I got this:
[   13.523816] SCSI subsystem initialized
[   13.528914] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level,
low) -> IRQ 19
[   14.529383] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5
Gbps 0x5 impl IDE mode
[   14.529439] ahci 0000:00:1f.2: flags: 64bit ncq pm led slum part
[   14.529565] ata1: SATA max UDMA/133 cmd 0xf8824d00 ctl 0x00000000
bmdma 0x00000000 irq 19
[   14.529683] ata2: SATA max UDMA/133 cmd 0xf8824d80 ctl 0x00000000
bmdma 0x00000000 irq 19
[   14.529801] ata3: SATA max UDMA/133 cmd 0xf8824e00 ctl 0x00000000
bmdma 0x00000000 irq 19
[   14.529921] ata4: SATA max UDMA/133 cmd 0xf8824e80 ctl 0x00000000
bmdma 0x00000000 irq 19
[   14.529984] scsi0 : ahci
[   14.987273] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   15.031823] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00
00 a0 ef
[   15.032119] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100
[   15.032168] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   15.034170] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00
00 a0 ef
[   15.034464] ata1.00: configured for UDMA/100
[   15.034515] scsi1 : ahci
[   15.337188] ata2: SATA link down (SStatus 0 SControl 0)
[   15.337241] scsi2 : ahci
[   15.640125] ata3: SATA link down (SStatus 0 SControl 300)
[   15.640178] scsi3 : ahci
[   15.943062] ata4: SATA link down (SStatus 0 SControl 0)
[   15.943191] scsi 0:0:0:0: Direct-Access     ATA      HTS541010G9SA00 
MBZO PQ: 0 ANSI: 5

and for each ata errors:
[   47.089624] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2
frozen
[   47.089682] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
cdb 0x0 data 4096 in
[   47.089684]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[   47.392549] ata1: soft resetting port
[   47.547533] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   47.549756] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00
00 a0 ef
[   47.552600] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00
00 a0 ef
[   47.552969] ata1.00: configured for UDMA/100
[   47.553022] ata1: EH complete
[   47.553104] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[   47.553160] sda: Write Protect is off
[   47.553226] SCSI device sda: write cache: enabled, read cache:
enabled, doesn't support DPO or FUA

-- 
Mathieu

Re: [3/6] 2.6.21-rc2: known regressions

[Tejun Heo]

Hello,

Mathieu Bérard wrote:
> [   15.031823] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00
> 00 a0 ef

Okay, this is interesting.  This is Enable Device-Initiated Interface
Power State Transitions.  So, after this command is executed the device
will try to transit to partial/slumber SATA PHY power states at its
discretion, which is all cool and dandy in theory but depending on
controller and drive firmware can cause all sorts of problems.

The NCQ problem you're seeing probably is some side effect of device
initiated link PS.  Can't tell whether the controller or the drive's
firmware is problem without further info.  Due to blacklisting, NCQ
won't be turned on your drive in future kernels and link PS doesn't seem
to cause any problem no non-NCQ, so your case is taken care of here but
this leaves me a bit worried about what _GTF feeds us.

I don't think we can reliably filter out command TFs as it might even
contain vendor-specific commands but it might be better to always log
TFs executed for _GTF such that we at least know what's going on with
the drive.

Thanks.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [3/6] 2.6.21-rc2: known regressions

[Tejun Heo]

Hello,

Mathieu Bérard wrote:
> [   15.031823] ata1.00: taskfile_load_raw: (0x1f1-1f7): hex: 10 03 00 00
> 00 a0 ef

Okay, this is interesting.  This is Enable Device-Initiated Interface
Power State Transitions.  So, after this command is executed the device
will try to transit to partial/slumber SATA PHY power states at its
discretion, which is all cool and dandy in theory but depending on
controller and drive firmware can cause all sorts of problems.

The NCQ problem you're seeing probably is some side effect of device
initiated link PS.  Can't tell whether the controller or the drive's
firmware is problem without further info.  Due to blacklisting, NCQ
won't be turned on your drive in future kernels and link PS doesn't seem
to cause any problem no non-NCQ, so your case is taken care of here but
this leaves me a bit worried about what _GTF feeds us.

I don't think we can reliably filter out command TFs as it might even
contain vendor-specific commands but it might be better to always log
TFs executed for _GTF such that we at least know what's going on with
the drive.

Thanks.

-- 
tejun

Re: [3/6] 2.6.21-rc2: known regressions

[Mathieu Bérard]

Tejun Heo a écrit :
> Hello,
>
>
> Due to blacklisting, NCQ
> won't be turned on your drive in future kernels.
>
>   
Hello thanks.
I have found on Hitachi website the technical datasheets of my drive
model:
http://www.hitachigst.com/tech/techlib.nsf/techdocs/28DCCB17E0EEC5A086256F4E006E2F5B/$file/5K100_SATA_sp1.2.pdf
It seems to state that the drive does not support NCQ...

--
Mathieu

[4/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : Asus A8N-VM motherboard:
             framebuffer/console boot failure boot failure (ACPI related)
References : http://lkml.org/lkml/2007/2/23/132
Submitter  : Andrew Nelless <andrew@nelless.net>
Caused-By  : Len Brown <len.brown@intel.com>
             commit 7f8f97c3cc75d5783d0b45cf323dedf17684be19
Handled-By : Antonino A. Daplas <adaplas@gmail.com>
Status     : problem is being debugged


Subject    : LCD is dimmed  (ibm-acpi related)
References : http://lkml.org/lkml/2007/2/25/206
Submitter  : Jiri Kosina <jikos@jikos.cz>
Caused-By  : Richard Purdie <rpurdie@rpsys.net>
             commit 994efacdf9a087b52f71e620b58dfa526b0cf928
Handled-By : Jiri Kosina <jikos@jikos.cz>
             Richard Purdie <rpurdie@rpsys.net>
             Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Status     : patches are being discussed


Subject    : no backlight on radeon
References : http://lkml.org/lkml/2007/2/19/1
Submitter  : Yaroslav Halchenko <kernel@onerussian.com>
             Alex Romosan <romosan@sycorax.lbl.gov>
             David Miller <davem@davemloft.net>
Caused-By  : James Simmons <jsimmons@infradead.org>
             commit e0e34ef7f02915cfe50e501e9f32c24217177a96
Handled-By : Richard Purdie <rpurdie@rpsys.net>
             James Simmons <jsimmons@infradead.org>
             Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Status     : problem is being discussed


Subject    : nvidiafb broken
References : http://lkml.org/lkml/2007/2/24/36
Submitter  : Andreas Schwab <schwab@suse.de>
Caused-By  : Richard Purdie <rpurdie@rpsys.net>
             commit 599a52d12629394236d785615808845823875868
Handled-By : Richard Purdie <rpurdie@rpsys.net>
Patch      : http://lkml.org/lkml/2007/2/26/43
Status     : patch available

Re: [4/6] 2.6.21-rc2: known regressions

[Antonino A. Daplas]

On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
> This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> that are not yet fixed in Linus' tree.
> 
> If you find your name in the Cc header, you are either submitter of one
> of the bugs, maintainer of an affectected subsystem or driver, a patch
> of you caused a breakage or I'm considering you in any other way
> possibly involved with one or more of these issues.
> 
> Due to the huge amount of recipients, please trim the Cc when answering.
> 
> 
> Subject    : Asus A8N-VM motherboard:
>              framebuffer/console boot failure boot failure (ACPI related)
> References : http://lkml.org/lkml/2007/2/23/132
> Submitter  : Andrew Nelless <andrew@nelless.net>
> Caused-By  : Len Brown <len.brown@intel.com>
>              commit 7f8f97c3cc75d5783d0b45cf323dedf17684be19
> Handled-By : Antonino A. Daplas <adaplas@gmail.com>
> Status     : problem is being debugged
> 

This is not a framebuffer nor console problem.

I think Andrew Nelless confirmed that the cause is from the above
commit. How to fix it, I don't know.  Perhaps the
acpi_skip_timer_override boot option has to be used.

Tony

Re: [4/6] 2.6.21-rc2: known regressions

[Andrew]

On Mon, March 5, 2007 10:35 am, Antonino A. Daplas wrote:
>
> This is not a framebuffer nor console problem.
>
>
> I think Andrew Nelless confirmed that the cause is from the above
> commit. How to fix it, I don't know.  Perhaps the acpi_skip_timer_override boot option has to
> be used.
>
> Tony
>

Yes, apologies for taking so long with this.
I tried the acpi_skip_timer_override boot option last night,
after Tony pointed it out, and this also works around the
problem.

To summarize the cause is the changes made to early-quirks.c
in the mentioned commit and when this is reverted the problem
goes away.

There doesn't seem to be any sign of a living HPET on this
board or any way of enabling it in the current BIOS revision
but it seems on intermittent boots the check in early-quirks.c
returns, the timer override doesn't happen, and the kernel
fails to boot properly.

Btw, this is the Asus A8N-VM *CSM* main board, the non-CSM
variety actually has a nForce 410 rather than an
nForce 430 chip. I don't know whether they behave any
differently but the two boards actually have different BIOS
releases.

If reverting the commit would disable the HPET on boards
that do actually support it I personally don't mind using
the acpi_skip_timer_override workaround.

-
  Andrew

Re: [4/6] 2.6.21-rc2: known regressions

[Len Brown]

On Monday 05 March 2007 05:35, Antonino A. Daplas wrote:
> On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
> > This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> > that are not yet fixed in Linus' tree.
> > 
> > If you find your name in the Cc header, you are either submitter of one
> > of the bugs, maintainer of an affectected subsystem or driver, a patch
> > of you caused a breakage or I'm considering you in any other way
> > possibly involved with one or more of these issues.
> > 
> > Due to the huge amount of recipients, please trim the Cc when answering.
> > 
> > 
> > Subject    : Asus A8N-VM motherboard:
> >              framebuffer/console boot failure boot failure (ACPI related)
> > References : http://lkml.org/lkml/2007/2/23/132
> > Submitter  : Andrew Nelless <andrew@nelless.net>
> > Caused-By  : Len Brown <len.brown@intel.com>
> >              commit 7f8f97c3cc75d5783d0b45cf323dedf17684be19
> > Handled-By : Antonino A. Daplas <adaplas@gmail.com>
> > Status     : problem is being debugged
> > 
> 
> This is not a framebuffer nor console problem.
> 
> I think Andrew Nelless confirmed that the cause is from the above
> commit. How to fix it, I don't know.  Perhaps the
> acpi_skip_timer_override boot option has to be used.

Looks like I got fooled by the negative logic for the nvidia_bugs().
Please test this patch -- it should fix it,
as well as simplify the code a bit.

thanks,
-Len


Subject: ACPI: repair nvidia early quirk breakage on x86_64

x86_64 nvidia_bugs() broke when we bailed out on not finding the HPET.
However, the quirk works by checking for _not_ finding the HPET...

Delete the nvidia_hpet_detected flag and simply test for
not finding the HPET, which is simple to do now that
acpi_table_parse returns 1 on failure.

Signed-off-by: Len Brown <len.brown@intel.com>
---
 i386/kernel/acpi/earlyquirk.c |    7 +------
 x86_64/kernel/early-quirks.c  |    9 +--------
 2 files changed, 2 insertions(+), 14 deletions(-)

diff --git a/arch/i386/kernel/acpi/earlyquirk.c b/arch/i386/kernel/acpi/earlyquirk.c
index bf86f76..7fdba8a 100644
--- a/arch/i386/kernel/acpi/earlyquirk.c
+++ b/arch/i386/kernel/acpi/earlyquirk.c
@@ -14,11 +14,8 @@
 
 #ifdef CONFIG_ACPI
 
-static int nvidia_hpet_detected __initdata;
-
 static int __init nvidia_hpet_check(struct acpi_table_header *header)
 {
-	nvidia_hpet_detected = 1;
 	return 0;
 }
 #endif
@@ -29,9 +26,7 @@ static int __init check_bridge(int vendor, int device)
 	/* According to Nvidia all timer overrides are bogus unless HPET
 	   is enabled. */
 	if (!acpi_use_timer_override && vendor == PCI_VENDOR_ID_NVIDIA) {
-		nvidia_hpet_detected = 0;
-		acpi_table_parse(ACPI_SIG_HPET, nvidia_hpet_check);
-		if (nvidia_hpet_detected == 0) {
+		if (acpi_table_parse(ACPI_SIG_HPET, nvidia_hpet_check) {
 			acpi_skip_timer_override = 1;
 			  printk(KERN_INFO "Nvidia board "
                        "detected. Ignoring ACPI "
diff --git a/arch/x86_64/kernel/early-quirks.c b/arch/x86_64/kernel/early-quirks.c
index 8047ea8..dec587b 100644
--- a/arch/x86_64/kernel/early-quirks.c
+++ b/arch/x86_64/kernel/early-quirks.c
@@ -30,11 +30,8 @@ static void via_bugs(void)
 
 #ifdef CONFIG_ACPI
 
-static int nvidia_hpet_detected __initdata;
-
 static int __init nvidia_hpet_check(struct acpi_table_header *header)
 {
-	nvidia_hpet_detected = 1;
 	return 0;
 }
 #endif
@@ -52,11 +49,7 @@ static void nvidia_bugs(void)
 	if (acpi_use_timer_override)
 		return;
 
-	nvidia_hpet_detected = 0;
-	if (acpi_table_parse(ACPI_SIG_HPET, nvidia_hpet_check))
-		return;
-
-	if (nvidia_hpet_detected == 0) {
+	if (acpi_table_parse(ACPI_SIG_HPET, nvidia_hpet_check)) {
 		acpi_skip_timer_override = 1;
 		printk(KERN_INFO "Nvidia board "
 		       "detected. Ignoring ACPI "

Re: [4/6] 2.6.21-rc2: known regressions

[Andrew]

On Thu, March 8, 2007 11:28 pm, Len Brown wrote:
> On Monday 05 March 2007 05:35, Antonino A. Daplas wrote:
>
>
> Looks like I got fooled by the negative logic for the nvidia_bugs().
> Please test this patch -- it should fix it,
> as well as simplify the code a bit.
>
> thanks, -Len
>

Yep. You can knock this one off the regression
list :)

Thanks,
  Andrew

Re: [4/6] 2.6.21-rc2: known regressions

[Richard Purdie]

On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
> Subject    : LCD is dimmed  (ibm-acpi related)
> References : http://lkml.org/lkml/2007/2/25/206
> Submitter  : Jiri Kosina <jikos@jikos.cz>
> Caused-By  : Richard Purdie <rpurdie@rpsys.net>
>              commit 994efacdf9a087b52f71e620b58dfa526b0cf928
> Handled-By : Jiri Kosina <jikos@jikos.cz>
>              Richard Purdie <rpurdie@rpsys.net>
>              Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Status     : patches are being discussed

The confirmed fix is in the ACPI test branch for this.

> Subject    : no backlight on radeon
> References : http://lkml.org/lkml/2007/2/19/1
> Submitter  : Yaroslav Halchenko <kernel@onerussian.com>
>              Alex Romosan <romosan@sycorax.lbl.gov>
>              David Miller <davem@davemloft.net>
> Caused-By  : James Simmons <jsimmons@infradead.org>
>              commit e0e34ef7f02915cfe50e501e9f32c24217177a96
> Handled-By : Richard Purdie <rpurdie@rpsys.net>
>              James Simmons <jsimmons@infradead.org>
>              Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Status     : problem is being discussed
> 
> 
> Subject    : nvidiafb broken
> References : http://lkml.org/lkml/2007/2/24/36
> Submitter  : Andreas Schwab <schwab@suse.de>
> Caused-By  : Richard Purdie <rpurdie@rpsys.net>
>              commit 599a52d12629394236d785615808845823875868
> Handled-By : Richard Purdie <rpurdie@rpsys.net>
> Patch      : http://lkml.org/lkml/2007/2/26/43
> Status     : patch available

The confirmed fixes for both of these are in the backlight tree. I was
waiting for any further feedback on the first issue above but will send
them to Linus now.

Cheers,

Richard

[GIT PULL] ibm-acpi 2.6.21-rc3 regression fixes

[Henrique de Moraes Holschuh]

On Mon, 05 Mar 2007, Richard Purdie wrote:
> On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
> > Subject    : LCD is dimmed  (ibm-acpi related)
> > References : http://lkml.org/lkml/2007/2/25/206
> > Submitter  : Jiri Kosina <jikos@jikos.cz>
> > Caused-By  : Richard Purdie <rpurdie@rpsys.net>
> >              commit 994efacdf9a087b52f71e620b58dfa526b0cf928
> > Handled-By : Jiri Kosina <jikos@jikos.cz>
> >              Richard Purdie <rpurdie@rpsys.net>
> >              Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> > Status     : patches are being discussed
> 
> The confirmed fix is in the ACPI test branch for this.

Len, since this is being tracked as a regression, please pull from
git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git
branch acpi-release

to receive the following patches:
      ACPI: ibm-acpi: fix initial status of backlight device
      ACPI: ibm-acpi: improve backlight power handling

against v2.6.21-rc3.

They are obvious bug-fixes, and address the above regression plus a related
problem in ibm-acpi backlight handling.

If we get these two patches into mainline, I will proceed to rediff the
pending 2.6.22 ibm-acpi stuff for acpi-test, so that you don't have any
extra work when the time comes to merge the ibm-acpi queue into acpi-test.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[PATCH] ACPI: ibm-acpi: fix initial status of backlight device

[Henrique de Moraes Holschuh]

The brightness class core does not update the initial status of the
device's brightness at register time.  Do it by ourselves.

Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Richard Purdie <rpurdie@rpsys.net>
---
 drivers/acpi/ibm_acpi.c |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index 4cc534e..7c1b418 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -1711,6 +1711,12 @@ static struct backlight_ops ibm_backlight_data = {
 
 static int brightness_init(void)
 {
+	int b;
+
+	b = brightness_get(NULL);
+	if (b < 0)
+		return b;
+
 	ibm_backlight_device = backlight_device_register("ibm", NULL, NULL,
 							 &ibm_backlight_data);
 	if (IS_ERR(ibm_backlight_device)) {
@@ -1718,7 +1724,9 @@ static int brightness_init(void)
 		return PTR_ERR(ibm_backlight_device);
 	}
 
-        ibm_backlight_device->props.max_brightness = 7;
+	ibm_backlight_device->props.max_brightness = 7;
+	ibm_backlight_device->props.brightness = b;
+	backlight_update_status(ibm_backlight_device);
 
 	return 0;
 }
-- 
1.5.0.3

Re: [PATCH] ACPI: ibm-acpi: fix initial status of backlight device

[Len Brown]

we checked this in already back on 2/22
it is on the ibm branch that i'll included in the next 2.6.21 pull request.

thanks,
-Len

On Thursday 08 March 2007 03:28, Henrique de Moraes Holschuh wrote:
> The brightness class core does not update the initial status of the
> device's brightness at register time.  Do it by ourselves.
> 
> Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Acked-by: Richard Purdie <rpurdie@rpsys.net>
> ---
>  drivers/acpi/ibm_acpi.c |   10 +++++++++-
>  1 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
> index 4cc534e..7c1b418 100644
> --- a/drivers/acpi/ibm_acpi.c
> +++ b/drivers/acpi/ibm_acpi.c
> @@ -1711,6 +1711,12 @@ static struct backlight_ops ibm_backlight_data = {
>  
>  static int brightness_init(void)
>  {
> +	int b;
> +
> +	b = brightness_get(NULL);
> +	if (b < 0)
> +		return b;
> +
>  	ibm_backlight_device = backlight_device_register("ibm", NULL, NULL,
>  							 &ibm_backlight_data);
>  	if (IS_ERR(ibm_backlight_device)) {
> @@ -1718,7 +1724,9 @@ static int brightness_init(void)
>  		return PTR_ERR(ibm_backlight_device);
>  	}
>  
> -        ibm_backlight_device->props.max_brightness = 7;
> +	ibm_backlight_device->props.max_brightness = 7;
> +	ibm_backlight_device->props.brightness = b;
> +	backlight_update_status(ibm_backlight_device);
>  
>  	return 0;
>  }

[PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

Improve the backlight code to emulate as much as possible the power
management events, as we are unable to really power on or power off the
backlight.

Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Richard Purdie <rpurdie@rpsys.net>
---
 drivers/acpi/ibm_acpi.c |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index 7c1b418..63d7a85 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -86,6 +86,7 @@
 
 #include <linux/proc_fs.h>
 #include <linux/backlight.h>
+#include <linux/fb.h>
 #include <asm/uaccess.h>
 
 #include <linux/dmi.h>
@@ -1701,7 +1702,10 @@ static int brightness_write(char *buf)
 
 static int brightness_update_status(struct backlight_device *bd)
 {
-	return brightness_set(bd->props.brightness);
+	return brightness_set(
+		(bd->props.fb_blank == FB_BLANK_UNBLANK &&
+		 bd->props.power == FB_BLANK_UNBLANK) ?
+				bd->props.brightness : 0);
 }
 
 static struct backlight_ops ibm_backlight_data = {
-- 
1.5.0.3

Re: [PATCH] ACPI: ibm-acpi: improve backlight power handling

[Len Brown]

Applied.

thanks,
-Len

On Thursday 08 March 2007 03:28, Henrique de Moraes Holschuh wrote:
> Improve the backlight code to emulate as much as possible the power
> management events, as we are unable to really power on or power off the
> backlight.
> 
> Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> Acked-by: Richard Purdie <rpurdie@rpsys.net>
> ---
>  drivers/acpi/ibm_acpi.c |    6 +++++-
>  1 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
> index 7c1b418..63d7a85 100644
> --- a/drivers/acpi/ibm_acpi.c
> +++ b/drivers/acpi/ibm_acpi.c
> @@ -86,6 +86,7 @@
>  
>  #include <linux/proc_fs.h>
>  #include <linux/backlight.h>
> +#include <linux/fb.h>
>  #include <asm/uaccess.h>
>  
>  #include <linux/dmi.h>
> @@ -1701,7 +1702,10 @@ static int brightness_write(char *buf)
>  
>  static int brightness_update_status(struct backlight_device *bd)
>  {
> -	return brightness_set(bd->props.brightness);
> +	return brightness_set(
> +		(bd->props.fb_blank == FB_BLANK_UNBLANK &&
> +		 bd->props.power == FB_BLANK_UNBLANK) ?
> +				bd->props.brightness : 0);
>  }
>  
>  static struct backlight_ops ibm_backlight_data = {

[5/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : soft lockup detected on CPU#0
References : http://lkml.org/lkml/2007/3/3/152
Submitter  : Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Handled-By : Thomas Gleixner <tglx@linutronix.de>
Status     : unknown


Subject    : dynticks makes ksoftirqd1 use unreasonable amount of cpu time
References : http://bugzilla.kernel.org/show_bug.cgi?id=8100
Submitter  : Emil Karlson <jkarlson@cc.hut.fi>
Handled-By : Thomas Gleixner <tglx@linutronix.de>
Status     : problem is being debugged


Subject    : ThinkPad T60: system doesn't come out of suspend to RAM
             (CONFIG_NO_HZ)
References : http://lkml.org/lkml/2007/2/22/391
Submitter  : Michael S. Tsirkin <mst@mellanox.co.il>
Handled-By : Thomas Gleixner <tglx@linutronix.de>
             Ingo Molnar <mingo@elte.hu>
Status     : unknown


Subject    : macbook pro suspend to ram broken  (clockevents)
References : http://lkml.org/lkml/2007/3/4/110
Submitter  : Soeren Sonnenburg <kernel@nn7.de>
Caused-By  : Thomas Gleixner <tglx@linutronix.de>
             commit e9e2cdb412412326c4827fc78ba27f410d837e6e
Status     : unknown


Subject    : i386: no boot with nmi_watchdog=1  (clockevents)
References : http://lkml.org/lkml/2007/2/21/208
Submitter  : Daniel Walker <dwalker@mvista.com>
Caused-By  : Thomas Gleixner <tglx@linutronix.de>
             commit e9e2cdb412412326c4827fc78ba27f410d837e6e
Handled-By : Thomas Gleixner <tglx@linutronix.de>
Status     : problem is being debugged

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Adrian Bunk <bunk@stusta.de> wrote:

> Subject    : i386: no boot with nmi_watchdog=1  (clockevents)
> References : http://lkml.org/lkml/2007/2/21/208
> Submitter  : Daniel Walker <dwalker@mvista.com>
> Caused-By  : Thomas Gleixner <tglx@linutronix.de>
>              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> Handled-By : Thomas Gleixner <tglx@linutronix.de>
> Status     : problem is being debugged

FYI, this is not a "wont boot" problem, this should be a "NMI watchdog 
does not work" problem - which has far lower severity. Also, Thomas did 
a fix for this which is now in -mm.

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Andrew Morton]

On Mon, 5 Mar 2007 08:57:47 +0100 Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Adrian Bunk <bunk@stusta.de> wrote:
> 
> > Subject    : i386: no boot with nmi_watchdog=1  (clockevents)
> > References : http://lkml.org/lkml/2007/2/21/208
> > Submitter  : Daniel Walker <dwalker@mvista.com>
> > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > Handled-By : Thomas Gleixner <tglx@linutronix.de>
> > Status     : problem is being debugged
> 
> FYI, this is not a "wont boot" problem, this should be a "NMI watchdog 
> does not work" problem - which has far lower severity. Also, Thomas did 
> a fix for this which is now in -mm.
>

yup, you should be able to cross this one off, Adrian.  The fix worked for me,
at least.

Re: [5/6] 2.6.21-rc2: known regressions

[Daniel Walker]

On Mon, 2007-03-05 at 00:13 -0800, Andrew Morton wrote:
> On Mon, 5 Mar 2007 08:57:47 +0100 Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > * Adrian Bunk <bunk@stusta.de> wrote:
> > 
> > > Subject    : i386: no boot with nmi_watchdog=1  (clockevents)
> > > References : http://lkml.org/lkml/2007/2/21/208
> > > Submitter  : Daniel Walker <dwalker@mvista.com>
> > > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> > >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > > Handled-By : Thomas Gleixner <tglx@linutronix.de>
> > > Status     : problem is being debugged
> > 
> > FYI, this is not a "wont boot" problem, this should be a "NMI watchdog 
> > does not work" problem - which has far lower severity. Also, Thomas did 
> > a fix for this which is now in -mm.
> >
> 
> yup, you should be able to cross this one off, Adrian.  The fix worked for me,
> at least.

I didn't see a fix for this one go by .. I'll check the usual places I
guess ..

Daniel

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Daniel Walker <dwalker@mvista.com> wrote:

> > > FYI, this is not a "wont boot" problem, this should be a "NMI 
> > > watchdog does not work" problem - which has far lower severity. 
> > > Also, Thomas did a fix for this which is now in -mm.
> > 
> > yup, you should be able to cross this one off, Adrian.  The fix 
> > worked for me, at least.
> 
> I didn't see a fix for this one go by .. I'll check the usual places I 
> guess ..

find it below.

	Ingo

------------------------------------------------------
Subject: fix "NMI appears to be stuck"
From: Thomas Gleixner <tglx@linutronix.de>

  Testing NMI watchdog ... CPU#0: NMI appears to be stuck (54->54)!
  CPU#1: NMI appears to be stuck (0->0)!

Keep the PIT/HPET alive when nmi_watchdog = 1 is given on the command
line.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 arch/i386/kernel/apic.c |   11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)

diff -puN arch/i386/kernel/apic.c~fix-nmi-appears-to-be-stuck arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c~fix-nmi-appears-to-be-stuck
+++ a/arch/i386/kernel/apic.c
@@ -493,8 +493,15 @@ void __init setup_boot_APIC_clock(void)
 		/* No broadcast on UP ! */
 		if (num_possible_cpus() == 1)
 			return;
-	} else
-		lapic_clockevent.features &= ~CLOCK_EVT_FEAT_DUMMY;
+	} else {
+		/*
+		 * If nmi_watchdog is set to IO_APIC, we need the
+		 * PIT/HPET going. So we register lapic as a dummy
+		 * device.
+		 */
+		if (nmi_watchdog != NMI_IO_APIC)
+			lapic_clockevent.features &= ~CLOCK_EVT_FEAT_DUMMY;
+	}
 
 	/* Setup the lapic or request the broadcast */
 	setup_APIC_timer();

Re: [5/6] 2.6.21-rc2: known regressions

[Daniel Walker]

On Mon, 2007-03-05 at 16:27 +0100, Ingo Molnar wrote:
> * Daniel Walker <dwalker@mvista.com> wrote:
> 
> > > > FYI, this is not a "wont boot" problem, this should be a "NMI 
> > > > watchdog does not work" problem - which has far lower severity. 
> > > > Also, Thomas did a fix for this which is now in -mm.
> > > 
> > > yup, you should be able to cross this one off, Adrian.  The fix 
> > > worked for me, at least.
> > 
> > I didn't see a fix for this one go by .. I'll check the usual places I 
> > guess ..
> 
> find it below.

This fix gets the NMI to tick like the timer (in /proc/interrupts) ..
However, now that it's ticking I don't think it's actually working
properly ..

I used this simple test case given by you a long time ago,

main ()
{
iopl(3);
for (;;) 
        asm("cli");

}

This doesn't look like a regression tho, 2.6.19-rc6 has the same
behavior ..

Daniel

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Daniel Walker <dwalker@mvista.com> wrote:

> I used this simple test case given by you a long time ago,
> 
> main ()
> {
> iopl(3);
> for (;;) 
>         asm("cli");
> 
> }
> 
> This doesn't look like a regression tho, 2.6.19-rc6 has the same 
> behavior ..

hm, so this doesnt get detected as a lockup at all? That's bad and needs 
fixing ...

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Bill Davidsen]

Ingo Molnar wrote:
> * Adrian Bunk <bunk@stusta.de> wrote:
> 
>> Subject    : i386: no boot with nmi_watchdog=1  (clockevents)
>> References : http://lkml.org/lkml/2007/2/21/208
>> Submitter  : Daniel Walker <dwalker@mvista.com>
>> Caused-By  : Thomas Gleixner <tglx@linutronix.de>
>>              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
>> Handled-By : Thomas Gleixner <tglx@linutronix.de>
>> Status     : problem is being debugged
> 
> FYI, this is not a "wont boot" problem, this should be a "NMI watchdog 
> does not work" problem - which has far lower severity. Also, Thomas did 
> a fix for this which is now in -mm.
> 
If a system normally runs a watchdog, and some do, then nmi would be 
forced on by grub.comf and the system would not boot. And if the system 
was counting on nmi to look for a hanging problem, "nmi does not work" 
would be a real problem if the failure was silent.

Actually, a lack of nmi would be worse than not booting, it would be a 
time bomb waiting for a bad moment to hang.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Bill Davidsen <davidsen@tmr.com> wrote:

> If a system normally runs a watchdog, and some do, then nmi would be 
> forced on by grub.comf and the system would not boot. [...]

uhm, what? The NMI watchdog is totally optional. If it doesnt work, we 
print some stuff and just continue with the bootup.

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

On Mon, Mar 05, 2007 at 08:57:47AM +0100, Ingo Molnar wrote:
> 
> * Adrian Bunk <bunk@stusta.de> wrote:
> 
> > Subject    : i386: no boot with nmi_watchdog=1  (clockevents)
> > References : http://lkml.org/lkml/2007/2/21/208
> > Submitter  : Daniel Walker <dwalker@mvista.com>
> > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > Handled-By : Thomas Gleixner <tglx@linutronix.de>
> > Status     : problem is being debugged
> 
> FYI, this is not a "wont boot" problem, this should be a "NMI watchdog 
> does not work" problem - which has far lower severity. Also, Thomas did 
> a fix for this which is now in -mm.

Thanks for your corrections, it's now:

Subject    : i386: NMI watchdog does not work  (clockevents)
References : http://lkml.org/lkml/2007/2/21/208
Submitter  : Daniel Walker <dwalker@mvista.com>
Caused-By  : Thomas Gleixner <tglx@linutronix.de>
             commit e9e2cdb412412326c4827fc78ba27f410d837e6e
Fixed-By   : Thomas Gleixner <tglx@linutronix.de>
Commit     : a5f5e43e2b1377392f9afe93aca29b9abf1d6a44
Status     : fixed in -rc3


> 	Ingo

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [5/6] 2.6.21-rc2: known regressions

[Thomas Gleixner]

On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
> Subject    : ThinkPad T60: system doesn't come out of suspend to RAM
>              (CONFIG_NO_HZ)
> References : http://lkml.org/lkml/2007/2/22/391
> Submitter  : Michael S. Tsirkin <mst@mellanox.co.il>
> Handled-By : Thomas Gleixner <tglx@linutronix.de>
>              Ingo Molnar <mingo@elte.hu>
> Status     : unknown
> 
> Subject    : macbook pro suspend to ram broken  (clockevents)
> References : http://lkml.org/lkml/2007/3/4/110
> Submitter  : Soeren Sonnenburg <kernel@nn7.de>
> Caused-By  : Thomas Gleixner <tglx@linutronix.de>
>              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> Status     : unknown

I can reproduce this on my dual core VAIO. There are some issues:

1) clockevents code needs probably a resume fix, which I'm working on

2) The BOGOMIPS calibration of CPU#1 after resume is completely hosed.
CPU#1 has ~ 200000 Bogomips after resume, which is off by factor 500.
BOGOMIPS is calibrated vs. jiffies, This was also observed by Ingo on
his T60. This is similar to the LAPIC calibration problems I had seen
before the LAPIC rework. IRQ#0 comes in extremly slow (probably caused
by SMM crap, e.g. PS/2 keyboard emulation)

3) on suspend we shut down CPU#1 on dual core machines. resume restarts
CPU#1. Now one would expect that acpi_processor_power_verify would be
called, so that the "LAPIC/TSC stops in C3"-workaround gets applied to
CPU#1. Len confirmed that it should be called, when the cpu is brought
online. This was not noticed before as the old apic code kept the
broadcast bit on cpu shutdown.

Len, can you please look into #3 ?

> Subject    : dynticks makes ksoftirqd1 use unreasonable amount of cpu time
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8100
> Submitter  : Emil Karlson <jkarlson@cc.hut.fi>
> Handled-By : Thomas Gleixner <tglx@linutronix.de>
> Status     : problem is being debugged

Delayed until the above is sorted out.

	tglx

Re: [5/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> > 
> > Subject    : macbook pro suspend to ram broken  (clockevents)
> > References : http://lkml.org/lkml/2007/3/4/110
> > Submitter  : Soeren Sonnenburg <kernel@nn7.de>
> > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > Status     : unknown
> 
> I can reproduce this on my dual core VAIO. There are some issues:

Yeah, I think I can too, on my dual-core Mac Mini. 

I'm not done with my bisection, but e9e2cdb4 is among the 28 commits left, 
so I'm pretty sure I'm hitting the same bug. I'll do a few more bootups to 
be 100% sure.

		Linus

Re: [5/6] 2.6.21-rc2: known regressions

[Thomas Gleixner]

On Mon, 2007-03-05 at 15:45 -0800, Linus Torvalds wrote:
> 
> On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> > > 
> > > Subject    : macbook pro suspend to ram broken  (clockevents)
> > > References : http://lkml.org/lkml/2007/3/4/110
> > > Submitter  : Soeren Sonnenburg <kernel@nn7.de>
> > > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> > >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > > Status     : unknown
> > 
> > I can reproduce this on my dual core VAIO. There are some issues:
> 
> Yeah, I think I can too, on my dual-core Mac Mini. 
> 
> I'm not done with my bisection, but e9e2cdb4 is among the 28 commits left, 
> so I'm pretty sure I'm hitting the same bug. I'll do a few more bootups to 
> be 100% sure.

I just got the resume fix cleaned up. The suspend / resume thing was
dropped unintentionally during the -mm code reshuffling.

It still needs the broadcast fix though.

Does this make the problem go away ?

	tglx

diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index 12b3efe..5567745 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
@@ -284,6 +284,42 @@ void tick_shutdown_broadcast(unsigned int *cpup)
 	spin_unlock_irqrestore(&tick_broadcast_lock, flags);
 }
 
+void tick_suspend_broadcast(void)
+{
+	struct clock_event_device *bc;
+	unsigned long flags;
+
+	spin_lock_irqsave(&tick_broadcast_lock, flags);
+
+	bc = tick_broadcast_device.evtdev;
+	if (bc && tick_broadcast_device.mode == TICKDEV_MODE_PERIODIC)
+		clockevents_set_mode(bc, CLOCK_EVT_MODE_SHUTDOWN);
+
+	spin_unlock_irqrestore(&tick_broadcast_lock, flags);
+}
+
+int tick_resume_broadcast(void)
+{
+	struct clock_event_device *bc;
+	unsigned long flags;
+	int broadcast = 0;
+
+	spin_lock_irqsave(&tick_broadcast_lock, flags);
+
+	bc = tick_broadcast_device.evtdev;
+	if (bc) {
+		if (tick_broadcast_device.mode == TICKDEV_MODE_PERIODIC &&
+		    !cpus_empty(tick_broadcast_mask))
+			tick_broadcast_start_periodic(bc);
+
+		broadcast = cpu_isset(smp_processor_id(), tick_broadcast_mask);
+	}
+	spin_unlock_irqrestore(&tick_broadcast_lock, flags);
+
+	return broadcast;
+}
+
+
 #ifdef CONFIG_TICK_ONESHOT
 
 static cpumask_t tick_broadcast_oneshot_mask;
diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c
index 0986a2b..43ba1bd 100644
--- a/kernel/time/tick-common.c
+++ b/kernel/time/tick-common.c
@@ -298,6 +298,28 @@ static void tick_shutdown(unsigned int *cpup)
 	spin_unlock_irqrestore(&tick_device_lock, flags);
 }
 
+static void tick_suspend_periodic(void)
+{
+	struct tick_device *td = &__get_cpu_var(tick_cpu_device);
+	unsigned long flags;
+
+	spin_lock_irqsave(&tick_device_lock, flags);
+	if (td->mode == TICKDEV_MODE_PERIODIC)
+		clockevents_set_mode(td->evtdev, CLOCK_EVT_MODE_SHUTDOWN);
+	spin_unlock_irqrestore(&tick_device_lock, flags);
+}
+
+static void tick_resume_periodic(void)
+{
+	struct tick_device *td = &__get_cpu_var(tick_cpu_device);
+	unsigned long flags;
+
+	spin_lock_irqsave(&tick_device_lock, flags);
+	if (td->mode == TICKDEV_MODE_PERIODIC)
+		tick_setup_periodic(td->evtdev, 0);
+	spin_unlock_irqrestore(&tick_device_lock, flags);
+}
+
 /*
  * Notification about clock event devices
  */
@@ -325,6 +347,16 @@ static int tick_notify(struct notifier_block *nb, unsigned long reason,
 		tick_shutdown(dev);
 		break;
 
+	case CLOCK_EVT_NOTIFY_SUSPEND:
+		tick_suspend_periodic();
+		tick_suspend_broadcast();
+		break;
+
+	case CLOCK_EVT_NOTIFY_RESUME:
+		if (!tick_resume_broadcast())
+			tick_resume_periodic();
+		break;
+
 	default:
 		break;
 	}
diff --git a/kernel/time/tick-internal.h b/kernel/time/tick-internal.h
index 54861a0..75890ef 100644
--- a/kernel/time/tick-internal.h
+++ b/kernel/time/tick-internal.h
@@ -67,6 +67,8 @@ extern int tick_check_broadcast_device(struct clock_event_device *dev);
 extern int tick_is_broadcast_device(struct clock_event_device *dev);
 extern void tick_broadcast_on_off(unsigned long reason, int *oncpu);
 extern void tick_shutdown_broadcast(unsigned int *cpup);
+extern void tick_suspend_broadcast(void);
+extern int tick_resume_broadcast(void);
 
 extern void
 tick_set_periodic_handler(struct clock_event_device *dev, int broadcast);
@@ -90,6 +92,8 @@ static inline int tick_device_uses_broadcast(struct clock_event_device *dev,
 static inline void tick_do_periodic_broadcast(struct clock_event_device *d) { }
 static inline void tick_broadcast_on_off(unsigned long reason, int *oncpu) { }
 static inline void tick_shutdown_broadcast(unsigned int *cpup) { }
+static inline void tick_suspend_broadcast(void) { }
+static inline int tick_resume_broadcast(void) { return 0; }
 
 /*
  * Set the periodic handler in non broadcast mode
diff --git a/kernel/timer.c b/kernel/timer.c
index 6663a87..718437f 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -997,6 +997,9 @@ static int timekeeping_resume(struct sys_device *dev)
 	write_sequnlock_irqrestore(&xtime_lock, flags);
 
 	touch_softlockup_watchdog();
+
+	clockevents_notify(CLOCK_EVT_NOTIFY_RESUME, NULL);
+
 	/* Resume hrtimers */
 	clock_was_set();
 
@@ -1011,6 +1014,9 @@ static int timekeeping_suspend(struct sys_device *dev, pm_message_t state)
 	timekeeping_suspended = 1;
 	timekeeping_suspend_time = read_persistent_clock();
 	write_sequnlock_irqrestore(&xtime_lock, flags);
+
+	clockevents_notify(CLOCK_EVT_NOTIFY_SUSPEND, NULL);
+
 	return 0;
 }
 

Re: [5/6] 2.6.21-rc2: known regressions

[Soeren Sonnenburg]

On Tue, 2007-03-06 at 01:25 +0100, Thomas Gleixner wrote:
> On Mon, 2007-03-05 at 15:45 -0800, Linus Torvalds wrote:
> > 
> > On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> > > > 
> > > > Subject    : macbook pro suspend to ram broken  (clockevents)
> > > > References : http://lkml.org/lkml/2007/3/4/110
> > > > Submitter  : Soeren Sonnenburg <kernel@nn7.de>
> > > > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> > > >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > > > Status     : unknown
> > > 
> > > I can reproduce this on my dual core VAIO. There are some issues:
> > 
> > Yeah, I think I can too, on my dual-core Mac Mini. 
> > 
> > I'm not done with my bisection, but e9e2cdb4 is among the 28 commits left, 
> > so I'm pretty sure I'm hitting the same bug. I'll do a few more bootups to 
> > be 100% sure.
> 
> I just got the resume fix cleaned up. The suspend / resume thing was
> dropped unintentionally during the -mm code reshuffling.
> 
> It still needs the broadcast fix though.
> 
> Does this make the problem go away ?

yes. works in my isolated test-setup. I'm now going to test this in
git-HEAD with the full config.

Soeren
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.

Re: [5/6] 2.6.21-rc2: known regressions

[Soeren Sonnenburg]

On Tue, 2007-03-06 at 07:49 +0100, Soeren Sonnenburg wrote:
> On Tue, 2007-03-06 at 01:25 +0100, Thomas Gleixner wrote:
> > On Mon, 2007-03-05 at 15:45 -0800, Linus Torvalds wrote:
> > > 
> > > On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> > > > > 
> > > > > Subject    : macbook pro suspend to ram broken  (clockevents)
> > > > > References : http://lkml.org/lkml/2007/3/4/110
> > > > > Submitter  : Soeren Sonnenburg <kernel@nn7.de>
> > > > > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> > > > >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > > > > Status     : unknown
> > Does this make the problem go away ?
> 
> yes. works in my isolated test-setup. I'm now going to test this in
> git-HEAD with the full config.

*argh* when using the full config on HEAD something still causes a hang
on resume, but no time to trace it (the this probably new problem) down
atm :(

Soeren
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.

Re: [5/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Mon, 5 Mar 2007, Linus Torvalds wrote:
> On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> > > 
> > > Subject    : macbook pro suspend to ram broken  (clockevents)
> > > References : http://lkml.org/lkml/2007/3/4/110
> > > Submitter  : Soeren Sonnenburg <kernel@nn7.de>
> > > Caused-By  : Thomas Gleixner <tglx@linutronix.de>
> > >              commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> > > Status     : unknown
> > 
> > I can reproduce this on my dual core VAIO. There are some issues:
> 
> Yeah, I think I can too, on my dual-core Mac Mini. 
> 
> I'm not done with my bisection, but e9e2cdb4 is among the 28 commits left, 
> so I'm pretty sure I'm hitting the same bug. I'll do a few more bootups to 
> be 100% sure.

Ok, it's in the last six candidates, so yeah, I'm pretty sure. I'll do a 
final compile/boot cycle to verify, but if you don't hear from me, you can 
pretty much assume that was it.

Thomas, Ingo, I'd _really_ like to get -rc3 out there, but I'd like to cut 
down the regression list a bit, and a number of them were about resume 
from RAM, and this is probably it. So I'd *really* like to get this one 
nailed, especially since the causing commit is known. Can you look at it 
as a high-priority thing, please?

I don't see anything interesting in my logs.

	..
	Time: acpi_pm clocksource has been installed.
	Real Time Clock Driver v1.12ac
	hpet_acpi_add: no address or irqs in _CRS
	..

(I also see "Time: tsc clocksource has been installed." on some boots)

		Linus

Re: [5/6] 2.6.21-rc2: known regressions

[Thomas Gleixner]

On Mon, 2007-03-05 at 16:38 -0800, Linus Torvalds wrote:
> > I'm not done with my bisection, but e9e2cdb4 is among the 28 commits left, 
> > so I'm pretty sure I'm hitting the same bug. I'll do a few more bootups to 
> > be 100% sure.
> 
> Ok, it's in the last six candidates, so yeah, I'm pretty sure. I'll do a 
> final compile/boot cycle to verify, but if you don't hear from me, you can 
> pretty much assume that was it.
> 
> Thomas, Ingo, I'd _really_ like to get -rc3 out there, but I'd like to cut 
> down the regression list a bit, and a number of them were about resume 
> from RAM, and this is probably it. So I'd *really* like to get this one 
> nailed, especially since the causing commit is known. Can you look at it 
> as a high-priority thing, please?

Sure. I fought it all day. Can you please test the patch I sent a couple
of minutes ago ? Would be great to have your feedback tomorrow morning. 

We need to fix that ACPI problem (acpi_processor_start is not called
when CPU#1 is resumed) as well. I look into this tomorrow unless Len
beats me.

	tglx

Re: [5/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> 
> Sure. I fought it all day. Can you please test the patch I sent a couple
> of minutes ago ? Would be great to have your feedback tomorrow morning. 

Compiling right now - delayed because I just had to pick up one of the 
kids from gymnastics.

> We need to fix that ACPI problem (acpi_processor_start is not called
> when CPU#1 is resumed) as well. I look into this tomorrow unless Len
> beats me.

Ok, thanks.

		Linus

Re: [5/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

On Mon, 5 Mar 2007, Linus Torvalds wrote:
> 
> Compiling right now - delayed because I just had to pick up one of the 
> kids from gymnastics.

Ok, it does indeed solve the problem for me.

Mind sending a signed-off thing with explanations etc?

		Linus

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> > Compiling right now - delayed because I just had to pick up one of 
> > the kids from gymnastics.
> 
> Ok, it does indeed solve the problem for me.
> 
> Mind sending a signed-off thing with explanations etc?

here's Thomas' patch with explanations:

------------------------->
From: Thomas Gleixner <tglx@linutronix.de>

The programming of periodic tick devices needs to be saved/restored 
across suspend/resume - otherwise we might end up with a system coming 
up that relies on getting a PIT (or HPET) interrupt, while those devices 
default to 'no interrupts' after powerup. (To confuse things it worked 
to a certain degree on some systems because the lapic gets initialized 
as a side-effect of SMP bootup.)

This suspend / resume thing was dropped unintentionally during the 
last-minute -mm code reshuffling.

Signed-off-by: Ingo Molnar <mingo@elte.hu>

diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index 12b3efe..5567745 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
@@ -284,6 +284,42 @@ void tick_shutdown_broadcast(unsigned int *cpup)
 	spin_unlock_irqrestore(&tick_broadcast_lock, flags);
 }
 
+void tick_suspend_broadcast(void)
+{
+	struct clock_event_device *bc;
+	unsigned long flags;
+
+	spin_lock_irqsave(&tick_broadcast_lock, flags);
+
+	bc = tick_broadcast_device.evtdev;
+	if (bc && tick_broadcast_device.mode == TICKDEV_MODE_PERIODIC)
+		clockevents_set_mode(bc, CLOCK_EVT_MODE_SHUTDOWN);
+
+	spin_unlock_irqrestore(&tick_broadcast_lock, flags);
+}
+
+int tick_resume_broadcast(void)
+{
+	struct clock_event_device *bc;
+	unsigned long flags;
+	int broadcast = 0;
+
+	spin_lock_irqsave(&tick_broadcast_lock, flags);
+
+	bc = tick_broadcast_device.evtdev;
+	if (bc) {
+		if (tick_broadcast_device.mode == TICKDEV_MODE_PERIODIC &&
+		    !cpus_empty(tick_broadcast_mask))
+			tick_broadcast_start_periodic(bc);
+
+		broadcast = cpu_isset(smp_processor_id(), tick_broadcast_mask);
+	}
+	spin_unlock_irqrestore(&tick_broadcast_lock, flags);
+
+	return broadcast;
+}
+
+
 #ifdef CONFIG_TICK_ONESHOT
 
 static cpumask_t tick_broadcast_oneshot_mask;
diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c
index 0986a2b..43ba1bd 100644
--- a/kernel/time/tick-common.c
+++ b/kernel/time/tick-common.c
@@ -298,6 +298,28 @@ static void tick_shutdown(unsigned int *cpup)
 	spin_unlock_irqrestore(&tick_device_lock, flags);
 }
 
+static void tick_suspend_periodic(void)
+{
+	struct tick_device *td = &__get_cpu_var(tick_cpu_device);
+	unsigned long flags;
+
+	spin_lock_irqsave(&tick_device_lock, flags);
+	if (td->mode == TICKDEV_MODE_PERIODIC)
+		clockevents_set_mode(td->evtdev, CLOCK_EVT_MODE_SHUTDOWN);
+	spin_unlock_irqrestore(&tick_device_lock, flags);
+}
+
+static void tick_resume_periodic(void)
+{
+	struct tick_device *td = &__get_cpu_var(tick_cpu_device);
+	unsigned long flags;
+
+	spin_lock_irqsave(&tick_device_lock, flags);
+	if (td->mode == TICKDEV_MODE_PERIODIC)
+		tick_setup_periodic(td->evtdev, 0);
+	spin_unlock_irqrestore(&tick_device_lock, flags);
+}
+
 /*
  * Notification about clock event devices
  */
@@ -325,6 +347,16 @@ static int tick_notify(struct notifier_block *nb, unsigned long reason,
 		tick_shutdown(dev);
 		break;
 
+	case CLOCK_EVT_NOTIFY_SUSPEND:
+		tick_suspend_periodic();
+		tick_suspend_broadcast();
+		break;
+
+	case CLOCK_EVT_NOTIFY_RESUME:
+		if (!tick_resume_broadcast())
+			tick_resume_periodic();
+		break;
+
 	default:
 		break;
 	}
diff --git a/kernel/time/tick-internal.h b/kernel/time/tick-internal.h
index 54861a0..75890ef 100644
--- a/kernel/time/tick-internal.h
+++ b/kernel/time/tick-internal.h
@@ -67,6 +67,8 @@ extern int tick_check_broadcast_device(struct clock_event_device *dev);
 extern int tick_is_broadcast_device(struct clock_event_device *dev);
 extern void tick_broadcast_on_off(unsigned long reason, int *oncpu);
 extern void tick_shutdown_broadcast(unsigned int *cpup);
+extern void tick_suspend_broadcast(void);
+extern int tick_resume_broadcast(void);
 
 extern void
 tick_set_periodic_handler(struct clock_event_device *dev, int broadcast);
@@ -90,6 +92,8 @@ static inline int tick_device_uses_broadcast(struct clock_event_device *dev,
 static inline void tick_do_periodic_broadcast(struct clock_event_device *d) { }
 static inline void tick_broadcast_on_off(unsigned long reason, int *oncpu) { }
 static inline void tick_shutdown_broadcast(unsigned int *cpup) { }
+static inline void tick_suspend_broadcast(void) { }
+static inline int tick_resume_broadcast(void) { return 0; }
 
 /*
  * Set the periodic handler in non broadcast mode
diff --git a/kernel/timer.c b/kernel/timer.c
index 6663a87..718437f 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -997,6 +997,9 @@ static int timekeeping_resume(struct sys_device *dev)
 	write_sequnlock_irqrestore(&xtime_lock, flags);
 
 	touch_softlockup_watchdog();
+
+	clockevents_notify(CLOCK_EVT_NOTIFY_RESUME, NULL);
+
 	/* Resume hrtimers */
 	clock_was_set();
 
@@ -1011,6 +1014,9 @@ static int timekeeping_suspend(struct sys_device *dev, pm_message_t state)
 	timekeeping_suspended = 1;
 	timekeeping_suspend_time = read_persistent_clock();
 	write_sequnlock_irqrestore(&xtime_lock, flags);
+
+	clockevents_notify(CLOCK_EVT_NOTIFY_SUSPEND, NULL);
+
 	return 0;
 }
 

Re: [5/6] 2.6.21-rc2: known regressions

[Thomas Gleixner]

On Tue, 2007-03-06 at 08:25 +0100, Ingo Molnar wrote:
> The programming of periodic tick devices needs to be saved/restored 
> across suspend/resume - otherwise we might end up with a system coming 
> up that relies on getting a PIT (or HPET) interrupt, while those devices 
> default to 'no interrupts' after powerup. (To confuse things it worked 
> to a certain degree on some systems because the lapic gets initialized 
> as a side-effect of SMP bootup.)
> 
> This suspend / resume thing was dropped unintentionally during the 
> last-minute -mm code reshuffling.
> 
> Signed-off-by: Ingo Molnar <mingo@elte.hu>

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Re: [5/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Linus Torvalds <torvalds@linux-foundation.org>:
>
> Ok, it does indeed solve the problem for me.

Not yet for me unfortunately, although this seems to help.
Is this the patch I should have applied?
http://lkml.org/lkml/2007/3/5/445

With this applied, on resume I get *some* screen output soon after resume
(e.g. with s2ram I get several characters on VGA, X starts drawing some windows)
but then the crescent symbol starts blinking again and the system hangs.

Could this be the ACPI problem Thomas mentions (acpi_processor_start is not called
when CPU#1 is resumed)?

-- 
MST

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Michael S. Tsirkin <mst@mellanox.co.il> wrote:

> > Quoting Linus Torvalds <torvalds@linux-foundation.org>:
> >
> > Ok, it does indeed solve the problem for me.
> 
> Not yet for me unfortunately, although this seems to help.
> Is this the patch I should have applied?
> http://lkml.org/lkml/2007/3/5/445
> 
> With this applied, on resume I get *some* screen output soon after 
> resume (e.g. with s2ram I get several characters on VGA, X starts 
> drawing some windows) but then the crescent symbol starts blinking 
> again and the system hangs.

could you try this via s2ram on a text console, to see whether the 
kernel spits out any warning before it locks up?

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [5/6] 2.6.21-rc2: known regressions
> 
> 
> * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
> 
> > > Quoting Linus Torvalds <torvalds@linux-foundation.org>:
> > >
> > > Ok, it does indeed solve the problem for me.
> > 
> > Not yet for me unfortunately, although this seems to help.
> > Is this the patch I should have applied?
> > http://lkml.org/lkml/2007/3/5/445
> > 
> > With this applied, on resume I get *some* screen output soon after 
> > resume (e.g. with s2ram I get several characters on VGA, X starts 
> > drawing some windows) but then the crescent symbol starts blinking 
> > again and the system hangs.
> 
> could you try this via s2ram on a text console, to see whether the 
> kernel spits out any warning before it locks up?

Yes, that's what I did. Unfortunately only a couple of characters were
shown before it locked up.

I still need to check what does this do in the NO_HZ configuration.

BTW, Ingo, can you suspend/resume any number of times with this patch?

-- 
MST

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

[-- Attachment #1: Type: text/plain, Size: 3526 bytes --]


* Michael S. Tsirkin <mst@mellanox.co.il> wrote:

> > > Not yet for me unfortunately, although this seems to help.
> > > Is this the patch I should have applied?
> > > http://lkml.org/lkml/2007/3/5/445
> > > 
> > > With this applied, on resume I get *some* screen output soon after 
> > > resume (e.g. with s2ram I get several characters on VGA, X starts 
> > > drawing some windows) but then the crescent symbol starts blinking 
> > > again and the system hangs.
> > 
> > could you try this via s2ram on a text console, to see whether the 
> > kernel spits out any warning before it locks up?
> 
> Yes, that's what I did. Unfortunately only a couple of characters were 
> shown before it locked up.
> 
> I still need to check what does this do in the NO_HZ configuration.
> 
> BTW, Ingo, can you suspend/resume any number of times with this patch?

yeah, i can now suspend/resume an arbitrary number of times, vga, 
network, SATA all works fine after that. (i tried it 5 times)

i also have the patch below applied - but i dont think it should make a 
difference to your case. (maybe it does though) I've attached my config 
as well.

	Ingo

------>
From: Thomas Gleixner <tglx@linutronix.de>

The TIMER_SOFTIRQ runs the hrtimers during bootup until a usable 
clocksource and clock event sources are registered. The switch to high 
resolution mode happens inside of the TIMER_SOFTIRQ, but runs the 
softirq afterwards. That way the tick emulation timer, which was set up 
in the switch to highres might be executed in the softirq context, which 
is a BUG. The rbtree has not to be touched by the softirq after the 
highres switch.

This BUG was observed by Andres Salomon, who provided the information to
debug it.

Return early from the softirq, when the switch was sucessful. 

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

---
 kernel/hrtimer.c |   12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

Index: linux/kernel/hrtimer.c
===================================================================
--- linux.orig/kernel/hrtimer.c
+++ linux/kernel/hrtimer.c
@@ -540,19 +540,19 @@ static inline int hrtimer_enqueue_reprog
 /*
  * Switch to high resolution mode
  */
-static void hrtimer_switch_to_hres(void)
+static int hrtimer_switch_to_hres(void)
 {
 	struct hrtimer_cpu_base *base = &__get_cpu_var(hrtimer_bases);
 	unsigned long flags;
 
 	if (base->hres_active)
-		return;
+		return 1;
 
 	local_irq_save(flags);
 
 	if (tick_init_highres()) {
 		local_irq_restore(flags);
-		return;
+		return 0;
 	}
 	base->hres_active = 1;
 	base->clock_base[CLOCK_REALTIME].resolution = KTIME_HIGH_RES;
@@ -565,13 +565,14 @@ static void hrtimer_switch_to_hres(void)
 	local_irq_restore(flags);
 	printk(KERN_INFO "Switched to high resolution mode on CPU %d\n",
 	       smp_processor_id());
+	return 1;
 }
 
 #else
 
 static inline int hrtimer_hres_active(void) { return 0; }
 static inline int hrtimer_is_hres_enabled(void) { return 0; }
-static inline void hrtimer_switch_to_hres(void) { }
+static inline int hrtimer_switch_to_hres(void) { return 0; }
 static inline void hrtimer_force_reprogram(struct hrtimer_cpu_base *base) { }
 static inline int hrtimer_enqueue_reprogram(struct hrtimer *timer,
 					    struct hrtimer_clock_base *base)
@@ -1173,7 +1174,8 @@ void hrtimer_run_queues(void)
 	 * deadlock vs. xtime_lock.
 	 */
 	if (tick_check_oneshot_change(!hrtimer_is_hres_enabled()))
-		hrtimer_switch_to_hres();
+		if (hrtimer_switch_to_hres())
+			return;
 
 	hrtimer_get_softirq_time(cpu_base);
 

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 77228 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.21-rc2-syslet-v6
# Tue Mar  6 09:49:08 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_ASYNC_SUPPORT=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_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
# CONFIG_TASK_XACCT is not set
# CONFIG_UTS_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
# CONFIG_IKCONFIG is not set
CONFIG_CPUSETS=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_INITRAMFS_SOURCE=""
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=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Block layer
#
CONFIG_BLOCK=y
CONFIG_LBD=y
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_LSF=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_SMP=y
# CONFIG_X86_PC is not set
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
CONFIG_X86_GENERICARCH=y
# CONFIG_X86_ES7000 is not set
CONFIG_PARAVIRT=y
CONFIG_VMI=y
CONFIG_X86_CYCLONE_TIMER=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MCORE2 is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_NR_CPUS=32
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
CONFIG_TOSHIBA=m
CONFIG_I8K=m
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_EFI_VARS=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_POPULATES_NODE_MAP=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_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_EFI=y
# CONFIG_IRQBALANCE is not set
CONFIG_BOOT_IOREMAP=y
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
CONFIG_PM_DEBUG=y
CONFIG_DISABLE_CONSOLE_SUSPEND=y
CONFIG_PM_TRACE=y
CONFIG_PM_SYSFS_DEPRECATED=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=""
CONFIG_SUSPEND_SMP=y

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=m
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_IBM=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_BLACKLIST_YEAR=1999
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=m

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEBUG=y
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_POWERNOW_K6 is not set
CONFIG_X86_POWERNOW_K7=y
CONFIG_X86_POWERNOW_K7_ACPI=y
CONFIG_X86_POWERNOW_K8=y
CONFIG_X86_POWERNOW_K8_ACPI=y
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=y
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=y
CONFIG_X86_SPEEDSTEP_SMI=y
CONFIG_X86_P4_CLOCKMOD=m
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
CONFIG_X86_LONGRUN=y
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=y
# CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
CONFIG_PCIEAER=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_K8_NB=y

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=y

#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_COMPAQ=m
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
CONFIG_HOTPLUG_PCI_IBM=m
CONFIG_HOTPLUG_PCI_ACPI=m
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_DEFAULT_BIC=y
# CONFIG_DEFAULT_CUBIC is not set
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="bic"
CONFIG_TCP_MD5SIG=y

#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_TUNNEL=m
# CONFIG_IPV6_MULTIPLE_TABLES is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK_ENABLED=m
CONFIG_NF_CONNTRACK_SUPPORT=y
# CONFIG_IP_NF_CONNTRACK_SUPPORT is not set
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CONNTRACK_AMANDA=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 is not set
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_XTABLES=m
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_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=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_HELPER=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_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=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_HASHLIMIT=m

#
# IP: Netfilter Configuration
#
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_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=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_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
# CONFIG_IP6_NF_MATCH_MH is not set
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m

#
# DECnet: Netfilter Configuration
#
# CONFIG_DECNET_NF_GRABULATOR is not set

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m

#
# DCCP Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
# CONFIG_NET_DCCPPROBE is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y

#
# TIPC Configuration (EXPERIMENTAL)
#
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
CONFIG_DECNET_ROUTER=y
CONFIG_LLC=y
# CONFIG_LLC2 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
# CONFIG_LTPC is not set
# CONFIG_COPS is not set
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_FIFO=y
# CONFIG_NET_SCH_CLK_JIFFIES is not set
CONFIG_NET_SCH_CLK_GETTIMEOFDAY=y
# CONFIG_NET_SCH_CLK_CPU is not set

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_CLS_IND=y
CONFIG_NET_ESTIMATOR=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m

#
# Old SIR device drivers
#

#
# Old Serial dongle support
#

#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_TOSHIBA_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
CONFIG_BT=m
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_CMTP=m
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
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_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
CONFIG_IEEE80211_SOFTMAC_DEBUG=y
CONFIG_WIRELESS_EXT=y
CONFIG_FIB_RULES=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
# CONFIG_SSFDC is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m
# CONFIG_MTD_OBSOLETE_CHIPS is not set

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_ESB2ROM is not set
# CONFIG_MTD_CK804XROM is not set
CONFIG_MTD_SCB2_FLASH=m
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set

#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_ECC_SMC=y
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
# CONFIG_MTD_NAND_CAFE is not set
CONFIG_MTD_NAND_CS553X=m
CONFIG_MTD_NAND_NANDSIM=m

#
# OneNAND Flash Device Drivers
#
# CONFIG_MTD_ONENAND is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
CONFIG_PARIDE=m

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m

#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_BPCK6=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_SX8=m
CONFIG_BLK_DEV_UB=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_RAM_BLOCKSIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m

#
# Misc devices
#
CONFIG_IBM_ASM=m
# CONFIG_SGI_IOC4 is not set
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
# CONFIG_ASUS_LAPTOP is not set
CONFIG_MSI_LAPTOP=m
# CONFIG_SONY_LAPTOP is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECS=m
# CONFIG_BLK_DEV_DELKIN is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_BLK_DEV_IDEACPI is not set
CONFIG_IDE_TASK_IOCTL=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_ATIIXP=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
# CONFIG_BLK_DEV_CY82C693 is not set
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_CS5535=y
CONFIG_BLK_DEV_HPT34X=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_JMICRON=m
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT8213 is not set
CONFIG_BLK_DEV_IT821X=y
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_BLK_DEV_TC86C001 is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=y
CONFIG_SCSI_SAS_LIBSAS=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set

#
# SCSI low-level drivers
#
CONFIG_ISCSI_TCP=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
# CONFIG_SCSI_7000FASST is not set
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=4
CONFIG_AIC7XXX_RESET_DELAY_MS=1000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=y
CONFIG_AIC79XX_CMDS_PER_DEVICE=4
CONFIG_AIC79XX_RESET_DELAY_MS=1000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC94XX=y
# CONFIG_AIC94XX_DEBUG is not set
# CONFIG_SCSI_DPT_I2O is not set
CONFIG_SCSI_ADVANSYS=m
# CONFIG_SCSI_IN2000 is not set
CONFIG_SCSI_ARCMSR=m
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_NCR53C406A is not set
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
CONFIG_SCSI_SRP=m

#
# PCMCIA SCSI adapter support
#
CONFIG_PCMCIA_AHA152X=m
CONFIG_PCMCIA_FDOMAIN=m
CONFIG_PCMCIA_NINJA_SCSI=m
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m

#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_SATA_AHCI=y
CONFIG_SATA_SVW=y
CONFIG_ATA_PIIX=y
CONFIG_SATA_MV=y
CONFIG_SATA_NV=y
CONFIG_PDC_ADMA=y
CONFIG_SATA_QSTOR=y
CONFIG_SATA_PROMISE=y
CONFIG_SATA_SX4=y
CONFIG_SATA_SIL=y
CONFIG_SATA_SIL24=y
CONFIG_SATA_SIS=y
CONFIG_SATA_ULI=y
CONFIG_SATA_VIA=y
CONFIG_SATA_VITESSE=y
# CONFIG_SATA_INIC162X is not set
CONFIG_SATA_INTEL_COMBINED=y
CONFIG_SATA_ACPI=y
CONFIG_PATA_ALI=y
CONFIG_PATA_AMD=y
CONFIG_PATA_ARTOP=y
CONFIG_PATA_ATIIXP=y
CONFIG_PATA_CMD64X=y
CONFIG_PATA_CS5520=y
CONFIG_PATA_CS5530=y
CONFIG_PATA_CS5535=y
CONFIG_PATA_CYPRESS=y
CONFIG_PATA_EFAR=y
CONFIG_ATA_GENERIC=y
CONFIG_PATA_HPT366=y
CONFIG_PATA_HPT37X=y
CONFIG_PATA_HPT3X2N=y
CONFIG_PATA_HPT3X3=y
CONFIG_PATA_ISAPNP=y
CONFIG_PATA_IT821X=y
# CONFIG_PATA_IT8213 is not set
CONFIG_PATA_JMICRON=y
CONFIG_PATA_LEGACY=m
CONFIG_PATA_TRIFLEX=y
CONFIG_PATA_MARVELL=y
CONFIG_PATA_MPIIX=y
CONFIG_PATA_OLDPIIX=y
CONFIG_PATA_NETCELL=y
CONFIG_PATA_NS87410=y
CONFIG_PATA_OPTI=y
CONFIG_PATA_OPTIDMA=y
CONFIG_PATA_PCMCIA=y
CONFIG_PATA_PDC_OLD=y
CONFIG_PATA_QDI=y
CONFIG_PATA_RADISYS=y
CONFIG_PATA_RZ1000=y
CONFIG_PATA_SC1200=y
CONFIG_PATA_SERVERWORKS=y
CONFIG_PATA_PDC2027X=y
CONFIG_PATA_SIL680=y
CONFIG_PATA_SIS=y
CONFIG_PATA_VIA=y
CONFIG_PATA_WINBOND=y
CONFIG_PATA_WINBOND_VLB=y

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m

#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y

#
# Device Drivers
#
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m

#
# I2O device support
#
CONFIG_I2O=m
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m

#
# Macintosh device drivers
#
# CONFIG_MAC_EMUMOUSEBTN is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_NET_SB1000=m

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_FIXED_PHY=m
CONFIG_FIXED_MII_10_FDX=y
CONFIG_FIXED_MII_100_FDX=y

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
CONFIG_EL3=m
# CONFIG_3C515 is not set
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
# CONFIG_LANCE is not set
CONFIG_NET_VENDOR_SMC=y
# CONFIG_WD80x3 is not set
CONFIG_ULTRA=m
# CONFIG_SMC9194 is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
CONFIG_TULIP_MMIO=y
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_ISA=y
# CONFIG_E2100 is not set
CONFIG_EWRK3=m
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_LP486E is not set
# CONFIG_ETH16I is not set
CONFIG_NE2000=m
# CONFIG_ZNET is not set
# CONFIG_SEEQ8005 is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_PCNET32_NAPI=y
CONFIG_AMD8111_ETH=m
CONFIG_AMD8111E_NAPI=y
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_ADAPTEC_STARFIRE_NAPI=y
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
CONFIG_B44=m
CONFIG_FORCEDETH=y
CONFIG_FORCEDETH_NAPI=y
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=y
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_VIA_RHINE_NAPI=y
# CONFIG_SC92031 is not set
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m

#
# Ethernet (1000 Mbit)
#
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=y
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_NAPI=y
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=y
CONFIG_SKY2=m
# CONFIG_SK98LIN is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=y
CONFIG_BNX2=m
CONFIG_QLA3XXX=m
# CONFIG_ATL1 is not set

#
# Ethernet (10000 Mbit)
#
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T1_NAPI=y
# CONFIG_CHELSIO_T3 is not set
CONFIG_IXGB=m
CONFIG_IXGB_NAPI=y
CONFIG_S2IO=m
CONFIG_S2IO_NAPI=y
CONFIG_MYRI10GE=m
CONFIG_NETXEN_NIC=m

#
# Token Ring devices
#
CONFIG_TR=y
# CONFIG_IBMTR is not set
CONFIG_IBMOL=m
CONFIG_IBMLS=m
CONFIG_3C359=m
# CONFIG_TMS380TR is not set
# CONFIG_SMCTR is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
CONFIG_NET_WIRELESS_RTNETLINK=y

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
# CONFIG_ARLAN is not set
# CONFIG_WAVELAN is not set
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m

#
# Wireless 802.11 Frequency Hopping cards support
#
# CONFIG_PCMCIA_RAYCS is not set

#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m

#
# Wireless 802.11b Pcmcia/Cardbus cards support
#
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_PCMCIA_WL3501=m

#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
CONFIG_BCM43XX=m
CONFIG_BCM43XX_DEBUG=y
CONFIG_BCM43XX_DMA=y
CONFIG_BCM43XX_PIO=y
CONFIG_BCM43XX_DMA_AND_PIO_MODE=y
# CONFIG_BCM43XX_DMA_MODE is not set
# CONFIG_BCM43XX_PIO_MODE is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
CONFIG_NET_WIRELESS=y

#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
CONFIG_PCMCIA_IBMTR=m

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# ATM drivers
#
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
# CONFIG_ATM_ZATM is not set
CONFIG_ATM_NICSTAR=m
# CONFIG_ATM_NICSTAR_USE_SUNI is not set
# CONFIG_ATM_NICSTAR_USE_IDT77105 is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=m
# CONFIG_ATM_AMBASSADOR_DEBUG is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
# CONFIG_ATM_IA is not set
CONFIG_ATM_FORE200E_MAYBE=m
# CONFIG_ATM_FORE200E_PCA is not set
CONFIG_ATM_HE=m
# CONFIG_ATM_HE_USE_SUNI is not set
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
CONFIG_SKFP=m
# CONFIG_HIPPI is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
# CONFIG_PPP_BSDCOMP is not set
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_NET_FC=y
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
CONFIG_ISDN=m

#
# Old ISDN4Linux
#
CONFIG_ISDN_I4L=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_IPPP_FILTER=y
# CONFIG_ISDN_PPP_BSDCOMP is not set
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y

#
# ISDN feature submodules
#
CONFIG_ISDN_DIVERSION=m

#
# ISDN4Linux hardware drivers
#

#
# Passive cards
#
CONFIG_ISDN_DRV_HISAX=m

#
# D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
CONFIG_HISAX_NO_SENDCOMPLETE=y
CONFIG_HISAX_NO_LLC=y
CONFIG_HISAX_NO_KEYPAD=y
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8

#
# HiSax supported cards
#
# CONFIG_HISAX_16_0 is not set
CONFIG_HISAX_16_3=y
CONFIG_HISAX_TELESPCI=y
CONFIG_HISAX_S0BOX=y
# CONFIG_HISAX_AVM_A1 is not set
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
# CONFIG_HISAX_IX1MICROR2 is not set
CONFIG_HISAX_DIEHLDIVA=y
# CONFIG_HISAX_ASUSCOM is not set
# CONFIG_HISAX_TELEINT is not set
# CONFIG_HISAX_HFCS is not set
CONFIG_HISAX_SEDLBAUER=y
# CONFIG_HISAX_SPORTSTER is not set
# CONFIG_HISAX_MIC is not set
CONFIG_HISAX_NETJET=y
CONFIG_HISAX_NETJET_U=y
CONFIG_HISAX_NICCY=y
# CONFIG_HISAX_ISURF is not set
# CONFIG_HISAX_HSTSAPHIR is not set
CONFIG_HISAX_BKM_A4T=y
CONFIG_HISAX_SCT_QUADRO=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_PCI=y
CONFIG_HISAX_W6692=y
CONFIG_HISAX_HFC_SX=y
CONFIG_HISAX_ENTERNOW_PCI=y
# CONFIG_HISAX_DEBUG is not set

#
# HiSax PCMCIA card service modules
#
CONFIG_HISAX_SEDLBAUER_CS=m
CONFIG_HISAX_ELSA_CS=m
CONFIG_HISAX_AVM_A1_CS=m
CONFIG_HISAX_TELES_CS=m

#
# HiSax sub driver modules
#
CONFIG_HISAX_ST5481=m
# CONFIG_HISAX_HFCUSB is not set
CONFIG_HISAX_HFC4S8S=m
CONFIG_HISAX_FRITZ_PCIPNP=m
CONFIG_HISAX_HDLC=y

#
# Active cards
#
# CONFIG_ISDN_DRV_ICN is not set
# CONFIG_ISDN_DRV_PCBIT is not set
# CONFIG_ISDN_DRV_SC is not set
# CONFIG_ISDN_DRV_ACT2000 is not set

#
# Siemens Gigaset
#
CONFIG_ISDN_DRV_GIGASET=m
CONFIG_GIGASET_BASE=m
CONFIG_GIGASET_M105=m
# CONFIG_GIGASET_M101 is not set
# CONFIG_GIGASET_DEBUG is not set
# CONFIG_GIGASET_UNDOCREQ is not set

#
# CAPI subsystem
#
CONFIG_ISDN_CAPI=m
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
CONFIG_CAPI_TRACE=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m
CONFIG_ISDN_CAPI_CAPIDRV=m

#
# CAPI hardware drivers
#

#
# Active AVM cards
#
CONFIG_CAPI_AVM=y
# CONFIG_ISDN_DRV_AVMB1_B1ISA is not set
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
# CONFIG_ISDN_DRV_AVMB1_T1ISA is not set
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_AVM_CS=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m

#
# Active Eicon DIVA Server cards
#
CONFIG_CAPI_EICON=y
CONFIG_ISDN_DIVAS=m
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_ISDN_DIVAS_DIVACAPI=m
CONFIG_ISDN_DIVAS_USERIDI=m
CONFIG_ISDN_DIVAS_MAINT=m

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_KEYBOARD_STOWAWAY=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
CONFIG_TOUCHSCREEN_UCB1400=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_WISTRON_BTNS=m
# CONFIG_INPUT_ATLAS_BTNS is not set
CONFIG_INPUT_UINPUT=m

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
CONFIG_MOXA_SMARTIO_NEW=m
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
# CONFIG_SERIAL_8250_FOURPORT is not set
# CONFIG_SERIAL_8250_ACCENT is not set
# CONFIG_SERIAL_8250_BOCA is not set
CONFIG_SERIAL_8250_EXAR_ST16C554=m
# CONFIG_SERIAL_8250_HUB6 is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
CONFIG_TIPAR=m

#
# IPMI
#
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
CONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not set
CONFIG_I6300ESB_WDT=m
CONFIG_I8XX_TCO=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
# CONFIG_SC1200_WDT is not set
CONFIG_PC87413_WDT=m
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not set

#
# ISA-based Watchdog Cards
#
# CONFIG_PCWATCHDOG is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_WDT is not set

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_NVRAM=y
CONFIG_RTC=y
CONFIG_DTLK=m
CONFIG_R3964=m
# CONFIG_APPLICOM is not set
CONFIG_SONYPI=m
CONFIG_AGP=y
CONFIG_AGP_ALI=y
CONFIG_AGP_ATI=y
CONFIG_AGP_AMD=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_NVIDIA=y
CONFIG_AGP_SIS=y
CONFIG_AGP_SWORKS=y
CONFIG_AGP_VIA=y
CONFIG_AGP_EFFICEON=y
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_MWAVE=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
# CONFIG_HPET_MMAP is not set
CONFIG_HANGCHECK_TIMER=m

#
# TPM devices
#
CONFIG_TCG_TPM=m
CONFIG_TCG_TIS=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
# CONFIG_TELCLOCK is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
# CONFIG_I2C_PASEMI is not set
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
# CONFIG_SCx200_ACB is not set
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_STUB=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
CONFIG_I2C_PCA_ISA=m

#
# Miscellaneous I2C Chip support
#
CONFIG_SENSORS_DS1337=m
CONFIG_SENSORS_DS1374=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#
CONFIG_W1=m
CONFIG_W1_CON=y

#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=m
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2433=m
CONFIG_W1_SLAVE_DS2433_CRC=y

#
# Hardware Monitoring support
#
CONFIG_HWMON=m
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
# CONFIG_SENSORS_ADM1029 is not set
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_FSCPOS=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y

#
# Video Capture Adapters
#

#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA7111=m
CONFIG_VIDEO_SAA7114=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m
# CONFIG_VIDEO_VIVI is not set
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_SAA6588=m
# CONFIG_VIDEO_PMS is not set
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m
CONFIG_VIDEO_CPIA2=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_TUNER_3036=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN_ZR36060=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_MEYE=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_DPC=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CAFE_CCIC=m

#
# V4L USB devices
#
CONFIG_VIDEO_PVRUSB2=m
# CONFIG_VIDEO_PVRUSB2_29XXX is not set
CONFIG_VIDEO_PVRUSB2_24XXX=y
CONFIG_VIDEO_PVRUSB2_SYSFS=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_USBVISION=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_QUICKCAM_MESSENGER=m
CONFIG_USB_ET61X251=m
CONFIG_VIDEO_OVCAMCHIP=m
CONFIG_USB_W9968CF=m
CONFIG_USB_OV511=m
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
CONFIG_USB_ZC0301=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set

#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set
CONFIG_USB_DSBR=m

#
# Digital Video Broadcasting Devices
#
CONFIG_DVB=y
CONFIG_DVB_CORE=m
# CONFIG_DVB_CORE_ATTACH is not set

#
# Supported SAA7146 based PCI Adapters
#
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m

#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
# CONFIG_DVB_USB_M920X is not set
# CONFIG_DVB_USB_GL861 is not set
# CONFIG_DVB_USB_AU6610 is not set
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_DVB_CINERGYT2=m
CONFIG_DVB_CINERGYT2_TUNING=y
CONFIG_DVB_CINERGYT2_STREAM_URB_COUNT=32
CONFIG_DVB_CINERGYT2_STREAM_BUF_SIZE=512
CONFIG_DVB_CINERGYT2_QUERY_INTERVAL=250
CONFIG_DVB_CINERGYT2_ENABLE_RC_INPUT_DEVICE=y
CONFIG_DVB_CINERGYT2_RC_QUERY_INTERVAL=100

#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set

#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m

#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m

#
# Supported DVB Frontends
#

#
# Customise DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set

#
# DVB-S (satellite) frontends
#
CONFIG_DVB_STV0299=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_MT312=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_TDA10086=m

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m

#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_STV0297=m

#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m

#
# Tuners/PLL support
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TDA826X=m
# CONFIG_DVB_TUNER_QT1010 is not set
CONFIG_DVB_TUNER_MT2060=m
CONFIG_DVB_TUNER_LGH06XF=m

#
# Miscellaneous devices
#
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_TUA6100=m
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_BUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_USB_DABUSB=m

#
# Graphics support
#
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_BACKLIGHT_PROGEAR is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frambuffer hardware drivers
#
CONFIG_FB_CIRRUS=m
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
# CONFIG_FB_IMAC is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_NVIDIA_BACKLIGHT=y
CONFIG_FB_RIVA=m
# CONFIG_FB_RIVA_I2C is not set
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_RIVA_BACKLIGHT=y
CONFIG_FB_I810=m
CONFIG_FB_I810_GTF=y
CONFIG_FB_I810_I2C=y
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
# CONFIG_FB_S3 is not set
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
# CONFIG_FB_SIS is not set
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
CONFIG_FB_3DFX_ACCEL=y
CONFIG_FB_VOODOO1=m
CONFIG_FB_CYBLA=m
CONFIG_FB_TRIDENT=m
CONFIG_FB_TRIDENT_ACCEL=y
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_OPL4_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MTS64=m
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m
# CONFIG_SND_PORTMAN2X4 is not set

#
# ISA devices
#
CONFIG_SND_CS4231_LIB=m
CONFIG_SND_ADLIB=m
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
CONFIG_SND_CS4236=m
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
CONFIG_SND_ES18XX=m
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
CONFIG_SND_OPL3SA2=m
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
CONFIG_SND_MIRO=m
# CONFIG_SND_SB8 is not set
CONFIG_SND_SB16=m
CONFIG_SND_SBAWE=m
# CONFIG_SND_SB16_CSP is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set

#
# PCI devices
#
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_CS5535AUDIO=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_FM801_TEA575X_BOOL=y
CONFIG_SND_FM801_TEA575X=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_AC97_POWER_SAVE=y

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set

#
# SoC audio support
#
# CONFIG_SND_SOC is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m

#
# HID Devices
#
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_EHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
CONFIG_USB_STORAGE_KARMA=y
CONFIG_USB_LIBUSUAL=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
# CONFIG_PANTHERLORD_FF is not set
CONFIG_THRUSTMASTER_FF=y
CONFIG_ZEROPLUS_FF=y
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
CONFIG_USB_ACECAD=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_TOUCHSCREEN=m
CONFIG_USB_TOUCHSCREEN_EGALAX=y
CONFIG_USB_TOUCHSCREEN_PANJIT=y
CONFIG_USB_TOUCHSCREEN_3M=y
CONFIG_USB_TOUCHSCREEN_ITM=y
CONFIG_USB_TOUCHSCREEN_ETURBO=y
CONFIG_USB_TOUCHSCREEN_GUNZE=y
CONFIG_USB_TOUCHSCREEN_DMC_TSC10=y
# CONFIG_USB_YEALINK is not set
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m
CONFIG_USB_ATI_REMOTE2=m
CONFIG_USB_KEYSPAN_REMOTE=m
CONFIG_USB_APPLETOUCH=m
# CONFIG_USB_GTCO is not set

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET_MII=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
# CONFIG_USB_NET_DM9601 is not set
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
# CONFIG_USB_KC2190 is not set
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_MON=y

#
# USB port drivers
#
CONFIG_USB_USS720=m

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_DEBUG=m
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
# CONFIG_USB_BERRY_CHARGE is not set
CONFIG_USB_LED=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
CONFIG_USB_PHIDGET=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETMOTORCONTROL=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
# CONFIG_USB_IOWARRIOR is not set
CONFIG_USB_TEST=m

#
# USB DSL modem support
#
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_BLOCK=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m

#
# LED devices
#
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=m

#
# InfiniBand support
#
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_MTHCA=m
CONFIG_INFINIBAND_MTHCA_DEBUG=y
# CONFIG_INFINIBAND_AMSO1100 is not set
CONFIG_INFINIBAND_IPOIB=m
# CONFIG_INFINIBAND_IPOIB_CM is not set
CONFIG_INFINIBAND_IPOIB_DEBUG=y
CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y
CONFIG_INFINIBAND_SRP=m
CONFIG_INFINIBAND_ISER=m

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD76X=m
CONFIG_EDAC_E7XXX=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82875P=m
CONFIG_EDAC_I82860=m
CONFIG_EDAC_R82600=m
CONFIG_EDAC_POLL=y

#
# Real Time Clock
#
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set

#
# RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_RS5C372=m
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_TEST is not set
CONFIG_RTC_DRV_V3020=m

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m

#
# Auxiliary Display support
#
# CONFIG_KS0108 is not set

#
# Virtualization
#
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
CONFIG_KVM_AMD=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_NOLOCK=m
CONFIG_GFS2_FS_LOCKING_DLM=m
CONFIG_OCFS2_FS=m
# CONFIG_OCFS2_DEBUG_MASKLOG is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
CONFIG_JFFS2_SUMMARY=y
# CONFIG_JFFS2_FS_XATTR is not set
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=m
CONFIG_VXFS_FS=m
# CONFIG_HPFS_FS is not set
CONFIG_QNX4FS_FS=m
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_AFS_FS is not set
CONFIG_9P_FS=m

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Distributed Lock Manager
#
CONFIG_DLM=m
CONFIG_DLM_TCP=y
# CONFIG_DLM_SCTP is not set
CONFIG_DLM_DEBUG=y

#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_KPROBES=y

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_LOG_BUF_SHIFT=20
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
CONFIG_RT_MUTEX_TESTER=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_VM=y
CONFIG_DEBUG_LIST=y
CONFIG_FRAME_POINTER=y
# CONFIG_FORCED_INLINING is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_LKDTM is not set
CONFIG_FAULT_INJECTION=y
CONFIG_FAILSLAB=y
CONFIG_FAIL_PAGE_ALLOC=y
CONFIG_FAIL_MAKE_REQUEST=y
CONFIG_FAULT_INJECTION_DEBUG_FS=y
# CONFIG_FAULT_INJECTION_STACKTRACE_FILTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Page alloc debug is incompatible with Software Suspend on i386
#
CONFIG_DEBUG_RODATA=y
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
# CONFIG_DEBUG_PARAVIRT is not set

#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_CAPABILITIES=m
# CONFIG_SECURITY_ROOTPLUG is not set
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT is not set
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_WP512=y
CONFIG_CRYPTO_TGR192=y
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_LRW=y
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
# CONFIG_CRYPTO_TWOFISH_586 is not set
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_586 is not set
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_TEA=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_KHAZAD=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_MICHAEL_MIC=y
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_GEODE=m

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=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_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y

Re: [5/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [5/6] 2.6.21-rc2: known regressions
> 
> 
> * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
> 
> > > > Not yet for me unfortunately, although this seems to help.
> > > > Is this the patch I should have applied?
> > > > http://lkml.org/lkml/2007/3/5/445
> > > > 
> > > > With this applied, on resume I get *some* screen output soon after 
> > > > resume (e.g. with s2ram I get several characters on VGA, X starts 
> > > > drawing some windows) but then the crescent symbol starts blinking 
> > > > again and the system hangs.
> > > 
> > > could you try this via s2ram on a text console, to see whether the 
> > > kernel spits out any warning before it locks up?
> > 
> > Yes, that's what I did. Unfortunately only a couple of characters were 
> > shown before it locked up.
> > 
> > I still need to check what does this do in the NO_HZ configuration.
> > 
> > BTW, Ingo, can you suspend/resume any number of times with this patch?
> 
> yeah, i can now suspend/resume an arbitrary number of times, vga, 
> network, SATA all works fine after that. (i tried it 5 times)
> 
> i also have the patch below applied - but i dont think it should make a 
> difference to your case. (maybe it does though)

Nope, system hangs on resume with or without this patch applied.

> I've attached my config as well.

Haven't tried that yet.

-- 
MST

Re: [5/6] 2.6.21-rc2: known regressions

[Linus Torvalds]

This is just a coding style thing, but I thought I should really point it 
out, because these kinds of things quite often result in nasty bugs simply 
because the source code is so hard to read properly:

On Tue, 6 Mar 2007, Ingo Molnar wrote:
>
> -static void hrtimer_switch_to_hres(void)
> +static int hrtimer_switch_to_hres(void)

Ok, so here's the quiz: does this function return "true on success, false 
on failure", or does it return "zero on success, negative on failure"?

>  	if (base->hres_active)
> -		return;
> +		return 1;

Ahh, it must be "true on success", right?

>  	local_irq_save(flags);
>  
>  	if (tick_init_highres()) {
>  		local_irq_restore(flags);
> -		return;
> +		return 0;

Ohh-oh! This is clearly a failure schenario! And indeed, 
"tick_init_highres()" will do the "negative on failure, zero on success" 
thing.

BUT! That means that you're testing the return value WRONG!

A function that returns a negative error value should be tested with

	if (tick_init_highres() < 0) {
		local_irq_restore(flags);
		return 0;
	}

because now you *see* that it's a failure.

So here's the coding style:

 - "true on success, false on failure" should be tested by just doing the 
   implicit test against zero (because that's how C booleans work!)

   Example:

	if (everything_is_done())
		return;

   Or:

	if (!something_worked_ok()) {
		printk("Aiee! Bug!\n");
		return;
	}

 - "negative error values" should preferably always be tested as such

	if (tick_init_highres() < 0) {
		printk("Aieee! Couldn't init!\n");
		return 0;
	}

   or, much better, actually use a temporary variable called "err" or 
   "error" or something, at which point "!error" is suddenly readable 
   again:

	err = tick_init_highres();
	if (!err)
		return;

I know this sounds stupid, but we've long since come to the point where 
source code readability on a *local* scale is damn important, simply 
because that's how people look at code: they may not always remember 
whether "zero is success" or "zero is false".

In general, I would suggest:

 - ALWAYS use "negative means error". If you had done that in this case, 
   then hrtimer_switch_to_hres() would have been a lot more readable, 
   *and* it could actually have returned the error code that it got to the 
   caller. In general, it's just more information when you see

	error = some_function();
	if (error)
		return error;

   because even if it may generate basically *exactly* same code as the 
   reversed "positive" version:

	if (!some_version_is_true())
		return 0;

   it simply has more semantic information for *humans*.

   And when you do this, *test it as such*. Either use an explicit "< 0" 
   so that you *see* that you're testing an error value, or use that 
   "retval/error = xyzzy()" pattern that is already showing "it's more 
   than just true/false"

 - use "true/false" only for things where it's *really* obvious that the 
   answer is never an error, and always a "was it true"?

Yeah, even so, the true/false kind of thing may be more common (especially 
with small helper functions that are literally *designed* to be used just 
as a conditional), but I think in this case, you really should have done 
it as a "returns error" function. Partly because now it was throwing away 
an error code, partly simply because in this case, it really wasn't about 
true/false as much as about "did something error out and keep it from 
succeeding?".

Maybe I'm just getting anal in my old age. I at one time tried to make 
sparse check for these things, but there was no really sane thing I could 
come up with (way way WAAY too much manual annotation).

I might have to break down and suggest people use

	bool somefunction(..)
	{
		if (... < 0)
			return false;
		...
		return true;
	}

just to (a) eventually have sparse check for these things but more 
importantly (b) have people see more at a glance whether a function is 
supposed to return "negative or success" or "true or false".

I've not generally been a huge fan of "boolean", especially in the 
traditional C kind of sense (capital screaming letters, and really just an 
"int" with lipstick). But with modern C, and "bool" defined as really 
holding just 0/1 (in practice - "unsigned char"), we could actually check 
these things (and verify with sparse that you never assign any integer 
except for 0/1 to a boolean, and otherwise always have to use a real 
boolean construct).

Thus endeth my overly long coding style rant.

		Linus

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> This is just a coding style thing, but I thought I should really point 
> it out, because these kinds of things quite often result in nasty bugs 
> simply because the source code is so hard to read properly:

yeah, agreed. We'll fix this.

	Ingo

[PATCH] highres: do not run the TIMER_SOFTIRQ after switching to highres mode

[Thomas Gleixner]

On Tue, 2007-03-06 at 08:44 -0800, Linus Torvalds wrote:
> This is just a coding style thing, but I thought I should really point it 
> out, because these kinds of things quite often result in nasty bugs simply 
> because the source code is so hard to read properly:

/me pleads guilty !

Replacement patch below.

	tglx

--------------------->

The TIMER_SOFTIRQ runs the hrtimers during bootup until a usable
clocksource and clock event sources are registered. The switch to high
resolution mode happens inside of the TIMER_SOFTIRQ, but runs the
softirq afterwards. That way the tick emulation timer, which was set up
in the switch to highres might be executed in the softirq context, which
is a BUG. The rbtree has not to be touched by the softirq after the
highres switch.

This BUG was observed by Andres Salomon, who provided the information to
debug it.

Return early from the softirq, when the switch was sucessful.

Remove also the superfluid hres_active check on top of
hrtimer_switch_to_hres(), as we never get there, once we switched over.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Cc: Andres Salomon <dilinger@debian.org>

diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index de93a81..2e465df 100644
--- a/kernel/hrtimer.c
+++ b/kernel/hrtimer.c
@@ -540,19 +540,18 @@ static inline int hrtimer_enqueue_reprogram(struct hrtimer *timer,
 /*
  * Switch to high resolution mode
  */
-static void hrtimer_switch_to_hres(void)
+static int hrtimer_switch_to_hres(void)
 {
 	struct hrtimer_cpu_base *base = &__get_cpu_var(hrtimer_bases);
 	unsigned long flags;
-
-	if (base->hres_active)
-		return;
+	int err;
 
 	local_irq_save(flags);
 
-	if (tick_init_highres()) {
+	err = tick_init_highres();
+	if (err < 0) {
 		local_irq_restore(flags);
-		return;
+		return err;
 	}
 	base->hres_active = 1;
 	base->clock_base[CLOCK_REALTIME].resolution = KTIME_HIGH_RES;
@@ -565,13 +564,14 @@ static void hrtimer_switch_to_hres(void)
 	local_irq_restore(flags);
 	printk(KERN_INFO "Switched to high resolution mode on CPU %d\n",
 	       smp_processor_id());
+	return 0;
 }
 
 #else
 
 static inline int hrtimer_hres_active(void) { return 0; }
 static inline int hrtimer_is_hres_enabled(void) { return 0; }
-static inline void hrtimer_switch_to_hres(void) { }
+static inline int hrtimer_switch_to_hres(void) { return -EINVAL; }
 static inline void hrtimer_force_reprogram(struct hrtimer_cpu_base *base) { }
 static inline int hrtimer_enqueue_reprogram(struct hrtimer *timer,
 					    struct hrtimer_clock_base *base)
@@ -1173,7 +1173,8 @@ void hrtimer_run_queues(void)
 	 * deadlock vs. xtime_lock.
 	 */
 	if (tick_check_oneshot_change(!hrtimer_is_hres_enabled()))
-		hrtimer_switch_to_hres();
+		if (!hrtimer_switch_to_hres())
+			return;
 
 	hrtimer_get_softirq_time(cpu_base);
 

Re: [PATCH] highres: do not run the TIMER_SOFTIRQ after switching to highres mode

[Linus Torvalds]

On Tue, 6 Mar 2007, Thomas Gleixner wrote:
> 
> /me pleads guilty !
> 
> Replacement patch below.

Well, I already applied the original one that came through Andrew, so I 
really just wanted to note the coding style in general, and your fixed 
patch no longer applied ;)

Also, you do end up testing for "not error" with a

>  	if (tick_check_oneshot_change(!hrtimer_is_hres_enabled()))
> -		hrtimer_switch_to_hres();
> +		if (!hrtimer_switch_to_hres())
> +			return;

which I guess is ok, if only because we simply don't care about what the 
exact error was. But it means that this particular code sequence ends up 
having the same problem (which is still fewer places than the original 
patch, so we're good).

I personally hate the

	if (hrtimer_switch_to_hres() == SUCCESS)
		return;

kind of syntax (it's just too long, and it's *not* obvious at all that 
SUCCESS is zero and that this is a "negative error or zero" kind of 
function, so it's actually *worse* than just doing what you did, but some 
projects seem to have that kind of approach.

We could encourage people to do

	if (hrtimer_switch_to_hres() >= 0)
		return;

which is fairly obviously a "success" case for a negative error value, but 
I'm not sure the extra typing really is worth it. Does anybody have any 
smart ideas that people might even be ok with following (just making 
things more cumbersome is anti-productive, so I don't want to have some 
stupid rule that everybody really hates)?

			Linus

Re: [5/6] 2.6.21-rc2: known regressions

[Randy Dunlap]

On Tue, 6 Mar 2007 08:44:43 -0800 (PST) Linus Torvalds wrote:

> 
> This is just a coding style thing, but I thought I should really point it 
> out, because these kinds of things quite often result in nasty bugs simply 
> because the source code is so hard to read properly:
> 
> On Tue, 6 Mar 2007, Ingo Molnar wrote:
> >
> > -static void hrtimer_switch_to_hres(void)
> > +static int hrtimer_switch_to_hres(void)
> 
> Ok, so here's the quiz: does this function return "true on success, false 
> on failure", or does it return "zero on success, negative on failure"?
> 
> >  	if (base->hres_active)
> > -		return;
> > +		return 1;
> 
> Ahh, it must be "true on success", right?
> 
> >  	local_irq_save(flags);
> >  
> >  	if (tick_init_highres()) {
> >  		local_irq_restore(flags);
> > -		return;
> > +		return 0;
> 
> Ohh-oh! This is clearly a failure schenario! And indeed, 
> "tick_init_highres()" will do the "negative on failure, zero on success" 
> thing.
> 
> BUT! That means that you're testing the return value WRONG!
> 
> A function that returns a negative error value should be tested with
> 
> 	if (tick_init_highres() < 0) {
> 		local_irq_restore(flags);
> 		return 0;
> 	}
> 
> because now you *see* that it's a failure.
> 
> So here's the coding style:
> 
>  - "true on success, false on failure" should be tested by just doing the 
>    implicit test against zero (because that's how C booleans work!)
> 
>    Example:
> 
> 	if (everything_is_done())
> 		return;
> 
>    Or:
> 
> 	if (!something_worked_ok()) {
> 		printk("Aiee! Bug!\n");
> 		return;
> 	}
> 
>  - "negative error values" should preferably always be tested as such
> 
> 	if (tick_init_highres() < 0) {
> 		printk("Aieee! Couldn't init!\n");
> 		return 0;
> 	}
> 
>    or, much better, actually use a temporary variable called "err" or 
>    "error" or something, at which point "!error" is suddenly readable 
>    again:
> 
[1b]
> 	err = tick_init_highres();
> 	if (!err)
> 		return;

So this one above and [2] below lose the obvious "negative error"
information, and also prevent such functions from returning a
positive value (> 0), e.g., to indicate a successful amount of
work done (like bytes read or written).  The second version above
[1b] also does not quite agree with your statement:
  - "negative error values" should preferably always be tested as such

so in the interest of CodingStyle, can you be even clearer?


> I know this sounds stupid, but we've long since come to the point where 
> source code readability on a *local* scale is damn important, simply 
> because that's how people look at code: they may not always remember 
> whether "zero is success" or "zero is false".
> 
> In general, I would suggest:
> 
>  - ALWAYS use "negative means error". If you had done that in this case, 
>    then hrtimer_switch_to_hres() would have been a lot more readable, 
>    *and* it could actually have returned the error code that it got to the 
>    caller. In general, it's just more information when you see
> 
[2]
> 	error = some_function();
> 	if (error)
> 		return error;
> 
>    because even if it may generate basically *exactly* same code as the 
>    reversed "positive" version:
> 
> 	if (!some_version_is_true())
> 		return 0;
> 
>    it simply has more semantic information for *humans*.
> 
>    And when you do this, *test it as such*. Either use an explicit "< 0" 
>    so that you *see* that you're testing an error value, or use that 
>    "retval/error = xyzzy()" pattern that is already showing "it's more 
>    than just true/false"
> 
>  - use "true/false" only for things where it's *really* obvious that the 
>    answer is never an error, and always a "was it true"?
> 
> Yeah, even so, the true/false kind of thing may be more common (especially 
> with small helper functions that are literally *designed* to be used just 
> as a conditional), but I think in this case, you really should have done 
> it as a "returns error" function. Partly because now it was throwing away 
> an error code, partly simply because in this case, it really wasn't about 
> true/false as much as about "did something error out and keep it from 
> succeeding?".
> 
> Maybe I'm just getting anal in my old age. I at one time tried to make 
> sparse check for these things, but there was no really sane thing I could 
> come up with (way way WAAY too much manual annotation).
> 
> I might have to break down and suggest people use
> 
> 	bool somefunction(..)
> 	{
> 		if (... < 0)
> 			return false;
> 		...
> 		return true;
> 	}
> 
> just to (a) eventually have sparse check for these things but more 
> importantly (b) have people see more at a glance whether a function is 
> supposed to return "negative or success" or "true or false".
> 
> I've not generally been a huge fan of "boolean", especially in the 
> traditional C kind of sense (capital screaming letters, and really just an 
> "int" with lipstick). But with modern C, and "bool" defined as really 
> holding just 0/1 (in practice - "unsigned char"), we could actually check 
> these things (and verify with sparse that you never assign any integer 
> except for 0/1 to a boolean, and otherwise always have to use a real 
> boolean construct).
> 
> Thus endeth my overly long coding style rant.
> 
> 		Linus


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: [5/6] 2.6.21-rc2: known regressions

[Soeren Sonnenburg]

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

On Tue, 2007-03-06 at 12:46 +0200, Michael S. Tsirkin wrote:
> > Quoting Ingo Molnar <mingo@elte.hu>:
> > Subject: Re: [5/6] 2.6.21-rc2: known regressions
> > 
> > 
> > * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
> > 
> > > > Quoting Linus Torvalds <torvalds@linux-foundation.org>:
> > > >
> > > > Ok, it does indeed solve the problem for me.
> > > 
> > > Not yet for me unfortunately, although this seems to help.
> > > Is this the patch I should have applied?
> > > http://lkml.org/lkml/2007/3/5/445
> > > 
> > > With this applied, on resume I get *some* screen output soon after 
> > > resume (e.g. with s2ram I get several characters on VGA, X starts 
> > > drawing some windows) but then the crescent symbol starts blinking 
> > > again and the system hangs.
> > 
> > could you try this via s2ram on a text console, to see whether the 
> > kernel spits out any warning before it locks up?
> 
> Yes, that's what I did. Unfortunately only a couple of characters were
> shown before it locked up.
> 
> I still need to check what does this do in the NO_HZ configuration.
> 
> BTW, Ingo, can you suspend/resume any number of times with this patch?

well I could at least two times in a row in my minimalistic setup
(config attached) however using the full kernel config it still
hangs ... (config also attached in case you watn to compare it).

Soeren
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.

[-- Attachment #2: linux-config-2.6.21-isolated-s2ram-debug.bz2 --]
[-- Type: application/x-bzip, Size: 5937 bytes --]

[-- Attachment #3: linux-config-2.6.21.bz2 --]
[-- Type: application/x-bzip, Size: 11603 bytes --]

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Soeren Sonnenburg <kernel@nn7.de> wrote:

> > BTW, Ingo, can you suspend/resume any number of times with this 
> > patch?
> 
> well I could at least two times in a row in my minimalistic setup 
> (config attached) however using the full kernel config it still hangs 
> ... (config also attached in case you watn to compare it).

i can confirm that with your full config i see a hang too. This is most 
likely the ACPI problem - we are debugging this now and will come up 
with a patch.

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

[-- Attachment #1: Type: text/plain, Size: 677 bytes --]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [5/6] 2.6.21-rc2: known regressions
> 
> 
> * Soeren Sonnenburg <kernel@nn7.de> wrote:
> 
> > > BTW, Ingo, can you suspend/resume any number of times with this 
> > > patch?
> > 
> > well I could at least two times in a row in my minimalistic setup 
> > (config attached) however using the full kernel config it still hangs 
> > ... (config also attached in case you watn to compare it).
> 
> i can confirm that with your full config i see a hang too. This is most 
> likely the ACPI problem - we are debugging this now and will come up 
> with a patch.
> 
> 	Ingo

Here's mine too, in case someone's interested.

-- 
MST


[-- Attachment #2: linux-2.6.21-work.config.gz --]
[-- Type: application/octet-stream, Size: 11476 bytes --]

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> > > BTW, Ingo, can you suspend/resume any number of times with this 
> > > patch?
> > 
> > well I could at least two times in a row in my minimalistic setup 
> > (config attached) however using the full kernel config it still 
> > hangs ... (config also attached in case you watn to compare it).
> 
> i can confirm that with your full config i see a hang too. This is 
> most likely the ACPI problem - we are debugging this now and will come 
> up with a patch.

update: this only happens with simulation, and even then it's not a full 
hang but 'hangs until i hit a key'. With real resume i'm hitting a real 
key anyway so it doesnt hang.

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: [5/6] 2.6.21-rc2: known regressions
> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > > > BTW, Ingo, can you suspend/resume any number of times with this 
> > > > patch?
> > > 
> > > well I could at least two times in a row in my minimalistic setup 
> > > (config attached) however using the full kernel config it still 
> > > hangs ... (config also attached in case you watn to compare it).
> > 
> > i can confirm that with your full config i see a hang too. This is 
> > most likely the ACPI problem - we are debugging this now and will come 
> > up with a patch.
> 
> update: this only happens with simulation, and even then it's not a full 
> hang but 'hangs until i hit a key'. With real resume i'm hitting a real 
> key anyway so it doesnt hang.

How 'bout my .config?


-- 
MST

Re: [5/6] 2.6.21-rc2: known regressions

[Ingo Molnar]

* Michael S. Tsirkin <mst@mellanox.co.il> wrote:

> > update: this only happens with simulation, and even then it's not a 
> > full hang but 'hangs until i hit a key'. With real resume i'm 
> > hitting a real key anyway so it doesnt hang.
> 
> How 'bout my .config?

your config works fine here too - did full suspend/resume twice without 
any problems. Maybe it's the ACPI related regression Thomas is seeing.

	Ingo

Re: [5/6] 2.6.21-rc2: known regressions

[Thomas Gleixner]

On Tue, 2007-03-06 at 13:51 +0100, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > > > BTW, Ingo, can you suspend/resume any number of times with this 
> > > > patch?
> > > 
> > > well I could at least two times in a row in my minimalistic setup 
> > > (config attached) however using the full kernel config it still 
> > > hangs ... (config also attached in case you watn to compare it).
> > 
> > i can confirm that with your full config i see a hang too. This is 
> > most likely the ACPI problem - we are debugging this now and will come 
> > up with a patch.
> 
> update: this only happens with simulation, and even then it's not a full 
> hang but 'hangs until i hit a key'. With real resume i'm hitting a real 
> key anyway so it doesnt hang.

Hmm. The key is consumed in the BIOS, so there should be no
interrupt. /me digs deeper.

	tglx

Re: [5/6] 2.6.21-rc2: known regressions

[Jeff Chua]

On 3/6/07, Soeren Sonnenburg <kernel@nn7.de> wrote:

> > > > Not yet for me unfortunately, although this seems to help.
> > > > Is this the patch I should have applied?
> > > > http://lkml.org/lkml/2007/3/5/445

Same problem for me on 2.6.21-rc2/rc1 on IBM X60s. I've applied this
patch and Ingo Molnar's patch and s2ram still can't suspend. I tried
turning off CONFIG_KVM as well, but makes no difference.

Will try turning off CONFIG_NO_HZ to see if this makes any difference.
2.6.20 works fine.
Jeff.

Re: [5/6] 2.6.21-rc2: known regressions

[Pavel Machek]

Hi!

> > > > Quoting Linus Torvalds <torvalds@linux-foundation.org>:
> > > >
> > > > Ok, it does indeed solve the problem for me.
> > > 
> > > Not yet for me unfortunately, although this seems to help.
> > > Is this the patch I should have applied?
> > > http://lkml.org/lkml/2007/3/5/445
> > > 
> > > With this applied, on resume I get *some* screen output soon after 
> > > resume (e.g. with s2ram I get several characters on VGA, X starts 
> > > drawing some windows) but then the crescent symbol starts blinking 
> > > again and the system hangs.
> > 
> > could you try this via s2ram on a text console, to see whether the 
> > kernel spits out any warning before it locks up?
> 
> Yes, that's what I did. Unfortunately only a couple of characters were
> shown before it locked up.

Was it 'Linu'? That's different debugging hack.

Anyway, I suspect yout problem is debuggable with printk+mdelay...

							Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [5/6] 2.6.21-rc2: known regressions

[Michael S. Tsirkin]

> Quoting Linus Torvalds <torvalds@linux-foundation.org>:
>
> Ok, it does indeed solve the problem for me.

Not yet for me unfortunately, although this seems to help.
Is this the patch I should have applied?
http://lkml.org/lkml/2007/3/5/445

With this applied, on resume I get *some* screen output soon after resume
(e.g. with s2ram I get several characters on VGA, X starts drawing some windows)
but then the crescent symbol starts blinking again and the system hangs.

Could this be the ACPI problem Thomas mentions (acpi_processor_start is not called
when CPU#1 is resumed)?

-- 
MST

[6/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
References : http://bugzilla.kernel.org/show_bug.cgi?id€97
Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
Caused-By  : David S. Miller <davem@sunset.davemloft.net>
             commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
Status     : unknown


Subject    : mmc reader no longer works
References : http://lkml.org/lkml/2007/2/27/91
Submitter  : Pavel Machek <pavel@ucw.cz>
Caused-By  : Oliver Neukum <oneukum@suse.de>
Status     : problem is being debugged


Subject    : usb-serial broken
             (ftdi serial device shows up as ttyUSB140 instead of ttyUSB0)
Submitter  : Craig Schlenter <craig@codefountain.com>
Caused-By  : Oliver Neukum <oneukum@suse.de>
             commit 34ef50e5b1f96c2d8c0f3d28b7d407743806256c
Handled-By : Oliver Neukum <oneukum@suse.de>
Status     : patch available


Subject    : Oops in rtc_cmos
References : http://lkml.org/lkml/2007/3/4/112
             http://lkml.org/lkml/2007/2/18/172
Submitter  : Paul Rolland <rol@as2917.net>
             Rafael J. Wysocki <rjw@sisk.pl>
Caused-By  : David Brownell <david-b@pacbell.net>
             commit 7be2c7c96aff2871240d61fef508c41176c688b5
Patch      : http://lkml.org/lkml/2007/2/23/184
Status     : patch available

[6/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
that are not yet fixed in Linus' tree.

If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly involved with one or more of these issues.

Due to the huge amount of recipients, please trim the Cc when answering.


Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
References : http://bugzilla.kernel.org/show_bug.cgi?id=8097
Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
Caused-By  : David S. Miller <davem@sunset.davemloft.net>
             commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
Status     : unknown


Subject    : mmc reader no longer works
References : http://lkml.org/lkml/2007/2/27/91
Submitter  : Pavel Machek <pavel@ucw.cz>
Caused-By  : Oliver Neukum <oneukum@suse.de>
Status     : problem is being debugged


Subject    : usb-serial broken
             (ftdi serial device shows up as ttyUSB140 instead of ttyUSB0)
Submitter  : Craig Schlenter <craig@codefountain.com>
Caused-By  : Oliver Neukum <oneukum@suse.de>
             commit 34ef50e5b1f96c2d8c0f3d28b7d407743806256c
Handled-By : Oliver Neukum <oneukum@suse.de>
Status     : patch available


Subject    : Oops in rtc_cmos
References : http://lkml.org/lkml/2007/3/4/112
             http://lkml.org/lkml/2007/2/18/172
Submitter  : Paul Rolland <rol@as2917.net>
             Rafael J. Wysocki <rjw@sisk.pl>
Caused-By  : David Brownell <david-b@pacbell.net>
             commit 7be2c7c96aff2871240d61fef508c41176c688b5
Patch      : http://lkml.org/lkml/2007/2/23/184
Status     : patch available

Re: [6/6] 2.6.21-rc2: known regressions

[David Miller]

From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 5 Mar 2007 02:50:45 +0100

> Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> References : http://bugzilla.kernel.org/show_bug.cgi?id€97
> Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> Caused-By  : David S. Miller <davem@sunset.davemloft.net>
>              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> Status     : unknown

Fixed in current GIT.

commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
Author: David S. Miller <davem@sunset.davemloft.net>
Date:   Wed Feb 28 13:09:34 2007 -0800

    [SPARC64]: Fix parport_pc build.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

Re: [6/6] 2.6.21-rc2: known regressions

[David Miller]

From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 5 Mar 2007 02:50:45 +0100

> Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8097
> Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> Caused-By  : David S. Miller <davem@sunset.davemloft.net>
>              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> Status     : unknown

Fixed in current GIT.

commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
Author: David S. Miller <davem@sunset.davemloft.net>
Date:   Wed Feb 28 13:09:34 2007 -0800

    [SPARC64]: Fix parport_pc build.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

Re: [6/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

On Sun, Mar 04, 2007 at 06:07:25PM -0800, David Miller wrote:
> From: Adrian Bunk <bunk@stusta.de>
> Date: Mon, 5 Mar 2007 02:50:45 +0100
> 
> > Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> > References : http://bugzilla.kernel.org/show_bug.cgi?id€97
> > Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> > Caused-By  : David S. Miller <davem@sunset.davemloft.net>
> >              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> > Status     : unknown
> 
> Fixed in current GIT.
> 
> commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
> Author: David S. Miller <davem@sunset.davemloft.net>
> Date:   Wed Feb 28 13:09:34 2007 -0800
> 
>     [SPARC64]: Fix parport_pc build.
>     
>     Signed-off-by: David S. Miller <davem@davemloft.net>

Horst's problem is with the floppy driver and 
claim_dma_lock/release_dma_lock in include/asm-sparc64/dma.h .

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [6/6] 2.6.21-rc2: known regressions

[Adrian Bunk]

On Sun, Mar 04, 2007 at 06:07:25PM -0800, David Miller wrote:
> From: Adrian Bunk <bunk@stusta.de>
> Date: Mon, 5 Mar 2007 02:50:45 +0100
> 
> > Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> > References : http://bugzilla.kernel.org/show_bug.cgi?id=8097
> > Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> > Caused-By  : David S. Miller <davem@sunset.davemloft.net>
> >              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> > Status     : unknown
> 
> Fixed in current GIT.
> 
> commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
> Author: David S. Miller <davem@sunset.davemloft.net>
> Date:   Wed Feb 28 13:09:34 2007 -0800
> 
>     [SPARC64]: Fix parport_pc build.
>     
>     Signed-off-by: David S. Miller <davem@davemloft.net>

Horst's problem is with the floppy driver and 
claim_dma_lock/release_dma_lock in include/asm-sparc64/dma.h .

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [6/6] 2.6.21-rc2: known regressions

[David Miller]

From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 5 Mar 2007 03:26:02 +0100

> On Sun, Mar 04, 2007 at 06:07:25PM -0800, David Miller wrote:
> > From: Adrian Bunk <bunk@stusta.de>
> > Date: Mon, 5 Mar 2007 02:50:45 +0100
> > 
> > > Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> > > References : http://bugzilla.kernel.org/show_bug.cgi?id€97
> > > Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> > > Caused-By  : David S. Miller <davem@sunset.davemloft.net>
> > >              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> > > Status     : unknown
> > 
> > Fixed in current GIT.
> > 
> > commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
> > Author: David S. Miller <davem@sunset.davemloft.net>
> > Date:   Wed Feb 28 13:09:34 2007 -0800
> > 
> >     [SPARC64]: Fix parport_pc build.
> >     
> >     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Horst's problem is with the floppy driver and 
> claim_dma_lock/release_dma_lock in include/asm-sparc64/dma.h .

Thanks for the clarification, I was thinking of the parport
problem reported by Meelis Roos.

I'll look into this.

Re: [6/6] 2.6.21-rc2: known regressions

[David Miller]

From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 5 Mar 2007 03:26:02 +0100

> On Sun, Mar 04, 2007 at 06:07:25PM -0800, David Miller wrote:
> > From: Adrian Bunk <bunk@stusta.de>
> > Date: Mon, 5 Mar 2007 02:50:45 +0100
> > 
> > > Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> > > References : http://bugzilla.kernel.org/show_bug.cgi?id=8097
> > > Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> > > Caused-By  : David S. Miller <davem@sunset.davemloft.net>
> > >              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> > > Status     : unknown
> > 
> > Fixed in current GIT.
> > 
> > commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
> > Author: David S. Miller <davem@sunset.davemloft.net>
> > Date:   Wed Feb 28 13:09:34 2007 -0800
> > 
> >     [SPARC64]: Fix parport_pc build.
> >     
> >     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Horst's problem is with the floppy driver and 
> claim_dma_lock/release_dma_lock in include/asm-sparc64/dma.h .

Thanks for the clarification, I was thinking of the parport
problem reported by Meelis Roos.

I'll look into this.

Re: [6/6] 2.6.21-rc2: known regressions

[David Miller]

From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 5 Mar 2007 03:26:02 +0100

> On Sun, Mar 04, 2007 at 06:07:25PM -0800, David Miller wrote:
> > From: Adrian Bunk <bunk@stusta.de>
> > Date: Mon, 5 Mar 2007 02:50:45 +0100
> > 
> > > Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> > > References : http://bugzilla.kernel.org/show_bug.cgi?id€97
> > > Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> > > Caused-By  : David S. Miller <davem@sunset.davemloft.net>
> > >              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> > > Status     : unknown
> > 
> > Fixed in current GIT.
> > 
> > commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
> > Author: David S. Miller <davem@sunset.davemloft.net>
> > Date:   Wed Feb 28 13:09:34 2007 -0800
> > 
> >     [SPARC64]: Fix parport_pc build.
> >     
> >     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Horst's problem is with the floppy driver and 
> claim_dma_lock/release_dma_lock in include/asm-sparc64/dma.h .

Here is the fix I will send to Linus for this, thanks:

commit 08414aa2516da65ae7a522c6834b8ea576f38c4b
Author: David S. Miller <davem@sunset.davemloft.net>
Date:   Sun Mar 4 20:36:18 2007 -0800

    [SPARC64]: Fix floppy build failure.
    
    Just define a local {claim,release}_dma_lock() implementation
    for the floppy driver to use so we don't need to define and
    export to modules the silly dma_spin_lock.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/include/asm-sparc64/dma.h b/include/asm-sparc64/dma.h
index 1bf4f7a..a9fd061 100644
--- a/include/asm-sparc64/dma.h
+++ b/include/asm-sparc64/dma.h
@@ -15,17 +15,6 @@
 #include <asm/delay.h>
 #include <asm/oplib.h>
 
-extern spinlock_t  dma_spin_lock;
-
-#define claim_dma_lock() \
-({	unsigned long flags; \
-	spin_lock_irqsave(&dma_spin_lock, flags); \
-	flags; \
-})
-
-#define release_dma_lock(__flags) \
-	spin_unlock_irqrestore(&dma_spin_lock, __flags);
-
 /* These are irrelevant for Sparc DMA, but we leave it in so that
  * things can compile.
  */
diff --git a/include/asm-sparc64/floppy.h b/include/asm-sparc64/floppy.h
index dbe033e..331013a 100644
--- a/include/asm-sparc64/floppy.h
+++ b/include/asm-sparc64/floppy.h
@@ -854,4 +854,15 @@ static unsigned long __init sun_floppy_init(void)
 
 #define EXTRA_FLOPPY_PARAMS
 
+static DEFINE_SPINLOCK(dma_spin_lock);
+
+#define claim_dma_lock() \
+({	unsigned long flags; \
+	spin_lock_irqsave(&dma_spin_lock, flags); \
+	flags; \
+})
+
+#define release_dma_lock(__flags) \
+	spin_unlock_irqrestore(&dma_spin_lock, __flags);
+
 #endif /* !(__ASM_SPARC64_FLOPPY_H) */

Re: [6/6] 2.6.21-rc2: known regressions

[David Miller]

From: Adrian Bunk <bunk@stusta.de>
Date: Mon, 5 Mar 2007 03:26:02 +0100

> On Sun, Mar 04, 2007 at 06:07:25PM -0800, David Miller wrote:
> > From: Adrian Bunk <bunk@stusta.de>
> > Date: Mon, 5 Mar 2007 02:50:45 +0100
> > 
> > > Subject    : sparc64 compile error due to GENERIC_ISA_DMA removal
> > > References : http://bugzilla.kernel.org/show_bug.cgi?id=8097
> > > Submitter  : Horst H. von Brand <vonbrand@inf.utfsm.cl>
> > > Caused-By  : David S. Miller <davem@sunset.davemloft.net>
> > >              commit 1b51d3a08b6c80a1e47d4c579c41abbe56cd3c44
> > > Status     : unknown
> > 
> > Fixed in current GIT.
> > 
> > commit 74bd7d093b8e87f35eaf3b14459b96a0e20d1d10
> > Author: David S. Miller <davem@sunset.davemloft.net>
> > Date:   Wed Feb 28 13:09:34 2007 -0800
> > 
> >     [SPARC64]: Fix parport_pc build.
> >     
> >     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Horst's problem is with the floppy driver and 
> claim_dma_lock/release_dma_lock in include/asm-sparc64/dma.h .

Here is the fix I will send to Linus for this, thanks:

commit 08414aa2516da65ae7a522c6834b8ea576f38c4b
Author: David S. Miller <davem@sunset.davemloft.net>
Date:   Sun Mar 4 20:36:18 2007 -0800

    [SPARC64]: Fix floppy build failure.
    
    Just define a local {claim,release}_dma_lock() implementation
    for the floppy driver to use so we don't need to define and
    export to modules the silly dma_spin_lock.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/include/asm-sparc64/dma.h b/include/asm-sparc64/dma.h
index 1bf4f7a..a9fd061 100644
--- a/include/asm-sparc64/dma.h
+++ b/include/asm-sparc64/dma.h
@@ -15,17 +15,6 @@
 #include <asm/delay.h>
 #include <asm/oplib.h>
 
-extern spinlock_t  dma_spin_lock;
-
-#define claim_dma_lock() \
-({	unsigned long flags; \
-	spin_lock_irqsave(&dma_spin_lock, flags); \
-	flags; \
-})
-
-#define release_dma_lock(__flags) \
-	spin_unlock_irqrestore(&dma_spin_lock, __flags);
-
 /* These are irrelevant for Sparc DMA, but we leave it in so that
  * things can compile.
  */
diff --git a/include/asm-sparc64/floppy.h b/include/asm-sparc64/floppy.h
index dbe033e..331013a 100644
--- a/include/asm-sparc64/floppy.h
+++ b/include/asm-sparc64/floppy.h
@@ -854,4 +854,15 @@ static unsigned long __init sun_floppy_init(void)
 
 #define EXTRA_FLOPPY_PARAMS
 
+static DEFINE_SPINLOCK(dma_spin_lock);
+
+#define claim_dma_lock() \
+({	unsigned long flags; \
+	spin_lock_irqsave(&dma_spin_lock, flags); \
+	flags; \
+})
+
+#define release_dma_lock(__flags) \
+	spin_unlock_irqrestore(&dma_spin_lock, __flags);
+
 #endif /* !(__ASM_SPARC64_FLOPPY_H) */

Re: [6/6] 2.6.21-rc2: known regressions

[Greg KH]

On Mon, Mar 05, 2007 at 02:50:45AM +0100, Adrian Bunk wrote:
> 
> Subject    : usb-serial broken
>              (ftdi serial device shows up as ttyUSB140 instead of ttyUSB0)
> Submitter  : Craig Schlenter <craig@codefountain.com>
> Caused-By  : Oliver Neukum <oneukum@suse.de>
>              commit 34ef50e5b1f96c2d8c0f3d28b7d407743806256c
> Handled-By : Oliver Neukum <oneukum@suse.de>
> Status     : patch available

Patch is queued up in my tree and will go to Linus in a few days.

But I think there is another usb-serial patch that Oliver needs to send
me to fix another problem with the usb-serial core...

thanks,

greg k-h

Re: [6/6] 2.6.21-rc2: known regressions

[Greg KH]

On Mon, Mar 05, 2007 at 02:50:45AM +0100, Adrian Bunk wrote:
> 
> Subject    : usb-serial broken
>              (ftdi serial device shows up as ttyUSB140 instead of ttyUSB0)
> Submitter  : Craig Schlenter <craig@codefountain.com>
> Caused-By  : Oliver Neukum <oneukum@suse.de>
>              commit 34ef50e5b1f96c2d8c0f3d28b7d407743806256c
> Handled-By : Oliver Neukum <oneukum@suse.de>
> Status     : patch available

Patch is queued up in my tree and will go to Linus in a few days.

But I think there is another usb-serial patch that Oliver needs to send
me to fix another problem with the usb-serial core...

thanks,

greg k-h

[PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

Improve the backlight code to emulate as much as possible the power
management events, as we are unable to really power on or power off the
backlight.

Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Richard Purdie <rpurdie@rpsys.net>
---

 Len, I have added this to the for-upstream/acpi-test branch
 of git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git
 for when you pull it.

 drivers/acpi/ibm_acpi.c |    5 ++++-
 drivers/acpi/ibm_acpi.h |    1 +
 2 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index dd36be0..6573d01 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -1664,7 +1664,10 @@ static void brightness_exit(void)
 
 static int brightness_update_status(struct backlight_device *bd)
 {
-	return brightness_set(bd->props.brightness);
+	return brightness_set(
+		(bd->props.fb_blank == FB_BLANK_UNBLANK &&
+		 bd->props.power == FB_BLANK_UNBLANK) ?
+				bd->props.brightness : 0);
 }
 
 static int brightness_get(struct backlight_device *bd)
diff --git a/drivers/acpi/ibm_acpi.h b/drivers/acpi/ibm_acpi.h
index 4d0387a..b63c014 100644
--- a/drivers/acpi/ibm_acpi.h
+++ b/drivers/acpi/ibm_acpi.h
@@ -32,6 +32,7 @@
 
 #include <linux/proc_fs.h>
 #include <linux/backlight.h>
+#include <linux/fb.h>
 #include <asm/uaccess.h>
 
 #include <linux/dmi.h>
-- 
1.5.0.1

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

Improve the backlight code to emulate as much as possible the power
management events, as we are unable to really power on or power off the
backlight.

Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Richard Purdie <rpurdie@rpsys.net>
---

 Len, I have added this to the for-upstream/acpi-test branch
 of git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git
 for when you pull it.

 drivers/acpi/ibm_acpi.c |    5 ++++-
 drivers/acpi/ibm_acpi.h |    1 +
 2 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index dd36be0..6573d01 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -1664,7 +1664,10 @@ static void brightness_exit(void)
 
 static int brightness_update_status(struct backlight_device *bd)
 {
-	return brightness_set(bd->props.brightness);
+	return brightness_set(
+		(bd->props.fb_blank == FB_BLANK_UNBLANK &&
+		 bd->props.power == FB_BLANK_UNBLANK) ?
+				bd->props.brightness : 0);
 }
 
 static int brightness_get(struct backlight_device *bd)
diff --git a/drivers/acpi/ibm_acpi.h b/drivers/acpi/ibm_acpi.h
index 4d0387a..b63c014 100644
--- a/drivers/acpi/ibm_acpi.h
+++ b/drivers/acpi/ibm_acpi.h
@@ -32,6 +32,7 @@
 
 #include <linux/proc_fs.h>
 #include <linux/backlight.h>
+#include <linux/fb.h>
 #include <asm/uaccess.h>
 
 #include <linux/dmi.h>
-- 
1.5.0.1

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Re: [PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

EWRONGLIST.

Sorry about this, it won't happen again.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

2.6.21-rc1 dims my LCD

[Jiri Kosina]

Richard,

2.6.21-rc1 on my ibm t42p dims a LCD after some time (I guess it happens 
at the time the console should normally be blanked). 

When I hit the keyboard, the brightness stays low (it's 50% of light or 
so, so I could read what's on the screen, but it's uncomfortably dim), and 
I have to manually raise the brightness on the LCD. Quite annoying :)

I have bisected this to your commit 
994efacdf9a087b52f71e620b58dfa526b0cf928

Thanks,

-- 
Jiri Kosina

Re: 2.6.21-rc1 dims my LCD

[Richard Purdie]

Hi,

On Mon, 2007-02-26 at 01:59 +0100, Jiri Kosina wrote:
> 2.6.21-rc1 on my ibm t42p dims a LCD after some time (I guess it happens 
> at the time the console should normally be blanked). 
> 
> When I hit the keyboard, the brightness stays low (it's 50% of light or 
> so, so I could read what's on the screen, but it's uncomfortably dim), and 
> I have to manually raise the brightness on the LCD. Quite annoying :)
>
> I have bisected this to your commit 
> 994efacdf9a087b52f71e620b58dfa526b0cf928

Which framebuffer driver and backlight driver are you using?
("ls /sys/class/backlight/" will show which backlight it is)

Is the machine in active use when it dims or at idle and does the screen
blank at the same time it dims? If so, does the keypress unblank the
screen (but not change the brightness)? 

Also, is this on a console or under something like X? 

Thanks,

Richard

Re: 2.6.21-rc1 dims my LCD

[Jiri Kosina]

On Mon, 26 Feb 2007, Richard Purdie wrote:

> > When I hit the keyboard, the brightness stays low (it's 50% of light 
> > or so, so I could read what's on the screen, but it's uncomfortably 
> > dim), and I have to manually raise the brightness on the LCD. Quite 
> > annoying :) I have bisected this to your commit 
> > 994efacdf9a087b52f71e620b58dfa526b0cf928
> Which framebuffer driver and backlight driver are you using?
> ("ls /sys/class/backlight/" will show which backlight it is)

It's IBM:

$ ll /sys/class/backlight/
drwxr-xr-x 2 root root 0 Feb 26 13:28 ibm

At the time the brightness goes low, there is '0' in 
/sys/class/backlight/ibm/actual_brightness and 
/sys/class/backlight/ibm/brightness

Echoing '7' into /sys/class/backlight/ibm/brightness gets the brightness 
back again to normal.

> Is the machine in active use when it dims or at idle and does the screen 
> blank at the same time it dims? If so, does the keypress unblank the 
> screen (but not change the brightness)?

It doesn't blank at the time it dims - it just decreases brightness. I 
will do some more tests, but it seemed on a first sight that it happens 
only when the machine is idle.

> Also, is this on a console or under something like X? 

I observed it only on console, but didn't experiment with it too much yet.

-- 
Jiri Kosina

Re: 2.6.21-rc1 dims my LCD

[Henrique de Moraes Holschuh]

On Mon, 26 Feb 2007, Jiri Kosina wrote:
> On Mon, 26 Feb 2007, Richard Purdie wrote:
> > > When I hit the keyboard, the brightness stays low (it's 50% of light 
> > > or so, so I could read what's on the screen, but it's uncomfortably 
> > > dim), and I have to manually raise the brightness on the LCD. Quite 
> > > annoying :) I have bisected this to your commit 
> > > 994efacdf9a087b52f71e620b58dfa526b0cf928
> > Which framebuffer driver and backlight driver are you using?
> > ("ls /sys/class/backlight/" will show which backlight it is)
> 
> It's IBM:

Please add me to the CC, then.  I noticed this thread by accident.

> $ ll /sys/class/backlight/
> drwxr-xr-x 2 root root 0 Feb 26 13:28 ibm
> 
> At the time the brightness goes low, there is '0' in 
> /sys/class/backlight/ibm/actual_brightness and 
> /sys/class/backlight/ibm/brightness

ibm-acpi does not implement display poweroff, so if a screen-saving function
on the kernel is trying to use it to shut the display off, it will either
fail to do anything, or if it ALSO sets brightness to zero, it will just dim
the display.

Richard, would you like a patch to -ENOSYS if a display power management
event reaches ibm-acpi?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: 2.6.21-rc1 dims my LCD

[Richard Purdie]

On Mon, 2007-02-26 at 11:21 -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 26 Feb 2007, Jiri Kosina wrote:
> > On Mon, 26 Feb 2007, Richard Purdie wrote:
> > > > When I hit the keyboard, the brightness stays low (it's 50% of light 
> > > > or so, so I could read what's on the screen, but it's uncomfortably 
> > > > dim), and I have to manually raise the brightness on the LCD. Quite 
> > > > annoying :) I have bisected this to your commit 
> > > > 994efacdf9a087b52f71e620b58dfa526b0cf928
> > > Which framebuffer driver and backlight driver are you using?
> > > ("ls /sys/class/backlight/" will show which backlight it is)
> > 
> > It's IBM:
> 
> Please add me to the CC, then.  I noticed this thread by accident.
> 
> > $ ll /sys/class/backlight/
> > drwxr-xr-x 2 root root 0 Feb 26 13:28 ibm
> > 
> > At the time the brightness goes low, there is '0' in 
> > /sys/class/backlight/ibm/actual_brightness and 
> > /sys/class/backlight/ibm/brightness
> 
> ibm-acpi does not implement display poweroff, so if a screen-saving function
> on the kernel is trying to use it to shut the display off, it will either
> fail to do anything, or if it ALSO sets brightness to zero, it will just dim
> the display.

I think I can explain whats going on. The commit you pointed to isn't
really at fault, it just happens to trigger an extra framebuffer
blanking call and this exposes a bug in the ibm backlight code which
there is already a fix for.

Basically, console blanking triggers a backlight_update_status() call
and bd->props.brightness wasn't set correctly at boot time. If
bd->props.brightness is set correctly, that call won't cause a problem. 

Jiri: I've appended a patch that should already be queued, could you
test and see if it solves the problem.

> Richard, would you like a patch to -ENOSYS if a display power management
> event reaches ibm-acpi?

The ibm backlight driver should really try and work with the system a
little more. Even if it can't turn the display off, the power attribute
should  minimise power usage as best it can. If that means just dimming
the display, so be it. Ideally, I'd still prefer for it to gain support
for turning the display off.

In the update_status function, there are three sources of information
you need to combine:

bd->props.brightness
bd->props.power
bd->props.fb_blank

Since the backlight class doesn't know the capabilities of the hardware,
it is left to each implementation to combine these options in a way that
makes sense. Currently ibm just looks at the first one but it could dim
if the latter two are anything other than FB_BLANK_UNBLANK. See corgi_bl
as an example (which also looks at its own variables too).

Richard

----

From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>

ACPI: ibm-acpi: fix initial status of backlight device

The brightness class core does not update the initial status of the
device's brightness at register time.  Do it by ourselves.

Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Richard Purdie <rpurdie@rpsys.net>
---
 drivers/acpi/ibm_acpi.c |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index 4cc534e..7c1b418 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -1711,6 +1711,12 @@ static struct backlight_ops ibm_backlight_data = {
 
 static int brightness_init(void)
 {
+       int b;
+
+       b = brightness_get(NULL);
+       if (b < 0)
+               return b;
+
        ibm_backlight_device = backlight_device_register("ibm", NULL, NULL,
                                                         &ibm_backlight_data);
        if (IS_ERR(ibm_backlight_device)) {
@@ -1718,7 +1724,9 @@ static int brightness_init(void)
                return PTR_ERR(ibm_backlight_device);
        }
 
-        ibm_backlight_device->props.max_brightness = 7;
+       ibm_backlight_device->props.max_brightness = 7;
+       ibm_backlight_device->props.brightness = b;
+       backlight_update_status(ibm_backlight_device);
 
        return 0;
 }

Re: 2.6.21-rc1 dims my LCD

[Henrique de Moraes Holschuh]

On Mon, 26 Feb 2007, Richard Purdie wrote:
> > Richard, would you like a patch to -ENOSYS if a display power management
> > event reaches ibm-acpi?
> 
> The ibm backlight driver should really try and work with the system a
> little more. Even if it can't turn the display off, the power attribute
> should  minimise power usage as best it can. If that means just dimming
> the display, so be it. Ideally, I'd still prefer for it to gain support
> for turning the display off.

Well, the thinkpad firmware doesn't know how to turn the backlight off, or
doesn't export that AFAIK.  It *can* do it in hardware (cuts power to the
inverter or somesuch in the lid switch, etc) but I know of no way to do it
using the firmware.  If I ever find a way, I will certainly add it.

The video card *can* do it, but we are talking either intel fb or radeon fb
here, I'd need a way to communicate with them, or they should be getting the
same events and doing it anyway.

> In the update_status function, there are three sources of information
> you need to combine:
> 
> bd->props.brightness
> bd->props.power
> bd->props.fb_blank
> 
> Since the backlight class doesn't know the capabilities of the hardware,
> it is left to each implementation to combine these options in a way that
> makes sense. Currently ibm just looks at the first one but it could dim
> if the latter two are anything other than FB_BLANK_UNBLANK. See corgi_bl
> as an example (which also looks at its own variables too).

I will implement that, and as usual I will request your ACK since it deals
with your subsystem too.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

Improve the backlight code to emulate as much as possible the power
management events, as we are unable to really power on or power off the
backlight.

Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Richard Purdie <rpurdie@rpsys.net>
---

 Status: waiting ACK from Richard Purdie <rpurdie@rpsys.net>

 drivers/acpi/ibm_acpi.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index e7309a6..cb5885e 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -86,6 +86,7 @@
 
 #include <linux/proc_fs.h>
 #include <linux/backlight.h>
+#include <linux/fb.h>
 #include <asm/uaccess.h>
 
 #include <linux/dmi.h>
@@ -1707,7 +1708,8 @@ static int brightness_write(char *buf)
 
 static int brightness_update_status(struct backlight_device *bd)
 {
-	return brightness_set(bd->props.brightness);
+	return brightness_set((bd->props.fb_blank == FB_BLANK_UNBLANK)? 
+				bd->props.brightness : 0);
 }
 
 static struct backlight_ops ibm_backlight_data = {
-- 
1.5.0.1

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: [PATCH] ACPI: ibm-acpi: improve backlight power handling

[Richard Purdie]

On Mon, 2007-02-26 at 13:12 -0300, Henrique de Moraes Holschuh wrote:
> @@ -1707,7 +1708,8 @@ static int brightness_write(char *buf)
>  
>  static int brightness_update_status(struct backlight_device *bd)
>  {
> -	return brightness_set(bd->props.brightness);
> +	return brightness_set((bd->props.fb_blank == FB_BLANK_UNBLANK)? 
> +				bd->props.brightness : 0);
>  }
>  
>  static struct backlight_ops ibm_backlight_data = {

Should we be looking at bd->props.power here too?

Richard

Re: [PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

On Mon, 26 Feb 2007, Richard Purdie wrote:
> On Mon, 2007-02-26 at 13:12 -0300, Henrique de Moraes Holschuh wrote:
> > @@ -1707,7 +1708,8 @@ static int brightness_write(char *buf)
> >  
> >  static int brightness_update_status(struct backlight_device *bd)
> >  {
> > -	return brightness_set(bd->props.brightness);
> > +	return brightness_set((bd->props.fb_blank == FB_BLANK_UNBLANK)? 
> > +				bd->props.brightness : 0);
> >  }
> >  
> >  static struct backlight_ops ibm_backlight_data = {
> 
> Should we be looking at bd->props.power here too?

Probably.  I will update the patch.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: [PATCH] ACPI: ibm-acpi: improve backlight power handling

[Jiri Kosina]

On Mon, 26 Feb 2007, Henrique de Moraes Holschuh wrote:

> Improve the backlight code to emulate as much as possible the power
> management events, as we are unable to really power on or power off the
> backlight.

This still easily leads to confusing behavior, doesn't it? As there are 
power-related calls from backlight driver, which won't get handled 
properly by your code, in result confusing the brightness status.

I would suggest applying something like the patch below instead, if you 
find it OK.



From: Jiri Kosina <jkosina@suse.cz>

[PATCH] ibm-acpi: handle power calls from backlight class

Don't ignore the power-related calls from backlight class driver
and always adjust the brightness accordingly.

Signed-off-by: Jiri Kosina <jkosina@suse.cz>

--- 

 drivers/acpi/ibm_acpi.c             |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/drivers/acpi/ibm_acpi.c b/drivers/acpi/ibm_acpi.c
index 7c1b418..4cfa5f8 100644
--- a/drivers/acpi/ibm_acpi.c
+++ b/drivers/acpi/ibm_acpi.c
@@ -87,6 +87,7 @@
 #include <linux/proc_fs.h>
 #include <linux/backlight.h>
 #include <asm/uaccess.h>
+#include <linux/fb.h>
 
 #include <linux/dmi.h>
 #include <linux/jiffies.h>
@@ -1701,7 +1702,12 @@ static int brightness_write(char *buf)
 
 static int brightness_update_status(struct backlight_device *bd)
 {
-	return brightness_set(bd->props.brightness);
+	int brightness = 0;
+
+	if (bd->props.fb_blank == FB_BLANK_UNBLANK || bd->props.power == FB_BLANK_UNBLANK)
+		brightness = bd->props.brightness;
+	return brightness_set(brightness); 
+
 }
 
 static struct backlight_ops ibm_backlight_data = {

Re: [PATCH] ACPI: ibm-acpi: improve backlight power handling

[Henrique de Moraes Holschuh]

On Mon, 26 Feb 2007, Jiri Kosina wrote:
> On Mon, 26 Feb 2007, Henrique de Moraes Holschuh wrote:
> > Improve the backlight code to emulate as much as possible the power
> > management events, as we are unable to really power on or power off the
> > backlight.
> 
> This still easily leads to confusing behavior, doesn't it? As there are 
> power-related calls from backlight driver, which won't get handled 

I failed to notice the power thing, I will update the patch to handle it.
Thanks.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh