Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 2002 06:24:35 -0700
From:      Will Andrews <will@csociety.org>
To:        current@FreeBSD.org
Subject:   Re: ACPI instability on Sony VAIOs?
Message-ID:  <20021014132435.GK19874@procyon.firepipe.net>
In-Reply-To: <20021014124931.GJ19874@procyon.firepipe.net>
References:  <20021014124931.GJ19874@procyon.firepipe.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 14, 2002 at 05:49:31AM -0700, Will Andrews wrote:
> The last time I tried to upgrade this machine (and it worked) is
> apparently March 29, 2002.  It badly needs an upgrade, and since
> we need to make -current more usable for 5.0R, if any ACPI or
> whatever hackers can tell me what they need I'll get it.  I can
> attach a serial console on the laptop if necessary.

For shits and grins, I set up a serial debugging line, built a
GDB/DDB debugging kernel, and all that stuff.  The remote debugger
connection seems to be working okay, but this is all I'm getting
from GDB:

(kgdb) bt
#0  0xc0399eb4 in ?? ()
#1  0xc0234d0b in ?? ()
#2  0xc02291b1 in ?? ()
#3  0xc05ad049 in ?? ()
#4  0xc05abe4b in ?? ()
#5  0xc05abff4 in ?? ()
#6  0xc05ac8d5 in ?? ()
#7  0xc05a828a in ?? ()
#8  0xc05a8da0 in ?? ()
#9  0xc02478f0 in ?? ()
#10 0xc0248328 in ?? ()
#11 0xc05a23f4 in ?? ()
#12 0xc05a1d27 in ?? ()
#13 0xc02478f0 in ?? ()
#14 0xc0248328 in ?? ()
#15 0xc03a485c in ?? ()
#16 0xc02478f0 in ?? ()
#17 0xc0249868 in ?? ()
#18 0xc0396cd5 in ?? ()
#19 0xc0210775 in ?? ()
(kgdb)

The only thing suspicious is, GDB says at the start:

---------------------------
<1 3760-0> (8:06:13) [will@puck ~]% gdb -k kernel.debug
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License,
and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty"
for details.
This GDB was configured as "i386-unknown-freebsd"...Deprecated
bfd_read called at
/net/puck/stable/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarf2read.c
line 3049 in dwarf2_read_section


Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
---------------------------

Ok, then I figured, this is probably an old GDB problem.  So I
started GDB 5.2 instead...

---------------------------
<1 3767-0> (8:21:07) [will@puck ~]% gdb52 kernel.debug
GNU gdb 5.2 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd4.7"...
(gdb) target remote /dev/cuaa0
Remote debugging using /dev/cuaa0
Debugger (msg=0x2a "") at ../../../i386/i386/db_interface.c:323
323     ../../../i386/i386/db_interface.c: No such file or directory.
        in ../../../i386/i386/db_interface.c
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
(gdb) bt
#0  Debugger (msg=0x2a "") at ../../../i386/i386/db_interface.c:323
#1  0xc03a339b in init386 (first=42) at ../../../i386/i386/machdep.c:1807
(gdb) continue
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
Debugger (msg=0x12 <Address 0x12 out of bounds>) at atomic.h:260
260     atomic.h: No such file or directory.
        in atomic.h
(gdb) bt
#0  Debugger (msg=0x12 <Address 0x12 out of bounds>) at atomic.h:260
#1  0xc0234d0b in panic (fmt=0x0) at ../../../kern/kern_shutdown.c:494
#2  0xc02291b1 in free (addr=0xc05ad021, type=0xc05b5580)
    at ../../../kern/kern_malloc.c:222
#3  0xc05ad049 in ?? ()
#4  0xc05abe4b in ?? ()
#5  0xc05abff4 in ?? ()
#6  0xc05ac8d5 in ?? ()
#7  0xc05a828a in ?? ()
#8  0xc05a8da0 in ?? ()
#9  0xc02478f0 in device_probe_and_attach (dev=0xa) at device_if.h:39
#10 0xc0248328 in bus_generic_attach (dev=0x12)
    at ../../../kern/subr_bus.c:1725
#11 0xc05a23f4 in ?? ()
#12 0xc05a1d27 in ?? ()
#13 0xc02478f0 in device_probe_and_attach (dev=0x4) at device_if.h:39
#14 0xc0248328 in bus_generic_attach (dev=0x12)
    at ../../../kern/subr_bus.c:1725
#15 0xc03a485c in nexus_attach (dev=0xc0effc80)
    at ../../../i386/i386/nexus.c:231
#16 0xc02478f0 in device_probe_and_attach (dev=0xc0effc80) at device_if.h:39
#17 0xc0249868 in root_bus_configure () at ../../../kern/subr_bus.c:2241
#18 0xc0396cd5 in configure (dummy=0x0) at ../../../i386/i386/autoconf.c:144
#19 0xc0210775 in mi_startup () at ../../../kern/init_main.c:214
(gdb) 
---------------------------

Seems to be OK.  Guess I need to have the source tree on the
debugging machine, not the target.  :-]
I'll get to that later I guess.  Comments appreciated.

Is there any way to use the same serial line to obtain the kernel
messages printed on the console (as it's an x86 box)?

regards,
-- 
wca

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?20021014132435.GK19874>