mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: David Brownell <david-b@pacbell.net>
Cc: Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOPS in 2.5.3-pre5 -- kernel BUG at slab.c:1101!
Date: 25 Jan 2002 13:01:39 -0800	[thread overview]
Message-ID: <1011992500.1251.0.camel@stomata.megapathdsl.net> (raw)
In-Reply-To: <03aa01c1a5d8$1d4d2ac0$6800000a@brownell.org>
In-Reply-To: <1011939163.1540.18.camel@stomata.megapathdsl.net> <1011986299.1370.77.camel@stomata.megapathdsl.net>  <03aa01c1a5d8$1d4d2ac0$6800000a@brownell.org>

On Fri, 2002-01-25 at 11:39, David Brownell wrote:
> > David and Greg, I think this OOPS may be related to the
> > new EHCI/ohci-hcd code.  This machine has an early NEC
> > USB 2.0 host controller and an USB OHCI host controller:
> 
> Configure with CONFIG_DEBUG_SLAB and it should go
> away.  Or, tweak drivers/usb/hcd/ohci-mem.c line 45 to
> be #ifdef CONFIG_DEBUG_SLAB.  A patch is pending,
> but it's included with some other updates to that code
> and I wanted to re-test.
> 
> Or a more fundamental fix would be to remove those
> #ifdefs from the EHCI and OHCI HCD code and just
> change drivers/pci/pci.c at about line 1065 to poison
> based on CONFIG_DEBUG_SLAB rather than using
> CONFIG_PCIPOOL_DEBUG ... that #ifdef predates
> CONFIG_DEBUG_SLAB.

Thanks, that worked.

	Miles



      parent reply	other threads:[~2002-01-25 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  6:12 OOPS in 2.5.3-pre5 -- kernel BUG at slab.c:1101! -- >>EIP; c012b1e6 <kmem_cache_grow+26/250> <===== Miles Lane
     [not found] ` <1011986299.1370.77.camel@stomata.megapathdsl.net>
2002-01-25 19:39   ` OOPS in 2.5.3-pre5 -- kernel BUG at slab.c:1101! David Brownell
2002-01-25 21:01   ` Miles Lane [this message]

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=1011992500.1251.0.camel@stomata.megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®