mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Gregor Suhr <Gregor@Suhr.home.cs.tu-berlin.de>
Cc: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: OOPS  at boot in 2.4.17-rc[12]  (kernel BUG at slab.c:815) maybe  devfs
Date: Fri, 21 Dec 2001 15:02:23 -0700	[thread overview]
Message-ID: <200112212202.fBLM2N717016@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <3C23A022.5040307@Suhr.home.cs.tu-berlin.de>
In-Reply-To: <3C210AB9.5000900@suhr.home.cs.tu-berlin.de> <200112202338.fBKNcCI05673@vindaloo.ras.ucalgary.ca> <3C227F0E.E6A9CF76@zip.com.au> <3C23842A.20407@Suhr.home.cs.tu-berlin.de> <200112211926.fBLJQ7814544@vindaloo.ras.ucalgary.ca> <3C23A022.5040307@Suhr.home.cs.tu-berlin.de>

Gregor Suhr writes:
> >
> >
> >
> >Now this is useful information! I see what's caused this: the second
> >mount of devfs (because you're using initrd) is creating the
> >devfsd_event slab cache again, which is a bug. I've appended a patch
> >which fixes this. Please test it out and let me know how it goes.
> >
> I applied the patch to 2.4.17 and it seems to work well (the system came 
> up).

Great.

> Do you have an idea how I can solve the err. -17 error or may i realy 
> ignore it?

I've added a section to the devfs FAQ to answer this.
http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-12-21 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C23843A.3040904@Suhr.home.cs.tu-berlin.de>
2001-12-19 21:46 ` Gregor Suhr
2001-12-20 23:38   ` Richard Gooch
2001-12-21  0:15     ` Andrew Morton
     [not found]       ` <3C23842A.20407@Suhr.home.cs.tu-berlin.de>
     [not found]         ` <200112211926.fBLJQ7814544@vindaloo.ras.ucalgary.ca>
2001-12-21 20:05           ` Richard Gooch
2001-12-21 22:02           ` Richard Gooch [this message]
2001-12-21 19:16     ` Richard Gooch

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=200112212202.fBLM2N717016@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=Gregor@Suhr.home.cs.tu-berlin.de \
    --cc=akpm@zip.com.au \
    --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
all inboxes | Powered by JetHome®