From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
rdunlap@xenotime.net, LKML <linux-kernel@vger.kernel.org>
Subject: [BUG] Re: [broken-out-2007-07-20-00-22] kernel bug at kernel/params:570
Date: Sat, 21 Jul 2007 12:09:18 +0530 [thread overview]
Message-ID: <a781481a0707202339s59b8a10bheb1e97773dcd027@mail.gmail.com> (raw)
In-Reply-To: <a781481a0707202300t781345afu1ca1154a1d14e5d8@mail.gmail.com>
On 7/21/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> [...]
> %eax == ffffffea == -22 == -EINVAL.
>
> But:
>
> When I replace the BUG_ON() with Greg's (or my modified) patch,
> the kernel ignores that error as we wanted, but _still_ crashes before
> finding the root block device (because ATA is not in kernel and my
> system seems to require it). Unfortunately, lots of dmesg output
> has scrolled up by then, and our "printk" is lost. Because of no
> CONFIG_ATA, nothing gets written to disk either.
The following hack worked:
if (ret) {
printk("~~~~~ .%s.%d.%s. ~~~~~\n", name, ret, kparam->name);
for (;;)
cpu_relax();
}
So I just hung my testbox at the point the info I wanted was printed out :-)
I hand-copied the following from the screen:
*****
The kobject at, or inside cpu_devices+0x10/0xe0 is not dynamically
allocated.
The kobject at, or inside cpu_devices+0x10/0xe0 is not dynamically
allocated. (printed twice)
WARNING: at lib/kobject.c:220 kobject_shadow_add()
...
show_trace
dump_stack
...
kobject_shadow_add+0x65/0x1b6
kobject_add
kernel_param_sysfs_setup
param_sysfs_init
...
...
~~~~~ ..-22.mtrr.show. ~~~~~
*****
Something wrong with "cpu_devices" and "mtrr.show" in 22-mm1 me thinks.
Wonder if latest -git is already fixed? Spent 4 hours on this, at least :-p
BTW "kobject at, or inside cpu_devices+0x10/0xe0 is not dynamically
allocated" sounds like something that could, and should, have been
caught at build time ...
Satyam
next prev parent reply other threads:[~2007-07-21 6:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 16:32 Michal Piotrowski
2007-07-20 22:50 ` Greg KH
2007-07-20 22:59 ` Andrew Morton
2007-07-20 23:10 ` Greg KH
2007-07-20 23:37 ` Randy Dunlap
2007-07-20 23:43 ` Satyam Sharma
2007-07-21 0:03 ` Satyam Sharma
2007-07-21 0:28 ` Michal Piotrowski
2007-07-21 1:02 ` Greg KH
2007-07-21 1:37 ` Andrew Morton
2007-07-21 1:44 ` Greg KH
2007-07-21 3:21 ` Satyam Sharma
2007-07-21 3:57 ` Satyam Sharma
2007-07-21 6:00 ` Satyam Sharma
2007-07-21 6:39 ` Satyam Sharma [this message]
2007-07-21 8:11 ` Michal Piotrowski
2007-07-21 8:00 ` Michal Piotrowski
2007-07-21 8:36 ` Satyam Sharma
2007-07-21 8:41 ` Michal Piotrowski
2007-07-21 16:00 ` Michal Piotrowski
2007-07-21 16:41 ` Andi Kleen
2007-07-21 16:52 ` Michal Piotrowski
2007-07-21 16:55 ` Michal Piotrowski
2007-07-21 18:11 ` Michal Piotrowski
2007-07-21 18:24 ` Andi Kleen
2007-07-22 17:51 ` Satyam Sharma
2007-07-21 19:13 ` Andrew Morton
2007-07-21 19:31 ` Michal Piotrowski
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=a781481a0707202339s59b8a10bheb1e97773dcd027@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®