RE: About forcing 32bit DMA patch for AMD690G(SB600)

2008-02-10 Thread Srihari Vijayaraghavan
Shane Huang <[EMAIL PROTECTED]> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM

2007-11-19 Thread Srihari Vijayaraghavan
Andi Kleen <[EMAIL PROTECTED]> wrote:
[...]
> 
> IOMMU merging should be always safe. If it is not the driver should
> not submit things in a single SG list.
> 
> > So the main option 
> > right now seems to revert the iommu_merge patch.
> 
> I don't think that is the correct fix.

Just to make sure this problem doesn't fall off the radar screen, I've filed
it on Kernel Bugzilla: 
http://bugzilla.kernel.org/show_bug.cgi?id=9412

Thanks



  Feel safe with award winning spam protection on Yahoo!7 Mail.  
www.yahoo.com.au/mail 

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM

2007-11-14 Thread Srihari Vijayaraghavan
[Sorry to reply to my own email thread]

Srihari Vijayaraghavan <[EMAIL PROTECTED]> wrote:
...
> No problems. Here's the log of unworking kernel with IOMMU turned on.
> Basically it goes on reseting the SATA ports throwing many errors (none are
> present in 2.6.23 or on 2.6.24-rc with mem=3500M) for many minutes at which
> point I do a power reset :-(.
> 
> Also the log of the working kernel with IOMMU but with mem=3500M is also
> attached for the record. It's basically the same above kernel just with the
> added parameter.

Gentlemen,

This changeset has introduced a regression in 2.6.24-rc, such that my machine
boots no more:
http://www.kernel.org/hg/linux-2.6/rev/ddf8804136fb
changeset:   72064:ddf8804136fb
user:Andi Kleen <[EMAIL PROTECTED]>
date:Fri Oct 19 20:35:03 2007 +0200
files:   arch/x86/kernel/pci-dma_64.c
description:
x86: enable iommu_merge by default

[ tglx: arch/x86 adaptation ]

Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>

committer: Thomas Gleixner <[EMAIL PROTECTED]>


diff -r 8c8683cbdc05 -r ddf8804136fb arch/x86/kernel/pci-dma_64.c
--- a/arch/x86/kernel/pci-dma_64.c  Fri Oct 19 20:35:03 2007 +0200
+++ b/arch/x86/kernel/pci-dma_64.c  Fri Oct 19 20:35:03 2007 +0200
@@ -11,7 +11,7 @@
 #include 
 #include 

-int iommu_merge __read_mostly = 0;
+int iommu_merge __read_mostly = 1;
 EXPORT_SYMBOL(iommu_merge);

 dma_addr_t bad_dma_address __read_mostly;

As a work-around, I can get it to boot with mem=3500M, but then it's ugly ;-)
& I lose some valuable memory I have.

Here's my email thread on linux-ide capturing the good & bad kernel behaviour
for reference:
http://marc.info/?t=11945621325&r=1&w=2

Thanks

Hari

PS: Here's hoping for a kernel mem= parameter free bootable 2.6.24 ;-).



  Feel safe with award winning spam protection on Yahoo!7 Mail.  
www.yahoo.com.au/mail 

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM

2007-11-13 Thread Srihari Vijayaraghavan
Tejun Heo <[EMAIL PROTECTED]> wrote:
> You need to turn on IOMMU.

(Actually when I started this thread, the kernel was with IOMMU, but I turned
it off as it was a new option in 2.4.24, so to see if it's causing the
regression. But it's back on.)

No problems. Here's the log of unworking kernel with IOMMU turned on.
Basically it goes on reseting the SATA ports throwing many errors (none are
present in 2.6.23 or on 2.6.24-rc with mem=3500M) for many minutes at which
point I do a power reset :-(.

Also the log of the working kernel with IOMMU but with mem=3500M is also
attached for the record. It's basically the same above kernel just with the
added parameter.

Thanks

Hari



  Feel safe with award winning spam protection on Yahoo!7 Mail.  
www.yahoo.com.au/mail 
Linux version 2.6.24-rc2 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red 
Hat 4.1.2-33)) #3 SMP Tue Nov 13 21:35:09 EST 2007
Command line: ro root=LABEL=/ 1 console=ttyS0,115200 console=tty0
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - dfee (usable)
 BIOS-e820: dfee - dfee3000 (ACPI NVS)
 BIOS-e820: dfee3000 - dfef (ACPI data)
 BIOS-e820: dfef - dff0 (reserved)
 BIOS-e820: e000 - f000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
 BIOS-e820: 0001 - 00012000 (usable)
end_pfn_map = 1179648
DMI 2.4 present.
ACPI: RSDP 000F8130, 0024 (r2 ATI   )
ACPI: XSDT DFEE3100, 004C (r1 ATIASUSACPI 42302E31 AWRD0)
ACPI: FACP DFEE8400, 00F4 (r3 ATIASUSACPI 42302E31 AWRD0)
ACPI: DSDT DFEE3280, 5136 (r1 ATIASUSACPI 1000 MSFT  300)
ACPI: FACS DFEE, 0040
ACPI: SSDT DFEE8600, 02CC (r1 PTLTD  POWERNOW1  LTP1)
ACPI: HPET DFEE8940, 0038 (r1 ATIASUSACPI 42302E31 AWRD   98)
ACPI: MCFG DFEE89C0, 003C (r1 ATIASUSACPI 42302E31 AWRD0)
ACPI: APIC DFEE8540, 0068 (r1 ATIASUSACPI 42302E31 AWRD0)
Scanning NUMA topology in Northbridge 24
CPU has 2 num_cores
No NUMA configuration found
Faking a node at -00012000
Bootmem setup node 0 -00012000
Zone PFN ranges:
  DMA 0 -> 4096
  DMA324096 ->  1048576
  Normal1048576 ->  1179648
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0:0 ->  159
0:  256 ->   917216
0:  1048576 ->  1179648
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x4008
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_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec0, 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)
Setting APIC routing to flat
ACPI: HPET id: 0x8200 base: 0xfed0
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at f100 (gap: f000:ec0)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PERCPU: Allocating 32848 bytes of per cpu data
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 1030058
Policy zone: Normal
Kernel command line: ro root=LABEL=/ 1 console=ttyS0,115200 console=tty0
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 2799.888 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
console [ttyS0] enabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:8
... MAX_LOCK_DEPTH:  30
... MAX_LOCKDEP_KEYS:2048
... CLASSHASH_SIZE:   1024
... MAX_LOCKDEP_ENTRIES: 8192
... MAX_LOCKDEP_CHAINS:  16384
... CHAINHASH_SIZE:  8192
 memory used by lock dependency info: 1648 kB
 per task-struct memory footprint: 1680 bytes
Checking aperture...
CPU 0: aperture @ c00 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 @ c00
Memory: 4055984k/4718592k available (2146k kernel code, 136780k reserved, 1273k 
data, 296k init)
SLUB: Genslabs=12, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Calibrating delay using timer specific routine.. 5604.88 BogoMIPS (lpj=11209778)
Security Framework initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as se

Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM

2007-11-12 Thread Srihari Vijayaraghavan
Tejun Heo <[EMAIL PROTECTED]> wrote:
> [...] Please post boot log.

Both the working (with mem= option) & a panicking ones attached.

Actually as you've pointed out, it may have nothing to do with ahci or sb600
as such, just that they helped in exposing the problem.

Because it started working with mem=3500M, I jumped to conclusions (as usual).

Thanks

PS: On the tip of http://www.kernel.org/hg/linux-2.6



  Feel safe with award winning spam protection on Yahoo!7 Mail.  
www.yahoo.com.au/mail 
Linux version 2.6.24-rc2 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red 
Hat 4.1.2-33)) #2 SMP Mon Nov 12 21:43:43 EST 2007
Command line: ro root=LABEL=/ 1 console=ttyS0,115200 console=tty0
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - dfee (usable)
 BIOS-e820: dfee - dfee3000 (ACPI NVS)
 BIOS-e820: dfee3000 - dfef (ACPI data)
 BIOS-e820: dfef - dff0 (reserved)
 BIOS-e820: e000 - f000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
 BIOS-e820: 0001 - 00012000 (usable)
end_pfn_map = 1179648
DMI 2.4 present.
ACPI: RSDP 000F8130, 0024 (r2 ATI   )
ACPI: XSDT DFEE3100, 004C (r1 ATIASUSACPI 42302E31 AWRD0)
ACPI: FACP DFEE8400, 00F4 (r3 ATIASUSACPI 42302E31 AWRD0)
ACPI: DSDT DFEE3280, 5136 (r1 ATIASUSACPI 1000 MSFT  300)
ACPI: FACS DFEE, 0040
ACPI: SSDT DFEE8600, 02CC (r1 PTLTD  POWERNOW1  LTP1)
ACPI: HPET DFEE8940, 0038 (r1 ATIASUSACPI 42302E31 AWRD   98)
ACPI: MCFG DFEE89C0, 003C (r1 ATIASUSACPI 42302E31 AWRD0)
ACPI: APIC DFEE8540, 0068 (r1 ATIASUSACPI 42302E31 AWRD0)
Scanning NUMA topology in Northbridge 24
CPU has 2 num_cores
No NUMA configuration found
Faking a node at -00012000
Bootmem setup node 0 -00012000
Zone PFN ranges:
  DMA 0 -> 4096
  DMA324096 ->  1048576
  Normal1048576 ->  1179648
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0:0 ->  159
0:  256 ->   917216
0:  1048576 ->  1179648
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x4008
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_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec0, 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)
Setting APIC routing to flat
ACPI: HPET id: 0x8200 base: 0xfed0
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at f100 (gap: f000:ec0)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PERCPU: Allocating 32848 bytes of per cpu data
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 1030061
Policy zone: Normal
Kernel command line: ro root=LABEL=/ 1 console=ttyS0,115200 console=tty0
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 2799.907 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
console [ttyS0] enabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:8
... MAX_LOCK_DEPTH:  30
... MAX_LOCKDEP_KEYS:2048
... CLASSHASH_SIZE:   1024
... MAX_LOCKDEP_ENTRIES: 8192
... MAX_LOCKDEP_CHAINS:  16384
... CHAINHASH_SIZE:  8192
 memory used by lock dependency info: 1648 kB
 per task-struct memory footprint: 1680 bytes
Memory: 4121532k/4718592k available (2141k kernel code, 71232k reserved, 1270k 
data, 292k init)
SLUB: Genslabs=12, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Calibrating delay using timer specific routine.. 5604.93 BogoMIPS (lpj=11209872)
Security Framework initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys cpuacct
Initializing cgroup subsys ns
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 0/0 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
lockdep: not fixing up alternatives.
ACPI: Core revision 20070126
Using local APIC timer interrupts.
Detected 12.499 MHz APIC timer.

Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM

2007-11-12 Thread Srihari Vijayaraghavan
> Tejun Heo <[EMAIL PROTECTED]> wrote:
[...]
> Hmmm.. weird.  The workaround is still there.  Please post boot log.

OK, that's good to hear. Alas, after the Fedora 7 to 8 upgrade, I'm no longer
able to compile a kernel (some uhci-hcd module not found for the initrd). And
I was too quick to overwrite the problematic kernel.

Anyway, once I get the kernel compiled, I'll post the boot log. Sorry for the
trouble.

Thanks

Hari



  Feel safe with award winning spam protection on Yahoo!7 Mail.  
www.yahoo.com.au/mail 

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


2.6.24-rc & SB600 AHCI no go on >=4GB of RAM

2007-11-08 Thread Srihari Vijayaraghavan
(Same symptoms/behaviour as before: 
http://marc.info/?l=linux-ide&m=117949823328798&w=2  & 
http://marc.info/?t=11781097043&r=1&w=2)

With mem=3500M all is well, otherwise it goes on reseting the ports in a loop & 
not booting :-(

Thanks

Hari





  Feel safe with award winning spam protection on Yahoo!7 Mail.  
www.yahoo.com.au/mail 

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PROBLEM] CDROM not ready. Make sure there is a disc in the drive.

2007-06-07 Thread Srihari Vijayaraghavan
Kernel throws these messages:
sr0: CDROM not ready.  Make sure there is a disc in the drive.
[many repeated entries]
sr0: CDROM not ready yet.
[many repeated entries]
sr0: disc change detected.

I've seen these errors on both x86 (Intel chipset) & x86-64 (AMD chipset),
vanilla 2.6.22-rc4 & vendor kernels (like Fedora 7's on both architectures)
with different drives (Liteon IDE CD drive, Asus SATA CD/DVD drive) with many
audio cd media.

(Interestingly, I haven't observed this problem with data CD/DVDs yet; nor
have I verified whether classic pata drivers rather than libata/ahci exhibit
the same. Later.)

When this happens, the audio cd player (like KsCD) stops responding. Retrying
manually will get the songs going again. Quite annoying. (Especially in KsCD,
one has to manually skip the tracks one already listened through. Painful
:-).)

Same behaviour observed with other applications like KAudioCreator also.

Having observed on a few machines now, I suspect it's rather easy to
reproduce.

The complete dmesg of 2.6.22-rc4 where this has been observed is attached.
More info on request.

Thanks


  
_
  

How would you spend $50,000 to create a more sustainable environment in 
Australia? Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html


Linux version 2.6.22-rc4 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070502 (Red 
Hat 4.1.2-12)) #8 SMP Tue Jun 5 20:02:26 EST 2007
Command line: ro root=LABEL=/ rhgb quiet
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - dfee (usable)
 BIOS-e820: dfee - dfee3000 (ACPI NVS)
 BIOS-e820: dfee3000 - dfef (ACPI data)
 BIOS-e820: dfef - dff0 (reserved)
 BIOS-e820: e000 - f000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
 BIOS-e820: 0001 - 00012000 (usable)
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 917216) 1 entries of 3200 used
Entering add_active_range(0, 1048576, 1179648) 2 entries of 3200 used
end_pfn_map = 1179648
DMI 2.4 present.
ACPI: RSDP 000F8110, 0024 (r2 ATI   )
ACPI: XSDT DFEE30C0, 0044 (r1 ATIASUSACPI 42302E31 AWRD0)
ACPI: FACP DFEE83C0, 00F4 (r3 ATIASUSACPI 42302E31 AWRD0)
ACPI: DSDT DFEE3240, 511E (r1 ATIASUSACPI 1000 MSFT  300)
ACPI: FACS DFEE, 0040
ACPI: SSDT DFEE85C0, 02CC (r1 PTLTD  POWERNOW1  LTP1)
ACPI: MCFG DFEE8980, 003C (r1 ATIASUSACPI 42302E31 AWRD0)
ACPI: APIC DFEE8500, 0068 (r1 ATIASUSACPI 42302E31 AWRD0)
Scanning NUMA topology in Northbridge 24
No NUMA configuration found
Faking a node at -00012000
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 917216) 1 entries of 3200 used
Entering add_active_range(0, 1048576, 1179648) 2 entries of 3200 used
Bootmem setup node 0 -00012000
Zone PFN ranges:
  DMA 0 -> 4096
  DMA324096 ->  1048576
  Normal1048576 ->  1179648
early_node_map[3] active PFN ranges
0:0 ->  159
0:  256 ->   917216
0:  1048576 ->  1179648
On node 0 totalpages: 1048191
  DMA zone: 56 pages used for memmap
  DMA zone: 1944 pages reserved
  DMA zone: 1999 pages, LIFO batch:0
  DMA32 zone: 14280 pages used for memmap
  DMA32 zone: 898840 pages, LIFO batch:31
  Normal zone: 1792 pages used for memmap
  Normal zone: 129280 pages, LIFO batch:31
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee0
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_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec0, 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
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at f100 (gap: f000:ec0)
PERCPU: Allocating 33608 bytes of per cpu data
Built 1 zonelists.  Total pages: 1030119
Kernel command line: ro root=LABEL=/ rhgb quiet
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Marking TSC unstable due to TSCs unsynchronized
time.c: Detected 2799.988 MHz processor.
Console: colour VGA+ 80x25
Lock depe

Re: [PATCH] ahci: disable 64bit dma on sb600

2007-05-21 Thread Srihari Vijayaraghavan
> Tejun Heo <[EMAIL PROTECTED]> wrote:
> > SB600 claims it can do 64bit DMA but it can't.  Disable it.
[...]
> > Srihari, can you test this against 2.6.22-rc1-git7 just in case?  I'll
> > send this upstream after you ack.

It's merged in today's git (quickly tested it & it's working good as expected)
:-). Impressive.

Well done & thank you Tejun & others!

Thanks

PS: Time to find other bugs & bug other maintainers :-).



  
___
How would you spend $50,000 to create a more sustainable environment in 
Australia?  Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] ahci: disable 64bit dma on sb600

2007-05-18 Thread Srihari Vijayaraghavan
Tejun Heo <[EMAIL PROTECTED]> wrote:
> SB600 claims it can do 64bit DMA but it can't.  Disable it.
> 
> DON'T APPLY YET
> ---
> 
> Srihari, can you test this against 2.6.22-rc1-git7 just in case?  I'll
> send this upstream after you ack.

Tejun,

Of course. Yes, it's working great without mem=4095M parameter on AMD690G
chipset (Asus M2A-VM) with 4 GB of RAM & Seagate SATA drives on SB600 AHCI
SATA controller (against the current http://www.kernel.org/hg/linux-2.6 repo
at changeset 56901:02db36c53917, which I believe is 2.6.22-rc1-git7
equivalent).

:-)

>  Thanks.

Thank you.

>  ahci.c |   11 ++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> index e00e1b9..bb94047 100644
> --- a/drivers/ata/ahci.c
> +++ b/drivers/ata/ahci.c
> @@ -170,6 +170,7 @@ enum {
>   AHCI_FLAG_IGN_IRQ_IF_ERR= (1 << 25), /* ignore IRQ_IF_ERR */
>   AHCI_FLAG_HONOR_PI  = (1 << 26), /* honor PORTS_IMPL */
>   AHCI_FLAG_IGN_SERR_INTERNAL = (1 << 27), /* ignore SERR_INTERNAL */
> + AHCI_FLAG_32BIT_ONLY= (1 << 28), /* force 32bit */
>  
>   AHCI_FLAG_COMMON= ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
> ATA_FLAG_MMIO | ATA_FLAG_PIO_DMA |
> @@ -354,7 +355,8 @@ static const struct ata_port_info ahci_p
>   /* board_ahci_sb600 */
>   {
>   .flags  = AHCI_FLAG_COMMON |
> -   AHCI_FLAG_IGN_SERR_INTERNAL,
> +   AHCI_FLAG_IGN_SERR_INTERNAL |
> +   AHCI_FLAG_32BIT_ONLY,
>   .pio_mask   = 0x1f, /* pio0-4 */
>   .udma_mask  = 0x7f, /* udma0-6 ; FIXME */
>   .port_ops   = &ahci_ops,
> @@ -492,6 +494,13 @@ static void ahci_save_initial_config(str
>   hpriv->saved_cap = cap = readl(mmio + HOST_CAP);
>   hpriv->saved_port_map = port_map = readl(mmio + HOST_PORTS_IMPL);
>  
> + /* some chips lie about 64bit support */
> + if ((cap & HOST_CAP_64) && (pi->flags & AHCI_FLAG_32BIT_ONLY)) {
> + dev_printk(KERN_INFO, &pdev->dev,
> +"controller can't do 64bit DMA, forcing 32bit\n");
> + cap &= ~HOST_CAP_64;
> + }
> +
>   /* fixup zero port_map */
>   if (!port_map) {
>   port_map = (1 << ahci_nr_ports(hpriv->cap)) - 1;
> 



  
___
How would you spend $50,000 to create a more sustainable environment in 
Australia?  Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-18 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Srihari Vijayaraghavan wrote:
> > --- Tejun Heo <[EMAIL PROTECTED]> wrote:
[...]
> > Can the Skymaster S3132, based on Sil3132,
> > (http://umart.net/au/product_info.php?cPath=21_211&products_id=106108) do
> 64
> > bit DMA on Linux?
> 
> Yeah, sil3124/32 can do 64bit alright.

Sorry, I couldn't quite convince myself wasting a little bit of money on that.
Temptation is hard to resist though.

> Maybe you can cc the ATI person here if you know the address.

Will do. Need to write a good story :-).
 
> > PS: FWIW, SB600 with your ahci fix has been working fine for the past
> week.
> > Thank you for that.
> 
> Great.

(I got the clue from yours, thanks for that) Actually, here's a crude one I'm
using for 2.6.22-rc:
--- a/drivers/ata/ahci.cThu May 17 20:02:36 2007 -0700
+++ b/drivers/ata/ahci.cFri May 18 22:17:27 2007 +1000
@@ -1563,6 +1563,7 @@ static int ahci_configure_dma_masks(stru
 static int ahci_configure_dma_masks(struct pci_dev *pdev, int using_dac)
 {
int rc;
+   using_dac = 0;

if (using_dac &&
!pci_set_dma_mask(pdev, DMA_64BIT_MASK)) {



  
___
How would you spend $50,000 to create a more sustainable environment in 
Australia?  Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-12 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Srihari Vijayaraghavan wrote:
> >> Oh well, that's the price you have to pay when you 1. have a device
> >> which can't access memory above 4G but 2. don't have IOMMU to do it for
> >> the device.  If performance becomes problem, you can always get a
> >> not-so-expensive external controller which can do 64.

Can the Skymaster S3132, based on Sil3132,
(http://umart.net/au/product_info.php?cPath=21_211&products_id=106108) do 64
bit DMA on Linux?

If so, I'm happy to buy that to isolate whether the current problem is limited
to SB600 SATA controller alone on AMD690G chipset.

It'd be nice if somebody from AMD/ATI could confirm the 64 bit DMA capability
of SB600 SATA controller. (I observe a few AMD/ATI folks have been submitting
a few patches on LKML lately, so who knows.)

Thanks

PS: FWIW, SB600 with your ahci fix has been working fine for the past week.
Thank you for that.


  Switch to Yahoo!7 Mail: Transfer all your contacts and emails from 
Hotmail and other providers to Yahoo!7 Mail. 
http://au.docs.yahoo.com/mail/trueswitch_info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-08 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:

[...]

> Just in case, can you post the result of 'lspci -nntv'?

No worries. Here it is as an attachment.

Thanks

Send instant messages to your online friends http://au.messenger.yahoo.com -[:00]-+-00.0  ATI Technologies Inc Unknown device [1002:7910]
   +-02.0-[: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-[: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-[: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]


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-08 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Hello,

Hello,
 
> Srihari Vijayaraghavan wrote:
> > --- Tejun Heo <[EMAIL PROTECTED]> wrote:
> >> It just seems sb600 claims that it can do DMA above 4G while it actually
> >> can't.  Can you test the attached patch?

[...]

> > With your patch, with 4 GB of RAM, all SATA drives are detected & working
> > normally. For the record dmesg is attached.
> 
> Thanks for testing.

Thank you for providing a good patch.

[...]

> Oh well, that's the price you have to pay when you 1. have a device
> which can't access memory above 4G but 2. don't have IOMMU to do it for
> the device.  If performance becomes problem, you can always get a
> not-so-expensive external controller which can do 64.

Well, I think my AM2 chip is capable of IOMMU (well that's one of the deciding
factor even since my original AMD64 3200+ :-)). BTW is there an easier way to
prove whether IOMMU is in use?

> Yeap, I'll forward it upstream and probably to -stable too.  The problem
> here is that I'm not sure whether the problem is in the ahci controller
> itself or some bridge chip above it.

Fair enough.

>  It would be best if Conke Hu can
> verify this but you can also test it by buying a ATA controller which
> can do 64bit and whether it works properly on the machine.  :-)

Let's hope he does.

Buying an (S)ATA controller now is a lofty goal (for the lack of money more
than anything :-)). But doesn't my current on-board IDE doesn't do 64bit DMA?

Here is its lspci -vvv:
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-
SERR- http://au.messenger.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-08 Thread Srihari Vijayaraghavan
--- Srihari Vijayaraghavan <[EMAIL PROTECTED]> wrote:
> --- Tejun Heo <[EMAIL PROTECTED]> wrote:
> With your patch, with 4 GB of RAM, all SATA drives are detected & working
> normally. For the record dmesg is attached.

Whoops. This time around dmesg is really attached.

(the -ahci in the kernel version string is to imply the usage of Tejun's
patch)

Thanks


Send instant messages to your online friends http://au.messenger.yahoo.com 

dmesg
Description: 2758069437-dmesg


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-08 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Hello,

Hello,

> It just seems sb600 claims that it can do DMA above 4G while it actually
> can't.  Can you test the attached patch?

Makes sense now. Gladly check the patch. Checking ...

Great news: everything just works without any parameters :-)). True genious.

With your patch, with 4 GB of RAM, all SATA drives are detected & working
normally. For the record dmesg is attached.

There's always a catch isn't it? Now no DMA over 32 bit memory space for SATA,
right? CPU will have to work harder, I presume. Perhaps putting more pressure.
While with 4 GB that might not be a problem, perhaps when I upgrade it to over
4 GB, it might be?? I see, even now, because a chunk of 512 MB is mapped over
4 GB (starting at 0x1), those are no good for the SATA's DMA access.
If so, too sad :-(.

> Thanks.

Thank you.

(I'll leave the patch for the poor souls stumble upon these emails some far
future :-))

PS: if this turns out to a hardware limitation, then perhaps may I request
this patch in better form (as not to impact on other ahci users) find its way
to mainstream? Even to -stable if I'm lucky, such that Fedora 7 etc. might
work out of the box for poor souls (not counting me; I'm used to quirky
things) trying out Linux on this chipset.

> -- 
> tejun
> > ---
>  drivers/ata/ahci.c |   10 +-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> Index: tree0/drivers/ata/ahci.c
> ===
> --- tree0.orig/drivers/ata/ahci.c
> +++ tree0/drivers/ata/ahci.c
> @@ -170,6 +170,7 @@ enum {
>   AHCI_FLAG_IGN_IRQ_IF_ERR= (1 << 25), /* ignore IRQ_IF_ERR */
>   AHCI_FLAG_HONOR_PI  = (1 << 26), /* honor PORTS_IMPL */
>   AHCI_FLAG_IGN_SERR_INTERNAL = (1 << 27), /* ignore SERR_INTERNAL */
> + AHCI_FLAG_32BIT_ONLY= (1 << 28), /* force 32bit */
>  };
>  
>  struct ahci_cmd_hdr {
> @@ -370,7 +371,8 @@ static const struct ata_port_info ahci_p
>   .flags  = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
> ATA_FLAG_MMIO | ATA_FLAG_PIO_DMA |
> ATA_FLAG_SKIP_D2H_BSY |
> -   AHCI_FLAG_IGN_SERR_INTERNAL,
> +   AHCI_FLAG_IGN_SERR_INTERNAL |
> +   AHCI_FLAG_32BIT_ONLY,
>   .pio_mask   = 0x1f, /* pio0-4 */
>   .udma_mask  = 0x7f, /* udma0-6 ; FIXME */
>   .port_ops   = &ahci_ops,
> @@ -1579,6 +1581,12 @@ static int ahci_host_init(struct ata_pro
>   probe_ent->n_ports = cap_n_ports;
>  
>   using_dac = hpriv->cap & HOST_CAP_64;
> + if (using_dac && (probe_ent->port_flags & AHCI_FLAG_32BIT_ONLY)) {
> + dev_printk(KERN_INFO, &pdev->dev,
> +"controller can't do 64bit DMA, forcing 32bit\n");
> + using_dac = 0;
> + }
> +
>   if (using_dac &&
>   !pci_set_dma_mask(pdev, DMA_64BIT_MASK)) {
>   rc = pci_set_consistent_dma_mask(pdev, DMA_64BIT_MASK);
> 


Send instant messages to your online friends http://au.messenger.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-07 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Srihari Vijayaraghavan wrote:

[...]

> > Thank you for your insight into the problem. If there are any tricks
> involved
> > in making use of all 4 GB of RAM with SATA drives & with system stability,
> > I'll be very happy to learn them :-)).
> 
> It might be that you just have a bad ram module.  Does the machine work
> properly if you exchange the installed two modules with the other two?
> memtet86 time, I guess.

With the new case, new power supply & a few extra fans to keep the system
ventilated nicely, memtest86+ ran 8 hours of 6 successful runs without an
issue. Before that it would be fine on only DDR2 667, but not at DDR2 800
mode. (all the Corsair 6400 DIMMs are DDR 800 by specification, of course. ie,
nothing is overclocked)

Having proven the hardware stability (I'm sure now Linux stability will
greatly improve also), system stability is no longer a concern for me.

Even now, when 4 GB of RAM is installed, by default, the SATA drives aren't
recongnised in Linux, except when I pass mem=4095MB. If I pass mem=4095M, alas
only 3.6 of RAM is detected under Linux!

Here's the relevant section from dmesg:
 BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - dfee (usable)
 BIOS-e820: dfee - dfee3000 (ACPI NVS)
 BIOS-e820: dfee3000 - dfef (ACPI data)
 BIOS-e820: dfef - dff0 (reserved)
 BIOS-e820: e000 - f000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
 BIOS-e820: 0001 - 00012000 (usable)
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 917216) 1 entries of 3200 used
end_pfn_map = 1048576
...
Memory: 3570504k/3668864k available (2465k kernel code, 97972k reserved, 1445k
data, 332k init)
...

Surprisingly, this usable ~3.6 GB equals to the initial two e820 sections
only. I believe, when mem= parameter is used, the third 'usable' section
(between 0x1 - 0x12000) isn't used at all by Linux.

I wonder if there is a trick involved in using mem= or memmap= needs to used
also (if so, I don't know yet how to construct memmap= parameter).

To recap:
System is very stable with the new case, power supply & fans
SATA drives aren't by default detected when 4 GB of RAM is used
SATA drives are detected by default when only 2 GB of RAM is physically
installed (ie, with both pairs of 2 GB of DIMMs individually)
SATA drives are detected when mem=4095M (the reported memory size in the
BIOS) is used, but only ~3.6 GB of RAM is used (suspected that the final e820
usable section, though detected, is not used).

Thank you for your help so far. I really appreciated that.

Hari


Send instant messages to your online friends http://au.messenger.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-03 Thread Srihari Vijayaraghavan
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Srihari Vijayaraghavan wrote:
> > Hardware:
> > ASUS M2A-VM (with the latest BIOS - 0402)
> > AMD AM2
> > Seagate IDE hard drive & LG IDE DVDRW
> > 
> > All works rather very nicely expect for the SATA
> :-).
> > 
> > No luck detecting the 2 Seagate ST3250620NS
> SATA-II
> > drives (Kernel.org's 2.6.21):

[...]
 
> Can you post dmesg with kernel parameter 'pci=nomsi'
> set?

Gladly.

Here it is (I'm on stable tree - 2.6.21.1 now):
Linux version 2.6.21.1 ([EMAIL PROTECTED]) (gcc version
4.1.2 20070424 (Red Hat 4.1.2-11)) #5 SMP Fri May 4
11:08:33 EST 2007
Command line: ro root=LABEL=/1234 console=ttyS0,115200
console=tty0 pci=nomsi
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000
(usable)
 BIOS-e820: 0009f000 - 000a
(reserved)
 BIOS-e820: 000f - 0010
(reserved)
 BIOS-e820: 0010 - dfee
(usable)
 BIOS-e820: dfee - dfee3000 (ACPI
NVS)
 BIOS-e820: dfee3000 - dfef (ACPI
data)
 BIOS-e820: dfef - dff0
(reserved)
 BIOS-e820: e000 - f000
(reserved)
 BIOS-e820: fec0 - 0001
(reserved)
 BIOS-e820: 0001 - 00012000
(usable)
Entering add_active_range(0, 0, 159) 0 entries of 3200
used
Entering add_active_range(0, 256, 917216) 1 entries of
3200 used
Entering add_active_range(0, 1048576, 1179648) 2
entries of 3200 used
end_pfn_map = 1179648
DMI 2.4 present.
ACPI: RSDP 000F80A0, 0024 (r2 ATI   )
ACPI: XSDT DFEE30C0, 0044 (r1 ATIASUSACPI 42302E31
AWRD0)
ACPI: FACP DFEE83C0, 00F4 (r3 ATIASUSACPI 42302E31
AWRD0)
ACPI: DSDT DFEE3240, 511F (r1 ATIASUSACPI 1000
MSFT  300)
ACPI: FACS DFEE, 0040
ACPI: SSDT DFEE85C0, 02CC (r1 PTLTD  POWERNOW1
 LTP1)
ACPI: MCFG DFEE8980, 003C (r1 ATIASUSACPI 42302E31
AWRD0)
ACPI: APIC DFEE8500, 0068 (r1 ATIASUSACPI 42302E31
AWRD0)
Scanning NUMA topology in Northbridge 24
Number of nodes 1
Node 0 MemBase  Limit 00012000
Entering add_active_range(0, 0, 159) 0 entries of 3200
used
Entering add_active_range(0, 256, 917216) 1 entries of
3200 used
Entering add_active_range(0, 1048576, 1179648) 2
entries of 3200 used
NUMA: Using 63 for the hash shift.
Using node hash shift of 63
Bootmem setup node 0 -00012000
Zone PFN ranges:
  DMA 0 -> 4096
  DMA324096 ->  1048576
  Normal1048576 ->  1179648
early_node_map[3] active PFN ranges
0:0 ->  159
0:  256 ->   917216
0:  1048576 ->  1179648
On node 0 totalpages: 1048191
  DMA zone: 88 pages used for memmap
  DMA zone: 2233 pages reserved
  DMA zone: 1678 pages, LIFO batch:0
  DMA32 zone: 22440 pages used for memmap
  DMA32 zone: 890680 pages, LIFO batch:31
  Normal zone: 2816 pages used for memmap
  Normal zone: 128256 pages, LIFO batch:31
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee0
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_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec0]
gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec0, 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 physical flat
Using ACPI (MADT) for SMP configuration information
Nosave address range: 0009f000 -
000a
Nosave address range: 000a -
000f
Nosave address range: 000f -
0010
Nosave address range: dfee -
dfee3000
Nosave address range: dfee3000 -
dfef
Nosave address range: dfef -
dff0
Nosave address range: dff0 -
e000
Nosave address range: e000 -
f000
Nosave address range: f000 -
fec0
Nosave address range: fec0 -
0001
Allocating PCI resources starting at f100 (gap:
f000:ec0)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PERCPU: Allocating 42048 bytes of per cpu data
Built 1 zonelists.  Total pages: 1020614
Kernel command line: ro root=LABEL=/1234
console=ttyS0,115200 console=tty0 pci=nomsi
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
time.c: Detected 2799.979 MHz processor.
Console: colour VGA+ 80x25
Lock dependency validator: Copyright (c) 2006 Red Hat,
Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:8
... MAX_LOCK_DEPT

ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem

2007-05-02 Thread Srihari Vijayaraghavan
Hardware:
ASUS M2A-VM (with the latest BIOS - 0402)
AMD AM2
Seagate IDE hard drive & LG IDE DVDRW

All works rather very nicely expect for the SATA :-).

No luck detecting the 2 Seagate ST3250620NS SATA-II
drives (Kernel.org's 2.6.21):
Linux version 2.6.21 ([EMAIL PROTECTED]) (gcc version 4.1.2
20070424 (Red Hat 4.1.2-1
1)) #3 SMP Mon Apr 30 18:49:04 EST 2007
Command line: ro root=LABEL=/1234 rhgb quiet
...
ahci :00:12.0: version 2.1
ACPI: PCI Interrupt :00:12.0[A] -> GSI 22 (level,
low) -> IRQ 22
PM: Adding info for No Bus:timer
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw
xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:1:0: Attached scsi CD-ROM sr0
PM: Adding info for No Bus:seq
PM: Adding info for No Bus:sequencer
PM: Adding info for No Bus:sequencer2
ahci :00:12.0: AHCI 0001.0100 32 slots 4 ports 3
Gbps 0xf impl SATA mode
ahci :00:12.0: flags: 64bit ncq ilck pm led clo
pmp pio slum part 
ata3: SATA max UDMA/133 cmd 0xc206a100 ctl
0x bmdma 0x00
00 irq 22
ata4: SATA max UDMA/133 cmd 0xc206a180 ctl
0x bmdma 0x00
00 irq 22
ata5: SATA max UDMA/133 cmd 0xc206a200 ctl
0x bmdma 0x00
00 irq 22
ata6: SATA max UDMA/133 cmd 0xc206a280 ctl
0x bmdma 0x00
00 irq 22
scsi2 : ahci
PM: Adding info for No Bus:host2
ata3: softreset failed (1st FIS failed)
ata3: softreset failed, retrying in 5 secs
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error,
err_mask=0x104)
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error,
err_mask=0x104)
ata3.00: limiting speed to UDMA7:PIO5
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error,
err_mask=0x104)
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
scsi3 : ahci
PM: Adding info for No Bus:host3
ata4: softreset failed (1st FIS failed)
ata4: softreset failed, retrying in 5 secs
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error,
err_mask=0x104)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error,
err_mask=0x104)
ata4.00: limiting speed to UDMA7:PIO5
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

(curiously irq 22 is exclusive to libata & irq count
is at 0)

(complete dmesg at the bottom of the email)

As was suggested by many folks
(http://marc.info/?l=linux-ide&w=2&r=1&s=SB600+Non-Raid-5+SATA&q=b),
tried various bootup parameters to no avail:
pci=nomsi
acpi=noirq
irqpoll
acpi=off pci=nomsi irqpoll

Also tried changing the BIOS SATA Controller from AHCI
to IDE to RAID to no avail (all observations in this
email captured while it was set was AHCI).

Here's lspci -vvv:
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 8231
Control: I/O+ Mem+ BusMaster+ SpecCycle-
MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr-
DEVSEL=medium >TAbort- SERR-  4096
  DMA324096 ->  1048576
  Normal1048576 ->  1179648
early_node_map[3] active PFN ranges
0:0 ->  159
0:  256 ->   917216
0:  1048576 ->  1179648
On node 0 totalpages: 1048191
  DMA zone: 88 pages used for memmap
  DMA zone: 2218 pages reserved
  DMA zone: 1693 pages, LIFO batch:0
  DMA32 zone: 22440 pages used for memmap
  DMA32 zone: 890680 pages, LIFO batch:31
  Normal zone: 2816 pages used for memmap
  Normal zone: 128256 pages, LIFO batch:31
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee0
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_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec0]
gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec0, 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 physical flat
Using ACPI (MADT) for SMP configuration information
Nosave address range: 0009f000 -
000a
Nosave address range: 000a -
000f
Nosave address range: 000f -
0010
Nosave address range: dfee -
dfee3000
Nosave address range: dfee3000 -
dfef
Nosave address range: dfef -
dff0
Nosave address range: dff0 -
e000
No