All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: alejandro.riveira@gmail.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: two different oopses with 2.6.26-rc4
Date: Thu, 29 May 2008 10:16:03 -0400	[thread overview]
Message-ID: <18494.47779.691031.764494@stoffel.org> (raw)
In-Reply-To: <20080529012652.6b9027a3.akpm@linux-foundation.org>

>>>>> "Andrew" == Andrew Morton <akpm@linux-foundation.org> writes:

Andrew> On Wed, 28 May 2008 11:50:34 +0200 Alejandro Riveira Fern__ndez  <alejandro.riveira@gmail.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

Andrew> whee, time warp.

Andrew> Ingo, Thomas: what's the story here?  There've been zillions of reports
Andrew> and I thought we'd already fixed it?

I'm seeing the same type of timewarp on a 2.6.26-rc4 x86_64 running
with a pretty recent ASUS m2n-sli deluxe mobo with AMD x2 CPU.

  [    0.000000] PM: Registered nosave memory: 00000000fec00000 -
  0000000100000000
  [    0.000000] Allocating PCI resources starting at e0000000 (gap:
  dff00000:10100000)
  [    0.000000] SMP: Allowing 4 CPUs, 2 hotplug CPUs
  [    0.000000] PERCPU: Allocating 33540 bytes of per cpu data
  [    0.000000] NR_CPUS: 8, nr_cpu_ids: 4
  [4294014.506571] Built 1 zonelists in Node order, mobility grouping
  on.  Total pages: 1030169
  [4294014.506571] Policy zone: Normal
  [4294014.506571] Kernel command line: root=/dev/sda2 ro
  earlyprintk=vga
  [4294014.506571] Initializing CPU#0
  [4294014.506571] Preemptible RCU implementation.
  [4294014.506571] PID hash table entries: 4096 (order: 12, 32768 byt


Haven't investigated in depth yet, but just chiming in with a report.

John

  parent reply	other threads:[~2008-05-29 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28  9:50 two different oopses with 2.6.26-rc4 Alejandro Riveira Fernández
2008-05-28 10:05 ` Johannes Berg
2008-05-29  8:26 ` Andrew Morton
2008-05-29  9:14   ` Gabriel C
2008-05-29  9:24     ` Peter Zijlstra
2008-05-29 14:16   ` John Stoffel [this message]
2008-05-29  8:31 ` Andrew Morton

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=18494.47779.691031.764494@stoffel.org \
    --to=john@stoffel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alejandro.riveira@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.