All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: LKML Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-x86_64@vger.kernel.org
Subject: Re: Fwd: Re: Boot failure 2.6.33 - 2.6.33-git12 - 2.6.34-rc2 inclusive
Date: Fri, 26 Mar 2010 04:16:21 +0000	[thread overview]
Message-ID: <4BAC3515.4030708@blueyonder.co.uk> (raw)
In-Reply-To: <4BA233A9.1030407@blueyonder.co.uk>

Problem still exists at 2.6.34-rc2-git2.
Motherboard/CPU/memory has been changed to Asus Crosshair III/AMD
Phenom(tm) II X4 965 Processor/8GB DDR3. Rebuilt kernel on the new
motherboard.
I notice that a kernel that boots generates far more output than I see
with kernels up to 2.6.34-rc2-git2, tried and rebuilt without netconsole.

Here is the full output
========================
==== 4 Penguins appear, then the following output and the freeze ====
Console: switching to colour frame buffer device 160x64
fb0: VESA VGA frame buffer device
Initializing Nozomi driver 2.1d (build date: Mar 25 2010 13:37:52)
Non-volatile memory driver 1.3
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 8 ports, IRQ sharing disables
Console [netcon0] enabled
netconsole: network logging started
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
registered taskstats version 1
Kmemleak: kernel memory leak detector initialized
Kmemleak: Automatic memory scanning thread started
No TPM chip found, activating TPM-bypass!
Freeing unused kernel memory: 688K freed
Write Protecting kernel memory read-only data: 6144K
Testing CPA: undo ffffffff81000000 - ffffffff81600000
Testing CPA: again
Freeing unused kernel memory: 964K freed
Freeing unused kernel memory: 212K freed
init[1] segfault at ffffffff8100eea8 ip ffffffff8100eea8 sp
00007fff62e804b8 error 15
kernel panic - not syncing: Attempted to kill init!
Pid: 1,comm: init not tainted 2.6.33-git12-smp #2
Call Trace:
[<ffffffff81300876>] panic+0x73/0xfa
[<ffffffff8104b45c>] do_exit+0x6d/0x713
[<ffffffff8104bd85>] do_group_exit+0x72/0x9b
[<ffffffff8105917e>] get_signal_to_deliver+0x356/0x375
[<ffffffff8130310b>] ? _raw_spin_unlock_irqrestore+0x2f/0x34
[<ffffffff81007fc3>] do_signal+0x6d/0x660
[<ffffffff81300939>] ? printk+0x3c/0x43
[<ffffffff8100eea8>] ? rdtsc_barrier+0x0/0xc
[<ffffffff81300939>] ? printk+0x3c/0x43
[<ffffffff8102b78c>] ? __bad_area_nosemaphore+0x183/0x1ad
[<ffffffff8100eea8>] ? rdtsc_barrier+0x0/0xc
[<ffffffff810085fc>] do_notify_resume+0x27/0x69
[<ffffffff8130351c>] retint_signal+0x48/0x8c
[<ffffffff8100eea8>] ? rdtsc_barrier+0x0/0xc
Regards
Sid.

-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


  parent reply	other threads:[~2010-03-26  4:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B9A4337.9030609@blueyonder.co.uk>
2010-03-18 14:07 ` Fwd: Re: Boot failure 2.6.33 - 2.6.33-git12 inclusive Sid Boyce
2010-03-24 14:44   ` Fwd: Re: Boot failure 2.6.33 - 2.6.33-git12 - 2.6.34-rc2 inclusive Sid Boyce
2010-03-26  4:16   ` Sid Boyce [this message]
2010-04-03 20:28     ` Sid Boyce

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=4BAC3515.4030708@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.