Re: strange ATA behavior with -STABLE
Eric Olsen <[EMAIL PROTECTED]> writes: > acd0: CDROM at ata1-slave PIO4 ... >> sysctl -a | egrep "\.ata" > hw.ata.atapi_dma: 1 Hmm, isn't that sysctl supposed to put the CDROM in DMA mode? -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< There is no distinctly native American criminal class except Congress. -- Mark Twain To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: strange ATA behavior with -STABLE
On 12 Jul 2002 at 23:38, Ian Dowse wrote: > In message <[EMAIL PROTECTED]>, Michiel Boland > writes : >Please correct me if I'm wrong but I don't think the splx > patch does >anything to help people with broken CD-ROM drives. > > Try the following. It fixes CD-ROM drives in VMWare for me, so > there is a good chance it may help with real CD-ROM drives too. > > Sorry, I meant to try to track this down ages ago as it sounded > (and was) really easy to find, but I rarely use CD-ROM drives in > VMWare so I never got around to it. It's just a simple race where > if the completion interrupt comes in between the splx() and the > tsleep(), the tsleep will sit in "atprq" forever. Moving the splx() to > after the tsleep ensures that this can't happen. > > Ian FWIW, a quick and dirty test shows that your patch works for me on this kernel: > uname -a FreeBSD hp.lonesome.org 4.6-STABLE FreeBSD 4.6-STABLE #1: Sun Jul 14 11:34:28 EDT 2002 [EMAIL PROTECTED]:/extra/src/sys/compile/HP i386 (that was 4-STABLE as of 02 July 2002, installed from a JP snapshot) with this CDROM: > dmesg |grep acd0 acd0: CDROM at ata1-slave PIO4 > and with the following sysctl settings: > sysctl -a | egrep "\.ata" hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.tags: 0 hw.ata.atapi_dma: 1 (The above sysctl settings didn't help before the patch. I haven't tried to find out if they matter after the patch.) Let's hope the patch can be included in 4.6.1-RELEASE. Thanks, Ian, for some much-needed relief! Eric To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: strange ATA behavior with -STABLE
* Michiel Boland ([EMAIL PROTECTED]): > Please correct me if I'm wrong but I don't think the splx patch does > anything to help people with broken CD-ROM drives. You are right. It fixes a coding mistake which panicked boxes using TQ. All other issues are still present. -- Thomas Seck This message was sent to a mailinglist I am subscribed to. Please send your replies to the list only and do *not* CC me. Thank you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: strange ATA behavior with -STABLE
Thus spake Bill Jones <[EMAIL PROTECTED]>: > There have been problems with 4.6-RELEASE with new installs -- CD- > ROM problems come to mind immediately. These are related to the > ata commits. I would like to see 4.6.1 remedy this situation before > our reputation as simple-to-install, always-works OS begins to falter. FreeBSD has a reputation of being easy to install? ... Well, I guess that's true if you're not using sysinstall. ``What do you mean `I have to choose /exit/ to proceed to the next step of the installation'?'' :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: strange ATA behavior with -STABLE
An interesting point. Perhaps my perspective has been coming across as arguing the wrong side. I agree that new installs are the most important. Changes which enable FreeBSD to work on what sort of systems people are purchasing at Dell, Best Buy, Circuit City and other retailers should matter greatly. Secondary, but still important, is making sure the changes break the least amount of legacy hardware as possible. I'd consider 5-6 years a good rule of thumb. If the hardware has gone unsupported for 5 years, then if it's not a huge installed base, losing support for it in BSD will have minimal impact. There have been problems with 4.6-RELEASE with new installs -- CD- ROM problems come to mind immediately. These are related to the ata commits. I would like to see 4.6.1 remedy this situation before our reputation as simple-to-install, always-works OS begins to falter. Admittedly, I can't argue as strongly for my case and the fact that I haven't upgraded. After all, I'm already running FreeBSD. :) I'll hop off the soapbox now. [EMAIL PROTECTED] wrote: But the new drivers probably support more first-time installs than the old one does. I know that it corrected multiple problems for me. I *am* running on a laptop, though. OTOH, that's sure getting to be more common rather than less over time. The *problem* is that it also broke some old hardware that previously worked. If you agree that the most important is what will work for most *new* installs, I believe that you are probably arguing the wrong side of the issue, or at the very least it's not clear what the right side of the issue would be. If you want to argue that the commit was a bad idea, then you'd have a much stronger case by arguing that FreeBSD shouldn't break what previously worked so that people aren't afraid to upgrade. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: strange ATA behavior with -STABLE
On Wed, 10 Jul 2002, Mike Tancsa wrote: > At 10:50 AM 10/07/2002 -0700, Bill Jones wrote: > >The obvious answer to me is "Most common platform someone installs > >FreeBSD on for the first time." > > ... Then its good that Soren committed his changes. The misplaced splx() > patch corrected the problem for some but not all which is in the .1 release. Please correct me if I'm wrong but I don't think the splx patch does anything to help people with broken CD-ROM drives. Cheers Michiel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: strange ATA behavior with -STABLE
On Tue, 09 Jul 2002 23:51:08 -0400 Mike Tancsa <[EMAIL PROTECTED]> wrote: > > Works correctly in what sense ? i.e. you can read and write to it under > some OS ? But not on this version of FreeBSD ? Yes, I tested the drive under FreeBSD 4.3-RELEASE and 4.5-STABLE (before new ATA drivers) and 4.6-stable (27th June). No problem. > > >And worked since 4.3-RELEASE with the same sysctl parameters > >ata-1 is dead > > Do you mean ad1 ? If so, If you take ad1 out and adjust ata-0's jumpers so > that its a master with no slave, does it now work ? I put ad2 to ad1, and on heavy load ATA channel 0 failed to. I removed my "strange disk" to and put, added another one. Same symptoms. > If not ad1, what do you mean by ata-1 is dead ? Or do you mean ata-1 the > controller is actually dead ? If so, get rid of the second drive. ATA channel 0 is dying to I think. It's not a big problem for, I'll get rid of ata drive for my box, I just wonder why FreeBSD get frozen on atapi failure :) > > Try sysctl -w hw.ata.ata_dma=0 or add hw.ata.ata_dma=0 into > /boot/loader.conf and reboot. No change. cheers clem ** UPDATE : of atacontrol cap of ad2 Sorry i mistyped :) [root@goofy|(510)| root]# atacontrol cap 1 0 ATA channel 1, Master, device ad2: ATA/ATAPI revision5 device model IC35L040AVER07-0 firmware revision ER4OA41A cylinders 16383 heads 16 sectors/track 63 lba supported 80418240 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued yes yes 31/1F SMART yes no microcode download no no security yes no power management yes yes advanced power management yes no 0/00 automatic acoustic management yes no 254/FE 128/80 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
