From: Andrew Morton <akpm@osdl.org>
To: Cal Peake <cp@absolutedigital.net>
Cc: torvalds@osdl.org, perex@suse.cz, linux-kernel@vger.kernel.org,
rostedt@goodmis.org
Subject: Re: Linux 2.6.13-rc4 (snd-cs46xx)
Date: Fri, 29 Jul 2005 12:51:35 -0700 [thread overview]
Message-ID: <20050729125135.19205830.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0507291315010.869@lancer.cnet.absolutedigital.net>
Cal Peake <cp@absolutedigital.net> wrote:
>
> On Thu, 28 Jul 2005, Andrew Morton wrote:
>
> > The procfs inode IDR tree is scrogged. I'd be suspecting a random memory
> > scribble. I'd suggest that you enable CONFIG_DEBUG_SLAB,
> > CONFIG_DEBUG_PAGEALLOC, CONFIG_DEBUG_everything_else and retest.
> >
> > If that doesn't show anything, try eliminating stuff from your kernel
> > config.
> >
> > If it _is_ a scribble then there's a good chance that changing the config
> > will simply make it disappear, or will make it manifest in different ways.
>
> Thanks Andrew! Indeed your suspicions are correct. Adding in all the
> debugging moved the problem around, it now shows itself when probing
> parport. Upon further investigation reverting the commit below seems to
> have nixed the problem.
>
> [PATCH] speed up on find_first_bit for i386 (let compiler do the work)
Thanks a million for that.
next prev parent reply other threads:[~2005-07-29 19:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 23:34 Linux 2.6.13-rc4 Linus Torvalds
2005-07-29 3:54 ` Linux 2.6.13-rc4 (snd-cs46xx) Cal Peake
2005-07-29 4:35 ` Andrew Morton
2005-07-29 17:16 ` Cal Peake
2005-07-29 17:29 ` Linus Torvalds
2005-07-29 17:49 ` Cal Peake
2005-07-29 19:01 ` Steven Rostedt
2005-08-02 16:13 ` Bill Davidsen
2005-08-02 16:15 ` Steven Rostedt
2005-07-29 19:51 ` Andrew Morton [this message]
2005-07-29 16:48 ` Linux 2.6.13-rc4 Jesper Juhl
2005-07-29 23:41 ` 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=20050729125135.19205830.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cp@absolutedigital.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®