Date: Mon, 18 May 2009 01:57:38 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Bruce Simpson <bms@incunabulum.net> Cc: svn-src-stable-7@freebsd.org, svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Bruce Simpson <bms@FreeBSD.org> Subject: Re: svn commit: r192033 - stable/7/sys/dev/ata Message-ID: <4A109662.9060909@FreeBSD.org> In-Reply-To: <4A103429.8040906@incunabulum.net> References: <200905130255.n4D2tMQZ040010@svn.freebsd.org> <4A0CF9EA.6080403@FreeBSD.org> <4A0D7B50.4090602@FreeBSD.org> <4A103429.8040906@incunabulum.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Simpson wrote: > Alexander Motin wrote: >> Bruce Simpson wrote: >>> Could this commit have broken boot on my amd64 system with an ULi >>> SATA controller? >> >> This commit could change driver used for controller and so expose some >> other bug in ALI driver. As I can see, there is present >> vendor-specific driver for this chip, but without pciconf output I >> can't say if AHCI driver is also able to attach it. > > atapci1@pci0:0:31:1: class=0x010400 card=0x81561043 chip=0x528710b9 > rev=0x02 hdr=0x00 > vendor = 'Acer Labs Incorporated (ALi/ULi)' > device = '52871849 ALI SATA controller' > class = mass storage > subclass = RAID This change is not anyhow related to your system. Looks like the real reason found by jhb@ on stable@. Probably something become more strict in system resource management last time and this driver violates now. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A109662.9060909>