panic's on KDE-launches (but only in WPA Wifi area) / kern/122331

Matthias Apitz guru at unixarea.de
Mon Sep 15 11:20:50 UTC 2008


Hello,

I'm booting my laptop 3 times a day: in the morning at home (WEP area),
when I arrive in my office (WPA area) and in the evening at home
(again);

the sequence is always the same: booting, login into console, startx
which launches via ~/.xinitrc the KDE;

in about 1 of 2-3 cases and only in the office(!) the system panics when
KDE comes up, at the end of the KDE booting and the jingle already
played; today it crashed again and again and after switching off the
Wifi radio on the laptop it came finally up fine;

I did this (Wifi off) because I'm assuming somehow a relation with
http://www.freebsd.org/cgi/query-pr.cgi?pr=122331
where my laptop as well only panic'ed in WPA mode (i.e. in the office)
and with 'bgscan' active; which I now have deactivated;

all these panics look in the debugger more or less like this one:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0xc
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc0788b98
stack pointer           = 0x28:0xe6960acc
frame pointer           = 0x28:0xe6960c50
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1426 (kdeinit)
trap number             = 12
panic: page fault
cpuid = 0
Uptime: 1m36s
Physical memory: 1009 MB
Dumping 129 MB: 114 98 82 66 50 34 18 2

#0  doadump () at pcpu.h:195
195     pcpu.h: No such file or directory.
        in pcpu.h
(kgdb) bt
#0  doadump () at pcpu.h:195
#1  0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc0754719 in panic (fmt=Variable "fmt" is not available.) at /usr/src/sys/kern/kern_shutdown.c:563
#3  0xc0a4905c in trap_fatal (frame=0xe6960a8c, eva=12) at /usr/src/sys/i386/i386/trap.c:899
#4  0xc0a492e0 in trap_pfault (frame=0xe6960a8c, usermode=0, eva=12)
    at /usr/src/sys/i386/i386/trap.c:812
#5  0xc0a49c8c in trap (frame=0xe6960a8c) at /usr/src/sys/i386/i386/trap.c:490
#6  0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc0788b98 in kern_select (td=0xc49d5630, nd=9, fd_in=0x298ad840, fd_ou=0x298ad9c4, 
    fd_ex=0x298adb48, tvp=0x0) at filedesc.h:136
#8  0xc07890de in select (td=0xc49d5630, uap=0xe6960cfc) at /usr/src/sys/kern/sys_generic.c:663
#9  0xc0a49635 in syscall (frame=0xe6960d38) at /usr/src/sys/i386/i386/trap.c:1035
#10 0xc0a2fc70 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196
#11 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) 

the 'current process' (kdeinit in the above crash) changes, but is
always one of the KDE parts; of course the problem is not KDE related,
it is just that the system comes under heavy usage in that moment;

I already run 'memtest 128' for some hours without any noted problem in
memory; test are just passing fine;

the same problem is with 7.0-RELEASE as with RELENG_7;

what can I do to nail this down? it sucks somehow seeing it crashing on
startup in the morning in the office :-((

thx

	matthias

-- 
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <matthias.apitz at oclc.org> - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
A computer is like an air conditioner, it stops working when you open Windows
Una computadora es como aire acondicionado, deja de funcionar si abres Windows


More information about the freebsd-net mailing list