Bug #1158: Problems with a SATA DVD burner - DragonFlyBSD - DragonFlyBSD bugtracker

Actions

Copy link

Bug #1158

closed

Problems with a SATA DVD burner

Added by steve over 15 years ago. Updated about 15 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

Due date:

% Done:

Estimated time:

Description

Hi,

My trusty (well not so trusty) DVD burner started acting up
(intermittently refusing to eject or load) so I had to pick up a
replacement, the only one available locally at a sane price was a SATA unit
so with a promise that I could return it I bought it and put it in my
workstation box and booted DragonFly.

As soon as the atapicam driver got to it an interrupt storm started
and the livelock went on, and off and on and off and ... well you get the
idea - 80% CPU utilisation in interrupt. A little research suggested DMA
problems as a possible cause - setting hw.ata.atapi_dma=0 in loader.conf
didn't help.

More research suggested a problem with having both atapicd and
atapicam loaded, so I built a kernel without atapicd. That got rid of the
livelock and the burner worked. Then I remembered that DMA was off so I
reenabled that and rebooted, the livelock promptly came back.

I haven't tried atapicd with DMA, but as far as I know there's no
software that will write a DVD through atapicd so that's not really an
option.

Relevant bits of verbose boot dmesg are very odd as they seem to
show that two devices are on ata4 one of them a UDMA133 hard disc, the
other the SATA DVD burner.

For now it's usable but not ideal, does anyone have any suggestions
as to how I might go about getting DMA working for this drive ?

Copyright (c) 2003-2008 The DragonFly Project.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
DragonFly 2.1.0-PREVIEW #51: Sat Nov 1 18:26:23 GMT 2008
root@df1.marelmo.com:/usr/obj/usr/src/sys/DF1_NATA
Calibrating clock(s) ... TSC clock: 2002632654 Hz, i8254 clock: 1193227 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.58-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
AMD Features=0xe0500000<NX,AMIE,LM,DSP,3DNow!>
Data TLB: 32 entries, fully associative
Instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative
real memory = 1610285056 (1572544K bytes)
Physical memory chunk(s):
0x00001000 - 0x0009efff, 647168 bytes (158 pages)
0x005ef000 - 0x5ff9ffff, 1603997696 bytes (391601 pages)
avail memory = 1552437248 (1516052K bytes)
bios32: Found BIOS32 Service Directory header at 0xc00f0000
bios32: Entry = 0xf0010 (c00f0010) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0x31
pnpbios: Found PnP BIOS data at 0xc00f5b30
pnpbios: Entry = f0000:689a Rev = 1.0
Other BIOS signatures found:
Preloaded elf kernel "/boot/kernel" at 0xc05c2000.
Preloaded elf module "/boot/modules/ubt.ko" at 0xc05c2218.
Preloaded elf module "/boot/modules/netbt.ko" at 0xc05c22c4.
crypto: <crypto core>
Pentium Pro MTRR support enabled
md0: Malloc disk
Math emulator present
ACPI: RSDP 0x0xfa7c0/0x0021 (v 2 ACPIAM) ACPI: XSDT 0x0x5ffb0100/0x0034 (v 1 A M I OEMXSDT 0x10000506 MSFT 0x00000097)
ACPI: FACP 0x0x5ffb0290/0x00F4 (v 3 A M I OEMFACP 0x10000506 MSFT 0x00000097) ACPI: DSDT 0x0x5ffb03f0/0x3A3E (v 1 A0036 A0036001 0x00000001 MSFT 0x0100000D)
ACPI: FACS 0x0x5ffc0000/0x0040 ACPI: OEMB 0x0x5ffc0040/0x003F (v 1 A M I OEMBIOS 0x10000506 MSFT 0x00000097)
pci_open(1): mode 1 addr port (0x0cf8) is 0x80010014
pci_open(1a): mode1res=0x80000000 (0x80000000)
pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=02821106)
pcibios: BIOS version 2.10
Using $PIR table, 12 entries at 0xc00f59b0
PCI-Only Interrupts: none
Location Bus Device Pin Link IRQs
embedded 0 1 A 0x01 3 4 5 7 10 11 14 15
embedded 0 1 B 0x02 3 4 5 7 10 11 14 15
embedded 0 17 C 0x03 3 4 5 7 10 11 14 15
embedded 0 15 A 0x01 3 4 5 7 10 11 14 15
embedded 0 15 B 0x02 3 4 5 7 10 11 14 15
embedded 0 15 C 0x03 3 4 5 7 10 11 14 15
embedded 0 15 D 0x05 3 4 5 7 10 11 14 15
embedded 0 16 A 0x01 3 4 5 7 10 11 14 15
embedded 0 16 B 0x02 3 4 5 7 10 11 14 15
embedded 0 16 C 0x03 3 4 5 7 10 11 14 15
embedded 0 16 D 0x05 3 4 5 7 10 11 14 15
slot 1 0 11 A 0x01 3 4 5 7 10 11 14 15
slot 1 0 11 B 0x02 3 4 5 7 10 11 14 15
slot 1 0 11 C 0x03 3 4 5 7 10 11 14 15
slot 1 0 11 D 0x05 3 4 5 7 10 11 14 15
slot 2 0 12 A 0x02 3 4 5 7 10 11 14 15
slot 2 0 12 B 0x03 3 4 5 7 10 11 14 15
slot 2 0 12 C 0x05 3 4 5 7 10 11 14 15
slot 2 0 12 D 0x01 3 4 5 7 10 11 14 15
slot 3 0 13 A 0x03 3 4 5 7 10 11 14 15
slot 3 0 13 B 0x05 3 4 5 7 10 11 14 15
slot 3 0 13 C 0x01 3 4 5 7 10 11 14 15
slot 3 0 13 D 0x02 3 4 5 7 10 11 14 15
slot 4 0 14 A 0x05 3 4 5 7 10 11 14 15
slot 4 0 14 B 0x01 3 4 5 7 10 11 14 15
slot 4 0 14 C 0x02 3 4 5 7 10 11 14 15
slot 4 0 14 D 0x03 3 4 5 7 10 11 14 15
slot 5 0 9 A 0x01 3 4 5 7 10 11 14 15
slot 5 0 9 B 0x02 3 4 5 7 10 11 14 15
slot 5 0 9 C 0x03 3 4 5 7 10 11 14 15
slot 5 0 9 D 0x05 3 4 5 7 10 11 14 15
embedded 0 7 A 0x01 3 4 5 7 10 11 14 15
embedded 0 10 A 0x02 3 4 5 7 10 11 14 15
embedded 0 8 A 0x03 3 4 5 7 10 11 14 15
acpi0.nexus0.root0
acpi0: <A M I OEMXSDT> [tentative] on motherboard
acpi0: Power Button (fixed)
Warning: ACPI is disabling APM's device. You can't run both
AcpiOsDerivePciId: bus 0 dev 17 func 0
AcpiOsDerivePciId: bus 0 dev 17 func 0
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
ACPI timer looks GOOD min = 2, max = 3, width = 1
acpi_timer0.acpi0.nexus0.root0
acpi_timer0: <24-bit timer at 3.579545MHz> [tentative] port 0x808-0x80b on acpi0
acpi_timer0: <24-bit timer at 3.579545MHz> [attached!] port 0x808-0x80b on acpi0
cpu0.acpi0.nexus0.root0
cpu0: <ACPI CPU> [tentative] on acpi0
cpu0: switching to generic Cx mode
cpu0: <ACPI CPU> [attached!] on acpi0
acpi_button0.acpi0.nexus0.root0
acpi_button0: <Power Button> [tentative] on acpi0
acpi_button0: <Power Button> [attached!] on acpi0
acpi_button1.acpi0.nexus0.root0
acpi_button1: <Sleep Button> [tentative] on acpi0
acpi_button1: <Sleep Button> [attached!] on acpi0
atkbdc0.acpi0.nexus0.root0
atkbdc0: <Keyboard controller (i8042)> [tentative] port 0x64,0x60 irq 1 on acpi0
atkbd0.atkbdc0.acpi0.nexus0.root0
atkbd0: <AT Keyboard> [tentative] flags 0x1 irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0065
atkbd: keyboard ID 0x41ab (2)
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000
atkbd0: <AT Keyboard> [attached!] flags 0x1 irq 1 on atkbdc0
psm0: current command byte:0065
psm0: failed to reset the aux device.
atkbdc0: <Keyboard controller (i8042)> [attached!] port 0x64,0x60 irq 1 on acpi0
unknown: not probed (disabled)
unknown: not probed (disabled)
unknown: not probed (disabled)
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: irq maps: 0 0 0 0
sio0.acpi0.nexus0.root0
sio0 [tentative] port 0x2f8-0x2ff irq 3 on acpi0
sio0: type 16550A
sio0 [attached!] port 0x2f8-0x2ff irq 3 on acpi0
sio1: configured irq 4 not in bitmap of probed irqs 0
sio1: irq maps: 0 0 0 0
sio1.acpi0.nexus0.root0
sio1 [tentative] port 0x3f8-0x3ff irq 4 on acpi0
sio1: type 16550A
sio1 [attached!] port 0x3f8-0x3ff irq 4 on acpi0
unknown: not probed (disabled)
unknown: not probed (disabled)
unknown: not probed (disabled)
unknown: not probed (disabled)
unknown: not probed (disabled)
unknown: not probed (disabled)
unknown: not probed (disabled)
acpi0: <A M I OEMXSDT> [attached!] at irq 9 on motherboard
sched_ithd: stray interrupt 7 on cpu 0
npx0.nexus0.root0
npx0: <math processor> [tentative] on motherboard
npx0: INT 16 interface
Using XMM optimized bcopy/copyin/copyout
npx0: <math processor> [attached!] on motherboard
legacypci0.nexus0.root0
legacypci0 [tentative] on motherboard
pcib0.legacypci0.nexus0.root0
pcib0: <Host to PCI bridge> [tentative] on legacypci0
pci0.pcib0.legacypci0.nexus0.root0
pci0: <PCI bus> [tentative] on pcib0
pci0: pci_attach() physical bus=0
map¹⁰: type 1, range 32, base d0000000, size 28
found-> vendor=0x1106, dev=0x0282, revid=0x00
bus=0, slot=0, func=0
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
found-> vendor=0x1106, dev=0x1282, revid=0x00
bus=0, slot=0, func=1
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
found-> vendor=0x1106, dev=0x2282, revid=0x00
bus=0, slot=0, func=2
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
found-> vendor=0x1106, dev=0x3282, revid=0x00
bus=0, slot=0, func=3
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
found-> vendor=0x1106, dev=0x4282, revid=0x00
bus=0, slot=0, func=4
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
found-> vendor=0x1106, dev=0x7282, revid=0x00
bus=0, slot=0, func=7
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
found-> vendor=0x1106, dev=0xb188, revid=0x00
bus=0, slot=1, func=0
class=[BRIDGE]06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=1 secondarybus=1
map¹⁰: type 1, range 32, base fb600000, size 11
map¹⁴: type 1, range 32, base 00008400, size 7
found-> vendor=0x1106, dev=0x3044, revid=0x80
bus=0, slot=7, func=0
class=[SERIALBUS]0c-00-10, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=11
map¹⁰: type 1, range 32, base 00009400, size 6
map¹⁴: type 1, range 32, base 00009000, size 4
map¹⁸: type 1, range 32, base 00008800, size 7
map[1c]: type 1, range 32, base fb800000, size 12
map²⁰: type 1, range 32, base fb700000, size 17
found-> vendor=0x105a, dev=0x3373, revid=0x02
bus=0, slot=8, func=0
class=[STORAGE]01-04-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=5
map¹⁰: type 1, range 32, base fba00000, size 14
map¹⁴: type 1, range 32, base 00009800, size 8
found-> vendor=0x11ab, dev=0x4320, revid=0x13
bus=0, slot=10, func=0
class=[NETWORK]02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=10
map¹⁰: type 1, range 32, base 0000a400, size 5
map¹⁴: type 1, range 32, base 0000a000, size 7
found-> vendor=0x1412, dev=0x1724, revid=0x01
bus=0, slot=12, func=0
class=[MULTIMEDIA]04-01-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=10
map¹⁰: type 1, range 32, base e7e00000, size 12
found-> vendor=0x109e, dev=0x036e, revid=0x11
bus=0, slot=14, func=0
class=[MULTIMEDIA]04-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=a, irq=7
map¹⁰: type 1, range 32, base e7f00000, size 12
found-> vendor=0x109e, dev=0x0878, revid=0x11
bus=0, slot=14, func=1
class=[MULTIMEDIA]04-80-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=a, irq=7
map¹⁰: type 1, range 32, base 0000c400, size 3
map¹⁴: type 1, range 32, base 0000c000, size 2
map¹⁸: type 1, range 32, base 0000b800, size 3
map[1c]: type 1, range 32, base 0000b400, size 2
map²⁰: type 1, range 32, base 0000b000, size 4
map²⁴: type 1, range 32, base 0000a800, size 8
found-> vendor=0x1106, dev=0x3149, revid=0x80
bus=0, slot=15, func=0
class=[STORAGE]01-04-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=b, irq=10
map²⁰: type 1, range 32, base 0000fc00, size 4
found-> vendor=0x1106, dev=0x0571, revid=0x06
bus=0, slot=15, func=1
class=[STORAGE]01-01-8a, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=255
map²⁰: type 1, range 32, base 0000c800, size 5
found-> vendor=0x1106, dev=0x3038, revid=0x81
bus=0, slot=16, func=0
class=[SERIALBUS]0c-03-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=a, irq=11
map²⁰: type 1, range 32, base 0000d000, size 5
found-> vendor=0x1106, dev=0x3038, revid=0x81
bus=0, slot=16, func=1
class=[SERIALBUS]0c-03-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=a, irq=11
map²⁰: type 1, range 32, base 0000d400, size 5
found-> vendor=0x1106, dev=0x3038, revid=0x81
bus=0, slot=16, func=2
class=[SERIALBUS]0c-03-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=b, irq=10
map²⁰: type 1, range 32, base 0000d800, size 5
found-> vendor=0x1106, dev=0x3038, revid=0x81
bus=0, slot=16, func=3
class=[SERIALBUS]0c-03-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=b, irq=10
map¹⁰: type 1, range 32, base fbc00000, size 8
found-> vendor=0x1106, dev=0x3104, revid=0x86
bus=0, slot=16, func=4
class=[SERIALBUS]0c-03-20, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=c, irq=5
found-> vendor=0x1106, dev=0x3227, revid=0x00
bus=0, slot=17, func=0
class=[BRIDGE]06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
found-> vendor=0x1022, dev=0x1100, revid=0x00
bus=0, slot=24, func=0
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
found-> vendor=0x1022, dev=0x1101, revid=0x00
bus=0, slot=24, func=1
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
found-> vendor=0x1022, dev=0x1102, revid=0x00
bus=0, slot=24, func=2
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
found-> vendor=0x1022, dev=0x1103, revid=0x00
bus=0, slot=24, func=3
class=[BRIDGE]06-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
agp0.pci0.pcib0.legacypci0.nexus0.root0
agp0: <VIA K8T800Pro host to PCI bridge> [tentative] mem 0xd0000000-0xdfffffff at device 0.0 on pci0
agp0: 1 Miscellaneous Control unit(s) found.
agp0: allocating GATT for aperture of size 256M
agp0: <VIA K8T800Pro host to PCI bridge> [attached!] mem 0xd0000000-0xdfffffff at device 0.0 on pci0
pcib1.pci0.pcib0.legacypci0.nexus0.root0
pcib1: <PCI to PCI bridge (vendor=1106 device=b188)> [tentative] at device 1.0 on pci0
pcib1: secondary bus 1
pcib1: subordinate bus 1
pcib1: I/O decode 0xe000-0xefff
pcib1: memory decode 0xfbd00000-0xfbffffff
pcib1: prefetched decode 0xe8000000-0xfaffffff
pci1.pcib1.pci0.pcib0.legacypci0.nexus0.root0
pci1: <PCI bus> [tentative] on pcib1
pci1: pci_attach() physical bus=1
map¹⁰: type 1, range 32, base e8000000, size 27
map¹⁴: type 1, range 32, base 0000e000, size 8
map¹⁸: type 1, range 32, base fbe00000, size 16
found-> vendor=0x1002, dev=0x5964, revid=0x01
bus=1, slot=0, func=0
class=[DISPLAY]03-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0 secondarybus=0
intpin=a, irq=11
map¹⁰: type 1, range 32, base f0000000, size 27
map¹⁴: type 1, range 32, base fbf00000, size 16
found-> vendor=0x1002, dev=0x5d44, revid=0x01
bus=1, slot=0, func=1
class=[DISPLAY]03-80-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
drm0.pci1.pcib1.pci0.pcib0.legacypci0.nexus0.root0
drm0: <ATI Radeon RV280 9200 SE> [tentative] port 0xe000-0xe0ff mem 0xfbe00000-0xfbe0ffff,0xe8000000-0xefffffff irq 11 at device 0.0 on pci1
info: [drm] AGP at 0xd0000000 256MB
info: [drm] Initialized radeon 1.28.0 20060524
drm0: <ATI Radeon RV280 9200 SE> [attached!] port 0xe000-0xe0ff mem 0xfbe00000-0xfbe0ffff,0xe8000000-0xefffffff irq 11 at device 0.0 on pci1
pci1: <ATI model 5d44 graphics accelerator> (vendor=0x1002, dev=0x5d44) at 0.1
pci1: <PCI bus> [attached!] on pcib1
pcib1: <PCI to PCI bridge (vendor=1106 device=b188)> [attached!] at device 1.0 on pci0
fwohci0.pci0.pcib0.legacypci0.nexus0.root0
fwohci0: <VIA Fire II (VT6306)> [tentative] port 0x8400-0x847f mem 0xfb600000-0xfb6007ff irq 11 at device 7.0 on pci0
fwohci0: latency timer 64 > 64.
fwohci0: cache size 16 -> 16.
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channel is 4.
fwohci0: EUI64 00:e0:18:00:00:a9:12:8f
fwohci0: resetting OHCI...done (loop=0)
fwohci0: fwphy_rddata: 0x2 loop=1, retry=0
fwohci0: fwphy_rddata: 0x3 loop=1, retry=0
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: fwphy_rddata: 0x5 loop=1, retry=0
fwohci0: Enable 1394a Enhancements
fwohci0: fwphy_rddata: 0x5 loop=1, retry=0
fwohci0: fwphy_rddata: 0x2 loop=1, retry=0
fwohci0: fwphy_rddata: 0x4 loop=1, retry=0
fwohci0: fwphy_rddata: 0x4 loop=1, retry=0
fwohci0: fwphy_rddata: 0x4 loop=1, retry=0
fwohci0: Link S400, max_rec 2048 bytes.
fwohci0: BUS_OPT 0xf800a202 -> 0xf800a202
fwohci0: fwohci_set_intr: 1
firewire0.fwohci0.pci0.pcib0.legacypci0.nexus0.root0
firewire0: <IEEE1394 bus> [tentative] on fwohci0
sbp0.firewire0.fwohci0.pci0.pcib0.legacypci0.nexus0.root0
sbp0: <SBP-2/SCSI over FireWire> [tentative] on firewire0
sbp_attach (cold=1)
sbp0: <SBP-2/SCSI over FireWire> [attached!] on firewire0
fwe0.firewire0.fwohci0.pci0.pcib0.legacypci0.nexus0.root0
fwe0: <Ethernet over FireWire> [tentative] on firewire0
fwe0: bpf attached
fwe0: MAC address: 02:e0:18:a9:12:8f
fwe0: <Ethernet over FireWire> [attached!] on firewire0
sbp_post_busreset
fwohci0: Initiate bus reset
fwohci0: fwphy_rddata: 0x1 loop=1, retry=0
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
fwohci0: fw_set_bus_manager: 0>0 (loop=0)
firewire0: bus manager 0 (me)
send phy_config root_node=-1 gap_count=5
fwohci0: maxdesc: 2
fwohci0: start AT DMA status=0
Current DB 0
ch = 0
Current OP KEY INT BR len Addr Depend Stat: Cnt
5c88b000 OUTL ST2 ALL ALL 12 00000000 5c88b080 8411:0008 RUN,ACTIVE, ack complete(11)
0x000000e0 0x00450000 0xffbaffff 0x00000000
fwohci0: fwphy_rddata: 0x1 loop=1, retry=0
firewire0: <IEEE1394 bus> [attached!] on fwohci0
fwohci0: <VIA Fire II (VT6306)> [attached!] port 0x8400-0x847f mem 0xfb600000-0xfb6007ff irq 11 at device 7.0 on pci0
atapci0.pci0.pcib0.legacypci0.nexus0.root0
atapci0: <Promise PDC20378 SATA150 controller> [tentative] port 0x8800-0x887f,0x9000-0x900f,0x9400-0x943f mem 0xfb700000-0xfb71ffff,0xfb800000-0xfb800fff irq 5 at device 8.0 on pci0
pci0: child atapci0 requested type 4 for rid 0x20, but the BAR says it is a memio
ata2.atapci0.pci0.pcib0.legacypci0.nexus0.root0
ata2: <ATA channel 0> [tentative] on atapci0
ata2: SATA connect time=0ms
ata2: reset tp1 mask=01 ostat0=50 ostat1=00
ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata2: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad4: 239372MB <Maxtor 6Y250M0 YAR51HW0> at ata2-master SATA150
ad4: 490234752 sectors [486344C/16H/63S] 16 sectors/interrupt 1 depth queue
ata2: <ATA channel 0> [attached!] on atapci0
ata3.atapci0.pci0.pcib0.legacypci0.nexus0.root0
ata3: <ATA channel 1> [tentative] on atapci0
ata3: SATA connect status=00000000
ata3: <ATA channel 1> [attached!] on atapci0
ata4.atapci0.pci0.pcib0.legacypci0.nexus0.root0
ata4: <ATA channel 2> [tentative] on atapci0
ata4: reset tp1 mask=03 ostat0=50 ostat1=00
ata4: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata4: stat1=0x00 err=0x01 lsb=0x00 msb=0x00
ata4: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
bus_explore done
sbp_post_explore
ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 wire
ad8: setting PIO4 on PDC20378 chip
ad8: setting UDMA133 on PDC20378 chip
ad8: 117246MB <Maxtor 6Y120P0 YAR41BW0> at ata4-master UDMA133
ad8: 240121728 sectors [238216C/16H/63S] 16 sectors/interrupt 1 depth queue
ata4: <ATA channel 2> [attached!] on atapci0
atapci0: <Promise PDC20378 SATA150 controller> [attached!] port 0x8800-0x887f,0x9000-0x900f,0x9400-0x943f mem 0xfb700000-0xfb71ffff,0xfb800000-0xfb800fff irq 5 at device 8.0 on pci0
skc0.pci0.pcib0.legacypci0.nexus0.root0
skc0: <Marvell Yukon 88E8001/8003/8010> [tentative] port 0x9800-0x98ff mem 0xfba00000-0xfba03fff irq 10 at device 10.0 on pci0
sk0.skc0.pci0.pcib0.legacypci0.nexus0.root0
sk0: <Marvell Yukon Lite rev.A3 (0x7)> [tentative] on skc0
miibus0.sk0.skc0.pci0.pcib0.legacypci0.nexus0.root0
miibus0: <MII bus> [tentative] on sk0
e1000phy0.miibus0.sk0.skc0.pci0.pcib0.legacypci0.nexus0.root0
e1000phy0: <Marvell Semiconductor 88E1011 Gigabit PHY> [tentative] on miibus0
e1000phy0: 1000baseT-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX, 10baseTX, auto
e1000phy0: <Marvell Semiconductor 88E1011 Gigabit PHY> [attached!] on miibus0
miibus0: <MII bus> [attached!] on sk0
sk0: bpf attached
sk0: MAC address: 00:11:2f:ba:bb:ee
sk0: <Marvell Yukon Lite rev.A3 (0x7)> [attached!] on skc0
skc0: <Marvell Yukon 88E8001/8003/8010> [attached!] port 0x9800-0x98ff mem 0xfba00000-0xfba03fff irq 10 at device 10.0 on pci0
pcm0.pci0.pcib0.legacypci0.nexus0.root0
pcm0: <Envy24HT-S audio (Chaintech AV710)> [tentative] port 0xa000-0xa07f,0xa400-0xa41f irq 10 at device 12.0 on pci0
pcm0: system configuration
SubVendorID: 0x1412, SubDeviceID: 0x1724
XIN2 Clock Source: 24.576MHz(96kHz*256)
MPU-401 UART #: not implemented
ADC #: 1
DAC #: 3
Multi-track converter type: I2S
S/PDIF: 0/1 ID# 0x00
GPIO: 0xff0000/0xff0000/0xff0000
pcm0: Mixer "vol":
pcm0: Mixer "treble":
pcm0: Mixer "synth":
pcm0: Mixer "pcm":
pcm0: Mixer "speaker":
pcm0: Mixer "line":
pcm0: Mixer "mic":
pcm0: Mixer "cd":
pcm0: Mixer "mix":
pcm0: <Envy24HT-S audio (Chaintech AV710)> [attached!] port 0xa000-0xa07f,0xa400-0xa41f irq 10 at device 12.0 on pci0
bktr0.pci0.pcib0.legacypci0.nexus0.root0
bktr0: <BrookTree 878> [tentative] mem 0xe7e00000-0xe7e00fff irq 7 at device 14.0 on pci0
brooktree0: PCI bus latency is 64.
bktr0: buffer size 3555328, addr 0x5000000
bktr0: GPIO is 0x00ffffff
bktr0: subsystem 0x11bd 0x0012
bktr0: MT2032: Companycode=3cbf Part=60 Revision=60
bktr0: MT2032 not found or unknown type
bktr0: Pinnacle/Miro TV, Temic NTSC tuner.
bktr0: <BrookTree 878> [attached!] mem 0xe7e00000-0xe7e00fff irq 7 at device 14.0 on pci0
pci0: <unknown card> (vendor=0x109e, dev=0x0878) at 14.1 irq 7
atapci1.pci0.pcib0.legacypci0.nexus0.root0
atapci1: <VIA 6420 SATA150 controller> [tentative] port 0xa800-0xa8ff,0xb000-0xb00f,0xb400-0xb403,0xb800-0xb807,0xc000-0xc003,0xc400-0xc407 irq 10 at device 15.0 on pci0
ata5.atapci1.pci0.pcib0.legacypci0.nexus0.root0
ata5: <ATA channel 0> [tentative] on atapci1
ata5: SATA connect time=0ms
ata5: reset tp1 mask=01 ostat0=50 ostat1=00
ata5: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata5: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
ata5-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad10: 286168MB <Seagate ST3300622AS 3.AAE> at ata5-master SATA150
ad10: 586072368 sectors [581421C/16H/63S] 16 sectors/interrupt 1 depth queue
ata5: <ATA channel 0> [attached!] on atapci1
ata6.atapci1.pci0.pcib0.legacypci0.nexus0.root0
ata6: <ATA channel 1> [tentative] on atapci1
ata6: SATA connect time=0ms
ata6: reset tp1 mask=01 ostat0=00 ostat1=00
ata6: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata6: reset tp2 stat0=00 stat1=00 devices=0x4<ATAPI_MASTER>
ata6-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire
ata6: <ATA channel 1> [attached!] on atapci1
atapci1: <VIA 6420 SATA150 controller> [attached!] port 0xa800-0xa8ff,0xb000-0xb00f,0xb400-0xb403,0xb800-0xb807,0xc000-0xc003,0xc400-0xc407 irq 10 at device 15.0 on pci0
atapci2.pci0.pcib0.legacypci0.nexus0.root0
atapci2: <VIA 8237 UDMA133 controller> [tentative] port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
ata0.atapci2.pci0.pcib0.legacypci0.nexus0.root0
ata0: <ATA channel 0> [tentative] on atapci2
atapci2: reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
atapci2: reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
ata0: reset tp1 mask=03 ostat0=60 ostat1=70
ata0: stat0=0x20 err=0x20 lsb=0x20 msb=0x20
ata0: stat1=0x30 err=0x30 lsb=0x30 msb=0x30
ata0: reset tp2 stat0=20 stat1=30 devices=0x0
ata0: <ATA channel 0> [attached!] on atapci2
ata1.atapci2.pci0.pcib0.legacypci0.nexus0.root0
ata1: <ATA channel 1> [tentative] on atapci2
atapci2: reserved 0x8 bytes for rid 0x18 type 4 at 0x170
atapci2: reserved 0x1 bytes for rid 0x1c type 4 at 0x376
ata1: reset tp1 mask=03 ostat0=50 ostat1=00
ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: stat1=0x00 err=0x00 lsb=0x7f msb=0x7f
ata1: reset tp2 stat0=00 stat1=00 devices=0x4<ATAPI_MASTER>
ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire
ata1: <ATA channel 1> [attached!] on atapci2
atapci2: <VIA 8237 UDMA133 controller> [attached!] port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
uhci0.pci0.pcib0.legacypci0.nexus0.root0
uhci0: <VIA 83C572 USB controller> [tentative] port 0xc800-0xc81f irq 11 at device 16.0 on pci0
uhci0: LegSup = 0x8030
usb0.uhci0.pci0.pcib0.legacypci0.nexus0.root0
usb0: <VIA 83C572 USB controller> [tentative] on uhci0
usb0: USB revision 1.0
usbd_get_string: getting lang failed, using 0
uhub0.usb0.uhci0.pci0.pcib0.legacypci0.nexus0.root0
uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [tentative] on usb0
uhub0: 2 ports with 2 removable, self powered
uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [attached!] on usb0
usb0: <VIA 83C572 USB controller> [attached!] on uhci0
uhci0: <VIA 83C572 USB controller> [attached!] port 0xc800-0xc81f irq 11 at device 16.0 on pci0
uhci1.pci0.pcib0.legacypci0.nexus0.root0
uhci1: <VIA 83C572 USB controller> [tentative] port 0xd000-0xd01f irq 11 at device 16.1 on pci0
uhci1: LegSup = 0x8030
usb1.uhci1.pci0.pcib0.legacypci0.nexus0.root0
usb1: <VIA 83C572 USB controller> [tentative] on uhci1
usb1: USB revision 1.0
usbd_get_string: getting lang failed, using 0
uhub1.usb1.uhci1.pci0.pcib0.legacypci0.nexus0.root0
uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [tentative] on usb1
uhub1: 2 ports with 2 removable, self powered
uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [attached!] on usb1
usb1: <VIA 83C572 USB controller> [attached!] on uhci1
uhci1: <VIA 83C572 USB controller> [attached!] port 0xd000-0xd01f irq 11 at device 16.1 on pci0
uhci2.pci0.pcib0.legacypci0.nexus0.root0
uhci2: <VIA 83C572 USB controller> [tentative] port 0xd400-0xd41f irq 10 at device 16.2 on pci0
uhci2: LegSup = 0x8030
usb2.uhci2.pci0.pcib0.legacypci0.nexus0.root0
usb2: <VIA 83C572 USB controller> [tentative] on uhci2
usb2: USB revision 1.0
usbd_get_string: getting lang failed, using 0
uhub2.usb2.uhci2.pci0.pcib0.legacypci0.nexus0.root0
uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [tentative] on usb2
uhub2: 2 ports with 2 removable, self powered
uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [attached!] on usb2
usb2: <VIA 83C572 USB controller> [attached!] on uhci2
uhci2: <VIA 83C572 USB controller> [attached!] port 0xd400-0xd41f irq 10 at device 16.2 on pci0
uhci3.pci0.pcib0.legacypci0.nexus0.root0
uhci3: <VIA 83C572 USB controller> [tentative] port 0xd800-0xd81f irq 10 at device 16.3 on pci0
uhci3: LegSup = 0x8030
usb3.uhci3.pci0.pcib0.legacypci0.nexus0.root0
usb3: <VIA 83C572 USB controller> [tentative] on uhci3
usb3: USB revision 1.0
usbd_get_string: getting lang failed, using 0
uhub3.usb3.uhci3.pci0.pcib0.legacypci0.nexus0.root0
uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [tentative] on usb3
uhub3: 2 ports with 2 removable, self powered
uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> [attached!] on usb3
usb3: <VIA 83C572 USB controller> [attached!] on uhci3
uhci3: <VIA 83C572 USB controller> [attached!] port 0xd800-0xd81f irq 10 at device 16.3 on pci0
ehci0.pci0.pcib0.legacypci0.nexus0.root0
ehci0: <VIA VT6202 USB 2.0 controller> [tentative] mem 0xfbc00000-0xfbc000ff irq 5 at device 16.4 on pci0
ehci0: Dropped interrupts workaround enabled
usb4: waiting for BIOS to give up control
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: (null) (null) (null) (null)
intr 5 at 40001/40000 hz, livelocked limit engaged!
usb4.ehci0.pci0.pcib0.legacypci0.nexus0.root0
usb4: <VIA VT6202 USB 2.0 controller> [tentative] on ehci0
usb4: USB revision 2.0
uhub4.usb4.ehci0.pci0.pcib0.legacypci0.nexus0.root0
uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> [tentative] on usb4
uhub4: 8 ports with 8 removable, self powered
uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> [attached!] on usb4
usb4: <VIA VT6202 USB 2.0 controller> [attached!] on ehci0
ehci0: <VIA VT6202 USB 2.0 controller> [attached!] mem 0xfbc00000-0xfbc000ff irq 5 at device 16.4 on pci0
isab0.pci0.pcib0.legacypci0.nexus0.root0
isab0: <PCI to ISA bridge (vendor=1106 device=3227)> [tentative] at device 17.0 on pci0
isa0.isab0.pci0.pcib0.legacypci0.nexus0.root0
isa0: <ISA bus> [tentative] on isab0
isa0: <ISA bus> [attached!] on isab0
isab0: <PCI to ISA bridge (vendor=1106 device=3227)> [attached!] at device 17.0 on pci0
pci0: <PCI bus> [attached!] on pcib0
pcib0: <Host to PCI bridge> [attached!] on legacypci0
legacypci0 [attached!] on motherboard
atkbdc-: atkbdc0 exists, using next available unit number
sio-: sio0 exists, using next available unit number
sio-: sio1 exists, using next available unit number
sio-: sio2 exists, using next available unit number
sio-: sio3 exists, using next available unit number
Trying Read_Port at 203
Trying Read_Port at 243
Trying Read_Port at 283
Trying Read_Port at 2c3
Trying Read_Port at 303
Trying Read_Port at 343
Trying Read_Port at 383
Trying Read_Port at 3c3
isa_probe_children: disabling PnP devices
isa_probe_children: probing non-PnP devices
fdc0: ready for input in output
fdc0: cmd 3 failed at out byte 1 of 3
fdc0 [tentative] failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
atkbdc1: <Keyboard controller (i8042)> [tentative] failed to probe at port 0x60 on isa0
vga0.isa0.isab0.pci0.pcib0.legacypci0.nexus0.root0
vga0: <Generic ISA VGA> [tentative] at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3c0-0x3df, mem:0xa0000 0x20000
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
vga0: vga: WARNING: video mode switching is not fully supported on this adapter
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 a7 5f 4f 4f 83 55 99
ac 1f 00 4f 0d 0e 00 00 07 80 92 08 8f 28 1f 8f
ad a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
VGA parameters in BIOS for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
VGA parameters to be used for mode 24
50 18 10 00 00 00 03 00 02 a7 5f 4f 4f 83 55 99
ac 1f 00 4f 0d 0e 00 00 07 80 92 08 8f 28 1f 8f
ad a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
vga0: <Generic ISA VGA> [attached!] at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0.isa0.isab0.pci0.pcib0.legacypci0.nexus0.root0
sc0: <System console> [tentative] at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sc0: fb0, kbd0, terminal emulator: sc (syscons terminal)
sc0: <System console> [attached!] at flags 0x100 on isa0
sio2 [tentative] failed to probe at port 0x3f8 irq 4 flags 0x10 on isa0
sio3 [tentative] failed to probe at port 0x2f8 irq 3 on isa0
sio4: not probed (disabled)
sio5: not probed (disabled)
ppc0: parallel port not found.
ppc0: <Parallel port> [tentative] failed to probe at irq 7 on isa0
isa_probe_children: probing PnP devices
ukbd0.uhub0.usb0.uhci0.pci0.pcib0.legacypci0.nexus0.root0
ukbd0: <Logitech USB Receiver, class 0/0, rev 1.10/13.10, addr 2> [tentative] on uhub0
kbd: new array size 4
kbd1 at ukbd0
kbd1: ukbd0, generic (0), config:0x0, flags:0x1d0000
ukbd0: <Logitech USB Receiver, class 0/0, rev 1.10/13.10, addr 2> [attached!] on uhub0
ums0.uhub0.usb0.uhci0.pci0.pcib0.legacypci0.nexus0.root0
ums0: <Logitech USB Receiver, class 0/0, rev 1.10/13.10, addr 2> [tentative] on uhub0
ums0: 5 buttons and Z dir.
ums0: <Logitech USB Receiver, class 0/0, rev 1.10/13.10, addr 2> [attached!] on uhub0
uhub5.uhub0.usb0.uhci0.pci0.pcib0.legacypci0.nexus0.root0
uhub5: <vendor 0x0451 product 0x2046, class 9/0, rev 1.10/1.25, addr 3> [tentative] on uhub0
uhub5: 4 ports with 4 removable, self powered
uhub5: <vendor 0x0451 product 0x2046, class 9/0, rev 1.10/1.25, addr 3> [attached!] on uhub0
uscanner0.uhub5.uhub0.usb0.uhci0.pci0.pcib0.legacypci0.nexus0.root0
uscanner0: <EPSON Perfection1240, class 255/255, rev 1.00/1.04, addr 4> [tentative] on uhub5
uscanner0: <EPSON Perfection1240, class 255/255, rev 1.00/1.04, addr 4> [attached!] on uhub5
ulpt0.uhub1.usb1.uhci1.pci0.pcib0.legacypci0.nexus0.root0
ulpt0: <Hewlett-Packard DeskJet 970C, class 0/0, rev 1.00/1.00, addr 2> [tentative] on uhub1
ulpt0: using bi-directional mode
ulpt0: <Hewlett-Packard DeskJet 970C, class 0/0, rev 1.00/1.00, addr 2> [attached!] on uhub1
ubt0.uhub1.usb1.uhci1.pci0.pcib0.legacypci0.nexus0.root0
ubt0: <vendor 0x0e5e product 0x6622, class 224/1, rev 1.10/1.34, addr 3> [tentative] on uhub1
ubt0: <vendor 0x0e5e product 0x6622, class 224/1, rev 1.10/1.34, addr 3> [attached!] on uhub1
BIOS Geometries:
0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors
1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
0 accounted for
Device configuration finished.
lo0: bpf attached
ppp0: bpf attached
sl0: bpf attached
(probe0:ata4:0:0:0): error 22
(probe0:ata4:0:0:0): Unretryable Error
(probe1:ata6:0:0:0): error 22
(probe1:ata6:0:0:0): Unretryable Error
pfsync0: bpf attached
crypto: assign driver 0, flags 2
crypto: driver 0 registers alg 1 flags 0 maxoplen 0
crypto: driver 0 registers alg 2 flags 0 maxoplen 0
crypto: driver 0 registers alg 3 flags 0 maxoplen 0
crypto: driver 0 registers alg 4 flags 0 maxoplen 0
crypto: driver 0 registers alg 5 flags 0 maxoplen 0
crypto: driver 0 registers alg 17 flags 0 maxoplen 0
crypto: driver 0 registers alg 6 flags 0 maxoplen 0
crypto: driver 0 registers alg 7 flags 0 maxoplen 0
crypto: driver 0 registers alg 15 flags 0 maxoplen 0
crypto: driver 0 registers alg 8 flags 0 maxoplen 0
crypto: driver 0 registers alg 16 flags 0 maxoplen 0
crypto: driver 0 registers alg 9 flags 0 maxoplen 0
crypto: driver 0 registers alg 10 flags 0 maxoplen 0
crypto: driver 0 registers alg 13 flags 0 maxoplen 0
crypto: driver 0 registers alg 14 flags 0 maxoplen 0
crypto: driver 0 registers alg 11 flags 0 maxoplen 0
crypto: driver 0 registers alg 18 flags 0 maxoplen 0
faith0: bpf attached
pflog0: bpf attached
(probe8:ata6:0:0:0): error 6
(probe8:ata6:0:0:0): Unretryable Error
(probe7:ata4:0:0:0): error 22
(probe7:ata4:0:0:0): Unretryable Error
(probe8:ata6:0:0:0): error 22
(probe8:ata6:0:0:0): Unretryable Error
intr 5 at 1/20000 hz, livelock removed
(probe0:sbp0:0:0:0): error 22
(probe0:sbp0:0:0:0): Unretryable Error
(probe1:sbp0:0:1:0): error 22
(probe1:sbp0:0:1:0): Unretryable Error
(probe2:sbp0:0:2:0): error 22
(probe2:sbp0:0:2:0): Unretryable Error
(probe3:sbp0:0:3:0): error 22
(probe3:sbp0:0:3:0): Unretryable Error
(probe4:sbp0:0:4:0): error 22
(probe4:sbp0:0:4:0): Unretryable Error
(probe5:sbp0:0:5:0): error 22
(probe5:sbp0:0:5:0): Unretryable Error
(probe6:sbp0:0:6:0): error 22
(probe6:sbp0:0:6:0): Unretryable Error
pass0 at ata4 bus 0 target 0 lun 0
pass0: <TSSTcorp CDDVDW SH-S223F SB00> Removable CD-ROM SCSI-0 device
pass0: 3.300MB/s transfers
pass1 at ata6 bus 0 target 0 lun 0
pass1: <LITE-ON DVD SOHD-167T 9S19> Removable CD-ROM SCSI-0 device
pass1: 3.300MB/s transfers
bootdev: a0200000 type=0 unit=0 slice=2 part=0 major=3
Mounting root from ufs:/dev/ad10s1a
cd0 at ata4 bus 0 target 0 lun 0
cd0: <TSSTcorp CDDVDW SH-S223F SB00> Removable CD-ROM SCSI-0 device
cd0: 3.300MB/s transfers
cd0: cd present [2295104 x 2048 byte records]
(cd1:ata6:0:0:0): error 6
(cd1:ata6:0:0:0): Unretryable Error
cd1 at ata6 bus 0 target 0 lun 0
cd1: <LITE-ON DVD SOHD-167T 9S19> Removable CD-ROM SCSI-0 device
cd1: 3.300MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Medium not present
ad10s1: type 0xa5, start 63, end = 586072367, size 586072305 : OK
start_init: trying /sbin/init
ad4s1: type 0xa5, start 63, end = 490234751, size 490234689 : OK
ad4s1: type 0xa5, start 63, end = 490234751, size 490234689 : OK

Files

atapicam-dma-workaround.patch (1.12 KB) atapicam-dma-workaround.patch

hasso, 11/16/2008 05:37 PM

Actions

Copy link

Updated by vince.dragonfly over 15 years ago

I was a bit surprised that I saw no replies to this. Here is my 2 cents
worth.

After having just bought a new SATA DVD burner and SATA card I ran in
this same problem and posted about it back on Jul 13, 2008 just before
the 2.0 release. I finally ended up buying another new non-SATA burner
in order to be able use the machine. Matt said he was pretty sure this
is an issue with the NATA driver. Hasso Tepper said he has seen that
many times and thinks it is a bug in the hardware. I don't think it is
since we have encountered it with various different hardware.

Also, we tested with the freebsd-7.0 live file system CD on one of our
machines and it worked fine. No livelock or other error messages.

To repeat some of my earlier posting on the subject, we have tested on
two different Intel machines, and an AMD64 machine, with an add on PCI
SiI 3512 SATA150 controller card. We also tested with the on board VIA
6420 SATA150 controller on the AMD64 machine. The problem exists in all
cases. We have also tested with 3 different SATA CD drives.

In addition, we had the same problem with a friends laptop (I don't
remember the type) which had an SATA DVD, causing us to not be able to
run DFBSD on his laptop.

We have found no cases where SATA optical drives have been able to run
on Dragonfly with hardware available to us.

With SATA drives becoming dominant this is becoming a serious show
stopper bug. It is concerning that it is lingering for so long. I hope
this becomes a priority.

Actions

Copy link

Updated by hasso over 15 years ago

Please test this patch.

Actions

Copy link

Updated by steve over 15 years ago

Hi,

It nearly works - I booted with atapicam and no atapicd, burned a
disc and read it back with DMA on with no troubles at all. Then I tried
burning a second disc and the interrupt storm started up just like before
with the livelock going on and off.

On Sun, 16 Nov 2008 17:37:01 -0000
Hasso Tepper <bugs@lists.dragonflybsd.org> wrote:

Actions

Copy link

Updated by hasso over 15 years ago

It might be different issue :(. What software you used to burn disc?

Actions

Copy link

Updated by steve over 15 years ago

On Mon, 17 Nov 2008 00:30:26 +0200
Hasso Tepper <hasso@estpak.ee> wrote:

I used wodim, I can try cdrecord.

Actions

Copy link

Updated by hasso over 15 years ago

Please test HEAD.

Actions

Copy link

Updated by hasso over 15 years ago

Follow up ...

My SATA CD/DVD writers fine now for reading data at least. Ie. I can
install DragonFly with all these.

The main part of fix I committed today was to disable DMA in atapicam
for all commands except READ_* and WRITE_*. It isn't correct fix of
course, but rather workaround. My (rather wild) guess is that alignment
is the real problem. Little googling gives some hints that for SATA
ATAPI DMA alignment padding DMA transfers to the 4 bytes boundary is
required, but the current ATA code only quarantees 2 bytes boundary.
I haven't investigated it too closely though and don't have time for
that now.
[See http://osdir.com/ml/ide/2005-07/msg00261.html for example.]

Cdrecord/wodim hanging seems to be a different issue. Attempting to
write second DVD (yes, the first one works) gives me this:
Nov 17 13:33:09 hasso sudo: hasso : TTY=ttyp6 ; PWD=/home/hasso ;
USER=root ; COMMAND=/usr/pkg/bin/cdrecord -v test.img
Nov 17 13:33:10 hasso kernel: acd0: FAILURE - READ_BUFFER ILLEGAL
REQUEST asc=0x24 ascq=0x00
Nov 17 13:33:10 hasso kernel: acd0: FAILURE - READ_BUFFER ILLEGAL
REQUEST asc=0x24 ascq=0x00
Nov 17 13:33:10 hasso kernel: ata4: FAILURE - non aligned DMA transfer
attempted
Nov 17 13:33:10 hasso kernel: acd0: setting up DMA failed

Actions

Copy link

Updated by steve over 15 years ago

Hi,

Same result on HEAD as with the patch - interrupt storm starts with
the second burn and continues as long as something tries to talk to the
drive. This is a big improvement over the original state of affairs where
the interrupt storm started during booting and didn't go away at all. It
may well be enough for some chipsets - wider testing is I think in order.

Also I get interrupt storms if I boot with atapicd enabled and no
atapicam whether or not I have DMA enabled.

I now have a hardware workaround (just arrived in the post) in the
shape of a bi-directional PATA/SATA adaptor but I'll happily test any
patches or updates.

Thank you very much for looking at this.

On Mon, 17 Nov 2008 07:55:03 -0000
Hasso Tepper <bugs@lists.dragonflybsd.org> wrote:

Actions

Copy link

Updated by vince.dragonfly over 15 years ago

Hi Hasso. Thanks for working on the problem.

Here is our results from testing HEAD.

It definitely works a lot better than before. We were able to write
to CDRW's and DVD's using cdrecord. Burning a second disc also worked.
We did not get the interrupt storm like Steve did.

The tests were run on an Intel processor with a SiI 3512 SATA150 add on card.
Cdrecord-Clone 2.01.01a04

Even though it works, there were some error messages.

These are from dmesg.

acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
   acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00

atapci0: &lt;SiI 3512 SATA150 controller&gt; port 0xd400-0xd40f,0xd480-0xd483,0xd800-0
  xd807,0xd880-0xd883,0xdc00-0xdc07 mem 0xff8ffc00-0xff8ffdff irq 10 at device 0.0
   on pci1
   ata2: &lt;ATA channel 0&gt; on atapci0
   intr 10 at 40001/40000 hz, livelocked limit engaged!
   intr 10 at 0/20000 hz, livelock removed
   acd0: DVDR &lt;TSSTcorp DVD+/-RW TS-H653A/D400&gt; at ata2-master SATA150
   ata3: &lt;ATA channel 1&gt; on atapci0

Which all seem to have been generated at boot time. Notice there was one
pair of livelock limit messages, but that was it.

There were also some errors generated on the console when writing.

CDRW write errors =================
acd0: FAILURE - READ_DVD_STRUCTURE ILLEGAL REQUEST asc=0x30 ascq=0x02
acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - REZERO ILLEGAL REQUEST asc=0x20 ascq=0x00
acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00

DVD write errors ================
acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 asc q=0x00
acd0: FAILURE - REZERO ILLEGAL REQUEST asc=0x20 ascq=0x00
acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00

This is the first time we have even been able to boot up a machine on Dragonfly
with a SATA optical drive. So this is a big step in the right direction :-).
I hope this information helps.

Actions

Copy link

#10

Updated by hasso over 15 years ago

These are debug messages and can be ignored. I left this in to get more
info about storms/locks Steve and me is seeing. Especially cdrecord and
friends are testing many commands on drives and some of them just fail
because drive doesn't support them. I'll switch this back of once we have
issues resolved.

Yeah, seems that it was able to restore. Good.

Many thanks to you for testing! ;)

Actions

Copy link

#11

Updated by hasso over 15 years ago

To clarify the state of the bug ...

The issue with SATA CD/DVD devices causing interrupt storms etc are solved
in both master and 2.0 branch. There are still issue with recording
though:

acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - READ_BUFFER ILLEGAL
ata4: FAILURE - non aligned DMA transfer
acd0: setting up DMA failed

I think that it's not specific to SATA CD/DVD writers though. And I
thought Matt already fixed the issues with non aligned DMA transfers? Or
was it in different path?

I don't have time and knowledge to work on this, but I think that it's
showstopper for 2.2. Any takers?

Actions

Copy link

#12

Updated by dillon over 15 years ago

:To clarify the state of the bug ...
:
:The issue with SATA CD/DVD devices causing interrupt storms etc are solved
:in both master and 2.0 branch. There are still issue with recording
:though:
:
:acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00
:acd0: FAILURE - READ_BUFFER ILLEGAL
:ata4: FAILURE - non aligned DMA transfer
:acd0: setting up DMA failed
:
:I think that it's not specific to SATA CD/DVD writers though. And I
:thought Matt already fixed the issues with non aligned DMA transfers? Or
:was it in different path?

I did for accesses via physical devices.

What action was performed to cause this particular error?  I do have
    a SATA CD/DVD I can test with.

-Matt
                    Matthew Dillon 
                    &lt;dillon@backplane.com&gt;

:I don't have time and knowledge to work on this, but I think that it's
:showstopper for 2.2. Any takers?
:
:--
:Hasso Tepper

Actions

Copy link

#13

Updated by steve over 15 years ago

Hi,

I'm not so sure about this - I just tried your 19 Nov version (I
didn't notice the commit earlier sorry), it gives me an interrupt storm on
boot while the 17 Nov version (DMA only on read/write) does not - but will
only burn once.

There was an issue with non aligned DMA transfers that Matt fixed
(with changes to physio() around on 10 August). From the commit message it
allocates a bounce buffer if the buffer is not 16 byte aligned - I don't
understand the code well enough to see how the bounce buffer is aligned but
presumably it is at least 16 byte.

On Mon, 1 Dec 2008 15:16:05 +0200
Hasso Tepper <hasso@estpak.ee> wrote:

Actions

Copy link

#14

Updated by hasso over 15 years ago

It happens for me if I start burning the second DVD (using DVD-R disks)
iso image with cdrecord (just using "cdrecord -v image.iso"). Burning the
first DVD image after boot works fine, so does burning to CD (tested only
RW) images repeatedly.

As far as I understand it, the same happens in Steve's machine. Except
that it doesn't end with interrupt storm for me though. But cdrecord
can't be killed any more and I have to reboot to make drive usable again.

Actions

Copy link

#15

Updated by dillon over 15 years ago

I picked up a HP SATA DVD Writer today to play and so far it has worked
flawlessly with the latest HEAD. I was able to format and write DVD-RW's,
and rewrite them half a dozen times without error. I put in a DVD-R and
burned it (with dfly.iso) no problem. I put in a second DVD-R and burned
IT no problem too.

I did get a bunch of transient errors from boot and from cdrecord trying
    various types of commands, but it didn't stop it from burning the DVD.

On boot:

acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
Mounting root from ufs:/dev/ad6s1a
cd0 at ata2 bus 0 target 0 lun 0
cd0: <HP DVD Writer 1070r RH22> Removable CD-ROM SCSI-0 device
cd0: 3.300MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed

The transient errors from burning the DVD-RW:

acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x30 ascq=0x02
acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - WRITE_BIG ILLEGAL REQUEST asc=0x30 ascq=0x06
acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00

The transient errors from burning the DVD-R:

The drive identification, box labeled "HP dvd1070i".  Id from
    -scanbus:

2,0,0   200) 'HP      ' 'DVD Writer 1070r' 'RH22' Removable CD-ROM

-Matt

Actions

Copy link

#16

Updated by steve over 15 years ago

On Wed, 10 Dec 2008 23:38:08 -0000
Matthew Dillon <bugs@lists.dragonflybsd.org> wrote:

Seems I didn't try hard enough with the latest version of the code.
At boot I get reams of:

Dec 11 12:05:03 df1 kernel: intr 10 at 40001/40000 hz, livelocked limit
engaged! Dec 11 12:05:04 df1 kernel: intr 10 at 8604/20000 hz, livelock
removed

With intermittent:

Dec 11 12:05:04 df1 kernel: unknown: FAILURE - INQUIRY timed out

Early on there are messages like:

Dec 11 11:47:05 df1 kernel: WARNING waiting for the following device to
fini sh configuring:
Dec 11 11:47:05 df1 kernel: xpt: func=0xc0146dd9 arg=0

After a few of these there is:

Dec 11 11:47:05 df1 kernel: Giving up, interrupt routing is probably hosed

Eventually however (and this is the bit I didn't wait long enough
for last time round) I get:

Dec 11 12:05:04 df1 kernel: cd0 at ata4 bus 0 target 0 lun 0
Dec 11 12:05:04 df1 kernel: cd0: <TSSTcorp CDDVDW SH-S223F SB00> Removable
CD-ROM SCSI-0 device Dec 11 12:05:04 df1 kernel: cd0: 3.300MB/s transfers
Dec 11 12:05:04 df1 kernel: cd0: cd present [2295104 x 2048 byte records]
Dec 11 12:05:04 df1 kernel: cd1 at ata6 bus 0 target 0 lun 0
Dec 11 12:05:04 df1 kernel: cd1: <LITE-ON DVD SOHD-167T 9S19> Removable
CD-ROM SCSI-0 device Dec 11 12:05:04 df1 kernel: cd1: 3.300MB/s transfers
Dec 11 12:05:04 df1 kernel: cd1: Attempt to query device size failed: NOT
READY, Medium not present

The livelock messages go away - and once I reenable DMA on atapi
(it gets turned off somewhere along the line in the boot process)
everything works fine. It just takes 15-20 minutes to get there.

I'm using an Asus A8V Deluxe motherboard - dmesg | grep ata

atapci0: <Promise PDC20378 SATA150 controller> port 0x8800-0x887f,0x9000-0x900f,0x9400-0x943f mem 0xfb700000-0xfb71ffff,0xfb800000-0xfb800fff irq 5 at device 8.0 on pci0
ata2: <ATA channel 0> on atapci0
ad4: 239372MB <Maxtor 6Y250M0 YAR51HW0> at ata2-master SATA150
ata3: <ATA channel 1> on atapci0
ata4: <ATA channel 2> on atapci0
ad8: 117246MB <Maxtor 6Y120P0 YAR41BW0> at ata4-master UDMA133
atapci1: <VIA 6420 SATA150 controller> port 0xa800-0xa8ff,0xb000-0xb00f,0xb400-0xb403,0xb800-0xb807,0xc000-0xc003,0xc400-0xc407 irq 10 at device 15.0 on pci0
ata5: <ATA channel 0> on atapci1
ad10: 286168MB <Seagate ST3300622AS 3.AAE> at ata5-master SATA150
ata6: <ATA channel 1> on atapci1
atapci2: <VIA 8237 UDMA133 controller> port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
ata0: <ATA channel 0> on atapci2
ata1: <ATA channel 1> on atapci2
cd0 at ata4 bus 0 target 0 lun 0
cd1 at ata6 bus 0 target 0 lun 0

The reuse of ata4 seems odd - related or irrelevant ?

Actions

Copy link

#17

Updated by jdc over 15 years ago

I'm trying very hard to stay out of this discussion because I'm in no
way familiar with DFBSD's changes to ATA and ATAPI. I am, however,
quite familiar with ATA/SATA on FreeBSD. One thing stands out here like
a sore thumb:

Your SATA CD/DVD drive is connected to a Promise RAID controller. I
have never seen this work, and vendors even go so far to state "DO NOT
HOOK UP CD/DVD DRIVES TO RAID CONTROLLERS". The RAID controller is
probably freaking out because it doesn't know how to speak ATAPI
properly.

Do you see the same problem if you hook the SATA CD/DVD drive to your
VIA SATA controller?

Actions

Copy link

#18

Updated by steve over 15 years ago

On Thu, 11 Dec 2008 04:50:51 -0800
Jeremy Chadwick <jdc@parodius.com> wrote:

It's not actually connected to the Promise, it's connected to the
VIA controller plugged in right next to the Seagate drive. The Promise
controller has ad4 (SATA) and ad8 (PATA) connected to it, the VIA has ad10
(SATA), cd0 (SATA) and cd1 (PATA) connected to it. I am deeply suspicious
about the mention of ata4 for two different devices (ad8 and cd0) connected
to two different controllers.

It doesn't even get recognised as being present if I connect it to
the Promise RAID controller, I made that mistake when I first connected it.

Actions

Copy link

#19

Updated by steve over 15 years ago

On Thu, 11 Dec 2008 12:24:08 +0000
"Steve O'Hara-Smith" <steve@sohara.org> wrote:

I spoke too soon - attempting to burn a DVD-R (which wodim decided
to do at 20X) provoked a return of the livelock messages which stopped
when I killed wodim, however the wodim process did not die (present in ps
and top, but kill claimed it didn't exist after the first kill). The drive
wouldn't stop spinning and the disc was of course a coaster (plenty more
where that came from).

This really does seem to be badly wrong - cd0 should be at ata6 and
cd1 should be at ata0

Actions

Copy link

#20

Updated by jdc over 15 years ago

So, part of the complexity is that your Promise controller offers both
SATA and PATA.

Well, the breakdown is this:

atapci0 = Promise FastTrak RAID
--> ata2 (SATA)
--> ad4 = Maxtor 6Y250M0
--> ata3 (SATA)
--> ata4 (PATA)
--> ad8 (master?) = Maxtor 6Y120P0
--> cd0 (slave?) = TSSTcorp CDDVDW SH-S223F SB00

atapci1 = VIA 6420 SATA
--> ata5
--> ad10 = Seagate ST3300622AS
--> ata6
--> cd1 = LITE-ON DVD SOHD-167T 9S19

atapci2 = VIA 8237 ATA133
--> ata0
--> ata1

cd0 showing up attached to ata4 (somehow) is indicative of a problem.

It might also help if you could provide "atacontrol list" output. I
assume DFBSD has atacontrol.

Makes perfect sense.

Actions

Copy link

#21

Updated by steve over 15 years ago

On Thu, 11 Dec 2008 07:15:53 -0800
Jeremy Chadwick <jdc@parodius.com> wrote:

Yes the Promise controller has two SATA ports and one PATA port.
I'm using the PATA and one of the SATA ports. The VIA controller has two
PATA and two SATA ports, I'm using both SATA and one of the PATA.

So far so good

But this is not in fact connected to ata4 - it's connected to ata6.

Yep but ...

This is in fact connected to ata1 (I thought it was ata0 but it's ata1)

Here it is:

ATA channel 0:
Master: no device present
Slave: no device present
ATA channel 1:
Master: acd1 <LITE-ON DVD SOHD-167T/9S19> ATA/ATAPI revision 5
Slave: no device present
ATA channel 2:
Master: ad4 <Maxtor 6Y250M0/YAR51HW0> Unknown serial ATA version
Slave: no device present
ATA channel 3:
Master: no device present
Slave: no device present
ATA channel 4:
Master: ad8 <Maxtor 6Y120P0/YAR41BW0> ATA/ATAPI revision 7
Slave: no device present
ATA channel 5:
Master: ad10 <ST3300622AS/3.AAE> Serial ATA v1.0
Slave: no device present
ATA channel 6:
Master: acd0 <TSSTcorp CDDVDW SH-S223F/SB00> Serial ATA v1.0
Slave: no device present

This listing matches where I have things plugged in.

Actions

Copy link

#22

Updated by dillon over 15 years ago

I couldn't find any SATA Lite-On's DVD writers at Best Buy. I do have
a lite-on SATA CD reader. I will hop onto newegg and get one.

Could you please tell me exactly which brand of lite-on you have?  I
    realize it could be (even likely to be) the controller and not the DVD
    unit but this way we can be sure, and these things are so cheap it
    doesn't really matter how wasteful I am getting units to test with.

--

I don't have a promise controller to test on either, unfortunately.
    At least I don't think I have one.  I never use those MB soft-raid
    features.  I wonder if there is an internal card solution that is
    reliable for people with those MB controllers.

I do appreciate all the input, thanks Jeremy, and I'm actually rather
    pround that DragonFly isn't crashing outright from these interrupt,
    driver, and hardware issues :-)

-Matt

Actions

Copy link

#23

Updated by steve over 15 years ago

On Fri, 12 Dec 2008 19:55:01 -0000
Matthew Dillon <bugs@lists.dragonflybsd.org> wrote:

The SATA burner is a TSSTCorp  SH-S223F - rebranded Samsung. The
Lite-On is just a PATA reader.

I thought you had an A8V based box - the SATA burner isn't
connected to the Promise controller at all it's connected to the VIA 6420
controller, but atapicam is reporting the wrong channel. See the post
where I put the atacontrol list in reply to Jeremy, atacontrol gets it
right.

The Promise controller is driving a couple of hard discs, one of
them carrying my hammer filesystem - no RAID.

It even burns discs despite them :)

Actions

Copy link

#24

Updated by dillon over 15 years ago

: I thought you had an A8V based box - the SATA burner isn't
:connected to the Promise controller at all it's connected to the VIA 6420
:controller, but atapicam is reporting the wrong channel. See the post
:where I put the atacontrol list in reply to Jeremy, atacontrol gets it
:right.
:
: The Promise controller is driving a couple of hard discs, one of
:them carrying my hammer filesystem - no RAID.

Ha.  I don't even know what all my boxes are.  Lets see.  I have
    three towers and six or seven shuttle cubes.  Two of the towers have
    A8N-SLI MB's, the third tower I don't know what it has.  The shuttle's
    are mostly AMD X2 based.

The A8N-SLI's have VIA 6420 (SATA) and 8237's (UDMA133).

It's possible that the soft RAID controllers are disabled in the
    BIOS on the A8N's.  I'll play with one of them and see if I can find it.

-Matt

Actions

Copy link

#25

Updated by hasso over 15 years ago

There is no solution yet, but I think that I already understand what's
going on. The problem is that the fix I committed int atapi-cam doesn't
have any effect in case of SATA controller in AHCI (or RAID) mode, so
switching IDE controller into IDE or legacy mode might help.

I still have two questions ...

How non aligned DMA transfer reaches this level at all. Should higher
layers try to avoid this?
Where and how requests should be padded to be aligned to 4 bytes (it's
required for SATA ATAPI only?)?

Actions

Copy link

#26

Updated by corecode over 15 years ago

It is an interesting question on where to put this alignment requirement.
Sephe argued that our busdma functions already provide an alignment
tool, so maybe it is just being handled not well enough. Apart from that,
I think the ATA driver should take care of that and not the kernel.

cheers
simon

Actions

Copy link

#27

Updated by steve over 15 years ago

On Tue, 16 Dec 2008 22:35:13 -0000
Hasso Tepper <bugs@lists.dragonflybsd.org> wrote:

This RAID thing is an illusion caused by atapicam misreporting the
channel - my SATA drive is not connected to a RAID controller it is
connected to the VIA 6420 SATA controller - which is also not an AHCI
controller (at least it does not report as AHCI). The misreporting becomes
clear when I have atapi-cd loaded as well viz:

acd0: DVDR <TSSTcorp CDDVDW SH-S223F/SB00> at ata6-master SATA150
acd1: DVDROM <LITE-ON DVD SOHD-167T/9S19> at ata1-master UDMA33
...
cd0 at ata4 bus 0 target 0 lun 0
cd0: <TSSTcorp CDDVDW SH-S223F SB00> Removable CD-ROM SCSI-0 device
cd0: 3.300MB/s transfers
cd0: cd present [2295104 x 2048 byte records]
cd1 at ata6 bus 0 target 0 lun 0
cd1: <LITE-ON DVD SOHD-167T 9S19> Removable CD-ROM SCSI-0 device
cd1: 33.000MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Medium not present

Actions

Copy link

#28

Updated by steve over 15 years ago

On Tue, 16 Dec 2008 22:35:13 -0000
Hasso Tepper <bugs@lists.dragonflybsd.org> wrote:

One more data point - I get the boot time interrupt storm with or
without atapi-dma enabled if I load both natapi-cd and natapi-cam. I also
get it without natapi-cd but then only if atapi-dma is enabled. Is there
some common code path that is brought into play by either enabling
atapi-dma or loading natapi-cam ?

Actions

Copy link

#29

Updated by steve about 15 years ago

Hi,

At least for me this problem has been cured by your changes
(Simon) for issue1240. Nice work much appreciated!

If nobody else is still having problems (Hasso ???) I think
you can mark this as fixed in 9f2212d too.

On Tue, 16 Dec 2008 23:47:55 +0100
"Simon 'corecode' Schubert" <corecode@fs.ei.tum.de> wrote:

Actions

Copy link

#30

Updated by hasso about 15 years ago

My problems were fixed even before that - with 969f6a6d.

Actions

Copy link

Also available in: Atom PDF

Project

General

Profile

DragonFlyBSD

Bug #1158

Problems with a SATA DVD burner

Updated by vince.dragonfly over 15 years ago

Updated by hasso over 15 years ago

Updated by steve over 15 years ago

Updated by hasso over 15 years ago

Updated by steve over 15 years ago

Updated by hasso over 15 years ago

Updated by hasso over 15 years ago

Updated by steve over 15 years ago

Updated by vince.dragonfly over 15 years ago

Updated by hasso over 15 years ago

Updated by hasso over 15 years ago

Updated by dillon over 15 years ago

Updated by steve over 15 years ago

Updated by hasso over 15 years ago

Updated by dillon over 15 years ago

Updated by steve over 15 years ago

Updated by jdc over 15 years ago

Updated by steve over 15 years ago

Updated by steve over 15 years ago

Updated by jdc over 15 years ago

Updated by steve over 15 years ago

Updated by dillon over 15 years ago

Updated by steve over 15 years ago

Updated by dillon over 15 years ago

Updated by hasso over 15 years ago

Updated by corecode over 15 years ago

Updated by steve over 15 years ago

Updated by steve over 15 years ago

Updated by steve about 15 years ago

Updated by hasso about 15 years ago