From owner-freebsd-i386@FreeBSD.ORG Sun Jul 13 01:13:07 2003 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBE6037B401; Sun, 13 Jul 2003 01:13:07 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C26B43FA3; Sun, 13 Jul 2003 01:13:07 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h6D8D6s8072249; Sun, 13 Jul 2003 04:13:06 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h6D8D6xe072248; Sun, 13 Jul 2003 08:13:06 GMT Date: Sun, 13 Jul 2003 08:13:06 GMT Message-Id: <200307130813.h6D8D6xe072248@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [-CURRENT tinderbox] failure on i386/pc98 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 08:13:08 -0000 TB --- 2003-07-13 07:14:14 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-07-13 07:14:14 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-13 07:19:12 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. [...] objcopy -S -O binary boot0.5.out boot0.5.bin cat boot0.5.bin /dev/zero | dd of=boot0.5 bs=1 count=7168 7168+0 records in 7168+0 records out 7168 bytes transferred in 0.222433 secs (32225 bytes/sec) ===> sys/boot/pc98/boot2 cc -elf -Os -mrtd -ffreestanding -fno-builtin -fno-guess-branch-probability -D_KERNEL -DPC98 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2/../../.. -I. -DCOMCONSOLE=0x238 -DCOMCONSOLE_CLK=16 -DCOMCONSOLE_MODE=0x0c -DCOMSPEED=9600 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -ffreestanding -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2/start.S /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2/start.S:474:16: pasting "disklabel" and ":" does not give a valid preprocessing token *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-07-13 08:13:06 - /usr/bin/make returned exit code 1 TB --- 2003-07-13 08:13:06 - ERROR: failed to build world TB --- 2003-07-13 08:13:06 - tinderbox aborted From owner-freebsd-i386@FreeBSD.ORG Sun Jul 13 11:20:06 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D11F37B404 for ; Sun, 13 Jul 2003 11:20:06 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08BF043FB1 for ; Sun, 13 Jul 2003 11:20:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6DIK4Up097196 for ; Sun, 13 Jul 2003 11:20:04 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6DIK4A1097195; Sun, 13 Jul 2003 11:20:04 -0700 (PDT) Date: Sun, 13 Jul 2003 11:20:04 -0700 (PDT) Message-Id: <200307131820.h6DIK4A1097195@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "KAREN THODE" Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 44 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KAREN THODE List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:20:06 -0000 The following reply was made to PR i386/53620; it has been noted by GNATS. From: "KAREN THODE" To: "Nick Triantos" , 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@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@msn.com] =20 Sent: Tuesday, July 08, 2003 4:02 PM To: Nick Triantos; freebsd-gnats-submit@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@msn.com] =20 Sent: Sunday, July 06, 2003 2:07 PM To: freebsd-gnats-submit@FreeBSD.org; nick@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
Did you add th= e dumpdev line to /etc/rc.conf?
 
-= ---- Original Message -----
From: Nick Triantos
Sent: Saturday, July 12, 2003 11:58 PM
To: 'KAREN THODE'; freebsd-gnats-sub= mit@freebsd.org
Subject: RE:= i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk o= n 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 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.
 
(1) Is there something I cou= ld / should do to build a custom install CD with the debug kernel?=
(1a) I could install = yet another hard disk in the machine that the CD could use as swap space<= /SPAN>
<= /FONT> 
(2) Or maybe I can somehow mount all of my working disk as a = read-only mount?
 
(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 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.
 
regards, and thanks for all the help.
 
-Nick
-----Original Message---= --
From: KAREN THODE [mailto:thode12@msn.com]
Sent: = Tuesday, July 08, 2003 4:02 PM
To: Nick Triantos; freebsd-gnats= -submit@freebsd.org
Subject: Re: i386/53620: Kernel panics / re= boots during install of 5.1 to 40GB disk on 44

=  
Boot off of the 20 GB hard drive.  Now, you need t= o make a copy of /usr/s= rc/sys/i386/conf/GENERIC 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.
"cd /usr/dbgker= n"
"rm GENERIC"
"cd /usr/src"
"make buil= dkernel KERNCONF=3D"/usr/dbgkern/DBGKERN""
"make installkernel= KERNCONF=3D"/usr/dbgkern/DBGKERN""
Now, reboot the machine.
 
As for the second question, you can perform k= ernel debugging without a serial cable.  You have to type the comman= d "gdb -k [-c name-of-core-dump-file]" 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.
 
Lucas
----- Original Message -----
From: Nick Triant= os
Sent: Monday, July 07, 20= 03 11:57 AM
To: 'KAREN THODE= '
Subject: RE: i386/53620: K= ernel panics / reboots during install of 5.1 to 40GB disk on 44
 
=
Hello,<= /SPAN>
 
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?
<= DIV> 
cheers,
-Nick
-----Origin= al Message-----
From: KAREN THODE [mailto:thode12@msn.com]
= Sent: Sunday, July 06, 2003 2:07 PM
To: freebsd-gnats-su= bmit@FreeBSD.org; nick@triantos.com
Subject: Re: i386/53620: Ke= rnel panics / reboots during install of 5.1 to 40GB disk on 44

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.
=  
Lucas

------=_NextPart_001_0000_01C34940.7F2E9640-- From owner-freebsd-i386@FreeBSD.ORG Sun Jul 13 11:30:22 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCE6B37B401 for ; Sun, 13 Jul 2003 11:30:22 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8F8343F93 for ; Sun, 13 Jul 2003 11:30:21 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6DIULUp097527 for ; Sun, 13 Jul 2003 11:30:21 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6DIULWR097526; Sun, 13 Jul 2003 11:30:21 -0700 (PDT) Resent-Date: Sun, 13 Jul 2003 11:30:21 -0700 (PDT) Resent-Message-Id: <200307131830.h6DIULWR097526@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Andreas Fuchs Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8896237B401 for ; Sun, 13 Jul 2003 11:22:35 -0700 (PDT) Received: from eris.void.at (212-88-187-152.ADSL.ycn.com [212.88.187.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2BC243F75 for ; Sun, 13 Jul 2003 11:22:33 -0700 (PDT) (envelope-from asf@eris.void.at) Received: from eris.void.at (localhost [127.0.0.1]) by eris.void.at (8.12.9/8.12.9) with ESMTP id h6DITw1P029459 for ; Sun, 13 Jul 2003 20:29:58 +0200 (CEST) (envelope-from asf@eris.void.at) Received: (from asf@localhost) by eris.void.at (8.12.9/8.12.9/Submit) id h6DITwLF029458; Sun, 13 Jul 2003 20:29:58 +0200 (CEST) Message-Id: <200307131829.h6DITwLF029458@eris.void.at> Date: Sun, 13 Jul 2003 20:29:58 +0200 (CEST) From: Andreas Fuchs To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: i386/54451: [patch] i386_{get|set}_ldt manual page is confusing X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andreas Fuchs List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:30:23 -0000 >Number: 54451 >Category: i386 >Synopsis: [patch] i386_{get|set}_ldt manual page is confusing >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Jul 13 11:30:16 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Andreas Fuchs >Release: FreeBSD 5.1-CURRENT i386 >Organization: >Environment: System: FreeBSD boinkine.defun.at 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sun Jun 22 15:11:58 CEST 2003 root@boinkine.defun.at:/usr/obj/usr/src/sys/BOINKINE i386 >Description: The i386_get_ldt (which serves for _set_, too) man page is written in a confusing and long-winded style, especially regarding the meaning of the start_ldt parameter. >How-To-Repeat: man 2 i386_get_ldt >Fix: I've rewritten the portions which were confusing to me and added an example section. I'm not so sure about what to do with the goofy WARNING, as many other syscalls can also really hose one's processes but don't state it explicitly. I've left it in in the patch, but my gut feeling says that is should go (-: The attached patch is against $FreeBSD: src/lib/libc/i386/sys/i386_get_ldt.2,v 1.17 2003/06/09 11:46:22 jhb Exp $ --- /usr/src/lib/libc/i386/sys/i386_get_ldt.2 Sun Jun 22 14:18:31 2003 +++ i386_get_ldt.2 Sun Jul 13 18:20:17 2003 @@ -52,46 +52,60 @@ The .Fn i386_get_ldt system call -will return the list of i386 descriptors that the process has in its -LDT. +will copy the list of i386 descriptors that the process has in its +LDT. It does so starting from the LDT entry index +.Fa start_sel +into an arrary pointed to by +.Fa descs , +which must be +.Fa num_sel +elements wide. +.Pp The .Fn i386_set_ldt system call will set a list of i386 descriptors for the current process in its -LDT. -Both routines accept a starting selector number -.Fa start_sel , -an array of memory that -will contain the descriptors to be set or returned -.Fa descs , -and the number of entries to set or return -.Fa num_sels . +LDT, starting from the LDT entry index +.Fa start_sel . +It copies +.Fa num_descs +descriptors in the array pointed to by +.Fa descs +into the LDT. .Pp The argument .Fa descs can be either segment_descriptor or gate_descriptor and are defined in .Aq Pa i386/segments.h . These structures are defined by the architecture -as disjoint bit-fields, so care must be taken in constructing them. +as disjoint bit-fields, so you must take care in constructing them. .Sh RETURN VALUES -Upon successful completion, +If successful, .Fn i386_get_ldt returns the number of descriptors currently in the LDT. -The .Fn i386_set_ldt -system call -returns the first selector set. -Otherwise, a value of -1 is returned and the global +returns the index first selector that it set on success. If an error +occurred, the procedures return a value of -1 and set the global variable .Va errno -is set to indicate the error. +to indicate the error. +.Sh EXAMPLES +To set the +.Va "my_ldt_index" +th slot of the process's LDT to the value of +.Va my_ldt_entry , +use something like this: +.Bd -literal -offset indent +if (i386_set_ldt(my_ldt_index, &my_ldt_entry, 1) < 0) { + perror("i386_set_ldt"); +} .Sh ERRORS The .Fn i386_get_ldt and .Fn i386_set_ldt system calls -will fail if: +will fail with: .Bl -tag -width Er .It Bq Er EINVAL An inappropriate value was used for >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-i386@FreeBSD.ORG Sun Jul 13 18:50:21 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A77137B401 for ; Sun, 13 Jul 2003 18:50:21 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A41D643F3F for ; Sun, 13 Jul 2003 18:50:20 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6E1oKUp036481 for ; Sun, 13 Jul 2003 18:50:20 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6E1oKWq036480; Sun, 13 Jul 2003 18:50:20 -0700 (PDT) Date: Sun, 13 Jul 2003 18:50:20 -0700 (PDT) Message-Id: <200307140150.h6E1oKWq036480@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "KAREN THODE" Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 44 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: KAREN THODE List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 01:50:21 -0000 The following reply was made to PR i386/53620; it has been noted by GNATS. From: "KAREN THODE" To: "Nick Triantos" , Cc: Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 44 Date: Sun, 13 Jul 2003 20:43:06 -0500 ------=_NextPart_001_0000_01C3497F.5CD3BB40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable See if you can rebuild the system, but change the rw to ro for the entry = in /etc/fstab for the root filesystem on ad0. Also, try not installing p= ackages. ----- Original Message ----- From: Nick Triantos Sent: Sunday, July 13, 2003 1:47 PM To: 'KAREN THODE'; freebsd-gnats-submit@freebsd.org Subject: RE: i386/53620: Kernel panics / reboots during install of 5.1 to= 40GB disk on 44 Yes, thanks for checking. The problem, I think, is that sysinstall tries= to install to ad0, though I'm not sure. This time I did not get a panic, instead, I just got the install overwrit= ing my live system. regards, -Nick -----Original Message----- From: KAREN THODE [mailto:thode12@msn.com] =20 Sent: Sunday, July 13, 2003 11:13 AM To: Nick Triantos; freebsd-gnats-submit@freebsd.org Subject: Re: i386/53620: Kernel panics / reboots during install of 5.1 to= 40GB disk on 44 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@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@msn.com] =20 Sent: Tuesday, July 08, 2003 4:02 PM To: Nick Triantos; freebsd-gnats-submit@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@msn.com] =20 Sent: Sunday, July 06, 2003 2:07 PM To: freebsd-gnats-submit@FreeBSD.org; nick@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_01C3497F.5CD3BB40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
See if you can= rebuild the system, but change the rw to ro for the entry in /etc/fstab = for the root filesystem on ad0.  Also, try not installing packages.<= /DIV>
 
----- Original Message -----
F= rom: Nick Triantos
Sent:= Sunday, July 13, 2003 1:47 PM
T= o: 'KAREN THODE'; freebsd-gnats-submit@freebsd.org
Subject: RE: i386/53620: Kernel panics / reboot= s during install of 5.1 to 40GB disk on 44
 
Yes, thanks for checking.  The= problem, I think, is that sysinstall tries to install to ad0, though I'm= not sure.
 
This time I did not get a panic, instead, I= just got the install overwriting my live system.
 
regards,
-Nick
-----Original= Message-----
From: KAREN THODE [mailto:thode12@msn.com]
Sent: Sunday, July 13, 2003 11:13 AM
To: Nick Triantos; fr= eebsd-gnats-submit@freebsd.org
Subject: Re: i386/53620: Kernel = panics / reboots during install of 5.1 to 40GB disk on 44

<= /DIV>
Did you add the dumpdev line to /etc/rc.conf?
 = ;
----- Original Message -----
From: Nick Tr= iantos
Sent: Saturday, July = 12, 2003 11:58 PM
To: 'KAREN= THODE'; freebsd-gnats-submit@freebsd.org
Subject: RE: i386/53620: Kernel panics / reboots during ins= tall of 5.1 to 40GB disk on 44
 
(re-sending, my mail server is having problems,= not sure if it made it through)
 
Hi, this did not work= as expected.
<= /SPAN> 
I built/installed a debug kernel, but when I ran /stand/sysinstall a= fter booting with that kernel (from the 20GB disk), it seemed to only kno= w 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 ok to /dev/ad1, but the install of packages seeme= d to want to force itself onto the live filesystem.
<= DIV>&= nbsp;
(1= ) Is there something I could / should do to build a custom install CD wit= h the debug kernel?
(1a) I could install yet another hard disk in the machine that the C= D could use as swap space
 
(2) Or maybe I can somehow mount al= l of my working disk as a read-only mount?
 
(3) It seem= s 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 d= o 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 windo= ws, and probably cygwin.
 
regards, and thanks for all t= he help.
 
-Nick
-----Original Message-----
From: KAREN THODE [mailto:thode1= 2@msn.com]
Sent: Tuesday, July 08, 2003 4:02 PM
To: = Nick Triantos; freebsd-gnats-submit@freebsd.org
Subject: Re: i3= 86/53620: Kernel panics / reboots during install of 5.1 to 40GB disk on 4= 4

 
Boot off of the 20 GB hard = drive.  Now, you need to make a copy of /usr/src/sys/i386/conf/GENERIC into a new di= rectory called /usr/dbgkern.  Now open up /usr/dbgkern/GENERIC in a = text editor.  Look for a line that says "#makeoptions   DE= BUG=3D-g" and remove the pound sign from the beginning.  Now change = "ident  GENERIC" to "ident  DBGKERN".  Save this file= as DBGKERN.  Exit the editor.  Now, type these commands (witho= ut the outer set of quotes) into the console while logged in as root= .
"cd /usr/dbgkern"
"rm GENERIC"
"cd /us= r/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 serial cable. = You have to type the command "gdb -k [-c name-of-core-dump-file]" into the s= hell while logged in as root, replacing name-of-core-dump-file with the n= ame of the kernel core dump.  Once gdb displays the (kgdb) prompt, y= ou can use hbreak {[file:]function|address} to set a breakpoint (maximum = 4), bt to perform a backtrace of the stack, c to continue running the ker= nel, next to step over function calls, step to step into function calls, = print expr to print the value of expr on the terminal screen, and quit to= quit gdb.
 
Lucas
----- Ori= ginal Message -----
From: Nick Triantos
S= ent: Monday, July 07, 2003 11:57 AM
To: 'KAREN THODE'
Su= bject: 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 h= ow to do that?  Since I'm booting from the CD image, I'm not sure ho= w I can get it to execute from a different kernel.  I suppose I can = build a special CD image, is that what you'd suggest?  I've also nev= er done kernel-level debugging of bsd, I assume it's done via serial inte= rface?
&= nbsp;
ch= eers,
-Nick
=
-----Original Message-----
From: KAREN THODE [= mailto:thode12@msn.com]
Sent: Sunday, July 06, 2003 2:07 PMTo: freebsd-gnats-submit@FreeBSD.org; nick@triantos.com
Sub= ject: Re: i386/53620: Kernel panics / reboots during install of 5.1 t= o 40GB disk on 44

Do you think that you could b= uild a debugging kernel with crashdumps enabled and then replicate t= he kernel panic?  If you can, post a panic message and gdb backtrace= as a follow-up.
 
Lucas

------=_NextPart_001_0000_01C3497F.5CD3BB40-- From owner-freebsd-i386@FreeBSD.ORG Mon Jul 14 01:13:55 2003 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFAD937B401; Mon, 14 Jul 2003 01:13:55 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id CED1043F93; Mon, 14 Jul 2003 01:13:54 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h6E8Dss8083934; Mon, 14 Jul 2003 04:13:54 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h6E8Ds9i083933; Mon, 14 Jul 2003 08:13:54 GMT Date: Mon, 14 Jul 2003 08:13:54 GMT Message-Id: <200307140813.h6E8Ds9i083933@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [-CURRENT tinderbox] failure on i386/i386 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 08:13:56 -0000 TB --- 2003-07-14 06:40:25 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-07-14 06:40:25 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-14 06:42:29 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-07-14 07:47:01 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Building an up-to-date make(1) >>> Kernel build for GENERIC started on Mon Jul 14 07:47:02 GMT 2003 >>> Kernel build for GENERIC completed on Mon Jul 14 08:01:22 GMT 2003 TB --- 2003-07-14 08:01:22 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- /usr/bin/make -B LINT TB --- 2003-07-14 08:01:22 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Building an up-to-date make(1) >>> Kernel build for LINT started on Mon Jul 14 08:01:23 GMT 2003 [...] dbdisply.o: In function `AcpiDbDisplayArguments': dbdisply.o(.text+0x69c): undefined reference to `AcpiDmDisplayArguments' dbdisply.o: In function `AcpiDbDisplayResults': dbdisply.o(.text+0x772): undefined reference to `AcpiDmDisplayInternalObject' dbdisply.o: In function `AcpiDbDisplayResultObject': dbdisply.o(.text+0x99c): undefined reference to `AcpiDmDisplayInternalObject' dbdisply.o: In function `AcpiDbDisplayArgumentObject': dbdisply.o(.text+0xa0c): undefined reference to `AcpiDmDisplayInternalObject' *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2003-07-14 08:13:53 - /usr/bin/make returned exit code 1 TB --- 2003-07-14 08:13:53 - ERROR: failed to build lint kernel TB --- 2003-07-14 08:13:53 - tinderbox aborted From owner-freebsd-i386@FreeBSD.ORG Mon Jul 14 13:11:52 2003 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7FD337B401; Mon, 14 Jul 2003 13:11:52 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1343543FCB; Mon, 14 Jul 2003 13:11:52 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h6EKBps8064466; Mon, 14 Jul 2003 16:11:51 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h6EKBpYu064465; Mon, 14 Jul 2003 20:11:51 GMT Date: Mon, 14 Jul 2003 20:11:51 GMT Message-Id: <200307142011.h6EKBpYu064465@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [-CURRENT tinderbox] failure on i386/i386 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 20:11:53 -0000 TB --- 2003-07-14 18:42:18 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-07-14 18:42:18 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-14 18:44:34 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-07-14 19:44:57 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Building an up-to-date make(1) >>> Kernel build for GENERIC started on Mon Jul 14 19:44:57 GMT 2003 >>> Kernel build for GENERIC completed on Mon Jul 14 19:59:21 GMT 2003 TB --- 2003-07-14 19:59:21 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- /usr/bin/make -B LINT TB --- 2003-07-14 19:59:21 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Building an up-to-date make(1) >>> Kernel build for LINT started on Mon Jul 14 19:59:22 GMT 2003 [...] dbdisply.o: In function `AcpiDbDisplayArguments': dbdisply.o(.text+0x69c): undefined reference to `AcpiDmDisplayArguments' dbdisply.o: In function `AcpiDbDisplayResults': dbdisply.o(.text+0x772): undefined reference to `AcpiDmDisplayInternalObject' dbdisply.o: In function `AcpiDbDisplayResultObject': dbdisply.o(.text+0x99c): undefined reference to `AcpiDmDisplayInternalObject' dbdisply.o: In function `AcpiDbDisplayArgumentObject': dbdisply.o(.text+0xa0c): undefined reference to `AcpiDmDisplayInternalObject' *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2003-07-14 20:11:51 - /usr/bin/make returned exit code 1 TB --- 2003-07-14 20:11:51 - ERROR: failed to build lint kernel TB --- 2003-07-14 20:11:51 - tinderbox aborted From owner-freebsd-i386@FreeBSD.ORG Tue Jul 15 00:51:00 2003 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 211B137B401; Tue, 15 Jul 2003 00:51:00 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F9FD43F75; Tue, 15 Jul 2003 00:50:59 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h6F7ows8058498; Tue, 15 Jul 2003 03:50:58 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h6F7owjn058497; Tue, 15 Jul 2003 07:50:58 GMT Date: Tue, 15 Jul 2003 07:50:58 GMT Message-Id: <200307150750.h6F7owjn058497@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [-CURRENT tinderbox] failure on i386/i386 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 07:51:00 -0000 TB --- 2003-07-15 06:18:18 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-07-15 06:18:18 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-15 06:20:28 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-07-15 07:24:08 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Building an up-to-date make(1) >>> Kernel build for GENERIC started on Tue Jul 15 07:24:08 GMT 2003 >>> Kernel build for GENERIC completed on Tue Jul 15 07:38:29 GMT 2003 TB --- 2003-07-15 07:38:29 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- /usr/bin/make -B LINT TB --- 2003-07-15 07:38:29 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Building an up-to-date make(1) >>> Kernel build for LINT started on Tue Jul 15 07:38:30 GMT 2003 [...] dbdisply.o: In function `AcpiDbDisplayArguments': dbdisply.o(.text+0x69c): undefined reference to `AcpiDmDisplayArguments' dbdisply.o: In function `AcpiDbDisplayResults': dbdisply.o(.text+0x772): undefined reference to `AcpiDmDisplayInternalObject' dbdisply.o: In function `AcpiDbDisplayResultObject': dbdisply.o(.text+0x99c): undefined reference to `AcpiDmDisplayInternalObject' dbdisply.o: In function `AcpiDbDisplayArgumentObject': dbdisply.o(.text+0xa0c): undefined reference to `AcpiDmDisplayInternalObject' *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2003-07-15 07:50:58 - /usr/bin/make returned exit code 1 TB --- 2003-07-15 07:50:58 - ERROR: failed to build lint kernel TB --- 2003-07-15 07:50:58 - tinderbox aborted From owner-freebsd-i386@FreeBSD.ORG Tue Jul 15 05:40:13 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3872F37B401 for ; Tue, 15 Jul 2003 05:40:13 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B209B43F75 for ; Tue, 15 Jul 2003 05:40:11 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6FCeBUp011391 for ; Tue, 15 Jul 2003 05:40:11 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6FCeBdg011390; Tue, 15 Jul 2003 05:40:11 -0700 (PDT) Resent-Date: Tue, 15 Jul 2003 05:40:11 -0700 (PDT) Resent-Message-Id: <200307151240.h6FCeBdg011390@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Gleb Smirnoff Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB4E837B401 for ; Tue, 15 Jul 2003 05:34:18 -0700 (PDT) Received: from cell.sick.ru (cell.sick.ru [195.91.162.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id B478543F75 for ; Tue, 15 Jul 2003 05:34:17 -0700 (PDT) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.6/8.12.8) with ESMTP id h6FCYFNx003033 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 15 Jul 2003 16:34:15 +0400 (MSD) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.6/8.12.6/Submit) id h6FCYE8O003032; Tue, 15 Jul 2003 16:34:14 +0400 (MSD) Message-Id: <200307151234.h6FCYE8O003032@cell.sick.ru> Date: Tue, 15 Jul 2003 16:34:14 +0400 (MSD) From: Gleb Smirnoff To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: i386/54501: Promise Ultra133 TX2 does not work properly X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gleb Smirnoff List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 12:40:13 -0000 >Number: 54501 >Category: i386 >Synopsis: Promise Ultra133 TX2 does not work properly >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 15 05:40:11 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Gleb Smirnoff >Release: FreeBSD 4.8-STABLE i386 >Organization: Bestcom ISP >Environment: FreeBSD video.bestcom.ru 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 15 15:15:48 M SD 2003 root@fade.bestcom.ru:/usr/obj/usr/src/sys/VIDEO i386 >Description: The box has Promise Ultra133 TX2 installed with one HDD on first channel - Seagate Barracuda, which is properly detected by controllers BIOS. Here is boot -v output: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-STABLE #0: Tue Jul 15 15:15:48 MSD 2003 root@fade.bestcom.ru:/usr/obj/usr/src/sys/VIDEO Calibrating clock(s) ... TSC clock: 266613535 Hz, i8254 clock: 1193179 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 266615912 Hz CPU: Pentium II/Pentium II Xeon/Celeron (266.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping = 4 Features=0x80fbff real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) 0x0033a000 - 0x01ff5fff, 30130176 bytes (7356 pages) avail memory = 29540352 (28848K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7c70 bios32: Entry = 0xfd6ff (c00fd6ff) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x47f pnpbios: Found PnP BIOS data at 0xc00f7c80 pnpbios: Entry = f0000:c432 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0313000. ccd0: Concatenated disk driver VESA: information block 56 45 53 41 02 01 6d 27 00 c0 00 00 00 00 14 00 00 01 10 00 03 01 04 01 00 01 01 01 05 01 11 01 14 01 10 01 13 01 02 01 06 01 12 01 7c 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 13 mode(s) found VESA: v1.2, 1024k memory, flags:0x0, mode table:0xc02ba754 (1000014) VESA: Cirrus Logic GD-5436/46 VGA Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x80000090 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1013, dev=0x00b8, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base fd000000, size 24 found-> vendor=0x105a, dev=0x4d69, revid=0x02 class=01-80-85, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 3, range 32, base 0000fcb8, size 3 map[14]: type 3, range 32, base 0000fcc8, size 2 map[18]: type 1, range 32, base 0000fcc0, size 3 map[1c]: type 3, range 32, base 0000fccc, size 2 map[20]: type 1, range 32, base 0000fcd0, size 4 map[24]: type 1, range 32, base fedf8000, size 14 found-> vendor=0x9004, dev=0x8078, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base 0000f800, size 8 map[14]: type 1, range 32, base fedff000, size 12 found-> vendor=0x9004, dev=0x6078, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000e800, size 8 map[14]: type 1, range 32, base fedfe000, size 12 found-> vendor=0x8086, dev=0x1229, revid=0x01 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base fedfd000, size 12 map[14]: type 1, range 32, base 0000fce0, size 5 map[18]: type 1, range 32, base feb00000, size 20 pci0: on pcib0 Correcting Natoma config for non-SMP isab0: at device 2.0 on pci0 I/O Recovery Timing: 8-bit 8 clocks, 16-bit 4 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: enabled Interrupt Routing: A: IRQ15, B: disabled, C: disabled, D: IRQ10 MB0: disabled, MB1: isa0: on isab0 atapci0: at device 2.1 on pci0 atapci0: ATA channel disabled by BIOS pci0: (vendor=0x1013, dev=0x00b8) at 4.0 atapci1: port 0xfcd0-0xfcdf,0xfccc-0xfccf,0xfcc0-0xfcc7,0xfcc8-0xfccb,0xfcb8-0xfcbf mem 0xfedf8000-0xfedfbfff irq 15 at device 6.0 on pci0 ata-: ata2 exists, using next available unit number ata2: iobase=0xfcb8 altiobase=0xfcca bmaddr=0xfcd0 ata2: mask=03 ostat0=20 ostat2=50 ata2-master: ATAPI 20 20 ata2-slave: ATAPI 30 30 ata2: mask=03 stat0=20 stat1=30 ata2-master: ATA 25 25 ata2-slave: ATA 25 25 ata2: devices=00 ata2: at 0xfcb8 on atapci1 ata3: iobase=0xfcc0 altiobase=0xfcce bmaddr=0xfcd8 ata3: mask=03 ostat0=20 ostat2=30 ata3-master: ATAPI 20 20 ata3-slave: ATAPI 30 30 ata3: mask=03 stat0=20 stat1=30 ata3-master: ATA 25 25 ata3-slave: ATA 25 25 ata3: devices=00 ata3: at 0xfcc0 on atapci1 using shared irq15. ahc0: port 0xf800-0xf8ff mem 0xfedff000-0xfedfffff irq 9 at device 8.0 on pci0 ahc0: Defaulting to MEMIO on ahc0: Reading SEEPROM...done. ahc0: High byte termination Enabled ahc0: Downloading Sequencer Program... 448 instructions downloaded ahc0: Features 0x5, Bugs 0x25, Flags 0x20481140 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs ahc1: port 0xe800-0xe8ff mem 0xfedfe000-0xfedfefff irq 11 at device 11.0 on pci0 ahc1: Defaulting to MEMIO on ahc1: Reading SEEPROM...done. ahc1: Low byte termination enabled ahc1: Downloading Sequencer Program... 459 instructions downloaded ahc1: Features 0x10101, Bugs 0x35, Flags 0x481540 aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs fxp0: port 0xfce0-0xfcff mem 0xfeb00000-0xfebfffff,0xfedfd000-0xfedfdfff irq 10 at device 12.0 on pci0 fxp0: using memory space register mapping fxp0: Ethernet address 00:a0:c9:23:48:4b fxp0: PCI IDs: 8086 1229 0000 0000 0001 fxp0: Dynamic Standby mode is disabled nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: fxp0 attached Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0:
The same problem can be found in ASUS P4C800 Deluxe=20 Motherboard.
------=_NextPart_000_0003_01C34C47.F3803300-- From owner-freebsd-i386@FreeBSD.ORG Thu Jul 17 14:40:14 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A696B37B401 for ; Thu, 17 Jul 2003 14:40:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A73A743FAF for ; Thu, 17 Jul 2003 14:40:13 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6HLeDUp081984 for ; Thu, 17 Jul 2003 14:40:13 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6HLeDTG081983; Thu, 17 Jul 2003 14:40:13 -0700 (PDT) Resent-Date: Thu, 17 Jul 2003 14:40:13 -0700 (PDT) Resent-Message-Id: <200307172140.h6HLeDTG081983@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Matthew West Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C98B537B401 for ; Thu, 17 Jul 2003 14:36:14 -0700 (PDT) Received: from casper2.cs.uct.ac.za (casper2.cs.uct.ac.za [137.158.96.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CDD443F93 for ; Thu, 17 Jul 2003 14:36:12 -0700 (PDT) (envelope-from mwest@cs.uct.ac.za) Received: from casper.cs.uct.ac.za ([137.158.96.14] ident=root) by casper2.cs.uct.ac.za with esmtp (Exim 3.20 #1) id 19dGQ7-000DzZ-00 for FreeBSD-gnats-submit@freebsd.org; Thu, 17 Jul 2003 23:36:11 +0200 Received: from casper.cs.uct.ac.za (mwest@localhost [127.0.0.1]) by casper.cs.uct.ac.za (8.12.6/8.12.6) with ESMTP id h6HLa8ko023860 for ; Thu, 17 Jul 2003 23:36:08 +0200 (SAST) (envelope-from mwest@casper.cs.uct.ac.za) Received: (from mwest@localhost) by casper.cs.uct.ac.za (8.12.6/8.12.6/Submit) id h6HLa8cV023859; Thu, 17 Jul 2003 23:36:08 +0200 (SAST) Message-Id: <200307172136.h6HLa8cV023859@casper.cs.uct.ac.za> Date: Thu, 17 Jul 2003 23:36:08 +0200 (SAST) From: Matthew West To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: i386/54595: emu10k1 sound driver locks system X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Matthew West List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 21:40:14 -0000 >Number: 54595 >Category: i386 >Synopsis: emu10k1 sound driver locks system >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 17 14:40:13 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Matthew West >Release: FreeBSD 5.1-RELEASE i386 >Organization: University of Cape Town >Environment: FreeBSD 4.8-RELEASE, FreeBSD 5.0-RELEASE and FreeBSD 5.1-RELEASE I've not tried any others yet. >Description: Loading the emu10k1 sound driver module, or building it into the kernel, causes the system to lock hard. Building the kernel with debugging on didn't help much either as the kernel is unable to flush its buffers to disk after the lockup, even though I can still ctrl-alt-esc in the kernel debugger. none2@pci0:12:0: class=0x040100 card=0x80271102 chip=0x00021102 rev=0x08 hdr=0x00 vendor = 'Creative Labs' device = 'EMU10K1 Audio Chipset (SB Live!)' class = multimedia subclass = audio I initially suspected a hardware problem, but the card works perfectly under other operatings systems on the same machine. This appears similar to i386/46646 and i386/44178, and the module and kernel are definitely in sync. >How-To-Repeat: kldload snd_emu10k1 >Fix: >Release-Note: >Audit-Trail: >Unformatted: