linux-kernel - Re: 2.6.19-rc5-mm1: HPC nx6325 breakage, VESA fb problem, md-raid problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200611101221.19581.rjw@sisk.pl>
Date:	Fri, 10 Nov 2006 12:21:18 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andi Kleen <ak@...e.de>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	fbuihuu@...il.com, adaplas@....net, NeilBrown <neilb@...e.de>
Subject: Re: 2.6.19-rc5-mm1: HPC nx6325 breakage, VESA fb problem, md-raid problem

On Friday, 10 November 2006 07:19, Andi Kleen wrote:
> On Friday 10 November 2006 06:15, Andrew Morton wrote:
> > On Fri, 10 Nov 2006 05:49:08 +0100
> > Andi Kleen <ak@...e.de> wrote:
> > 
> > > 
> > > > > > 
> > > > > > Well, I've got some data from earlyprintk (forgot I needed to boot with
> > > > > > vga=normal).
> > > > > > 
> > > > > > Unfortunately, I had to rewrite the trace manually:
> > > > > > 
> > > > > > clear_IO_APIC_pin+0x15/0x6a
> > > > > > try_apic_pin+0x7a/0x98
> > > > > > setup_IO_APIC+0x600/0xb7a
> > > > > > smp_prepare_cpus+0x33a/0x371
> > > > > > init+0x60/0x32d
> > > > > > child_rip+0xa/0x12
> > > > > > 
> > > > > > [And then the unwinder said it got stuck.]
> > > > > > 
> > > > > > RIP is reported to be at ioapic_read_entry+0x33/0x61,
> > > > > 
> > > > > This is 100% reproducible on the nx6325 (but not on the other boxes) and
> > > > > apparently caused by x86_64-mm-try-multiple-timer-pins.patch (doesn't
> > > > > happen with this patch reverted).
> > > > 
> > > > Thanks, dropped.
> > > 
> > > can I have details please? 
> > 
> > I think what's in this thread is all you'll get.
> 
> That's probably not enough then.
> 
> 
> > 
> > It would be nice to see the access address.  I'd be guessing that it's
> > trying to read the io-apic before we're ready to read it and io_apic_base()
> > is returning gunk and boom.
> 
> I would like to see the full output from the earlyprintk crash please.
> .jpg would be ok.

Full is impossible, because it doesn't fit in the screen.  Also JPG would be
difficult, because I have no camera here. :-(

Still I can post a dmesg log from a non-failing kernel, the output of lspci
etc. if that helps.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/