Re: panic ! panic ! panic !
On Wed, May 12, 1999 at 06:41:15PM +0200, Gianmarco Giovannelli gma...@scotty.masternet.it wrote: Ok... it's a bit long ... (Tell me there isn't a command to write the trace output on a disk :-) After the panic make by screen ... trace Stopped at ttyflush+0x48: movl 0x14(%eax), %eax [chop] A nightmare ! :-) You can enable serial console for one of your serial ports, preferably sio0 (COM1) and boot with -h (check /usr/src/sys/i386/conf/LINT). Then you can capture all such things if you have null-modem cable connected to another computer and some terminal program running on the port the cable is connected. Otherwise you can use true terminal. Default connection speed is 9600 bps and no extraordinary settings, 8N1. -- Vallo Kallaste va...@matti.ee To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with screen, but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
At 12/05/99, you wrote: Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. Pardon, but I am not be able to figure by myself what you asked to me... If you can explain me step by step in a newbie way I can do everything ... The crashes is easily reproducible... Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
Luoqi Chen writes : I'm trying to get a crash dump myself, but the kernel I have right now, is screwing up my keyboard, and I cannot even log in! I will try again. Geoff. After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with screen, but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
At least put DDB in your kernel, type trace when it panics and tell us what it says. In message 19990512154854.78032.qm...@rucus.ru.ac.za, Geoff Rehmet writes: Luoqi Chen writes : I'm trying to get a crash dump myself, but the kernel I have right now, is screwing up my keyboard, and I cannot even log in! I will try again. Geoff. After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with screen, but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: panic ! panic ! panic !
Only one problem with that - screen and keyboard are not responding when it panics. I'm hoping that I will be able to get a dump which I can look at post mortem. I'm going to try again though. The kernel I have at the moment is totally messing up my keyboard, and I cannot even get a single user login! Geoff. -Original Message- From: Poul-Henning Kamp [mailto:p...@critter.freebsd.dk] Sent: 12 May 1999 05:56 To: Geoff Rehmet Cc: lu...@watermarkgroup.com; curr...@freebsd.org Subject: Re: panic ! panic ! panic ! At least put DDB in your kernel, type trace when it panics and tell us what it says. In message 19990512154854.78032.qm...@rucus.ru.ac.za, Geoff Rehmet writes: Luoqi Chen writes : I'm trying to get a crash dump myself, but the kernel I have right now, is screwing up my keyboard, and I cannot even log in! I will try again. Geoff. After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with screen, but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
At 12/05/99, you wrote: At least put DDB in your kernel, type trace when it panics and tell us what it says. Ok... it's a bit long ... (Tell me there isn't a command to write the trace output on a disk :-) After the panic make by screen ... trace Stopped at ttyflush+0x48: movl 0x14(%eax), %eax ttyflush (c025f2a0,3,c02601e0,c025f2a0,80047410) at ttyflush+0x48 ttioctl(c025f2a0,80047410,c6860ee4,3,c6860e20) at ttioctl+0x4a9 ptyioctl(f700,80047410,c6860e04,c01de031,c6860e20,c6860eb0) at spec_ioctl+0x44 spec_vnoperate(c686e20,c6860eb0,c0172821,c6860e20,0) at spec_vnoperate+0x15 ufs_vnoperatespec(c6860e20,0,c0a44cc0,4,c6860f90) at ufs_vnoperatespec+0x15 vn_ioctl(c0a44cc0,80047410,c6860ee4,c5de94a0) at vn_ioctl+0xdd ioctl(c5de94a0,c6860f90,28113874,806df09,8073720) at ioctl+0x1ef syscall(2f,2f,2f,8073720,806df09) at syscall+0x126 Xint0x80_syscall() at Xint 0x80_syscall+0x30 A nightmare ! :-) Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
At 12/05/99, you wrote: Ok, what I'd like you to do is, run this command, nm -n /kernel | more the output is the list of symbols in the kernel sorted by their addresses (the left-most column), page through the output, find symbols around the address 0xc0155ca4, and send me those symbol names along with their addresses. c0154d2c T ptrace c0155244 T trace_req c0155250 T stopevent c01552ac t gcc2_compiled. c01552ac T rman_init c015534c T rman_manage_region c0155404 T rman_fini c015549c T rman_reserve_resource c015584c t int_rman_activate_resource c01558a4 T rman_activate_resource c01558bc T rman_await_resource c0155940 t int_rman_deactivate_resource c0155960 T rman_deactivate_resource c0155970 t int_rman_release_resource c0155b18 T rman_release_resource c0155b2c t gcc2_compiled. c0155b2c T soo_read c0155b50 T soo_write c0155b78 T soo_ioctl c0155cd8 T soo_poll c0155cf8 T soo_stat c0155d28 T soo_close c0155d4c t gcc2_compiled. c0155d4c T ipcperm c0155dd8 t gcc2_compiled. c0155dd8 t msginit c0155f3c T msgsys c0155f6c t msg_freehdr c0156010 T msgctl c01561f0 T msgget c015638c T msgsnd c015678c T msgrcv c0156aa0 t gcc2_compiled. c0156aa0 t seminit c0156b38 T semsys c0156b9c T semconfig c0156bfc t semu_alloc c0156cb4 t semundo_adjust c0156da8 t semundo_clear c0156e1c T __semctl c0157398 T semget c01575c4 T semop c0157988 T semexit c0157b00 t gcc2_compiled. c0157b00 t shm_find_segment_by_key but now the kernel is changed because I add options ddb so you are more interested in the old kernel that was up when the crahs happens : This is : c0154084 T shmctl c0154190 t shmget_existing c0154238 t shmget_allocate_segment c015442c T shmget c0154488 T shmsys c01544b8 T shmfork c0154538 T shmexit c0154598 t shminit c01545ec t gcc2_compiled. c01545ec T ttyopen c0154644 T ttyclose c01546c4 T ttyinput c0154df8 t ttyoutput c0154f5c T ttioctl c0155a70 T ttypoll c0155b1c T ttpoll c0155b50 t ttnread c0155b94 T ttywait c0155c34 t ttywflush c0155c5c T ttyflush c0155d68 T termioschars c0155d80 T ttychars c0155d94 T ttyblock c0155dd8 t ttyunblock c0155e1c T ttstart c0155e38 T ttylclose c0155e64 T ttymodem c0155f38 t ttypend c0155fa0 T ttread c0156560 T ttycheckoutq c015660c T ttwrite c01569a0 t ttyrub c0156b3c t ttyrubo c0156b78 t ttyretype c0156c54 t ttyecho c0156ce0 T ttwakeup c0156d30 T ttwwakeup c0156d9c T ttspeedtab c0156dc8 T ttsetwater c0156f40 T ttyinfo c0157100 t proc_compare c01571cc T tputchar c0157224 T ttysleep c0157260 t gcc2_compiled. c0157260 t ttcompatspeedtab c0157290 T ttsetcompat c0157484 T ttcompat c01576e8 t ttcompatgetflags c0157840 t ttcompatsetflags c015797c t ttcompatsetlflags c0157a9c t gcc2_compiled. c0157a9c T ldisc_register and the trace of ddb on panic (new kernel) generated by screen is : trace Stopped at ttyflush+0x48: movl 0x14(%eax), %eax ttyflush (c025f2a0,3,c02601e0,c025f2a0,80047410) at ttyflush+0x48 ttioctl(c025f2a0,80047410,c6860ee4,3,c6860e20) at ttioctl+0x4a9 ptyioctl(f700,80047410,c6860e04,c01de031,c6860e20,c6860eb0) at spec_ioctl+0x44 spec_vnoperate(c686e20,c6860eb0,c0172821,c6860e20,0) at spec_vnoperate+0x15 ufs_vnoperatespec(c6860e20,0,c0a44cc0,4,c6860f90) at ufs_vnoperatespec+0x15 vn_ioctl(c0a44cc0,80047410,c6860ee4,c5de94a0) at vn_ioctl+0xdd ioctl(c5de94a0,c6860f90,28113874,806df09,8073720) at ioctl+0x1ef syscall(2f,2f,2f,8073720,806df09) at syscall+0x126 Xint0x80_syscall() at Xint 0x80_syscall+0x30 Hope it helps... Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
Pardon, but I am not be able to figure by myself what you asked to me... If you can explain me step by step in a newbie way I can do everything ... The crashes is easily reproducible... No offense, but are you sure you should even be running -current? A certain amount of skill in doing such diagnosis is generally considered mandatory for people running it, even though many people who shouldn't be doing so for that reason still do it. :) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
On Wednesday, 12 May 1999 at 18:41:15 +0200, Gianmarco Giovannelli wrote: At 12/05/99, you wrote: At least put DDB in your kernel, type trace when it panics and tell us what it says. Ok... it's a bit long ... (Tell me there isn't a command to write the trace output on a disk :-) You should have a kernel built with the -g option, and have enabled dumps. Then you can analyse the dump at your leisure, and you'll also get more information. There's a section in the handbook about it. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
