Re: Infinite interrupt loop, INTSTAT = 8 ( WAS: BUG: spinlock recursion on CPU,

From: Chuck Ebbert
Date: Wed Jun 21 2006 - 05:20:19 EST


In-Reply-To: <44971B43.7090802@xxxxxxxxxxxxxxx>

On Mon, 19 Jun 2006 14:46:43 -0700, Konstantin Antselovich wrote:

> But other some problems evolved: when I take a HDD out then push it
> right back, kernel freezes and the following messages are logged:
>
> ---(see detailed log in attachment)---
> Jun 19 13:52:05 192.168.0.201 Infinite interrupt loop, INTSTAT = 8
> Jun 19 13:52:05 192.168.0.201 scsi0: At time of recovery, card was paused
> Jun 19 13:52:05 192.168.0.201 >>>>>>>>>>>>>>>>>> Dump Card State Begins
> <<<<<<<<<<<<<<<<<
> Jun 19 13:52:05 192.168.0.201 scsi0: Dumping Card State at program
> address 0x0 Mode 0x33
> Jun 19 13:52:05 192.168.0.201 Card was paused

Sorry, can't help with that.

You should try:

echo 'scsi remove-single-device 0 1 2 3' >/proc/scsi/scsi

where you replace the example numbers with:

0 = host adapter number
1 = host channel number
2 = device SCSI id
3 = device lun

before removing the device. Then do:

echo 'scsi add-single-device 0 1 2 3' >/proc/scsi/scsi

after putting it back.

To see your host adapter numbers, do:

cat /proc/scsi/scsi


> After some more scsi messages are logged, other issue with networking
> pops up (see below). At that point top shows 100% CPU is taken by event
> kernel thread, machine locks and I had to push restart.

Try posting this separately to netdev@xxxxxxxxxxxxxxxx I don't think it
should happen.

--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/