Comment 33 for bug 356768

Hm okay well I went away for a few days, came back, box was still running stable. I started checking my email and within 5 minutes I had a kernel panic (flashing numlock lights etc)

Here's the kern.log snapshot
Mar 18 18:55:20 failwhale-desktop kernel: [276251.587698] ath5k phy0: unsupported jumbo
Mar 18 20:10:10 failwhale-desktop kernel: [280741.897414] ath5k phy0: unsupported jumbo
Mar 18 20:29:50 failwhale-desktop kernel: [281921.096017] wlan0: no probe response from AP 00:e0:98:fe:ba:66 - disassociating
Mar 18 20:29:51 failwhale-desktop kernel: [281922.142586] wlan0: authenticate with AP 00:e0:98:fe:ba:66
Mar 18 20:29:51 failwhale-desktop kernel: [281922.143968] wlan0: authenticated
Mar 18 20:29:51 failwhale-desktop kernel: [281922.143972] wlan0: associate with AP 00:e0:98:fe:ba:66
Mar 18 20:29:51 failwhale-desktop kernel: [281922.146018] wlan0: RX ReassocResp from 00:e0:98:fe:ba:66 (capab=0x461 status=0 aid=1)
Mar 18 20:29:51 failwhale-desktop kernel: [281922.146021] wlan0: associated
Mar 18 20:30:28 failwhale-desktop kernel: [281959.272019] wlan0: no probe response from AP 00:e0:98:fe:ba:66 - disassociating
Mar 18 20:30:29 failwhale-desktop kernel: [281960.312955] wlan0: authenticate with AP 00:e0:98:fe:ba:66
Mar 18 20:30:29 failwhale-desktop kernel: [281960.316042] wlan0: authenticated
Mar 18 20:30:29 failwhale-desktop kernel: [281960.316047] wlan0: associate with AP 00:e0:98:fe:ba:66
Mar 18 20:30:29 failwhale-desktop kernel: [281960.321391] wlan0: RX ReassocResp from 00:e0:98:fe:ba:66 (capab=0x461 status=0 aid=1)
Mar 18 20:30:29 failwhale-desktop kernel: [281960.321395] wlan0: associated
#KERNEL PANIC SOMEWHERE IN THIS TIME INTERVAL
#SHAMWOW MAKES FAILWHALE REBOOT
Mar 18 21:38:20 failwhale-desktop kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started.
Mar 18 21:38:20 failwhale-desktop kernel: [ 0.000000] Initializing cgroup subsys cpuset
Mar 18 21:38:20 failwhale-desktop kernel: [ 0.000000] Initializing cgroup subsys cpu
Mar 18 21:38:20 failwhale-desktop kernel: [ 0.000000] Linux version 2.6.31-20-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu SMP Mon Feb 8 09:05:19 UTC 2010 (Ubuntu 2.6.31-20.57-generic)

So I have no idea what's going on, I suppose I'll just upgrade and recompile the kernel. I still think it's some instability problem in ath5k, there is probably a missing sanity check elsewhere in the code during wireless access point communication / reassociation. Either that or the kernel panic has something to do with graphics (it was stable until I came back and started surfing the internet and moving the mouse). Thanks Luis I'll probably upgrade the kernel, but Ubuntu 9.10 was the latest release so I blame them ! hah

I will post here if I solve the stability issue. The patch to ath5k has helped but not solved the problem. Now its stable for 96hours instead of 24 hours.