Request for testing: ata(4) MFC

[Jeremy Chadwick]

On Thu, Oct 16, 2008 at 12:17:00AM -0700, Jeremy Chadwick wrote:
> On Fri, Oct 10, 2008 at 04:58:55AM -0700, Jeremy Chadwick wrote:
> > On Sun, Oct 05, 2008 at 10:12:11PM -0700, Jeremy Chadwick wrote:
> > > On Mon, Oct 06, 2008 at 09:03:20AM +0400, Andrey V. Elsukov wrote:
> > > > Jeremy Chadwick wrote:
> > > >> Also, does your patch include any fixes (intentional or inadvertent) for
> > > >> Intel MatrixRAID?  This has been a sore spot for FreeBSD for quite
> > > >> some time, and I'm curious to know if that has been fixed.
> > > >
> > > > There is only one fix for Intel Matrix RAID:
> > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/121899
> > > 
> > > Ahh, yeah, I've seen that one as well.  I'll apply the patch and let you
> > > know if the behaviour documented in the PR happens.
> > 
> > I'm sorry I haven't gotten around to testing this -- my day (night) job
> > has kept me incredibly busy, and I've had hardly any time at home to
> > work on personal projects.  It sucks.
> > 
> > I'll try to make time for testing either today or tomorrow.
> 
> I finally got around to testing this patch tonight on my P4SCE box.

And I just ran into a problem with the new patch.  First time I've ever
seen this.  Machine has been rebooted a couple times this morning,
nothing out of the ordinary
where (machine has been rebooted a few times, had no problem).  First
time I've seen it:

atapci0: <Intel ICH5 SATA150 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
{snip non-relevant stuff}
Timecounters tick every 1.000 msec
unknown: timeout waiting to issue command
unknown: error issuing ATA_IDENTIFY command
unknown: timeout waiting to issue command
unknown: error issuing ATA_IDENTIFY command
acd0: CDROM <CD-224E/1.9A> at ata1-master UDMA33
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad0s1a

Manual root filesystem specification:
  <fstype>:<device>  Mount <device> using filesystem <fstype>
                       eg. ufs:da0s1a
  ?                  List valid disk boot devices
  <empty line>       Abort manual input
mountroot>

I rebooted the box at this point.  Sure enough, it came up fine:

atapci0: <Intel ICH5 SATA150 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
{snip non-relevant stuff}
Timecounters tick every 1.000 msec
ad0: 114473MB <Seagate ST3120026AS 3.05> at ata0-master SATA150
acd0: CDROM <CD-224E/1.9A> at ata1-master UDMA33
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad0s1a
Loading configuration files.
kernel dumps on /dev/ad0s1b
Entropy harvesting: interrupts ethernet point_to_point kickstart.
swapon: adding /dev/ad0s1b as swap device
Starting file system checks:
/dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS

And so on.

I'm not sure how to reproduce this bug, but it does appear to be a bug.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |