2007/8/1, Ingo Molnar <[email protected]>:
> ok, it wasnt supposed to be _that_ easy i guess :-) Can you please
> (re-)confirm that the workaround below indeed fixes the hung card
> problem? (after producing a single WARN_ON message into the syslog)
yes, with this patch everything works fine
end of dmesg:
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1020112k swap on /dev/sda2. Priority:-1 extents:1 across:1020112k
skge eth1: enabling interface
NET: Registered protocol family 17
WARNING: at kernel/irq/resend.c:70 check_irq_resend()
Call Trace:
[<ffffffff8025e5c8>] check_irq_resend+0xa8/0xc0
[<ffffffff8025e1ca>] enable_irq+0xea/0xf0
[<ffffffff8800f21d>] :8390:ei_start_xmit+0x14d/0x30c
[<ffffffff8052b5ce>] dev_hard_start_xmit+0x26e/0x2d0
[<ffffffff80539b10>] __qdisc_run+0xc0/0x1f0
[<ffffffff8052db9f>] dev_queue_xmit+0x24f/0x310
[<ffffffff880d7ac9>] :af_packet:packet_sendmsg+0x259/0x2c0
[<ffffffff8051f0bf>] sock_sendmsg+0xdf/0x110
[<ffffffff8024b8c9>] trace_hardirqs_on+0xd9/0x180
[<ffffffff8024c1dd>] __lock_acquire+0x31d/0xff0
[<ffffffff80243290>] autoremove_wake_function+0x0/0x40
[<ffffffff803e3103>] __up_read+0x23/0xb0
[<ffffffff803e3125>] __up_read+0x45/0xb0
[<ffffffff805bd8f5>] _spin_unlock_irqrestore+0x65/0x80
[<ffffffff8024b8c9>] trace_hardirqs_on+0xd9/0x180
[<ffffffff803e3125>] __up_read+0x45/0xb0
[<ffffffff802464b6>] up_read+0x26/0x30
[<ffffffff8051f4f1>] sys_sendto+0x111/0x150
[<ffffffff8024b8c9>] trace_hardirqs_on+0xd9/0x180
[<ffffffff805bd93b>] _spin_unlock_irq+0x2b/0x60
[<ffffffff8023861a>] do_sigaction+0x11a/0x1d0
[<ffffffff802097fe>] system_call+0x7e/0x83
Marking TSC unstable due to cpufreq changes
Time: acpi_pm clocksource has been installed.
> also, does removing the ne2k-pci module and reinserting it again solve
> the problem too, or is your network card stuck forever once it got into
> that state?
it doesn't change anything - i tried reloading both modules (ne2k_pci and skge)
Marcin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
