public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Meelis Roos <mroos@linux.ee>
Cc: David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: boot panic after oops from sysfs_new_dirent
Date: Tue, 01 Sep 2009 16:14:49 +0900	[thread overview]
Message-ID: <4A9CC9E9.2070609@kernel.org> (raw)
In-Reply-To: <Pine.SOC.4.64.0909011003460.10184@math.ut.ee>

Meelis Roos wrote:
>>> I powered on my 6-CPU E3000 after a summer pause and tried todays 
>>> 2.6.31-rc8+git on it. It fails - first it spills lots of warnings about 
>>> percpu things, then oopses in sysfs_new_dirent and then panics.
> 
> Bisecting shows that there may be different crashes, like in
> 56513ed50cc8a5c184a3f347e81d74c850cc14fa below:

Yeah, I was trying to fix that one with
74d46d6b2d23d44d72c37df4c6a5d2e782f7b088 and it seemingly fixed it on
my machine.  Apparently broken on yours.  Are the errors different
before and after 74d46d6b2d?

Thanks.

-- 
tejun

  reply	other threads:[~2009-09-01  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SOC.4.64.0908311646150.20934@math.ut.ee>
2009-08-31 21:22 ` boot panic after oops from sysfs_new_dirent David Miller
2009-09-01  7:05   ` Meelis Roos
2009-09-01  7:14     ` Tejun Heo [this message]
2009-09-01  7:30       ` Tejun Heo
2009-09-01  7:33         ` Meelis Roos
2009-09-01  7:58           ` Tejun Heo
2009-09-01 11:48             ` Meelis Roos
2009-09-01 12:30               ` [PATCH] percpu: don't assume existence of cpu0 Tejun Heo
2009-09-01 22:52                 ` David Miller

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=4A9CC9E9.2070609@kernel.org \
    --to=tj@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=sparclinux@vger.kernel.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