Home » Mailing list archives » linux-kernel » 2007 » January » 26

Re: SATA ahci Bug in 2.6.19.x

Previous thread: [patch] md: bitmap read_page error by yang yin on Monday, January 22, 2007 - 1:03 am. (1 message)

Next thread: [RFC] Asynchronous Messaging by Wink Saville on Monday, January 22, 2007 - 1:19 am. (3 messages)
[view original message]
From: Stefan Priebe - FH
Subject: SATA ahci Bug in 2.6.19.x
Date: Monday, January 22, 2007 - 1:02 am

Hello!

I've an Asus A8V Mainboard which works wonderful with a 2.6.18.X kernel. 
But i cannot use the SATA Controller with a 2.6.19.x Kernel.

dmesg output from 2.6.18.3 where it works perfectly:
libata version 2.00 loaded.
ahci 0000:00:0f.0: version 2.0
GSI 19 sharing vector 0xD9 and IRQ 19
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI
21 (level, low) -> IRQ 217
ahci 0000:00:0f.0: AHCI 0001.0000 32 slots 4
ports 3 Gbps 0xf impl IDE mode
ahci 0000:00:0f.0: flags: 64bit ncq pm led
clo pmp pio slum part
ata1: SATA max UDMA/133 cmd
0xFFFFC20000004D00 ctl 0x0 bmdma 0x0 irq 225
ata2: SATA max UDMA/133 cmd
0xFFFFC20000004D80 ctl 0x0 bmdma 0x0 irq 225
ata3: SATA max UDMA/133 cmd
0xFFFFC20000004E00 ctl 0x0 bmdma 0x0 irq 225
ata4: SATA max UDMA/133 cmd
0xFFFFC20000004E80 ctl 0x0 bmdma 0x0 irq 225
scsi0 : ahci
ata1: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
ata1.00: ATA-7, max UDMA7, 312581808
sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : ahci
ata2: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
ata2.00: ATA-7, max UDMA7, 312581808
sectors: LBA48 NCQ (depth 0/32)
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133
scsi2 : ahci
ata3: SATA link down (SStatus 0 SControl 300)
scsi3 : ahci
ata4: SATA link down (SStatus 0 SControl 300)
   Vendor: ATA       Model: SAMSUNG HD160JJ
  Rev: ZM10
   Type:   Direct-Access
  ANSI SCSI revision: 05
   Vendor: ATA       Model: SAMSUNG HD160JJ
  Rev: ZM10
   Type:   Direct-Access
  ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr
sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr
sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
  sda: sda1 < sda5 sda6 sda7 >
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 312581808 512-byte hdwr
sectors (160042 ...
[ message continues ]
[view original message]
From: Stephen Evanchik
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Monday, January 22, 2007 - 7:00 am

I also have an Asus A8V motherboard that cannot boot a newer kernel
because the SATA controller does not come up properly. I have tried
kernels 2.6.19.2 and 2.6.20-rc5 with no luck. It looks like later
kernels don't recognize the proper IRQ of the device as compared to

Similar output as above.


Does any one have any ideas?


Stephen
-


[ message continues ]
[view original message]
From: Stefan Priebe - FH
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Thursday, January 25, 2007 - 2:24 pm

Hello....

Nobody here who cares???

Stefan


-


[ message continues ]
[view original message]
From: Luming Yu
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Thursday, January 25, 2007 - 8:25 pm

>From the log:
2.6.18.3:
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 21 (level, low) -> IRQ 217
2.6.20-rc5:
"ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 21 (level, low) -> IRQ 21"

Sounds like acpi interrupt configure problem. Please try acpi=off first.
-


[ message continues ]
[view original message]
From: Stephen Evanchik
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Thursday, January 25, 2007 - 9:46 pm

Still does not recognize the SATA device (and the machine fails to
come up). I tested this with 2.6.19.2, 2.6.20-rc5 and -rc6 this
evening. I am going to build a vanilla 2.6.18 and see if that still
works as I am currently running an FC5 kernel.

Stephen


-- 
Stephen Evanchik
http://stephen.evanchik.com
-


[ message continues ]
[view original message]
From: Luming Yu
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Thursday, January 25, 2007 - 10:22 pm

Is there any difference in dmesg with acpi=off?
what is your sata driver?
-


[ message continues ]
[view original message]
From: Stephen Evanchik
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Thursday, January 25, 2007 - 11:18 pm

The only difference is that I don't see the "ACPI: PCI Interrupt
0000:00:0f.0[B] -> GSI
21 (level, low) -> IRQ 19" printk. The driver is AHCI but the device
is a VIA chip.

I'll get a caputre of the boot log when I find my serial cable. This
could be related to the VIA PIC quirks that was changed by Alan.

Stephen
-


[ message continues ]
[view original message]
From: Alan
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Friday, January 26, 2007 - 3:33 am

Stuff a printk in and check by all means but _in theory_ the VIA quirk
shouldn't touch IRQ > 15 as those are not PIC but APIC routed.
-


[ message continues ]
[view original message]
From: Stefan Priebe - FH
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Friday, January 26, 2007 - 2:19 am

Hi!

acpi=off does not help i've already tried that.


Ok here some outputs:
1.) complete dmesg with 2.6.16.27 (works)

Linux version 2.6.16.27amd (root@server275-han) (gcc version 3.3.5 
(Debian 1:3.3.5-13)) #6 SMP Sat Aug 26 14:29:07 CEST 2006
BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
  BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
  BIOS-e820: 0000000000100000 - 000000003bfb0000 (usable)
  BIOS-e820: 000000003bfb0000 - 000000003bfbe000 (ACPI data)
  BIOS-e820: 000000003bfbe000 - 000000003bfe0000 (ACPI NVS)
  BIOS-e820: 000000003bfe0000 - 000000003c000000 (reserved)
  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
  BIOS-e820: 00000000fecc0000 - 00000000fecc1000 (reserved)
  BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved)
ACPI: RSDP (v002 ACPIAM                                ) @ 
0x00000000000fa850
ACPI: XSDT (v001 A M I  OEMXSDT  0x12000527 MSFT 0x00000097) @ 
0x000000003bfb0100
ACPI: FADT (v003 A M I  OEMFACP  0x12000527 MSFT 0x00000097) @ 
0x000000003bfb0290
ACPI: MADT (v001 A M I  OEMAPIC  0x12000527 MSFT 0x00000097) @ 
0x000000003bfb0390
ACPI: MCFG (v001 A M I  OEMMCFG  0x12000527 MSFT 0x00000097) @ 
0x000000003bfb0400
ACPI: OEMB (v001 A M I  AMI_OEM  0x12000527 MSFT 0x00000097) @ 
0x000000003bfbe040
ACPI: DSDT (v001  A0339 A0339000 0x00000000 INTL 0x02002026) @ 
0x0000000000000000
Scanning NUMA topology in Northbridge 24
Number of nodes 1
Node 0 MemBase 0000000000000000 Limit 000000003bfb0000
NUMA: Using 63 for the hash shift.
Using node hash shift of 63
Bootmem setup node 0 0000000000000000-000000003bfb0000
On node 0 totalpages: 240991
   DMA zone: 2709 pages, LIFO batch:0
   DMA32 zone: 238282 pages, LIFO batch:31
   Normal zone: 0 pages, LIFO batch:0
   HighMem zone: 0 pages, LIFO batch:0
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] ...
[ message continues ]
[view original message]
From: Stefan Priebe - FH
Subject: Re: SATA ahci Bug in 2.6.19.x
Date: Tuesday, January 30, 2007 - 3:44 am

Hi!

Any News?

Stefan


-


[ message continues ]
Previous thread: [patch] md: bitmap read_page error by yang yin on Monday, January 22, 2007 - 1:03 am. (1 message)

Next thread: [RFC] Asynchronous Messaging by Wink Saville on Monday, January 22, 2007 - 1:19 am. (3 messages)