public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Maciej Rutecki <maciej.rutecki@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	tj@kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Yinghai Lu <yhlu.kernel@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [2.6.26.*] boot problem (ahci/irq related?)
Date: Mon, 11 Aug 2008 17:48:50 -0600	[thread overview]
Message-ID: <48A0CFE2.6090705@shaw.ca> (raw)
In-Reply-To: <20080811210140.GW9038@one.firstfloor.org>

Andi Kleen wrote:
> On Mon, Aug 11, 2008 at 10:27:31PM +0200, Ingo Molnar wrote:
>> * Maciej Rutecki <maciej.rutecki@gmail.com> wrote:
>>
>>> A have problem with booting 2.6.26* and 2.6.27-rc* kernels. Very often
>>> booting stops on this message:
>>>
>>> [...]
>>> Uniform Multi-Platform E-IDE driver
>>> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
>>> ICH7: IDE controller (0x8086:0x27df rev 0x01) at  PCI slot 0000:00:1f.1
>>> ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16
>>> ICH7: not 100% native mode: will probe irqs later
>>> ICH7: IDE port disabled
>>>     ide0: BM-DMA at 0x60a0-0x60a7
>>>
>>> afer should be:
>>> hda: MATSHITADVD-RAM UJ-840S, ATAPI CD/DVD-ROM drive
>>> hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
>>> hda: MWDMA2 mode selected
>>> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>> [...]
>>>
>>> Initially I was think, that is hardware problem. But XP and 2.6.25.8 
>>> work with _no_ problem (booting from xp, linux, knoppix, linux 
>>> firmware development kit - about 50 reboots).
>>> http://unixy.pl/maciek/download/kernel/dupa/dmesg-2.6.26.2.txt
>>> dmesg: http://unixy.pl/maciek/download/kernel/dupa/dmesg-2.6.25.8.txt
>> i had a look at diff -up dmesg-2.6.25.8.txt dmesg-2.6.26.2.txt, and 
>> these changes stood out:
> 
> Yes post 2.6.25 changed to trust the ACPI motherboard resources
> to signify working mmcfg, previously it would use the e820 table
> which excluded near all motherboards which were not white listed
> by PCI-ID because BIOS programmers were generally not aware
> they had to reserve mcfg in e820. 
> 
> You can verify this by booting with pci=nommconf. If it works
> then it's likely that.
> 
> The new heuristic is apparently the same as what Vista does.
> 
> Robert Hancock (cc'ed, fullquote) is mr. mmconfig quirk.
> 
> -Andi

Wouldn't hurt to try it, but I'm kind of doubtful it's that - MMCONFIG 
failures don't normally get that far into bootup, and I believe we're 
not using it for non-extended config space anyways - I doubt IDE is 
doing extended config space access..

  reply	other threads:[~2008-08-11 23:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 20:12 [2.6.26.*] boot problem (ahci/irq related?) Maciej Rutecki
2008-08-11 20:27 ` Ingo Molnar
2008-08-11 21:01   ` Andi Kleen
2008-08-11 23:48     ` Robert Hancock [this message]
2008-08-12  5:50     ` Maciej Rutecki
2008-08-12  7:05       ` Andi Kleen
2008-08-12  6:52   ` Yinghai Lu
2008-08-12  7:16     ` Alan Cox
2008-08-12  8:07       ` Maciej Rutecki
2008-08-12 14:45         ` Rafael J. Wysocki
2008-08-13  7:40           ` Maciej Rutecki
2008-08-16  9:36             ` Maciej Rutecki
2008-08-20 18:36               ` Maciej Rutecki
2008-08-21 12:45                 ` Rafael J. Wysocki
2008-08-22  8:58                   ` Maciej Rutecki
2008-08-22 10:10                     ` Rafael J. Wysocki
2008-08-22 10:50                       ` Maciej Rutecki
2008-08-24 21:27                         ` Rafael J. Wysocki
2008-09-02  9:59                           ` [SOLVED] " Maciej Rutecki
2008-08-12  7:22     ` Yinghai Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48A0CFE2.6090705@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox