Date: Sun, 20 Sep 1998 19:35:59 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: gibbs@plutotech.com, mantar@netcom.com, kato@ganko.eps.nagoya-u.ac.jp, current@FreeBSD.ORG Subject: Re: [CAM] Broken tagged queuing drive? Message-ID: <199809201735.TAA18431@zibbi.mikom.csir.co.za> In-Reply-To: <18392.906310982@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 20, 98 10:03:02 am"
next in thread | previous in thread | raw e-mail | index | archive | help
I also see it here on my dual P5 machine. It seems to be caused by the latest version of isa/clock.c. If I go to the previous version (while keeping the rest of the source the same), the panic disappear. It only happens on the dual P5 machine, the 486 runs happily with the latest version of isa/clock.c. John -- John Hay -- John.Hay@mikom.csir.co.za > Aha! That message looks very similiar to what flashes by very quickly > on Bento. I'm glad that someone, at least, was able to see it long > enough to transcribe it. :) I believe it's exactly the same problem I > reported earlier (with SMP). I can build and install a UMP kernel > on bento if you think it will help. > > - Jordan > > > >It still does it. > > >I booted in single user and did fsck. It panicked > > >This time it stopped scrolling and here is the output.: > > >panic: rslock: cpu: 1, addr: 0xf0248fcc, lock: 0x01000001 > > >mp_lock = 01000003; cpuid = 1; lapic.id = 0c000000 > > >boot() called on cpu#1 > > > > Can you reproduce a panic using a UP kernel? What kind of > > DPT board are you using? > > > > -- > > Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809201735.TAA18431>