Sadly I needed to change my ASUS CUV4X-D (dual 1ghz) about 9 months
ago... It was running slowly but smoothly.
Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
- My SATA Controller make my Linux crash when connecting a Plextor 716SA
CD-DVD-R (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
- My onboard network card either stops responding (using sk98lin) or
make my PC freeze (using skge)
- My USB mouse goes crazy from times to times (at least every few hours)
until I remove ehci_hcd and uhci_hcd and readd uhci_hcd
- My PC partially wakes up and freeze after a few hours of no usage
Although most of my job is doing Linux system administration and even if
I try to keep myself has informed has I can I still can't get my Linux
working properly (I keep on reading lwn and I subscribed to lkml
recently). I just can't keep my PC running smoothly...
Where should I start from? Is this a good place to ask for help?
Any help appreciated!
- vin
Here are my devices and I also attached my dmesg... just in case:
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge
[K8T800/K8T890 South] 00:07.0 FireWire (IEEE 1394): VIA Technologies,
Inc. IEEE 1394 Host Controller (rev 80) 00:0a.0 Ethernet controller:
Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev
13) 00:0d.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet
Pro 100] (rev 01) 00:0f.0 RAID bus controller: VIA Technologies, Inc.
VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0
USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
(rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0
ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge
[KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem
Controller (rev 80) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control 01:00.0 VGA compatible controller: nVidia
Corporation NV40 [GeForce 6800] (rev a1)
On Mon, May 15, 2006 at 08:05:17AM -0400, Fortier,Vincent [Montreal] wrote:
> nvidia: module license 'NVIDIA' taints kernel.
Do any of these problems happen without the nvidia driver loaded? If
so, please send us the logs for that.
thanks,
greg k-h
> > nvidia: module license 'NVIDIA' taints kernel.
>
> Do any of these problems happen without the nvidia driver
> loaded? If so, please send us the logs for that.
>
I'll give it a try tonight using the nv driver instead...
I will also let a memtest running all night to make sure memory is not
involved in any of the other problems I have.
Thnx
- vin
> I also have A8V Deluxe.
>
> No real problems with single core A64 3000.
>
> But now with and X2 dual core CPU, I needed to disable
> irqbalance to get any stability.
Hein? Via xconfig?
> (also look at tsc vs pmtmr if you have any problems with clock).
What is tsc vs pmtmr
Thnx!
- vin
"Fortier,Vincent [Montreal]" <[email protected]> writes:
> > I also have A8V Deluxe.
> >
> > No real problems with single core A64 3000.
> >
> > But now with and X2 dual core CPU, I needed to disable
> > irqbalance to get any stability.
>
> Hein? Via xconfig?
I cant't see the parent message (did you mess up the cc?) of the
person with irqbalanced troubles, but most likely he has a SIS chipset, right?
-Andi
Andi Kleen wrote:
> "Fortier,Vincent [Montreal]" <[email protected]> writes:
>
>>> I also have A8V Deluxe.
>>>
>>> No real problems with single core A64 3000.
>>>
>>> But now with and X2 dual core CPU, I needed to disable
>>> irqbalance to get any stability.
>> Hein? Via xconfig?
>
> I cant't see the parent message (did you mess up the cc?) of the
> person with irqbalanced troubles, but most likely he has a SIS chipset, right?
No, VIA A8V Deluxe.
See for example:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182618
Regards,
Mark
On Monday 15 May 2006 21:23, Marko Macek wrote:
> Andi Kleen wrote:
> > "Fortier,Vincent [Montreal]" <[email protected]> writes:
> >
> >>> I also have A8V Deluxe.
> >>>
> >>> No real problems with single core A64 3000.
> >>>
> >>> But now with and X2 dual core CPU, I needed to disable
> >>> irqbalance to get any stability.
> >> Hein? Via xconfig?
> >
> > I cant't see the parent message (did you mess up the cc?) of the
> > person with irqbalanced troubles, but most likely he has a SIS chipset, right?
>
> No, VIA A8V Deluxe.
>
> See for example:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182618
Ok, that's new. We knew that SIS didn't like setting interrupt
affinity on IRQ 0. Maybe VIA forgot to validate one of these cases too.
On SUSE it was workarounded in irqbalanced user space but since other
distributions seem to be lazy to pick that fix up we should probably
do a kernel side fix. I'll put it on my todo list.
-Andi
> > Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
> >
> > - My SATA Controller make my Linux crash when connecting a
> > Plextor 716SA CD-DVD-R
> > (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
> Patch:
>
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.17-rc4-
git2-libata1.patch.bz2
> (diff'd against 2.6.17-rc4-git2, but should apply to most recent
2.6.17-rcX[-gitY] kernels)
I gave a try at the latest ata patches announced yesterday by Jeff and
it completelly solved my SATA ATAPI bug.. I even been able to burn my
first DVD using my Plextor 716SA on my Linux!!! Really nice and much
anticipated work! Thnx a lot!
I have already marked bug 5533 as resolved and I'll wait until inclusion
into 2.6.18 to close it. I've also marked bug 6317 has closed since
that did not occur since around rc2 or rc3 of 2.6.17.
I also ran a memtest86+ all night to make sure there where no problems
with my memory... And everything is fine so no problems there.
> "Fortier,Vincent [Montreal]" <[email protected]> writes:
> - My onboard network card either stops responding (using
> sk98lin) or make my PC freeze (using skge)
> - My USB mouse goes crazy from times to times (at least every
> few hours) until I remove ehci_hcd and uhci_hcd and readd uhci_hcd
> - My PC partially wakes up and freeze after a few hours of no usage
> On Monday 15 May 2006 21:23, Marko Macek wrote:
> > Andi Kleen wrote:
> > > "Fortier,Vincent [Montreal]" <[email protected]> writes:
> > >>> I also have A8V Deluxe.
> > >>> No real problems with single core A64 3000.
> > >>> But now with and X2 dual core CPU, I needed to disable
irqbalance
> > >>> to get any stability.
> > See for example:
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182618
Wow.. This exactly resume all my other BUGS I have... And they where
quite hard to find actually... Thnx for the info. I'll disable
irqbalance tonight for sure until there is a final fix into the kernel.
> Ok, that's new. We knew that SIS didn't like setting
> interrupt affinity on IRQ 0. Maybe VIA forgot to validate one
> of these cases too.
> we should probably do a kernel side fix. I'll put it on my todo list.
Thnx.. Would be really appreciated... And just ask if you need a tester!
Thanks to all of you!
- vin
Fortier,Vincent [Montreal] wrote:
>>> Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
>>>
>>> - My SATA Controller make my Linux crash when connecting a
>>> Plextor 716SA CD-DVD-R
>>> (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
>
>> Patch:
>>
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.17-rc4-
> git2-libata1.patch.bz2
>> (diff'd against 2.6.17-rc4-git2, but should apply to most recent
> 2.6.17-rcX[-gitY] kernels)
>
> I gave a try at the latest ata patches announced yesterday by Jeff and
> it completelly solved my SATA ATAPI bug.. I even been able to burn my
> first DVD using my Plextor 716SA on my Linux!!! Really nice and much
> anticipated work! Thnx a lot!
>
> I have already marked bug 5533 as resolved and I'll wait until inclusion
> into 2.6.18 to close it. I've also marked bug 6317 has closed since
> that did not occur since around rc2 or rc3 of 2.6.17.
>
Jeff, do you know what fixed this one? I've been following the bug and
thought it was one of those via-ATAPI-have-no-idea bugs. How come the
update fix this one? Have I missed something?
--
tejun
Tejun Heo wrote:
> Fortier,Vincent [Montreal] wrote:
>
>>>> Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
>>>>
>>>> - My SATA Controller make my Linux crash when connecting a Plextor
>>>> 716SA CD-DVD-R (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
>>
>>
>>> Patch:
>>>
>> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.17-rc4-
>> git2-libata1.patch.bz2
>>
>>> (diff'd against 2.6.17-rc4-git2, but should apply to most recent
>>
>> 2.6.17-rcX[-gitY] kernels)
>>
>> I gave a try at the latest ata patches announced yesterday by Jeff and
>> it completelly solved my SATA ATAPI bug.. I even been able to burn my
>> first DVD using my Plextor 716SA on my Linux!!! Really nice and much
>> anticipated work! Thnx a lot!
>>
>> I have already marked bug 5533 as resolved and I'll wait until inclusion
>> into 2.6.18 to close it. I've also marked bug 6317 has closed since
>> that did not occur since around rc2 or rc3 of 2.6.17.
>>
>
> Jeff, do you know what fixed this one? I've been following the bug and
> thought it was one of those via-ATAPI-have-no-idea bugs. How come the
> update fix this one? Have I missed something?
>
I'm also curious how the svia-atapi problem got fixed.
Reinhard has a Plextor PX-712SA + svia.
Maybe he can also help to check whether the patch fixes the problem on his box.
--
albert
Albert Lee wrote:
> Tejun Heo wrote:
>> Fortier,Vincent [Montreal] wrote:
>>
>>>>> Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
>>>>>
>>>>> - My SATA Controller make my Linux crash when connecting a Plextor
>>>>> 716SA CD-DVD-R (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
>>>
>>>> Patch:
>>>>
>>> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.17-rc4-
>>> git2-libata1.patch.bz2
>>>
>>>> (diff'd against 2.6.17-rc4-git2, but should apply to most recent
>>> 2.6.17-rcX[-gitY] kernels)
>>>
>>> I gave a try at the latest ata patches announced yesterday by Jeff and
>>> it completelly solved my SATA ATAPI bug.. I even been able to burn my
>>> first DVD using my Plextor 716SA on my Linux!!! Really nice and much
>>> anticipated work! Thnx a lot!
>>>
>>> I have already marked bug 5533 as resolved and I'll wait until inclusion
>>> into 2.6.18 to close it. I've also marked bug 6317 has closed since
>>> that did not occur since around rc2 or rc3 of 2.6.17.
>>>
>> Jeff, do you know what fixed this one? I've been following the bug and
>> thought it was one of those via-ATAPI-have-no-idea bugs. How come the
>> update fix this one? Have I missed something?
>>
>
> I'm also curious how the svia-atapi problem got fixed.
This is funny. I thought you would know. We're just a bunch of
clueless people, aren't we? :-)
Fortier, can you please post full boot dmesg?
--
tejun
Tejun Heo wrote:
> Fortier,Vincent [Montreal] wrote:
>>>> Now I'm having an ASUS A8V Deluxe.... and sadly a lot of problems:
>>>>
>>>> - My SATA Controller make my Linux crash when connecting a Plextor
>>>> 716SA CD-DVD-R (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
>>
>>> Patch:
>>>
>> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.17-rc4-
>> git2-libata1.patch.bz2
>>> (diff'd against 2.6.17-rc4-git2, but should apply to most recent
>> 2.6.17-rcX[-gitY] kernels)
>>
>> I gave a try at the latest ata patches announced yesterday by Jeff and
>> it completelly solved my SATA ATAPI bug.. I even been able to burn my
>> first DVD using my Plextor 716SA on my Linux!!! Really nice and much
>> anticipated work! Thnx a lot!
>>
>> I have already marked bug 5533 as resolved and I'll wait until inclusion
>> into 2.6.18 to close it. I've also marked bug 6317 has closed since
>> that did not occur since around rc2 or rc3 of 2.6.17.
>>
>
> Jeff, do you know what fixed this one? I've been following the bug and
> thought it was one of those via-ATAPI-have-no-idea bugs. How come the
> update fix this one? Have I missed something?
No idea :)
Though this update should solve several classes of longstanding bugs.
* irq-pio is much friendlier to the controller, and should eliminate
several screaming interrupt problems, particularly on sata_sil.
* The better EH should allow recovery from problems we couldn't recover
from before.
* The removal of assert()s (or, removal of conditions that caused
asserts) that triggered in earlier kernels will also eliminate the
associated forced oopsen.
But in the via+ATAPI case, the only thing I can think of is that VIA
AHCI support is included in the update. Other than that... <shrug>
Jeff
> But in the via+ATAPI case, the only thing I can think of is
> that VIA AHCI support is included in the update. Other than
> that... <shrug>
For the sake of understanding what patch fixed this would you like me to
test individual patches or is it useless?
- vin
> Fortier, can you please post full boot dmesg?
Sure.. Tonight when I`ll come back home.
BTW, you can use vincent instead :)
Fortier,Vincent [Montreal] wrote:
>> Fortier, can you please post full boot dmesg?
>
> Sure.. Tonight when I`ll come back home.
>
> BTW, you can use vincent instead :)
>
Yeap, Vincent. :-)
As bisecting patches is painful, let's postpone it until it can't be
anymore. If the boot log doesn't show much, I think I can insert codes
disabling some of the new features such that full bisecting isn't necessary.
--
tejun
> >> Fortier, can you please post full boot dmesg?
> As bisecting patches is painful, let's postpone it until it
> can't be anymore. If the boot log doesn't show much, I think
> I can insert codes disabling some of the new features such
> that full bisecting isn't necessary.
Here is my dmesg... I also tought of taking a screenshot of k3b in a burning process but letf it home :)
Anyhow, if you need me to run a few tests to find out exactly where/how/what made ATAPI work correctly on sata_via just ask.
Also note that I disabled irqbalance and switch back to my onboard nic using skge yesterday night and it did solved all my other problems (jerky mouse, lan dropping, PC freezing, etc.). I presume that using sk98lin would work also. A fix for that would solve many problems on K8T800 chipsets.
- vin
Here is the most interesting part which does not say much more than it used to... except that it does detect it properly:
libata version 1.30 loaded.
sata_via 0000:00:0f.0: version 1.2
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16
sata_via 0000:00:0f.0: routed to hard irq line 10
ata1: SATA max UDMA/133 cmd 0xD000 ctl 0xC802 bmdma 0xB800 irq 16
ata2: SATA max UDMA/133 cmd 0xC400 ctl 0xC002 bmdma 0xB808 irq 16
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c69 86:3e01 87:4663 88:407f
ata1.00: ATA-7, max UDMA/133, 490234752 sectors: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
scsi0 : sata_via
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:001f
ata2.00: ATAPI, max UDMA/66
ata2.00: applying bridge limits
ata2.00: configured for UDMA/66
scsi1 : sata_via
Vendor: ATA Model: Maxtor 6B250S0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 >
sd 0:0:0:0: Attached scsi disk sda
Vendor: PLEXTOR Model: DVDR PX-716A Rev: 1.09
Type: CD-ROM ANSI SCSI revision: 05
Fortier,Vincent [Montreal] wrote:
> scsi0 : sata_via
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2.00: cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:001f
> ata2.00: ATAPI, max UDMA/66
> ata2.00: applying bridge limits
> ata2.00: configured for UDMA/66
[--snip--]
> sd 0:0:0:0: Attached scsi disk sda
> Vendor: PLEXTOR Model: DVDR PX-716A Rev: 1.09
> Type: CD-ROM ANSI SCSI revision: 05
Above and the detailed log too indicate that everything went smooth the
first time around. Albert, do you have any ideas? Could it be
something related to irq-pio?
--
tejun
Tejun Heo wrote:
> Fortier,Vincent [Montreal] wrote:
>
>> scsi0 : sata_via
>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata2.00: cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000
>> 88:001f
>> ata2.00: ATAPI, max UDMA/66
>> ata2.00: applying bridge limits
>> ata2.00: configured for UDMA/66
>
> [--snip--]
>
>> sd 0:0:0:0: Attached scsi disk sda
>> Vendor: PLEXTOR Model: DVDR PX-716A Rev: 1.09
>> Type: CD-ROM ANSI SCSI revision: 05
>
>
> Above and the detailed log too indicate that everything went smooth the
> first time around. Albert, do you have any ideas? Could it be
> something related to irq-pio?
>
I've checked Vincent't dmesg for 2.6.17-rc0 again.
(http://bugzilla.kernel.org/show_bug.cgi?id=5533)
(http://bugzilla.kernel.org/attachment.cgi?id=7700&action=view)
It seems DMA commands are also affected by this problem, not PIO unique.
ata2: command 0xa0 timeout, stat 0xd0 host_stat 0x1 <==== Device busy. DMA on going.
ata2: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
sr0: scsi-1 drive
sr 1:0:0:0: Attached scsi CD-ROM sr0
ata2 is slow to respond, please be patient
ata2 failed to respond (30 secs)
BUG: warning at drivers/scsi/libata-core.c:3303/ata_pio_complete()
Call Trace: <ffffffff88031bd0>{:libata:ata_pio_task+1398}
<ffffffff810298cf>{__wake_up+56} <ffffffff81219b3a>{_spin_unlock_irqrestore+11}
<ffffffff8803165a>{:libata:ata_pio_task+0} <ffffffff8103f2ed>{run_workqueue+159}
<ffffffff8103fcd0>{worker_thread+0} <ffffffff8104265f>{keventd_create_kthread+0}
<ffffffff8103fdd9>{worker_thread+265} <ffffffff8102880b>{default_wake_function+0}
<ffffffff8104265f>{keventd_create_kthread+0} <ffffffff8104265f>{keventd_create_kthread+0}
<ffffffff81042964>{kthread+212} <ffffffff8100a7a6>{child_rip+8}
<ffffffff8104265f>{keventd_create_kthread+0} <ffffffff81218504>{thread_return+0}
<ffffffff81042890>{kthread+0} <ffffffff8100a79e>{child_rip+0}
ata2: command 0xa0 timeout, stat 0xd0 host_stat 0x0 <==== Device busy, PIO.
ata2: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
=> It looks like the device is waiting for something.
After comparing the code of 2.6.17-rc4 and current libata upstream, maybe "flush" is the fix:
The CDB was sent to the ATAPI device by PIO, but not flushed to device.
So, the device was busy waiting for the CDB to arrive.
Hi Vincent,
Could you please try 2.6.17-rc4, both with and without the attached patch,
to see if the flush works. Thanks.
--
albert
--- linux-2.6.17-rc4/drivers/scsi/libata-core.c 2006-05-18 12:59:23.000000000 +0800
+++ linux-2.6.17-rc4-mod/drivers/scsi/libata-core.c 2006-05-18 13:04:11.000000000 +0800
@@ -3638,6 +3638,8 @@ static void ata_pio_block(struct ata_por
ata_pio_sector(qc);
}
+
+ ata_altstatus(ap); /* flush */
}
static void ata_pio_error(struct ata_port *ap)
@@ -3754,11 +3756,14 @@ static void atapi_packet_task(void *_dat
spin_lock_irqsave(&ap->host_set->lock, flags);
ap->flags &= ~ATA_FLAG_NOINTR;
ata_data_xfer(ap, qc->cdb, qc->dev->cdb_len, 1);
+ ata_altstatus(ap); /* flush */
+
if (qc->tf.protocol == ATA_PROT_ATAPI_DMA)
ap->ops->bmdma_start(qc); /* initiate bmdma */
spin_unlock_irqrestore(&ap->host_set->lock, flags);
} else {
ata_data_xfer(ap, qc->cdb, qc->dev->cdb_len, 1);
+ ata_altstatus(ap); /* flush */
/* PIO commands are handled by polling */
ap->hsm_task_state = HSM_ST;
> >> sd 0:0:0:0: Attached scsi disk sda
> >> Vendor: PLEXTOR Model: DVDR PX-716A Rev: 1.09
> >> Type: CD-ROM ANSI SCSI revision: 05
> >
> > Above and the detailed log too indicate that everything went smooth
> > the first time around. Albert, do you have any ideas? Could it be
> > something related to irq-pio?
You cannot image how happy I was :)
> I've checked Vincent't dmesg for 2.6.17-rc0 again.
> (http://bugzilla.kernel.org/show_bug.cgi?id=5533)
> (http://bugzilla.kernel.org/attachment.cgi?id=7700&action=view)
>
> It seems DMA commands are also affected by this problem, not
> PIO unique.
> After comparing the code of 2.6.17-rc4 and current libata
> upstream, maybe "flush" is the fix:
> The CDB was sent to the ATAPI device by PIO, but not flushed
> to device.
> So, the device was busy waiting for the CDB to arrive.
> Hi Vincent,
> Could you please try 2.6.17-rc4, both with and without the
> attached patch, to see if the flush works. Thanks.
On a pure 2.6.17-rc4 without upstream libata patches I presume? Sure I will tonight.
I'll forward this patch to my home email address and come back to you.
- vin
Fortier,Vincent [Montreal] wrote:
>
>
>>Hi Vincent,
>> Could you please try 2.6.17-rc4, both with and without the
>>attached patch, to see if the flush works. Thanks.
>
>
> On a pure 2.6.17-rc4 without upstream libata patches I presume? Sure I will tonight.
> I'll forward this patch to my home email address and come back to you.
>
Yes, pure 2.6.17-rc4 without upstream libata patches. Thanks.
-- albert
Hi, I have the latest libata stuff from git as of a couple days ago and all
appeared to be working, my Plextor PX716-SA appeared to be detected, and I could
read from it fine. But if I burn CDs, no matter what I do, burnfree on, burnfree
off, 4x, I get corruption, with either total coasters or readable filesystems
with md5s that are all off. I'm not sure what I could possibly be doing wrong, I
know it shouldn't be this difficult to write a CD. I also have a Asus A8V.
Here's some cdrecord output, I do notice some things which may or may not be as
bad as they look:
cdrecord stderr: cdrecord: Warning: Running on Linux-2.6.17-rc4-floam1
cdrecord stderr: cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord stderr: cdrecord: If you have unexpected problems, please try Linux-2.4
or Solaris.
cdrecord stderr: scsidev: '/dev/scd0'
cdrecord stderr: devname: '/dev/scd0'
cdrecord stderr: scsibus: -2 target: -2 lun: -2
cdrecord stderr: Warning: Open by 'devname' is unintentional and not supported.
cdrecord stderr: Linux sg driver version: 3.5.27
cdrecord stderr: cdrecord: Warning: using inofficial version of libscg (debian-0
.8debian2 '@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J. S
chilling').
cdrecord stderr: SCSI buffer size: 64512
cdrecord stderr: cdrecord: This version of cdrecord does not include DVD-R/DVD-R
W support code.
cdrecord stderr: cdrecord: See /usr/share/doc/cdrecord/README.DVD.Debian for det
ails on DVD support.
cdrecord stdout: Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 199
5-2004 Joerg Schilling
cdrecord stdout: NOTE: this version of cdrecord is an inofficial (modified) rele
ase of cdrecord
cdrecord stdout: and thus may have bugs that are not present in the origin
al version.
cdrecord stdout: Please send bug reports and support requests to <cdrtools
@packages.debian.org>.
cdrecord stdout: The original author should not be bothered with problems
of this version.
cdrecord stdout:
cdrecord stdout: TOC Type: 1 = CD-ROM
cdrecord stdout: Using libscg version 'debian-0.8debian2'.
cdrecord stdout: Driveropts: 'burnfree'
cdrecord stdout: atapi: 1
cdrecord stdout: Device type : Removable CD-ROM
cdrecord stdout: Version : 5
cdrecord stdout: Response Format: 2
cdrecord stdout: Capabilities :
cdrecord stdout: Vendor_info : 'PLEXTOR '
cdrecord stdout: Identifikation : 'DVDR PX-716A '
cdrecord stdout: Revision : '1.08'
cdrecord stdout: Device seems to be: Generic mmc2 DVD-R/DVD-RW.
cdrecord stdout: Current: 0x0009
cdrecord stdout: Profile: 0x002B
cdrecord stdout: Profile: 0x001B
cdrecord stdout: Profile: 0x001A
cdrecord stdout: Profile: 0x0015
cdrecord stdout: Profile: 0x0014
cdrecord stdout: Profile: 0x0013
cdrecord stdout: Profile: 0x0011
cdrecord stdout: Profile: 0x0010
cdrecord stdout: Profile: 0x000A
cdrecord stdout: Profile: 0x0009 (current)
cdrecord stdout: Profile: 0x0008
cdrecord stdout: Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
cdrecord stdout: Driver flags : MMC-3 SWABAUDIO BURNFREE VARIREC GIGAREC FORCE
SPEED SPEEDREAD SINGLESESSION HIDECDR
cdrecord stdout: Supported modes: TAO SAO SAO/R96P SAO/R96R RAW/R96R
cdrecord stdout: Drive buf size : 4802784 = 4690 KB
cdrecord stdout: Drive DMA Speed: 22958 kB/s 130x CD 16x DVD
cdrecord stdout: FIFO size : 16777216 = 16384 KB
cdrecord stdout: Track 01: data 100 MB
cdrecord stdout: Total size: 115 MB (11:25.48) = 51411 sectors
cdrecord stdout: Lout start: 115 MB (11:27/36) = 51411 sectors
cdrecord stdout: Current Secsize: 2048
cdrecord stdout: ATIP info from disk:
cdrecord stdout: Indicated writing power: 4
cdrecord stdout: Is not unrestricted
cdrecord stdout: Is not erasable
cdrecord stdout: Disk sub type: Medium Type A, low Beta category (A-) (2)
cdrecord stdout: ATIP start of lead in: -12508 (97:15/17)
cdrecord stdout: ATIP start of lead out: 359845 (79:59/70)
cdrecord stdout: Disk type: Short strategy type (Phthalocyanine or similar)
cdrecord stdout: Manuf. index: 22
cdrecord stdout: Manufacturer: Ritek Co.
cdrecord stdout: Single session is OFF.
cdrecord stdout: Hide CDR is OFF.
cdrecord stdout: Speed-Read is OFF.
cdrecord stdout: GigaRec is off.
cdrecord stdout: Blocks total: 359845 Blocks current: 359845 Blocks remaining: 3
08434
cdrecord stdout: Forcespeed is OFF.
cdrecord stdout: Power-Rec is ON.
cdrecord stdout: Power-Rec write speed: 48x (recommended)
cdrecord stdout: Starting to write CD/DVD at speed 16 in real SAO mode for singl
e session.
cdrecord stdout: Last chance to quit, starting real write 0 seconds.
Operation starts.
cdrecord stderr: cdrecord: Input/output error. mode select g1: scsi sendcmd: no
error
cdrecord stdout: Waiting for reader process to fill input buffer ... input
buffer ready.
cdrecord stderr: CDB: 55 10 00 00 00 00 00 00 3C 00
cdrecord stdout: BURN-Free is ON.
cdrecord stderr: status: 0x2 (CHECK CONDITION)
cdrecord stdout: Performing OPC...
cdrecord stderr: Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 26 00 00 00
cdrecord stderr: Sense Key: 0x5 Illegal Request, Segment 0
cdrecord stderr: Sense Code: 0x26 Qual 0x00 (invalid field in parameter list)
Fru 0x0
cdrecord stderr: Sense flags: Blk 0 (not valid)
cdrecord stderr: resid: 60
cdrecord stderr: cmd finished after 0.000s timeout 200s
cdrecord stderr: cdrecord: Warning: using default CD write parameter data.
cdrecord stderr: Mode Select Data 00 10 00 00 05 32 41 04 08 10 00 00 00 00 00
00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
cdrecord stderr: cdrecord: Cannot set up 2nd set of driver options.
cdrecord stdout: Sending CUE sheet...
cdrecord stdout: Writing pregap for track 1 at -150
cdrecord stdout: Starting new track at sector: 0
cdrecord stdout: Track 01: 100 of 100 MB written (fifo 100%) [buf 99%] 16.9x.
cdrecord stdout: Track 01: Total bytes read/written: 105289728/105289728 (51411
sectors).
cdrecord stdout: Writing time: 64.725s
cdrecord stdout: Average write speed 12.7x.
cdrecord stdout: Min drive buffer fill was 99%
cdrecord stdout: Fixating...
cdrecord stdout: Fixating time: 7.316s
cdrecord stdout: Last selected write speed: 16x
cdrecord stderr: cdrecord: fifo had 1659 puts and 1659 gets.
cdrecord stdout: Max media write speed: 48x
cdrecord stderr: cdrecord: fifo was 0 times empty and 1403 times full, min fill
was 99%.
cdrecord stdout: Last actual write speed: 16x