From: "Américo Wang" <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: sboyce-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: Boot failure 2.6.33 - 2.6.33-git12 inclusive
Date: Fri, 12 Mar 2010 11:01:55 +0800 [thread overview]
Message-ID: <2375c9f91003111901s77c4851emee33d9efe1f5bb14@mail.gmail.com> (raw)
In-Reply-To: <4B99736D.2070801-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org>
On Fri, Mar 12, 2010 at 6:49 AM, Sid Boyce <sboyce-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org> wrote:
> Same problem up to 2.6.33-git15 and 2.6.34-rc1. No response since posted
> to LKML last week.
> --------------------------------------------------
You need to Cc x86 people. Added.
>
> Asus Crosshair II motherboard, 4xCPU 8Gig storage fails, the M2N32-SLI
> 2x CPU, 4 Gig and laptop 2x CPU, 2 Gig have no problems running
> 2.6.33-git11 - all AMD CPU's.
> Lockup requiring a hard reset.
>
> 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
>
>
>
prev parent reply other threads:[~2010-03-12 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 22:49 Boot failure 2.6.33 - 2.6.33-git12 inclusive Sid Boyce
[not found] ` <4B99736D.2070801-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org>
2010-03-12 3:01 ` Américo Wang [this message]
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=2375c9f91003111901s77c4851emee33d9efe1f5bb14@mail.gmail.com \
--to=xiyou.wangcong-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
--cc=sboyce-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).