On Tue, Jul 04, 2006 at 10:53:27PM +0200, Luca Tettamanti wrote:
> The blinking is done by the kernel panic handler.
yes.
> >bcm43xx: set security called enabled = 1 encrypt = 1
> >hda: dma_timer_expiry: dma status == 0x21
> >hda: DMA timeout error
> >
> >HARDWARE ERROR
> >CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f
> >TSC 136e4622cf
> >This is not a software problem!
>
> Probably the PCI bus is confused. Don't know if it's ide driver or bcm
> fault...
I'm pretty sure it's IDE. The common thread to all the resume lockups is
the IDE light being stuck on.
> I fixed a spurious MCE during resume on Athlon a couple of years ago,
> but this one seems unrelated.
What was the nature of the fix?
> Try to unload the wireless driver before suspending.
Here's the netconsole output with all possible modules unloaded (except
8139too and netconsole, obviously). In addition, I stopped all the
processes I could and did "hdparm -d0 /dev/hda" to disable DMA.
hda: DMA disabled
Stopping tasks: =======================================|
PM: Writing back config space on device 0000:01:02.0 at offset f (was 100,
writing 10b)
PM: Writing back config space on device 0000:01:02.0 at offset 4 (was 0,
writing e0104000)
PM: Writing back config space on device 0000:01:02.0 at offset 3 (was 0,
writing 4000)
PM: Writing back config space on device 0000:01:02.0 at offset 1 (was 0,
writing 102)
This device is the wireless card:
01:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
PM: Writing back config space on device 0000:01:04.0 at offset f (was 34001ff,
writing 5c0010b)
PM: Writing back config space on device 0000:01:04.0 at offset e (was 0,
writing 34fc)
PM: Writing back config space on device 0000:01:04.0 at offset d (was 0,
writing 3400)
PM: Writing back config space on device 0000:01:04.0 at offset c (was 0,
writing 30fc)
PM: Writing back config space on device 0000:01:04.0 at offset b (was 0,
writing 3000)
PM: Writing back config space on device 0000:01:04.0 at offset a (was 0,
writing e07ff000)
PM: Writing back config space on device 0000:01:04.0 at offset 8 (was 0,
writing 31fff000)
PM: Writing back config space on device 0000:01:04.0 at offset 6 (was 40000000,
writing b0050201)
PM: Writing back config space on device 0000:01:04.0 at offset 3 (was 824008,
writing 82a810)
PM: Writing back config space on device 0000:01:04.0 at offset 1 (was 2100107,
writing 2100003)
PM: Writing back config space on device 0000:01:04.1 at offset f (was 34002ff,
writing 5c0020a)
PM: Writing back config space on device 0000:01:04.1 at offset e (was 0,
writing 3cfc)
PM: Writing back config space on device 0000:01:04.1 at offset d (was 0,
writing 3c00)
PM: Writing back config space on device 0000:01:04.1 at offset c (was 0,
writing 38fc)
PM: Writing back config space on device 0000:01:04.1 at offset b (was 0,
writing 3800)
PM: Writing back config space on device 0000:01:04.1 at offset a (was 0,
writing e0fff000)
PM: Writing back config space on device 0000:01:04.1 at offset 8 (was 0,
writing 33fff000)
PM: Writing back config space on device 0000:01:04.1 at offset 7 (was e1000000,
writing 32000000)
PM: Writing back config space on device 0000:01:04.1 at offset 6 (was 40000000,
writing b0090601)
PM: Writing back config space on device 0000:01:04.1 at offset 3 (was 824008,
writing 82a810)
PM: Writing back config space on device 0000:01:04.1 at offset 1 (was 2100103,
writing 2100003)
These two are cardbus bridges:
01:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
01:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller
(rev 01)
I don't have any cardbus cards for this laptop. (Unless the
internal broadcomm minipci wireless is cardbus, but I don't
think so).
I don't know if this is related, but - the cardbus bridges make
the kernel say this at boot:
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Bus #03 (-#06) is hidden behind bridge #02 (-#02) (try
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
PCI: Bus #07 (-#0a) is hidden behind bridge #02 (-#02) (try
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
So I boot with "pci=assign-busses" now, and these warnings go
away. I haven't reported it yet.
PM: Writing back config space on device 0000:01:04.2 at offset 4 (was 1,
writing 7401)
PM: Writing back config space on device 0000:01:04.2 at offset 3 (was 0,
writing 4010)
PM: Writing back config space on device 0000:01:04.2 at offset 1 (was 2100000,
writing 2100107)
This one is:
01:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading
Function (rev 01)
PM: Writing back config space on device 0000:0a:00.0 at offset f (was 1050100,
writing 105010b)
PM: Writing back config space on device 0000:0a:00.0 at offset 6 (was 8,
writing f8000008)
PM: Writing back config space on device 0000:0a:00.0 at offset 5 (was 8,
writing f0000008)
PM: Writing back config space on device 0000:0a:00.0 at offset 4 (was 0,
writing e2000000)
PM: Writing back config space on device 0000:0a:00.0 at offset 3 (was 0,
writing 4000)
PM: Writing back config space on device 0000:0a:00.0 at offset 1 (was 2b00000,
writing 2b00007)
And this is:
0a:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4
420 Go 32M] (rev a3)
pnp: Res cnt 3
pnp: res cnt 3
pnp: Encode io
pnp: Encode io
pnp: Encode irq
pnp: Failed to activate device 00:08.
pnp: Res cnt 1
pnp: res cnt 1
pnp: Encode irq
pnp: Failed to activate device 00:09.
These devices are detected at boot like this:
pnp: the driver 'i8042 kbd' has been registered
pnp: match found with the PnP device '00:08' and the driver 'i8042 kbd'
pnp: the driver 'i8042 aux' has been registered
pnp: match found with the PnP device '00:09' and the driver 'i8042 aux'
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
Restarting tasks... done
ACPI Error (evevent-0312): No installed handler for fixed event [00000002]
[20060127]
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
This ACPI thing is new. Maybe it's because I've unloaded some of
the acpi modules this time. Maybe the event is the power button
press that woke the sleeping computer? With the psmouse module
unloaded, I have to use the power button to wake it. Normally I
would use the touchpad.
It's interesting here that it's complaining about ide dma
timeout, since I disabled DMA before suspend.
HARDWARE ERROR
CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f
TSC 765865366
This is not a software problem!
Run through mcelog --ascii to decode and contact your hardware vendor
Kernel panic - not syncing: Machine check
<4>atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might
be trying access hardware directly.
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be
trying access hardware directly.
Then this stuff again.
Jason
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
