Suspend bug

[David G. Miller]

Alan <alan at lxorguk.ukuu.org.uk> wrote:

> the wall wart and assumed all was good.  Yesterday I found the laptop in 
> > some sort of "suspended" condition with the caps lock light blinking, 
> > other lights (power, touchpad, etc.) on but the system totally 
>   
>
> That's a kernel panic indicator
>
> Do you have a sequence of actions that repeats the problem and causes it
> to occur again ?
What I recall doing is:

1) ifdown the wired LAN connection.
2) ifup the wireless.
3) Unplug the wall wart.
4) My wife accessed some stuff on her USB flash drive (automounted, 
unmounted through the GUI).
5) Return system to wall wart.
6) ifdown wireless.
7) ifup LAN.

I can try repeating this.  Let me know.

This was reported by log watch:

 WARNING:  Kernel Errors Present
    aer: probe of 0000:00:04.0:pcie01 failed with error 1 ...:  1 Time(s)
 
It seems to be the only thing interesting that was logged but this is 
from the restart on the 31st.  lspci tells me:

00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 
[Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot-) IRQ 0
        Capabilities: [80] Message Signalled Interrupts: 64bit- 
Queue=0/0 Enable+
        Capabilities: [b0] #0d [0000]
        Capabilities: [b8] HyperTransport: MSI Mapping
        Capabilities: [100] Advanced Error Reporting

Looking at /var/log/messages, it looks like the system packed up at 
about on the 31st:

Jan 31 12:45:52 fubar ntpd[19060]: sendto(192.168.255.254) (fd=18): 
Invalid argument
Jan 31 13:02:56 fubar ntpd[19060]: sendto(192.168.255.254) (fd=18): 
Invalid argument
Jan 31 13:16:24 fubar dhclient: DHCPREQUEST on eth0 to 192.168.255.254 
port 67
Jan 31 13:16:25 fubar dhclient: DHCPACK from 192.168.255.254
Jan 31 13:16:25 fubar dhclient: bound to 192.168.0.181 -- renewal in 
8347 seconds.
Jan 31 15:19:48 fubar syslogd 1.4.1: restart.
Jan 31 15:19:48 fubar kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 31 15:19:48 fubar kernel: Linux version 2.6.19-1.2895.fc6 
(brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.
1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 18:50:56 EST 2007
Jan 31 15:19:48 fubar kernel: Command line: ro root=LABEL=/ rhgb quiet

Apparently, ntpd doesn't like having the interface its using switched so 
ntpd was conveniently giving the "Invalid argument" message every 
fifteen minutes or so from the time I removed the system from AC power 
until it barfed.  Also, acpid has:

[Tue Jan 30 20:59:41 2007] received event "ac_adapter ACAD 00000001 
00000000"
[Tue Jan 30 20:59:41 2007] notifying client 2869[68:68]
[Tue Jan 30 20:59:41 2007] notifying client 6358[0:500]
[Tue Jan 30 20:59:41 2007] completed event "ac_adapter ACAD 00000001 
00000000"
[Tue Jan 30 20:59:41 2007] received event "battery BAT1 00000080 00000001"
[Tue Jan 30 20:59:41 2007] notifying client 2869[68:68]
[Tue Jan 30 20:59:41 2007] notifying client 6358[0:500]
[Tue Jan 30 20:59:41 2007] completed event "battery BAT1 00000080 00000001"
[Tue Jan 30 20:59:41 2007] received event "processor CPU0 00000080 00000002"
[Tue Jan 30 20:59:41 2007] notifying client 2869[68:68]
[Tue Jan 30 20:59:41 2007] notifying client 6358[0:500]
[Tue Jan 30 20:59:41 2007] completed event "processor CPU0 00000080 
00000002"
[Tue Jan 30 21:21:34 2007] received event "ac_adapter ACAD 00000000 
00000001"
[Tue Jan 30 21:21:34 2007] notifying client 2869[68:68]
[Tue Jan 30 21:21:34 2007] notifying client 6358[0:500]
[Tue Jan 30 21:21:34 2007] completed event "ac_adapter ACAD 00000000 
00000001"
[Tue Jan 30 21:21:34 2007] received event "battery BAT1 00000080 00000001"
[Tue Jan 30 21:21:34 2007] notifying client 2869[68:68]
[Tue Jan 30 21:21:34 2007] notifying client 6358[0:500]
[Tue Jan 30 21:21:34 2007] completed event "battery BAT1 00000080 00000001"
[Tue Jan 30 21:21:34 2007] received event "processor CPU0 00000080 00000000"
[Tue Jan 30 21:21:34 2007] notifying client 2869[68:68]
[Tue Jan 30 21:21:34 2007] notifying client 6358[0:500]
[Tue Jan 30 21:21:34 2007] completed event "processor CPU0 00000080 
00000000"
[Wed Jan 31 15:19:55 2007] starting up
[Wed Jan 31 15:19:55 2007] 1 rule loaded
[Wed Jan 31 15:20:09 2007] client connected from 2945[68:68]
...

Let me know if you need any additional information.  If it's lengthy, 
feel free to go off list.

Cheers,
Dave

-- 
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce