New libata PATA patch for 2.6.16-rc1
Available from
http://zeniv.linux.org.uk/~alan/IDE/
Main changes:
Various drivers moved to use SRST
Probe code now knows about 0xFF return due to missing pulldowns
on cheap controllers
HPT37x masking bug fixed
Try to issue LBA28 commands whenever possible
Above should fix ALi speed problems
VIA ATAPI now works for me
IT8212 prints raid data
Fix IT8212 sector clamping
Report aborted command for unknown errors
Fix HPT371 crash on probe
Quoted 4 lines · Alan Cox
Available from
Alan, I've been using your patchset for a while on a small-memory machine with an AMD IDE controller, so that the legacy PATA port can be used to run an optical drive without bloating the vmlinux size with ide-* (already have SCSI built in for usb-storage and SATA). I've not had a single problem to date.
What's your merge plan for the 'complete' drivers? Is it reasonable to merge some drivers but not others? (I'm ignorant to your core libata changes, I've not yet had a chance to read the patch.)
Signature · 6 lines
Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 10 lines · Alistair John Strachan
Quoted 3 lines · Alan Cox
Available from
Alan, I've been using your patchset for a while on a small-memory machine with an AMD IDE controller, so that the legacy PATA port can be used to run an optical drive without bloating the vmlinux size with ide-* (already have SCSI built in for usb-storage and SATA). I've not had a single problem to date.
However, I just tried the same driver on my desktop PC (4xSATA HDs, 1xPATA) and I get the following periodically (when the PATA device is NOT being used):
ata1: irq trap
ata1: command 0x25 timeout, stat 0x50 host_stat 0x20
ata2: irq trap
ata2: command 0xca timeout, stat 0x50 host_stat 0x20
ata4: irq trap
ata4: irq trap
ata4: irq trap
ata4: irq trap
ata4: command 0xc8 timeout, stat 0x50 host_stat 0x20
ata1-4 are the HDs, ata5 is the PATA device (it does not trigger).
This could however be some bug in 2.6.16-rc6, the last kernel on this box with 2.6.16-rc4 without your IDE patches.
Any ideas?
Signature · 6 lines
Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 5 lines · Alistair John Strachan
However, I just tried the same driver on my desktop PC (4xSATA HDs, 1xPATA) and I get the following periodically (when the PATA device is NOT being used):
Can you try the vanilla rc6 kernel to check, and if it does it then let Jeff Garzik known ASAP - especially if rc4 was ok.
Quoted 1 line
ata1: irq trap
Quoted 9 lines · Alan Cox
Quoted 3 lines · Alistair John Strachan
However, I just tried the same driver on my desktop PC (4xSATA HDs, 1xPATA) and I get the following periodically (when the PATA device is NOT being used):
Can you try the vanilla rc6 kernel to check, and if it does it then let Jeff Garzik known ASAP - especially if rc4 was ok.
Quoted 1 line
ata1: irq trap
No such error without your patch on this machine. I've got a RAID5 spanning four SATA drives on a dual core Athlon 64, and it'll happily do 185MB/s to /dev/null with the command:
for FILE in *; do dd if="$FILE" of=/dev/null bs=1M; done
300,000 interrupts later, still no messages. Anything I can do to isolate this further?
Signature · 6 lines
Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 8 lines · Alistair John Strachan
Quoted 7 lines · Alan Cox
Quoted 3 lines · Alistair John Strachan
However, I just tried the same driver on my desktop PC (4xSATA HDs, 1xPATA) and I get the following periodically (when the PATA device is NOT being used):
Can you try the vanilla rc6 kernel to check, and if it does it then let Jeff Garzik known ASAP - especially if rc4 was ok.
Quoted 8 lines
Quoted 1 line
Quoted 1 line
ata1: irq trap
No such error without your patch on this machine. I've got a RAID5 spanning four SATA drives on a dual core Athlon 64, and it'll happily do 185MB/s to
/dev/nullwith the command:for FILE in *; do dd if="$FILE" of=/dev/null bs=1M; done
300,000 interrupts later, still no messages. Anything I can do to isolate this further?
I'd like to second this. On -rc5-ide{1,2} I didn't have any trouble, but now on -rc6-ide1 I keep getting the messages on all 4 of my SATA drives (2 on sata_via, 2 on sata_sil). I haven't tried with vanilla -rc6 but let me know if that can help.
HTH,
Chris
Signature · 3 lines
Chris Boot [email protected] http://www.bootc.net/
Quoted 4 lines · Alistair John Strachan
for FILE in *; do dd if="$FILE" of=/dev/null bs=1M; done
300,000 interrupts later, still no messages. Anything I can do to isolate this further?
I left the IRQ trap code define enabled in the tree when I did the diff. Ok thats that one explained
Quoted 7 lines · Alan Cox
Quoted 3 lines · Alistair John Strachan
for FILE in *; do dd if="$FILE" of=/dev/null bs=1M; done
300,000 interrupts later, still no messages. Anything I can do to isolate this further?
I left the IRQ trap code define enabled in the tree when I did the diff. Ok thats that one explained
Would this cause hangs? I seem to get hangs on SATA I/O occasionally (not PATA) which coincide with those IRQ trap messages.
Signature · 3 lines
Chris Boot [email protected] http://www.bootc.net/
Hi Alan,
Le Mon, 13 Mar 2006 15:07:10 +0000, Alan Cox a écrit :
Quoted 5 lines
Available from
http://zeniv.linux.org.uk/~alan/IDE/
VIA ATAPI now works for me
It still doesn't work for me [1].
May be it has something to do with the lost interrupt I described in my previous mail.
I will try ata_piix in order to see if all PATA device are seen.
Matthieu
[1]
Linux version 2.6.16-rc6 (root@mat-pc) (gcc version 4.1.0 20060219 (prerelease) (Debian 4.1-0exp9)) #11 PREEMPT Mon Mar 13 21:13:11 CET 2006 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
BIOS-e820: 000000003fff0000 - 000000003fff8000 (ACPI data)
BIOS-e820: 000000003fff8000 - 0000000040000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000fb940
On node 0 totalpages: 262128
DMA zone: 4096 pages, LIFO batch:0
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 225280 pages, LIFO batch:31
HighMem zone: 32752 pages, LIFO batch:7
DMI 2.3 present.
ACPI: RSDP (v000 AMI ) @ 0x000fa8e0
ACPI: RSDT (v001 AMIINT VIA_K7 0x00000010 MSFT 0x00000097) @ 0x3fff0000
ACPI: FADT (v001 AMIINT VIA_K7 0x00000011 MSFT 0x00000097) @ 0x3fff0030
ACPI: MADT (v001 AMIINT VIA_K7 0x00000009 MSFT 0x00000097) @ 0x3fff00c0
ACPI: DSDT (v001 VIA VIA_K7 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:6 APIC version 16
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Built 1 zonelists
Kernel command line: root=/dev/sdc3 ro ide=reverse init=/bin/sh
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 1533.562 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1036440k/1048512k available (1559k kernel code, 11480k reserved, 532k data, 136k init, 131008k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3071.81 BogoMIPS (lpj=6143635)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1c3fbff 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: 0383fbff c1c3fbff 00000000 00000020 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 1800+ stepping 02
Checking 'hlt' instruction... OK.
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfdaf1, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 0800-087f claimed by vt8235 PM
PCI quirk: region 0400-040f claimed by vt8235 SMB
PCI: Ignoring BAR0-3 of IDE controller 0000:00:11.1
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 13 devices
PnPBIOS: Disabled by ACPI PNP
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
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: disabled.
MEM window: ddd00000-dfdfffff
PREFETCH window: cda00000-ddbfffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
Machine check exception polling timer started.
highmem bounce pool size: 64 pages
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
libata version 1.20 loaded.pata_sil680 0000:00:07.0: version 0.2.1
sil680: BA5_EN = 1 clock = 00
sil680: BA5_EN = 1 clock = 10
sil680: 133MHz clock.
ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 18 (level, low) -> IRQ 16
ata1: PATA max UDMA/133 cmd 0xE800 ctl 0xE402 bmdma 0xD800 irq 16
ata2: PATA max UDMA/133 cmd 0xE000 ctl 0xDC02 bmdma 0xD808 irq 16
ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3e01 87:4003 88:007f
ata1: dev 0 ATA-7, max UDMA/133, 156368016 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : pata_sil680
ATA: abnormal status 0x7F on port 0xE007
ata2: disabling port
scsi1 : pata_sil680
Vendor: ATA Model: SAMSUNG SP0802N Rev: TK10
Type: Direct-Access ANSI SCSI revision: 05pata_via 0000:00:11.1: version 0.1.6
ACPI: PCI Interrupt 0000:00:11.1[A]: no GSI
PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 15
ata3: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xFC00 irq 14via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10
FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9
ata3: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3c01 87:4003 88:203f
ata3: dev 0 ATA-7, max UDMA/100, 156368016 sectors: LBA48via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10
FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9
ata3: dev 1 cfg 49:2f00 82:74eb 83:5bea 84:4000 85:7469 86:1a02 87:4003 88:203f
ata3: dev 1 ATA-5, max UDMA/100, 80418240 sectors: LBAvia_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 3, t.recover = 1
FIT t.act8b = 10, t.rec8b = 8, t.active = 2, t.recover = 0via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 3, t.recover = 1
FIT t.act8b = 10, t.rec8b = 8, t.active = 2, t.recover = 0
ata3: dev 0 configured for UDMA/33via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1
FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1
FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0
ata3: dev 1 configured for UDMA/33
scsi2 : pata_via
Vendor: ATA Model: SAMSUNG SP0802N Rev: TK10 Type: Direct-Access ANSI SCSI revision: 05 Vendor: ATA Model: IC35L040AVVA07-0 Rev: VA2O Type: Direct-Access ANSI SCSI revision: 05
ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFC08 irq 15via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10
FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9
ata4: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407
ata4: dev 0 ATAPI, max UDMA/33via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10
FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9
ata4: dev 1 cfg 49:0b00 82:0210 83:1000 84:0000 85:0000 86:0000 87:0000 88:0407
ata4: dev 1 ATAPI, max UDMA/33via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 3, t.recover = 1
FIT t.act8b = 10, t.rec8b = 8, t.active = 2, t.recover = 0via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
t.act8b = 11, t.rec8b = 9, t.active = 3, t.recover = 1
FIT t.act8b = 10, t.rec8b = 8, t.active = 2, t.recover = 0
ata4: dev 0 configured for UDMA/33via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1
FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1
FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0
ata4: qc timeout (cmd 0xef)
ata4: failed to set xfermode, disabled
ata4: dev 1 configured for UDMA/33
scsi3 : pata_via
SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156368016 512-byte hdwr sectors (80060 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 156368016 512-byte hdwr sectors (80060 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 156368016 512-byte hdwr sectors (80060 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2 < sdb5 >
sd 2:0:0:0: Attached scsi disk sdb
SCSI device sdc: 80418240 512-byte hdwr sectors (41174 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 80418240 512-byte hdwr sectors (41174 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 sdc7 sdc8 >
sd 2:0:1:0: Attached scsi disk sdc
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:1:0: Attached scsi generic sg2 type 0
Le Mon, 13 Mar 2006 21:28:35 +0100, Matthieu CASTET a écrit :
Quoted 21 lines
Hi Alan,
Le Mon, 13 Mar 2006 15:07:10 +0000, Alan Cox a écrit :
Quoted 5 lines
Available from
http://zeniv.linux.org.uk/~alan/IDE/
VIA ATAPI now works for me
It still doesn't work for me [1].
May be it has something to do with the lost interrupt I described in my previous mail.I will try
ata_piixin order to see if all PATA device are seen.Matthieu
ata3: PATA max UDMA/100 cmd
0x1F0ctl0x3F6bmdma0xFC00irq 14
Quoted 7 lines
ata3: dev 0 ATA-7, max UDMA/100, 156368016 sectors: LBA48
ata3: dev 1 ATA-5, max UDMA/100, 80418240 sectors: LBA
ata3: dev 0 configured for UDMA/33
ata3: dev 1 configured for UDMA/33
This seems be wrong : why UDMA/100 isn't choosed ? It was in previous release.
Thanks for your work
Matthieu
PS : Yes I have a 80 pins an ata3 but a 40 pins on ata4
Quoted 3 lines · Alan Cox
Available from
I still see the same oops in make_class_name with pata_pcmcia upon insertion of a CF memory card as I previously reported to you with 2.6.16-rc5-ide1.
--
Kevin 'radsaq' Radloff
[email protected]
http://thesaq.com/
Hi,
I tried your ide1 patch with 2.6.16-rc6 and NFORCE2 board, thus using the AMD driver (and sil sata driver).
I get this in dmesg:
libata version 1.20 loaded.sata_sil 0000:01:0b.0: version 0.9
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 18
ata1: SATA max UDMA/100 cmd 0xF0806080 ctl 0xF080608A bmdma 0xF0806000 irq 18
ata2: SATA max UDMA/100 cmd 0xF08060C0 ctl 0xF08060CA bmdma 0xF0806008 irq 18
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01 87:4763 88:207f
ata1: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: SATA link down (SStatus 0)
scsi1 : sata_sil
Vendor: ATA Model: Maxtor 7V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision: 05pata_amd 0000:00:09.0: version 0.1.3
PCI: Setting latency timer of device 0000:00:09.0 to 64
ata3: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata3: dev 0 cfg 49:0b00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407
ata3: dev 0 ATAPI, max UDMA/33
ata3: PIO error
ata3: dev 0 configured for UDMA/33
scsi2 : pata_amd
Vendor: NU Model: DVDRW DDW-081 Rev: BX32
Type: CD-ROM ANSI SCSI revision: 05
ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
ATA: abnormal status 0x7F on port 0x177
ata4: dev 0 cfg 49:0e00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0000
ata4: no dma
ata4: dev 0 not supported, ignoring
scsi3 : pata_amd
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > sda3
sd 0:0:0:0: Attached scsi disk sda
sr0: scsi3-mmc drive: 12x/40x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20
sr 2:0:0:0: Attached scsi CD-ROM sr0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 2:0:0:0: Attached scsi generic sg1 type 5
Though log gives a PIO error (see above) for the DVD+RW drive, it seems to work w/o problems in a quick test. But I have a ATAPI ZIP-100 drive connected to the secondary master port and this device doesn't show up. The log seems to indicate some problems. I know it is a PIO0 device, so maybe this is the problem? PIO not implemented, yet? Or have I missed a SCSI option to be enabled?
I will see how the DVD+RW drive behaves and let you know whether it makes troubles. :-)
Cheers,
Signature · 3 lines
(°= =°) //\ Prakash Punnoor /\\ V_/ \_V
Am Montag März 13 2006 23:31 schrieb Prakash Punnoor:
Quoted 4 lines
Hi,
I tried your ide1 patch with 2.6.16-rc6 and NFORCE2 board, thus using the AMD driver (and sil sata driver).
[...]
Quoted 2 lines
I will see how the DVD+RW drive behaves and let you know whether it makes troubles. :-)
Ok, I am having some troubles burning CDs/DVDs. I am using k3b as front-end and it has troubles to detect the type of disc inserted. If you eg insert a cd-rw the dialog changes the detected medium around (about each second):
cd-rom, cd-rw, etc. Same with DVD+R. It detects DVD+R, waiting a second, than appendable DVD+R etc. But then it thinks it is a RW so it wants to blank/format/whatever it and this breaks, ie. I can't start the burning. It worked fine with a DVD+RW though. And ignoring the message and blanking in menu, I could also write a cd-rw.
I am not sure what is causing the problem. Could dbus/hal be also trouble makers? I don't know whether k3b is making something stupid, as well. Last time I tried I had no problem with the ide driver though. So I don't know whether ATAPI support in libata still needs polishing or whether Alan's PATA patch is missing something or whatever...
What infos should I provide to make diagnosis easier?
Signature · 3 lines
(°= =°) //\ Prakash Punnoor /\\ V_/ \_V
Quoted 19 lines · Prakash Punnoor
Am Montag März 13 2006 23:31 schrieb Prakash Punnoor:
Quoted 6 lines
Hi,
I tried your ide1 patch with 2.6.16-rc6 and NFORCE2 board, thus using the AMD driver (and sil sata driver).
[...]
Quoted 4 lines
I will see how the DVD+RW drive behaves and let you know whether it makes troubles. :-)
Quoted 9 lines
Ok, I am having some troubles burning CDs/DVDs. I am using k3b as front-end and it has troubles to detect the type of disc inserted. If you eg insert a cd-rw the dialog changes the detected medium around (about each second): cd-rom, cd-rw, etc. Same with DVD+R. It detects DVD+R, waiting a second, than appendable DVD+R etc. But then it thinks it is a RW so it wants to blank/format/whatever it and this breaks, ie. I can't start the burning. It worked fine with a DVD+RW though. And ignoring the message and blanking in menu, I could also write a cd-rw.
I am not sure what is causing the problem. Could dbus/hal be also trouble makers? I don't know whether k3b is making something stupid, as well. Last time I tried I had no problem with the ide driver though. So I don't know whether ATAPI support in libata still needs polishing or whether Alan's PATA patch is missing something or whatever...
What infos should I provide to make diagnosis easier?
graveman had the same problem. I went and used cdrecord-prodvd and haven't had a problem with direct command line, gcombust, or xcdroast (those are all plain frontends to the userspace tools).
This seems to be a userspace problem in operating with libata/pata. xcdroast/gcombust and regular commandline usage of cdrecord-prodvd work fine.
Am Mittwoch März 15 2006 12:29 schrieb Ed Sweetman:
Quoted 5 lines
Quoted 4 lines · Prakash Punnoor
Ok, I am having some troubles burning CDs/DVDs. I am using k3b as front-end and it has troubles to detect the type of disc inserted. If you eg insert a cd-rw the dialog changes the detected medium around (about each second): cd-rom, cd-rw, etc. Same with DVD+R. It detects DVD+R,
[..]
Quoted 8 lines
graveman had the same problem. I went and used cdrecord-prodvd and
haven't had a problem with direct command line, gcombust, or xcdroast (those are all plain frontends to the userspace tools).This seems to be a userspace problem in operating with libata/pata. xcdroast/gcombust and regular commandline usage of cdrecord-prodvd work fine.
Ok, thx for the info. I think for the moment I'll go back to the ide driver, as I really don't want to use other tools.
Signature · 3 lines
(°= =°) //\ Prakash Punnoor /\\ V_/ \_V
Quoted 5 lines · Alan Cox
Available from
Quoted 12 lines
Main changes:
Various drivers moved to use SRST
Probe code now knows about0xFFreturn due to missing pulldowns
on cheap controllers
HPT37x masking bug fixed
Try to issue LBA28 commands whenever possible
Above should fix ALi speed problems
VIA ATAPI now works for me
IT8212 prints raid data
Fix IT8212 sector clamping
Report aborted command for unknown errors
Fix HPT371 crash on probe
Alan,
pata_via detects my HP Colorado 5GB again, although I still haven't had a chance to test it yet: tapes are on back order. The DVD-RW also gets detected and haven't tested yet but I don't doubt it'll work since it has worked fine for me since it was detected. I notice the driver seems much more verbose now as well.
Here is my bootlog:
[4294688.651000] pata_via 0000:00:0f.1: version 0.1.6 [4294688.651000] ACPI: PCI Interrupt 0000:00:0f.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 177 [4294688.651000] PCI: Via IRQ fixup for 0000:00:0f.1, from 255 to 1 [4294688.651000] ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xD000 irq 14 [4294688.802000] via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4 [4294688.802000] t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10 [4294688.802000] FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9 [4294688.956000] ata5: dev 0 cfg 49:0f00 82:0218 83:4000 84:4000 85:0218 86:0000 87:4000 88:101f [4294688.956000] ata5: dev 0 ATAPI, max UDMA/66 [4294688.956000] via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4 [4294688.956000] t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10 [4294688.956000] FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9 [4294688.956000] via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4 [4294688.956000] t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1 [4294688.956000] FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0 [4294688.956000] via_do_set_mode: Mode=68 ast broken=Y udma=133 mul=4 [4294688.956000] t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1 [4294688.956000] FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0 [4294688.956000] ata5: dev 0 configured for UDMA/66 [4294688.956000] scsi4 : pata_via [4294688.968000] Vendor: PIONEER Model: DVD-RW DVR-110D Rev: 1.39 [4294688.968000] Type: CD-ROM ANSI SCSI revision: 05 [4294689.072000] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray [4294689.072000] Uniform CD-ROM driver Revision: 3.20 [4294689.072000] sr 4:0:0:0: Attached scsi CD-ROM sr0 [4294689.072000] sr 4:0:0:0: Attached scsi generic sg4 type 5 [4294689.073000] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xD008 irq 15 [4294689.554000] via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4 [4294689.554000] t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10 [4294689.554000] FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9 [4294689.711000] ata6: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0000 [4294689.711000] ata6: dev 0 ATAPI, max MWDMA2 [4294689.711000] via_do_set_mode: Mode=8 ast broken=Y udma=133 mul=4 [4294689.711000] t.act8b = 11, t.rec8b = 9, t.active = 10, t.recover = 10 [4294689.711000] FIT t.act8b = 10, t.rec8b = 8, t.active = 9, t.recover = 9 [4294689.828000] usb 1-1: new low speed USB device using uhci_hcd and address 3 [4294689.862000] ata6: PIO error [4294689.862000] via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4 [4294689.862000] t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1 [4294689.862000] FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0 [4294689.862000] via_do_set_mode: Mode=34 ast broken=Y udma=133 mul=4 [4294689.862000] t.act8b = 3, t.rec8b = 1, t.active = 3, t.recover = 1 [4294689.862000] FIT t.act8b = 2, t.rec8b = 0, t.active = 2, t.recover = 0 [4294689.862000] ata6: dev 0 configured for MWDMA2 [4294689.862000] scsi5 : pata_via [4294689.875000] Vendor: HP Model: COLORADO 5GB Rev: 2.06 [4294689.875000] Type: Sequential-Access ANSI SCSI revision: 02 [4294689.876000] st 5:0:0:0: Attached scsi tape st0<4>st0: try direct i/o: yes (alignment 512 B) [4294689.876000] st 5:0:0:0: Attached scsi generic sg5 type 1
HTH,
Chris
Signature · 3 lines
Chris Boot [email protected] http://www.bootc.net/
Quoted 2 lines · Chris Boot
pata_viadetects my HP Colorado 5GB again, although I still haven't had a chance to test it yet: tapes are on back order. The DVD-RW also
Good to know
Quoted 3 lines
gets detected and haven't tested yet but I don't doubt it'll work since it has worked fine for me since it was detected. I notice the driver seems much more verbose now as well.
Debug bits - they will go away again shortly.