Re: Boot broken by "PCI : ability to relocate assigned pci-resources"

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

 



On Wed, Aug 31, 2011 at 4:18 AM, Michal Ludvig <mludvig@xxxxxxxxxxxx> wrote:
> Hi guys,
>
> I'm unable to boot 3.1-rc3+ on my Jetway NC9C-550-LF board with Intel
> Atom N550. Same config that works for 3.0 plus defaults for the new options.
>
> git bisect came up with this culprit:
>
> | From 2bbc6942273b5b3097bd265d82227bdd84b351b2 Mon Sep 17 00:00:00 2001
> | From: Ram Pai<linuxram@xxxxxxxxxx  <mailto:linuxram@xxxxxxxxxx>>
> | Date: Mon, 25 Jul 2011 13:08:39 -0700
> | Subject: [PATCH] PCI : ability to relocate assigned pci-resources
>
> Here's the captured crash:
>
> [...]
> [    7.027487] pci 0000:00:1f.2: BAR 5: assigned [mem 0xfed98400-0xfed987ff]
> [    7.108769] pci 0000:00:1f.2: BAR 5: set to [mem 0xfed98400-0xfed987ff]
> (PCI
> address [0xfed98400-0xfed987ff])
> [    7.227488] pci 0000:00:1c.3: BAR 14: assigned [mem
> 0xff400000-0xff6fffff]
> [    7.309808] pci 0000:00:1c.3: BAR 15: assigned [mem 0xff700000-0xff8fffff
> 64bit pref]
> [    7.403544] pci 0000:00:1c.2: BAR 14: assigned [mem
> 0xff900000-0xffafffff]

It'd be handy to have a kernel.org bugzilla report with the complete
working dmesg from 3.0 attached, as well as the complete log from
3.1-rc3 (as far as it got).  Those will contain additional information
about the PCI config we inherited from BIOS and what we did with it,
which might be useful to Ram.

Thanks for doing all the work of a bisection, by the way.  That really
speeds things up.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux