[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080529012652.6b9027a3.akpm@linux-foundation.org>
Date: Thu, 29 May 2008 01:26:52 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: alejandro.riveira@...il.com
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: two different oopses with 2.6.26-rc4
On Wed, 28 May 2008 11:50:34 +0200 Alejandro Riveira Fern__ndez <alejandro.riveira@...il.com> wrote:
> I sent this to the list with other mail address and it didn't reach it
> afaics. apologies if someone sees this twice
>
> i cced wireless becouse of the first oops
>
> First boot into 2.6.26-rc4
>
> Compiled and booting into 2.6.26-rc4
>
> 1) With splash quiet on grub line it doesn't boot (or i didin't wait long
> enough)
> 2) without quiet and splash I get into VT X filas becouse i use the evil
> nvidia driver that's expected. But ubuntu failsafe mode (xserver with vesa
> in low res) doesn't show up either *regression*
> 3) i get an oops with network manager
> 4) if i try to run some sudo command it gets stuck (Crtl +C doesnt' help)
> "ip route" gets stuck too. User programs i tried wrok fine (only ls and
> htop). Network realted problem?
>
> 5) printk times on dmesg go crazy
>
> But the second time a boot into it i got a working system (i even compiled the
> *famous* nvidia driver) with only a bluetooth related oops ...
>
> Both dmesg follow. This is on a hardy 8.04 64 bits system. If more info is needed
> just ask
>
> No working first one
>
> ...
>
> [ 0.000000] Using ACPI (MADT) for SMP configuration information
> [ 0.000000] Allocating PCI resources starting at c4000000 (gap: c0000000:3f380000)
> [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
> [ 0.000000] PERCPU: Allocating 33860 bytes of per cpu data
> [ 0.000000] NR_CPUS: 2, nr_cpu_ids: 2
> [4294014.506571] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 774451
> [4294014.506571] Kernel command line: BOOT_IMAGE=(hd0,2)/vmlinuz-2.6.26-rc4 root=UUID=ee465ea1-394d-4dd2-a5f9-a35567176c40 ro
> [4294014.506571] Initializing CPU#0
whee, time warp.
Ingo, Thomas: what's the story here? There've been zillions of reports
and I thought we'd already fixed it?
--
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/
Powered by blists - more mailing lists