Date: Fri, 8 Jun 2012 22:11:48 -0700 From: Kevin Oberman <kob6558@gmail.com> To: Marius Strobl <marius@alchemy.franken.de> Cc: Ian Lepore <freebsd@damnhippie.dyndns.org>, "freebsd-stable@freebsd.org Stable" <freebsd-stable@freebsd.org> Subject: Re: Boot hangs on v9 system at CD device probe Message-ID: <CAN6yY1tCU8=bmdbu=huwBsv-nAAvT891B0aTiR5TK4wntWRSyw@mail.gmail.com> In-Reply-To: <CAN6yY1twcXVMm6o9HVef_PJKFj_%2BPbwhYkj3=_FmQidq89gJZQ@mail.gmail.com> References: <CAN6yY1vV-_Dt=2SRy2A-ppPQBHmz2FfjU-JzsNNFAB_xBV%2BoHA@mail.gmail.com> <1338419624.36051.94.camel@revolution.hippie.lan> <20120531110215.GA78200@alchemy.franken.de> <CAN6yY1twcXVMm6o9HVef_PJKFj_%2BPbwhYkj3=_FmQidq89gJZQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 31, 2012 at 9:10 AM, Kevin Oberman <kob6558@gmail.com> wrote: > On Thu, May 31, 2012 at 4:02 AM, Marius Strobl > <marius@alchemy.franken.de> wrote: >> On Wed, May 30, 2012 at 05:13:44PM -0600, Ian Lepore wrote: >>> On Wed, 2012-05-30 at 14:54 -0700, Kevin Oberman wrote: >>> > I sent a note about this a couple of weeks ago, but have not heard >>> > anything. I'm really getting a bit desperate. >>> > >>> > I have a system that I am trying to upgrade from 8.2 to 9.0. I have >>> > built it and installed the kernel, but it fails to boot. The boot >>> > freezes after probing for my hard drives during the probe of the >>> > CDROM. It just sits there, seemingly forever, though I have never >>> > waited longer then a few minutes. >>> > >>> > The system is a SuperMicro C25BX mother board. The DVD is PATA, >>> > reported on boot of 8-Stable as: >>> > acd0: DVDR <ATAPI DVD A DH20A4P/9P59> at ata2-master UDMA66 >>> > >>> > If I unplug the CDROM, it boots fine, but I really need the device on >>> > the system, so I really can't leave it unplugged. Also, after the 9 >>> > kernel is installed, my Mk file have been updated so that I can't >>> > build some ports if I boot the 8.2 kernel. Does anyone remember this >>> > being reported by others? It was most likely on current, as it was >>> > probably prior to the release of 9. I googled around, but could not >>> > find it. >>> > >>> > I'd really appreciate it if anyone can point me toward a solution. >>> > >>> > Thanks, >>> >>> When faced with a mystery like this I sometimes go into the mode of >>> "poke it with a stick and see if it twitches." =A0If you can get it to >>> twitch at all, maybe that's a starting point. =A0In this case, I guess = I >>> might start with seeing if setting hw.ata.atapi_dma=3D0 in the loader >>> makes any difference. >>> >> >> Note that hw.ata.atapi_dma isn't honored by 9.0 with options ATA_CAM >> (default in GENERIC). Support for that loader tuneable was only >> resurrected rather recently (but is available in stable/9). The >> equivalent for 9.0 would be setting hint.ata.X.mode to PIO4 where >> X is the number of the ata(4) device attached for the channel the >> CDROM is connected to. >> ATA_CAM is indeed known to break ATAPI DMA for some ATA controllers >> though. What's the `pciconf -lv` output for this one? > > Good point. I had forgotten about the hw.ata.atapi_dma removal and was > not even awarethat it had been recently re-enabled. > My controller is: > atapci0@pci0:17:4:0: =A0 =A0class=3D0x010185 card=3D0x82131283 chip=3D0x8= 2131283 > rev=3D0x00 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Integrated Technology Express (ITE) Inc' > =A0 =A0device =A0 =A0 =3D 'IDE Controller (IT8213F)' > =A0 =A0class =A0 =A0 =A0=3D mass storage > =A0 =A0subclass =A0 =3D ATA > > It is used ONLY for the CD/DVD as all other disks use the 3ware RAID cont= roller. > > Unfortunately, the system is not located where I am, so I can't really > try anything until I get over there. Maybe later today I can run into > that office and try some of the suggestions. I can certainly build a > kernel without ATA_CAM. I just did the obvious as suggested and built a kernel without ATA_CAM and with atapicam. It boots fine and I have my CD/DVD working on 9.0. Clearly, there is some issue with ATAPI drives with ATA_CAM as others have seen the same thing. It is entirely possible that a serial connected drives don't have this issue. It does look like there is some locking issue between CAM and GEOM under some circumstances. I worry that 10 will lose support for other than ATA_CAM and that the work-around will no longer be available. Of course, if ahci fixes it, the problem will go away on systems that support it. Next time I get to the system I will try putting ATA_CAM back and adding ahci and report on the results. Thanks for the suggestions! --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tCU8=bmdbu=huwBsv-nAAvT891B0aTiR5TK4wntWRSyw>