ATA boot hang

After I did a buildworld (10/13), I'm getting a hang on boot on a Compaq DeskPro Workstation: ata1: spurious interrupt - status=0x00 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: setting UDMA100 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc62c5570 ad0: ATA-6 disk at ata0

ATA_IDENTITY soft error

Did a -CURRENT buildworld this AM, and restarted on the new kernel. On detecting ad0, it throws an error: ad0: 38166MB [77545/16/63] at ata0-master UDMA 100 ata1-master: WARNING - ATA_IDENTITY soft error (ECC corrected) What's this? Patrick ___ [EMAIL

Fatal Trap 3?

I'm used to seeing fatal traps 1, 11 and 12, but 3 is a new one to me. Before I go digging into code to try to find out what's wrong, could someone *briefly* explain what a "fatal trap 3: Breakpoint instruction fault" is? I don't want to waste a lot of time on a hardware problem... Patrick T

Re: hang when making port

lready)? On a side note, this also occurs on -current, since I saw it happening right after I installed -current on a new laptop. (Fresh build). I'll dig into it today to see if I can figure out what's causing it. I'd hate to see this happen when 4.2 is released. Patrick --

Re: XFree86 3.3.6_3 build dies on -current

"Rogier R. Mulhuijzen" wrote: > > >In file included from /usr/include/sys/wait.h:93, > > from vgaHW.c:44: > >/usr/include/machine/endian.h:72: syntax error before > >`__uint16_swap_unit32' > >/usr/include/machine/endian.h:72: syntax error before `__x' > > > > > >I've not seen thi

XFree86 3.3.6_3 build dies on -current

I built and installed -current on a laptop yesterday (10/23/00), and went to build XFree86 3.3.6_3 today from the ports directory. It built fine, but when you run make install, it dies, complaining of syntax errors in machine/endian.h: In file included from /usr/include/sys/wait.h:93,

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

Re: Burned by config changes?

ll > be your problem. > > -Dan > > On Tue, Jul 11, 2000 at 09:28:44PM -0400, Patrick Gardella wrote: > > I've somehow been burned by the config changes when I build world > > yesterday. The build went fine, and then I followed the instructions > > on: http://

Burned by config changes?

p, but I'd rather learn how to fix this!) Patrick Gardella To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: -CURRENT make world broken

I build world this morning, and it built fine. Patrick - Original Message - From: Kenneth Wayne Culver <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 30, 1999 12:23 PM Subject: -CURRENT make world broken > I was just wondering if anyone else was having a problem m