Subject: panic on 3.0_BETA uniprocessor
To: None <>
From: Miles Nordin <carton@Ivy.NET>
List: port-alpha
Date: 10/24/2005 02:21:35
I got this panic ~10sec after starting gwenview, which is a KDE
program.  The kernel/userland is 3.0_BETA from 2005-08-24, and the
machine is DS10, which is uniprocessor.  I got a coredump and have a
netbsd.gdb.  I guess the trace is useless---I think maybe gdb is still
broken on alpha, or else I'm using it wrong (should have done 'reboot
0x104' right off the bat, and give up on this old idea of syncing the
disks first?).  If there is likely to be anything interesting in the
core file and someone is interested in looking at it, just let me
know, and I'll be happy to post it somewhere.  Thanks!

(gdb) bt
#0  0xfffffc00007485e8 in dumpsys ()
    at ../../../../arch/alpha/alpha/machdep.c:1226
#1  0xfffffc0000748258 in cpu_reboot (howto=0, bootstr=0x0)
    at ../../../../arch/alpha/alpha/machdep.c:1047
#2  0xfffffc000056195c in db_reboot_cmd (addr=0, have_addr=0, count=0, 
    modif=0x0) at ../../../../ddb/db_command.c:689
#3  0xfffffc00005610c8 in db_command (last_cmdp=0xfffffc0000955aa0, 
    cmd_table=0xfffffc0000951578) at ../../../../ddb/db_command.c:464
#4  0xfffffc0000560c1c in db_command_loop ()
    at ../../../../ddb/db_command.c:255
#5  0xfffffc000056598c in db_trap (type=0, code=0)
    at ../../../../ddb/db_trap.c:101
#6  0xfffffc0000757398 in ddb_trap (a0=1, a1=0, a2=0, entry=3, regs=0x0)
    at ../../../../arch/alpha/alpha/db_interface.c:211
#7  0xfffffc0000300194 in inc6 () at ../../../../arch/alpha/alpha/debug.s:50
#8  0xfffffc000074f98c in trap (a0=1, a1=18446740783697495037, 
    a2=18446739675671500152, entry=3, framep=0xfffffe000eb7bbe8)
    at ../../../../arch/alpha/alpha/trap.c:331
#9  0xfffffc000030038c in XentIF ()
    at ../../../../arch/alpha/alpha/locore.s:461
#10 0xfffffc0000466464 in comintr (arg=0x0) at ../../../../dev/ic/com.c:2147
warning: Hit beginning of text section without finding
warning: enclosing function for address 0x4
This warning occurs if you are debugging a function without any symbols
(for example, in a stripped executable).  In that case, you may wish to
---Type <return> to continue, or q <return> to quit---
increase the size of the search with the `set heuristic-fence-post' command.

Otherwise, you told GDB there was a function where there isn't one, or
(more likely) you have encountered a bug in GDB.