On Sat, Jan 20, 2007 at 06:05:37PM -0800, Luke S. Crawford wrote:
> On Tue, 16 Jan 2007, Manuel Bouyer wrote:
> 
> >
> >On Tue, Jan 16, 2007 at 01:52:19PM +0000, Matthias Scheler wrote:
> >>On Tue, Jan 16, 2007 at 03:26:48AM +0000, reed@reedmedia.net wrote:
> >>>Anyone seen anything like this?
> >>>
> >>>My kernel is netbsd-3.
> >>
> >>This pullup might fix your problem:
> >>
> >>http://mail-index.netbsd.org/source-changes/2007/01/15/0016.html
> >>
> >
> >I don't think so, this pullup was to fix a possible panic at boot with more
> >than one xbd.
> >This commit could be the fix:
> >http://mail-index.netbsd.org/source-changes/2007/01/01/0033.html
> >
> >but the author has not submitted a pullup request to netbsd-3 yet ...
> 
> Hm.  I am the xen provider in question  (we are a small shop, and I have a 
> dayjob, so I haven't gotten around to really looking at it until now)  but 
> using the same kernel, I do get occasional heavy disk load panics. 
> Actually I just triggered one right now (incidentally while I was 
> attempting to manually apply the patch you suggested;  all my NetBSD boxes 
> at the moment are XenUs. )

This looks like corruption in the softdep code (I guess one of the b_hash
or b_vnbufs lists, or sdpcpool pool). I can't see why this would happen
only on Xen3 domUs. Also I have seveeral domUs with softdep, and never
encountered this  ...

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 26 ans d'experience feront toujours la difference
--