Re: [Xen-devel] linux-3.9-rc0 regression from 3.8 SATA controller not detected under xen

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Wednesday, February 27, 2013, 12:06:31 PM, you wrote:

>>>> On 27.02.13 at 11:57, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:

>> Tuesday, February 26, 2013, 9:41:53 AM, you wrote:
>> 
>>>>>> On 25.02.13 at 23:18, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:
>>>> I can't get linux-3.9 rc0 to boot under xen-unstable.
>>>> It doesn't detect the s-ata controller, so it ends op with udev timing and 
>>>> bailing out to busybox.
>>>> 
>>>> I don't see a obvious error in the logs.
>> 
>>> Perhaps because the log is far from being complete? There's a huge
>>> gap right before the first pciback message, yet that's quite likely
>>> the relevant part.
>> 
>> Hi Jan / Konrad,
>> 
>> Tried bisecting, but that ended up no where, so back to the logs...
>> 
>> With v3.9-rc0 + xen, it's indeed missing a part of the log:
>>   [    4.141328] Brought up 6 CPUs
>>   [    4.142654] Grant tables using version 2 layout.
>>   [    4.142676] Grant table initialized
>>   [    4.142813] NET: Registered protocol family 16
>>   [    4.145343] node 0 link 0: io port [1000, ffffff]
>>   [    4.145354] TOM: 00000000b0000000 aka 2816M
>>   [    4.145360] Fam 10h mmconf [mem 0xe0000000-0xefffffff]
>>   [    4.145373] node 0 link 0: mmio [e0000000, efffffff] ==> none
>>   [    4.145381] node 0 link 0: mmio [f0000000, ffffffff]
>>   [    4.145388] node 0 link 0: mmio [a0000, bffff]
>>   [    4.145395] node 0 link 0: mmio [b0000000, dfffffff]
>>   [    4.145401] TOM2: 0000000250000000 aka 9472M
>>   [    4.145406] bus: [bus 00-07] on node 0 link 0
>>   [    4.145411] bus: 00 [io  0x0000-0xffff]
>>   [    4.145415] bus: 00 [mem 0xf0000000-0xffffffff]
>>   [    4.145420] bus: 00 [mem 0x000a0000-0x000bffff]
>>   [    4.145424] bus: 00 [mem 0xb0000000-0xdfffffff]
>>   [    4.145429] bus: 00 [mem 0x250000000-0xfcffffffff]
>>   [    4.145702] ACPI: bus type pci registered
>>   [    4.146801] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 
>> 0xe0000000-0xefffffff] (base 0xe0000000)
>>   [    4.146812] PCI: not using MMCONFIG
>>   [    4.146817] PCI: Using configuration type 1 for base access
>>   [    4.146822] PCI: Using configuration type 1 for extended access
>>   [    4.191935] bio: create slab <bio-0> at 0
>>   [    4.192623] ACPI: Added _OSI(Module Device)
>>   [    4.192630] ACPI: Added _OSI(Processor Device)
>>   [    4.192636] ACPI: Added _OSI(3.0 _SCP Extensions)
>>   [    4.192642] ACPI: Added _OSI(Processor Aggregator Device)
>>   [    4.195958] ACPI: EC: Look up EC in DSDT
>>   [    4.199659] ACPI: Executed 3 blocks of module-level executable AML code
>>   [    4.204162] ACPI: Interpreter enabled
>>   [    4.204170] ACPI: (supports S0 S5)
>>   [    4.204181] ACPI: Using IOAPIC for interrupt routing
>>   [    4.204219] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 
>> 0xe0000000-0xefffffff] (base 0xe0000000)
>>   [    4.205800] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in 
>> ACPI motherboa[    7.107382] usb usb5: New USB device found, idVendor=1d6b, 
>> idProduct=0001
>> 
>> 
>> The line in the serial-log also seems to be truncated somehow and the rest 
>> of 
>> the info missing ..
>> 
>> When booting v3.9-rc0 Baremetal the complete pci enumeration seems to be in 
>> between:
>> ...
>> Tried booting with pci=nommconf,nocrs but to no avail.
>> Are there any other boot options i could try to narrow it down ?

> You first of all want to make sure you get a complete log.
> "sync_console" or "serial_tx_buffer=<size>" are your friends...

Ah that worked :-)

Complete serial log and lspci-v38 attached.

Sata device is: 00:11.0

From the log i see:

  [   16.132653] pci 0000:00:11.0: [1002:4390] type 00 class 0x01018f
  [   16.150679] pci 0000:00:11.0: calling quirk_no_ata_d3+0x0/0x10
  [   16.168365] pci 0000:00:11.0: reg 10: [io  0x7000-0x7007]
  [   16.184733] pci 0000:00:11.0: reg 14: [io  0x6000-0x6003]
  [   16.201116] pci 0000:00:11.0: reg 18: [io  0x5000-0x5007]
  [   16.217491] pci 0000:00:11.0: reg 1c: [io  0x3000-0x3003]
  [   16.233868] pci 0000:00:11.0: reg 20: [io  0x2000-0x200f]
  [   16.250249] pci 0000:00:11.0: reg 24: [mem 0xf96ff000-0xf96ff3ff]
  [   16.268714] pci 0000:00:11.0: calling quirk_amd_ide_mode+0x0/0xe0
  [   16.287163] pci 0000:00:11.0: set SATA to AHCI mode

<snip>

  [   21.524945] pci 0000:00:11.0: BAR 0: reserving [io  0x7000-0x7007 flags 
0x40101] (d=0, p=0)
  [   21.550163] pci 0000:00:11.0: BAR 1: reserving [io  0x6000-0x6003 flags 
0x40101] (d=0, p=0)
  [   21.575411] pci 0000:00:11.0: BAR 2: reserving [io  0x5000-0x5007 flags 
0x40101] (d=0, p=0)
  [   21.600648] pci 0000:00:11.0: BAR 3: reserving [io  0x3000-0x3003 flags 
0x40101] (d=0, p=0)
  [   21.625849] pci 0000:00:11.0: BAR 4: reserving [io  0x2000-0x200f flags 
0x40101] (d=0, p=0)
  [   21.651069] pci 0000:00:11.0: BAR 5: reserving [mem 0xf96ff000-0xf96ff3ff 
flags 0x40200] (d=0, p=0)

<snip>

  [   24.957481] pci 0000:00:11.0: calling 
quirk_msi_intx_disable_ati_bug+0x0/0x50

<snip>

  [   89.189428] ahci 0000:00:11.0: version 3.0
  [   89.207872] xen: registering gsi 19 triggering 0 polarity 1
  [   89.230656] xen: --> pirq=19 -> irq=19 (gsi=19)
  (XEN) [2013-02-27 11:21:21] IOAPIC[0]: Set PCI routing entry (6-19 -> 0xa9 -> 
IRQ 19 Mode:1 Active:1)
  [   89.277231] ahci 0000:00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf 
impl SATA mode
  [   89.307529] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp 
pio slum part 
  [   89.338827] ahci: probe of 0000:00:11.0 failed with error -22


> But then again I would guess it's not bus enumeration related.
> Did the multiple-MSI-vectors suspicion lead nowhere?

> Jan

Attachment: lspci-v38.txt
Description: Text document

Attachment: v39sync.log
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel