Re: Panic on fxp
On Thu, Apr 03, 2003 at 04:10:04PM -0500, Robin P. Blanchard wrote: > # ls -ltr /usr/src/sys/dev/fxp/ > total 116 > -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h > -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h > -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c > -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h "fgrep '$FreeBSD' *fxp*" would be more useful. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Panic on fxp
I'm seeing the same thing. A kernel from first thing this morning paniced the kernel whilst attempting to probe the device. I saw a commit go in shortly after 15.00 and rebuilt the kernel. Kernel built on that commit allows the box to boot, but the device simply doesn't pass (or see) any traffic...Reverted back to a working kernel from 10March. # ls -ltr /usr/src/sys/dev/fxp/ total 116 -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h Peter Wemm wrote: > "Daniel C. Sobral" wrote: > >>It seems recent current doesn't like my fxp. A current from some 10 >>hours ago keeps complaining about device timeout and dma timeout. I >>don't *know* it's fxp fault (for one thing, because it says "unknown"), >>but... >> >>So, two hours ago, I cvsupped and tried a new world. This one panics >>on >>boot, while doing something with fxp (attaching, I think), and doesn't >>even get me a core dump. >> >>I'll try a new world tomorrow. People tweaking fxp, do please try to >>get >>it fixed? > > > Some details would be useful. Pencil and paper perhaps? Serial cable > to another machine and boot -h? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on fxp
Daniel C. Sobral wrote: > Peter Wemm wrote: > >"Daniel C. Sobral" wrote: > > > >>It seems recent current doesn't like my fxp. A current from some 10 > >>hours ago keeps complaining about device timeout and dma timeout. I > >>don't *know* it's fxp fault (for one thing, because it says "unknown"), > >>but... > >> > >>So, two hours ago, I cvsupped and tried a new world. This one panics on > >>boot, while doing something with fxp (attaching, I think), and doesn't > >>even get me a core dump. > >> > >>I'll try a new world tomorrow. People tweaking fxp, do please try to get > >>it fixed? > > > > > >Some details would be useful. Pencil and paper perhaps? Serial cable > >to another machine and boot -h? > > I'll have to see if I can manage a serial cable here. It shouldn't be > difficult, I just have never done it before, let alone on this computer, > so I don't know what traps I might fall into. > > If not that, I'll get at least the functions and the offset of the first > few. But not today. Tomorrow, after a new cvsup and a new world. I see > there were at least two commits to fxp since my last cvsup. This should be fixed in revision 1.30 of if_fxpreg.h that I committed recently. Sorry for that guys. Cheers, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on fxp
Peter Wemm wrote: "Daniel C. Sobral" wrote: It seems recent current doesn't like my fxp. A current from some 10 hours ago keeps complaining about device timeout and dma timeout. I don't *know* it's fxp fault (for one thing, because it says "unknown"), but... So, two hours ago, I cvsupped and tried a new world. This one panics on boot, while doing something with fxp (attaching, I think), and doesn't even get me a core dump. I'll try a new world tomorrow. People tweaking fxp, do please try to get it fixed? Some details would be useful. Pencil and paper perhaps? Serial cable to another machine and boot -h? I'll have to see if I can manage a serial cable here. It shouldn't be difficult, I just have never done it before, let alone on this computer, so I don't know what traps I might fall into. If not that, I'll get at least the functions and the offset of the first few. But not today. Tomorrow, after a new cvsup and a new world. I see there were at least two commits to fxp since my last cvsup. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] No wonder you're tired! You understood so much today. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on fxp
"Daniel C. Sobral" wrote: > It seems recent current doesn't like my fxp. A current from some 10 > hours ago keeps complaining about device timeout and dma timeout. I > don't *know* it's fxp fault (for one thing, because it says "unknown"), > but... > > So, two hours ago, I cvsupped and tried a new world. This one panics on > boot, while doing something with fxp (attaching, I think), and doesn't > even get me a core dump. > > I'll try a new world tomorrow. People tweaking fxp, do please try to get > it fixed? Some details would be useful. Pencil and paper perhaps? Serial cable to another machine and boot -h? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic on fxp
It seems recent current doesn't like my fxp. A current from some 10 hours ago keeps complaining about device timeout and dma timeout. I don't *know* it's fxp fault (for one thing, because it says "unknown"), but... So, two hours ago, I cvsupped and tried a new world. This one panics on boot, while doing something with fxp (attaching, I think), and doesn't even get me a core dump. I'll try a new world tomorrow. People tweaking fxp, do please try to get it fixed? -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Experience is something you don't get until just after you need it. -- Olivier ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic on fxp
In article <[EMAIL PROTECTED]>, Patrick Gardella <[EMAIL PROTECTED]> wrote: > I've been working for a while to try to figure out a problem I'm having > here. > > I did a buildworld Sunday, and started to get kernel panics on boot when > it probed fxp. So I removed fxp from my kernel and loaded it as a > module (via loader.conf.local). It paniced. Then I unloaded the > if_fxp.ko on startup, and it booted. But if I load the fxp module now, > after a full boot, everything is great. Rebooting with fxp in the > kernel or loading the module on boot will cause a panic *every* time. > > Thinking it might be build problem, I redid the build/install/kernel > again on Monday, and am having the same problems. The panics only > started on the upgrade from a -current dated sometime in early July. A problem with these precise symptoms was fixed in revision 1.54 of "src/sys/sys/mbuf.h". Make sure your sources really are up-to-date. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic on fxp
PLEASE read this: http://www.freebsd.org/FAQ/hackers.html#AEN4885 Basically, by just looking at the page fault message, this appears to be the dereferencing of a NULL pointer. That's all that I'm afraid pretty much anybody will be able to conclude from this unless you, at least, provide us with a backtrace as well as an assembly dump of whatever function the crash occured in. On Tue, 22 Aug 2000, Patrick Gardella wrote: > I've been working for a while to try to figure out a problem I'm having > here. > > I did a buildworld Sunday, and started to get kernel panics on boot when > it probed fxp. So I removed fxp from my kernel and loaded it as a > module (via loader.conf.local). It paniced. Then I unloaded the > if_fxp.ko on startup, and it booted. But if I load the fxp module now, > after a full boot, everything is great. Rebooting with fxp in the > kernel or loading the module on boot will cause a panic *every* time. > > Thinking it might be build problem, I redid the build/install/kernel > again on Monday, and am having the same problems. The panics only > started on the upgrade from a -current dated sometime in early July. > > As you will see from below, this is an SMP machine (dual P200) with 256 > Megs RAM. > I am also using NETGRAPH to run PPPoE. > > Any ideas? > > Patrick > > The panic is: > Fatal trap 12: page fault while in kernel mode > mp_lock=0005; cpuid = 0; lapic.id= > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc034e304 > stack pointer = 0x10:0xc038bea8 > frame pointer = 0x10=0xc038bebc > code segment= base 0x0, limit 0xf, type 0x1b > = DPC 0, pres 1, def 32 1, gran 1 > processor eflag = interrupt enabled, resume, IOPC=0 > current process = 0 (swapper) > interrupt mask = net tty bio cam <- SMP:XXX > trap number = 12 > panic: page fault Cheers, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 [EMAIL PROTECTED] * http://www.technokratis.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kernel panic on fxp
I've been working for a while to try to figure out a problem I'm having here. I did a buildworld Sunday, and started to get kernel panics on boot when it probed fxp. So I removed fxp from my kernel and loaded it as a module (via loader.conf.local). It paniced. Then I unloaded the if_fxp.ko on startup, and it booted. But if I load the fxp module now, after a full boot, everything is great. Rebooting with fxp in the kernel or loading the module on boot will cause a panic *every* time. Thinking it might be build problem, I redid the build/install/kernel again on Monday, and am having the same problems. The panics only started on the upgrade from a -current dated sometime in early July. As you will see from below, this is an SMP machine (dual P200) with 256 Megs RAM. I am also using NETGRAPH to run PPPoE. Any ideas? Patrick The panic is: Fatal trap 12: page fault while in kernel mode mp_lock=0005; cpuid = 0; lapic.id= fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc034e304 stack pointer = 0x10:0xc038bea8 frame pointer = 0x10=0xc038bebc code segment= base 0x0, limit 0xf, type 0x1b = DPC 0, pres 1, def 32 1, gran 1 processor eflag = interrupt enabled, resume, IOPC=0 current process = 0 (swapper) interrupt mask = net tty bio cam <- SMP:XXX trap number = 12 panic: page fault To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
