Re: Decision time.... should NATA become the default for this release?
YONETANI Tomokazu <qhwt+dfly <at> les.ath.cx>
2007-06-01 09:08:57 GMT
On Thu, May 31, 2007 at 05:35:49PM -0700, Matthew Dillon wrote:
> We need to make a decision on the next release as to whether NATA
> should become the default. I would really like to make it the default,
> but to do so we need some assurance that it won't break things that
> currently work.
> So I'm asking all developers running HEAD who have not already started
> using the NATA driver to start using it instead of the ATA driver.
> Lets give it a good whack!
I gave NATA a try on my notebook PC, and now it boots into single-user mode!
This is a progress, as it used to just get stuck somewhere in init(8) (BTW
I tried to add debug print's in init, but somehow it didn't work), and
all I could do then was to drop in to DDB or reboot.
However, core dumping of random processes still remains, so it's still not
usable in multi-user mode. Sometimes, it panics on umount, after some
read-only disk activities:
# mount -r /home
# find /home >/dev/null
# umount /home
panic: unmount: dangling vnode
Another weird thing with NATA is that I'm seeing odd interrupt counts
from `vmstat -i'; with old-ATA, it looks like this:
# vmstat -iv
interrupt total rate
irq0: clk 402493 277
irq1: atkbd0 4 0
irq9: acpi0 54 0