Date: Fri, 30 Apr 2010 13:49:34 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Vladimir Grebenschikov <vova@fbsd.ru> Cc: Jeff Roberson <jroberson@jroberson.net>, current@freebsd.org Subject: Re: SUJ update Message-ID: <20100430104934.GL2391@deviant.kiev.zoral.com.ua> In-Reply-To: <1272624229.2142.8.camel@localhost> References: <alpine.BSF.2.00.1004291832080.1398@desktop> <1272620170.9401.14.camel@localhost> <1272624229.2142.8.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, Apr 30, 2010 at 02:43:49PM +0400, Vladimir Grebenschikov wrote: > Hi > > Ehh, looks like fresh kernel is not too stable, it holds after some time > of activity. > > DDB may be activated, but even 'call cpu_reset' does nothing here. > > Looks like it is not related to SUJ, it happens even with SUJ disabled. Does reverting r207410 + r207412 help ? > > > -----Original Message----- > From: Vladimir Grebenschikov <vova@fbsd.ru> > Reply-to: vova@fbsd.ru > To: Jeff Roberson <jroberson@jroberson.net> > Cc: current@freebsd.org > Subject: Re: SUJ update > Date: Fri, 30 Apr 2010 13:36:10 +0400 > > Hi > > 1) now works for me (no panics so far) > > -----Original Message----- > From: Jeff Roberson <jroberson@jroberson.net> > To: current@freebsd.org > Subject: SUJ update > Date: Thu, 29 Apr 2010 18:37:00 -1000 (HST) > > Hello, > > I fixed a few SUJ bugs. If those of you who reported one of the following > bugs could re-test I would greatly appreciate it. > > 1) panic on gnome start via softdep_cancel_link(). > 2) Difficulty setting flags on /. This can only be done from a direct > boot into single user but there were problems with tunefs that could lead > to the kernel and disk becoming out of sync with filesystem state. > 3) Kernel compiles without SOFTUPDATES defined in the config now work. > > I have had some reports of a hang waiting on journal space with certain > types of activity. I have only had this reported twice and I am not able > to reproduce no matter how much load I throw at the machine. If you > reproduce this please try to get a coredump or minidump. > > Thanks, > Jeff > _______________________________________________ > 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" > > > -- > Vladimir B. Grebenschikov > vova@fbsd.ru > _______________________________________________ > 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" [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkvatb0ACgkQC3+MBN1Mb4gl/ACcCph7krKBkX9P/D7tB+Jtl1eR YhAAoL5sSTK2Zmh7JOvNMMZ1YQu5z8KE =XF3U -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100430104934.GL2391>