Messages in this thread | | | Date | Wed, 15 Nov 2006 10:29:00 +1100 | From | CaT <> | Subject | Re: BUG: soft lockup detected on CPU#0! in sys_close and ext3 |
| |
On Tue, Nov 14, 2006 at 02:01:25AM -0800, Andrew Morton wrote: > > It did for me in all cases. Should it be taking long enough to trigger > > the softlock timeout to do this? The size of the device is approx 280gig. > > It's a bit of a worry if it's taking all that time to shoot down 4g of > pagecache. The 280G will affect things - the radix-tree will be sparse and > the invalidate has firther to walk. But still...
Yeah. I would've thought that legitimate usage would not trigger such things, which is why I have it on whilst I'm building this box up.
> I assume that a fsck does the same thing?
Just did an e2fsck and it did the same thing.
-- "To the extent that we overreact, we proffer the terrorists the greatest tribute." - High Court Judge Michael Kirby - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |