All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bongani Hlope <bonganilinux@mweb.co.za>
To: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre5 not easy to boot with devfs
Date: Sun, 02 Dec 2001 21:40:38 +0200	[thread overview]
Message-ID: <3C0A83B6.5060209@mweb.co.za> (raw)
In-Reply-To: <3C085FF3.813BAA57@wanadoo.fr> <9u9qas$1eo$1@penguin.transmeta.com> <200112010701.fB171N824084@vindaloo.ras.ucalgary.ca> <3C0898AD.FED8EF4A@wanadoo.fr>

I am using Mandrake 8.1 (I think it loads devfs on startup)
I have compiled  2.4.17-pre1 and i get the same oops.

Pierre Rousselet wrote:

> Richard Gooch wrote:
> 
>>Linus Torvalds writes:
>>
>>>In article <3C085FF3.813BAA57@wanadoo.fr>,
>>>Pierre Rousselet  <pierre.rousselet@wanadoo.fr> wrote:
>>>
>>>>As far as I can see,
>>>>
>>>>when CONFIG_DEBUG_KERNEL is set
>>>> and
>>>>when devfsd is started at boot time
>>>>I get an Oops when remounting, rw the root fs :
>>>>
>>>>Unable to handle kernel request at va 5a5a5a5e
>>>>
>>>POISON_BYTE is 0x5a. Something in devfs is using a pointer from a data
>>>structure that was already free'd, and was thus corrupted by poisoning.
>>>
>>>(the above is almost certainly just a pointer dereference off 0x5a5a5a5a
>>>with an offset of 4 for some entry at the beginning of a structure,
>>>which is why you get the final "5e" in the page fault address).
>>>
>>>
>>>>It boots OK with devfsd when CONFIG_DEBUG_KERNEL is not set.
>>>>It boots OK without devfsd when CONFIG_DEBUG_KERNEL is set (then devfsd
>>>>can be started after login).
>>>>
>>>Well, not poisoning the free'd memory makes it "work" only in the sense
>>>that usually the free'd memory hasn't been re-allocated yet, so you
>>>don't see the bug even if it is still there.
>>>
>>>Richard Gooch probably wants a full stack trace, with symbols. Which
>>>should show it fairly clearly. At least EIP and the first few "stack
>>>trace" entries..
>>>
>>Indeed I do. Please Cc: me on devfs related stuff. And please apply
>>devfs-patch-v200, which fixes a stupid typo. I'd also be interested in
>>knowing the behaviour with 2.4.17-pre1.


<snip very long config file>
.......
</snip>

I am using Mandrake 8.1 (I think it loads devfs on startup)
I have compiled  2.4.17-pre1 and i get the same oops.
2.4.16-pre1 does not seem to have a problem. I will try
2.4.17-pre2 and see how it goes.
-Bongani



  parent reply	other threads:[~2001-12-02 19:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  4:43 2.5.1-pre5 not easy to boot with devfs Pierre Rousselet
2001-12-01  5:01 ` Alexander Viro
2001-12-01  5:37 ` Linus Torvalds
2001-12-01  7:01   ` Richard Gooch
2001-12-01  8:45     ` Pierre Rousselet
2001-12-01 18:36       ` Richard Gooch
2001-12-01 20:37         ` Pierre Rousselet
2001-12-01 23:20           ` Richard Gooch
2001-12-02  1:11             ` Pierre Rousselet
2001-12-02 10:28               ` Pierre Rousselet
2001-12-02 16:59                 ` Alexander Viro
2001-12-02 17:14                   ` Alan Cox
2001-12-02 18:02                     ` Richard Gooch
2001-12-03 12:58                       ` Jens Axboe
2001-12-03 19:06                         ` Richard Gooch
2001-12-03 20:52                           ` Jens Axboe
2001-12-02 17:55                   ` Richard Gooch
2001-12-03 19:54                     ` Alexander Viro
2001-12-02 22:57                   ` Keith Owens
2001-12-03  4:50                     ` Pierre Rousselet
2001-12-02  8:05             ` Pierre Rousselet
2001-12-01 23:47           ` Richard Gooch
2001-12-02  7:11             ` Pierre Rousselet
2001-12-02 21:22               ` Richard Gooch
2001-12-02  9:27         ` Pierre Rousselet
2001-12-02 19:40       ` Bongani Hlope [this message]
2001-12-01  9:59     ` Pierre Rousselet
2001-12-03  6:33 ` Richard Gooch
2001-12-03  5:57   ` Pierre ROUSSELET
2001-12-03 12:16   ` Pierre Rousselet

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=3C0A83B6.5060209@mweb.co.za \
    --to=bonganilinux@mweb.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.rousselet@wanadoo.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.