Comment 19 for bug 68338

On Sat, Feb 10, 2007 at 08:56:06PM -0000, Anders wrote:
> It appears I spoke too quickly - the bug (or a very similar one)
> reoccurred on Feisty just now. Computer was hung when I got back, but
> from the syslog file it appears it kept writing -- MARK -- entries while
> 'dead':
>
> Feb 10 19:58:25 plasken -- MARK --
> Feb 10 20:07:15 plasken kernel: [25996.296585] NETDEV WATCHDOG: eth0: transmit timed out
> Feb 10 20:07:15 plasken kernel: [25996.296599] sky2 status report lost?
> Feb 10 20:07:24 plasken kernel: [26005.771487] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0
> Feb 10 20:07:24 plasken kernel: [26005.771503] [update_process_times+51/128] update_process_times+0x33/0x80
> Feb 10 20:07:24 plasken kernel: [26005.771512] [smp_apic_timer_interrupt+112/128] smp_apic_timer_interrupt+0x70/0x80
> Feb 10 20:07:24 plasken kernel: [26005.771519] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
> Feb 10 20:07:24 plasken kernel: [26005.771532] [_spin_lock_bh+15/32] _spin_lock_bh+0xf/0x20
> Feb 10 20:07:24 plasken kernel: [26005.771541] [<f89f16f5>] sky2_tx_timeout+0xf5/0x1c0 [sky2]
> Feb 10 20:07:24 plasken kernel: [26005.771558] [dev_watchdog+0/208] dev_watchdog+0x0/0xd0
> Feb 10 20:07:24 plasken kernel: [26005.771564] [dev_watchdog+193/208] dev_watchdog+0xc1/0xd0
> Feb 10 20:07:24 plasken kernel: [26005.771573] [run_timer_softirq+303/416] run_timer_softirq+0x12f/0x1a0
> Feb 10 20:07:24 plasken kernel: [26005.771585] [__do_softirq+130/256] __do_softirq+0x82/0x100
> Feb 10 20:07:24 plasken kernel: [26005.771596] [do_softirq+85/96] do_softirq+0x55/0x60
> Feb 10 20:07:24 plasken kernel: [26005.771602] [smp_apic_timer_interrupt+117/128] smp_apic_timer_interrupt+0x75/0x80
> Feb 10 20:07:24 plasken kernel: [26005.771609] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
> Feb 10 20:07:24 plasken kernel: [26005.771621] [mwait_idle_with_hints+70/96] mwait_idle_with_hints+0x46/0x60
> Feb 10 20:07:24 plasken kernel: [26005.771629] [cpu_idle+73/208] cpu_idle+0x49/0xd0
> Feb 10 20:07:24 plasken kernel: [26005.771636] [start_kernel+863/1056] start_kernel+0x35f/0x420
> Feb 10 20:07:24 plasken kernel: [26005.771643] [unknown_bootoption+0/608] unknown_bootoption+0x0/0x260
> Feb 10 20:07:24 plasken kernel: [26005.771654] =======================

I belive this is a separate issue. My symptoms (which have gone away since
upgrading my kernel) involved the network interface itself locking up, and the
problem was restricted to that only. You are getting "softlockup..." and
whatnot, plus some message that indicate to me that you have acpi issues. Maybe
try booting with "acpi=off" or "acpi=force" or something like that ... ?

-Forest