Date: Sat, 4 Aug 2007 12:09:33 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Bruno Damour <freebsd.ruomad@free.fr> Cc: re@FreeBSD.org, current@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: reboot hanging Message-ID: <20070804160933.GA8664@rot26.obsecurity.org> In-Reply-To: <46B4366F.1040609@free.fr> References: <20070803210113.GA68807@rot26.obsecurity.org> <46B40D98.4020304@free.fr> <20070804064215.GA2787@rot26.obsecurity.org> <46B4366F.1040609@free.fr>
index | next in thread | previous in thread | raw e-mail
On Sat, Aug 04, 2007 at 10:18:55AM +0200, Bruno Damour wrote: > Kris Kennaway wrote: > >On Sat, Aug 04, 2007 at 07:24:40AM +0200, Bruno Damour wrote: > > > >>I see this also quite frequently (and have seen it for a period of time, > >>running current amd64 updated almost each week). > >>each time i have to hard reboot, and restart in single mode to fsck my > >>small boot partition (the rest is zfs, no problem there). > >>My proc is a core2 6400. I'm using : > >> > >>nooptions SCHED_4BSD # 4BSD scheduler > >>options SCHED_ULE # Newer scheduler > >>options PREEMPTION # Enable kernel thread preemption > >> > >>But I was using SCHED_4BSD before and it did happen as well. > >> > >>Sorry no debugging available. > >> > > > >It doesn't sound like the same problem. In my case buffers are > >synched so the filesystems are clean. > > > >Kris > >_______________________________________________ > >freebsd-current@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-current > >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > allright... > just thought I might have a help there ;-) > guess I'll keep on living with that. Up to you, but if you'd like to get it fixed you need to submit your own complete bug report. Krishome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070804160933.GA8664>