Date: Thu, 18 Jul 2002 09:20:58 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: freebsd-alpha@FreeBSD.ORG Subject: Re: machine checks on a AlphaPC 164LX Message-ID: <15670.49338.264301.989244@grasshopper.cs.duke.edu> In-Reply-To: <15669.57930.427134.220183@grasshopper.cs.duke.edu> References: <15669.57930.427134.220183@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin writes: > > I've got a PC164LX which will crash with a machine check under heavy > disk IO to its on-board CMD 646 ATA controller. <..> > db> tr > Debugger() at Debugger+0x2c > panic() at panic+0x100 > machine_check() at machine_check+0x1f0 > interrupt() at interrupt+0x198 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 4) --- > cia_bwx_inb() at cia_bwx_inb+0x24 > ata_dmastatus() at ata_dmastatus+0x30 <..> > I'm starting to think that this might be just a sick motherboard. Does > anybody else have any feelings about this? > The truely scary thing is that using swiz chipset access, rather the bwx chipset access seems to stablize the machine. I still think I'm going to put it down to a sick motherboard, but I wonder if there's a chance there's something wrong with our CIA bwx code.... Drew 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?15670.49338.264301.989244>