From: Georg Schild <dangertools@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc[2|3] protection fault on /proc/devices
Date: Tue, 07 Dec 2004 09:31:20 +0100 [thread overview]
Message-ID: <41B56A58.8050404@gmx.net> (raw)
In-Reply-To: <20041206234044.51667e94.akpm@osdl.org>
Andrew Morton wrote:
> Georg Schild <dangertools@gmx.net> wrote:
>
>>Since 2.6.10-rc2 I am having problems accessing /proc/devices. On
>>startup some init-skripts access this node and print out a protection
>>fault. i am having this on pcmcia and swap startup. My system is an
>>amd64 @3000+ in an Acer Aspire 1501Lmi at 64bit mode running gentoo.
>>.config is the same as on 2.6.10-rc1 which works good. cat on
>>/proc/devices gives the same problems. The kernel has just a patch for
>>wbsd (builtin mmc-cardreader) from Pierre Ossman in use, everything else
>>is vanilla. Does anyone know of this issue and perhaps on how to solve this?
>>
>>
> How odd. All I can think is that something has registered a zillion
> devices and get_blkdev_list() has run off the /proc page. But then, it
> should have oopsed in sprintf()..
>
> Still. Please send a copy of your /proc/devices from 2.6.10-rc1 and also
> apply this:
>
> to 2.6.10-rc3 and see if that fixes it. If so, please send the
> /proc/devices content from this kernel.
>
> Beyond that, perhaps something scribbled on the data structures in there.
> Setting CONFIG_SLAB_DEBUG and/or CONFIG_DEBUG_PAGEALLOC might turn
> something up.
I have tried now with applied patch against the vanilla-sources, that
means without the wbsd-patch, nothing changed. same is with the
wbsd-patch. i did a complete rebuild (make clean etc.) everytime. How
can i enable some debugging?
next prev parent reply other threads:[~2004-12-07 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 23:11 2.6.10-rc[2|3] protection fault on /proc/devices Georg Schild
2004-12-07 7:40 ` Andrew Morton
2004-12-07 7:50 ` Georg Schild
2004-12-07 8:31 ` Georg Schild [this message]
2004-12-07 9:05 ` Andrew Morton
2004-12-07 9:02 ` Georg Schild
2004-12-07 15:29 ` George Alexandru Dragoi
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=41B56A58.8050404@gmx.net \
--to=dangertools@gmx.net \
--cc=linux-kernel@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