Date: Wed, 28 Apr 1999 13:37:15 +0200 From: Thomas Seidmann <tseidmann@SIMULTAN.CH> To: current@FreeBSD.ORG Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com> Subject: New ATA drivers problem? (Was: New kernels won't boot) Message-ID: <3726F2EB.2B4A6AA5@simultan.ch> References: <199904280051.IAA09151@ariadne.tensor.pgs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, In the great new ATA device driver framework (thanks Soren) there seems to be a problem reported before by Stephen: Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > On my machine, a kernel newer than one built on the 22nd will not complete > booting, panicing about not being able to mount root. Another machine with a > very similar config is fine. The main difference is that the faulty machine > has its FreeBSD partition in an odd spot on the disk. Below is the dmesg > output, the fdisk output and the config file. [stuff deleted] I have three hosts with -current, all with the new ATA in function. Booting the same kernel produces different results on all of them wrt root file system mounting: - one reports 'changing root device to wd0s3a' - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and continues flawlessly - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and panics with 'cannot mount root file system (2), err 22' All motherboards are equipped with the PIIX4 IDE controller. If I need to supply the dmesg output and/or configuration, please let me know. All three hosts have FreeBSD on the first disk (on different disk locations, though). Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3726F2EB.2B4A6AA5>