Date: Wed, 28 Jul 2010 15:06:19 +0300 From: Alexander Motin <mav@FreeBSD.org> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no>, FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: k3b causing system freeze/panic Message-ID: <4C501D3B.1070509@FreeBSD.org> In-Reply-To: <mailpost.1280317392.7848726.74801.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> References: <867hkfncod.fsf@ds4.des.no> <mailpost.1280317392.7848726.74801.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > Dag-Erling Smørgrav <des@des.no> writes: >> Andriy Gapon <avg@icyb.net.ua> writes: >>> Michael Butler <imb@protected-networks.net> writes: >>>> I have a custom kernel for my laptop which uses ATA_CAM rather than >>>> the now aging ATA driver .. >>> You do realize that ATA_CAM just (well, mostly) introduces a wrapper >>> around the "now aging ATA driver" ? >> Only for legacy drives, but since Micahel's panic message contains >> "current process = 12 (irq15: ata1)", his BIOS is probably in legacy >> mode. > > Sorry, I misparsed ATA_CAM as ahci. Why on earth would anyone want to > use ATA_CAM these days? Because there is still a lot of legacy controllers, while ata(4)'s bus management code is buggy in some aspects, that are difficult to fix without complete rewrite. ATA_CAM wrapper replaces all that problematic code and works better now. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C501D3B.1070509>