Skip to contentSkip to conversation

2.6.23 spinlock hang in kswapd under heavy disk write loads

DISCUSSION Mr. Berkley Shands 2 participants 2 messages Oct 11, 2007 – Oct 12, 2007

lore
Share & tools
lore
#0 lore raw

With DEBUG_SLAB on, I can run only a very short time under 2.6.23 before a kernel panic.

[  626.028180] eth0: too many iterations (6) in nv_nic_irq.
[  626.167583] eth0: too many iterations (6) in nv_nic_irq.
[  626.206729] eth0: too many iterations (6) in nv_nic_irq.
[  626.400171] eth0: too many iterations (6) in nv_nic_irq.
[  626.446374] eth0: too many iterations (6) in nv_nic_irq.

followed by the crash at
forcedeth:nv_nic_irq_optimized+0x89
handle_IRQ_event+0x25
handle_edge_IRQ+0xe3
do_IRQ

berkley

This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others.

#1 lore raw
Quoted 9 lines · Mr. Berkley Shands

With DEBUG_SLAB on, I can run only a very short time under 2.6.23 before a kernel panic.

[  626.028180] eth0: too many iterations (6) in nv_nic_irq.
[  626.167583] eth0: too many iterations (6) in nv_nic_irq.
[  626.206729] eth0: too many iterations (6) in nv_nic_irq.
[  626.400171] eth0: too many iterations (6) in nv_nic_irq.
[  626.446374] eth0: too many iterations (6) in nv_nic_irq.
Quoted 5 lines

followed by the crash at
forcedeth:nv_nic_irq_optimized+0x89
handle_IRQ_event+0x25
handle_edge_IRQ+0xe3
do_IRQ

OK, thanks. Probably we should try to fix this problem before attempting the more elusive looking corruption.

CC'ed forcedeth maintainer and netdev.

Can you reiterate what your hardware is (including lspci)?