From: Dariusz K. <ce...@ta...> - 2004-01-08 00:31:13
|
Hello, I don't know it that was cerb related or not, but I only have cerb as third party module, so either is cerb or bug in freebsd (mine is 4.8) rl0: promiscuous mode disabled tap0: promiscuous mode disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x26 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ccf37 stack pointer = 0x10:0xcda45e30 frame pointer = 0x10:0xcda45e4c 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 = 89886 (python) interrupt mask = trap number = 12 panic: page fault syncing disks... 56 45 35 16 done Uptime: 91d3h55m20s Automatic reboot in 15 seconds - press a key on the console to abort I was playing with openvpn, and bridging, I belive result of crash was when I unloaded bridging module. My kernel was compiled with debugging symbols, but I don't know what to do to get more informations. I have also /var/crash/vmcore.0 file from crash. -- Best regards, Dariusz mailto:ce...@ta... |
From: Pawel J. D. <ni...@ga...> - 2004-01-08 08:48:57
|
On Wed, Jan 07, 2004 at 04:31:03PM -0800, Dariusz Kulinski wrote: +> Fatal trap 12: page fault while in kernel mode +> fault virtual address =3D 0x26 +> fault code =3D supervisor read, page not present +> instruction pointer =3D 0x8:0xc01ccf37 +> stack pointer =3D 0x10:0xcda45e30 +> frame pointer =3D 0x10:0xcda45e4c +> code segment =3D base 0x0, limit 0xfffff, type 0x1b +> =3D DPL 0, pres 1, def32 1, gran 1 +> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 +> current process =3D 89886 (python) +> interrupt mask =3D +> trap number =3D 12 +> panic: page fault +>=20 +> syncing disks... 56 45 35 16 +> done +> Uptime: 91d3h55m20s +> Automatic reboot in 15 seconds - press a key on the console to abort +>=20 +> I was playing with openvpn, and bridging, I belive result of crash was +> when I unloaded bridging module. +>=20 +> My kernel was compiled with debugging symbols, but I don't know what +> to do to get more informations. +> I have also /var/crash/vmcore.0 file from crash. Could you show backtrace? There is a description in developers-handbook how to get backtrace and how to load kld module symbols. --=20 Pawel Jakub Dawidek pa...@da... UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net |
From: Dariusz K. <ce...@ta...> - 2004-01-09 07:35:05
|
Hello Pawel, Thursday, January 8, 2004, 12:49:06 AM, you wrote: > Could you show backtrace? > There is a description in developers-handbook how to get backtrace > and how to load kld module symbols. Ehh, I was trying couple of the times, and it didn't give me any backtrace, I checked logs and I noticed this: Jan 7 16:15:21 freebsd /kernel: dumpon: Jan 7 16:15:21 freebsd /kernel: sysctl: kern.dumpdev Jan 7 16:15:21 freebsd /kernel: : Jan 7 16:15:21 freebsd /kernel: No space left on device Jan 7 16:15:21 freebsd /kernel: swapon: adding /dev/ad0s1b as swap device Jan 7 16:15:21 freebsd /kernel: Loading cerb... Ehh, sorry :((( Since last restart I installed more memory, but didn't increase swap, since I didn't wanted to destroy slices, damn. -- Best regards, Dariusz mailto:ce...@ta... http://eggdrop.takeda.tk - eggdrop help |
From: Simon L. N. <simon@FreeBSD.org> - 2004-01-08 12:46:13
|
On 2004.01.07 16:31:03 -0800, Dariusz Kulinski wrote: > Hello, >=20 > I don't know it that was cerb related or not, but I only have cerb as > third party module, so either is cerb or bug in freebsd (mine is > 4.8) >=20 [snip] > I was playing with openvpn, and bridging, I belive result of crash was > when I unloaded bridging module. Some modules does not handle being unloaded very well, so I don't think it's unlikely that the problem is a FreeBSD bug and not Cerber. I just tested on my 4.9 crashbox and that didn't panic when I unloaded the bridge module, but of course the problem might have been solved after 4.8. --=20 Simon L. Nielsen FreeBSD Documentation Team |
From: Dariusz K. <ce...@ta...> - 2004-01-09 07:44:42
|
Hello Simon, Thursday, January 8, 2004, 4:46:04 AM, you wrote: >> I was playing with openvpn, and bridging, I belive result of crash was >> when I unloaded bridging module. > Some modules does not handle being unloaded very well, so I don't think > it's unlikely that the problem is a FreeBSD bug and not Cerber. > I just tested on my 4.9 crashbox and that didn't panic when I unloaded > the bridge module, but of course the problem might have been solved > after 4.8. You know what, I was unloading bridging and if_tap, on the logs I had: rl0: promiscuous mode disabled tap0: promiscuous mode disabled so I belive that bridging unloaded successfully, but system crashed while I was unloading tap device. -- Best regards, Dariusz mailto:ce...@ta... http://eggdrop.takeda.tk - eggdrop help |