Created attachment 320648 [details] dmesg output from its boot earlier in the week Description of problem: Last night my 'Tyan Thunder K7 S2462' Dual-AMD based machine locked-up, power cycling it brought it back into service while I looked into possible causes. Around the same time monitoring lost contact with the machine I saw the following in my /var/log/messages Oct 17 03:23:42 lobstertechnology kernel: ------------[ cut here ]------------ Oct 17 03:23:42 lobstertechnology kernel: WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x89/0xda() (Not tainted) Oct 17 03:23:42 lobstertechnology kernel: Modules linked in: autofs4 hwmon_vid hwmon tun sunrpc ipv6 nf_conntrack_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables reiserfs dm_mirror dm_log dm_mod sr_mod cdrom ata_generic pata_acpi floppy pata_amd i2c_amd756 libata 3c59x i2c_core pcspkr mii e1000 sg aic7xxx scsi_transport_spi sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan] Oct 17 03:23:42 lobstertechnology kernel: Pid: 0, comm: swapper Not tainted 2.6.26.5-45.fc9.i686 #1 Oct 17 03:23:42 lobstertechnology kernel: [<c062ed3f>] ? printk+0xf/0x18 Oct 17 03:23:42 lobstertechnology kernel: [<c0428da5>] warn_on_slowpath+0x47/0x87 Oct 17 03:23:42 lobstertechnology kernel: [<c0420da8>] ? try_to_wake_up+0x1b4/0x1be Oct 17 03:23:42 lobstertechnology kernel: [<c0420dbd>] ? default_wake_function+0xb/0xd Oct 17 03:23:42 lobstertechnology kernel: [<c043965e>] ? autoremove_wake_function+0xf/0x33 Oct 17 03:23:42 lobstertechnology kernel: [<c041dbbb>] ? __wake_up_common+0x35/0x5b Oct 17 03:23:42 lobstertechnology kernel: [<c0420666>] ? __wake_up+0x31/0x3b Oct 17 03:23:42 lobstertechnology kernel: [<c0436a6b>] ? insert_work+0x49/0x4f Oct 17 03:23:42 lobstertechnology kernel: [<c0436db1>] ? __queue_work+0x28/0x2d Oct 17 03:23:42 lobstertechnology kernel: [<c0436e22>] ? queue_work+0x3e/0x48 Oct 17 03:23:42 lobstertechnology kernel: [<c0436e3b>] ? schedule_work+0xf/0x11 Oct 17 03:23:42 lobstertechnology kernel: [<c05cefe4>] dev_watchdog+0x89/0xda Oct 17 03:23:42 lobstertechnology kernel: [<c0430ce3>] run_timer_softirq+0x141/0x1a7 Oct 17 03:23:42 lobstertechnology kernel: [<c05cef5b>] ? dev_watchdog+0x0/0xda Oct 17 03:23:42 lobstertechnology kernel: [<c05cef5b>] ? dev_watchdog+0x0/0xda Oct 17 03:23:42 lobstertechnology kernel: [<c042d663>] __do_softirq+0x79/0xe7 Oct 17 03:23:42 lobstertechnology kernel: [<c0406e2f>] do_softirq+0x74/0xb5 Oct 17 03:23:42 lobstertechnology kernel: [<c042d46b>] irq_exit+0x38/0x6b Oct 17 03:23:42 lobstertechnology kernel: [<c041420c>] smp_apic_timer_interrupt+0x6e/0x7c Oct 17 03:23:42 lobstertechnology kernel: [<c0403024>] ? default_idle+0x0/0x58 Oct 17 03:23:42 lobstertechnology kernel: [<c04056a8>] apic_timer_interrupt+0x28/0x30 Oct 17 03:23:42 lobstertechnology kernel: [<c0403024>] ? default_idle+0x0/0x58 Oct 17 03:23:42 lobstertechnology kernel: [<c0419657>] ? native_safe_halt+0x5/0x7 Oct 17 03:23:42 lobstertechnology kernel: [<c0403054>] default_idle+0x30/0x58 Oct 17 03:23:42 lobstertechnology kernel: [<c0403c4a>] cpu_idle+0xae/0xd0 Oct 17 03:23:42 lobstertechnology kernel: [<c0621e2e>] rest_init+0x4e/0x50 Oct 17 03:23:42 lobstertechnology kernel: ======================= Oct 17 03:23:42 lobstertechnology kernel: ---[ end trace c9af6727361f96b7 ]--- Version-Release number of selected component (if applicable): - kernel-2.6.26.5-45.fc9.i686 "Linux <hostname> 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 athlon i386 GNU/Linux" How reproducible: Uncertain, this has occured twice this week since upgrading from Fedora Core 8 'kernel-2.6.26.3-14.fc8.i686' to Fedora Core 9 'kernel-2.6.26.5-45.fc9.i686'. Steps to Reproduce: 1. Leave the machine running servicing normal traffic (SMTP/HTTP) for a number of days. Actual results: Machine locks up, requires power cycle to resume operations. Expected results: Not to lock up in the first place. Additional info: Attached are dmesg, /var/log/messages, lspci output etc.
Created attachment 320649 [details] /var/log/messages
Created attachment 320650 [details] lspci output
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.