Re: 2.6.19-rc3: known unfixed regressions (v3)

public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed

* Re: 2.6.19-rc3: known unfixed regressions (v3)
       [not found] <20061029231358.GI27968@stusta.de>
@ 2006-10-30 13:56 ` Michael S. Tsirkin
  2006-10-30 15:27   ` Martin Lorenz
                     ` (2 more replies)
  0 siblings, 3 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-10-30 13:56 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Andrew Morton, len.brown, Linus Torvalds, linux-pm, linux-acpi,
	Jun'ichi Nomura, Martin Lorenz, Linux Kernel Mailing List,
	Adrian Bunk

Quoting r. Adrian Bunk <bunk@stusta.de>:
> Subject    : T60 stops triggering any ACPI events
> References : http://lkml.org/lkml/2006/10/4/425
>              http://lkml.org/lkml/2006/10/16/262
>              http://bugzilla.kernel.org/show_bug.cgi?id=7408
> Submitter  : "Michael S. Tsirkin" <mst@mellanox.co.il>
> Status     : unknown

OK, I spent half a night with git-bisect, and the patch that triggers this issue
seems to be this:

commit d7dd8fd9557840162b724a8ac1366dd78a12dff
Author: Andrew Morton <akpm@osdl.org> 
    [PATCH] blockdev.c: check driver layer errors

Reset to d7dd8fd9557840162b724a8ac1366dd78a12dff seems to hide part of the issue
(I have ACPI after kernel build, but not after suspend/resume).  Both reverting
this patch, and reset to the parent of this patch seem to solve (or at least,
hide) both problems for me (no ACPI after suspend/resume and no ACPI after
kernel build).

I am currently running on 2.6.19-rc3 minus
d7dd8fd9557840162b724a8ac1366dd78a12dff, and in a full day of use I have not
observed any issues yet. 2.6.19-rc3 without reverting
d7dd8fd9557840162b724a8ac1366dd78a12dff stops receiving ACPI events after some
use (sometimes after suspend/resume, sometimes after kernel build stress).  Now,
what does this tell us? Andrew, any idea?


Martin, could you test whether reverting this helps you, too, by chance?
Here's a patch to apply for testing this.

---

commit 658488b7577b7b2242372c43f081f55e2d274615
Author: Michael S. Tsirkin <mst@mellanox.co.il>
Date:   Mon Oct 30 01:28:40 2006 +0200

    Revert "[PATCH] blockdev.c: check driver layer errors"
    
    This reverts commit 4d7dd8fd9557840162b724a8ac1366dd78a12dff.

diff --git a/fs/block_dev.c b/fs/block_dev.c
index bc8f27c..b15ad29 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -545,11 +545,11 @@ static struct kobject *bdev_get_holder(s
 		return kobject_get(bdev->bd_disk->holder_dir);
 }
 
-static int add_symlink(struct kobject *from, struct kobject *to)
+static void add_symlink(struct kobject *from, struct kobject *to)
 {
 	if (!from || !to)
-		return 0;
-	return sysfs_create_link(from, to, kobject_name(to));
+		return;
+	sysfs_create_link(from, to, kobject_name(to));
 }
 
 static void del_symlink(struct kobject *from, struct kobject *to)
@@ -650,38 +650,30 @@ static void free_bd_holder(struct bd_hol
  * If there is no matching entry with @bo in @bdev->bd_holder_list,
  * add @bo to the list, create symlinks.
  *
- * Returns 0 if symlinks are created or already there.
- * Returns -ve if something fails and @bo can be freed.
+ * Returns 1 if @bo was added to the list.
+ * Returns 0 if @bo wasn't used by any reason and should be freed.
  */
 static int add_bd_holder(struct block_device *bdev, struct bd_holder *bo)
 {
 	struct bd_holder *tmp;
-	int ret;
 
 	if (!bo)
-		return -EINVAL;
+		return 0;
 
 	list_for_each_entry(tmp, &bdev->bd_holder_list, list) {
 		if (tmp->sdir == bo->sdir) {
 			tmp->count++;
-			/* We've already done what we need to do here. */
-			free_bd_holder(bo);
 			return 0;
 		}
 	}
 
 	if (!bd_holder_grab_dirs(bdev, bo))
-		return -EBUSY;
+		return 0;
 
-	ret = add_symlink(bo->sdir, bo->sdev);
-	if (ret == 0) {
-		ret = add_symlink(bo->hdir, bo->hdev);
-		if (ret)
-			del_symlink(bo->sdir, bo->sdev);
-	}
-	if (ret == 0)
-		list_add_tail(&bo->list, &bdev->bd_holder_list);
-	return ret;
+	add_symlink(bo->sdir, bo->sdev);
+	add_symlink(bo->hdir, bo->hdev);
+	list_add_tail(&bo->list, &bdev->bd_holder_list);
+	return 1;
 }
 
 /**
@@ -751,9 +743,7 @@ static int bd_claim_by_kobject(struct bl
 
 	mutex_lock_nested(&bdev->bd_mutex, BD_MUTEX_PARTITION);
 	res = bd_claim(bdev, holder);
-	if (res == 0)
-		res = add_bd_holder(bdev, bo);
-	if (res)
+	if (res || !add_bd_holder(bdev, bo))
 		free_bd_holder(bo);
 	mutex_unlock(&bdev->bd_mutex);
 


-- 
MST

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
@ 2006-10-30 15:27   ` Martin Lorenz
  2006-10-30 16:17   ` Jun'ichi Nomura
  2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
  2 siblings, 0 replies; 41+ messages in thread
From: Martin Lorenz @ 2006-10-30 15:27 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Andrew Morton, len.brown, linux-pm, linux-acpi, Linus Torvalds,
	Jun'ichi Nomura, Linux Kernel Mailing List, Adrian Bunk

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

On Mon, Oct 30, 2006 at 03:56:26PM +0200, Michael S. Tsirkin wrote:
> Quoting r. Adrian Bunk <bunk@stusta.de>:
> > Subject    : T60 stops triggering any ACPI events
> > References : http://lkml.org/lkml/2006/10/4/425
> >              http://lkml.org/lkml/2006/10/16/262
> >              http://bugzilla.kernel.org/show_bug.cgi?id=7408
> > Submitter  : "Michael S. Tsirkin" <mst@mellanox.co.il>
> > Status     : unknown
> 
> OK, I spent half a night with git-bisect, and the patch that triggers this issue
> seems to be this:
> 
> commit d7dd8fd9557840162b724a8ac1366dd78a12dff

great!
I was about bisecting myself this weekend but had to let go in favour 
of my daughter...
thank you for that

> I am currently running on 2.6.19-rc3 minus
> d7dd8fd9557840162b724a8ac1366dd78a12dff, and in a full day of use I have not

applied your patch and compiling...

but I can hardly belive something in the block_dev layer can interfere with
ACPI to result in the behavieour we experienced


> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index bc8f27c..b15ad29 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c

and it dosen't change anything for me



gruss
  mlo
--
Dipl.-Ing. Martin Lorenz

            They that can give up essential liberty 
	    to obtain a little temporary safety 
	    deserve neither liberty nor safety.
                                   Benjamin Franklin

please encrypt your mail to me
GnuPG key-ID: F1AAD37D
get it here:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D

ICQ UIN: 33588107

[-- Attachment #2: dmesg.2.6.19-rc3-ts-tp-ie-e1-44.1+1430-g06df5d4f-dirty.boot --]
[-- Type: text/plain, Size: 31340 bytes --]

    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   521952
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   521952
[    0.000000] On node 0 totalpages: 521952
[    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]   HighMem zone: 2285 pages used for memmap
[    0.000000]   HighMem zone: 290291 pages, LIFO batch:31
[    0.000000] DMI present.
[    0.000000] ACPI: RSDP (v002 LENOVO                                ) @ 0x000f6870
[    0.000000] ACPI: XSDT (v001 LENOVO TP-7B    0x00001100  LTP 0x00000000) @ 0x7f6e6526
[    0.000000] ACPI: FADT (v003 LENOVO TP-7B    0x00001100 LNVO 0x00000001) @ 0x7f6e6600
[    0.000000] ACPI: SSDT (v001 LENOVO TP-7B    0x00001100 MSFT 0x0100000e) @ 0x7f6e67b4
[    0.000000] ACPI: ECDT (v001 LENOVO TP-7B    0x00001100 LNVO 0x00000001) @ 0x7f6f2d45
[    0.000000] ACPI: TCPA (v002 LENOVO TP-7B    0x00001100 LNVO 0x00000001) @ 0x7f6f2d97
[    0.000000] ACPI: MADT (v001 LENOVO TP-7B    0x00001100 LNVO 0x00000001) @ 0x7f6f2dc9
[    0.000000] ACPI: MCFG (v001 LENOVO TP-7B    0x00001100 LNVO 0x00000001) @ 0x7f6f2e31
[    0.000000] ACPI: HPET (v001 LENOVO TP-7B    0x00001100 LNVO 0x00000001) @ 0x7f6f2e6f
[    0.000000] ACPI: BOOT (v001 LENOVO TP-7B    0x00001100  LTP 0x00000001) @ 0x7f6f2fd8
[    0.000000] ACPI: SSDT (v001 LENOVO TP-7B    0x00001100 INTL 0x20050513) @ 0x7f6e5ae1
[    0.000000] ACPI: SSDT (v001 LENOVO TP-7B    0x00001100 INTL 0x20050513) @ 0x7f6e5909
[    0.000000] ACPI: DSDT (v001 LENOVO TP-7B    0x00001100 MSFT 0x0100000e) @ 0x00000000
[    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 88000000 (gap: 80000000:70000000)
[    0.000000] Detected 1662.624 MHz processor.
[   10.539368] Built 1 zonelists.  Total pages: 517875
[   10.539373] Kernel command line: root=/dev/sda5 ro resume
[   10.539720] mapped APIC to ffffd000 (fee00000)
[   10.539724] mapped IOAPIC to ffffc000 (fec00000)
[   10.539728] Enabling fast FPU save and restore... done.
[   10.539733] Enabling unmasked SIMD FPU exception support... done.
[   10.539737] Initializing CPU#0
[   10.539818] PID hash table entries: 4096 (order: 12, 16384 bytes)
[   10.541567] Console: colour VGA+ 80x25
[   10.545995] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[   10.546589] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[   10.688172] Memory: 2065788k/2087808k available (1949k kernel code, 20860k reserved, 775k data, 176k init, 1170304k highmem)
[   10.688330] virtual kernel memory layout:
[   10.688332]     fixmap  : 0xfff9d000 - 0xfffff000   ( 392 kB)
[   10.688334]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[   10.688336]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[   10.688339]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   10.688341]       .init : 0xc0400000 - 0xc042c000   ( 176 kB)
[   10.688343]       .data : 0xc02e77a9 - 0xc03a9414   ( 775 kB)
[   10.688346]       .text : 0xc0100000 - 0xc02e77a9   (1949 kB)
[   10.689084] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[   10.689471] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[   10.689749] hpet0: 3 64-bit timers, 14318180 Hz
[   10.690845] Using HPET for base-timer
[   10.750381] Calibrating delay using timer specific routine.. 3328.29 BogoMIPS (lpj=1664148)
[   10.750612] Security Framework v1.0.0 initialized
[   10.750710] Capability LSM initialized
[   10.750819] Mount-cache hash table entries: 512
[   10.751046] CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
[   10.751058] monitor/mwait feature present.
[   10.751150] using mwait in idle threads.
[   10.751243] CPU: L1 I cache: 32K, L1 D cache: 32K
[   10.751392] CPU: L2 cache: 2048K
[   10.751481] CPU: Physical Processor ID: 0
[   10.751571] CPU: Processor Core ID: 0
[   10.751661] CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9 00000000 00000000
[   10.751672] Intel machine check architecture supported.
[   10.751771] Intel machine check reporting enabled on CPU#0.
[   10.751869] Compat vDSO mapped to ffffe000.
[   10.751972] Checking 'hlt' instruction... OK.
[   10.755540] SMP alternatives: switching to UP code
[   10.755838] ACPI: Core revision 20060707
[   10.779647] CPU0: Intel Genuine Intel(R) CPU           L2400  @ 1.66GHz stepping 08
[   10.779925] SMP alternatives: switching to SMP code
[   10.780081] Booting processor 1/1 eip 3000
[   10.791299] Initializing CPU#1
[   10.851566] Calibrating delay using timer specific routine.. 3325.08 BogoMIPS (lpj=1662541)
[   10.851575] CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
[   10.851584] monitor/mwait feature present.
[   10.851589] CPU: L1 I cache: 32K, L1 D cache: 32K
[   10.851593] CPU: L2 cache: 2048K
[   10.851596] CPU: Physical Processor ID: 0
[   10.851599] CPU: Processor Core ID: 1
[   10.851601] CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9 00000000 00000000
[   10.851610] Intel machine check architecture supported.
[   10.851619] Intel machine check reporting enabled on CPU#1.
[   10.851890] CPU1: Intel Genuine Intel(R) CPU           L2400  @ 1.66GHz stepping 08
[   10.853013] Total of 2 processors activated (6653.37 BogoMIPS).
[   10.853317] ENABLING IO-APIC IRQs
[   10.853624] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[   10.965046] checking TSC synchronization across 2 CPUs: 
[    0.000086] CPU#0 had -172 usecs TSC skew, fixed it up.
[    0.000181] CPU#1 had 172 usecs TSC skew, fixed it up.
[    0.000949] Brought up 2 CPUs
[    0.307634] migration_cost=117
[    0.308430] NET: Registered protocol family 16
[    0.308637] ACPI: bus type pci registered
[    0.308735] PCI: Using MMCONFIG
[    0.309658] Setting up standard PCI resources
[    0.328979] ACPI: Interpreter enabled
[    0.329072] ACPI: Using IOAPIC for interrupt routing
[    0.330596] ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 6 7 9 10 11)
[    0.332204] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 9 10 11)
[    0.333820] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11)
[    0.335446] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 7 9 10 11)
[    0.337062] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11)
[    0.338682] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11)
[    0.340286] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11)
[    0.341902] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
[    0.343116] ACPI: PCI Root Bridge [PCI0] (0000:00)
[    0.343214] PCI: Probing PCI hardware (bus 00)
[    0.348387] Boot video device is 0000:00:02.0
[    0.348988] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[    0.349086] PCI quirk: region 1180-11bf claimed by ICH6 GPIO
[    0.349227] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[    0.350564] PCI: Transparent bridge - 0000:00:1e.0
[    0.350806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.358912] ACPI: Power Resource [PUBS] (on)
[    0.361453] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT]
[    0.361772] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
[    0.362089] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
[    0.362477] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
[    0.362853] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
[    0.365662] Linux Plug and Play Support v0.97 (c) Adam Belay
[    0.365766] pnp: PnP ACPI init
[    0.372613] pnp: PnP ACPI: found 12 devices
[    0.372737] intel_rng: FWH not detected
[    0.373008] SCSI subsystem initialized
[    0.373188] PCI: Using ACPI for IRQ routing
[    0.373280] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[    0.374947] PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
[    0.375046] PCI: Bridge: 0000:00:1c.0
[    0.375138]   IO window: 2000-2fff
[    0.375231]   MEM window: ee000000-ee0fffff
[    0.375323]   PREFETCH window: disabled.
[    0.375425] PCI: Bridge: 0000:00:1c.1
[    0.375516]   IO window: 3000-4fff
[    0.375609]   MEM window: ec000000-edffffff
[    0.375702]   PREFETCH window: e4000000-e40fffff
[    0.375798] PCI: Bridge: 0000:00:1c.2
[    0.375891]   IO window: 5000-6fff
[    0.375985]   MEM window: e8000000-e9ffffff
[    0.376080]   PREFETCH window: e4100000-e41fffff
[    0.376175] PCI: Bridge: 0000:00:1c.3
[    0.376267]   IO window: 7000-8fff
[    0.376370]   MEM window: ea000000-ebffffff
[    0.376465]   PREFETCH window: e4200000-e42fffff
[    0.376567] PCI: Bus 22, cardbus bridge: 0000:15:00.0
[    0.376661]   IO window: 00009000-000090ff
[    0.376756]   IO window: 00009400-000094ff
[    0.376852]   PREFETCH window: e0000000-e1ffffff
[    0.376948]   MEM window: e6000000-e7ffffff
[    0.377042] PCI: Bridge: 0000:00:1e.0
[    0.377135]   IO window: 9000-cfff
[    0.377229]   MEM window: e4300000-e7ffffff
[    0.377324]   PREFETCH window: e0000000-e3ffffff
[    0.377449] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 20 (level, low) -> IRQ 16
[    0.377635] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    0.377658] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 21 (level, low) -> IRQ 17
[    0.377843] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    0.377866] ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 22 (level, low) -> IRQ 18
[    0.378050] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[    0.378072] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 23 (level, low) -> IRQ 19
[    0.378257] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    0.378268] PCI: Enabling device 0000:00:1e.0 (0005 -> 0007)
[    0.378374] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[    0.378393] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    0.378579] PCI: Setting latency timer of device 0000:15:00.0 to 64
[    0.378614] NET: Registered protocol family 2
[    0.391378] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.391621] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.394548] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.395357] TCP: Hash tables configured (established 262144 bind 65536)
[    0.395453] TCP reno registered
[    0.395768] Simple Boot Flag at 0x35 set to 0x1
[    0.396509] audit: initializing netlink socket (disabled)
[    0.396620] audit(1162223349.853:1): initialized
[    0.396812] highmem bounce pool size: 64 pages
[    0.397170] io scheduler noop registered
[    0.397313] io scheduler anticipatory registered
[    0.397454] io scheduler deadline registered
[    0.397607] io scheduler cfq registered (default)
[    0.398102] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    0.398156] assign_interrupt_mode Found MSI capability
[    0.398309] Allocate Port Service[0000:00:1c.0:pcie00]
[    0.398370] Allocate Port Service[0000:00:1c.0:pcie02]
[    0.398428] Allocate Port Service[0000:00:1c.0:pcie03]
[    0.398548] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    0.398601] assign_interrupt_mode Found MSI capability
[    0.399564] Allocate Port Service[0000:00:1c.1:pcie00]
[    0.399614] Allocate Port Service[0000:00:1c.1:pcie02]
[    0.399661] Allocate Port Service[0000:00:1c.1:pcie03]
[    0.399775] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[    0.399828] assign_interrupt_mode Found MSI capability
[    0.399962] Allocate Port Service[0000:00:1c.2:pcie00]
[    0.400009] Allocate Port Service[0000:00:1c.2:pcie02]
[    0.400061] Allocate Port Service[0000:00:1c.2:pcie03]
[    0.400175] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    0.400228] assign_interrupt_mode Found MSI capability
[    0.400368] Allocate Port Service[0000:00:1c.3:pcie00]
[    0.400418] Allocate Port Service[0000:00:1c.3:pcie02]
[    0.400465] Allocate Port Service[0000:00:1c.3:pcie03]
[    0.433651] Real Time Clock Driver v1.12ac
[    0.433809] hpet_resources: 0xfed00000 is busy
[    0.433837] Linux agpgart interface v0.101 (c) Dave Jones
[    0.433975] agpgart: Detected an Intel 945GM Chipset.
[    0.435945] agpgart: Detected 7932K stolen memory.
[    0.453538] agpgart: AGP aperture is 256M @ 0xd0000000
[    0.453679] [drm] Initialized drm 1.0.1 20051102
[    0.454166] loop: loaded (max 8 devices)
[    0.454264] Intel(R) PRO/1000 Network Driver - version 7.2.9-k2-NAPI
[    0.454358] Copyright (c) 1999-2006 Intel Corporation.
[    0.454526] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    0.454719] PCI: Setting latency timer of device 0000:02:00.0 to 64
[    0.460267] e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:32-bit) 00:16:d3:22:9b:82
[    0.505134] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[    0.505373] netconsole: not configured, aborting
[    0.505579] libata version 2.00 loaded.
[    0.505629] ahci 0000:00:1f.2: version 2.0
[    0.505647] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
[    1.507573] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[    1.507583] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x1 impl SATA mode
[    1.507722] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
[    1.507910] ata1: SATA max UDMA/133 cmd 0xF8824500 ctl 0x0 bmdma 0x0 irq 219
[    1.508079] ata2: SATA max UDMA/133 cmd 0xF8824580 ctl 0x0 bmdma 0x0 irq 219
[    1.508251] ata3: SATA max UDMA/133 cmd 0xF8824600 ctl 0x0 bmdma 0x0 irq 219
[    1.508419] ata4: SATA max UDMA/133 cmd 0xF8824680 ctl 0x0 bmdma 0x0 irq 219
[    1.508524] scsi0 : ahci
[    1.966832] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.967289] ata1.00: ATA-7, max UDMA/100, 156301488 sectors: LBA48 NCQ (depth 31/32)
[    1.967424] ata1.00: ata1: dev 0 multi count 16
[    1.969850] ata1.00: configured for UDMA/100
[    1.969952] scsi1 : ahci
[    2.273333] ata2: SATA link down (SStatus 0 SControl 0)
[    2.273440] scsi2 : ahci
[    2.576850] ata3: SATA link down (SStatus 0 SControl 0)
[    2.576953] scsi3 : ahci
[    2.880368] ata4: SATA link down (SStatus 0 SControl 0)
[    2.880597] scsi 0:0:0:0: Direct-Access     ATA      FUJITSU MHV2080B 0084 PQ: 0 ANSI: 5
[    2.880870] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    2.880982] sda: Write Protect is off
[    2.881073] sda: Mode Sense: 00 3a 00 00
[    2.881099] SCSI device sda: drive cache: write back
[    2.881251] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    2.881362] sda: Write Protect is off
[    2.881453] sda: Mode Sense: 00 3a 00 00
[    2.881478] SCSI device sda: drive cache: write back
[    2.881575]  sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 >
[    3.052953] sd 0:0:0:0: Attached scsi disk sda
[    3.053295] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[    3.064269] serio: i8042 KBD port at 0x60,0x64 irq 1
[    3.064367] serio: i8042 AUX port at 0x60,0x64 irq 12
[    3.064626] mice: PS/2 mouse device common for all mice
[    3.064722] i2c /dev entries driver
[    3.064957] ACPI: PCI Interrupt 0000:00:1f.3[A] -> GSI 23 (level, low) -> IRQ 19
[    3.065268] hdaps: LENOVO ThinkPad X60 detected, inverting axes
[    3.069987] input: AT Translated Set 2 keyboard as /class/input/input0
[    3.076297] hdaps: initial mode latch is 0x05
[    3.076468] hdaps: setting ec_rate=250, filter_order=2
[    3.076509] hdaps: fake_data_mode set to 0
[    3.076732] hdaps: device successfully initialized.
[    3.076906] input: hdaps as /class/input/input1
[    3.076999] hdaps: driver successfully loaded.
[    3.077093] EDAC MC: Ver: 2.0.1 Oct 30 2006
[    3.077714] thinkpad_ec: thinkpad_ec 0.30 loaded.
[    3.077956] TCP bic registered
[    3.078057] NET: Registered protocol family 1
[    3.078153] NET: Registered protocol family 17
[    3.078263] Starting balanced_irq
[    3.078359] Using IPI No-Shortcut mode
[    3.078884] ACPI: (supports S0 S3 S4 S5)
[    3.079246] Time: tsc clocksource has been installed.
[    3.079386] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
[    3.082224] VFS: Mounted root (ext2 filesystem) readonly.
[    3.082457] Freeing unused kernel memory: 176k freed
[    6.179063] ieee1394: Initialized config rom entry `ip1394'
[    6.181760] ACPI: PCI Interrupt 0000:15:00.1[B] -> GSI 17 (level, low) -> IRQ 21
[    6.181958] PCI: Setting latency timer of device 0000:15:00.1 to 64
[    6.235209] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[21]  MMIO=[e4301000-e43017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
[    6.349287] input: PC Speaker as /class/input/input2
[    6.712159] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[    6.712263] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[    6.908445] usbcore: registered new interface driver usbfs
[    6.908579] usbcore: registered new interface driver hub
[    6.908711] usbcore: registered new device driver usb
[    7.089196] irda_init()
[    7.089213] NET: Registered protocol family 23
[    7.146382] USB Universal Host Controller Interface driver v3.0
[    7.146545] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
[    7.146745] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[    7.146751] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    7.147058] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[    7.147234] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001820
[    7.147488] usb usb1: configuration #1 chosen from 1 choice
[    7.147628] hub 1-0:1.0: USB hub found
[    7.147726] hub 1-0:1.0: 2 ports detected
[    7.198161] sdhci: Secure Digital Host Controller Interface driver, 0.12
[    7.198263] sdhci: Copyright(c) Pierre Ossman
[    7.248594] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 21
[    7.248798] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[    7.248804] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    7.248942] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[    7.249108] uhci_hcd 0000:00:1d.1: irq 21, io base 0x00001840
[    7.249338] usb usb2: configuration #1 chosen from 1 choice
[    7.249818] hub 2-0:1.0: USB hub found
[    7.249917] hub 2-0:1.0: 2 ports detected
[    7.351432] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 22
[    7.351634] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[    7.351640] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.351771] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[    7.351940] uhci_hcd 0000:00:1d.2: irq 22, io base 0x00001860
[    7.352165] usb usb3: configuration #1 chosen from 1 choice
[    7.352305] hub 3-0:1.0: USB hub found
[    7.352401] hub 3-0:1.0: 2 ports detected
[    7.453217] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 23
[    7.453403] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[    7.453408] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[    7.453537] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[    7.453701] uhci_hcd 0000:00:1d.3: irq 23, io base 0x00001880
[    7.453921] usb usb4: configuration #1 chosen from 1 choice
[    7.454051] hub 4-0:1.0: USB hub found
[    7.454150] hub 4-0:1.0: 2 ports detected
[    7.499170] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000ae40600192017]
[    7.555770] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 23
[    7.555969] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[    7.555975] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    7.556109] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[    7.556283] ehci_hcd 0000:00:1d.7: debug port 1
[    7.556384] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[    7.556395] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xee444000
[    7.560381] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    7.560837] usb usb5: configuration #1 chosen from 1 choice
[    7.560967] hub 5-0:1.0: USB hub found
[    7.561064] hub 5-0:1.0: 8 ports detected
[    7.563438] eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
[    7.637032] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[    7.657935] input: TPPS/2 IBM TrackPoint as /class/input/input3
[    7.661955] Yenta: CardBus bridge found at 0000:15:00.0 [17aa:201c]
[    7.663374] pnp: Device 00:0a activated.
[    7.663471] nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 7 ; dma 1.
[    7.663500] nsc-ircc, chip->init
[    7.663605] nsc-ircc, Found chip at base=0x164e
[    7.663738] nsc-ircc, driver loaded (Dag Brattli)
[    7.663925] IrDA: Registered device irda0
[    7.664080] nsc-ircc, Found dongle: No dongle connected
[    7.664183] nsc_ircc_init_dongle_interface(), No dongle connected
[    7.785417] Yenta: ISA IRQ mask 0x0c38, PCI irq 20
[    7.785519] Socket status: 30000006
[    7.785615] pcmcia: parent PCI bridge I/O window: 0x9000 - 0xcfff
[    7.785713] pcmcia: parent PCI bridge Memory window: 0xe4300000 - 0xe7ffffff
[    7.785812] pcmcia: parent PCI bridge Memory window: 0xe0000000 - 0xe3ffffff
[    7.786199] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
[    7.786450] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[    8.303763] usb 4-1: new full speed USB device using uhci_hcd and address 2
[    8.465387] usb 4-1: configuration #1 chosen from 1 choice
[    8.550092] Bluetooth: Core ver 2.11
[    8.550695] NET: Registered protocol family 31
[    8.550795] Bluetooth: HCI device and connection manager initialized
[    8.550892] Bluetooth: HCI socket layer initialized
[    8.559175] Bluetooth: HCI USB driver ver 2.9
[    8.677160] usb 4-2: new full speed USB device using uhci_hcd and address 3
[    8.833905] hda_intel: No response from codec, disabling MSI...
[    8.842826] usb 4-2: configuration #1 chosen from 1 choice
[    8.847946] usbcore: registered new interface driver hci_usb
[    9.833318] hda_intel: azx_get_response timeout, switching to polling mode...
[   10.832730] hda_intel: azx_get_response timeout, switching to single_cmd mode...
[   21.618159] sdhci: SDHCI controller found at 0000:15:00.2 [1180:0822] (rev 18)
[   21.619154] ACPI: PCI Interrupt 0000:15:00.2[C] -> GSI 18 (level, low) -> IRQ 22
[   21.620362] PCI: Setting latency timer of device 0000:15:00.2 to 64
[   21.622574] mmc0: SDHCI at 0xe4301800 irq 22 DMA
[   22.346566] Adding 1951856k swap on /dev/sda12.  Priority:-1 extents:1 across:1951856k
[   22.347780] Adding 2931820k swap on /dev/sda13.  Priority:-2 extents:1 across:2931820k
[   22.692872] Non-volatile memory driver v1.2
[   22.731265] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
[   22.731365] ieee1394: sbp2: Try serialize_io=0 for better performance
[   22.764737] ibm_acpi: IBM ThinkPad ACPI Extras v0.12a
[   22.764844] ibm_acpi: http://ibm-acpi.sf.net/
[   22.785014] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Ist] [20060707]
[   22.785828] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Cst] [20060707]
[   22.787166] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[   22.787446] ACPI: Processor [CPU0] (supports 8 throttling states)
[   22.788615] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Ist] [20060707]
[   22.789318] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Cst] [20060707]
[   22.790705] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[   22.790991] ACPI: Processor [CPU1] (supports 8 throttling states)
[   23.002000] Time: hpet clocksource has been installed.
[   23.019000] mmcblk0: mmc0:b368 SD    249856KiB 
[   23.019000]  mmcblk0: p1
[   38.427000] ReiserFS: sda14: found reiserfs format "3.6" with standard journal
[   38.427000] ReiserFS: sda14: warning: CONFIG_REISERFS_CHECK is set ON
[   38.427000] ReiserFS: sda14: warning: - it is slow mode for debugging.
[   38.427000] ReiserFS: sda14: using ordered data mode
[   38.450000] ReiserFS: sda14: journal params: device sda14, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.451000] ReiserFS: sda14: checking transaction log (sda14)
[   38.451000] ReiserFS: sda14: journal-1153: found in header: first_unflushed_offset 7418, last_flushed_trans_id 30277
[   38.453000] ReiserFS: sda14: journal-1206: Starting replay from offset 130043019795706, trans_id 3223281428
[   38.453000] ReiserFS: sda14: journal-1299: Setting newest_mount_id to 176
[   38.495000] ReiserFS: sda14: Using r5 hash to sort names
[   38.558000] ReiserFS: sda8: found reiserfs format "3.6" with standard journal
[   38.558000] ReiserFS: sda8: warning: CONFIG_REISERFS_CHECK is set ON
[   38.558000] ReiserFS: sda8: warning: - it is slow mode for debugging.
[   38.558000] ReiserFS: sda8: using ordered data mode
[   38.565000] ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.566000] ReiserFS: sda8: checking transaction log (sda8)
[   38.566000] ReiserFS: sda8: journal-1153: found in header: first_unflushed_offset 6697, last_flushed_trans_id 571523
[   38.574000] ReiserFS: sda8: journal-1206: Starting replay from offset 2454676888885801, trans_id 3223281428
[   38.574000] ReiserFS: sda8: journal-1299: Setting newest_mount_id to 176
[   38.617000] ReiserFS: sda8: Using r5 hash to sort names
[   38.687000] ReiserFS: sda11: found reiserfs format "3.6" with standard journal
[   38.688000] ReiserFS: sda11: warning: CONFIG_REISERFS_CHECK is set ON
[   38.688000] ReiserFS: sda11: warning: - it is slow mode for debugging.
[   38.688000] ReiserFS: sda11: using ordered data mode
[   38.715000] ReiserFS: sda11: journal params: device sda11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.716000] ReiserFS: sda11: checking transaction log (sda11)
[   38.716000] ReiserFS: sda11: journal-1153: found in header: first_unflushed_offset 5253, last_flushed_trans_id 20436
[   38.749000] ReiserFS: sda11: journal-1206: Starting replay from offset 87776246633605, trans_id 3223281428
[   38.749000] ReiserFS: sda11: journal-1299: Setting newest_mount_id to 176
[   38.771000] ReiserFS: sda11: Using r5 hash to sort names
[   38.798000] ReiserFS: sda10: found reiserfs format "3.6" with standard journal
[   38.799000] ReiserFS: sda10: warning: CONFIG_REISERFS_CHECK is set ON
[   38.799000] ReiserFS: sda10: warning: - it is slow mode for debugging.
[   38.799000] ReiserFS: sda10: using ordered data mode
[   38.809000] ReiserFS: sda10: journal params: device sda10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.809000] ReiserFS: sda10: checking transaction log (sda10)
[   38.810000] ReiserFS: sda10: journal-1153: found in header: first_unflushed_offset 3806, last_flushed_trans_id 20392
[   38.820000] ReiserFS: sda10: journal-1206: Starting replay from offset 87587268071134, trans_id 3223281428
[   38.820000] ReiserFS: sda10: journal-1299: Setting newest_mount_id to 176
[   38.831000] ReiserFS: sda10: Using r5 hash to sort names
[   38.848000] ReiserFS: sda9: found reiserfs format "3.6" with standard journal
[   38.848000] ReiserFS: sda9: warning: CONFIG_REISERFS_CHECK is set ON
[   38.848000] ReiserFS: sda9: warning: - it is slow mode for debugging.
[   38.849000] ReiserFS: sda9: using ordered data mode
[   38.855000] ReiserFS: sda9: journal params: device sda9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.856000] ReiserFS: sda9: checking transaction log (sda9)
[   38.856000] ReiserFS: sda9: journal-1153: found in header: first_unflushed_offset 6872, last_flushed_trans_id 96225
[   38.859000] ReiserFS: sda9: journal-1206: Starting replay from offset 413287523031768, trans_id 4155609112
[   38.859000] ReiserFS: sda9: journal-1299: Setting newest_mount_id to 176
[   38.871000] ReiserFS: sda9: Using r5 hash to sort names
[   38.898000] ReiserFS: sda7: found reiserfs format "3.6" with standard journal
[   38.898000] ReiserFS: sda7: warning: CONFIG_REISERFS_CHECK is set ON
[   38.899000] ReiserFS: sda7: warning: - it is slow mode for debugging.
[   38.899000] ReiserFS: sda7: using ordered data mode
[   38.903000] ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.903000] ReiserFS: sda7: checking transaction log (sda7)
[   38.904000] ReiserFS: sda7: journal-1153: found in header: first_unflushed_offset 5590, last_flushed_trans_id 581233
[   38.909000] ReiserFS: sda7: journal-1206: Starting replay from offset 2496381021328854, trans_id 24000000
[   38.910000] ReiserFS: sda7: journal-1299: Setting newest_mount_id to 176
[   38.953000] ReiserFS: sda7: Using r5 hash to sort names
[   39.014000] ReiserFS: sda6: found reiserfs format "3.6" with standard journal
[   39.015000] ReiserFS: sda6: warning: CONFIG_REISERFS_CHECK is set ON
[   39.015000] ReiserFS: sda6: warning: - it is slow mode for debugging.
[   39.015000] ReiserFS: sda6: using ordered data mode
[   39.052000] ReiserFS: sda6: journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   39.052000] ReiserFS: sda6: checking transaction log (sda6)
[   39.052000] ReiserFS: sda6: journal-1153: found in header: first_unflushed_offset 2919, last_flushed_trans_id 787426
[   39.078000] ReiserFS: sda6: journal-1206: Starting replay from offset 3381973212990311, trans_id 30000000
[   39.078000] ReiserFS: sda6: journal-1299: Setting newest_mount_id to 176
[   39.167000] ReiserFS: sda6: Using r5 hash to sort names
[   39.284000] kjournald starting.  Commit interval 5 seconds
[   39.284000] EXT3 FS on mmcblk0p1, internal journal
[   39.284000] EXT3-fs: mounted filesystem with ordered data mode.

[-- Attachment #3: dmesg.2.6.19-rc3-ts-tp-ie-e1-44.1+1430-g06df5d4f-dirty.run --]
[-- Type: text/plain, Size: 31340 bytes --]

 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 88000000 (gap: 80000000:70000000)
[    0.000000] Detected 1662.624 MHz processor.
[   10.539368] Built 1 zonelists.  Total pages: 517875
[   10.539373] Kernel command line: root=/dev/sda5 ro resume
[   10.539720] mapped APIC to ffffd000 (fee00000)
[   10.539724] mapped IOAPIC to ffffc000 (fec00000)
[   10.539728] Enabling fast FPU save and restore... done.
[   10.539733] Enabling unmasked SIMD FPU exception support... done.
[   10.539737] Initializing CPU#0
[   10.539818] PID hash table entries: 4096 (order: 12, 16384 bytes)
[   10.541567] Console: colour VGA+ 80x25
[   10.545995] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[   10.546589] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[   10.688172] Memory: 2065788k/2087808k available (1949k kernel code, 20860k reserved, 775k data, 176k init, 1170304k highmem)
[   10.688330] virtual kernel memory layout:
[   10.688332]     fixmap  : 0xfff9d000 - 0xfffff000   ( 392 kB)
[   10.688334]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[   10.688336]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[   10.688339]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   10.688341]       .init : 0xc0400000 - 0xc042c000   ( 176 kB)
[   10.688343]       .data : 0xc02e77a9 - 0xc03a9414   ( 775 kB)
[   10.688346]       .text : 0xc0100000 - 0xc02e77a9   (1949 kB)
[   10.689084] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[   10.689471] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[   10.689749] hpet0: 3 64-bit timers, 14318180 Hz
[   10.690845] Using HPET for base-timer
[   10.750381] Calibrating delay using timer specific routine.. 3328.29 BogoMIPS (lpj=1664148)
[   10.750612] Security Framework v1.0.0 initialized
[   10.750710] Capability LSM initialized
[   10.750819] Mount-cache hash table entries: 512
[   10.751046] CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
[   10.751058] monitor/mwait feature present.
[   10.751150] using mwait in idle threads.
[   10.751243] CPU: L1 I cache: 32K, L1 D cache: 32K
[   10.751392] CPU: L2 cache: 2048K
[   10.751481] CPU: Physical Processor ID: 0
[   10.751571] CPU: Processor Core ID: 0
[   10.751661] CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9 00000000 00000000
[   10.751672] Intel machine check architecture supported.
[   10.751771] Intel machine check reporting enabled on CPU#0.
[   10.751869] Compat vDSO mapped to ffffe000.
[   10.751972] Checking 'hlt' instruction... OK.
[   10.755540] SMP alternatives: switching to UP code
[   10.755838] ACPI: Core revision 20060707
[   10.779647] CPU0: Intel Genuine Intel(R) CPU           L2400  @ 1.66GHz stepping 08
[   10.779925] SMP alternatives: switching to SMP code
[   10.780081] Booting processor 1/1 eip 3000
[   10.791299] Initializing CPU#1
[   10.851566] Calibrating delay using timer specific routine.. 3325.08 BogoMIPS (lpj=1662541)
[   10.851575] CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
[   10.851584] monitor/mwait feature present.
[   10.851589] CPU: L1 I cache: 32K, L1 D cache: 32K
[   10.851593] CPU: L2 cache: 2048K
[   10.851596] CPU: Physical Processor ID: 0
[   10.851599] CPU: Processor Core ID: 1
[   10.851601] CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9 00000000 00000000
[   10.851610] Intel machine check architecture supported.
[   10.851619] Intel machine check reporting enabled on CPU#1.
[   10.851890] CPU1: Intel Genuine Intel(R) CPU           L2400  @ 1.66GHz stepping 08
[   10.853013] Total of 2 processors activated (6653.37 BogoMIPS).
[   10.853317] ENABLING IO-APIC IRQs
[   10.853624] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[   10.965046] checking TSC synchronization across 2 CPUs: 
[    0.000086] CPU#0 had -172 usecs TSC skew, fixed it up.
[    0.000181] CPU#1 had 172 usecs TSC skew, fixed it up.
[    0.000949] Brought up 2 CPUs
[    0.307634] migration_cost=117
[    0.308430] NET: Registered protocol family 16
[    0.308637] ACPI: bus type pci registered
[    0.308735] PCI: Using MMCONFIG
[    0.309658] Setting up standard PCI resources
[    0.328979] ACPI: Interpreter enabled
[    0.329072] ACPI: Using IOAPIC for interrupt routing
[    0.330596] ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 6 7 9 10 11)
[    0.332204] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 *4 5 6 7 9 10 11)
[    0.333820] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11)
[    0.335446] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 7 9 10 11)
[    0.337062] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11)
[    0.338682] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11)
[    0.340286] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11)
[    0.341902] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
[    0.343116] ACPI: PCI Root Bridge [PCI0] (0000:00)
[    0.343214] PCI: Probing PCI hardware (bus 00)
[    0.348387] Boot video device is 0000:00:02.0
[    0.348988] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[    0.349086] PCI quirk: region 1180-11bf claimed by ICH6 GPIO
[    0.349227] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[    0.350564] PCI: Transparent bridge - 0000:00:1e.0
[    0.350806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.358912] ACPI: Power Resource [PUBS] (on)
[    0.361453] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT]
[    0.361772] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
[    0.362089] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
[    0.362477] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT]
[    0.362853] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
[    0.365662] Linux Plug and Play Support v0.97 (c) Adam Belay
[    0.365766] pnp: PnP ACPI init
[    0.372613] pnp: PnP ACPI: found 12 devices
[    0.372737] intel_rng: FWH not detected
[    0.373008] SCSI subsystem initialized
[    0.373188] PCI: Using ACPI for IRQ routing
[    0.373280] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[    0.374947] PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
[    0.375046] PCI: Bridge: 0000:00:1c.0
[    0.375138]   IO window: 2000-2fff
[    0.375231]   MEM window: ee000000-ee0fffff
[    0.375323]   PREFETCH window: disabled.
[    0.375425] PCI: Bridge: 0000:00:1c.1
[    0.375516]   IO window: 3000-4fff
[    0.375609]   MEM window: ec000000-edffffff
[    0.375702]   PREFETCH window: e4000000-e40fffff
[    0.375798] PCI: Bridge: 0000:00:1c.2
[    0.375891]   IO window: 5000-6fff
[    0.375985]   MEM window: e8000000-e9ffffff
[    0.376080]   PREFETCH window: e4100000-e41fffff
[    0.376175] PCI: Bridge: 0000:00:1c.3
[    0.376267]   IO window: 7000-8fff
[    0.376370]   MEM window: ea000000-ebffffff
[    0.376465]   PREFETCH window: e4200000-e42fffff
[    0.376567] PCI: Bus 22, cardbus bridge: 0000:15:00.0
[    0.376661]   IO window: 00009000-000090ff
[    0.376756]   IO window: 00009400-000094ff
[    0.376852]   PREFETCH window: e0000000-e1ffffff
[    0.376948]   MEM window: e6000000-e7ffffff
[    0.377042] PCI: Bridge: 0000:00:1e.0
[    0.377135]   IO window: 9000-cfff
[    0.377229]   MEM window: e4300000-e7ffffff
[    0.377324]   PREFETCH window: e0000000-e3ffffff
[    0.377449] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 20 (level, low) -> IRQ 16
[    0.377635] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    0.377658] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 21 (level, low) -> IRQ 17
[    0.377843] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    0.377866] ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 22 (level, low) -> IRQ 18
[    0.378050] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[    0.378072] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 23 (level, low) -> IRQ 19
[    0.378257] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    0.378268] PCI: Enabling device 0000:00:1e.0 (0005 -> 0007)
[    0.378374] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[    0.378393] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    0.378579] PCI: Setting latency timer of device 0000:15:00.0 to 64
[    0.378614] NET: Registered protocol family 2
[    0.391378] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.391621] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.394548] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.395357] TCP: Hash tables configured (established 262144 bind 65536)
[    0.395453] TCP reno registered
[    0.395768] Simple Boot Flag at 0x35 set to 0x1
[    0.396509] audit: initializing netlink socket (disabled)
[    0.396620] audit(1162223349.853:1): initialized
[    0.396812] highmem bounce pool size: 64 pages
[    0.397170] io scheduler noop registered
[    0.397313] io scheduler anticipatory registered
[    0.397454] io scheduler deadline registered
[    0.397607] io scheduler cfq registered (default)
[    0.398102] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    0.398156] assign_interrupt_mode Found MSI capability
[    0.398309] Allocate Port Service[0000:00:1c.0:pcie00]
[    0.398370] Allocate Port Service[0000:00:1c.0:pcie02]
[    0.398428] Allocate Port Service[0000:00:1c.0:pcie03]
[    0.398548] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    0.398601] assign_interrupt_mode Found MSI capability
[    0.399564] Allocate Port Service[0000:00:1c.1:pcie00]
[    0.399614] Allocate Port Service[0000:00:1c.1:pcie02]
[    0.399661] Allocate Port Service[0000:00:1c.1:pcie03]
[    0.399775] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[    0.399828] assign_interrupt_mode Found MSI capability
[    0.399962] Allocate Port Service[0000:00:1c.2:pcie00]
[    0.400009] Allocate Port Service[0000:00:1c.2:pcie02]
[    0.400061] Allocate Port Service[0000:00:1c.2:pcie03]
[    0.400175] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    0.400228] assign_interrupt_mode Found MSI capability
[    0.400368] Allocate Port Service[0000:00:1c.3:pcie00]
[    0.400418] Allocate Port Service[0000:00:1c.3:pcie02]
[    0.400465] Allocate Port Service[0000:00:1c.3:pcie03]
[    0.433651] Real Time Clock Driver v1.12ac
[    0.433809] hpet_resources: 0xfed00000 is busy
[    0.433837] Linux agpgart interface v0.101 (c) Dave Jones
[    0.433975] agpgart: Detected an Intel 945GM Chipset.
[    0.435945] agpgart: Detected 7932K stolen memory.
[    0.453538] agpgart: AGP aperture is 256M @ 0xd0000000
[    0.453679] [drm] Initialized drm 1.0.1 20051102
[    0.454166] loop: loaded (max 8 devices)
[    0.454264] Intel(R) PRO/1000 Network Driver - version 7.2.9-k2-NAPI
[    0.454358] Copyright (c) 1999-2006 Intel Corporation.
[    0.454526] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    0.454719] PCI: Setting latency timer of device 0000:02:00.0 to 64
[    0.460267] e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:32-bit) 00:16:d3:22:9b:82
[    0.505134] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[    0.505373] netconsole: not configured, aborting
[    0.505579] libata version 2.00 loaded.
[    0.505629] ahci 0000:00:1f.2: version 2.0
[    0.505647] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
[    1.507573] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[    1.507583] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x1 impl SATA mode
[    1.507722] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
[    1.507910] ata1: SATA max UDMA/133 cmd 0xF8824500 ctl 0x0 bmdma 0x0 irq 219
[    1.508079] ata2: SATA max UDMA/133 cmd 0xF8824580 ctl 0x0 bmdma 0x0 irq 219
[    1.508251] ata3: SATA max UDMA/133 cmd 0xF8824600 ctl 0x0 bmdma 0x0 irq 219
[    1.508419] ata4: SATA max UDMA/133 cmd 0xF8824680 ctl 0x0 bmdma 0x0 irq 219
[    1.508524] scsi0 : ahci
[    1.966832] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.967289] ata1.00: ATA-7, max UDMA/100, 156301488 sectors: LBA48 NCQ (depth 31/32)
[    1.967424] ata1.00: ata1: dev 0 multi count 16
[    1.969850] ata1.00: configured for UDMA/100
[    1.969952] scsi1 : ahci
[    2.273333] ata2: SATA link down (SStatus 0 SControl 0)
[    2.273440] scsi2 : ahci
[    2.576850] ata3: SATA link down (SStatus 0 SControl 0)
[    2.576953] scsi3 : ahci
[    2.880368] ata4: SATA link down (SStatus 0 SControl 0)
[    2.880597] scsi 0:0:0:0: Direct-Access     ATA      FUJITSU MHV2080B 0084 PQ: 0 ANSI: 5
[    2.880870] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    2.880982] sda: Write Protect is off
[    2.881073] sda: Mode Sense: 00 3a 00 00
[    2.881099] SCSI device sda: drive cache: write back
[    2.881251] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    2.881362] sda: Write Protect is off
[    2.881453] sda: Mode Sense: 00 3a 00 00
[    2.881478] SCSI device sda: drive cache: write back
[    2.881575]  sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 >
[    3.052953] sd 0:0:0:0: Attached scsi disk sda
[    3.053295] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[    3.064269] serio: i8042 KBD port at 0x60,0x64 irq 1
[    3.064367] serio: i8042 AUX port at 0x60,0x64 irq 12
[    3.064626] mice: PS/2 mouse device common for all mice
[    3.064722] i2c /dev entries driver
[    3.064957] ACPI: PCI Interrupt 0000:00:1f.3[A] -> GSI 23 (level, low) -> IRQ 19
[    3.065268] hdaps: LENOVO ThinkPad X60 detected, inverting axes
[    3.069987] input: AT Translated Set 2 keyboard as /class/input/input0
[    3.076297] hdaps: initial mode latch is 0x05
[    3.076468] hdaps: setting ec_rate=250, filter_order=2
[    3.076509] hdaps: fake_data_mode set to 0
[    3.076732] hdaps: device successfully initialized.
[    3.076906] input: hdaps as /class/input/input1
[    3.076999] hdaps: driver successfully loaded.
[    3.077093] EDAC MC: Ver: 2.0.1 Oct 30 2006
[    3.077714] thinkpad_ec: thinkpad_ec 0.30 loaded.
[    3.077956] TCP bic registered
[    3.078057] NET: Registered protocol family 1
[    3.078153] NET: Registered protocol family 17
[    3.078263] Starting balanced_irq
[    3.078359] Using IPI No-Shortcut mode
[    3.078884] ACPI: (supports S0 S3 S4 S5)
[    3.079246] Time: tsc clocksource has been installed.
[    3.079386] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
[    3.082224] VFS: Mounted root (ext2 filesystem) readonly.
[    3.082457] Freeing unused kernel memory: 176k freed
[    6.179063] ieee1394: Initialized config rom entry `ip1394'
[    6.181760] ACPI: PCI Interrupt 0000:15:00.1[B] -> GSI 17 (level, low) -> IRQ 21
[    6.181958] PCI: Setting latency timer of device 0000:15:00.1 to 64
[    6.235209] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[21]  MMIO=[e4301000-e43017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
[    6.349287] input: PC Speaker as /class/input/input2
[    6.712159] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[    6.712263] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[    6.908445] usbcore: registered new interface driver usbfs
[    6.908579] usbcore: registered new interface driver hub
[    6.908711] usbcore: registered new device driver usb
[    7.089196] irda_init()
[    7.089213] NET: Registered protocol family 23
[    7.146382] USB Universal Host Controller Interface driver v3.0
[    7.146545] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
[    7.146745] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[    7.146751] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    7.147058] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[    7.147234] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001820
[    7.147488] usb usb1: configuration #1 chosen from 1 choice
[    7.147628] hub 1-0:1.0: USB hub found
[    7.147726] hub 1-0:1.0: 2 ports detected
[    7.198161] sdhci: Secure Digital Host Controller Interface driver, 0.12
[    7.198263] sdhci: Copyright(c) Pierre Ossman
[    7.248594] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 21
[    7.248798] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[    7.248804] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    7.248942] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[    7.249108] uhci_hcd 0000:00:1d.1: irq 21, io base 0x00001840
[    7.249338] usb usb2: configuration #1 chosen from 1 choice
[    7.249818] hub 2-0:1.0: USB hub found
[    7.249917] hub 2-0:1.0: 2 ports detected
[    7.351432] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 22
[    7.351634] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[    7.351640] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.351771] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[    7.351940] uhci_hcd 0000:00:1d.2: irq 22, io base 0x00001860
[    7.352165] usb usb3: configuration #1 chosen from 1 choice
[    7.352305] hub 3-0:1.0: USB hub found
[    7.352401] hub 3-0:1.0: 2 ports detected
[    7.453217] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 23
[    7.453403] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[    7.453408] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[    7.453537] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[    7.453701] uhci_hcd 0000:00:1d.3: irq 23, io base 0x00001880
[    7.453921] usb usb4: configuration #1 chosen from 1 choice
[    7.454051] hub 4-0:1.0: USB hub found
[    7.454150] hub 4-0:1.0: 2 ports detected
[    7.499170] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000ae40600192017]
[    7.555770] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 23
[    7.555969] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[    7.555975] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    7.556109] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[    7.556283] ehci_hcd 0000:00:1d.7: debug port 1
[    7.556384] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[    7.556395] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xee444000
[    7.560381] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    7.560837] usb usb5: configuration #1 chosen from 1 choice
[    7.560967] hub 5-0:1.0: USB hub found
[    7.561064] hub 5-0:1.0: 8 ports detected
[    7.563438] eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
[    7.637032] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[    7.657935] input: TPPS/2 IBM TrackPoint as /class/input/input3
[    7.661955] Yenta: CardBus bridge found at 0000:15:00.0 [17aa:201c]
[    7.663374] pnp: Device 00:0a activated.
[    7.663471] nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 7 ; dma 1.
[    7.663500] nsc-ircc, chip->init
[    7.663605] nsc-ircc, Found chip at base=0x164e
[    7.663738] nsc-ircc, driver loaded (Dag Brattli)
[    7.663925] IrDA: Registered device irda0
[    7.664080] nsc-ircc, Found dongle: No dongle connected
[    7.664183] nsc_ircc_init_dongle_interface(), No dongle connected
[    7.785417] Yenta: ISA IRQ mask 0x0c38, PCI irq 20
[    7.785519] Socket status: 30000006
[    7.785615] pcmcia: parent PCI bridge I/O window: 0x9000 - 0xcfff
[    7.785713] pcmcia: parent PCI bridge Memory window: 0xe4300000 - 0xe7ffffff
[    7.785812] pcmcia: parent PCI bridge Memory window: 0xe0000000 - 0xe3ffffff
[    7.786199] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
[    7.786450] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[    8.303763] usb 4-1: new full speed USB device using uhci_hcd and address 2
[    8.465387] usb 4-1: configuration #1 chosen from 1 choice
[    8.550092] Bluetooth: Core ver 2.11
[    8.550695] NET: Registered protocol family 31
[    8.550795] Bluetooth: HCI device and connection manager initialized
[    8.550892] Bluetooth: HCI socket layer initialized
[    8.559175] Bluetooth: HCI USB driver ver 2.9
[    8.677160] usb 4-2: new full speed USB device using uhci_hcd and address 3
[    8.833905] hda_intel: No response from codec, disabling MSI...
[    8.842826] usb 4-2: configuration #1 chosen from 1 choice
[    8.847946] usbcore: registered new interface driver hci_usb
[    9.833318] hda_intel: azx_get_response timeout, switching to polling mode...
[   10.832730] hda_intel: azx_get_response timeout, switching to single_cmd mode...
[   21.618159] sdhci: SDHCI controller found at 0000:15:00.2 [1180:0822] (rev 18)
[   21.619154] ACPI: PCI Interrupt 0000:15:00.2[C] -> GSI 18 (level, low) -> IRQ 22
[   21.620362] PCI: Setting latency timer of device 0000:15:00.2 to 64
[   21.622574] mmc0: SDHCI at 0xe4301800 irq 22 DMA
[   22.346566] Adding 1951856k swap on /dev/sda12.  Priority:-1 extents:1 across:1951856k
[   22.347780] Adding 2931820k swap on /dev/sda13.  Priority:-2 extents:1 across:2931820k
[   22.692872] Non-volatile memory driver v1.2
[   22.731265] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
[   22.731365] ieee1394: sbp2: Try serialize_io=0 for better performance
[   22.764737] ibm_acpi: IBM ThinkPad ACPI Extras v0.12a
[   22.764844] ibm_acpi: http://ibm-acpi.sf.net/
[   22.785014] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Ist] [20060707]
[   22.785828] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Cst] [20060707]
[   22.787166] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[   22.787446] ACPI: Processor [CPU0] (supports 8 throttling states)
[   22.788615] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Ist] [20060707]
[   22.789318] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Cst] [20060707]
[   22.790705] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[   22.790991] ACPI: Processor [CPU1] (supports 8 throttling states)
[   23.002000] Time: hpet clocksource has been installed.
[   23.019000] mmcblk0: mmc0:b368 SD    249856KiB 
[   23.019000]  mmcblk0: p1
[   38.427000] ReiserFS: sda14: found reiserfs format "3.6" with standard journal
[   38.427000] ReiserFS: sda14: warning: CONFIG_REISERFS_CHECK is set ON
[   38.427000] ReiserFS: sda14: warning: - it is slow mode for debugging.
[   38.427000] ReiserFS: sda14: using ordered data mode
[   38.450000] ReiserFS: sda14: journal params: device sda14, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.451000] ReiserFS: sda14: checking transaction log (sda14)
[   38.451000] ReiserFS: sda14: journal-1153: found in header: first_unflushed_offset 7418, last_flushed_trans_id 30277
[   38.453000] ReiserFS: sda14: journal-1206: Starting replay from offset 130043019795706, trans_id 3223281428
[   38.453000] ReiserFS: sda14: journal-1299: Setting newest_mount_id to 176
[   38.495000] ReiserFS: sda14: Using r5 hash to sort names
[   38.558000] ReiserFS: sda8: found reiserfs format "3.6" with standard journal
[   38.558000] ReiserFS: sda8: warning: CONFIG_REISERFS_CHECK is set ON
[   38.558000] ReiserFS: sda8: warning: - it is slow mode for debugging.
[   38.558000] ReiserFS: sda8: using ordered data mode
[   38.565000] ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.566000] ReiserFS: sda8: checking transaction log (sda8)
[   38.566000] ReiserFS: sda8: journal-1153: found in header: first_unflushed_offset 6697, last_flushed_trans_id 571523
[   38.574000] ReiserFS: sda8: journal-1206: Starting replay from offset 2454676888885801, trans_id 3223281428
[   38.574000] ReiserFS: sda8: journal-1299: Setting newest_mount_id to 176
[   38.617000] ReiserFS: sda8: Using r5 hash to sort names
[   38.687000] ReiserFS: sda11: found reiserfs format "3.6" with standard journal
[   38.688000] ReiserFS: sda11: warning: CONFIG_REISERFS_CHECK is set ON
[   38.688000] ReiserFS: sda11: warning: - it is slow mode for debugging.
[   38.688000] ReiserFS: sda11: using ordered data mode
[   38.715000] ReiserFS: sda11: journal params: device sda11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.716000] ReiserFS: sda11: checking transaction log (sda11)
[   38.716000] ReiserFS: sda11: journal-1153: found in header: first_unflushed_offset 5253, last_flushed_trans_id 20436
[   38.749000] ReiserFS: sda11: journal-1206: Starting replay from offset 87776246633605, trans_id 3223281428
[   38.749000] ReiserFS: sda11: journal-1299: Setting newest_mount_id to 176
[   38.771000] ReiserFS: sda11: Using r5 hash to sort names
[   38.798000] ReiserFS: sda10: found reiserfs format "3.6" with standard journal
[   38.799000] ReiserFS: sda10: warning: CONFIG_REISERFS_CHECK is set ON
[   38.799000] ReiserFS: sda10: warning: - it is slow mode for debugging.
[   38.799000] ReiserFS: sda10: using ordered data mode
[   38.809000] ReiserFS: sda10: journal params: device sda10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.809000] ReiserFS: sda10: checking transaction log (sda10)
[   38.810000] ReiserFS: sda10: journal-1153: found in header: first_unflushed_offset 3806, last_flushed_trans_id 20392
[   38.820000] ReiserFS: sda10: journal-1206: Starting replay from offset 87587268071134, trans_id 3223281428
[   38.820000] ReiserFS: sda10: journal-1299: Setting newest_mount_id to 176
[   38.831000] ReiserFS: sda10: Using r5 hash to sort names
[   38.848000] ReiserFS: sda9: found reiserfs format "3.6" with standard journal
[   38.848000] ReiserFS: sda9: warning: CONFIG_REISERFS_CHECK is set ON
[   38.848000] ReiserFS: sda9: warning: - it is slow mode for debugging.
[   38.849000] ReiserFS: sda9: using ordered data mode
[   38.855000] ReiserFS: sda9: journal params: device sda9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.856000] ReiserFS: sda9: checking transaction log (sda9)
[   38.856000] ReiserFS: sda9: journal-1153: found in header: first_unflushed_offset 6872, last_flushed_trans_id 96225
[   38.859000] ReiserFS: sda9: journal-1206: Starting replay from offset 413287523031768, trans_id 4155609112
[   38.859000] ReiserFS: sda9: journal-1299: Setting newest_mount_id to 176
[   38.871000] ReiserFS: sda9: Using r5 hash to sort names
[   38.898000] ReiserFS: sda7: found reiserfs format "3.6" with standard journal
[   38.898000] ReiserFS: sda7: warning: CONFIG_REISERFS_CHECK is set ON
[   38.899000] ReiserFS: sda7: warning: - it is slow mode for debugging.
[   38.899000] ReiserFS: sda7: using ordered data mode
[   38.903000] ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.903000] ReiserFS: sda7: checking transaction log (sda7)
[   38.904000] ReiserFS: sda7: journal-1153: found in header: first_unflushed_offset 5590, last_flushed_trans_id 581233
[   38.909000] ReiserFS: sda7: journal-1206: Starting replay from offset 2496381021328854, trans_id 24000000
[   38.910000] ReiserFS: sda7: journal-1299: Setting newest_mount_id to 176
[   38.953000] ReiserFS: sda7: Using r5 hash to sort names
[   39.014000] ReiserFS: sda6: found reiserfs format "3.6" with standard journal
[   39.015000] ReiserFS: sda6: warning: CONFIG_REISERFS_CHECK is set ON
[   39.015000] ReiserFS: sda6: warning: - it is slow mode for debugging.
[   39.015000] ReiserFS: sda6: using ordered data mode
[   39.052000] ReiserFS: sda6: journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   39.052000] ReiserFS: sda6: checking transaction log (sda6)
[   39.052000] ReiserFS: sda6: journal-1153: found in header: first_unflushed_offset 2919, last_flushed_trans_id 787426
[   39.078000] ReiserFS: sda6: journal-1206: Starting replay from offset 3381973212990311, trans_id 30000000
[   39.078000] ReiserFS: sda6: journal-1299: Setting newest_mount_id to 176
[   39.167000] ReiserFS: sda6: Using r5 hash to sort names
[   39.284000] kjournald starting.  Commit interval 5 seconds
[   39.284000] EXT3 FS on mmcblk0p1, internal journal
[   39.284000] EXT3-fs: mounted filesystem with ordered data mode.
[   51.071000] ACPI: AC Adapter [AC] (off-line)
[   51.096000] ACPI: Battery Slot [BAT0] (battery present)
[   51.111000] ACPI: Power Button (FF) [PWRF]
[   51.111000] ACPI: Lid Switch [LID]
[   51.111000] ACPI: Sleep Button (CM) [SLPB]
[   51.127000] ACPI: ACPI Dock Station Driver 
[   51.177000] ACPI: Thermal Zone [THM0] (46 C)
[   51.179000] ACPI: Thermal Zone [THM1] (47 C)
[   51.194000] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   51.195000] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   64.840000] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
[   65.195000] PCI: Enabling device 0000:00:1b.0 (0100 -> 0102)
[   65.195000] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
[   65.198000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[   66.484000] hda_intel: No response from codec, disabling MSI...
[   67.485000] hda_intel: azx_get_response timeout, switching to polling mode...
[   71.911000] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
[   71.912000] [drm] Initialized i915 1.5.0 20060119 on minor 0
[  155.470000] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
[  155.470000] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
[  155.914000] ACPI: docking
[  156.289000] usb 5-6: new high speed USB device using ehci_hcd and address 4
[  156.403000] usb 5-6: configuration #1 chosen from 1 choice
[  156.403000] hub 5-6:1.0: USB hub found
[  156.403000] hub 5-6:1.0: 4 ports detected
[  156.682000] usb 5-6.1: new low speed USB device using ehci_hcd and address 5
[  156.773000] usb 5-6.1: configuration #1 chosen from 1 choice
[  156.951000] usb 5-6.3: new low speed USB device using ehci_hcd and address 6
[  157.057000] usb 5-6.3: configuration #1 chosen from 1 choice
[  157.202000] usbcore: registered new interface driver hiddev
[  157.204000] input: Logitech USB-PS/2 Optical Mouse as /class/input/input4
[  157.205000] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-6.1
[  157.212000] input: Microsoft Comfort Curve Keyboard 2000 as /class/input/input5
[  157.212000] input: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:1d.7-6.3
[  157.223000] input: Microsoft Comfort Curve Keyboard 2000 as /class/input/input6
[  157.223000] input: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:1d.7-6.3
[  157.223000] usbcore: registered new interface driver usbhid
[  157.223000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver

[-- Attachment #4: dmesg.2.6.19-rc3-ts-tp-ie-e1-44.1+1430-g06df5d4f-dirty.run2 --]
[-- Type: text/plain, Size: 31421 bytes --]

ded (max 8 devices)
[    0.454264] Intel(R) PRO/1000 Network Driver - version 7.2.9-k2-NAPI
[    0.454358] Copyright (c) 1999-2006 Intel Corporation.
[    0.454526] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[    0.454719] PCI: Setting latency timer of device 0000:02:00.0 to 64
[    0.460267] e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:32-bit) 00:16:d3:22:9b:82
[    0.505134] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[    0.505373] netconsole: not configured, aborting
[    0.505579] libata version 2.00 loaded.
[    0.505629] ahci 0000:00:1f.2: version 2.0
[    0.505647] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
[    1.507573] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[    1.507583] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x1 impl SATA mode
[    1.507722] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
[    1.507910] ata1: SATA max UDMA/133 cmd 0xF8824500 ctl 0x0 bmdma 0x0 irq 219
[    1.508079] ata2: SATA max UDMA/133 cmd 0xF8824580 ctl 0x0 bmdma 0x0 irq 219
[    1.508251] ata3: SATA max UDMA/133 cmd 0xF8824600 ctl 0x0 bmdma 0x0 irq 219
[    1.508419] ata4: SATA max UDMA/133 cmd 0xF8824680 ctl 0x0 bmdma 0x0 irq 219
[    1.508524] scsi0 : ahci
[    1.966832] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.967289] ata1.00: ATA-7, max UDMA/100, 156301488 sectors: LBA48 NCQ (depth 31/32)
[    1.967424] ata1.00: ata1: dev 0 multi count 16
[    1.969850] ata1.00: configured for UDMA/100
[    1.969952] scsi1 : ahci
[    2.273333] ata2: SATA link down (SStatus 0 SControl 0)
[    2.273440] scsi2 : ahci
[    2.576850] ata3: SATA link down (SStatus 0 SControl 0)
[    2.576953] scsi3 : ahci
[    2.880368] ata4: SATA link down (SStatus 0 SControl 0)
[    2.880597] scsi 0:0:0:0: Direct-Access     ATA      FUJITSU MHV2080B 0084 PQ: 0 ANSI: 5
[    2.880870] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    2.880982] sda: Write Protect is off
[    2.881073] sda: Mode Sense: 00 3a 00 00
[    2.881099] SCSI device sda: drive cache: write back
[    2.881251] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[    2.881362] sda: Write Protect is off
[    2.881453] sda: Mode Sense: 00 3a 00 00
[    2.881478] SCSI device sda: drive cache: write back
[    2.881575]  sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 >
[    3.052953] sd 0:0:0:0: Attached scsi disk sda
[    3.053295] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[    3.064269] serio: i8042 KBD port at 0x60,0x64 irq 1
[    3.064367] serio: i8042 AUX port at 0x60,0x64 irq 12
[    3.064626] mice: PS/2 mouse device common for all mice
[    3.064722] i2c /dev entries driver
[    3.064957] ACPI: PCI Interrupt 0000:00:1f.3[A] -> GSI 23 (level, low) -> IRQ 19
[    3.065268] hdaps: LENOVO ThinkPad X60 detected, inverting axes
[    3.069987] input: AT Translated Set 2 keyboard as /class/input/input0
[    3.076297] hdaps: initial mode latch is 0x05
[    3.076468] hdaps: setting ec_rate=250, filter_order=2
[    3.076509] hdaps: fake_data_mode set to 0
[    3.076732] hdaps: device successfully initialized.
[    3.076906] input: hdaps as /class/input/input1
[    3.076999] hdaps: driver successfully loaded.
[    3.077093] EDAC MC: Ver: 2.0.1 Oct 30 2006
[    3.077714] thinkpad_ec: thinkpad_ec 0.30 loaded.
[    3.077956] TCP bic registered
[    3.078057] NET: Registered protocol family 1
[    3.078153] NET: Registered protocol family 17
[    3.078263] Starting balanced_irq
[    3.078359] Using IPI No-Shortcut mode
[    3.078884] ACPI: (supports S0 S3 S4 S5)
[    3.079246] Time: tsc clocksource has been installed.
[    3.079386] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
[    3.082224] VFS: Mounted root (ext2 filesystem) readonly.
[    3.082457] Freeing unused kernel memory: 176k freed
[    6.179063] ieee1394: Initialized config rom entry `ip1394'
[    6.181760] ACPI: PCI Interrupt 0000:15:00.1[B] -> GSI 17 (level, low) -> IRQ 21
[    6.181958] PCI: Setting latency timer of device 0000:15:00.1 to 64
[    6.235209] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[21]  MMIO=[e4301000-e43017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
[    6.349287] input: PC Speaker as /class/input/input2
[    6.712159] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[    6.712263] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[    6.908445] usbcore: registered new interface driver usbfs
[    6.908579] usbcore: registered new interface driver hub
[    6.908711] usbcore: registered new device driver usb
[    7.089196] irda_init()
[    7.089213] NET: Registered protocol family 23
[    7.146382] USB Universal Host Controller Interface driver v3.0
[    7.146545] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
[    7.146745] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[    7.146751] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    7.147058] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[    7.147234] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001820
[    7.147488] usb usb1: configuration #1 chosen from 1 choice
[    7.147628] hub 1-0:1.0: USB hub found
[    7.147726] hub 1-0:1.0: 2 ports detected
[    7.198161] sdhci: Secure Digital Host Controller Interface driver, 0.12
[    7.198263] sdhci: Copyright(c) Pierre Ossman
[    7.248594] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 21
[    7.248798] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[    7.248804] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    7.248942] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[    7.249108] uhci_hcd 0000:00:1d.1: irq 21, io base 0x00001840
[    7.249338] usb usb2: configuration #1 chosen from 1 choice
[    7.249818] hub 2-0:1.0: USB hub found
[    7.249917] hub 2-0:1.0: 2 ports detected
[    7.351432] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 22
[    7.351634] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[    7.351640] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    7.351771] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[    7.351940] uhci_hcd 0000:00:1d.2: irq 22, io base 0x00001860
[    7.352165] usb usb3: configuration #1 chosen from 1 choice
[    7.352305] hub 3-0:1.0: USB hub found
[    7.352401] hub 3-0:1.0: 2 ports detected
[    7.453217] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 23
[    7.453403] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[    7.453408] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[    7.453537] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[    7.453701] uhci_hcd 0000:00:1d.3: irq 23, io base 0x00001880
[    7.453921] usb usb4: configuration #1 chosen from 1 choice
[    7.454051] hub 4-0:1.0: USB hub found
[    7.454150] hub 4-0:1.0: 2 ports detected
[    7.499170] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000ae40600192017]
[    7.555770] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 23
[    7.555969] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[    7.555975] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    7.556109] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[    7.556283] ehci_hcd 0000:00:1d.7: debug port 1
[    7.556384] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[    7.556395] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xee444000
[    7.560381] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    7.560837] usb usb5: configuration #1 chosen from 1 choice
[    7.560967] hub 5-0:1.0: USB hub found
[    7.561064] hub 5-0:1.0: 8 ports detected
[    7.563438] eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
[    7.637032] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[    7.657935] input: TPPS/2 IBM TrackPoint as /class/input/input3
[    7.661955] Yenta: CardBus bridge found at 0000:15:00.0 [17aa:201c]
[    7.663374] pnp: Device 00:0a activated.
[    7.663471] nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 7 ; dma 1.
[    7.663500] nsc-ircc, chip->init
[    7.663605] nsc-ircc, Found chip at base=0x164e
[    7.663738] nsc-ircc, driver loaded (Dag Brattli)
[    7.663925] IrDA: Registered device irda0
[    7.664080] nsc-ircc, Found dongle: No dongle connected
[    7.664183] nsc_ircc_init_dongle_interface(), No dongle connected
[    7.785417] Yenta: ISA IRQ mask 0x0c38, PCI irq 20
[    7.785519] Socket status: 30000006
[    7.785615] pcmcia: parent PCI bridge I/O window: 0x9000 - 0xcfff
[    7.785713] pcmcia: parent PCI bridge Memory window: 0xe4300000 - 0xe7ffffff
[    7.785812] pcmcia: parent PCI bridge Memory window: 0xe0000000 - 0xe3ffffff
[    7.786199] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
[    7.786450] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[    8.303763] usb 4-1: new full speed USB device using uhci_hcd and address 2
[    8.465387] usb 4-1: configuration #1 chosen from 1 choice
[    8.550092] Bluetooth: Core ver 2.11
[    8.550695] NET: Registered protocol family 31
[    8.550795] Bluetooth: HCI device and connection manager initialized
[    8.550892] Bluetooth: HCI socket layer initialized
[    8.559175] Bluetooth: HCI USB driver ver 2.9
[    8.677160] usb 4-2: new full speed USB device using uhci_hcd and address 3
[    8.833905] hda_intel: No response from codec, disabling MSI...
[    8.842826] usb 4-2: configuration #1 chosen from 1 choice
[    8.847946] usbcore: registered new interface driver hci_usb
[    9.833318] hda_intel: azx_get_response timeout, switching to polling mode...
[   10.832730] hda_intel: azx_get_response timeout, switching to single_cmd mode...
[   21.618159] sdhci: SDHCI controller found at 0000:15:00.2 [1180:0822] (rev 18)
[   21.619154] ACPI: PCI Interrupt 0000:15:00.2[C] -> GSI 18 (level, low) -> IRQ 22
[   21.620362] PCI: Setting latency timer of device 0000:15:00.2 to 64
[   21.622574] mmc0: SDHCI at 0xe4301800 irq 22 DMA
[   22.346566] Adding 1951856k swap on /dev/sda12.  Priority:-1 extents:1 across:1951856k
[   22.347780] Adding 2931820k swap on /dev/sda13.  Priority:-2 extents:1 across:2931820k
[   22.692872] Non-volatile memory driver v1.2
[   22.731265] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
[   22.731365] ieee1394: sbp2: Try serialize_io=0 for better performance
[   22.764737] ibm_acpi: IBM ThinkPad ACPI Extras v0.12a
[   22.764844] ibm_acpi: http://ibm-acpi.sf.net/
[   22.785014] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Ist] [20060707]
[   22.785828] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu0Cst] [20060707]
[   22.787166] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[   22.787446] ACPI: Processor [CPU0] (supports 8 throttling states)
[   22.788615] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Ist] [20060707]
[   22.789318] ACPI (exconfig-0455): Dynamic SSDT Load - OemId [ PmRef] OemTableId [ Cpu1Cst] [20060707]
[   22.790705] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[   22.790991] ACPI: Processor [CPU1] (supports 8 throttling states)
[   23.002000] Time: hpet clocksource has been installed.
[   23.019000] mmcblk0: mmc0:b368 SD    249856KiB 
[   23.019000]  mmcblk0: p1
[   38.427000] ReiserFS: sda14: found reiserfs format "3.6" with standard journal
[   38.427000] ReiserFS: sda14: warning: CONFIG_REISERFS_CHECK is set ON
[   38.427000] ReiserFS: sda14: warning: - it is slow mode for debugging.
[   38.427000] ReiserFS: sda14: using ordered data mode
[   38.450000] ReiserFS: sda14: journal params: device sda14, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.451000] ReiserFS: sda14: checking transaction log (sda14)
[   38.451000] ReiserFS: sda14: journal-1153: found in header: first_unflushed_offset 7418, last_flushed_trans_id 30277
[   38.453000] ReiserFS: sda14: journal-1206: Starting replay from offset 130043019795706, trans_id 3223281428
[   38.453000] ReiserFS: sda14: journal-1299: Setting newest_mount_id to 176
[   38.495000] ReiserFS: sda14: Using r5 hash to sort names
[   38.558000] ReiserFS: sda8: found reiserfs format "3.6" with standard journal
[   38.558000] ReiserFS: sda8: warning: CONFIG_REISERFS_CHECK is set ON
[   38.558000] ReiserFS: sda8: warning: - it is slow mode for debugging.
[   38.558000] ReiserFS: sda8: using ordered data mode
[   38.565000] ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.566000] ReiserFS: sda8: checking transaction log (sda8)
[   38.566000] ReiserFS: sda8: journal-1153: found in header: first_unflushed_offset 6697, last_flushed_trans_id 571523
[   38.574000] ReiserFS: sda8: journal-1206: Starting replay from offset 2454676888885801, trans_id 3223281428
[   38.574000] ReiserFS: sda8: journal-1299: Setting newest_mount_id to 176
[   38.617000] ReiserFS: sda8: Using r5 hash to sort names
[   38.687000] ReiserFS: sda11: found reiserfs format "3.6" with standard journal
[   38.688000] ReiserFS: sda11: warning: CONFIG_REISERFS_CHECK is set ON
[   38.688000] ReiserFS: sda11: warning: - it is slow mode for debugging.
[   38.688000] ReiserFS: sda11: using ordered data mode
[   38.715000] ReiserFS: sda11: journal params: device sda11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.716000] ReiserFS: sda11: checking transaction log (sda11)
[   38.716000] ReiserFS: sda11: journal-1153: found in header: first_unflushed_offset 5253, last_flushed_trans_id 20436
[   38.749000] ReiserFS: sda11: journal-1206: Starting replay from offset 87776246633605, trans_id 3223281428
[   38.749000] ReiserFS: sda11: journal-1299: Setting newest_mount_id to 176
[   38.771000] ReiserFS: sda11: Using r5 hash to sort names
[   38.798000] ReiserFS: sda10: found reiserfs format "3.6" with standard journal
[   38.799000] ReiserFS: sda10: warning: CONFIG_REISERFS_CHECK is set ON
[   38.799000] ReiserFS: sda10: warning: - it is slow mode for debugging.
[   38.799000] ReiserFS: sda10: using ordered data mode
[   38.809000] ReiserFS: sda10: journal params: device sda10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.809000] ReiserFS: sda10: checking transaction log (sda10)
[   38.810000] ReiserFS: sda10: journal-1153: found in header: first_unflushed_offset 3806, last_flushed_trans_id 20392
[   38.820000] ReiserFS: sda10: journal-1206: Starting replay from offset 87587268071134, trans_id 3223281428
[   38.820000] ReiserFS: sda10: journal-1299: Setting newest_mount_id to 176
[   38.831000] ReiserFS: sda10: Using r5 hash to sort names
[   38.848000] ReiserFS: sda9: found reiserfs format "3.6" with standard journal
[   38.848000] ReiserFS: sda9: warning: CONFIG_REISERFS_CHECK is set ON
[   38.848000] ReiserFS: sda9: warning: - it is slow mode for debugging.
[   38.849000] ReiserFS: sda9: using ordered data mode
[   38.855000] ReiserFS: sda9: journal params: device sda9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.856000] ReiserFS: sda9: checking transaction log (sda9)
[   38.856000] ReiserFS: sda9: journal-1153: found in header: first_unflushed_offset 6872, last_flushed_trans_id 96225
[   38.859000] ReiserFS: sda9: journal-1206: Starting replay from offset 413287523031768, trans_id 4155609112
[   38.859000] ReiserFS: sda9: journal-1299: Setting newest_mount_id to 176
[   38.871000] ReiserFS: sda9: Using r5 hash to sort names
[   38.898000] ReiserFS: sda7: found reiserfs format "3.6" with standard journal
[   38.898000] ReiserFS: sda7: warning: CONFIG_REISERFS_CHECK is set ON
[   38.899000] ReiserFS: sda7: warning: - it is slow mode for debugging.
[   38.899000] ReiserFS: sda7: using ordered data mode
[   38.903000] ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   38.903000] ReiserFS: sda7: checking transaction log (sda7)
[   38.904000] ReiserFS: sda7: journal-1153: found in header: first_unflushed_offset 5590, last_flushed_trans_id 581233
[   38.909000] ReiserFS: sda7: journal-1206: Starting replay from offset 2496381021328854, trans_id 24000000
[   38.910000] ReiserFS: sda7: journal-1299: Setting newest_mount_id to 176
[   38.953000] ReiserFS: sda7: Using r5 hash to sort names
[   39.014000] ReiserFS: sda6: found reiserfs format "3.6" with standard journal
[   39.015000] ReiserFS: sda6: warning: CONFIG_REISERFS_CHECK is set ON
[   39.015000] ReiserFS: sda6: warning: - it is slow mode for debugging.
[   39.015000] ReiserFS: sda6: using ordered data mode
[   39.052000] ReiserFS: sda6: journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[   39.052000] ReiserFS: sda6: checking transaction log (sda6)
[   39.052000] ReiserFS: sda6: journal-1153: found in header: first_unflushed_offset 2919, last_flushed_trans_id 787426
[   39.078000] ReiserFS: sda6: journal-1206: Starting replay from offset 3381973212990311, trans_id 30000000
[   39.078000] ReiserFS: sda6: journal-1299: Setting newest_mount_id to 176
[   39.167000] ReiserFS: sda6: Using r5 hash to sort names
[   39.284000] kjournald starting.  Commit interval 5 seconds
[   39.284000] EXT3 FS on mmcblk0p1, internal journal
[   39.284000] EXT3-fs: mounted filesystem with ordered data mode.
[   51.071000] ACPI: AC Adapter [AC] (off-line)
[   51.096000] ACPI: Battery Slot [BAT0] (battery present)
[   51.111000] ACPI: Power Button (FF) [PWRF]
[   51.111000] ACPI: Lid Switch [LID]
[   51.111000] ACPI: Sleep Button (CM) [SLPB]
[   51.127000] ACPI: ACPI Dock Station Driver 
[   51.177000] ACPI: Thermal Zone [THM0] (46 C)
[   51.179000] ACPI: Thermal Zone [THM1] (47 C)
[   51.194000] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   51.195000] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   64.840000] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
[   65.195000] PCI: Enabling device 0000:00:1b.0 (0100 -> 0102)
[   65.195000] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
[   65.198000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[   66.484000] hda_intel: No response from codec, disabling MSI...
[   67.485000] hda_intel: azx_get_response timeout, switching to polling mode...
[   71.911000] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
[   71.912000] [drm] Initialized i915 1.5.0 20060119 on minor 0
[  155.470000] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
[  155.470000] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
[  155.914000] ACPI: docking
[  156.289000] usb 5-6: new high speed USB device using ehci_hcd and address 4
[  156.403000] usb 5-6: configuration #1 chosen from 1 choice
[  156.403000] hub 5-6:1.0: USB hub found
[  156.403000] hub 5-6:1.0: 4 ports detected
[  156.682000] usb 5-6.1: new low speed USB device using ehci_hcd and address 5
[  156.773000] usb 5-6.1: configuration #1 chosen from 1 choice
[  156.951000] usb 5-6.3: new low speed USB device using ehci_hcd and address 6
[  157.057000] usb 5-6.3: configuration #1 chosen from 1 choice
[  157.202000] usbcore: registered new interface driver hiddev
[  157.204000] input: Logitech USB-PS/2 Optical Mouse as /class/input/input4
[  157.205000] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-6.1
[  157.212000] input: Microsoft Comfort Curve Keyboard 2000 as /class/input/input5
[  157.212000] input: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:1d.7-6.3
[  157.223000] input: Microsoft Comfort Curve Keyboard 2000 as /class/input/input6
[  157.223000] input: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:1d.7-6.3
[  157.223000] usbcore: registered new interface driver usbhid
[  157.223000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[  579.730000] usb 5-6.2: new high speed USB device using ehci_hcd and address 7
[  579.815000] usb 5-6.2: configuration #1 chosen from 1 choice
[  579.882000] Initializing USB Mass Storage driver...
[  579.882000] scsi4 : SCSI emulation for USB Mass Storage devices
[  579.882000] usb-storage: device found at 7
[  579.882000] usb-storage: waiting for device to settle before scanning
[  579.882000] usbcore: registered new interface driver usb-storage
[  579.882000] USB Mass Storage support registered.
[  584.884000] scsi 4:0:0:0: Direct-Access     USB 2.0  memory           0.00 PQ: 0 ANSI: 2
[  584.885000] SCSI device sdb: 1024000 512-byte hdwr sectors (524 MB)
[  584.886000] sdb: Write Protect is off
[  584.886000] sdb: Mode Sense: 00 00 00 00
[  584.886000] sdb: assuming drive cache: write through
[  584.888000] SCSI device sdb: 1024000 512-byte hdwr sectors (524 MB)
[  584.888000] sdb: Write Protect is off
[  584.888000] sdb: Mode Sense: 00 00 00 00
[  584.888000] sdb: assuming drive cache: write through
[  584.889000]  sdb: sdb1
[  585.076000] sd 4:0:0:0: Attached scsi removable disk sdb
[  585.077000] usb-storage: device scan complete
[  599.265000] usb 5-6.2: USB disconnect, address 7
[  702.852000] ACPI: undocking
[  703.083000] usb 5-6: USB disconnect, address 4
[  703.083000] usb 5-6.1: USB disconnect, address 5
[  703.083000] usb 5-6.3: USB disconnect, address 6
[  708.397000] e1000: eth0: e1000_watchdog: NIC Link is Down
[  729.483000] Disabling non-boot CPUs ...
[  729.537000] Breaking affinity for irq 219
[  729.538000] CPU 1 is now offline
[  729.538000] SMP alternatives: switching to UP code
[  729.547000] CPU1 is down
[  729.547000] Stopping tasks: =========================================================================================================================|
[  730.081000] Suspending console(s)
[  730.081000]  usbdev4.3_ep83: PM: suspend 0->2, parent 4-2:1.0 already 2
[  730.081000]  usbdev4.3_ep02: PM: suspend 0->2, parent 4-2:1.0 already 2
[  730.081000]  usbdev4.3_ep81: PM: suspend 0->2, parent 4-2:1.0 already 2
[  730.081000] usb 4-2:1.0: PM: suspend 2->2, parent 4-2 already 2
[  730.081000]  usbdev4.3_ep00: PM: suspend 0->2, parent 4-2 already 2
[  730.094000] hdaps: setting ec_rate=0, filter_order=1
[  731.775000] pnp: Device 00:0a disabled.
[  731.776000] ACPI: PCI interrupt for device 0000:15:00.2 disabled
[  731.798000] ACPI: PCI interrupt for device 0000:15:00.0 disabled
[  731.846000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
[  731.859000] ACPI: PCI interrupt for device 0000:00:1f.2 disabled
[  731.870000] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
[  731.982000] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
[  731.982000] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
[  731.982000] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
[  731.982000] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
[  731.984000] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
[  731.995000] Intel machine check architecture supported.
[  731.995000] Intel machine check reporting enabled on CPU#0.
[  731.995000] Back to C!
[ 1633.713000] PM: Writing back config space on device 0000:00:02.1 at offset 1 (was 900000, writing 900003)
[ 1633.725000] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100106, writing 100100)
[ 1633.725000] PCI: Enabling device 0000:00:1b.0 (0100 -> 0102)
[ 1633.725000] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
[ 1633.725000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.2 at offset 7 (was 20006050, writing 6050)
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1c.2 to 64
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.3 at offset f (was 40400, writing 4040b)
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.3 at offset 9 (was 10001, writing e421e421)
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.3 at offset 8 (was 0, writing ebf0ea00)
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.3 at offset 7 (was 20000000, writing 8070)
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.3 at offset 3 (was 810000, writing 810010)
[ 1633.743000] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100000, writing 100507)
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[ 1633.743000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 20
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[ 1633.743000] usb usb1: root hub lost power or was reset
[ 1633.743000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 21
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[ 1633.743000] usb usb2: root hub lost power or was reset
[ 1633.743000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 22
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[ 1633.743000] usb usb3: root hub lost power or was reset
[ 1633.743000] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 23
[ 1633.743000] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[ 1633.743000] usb usb4: root hub lost power or was reset
[ 1634.104000] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 23
[ 1634.104000] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[ 1634.104000] PM: Writing back config space on device 0000:00:1e.0 at offset 1 (was 100005, writing 100007)
[ 1634.104000] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[ 1634.115000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 20
[ 1634.115000] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[ 1635.129000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[ 1635.129000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 1635.172000] PM: Writing back config space on device 0000:15:00.0 at offset 1 (was 2100000, writing 2100007)
[ 1635.172000] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 20
[ 1635.214000] PM: Writing back config space on device 0000:15:00.1 at offset 4 (was 0, writing e4301000)
[ 1635.214000] PM: Writing back config space on device 0000:15:00.1 at offset 3 (was 800000, writing 804000)
[ 1635.214000] PM: Writing back config space on device 0000:15:00.1 at offset 1 (was 2100000, writing 2100006)
[ 1635.225000] PM: Writing back config space on device 0000:15:00.2 at offset 4 (was 0, writing e4301800)
[ 1635.225000] PM: Writing back config space on device 0000:15:00.2 at offset 3 (was 800000, writing 804000)
[ 1635.225000] PM: Writing back config space on device 0000:15:00.2 at offset 1 (was 2100000, writing 2100006)
[ 1635.225000] ACPI: PCI Interrupt 0000:15:00.2[C] -> GSI 18 (level, low) -> IRQ 22
[ 1635.400000] pnp: Device 00:08 does not support activation.
[ 1635.400000] pnp: Device 00:09 does not support activation.
[ 1635.401000] pnp: Device 00:0a activated.
[ 1635.421000] ata2: SATA link down (SStatus 0 SControl 0)
[ 1635.421000] ata3: SATA link down (SStatus 0 SControl 0)
[ 1635.421000] ata4: SATA link down (SStatus 0 SControl 0)
[ 1635.680000] hdaps: initial mode latch is 0x05
[ 1635.680000] hdaps: setting ec_rate=250, filter_order=2
[ 1635.680000] hdaps: fake_data_mode set to 0
[ 1635.821000] nsc_ircc_init_dongle_interface(), No dongle connected
[ 1635.821000] nsc_ircc_change_dongle_speed(), No dongle connected is not for IrDA mode
[ 1635.821000]  usbdev4.2_ep00: PM: resume from 0, parent 4-1 still 2
[ 1635.821000] hci_usb 4-1:1.0: PM: resume from 2, parent 4-1 still 2
[ 1635.821000]  usbdev4.2_ep81: PM: resume from 0, parent 4-1:1.0 still 2
[ 1635.821000]  usbdev4.2_ep82: PM: resume from 0, parent 4-1:1.0 still 2
[ 1635.821000]  usbdev4.2_ep02: PM: resume from 0, parent 4-1:1.0 still 2
[ 1635.821000] hci_usb 4-1:1.1: PM: resume from 2, parent 4-1 still 2
[ 1635.821000] usb 4-1:1.2: PM: resume from 2, parent 4-1 still 2
[ 1635.821000]  usbdev4.2_ep84: PM: resume from 0, parent 4-1:1.2 still 2
[ 1635.821000]  usbdev4.2_ep04: PM: resume from 0, parent 4-1:1.2 still 2
[ 1635.821000] usb 4-1:1.3: PM: resume from 2, parent 4-1 still 2
[ 1635.821000]  usbdev4.3_ep00: PM: resume from 0, parent 4-2 still 2
[ 1635.821000]  usbdev4.3_ep81: PM: resume from 0, parent 4-2:1.0 still 2
[ 1635.821000]  usbdev4.3_ep02: PM: resume from 0, parent 4-2:1.0 still 2
[ 1635.821000]  usbdev4.3_ep83: PM: resume from 0, parent 4-2:1.0 still 2
[ 1635.821000]  usbdev4.2_ep83: PM: resume from 0, parent 4-1:1.1 still 2
[ 1635.821000]  usbdev4.2_ep03: PM: resume from 0, parent 4-1:1.1 still 2
[ 1635.821000]  hci0: PM: resume from 0, parent 4-1:1.0 still 2
[ 1635.822000] Restarting tasks...<6>usb 4-1: USB disconnect, address 2
[ 1635.832000]  done
[ 1635.832000] Enabling non-boot CPUs ...
[ 1635.845000] SMP alternatives: switching to SMP code
[ 1635.846000] Booting processor 1/1 eip 3000
[ 1635.856000] Initializing CPU#1
[ 1635.917000] Calibrating delay using timer specific routine.. 3325.06 BogoMIPS (lpj=1662531)
[ 1635.917000] CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
[ 1635.917000] monitor/mwait feature present.
[ 1635.917000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 1635.917000] CPU: L2 cache: 2048K
[ 1635.917000] CPU: Physical Processor ID: 0
[ 1635.917000] CPU: Processor Core ID: 1
[ 1635.917000] CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000940 0000c1a9 00000000 00000000
[ 1635.917000] Intel machine check architecture supported.
[ 1635.917000] Intel machine check reporting enabled on CPU#1.
[ 1635.917000] CPU1: Intel Genuine Intel(R) CPU           L2400  @ 1.66GHz stepping 08
[ 1635.996000] usb 4-2: USB disconnect, address 3
[ 1636.202000] usb 4-2: new full speed USB device using uhci_hcd and address 4
[ 1636.365000] usb 4-2: configuration #1 chosen from 1 choice
[ 1636.647000] ata1: waiting for device to spin up (7 secs)
[ 1636.817000] usb 4-1: new full speed USB device using uhci_hcd and address 5
[ 1636.977000] usb 4-1: configuration #1 chosen from 1 choice
[ 1638.293000] CPU1 is up
[ 1644.484000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1644.488000] ata1.00: configured for UDMA/100
[ 1644.489000] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[ 1644.489000] sda: Write Protect is off
[ 1644.489000] sda: Mode Sense: 00 3a 00 00
[ 1644.489000] SCSI device sda: drive cache: write back
[ 1831.582000] thinkpad_ec: thinkpad_ec_request_row: bad end STR3: (0x11:0x00)->0x80

[-- Attachment #5: ibm_acpi.dump.2006-10-30-150116-UTC_before --]
[-- Type: text/plain, Size: 3479 bytes --]

/proc/acpi/ibm/bay
status:		not supported
================================================================

/proc/acpi/ibm/beep
status:		supported
commands:	<cmd> (<cmd> is 0-17)
================================================================

/proc/acpi/ibm/bluetooth
status:		enabled
commands:	enable, disable
================================================================

/proc/acpi/ibm/brightness
level:		3
commands:	up, down
commands:	level <level> (<level> is 0-7)
================================================================

/proc/acpi/ibm/cmos
status:		supported
commands:	<cmd> (<cmd> is 0-21)
================================================================

/proc/acpi/ibm/driver
driver:		IBM ThinkPad ACPI Extras
version:	0.12a
================================================================

/proc/acpi/ibm/ecdump
EC       +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
EC 0x00: *a6 *05 *a0 *01 *fe *96  00  00 *1f *02 *47  00  00  00 *80  00
EC 0x10:  00  00 *ff *ff *f4 *3c *87 *09 *43 *ff *82 *01 *ff *ff *2d  00
EC 0x20:  00  00  00  00  00  00  00  00  00  00  00  00 *85  00  00 *80
EC 0x30: *4a *03 *12  00 *30 *04  00  00 *c5  00 *b0 *10  00 *50  00  00
EC 0x40:  00  00  00  00  00  00 *84 *01 *0a  00  00  00  00  00  00  00
EC 0x50:  00 *c0 *02 *23 *41  00 *33 *2d *03 *2f *2d *06 *21 *23 *30  00
EC 0x60: *80  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0x70:  00  00  00  00  00 *12 *30 *40 *2e *2a *80 *2d *21 *80 *1f *80
EC 0x80:  00  00  00 *06  00  00 *03  00  00  00 *0e *78  00  00  00  00
EC 0x90:  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xa0: *11 *0a *74 *0a *62  00 *61  00 *34 *fc *3b *3f *ff *ff *e0  00
EC 0xb0:  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xc0: *2b *29 *80 *80 *80 *80 *80 *80  00  00  00  00  00  00 *10  00
EC 0xd0: *06  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xe0:  00  00  00  00  00  00  00  00 *10 *80 *a6 *04 *24 *2e *55 *03
EC 0xf0: *37 *42 *48 *54 *33 *35 *57 *57 *0c *f5 *60 *7c *0c *e7 *63 *93
================================================================

/proc/acpi/ibm/fan
status:		enabled
speed:		0
commands:	enable, disable
================================================================

/proc/acpi/ibm/hotkey
status:		enabled
mask:		0xff9f
commands:	enable, disable, reset, <mask>
================================================================

/proc/acpi/ibm/led
status:		supported
commands:	<led> on, <led> off, <led> blink (<led> is 0-7)
================================================================

/proc/acpi/ibm/light
status:		off
commands:	on, off
================================================================

/proc/acpi/ibm/thermal
temperatures:	46 42 -128 45 33 -128 31 -128
================================================================

/proc/acpi/ibm/video
status:		supported
lcd:		enabled
crt:		enabled
dvi:		disabled
auto:		enabled
commands:	lcd_enable, lcd_disable
commands:	crt_enable, crt_disable
commands:	dvi_enable, dvi_disable
commands:	auto_enable, auto_disable
commands:	video_switch, expand_toggle
================================================================

/proc/acpi/ibm/volume
level:		10
mute:		on
commands:	up, down, mute
commands:	level <level> (<level> is 0-15)
================================================================

/proc/acpi/ibm/wan
status:		not installed
================================================================


[-- Attachment #6: ibm_acpi.dump.2006-10-30-151632-UTC_after1 --]
[-- Type: text/plain, Size: 3479 bytes --]

/proc/acpi/ibm/bay
status:		not supported
================================================================

/proc/acpi/ibm/beep
status:		supported
commands:	<cmd> (<cmd> is 0-17)
================================================================

/proc/acpi/ibm/bluetooth
status:		enabled
commands:	enable, disable
================================================================

/proc/acpi/ibm/brightness
level:		3
commands:	up, down
commands:	level <level> (<level> is 0-7)
================================================================

/proc/acpi/ibm/cmos
status:		supported
commands:	<cmd> (<cmd> is 0-21)
================================================================

/proc/acpi/ibm/driver
driver:		IBM ThinkPad ACPI Extras
version:	0.12a
================================================================

/proc/acpi/ibm/ecdump
EC       +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
EC 0x00: *a7  05  a0  01  fe  96  00  00  1f  02  47  00  00  00  80  00
EC 0x10:  00  00  ff  ff  f4  3c  87  09  43  ff  82  01  ff  ff  2d  00
EC 0x20:  00  00  00  00  00  00  00  00  00  00  00  00  85  00  00  80
EC 0x30:  4a  03 *02  00  30  04 *04  00  c5  00 *30  10 *2a  50  00  00
EC 0x40:  00  00  00  00  00  00  84  01  0a  00  00  00  00  00 *04  00
EC 0x50:  00  c0  02  23  41  00  33  2d  03  2f  2d  06  21  23  30  00
EC 0x60:  80  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0x70:  00  00  00  00  00  12  30  40 *24 *1e  80 *20 *1c  80 *1c  80
EC 0x80:  00  00  00  06  00  00  03  00  00  00  0e  78  00  00  00  00
EC 0x90:  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xa0: *ef *09  74  0a *6e  00 *5f  00 *9e  fc *f0 *3e  ff  ff *c0  00
EC 0xb0:  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xc0: *1d *1e  80  80  80  80  80  80  00  00  00  00  00  00  10  00
EC 0xd0:  06  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xe0:  00  00  00  00  00  00  00  00  10  80  a6  04  24  2e  55  03
EC 0xf0:  37  42  48  54  33  35  57  57  0c  f5  60  7c  0c  e7  63  93
================================================================

/proc/acpi/ibm/fan
status:		enabled
speed:		0
commands:	enable, disable
================================================================

/proc/acpi/ibm/hotkey
status:		enabled
mask:		0xff9f
commands:	enable, disable, reset, <mask>
================================================================

/proc/acpi/ibm/led
status:		supported
commands:	<led> on, <led> off, <led> blink (<led> is 0-7)
================================================================

/proc/acpi/ibm/light
status:		off
commands:	on, off
================================================================

/proc/acpi/ibm/thermal
temperatures:	41 31 -128 37 29 -128 28 -128
================================================================

/proc/acpi/ibm/video
status:		supported
lcd:		enabled
crt:		enabled
dvi:		disabled
auto:		enabled
commands:	lcd_enable, lcd_disable
commands:	crt_enable, crt_disable
commands:	dvi_enable, dvi_disable
commands:	auto_enable, auto_disable
commands:	video_switch, expand_toggle
================================================================

/proc/acpi/ibm/volume
level:		10
mute:		on
commands:	up, down, mute
commands:	level <level> (<level> is 0-15)
================================================================

/proc/acpi/ibm/wan
status:		not installed
================================================================


[-- Attachment #7: ibm_acpi.dump.2006-10-30-151747-UTC_after2 --]
[-- Type: text/plain, Size: 3480 bytes --]

/proc/acpi/ibm/bay
status:		not supported
================================================================

/proc/acpi/ibm/beep
status:		supported
commands:	<cmd> (<cmd> is 0-17)
================================================================

/proc/acpi/ibm/bluetooth
status:		enabled
commands:	enable, disable
================================================================

/proc/acpi/ibm/brightness
level:		3
commands:	up, down
commands:	level <level> (<level> is 0-7)
================================================================

/proc/acpi/ibm/cmos
status:		supported
commands:	<cmd> (<cmd> is 0-21)
================================================================

/proc/acpi/ibm/driver
driver:		IBM ThinkPad ACPI Extras
version:	0.12a
================================================================

/proc/acpi/ibm/ecdump
EC       +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
EC 0x00:  a7  05  a0  01  fe  96  00  00  1f  02  47  00  00  00  80  00
EC 0x10:  00  00  ff  ff  f4  3c  87  09  43  ff  82  01  ff  ff  2d  00
EC 0x20:  00  00  00  00  00  00  00  00  00  00  00  00  85  00  00  80
EC 0x30:  4a  03  02  00  30  04  00  00  c5  00  30  10  2a  50  00  00
EC 0x40:  00  00  00  00  00  00  84  01  0a  00  00  00  00  00  00  00
EC 0x50:  00  c0  02  23  41  00  33  2d  03  2f  2d  06  21  23  30  00
EC 0x60:  80  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0x70:  00  00  00  00  00  12  30  40 *2b *1f  80 *26  1d  80  1c  80
EC 0x80:  00  00  00  06  00  00  03  00  00  00  0e  78  00  00  00  00
EC 0x90:  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xa0: *c7  09  74  0a *4d  00 *5e  00 *28  fc *87  3e  ff  ff  c0  00
EC 0xb0:  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xc0: *20 *21  80  80  80  80  80  80  00  00  00  00  00  00  10  00
EC 0xd0:  06  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
EC 0xe0:  00  00  00  00  00  00  00  00  10  80  a6  04  24  2e  55  03
EC 0xf0:  37  42  48  54  33  35  57  57  0c  f5  60  7c  0c  e7  63  93
================================================================

/proc/acpi/ibm/fan
status:		enabled
speed:		0
commands:	enable, disable
================================================================

/proc/acpi/ibm/hotkey
status:		disabled
mask:		0x080c
commands:	enable, disable, reset, <mask>
================================================================

/proc/acpi/ibm/led
status:		supported
commands:	<led> on, <led> off, <led> blink (<led> is 0-7)
================================================================

/proc/acpi/ibm/light
status:		off
commands:	on, off
================================================================

/proc/acpi/ibm/thermal
temperatures:	45 32 -128 40 29 -128 28 -128
================================================================

/proc/acpi/ibm/video
status:		supported
lcd:		enabled
crt:		enabled
dvi:		disabled
auto:		enabled
commands:	lcd_enable, lcd_disable
commands:	crt_enable, crt_disable
commands:	dvi_enable, dvi_disable
commands:	auto_enable, auto_disable
commands:	video_switch, expand_toggle
================================================================

/proc/acpi/ibm/volume
level:		10
mute:		on
commands:	up, down, mute
commands:	level <level> (<level> is 0-15)
================================================================

/proc/acpi/ibm/wan
status:		not installed
================================================================


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



^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
  2006-10-30 15:27   ` Martin Lorenz
@ 2006-10-30 16:17   ` Jun'ichi Nomura
  2006-10-30 16:32     ` Michael S. Tsirkin
  2006-10-30 16:44     ` Linus Torvalds
  2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
  2 siblings, 2 replies; 41+ messages in thread
From: Jun'ichi Nomura @ 2006-10-30 16:17 UTC (permalink / raw)
  To: Michael S. Tsirkin, Martin Lorenz
  Cc: Pavel Machek, Adrian Bunk, Linus Torvalds, Andrew Morton,
	Linux Kernel Mailing List, len.brown, linux-acpi, linux-pm,
	Randy.Dunlap

Hi Michael,

 > 2.6.19-rc3 without reverting
 > d7dd8fd9557840162b724a8ac1366dd78a12dff stops receiving ACPI events after some
 > use (sometimes after suspend/resume, sometimes after kernel build stress).  Now,
 > what does this tell us? Andrew, any idea?

The code is related to bd_claim_by_disk which is called when
device-mapper or md tries to mark the underlying devices
for exclusive use and creates symlinks from/to the devices
in sysfs. The patch added error handlings which weren't in
the original code.

I have no idea how it affects ACPI event handling.
Are you using dm and/or md on your machine?
Have you seen any unusual kernel messages or symptoms regarding
dm/md before the ACPI problem occurs?

Michael S. Tsirkin wrote:
> Quoting r. Adrian Bunk <bunk@stusta.de>:
>> Subject    : T60 stops triggering any ACPI events
>> References : http://lkml.org/lkml/2006/10/4/425
>>              http://lkml.org/lkml/2006/10/16/262
>>              http://bugzilla.kernel.org/show_bug.cgi?id=7408
>> Submitter  : "Michael S. Tsirkin" <mst@mellanox.co.il>
>> Status     : unknown
> 
> OK, I spent half a night with git-bisect, and the patch that triggers this issue
> seems to be this:
> 
> commit d7dd8fd9557840162b724a8ac1366dd78a12dff
> Author: Andrew Morton <akpm@osdl.org> 
>     [PATCH] blockdev.c: check driver layer errors
> 
> Reset to d7dd8fd9557840162b724a8ac1366dd78a12dff seems to hide part of the issue
> (I have ACPI after kernel build, but not after suspend/resume).  Both reverting
> this patch, and reset to the parent of this patch seem to solve (or at least,
> hide) both problems for me (no ACPI after suspend/resume and no ACPI after
> kernel build).
> 
> I am currently running on 2.6.19-rc3 minus
> d7dd8fd9557840162b724a8ac1366dd78a12dff, and in a full day of use I have not
> observed any issues yet. 2.6.19-rc3 without reverting
> d7dd8fd9557840162b724a8ac1366dd78a12dff stops receiving ACPI events after some
> use (sometimes after suspend/resume, sometimes after kernel build stress).  Now,
> what does this tell us? Andrew, any idea?
> 
> 
> Martin, could you test whether reverting this helps you, too, by chance?
> Here's a patch to apply for testing this.
> 
> ---
> 
> commit 658488b7577b7b2242372c43f081f55e2d274615
> Author: Michael S. Tsirkin <mst@mellanox.co.il>
> Date:   Mon Oct 30 01:28:40 2006 +0200
> 
>     Revert "[PATCH] blockdev.c: check driver layer errors"
>     
>     This reverts commit 4d7dd8fd9557840162b724a8ac1366dd78a12dff.

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 16:17   ` Jun'ichi Nomura
@ 2006-10-30 16:32     ` Michael S. Tsirkin
  2006-10-30 17:20       ` Jun'ichi Nomura
  2006-10-30 16:44     ` Linus Torvalds
  1 sibling, 1 reply; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-10-30 16:32 UTC (permalink / raw)
  To: Jun'ichi Nomura
  Cc: Martin Lorenz, Pavel Machek, Adrian Bunk, Linus Torvalds,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Randy.Dunlap

Quoting r. Jun'ichi Nomura <j-nomura@ce.jp.nec.com>:
> Subject: Re: 2.6.19-rc3: known unfixed regressions (v3)
> 
> Hi Michael,
> 
>  > 2.6.19-rc3 without reverting
>  > d7dd8fd9557840162b724a8ac1366dd78a12dff stops receiving ACPI events after some
>  > use (sometimes after suspend/resume, sometimes after kernel build stress).  Now,
>  > what does this tell us? Andrew, any idea?
> 
> The code is related to bd_claim_by_disk which is called when
> device-mapper or md tries to mark the underlying devices
> for exclusive use and creates symlinks from/to the devices
> in sysfs. The patch added error handlings which weren't in
> the original code.
> 
> I have no idea how it affects ACPI event handling.

It's a mystery. Probably exposes a bug somewhere?

> Are you using dm and/or md on your machine?

The .config is attached to bugzilla.

> Have you seen any unusual kernel messages or symptoms regarding
> dm/md before the ACPI problem occurs?

I haven't.

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 16:32     ` Michael S. Tsirkin
@ 2006-10-30 17:20       ` Jun'ichi Nomura
  2006-10-30 17:54         ` Michael S. Tsirkin
  0 siblings, 1 reply; 41+ messages in thread
From: Jun'ichi Nomura @ 2006-10-30 17:20 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Andrew Morton, len.brown, Linus Torvalds, linux-pm, linux-acpi,
	Linux Kernel Mailing List, Adrian Bunk, Martin Lorenz

Hi Michael,

Michael S. Tsirkin wrote:
>> The code is related to bd_claim_by_disk which is called when
>> device-mapper or md tries to mark the underlying devices
>> for exclusive use and creates symlinks from/to the devices
>> in sysfs. The patch added error handlings which weren't in
>> the original code.
>>
>> I have no idea how it affects ACPI event handling.
> 
> It's a mystery. Probably exposes a bug somewhere?
> 
>> Are you using dm and/or md on your machine?
> 
> The .config is attached to bugzilla.

OK, I found you disabled CONFIG_MD, which means neither
dm.ko nor md.ko was built.
Do you have any out-of-tree kernel modules which call either
bd_claim_by_kobject or bd_claim_by_disk?

If you aren't using either of them, I'm afraid reverting
the patch doesn't really solve your problem because the patched
code is called only from them.

>> Have you seen any unusual kernel messages or symptoms regarding
>> dm/md before the ACPI problem occurs?
> 
> I haven't.

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 17:20       ` Jun'ichi Nomura
@ 2006-10-30 17:54         ` Michael S. Tsirkin
  0 siblings, 0 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-10-30 17:54 UTC (permalink / raw)
  To: Jun'ichi Nomura
  Cc: Andrew Morton, len.brown, Linus Torvalds, linux-pm, linux-acpi,
	Linux Kernel Mailing List, Adrian Bunk, Martin Lorenz

Quoting r. Jun'ichi Nomura <j-nomura@ce.jp.nec.com>:
> Subject: Re: 2.6.19-rc3: known unfixed regressions (v3)
> 
> Hi Michael,
> 
> Michael S. Tsirkin wrote:
> >> The code is related to bd_claim_by_disk which is called when
> >> device-mapper or md tries to mark the underlying devices
> >> for exclusive use and creates symlinks from/to the devices
> >> in sysfs. The patch added error handlings which weren't in
> >> the original code.
> >>
> >> I have no idea how it affects ACPI event handling.
> > 
> > It's a mystery. Probably exposes a bug somewhere?
> > 
> >> Are you using dm and/or md on your machine?
> > 
> > The .config is attached to bugzilla.
> 
> OK, I found you disabled CONFIG_MD, which means neither
> dm.ko nor md.ko was built.
> Do you have any out-of-tree kernel modules which call either
> bd_claim_by_kobject or bd_claim_by_disk?

No, I don't have any out-of-tree modules.

> If you aren't using either of them, I'm afraid reverting
> the patch doesn't really solve your problem because the patched
> code is called only from them.

I agree this could be just papering over some issue.
The test results (of both git-bisect and reverting the patch) seem to be pretty
consistent so far though. Keep me posted if you rework the patch.

> >> Have you seen any unusual kernel messages or symptoms regarding
> >> dm/md before the ACPI problem occurs?
> > 
> > I haven't.
> 
> Thanks,

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 16:17   ` Jun'ichi Nomura
  2006-10-30 16:32     ` Michael S. Tsirkin
@ 2006-10-30 16:44     ` Linus Torvalds
  2006-10-30 17:34       ` Jun'ichi Nomura
  1 sibling, 1 reply; 41+ messages in thread
From: Linus Torvalds @ 2006-10-30 16:44 UTC (permalink / raw)
  To: Jun'ichi Nomura
  Cc: Michael S. Tsirkin, Martin Lorenz, Pavel Machek, Adrian Bunk,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Randy.Dunlap

On Mon, 30 Oct 2006, Jun'ichi Nomura wrote:
> 
> The code is related to bd_claim_by_disk which is called when
> device-mapper or md tries to mark the underlying devices
> for exclusive use and creates symlinks from/to the devices
> in sysfs. The patch added error handlings which weren't in
> the original code.

Actually, looking closer at the code, the patch seems to add _incorrect_ 
error handling.

For example, look at bd_claim_by_kobject(): if the "bd_claim()" inside of 
it succeeds, we used to always return success. Now, we don't necessarily 
do that: we may have done a _successful_ "bd_claim()" call, but then we 
return an error because something else failed, and now we're returning 
with from bd_claim_by_kobject() with the bd_claim() done, but with an 
error return (so the caller will _not_ call "bd_release()", and the 
block_device will forever stay exclusive).

No?

Now, exactly why acpi stops working as a result, I don't know, but maybe 
something else tries to get exclusive access to a swap partition, for 
example, and now fails, causing some acpi sequence to not be set up? 
Dunno.

So I suspect it should be reverted, but maybe somebody can see exactly 
what goes wrong here.

		Linus

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 16:44     ` Linus Torvalds
@ 2006-10-30 17:34       ` Jun'ichi Nomura
  2006-10-30 18:16         ` Linus Torvalds
  0 siblings, 1 reply; 41+ messages in thread
From: Jun'ichi Nomura @ 2006-10-30 17:34 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Michael S. Tsirkin, Martin Lorenz, Pavel Machek, Adrian Bunk,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Randy.Dunlap

Hi Linus,

Linus Torvalds wrote:
> Actually, looking closer at the code, the patch seems to add _incorrect_ 
> error handling.
> 
> For example, look at bd_claim_by_kobject(): if the "bd_claim()" inside of 
> it succeeds, we used to always return success. Now, we don't necessarily 
> do that: we may have done a _successful_ "bd_claim()" call, but then we 
> return an error because something else failed, and now we're returning 
> with from bd_claim_by_kobject() with the bd_claim() done, but with an 
> error return (so the caller will _not_ call "bd_release()", and the 
> block_device will forever stay exclusive).
> 
> No?

You're right.

> Now, exactly why acpi stops working as a result, I don't know, but maybe 
> something else tries to get exclusive access to a swap partition, for 
> example, and now fails, causing some acpi sequence to not be set up? 
> Dunno.
> 
> So I suspect it should be reverted, but maybe somebody can see exactly 
> what goes wrong here.

Please revert the patch. I'll fix the wrong error handling.

I'm not sure reverting the patch solves the ACPI problem
because Michael's kernel seems not having any user of
bd_claim_by_kobject.

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 17:34       ` Jun'ichi Nomura
@ 2006-10-30 18:16         ` Linus Torvalds
  2006-10-30 18:35           ` Adrian Bunk
                             ` (2 more replies)
  0 siblings, 3 replies; 41+ messages in thread
From: Linus Torvalds @ 2006-10-30 18:16 UTC (permalink / raw)
  To: Jun'ichi Nomura
  Cc: Andrew Morton, len.brown, linux-pm, linux-acpi,
	Michael S. Tsirkin, Adrian Bunk, Martin Lorenz,
	Linux Kernel Mailing List

On Mon, 30 Oct 2006, Jun'ichi Nomura wrote:
> 
> Please revert the patch. I'll fix the wrong error handling.
> 
> I'm not sure reverting the patch solves the ACPI problem
> because Michael's kernel seems not having any user of
> bd_claim_by_kobject.

Yeah, doing a grep does seem to imply that there is no way that those 
changes could matter.

Michael, can you double-check? I think Jun'ichi is right - in your kernel, 
according to the config posted on bugzilla, I don't think there should be 
a single caller of bd_claim_by_disk, since CONFIG_MD is disabled.

So it does seem strange. But if you bisected to that patch, and it 
reliably does _not_ have problems with the patch reverted, maybe there is 
some strange preprocessor thing that makes "grep" not find the caller.

Michael, you also reported:

> Reset to d7dd8fd9557840162b724a8ac1366dd78a12dff seems to hide part of 
> the issue (I have ACPI after kernel build, but not after 
> suspend/resume).  Both reverting this patch, and reset to the parent of
> this patch seem to solve (or at least, hide) both problems for me (no 
> ACPI after suspend/resume and no ACPI after kernel build).

(where that "d7dd8f.." is actually missing the initial "4" - I think you 
cut-and-pasted things incorrectly). 

So I wonder.. You still had ACPI working _after_ the kernel build even 
with that patch in place, and it seems that suspend/resume is the real 
issue. Martin Lorenz reports on the same bugzilla entry, and he only has 
problems with suspend/resume.

I assume that "compile the kernel" just triggers some magic ACPI event 
(probably fan-related due to heat), and I wonder if the bisection faked 
you out because once you get "close enough" the differences are small 
enough that the kernel compile is quick and the heat event doesn't 
actually trigger?

See what I'm saying? Maybe the act of bisecting itself changed the 
results, and then when you just revert the patch, you end up in the same 
situation: you only recompile a small part (you only recompile that 
particular file), and the problem doesn't occur, so you'd think that the 
revert "fixed" it.

If it's heat-related, it should probably trigger by anything that does a 
lot of CPU (and perhaps disk) accesses, not just kernel builds. It might 
be good to try to find another test-case for it than a kernel recompile, 
one that doesn't depend on how much changed in the kernel..

		Linus

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 18:16         ` Linus Torvalds
@ 2006-10-30 18:35           ` Adrian Bunk
  2006-10-30 19:00             ` Michael S. Tsirkin
                               ` (2 more replies)
  2006-10-30 18:58           ` Michael S. Tsirkin
  2006-10-31 21:15           ` Michael S. Tsirkin
  2 siblings, 3 replies; 41+ messages in thread
From: Adrian Bunk @ 2006-10-30 18:35 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Jun'ichi Nomura, Michael S. Tsirkin, Martin Lorenz,
	Pavel Machek, Andrew Morton, Linux Kernel Mailing List, len.brown,
	linux-acpi, linux-pm, Randy.Dunlap

On Mon, Oct 30, 2006 at 10:16:34AM -0800, Linus Torvalds wrote:
>...
> I assume that "compile the kernel" just triggers some magic ACPI event 
> (probably fan-related due to heat), and I wonder if the bisection faked 
> you out because once you get "close enough" the differences are small 
> enough that the kernel compile is quick and the heat event doesn't 
> actually trigger?
> 
> See what I'm saying? Maybe the act of bisecting itself changed the 
> results, and then when you just revert the patch, you end up in the same 
> situation: you only recompile a small part (you only recompile that 
> particular file), and the problem doesn't occur, so you'd think that the 
> revert "fixed" it.
> 
> If it's heat-related, it should probably trigger by anything that does a 
> lot of CPU (and perhaps disk) accesses, not just kernel builds. It might 
> be good to try to find another test-case for it than a kernel recompile, 
> one that doesn't depend on how much changed in the kernel..

Martin's original bug report stated "now I loose ACPI events after 
suspend/resume. not every time, but roughly 3 out of 4 times."
This seems to support your theory.

But considering that two people have independently reported this as a 
2.6.19-rc regression for similar hardware (Michael for a T60 and Martin 
for an X60), a problem in the kernel seems to be involved.

Martin, Michael, can you send complete "dmesg -s 1000000" for both 
2.6.18.1 and a non-working 2.6.19-rc kernel after resume?
I don't have high hopes, but perhaps looking at the dmesg and/or 
diff'ing them might give a hint.

> 		Linus

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


^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 18:35           ` Adrian Bunk
@ 2006-10-30 19:00             ` Michael S. Tsirkin
  2006-10-30 19:06             ` Hugh Dickins
  2006-10-31 12:47             ` Martin Lorenz
  2 siblings, 0 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-10-30 19:00 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Linus Torvalds, Jun'ichi Nomura, Martin Lorenz, Pavel Machek,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Randy.Dunlap

Quoting r. Adrian Bunk <bunk@stusta.de>:
> Martin, Michael, can you send complete "dmesg -s 1000000" for both 
> 2.6.18.1 and a non-working 2.6.19-rc kernel after resume?
> I don't have high hopes, but perhaps looking at the dmesg and/or 
> diff'ing them might give a hint.

OK, I'll try to go back to this, just not today.

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 18:35           ` Adrian Bunk
  2006-10-30 19:00             ` Michael S. Tsirkin
@ 2006-10-30 19:06             ` Hugh Dickins
  2006-10-31 12:47             ` Martin Lorenz
  2 siblings, 0 replies; 41+ messages in thread
From: Hugh Dickins @ 2006-10-30 19:06 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Linus Torvalds, Jun'ichi Nomura, Michael S. Tsirkin,
	Martin Lorenz, Pavel Machek, Andrew Morton,
	Linux Kernel Mailing List, len.brown, linux-acpi, linux-pm,
	Randy.Dunlap

On Mon, 30 Oct 2006, Adrian Bunk wrote:
> 
> Martin's original bug report stated "now I loose ACPI events after 
> suspend/resume. not every time, but roughly 3 out of 4 times."
> This seems to support your theory.
> 
> But considering that two people have independently reported this as a 
> 2.6.19-rc regression for similar hardware (Michael for a T60 and Martin 
> for an X60), a problem in the kernel seems to be involved.

Add me to the list, on a T43p.  I believe it was happening in -rc1,
but seems worse with -rc3 and current.  But it's one of those things
which doesn't happen if you just go to test it out, only when you
need to suspend and resume for real.

Hugh 

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 18:35           ` Adrian Bunk
  2006-10-30 19:00             ` Michael S. Tsirkin
  2006-10-30 19:06             ` Hugh Dickins
@ 2006-10-31 12:47             ` Martin Lorenz
  2 siblings, 0 replies; 41+ messages in thread
From: Martin Lorenz @ 2006-10-31 12:47 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Linus Torvalds, Jun'ichi Nomura, Michael S. Tsirkin,
	Pavel Machek, Andrew Morton, Linux Kernel Mailing List, len.brown,
	linux-acpi, linux-pm, Randy.Dunlap

On Mon, Oct 30, 2006 at 07:35:22PM +0100, Adrian Bunk wrote:
> On Mon, Oct 30, 2006 at 10:16:34AM -0800, Linus Torvalds wrote:
[...]
> Martin, Michael, can you send complete "dmesg -s 1000000" for both 
> 2.6.18.1 and a non-working 2.6.19-rc kernel after resume?
> I don't have high hopes, but perhaps looking at the dmesg and/or 
> diff'ing them might give a hint.
> 
there are quite a few outputs from different kernels on my webpage
www.lorenz.eu.org/~mlo/kernel/?C=M;O=D

I hope I can go deeper into that tonight, but at the moment I can't promise
anything.


gruss
  mlo
--
Dipl.-Ing. Martin Lorenz

            They that can give up essential liberty 
	    to obtain a little temporary safety 
	    deserve neither liberty nor safety.
                                   Benjamin Franklin

please encrypt your mail to me
GnuPG key-ID: F1AAD37D
get it here:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D

ICQ UIN: 33588107

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 18:16         ` Linus Torvalds
  2006-10-30 18:35           ` Adrian Bunk
@ 2006-10-30 18:58           ` Michael S. Tsirkin
  2006-10-31 21:15           ` Michael S. Tsirkin
  2 siblings, 0 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-10-30 18:58 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Jun'ichi Nomura, Martin Lorenz, Pavel Machek, Adrian Bunk,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Randy.Dunlap

Quoting r. Linus Torvalds <torvalds@osdl.org>:
> Subject: Re: 2.6.19-rc3: known unfixed regressions (v3)
> 
> 
> 
> On Mon, 30 Oct 2006, Jun'ichi Nomura wrote:
> > 
> > Please revert the patch. I'll fix the wrong error handling.
> > 
> > I'm not sure reverting the patch solves the ACPI problem
> > because Michael's kernel seems not having any user of
> > bd_claim_by_kobject.
> 
> Yeah, doing a grep does seem to imply that there is no way that those 
> changes could matter.
> 
> Michael, can you double-check? I think Jun'ichi is right - in your kernel, 
> according to the config posted on bugzilla, I don't think there should be 
> a single caller of bd_claim_by_disk, since CONFIG_MD is disabled.

I will, just maybe not today.

> So it does seem strange. But if you bisected to that patch, and it 
> reliably does _not_ have problems with the patch reverted, maybe there is 
> some strange preprocessor thing that makes "grep" not find the caller.
> 
> Michael, you also reported:
> 
> > Reset to d7dd8fd9557840162b724a8ac1366dd78a12dff seems to hide part of 
> > the issue (I have ACPI after kernel build, but not after 
> > suspend/resume).  Both reverting this patch, and reset to the parent of
> > this patch seem to solve (or at least, hide) both problems for me (no 
> > ACPI after suspend/resume and no ACPI after kernel build).
> 
> (where that "d7dd8f.." is actually missing the initial "4" - I think you 
> cut-and-pasted things incorrectly). 

Yes.

> So I wonder.. You still had ACPI working _after_ the kernel build even 
> with that patch in place, and it seems that suspend/resume is the real 
> issue. Martin Lorenz reports on the same bugzilla entry, and he only has 
> problems with suspend/resume.
> 
> I assume that "compile the kernel" just triggers some magic ACPI event 
> (probably fan-related due to heat), and I wonder if the bisection faked 
> you out because once you get "close enough" the differences are small 
> enough that the kernel compile is quick and the heat event doesn't 
> actually trigger?
> 
> See what I'm saying? Maybe the act of bisecting itself changed the 
> results, and then when you just revert the patch, you end up in the same 
> situation: you only recompile a small part (you only recompile that 
> particular file), and the problem doesn't occur, so you'd think that the 
> revert "fixed" it.
> 
> If it's heat-related, it should probably trigger by anything that does a 
> lot of CPU (and perhaps disk) accesses, not just kernel builds. It might 
> be good to try to find another test-case for it than a kernel recompile, 
> one that doesn't depend on how much changed in the kernel..
> 
> 		Linus
> 
> 

Linus, I agree something fishy is going on, I'm just not sure how to debug.
It kind of looks like some memory corruption, or something.
I plan double-checking sometime later.

2 points I'd like to clarify:
1. When I git-bisected, I tested ACPI after suspend/resume,
   this is much faster to test but might be a separate issue.
   I really tested several times, and unless I repeated
   same mistake several times just switching between commit above 
   and its parent made ACPI after resume work/not work.

2. When I test kernel compile, I do
git clone -s ~/scm/linux-2.6
cd linux-2.6
make defconfig
make -j 4

so the build I do in testing is repeatable.

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc3: known unfixed regressions (v3)
  2006-10-30 18:16         ` Linus Torvalds
  2006-10-30 18:35           ` Adrian Bunk
  2006-10-30 18:58           ` Michael S. Tsirkin
@ 2006-10-31 21:15           ` Michael S. Tsirkin
  2 siblings, 0 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-10-31 21:15 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, len.brown, linux-pm, linux-acpi,
	Jun'ichi Nomura, Adrian Bunk, Martin Lorenz,
	Linux Kernel Mailing List

Quoting r. Linus Torvalds <torvalds@osdl.org>:
> Subject: Re: 2.6.19-rc3: known unfixed regressions (v3)
> 
> 
> 
> On Mon, 30 Oct 2006, Jun'ichi Nomura wrote:
> > 
> > Please revert the patch. I'll fix the wrong error handling.
> > 
> > I'm not sure reverting the patch solves the ACPI problem
> > because Michael's kernel seems not having any user of
> > bd_claim_by_kobject.
> 
> Yeah, doing a grep does seem to imply that there is no way that those 
> changes could matter.
> 
> Michael, can you double-check? I think Jun'ichi is right - in your kernel, 
> according to the config posted on bugzilla, I don't think there should be 
> a single caller of bd_claim_by_disk, since CONFIG_MD is disabled.

I double-checked, and of course you are right - the issues resurfaced after some
more use, even with the patch reverted.  I've written some scripts that do some
compiles from scratch, and suspend/resume several times.  Plan to try bi-secting
with that and see what that will come up with.

OTOH, from the discussion it seems just randomly pointing a finger at a patch
has uncovered some bugs - so maybe we should do this a bit more :)


-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* 2.6.19-rc <-> ThinkPads
  2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
  2006-10-30 15:27   ` Martin Lorenz
  2006-10-30 16:17   ` Jun'ichi Nomura
@ 2006-11-01  3:01   ` Adrian Bunk
  2006-11-01  3:15     ` Len Brown
                       ` (2 more replies)
  2 siblings, 3 replies; 41+ messages in thread
From: Adrian Bunk @ 2006-11-01  3:01 UTC (permalink / raw)
  To: Hugh Dickins
  Cc: Michael S. Tsirkin, Pavel Machek, Linus Torvalds, Andrew Morton,
	Linux Kernel Mailing List, len.brown, linux-acpi, linux-pm,
	Martin Lorenz

FYI:

Subject    : Thinkpad R50p: boot fail with (lapic && on_battery)
References : http://lkml.org/lkml/2006/10/31/333
Submitter  : Ernst Herzberg <earny@net4u.de>
Status     : submitter was asked to bisect

It seems to be completely unrelated (except that it's also a ThinkPad), 
but it might be worth a try whether a (non-SMP) kernel without APIC 
support fixes the issues after resume.

Hugh, your laptop seems to be a non-SMP laptop.
Do you have APIC enabled, and if yes does disabling help?

cu
Adrian


VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 19
EXTRAVERSION = -rc4
NAME=ThinkPad Killer


^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
@ 2006-11-01  3:15     ` Len Brown
  2006-11-01  5:11       ` Ernst Herzberg
  2006-11-01 16:36     ` Hugh Dickins
  2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
  2 siblings, 1 reply; 41+ messages in thread
From: Len Brown @ 2006-11-01  3:15 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Andrew Morton, linux-acpi, linux-pm, Michael S. Tsirkin,
	Hugh Dickins, Linus Torvalds, Martin Lorenz,
	Linux Kernel Mailing List

The BIOS disables the LAPIC for a reason.
A couple of years ago Linux made the mistake of enabling the LAPIC
that the BIOS disabled, and all hell broke loose.
We fixed that bug about a year ago, but left "lapic"
to force it on for those where forcing it to be enabled actually
works (eg. some folks want the NMI profiling on their IOAPIC-less  laptop)

But if you force the lapic to be enabled, you are running the system
in a mode not supported by the manufacturer and you are on your own.

I don't see an indication that this is a bug.
If it used to work and it is important to you,
 then run the old software where it used to work --
because chances are good that it worked by accident.

-Len

On Tuesday 31 October 2006 22:01, Adrian Bunk wrote:
> FYI:
> 
> Subject    : Thinkpad R50p: boot fail with (lapic && on_battery)
> References : http://lkml.org/lkml/2006/10/31/333
> Submitter  : Ernst Herzberg <earny@net4u.de>
> Status     : submitter was asked to bisect
> 
> It seems to be completely unrelated (except that it's also a ThinkPad), 
> but it might be worth a try whether a (non-SMP) kernel without APIC 
> support fixes the issues after resume.
> 
> Hugh, your laptop seems to be a non-SMP laptop.
> Do you have APIC enabled, and if yes does disabling help?
> 
> cu
> Adrian
> 
> 
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 19
> EXTRAVERSION = -rc4
> NAME=ThinkPad Killer
> 
> -
> 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/
> 

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  3:15     ` Len Brown
@ 2006-11-01  5:11       ` Ernst Herzberg
  2006-11-01  5:26         ` Linus Torvalds
  0 siblings, 1 reply; 41+ messages in thread
From: Ernst Herzberg @ 2006-11-01  5:11 UTC (permalink / raw)
  To: Len Brown
  Cc: Adrian Bunk, Hugh Dickins, Michael S. Tsirkin, Pavel Machek,
	Linus Torvalds, Andrew Morton, Linux Kernel Mailing List,
	linux-acpi, linux-pm, Martin Lorenz

On Wednesday 01 November 2006 04:15, Len Brown wrote:
> The BIOS disables the LAPIC for a reason.
> A couple of years ago Linux made the mistake of enabling the LAPIC
> that the BIOS disabled, and all hell broke loose.
> We fixed that bug about a year ago, but left "lapic"
> to force it on for those where forcing it to be enabled actually
> works (eg. some folks want the NMI profiling on their IOAPIC-less  laptop)
>
> But if you force the lapic to be enabled, you are running the system
> in a mode not supported by the manufacturer and you are on your own.
>
> I don't see an indication that this is a bug.
> If it used to work and it is important to you,
>  then run the old software where it used to work --
> because chances are good that it worked by accident.

Maybe. But why does it boot with AC connected and lapic enabled, bot not if AC 
is disconnected and lapic enabled? If have no problem to run this laptop 
without lapic, i don't relly need it. But i wondering that this happens only 
if the machine runs (by accident:) on battery.

still bisecting, will report the result.

<earny>

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  5:11       ` Ernst Herzberg
@ 2006-11-01  5:26         ` Linus Torvalds
  2006-11-01  5:54           ` Michael S. Tsirkin
  2006-11-01 13:50           ` Stefan Seyfried
  0 siblings, 2 replies; 41+ messages in thread
From: Linus Torvalds @ 2006-11-01  5:26 UTC (permalink / raw)
  To: Ernst Herzberg
  Cc: Andrew Morton, linux-acpi, linux-pm, Michael S. Tsirkin,
	Hugh Dickins, Linux Kernel Mailing List, Martin Lorenz,
	Adrian Bunk

On Wed, 1 Nov 2006, Ernst Herzberg wrote:
> 
> still bisecting, will report the result.

Figuring out what caused an apparent change of behaviour is definitely a 
good idea - it might give us some clue to what really is going on.

(Or it might not. Sometimes the patch that triggers changes really doesn't 
seem to have anything to do with anything, and it literally was just a 
latent bug that just happened to be exposed by something that had nothing 
to do with anything at all but perhaps timing. But that's pretty rare in 
the end. It happens, but it's definitely not the common case at all, and I 
think it's great that you're bisecting even if there is a possibility 
that we'll be left with a big "Huh? Whaa?" as the end result ;^)

		Linus

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  5:26         ` Linus Torvalds
@ 2006-11-01  5:54           ` Michael S. Tsirkin
  2006-11-01  6:16             ` Linus Torvalds
  2006-11-01  6:18             ` Michael S. Tsirkin
  2006-11-01 13:50           ` Stefan Seyfried
  1 sibling, 2 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-11-01  5:54 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, linux-pm, Ernst Herzberg, Andi Kleen,
	Linux Kernel Mailing List, linux-acpi, Hugh Dickins, Adrian Bunk,
	Martin Lorenz

Quoting r. Linus Torvalds <torvalds@osdl.org>:
> Subject: Re: 2.6.19-rc <-> ThinkPads
> 
> 
> 
> On Wed, 1 Nov 2006, Ernst Herzberg wrote:
> > 
> > still bisecting, will report the result.
> 
> Figuring out what caused an apparent change of behaviour is definitely a 
> good idea - it might give us some clue to what really is going on.

I've been bisecting ACPI/suspend thinkpad issue myself and I seem to get
eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2 good,
cf4c6a2f27f5db810b69dcb1da7f194489e8ff88 bad.

At least this makes some sense since the log speaks about suspend.  Problem is,
ACPI issues are in rare cases going away for a while for me so this needs more
testing before I can say for sure about the good part - I already had one false
negative.  What I plan to do is using eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2
for a couple of days and see how this works out.

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  5:54           ` Michael S. Tsirkin
@ 2006-11-01  6:16             ` Linus Torvalds
  2006-11-01 17:25               ` Andi Kleen
  2006-11-01 22:35               ` Bill Davidsen
  2006-11-01  6:18             ` Michael S. Tsirkin
  1 sibling, 2 replies; 41+ messages in thread
From: Linus Torvalds @ 2006-11-01  6:16 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Andrew Morton, linux-pm, Ernst Herzberg, Andi Kleen,
	Linux Kernel Mailing List, linux-acpi, Hugh Dickins, Adrian Bunk,
	Martin Lorenz

On Wed, 1 Nov 2006, Michael S. Tsirkin wrote:
> 
> I've been bisecting ACPI/suspend thinkpad issue myself and I seem to get
> eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2 good,
> cf4c6a2f27f5db810b69dcb1da7f194489e8ff88 bad.

Very interesting..

That commit cf4c6a2f on the face of it looks like an obvious cleanup, but 
looking closer, it actually changes the order of the apic writes in many 
cases (high word first -> low word first).

It also does something else that looks really really wrong: it turns an 
atomic "update ioapic and set irq-info" into two separate events, where 
interrupts can happen in between. Same goes for resume (instead of 
atomically changing all entries with the ioapic lock held, it now does 
them individually, and locks them individually).

I wonder if the order matters more, though. Andi? We _used_ to write the 
high word first, and I think the order matters. The low word contains the 
enable bit, for example, so when enabling an interrupt, you should write 
the low word last, when you disable it you should write the low word 
first.

And that's exactly what we _used_ to do, and it's what that particular 
commit totally and utterly _broke_.

I think that commit should either be reverted, or the code should be fixed 
to do the writes in the proper order. 

I suspect reverting it is the right thing to do - the patch only 
introduces bugs, an doesn't actually _fix_ anything, it just "cleans 
things up".

Andi, you need to be a hell of a lot more careful! Apparently x86-64 is 
also totally broken in this regard, because somebody didn't realize that 
the ordering _matters_.

		Linus

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  6:16             ` Linus Torvalds
@ 2006-11-01 17:25               ` Andi Kleen
  2006-11-01 18:12                 ` Michael S. Tsirkin
  2006-11-01 18:25                 ` Linus Torvalds
  2006-11-01 22:35               ` Bill Davidsen
  1 sibling, 2 replies; 41+ messages in thread
From: Andi Kleen @ 2006-11-01 17:25 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Michael S. Tsirkin, Ernst Herzberg, Len Brown, Adrian Bunk,
	Hugh Dickins, Pavel Machek, Andrew Morton,
	Linux Kernel Mailing List, linux-acpi, linux-pm, Martin Lorenz


> I suspect reverting it is the right thing to do - the patch only 
> introduces bugs, an doesn't actually _fix_ anything, it just "cleans 
> things up".

Ok please revert the i386 patch for now then if it fixes the ThinkPads. 
The x86-64 version should be probably fixed too, but doesn't cleanly. I will 
send you later a patch to fix this there properly.

-Andi

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 17:25               ` Andi Kleen
@ 2006-11-01 18:12                 ` Michael S. Tsirkin
  2006-11-01 18:25                 ` Linus Torvalds
  1 sibling, 0 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-11-01 18:12 UTC (permalink / raw)
  To: Andi Kleen
  Cc: Andrew Morton, linux-pm, Ernst Herzberg,
	Linux Kernel Mailing List, linux-acpi, Linus Torvalds,
	Hugh Dickins, Adrian Bunk, Martin Lorenz

Quoting r. Andi Kleen <ak@suse.de>:
> Subject: Re: 2.6.19-rc <-> ThinkPads
> 
> 
> > I suspect reverting it is the right thing to do - the patch only 
> > introduces bugs, an doesn't actually _fix_ anything, it just "cleans 
> > things up".
> 
> Ok please revert the i386 patch for now then if it fixes the ThinkPads. 
> The x86-64 version should be probably fixed too, but doesn't cleanly. I will 
> send you later a patch to fix this there properly.

Could you sent the patch so I can test it, pls?
git revert creates conflicts.

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 17:25               ` Andi Kleen
  2006-11-01 18:12                 ` Michael S. Tsirkin
@ 2006-11-01 18:25                 ` Linus Torvalds
  2006-11-01 19:33                   ` Michael S. Tsirkin
  2006-11-01 19:34                   ` Andi Kleen
  1 sibling, 2 replies; 41+ messages in thread
From: Linus Torvalds @ 2006-11-01 18:25 UTC (permalink / raw)
  To: Andi Kleen
  Cc: Andrew Morton, linux-pm, Ernst Herzberg,
	Linux Kernel Mailing List, Adrian Bunk, linux-acpi,
	Michael S. Tsirkin, Hugh Dickins, Martin Lorenz



On Wed, 1 Nov 2006, Andi Kleen wrote:
>
> Ok please revert the i386 patch for now then if it fixes the ThinkPads. 
> The x86-64 version should be probably fixed too, but doesn't cleanly. I will 
> send you later a patch to fix this there properly.

Actually, I should have just fixed the ordering. I did some cleanups too, 
but those are unrelated (except in the sense that I wanted to look at the 
assembly code, and the cleanups made the code generation at least half-way 
sane!)

I've pushed out the changes, but here is the part that may or may not 
matter for anybody who wants to test it if they don't use git or if it 
hasn't mirrored out yet. Michael? Martin?

Andi: I think the patches should work pretty much as-is for x86-64 too, 
since all the issues would seem to be similar. 

I'm not entirely happy with "ioapic_write_entry()" now either (if we 
change an entry that was already unmasked, we should probably mask it 
first by writing the low word with the mask bit set, then write the high 
word, and then write the low word again), but 

 - this makes us match the ordering we _used_ to have, so if the cleanup 
   broke things for people, this should unbreak it, and at least not be 
   any worse than it used to be.

 - when we write new unmasked entries, they all _should_ have been masked 
   before, so hopefully the "change a unmasked entry while it's unmasked" 
   case doesn't actually ever happen. But I didn't actually _check_.

Somebody should look into that case. Does anybody feel like they want to 
learn more about the IO-APIC? Halloween is over and gone, but if you want 
to scare small children _next_ year, telling them about the IO-APIC is 
likely a good strategy.

		Linus

---
commit f9dadfa71bc594df09044da61d1c72701121d802
Author: Linus Torvalds <torvalds@macmini.osdl.org>
Date:   Wed Nov 1 10:05:35 2006 -0800

    i386: write IO APIC irq routing entries in correct order
    
    Since the "mask" bit is in the low word, when we write a new entry, we
    need to write the high word first, before we potentially unmask it.
    
    The exception is when we actually want to mask the interrupt, in which
    case we want to write the low word first to make sure that the high word
    doesn't change while the interrupt routing is still active.
    
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>

diff --git a/arch/i386/kernel/io_apic.c b/arch/i386/kernel/io_apic.c
index eb10bd5..507983c 100644
--- a/arch/i386/kernel/io_apic.c
+++ b/arch/i386/kernel/io_apic.c
@@ -147,12 +147,34 @@ static struct IO_APIC_route_entry ioapic
 	return eu.entry;
 }
 
+/*
+ * When we write a new IO APIC routing entry, we need to write the high
+ * word first! If the mask bit in the low word is clear, we will enable
+ * the interrupt, and we need to make sure the entry is fully populated
+ * before that happens.
+ */
 static void ioapic_write_entry(int apic, int pin, struct IO_APIC_route_entry e)
 {
 	unsigned long flags;
 	union entry_union eu;
 	eu.entry = e;
 	spin_lock_irqsave(&ioapic_lock, flags);
+	io_apic_write(apic, 0x11 + 2*pin, eu.w2);
+	io_apic_write(apic, 0x10 + 2*pin, eu.w1);
+	spin_unlock_irqrestore(&ioapic_lock, flags);
+}
+
+/*
+ * When we mask an IO APIC routing entry, we need to write the low
+ * word first, in order to set the mask bit before we change the
+ * high bits!
+ */
+static void ioapic_mask_entry(int apic, int pin)
+{
+	unsigned long flags;
+	union entry_union eu = { .entry.mask = 1 };
+
+	spin_lock_irqsave(&ioapic_lock, flags);
 	io_apic_write(apic, 0x10 + 2*pin, eu.w1);
 	io_apic_write(apic, 0x11 + 2*pin, eu.w2);
 	spin_unlock_irqrestore(&ioapic_lock, flags);
@@ -274,9 +296,7 @@ static void clear_IO_APIC_pin(unsigned i
 	/*
 	 * Disable it in the IO-APIC irq-routing table:
 	 */
-	memset(&entry, 0, sizeof(entry));
-	entry.mask = 1;
-	ioapic_write_entry(apic, pin, entry);
+	ioapic_mask_entry(apic, pin);
 }
 
 static void clear_IO_APIC (void)

^ permalink raw reply related	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 18:25                 ` Linus Torvalds
@ 2006-11-01 19:33                   ` Michael S. Tsirkin
  2006-11-01 19:44                     ` Linus Torvalds
  2006-11-01 19:34                   ` Andi Kleen
  1 sibling, 1 reply; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-11-01 19:33 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, linux-pm, Ernst Herzberg, Andi Kleen,
	Linux Kernel Mailing List, linux-acpi, Hugh Dickins, Adrian Bunk,
	Martin Lorenz

Quoting r. Linus Torvalds <torvalds@osdl.org>:
> Subject: Re: 2.6.19-rc <-> ThinkPads
> 
> 
> 
> On Wed, 1 Nov 2006, Andi Kleen wrote:
> >
> > Ok please revert the i386 patch for now then if it fixes the ThinkPads. 
> > The x86-64 version should be probably fixed too, but doesn't cleanly. I will 
> > send you later a patch to fix this there properly.
> 
> Actually, I should have just fixed the ordering. I did some cleanups too, 
> but those are unrelated (except in the sense that I wanted to look at the 
> assembly code, and the cleanups made the code generation at least half-way 
> sane!)
> 
> I've pushed out the changes, but here is the part that may or may not 
> matter for anybody who wants to test it if they don't use git or if it 
> hasn't mirrored out yet. Michael? Martin?

I pulled the latest git, and seems to work for me, thanks.
This still could be a false negative (happened already) so I'll
continue using this, and will post the results.

> Andi: I think the patches should work pretty much as-is for x86-64 too, 
> since all the issues would seem to be similar. 
> 
> I'm not entirely happy with "ioapic_write_entry()" now either (if we 
> change an entry that was already unmasked, we should probably mask it 
> first by writing the low word with the mask bit set, then write the high 
> word, and then write the low word again), but 
> 
>  - this makes us match the ordering we _used_ to have, so if the cleanup 
>    broke things for people, this should unbreak it, and at least not be 
>    any worse than it used to be.
> 
>  - when we write new unmasked entries, they all _should_ have been masked 
>    before, so hopefully the "change a unmasked entry while it's unmasked" 
>    case doesn't actually ever happen. But I didn't actually _check_.
> 
> Somebody should look into that case. Does anybody feel like they want to 
> learn more about the IO-APIC? Halloween is over and gone, but if you want 
> to scare small children _next_ year, telling them about the IO-APIC is 
> likely a good strategy.
> 
> 		Linus

Hmm, sounds interesting :)
Is this a good place to start (I'm feeling lucky hit for IO-APIC)?
http://www.intel.com/design/chipsets/datashts/290566.htm

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 19:33                   ` Michael S. Tsirkin
@ 2006-11-01 19:44                     ` Linus Torvalds
  0 siblings, 0 replies; 41+ messages in thread
From: Linus Torvalds @ 2006-11-01 19:44 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Andrew Morton, linux-pm, Ernst Herzberg, Andi Kleen,
	Linux Kernel Mailing List, linux-acpi, Hugh Dickins, Adrian Bunk,
	Martin Lorenz



On Wed, 1 Nov 2006, Michael S. Tsirkin wrote:

> > I've pushed out the changes, but here is the part that may or may not 
> > matter for anybody who wants to test it if they don't use git or if it 
> > hasn't mirrored out yet. Michael? Martin?
> 
> I pulled the latest git, and seems to work for me, thanks.
> This still could be a false negative (happened already) so I'll
> continue using this, and will post the results.

Ok, thanks.

> > Somebody should look into that case. Does anybody feel like they want to 
> > learn more about the IO-APIC? Halloween is over and gone, but if you want 
> > to scare small children _next_ year, telling them about the IO-APIC is 
> > likely a good strategy.
> 
> Hmm, sounds interesting :)
> Is this a good place to start (I'm feeling lucky hit for IO-APIC)?
> http://www.intel.com/design/chipsets/datashts/290566.htm

Yeah, that's the datasheet. Note that a lot of the IO-APIC complexity is 
not so much in the programming interfaces themselves, but in keeping track 
of how the heck the thing is connected (ie ExtINT vs SCI vs "normal apic 
interrupt" etc).

		Linus

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 18:25                 ` Linus Torvalds
  2006-11-01 19:33                   ` Michael S. Tsirkin
@ 2006-11-01 19:34                   ` Andi Kleen
  2006-11-01 19:52                     ` Linus Torvalds
  1 sibling, 1 reply; 41+ messages in thread
From: Andi Kleen @ 2006-11-01 19:34 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Michael S. Tsirkin, Ernst Herzberg, Len Brown, Adrian Bunk,
	Hugh Dickins, Pavel Machek, Andrew Morton,
	Linux Kernel Mailing List, linux-acpi, linux-pm, Martin Lorenz

On Wednesday 01 November 2006 19:25, Linus Torvalds wrote:
> 
> On Wed, 1 Nov 2006, Andi Kleen wrote:
> >
> > Ok please revert the i386 patch for now then if it fixes the ThinkPads. 
> > The x86-64 version should be probably fixed too, but doesn't cleanly. I will 
> > send you later a patch to fix this there properly.
> 
> Actually, I should have just fixed the ordering. I did some cleanups too, 
> but those are unrelated (except in the sense that I wanted to look at the 
> assembly code, and the cleanups made the code generation at least half-way 
> sane!)

Thanks.

Some of them are still different than the old code now, but that's probably
ok.

But the irq race you pointed out is still there (unless you fixed it in a differnet patch) 
I don't know if it makes
a difference, but here is a patch to fix it.

-Andi

Fix race in IO-APIC routing entry setup.

Interrupt could happen between setting the IO-APIC entry
and setting its interrupt data.

Pointed out by Linus.

Signed-off-by: Andi Kleen <ak@suse.de>

Index: linux/arch/i386/kernel/io_apic.c
===================================================================
--- linux.orig/arch/i386/kernel/io_apic.c
+++ linux/arch/i386/kernel/io_apic.c
@@ -1298,10 +1298,12 @@ static void __init setup_IO_APIC_irqs(vo
 			if (!apic && (irq < 16))
 				disable_8259A_irq(irq);
 		}
+		local_irq_save(flags);
 		ioapic_write_entry(apic, pin, entry);
-		spin_lock_irqsave(&ioapic_lock, flags);
+		spin_lock(&ioapic_lock);
 		set_native_irq_info(irq, TARGET_CPUS);
-		spin_unlock_irqrestore(&ioapic_lock, flags);
+		spin_unlock(&ioapic_lock);
+		local_irq_restore(flags);
 	}
 	}
 

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 19:34                   ` Andi Kleen
@ 2006-11-01 19:52                     ` Linus Torvalds
  2006-11-01 21:15                       ` Andi Kleen
  0 siblings, 1 reply; 41+ messages in thread
From: Linus Torvalds @ 2006-11-01 19:52 UTC (permalink / raw)
  To: Andi Kleen
  Cc: Andrew Morton, linux-pm, Ernst Herzberg,
	Linux Kernel Mailing List, Adrian Bunk, linux-acpi,
	Michael S. Tsirkin, Hugh Dickins, Martin Lorenz

On Wed, 1 Nov 2006, Andi Kleen wrote:
> 
> Fix race in IO-APIC routing entry setup.
> 
> Interrupt could happen between setting the IO-APIC entry
> and setting its interrupt data.

This doesn't fix anything at all.

The interrupt can come in on another CPU, and if we end up having an 
affinity change due to that, we then have "set_ioapic_affinity_irq()" 
called on that other irq, and it might get to mess with the cpumask 
because we dropped the ioapic_lock.

In other words, the problem is not that interrupts were re-enabled, the 
problem is literally that the locking is _wrong_. 

It's a small window, but we simply should not release the ioapic_lock in 
between setting the routing and doing the "set_native_irq_info()" call.

So I think doing the locking inside "ioapic_write_entry()" is simply 
fundamentally wrong. When you did the cleanup, your commit message talked 
about how it might add a few more lock/unlock things:

    In a few cases the IO APIC lock is taken more often now, but this
    isn't a problem because it's all initialization/shutdown only
    slow path code.

but the point is, this is not about "performance". It's about 
_correctness_.

			Linus

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01 19:52                     ` Linus Torvalds
@ 2006-11-01 21:15                       ` Andi Kleen
  0 siblings, 0 replies; 41+ messages in thread
From: Andi Kleen @ 2006-11-01 21:15 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, linux-pm, Ernst Herzberg,
	Linux Kernel Mailing List, Adrian Bunk, linux-acpi,
	Michael S. Tsirkin, Hugh Dickins, Martin Lorenz

On Wednesday 01 November 2006 20:52, Linus Torvalds wrote:
> 
> On Wed, 1 Nov 2006, Andi Kleen wrote:
> > 
> > Fix race in IO-APIC routing entry setup.
> > 
> > Interrupt could happen between setting the IO-APIC entry
> > and setting its interrupt data.
> 
> This doesn't fix anything at all.
> 
> The interrupt can come in on another CPU, 

Only BP should be active at this point. At least not until
we implement IO-APIC hotplug, but so far that isn't there.

Ok in theory the BIOS could have put the other CPUs into
weird states where they are still doing something and causing
interrupts, but that would be a BIOS bug.

I suppose it could happen with kexec, but that has still
other problems anyways.

The common case of no kexec shouldn't be affected at least.

-Andi

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  6:16             ` Linus Torvalds
  2006-11-01 17:25               ` Andi Kleen
@ 2006-11-01 22:35               ` Bill Davidsen
  1 sibling, 0 replies; 41+ messages in thread
From: Bill Davidsen @ 2006-11-01 22:35 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, linux-pm, Martin Lorenz, linux-acpi,
	Ernst Herzberg, Hugh Dickins, Adrian Bunk, Andi Kleen,
	Linux Kernel Mailing List

Linus Torvalds wrote:

> I wonder if the order matters more, though. Andi? We _used_ to write the 
> high word first, and I think the order matters. The low word contains the 
> enable bit, for example, so when enabling an interrupt, you should write 
> the low word last, when you disable it you should write the low word 
> first.
> 
Although you can argue that anyone coding here should be a guru, in 
practice things this subtle really would be helped by a comment in the 
initial code. I don't agree that "if it was hard to write it should be 
hard to understand." Clearly several competent people missed this 
dependency, or the patch would not have gone in.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  5:54           ` Michael S. Tsirkin
  2006-11-01  6:16             ` Linus Torvalds
@ 2006-11-01  6:18             ` Michael S. Tsirkin
  2006-11-01  9:33               ` Pavel Machek
  2006-11-01 17:17               ` Andi Kleen
  1 sibling, 2 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-11-01  6:18 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, linux-pm, Ernst Herzberg, Andi Kleen,
	Linux Kernel Mailing List, linux-acpi, Hugh Dickins, Adrian Bunk,
	Martin Lorenz

Quoting r. Michael S. Tsirkin <mst@mellanox.co.il>:
> What I plan to do is using eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2
> for a couple of days and see how this works out.

Ugh. Unfortunately in that kernel version, the e1000 driver says
the eeprom checksum is bad (works fine with 2.6.19-rc3).
So, I tried some suspends/resumes and things seem to work, but
I won't be able to test it under real use conditions.

But maybe its another red herring?
Andi, could you maybe look at that commit and tell me whether
it could cause troubles with ACPI after suspend/resume even
theoretically?

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  6:18             ` Michael S. Tsirkin
@ 2006-11-01  9:33               ` Pavel Machek
  2006-11-01 12:02                 ` Michael S. Tsirkin
  2006-11-01 17:17               ` Andi Kleen
  1 sibling, 1 reply; 41+ messages in thread
From: Pavel Machek @ 2006-11-01  9:33 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Linus Torvalds, Ernst Herzberg, Len Brown, Adrian Bunk,
	Hugh Dickins, Andrew Morton, Linux Kernel Mailing List,
	linux-acpi, linux-pm, Martin Lorenz, Andi Kleen

On Wed 2006-11-01 08:18:57, Michael S. Tsirkin wrote:
> Quoting r. Michael S. Tsirkin <mst@mellanox.co.il>:
> > What I plan to do is using eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2
> > for a couple of days and see how this works out.
> 
> Ugh. Unfortunately in that kernel version, the e1000 driver says
> the eeprom checksum is bad (works fine with 2.6.19-rc3).
> So, I tried some suspends/resumes and things seem to work, but
> I won't be able to test it under real use conditions.

Just comment out the eeprom checksum check...

									Pavel

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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  9:33               ` Pavel Machek
@ 2006-11-01 12:02                 ` Michael S. Tsirkin
  0 siblings, 0 replies; 41+ messages in thread
From: Michael S. Tsirkin @ 2006-11-01 12:02 UTC (permalink / raw)
  To: Pavel Machek
  Cc: Andrew Morton, linux-pm, Ernst Herzberg, Andi Kleen,
	Linux Kernel Mailing List, linux-acpi, Linus Torvalds,
	Hugh Dickins, Adrian Bunk, Martin Lorenz

Quoting Pavel Machek <pavel@ucw.cz>:
> > > What I plan to do is using eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2
> > > for a couple of days and see how this works out.
> > 
> > Ugh. Unfortunately in that kernel version, the e1000 driver says
> > the eeprom checksum is bad (works fine with 2.6.19-rc3).
> > So, I tried some suspends/resumes and things seem to work, but
> > I won't be able to test it under real use conditions.
> 
> Just comment out the eeprom checksum check...
> 

Right, that worked, thanks.
I'm running on eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2 now, seems to be fine
so far.

-- 
MST

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  6:18             ` Michael S. Tsirkin
  2006-11-01  9:33               ` Pavel Machek
@ 2006-11-01 17:17               ` Andi Kleen
  1 sibling, 0 replies; 41+ messages in thread
From: Andi Kleen @ 2006-11-01 17:17 UTC (permalink / raw)
  To: Michael S. Tsirkin
  Cc: Linus Torvalds, Ernst Herzberg, Len Brown, Adrian Bunk,
	Hugh Dickins, Pavel Machek, Andrew Morton,
	Linux Kernel Mailing List, linux-acpi, linux-pm, Martin Lorenz

On Wednesday 01 November 2006 07:18, Michael S. Tsirkin wrote:
> Quoting r. Michael S. Tsirkin <mst@mellanox.co.il>:
> > What I plan to do is using eea0e11c1f0d6ef89e64182b2f1223a4ca2b74a2
> > for a couple of days and see how this works out.
> 
> Ugh. Unfortunately in that kernel version, the e1000 driver says
> the eeprom checksum is bad (works fine with 2.6.19-rc3).
> So, I tried some suspends/resumes and things seem to work, but
> I won't be able to test it under real use conditions.
> 
> But maybe its another red herring?
> Andi, could you maybe look at that commit and tell me whether
> it could cause troubles with ACPI after suspend/resume even
> theoretically?

It touches suspend/resume so it could break something theoretically.

-Andi

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  5:26         ` Linus Torvalds
  2006-11-01  5:54           ` Michael S. Tsirkin
@ 2006-11-01 13:50           ` Stefan Seyfried
  1 sibling, 0 replies; 41+ messages in thread
From: Stefan Seyfried @ 2006-11-01 13:50 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Andrew Morton, linux-acpi, linux-pm, Michael S. Tsirkin,
	Hugh Dickins, Linux Kernel Mailing List, Martin Lorenz,
	Adrian Bunk, Ernst Herzberg

On Tue, Oct 31, 2006 at 09:26:12PM -0800, Linus Torvalds wrote:
> (Or it might not. Sometimes the patch that triggers changes really doesn't 
> seem to have anything to do with anything, and it literally was just a 
> latent bug that just happened to be exposed by something that had nothing 
> to do with anything at all but perhaps timing.

Especially when "booting on AC works, but on battery it doesn't", (or the
other way round), looking at timing problems seems sane to me.
-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 
-
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

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads
  2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
  2006-11-01  3:15     ` Len Brown
@ 2006-11-01 16:36     ` Hugh Dickins
  2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
  2 siblings, 0 replies; 41+ messages in thread
From: Hugh Dickins @ 2006-11-01 16:36 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Andrew Morton, len.brown, linux-pm, linux-acpi,
	Michael S. Tsirkin, Linus Torvalds, Martin Lorenz,
	Linux Kernel Mailing List

On Wed, 1 Nov 2006, Adrian Bunk wrote:
> 
> Subject    : Thinkpad R50p: boot fail with (lapic && on_battery)
> References : http://lkml.org/lkml/2006/10/31/333
> Submitter  : Ernst Herzberg <earny@net4u.de>
> Status     : submitter was asked to bisect
> 
> It seems to be completely unrelated (except that it's also a ThinkPad), 
> but it might be worth a try whether a (non-SMP) kernel without APIC 
> support fixes the issues after resume.
> 
> Hugh, your laptop seems to be a non-SMP laptop.

That's right.

> Do you have APIC enabled, and if yes does disabling help?

Yes, I do.  But I've just tried booting with "noapic" and with "nolapic"
and with "noapic nolapic", but none of those make any difference.

(That is, they make no difference to the FnF4-ineffective-after-resume
behaviour that I'm finding fairly easy to reproduce at will today on
2.6.19-rc4; whereas yesterday it was seeming to me that -rc4 was much
better than -rc3 in this regard.  Something I have learnt today is that
the key is ineffective "for a while", but may become effective later.
It's conceivable that the behaviour I'm reproducing today is not quite
the same as what I was experiencing earlier with real-life suspends.)

More to the point, with great hope in my heart, I've tried backing
out Andi's git-cf4c6a2f27f5db810b69dcb1da7f194489e8ff88.patch
to arch/i386/kernel/io_apic.c, the one which Michael and Linus have
homed in on.  But sadly that makes no difference for me: I'd better
get down to my own bisection.

Hugh

^ permalink raw reply	[flat|nested] 41+ messages in thread

* 2.6.19-rc <-> ThinkPads, summary
  2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
  2006-11-01  3:15     ` Len Brown
  2006-11-01 16:36     ` Hugh Dickins
@ 2006-11-04  3:49     ` Adrian Bunk
  2006-11-04 13:51       ` Hugh Dickins
                         ` (2 more replies)
  2 siblings, 3 replies; 41+ messages in thread
From: Adrian Bunk @ 2006-11-04  3:49 UTC (permalink / raw)
  To: Hugh Dickins, Michael S. Tsirkin, Pavel Machek, Linus Torvalds,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Martin Lorenz, Andi Kleen, discuss, Russell King,
	linux-serial, linux-thinkpad, Ernst Herzberg

As far as I can see, the 2.6.19-rc ThinkPad situation is still 
confusing and we don't even know how many different bugs we are 
chasing...

Below is all the information I have found, plus some questions for the 
four people who reported problems that might hopefully bring us nearer 
to solutions.


Michael S. Tsirkin:
- ThinkPad T60 not coming out of suspend to RAM
- broken by commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
  ("i386: Factor out common io apic routing entry access")
- question: Did the post -rc4 arch/i386/kernel/io_apic.c changes fix it?


Ernst Herzberg:
- ThinkPad R50p: boot fail with (lapic && on_battery)
- kernel compiled without cardbus support works
- question: Does reverting  the bisected
            commit 1fbbac4bcb03033d325c71fc7273aa0b9c1d9a03 
            ("serial_cs: convert multi-port table to quirk table")
            fix the problem?
- question: Does reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
            ("i386: Factor out common io apic routing entry access") help?
- question: If yes, did the post -rc4 arch/i386/kernel/io_apic.c changes
            fix it?


Hugh Dickins:
- ThinkPad T43p
- booting with "noapic nolapic" didn't make any difference
- reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
  ("i386: Factor out common io apic routing entry access") didn't help
- question: Was your bisecting successful?


Martin Lorenz:
- ThinkPad X60: lose ACPI events after suspend/resume
                not every time, but roughly 3 out of 4 times
- question: Does reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
            ("i386: Factor out common io apic routing entry access")
            in -rc4 help?
- question: If yes, did the post -rc4 arch/i386/kernel/io_apic.c changes
            fix it?


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


^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads, summary
  2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
@ 2006-11-04 13:51       ` Hugh Dickins
  2006-11-04 14:04       ` Russell King
  2006-11-17  1:53       ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg
  2 siblings, 0 replies; 41+ messages in thread
From: Hugh Dickins @ 2006-11-04 13:51 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Michael S. Tsirkin, Pavel Machek, Linus Torvalds, Andrew Morton,
	Linux Kernel Mailing List, len.brown, linux-acpi, linux-pm,
	Martin Lorenz, Andi Kleen, discuss, Russell King, linux-serial,
	linux-thinkpad, Ernst Herzberg

On Sat, 4 Nov 2006, Adrian Bunk wrote:
> 
> Hugh Dickins:
> - ThinkPad T43p
> - booting with "noapic nolapic" didn't make any difference
> - reverting commit cf4c6a2f27f5db810b69dcb1da7f194489e8ff88
>   ("i386: Factor out common io apic routing entry access") didn't help
> - question: Was your bisecting successful?

Not quite what I'd call successful, but I think I've just about arrived
at some kind of conclusion.

Short summary: forget my complaint, assume it's fixed in current -git.

Boring version:

I think I have two slightly different, perhaps not unrelated, issues.
One manifested in habitual usage, to and from work, suspending for quiet
at home, etc, etc.  As 2.6.19-rc progressed, I more and more often found
it impossible to re-suspend after the first time: suspend key ignored.
rc3 seemed worst, rc4 at first seemed okay, then not, perhaps because...

In order to bisect on this, I had to speed up the testing from a day
or two to a few minutes; and I'm now thinking that this may have
focussed on a different problem.  After several reset bisections
converging on absurd patches (e.g. sparse annotations or unbuilt
sources), I grew even more suspicious of my "good" cases, and
yesterday found even 2.6.18 and 2.6.17 (didn't try earlier) behave
like this: occasionally the suspend key gets ignored for about one
minute (in the few cases I timed).

So whatever I was bisecting on, it's not a regression in 2.6.19.
It may be a software bug, it would be worth fixing if I can work
it out (though the pleasure of bisection was not having to think,
I've grown addicted); but it's not anything to hold up 2.6.19.

And as far as habitual usage goes, experience so far with -gits
post rc4 suggests that that problem has gone away: it's a little
too early to tell for sure, but I've not had to go back to using
2.6.18 to avoid it yet.

Hugh

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads, summary
  2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
  2006-11-04 13:51       ` Hugh Dickins
@ 2006-11-04 14:04       ` Russell King
  2006-11-05  6:23         ` Adrian Bunk
  2006-11-17  1:53       ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg
  2 siblings, 1 reply; 41+ messages in thread
From: Russell King @ 2006-11-04 14:04 UTC (permalink / raw)
  To: Adrian Bunk
  Cc: Hugh Dickins, Michael S. Tsirkin, Pavel Machek, Linus Torvalds,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Martin Lorenz, Andi Kleen, discuss, linux-serial,
	linux-thinkpad, Ernst Herzberg

On Sat, Nov 04, 2006 at 04:49:07AM +0100, Adrian Bunk wrote:
> As far as I can see, the 2.6.19-rc ThinkPad situation is still 
> confusing and we don't even know how many different bugs we are 
> chasing...

Why am I copied on this?  Nothing jumps out as being in any area of my
interest (which today is limited to ARM architecture only.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads, summary
  2006-11-04 14:04       ` Russell King
@ 2006-11-05  6:23         ` Adrian Bunk
  0 siblings, 0 replies; 41+ messages in thread
From: Adrian Bunk @ 2006-11-05  6:23 UTC (permalink / raw)
  To: Hugh Dickins, Michael S. Tsirkin, Pavel Machek, Linus Torvalds,
	Andrew Morton, Linux Kernel Mailing List, len.brown, linux-acpi,
	linux-pm, Martin Lorenz, Andi Kleen, discuss, linux-serial,
	linux-thinkpad, Ernst Herzberg

On Sat, Nov 04, 2006 at 02:04:40PM +0000, Russell King wrote:
> On Sat, Nov 04, 2006 at 04:49:07AM +0100, Adrian Bunk wrote:
> > As far as I can see, the 2.6.19-rc ThinkPad situation is still 
> > confusing and we don't even know how many different bugs we are 
> > chasing...
> 
> Why am I copied on this?  Nothing jumps out as being in any area of my
> interest (which today is limited to ARM architecture only.)

Ernst bisected his problem to your
commit 1fbbac4bcb03033d325c71fc7273aa0b9c1d9a03 
("serial_cs: convert multi-port table to quirk table").

It might be a false positive of the bisecting, but if it turns out to 
actually cause problems it was your commit.

> Russell King

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


^ permalink raw reply	[flat|nested] 41+ messages in thread

* Re: 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report)
  2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
  2006-11-04 13:51       ` Hugh Dickins
  2006-11-04 14:04       ` Russell King
@ 2006-11-17  1:53       ` Mark Stosberg
  2 siblings, 0 replies; 41+ messages in thread
From: Mark Stosberg @ 2006-11-17  1:53 UTC (permalink / raw)
  To: linux-thinkpad; +Cc: linux-kernel, linux-acpi, linux-pm, discuss

Adrian Bunk wrote:
> As far as I can see, the 2.6.19-rc ThinkPad situation is still 
> confusing and we don't even know how many different bugs we are 
> chasing...

Hello,

I just hoped on this list to see what "ThinkPad" discussion there was.
Here my own observations:

Using Mandriva 2006 with 2.6.12, ACPI suspend/resume works great on a
ThinkPad T20. It didn't work with 2.6.14, and it doesn't work with
2.6.17 with Mandriva. Further, it doesn't seem to work with on some
ThinkPads with Ubuntu and 2.6.15 and 2.6.17 either, as this now-lengthy
bug report documents:

https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/50031

I added a comment there encouraging the other bug reporters to include
the kind of information requested on the ACPI website, but so far no have.

Personally, I'm still using 2.6.12 daily because of this regression.

I'm interested to help resolve it, but am not currently tracking the
latest kernel sources.

I realize this bug report is a bit out of date with respect to 2.6.19,
but as another poster suggested, this could simply indicate that at
least one regressions may not be recent.

   Mark

-- 
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad

^ permalink raw reply	[flat|nested] 41+ messages in thread

end of thread, other threads:[~2006-11-17  1:53 UTC | newest]

Thread overview: 41+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20061029231358.GI27968@stusta.de>
2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
2006-10-30 15:27   ` Martin Lorenz
2006-10-30 16:17   ` Jun'ichi Nomura
2006-10-30 16:32     ` Michael S. Tsirkin
2006-10-30 17:20       ` Jun'ichi Nomura
2006-10-30 17:54         ` Michael S. Tsirkin
2006-10-30 16:44     ` Linus Torvalds
2006-10-30 17:34       ` Jun'ichi Nomura
2006-10-30 18:16         ` Linus Torvalds
2006-10-30 18:35           ` Adrian Bunk
2006-10-30 19:00             ` Michael S. Tsirkin
2006-10-30 19:06             ` Hugh Dickins
2006-10-31 12:47             ` Martin Lorenz
2006-10-30 18:58           ` Michael S. Tsirkin
2006-10-31 21:15           ` Michael S. Tsirkin
2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
2006-11-01  3:15     ` Len Brown
2006-11-01  5:11       ` Ernst Herzberg
2006-11-01  5:26         ` Linus Torvalds
2006-11-01  5:54           ` Michael S. Tsirkin
2006-11-01  6:16             ` Linus Torvalds
2006-11-01 17:25               ` Andi Kleen
2006-11-01 18:12                 ` Michael S. Tsirkin
2006-11-01 18:25                 ` Linus Torvalds
2006-11-01 19:33                   ` Michael S. Tsirkin
2006-11-01 19:44                     ` Linus Torvalds
2006-11-01 19:34                   ` Andi Kleen
2006-11-01 19:52                     ` Linus Torvalds
2006-11-01 21:15                       ` Andi Kleen
2006-11-01 22:35               ` Bill Davidsen
2006-11-01  6:18             ` Michael S. Tsirkin
2006-11-01  9:33               ` Pavel Machek
2006-11-01 12:02                 ` Michael S. Tsirkin
2006-11-01 17:17               ` Andi Kleen
2006-11-01 13:50           ` Stefan Seyfried
2006-11-01 16:36     ` Hugh Dickins
2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
2006-11-04 13:51       ` Hugh Dickins
2006-11-04 14:04       ` Russell King
2006-11-05  6:23         ` Adrian Bunk
2006-11-17  1:53       ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox