On Thursday, 9 November 2006 01:55, Andrew Morton wrote:
> On Thu, 9 Nov 2006 01:44:53 +0100
> "Rafael J. Wysocki" <[email protected]> wrote:
>
> > On Thursday, 9 November 2006 01:17, Andrew Morton wrote:
> > > On Thu, 9 Nov 2006 00:31:34 +0100
> > > "Rafael J. Wysocki" <[email protected]> wrote:
> > >
> > > > On Wednesday, 8 November 2006 10:54, Andrew Morton wrote:
> > > > >
> > > > > Temporarily at
> > > > >
> > > > > http://userweb.kernel.org/~akpm/2.6.19-rc5-mm1/
> > > > >
> > > > > will turn up at
> > > > >
> > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc5/2.6.19-rc5-mm1/
> > > > >
> > > > > when kernel.org mirroring catches up.
> > > > >
> > > > >
> > > > >
> > > > > - Merged the Kernel-based Virtual Machine patches. See kvm.sf.net for
> > > > > userspace tools, instructions, etc.
> > > > >
> > > > > It needs a recent binutils to build.
> > > > >
> > > > > - The hrtimer+dynticks code still doesn't work right for machines which halt
> > > > > their TSC in low-power states.
> > > >
> > > > On my HPC nx6325 it doesn't even reach the point in which the messages become
> > > > visible on the console, so I'm unable to get any debug info from it.
> > >
> > > Nice. You're using earlyprintk?
> >
> > earlyprintk=vga doesn't show anything (ie. blank screen), so it seems to crash
> > really early.
>
> OK, so it's definitely bisection time.
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, which according to gdb
is:
0xffffffff80271418 is in ioapic_read_entry (include/asm/io.h:204).
199
200 #define mmiowb()
201
202 static inline void __writel(__u32 b, volatile void __iomem *addr)
203 {
204 *(__force volatile __u32 *)addr = b;
205 }
206 static inline void __writeq(__u64 b, volatile void __iomem *addr)
207 {
208 *(__force volatile __u64 *)addr = b;
> > I'm unable to reproduce the problem on a non-SMP box (Asus L5D), which works
> > just fine with this kernel,
Well, it's booted with 'noapic', so no wonder ...
> > but on the other SMP box the framebuffer is broken
> > (displays all fonts inverted, as in a mirror)
>
> Which fbdev driver? (suspect fbcon-rere-fix-little-endian-bogosity-in-slow_imageblit.patch)
vga=792
> > and the kernel says it cannot mount the root fs (which is on an md-raid).
>
> hm, there was probably some earlier message which tells us why that
> happened. Doing a capure-and-compare on the dmesg output would be nice
> (netconsole?)
Tomorrow I'll try a serial one, but now I must get some sleep (I can hardly
see anything).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
