Re: 5.3-RC2: Fatal trap 19: non-maskable interrupt trap while in kernel mode

I compiled a kernel without firewire support and made custom miniinst
CD. After that I succesfully installed 5.3-RELEASE. 

No doubt, this is a firewire proble

2004-11-06, szo keltezéssel 18:40-kor Gabor MICSKO ezt írta:
> Quote from Matthew Dillon:
> 
> ":Type '?' for a list of commands, 'help' for more detailed help.
> :OK boot -Dh
> :...
> :fwohci0: OHCI version 1.10 (ROM=1)
> :NMI ISA b1, EISA ff
> :RAM parity error, likely hardware failure.
> :
> :Fatal trap 19: non-maskable interrupt trap while in kernel mode
> :instruction pointer     = 0x8:0xc01e3b6e
> :...
> :interrupt mask          = net tty bio cam
> :kernel: type 19 trap, code=0
> :Stopped at      fwohci_init+0xfa:       movl    %ecx,%edi
> :db> tr
> :fwohci_init(c9823000,c604af18) at fwohci_init+0xfa
> 
>     Ok.  Hmm.  It fails in the same place.  The code in question is
> this:
> 
> ...
> /* Available Isochrounous DMA channel probe */
>         OWRITE(sc, OHCI_IT_MASK, 0xffffffff);
>         OWRITE(sc, OHCI_IR_MASK, 0xffffffff);
>         reg = OREAD(sc, OHCI_IT_MASK) & OREAD(sc, OHCI_IR_MASK);
>         OWRITE(sc, OHCI_IT_MASKCLR, 0xffffffff);
>         OWRITE(sc, OHCI_IR_MASKCLR, 0xffffffff);
>         for (i = 0; i < 0x20; i++)
>                 if ((reg & (1 << i)) == 0)
>                         break;
> ...
> 
>     It fails just after the OREAD's.  My guess is that something in the
>     fwohci init code is blowing up the system hardware.
> 
>     OpenBSD has similar but slightly different initialization code, but
> the
>     differences shouldn't account for the failure. 
> 
>     The question is... when you booted up OpenBSD did it probe the
> firewire
>     interface at all?
> 
>     NetBSD also has similar code, but in NetBSD's case it also clears
> the
>     command pointers after probing the transmit bitmap.  But this occurs
>     after the crash point.
> 
>     In anycase, my guess is that if you do not use firewire you can
> compile
>     up a DragonFly kernel that does not probe the firewire controller
> and
>     it will work.  It is clearly NOT a ram problem... it's definitely a
>     firewire initialization issue that is causing the firewire hardware
> to
>     blow up the system bus.
> 
>     If you have the ability to compile up DragonFly kernels with some
> patches
>     and want to try to get the firewire working I could put together a
> patch
>     for you to try."
> 
> Please read this thread:
> 
> http://marc.theaimsgroup.com/?t=109967176800001&r=1&w=2
> 
> I have problem ONLY with FreeBSD 5.x and DragonFly BSD. IMHO this is a
> FreeBSD specific thing. CPU not overclocked, memtest86 said my memory
> module is OK. I tested this thing six different brand new memory module.
> Maybe this is a firewire specific problem. 
> 
> 2004-11-06, szo keltezéssel 17:51-kor Hans Lambermont ezt írta:
> > Gabor MICSKO wrote:
> > 
> > > I've tried to install FreeBSD 5.3-RC2, FreeBSD 5.3-RC*, FreeBSD
> > > 5.2.1-RELEASE, FreeBSD 5.2-RELEASE on my amd64 based laptop, but at
> > > boot kernel is paniced. 
> > 
> > Just to be clear about the obvious:
> > 
> > > NMI ISA a1, EISA ff
> > > RAM parity error, likely hardware failure.
> >   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> > I'm not surprised you get a kernel panic with this system. Your RAM has
> > faults.  Unless you're absolutely sure this is not the case and the NMI
> > complaint is bogus (I see you've tested with various other OSes, and
> > even then it might be true) I suggest swapping RAM and trying again.
> > 
> > regards,
> >    Hans Lambermont
-- 
Micskó Gábor
HP Accredited Platform Specialist, System Engineer (APS, ASE)
Szintézis Computer Rendszerház Rt.      
H-9021 Győr, Tihanyi Árpád út 2.
Tel: +36-96-502-216
Fax: +36-96-318-658
E-mail: gmicsko_at_szintezis.hu
Web: http://www.hup.hu/
GPG Key fingerprint: 6FA1 D8BF 3C73 0570 ED5D  82AC A3BE 4E6A CF95 5F50