[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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:

[    0.288861] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 
0xe0000000-0xefffffff] (base 0xe0000000)
[    0.288867] PCI: not using MMCONFIG
[    0.288872] PCI: Using configuration type 1 for base access
[    0.288875] PCI: Using configuration type 1 for extended access
[    0.360826] bio: create slab <bio-0> at 0
[    0.361873] ACPI: Added _OSI(Module Device)
[    0.361883] ACPI: Added _OSI(Processor Device)
[    0.361891] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.361899] ACPI: Added _OSI(Processor Aggregator Device)
[    0.365516] ACPI: EC: Look up EC in DSDT
[    0.373572] ACPI: Executed 3 blocks of module-level executable AML code
[    0.452047] ACPI: Interpreter enabled
[    0.452052] ACPI: (supports S0 S5)
[    0.452077] ACPI: Using IOAPIC for interrupt routing
[    0.452249] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 
0xe0000000-0xefffffff] (base 0xe0000000)
[    0.465175] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI 
motherboard resources
[    0.479870] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug
[    0.605451] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.609907] acpi PNP0A03:00: Requesting ACPI _OSC control (0x1d)
[    0.613973] acpi PNP0A03:00: ACPI _OSC control (0x1d) granted
[    0.617005] PCI host bridge to bus 0000:00
[    0.617027] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.617037] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
[    0.617046] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
[    0.617055] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[    0.617064] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
[    0.617073] pci_bus 0000:00: root bus resource [mem 0xb0000000-0xdfffffff]
[    0.617081] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfebfffff]
[    0.617094] pci_bus 0000:00: scanning bus


Tried booting with pci=nommconf,nocrs but to no avail.
Are there any other boot options i could try to narrow it down ?

--
Sander

> Jan




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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.