Re: unexpected machine check on 5.0 alpha
Wilko Bulte wrote: Time to check the fan for the CPU, and the air'tunnel' feeding the air to the heatsink. I had one come loose after servicing the machine. I just got a similar crash: unexpected machine check: mces= 0x1 vector = 0x670 param = 0xfc004e10 pc = 0xfc4069bc ra = 0xfc4069b4 curproc = 0xfc001f169200 pid = 23, comm = intr: sym1 panic: machine check cpuid = 1; boot() called on cpu#1 syncing disks, buffers remaining... panic: bdwrite: buffer is not busy cpuid = 1; boot() called on cpu#1 Uptime: 19h27m51s It's an Alphaserver 4100, dual 5/300 with 512 MB RAM and one power supply, running 5.0-RC3 (kernel is GENERIC plus the line from ccd(4)). I had been trying to compile a few large things from the ports collection, Beonex for example, and all the compilations had finished so the main task was dd if=zero of=da2 which had been running from /dev since a few minutes after boot (only a 4 GB disk--I wonder why it's so slow). $ strings /tmp/4100-20030113-cu4.log | grep degrees System temperature is 23 degrees C System temperature is 23 degrees C System temperature is 23 degrees C System temperature is 23 degrees C System temperature is 24 degrees C I was sitting next to it when it crashed, and I would have noticed if the fans had stopped. From earlier logs, I see that the temperature has varied between 21 and 27 Celsius. I don't know what it is now, but it feels warmish when I'm wearing just a tee shirt. There's a fan that constantly blows air into the room, which points toward the back of the computer. Should I run the air conditioner more often? -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unexpected machine check on 5.0 alpha
I wrote: dd if=zero of=da2 I forgot to mention that after the crash, the LED on disk da2 remains lit, as is the one on da0 (which contains /, /tmp, /usr, and /var but not /home). When I had the same disk drives attached to a PC, I could write to them at about 45 kilobytes per second. Multiplying that by 19 hours gives about 3 gigabytes, and it was a 4 gigabyte disk. I was doing the dd in an attempt to follow the recipe posted by Andre Albsmeier on URL:http://groups.google.com/groups?hl=enlr=ie=UTF-8oe=UTF-8th=440939b0f4db6bdbseekm=arg34b%2410hi%241%40FreeBSD.csie.NCTU.edu.twframe=off. I had experienced the same problem that John De Boskey had been having: -- begin log -- # ccdconfig ccd0 128 CCDF_UNIFORM /dev/da2 /dev/da3 /dev/da4 /dev/da5 # ccdconfig -g /etc/ccd.conf # cat /etc/ccd.conf ccd0128 2 /dev/da2 /dev/da3 /dev/da4 /dev/da5 # ls /dev/ccd* /dev/ccd0c # newfs /dev/ccd0c /dev/ccd0c: 16380.2MB (33546752 sectors) block size 16384, fragment size 2048 using 90 cylinder groups of 183.62MB, 11752 blks, 23552 inodes. super-block backups (for fsck -b #) at: 32, 376096, 752160, 1128224, 1504288, 1880352, 2256416, 2632480, 3008544, 3384608, 3760672, 4136736, 4512800, 464, 5264928, 5640992, 6017056, 6393120, 6769184, 7145248, 7521312, 7897376, 8273440, 8649504, 9025568, 9401632, 9777696, 10153760, 10529824, 10905888, 11281952, 11658016, 12034080, 12410144, 12786208, 13162272, 13538336, 13914400, 14290464, 14666528, 15042592, 15418656, 15794720, 16170784, 16546848, 16922912, 17298976, 17675040, 18051104, 18427168, 18803232, 19179296, 19555360, 19931424, 20307488, 20683552, 21059616, 21435680, 21811744, 22187808, 22563872, 22939936, 23316000, 23692064, 24068128, 2192, 24820256, 25196320, 25572384, 25948448, 26324512, 26700576, 27076640, 27452704, 27828768, 28204832, 28580896, 28956960, 29333024, 29709088, 30085152, 30461216, 30837280, 31213344, 31589408, 31965472, 32341536, 32717600, 33093664, 33469728 newfs: ioctl (WDINFO): /dev/ccd0c: can't rewrite disk label: No such process -- end log -- Before adding the ccd line to my kernel configuration file, I had attempted to run ccdconfig while using just the GENERIC kernel (also 5.0-RC3). I suppos e I shouldn't have been surprised that it didn't work: -- begin log -- # ccdconfig ccd0 128 CCDF_UNIFORM /dev/da2 /dev/da3 /dev/da4 /dev/da5 fatal kernel trap: trap entry = 0x4 (unaligned access fault) cpuid = 1 faulting va= 0xe4a00ed opcode = 0x29 register = 0x1b pc = 0xfe0002bd1f1c ra = 0xfe0002bd1eec sp = 0xfe00140898a0 usp= 0x11fff9f8 curthread = 0xfc0017efe1f0 pid = 3658, comm = ccdconfig panic: trap cpuid = 1; boot() called on cpu#1 syncing disks, buffers remaining... panic: bwrite: buffer is not busy??? cpuid = 1; boot() called on cpu#1 Uptime: 18h56m35s Automatic reboot in 15 seconds - press a key on the console to abort -- end log -- -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unexpected machine check on 5.0 alpha
Andrew Gallatin wrote: No, that's a 660. (system machine check). A 670 is much more likely to be bad ram, bad cache, bad CPU, etc. Its not always overheating. It's looking like at least my troubles are not from FreeBSD, but from the hardware, probably the SCSI card. I tried dd if=/dev/zero of=/dev/da3 and got a pair of 670 machine checks, shown below. After I pressed the reset button, the SRM said I/O-detected PCI bus data parity error on IOD0 just after looking at the Symbios SCSI card to which the hard drives are attached (I had gotten this before, when I had tried replacing the Ethernet card). Then there was a 660 machine check, then the SRM crashed--URL:http://people.freebsd.org/~trevor/alpha/4100-20030116-cu2.log. -- begin log -- (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. sym1: unable to abort current chip operation. unexpected machine check: mces= 0x1 vector = 0x670 param = 0xfc004e10 pc = 0xfc642970 ra = 0xfc406f70 curproc = 0xfc001f169200 pid = 23, comm = intr: sym1 panic: machine check cpuid = 1; boot() called on cpu#1 syncing disks, buffers remaining... panic: bwrite: buffer is not busy??? cpuid = 1; boot() called on cpu#1 Uptime: 1h42m51s (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. sym1: unable to abort current chip operation. unexpected machine check: mces= 0x1 vector = 0x670 param = 0xfc004e10 pc = 0xfc642970 ra = 0xfc406f70 curproc = 0xfc001f169200 pid = 23, comm = intr: sym1 panic: machine check cpuid = 1; boot() called on cpu#1 Uptime: 1h42m53s panic: bremfree: removing a buffer not on a queue cpuid = 1; boot() called on cpu#1 Uptime: 1h43m16s sym1: suspicious SCSI data while resetting the BUS. sym1: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x7ff, expecting 0x100 -- end log -- -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create worldwriteable dirs
I've just noticed that something wrong with the new tar in the base system (1.13.25) - when extracting some archives it creates 777 dirs, while permissions in the archive itself are OK (for example GNU make make-3.79.1.tar.gz - top level dir gets 777 as well as several other lowel level dirs). The issue is under investigation. The latest version on ftp://ftp.gnu.org/gnu/tar/ is 1.13. The ones on ftp://alpha.gnu.org/gnu/tar/ (and everything else on that site) are considered unstable. I suppose it's too late to suggest tar 1.13 as a starting point, but maybe this could be kept in mind when importing other GNU products. -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create worldwriteable dirs
Dan Nelson wrote: The latest version on ftp://ftp.gnu.org/gnu/tar/ is 1.13. The ones on ftp://alpha.gnu.org/gnu/tar/ (and everything else on that site) are considered unstable. I suppose it's too late to suggest tar 1.13 as a starting point, but maybe this could be kept in mind when importing other GNU products. The point I was trying to make is perhaps better conveyed by ftp://alpha.gnu.org/README . Tar 1.13 is 3 years old, and has many bugs (incremental backups are unusable, for example). I don't know why the GNU tar programmers decide that certain versions are stable and others are unstable. I do know that the former are found on ftp.gnu.org, and the latter on alpha.gnu.org. Now you know too, in case you didn't already. :-) I just discovered Jorg Schilling's star (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/star.html) . He says that it supports POSIX.1-2001, which I assume dates from last year. It's available in the ports collection and it's under the GNU GPL. The documentation for GNU tar 1.13.25 says that it complies with POSIX 1003.1b, which was drafted in 1987 and completed in 1990. The GNU tar in FreeBSD-STABLE is from 1993 and it still works most of the time! According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug: ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I guess it qualifies as a non-trivial program. :-) On my friend's BSD/OS system, there is no tar--or rather, it's just a hard link to pax: % ls -li `which tar` `which pax` 1819 -r-xr-xr-x 2 bin bin 58288 Jun 12 1998 /bin/pax 1819 -r-xr-xr-x 2 bin bin 58288 Jun 12 1998 /bin/tar Their tar/pax hybrid must check its argv[0]. Isn't that evil? -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make installworld runs out of space on / ...
Removing unused files from /boot/modules can free up space. -- Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
od driver for -CURRENT
I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od driver for magneto-optical disks, which I got from his archives at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/OD/ . I have only tested it a little, but I'm able to do "tar cf /dev/od0 ..." under 4-STABLE and untar under Linux 2.2.16 or FreeBSD 5-CURRENT. If under -CURRENT I boot up while the MO disk (a 640 MB one) is in the drive (Olympus MOS364), the data read from it gets corrupted. That happens with the da driver as well. I merged the changes from the da driver into the od driver, so I probably brought the bug in too. Anyway, it's at http://people.freebsd.org/~trevor/src/od-20010203-current.diff.gz . -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: od driver for -CURRENT
I was able to do: # mount_msdos /dev/od0 /mnt # newfs_msdos /dev/od0 # cp mozilla-win32-0.7.zip /mnt/ under FreeBSD -CURRENT, then unzip the file under Windows 95 OSR2 with no problems. However, the patched sysinstall still crashes, and neither disklabel nor newfs are working: # disklabel -r -w /dev/od0 mo640 disklabel: ioctl DIOCWLABEL: Operation not supported by device # newfs -T mo640 /dev/od0c Warning: Block size restricts cylinders per group to 10. Warning: 3776 sector(s) in last cylinder unallocated /dev/od0c: 1241408 sectors in 76 cylinders of 1 tracks, 16384 sectors 606.2MB in 8 cyl groups (10 c/g, 80.00MB/g, 9600 i/g) super-block backups (for fsck -b #) at: write error: 1241404 newfs: wtfs - writecombine: Invalid argument -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Progress report: Multilingual sysinstall for -current
People who run -CURRENT should be able to read and write English to understand the code comments, report bugs, and post to the lists in English. "If you don't know what to do with -CURRENT, don't install it." You seem to be working from the assumption that people who understand English can't understand any other language. I don't know anything about the design question you raise, except that code which has not yet been written always seems more perfect than that which has. :-) -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNA?
Mike Smith wrote: Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G. 3com 3c410, or D-Link DHN-520? No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom refuse to give us documentation. I don't know whether their chips support version 2.0 of the standard (how important is this?) but Davicom Semiconductor is listed at http://www.freebsd.org/commercial/hardware.html . -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Other Linux stuff...
For trivial cases, the simplest solution would be to just remove /compat/linux/usr/bin/ldd and have our native ldd do the work. If something depends on the switches, this won't work. At http://huizen.dds.nl/~frodol/glibc/problems.html it says: * ldd gives real strange output, sometimes... The ldd script that comes with glibc-2.0.6 handles libc5 executables incorrectly, resulting in strange output. You are probably better off if you always use the ldd that comes with ld.so-1.9.9. Implement this by deleting or renaming /usr/i486-linux-libc6/bin/ldd I've done this under Linux itself, and it worked well. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: netscape
You need to install the XFree86 a.out library package. It's not needed for the bsdi-netscape ports, because those versions of Netscape are statically linked. Most people don't need the a.out X libraries for anything else. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netscape
Are the fixed in Netscape 4.74 bugs not critical for release? Who knows? I don't know of any changelog for Netscape. The release notes are at http://home.netscape.com/eng/mozilla/4.7/relnotes/unix-4.74.html#whatnew . The only change that looks like it applies to us is a new feature to delete all your e-mail when exiting the program. I haven't tried it, but it seems to me that making an alias like alias netscape='/usr/local/bin/netscape rm -rf ~/nsmail/*' or putting something similar in your .logout would achieve the same thing. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
I found that I always got the same fortune quote after reboot, over and over again. It means that /dev/random produce exact the same values after reboot. There were some special instructions for the new random device: 2) If you do not have the randomdev module loaded, ssh will fail in strange and creative ways (like RSA or DH not working for strange reasons). 3) It is not built by default (except as a kernel module), so you either need to add the "options RANDOMDEV" like to your kernel config, or load it at boot time in /dev/loader.conf 4) Make sure that you update your /etc area (mergemaster is your friend). The rndcontrol(8) utility is now OBE, and no longer of relevance. ([EMAIL PROTECTED] from Mark Murray [EMAIL PROTECTED]) -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: burncd fixate error
I'm running 4.0-STABLE and my CDR drive can't write the toc. I tried twice and each time I get the following error: fixating CD, please wait.. burncd: ioctl(CDRIOCCLOSEDISK): Input/output error Hi, Nate. I was getting that error too. Unlike you, I have an H-P 8100 like the ones in the messages you directed us to. I did some testing for Soren Schmidt and he got everything working to my satisfaction. Not everything he fixed was specific to the H-P drives. That was around 6 May and the changes did go into 4.0-STABLE. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs-crypto unknown
Rodney W. Grimes wrote: Oopsss... never mind. I think this has all been folded into the baseline cvs target. *-crypto is no more. Hi, Rodney. This recent message explains what's happening: From: John Polstra [EMAIL PROTECTED] Subject: Re: HEADS UP: Crypto changes coming soon Oops, Alan Edmonds pointed out a typo in my announcement: src-crypto src-eBones src-secure src-sys-crypto will remain valid and unchanged, except that they will become sub-collections of "src-all" instead of the soon-to-be-defunct "cvs-all" collection. ^^^ should say "cvs-crypto" Personally, I use the separate collections because cvsup times out otherwise (I guess my connection is too slow). -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
Matthew Dillon wrote: : May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ). Now, I must say, that there is no way we are going to add that hack back in ... it was a real mess and is simply not worth it, and when we move to the interrupt threading model we can truely make the serial interrupt SMP-safe and do away with the issue once and for all. Looking at the old driver (src/sys/i386/isa/Attic/psm.c,v) I see a note that the hardware offers a polling mode (not implemented in that driver), where the mouse only sends packets after getting requests for them. If there are intractable problems with handling interrupts, perhaps that mode could be used instead (maybe if no one had used the mouse recently, polling could be done less often, to conserve CPU time). I don't know if the mouse problems are related or not, did anyone have jumpy-mouse problems before the SMP cleanup was committed? (i.e. in kernels then two weeks old for 4.0, and four weeks old for 5.0). I'm running 4.0-STABLE from May 5 23:39 PDT and I found one of those messages (just like Jordan's except for the hostname and time). I think I was at the computer when it happened, but I don't remember any erratic movement of the mouse pointer, nor have I ever noticed any under FreeBSD. I have XFree86 3.3.6 running from xdm, using /dev/sysmouse as the mouse device. I have moused running too, and was probably in text mode when the tragedy^H^H^H^H^H^H^H error message happened. My computer has a Digital Equipment Corp. PC7XS-CA three-button mouse, a Winbond W83977TF-AW I/O chip, and Intel 440 BX chip set. I saw this problem a long time ago, most memorably on an IBM PS/2 55SX with an IBM mouse, under Windows 3.0. Sometimes the mouse pointer would move suddenly all around the screen, and programs would behave as though someone were pressing the mouse buttons. Searching the Web, I see that the Linux folks have had the problem too: http://www.tux.org/hypermail/linux-kernel/1999week01/0953.html http://gwyn.tux.org/hypermail/linux-kernel/1999week03/0435.html One wanted to program the remote (polling) mode: http://www.linuxhq.com/guides/KHG/HyperNews/get/khg/333.html . -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel build broken...
during the mkdep, I get: ../../kern/kern_linker.c:49: linker_if.h: No such file or directory ../../kern/link_aout.c:45: linker_if.h: No such file or directory ../../kern/link_elf.c:55: linker_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/compile/MONITOR. And the compile fails. I can't find linker_if.h anywhere. Hi, Eric. I noticed that too, but it's fixed now (for me anyway). I see this in the commit logs: obrien 2000/04/24 16:08:25 PDT Modified files: sys/conf files Log: Add linker_if.m to the mix. Revision ChangesPath 1.359 +2 -1 src/sys/conf/files -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Quickie question on UDMA/33
Western Digital Caviar hard drives that should support UDMA/33, as should the Chipset. Both boot up, trying UDMA mode, throwing ICRC READ ERROR's then kick back down to PIO mode 4. Bios's are set to do auto-chose pio/dma modes. There may be a BIOS option that will disable DMA entirely. I've resolved to simply adding in the rc to reset them to pio mode, to get it over with (but I still get the errors at boot-up prior to the rc doing them). I simply use 'device ata' etc. forms in the knerel config. You might try commenting out this option (if you're using it): options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
I say with 99% certainty that assigning 0.0.0.0 to the interface is a requirement of dhcp. You can't stop using it and expect dhcp to work. The Linux folks stopped doing it: 2.0 supported the net interface 0.0.0.0 IP address convention (meaning the kernel should accept all IP packets). 2.[12] don't, hence things like many bootp/dhcp configurations which used this feature break. The proper fix is to modify bootp/dhcp clients to accomplish the same thing using raw sockets instead. I think dhcpcd (URL:http://www.phystech.com/download/dhcpcd.html) already works this way, but bootpc hasn't been updated yet. --message from David Wragg ([EMAIL PROTECTED]) at http://www.tux.org/hypermail/linux-kernel/1999week05/0601.html __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
trouble with burncd on FreeBSD-CURRENT
uot; drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: parallel port not found. pca0 at port 0x40 on isa0 sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: SB DSP 4.13 on sbc0 unknown0: Generic ESDI/IDE/ATA controller at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown1: WaveTable at port 0x620-0x623 on isa0 unknown2: Game at port 0x200-0x207 on isa0 unknown3: StereoEnhance at port 0x100 on isa0 ad0: 6149MB Maxtor 90645D3 [12495/16/63] at ata0-master using UDMA33 ad1: 3820MB Maxtor 84000A6 [7763/16/63] at ata0-slave using WDMA2 acd0: CD-RW Hewlett-Packard CD-Writer Plus 8100 at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s1a ed0: starting DAD for fe80:0001::0240:05ff:fe39:7de0 ed0: DAD complete for fe80:0001::0240:05ff:fe39:7de0 - no duplicates found WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata delay
Hi! Hi, Thomas. I switched to the ata IDE driver some time ago. Since then, booting stops for about 30 seconds when the driver is installed. It didn't happen when using the old wd driver. In /usr/src/sys/i386/conf/LINT it says: # This option allow you to override the default probe time for IDE # devices, to get a faster probe. Setting this below 1 violate # the IDE specs, but may still work for you (it will work for most # people). # options IDE_DELAY=8000 # Be optimistic about Joe IDE device __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
