Bug #1160

Fatal trap on HEAD while doing nothing special

Added by ahuete.devel over 5 years ago. Updated about 5 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi all,

Recently I had an strange panic on my tiny PIII 900 Mhz machine running
HEAD (03-Nov) but I wasn't doing anything special. Just a ssh session
opened, and few logins on ttys. No X or any other programs running. The
laptop is connected to the network via an atheros compatible cardbus
card and authenticated with WPA PSK.

For convenience, I've put a dump on this URL:
ftp://earthborder.quantumachine.net/pub/DragonFlyBSD/dumps/dump01.tbz2
Below you can find also a backtrace. Please, let me know if I have to
provide further information:

Regards,
Antonio Huete

.............................................................................................................................................................................

#0 dumpsys () at ./machine/thread.h:83
#1 0xc02dad1e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:375
#2 0xc02dae3f in panic (fmt=0xc0531356 "from debugger") at
/usr/src/sys/kern/kern_shutdown.c:800
#3 0xc0164fe5 in db_panic (addr=-1070225257, have_addr=0, count=1,
modif=0xc9c79ae8 "") at /usr/src/sys/ddb/db_command.c:447
#4 0xc0165650 in db_command_loop () at /usr/src/sys/ddb/db_command.c:343
#5 0xc0167c04 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_trap.c:71
#6 0xc04cddbb in kdb_trap (type=12, code=0, regs=0xc9c79c2c) at
/usr/src/sys/platform/pc32/i386/db_interface.c:148
#7 0xc04deafa in trap_fatal (frame=0xc9c79c2c, eva=<value optimized
out>) at /usr/src/sys/platform/pc32/i386/trap.c:1135
#8 0xc04dec8a in trap_pfault (frame=0xc9c79c2c, usermode=0, eva=0) at
/usr/src/sys/platform/pc32/i386/trap.c:1041
#9 0xc04df523 in trap (frame=0xc9c79c2c) at
/usr/src/sys/platform/pc32/i386/trap.c:721
#10 0xc04ceac7 in calltrap () at
/usr/src/sys/platform/pc32/i386/exception.s:785
#11 0xc035a897 in ieee80211_find_rxnode_withkey (ic=0xc9e4a8b8, wh=0x0,
keyix=65535) at /usr/src/sys/netproto/802_11/wlan/ieee80211_node.c:1418
#12 0xc07637a0 in ?? ()
#13 0xc02e384c in lwkt_serialize_handler_call (s=0xc9d96000,
func=0xc07632be, arg=0xc9e4a8b8, frame=0x0) at
/usr/src/sys/kern/lwkt_serialize.c:242
#14 0xc016d4b7 in cbb_func_intr (arg=0xc14a2d60) at
/usr/src/sys/dev/pccard/pccbb/pccbb.c:607
#15 0xc02bde77 in ithread_handler (arg=0xb) at
/usr/src/sys/kern/kern_intr.c:794
#16 0xc02e1846 in lwkt_deschedule_self (td=Cannot access memory at
address 0x8
) at /usr/src/sys/kern/lwkt_thread.c:228
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

History

#1 Updated by tuxillo over 5 years ago

As I said in the subject, it was a fatal trap, not a panic.
I paniced to get the dump.

#2 Updated by sepherosa about 5 years ago

Grab. I believe it is caused by bad memory.

#3 Updated by tuxillo about 5 years ago

Yes, it is caused by bad memory. In fact, I used memtest and it reported there
was a memory problem.
But I've been using this laptop for months now and I've only experimented two
reboots. Is this only luck? :)

Also available in: Atom PDF