Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Stanislav Brabec]

Albert Lee wrote:
> Tejun Heo wrote:

> > Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
> > don't think the low level driver is causing the difference.  They both
> > use the standard libata HSM implementation.  Any ideas?  Stanislav, can
> > you try to connect that zip drive to another IDE controller?

> Maybe it's also worth a try to replace the medium, cable or even the
> drive itself to rule out the possibility of hardware problem.

I'll try it. I cannot replace the drive, I don't have any spare one, but
my colleague has. He will try it on his machine. So let's wait for
result.

Looking at the syslog in Novell bug 232086 in detail, following line may
indicate hardware failure:
usb 5-1: string descriptor 0 read error: -22

My drive is a slave on bus, where master is a modern Seagate ST3160812A.

On my system I see two regressions:
- One between year 2002 kernels and SuSE Linux 10.0:
  Delay with "packet command initiated yet DRQ isn't asserted" before
  first read access, then the read will succeed.
  I did not yet reproduce this regression just now on my hardware.
- Second between SuSE 10.1 and 10.2:
  Delay with "packet command initiated yet DRQ isn't asserted" before
  any attempt to access, then it will fail.
  This regression is reproducible just now on my hardware, but still may
  be caused by hardware problems raised by a slightly different
  initialization order.

Tejun Heo wrote:
> [libata]
> And, as the device requires custom high level driver, libata fails
> miserably.  Would it be worth to try support these devices?  Or are
> they just too outdated to put the effort in?

As far as I remember, it was working without any special driver with
ide-scsi.

-- 
Best Regards,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec@suse.cz
Lihovarska 1060/12                            tel: +420 284 028 966
190 00 Praha 9                                fax: +420 284 028 951
Czech Republic                                http://www.suse.cz/

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

Stanislav Brabec wrote:
> Looking at the syslog in Novell bug 232086 in detail, following line may
> indicate hardware failure:
> usb 5-1: string descriptor 0 read error: -22

I don't think usb 5-1 is related to ide-floppy problem.

> My drive is a slave on bus, where master is a modern Seagate ST3160812A.
> 
> On my system I see two regressions:
> - One between year 2002 kernels and SuSE Linux 10.0:
>   Delay with "packet command initiated yet DRQ isn't asserted" before
>   first read access, then the read will succeed.
>   I did not yet reproduce this regression just now on my hardware.
> - Second between SuSE 10.1 and 10.2:
>   Delay with "packet command initiated yet DRQ isn't asserted" before
>   any attempt to access, then it will fail.
>   This regression is reproducible just now on my hardware, but still may
>   be caused by hardware problems raised by a slightly different
>   initialization order.

I see.

> Tejun Heo wrote:
>> [libata]
>> And, as the device requires custom high level driver, libata fails
>> miserably.  Would it be worth to try support these devices?  Or are
>> they just too outdated to put the effort in?
> 
> As far as I remember, it was working without any special driver with
> ide-scsi.

If that's the case, libata should work too as long as the HSM problem is
fixed.

-- 
tejun

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Mark Lord]

Tejun wrote:
> If that's the case, libata should work too as long as the HSM problem is
> fixed.

Really?  I didn't notice when libata gained ATAPI-disk support.

Are you *sure* about that??

Cool.

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Bartlomiej Zolnierkiewicz]

On Wednesday 14 March 2007, Stanislav Brabec wrote:
> Albert Lee wrote:
> > Tejun Heo wrote:
> 
> > > Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
> > > don't think the low level driver is causing the difference.  They both
> > > use the standard libata HSM implementation.  Any ideas?  Stanislav, can
> > > you try to connect that zip drive to another IDE controller?
> 
> > Maybe it's also worth a try to replace the medium, cable or even the
> > drive itself to rule out the possibility of hardware problem.
> 
> I'll try it. I cannot replace the drive, I don't have any spare one, but
> my colleague has. He will try it on his machine. So let's wait for
> result.
> 
> Looking at the syslog in Novell bug 232086 in detail, following line may
> indicate hardware failure:
> usb 5-1: string descriptor 0 read error: -22
> 
> My drive is a slave on bus, where master is a modern Seagate ST3160812A.
> 
> On my system I see two regressions:
> - One between year 2002 kernels and SuSE Linux 10.0:
>   Delay with "packet command initiated yet DRQ isn't asserted" before
>   first read access, then the read will succeed.
>   I did not yet reproduce this regression just now on my hardware.
> - Second between SuSE 10.1 and 10.2:
>   Delay with "packet command initiated yet DRQ isn't asserted" before
>   any attempt to access, then it will fail.
>   This regression is reproducible just now on my hardware, but still may
>   be caused by hardware problems raised by a slightly different
>   initialization order.

It is reproduceable, SuSE 10.1 kernel is "good" and SuSE 10.2 is "bad".
So even if this is caused by some hardware problems or different
initialization order git-bisect on 2.6.16-2.6.20 should tell us what
change caused the problem.

PS Tejun, I praise efforts to make ATA floppy drives work with libata
but this is IMO a _future_ work (won't help et all for existing
systems/distributions) and we need to have ide-floppy fixed _now_.

Bart

> Tejun Heo wrote:
> > [libata]
> > And, as the device requires custom high level driver, libata fails
> > miserably.  Would it be worth to try support these devices?  Or are
> > they just too outdated to put the effort in?
> 
> As far as I remember, it was working without any special driver with
> ide-scsi.
> 
> -- 
> Best Regards,
> 
> Stanislav Brabec
> software developer
> ---------------------------------------------------------------------
> SUSE LINUX, s. r. o.                          e-mail: sbrabec@suse.cz
> Lihovarska 1060/12                            tel: +420 284 028 966
> 190 00 Praha 9                                fax: +420 284 028 951
> Czech Republic                                http://www.suse.cz/

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

Bartlomiej Zolnierkiewicz wrote:
>> My drive is a slave on bus, where master is a modern Seagate ST3160812A.
>>
>> On my system I see two regressions:
>> - One between year 2002 kernels and SuSE Linux 10.0:
>>   Delay with "packet command initiated yet DRQ isn't asserted" before
>>   first read access, then the read will succeed.
>>   I did not yet reproduce this regression just now on my hardware.
>> - Second between SuSE 10.1 and 10.2:
>>   Delay with "packet command initiated yet DRQ isn't asserted" before
>>   any attempt to access, then it will fail.
>>   This regression is reproducible just now on my hardware, but still may
>>   be caused by hardware problems raised by a slightly different
>>   initialization order.
> 
> It is reproduceable, SuSE 10.1 kernel is "good" and SuSE 10.2 is "bad".
> So even if this is caused by some hardware problems or different
> initialization order git-bisect on 2.6.16-2.6.20 should tell us what
> change caused the problem.
> 
> PS Tejun, I praise efforts to make ATA floppy drives work with libata
> but this is IMO a _future_ work (won't help et all for existing
> systems/distributions) and we need to have ide-floppy fixed _now_.

Yeap, agreed but I think getting more info on the libata HSM violation
can help diagnosing ide problem too.  Anyways, Stanislav, can you bisect
as Bartlomiej requested?

-- 
tejun

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

Mark Lord wrote:
> Tejun wrote:
>> If that's the case, libata should work too as long as the HSM problem is
>> fixed.
> 
> Really?  I didn't notice when libata gained ATAPI-disk support.
> 
> Are you *sure* about that??

Not sure sure but almost sure.  :-)  What ide-scsi does is borrowing
SCSI mid and high level drivers while using ide as SCSI low level
driver.  To SCSI, libata and ide-scsi aren't very different except that
libata also exports SBC device to it.  So, if SCSI could handle ATAPI
disk via ide-scsi, I don't think there is any reason it can't with libata.

Thanks.

-- 
tejun

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Jeff Garzik]

Mark Lord wrote:
> Tejun wrote:
>> If that's the case, libata should work too as long as the HSM problem is
>> fixed.
> 
> Really?  I didn't notice when libata gained ATAPI-disk support.

ATAPI just passes through to SCSI.  There is no limitation on the 
peripheral device types supported, except in the SCSI midlayer itself.

Some rare ATAPI devices are even pure SCSI bridges, allowing you to hook 
up any SCSI-2 device to the bridge, and in turn, to any ATA/ATAPI 
controller.

	Jeff

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Mark Lord]

Tejun Heo wrote:
> 
> Yeap, agreed but I think getting more info on the libata HSM violation
> can help diagnosing ide problem too.  Anyways, Stanislav, can you bisect
> as Bartlomiej requested?
> 

Tejun, do you have a Zip100 (ATAPI) drive to play with there?

Cheers

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Stanislav Brabec]

Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 14 March 2007, Stanislav Brabec wrote:
> > Albert Lee wrote:
> > > Tejun Heo wrote:
> > 
> > > > Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
> > > > don't think the low level driver is causing the difference.  They both
> > > > use the standard libata HSM implementation.  Any ideas?  Stanislav, can
> > > > you try to connect that zip drive to another IDE controller?
> > 
> > > Maybe it's also worth a try to replace the medium, cable or even the
> > > drive itself to rule out the possibility of hardware problem.
> > 
> > I'll try it. I cannot replace the drive, I don't have any spare one, but
> > my colleague has. He will try it on his machine. So let's wait for
> > result.
> > 
> > Looking at the syslog in Novell bug 232086 in detail, following line may
> > indicate hardware failure:
> > usb 5-1: string descriptor 0 read error: -22
> > 
> > My drive is a slave on bus, where master is a modern Seagate ST3160812A.
> > 
> > On my system I see two regressions:

> 
> It is reproduceable, SuSE 10.1 kernel is "good" and SuSE 10.2 is "bad".
> So even if this is caused by some hardware problems or different
> initialization order git-bisect on 2.6.16-2.6.20 should tell us what
> change caused the problem.

After more kernels testing I am inclined to suspect broken hardware.

2.4.20 (SuSE 8.1) and newer kernels  exhibits this "DRQ isn't asserted"
error. The latest kernel working without any problem is five years old
2.4.18 (SuSE 8.0).

In some older systems the delay was "hidden" somewhere in the boot
process, now userspace processes repeatedly scan all media, which makes
delay permanent.

-- 
Best Regards,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec@suse.cz
Lihovarska 1060/12                            tel: +420 284 028 966
190 00 Praha 9                                fax: +420 284 028 951
Czech Republic                                http://www.suse.cz/

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

Mark Lord wrote:
> Tejun Heo wrote:
>>
>> Yeap, agreed but I think getting more info on the libata HSM violation
>> can help diagnosing ide problem too.  Anyways, Stanislav, can you bisect
>> as Bartlomiej requested?
>>
> 
> Tejun, do you have a Zip100 (ATAPI) drive to play with there?

Nope.  Do you happen to have a spare one?

-- 
tejun

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Albert Lee]

Stanislav Brabec wrote:
> Bartlomiej Zolnierkiewicz wrote:
> 
>>On Wednesday 14 March 2007, Stanislav Brabec wrote:
>>
>>>Albert Lee wrote:
>>>
>>>>Tejun Heo wrote:
>>>
>>>>>Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
>>>>>don't think the low level driver is causing the difference.  They both
>>>>>use the standard libata HSM implementation.  Any ideas?  Stanislav, can
>>>>>you try to connect that zip drive to another IDE controller?
>>>
>>>>Maybe it's also worth a try to replace the medium, cable or even the
>>>>drive itself to rule out the possibility of hardware problem.
>>>
>>>I'll try it. I cannot replace the drive, I don't have any spare one, but
>>>my colleague has. He will try it on his machine. So let's wait for
>>>result.
>>>
>>>Looking at the syslog in Novell bug 232086 in detail, following line may
>>>indicate hardware failure:
>>>usb 5-1: string descriptor 0 read error: -22
>>>
>>>My drive is a slave on bus, where master is a modern Seagate ST3160812A.
>>>
>>>On my system I see two regressions:
> 
> 
>>It is reproduceable, SuSE 10.1 kernel is "good" and SuSE 10.2 is "bad".
>>So even if this is caused by some hardware problems or different
>>initialization order git-bisect on 2.6.16-2.6.20 should tell us what
>>change caused the problem.
> 
> 
> After more kernels testing I am inclined to suspect broken hardware.
> 
> 2.4.20 (SuSE 8.1) and newer kernels  exhibits this "DRQ isn't asserted"
> error. The latest kernel working without any problem is five years old
> 2.4.18 (SuSE 8.0).
> 
> In some older systems the delay was "hidden" somewhere in the boot
> process, now userspace processes repeatedly scan all media, which makes
> delay permanent.
> 

Hi Stanislav,

Could you apply the attached HSM debug patch and post the dmesg, thanks.
(Hopefully we can get some clue from the HSM trace.)

--
albert

--- linux-2.6.20.3/drivers/ata/libata-core.c	2007-03-15 12:13:12.000000000 +0800
+++ linux-2.6.20.3-mod/drivers/ata/libata-core.c	2007-03-15 12:13:55.000000000 +0800
@@ -4371,8 +4371,9 @@ int ata_hsm_move(struct ata_port *ap, st
 	WARN_ON(in_wq != ata_hsm_ok_in_wq(ap, qc));
 
 fsm_start:
-	DPRINTK("ata%u: protocol %d task_state %d (dev_stat 0x%X)\n",
-		ap->id, qc->tf.protocol, ap->hsm_task_state, status);
+	if (is_atapi_taskfile(&qc->tf))
+		printk(KERN_ERR "ata%u: protocol %d task_state %d (dev_stat 0x%X)\n",
+		       ap->id, qc->tf.protocol, ap->hsm_task_state, status);
 
 	switch (ap->hsm_task_state) {
 	case HSM_ST_FIRST:
@@ -5091,8 +5092,9 @@ inline unsigned int ata_host_intr (struc
 	struct ata_eh_info *ehi = &ap->eh_info;
 	u8 status, host_stat = 0;
 
-	VPRINTK("ata%u: protocol %d task_state %d\n",
-		ap->id, qc->tf.protocol, ap->hsm_task_state);
+	if (is_atapi_taskfile(&qc->tf))
+		printk(KERN_ERR "ata%u: protocol %d task_state %d\n",
+		       ap->id, qc->tf.protocol, ap->hsm_task_state);
 
 	/* Check whether we are expecting interrupt in this state */
 	switch (ap->hsm_task_state) {

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Bartlomiej Zolnierkiewicz]

On Wednesday 14 March 2007, Stanislav Brabec wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Wednesday 14 March 2007, Stanislav Brabec wrote:
> > > Albert Lee wrote:
> > > > Tejun Heo wrote:
> > > 
> > > > > Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
> > > > > don't think the low level driver is causing the difference.  They both
> > > > > use the standard libata HSM implementation.  Any ideas?  Stanislav, can
> > > > > you try to connect that zip drive to another IDE controller?
> > > 
> > > > Maybe it's also worth a try to replace the medium, cable or even the
> > > > drive itself to rule out the possibility of hardware problem.
> > > 
> > > I'll try it. I cannot replace the drive, I don't have any spare one, but
> > > my colleague has. He will try it on his machine. So let's wait for
> > > result.
> > > 
> > > Looking at the syslog in Novell bug 232086 in detail, following line may
> > > indicate hardware failure:
> > > usb 5-1: string descriptor 0 read error: -22
> > > 
> > > My drive is a slave on bus, where master is a modern Seagate ST3160812A.
> > > 
> > > On my system I see two regressions:
> 
> > 
> > It is reproduceable, SuSE 10.1 kernel is "good" and SuSE 10.2 is "bad".
> > So even if this is caused by some hardware problems or different
> > initialization order git-bisect on 2.6.16-2.6.20 should tell us what
> > change caused the problem.
> 
> After more kernels testing I am inclined to suspect broken hardware.
> 
> 2.4.20 (SuSE 8.1) and newer kernels  exhibits this "DRQ isn't asserted"
> error. The latest kernel working without any problem is five years old
> 2.4.18 (SuSE 8.0).
> 
> In some older systems the delay was "hidden" somewhere in the boot
> process, now userspace processes repeatedly scan all media, which makes
> delay permanent.

I'm lost, weren't you saying that there are two problems actually:

* "DRQ isn't asserted" one which has always been there (but ide-floppy works)

* the 2.6.16->2.6.20 (SuSE 10.1->10.2) regression (ide-floppy doesn't work)

?

Bart

IOMEGA IDE ZIP (ATAPI) drive

[Mark Lord]

Tejun Heo wrote:
> Mark Lord wrote:
>> Really?  I didn't notice when libata gained ATAPI-disk support.
>>
>> Are you *sure* about that??
> 
> Not sure sure but almost sure.  :-)  What ide-scsi does is borrowing
> SCSI mid and high level drivers while using ide as SCSI low level
> driver.  To SCSI, libata and ide-scsi aren't very different except that
> libata also exports SBC device to it.  So, if SCSI could handle ATAPI
> disk via ide-scsi, I don't think there is any reason it can't with libata.

Okay, I dusted off one of my old (actually, I believe *the oldest*)
Zip100 drives in the collection, and tried it out here with both
2.6.20 and 2.6.21-rc3-git9.   It works mostly fine with each.

A couple of minor issues, though.

(1) When ejecting a disk, either with the "eject /dev/sdc" command
or using the front-panel soft-eject button on the drive,
I get the following in syslog from libata:

sdc: Spinning up disk...<3>ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
         res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
ata4: soft resetting port
ATA: abnormal status 0x7F on port 0x00010177
ATA: abnormal status 0x7F on port 0x00010177
ata4.00: configured for PIO2
ata4: EH complete


(2) The above log says PIO2, but the IDENTIFY data for this drive,
which I had to patch the kernel to get (ATAPI ATA_16 support),
indicates max PIO0 for this unit.  I suppose maybe the chipset
doesn't go that low, but no big deal since IORDY handshakes it anyway.

Chipset is VIA, PCI ID 1106:0571, Rev.6.


Tejun, if you want one for your testbed, then email me shipping
info (again) and I'll send you this exact unit, with one disc.

Here's the IDENTIFY data, for anyone else here who collects antiques:

/dev/sdc:
80a0 0000 0000 0000 0000 0000 0000 0000
0000 0000 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 0000 0000 0000 3233
2e44 2020 2020 494f 4d45 4741 2020 5a49
5020 3130 3020 2020 2020 2020 4154 4150
4920 2020 2020 2020 2020 2020 2020 0000
0000 0e00 0000 0000 0000 0002 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 01f4 01f4 0000 0000 0000
0000 0006 0009 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0101
2863 2920 436f 7079 7269 6768 7420 494f
4d45 4741 2031 3939 3720 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000

Cheers

Re: IOMEGA IDE ZIP (ATAPI) drive

[Albert Lee]

Mark Lord wrote:
> Tejun Heo wrote:
> 
>> Mark Lord wrote:
>>
>>> Really?  I didn't notice when libata gained ATAPI-disk support.
>>>
>>> Are you *sure* about that??
>>
>>
>> Not sure sure but almost sure.  :-)  What ide-scsi does is borrowing
>> SCSI mid and high level drivers while using ide as SCSI low level
>> driver.  To SCSI, libata and ide-scsi aren't very different except that
>> libata also exports SBC device to it.  So, if SCSI could handle ATAPI
>> disk via ide-scsi, I don't think there is any reason it can't with
>> libata.
> 
> 
> Okay, I dusted off one of my old (actually, I believe *the oldest*)
> Zip100 drives in the collection, and tried it out here with both
> 2.6.20 and 2.6.21-rc3-git9.   It works mostly fine with each.
> 
> A couple of minor issues, though.
> 
> (1) When ejecting a disk, either with the "eject /dev/sdc" command
> or using the front-panel soft-eject button on the drive,
> I get the following in syslog from libata:
> 
> sdc: Spinning up disk...<3>ata4.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x2
>         res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
> ata4: soft resetting port
> ATA: abnormal status 0x7F on port 0x00010177
> ATA: abnormal status 0x7F on port 0x00010177
> ata4.00: configured for PIO2
> ata4: EH complete

The device status of 0x00 looks strange.
Could you please apply the attached debugging patch for 
clue about what caused the HSM violation, thanks.

> 
> 
> (2) The above log says PIO2, but the IDENTIFY data for this drive,
> which I had to patch the kernel to get (ATAPI ATA_16 support),
> indicates max PIO0 for this unit.  I suppose maybe the chipset
> doesn't go that low, but no big deal since IORDY handshakes it anyway.
> 

I saw this strange behavior, too.
The Promise BIOS identified my zip 100 drive as "PIO 0" during boot,
but libata identified it as "PIO2":

ata4.00: ATAPI, max PIO2, CDB intr
ata4.00: configured for PIO2

--
albert

--- linux-2.6.20.3/drivers/ata/libata-core.c	2007-03-15 12:13:12.000000000 +0800
+++ linux-2.6.20.3-mod/drivers/ata/libata-core.c	2007-03-15 12:13:55.000000000 +0800
@@ -4371,8 +4371,9 @@ int ata_hsm_move(struct ata_port *ap, st
 	WARN_ON(in_wq != ata_hsm_ok_in_wq(ap, qc));
 
 fsm_start:
-	DPRINTK("ata%u: protocol %d task_state %d (dev_stat 0x%X)\n",
-		ap->id, qc->tf.protocol, ap->hsm_task_state, status);
+	if (is_atapi_taskfile(&qc->tf))
+		printk(KERN_ERR "ata%u: protocol %d task_state %d (dev_stat 0x%X)\n",
+		       ap->id, qc->tf.protocol, ap->hsm_task_state, status);
 
 	switch (ap->hsm_task_state) {
 	case HSM_ST_FIRST:
@@ -5091,8 +5092,9 @@ inline unsigned int ata_host_intr (struc
 	struct ata_eh_info *ehi = &ap->eh_info;
 	u8 status, host_stat = 0;
 
-	VPRINTK("ata%u: protocol %d task_state %d\n",
-		ap->id, qc->tf.protocol, ap->hsm_task_state);
+	if (is_atapi_taskfile(&qc->tf))
+		printk(KERN_ERR "ata%u: protocol %d task_state %d\n",
+		       ap->id, qc->tf.protocol, ap->hsm_task_state);
 
 	/* Check whether we are expecting interrupt in this state */
 	switch (ap->hsm_task_state) {

Re: IOMEGA IDE ZIP (ATAPI) drive

[Mark Lord]

Albert Lee wrote:
> Mark Lord wrote:
>..
>> (1) When ejecting a disk, either with the "eject /dev/sdc" command
>> or using the front-panel soft-eject button on the drive,
>> I get the following in syslog from libata:
>>
>> sdc: Spinning up disk...<3>ata4.00: exception Emask 0x0 SAct 0x0 SErr
>> 0x0 action 0x2
>>         res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
>> ata4: soft resetting port
>> ATA: abnormal status 0x7F on port 0x00010177
>> ATA: abnormal status 0x7F on port 0x00010177
>> ata4.00: configured for PIO2
>> ata4: EH complete
> 
> The device status of 0x00 looks strange.

Not to me.  The device likely generated an unsolicitied interrupt,
and status==0x00 is correct for a few seconds here:  the drive is
not busy with a command, not in an error state, and not ready
for a new command since it is busy ejecting a disc.

> Could you please apply the attached debugging patch for 
> clue about what caused the HSM violation, thanks.

I'll unpack the drive and hook it up again.

Cheers

Re: IOMEGA IDE ZIP (ATAPI) drive

[Mark Lord]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

Albert Lee wrote:
> Could you please apply the attached debugging patch for 
> clue about what caused the HSM violation, thanks.

I had to edit the patch to get it to apply on 2.6.21-rc3-git9,
but here (attached) is the output from syslog.

zip_insert.txt :: response to inserting a disc into the drive.
zip_button.txt :: response to pressing the eject button.
zip_eject.txt  :: response to using "eject /dev/sdc".

Enjoy!


[-- Attachment #2: zip_button.txt --]
[-- Type: text/plain, Size: 421 bytes --]

11:08:57: sdc: Spinning up disk...<3>ata port 1: protocol 6 task_state 4
11:08:57:          res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
11:08:57: ata4: soft resetting port
11:08:57: ATA: abnormal status 0x7F on port 0x00010177
11:08:57: ATA: abnormal status 0x7F on port 0x00010177
11:08:58: ata4.00: configured for PIO2
11:08:58: ata4: EH complete
11:08:58: .<3>ata port 1: protocol 6 task_state 4

[-- Attachment #3: zip_eject.txt --]
[-- Type: text/plain, Size: 494 bytes --]

11:09:55: sdc: Spinning up disk...<3>ata port 1: protocol 6 task_state 4
11:09:55:          res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
11:09:55: ata4: soft resetting port
11:09:55: ATA: abnormal status 0x7F on port 0x00010177
11:09:55: ATA: abnormal status 0x7F on port 0x00010177
11:09:56: ata4.00: configured for PIO2
11:09:56: ata4: EH complete
11:09:56: sdc: Spinning up disk...<3>ata port 1: protocol 6 task_state 4
11:09:57: .<3>ata port 1: protocol 6 task_state 4

[-- Attachment #4: zip_insert.txt --]
[-- Type: text/plain, Size: 1454 bytes --]

11:07:19: sdc: Spinning up disk...<3>ata port 1: protocol 6 task_state 4
11:07:19:          res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
11:07:19: ata4: soft resetting port
11:07:19: ATA: abnormal status 0x7F on port 0x00010177
11:07:19: ATA: abnormal status 0x7F on port 0x00010177
11:07:19: ata4.00: configured for PIO2
11:07:19: ata4: EH complete
11:07:20: sdc: Spinning up disk...<3>ata port 1: protocol 6 task_state 4
11:07:20:          res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
11:07:20: ata4: soft resetting port
11:07:20: ATA: abnormal status 0x7F on port 0x00010177
11:07:20: ATA: abnormal status 0x7F on port 0x00010177
11:07:21: .<6>ata4.00: configured for PIO2
11:07:21: ata4: EH complete
11:07:21: ready
11:07:21: SCSI device sdc: 196608 512-byte hdwr sectors (101 MB)
11:07:21: sdc: Write Protect is off
11:07:21: sdc: cache data unavailable
11:07:21: SCSI device sdc: 196608 512-byte hdwr sectors (101 MB)
11:07:21: sdc: Write Protect is off
11:07:21: sdc: cache data unavailable
11:07:21:  sdc:<3>ata port 1: protocol 5 task_state 4
11:07:21:  sdc4
11:07:22: .<3>ata port 1: protocol 6 task_state 4
11:07:22: ready
11:07:22: SCSI device sdc: 196608 512-byte hdwr sectors (101 MB)
11:07:22: sdc: Write Protect is off
11:07:22: sdc: cache data unavailable
11:07:22: SCSI device sdc: 196608 512-byte hdwr sectors (101 MB)
11:07:22: sdc: Write Protect is off
11:07:22: sdc: cache data unavailable

Re: IOMEGA IDE ZIP (ATAPI) drive

[Albert Lee]

Mark Lord wrote:
> Albert Lee wrote:
> 
>> Could you please apply the attached debugging patch for clue about
>> what caused the HSM violation, thanks.
> 
> 
> I had to edit the patch to get it to apply on 2.6.21-rc3-git9,
> but here (attached) is the output from syslog.
> 
> zip_insert.txt :: response to inserting a disc into the drive.
> zip_button.txt :: response to pressing the eject button.
> zip_eject.txt  :: response to using "eject /dev/sdc".
> 
> Enjoy!
> 
> 
> ------------------------------------------------------------------------
> 
> 11:08:57: sdc: Spinning up disk...<3>ata port 1: protocol 6 task_state 4
> 11:08:57:          res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
> 11:08:57: ata4: soft resetting port
> 11:08:57: ATA: abnormal status 0x7F on port 0x00010177
> 11:08:57: ATA: abnormal status 0x7F on port 0x00010177
> 11:08:58: ata4.00: configured for PIO2
> 11:08:58: ata4: EH complete

Thanks for this good clue.

<3>ata port 1: protocol 6 task_state 4
11:08:57:          res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)

>From the trace, the zip 100 drive clears BSY and raises irq to tell libata
when it is ready to transfer the CDB. However, the DRQ is not set yet. The status
0x00 causes libata HSM violation.

Maybe we can wait a moment and give the slow ATAPI devices some time to set DRQ.
Could you please try if the attached patch works, thanks.
--
albert

--- linux-2.6.20.3/drivers/ata/libata-core.c	2007-03-15 18:03:27.000000000 +0800
+++ linux-2.6.20.3-mod2/drivers/ata/libata-core.c	2007-03-17 01:12:53.000000000 +0800
@@ -4384,6 +4384,19 @@ fsm_start:
 		 */
 		poll_next = (qc->tf.flags & ATA_TFLAG_POLLING);
 
+		/* wait for some slow ATAPI devices to set DRQ */
+		if (unlikely((status & ATA_DRQ) == 0) &&
+		    is_atapi_taskfile(&qc->tf)) {
+			int max = 100;
+
+			do {
+				udelay(10);
+				status = ata_chk_status(ap);
+				max--;
+				ata_port_printk(ap, KERN_ERR, "wait for DRQ %d\n", 100-max);	
+			} while (((status & ATA_DRQ) == 0) && (max > 0));
+		}
+
 		/* check device status */
 		if (unlikely((status & ATA_DRQ) == 0)) {
 			/* handle BSY=0, DRQ=0 as error */

Re: IOMEGA IDE ZIP (ATAPI) drive

[Mark Lord]

Albert Lee wrote:
>..
> Maybe we can wait a moment and give the slow ATAPI devices some time to set DRQ.
> Could you please try if the attached patch works, thanks.
> --
> albert
> 
> --- linux-2.6.20.3/drivers/ata/libata-core.c	2007-03-15 18:03:27.000000000 +0800
> +++ linux-2.6.20.3-mod2/drivers/ata/libata-core.c	2007-03-17 01:12:53.000000000 +0800
> @@ -4384,6 +4384,19 @@ fsm_start:
>  		 */
>  		poll_next = (qc->tf.flags & ATA_TFLAG_POLLING);
>  
> +		/* wait for some slow ATAPI devices to set DRQ */
> +		if (unlikely((status & ATA_DRQ) == 0) &&
> +		    is_atapi_taskfile(&qc->tf)) {
> +			int max = 100;
> +
> +			do {
> +				udelay(10);
> +				status = ata_chk_status(ap);
> +				max--;
> +				ata_port_printk(ap, KERN_ERR, "wait for DRQ %d\n", 100-max);	
> +			} while (((status & ATA_DRQ) == 0) && (max > 0));
> +		}
> +
>  		/* check device status */
>  		if (unlikely((status & ATA_DRQ) == 0)) {
>  			/* handle BSY=0, DRQ=0 as error */
> 

I patched the above in, and it was NEVER hit.

-ml

Re: IOMEGA IDE ZIP (ATAPI) drive

[Albert Lee]

Mark Lord wrote:
> Albert Lee wrote:
> 
>> ..
>> Maybe we can wait a moment and give the slow ATAPI devices some time
>> to set DRQ.
>> Could you please try if the attached patch works, thanks.
>> -- 
>> albert
>>
>> --- linux-2.6.20.3/drivers/ata/libata-core.c    2007-03-15
>> 18:03:27.000000000 +0800
>> +++ linux-2.6.20.3-mod2/drivers/ata/libata-core.c    2007-03-17
>> 01:12:53.000000000 +0800
>> @@ -4384,6 +4384,19 @@ fsm_start:
>>           */
>>          poll_next = (qc->tf.flags & ATA_TFLAG_POLLING);
>>  
>> +        /* wait for some slow ATAPI devices to set DRQ */
>> +        if (unlikely((status & ATA_DRQ) == 0) &&
>> +            is_atapi_taskfile(&qc->tf)) {
>> +            int max = 100;
>> +
>> +            do {
>> +                udelay(10);
>> +                status = ata_chk_status(ap);
>> +                max--;
>> +                ata_port_printk(ap, KERN_ERR, "wait for DRQ %d\n",
>> 100-max);   
>> +            } while (((status & ATA_DRQ) == 0) && (max > 0));
>> +        }
>> +
>>          /* check device status */
>>          if (unlikely((status & ATA_DRQ) == 0)) {
>>              /* handle BSY=0, DRQ=0 as error */
>>
> 
> I patched the above in, and it was NEVER hit.

Do you mean no "wait for DRQ" messages at all?
Is the HSM violation still seen?

--
albert

Re: IOMEGA IDE ZIP (ATAPI) drive

[Mark Lord]

Albert Lee wrote:
> Mark Lord wrote:
>..
>> I patched the above in, and it was NEVER hit.
> 
> Do you mean no "wait for DRQ" messages at all?
> Is the HSM violation still seen?

The code you sent me to patch in was never hit.
The "wait for DRQ" message therefore never gets output.
The exact same set of HSM violation messages still appear.

Of course this makes perfect sense -- the HSM messages
are not being generated in response to any command,
but rather in response to ejecting a disk -- which I think
causes the drive to generate an unsolicited event.

Cheers

Re: IOMEGA IDE ZIP (ATAPI) drive

[Albert Lee]

Mark Lord wrote:
> Albert Lee wrote:
> 
>> Mark Lord wrote:
>> ..
>>
>>> I patched the above in, and it was NEVER hit.
>>
>>
>> Do you mean no "wait for DRQ" messages at all?
>> Is the HSM violation still seen?
> 
> 
> The code you sent me to patch in was never hit.
> The "wait for DRQ" message therefore never gets output.
> The exact same set of HSM violation messages still appear.
> 
> Of course this makes perfect sense -- the HSM messages
> are not being generated in response to any command,
> but rather in response to ejecting a disk -- which I think
> causes the drive to generate an unsolicited event.
> 

Hi Mark,

Could you please apply the attached debug patch (against 2.6.21-rc4).
(BTW, the zip 100 must be connected to ata4.)
Hopefully we could have more clue about the HSM violation.

--
thanks,

albert


diff -Nrup linux-2.6.21-rc4/drivers/ata/libata-core.c linux-2.6.21-rc4-mod/drivers/ata/libata-core.c
--- linux-2.6.21-rc4/drivers/ata/libata-core.c	2007-03-16 08:20:01.000000000 +0800
+++ linux-2.6.21-rc4-mod/drivers/ata/libata-core.c	2007-03-20 18:04:15.000000000 +0800
@@ -4350,8 +4350,9 @@ int ata_hsm_move(struct ata_port *ap, st
 	WARN_ON(in_wq != ata_hsm_ok_in_wq(ap, qc));
 
 fsm_start:
-	DPRINTK("ata%u: protocol %d task_state %d (dev_stat 0x%X)\n",
-		ap->print_id, qc->tf.protocol, ap->hsm_task_state, status);
+	if (ap->print_id == 4)
+		printk(KERN_ERR "ata%u: protocol %d task_state %d (dev_stat 0x%X)\n",
+		       ap->print_id, qc->tf.protocol, ap->hsm_task_state, status);
 
 	switch (ap->hsm_task_state) {
 	case HSM_ST_FIRST:
@@ -5071,8 +5072,14 @@ inline unsigned int ata_host_intr (struc
 	struct ata_eh_info *ehi = &ap->eh_info;
 	u8 status, host_stat = 0;
 
-	VPRINTK("ata%u: protocol %d task_state %d\n",
-		ap->print_id, qc->tf.protocol, ap->hsm_task_state);
+	if (ap->print_id == 4) {
+		printk(KERN_ERR "ata%u: protocol %d task_state %d\n",
+		       ap->print_id, qc->tf.protocol, ap->hsm_task_state);
+
+		host_stat = ap->ops->bmdma_status(ap);
+		printk(KERN_ERR "ata%u: host_stat 0x%X\n", ap->print_id, host_stat);
+	}
+
 
 	/* Check whether we are expecting interrupt in this state */
 	switch (ap->hsm_task_state) {
@@ -5118,11 +5125,17 @@ inline unsigned int ata_host_intr (struc
 
 	/* check altstatus */
 	status = ata_altstatus(ap);
+	if (ap->print_id == 4)
+		printk(KERN_ERR "ata%u: dev_altstatus 0x%X\n",
+		       ap->print_id, status);
 	if (status & ATA_BUSY)
 		goto idle_irq;
 
 	/* check main status, clearing INTRQ */
 	status = ata_chk_status(ap);
+	if (ap->print_id == 4)
+		printk(KERN_ERR "ata%u: dev_status 0x%X\n",
+		       ap->print_id, status);
 	if (unlikely(status & ATA_BUSY))
 		goto idle_irq;
 
diff -Nrup linux-2.6.21-rc4/drivers/ata/libata-scsi.c linux-2.6.21-rc4-mod/drivers/ata/libata-scsi.c
--- linux-2.6.21-rc4/drivers/ata/libata-scsi.c	2007-03-16 08:20:01.000000000 +0800
+++ linux-2.6.21-rc4-mod/drivers/ata/libata-scsi.c	2007-03-20 18:05:38.000000000 +0800
@@ -2773,17 +2773,17 @@ static inline ata_xlat_func_t ata_get_xl
 static inline void ata_scsi_dump_cdb(struct ata_port *ap,
 				     struct scsi_cmnd *cmd)
 {
-#ifdef ATA_DEBUG
 	struct scsi_device *scsidev = cmd->device;
 	u8 *scsicmd = cmd->cmnd;
 
-	DPRINTK("CDB (%u:%d,%d,%d) %02x %02x %02x %02x %02x %02x %02x %02x %02x\n",
-		ap->print_id,
-		scsidev->channel, scsidev->id, scsidev->lun,
-		scsicmd[0], scsicmd[1], scsicmd[2], scsicmd[3],
-		scsicmd[4], scsicmd[5], scsicmd[6], scsicmd[7],
-		scsicmd[8]);
-#endif
+	if (ap->print_id == 4) {
+		printk(KERN_ERR "CDB (%u:%d,%d,%d) %02x %02x %02x %02x %02x %02x %02x %02x %02x\n",
+		       ap->print_id,
+		       scsidev->channel, scsidev->id, scsidev->lun,
+		       scsicmd[0], scsicmd[1], scsicmd[2], scsicmd[3],
+		       scsicmd[4], scsicmd[5], scsicmd[6], scsicmd[7],
+		       scsicmd[8]);
+	}
 }
 
 static inline int __ata_scsi_queuecmd(struct scsi_cmnd *scmd,

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Albert Lee]

Tejun Heo wrote:

> 
> 
> Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
> don't think the low level driver is causing the difference.  They both
> use the standard libata HSM implementation.  Any ideas?  Stanislav, can
> you try to connect that zip drive to another IDE controller?
> 

Maybe it's also worth a try to replace the medium, cable or even the
drive itself to rule out the possibility of hardware problem.

--
albert

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

Albert Lee wrote:
> Jeff Garzik wrote:
>> Tejun Heo wrote:
>>
>>> [libata]
>>> And, as the device requires custom high level driver, libata fails
>>> miserably.  Would it be worth to try support these devices?  Or are
>>> they just too outdated to put the effort in?
>>
>> What SCSI peripheral device type does it report, when booted under libata?
>>
>>     Jeff
>>
>>
>> P.S.  As an aside, this reminds to unpack the SATA tape drive I was
>> handed many moons ago, and test it with libata.
>>
> 
> Libata works well with my zip 100 drive since 2.6.18 or even earlier.
> I just test it again with 2.6.20.3, it looks good on detection (except
> the "abnormal status 0x7F on port 0xE08895DF" warning):
> 
> ata3.00: ATAPI, max UDMA/33
> ata3.01: ATAPI, max UDMA/33
> ata3.00: configured for UDMA/33
> ata3.01: configured for UDMA/33
> scsi3 : pata_pdc2027x
> ATA: abnormal status 0x7F on port 0xE08895DF
> ATA: abnormal status 0x7F on port 0xE08895DF
> ata4.00: ATAPI, max PIO2, CDB intr
> ata4.00: configured for PIO2
> scsi 2:0:0:0: CD-ROM            LITE-ON  CD-RW SOHR-5238S 4S07 PQ: 0 ANSI: 5
> scsi 2:0:1:0: CD-ROM            HL-DT-ST DVDRAM GSA-4163B A105 PQ: 0 ANSI: 5
> scsi 3:0:0:0: Direct-Access     IOMEGA   ZIP 100          14.A PQ: 0 ANSI: 5
> 
> Read/write/eject also works without error.
> Full dmesg attached for your reference.

Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
don't think the low level driver is causing the difference.  They both
use the standard libata HSM implementation.  Any ideas?  Stanislav, can
you try to connect that zip drive to another IDE controller?

Thanks.

-- 
tejun

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Albert Lee]

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

Jeff Garzik wrote:
> Tejun Heo wrote:
> 
>> [libata]
>> And, as the device requires custom high level driver, libata fails
>> miserably.  Would it be worth to try support these devices?  Or are
>> they just too outdated to put the effort in?
> 
> 
> What SCSI peripheral device type does it report, when booted under libata?
> 
>     Jeff
> 
> 
> P.S.  As an aside, this reminds to unpack the SATA tape drive I was
> handed many moons ago, and test it with libata.
> 

Libata works well with my zip 100 drive since 2.6.18 or even earlier.
I just test it again with 2.6.20.3, it looks good on detection (except
the "abnormal status 0x7F on port 0xE08895DF" warning):

ata3.00: ATAPI, max UDMA/33
ata3.01: ATAPI, max UDMA/33
ata3.00: configured for UDMA/33
ata3.01: configured for UDMA/33
scsi3 : pata_pdc2027x
ATA: abnormal status 0x7F on port 0xE08895DF
ATA: abnormal status 0x7F on port 0xE08895DF
ata4.00: ATAPI, max PIO2, CDB intr
ata4.00: configured for PIO2
scsi 2:0:0:0: CD-ROM            LITE-ON  CD-RW SOHR-5238S 4S07 PQ: 0 ANSI: 5
scsi 2:0:1:0: CD-ROM            HL-DT-ST DVDRAM GSA-4163B A105 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access     IOMEGA   ZIP 100          14.A PQ: 0 ANSI: 5

Read/write/eject also works without error.
Full dmesg attached for your reference.
--
albert

[-- Attachment #2: dmesg_2.6.20.3_zip100.txt --]
[-- Type: text/plain, Size: 16398 bytes --]

Linux version 2.6.20.3 (albertcc@p4ht-s.tw.ibm.com) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 PREEMPT Wed Mar 14 15:03:36 CST 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000001fef0000 end: 000000001fff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000001fff0000 size: 0000000000003000 end: 000000001fff3000 type: 4
copy_e820_map() start: 000000001fff3000 size: 000000000000d000 end: 0000000020000000 type: 3
copy_e820_map() start: 00000000fec00000 size: 0000000001400000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
 BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
 BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
Entering add_active_range(0, 0, 131056) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   131056
  HighMem    131056 ->   131056
early_node_map[1] active PFN ranges
    0:        0 ->   131056
On node 0 totalpages: 131056
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 991 pages used for memmap
  Normal zone: 125969 pages, LIFO batch:31
  HighMem zone: 0 pages used for memmap
DMI 2.2 present.
ACPI: RSDP (v000 IntelR                                ) @ 0x000f6e00
ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3000
ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3040
ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff7680
ACPI: DSDT (v001 INTELR AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x408
Allocating PCI resources starting at 30000000 (gap: 20000000:dec00000)
Detected 2424.104 MHz processor.
Built 1 zonelists.  Total pages: 130033
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c041e000 soft=c041f000
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 513740k/524224k available (2180k kernel code, 9820k reserved, 786k data, 200k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffdd000 - 0xfffff000   ( 136 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xe0800000 - 0xff7fe000   ( 495 MB)
    lowmem  : 0xc0000000 - 0xdfff0000   ( 511 MB)
      .init : 0xc03e7000 - 0xc0419000   ( 200 kB)
      .data : 0xc0321347 - 0xc03e5c10   ( 786 kB)
      .text : 0xc0100000 - 0xc0321347   (2180 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4851.82 BogoMIPS (lpj=9703655)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 128K
CPU: After all inits, caps: bfebfbff 00000000 00000000 00003080 00004400 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
Compat vDSO mapped to ffffe000.
CPU: Intel(R) Celeron(R) CPU 2.40GHz stepping 09
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0e20)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfae20, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
* The chipset may have PM-Timer Bug. Due to workarounds for a bug,
* this clock source is slow. If you are sure your timer does not have
* this bug, please use "acpi_pm_good" to disable the workaround
PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH4 GPIO
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 *10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pnp: 00:02: ioport range 0x400-0x4bf could not be reserved
PCI: Bridge: 0000:00:01.0
  IO window: disabled.
  MEM window: ec000000-edffffff
  PREFETCH window: e0000000-e7ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: a000-cfff
  MEM window: ee000000-ee0fffff
  PREFETCH window: 30000000-300fffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 1796k freed
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1173886126.644:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: Fan [FAN] (on)
ACPI: Thermal Zone [THRM] (25 C)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
intel_rng: FWH not detected
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 845G Chipset.
agpgart: AGP aperture is 64M @ 0xe8000000
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
ACPI: (supports S0 S1 S4 S5)
Freeing unused kernel memory: 200k freed
SCSI subsystem initialized
libata version 2.00 loaded.
ata_piix 0000:00:1f.1: version 2.00ac7
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.1 to 64
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi0 : ata_piix
logips2pp: Detected unknown logitech mouse model 11
ata1.00: ATA-6, max UDMA/100, 390721968 sectors: LBA48 
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : ata_piix
scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00K 08.0 PQ: 0 ANSI: 5
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
pata_pdc2027x 0000:02:05.0: version 0.74-ac5
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 10
ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [LNK1] -> GSI 10 (level, low) -> IRQ 10
pata_pdc2027x 0000:02:05.0: PLL input clock 16961 kHz
ata3: PATA max UDMA/133 cmd 0xE08897C0 ctl 0xE0889FDA bmdma 0xE0889000 irq 10
ata4: PATA max UDMA/133 cmd 0xE08895C0 ctl 0xE0889DDA bmdma 0xE0889008 irq 10
scsi2 : pata_pdc2027x
input: ImPS/2 Logitech Wheel Mouse as /class/input/input1
ata3.00: ATAPI, max UDMA/33
ata3.01: ATAPI, max UDMA/33
ata3.00: configured for UDMA/33
ata3.01: configured for UDMA/33
scsi3 : pata_pdc2027x
ATA: abnormal status 0x7F on port 0xE08895DF
ATA: abnormal status 0x7F on port 0xE08895DF
ata4.00: ATAPI, max PIO2, CDB intr
ata4.00: configured for PIO2
scsi 2:0:0:0: CD-ROM            LITE-ON  CD-RW SOHR-5238S 4S07 PQ: 0 ANSI: 5
scsi 2:0:1:0: CD-ROM            HL-DT-ST DVDRAM GSA-4163B A105 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access     IOMEGA   ZIP 100          14.A PQ: 0 ANSI: 5
sd 3:0:0:0: Attached scsi removable disk sdb
sata_sil 0000:02:04.0: version 2.0
ACPI: PCI Interrupt Link [LNK0] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK0] -> GSI 11 (level, low) -> IRQ 11
ata5: SATA max UDMA/100 cmd 0xE0832080 ctl 0xE083208A bmdma 0xE0832000 irq 11
ata6: SATA max UDMA/100 cmd 0xE08320C0 ctl 0xE08320CA bmdma 0xE0832008 irq 11
scsi4 : sata_sil
ata5: SATA link down (SStatus 0 SControl 310)
scsi5 : sata_sil
ata6: SATA link down (SStatus 0 SControl 310)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
SELinux:  Disabled at runtime.
SELinux:  Unregistering netfilter hooks
audit(1173886130.848:2): selinux=0 auid=4294967295
sr0: scsi3-mmc drive: 95x/52x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 2:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
sr 2:0:1:0: Attached scsi CD-ROM sr1
FDC 0 is a post-1991 82077
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
eth0: RealTek RTL8139 at 0xa000, 00:d0:68:01:36:f9, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNK1] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 10, io mem 0xee100000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ 9
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 9, io base 0x0000d800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 5, io base 0x0000d000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 10, io base 0x0000d400
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
asus_acpi: Unknown symbol backlight_device_unregister
asus_acpi: Unknown symbol backlight_device_register
input: Power Button (FF) as /class/input/input2
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input3
ACPI: Power Button (CM) [PWRB]
ibm_acpi: Unknown symbol backlight_device_unregister
ibm_acpi: Unknown symbol backlight_device_register
toshiba_acpi: Unknown symbol backlight_device_unregister
toshiba_acpi: Unknown symbol backlight_device_register
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3 FS on dm-0, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1048568k swap on /dev/VolGroup00/LogVol01.  Priority:-1 extents:1 across:1048568k
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
audit(1173857362.508:3): audit_pid=1780 old=0 by auid=4294967295
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
lp0: console ready
eth0: no IPv6 routers present
sdb: Spinning up disk.....ready
SCSI device sdb: 196608 512-byte hdwr sectors (101 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 40 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdb: 196608 512-byte hdwr sectors (101 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 40 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb4

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

Alan Cox wrote:
>> It seems ide-floppy needs some special handlings in interrupt handling
>> too like delaying data transfer by several ticks after device indicates
>> readiness.  Apart from separate high level driver, we might have to
>> modify libata HSM implementation if we're gonna support these devices.
> 
> The data transfer delay may well be down to the DMA bug

I see.

>> Can someone more knowledgeable explain what needs to be done differently
>> from standard ATAPI for these devices?
> 
> In theory not a lot if anything. I don't have a ZIP drive but have got an
> old Iomega Clik! PCMCIA drive somewhere if you need an ide-floppy device
> Tejun.

If you've got a spare one, that would be great but otherwise I think
you're much better qualified for libata ide-floppy support. :-)

Thanks.

-- 
tejun

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Alan Cox]

> It seems ide-floppy needs some special handlings in interrupt handling
> too like delaying data transfer by several ticks after device indicates
> readiness.  Apart from separate high level driver, we might have to
> modify libata HSM implementation if we're gonna support these devices.

The data transfer delay may well be down to the DMA bug

> Can someone more knowledgeable explain what needs to be done differently
> from standard ATAPI for these devices?

In theory not a lot if anything. I don't have a ZIP drive but have got an
old Iomega Clik! PCMCIA drive somewhere if you need an ide-floppy device
Tejun.

Alan

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]

Stanislav Brabec wrote:
> Jeff Garzik wrote:
>> Tejun Heo wrote:
>>> [libata]
>>> And, as the device requires custom high level driver, libata fails
>>> miserably.  Would it be worth to try support these devices?  Or are
>>> they just too outdated to put the effort in?
>> What SCSI peripheral device type does it report, when booted under libata?
> 
> Internal IOMEGA ZIP 100 IDE (manufactured by NEC).
> 
> ata1.01: ATAPI, max PIO2, CDB intr
> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
>          res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
> ata1: soft resetting port
> ata1.01: configured for PIO2
> ata1: EH complete
> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
>          res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
> ata1.01: configured for PIO2
> ata1: EH complete
> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
>          res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
> ata1: soft resetting port
> ... and so on
> 
> For more see
> https://bugzilla.novell.com/show_bug.cgi?id=232086
> (complete ide-floppy and libata logs are there)

I'm attaching full dmesg with libata here just in case.

It seems ide-floppy needs some special handlings in interrupt handling
too like delaying data transfer by several ticks after device indicates
readiness.  Apart from separate high level driver, we might have to
modify libata HSM implementation if we're gonna support these devices.

Can someone more knowledgeable explain what needs to be done differently
from standard ATAPI for these devices?

Thanks.

-- 
tejun

[-- Attachment #2: sata.log --]
[-- Type: text/x-log, Size: 90160 bytes --]

Linux version 2.6.20.1-default (root@utx) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Thu Feb 22 21:41:49 CET 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000002fef0000 end: 000000002fff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000002fff0000 size: 0000000000008000 end: 000000002fff8000 type: 3
copy_e820_map() start: 000000002fff8000 size: 0000000000008000 end: 0000000030000000 type: 4
copy_e820_map() start: 00000000fff80000 size: 0000000000080000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002fff0000 (usable)
 BIOS-e820: 000000002fff0000 - 000000002fff8000 (ACPI data)
 BIOS-e820: 000000002fff8000 - 0000000030000000 (ACPI NVS)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
767MB LOWMEM available.
Entering add_active_range(0, 0, 196592) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   196592
  HighMem    196592 ->   196592
early_node_map[1] active PFN ranges
    0:        0 ->   196592
On node 0 totalpages: 196592
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 1503 pages used for memmap
  Normal zone: 190993 pages, LIFO batch:31
  HighMem zone: 0 pages used for memmap
DMI 2.3 present.
Using APIC driver default
ACPI: RSDP (v000 AMI                                   ) @ 0x000fc3c0
ACPI: RSDT (v001 AMIINT          0x00000011 MSFT 0x00000097) @ 0x2fff0000
ACPI: FADT (v001 AMIINT          0x00000011 MSFT 0x00000097) @ 0x2fff0030
ACPI: DSDT (v001    VIA   VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 40000000 (gap: 30000000:cff80000)
Detected 1338.095 MHz processor.
Built 1 zonelists.  Total pages: 195057
Kernel command line: root=/dev/sda1 vga=0x31a resume=/dev/sda5 splash=silent
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (0160c000)
Enabling fast FPU save and restore... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 772536k/786368k available (1708k kernel code, 13248k reserved, 719k data, 192k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xffe15000 - 0xfffff000   (1960 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf0800000 - 0xff7fe000   ( 239 MB)
    lowmem  : 0xc0000000 - 0xefff0000   ( 767 MB)
      .init : 0xc0366000 - 0xc0396000   ( 192 kB)
      .data : 0xc02ab3af - 0xc035f354   ( 719 kB)
      .text : 0xc0100000 - 0xc02ab3af   (1708 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2678.90 BogoMIPS (lpj=5357803)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 1c20)
CPU0: AMD Athlon(tm) Processor stepping 04
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 *12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:01.0
  IO window: 8000-9fff
  MEM window: dfe00000-dfefffff
  PREFETCH window: d7c00000-dfcfffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 3241k freed
Machine check exception polling timer started.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1172434137.792:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xd8000000, mapped to 0xf0880000, using 5120k, total 32768k
vesafb: mode is 1280x1024x16, linelength=2560, pages=11
vesafb: protected mode interface info at c000:4d22
vesafb: pmi: set display start = c00c4d90, set palette = c00c4dca
vesafb: pmi: ports = 9810 9816 9854 9838 983c 985c 9800 9804 98b0 98b2 98b4 
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 160x64
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
input: PC Speaker as /class/input/input1
NET: Registered protocol family 1
Using IPI No-Shortcut mode
ACPI: (supports S0 S3 S4 S5)
Time: tsc clocksource has been installed.
Freeing unused kernel memory: 192k freed
SCSI subsystem initialized
ACPI: Processor [CPU1] (supports 16 throttling states)
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
dc395x: Used settings: AdapterID=07, Speed=0(20.0MHz), dev_mode=0x57
dc395x:                AdaptMode=0x0f, Tags=4(16), DelayReset=1s
dc395x: Connectors:  Termination: Auto Low High 
dc395x: Performing initial SCSI bus reset
scsi0 : Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
libata version 2.00 loaded.
pata_via 0000:00:11.1: version 0.2.1
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xFF00 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xFF08 irq 15
scsi1 : pata_via
ata1.00: ATA-7, max UDMA/100, 312581808 sectors: LBA48 
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATAPI, max PIO2, CDB intr
ata1.00: configured for UDMA/100
ata1.01: configured for PIO2
scsi2 : pata_via
ata2.00: ATAPI, max UDMA/66
ata2.01: ATAPI, max UDMA/33
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
scsi 1:0:0:0: Direct-Access     ATA      ST3160812A       3.AA PQ: 0 ANSI: 5
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
sd 1:0:0:0: Attached scsi disk sda
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1: soft resetting port
sd 1:0:0:0: Attached scsi generic sg0 type 0
ata1.00: configured for UDMA/33
ata1.01: configured for PIO2
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1.01: configured for PIO2
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1.01: configured for PIO2
ata1: EH complete
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1.01: configured for PIO2
ata1: EH complete
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GSA-4160B A306 PQ: 0 ANSI: 5
scsi 2:0:0:0: Attached scsi generic sg1 type 5
scsi 2:0:1:0: CD-ROM            TEAC     CD-W540E         1.0K PQ: 0 ANSI: 5
scsi 2:0:1:0: Attached scsi generic sg2 type 5
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/64:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
spurious 8259A interrupt: IRQ7.
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 2:0:0:0: Attached scsi CD-ROM sr0
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: (BMDMA stat 0x65)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
         res 51/54:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: (BMDMA stat 0x65)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
         res 51/54:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr1: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
sr 2:0:1:0: Attached scsi CD-ROM sr1
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
Attempting manual resume
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]
lp0: using parport0 (interrupt-driven).
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ieee80211_crypt: registered algorithm 'NULL'
ata2.00: configured for UDMA/66
ACPI: PCI Interrupt 0000:00:07.2[C] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
ehci_hcd 0000:00:07.2: EHCI Host Controller
ehci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
NET: Registered protocol family 23
ehci_hcd 0000:00:07.2: irq 10, io mem 0xdfffee00
ehci_hcd 0000:00:07.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
8139too Fast Ethernet driver 0.9.28
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf0814f00, 00:50:fc:33:ce:ba, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
hostap_pci: Registered netdevice wifi0
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
wifi0: Original COR value: 0x0
USB Universal Host Controller Interface driver v3.0
ata2.00: configured for UDMA/66
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
prism2_hw_init: initialized in 580 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.0.7
wifi0: STA: id=0x1f v1.3.6
ata2.00: configured for UDMA/66
Linux agpgart interface v0.101 (c) Dave Jones
gameport: NS558 PnP Gameport is pnp00:0a/gameport0, io 0x200, speed 877kHz
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
wifi0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: Intersil Prism2.5 PCI: mem=0xdfdff000, irq=12
wifi0: registered netdevice wlan0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
uhci_hcd 0000:00:11.2: UHCI Host Controller
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 2
ata2.01: configured for UDMA/33
ata2: EH complete
uhci_hcd 0000:00:11.2: irq 12, io base 0x0000c800
usb usb2: configuration #1 chosen from 1 choice
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:11.3[D] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
uhci_hcd 0000:00:11.3: UHCI Host Controller
uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:11.3: irq 12, io base 0x0000cc00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
es1968: not attempting power management.
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
usb 3-2: new full speed USB device using uhci_hcd and address 2
es1968: clocking to 48000
ata2.00: configured for UDMA/66
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
ohci_hcd 0000:00:07.0: OHCI Host Controller
ohci_hcd 0000:00:07.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:07.0: irq 5, io mem 0xdfffc000
usb 3-2: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ACPI: PCI Interrupt 0000:00:07.1[B] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
ohci_hcd 0000:00:07.1: OHCI Host Controller
ohci_hcd 0000:00:07.1: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:07.1: irq 12, io mem 0xdfffd000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
agpgart: Detected VIA KT266/KY266x/KT333 chipset
agpgart: AGP aperture is 64M @ 0xe0000000
usb0: register 'gl620a' at usb-0000:00:11.3-2, Genesys GeneLink, 5e:c0:c5:2a:8a:0a
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
usb 4-2: new low speed USB device using ohci_hcd and address 2
ata2.00: configured for UDMA/66
usb 4-2: configuration #1 chosen from 1 choice
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
usb 4-3: new full speed USB device using ohci_hcd and address 3
ata2.00: configured for UDMA/66
usb 4-3: configuration #1 chosen from 1 choice
usbcore: registered new interface driver gl620a
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
usb 5-1: new low speed USB device using ohci_hcd and address 2
ata2.00: configured for UDMA/66
usb 5-1: string descriptor 0 read error: -22
usb 5-1: string descriptor 0 read error: -22
usb 5-1: configuration #1 chosen from 1 choice
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: (BMDMA stat 0x65)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
         res 51/54:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
input: ATI/X10 RF USB Remote Control(0bc7,0004) as /class/input/input2
usbcore: registered new interface driver ati_remote
drivers/usb/input/ati_remote.c: Weird data, len=1 ff 00 00 00 00 00 ...
drivers/usb/input/ati_remote.c: Registered USB driver ATI/X10 RF USB Remote Control v. 2.2.1
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: (BMDMA stat 0x65)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
         res 51/54:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
Adding 2104472k swap on /dev/sda5.  Priority:-1 extents:1 across:2104472k
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
loop: loaded (max 8 devices)
ReiserFS: sda6: found reiserfs format "3.6" with standard journal
ReiserFS: sda6: using ordered data mode
ReiserFS: sda6: journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda6: checking transaction log (sda6)
ReiserFS: sda6: Using r5 hash to sort names
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ReiserFS: sda2: found reiserfs format "3.6" with standard journal
ReiserFS: sda2: using ordered data mode
ReiserFS: sda2: journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda2: checking transaction log (sda2)
ReiserFS: sda2: Using r5 hash to sort names
input: Power Button (FF) as /class/input/input3
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input4
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /class/input/input5
ACPI: Sleep Button (CM) [SLPB]
powernow-k8: Processor cpuid 644 not supported
powernow: No powernow capabilities detected
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 17
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
audit(1172434229.307:2): audit_pid=3602 old=0 by auid=4294967295
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
ata2.00: configured for UDMA/66
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
eth0: no IPv6 routers present
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
[drm] Initialized r128 2.5.0 20030725 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x0 data 0 
         res 51/20:03:00:00:20/00:00:00:00:00/b0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr1: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ACPI: PCI interrupt for device 0000:00:06.0 disabled
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf12f6f00, 00:50:fc:33:ce:ba, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
eth0: no IPv6 routers present
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 
         res 51/24:03:00:00:20/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: configured for UDMA/66
ata2.01: configured for UDMA/33
ata2: EH complete
sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
sr: Current [descriptor]: sense key: Aborted Command
    Additional sense: No additional sense information

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Bartlomiej Zolnierkiewicz]

Hi,

On Monday 12 March 2007, Sergei Shtylyov wrote:
> Hello.
> 
> Tejun Heo wrote:
> 
> > Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
> > recent kernels.  Low level driver is via82cxxx.  Relevant part of
> > 2.6.20.1 boot message follows.
> 
> >  VP_IDE: IDE controller at PCI slot 0000:00:11.1
> >  VP_IDE: chipset revision 6
> >  VP_IDE: not 100% native mode: will probe irqs later
> >  VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
> >      ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
> >      ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
> >  Probing IDE interface ide0...
> >  hda: ST3160812A, ATA DISK drive
> >  hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
> >  ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >  ...
> >  hdb: lost interrupt
> >  hdb: status error: status=0x00 { }
> >  ide: failed opcode was: unknown
> >  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> >  ...
> >  hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
> >  hdb: No disk in drive
> >  hdb: lost interrupt
> >  hdb: status error: status=0x00 { }
> >  ide: failed opcode was: unknown
> >  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> >  [above repeats several times]
> >  ...
> >  hdb: lost interrupt
> >  hdb: status error: status=0x00 { }
> >  ide: failed opcode was: unknown
> >  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> >  hdb: 98304kB, 196608 blocks, 512 sector size
> >   hdb: unknown partition table
> >   hdb: unknown partition table
> >   hdb: unknown partition table
> >   hdb: unknown partition table
> 
> > And the device is inaccessible after boot completed.  On suse 10.1
> > kernel (2.6.16 based), it works better.
> 
> >  VP_IDE: IDE controller at PCI slot 0000:00:11.1
> >  PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
> >  VP_IDE: chipset revision 6
> >  VP_IDE: not 100% native mode: will probe irqs later
> >  VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
> >      ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
> >      ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
> >  Probing IDE interface ide0...
> >  hda: ST3160812A, ATA DISK drive
> >  hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
> >  ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> >  ...
> >  hdb: No disk in drive
> >  hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
> >  ...
> >  hdb: lost interrupt
> >  hdb: status error: status=0x00 { }
> >  ide: failed opcode was: unknown
> >  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
> >  hdb: 98304kB, 196608 blocks, 512 sector size
> >   hdb: unknown partition table
> 
> > There is one lost interrupt message but the drive reportedly works
> > fine after that.  Stanislav also seems to recall that ide-floppy
> > worked without any error message with older kernel.
> 
> > I'm attaching full boot log messages for 2.6.20.1 and suse 10.1.
> 
> > Any ideas?
> 
>     BTW... I've looked at that code last spring and found it strange that 
> ide-floopy is the only driver that still calls dma_start() method *before* 
> issuing a command *while this is not a right thing to do accoring to spec and 
> is known to not work with some chips, namely Promise).  I was going to send a 
> patch then but lacking both time and actual hardware, kept deferring it 
> since... :-)

We are probably hitting two bugs here:

* regression between 2.6.16-2.6.20

* the issue that Sergei described

Stanislav, could you use git bisect to narrow down the problem
to the specific patch?

Good practical example of using git-bisect is here:
http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/

Thanks,
Bart

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Stanislav Brabec]

Jeff Garzik wrote:
> Tejun Heo wrote:
> > [libata]
> > And, as the device requires custom high level driver, libata fails
> > miserably.  Would it be worth to try support these devices?  Or are
> > they just too outdated to put the effort in?
> 
> What SCSI peripheral device type does it report, when booted under libata?

Internal IOMEGA ZIP 100 IDE (manufactured by NEC).

ata1.01: ATAPI, max PIO2, CDB intr
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1: soft resetting port
ata1.01: configured for PIO2
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1.01: configured for PIO2
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
         res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
ata1: soft resetting port
... and so on

For more see
https://bugzilla.novell.com/show_bug.cgi?id=232086
(complete ide-floppy and libata logs are there)

-- 
Best Regards,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec@suse.cz
Lihovarska 1060/12                            tel: +420 284 028 966
190 00 Praha 9                                fax: +420 284 028 951
Czech Republic                                http://www.suse.cz/

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Jeff Garzik]

Tejun Heo wrote:
> [libata]
> And, as the device requires custom high level driver, libata fails
> miserably.  Would it be worth to try support these devices?  Or are
> they just too outdated to put the effort in?

What SCSI peripheral device type does it report, when booted under libata?

	Jeff


P.S.  As an aside, this reminds to unpack the SATA tape drive I was 
handed many moons ago, and test it with libata.

Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Sergei Shtylyov]

Hello.

Tejun Heo wrote:

> Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
> recent kernels.  Low level driver is via82cxxx.  Relevant part of
> 2.6.20.1 boot message follows.

>  VP_IDE: IDE controller at PCI slot 0000:00:11.1
>  VP_IDE: chipset revision 6
>  VP_IDE: not 100% native mode: will probe irqs later
>  VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
>      ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
>      ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
>  Probing IDE interface ide0...
>  hda: ST3160812A, ATA DISK drive
>  hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
>  ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>  ...
>  hdb: lost interrupt
>  hdb: status error: status=0x00 { }
>  ide: failed opcode was: unknown
>  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
>  ...
>  hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
>  hdb: No disk in drive
>  hdb: lost interrupt
>  hdb: status error: status=0x00 { }
>  ide: failed opcode was: unknown
>  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
>  [above repeats several times]
>  ...
>  hdb: lost interrupt
>  hdb: status error: status=0x00 { }
>  ide: failed opcode was: unknown
>  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
>  hdb: 98304kB, 196608 blocks, 512 sector size
>   hdb: unknown partition table
>   hdb: unknown partition table
>   hdb: unknown partition table
>   hdb: unknown partition table

> And the device is inaccessible after boot completed.  On suse 10.1
> kernel (2.6.16 based), it works better.

>  VP_IDE: IDE controller at PCI slot 0000:00:11.1
>  PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
>  VP_IDE: chipset revision 6
>  VP_IDE: not 100% native mode: will probe irqs later
>  VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
>      ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
>      ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
>  Probing IDE interface ide0...
>  hda: ST3160812A, ATA DISK drive
>  hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
>  ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>  ...
>  hdb: No disk in drive
>  hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
>  ...
>  hdb: lost interrupt
>  hdb: status error: status=0x00 { }
>  ide: failed opcode was: unknown
>  ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
>  hdb: 98304kB, 196608 blocks, 512 sector size
>   hdb: unknown partition table

> There is one lost interrupt message but the drive reportedly works
> fine after that.  Stanislav also seems to recall that ide-floppy
> worked without any error message with older kernel.

> I'm attaching full boot log messages for 2.6.20.1 and suse 10.1.

> Any ideas?

    BTW... I've looked at that code last spring and found it strange that 
ide-floopy is the only driver that still calls dma_start() method *before* 
issuing a command *while this is not a right thing to do accoring to spec and 
is known to not work with some chips, namely Promise).  I was going to send a 
patch then but lacking both time and actual hardware, kept deferring it 
since... :-)

MBR, Sergei

regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 2906 bytes --]

Hello, all.

Stanislav Brabec reported that IOMEGA IDE ZIP drive doesn't work with
recent kernels.  Low level driver is via82cxxx.  Relevant part of
2.6.20.1 boot message follows.

 VP_IDE: IDE controller at PCI slot 0000:00:11.1
 VP_IDE: chipset revision 6
 VP_IDE: not 100% native mode: will probe irqs later
 VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
     ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
     ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
 Probing IDE interface ide0...
 hda: ST3160812A, ATA DISK drive
 hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
 ...
 hdb: lost interrupt
 hdb: status error: status=0x00 { }
 ide: failed opcode was: unknown
 ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
 ...
 hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
 hdb: No disk in drive
 hdb: lost interrupt
 hdb: status error: status=0x00 { }
 ide: failed opcode was: unknown
 ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
 [above repeats several times]
 ...
 hdb: lost interrupt
 hdb: status error: status=0x00 { }
 ide: failed opcode was: unknown
 ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
 hdb: 98304kB, 196608 blocks, 512 sector size
  hdb: unknown partition table
  hdb: unknown partition table
  hdb: unknown partition table
  hdb: unknown partition table

And the device is inaccessible after boot completed.  On suse 10.1
kernel (2.6.16 based), it works better.

 VP_IDE: IDE controller at PCI slot 0000:00:11.1
 PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
 VP_IDE: chipset revision 6
 VP_IDE: not 100% native mode: will probe irqs later
 VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
     ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
     ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
 Probing IDE interface ide0...
 hda: ST3160812A, ATA DISK drive
 hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
 ...
 hdb: No disk in drive
 hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
 ...
 hdb: lost interrupt
 hdb: status error: status=0x00 { }
 ide: failed opcode was: unknown
 ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
 hdb: 98304kB, 196608 blocks, 512 sector size
  hdb: unknown partition table

There is one lost interrupt message but the drive reportedly works
fine after that.  Stanislav also seems to recall that ide-floppy
worked without any error message with older kernel.

I'm attaching full boot log messages for 2.6.20.1 and suse 10.1.

Any ideas?

[libata]
And, as the device requires custom high level driver, libata fails
miserably.  Would it be worth to try support these devices?  Or are
they just too outdated to put the effort in?

Thanks.

-- 
tejun

[-- Attachment #2: zip-failure-2.6.16-based-suse10.1.txt --]
[-- Type: text/plain, Size: 19494 bytes --]

Linux version 2.6.16.27-0.6-default (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 Wed Dec 13 09:34:50 UTC 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002fff0000 (usable)
 BIOS-e820: 000000002fff0000 - 000000002fff8000 (ACPI data)
 BIOS-e820: 000000002fff8000 - 0000000030000000 (ACPI NVS)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
767MB LOWMEM available.
No mptable found.
On node 0 totalpages: 196592
  DMA zone: 4096 pages, LIFO batch:0
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 192496 pages, LIFO batch:31
  HighMem zone: 0 pages, LIFO batch:0
DMI 2.3 present.
IO/L-APIC allowed because system is MP or new enough
ACPI: RSDP (v000 AMI                                   ) @ 0x000fc3c0
ACPI: RSDT (v001 AMIINT          0x00000011 MSFT 0x00000097) @ 0x2fff0000
ACPI: FADT (v001 AMIINT          0x00000011 MSFT 0x00000097) @ 0x2fff0030
ACPI: DSDT (v001    VIA   VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 40000000 (gap: 30000000:cff80000)
Built 1 zonelists
Kernel command line: root=/dev/hda2 vga=0x31a resume=/dev/hda5 splash=silent elevator=
bootsplash: silent mode.
Local APIC disabled by BIOS -- you can enable it with "lapic"
Enabling fast FPU save and restore... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 1338.227 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 773800k/786368k available (1490k kernel code, 12016k reserved, 608k data, 156k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2681.18 BogoMIPS (lpj=5362373)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) Processor stepping 04
Checking 'hlt' instruction... OK.
checking if image is initramfs... it is
Freeing initrd memory: 2365k freed
 not found!
ACPI: setting ELCR to 0200 (from 1c20)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 *12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
Setting up standard PCI resources
PCI: Bridge: 0000:00:01.0
  IO window: 8000-9fff
  MEM window: dfe00000-dfefffff
  PREFETCH window: d7c00000-dfcfffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1172471433.628:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xd8000000, mapped to 0xf0880000, using 10240k, total 32768k
vesafb: mode is 1280x1024x16, linelength=2560, pages=11
vesafb: protected mode interface info at c000:4d22
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 76045 bytes,<6>...found (1280x1024, 33692 bytes, v3).
Console: switching to colour frame buffer device 156x60
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
input: PC Speaker as /class/input/input1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Using IPI Shortcut mode
ACPI wakeup devices: 
PCI0 UAR1  USB USB1 USB2  AC9  MC9 ILAN SLPB 
ACPI: (supports S0 S3 S4 S5)
Freeing unused kernel memory: 156k freed
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SCSI subsystem initialized
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
dc395x: Used settings: AdapterID=07, Speed=0(20.0MHz), dev_mode=0x57
dc395x:                AdaptMode=0x0f, Tags=4(16), DelayReset=1s
dc395x: Connectors:  Termination: Auto Low High 
dc395x: Performing initial SCSI bus reset
scsi0 : Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
VP_IDE: IDE controller at PCI slot 0000:00:11.1
PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: ST3160812A, ATA DISK drive
hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 512KiB
hda: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
Probing IDE interface ide1...
hdc: HL-DT-ST DVDRAM GSA-4160B, ATAPI CD/DVD-ROM drive
hdd: CD-W540E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: Processor [CPU1] (supports 16 throttling states)
Attempting manual resume
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
Adding 2104472k swap on /dev/hda5.  Priority:-1 extents:1 across:2104472k
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]
ppdev: user-space parallel port driver
lp0: using parport0 (interrupt-driven).
usbcore: registered new driver usbfs
usbcore: registered new driver hub
hdc: ATAPI 63X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
uhci_hcd 0000:00:11.2: UHCI Host Controller
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:11.2: irq 12, io base 0x0000c800
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.16.27-0.6-default uhci_hcd
usb usb1: SerialNumber: 0000:00:11.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ieee80211_crypt: module not supported by Novell, setting U taint flag.
ACPI: PCI Interrupt 0000:00:11.3[D] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
uhci_hcd 0000:00:11.3: UHCI Host Controller
uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:11.3: irq 12, io base 0x0000cc00
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.16.27-0.6-default uhci_hcd
usb usb2: SerialNumber: 0000:00:11.3
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ieee80211_crypt: registered algorithm 'NULL'
ide-floppy driver 0.99.newide
hostap: module not supported by Novell, setting U taint flag.
NET: Registered protocol family 23
hostap_pci: module not supported by Novell, setting U taint flag.
hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
hdb: No disk in drive
hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
usb 2-2: new full speed USB device using uhci_hcd and address 2
prism2_hw_init: initialized in 288 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.0.7
wifi0: STA: id=0x1f v1.3.6
gameport: NS558 PnP Gameport is pnp00:0a/gameport0, io 0x200, speed 864kHz
via_ircc: module not supported by Novell, setting U taint flag.
usb 2-2: new device found, idVendor=05e3, idProduct=0502
usb 2-2: new device strings: Mfr=0, Product=1, SerialNumber=0
usb 2-2: Product: USB Host To Host Bridge
usb 2-2: configuration #1 chosen from 1 choice
8139too Fast Ethernet driver 0.9.27
Linux agpgart interface v0.101 (c) Dave Jones
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
wifi0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: Intersil Prism2.5 PCI: mem=0xdfdff000, irq=12
wifi0: registered netdevice wlan0
ACPI: PCI Interrupt 0000:00:07.2[C] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
ehci_hcd 0000:00:07.2: EHCI Host Controller
ehci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:07.2: irq 10, io mem 0xdfffee00
ehci_hcd 0000:00:07.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb3: new device found, idVendor=0000, idProduct=0000
usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: EHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.16.27-0.6-default ehci_hcd
usb usb3: SerialNumber: 0000:00:07.2
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 5 ports detected
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
es1968: not attempting power management.
prism2_download: dl_cmd=6 start_addr=0x003f0000 num_areas=3
wifi0: test Genesis mode with HCR 0x1f
wifi0: Original COR value: 0x0
Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 c1 a1 c1
wifi0: test Genesis mode with HCR 0x0f
wifi0: Original COR value: 0xa1
Readback test succeeded, HCR 0x0f
prism2_hw_init: initialized in 0 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.4
Could not get RID for component STA
wifi0: Failed to read STA f/w version - only Primary f/w present
usb0: register 'gl620a' at usb-0000:00:11.3-2, Genesys GeneLink, ca:43:3b:7e:19:3a
usbcore: registered new driver gl620a
es1968: clocking to 48000
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf1578f00, 00:50:fc:33:ce:ba, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
ohci_hcd 0000:00:07.0: OHCI Host Controller
ohci_hcd 0000:00:07.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:07.0: irq 5, io mem 0xdfffc000
prism2_download: dl_cmd=5 start_addr=0x003f0c01 num_areas=3
usb usb4: new device found, idVendor=0000, idProduct=0000
usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: OHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.16.27-0.6-default ohci_hcd
usb usb4: SerialNumber: 0000:00:07.0
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
prism2_hw_init: initialized in 300 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.4
wifi0: STA: id=0x1f v1.8.4
ACPI: PCI Interrupt 0000:00:07.1[B] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
ohci_hcd 0000:00:07.1: OHCI Host Controller
ohci_hcd 0000:00:07.1: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:07.1: irq 12, io mem 0xdfffd000
usb usb5: new device found, idVendor=0000, idProduct=0000
usb usb5: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: OHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.16.27-0.6-default ohci_hcd
usb usb5: SerialNumber: 0000:00:07.1
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
agpgart: Detected VIA KT266/KY266x/KT333 chipset
agpgart: AGP aperture is 64M @ 0xe0000000
usb 4-2: new low speed USB device using ohci_hcd and address 2
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
usb 4-2: new device found, idVendor=051d, idProduct=0002
usb 4-2: new device strings: Mfr=3, Product=1, SerialNumber=2
usb 4-2: Product: Back-UPS RS 500 FW:30.j4.I USB FW:j4
usb 4-2: Manufacturer: American Power Conversion
usb 4-2: SerialNumber: BB0328000279  
usb 4-2: configuration #1 chosen from 1 choice
usb 4-3: new full speed USB device using ohci_hcd and address 3
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
dm-netlink version 0.0.2 loaded
usb 4-3: new device found, idVendor=0a12, idProduct=0001
usb 4-3: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 4-3: configuration #1 chosen from 1 choice
usb 5-1: new low speed USB device using ohci_hcd and address 2
usb 5-1: string descriptor 0 read error: -22
usb 5-1: string descriptor 0 read error: -22
usb 5-1: new device found, idVendor=0bc7, idProduct=0004
usb 5-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-1: configuration #1 chosen from 1 choice
input: ATI/X10 RF USB Remote Control(0bc7,0004) as /class/input/input2
usbcore: registered new driver ati_remote
drivers/usb/input/ati_remote.c: Weird data, len=1 ff 00 00 00 00 00 ...
drivers/usb/input/ati_remote.c: Registered USB driver ATI/X10 RF USB Remote Control v. 2.2.1
loop: loaded (max 8 devices)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ReiserFS: hda6: found reiserfs format "3.6" with standard journal
ReiserFS: hda6: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda6: journal params: device hda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda6: checking transaction log (hda6)
ReiserFS: hda6: Using r5 hash to sort names
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
AppArmor: AppArmor (version 2.0-19.43r6320) initialized
audit(1172471464.465:2): AppArmor (version 2.0-19.43r6320) initialized

ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 17
Bluetooth: Core ver 2.8
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.7
hwmon: module not supported by Novell, setting U taint flag.
hwmon_vid: module not supported by Novell, setting U taint flag.
w83627hf: module not supported by Novell, setting U taint flag.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
powernow-k8: Processor cpuid 644 not supported
powernow: No powernow capabilities detected
u32 classifier
    Perfomance counters on
    Actions configured 
act_police: module not supported by Novell, setting U taint flag.
8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf17dcf00, 00:50:fc:33:ce:ba, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
bootsplash: status on console 0 changed to on
eth0: no IPv6 routers present
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
hdb: 98304kB, 196608 blocks, 512 sector size
 hdb: unknown partition table

[-- Attachment #3: zip-failure-2.6.20.1.txt --]
[-- Type: text/plain, Size: 18807 bytes --]

Linux version 2.6.20.1-default (root@utx) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Thu Feb 22 21:41:49 CET 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000002fef0000 end: 000000002fff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000002fff0000 size: 0000000000008000 end: 000000002fff8000 type: 3
copy_e820_map() start: 000000002fff8000 size: 0000000000008000 end: 0000000030000000 type: 4
copy_e820_map() start: 00000000fff80000 size: 0000000000080000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002fff0000 (usable)
 BIOS-e820: 000000002fff0000 - 000000002fff8000 (ACPI data)
 BIOS-e820: 000000002fff8000 - 0000000030000000 (ACPI NVS)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
767MB LOWMEM available.
Entering add_active_range(0, 0, 196592) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   196592
  HighMem    196592 ->   196592
early_node_map[1] active PFN ranges
    0:        0 ->   196592
On node 0 totalpages: 196592
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 1503 pages used for memmap
  Normal zone: 190993 pages, LIFO batch:31
  HighMem zone: 0 pages used for memmap
DMI 2.3 present.
Using APIC driver default
ACPI: RSDP (v000 AMI                                   ) @ 0x000fc3c0
ACPI: RSDT (v001 AMIINT          0x00000011 MSFT 0x00000097) @ 0x2fff0000
ACPI: FADT (v001 AMIINT          0x00000011 MSFT 0x00000097) @ 0x2fff0030
ACPI: DSDT (v001    VIA   VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 40000000 (gap: 30000000:cff80000)
Detected 1338.228 MHz processor.
Built 1 zonelists.  Total pages: 195057
Kernel command line: root=/dev/hda1 vga=0x31a resume=/dev/hda5 splash=silent
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (0160c000)
Enabling fast FPU save and restore... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 772536k/786368k available (1708k kernel code, 13196k reserved, 719k data, 192k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xffe15000 - 0xfffff000   (1960 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf0800000 - 0xff7fe000   ( 239 MB)
    lowmem  : 0xc0000000 - 0xefff0000   ( 767 MB)
      .init : 0xc0366000 - 0xc0396000   ( 192 kB)
      .data : 0xc02ab3af - 0xc035f354   ( 719 kB)
      .text : 0xc0100000 - 0xc02ab3af   (1708 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2678.89 BogoMIPS (lpj=5357799)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 1c20)
CPU0: AMD Athlon(tm) Processor stepping 04
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 *12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:01.0
  IO window: 8000-9fff
  MEM window: dfe00000-dfefffff
  PREFETCH window: d7c00000-dfcfffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 3190k freed
Machine check exception polling timer started.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1172249290.788:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xd8000000, mapped to 0xf0880000, using 5120k, total 32768k
vesafb: mode is 1280x1024x16, linelength=2560, pages=11
vesafb: protected mode interface info at c000:4d22
vesafb: pmi: set display start = c00c4d90, set palette = c00c4dca
vesafb: pmi: ports = 9810 9816 9854 9838 983c 985c 9800 9804 98b0 98b2 98b4 
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 160x64
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
input: PC Speaker as /class/input/input1
NET: Registered protocol family 1
Using IPI No-Shortcut mode
ACPI: (supports S0 S3 S4 S5)
Freeing unused kernel memory: 192k freed
Time: tsc clocksource has been installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SCSI subsystem initialized
ACPI: Processor [CPU1] (supports 16 throttling states)
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
dc395x: Used settings: AdapterID=07, Speed=0(20.0MHz), dev_mode=0x57
dc395x:                AdaptMode=0x0f, Tags=4(16), DelayReset=1s
dc395x: Connectors:  Termination: Auto Low High 
dc395x: Performing initial SCSI bus reset
scsi0 : Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
VP_IDE: IDE controller at PCI slot 0000:00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: ST3160812A, ATA DISK drive
hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 512KiB
hda: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
Probing IDE interface ide1...
hdc: HL-DT-ST DVDRAM GSA-4160B, ATAPI CD/DVD-ROM drive
hdd: CD-W540E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Attempting manual resume
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]
lp0: using parport0 (interrupt-driven).
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA KT266/KY266x/KT333 chipset
agpgart: AGP aperture is 64M @ 0xe0000000
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ACPI: PCI Interrupt 0000:00:07.2[C] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
ehci_hcd 0000:00:07.2: EHCI Host Controller
ehci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
USB Universal Host Controller Interface driver v3.0
ehci_hcd 0000:00:07.2: irq 10, io mem 0xdfffee00
ehci_hcd 0000:00:07.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
8139too Fast Ethernet driver 0.9.28
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
uhci_hcd 0000:00:11.2: UHCI Host Controller
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:11.2: irq 12, io base 0x0000c800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
NET: Registered protocol family 23
ACPI: PCI Interrupt 0000:00:11.3[D] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
uhci_hcd 0000:00:11.3: UHCI Host Controller
uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:11.3: irq 12, io base 0x0000cc00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ieee80211_crypt: registered algorithm 'NULL'
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf0e90f00, 00:50:fc:33:ce:ba, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
ohci_hcd 0000:00:07.0: OHCI Host Controller
ohci_hcd 0000:00:07.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:07.0: irq 5, io mem 0xdfffc000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 3 ports detected
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
ACPI: PCI Interrupt 0000:00:07.1[B] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
ohci_hcd 0000:00:07.1: OHCI Host Controller
ohci_hcd 0000:00:07.1: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:07.1: irq 12, io mem 0xdfffd000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
es1968: not attempting power management.
hostap_pci: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
es1968: clocking to 48000
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
gameport: NS558 PnP Gameport is pnp00:0a/gameport0, io 0x200, speed 864kHz
usb 3-2: new full speed USB device using uhci_hcd and address 2
hdc: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
usb 3-2: configuration #1 chosen from 1 choice
ide-floppy driver 0.99.newide
usb 4-2: new low speed USB device using ohci_hcd and address 2
prism2_hw_init: initialized in 816 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.0.7
wifi0: STA: id=0x1f v1.3.6
usb 4-2: configuration #1 chosen from 1 choice
usb 4-3: new full speed USB device using ohci_hcd and address 3
wifi0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: Intersil Prism2.5 PCI: mem=0xdfdff000, irq=12
wifi0: registered netdevice wlan0
usb 4-3: configuration #1 chosen from 1 choice
usb 5-1: new low speed USB device using ohci_hcd and address 2
usb 5-1: string descriptor 0 read error: -22
usb 5-1: string descriptor 0 read error: -22
usb 5-1: configuration #1 chosen from 1 choice
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
input: ATI/X10 RF USB Remote Control(0bc7,0004) as /class/input/input2
usbcore: registered new interface driver ati_remote
drivers/usb/input/ati_remote.c: Weird data, len=1 ff 00 00 00 00 00 ...
drivers/usb/input/ati_remote.c: Registered USB driver ATI/X10 RF USB Remote Control v. 2.2.1
usb0: register 'gl620a' at usb-0000:00:11.3-2, Genesys GeneLink, 8e:63:75:81:10:77
usbcore: registered new interface driver gl620a
hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
hdb: No disk in drive
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
Adding 2104472k swap on /dev/hda5.  Priority:-1 extents:1 across:2104472k
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
hdb: No disk in drive
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
loop: loaded (max 8 devices)
ReiserFS: hda6: found reiserfs format "3.6" with standard journal
ReiserFS: hda6: using ordered data mode
ReiserFS: hda6: journal params: device hda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda6: checking transaction log (hda6)
ReiserFS: hda6: Using r5 hash to sort names
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
input: Power Button (FF) as /class/input/input3
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input4
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /class/input/input5
ACPI: Sleep Button (CM) [SLPB]
powernow-k8: Processor cpuid 644 not supported
powernow: No powernow capabilities detected
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 17
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
audit(1172249534.514:2): audit_pid=3590 old=0 by auid=4294967295
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
hdb: No disk in drive
eth0: no IPv6 routers present
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
[drm] Initialized r128 2.5.0 20030725 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
ACPI: PCI interrupt for device 0000:00:06.0 disabled
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xf1328f00, 00:50:fc:33:ce:ba, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
st: Version 20061107, fixed bufsize 32768, s/g segs 256
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
hdb: No disk in drive
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
hdb: lost interrupt
hdb: status error: status=0x00 { }
ide: failed opcode was: unknown
ide-floppy: Strange, packet command initiated yet DRQ isn't asserted
hdb: 98304kB, 196608 blocks, 512 sector size
 hdb: unknown partition table
 hdb: unknown partition table
 hdb: unknown partition table
 hdb: unknown partition table
ip_tables: (C) 2000-2006 Netfilter Core Team