* Re: About forcing 32bit DMA patch for AMD690G(SB600)
@ 2008-01-29 20:10 Kelly Anderson
0 siblings, 0 replies; 15+ messages in thread
From: Kelly Anderson @ 2008-01-29 20:10 UTC (permalink / raw)
To: linux-ide
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Good news! (so far)
I've got a M2A-VM HDMI with 4 Gigs, some of that is mapped over the 4G
barrier. I patched the 2.6.24 kernel to allow the SB600 to do 64-bit
DMA. Then I ran a torture test overnight, copying the /usr tree 30
times while at the same time looping through a kernel compile 30 times.
No abnormal messages at all. Dmesg is clean, syslog is clean.
On another note I think Asus, or more accurately their BIOS vendor, has
improved the M2A-VM BIOS quite a bit lately. I'm using
version 1603. FlashRom from coreboot.org will successfully flash the
BIOS on the M2A-VM's! No more DOS/Windows required for BIOS updates on
this board.
[-- Attachment #2: ahci_c_sb600_dont_disable_64_bit.patch --]
[-- Type: text/plain, Size: 496 bytes --]
--- ./drivers/ata/ahci.c.orig 2008-01-24 15:58:37.000000000 -0700
+++ ./drivers/ata/ahci.c 2008-01-29 01:30:25.567532947 -0700
@@ -423,8 +423,11 @@ static const struct ata_port_info ahci_p
},
/* board_ahci_sb600 */
{
+/*
AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL |
AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_PMP),
+*/
+ AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL | AHCI_HFLAG_NO_PMP),
.flags = AHCI_FLAG_COMMON,
.link_flags = AHCI_LFLAG_COMMON,
.pio_mask = 0x1f, /* pio0-4 */
[-- Attachment #3: dmesg.txt --]
[-- Type: text/plain, Size: 18627 bytes --]
Linux version 2.6.24-myKsmp (kelly@speedy) (gcc version 4.1.2) #1 SMP Tue Jan 29 01:41:13 MST 2008
Command line: BOOT_IMAGE=myK-2.6.24 ro root=803
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000d7ee0000 (usable)
BIOS-e820: 00000000d7ee0000 - 00000000d7ee3000 (ACPI NVS)
BIOS-e820: 00000000d7ee3000 - 00000000d7ef0000 (ACPI data)
BIOS-e820: 00000000d7ef0000 - 00000000d7f00000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
Entering add_active_range(0, 0, 159) 0 entries of 256 used
Entering add_active_range(0, 256, 884448) 1 entries of 256 used
Entering add_active_range(0, 1048576, 1179648) 2 entries of 256 used
end_pfn_map = 1179648
DMI 2.4 present.
ACPI: RSDP 000F82B0, 0024 (r2 ATI )
ACPI: XSDT D7EE3100, 004C (r1 ATI ASUSACPI 42302E31 AWRD 0)
ACPI: FACP D7EE8500, 00F4 (r3 ATI ASUSACPI 42302E31 AWRD 0)
ACPI: DSDT D7EE3280, 5213 (r1 ATI ASUSACPI 1000 MSFT 3000000)
ACPI: FACS D7EE0000, 0040
ACPI: SSDT D7EE8740, 0248 (r1 PTLTD POWERNOW 1 LTP 1)
ACPI: HPET D7EE8A00, 0038 (r1 ATI ASUSACPI 42302E31 AWRD 98)
ACPI: MCFG D7EE8A80, 003C (r1 ATI ASUSACPI 42302E31 AWRD 0)
ACPI: APIC D7EE8640, 0084 (r1 ATI ASUSACPI 42302E31 AWRD 0)
Entering add_active_range(0, 0, 159) 0 entries of 256 used
Entering add_active_range(0, 256, 884448) 1 entries of 256 used
Entering add_active_range(0, 1048576, 1179648) 2 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
DMA32 4096 -> 1048576
Normal 1048576 -> 1179648
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0: 0 -> 159
0: 256 -> 884448
0: 1048576 -> 1179648
On node 0 totalpages: 1015423
DMA zone: 56 pages used for memmap
DMA zone: 1274 pages reserved
DMA zone: 2669 pages, LIFO batch:0
DMA32 zone: 14280 pages used for memmap
DMA32 zone: 866072 pages, LIFO batch:31
Normal zone: 1792 pages used for memmap
Normal zone: 129280 pages, LIFO batch:31
Movable zone: 0 pages used for memmap
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, 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.
Setting APIC routing to flat
ACPI: HPET id: 0x8200 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
swsusp: Registered nosave memory region: 00000000d7ee0000 - 00000000d7ee3000
swsusp: Registered nosave memory region: 00000000d7ee3000 - 00000000d7ef0000
swsusp: Registered nosave memory region: 00000000d7ef0000 - 00000000d7f00000
swsusp: Registered nosave memory region: 00000000d7f00000 - 00000000e0000000
swsusp: Registered nosave memory region: 00000000e0000000 - 00000000f0000000
swsusp: Registered nosave memory region: 00000000f0000000 - 00000000fec00000
swsusp: Registered nosave memory region: 00000000fec00000 - 0000000100000000
Allocating PCI resources starting at f1000000 (gap: f0000000:ec00000)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PERCPU: Allocating 33016 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 998021
Kernel command line: BOOT_IMAGE=myK-2.6.24 ro root=803
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
Marking TSC unstable due to TSCs unsynchronized
time.c: Detected 2299.910 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Checking aperture...
CPU 0: aperture @ 8000000 size 32 MB
Aperture too small (32 MB)
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 8000000
Memory: 3920016k/4718592k available (3134k kernel code, 141516k reserved, 1176k data, 248k init)
SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Calibrating delay using timer specific routine.. 4604.00 BogoMIPS (lpj=7670412)
Security Framework initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
ACPI: Core revision 20070126
Using local APIC timer interrupts.
APIC timer calibration result 12499501
Detected 12.499 MHz APIC timer.
SMP alternatives: switching to SMP code
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 4601.53 BogoMIPS (lpj=7666456)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
AMD Athlon(tm) X2 Dual Core Processor BE-2400 stepping 02
Brought up 2 CPUs
CPU0 attaching sched-domain:
domain 0: span 3
groups: 1 2
CPU1 attaching sched-domain:
domain 0: span 3
groups: 2 1
net_namespace: 120 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: No mmconfig possible on device 00:18
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:14.4
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE7._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnpacpi: exceeded the max number of mem resources: 12
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI-DMA: Disabling AGP.
PCI-DMA: aperture base @ 8000000 size 65536 KB
PCI-DMA: using GART IOMMU.
PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
ACPI: RTC can wake from S4
system 00:01: ioport range 0x4100-0x411f has been reserved
system 00:01: ioport range 0x228-0x22f has been reserved
system 00:01: ioport range 0x40b-0x40b has been reserved
system 00:01: ioport range 0x4d6-0x4d6 has been reserved
system 00:01: ioport range 0xc00-0xc01 has been reserved
system 00:01: ioport range 0xc14-0xc14 has been reserved
system 00:01: ioport range 0xc50-0xc52 has been reserved
system 00:01: ioport range 0xc6c-0xc6d has been reserved
system 00:01: ioport range 0xc6f-0xc6f has been reserved
system 00:01: ioport range 0xcd0-0xcd1 has been reserved
system 00:01: ioport range 0xcd2-0xcd3 has been reserved
system 00:01: ioport range 0xcd4-0xcdf has been reserved
system 00:01: ioport range 0x4000-0x40fe has been reserved
system 00:01: ioport range 0x4210-0x4217 has been reserved
system 00:01: ioport range 0xb00-0xb0f has been reserved
system 00:01: ioport range 0xb10-0xb1f has been reserved
system 00:07: ioport range 0x4d0-0x4d1 has been reserved
system 00:07: ioport range 0x220-0x225 has been reserved
system 00:09: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:0a: iomem range 0xcd600-0xcffff has been reserved
system 00:0a: iomem range 0xf0000-0xf7fff could not be reserved
system 00:0a: iomem range 0xf8000-0xfbfff could not be reserved
system 00:0a: iomem range 0xfc000-0xfffff could not be reserved
system 00:0a: iomem range 0xd7ef0000-0xd7feffff could not be reserved
system 00:0a: iomem range 0xfed00000-0xfed000ff has been reserved
system 00:0a: iomem range 0xd7ee0000-0xd7efffff could not be reserved
system 00:0a: iomem range 0xffff0000-0xffffffff has been reserved
system 00:0a: iomem range 0x0-0x9ffff could not be reserved
system 00:0a: iomem range 0x100000-0xd7edffff could not be reserved
system 00:0a: iomem range 0xd7ff0000-0xdffeffff has been reserved
system 00:0a: iomem range 0xfec00000-0xfec00fff has been reserved
PCI: Bridge: 0000:00:01.0
IO window: c000-cfff
MEM window: fdb00000-fdcfffff
PREFETCH window: f0000000-f7ffffff
PCI: Bridge: 0000:00:07.0
IO window: d000-dfff
MEM window: fda00000-fdafffff
PREFETCH window: fdf00000-fdffffff
PCI: Bridge: 0000:00:14.4
IO window: b000-bfff
MEM window: fde00000-fdefffff
PREFETCH window: fdd00000-fddfffff
PCI: Setting latency timer of device 0000:00:07.0 to 64
NET: Registered protocol family 2
Time: acpi_pm clocksource has been installed.
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1201571463.380:1): initialized
Total HugeTLB memory allocated, 0
JFS: nTxBlock = 8192, nTxLock = 65536
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Boot video device is 0000:01:05.0
PCI: Setting latency timer of device 0000:00:07.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:07.0:pcie00]
Allocate Port Service[0000:00:07.0:pcie03]
vesafb: framebuffer at 0xf0000000, mapped to 0xffffc20010680000, using 1536k, total 16384k
vesafb: mode is 1024x768x8, linelength=1024, pages=18
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
hpet_acpi_add: no address or irqs in _CRS
Linux agpgart interface v0.102
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ahci 0000:00:12.0: version 3.0
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: 64bit ncq sntf ilck pm led clo pio slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 22
ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 22
ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 22
ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 22
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: ST31000340AS, AD14, max UDMA/133
ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATAPI: TSSTcorp CDDVDW SH-S203N, SB01, max UDMA/100, ATAPI AN
ata2.00: configured for UDMA/100
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access ATA ST31000340AS AD14 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors (1000205 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors (1000205 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 >
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: CD-ROM TSSTcorp CDDVDW SH-S203N SB01 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 16
scsi4 : pata_atiixp
scsi5 : pata_atiixp
ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xe400 irq 14
ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xe408 irq 15
usbmon: debugfs is not available
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
EDAC MC: Ver: 2.1.0 Jan 29 2008
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
UDF-fs: No VRS found
VFS: Mounted root (jfs filesystem) readonly.
Freeing unused kernel memory: 248k freed
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 1:0:0:0: Attached scsi generic sg1 type 5
ACPI: PCI Interrupt 0000:00:13.5[D] -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:13.5: EHCI Host Controller
ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.5: debug port 1
ehci_hcd 0000:00:13.5: irq 19, io mem 0xfe029000
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ehci_hcd 0000:00:13.5: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
input: PC Speaker as /devices/platform/pcspkr/input/input1
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 16, io mem 0xfe02e000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.1[B] -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 17, io mem 0xfe02d000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.2[C] -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.2: OHCI Host Controller
ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:13.2: irq 18, io mem 0xfe02c000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI: PCI Interrupt 0000:00:13.3[B] -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.3: OHCI Host Controller
ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.3: irq 17, io mem 0xfe02b000
rtc_cmos: probe of 00:04 failed with error -16
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: Thermal Zone [THRM] (40 C)
ACPI: Fan [FAN] (on)
ACPI: PCI Interrupt 0000:00:13.4[C] -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.4: OHCI Host Controller
ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.4: irq 18, io mem 0xfe02a000
input: Power Button (FF) as /devices/virtual/input/input2
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /devices/virtual/input/input3
ACPI: Power Button (CM) [PWRB]
piix4_smbus 0000:00:14.0: Found 0000:00:14.0 device
ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16
r8169 Gigabit Ethernet driver 2.2LK loaded
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:02:00.0 to 64
r8169 0000:02:00.0: no MSI. Back to INTx.
eth0: RTL8168b/8111b at 0xffffc2000003e000, 00:1b:fc:1b:ac:f6, XID 38000000 IRQ 19
ACPI: PCI Interrupt 0000:03:07.0[A] -> GSI 22 (level, low) -> IRQ 22
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[22] MMIO=[fdeff000-fdeff7ff] Max Packet=[1024] IR/IT contexts=[4/8]
Adding 1951888k swap on /dev/sda2. Priority:-1 extents:1 across:1951888k
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0000000000000000]
lp: driver loaded but no devices found
[-- Attachment #4: lspci-vv.txt --]
[-- Type: text/plain, Size: 14454 bytes --]
00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
Subsystem: ASUSTeK Computer Inc. Unknown device 826d
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 64
00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 99
Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fdb00000-fdcfffff
Prefetchable memory behind bridge: 00000000f0000000-00000000f7ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: [44] HyperTransport: MSI Mapping
Capabilities: [b0] Subsystem: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
00:07.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fda00000-fdafffff
Prefetchable memory behind bridge: 00000000fdf00000-00000000fdffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express Root Port (Slot-) IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <64ns, L1 <1us
Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 4
Link: Latency L0s <64ns, L1 <1us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Root: Correctable- Non-Fatal- Fatal- PME-
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [b0] Subsystem: ASUSTeK Computer Inc. Unknown device 826d
Capabilities: [b8] HyperTransport: MSI Mapping
Capabilities: [100] Virtual Channel
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 22
Region 0: I/O ports at fc00 [size=8]
Region 1: I/O ports at f800 [size=4]
Region 2: I/O ports at f400 [size=8]
Region 3: I/O ports at f000 [size=4]
Region 4: I/O ports at ec00 [size=16]
Region 5: Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [70] #12 [0010]
00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 18
Region 0: Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 18
Region 0: Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 19
Region 0: Memory at fe029000 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+
Capabilities: [e4] Debug port
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 13)
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Region 0: I/O ports at 0b00 [size=16]
Region 1: Memory at fed00000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [b0] HyperTransport: MSI Mapping
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at e400 [size=16]
Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia
Subsystem: ASUSTeK Computer Inc. Unknown device 8249
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin ? routed to IRQ 16
Region 0: Memory at fe020000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=03, subordinate=03, sec-latency=64
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fde00000-fdefffff
Prefetchable memory behind bridge: fdd00000-fddfffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Capabilities: [80] HyperTransport: Host or Secondary Interface
!!! Possibly incomplete decoding
Command: WarmRst+ DblEnd-
Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
Link Config: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
Revision ID: 1.02
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Capabilities: [f0] #0f [0010]
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon X1200 Series (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Unknown device 826d
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f0000000 (64-bit, prefetchable) [size=128M]
Region 2: Memory at fdcf0000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at cc00 [size=256]
Region 5: Memory at fdb00000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
Subsystem: ASUSTeK Computer Inc. Unknown device 81aa
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at dc00 [size=256]
Region 2: Memory at fdaff000 (64-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at fdf00000 [disabled] [size=128K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [48] Vital Product Data
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [60] Express Endpoint IRQ 0
Device: Supported: MaxPayload 1024 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <1us, L1 unlimited
Device: AtnBtn+ AtnInd+ PwrInd+
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
Link: Latency L0s unlimited, L1 unlimited
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [84] Vendor Specific Information
Capabilities: [100] Advanced Error Reporting
Capabilities: [12c] Virtual Channel
Capabilities: [148] Device Serial Number 68-81-ec-10-00-00-00-1a
Capabilities: [154] Power Budgeting
03:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev c0) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81fe
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at fdeff000 (32-bit, non-prefetchable) [size=2K]
Region 1: I/O ports at bc00 [size=128]
Capabilities: [50] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
^ permalink raw reply [flat|nested] 15+ messages in thread* About forcing 32bit DMA patch for AMD690G(SB600)
@ 2008-01-23 7:44 Shane Huang
2008-01-24 3:53 ` Shane Huang
2008-01-25 0:21 ` Tejun Heo
0 siblings, 2 replies; 15+ messages in thread
From: Shane Huang @ 2008-01-23 7:44 UTC (permalink / raw)
To: sriharivijayaraghavan, Tejun Heo; +Cc: linux-ide, Shane Huang
[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]
Resending this mail and adding linux-ide mail list...
Quoting Tejun:
> Uh-oh, wait a bit. Nope. Until we figure out what the something else
is
> and positively verify 64bit DMA works fine, the quirk stays in.
Our HW engineer has confirmed that our SB600 SATA controller indeed has
some MSI issue, and we do not have any workaround.
The workaround "quirk_msi_intx_disable_bug" to SB700 SATA controller
can NOT work to SB600 SATA controller in my debug, while disablement to
RS690 MSI in kernel source can fix it.
As to the SB600 64 bit DMA capacity, do you have any methods to do
further
verification? I do NOT find any problem in my debug after I disabled
RS690
MSI in kernel 2.6.24-rc7.
Thanks
Best Regards
Shane
-----Original Message-----
From: Shane Huang
Sent: Wednesday, January 23, 2008 2:56 PM
To: sriharivijayaraghavan@yahoo.com.au
Cc: 'Tejun Heo'; Shane Huang
Subject: About forcing 32bit DMA patch for AMD690G(SB600)
Importance: High
Hi Srihari:
This Shane @ AMD. I'm sorry to disturb you.
I find that there is one patch which forces SB600 use 32bit DMA:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
t;h=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c
This patch was submitted by Tejun to fix one issue on your platform:
http://marc.info/?l=linux-ide&m=117810966106759&w=2
But after a discussion with our hardware engineers, Tejun(the patch
author),
and some debugging, we believe that that SB600 can support 64 bit DMA,
the root cause should be something else, while disablement to RS690 MSI
in kernel source can be the workaround.
So, we are going withdraw Tejun's patch ASAP.
I wonder whether you still have that AMD690G platform or not?
Are you able to help to do further confirmation before we withdraw it?
You can just download kernel 2.6.21.1(which was used when you reported
the bug), apply the attached disable_RS690_MSI.patch, and build the
kernel.
Please tell me if that patch can fix your issue without Tejun's patch.
This patch has been proved to work on my RS690+SB600 under Fedora7
x86_64.
You can also try my another disable_MSI_and_withdraw_32bit.patch
under linux kernel 2.6.24-rc7, to see whether this patch can fix your
issue too. This method also can work on my RS690+SB600 platform.
Thanks & waiting for your test result~~~ :-)
Best Regards
Shane
[-- Attachment #2: disable_RS690_MSI.patch --]
[-- Type: application/octet-stream, Size: 1009 bytes --]
diff -ruN linux-2.6.21.1_org/drivers/pci/quirks.c linux-2.6.21.1_new/drivers/pci/quirks.c
--- linux-2.6.21.1_org/drivers/pci/quirks.c 2008-01-23 14:22:25.000000000 +0800
+++ linux-2.6.21.1_new/drivers/pci/quirks.c 2008-01-23 14:22:44.000000000 +0800
@@ -1743,12 +1743,13 @@
* Instead of setting the flag on all busses in the machine, simply disable MSI
* globally.
*/
-static void __init quirk_svw_msi(struct pci_dev *dev)
+static void __init quirk_disable_all_msi(struct pci_dev *dev)
{
pci_no_msi();
printk(KERN_WARNING "PCI: MSI quirk detected. MSI deactivated.\n");
}
-DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_GCNB_LE, quirk_svw_msi);
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_GCNB_LE, quirk_disable_all_msi);
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x7910, quirk_disable_all_msi);//RS690
/* Disable MSI on chipsets that are known to not support it */
static void __devinit quirk_disable_msi(struct pci_dev *dev)
[-- Attachment #3: disable_MSI_and_withdraw_32bit.patch --]
[-- Type: application/octet-stream, Size: 1347 bytes --]
diff -ruN linux-2.6.24-rc7_org/drivers/ata/ahci.c linux-2.6.24-rc7_new/drivers/ata/ahci.c
--- linux-2.6.24-rc7_org/drivers/ata/ahci.c 2008-01-23 14:43:57.000000000 +0800
+++ linux-2.6.24-rc7_new/drivers/ata/ahci.c 2008-01-23 14:44:08.000000000 +0800
@@ -424,7 +424,7 @@
/* board_ahci_sb600 */
{
AHCI_HFLAGS (AHCI_HFLAG_IGN_SERR_INTERNAL |
- AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_PMP),
+ AHCI_HFLAG_NO_PMP),
.flags = AHCI_FLAG_COMMON,
.link_flags = AHCI_LFLAG_COMMON,
.pio_mask = 0x1f, /* pio0-4 */
diff -ruN linux-2.6.24-rc7_org/drivers/pci/quirks.c linux-2.6.24-rc7_new/drivers/pci/quirks.c
--- linux-2.6.24-rc7_org/drivers/pci/quirks.c 2008-01-23 14:44:53.000000000 +0800
+++ linux-2.6.24-rc7_new/drivers/pci/quirks.c 2008-01-23 14:45:00.000000000 +0800
@@ -1623,6 +1623,7 @@
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_SERVERWORKS, PCI_DEVICE_ID_SERVERWORKS_GCNB_LE, quirk_disable_all_msi);
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RS400_200, quirk_disable_all_msi);
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_RS480, quirk_disable_all_msi);
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATI, 0x7910, quirk_disable_all_msi);//RS690
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_VT3351, quirk_disable_all_msi);
/* Disable MSI on chipsets that are known to not support it */
^ permalink raw reply [flat|nested] 15+ messages in thread* RE: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-23 7:44 Shane Huang
@ 2008-01-24 3:53 ` Shane Huang
2008-01-25 0:21 ` Tejun Heo
1 sibling, 0 replies; 15+ messages in thread
From: Shane Huang @ 2008-01-24 3:53 UTC (permalink / raw)
To: jgarzik, sriharivijayaraghavan, Tejun Heo; +Cc: linux-ide, Shane Huang
Hi Jeff:
Do you have any suggestion on my plan to withdraw Tejun's forcing 32 bit
DMA patch?
As well as further validation to the 64 bit DMA capacity of SB600 SATA
controller?
Thanks
Best Regards
Shane
> -----Original Message-----
> From: Shane Huang
> Sent: Wednesday, January 23, 2008 3:44 PM
> To: sriharivijayaraghavan@yahoo.com.au; 'Tejun Heo'
> Cc: 'linux-ide@vger.kernel.org'; Shane Huang
> Subject: About forcing 32bit DMA patch for AMD690G(SB600)
> Importance: High
>
> Resending this mail and adding linux-ide mail list...
>
>
> Quoting Tejun:
> > Uh-oh, wait a bit. Nope. Until we figure out what the something else
is
> > and positively verify 64bit DMA works fine, the quirk stays in.
>
> Our HW engineer has confirmed that our SB600 SATA controller indeed
has
> some MSI issue, and we do not have any workaround.
>
> The workaround "quirk_msi_intx_disable_bug" to SB700 SATA controller
> can NOT work to SB600 SATA controller in my debug, while disablement
to
> RS690 MSI in kernel source can fix it.
>
> As to the SB600 64 bit DMA capacity, do you have any methods to do
further
> verification? I do NOT find any problem in my debug after I disabled
RS690
> MSI in kernel 2.6.24-rc7.
>
>
>
> Thanks
>
> Best Regards
> Shane
>
>
> -----Original Message-----
> From: Shane Huang
> Sent: Wednesday, January 23, 2008 2:56 PM
> To: sriharivijayaraghavan@yahoo.com.au
> Cc: 'Tejun Heo'; Shane Huang
> Subject: About forcing 32bit DMA patch for AMD690G(SB600)
> Importance: High
>
> Hi Srihari:
>
> This Shane @ AMD. I'm sorry to disturb you.
>
> I find that there is one patch which forces SB600 use 32bit DMA:
>
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
t;h=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c
>
> This patch was submitted by Tejun to fix one issue on your platform:
> http://marc.info/?l=linux-ide&m=117810966106759&w=2
>
> But after a discussion with our hardware engineers, Tejun(the patch
author),
> and some debugging, we believe that that SB600 can support 64 bit DMA,
> the root cause should be something else, while disablement to RS690
MSI
> in kernel source can be the workaround.
> So, we are going withdraw Tejun's patch ASAP.
>
> I wonder whether you still have that AMD690G platform or not?
> Are you able to help to do further confirmation before we withdraw it?
>
> You can just download kernel 2.6.21.1(which was used when you reported
> the bug), apply the attached disable_RS690_MSI.patch, and build the
kernel.
> Please tell me if that patch can fix your issue without Tejun's patch.
> This patch has been proved to work on my RS690+SB600 under Fedora7
x86_64.
>
> You can also try my another disable_MSI_and_withdraw_32bit.patch
> under linux kernel 2.6.24-rc7, to see whether this patch can fix your
> issue too. This method also can work on my RS690+SB600 platform.
>
>
> Thanks & waiting for your test result~~~ :-)
>
>
> Best Regards
> Shane
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-23 7:44 Shane Huang
2008-01-24 3:53 ` Shane Huang
@ 2008-01-25 0:21 ` Tejun Heo
2008-01-25 4:19 ` Andrew Paprocki
1 sibling, 1 reply; 15+ messages in thread
From: Tejun Heo @ 2008-01-25 0:21 UTC (permalink / raw)
To: Shane Huang; +Cc: sriharivijayaraghavan, linux-ide
Hello, Shane. Sorry about the delay. Got caught up in other stuff.
Shane Huang wrote:
> Quoting Tejun:
>> Uh-oh, wait a bit. Nope. Until we figure out what the something
>> else
> is
>> and positively verify 64bit DMA works fine, the quirk stays in.
>
> Our HW engineer has confirmed that our SB600 SATA controller indeed
> has some MSI issue, and we do not have any workaround.
>
> The workaround "quirk_msi_intx_disable_bug" to SB700 SATA controller
> can NOT work to SB600 SATA controller in my debug, while disablement
> to RS690 MSI in kernel source can fix it.
Hmmm... Okay. Is the SB600 SATA controller culprit or the north bridge
- RS690? If the former is the case, proper way to work around it is to
add AHCI_HFLAG_NO_MSI for SB600 AHCI.
> As to the SB600 64 bit DMA capacity, do you have any methods to do
> further verification? I do NOT find any problem in my debug after I
> disabled RS690 MSI in kernel 2.6.24-rc7.
The problem is that we didn't actually prove anything. In the tests
you've done, pci=nomsi didn't fix the problem but disable_all_msi quirk
did. pci=nomsi and disable_all_msi quirk are identical. Also,
Srihari's problem was not reproduced, so currently we can't say much
from the test results. Srihari, do you still have the system around?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-25 0:21 ` Tejun Heo
@ 2008-01-25 4:19 ` Andrew Paprocki
2008-01-25 5:50 ` Tejun Heo
0 siblings, 1 reply; 15+ messages in thread
From: Andrew Paprocki @ 2008-01-25 4:19 UTC (permalink / raw)
To: Tejun Heo; +Cc: Shane Huang, sriharivijayaraghavan, linux-ide
Tejun,
I have an SB600/RS690 here with SATA drives connected. I haven't been
following this thread, but I can help test something if it would help.
Thanks,
-Andrew
On Jan 24, 2008 7:21 PM, Tejun Heo <htejun@gmail.com> wrote:
> Hello, Shane. Sorry about the delay. Got caught up in other stuff.
>
> Shane Huang wrote:
> > Quoting Tejun:
> >> Uh-oh, wait a bit. Nope. Until we figure out what the something
> >> else
> > is
> >> and positively verify 64bit DMA works fine, the quirk stays in.
> >
> > Our HW engineer has confirmed that our SB600 SATA controller indeed
> > has some MSI issue, and we do not have any workaround.
> >
> > The workaround "quirk_msi_intx_disable_bug" to SB700 SATA controller
> > can NOT work to SB600 SATA controller in my debug, while disablement
> > to RS690 MSI in kernel source can fix it.
>
> Hmmm... Okay. Is the SB600 SATA controller culprit or the north bridge
> - RS690? If the former is the case, proper way to work around it is to
> add AHCI_HFLAG_NO_MSI for SB600 AHCI.
>
> > As to the SB600 64 bit DMA capacity, do you have any methods to do
> > further verification? I do NOT find any problem in my debug after I
> > disabled RS690 MSI in kernel 2.6.24-rc7.
>
> The problem is that we didn't actually prove anything. In the tests
> you've done, pci=nomsi didn't fix the problem but disable_all_msi quirk
> did. pci=nomsi and disable_all_msi quirk are identical. Also,
> Srihari's problem was not reproduced, so currently we can't say much
> from the test results. Srihari, do you still have the system around?
>
> Thanks.
>
> --
> tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-25 4:19 ` Andrew Paprocki
@ 2008-01-25 5:50 ` Tejun Heo
2008-01-25 20:57 ` Konstantin A. Lepikhov
2008-01-26 1:07 ` Andrew Paprocki
0 siblings, 2 replies; 15+ messages in thread
From: Tejun Heo @ 2008-01-25 5:50 UTC (permalink / raw)
To: Andrew Paprocki; +Cc: Shane Huang, sriharivijayaraghavan, linux-ide
Andrew Paprocki wrote:
> I have an SB600/RS690 here with SATA drives connected. I haven't been
> following this thread, but I can help test something if it would help.
We're trying to determine whether SB600 ahci controller can do 64bit DMA
or not. Srihari's couldn't but Shane's test result tells a different
story. Do you have memory mapped over 4G (if you have 4G some of them
will be over 4G, you can know this by looking at the e820 map printed
during boot)?
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-25 5:50 ` Tejun Heo
@ 2008-01-25 20:57 ` Konstantin A. Lepikhov
2008-01-25 23:13 ` Jeff Garzik
2008-01-26 1:24 ` Tejun Heo
2008-01-26 1:07 ` Andrew Paprocki
1 sibling, 2 replies; 15+ messages in thread
From: Konstantin A. Lepikhov @ 2008-01-25 20:57 UTC (permalink / raw)
To: Tejun Heo; +Cc: Andrew Paprocki, Shane Huang, sriharivijayaraghavan, linux-ide
Hi Tejun!
Friday 25, at 02:50:06 PM you wrote:
> Andrew Paprocki wrote:
> > I have an SB600/RS690 here with SATA drives connected. I haven't been
> > following this thread, but I can help test something if it would help.
>
> We're trying to determine whether SB600 ahci controller can do 64bit DMA
> or not. Srihari's couldn't but Shane's test result tells a different
> story. Do you have memory mapped over 4G (if you have 4G some of them
> will be over 4G, you can know this by looking at the e820 map printed
> during boot)?
$ lspci -nn
00:00.0 Host bridge [0600]: ATI Technologies Inc RD580 [CrossFire Xpress 3200] Chipset Host Bridge [1002:5952]
00:02.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI-X Root Port [1002:5a34]
00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
...
Is this hardware enough for testing? I can add 2G to existing 4G of RAM
and post dmesg.
--
WBR et al.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-25 20:57 ` Konstantin A. Lepikhov
@ 2008-01-25 23:13 ` Jeff Garzik
2008-01-26 1:24 ` Tejun Heo
1 sibling, 0 replies; 15+ messages in thread
From: Jeff Garzik @ 2008-01-25 23:13 UTC (permalink / raw)
To: Tejun Heo, Andrew Paprocki, Shane Huang, sriharivijayaraghavan,
linux-ide
Konstantin A. Lepikhov wrote:
> Hi Tejun!
>
> Friday 25, at 02:50:06 PM you wrote:
>
>> Andrew Paprocki wrote:
>>> I have an SB600/RS690 here with SATA drives connected. I haven't been
>>> following this thread, but I can help test something if it would help.
>> We're trying to determine whether SB600 ahci controller can do 64bit DMA
>> or not. Srihari's couldn't but Shane's test result tells a different
>> story. Do you have memory mapped over 4G (if you have 4G some of them
>> will be over 4G, you can know this by looking at the e820 map printed
>> during boot)?
> $ lspci -nn
> 00:00.0 Host bridge [0600]: ATI Technologies Inc RD580 [CrossFire Xpress 3200] Chipset Host Bridge [1002:5952]
> 00:02.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI-X Root Port [1002:5a34]
> 00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
> 00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
> ...
>
> Is this hardware enough for testing? I can add 2G to existing 4G of RAM
> and post dmesg.
"greater than 4G" would be a highly useful configuration...
Jeff
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-25 20:57 ` Konstantin A. Lepikhov
2008-01-25 23:13 ` Jeff Garzik
@ 2008-01-26 1:24 ` Tejun Heo
2008-01-31 9:14 ` Shane Huang
1 sibling, 1 reply; 15+ messages in thread
From: Tejun Heo @ 2008-01-26 1:24 UTC (permalink / raw)
To: Tejun Heo, Andrew Paprocki, Shane Huang, sriharivijayaraghavan,
linux-ide
Hello, Konstantin.
Konstantin A. Lepikhov wrote:
> $ lspci -nn
> 00:00.0 Host bridge [0600]: ATI Technologies Inc RD580 [CrossFire Xpress 3200] Chipset Host Bridge [1002:5952]
> 00:02.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI-X Root Port [1002:5a34]
> 00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
> 00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
> ...
>
> Is this hardware enough for testing? I can add 2G to existing 4G of RAM
> and post dmesg.
Srihari's system which couldn't do 64bit DMA was ASUS M2A-VM. I'm
including the result of lspci below. Shane verified 64bit works on a
configuration which has SB600 and different bridge, RS690, but Shane's
test result wasn't perfect either. AHCI triggers SERR_INTERNAL if
quirk_disable_all_msi is not used. quirk_disable_all_msi removes the
problem but specifying "pci=nomsi" doesn't.
It's unknown whether the difference between Srihari's and Shane's is
on the AHCI controller itself (different revisions?) or stemming from
the differences in the rest of the system (host/pci bridges).
The test results point to varied kinds and degrees of problems. At
the moment. To avoid turning off anything fancy on systems involving
SB600/700, we definitely need more info.
Shane, can you please summarize chipset product lines and revisions
and how they're configured together (e.g. SB600 Axx goes together with
RSxxx kind of stuff)?
Currently the following issues have been discovered and we need to
find out what's caused by which.
* MSI doesn't work at all. Possibly host or PCI bridge issue. Should
be worked around by quirk_disable_all_msi. Shane has verified some
systems do have this problem. It's still not clear which
configurations have the problem and in such configurations which
part. Currently quirk is applied if the system contains RS400_200
or RS480 (these are host bridges, right?).
* Disabling INTx disables MSI too. Should be worked around with
quirk_msi_intx_disable_bug. This one seems to be mostly taken care
of. New revs of SB700 and all SB800s will have this fixed and Shane
recently submitted patch to apply quirk to only affected machines.
Let's wait and see if anything blows.
* 64bit DMA doesn't work. Should be worked around by adding
AHCI_HFLAG_32BIT_ONLY in ahci driver. Srihari's system showed
failures firmly pointing to this problem. Shane tested different
system with SB600 and 64bit DMA itself seemed to work although there
were some issues. As written above, it's unclear what causes the
difference.
* Shane's test with RS690 + SB600 triggered a weird SERR_INTERNAL
error condition if pci=nomsi is used insted of
quirk_disable_all_msi. This is super-weird. Maybe difference in
memory layout and 64bit DMA acutally didn't work? Shane, can you
please do some data write/read/verify test on the setup?
Thanks.
-[0000:00]-+-00.0 ATI Technologies Inc Unknown device [1002:7910]
+-02.0-[0000:01]--+-00.0 ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] [1002:5b60]
| \-00.1 ATI Technologies Inc RV370 [Radeon X300SE] [1002:5b70]
+-07.0-[0000:02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168]
+-12.0 ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
+-13.0 ATI Technologies Inc SB600 USB (OHCI0) [1002:4387]
+-13.1 ATI Technologies Inc SB600 USB (OHCI1) [1002:4388]
+-13.2 ATI Technologies Inc SB600 USB (OHCI2) [1002:4389]
+-13.3 ATI Technologies Inc SB600 USB (OHCI3) [1002:438a]
+-13.4 ATI Technologies Inc SB600 USB (OHCI4) [1002:438b]
+-13.5 ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386]
+-14.0 ATI Technologies Inc SB600 SMBus [1002:4385]
+-14.1 ATI Technologies Inc SB600 IDE [1002:438c]
+-14.2 ATI Technologies Inc SB600 Azalia [1002:4383]
+-14.3 ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d]
+-14.4-[0000:03]--
+-18.0 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
+-18.1 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
+-18.2 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
\-18.3 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 82 [Master PriP])
Subsystem: ASUSTeK Computer Inc. Unknown device 81ef
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at f900 [size=16]
Capabilities: [70] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread* RE: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-26 1:24 ` Tejun Heo
@ 2008-01-31 9:14 ` Shane Huang
0 siblings, 0 replies; 15+ messages in thread
From: Shane Huang @ 2008-01-31 9:14 UTC (permalink / raw)
To: Tejun Heo; +Cc: Andrew Paprocki, sriharivijayaraghavan, linux-ide, Shane Huang
Dear Tejun:
> The test results point to varied kinds and degrees of problems. At
> the moment. To avoid turning off anything fancy on systems involving
> SB600/700, we definitely need more info.
>
> Shane, can you please summarize chipset product lines and revisions
> and how they're configured together (e.g. SB600 Axx goes together with
> RSxxx kind of stuff)?
I'll have to ask for other guys' help to summarize them, and will
provide
it here once I get it.
> Currently the following issues have been discovered and we need to
> find out what's caused by which.
> ..........
> ..........
> * Shane's test with RS690 + SB600 triggered a weird SERR_INTERNAL
> error condition if pci=nomsi is used insted of
> quirk_disable_all_msi. This is super-weird. Maybe difference in
> memory layout and 64bit DMA acutally didn't work? Shane, can you
> please do some data write/read/verify test on the setup?
I will do further debug on these issues before long, because I'm busy
with other issues and my SB600 board is being used by other guy.. :-(
Thanks
Shane
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-25 5:50 ` Tejun Heo
2008-01-25 20:57 ` Konstantin A. Lepikhov
@ 2008-01-26 1:07 ` Andrew Paprocki
2008-01-31 8:53 ` Shane Huang
1 sibling, 1 reply; 15+ messages in thread
From: Andrew Paprocki @ 2008-01-26 1:07 UTC (permalink / raw)
To: Tejun Heo; +Cc: Shane Huang, sriharivijayaraghavan, linux-ide
I'll try to get that configuration together.. right now I only have 2
1gb sticks installed on the board, so I would need to track down 2gb
ones. If I can find some laying around, I'll let you know.
Thanks,
-Andrew
On Jan 25, 2008 12:50 AM, Tejun Heo <htejun@gmail.com> wrote:
> Andrew Paprocki wrote:
> > I have an SB600/RS690 here with SATA drives connected. I haven't been
> > following this thread, but I can help test something if it would help.
>
> We're trying to determine whether SB600 ahci controller can do 64bit DMA
> or not. Srihari's couldn't but Shane's test result tells a different
> story. Do you have memory mapped over 4G (if you have 4G some of them
> will be over 4G, you can know this by looking at the e820 map printed
> during boot)?
>
> --
> tejun
>
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-26 1:07 ` Andrew Paprocki
@ 2008-01-31 8:53 ` Shane Huang
2008-02-01 8:23 ` Tejun Heo
0 siblings, 1 reply; 15+ messages in thread
From: Shane Huang @ 2008-01-31 8:53 UTC (permalink / raw)
To: Andrew Paprocki, Tejun Heo; +Cc: sriharivijayaraghavan, linux-ide, Shane Huang
Hi Andrew:
Thanks for your help on your platform.
And Is there any update at your side on SB600 64bit DMA capacity?
As Tejun mentioned, the test result on my SB600 engineering board
(RS690 A12 +SB600 A21) is a little different from the result of Srihari.
But I do not have other SB600 boards especially ASUS M2A-VM to do
further debug. So if you can provide us your test result, that's really
good.
Thanks
Shane
> -----Original Message-----
> From: andrew.m.paprocki@gmail.com
> [mailto:andrew.m.paprocki@gmail.com] On Behalf Of Andrew Paprocki
> Sent: Saturday, January 26, 2008 9:08 AM
> To: Tejun Heo
> Cc: Shane Huang; sriharivijayaraghavan@yahoo.com.au;
> linux-ide@vger.kernel.org
> Subject: Re: About forcing 32bit DMA patch for AMD690G(SB600)
>
> I'll try to get that configuration together.. right now I only have 2
> 1gb sticks installed on the board, so I would need to track down 2gb
> ones. If I can find some laying around, I'll let you know.
>
> Thanks,
> -Andrew
>
> On Jan 25, 2008 12:50 AM, Tejun Heo <htejun@gmail.com> wrote:
> > Andrew Paprocki wrote:
> > > I have an SB600/RS690 here with SATA drives connected. I
> haven't been
> > > following this thread, but I can help test something if
> it would help.
> >
> > We're trying to determine whether SB600 ahci controller can
> do 64bit DMA
> > or not. Srihari's couldn't but Shane's test result tells a
> different
> > story. Do you have memory mapped over 4G (if you have 4G
> some of them
> > will be over 4G, you can know this by looking at the e820
> map printed
> > during boot)?
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: About forcing 32bit DMA patch for AMD690G(SB600)
2008-01-31 8:53 ` Shane Huang
@ 2008-02-01 8:23 ` Tejun Heo
2008-02-02 4:04 ` Shane Huang
0 siblings, 1 reply; 15+ messages in thread
From: Tejun Heo @ 2008-02-01 8:23 UTC (permalink / raw)
To: Shane Huang; +Cc: Andrew Paprocki, sriharivijayaraghavan, linux-ide
Shane Huang wrote:
> As Tejun mentioned, the test result on my SB600 engineering board
> (RS690 A12 +SB600 A21) is a little different from the result of Srihari.
> But I do not have other SB600 boards especially ASUS M2A-VM to do
> further debug. So if you can provide us your test result, that's really
> good.
My 5 cents: Just order the board. These stock PC hardware are too cheap
these days, it doesn't make any sense to try to debug somewhat difficult
problem remotely if the hardware is available on the market. Even if
you have to spend your own money, it will be money well spent compared
to the time and effort you'll have to spend in comparison - hardware is
just too cheap.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: About forcing 32bit DMA patch for AMD690G(SB600)
2008-02-01 8:23 ` Tejun Heo
@ 2008-02-02 4:04 ` Shane Huang
2008-02-10 20:55 ` Srihari Vijayaraghavan
0 siblings, 1 reply; 15+ messages in thread
From: Shane Huang @ 2008-02-02 4:04 UTC (permalink / raw)
To: Tejun Heo; +Cc: Andrew Paprocki, sriharivijayaraghavan, linux-ide, Shane Huang
Dear Tejun:
> My 5 cents: Just order the board. These stock PC hardware
> are too cheap
> these days, it doesn't make any sense to try to debug
> somewhat difficult
> problem remotely if the hardware is available on the market. Even if
> you have to spend your own money, it will be money well spent compared
> to the time and effort you'll have to spend in comparison -
> hardware is just too cheap.
Yes you are right, we are trying to get one ASUS M2A-VM board.
Thanks
Shane
^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: About forcing 32bit DMA patch for AMD690G(SB600)
2008-02-02 4:04 ` Shane Huang
@ 2008-02-10 20:55 ` Srihari Vijayaraghavan
0 siblings, 0 replies; 15+ messages in thread
From: Srihari Vijayaraghavan @ 2008-02-10 20:55 UTC (permalink / raw)
To: Tejun Heo; +Cc: Andrew Paprocki, sriharivijayaraghavan, linux-ide, Shane Huang
Shane Huang <Shane.Huang@amd.com> wrote:
> Dear Tejun:
>
>
> > My 5 cents: Just order the board. These stock PC hardware
> > are too cheap
> > these days, it doesn't make any sense to try to debug
> > somewhat difficult
> > problem remotely if the hardware is available on the market. Even if
> > you have to spend your own money, it will be money well spent compared
> > to the time and effort you'll have to spend in comparison -
> > hardware is just too cheap.
>
> Yes you are right, we are trying to get one ASUS M2A-VM board.
Sorry folks I've been offline for a few weeks & I notice I missed out a lot of
important emails.
Now that I see I need to verify certain things, I'm very happy to do it. Just
give me a day or two.
> Thanks
> Shane
Thanks
Srihari
Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2008-02-10 21:02 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-29 20:10 About forcing 32bit DMA patch for AMD690G(SB600) Kelly Anderson
-- strict thread matches above, loose matches on Subject: below --
2008-01-23 7:44 Shane Huang
2008-01-24 3:53 ` Shane Huang
2008-01-25 0:21 ` Tejun Heo
2008-01-25 4:19 ` Andrew Paprocki
2008-01-25 5:50 ` Tejun Heo
2008-01-25 20:57 ` Konstantin A. Lepikhov
2008-01-25 23:13 ` Jeff Garzik
2008-01-26 1:24 ` Tejun Heo
2008-01-31 9:14 ` Shane Huang
2008-01-26 1:07 ` Andrew Paprocki
2008-01-31 8:53 ` Shane Huang
2008-02-01 8:23 ` Tejun Heo
2008-02-02 4:04 ` Shane Huang
2008-02-10 20:55 ` Srihari Vijayaraghavan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).