Date: Thu, 21 Jan 1999 01:21:29 -0500 From: "Matthew R. Briggs" <mbriggs@switchboard.net> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: latest install stuff not working? Message-ID: <99012101354000.77614@angelica.alex-va-n013c109.moon.jic.com> References: <13990.41447.527727.342292@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Jan 1999, Andrew Gallatin wrote: >Matthew R. Briggs writes: > > I have an install report of a different nature...my machine, an AS200 > > 4/233, refuses to finish booting and dies with a panic. > > Using the 1/14 SNAP from ftp4.freebsd.org, it loads kernel and > > MFS root, starts detecting devices, and when it reaches my second ethernet > > card (this machine has a built-in Tulip, and another in a PCI slot), it > > dies with a "Possible stack overflow" and this panic: > > > > de1: allocated 10baseT port <--this line from my memory > > Panic: > > stopped at Debugger..ng+0x24: ldq ra,0(sp) <0xfffffc0000861eb0> > > <ra=0xfffffc00004654b8,sp=0xfffffc0000861eb0> > > db> > >This is probably due to an improperly handled interrupt. This is odd, >as I run my AS200 with an additional tulip NIC & it works just fine. > >Can you mail me some boot messages? If you want to condense it, I'm >specifically interested in FreeBSD's opinion of what device is in what >slot and at what irq. I'm also interested in the last few messages >before the panic. > >What OS are you running now? You might want to try typing 'init' at >the SRM console prompt before attempting to boot FreeBSD. > >Cheers, > >Drew >------------------------------------------------------------------------------ >Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin >Duke University Email: gallatin@cs.duke.edu >Department of Computer Science Phone: (919) 660-6590 Well, I tried really hard to get a serial console going, but my Linux minicom doesn't want to send out my commands, making it hard to hit "enter" when it asks for the mfsroot floppy. I'll have to work on that some more, but for now I will type by hand.. Here is what I see on the screen when it panics: ---top of screen--- isa0 Probing for devices on PCI bus 0: ncr0: <ncr 53c810 fast10 scsi> rev 0x02 int a irq 11 on pci0.6.0 chip0: <Intel 82378IB PCI to ISA bridge> rev 0x04 on pci0.7.0 de0: <Digital 21040 Ethernet> rev 0x24 int a irq 5 on pci0.11.0 de0: DEC 21040 [10Mb/s] pass 2.4 de0: address 00:00:f8:23:3e:83 de1: <Digital 21041 Ethernet> rev 0x21 int a irq 10 on pci0.12.0 de1: DEC 21041 [10Mb/s] pass 2.1 de1: address 00:c0:f0:37:22:fd vga0: <Trident model 9660 VGA-compatible display device> rev 0xd3 int a irq 15 on pci0.13.0 <--(aka "Joe random crappy video card," used because my nice TGA board isn't supported yet) mcclock0: <MC146818A real time clock> at port 0x70-0x71 on isa0 sc0 at port 0x60-0x6f irq 1 on isa0 sc0: CGA <4 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq4 on isa0 sio0: type 16550A sio1: reserved for low-level i/o de1: enabling 10baseT port panic: possible stack overflow panic Stopped at Debugger..ng+0x24: ldg ra,0(sp) <0xfffffc0000862238> <ra=0xfffffc00004654b8,sp=0xfffffc0000862238> db> ---bottom of screen--- Hope that helps. This machine usually runs Debian Linux with a 2.2.0pre7 kernel, which works fine (but it's not FreeBSD). I have to flash the SRM console in to boot FreeBSD, and I flash the ARC console back to use Linux. Let me know if I can help in any way...I can't really move forward from here. -- Matt Briggs mbriggs at switchboard dot net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99012101354000.77614>