Re: installworld problem - Solved

2001-08-27 Thread Kris Kennaway
On Mon, Aug 27, 2001 at 10:10:09PM -0700, ADiNA wrote: > hi all, > > seems that the problem is caused by CPUTYPE=k7 in make.conf. change to > i686 and all went well. this is on duron/kt133 combo. maybe this can be > reproduced since i still got the error even after fresh install/cvsup. That soun

Update (was: 4.4-RC: ad0: WRITE command timeout tag=0 serv=0 - resetting)

2001-08-27 Thread francisv
I now have the chipset model: Acer Labs Aladdin ATA33 controller Are there current issues regarding this controller? If there's none, then it might be the cables. My IDE devices: ad0: 19541MB [39704/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-slave using PIO4 --

Re: fxp SCB timeout problems [FIX]

2001-08-27 Thread Mike Tancsa
At 10:52 PM 8/27/2001 -0700, Terry Lambert wrote: >Mike Tancsa wrote: > > >fxp0: port 0xc400-0xc43f mem > > >0xd5001000-0xd5001fff irq 11 at device 8.0 on pci1 > > >fxp0: *** DISABLING DYNAMIC STANDBY MODE IN EEPROM *** > > >fxp0: New EEPROM ID: 0x49a0 > > >fxp0: EEPROM checksum @ 0xff: 0xe441 ->

Re: fxp SCB timeout problems [FIX]

2001-08-27 Thread Terry Lambert
Mike Tancsa wrote: > >fxp0: port 0xc400-0xc43f mem > >0xd5001000-0xd5001fff irq 11 at device 8.0 on pci1 > >fxp0: *** DISABLING DYNAMIC STANDBY MODE IN EEPROM *** > >fxp0: New EEPROM ID: 0x49a0 > >fxp0: EEPROM checksum @ 0xff: 0xe441 -> 0xe443 > >fxp0: *** PLEASE REBOOT THE SYSTEM NOW FOR CORRECT

Re: IRQ Problems with Stable

2001-08-27 Thread Warner Losh
In message <[EMAIL PROTECTED]> Doug Denault writes: : I cvsup'd with date=2001.08.26.23.30.00, with worse results. I am not : sure if this is just another example of known problems. In the hope : that more info will help: I fixed bugs in the ISA fallback and a few other things since then: -

thoughts on %busy in iostat

2001-08-27 Thread mki
It would be cool if iostat would show %busy times, I managed to get this into my local copy (see attached), by taking some of the stuff off of systat. Thoughts? -mohan --- /usr/src/usr.sbin/iostat/iostat.c Thu Aug 16 18:33:52 2001 +++ iostat.cMon Aug 20 10:21:41 2001 @@ -563,14 +563,14 @

Re: IRQ Problems with Stable

2001-08-27 Thread Doug Denault
I cvsup'd with date=2001.08.26.23.30.00, with worse results. I am not sure if this is just another example of known problems. In the hope that more info will help: System -- Dell Latitude LM-166 Microprocessor type/speed: Pentium MMX,166 MHz System chip set : Intel 430MX PCI set I

RE: installworld problem - Solved

2001-08-27 Thread ADiNA
hi all, seems that the problem is caused by CPUTYPE=k7 in make.conf. change to i686 and all went well. this is on duron/kt133 combo. maybe this can be reproduced since i still got the error even after fresh install/cvsup. thanks zaidi --- ADiNA <[EMAIL PROTECTED]> wrote: > Date: Sat, 25 Aug 200

4.4-RC -- ad0: WRITE command timeout tag=0 serv=0 - resetting

2001-08-27 Thread francisv
Hi all, I've updated my 4.3-STABLE box to 4.4-RC but still I get the error: ad0: WRITE command timeout tag=0 serv=0 - resetting I would like to believe that this is not because of FreeBSD but because of the hardware. I'll try to post the detailed spec of the motherboard and IDE HDDs on

Re: kernel panic when bringing up a VLAN interface (netgraph?)

2001-08-27 Thread Mike Tancsa
At 08:37 PM 8/27/2001 -0700, Archie Cobbs wrote: >Mike Tancsa writes: > > >>On a new machine I am trying to bring up a trunked port to my vlan > > >>interface. This is with the most recent fxp patches and STABLE as of > > >>this afternoon > > > > > >4.4-RC FreeBSD 4.4-RC #0: Mon Aug 27 16:46:47 E

Re: kernel panic when bringing up a VLAN interface (netgraph?)

2001-08-27 Thread Archie Cobbs
Mike Tancsa writes: > >>On a new machine I am trying to bring up a trunked port to my vlan > >>interface. This is with the most recent fxp patches and STABLE as of > >>this afternoon > > > >4.4-RC FreeBSD 4.4-RC #0: Mon Aug 27 16:46:47 EDT 2001 > > > >OK, here is a backtrace. If there is more i