From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754822AbYE2I13 (ORCPT ); Thu, 29 May 2008 04:27:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751379AbYE2I1W (ORCPT ); Thu, 29 May 2008 04:27:22 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:54158 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751745AbYE2I1U (ORCPT ); Thu, 29 May 2008 04:27:20 -0400 Date: Thu, 29 May 2008 01:26:52 -0700 From: Andrew Morton To: alejandro.riveira@gmail.com Cc: linux-kernel , Ingo Molnar , Thomas Gleixner Subject: Re: two different oopses with 2.6.26-rc4 Message-Id: <20080529012652.6b9027a3.akpm@linux-foundation.org> In-Reply-To: <1211968234.9895.7.camel@Varda> References: <1211968234.9895.7.camel@Varda> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 May 2008 11:50:34 +0200 Alejandro Riveira Fern__ndez 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?