atom feed22 messages in org.freebsd.freebsd-currentRe: interesting problem
FromSent OnAttachments
Tony JohnsonSep 27, 2000 3:55 pm 
Kris KennawaySep 27, 2000 4:48 pm 
Tony JohnsonSep 27, 2000 5:06 pm 
Kris KennawaySep 27, 2000 5:17 pm 
Alfred PerlsteinSep 27, 2000 5:18 pm 
Greg LeheySep 27, 2000 5:34 pm 
Tony JohnsonSep 27, 2000 6:25 pm 
Alfred PerlsteinSep 27, 2000 6:39 pm 
Thomas David RiversSep 28, 2000 3:32 am 
Tony JohnsonSep 28, 2000 5:53 pm 
Greg LeheySep 28, 2000 6:50 pm 
Tony JohnsonSep 28, 2000 7:44 pm 
Nickolay DudorovSep 28, 2000 8:00 pm 
Greg LeheySep 28, 2000 8:04 pm 
Jordan HubbardSep 28, 2000 9:05 pm 
Alfred PerlsteinSep 29, 2000 12:18 am 
Alfred PerlsteinSep 29, 2000 12:30 am 
Gerhard SittigSep 29, 2000 10:11 am 
Tony JohnsonSep 30, 2000 4:46 pm 
Bill FumerolaSep 30, 2000 5:01 pm 
Matthew ThyerSep 30, 2000 6:53 pm 
Siobhan Patricia LynchOct 2, 2000 6:34 pm 
Subject:Re: interesting problem
From:Alfred Perlstein (bri@wintelcom.net)
Date:Sep 27, 2000 6:39:17 pm
List:org.freebsd.freebsd-current

* Tony Johnson <gjoh@gs.verio.net> [000927 18:26] wrote:

OK Well Here is the issue. If I put in the 2 boot floppies I get a page fault 12 after I press Q for "quit" on the visual kernel config. If I can save a crash dump before any FS's are mounted or even before I tell FBSD where to put the crash dump, I'd really like to know this... I'd like to read a handbook page on thisb since some people think I just haven't read it.

At this point in an install, if you could tell me (and the rest of the FreeBSD users) where I could get the boot floppies to save a crash dump (because I haven't even gotten this far) then I would appreciate this amd be more then happy to substantiate this by sending you a crash dump.

Do you realize how much developer time you're wasting by thrashing around cluelessly on the list demanding help?

Here's a clue:

Forget about your damn irq problem, boot with the disks installed, then read section of the handbook about crashdumps, compile a debug kernel and figure out what the problem is. Fix it and send us a patch.

Or you could simply run -stable.

thanks, -Alfred

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message