public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Robin Lee Powell <rlpowell@digitalkingdom.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM
Date: Tue, 19 Sep 2006 08:39:51 +0200	[thread overview]
Message-ID: <200609190839.51123.ak@suse.de> (raw)
In-Reply-To: <20060919062828.GD7845@chain.digitalkingdom.org>

On Tuesday 19 September 2006 08:28, Robin Lee Powell wrote:
> On Tue, Sep 19, 2006 at 08:04:14AM +0200, Andi Kleen wrote:
> > 
> > > Done; it's at
> > > http://teddyb.org/~rlpowell/media/regular/lkml/hacked-boot.txt
> > > 
> > > Note that I had to us "mce=off acpi=off pci=conf1" to get any of
> > > that hack's output to show up at all; I wasn't clear whether you
> > > intended that or not.
> > 
> > Unfortunately with mce=off we can't see which device breaks. Can
> > you please boot with the patch and just 
> > 
> > acpi=off pci=conf1 ? 
> > 
> > and send the full output?
> 
> The result is a reboot in the middle of bringing up CPU#1.  No
> output from the patch is printed.
> 
> I've printed it below anyways.


What happens when you additionally add this patch and boot with
the same options again? 

-Andi


diff -u linux-2.6.17-hack/include/asm-x86_64/pci-direct.h-o linux-2.6.17-hack/include/asm-x86_64/pci-direct.h
--- linux-2.6.17-hack/include/asm-x86_64/pci-direct.h-o	2006-03-03 08:14:00.000000000 +0100
+++ linux-2.6.17-hack/include/asm-x86_64/pci-direct.h	2006-09-19 08:38:25.000000000 +0200
@@ -7,33 +7,32 @@
 /* Direct PCI access. This is used for PCI accesses in early boot before
    the PCI subsystem works. */ 
 
-#define PDprintk(x...)
+#define PDprintk(x...) printk(x)
 
 static inline u32 read_pci_config(u8 bus, u8 slot, u8 func, u8 offset)
 {
 	u32 v; 
+	PDprintk("%x reading 4 from %x: %x\n", slot, offset, v);
 	outl(0x80000000 | (bus<<16) | (slot<<11) | (func<<8) | offset, 0xcf8);
 	v = inl(0xcfc); 
-	if (v != 0xffffffff)
-		PDprintk("%x reading 4 from %x: %x\n", slot, offset, v);
 	return v;
 }
 
 static inline u8 read_pci_config_byte(u8 bus, u8 slot, u8 func, u8 offset)
 {
 	u8 v; 
+	PDprintk("%x reading 1 from %x: %x\n", slot, offset, v);
 	outl(0x80000000 | (bus<<16) | (slot<<11) | (func<<8) | offset, 0xcf8);
 	v = inb(0xcfc + (offset&3)); 
-	PDprintk("%x reading 1 from %x: %x\n", slot, offset, v);
 	return v;
 }
 
 static inline u16 read_pci_config_16(u8 bus, u8 slot, u8 func, u8 offset)
 {
 	u16 v; 
+	PDprintk("%x reading 2 from %x: %x\n", slot, offset, v);
 	outl(0x80000000 | (bus<<16) | (slot<<11) | (func<<8) | offset, 0xcf8);
 	v = inw(0xcfc + (offset&2)); 
-	PDprintk("%x reading 2 from %x: %x\n", slot, offset, v);
 	return v;
 }
 

  reply	other threads:[~2006-09-19  6:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 22:32 Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Robin Lee Powell
2006-09-14 19:05 ` Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM) Robin Lee Powell
2006-09-14 19:14   ` Lee Revell
2006-09-14 19:15     ` Robin Lee Powell
2006-09-15  5:42       ` Bharath Ramesh
2006-09-15 17:47         ` Robin Lee Powell
2006-09-15 18:07           ` Robin Lee Powell
2006-09-15 18:22           ` Alan Cox
2006-09-15 18:12             ` Robin Lee Powell
2006-09-18  7:52         ` Andi Kleen
2006-09-18 18:59           ` Robin Lee Powell
2006-09-15 11:45   ` Alan Cox
2006-09-15 18:29     ` Robin Lee Powell
2006-09-15 20:50       ` Alan Cox
2006-09-15 20:31         ` Robin Lee Powell
2006-09-15 23:18           ` Robin Lee Powell
2006-09-18  7:50 ` Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Andi Kleen
2006-09-18 19:06   ` Robin Lee Powell
2006-09-18 23:58   ` Robin Lee Powell
2006-09-19  6:04     ` Andi Kleen
2006-09-19  6:28       ` Robin Lee Powell
2006-09-19  6:39         ` Andi Kleen [this message]
2006-09-19 17:46           ` Robin Lee Powell
2006-09-19 21:07             ` Robin Lee Powell

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=200609190839.51123.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlpowell@digitalkingdom.org \
    /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