i386/53620: Kernel panics / reboots during install of 5.1 to
40GB disk on 44
KAREN THODE
thode12 at msn.com
Sun Jul 13 11:20:06 PDT 2003
The following reply was made to PR i386/53620; it has been noted by GNATS.
From: "KAREN THODE" <thode12 at msn.com>
To: "Nick Triantos" <nick at triantos.com>,
<freebsd-gnats-submit at freebsd.org>
Cc:
Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 44
Date: Sun, 13 Jul 2003 13:13:05 -0500
------=_NextPart_001_0000_01C34940.7F2E9640
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Did you add the dumpdev line to /etc/rc.conf?
----- Original Message -----
From: Nick Triantos
Sent: Saturday, July 12, 2003 11:58 PM
To: 'KAREN THODE'; freebsd-gnats-submit at freebsd.org
Subject: RE: i386/53620: Kernel panics / reboots during install of 5.1 to=
40GB disk on 44
(re-sending, my mail server is having problems, not sure if it made it th=
rough)
Hi, this did not work as expected.
I built/installed a debug kernel, but when I ran /stand/sysinstall after =
booting with that kernel (from the 20GB disk), it seemed to only know how=
to install to /dev/ad0, which is the 20GB disk. It overwrote part of my=
working installation before I could cancel it. fdisk/disklabel worked o=
k to /dev/ad1, but the install of packages seemed to want to force itself=
onto the live filesystem.
(1) Is there something I could / should do to build a custom install CD w=
ith the debug kernel?
(1a) I could install yet another hard disk in the machine that the CD cou=
ld use as swap space
(2) Or maybe I can somehow mount all of my working disk as a read-only mo=
unt?
(3) It seems I should be able to get sysinstall to forcibly write to /dev=
/ad1 only, but from reading over all the docs I can find, I could not see=
a way to do that.
(4) I could also use null-model to debug this, if it's reasonably easy to=
set up. The only compilication is that my other PCs all run WinXP, so I=
'd have to install a gdb client for windows, and probably cygwin.
regards, and thanks for all the help.
-Nick
-----Original Message-----
From: KAREN THODE [mailto:thode12 at msn.com] =20
Sent: Tuesday, July 08, 2003 4:02 PM
To: Nick Triantos; freebsd-gnats-submit at freebsd.org
Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to=
40GB disk on 44
Boot off of the 20 GB hard drive. Now, you need to make a copy of /usr/s=
rc/sys/i386/conf/GENERIC into a new directory called /usr/dbgkern. Now o=
pen up /usr/dbgkern/GENERIC in a text editor. Look for a line that says =
"#makeoptions DEBUG=3D-g" and remove the pound sign from the beginning.=
Now change "ident GENERIC" to "ident DBGKERN". Save this file as DBG=
KERN. Exit the editor. Now, type these commands (without the outer set =
of quotes) into the console while logged in as root.
"cd /usr/dbgkern"
"rm GENERIC"
"cd /usr/src"
"make buildkernel KERNCONF=3D"/usr/dbgkern/DBGKERN""
"make installkernel KERNCONF=3D"/usr/dbgkern/DBGKERN""
Now, reboot the machine.
As for the second question, you can perform kernel debugging without a se=
rial cable. You have to type the command "gdb -k [-c name-of-core-dump-f=
ile]" into the shell while logged in as root, replacing name-of-core-dump=
-file with the name of the kernel core dump. Once gdb displays the (kgdb=
) prompt, you can use hbreak {[file:]function|address} to set a breakpoin=
t (maximum 4), bt to perform a backtrace of the stack, c to continue runn=
ing the kernel, next to step over function calls, step to step into funct=
ion calls, print expr to print the value of expr on the terminal screen, =
and quit to quit gdb.
Lucas
----- Original Message -----
From: Nick Triantos
Sent: Monday, July 07, 2003 11:57 AM
To: 'KAREN THODE'
Subject: RE: i386/53620: Kernel panics / reboots during install of 5.1 to=
40GB disk on 44
Hello,
Is there a link somewhere on the freebsd.org web site as to how to do tha=
t? Since I'm booting from the CD image, I'm not sure how I can get it to=
execute from a different kernel. I suppose I can build a special CD ima=
ge, is that what you'd suggest? I've also never done kernel-level debugg=
ing of bsd, I assume it's done via serial interface?
cheers,
-Nick
-----Original Message-----
From: KAREN THODE [mailto:thode12 at msn.com] =20
Sent: Sunday, July 06, 2003 2:07 PM
To: freebsd-gnats-submit at FreeBSD.org; nick at triantos.com
Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to=
40GB disk on 44
Do you think that you could build a debugging kernel with crashdumps enab=
led and then replicate the kernel panic? If you can, post a panic messag=
e and gdb backtrace as a follow-up.
Lucas
------=_NextPart_001_0000_01C34940.7F2E9640
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Did you add th=
e dumpdev line to /etc/rc.conf?</DIV> <DIV> </DIV> <BLOCKQUOTE style=
=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT:=
#000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt Arial">-=
---- Original Message -----</DIV> <DIV style=3D"BACKGROUND: #e4e4e4; FONT=
: 10pt Arial; COLOR: black"><B>From:</B> Nick Triantos</DIV> <DIV style=3D=
"FONT: 10pt Arial"><B>Sent:</B> Saturday, July 12, 2003 11:58 PM</DIV> <D=
IV style=3D"FONT: 10pt Arial"><B>To:</B> 'KAREN THODE'; freebsd-gnats-sub=
mit at freebsd.org</DIV> <DIV style=3D"FONT: 10pt Arial"><B>Subject:</B> RE:=
i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk o=
n 44</DIV> <DIV> </DIV> <META content=3D"MSHTML 6.00.2800.1170" name=
=3DGENERATOR> <DIV><SPAN class=3D562292904-14072003><FONT face=3Dverdana>=
(re-sending, my mail server is having problems, not sure if it made it th=
rough)</FONT></SPAN></DIV> <DIV><SPAN class=3D562292904-14072003><FONT fa=
ce=3Dverdana></FONT></SPAN> </DIV> <DIV><SPAN class=3D562292904-1407=
2003><FONT face=3Dverdana>Hi, this did not work as expected.</FONT></SPAN=
></DIV> <DIV><SPAN class=3D562292904-14072003></SPAN> </DIV> <DIV><S=
PAN class=3D562292904-14072003><FONT face=3Dverdana>I built/installed a d=
ebug kernel, but when I ran /stand/sysinstall after booting with that ker=
nel (from the 20GB disk), it seemed to only know how to install to /dev/a=
d0, which is the 20GB disk. It overwrote part of my working in=
stallation before I could cancel it. fdisk/disklabel worked ok=
to /dev/ad1, but the install of packages seemed to want to force itself =
onto the live filesystem.</FONT></SPAN></DIV> <DIV><SPAN class=3D56229290=
4-14072003><FONT face=3Dverdana></FONT></SPAN> </DIV> <DIV><SPAN cla=
ss=3D562292904-14072003><FONT face=3Dverdana>(1) Is there something I cou=
ld / should do to build a custom install CD with the debug kernel?</FONT>=
</SPAN></DIV> <DIV><SPAN class=3D562292904-14072003>(1a) I could install =
yet another hard disk in the machine that the CD could use as swap space<=
/SPAN></DIV> <DIV><SPAN class=3D562292904-14072003><FONT face=3Dverdana><=
/FONT></SPAN> </DIV> <DIV><SPAN class=3D562292904-14072003><FONT fac=
e=3Dverdana>(2) Or maybe I can somehow mount all of my working disk as a =
read-only mount?</FONT></SPAN></DIV> <DIV><SPAN class=3D562292904-1407200=
3><FONT face=3Dverdana></FONT></SPAN> </DIV> <DIV><SPAN class=3D5622=
92904-14072003><FONT face=3Dverdana>(3) It seems I should be able to get =
sysinstall to forcibly write to /dev/ad1 only, but from reading over all =
the docs I can find, I could not see a way to do that.</FONT></SPAN></DIV=
> <DIV><SPAN class=3D562292904-14072003><FONT face=3Dverdana></FONT></SPA=
N> </DIV> <DIV><SPAN class=3D562292904-14072003><FONT face=3Dverdana=
>(4) I could also use null-model to debug this, if it's reasonably easy t=
o set up. The only compilication is that my other PCs all run WinXP=
, so I'd have to install a gdb client for windows, and probably cygwin.</=
FONT></SPAN></DIV> <DIV><SPAN class=3D562292904-14072003><FONT face=3Dver=
dana></FONT></SPAN> </DIV> <DIV><SPAN class=3D562292904-14072003><FO=
NT face=3Dverdana>regards, and thanks for all the help.</FONT></SPAN></DI=
V> <DIV><SPAN class=3D562292904-14072003></SPAN> </DIV> <DIV><SPAN c=
lass=3D562292904-14072003>-Nick</SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D=
"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3D=
en-us dir=3Dltr align=3Dleft><FONT face=3DTahoma>-----Original Message---=
--<BR><B>From:</B> KAREN THODE [mailto:thode12 at msn.com] <BR><B>Sent:</B> =
Tuesday, July 08, 2003 4:02 PM<BR><B>To:</B> Nick Triantos; freebsd-gnats=
-submit at freebsd.org<BR><B>Subject:</B> Re: i386/53620: Kernel panics / re=
boots during install of 5.1 to 40GB disk on 44<BR><BR></FONT></DIV> <DIV>=
</DIV> <DIV>Boot off of the 20 GB hard drive. Now, you need t=
o make a copy of <FONT face=3D"Verdana, Geneva, Arial, Sans-serif">/usr/s=
rc/sys/i386/conf/GENERIC</FONT> into a new directory called /usr/dbgkern.=
Now open up /usr/dbgkern/GENERIC in a text editor. Look for =
a line that says "#makeoptions DEBUG=3D-g" and remove the pou=
nd sign from the beginning. Now change "ident GENERIC" t=
o "ident DBGKERN". Save this file as DBGKERN. Exit the =
editor. Now, type these commands (without the outer set of quotes)&=
nbsp;into the console while logged in as root.</DIV> <DIV>"cd /usr/dbgker=
n"</DIV> <DIV>"rm GENERIC"</DIV> <DIV>"cd /usr/src"</DIV> <DIV>"make buil=
dkernel KERNCONF=3D"/usr/dbgkern/DBGKERN""</DIV> <DIV>"make installkernel=
KERNCONF=3D"/usr/dbgkern/DBGKERN""</DIV> <DIV>Now, reboot the machine.</=
DIV> <DIV> </DIV> <DIV>As for the second question, you can perform k=
ernel debugging without a serial cable. You have to type the comman=
d<FONT face=3DArial><EM> "</EM><FONT face=3D"Verdana, Geneva, Arial, Sans=
-serif">gdb -k [-c name-of-core-dump-file]</FONT>"</FONT><FONT face=3D"Ve=
rdana, Geneva, Arial, Sans-serif"> into the shell while logged in as root=
, replacing name-of-core-dump-file with the name of the kernel core dump.=
Once gdb displays the (kgdb) prompt, you can use hbreak {[file:]fu=
nction|address} to set a breakpoint (maximum 4), bt to perform a backtrac=
e of the stack, c to continue running the kernel, next to step over funct=
ion calls, step to step into function calls, print expr to print the valu=
e of expr on the terminal screen, and quit to quit gdb.</FONT></DIV> <DIV=
> </DIV> <DIV>Lucas</DIV> <DIV>----- Original Message -----</DIV> <B=
LOCKQUOTE style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"BACK=
GROUND: #e4e4e4; FONT: 10pt Arial; COLOR: black"><B>From:</B> Nick Triant=
os</DIV> <DIV style=3D"FONT: 10pt Arial"><B>Sent:</B> Monday, July 07, 20=
03 11:57 AM</DIV> <DIV style=3D"FONT: 10pt Arial"><B>To:</B> 'KAREN THODE=
'</DIV> <DIV style=3D"FONT: 10pt Arial"><B>Subject:</B> RE: i386/53620: K=
ernel panics / reboots during install of 5.1 to 40GB disk on 44</DIV> <DI=
V> </DIV> <META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR> =
<DIV><SPAN class=3D101265516-07072003><FONT face=3Dverdana>Hello,</FONT><=
/SPAN></DIV> <DIV><SPAN class=3D101265516-07072003></SPAN> </DIV> <D=
IV><SPAN class=3D101265516-07072003><FONT face=3Dverdana>Is there a link =
somewhere on the freebsd.org web site as to how to do that? Since I=
'm booting from the CD image, I'm not sure how I can get it to execute fr=
om a different kernel. I suppose I can build a special CD image, is=
that what you'd suggest? I've also never done kernel-level debuggi=
ng of bsd, I assume it's done via serial interface?</FONT></SPAN></DIV> <=
DIV><SPAN class=3D101265516-07072003></SPAN> </DIV> <DIV><SPAN class=
=3D101265516-07072003><FONT face=3Dverdana>cheers,</FONT></SPAN></DIV> <D=
IV><SPAN class=3D101265516-07072003>-Nick</SPAN></DIV> <BLOCKQUOTE dir=3D=
ltr style=3D"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageH=
eader lang=3Den-us dir=3Dltr align=3Dleft><FONT face=3DTahoma>-----Origin=
al Message-----<BR><B>From:</B> KAREN THODE [mailto:thode12 at msn.com] <BR>=
<B>Sent:</B> Sunday, July 06, 2003 2:07 PM<BR><B>To:</B> freebsd-gnats-su=
bmit at FreeBSD.org; nick at triantos.com<BR><B>Subject:</B> Re: i386/53620: Ke=
rnel panics / reboots during install of 5.1 to 40GB disk on 44<BR><BR></F=
ONT></DIV> <DIV>Do you think that you could build a debugging kernel with=
crashdumps enabled and then replicate the kernel panic? If yo=
u can, post a panic message and gdb backtrace as a follow-up.</DIV> <DIV>=
</DIV> <DIV>Lucas<BR><BR></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_001_0000_01C34940.7F2E9640--
More information about the freebsd-i386
mailing list