Re: [patch 0/5] [PATCH,RFC] vfs: per-superblock unused dentries list (2nd version)

[David Chinner]

On Sun, Jun 18, 2006 at 11:33:39PM -0700, Andrew Morton wrote:
> On Mon, 19 Jun 2006 15:55:23 +1000
> David Chinner <dgc@xxxxxxx> wrote:
> > 
> > The boot warnings:
> > 
> > ....
> >     eth3      device: S2io Inc. Xframe 10 Gigabit Ethernet PCI-X (rev 03)
> >     eth3      configuration: eth-id-00:0c:fc:00:02:c8
> > irq 60, desc: a0000001009a2d00, depth: 1, count: 0, unhandled: 0
> > ->handle_irq():  0000000000000000, 0x0
> > ->chip(): a000000100a0fe40, irq_type_sn+0x0/0x80
> > ->action(): e00000b007471b80
> > ->action->handler(): a0000002059373d0, s2io_msi_handle+0x1510/0x660 [s2io]    eth3
> > IP address: 192.168.1.248/24
> > Unexpected irq vector 0x3c on CPU 3!
> 
> I guess that's where things start to go bad.  genirq changes?

Seems likely. Plain 2.6.17-rc6 doesn't give this error.

> > BUG: warning at drivers/serial/sn_console.c:976/sn_sal_console_write()
> 
> There's a warning patch in -mm which shouts when someone does a busywait
> delay of over a millisecond, and sn_sal_console_write() is doing
> mdelay(150).
> 
> And it's doing that mdelay because it thinks port->sc_port.lock is already
> held.  I don't know why.

Ok, that explains why I haven't seen it before...

> > ip is at kmem_freepages+0x100/0x200
....
> 
> slab got messed up - I don't know what did this, either.

2.6.17-rc6 seems fine here as well. I've run with slab debuging
turned on and got the same panic, so it's not something obvious....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
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/