Re: Freebsd vs. linux
Did I miss something here? If so, please forgive the intrusion and waste of bandwidth. But I don't recall David saying that FreeBSD had a superior human interface... anywhere. I tend to agree with David having had to try to build software on my FBSD systems that came from the 'Linux community' (i.e. stuff outside of the ports or packages trees) and some of it has a MS-ish 'feel' in that it's our way or the highway. Much of this stuff seems to have a definite MS look-and-feel and even to the point of MS-like annoyances. I agree with you however that Linux is lovable. Indeed. I am fortunate enough to work for a company who uses it in every one of it's 3300+ stores across the nation. And it does things that MS can only DREAM of doing. What really separates the OS's though is the kernel. Not userland software. In my humble ( and somewhat limited ) opinion the BSD kernel has proven to be far more robust and reliable than it's Linux counterpart. I've used FBSD since 2.1.0 and in all but a few occasions, FBSD's TCP/IP and networking performance exceeded any of the Linux distros performance by margins of as little as 5%, to as much as 20% in measurable throughput. ( I used to have a lot of time on my hands so I could fool with such things) >From a personal standpoint, what bugs me MOST about the Linux kernel, is the "thread-is-a-process" notion. It drives me nuts. (I'll make an appointment tomorrow) The latest 5x FBSD kernels have shown significant progress (and advantage over Linux) in multi-threading in my limited testing. Out of the box Linux distros might be 'prettier' with more elaborate 'default' menu configurations and such. But IMH(and limited)O the kernels can't compete. But let your own bit/byte counts be your guide. Humbly -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Sat 02/12, darren kirby < [EMAIL PROTECTED] > wrote: From: darren kirby [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Sat, 12 Feb 2005 11:41:01 -0800 Subject: Re: Freebsd vs. linux quoth the David Kelly:> Look closely at the Linux community and you'll find its mostly> ex-Windows users focused on what Microsoft is doing. The desire is to> one-up Microsoft at Microsoft's own game. Their definition of> "computer" and "human interface" was written by Microsoft and still> can't think outside of that box.I think your interpretation here is a tad glib. Sure there are thousands of people coming to Linux because they 'hate' MS. Sure they don't know gcc from ppc but I don't think it is fair to call them the 'community', rather a small subset. Do you think these people are writing any software? Are they designing programming interfaces? Do they have a damn thing to do with the development of Linux or any of its supporting software? Hell no. They are just users clogging up the message boards and mailing lists with stupid questions. "Human Interface"? Am I missing something? Can you please tell me where the much superior FreeBSD human interface can be downloaded? In the console they are pretty much the same keystroke for keystroke, and on the desktop it is all the same software...I run FreeBSD and Linux, and I love them both. I am trying to point out that when you slam Linux developers with pettiness and name calling that you are no better than all the lusers slamming MS, and thinking they're leet because they installed Fedora? I have noticed a lot of this on FreeBSD lists, and I think it is counterproductive because it is unprofessional and in the end more people using Linux means more people running free software which benefits _all_ of us...and besides, it is offensive to people like me that just like playing with 'nix boxes and run both.Why can't you just run your FreeBSD and feel superior, silently?> Look closely at the BSD community and you'll find those who are working> at creating a better tool to serv e their needs. Much debate about> exactly what constitutes "better" so there is also quite a bit of> experimenting. What you won't find is Microsoft as the yardstick by> which BSD's measure.>> --> David Kelly N4HHE, [EMAIL PROTECTED]> > Whom computers would destroy, they must first drive mad.>> ___> freebsd-questions@freebsd.org mailing list> http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, send any mail to> "[EMAIL PROTECTED]"-- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org"...the number of UNIX installations has grown to 10, with more
5.3 ata / atapicam issues (update)
Greetings, Just an update I pulled out the Promise adapter and connected my disk to the primary embedded IDE controller (max speed PIO 4) Left the atapi CDRW drive as a SLAVE on the secondary controller. Next, I tried ripping an audio CD with cdda2wav, and to my surprise, it was successful. The system did report several messages during the ripping process, like. Feb 3 00:11:33 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=136492211 Feb 3 00:11:34 arabian kernel: ad0: FAILURE - READ_DMA timed out Feb 3 00:11:39 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=136414323 Feb 3 00:11:39 arabian kernel: ad0: FAILURE - READ_DMA timed out Feb 3 00:12:05 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=137621267 Feb 3 00:12:05 arabian kernel: ad0: FAILURE - READ_DMA timed out Feb 3 00:12:11 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=137543379 Feb 3 00:12:11 arabian kernel: ad0: FAILURE - READ_DMA timed out but it was successful. I disabled all ATA DMA (hw.ata.ata_dma="0" my in loader.conf) and tried to rip the disk again. It completed without a single error. Further, I was able to burn 5 CDs on the same drive at ridiculous speeds (48X reported by cdrecord) without a single issue. Hope this helps someone. I'm not at all sure where/what the problem is but I'll be happy to run on the embedded controller for the time being. (while PIO 4 != DMA 133, reliability/functionality is king!) If there's any way I can help solve this issue just say how! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 and atapicam....
Greetings, I seem to have made a small amount of progress with my atapicam boggle. I was able to get a kernel with the atapicam driver configured to boot by taking the drive off of the 2nd channel of my PDC20269-based atapter and configure it as a slave on the 2nd channel of my motherboard's embedded controller. I was even able to 'rip' a disk using cdda2wav. I attempted to rip a 2nd one but it failed with an I/O error. A dmesg reveals... cd9660: RockRidge Extension acd0: WARNING - READ_CD read data overrun 61152>2352 cd9660: RockRidge Extension acd0: timeout waiting for ATAPI ready acd0: timeout waiting for ATAPI ready acd0: timeout waiting for ATAPI ready acd0: timeout waiting for ATAPI ready acd0: READ_BIG trying to write on read buffer acd0: WARNING - removed from configuration (cd1:ata1:0:0:0): cddone: got error 0x16 back (cd1:ata1:0:0:0): lost device (probe0:ata1:0:0:0): Lost target 0??? vm_fault: pager read error, pid 988 (cp) vm_fault: pager read error, pid 988 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) . . . . . vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) (cd1:ata1:0:0:0): removing device entry I don't seem to be able to bring the device back online with any combination of args with either atacontrol or camcontrol. I also find it strange that I could not access the drive with it attached to the motherboard's PRIMARY controller port. I'm beginning to think this may be some sort of funky I/O conflict or something. Going down for a reboot -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
Daniel I wonder if you can mount a CD with a GENERIC kernel? I also wonder if you can avoid the "interrupt storm" with your custom kernel but by disabling atapi dma? (hw.ata.atapi_dma="0" in /boot/loader.conf) If this kernel boots, can you mount a CD? If you get some free time and feel like messing around with it, I'd be curious what you find. Regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:38:14 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error oops, did forget the tixt file ...Daniel S. Haischt schrieb:> I don't know whether this is related to your issue,> but on one of my boxes I am also getting an interrupt> storm with atapicam enabled.> > On FreeBSD 5.2.1 I did not experience any interrupt> storm issues, even if using the same hardware configuration.> > Have a look at the attached text file for a detailed> description ...> > Olivier Certner schrieb:> >> Hi,>>>> Could you give a look at my post dated 04/01/2005 entitled "Freeze >> with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug >> concerning atapicam.>>>> If you have KDE, maybe you should try to reproduce the problem I had. >> I've no time to test your scenario (the one with the EIDE drive, I >> don't have SCSI) now, but I'll try to reproduce it at the beginning of >> next week, in order to see if the freeze happens also on my computer.>>>> Hope this will help us to progress on our issues.>>>> >>> Regards,>>>> Olivier>> >>> ___>> >>> freebsd-questions@freebsd.org mailing list>> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions>> To >>> unsubscribe, send any mail to >> "[EMAIL PROTECTED]"> > >>> -- Mit freundlichen Gruessen / With kind regardsDAn.I.El >>> S. HaischtWant a complete signature??? Type at a shell >>> prompt:$ > finger -l [EMAIL PROTECTED]Hello,recently I >>> updated one of my FreeBSD boxes tov 5.3. This box got a builtin >>> Promise PDC20269UDMA133 controller. Actually it's a controllerwith >>> two IDE channels.So far if using the GENERIC kernel that >>> comeswith FreeBSD, I do not experience any problems.If using >>> my own customized kernel I am gettingthe following error message while >>> booting thesystem:8< 8<8<---8<-8<-Interrupt storm detected on "irq10: atapci1";throtteling interrupt source:>8>8>8--->8->8-After some trail-and-error based investigations,I did figure out that if I don't plugin any deviceinto IDE channel two, the just described errordoes not occur.So it has something to do with IDE channel two.As an additional note - The controller worksunder Linux, FreeBSD 5.3 (GENERIC) and FreeBSD5.2.1 (custom kernel).Any hints on how to solve this issue would begreatly appreciated. ___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 .. acd0: WARNING - READ_TOC read data overrun 12>0
Greetings, This is the first time I really tried to do anything with the atapi CD since installing 5.3. Note that on 5.2.1 I was able to read and write cds on this drive without incident. I sent you my kernel config in a previous msg. Here's the dmesg output.. Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #3: Sat Jan 29 21:17:19 UTC 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ARABIAN-SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Overdrive Pentium II/Pentium II Xeon/Celeron (332.39-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x1632 Stepping = 2 Features=0x183fbff real memory = 369098752 (352 MB) avail memory = 355692544 (339 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 de0: port 0xe480-0xe4ff mem 0xfebfdf80-0xfebfdfff irq 15 at device 17.0 on pci0 de0: [GIANT-LOCKED] de0: SMC 8432BT 21040 [10Mb/s] pass 2.3 de0: Ethernet address: 00:00:c0:85:9a:0d de0: if_start running deferred for Giant pci0: at device 18.0 (no driver attached) ahc0: port 0xe800-0xe8ff mem 0xfebfe000-0xfebfefff irq 9 at device 19.0 on pci0 ahc0: [GIANT-LOCKED] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs atapci1: port 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 mem 0xfebf8000-0xfebfbfff irq 10 at device 20.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xce800-0xcefff,0xcc000-0xce7ff,0xc-0xcbfff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sbc0: at port 0x388-0x38b,0x330-0x331,0x220-0x22f irq 5 drq 5,1 on isa0 sbc0: [GIANT-LOCKED] unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default ad4: 78167MB [158816/16/63] at ata2-master UDMA133 acd0: CDRW at ata3-master PIO4 Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/ad4s2a de0: autosense failed: cable problem? acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 20>0 acd0: WARNING - READ_TOC read data overrun 8>0 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 sio1: 1 more silo overflow (total 1) -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Sat 01/29, Jason Henson < [EMAIL PROTECTED] > wrote: From: Jason Henson [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Sun, 30 Jan 2005 04:59:28 +0000 Subject: Re: 5.3 .. acd0: WARNING - READ_TOC read data overrun 12>0 On 01/29/05 18:40:26, ad5gb wrote:> > Greetings,> > I have discovered more problems with atapi stuff on my system. Tried> to mount a> cd using my IDE CD and the system responded w
Re: 5.3 interrupt storm (atapicam) and I/O error
evices. @@ -242,6 +260,9 @@ device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) +#device disc# discard device (ds0, ds1 etc) + + # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter @@ -251,22 +272,22 @@ device ohci# OHCI PCI->USB interface device usb # USB Bus (required) #deviceudbp# USB Double Bulk Pipe devices -device ugen# Generic -device uhid# "Human Interface Devices" -device ukbd# Keyboard -device ulpt# Printer -device umass # Disks/Mass storage - Requires scbus and da -device ums # Mouse -device urio# Diamond Rio 500 MP3 player -device uscanner# Scanners +#deviceugen# Generic +#deviceuhid# "Human Interface Devices" +#deviceukbd# Keyboard +#deviceulpt# Printer +#deviceumass # Disks/Mass storage - Requires scbus and da +#deviceums # Mouse +#deviceurio# Diamond Rio 500 MP3 player +#deviceuscanner# Scanners # USB Ethernet, requires mii -device aue # ADMtek USB Ethernet -device axe # ASIX Electronics USB Ethernet -device cue # CATC USB Ethernet -device kue # Kawasaki LSI USB Ethernet -device rue # RealTek RTL8150 USB Ethernet +#deviceaue # ADMtek USB Ethernet +#deviceaxe # ASIX Electronics USB Ethernet +#devicecue # CATC USB Ethernet +#devicekue # Kawasaki LSI USB Ethernet +#devicerue # RealTek RTL8150 USB Ethernet # FireWire support -device firewire# FireWire bus code -device sbp # SCSI over FireWire (Requires scbus and da) -device fwe # Ethernet over FireWire (non-standard!) +#devicefirewire# FireWire bus code +#devicesbp # SCSI over FireWire (Requires scbus and da) +#devicefwe # Ethernet over FireWire (non-standard!) -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Sat 01/29, Jason Henson < [EMAIL PROTECTED] > wrote: From: Jason Henson [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Sun, 30 Jan 2005 04:58:31 + Subject: Re: 5.3 interrupt storm (atapicam) and I/O error On 01/28/05 08:38:14, Daniel S. Haischt wrote:> oops, did forget the tixt file ...> > Daniel S. Haischt schrieb:>> I don't know whether this is related to your issue,>> but on one of my boxes I am also getting an interrupt>> storm with atapicam enabled.>> >> On FreeBSD 5.2.1 I did not experience any interrupt>> storm issues, even if using the same hardware configuration.>> >> Have a look at the attached text file for a detailed>> description ...>> >> Olivier Certner schrieb:>> >>> Hi,>>> >>> Could you give a look at my post dated 04/01/2005 entitled "Freeze >>> with CAM (using KsCD)"? Maybe we have fallen on the same kind of >>> bug concerning atapicam.>>> >>> If you have KDE, maybe you should try to reproduce the problem I >>> had. I've no time to test your scenario (the one with the EIDE >>> drive, I don't have SCSI) now, but I'll try to reproduce it at the >>> beginn ing of next week, in order to see if the freeze happens also >>> on my computer.>>> >>> Hope this will help us to progress on our issues.>>> >>> Regards,>>> >>> Olivier>>> ___>>> freebsd-questions@freebsd.org mailing list>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions>>> To unsubscribe, send any mail to "freebsd-questions- >>> [EMAIL PROTECTED]">> >>> >-- > Mit freundlichen Gruessen / With kind regards> DAn.I.El S. Haischt> > Want a complete signature??? Type at a shell prompt:> $ > finger -l [EMAIL PROTECTED]>> Hello,> > recently I updated one of my FreeBSD boxes to> v 5.3. This box got a builtin Promise PDC20269> UDMA133 controller. Actually it's a controller> with two IDE channels.
Re: 5.3 interrupt storm (atapicam)
Greetings, I seem to have made a little progress with the atapicam driver. It seems if I force PIO mode (hw.ata.atapi_dma="0" in /boot/loader.conf) a kernel with the atapicam device will boot. I still cannot access a disk in the drive however either via the acdx device or the new cdx device provided by the atapicam driver. Perhaps you could try adding that line in your /boot/loader.conf and see if it cures your problem -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner < [EMAIL PROTECTED] > wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 .. acd0: WARNING - READ_TOC read data overrun 12>0
Greetings, I have discovered more problems with atapi stuff on my system. Tried to mount a cd using my IDE CD and the system responded with... acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 20>0 acd0: WARNING - READ_TOC read data overrun 8>0 acd0: TIMEOUT - READ_BIG retrying (2 retries left) acd0: FAILURE - READ_BIG timed out acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 20>0 acd0: WARNING - READ_TOC read data overrun 8>0 acd0: TIMEOUT - READ_BIG retrying (2 retries left) acd0: FAILURE - READ_BIG timed out acd0: TIMEOUT - READ_BIG retrying (2 retries left) acd0: FAILURE - READ_BIG timed out I first added hw.ata.atapi_dma="0 to /boot/loader.conf but it didn't help. I then added hw.ata.ata_dma="0" and tried again. If I leave the disc in the drive and reboot it reports: acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 12>0 acd0: WARNING - READ_TOC read data overrun 20>0 acd0: WARNING - READ_TOC read data overrun 8>0 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x21 ascq=0x00 error=4 SMP: AP CPU #1 Launched! Between this and the atapicam problem I found a couple days ago, I'm totally stumped. Any ideas? -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
Greetings, Not sure what to think about this yet but it definitely has something to do with having my ATAPI CD connected to the 2nd channel of my Promise Ultra 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the kernel will boot with atapicam enabled. I don't seem to be able to use my motherboard's embedded EIDE controller with the Promise adapter installed. I don't see any obvious I/O or interrupt conflicts, but I also don't have too much control over it with this old SuperMicro mainboard. Seems odd to me though, since this all worked on 5.2.1. Open for suggestions, but for now I'm going to try to track down the SCSI I/O error problem so I can get some CD burning done (critical system backups) and then I'll see if I can try to figure out if this is an EIDE driver issue or a atapicam issue. If anyone comes up with anything in the meantime... please YELL! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:37:21 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error I don't know whether this is related to your issue,but on one of my boxes I am also getting an interruptstorm with atapicam enabled.On FreeBSD 5.2.1 I did not experience any interruptstorm issues, even if using the same hardware configuration.Have a look at the attached text file for a detaileddescription ...Olivier Certner schrieb:> Hi,> > Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM > (using KsCD)"? Maybe we have fallen on the same kind of bug concerning > atapicam.> > If you have KDE, maybe you should try to reproduce the problem I had. I've no > time to test your scenario (the one with the EIDE drive, I don't have SCSI) > now, but I'll try to reproduce it at the beginning of next week, in order to > see if the freeze happens also on my computer.> > Hope this will help us to progress on our issues.> > Regards,> > Olivier> ___ > freebsd-questions@freebsd.org mailing list> http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, send any mail to "[EMAIL PROTECTED]"-- Mit freundlichen Gruessen / With kind regardsDAn.I.El S. HaischtWant a complete signature??? Type at a shell prompt:$ > finger -l [EMAIL PROTECTED]___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 interrupt storm (atapicam) and I/O error
Greetings, My problem might be slightly different than yours. My system hangs during the boot process whenever I boot a kernel with atapicam enabled. A can't do anything but reboot the box at that point. Maybe this is a good time to learn to use the kernel debugger. When I get home this evening I'll try a few more things. This problem didn't happen in 5.2.1. Thanks! -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner < [EMAIL PROTECTED] > wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 interrupt storm (atapicam) and I/O error
Greetings, I've recently returned to FreeBSD (x86) after my Ultra 30 died. I've had good results with the 5.2* and 5.3 releases until I tried to copy an audio cd with cdda2wav. I'm a bit 'out-of-touch' with the changes to FBSD over the last 4 years or so and am hoping someone can point me straight. First... I tried cdda2wav on the disk in my SCSI CD drive attached to a 2940 controller. Got a boatload of messages like the following which eventually resulted in a hung process. cmd finished after 0.175s timeout 300s 1/ 1/ 1/ 51495 54573%cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: retryable error CDB: 28 00 00 02 36 4F 00 00 1A 00 status: 0x0 (GOOD STATUS) resid: 53248 cmd finished after 0.174s timeout 300s 1/ 1/ 1/ 51496 54573%cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: retryable error CDB: 28 00 00 02 36 68 00 00 0C 00 status: 0x0 (GOOD STATUS) resid: 24576 So I thought I'd try enabling atapicam and trying to use my EIDE CD drive but the system hangs on boot with a message about an "interrupt storm" (throttling input). I tried to disable the 'atapicd' device but it didn't seem to help. Hoping someone has the magic potion for this.. Many thanks! -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
