Re: 6.1 prerelease graid3 livelock?



It looks like the second patch fixed the problem. The box has been up for
just over a day and a half without any problems.

Thanks,
Brad


Well I don't know what was going on earlier but I reverted to good kernel,
synced my raid arrays (no longer degraded from the panics), then booted a
kernel with the second patch applied, this time no problems so far. I'll
let you know how things go after the box is running for a while.

Thanks,
Brad


Ok, I had already installed and booted the first patch. I then rebuilt
the
kernel with the second patch. Trying to reboot from the first patch to
the
second resulted in a crash/panic on shutdown. I didn't capture the
output
from this. Once I booted the second patch the machine panics in the boot
process, in short:
/dev/raid3t/moviesf: clean,o 190615 free (19p11 frags, 23588 oblocks,
0.8%
fralogy locked @ /usr/src/sys/geom/raid3/g_raid3.c:773.
KDB: enter: panic
[thread pid 35 tid 100030 ]
Stopped at kdb_enter+0x30: leave

The text copied from the serial console was a little garbled, it did say
something like:
sx lock, geom topology locked...

I did an "alltrace" at that point which I'll send seperately.

Thanks,
Brad


On Thu, Apr 27, 2006 at 08:55:35AM +0200, Pawel Jakub Dawidek wrote:
+> On Sun, Apr 23, 2006 at 12:04:33PM -0700, Bradley W. Dutton wrote:
+> +> Hi,
+> +>
+> +> I'm experiencing a sort of livelock on a 6.1 prerelease box. It
appears
+> +> all of the IO related activity hangs but the box continues to do
+> +> routing/NAT/etc for internet access from my other boxes. I can
usually
+> +> get the lockup to occur within about 12 hours of booting.
+>
+> Ok, I think I found it. Could you try this patch:
+>
+> http://people.freebsd.org/~pjd/patches/g_raid3.c.4.patch

markus@ reported the livelock is still there, so please try this patch
instead:

http://people.freebsd.org/~pjd/patches/g_raid3.c.5.patch


_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@xxxxxxxxxxx"



_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"



_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: 6.1 prerelease graid3 livelock?
    ... Well I don't know what was going on earlier but I reverted to good kernel, ... synced my raid arrays, ... kernel with the second patch applied, this time no problems so far. ... Once I booted the second patch the machine panics in the boot ...
    (freebsd-stable)
  • Re: 6.1 prerelease graid3 livelock?
    ... As a workaround I would boot a pre March 20 kernel, rebuild the array, ... kernel with the second patch applied, this time no problems so far. ... Once I booted the second patch the machine panics in the ...
    (freebsd-stable)
  • Re: Asterisk on FreeBSD, anyone?
    ... they were panicing the 6.0 kernel during the shutdown ... >out the stop) part of the script and no more panics. ...
    (freebsd-questions)
  • Re: [PATCH] fix sys cpumap for > 352 NR_CPUS
    ... There are over 300 such constructs in the kernel. ... Since I am most impressed with your abilities, ... The second patch would ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Timekeeping hosed by factor 3, high lapic[01] interrupt rates
    ... > # Forget SMP and go back to UP for now. ... > # And try it both with the timecounter set to TSC and with the timecounter ... > Here we go, kernel with your second patch, boot with kern.smp.disabled=1. ... Can you get the same ntpdate output for the kernel without the patch? ...
    (freebsd-current)