mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Sumit Pandya <sumit@elitecore.com>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Infinite do_IRQ
Date: Thu, 20 Nov 2003 11:05:29 +0100	[thread overview]
Message-ID: <20031120100529.GA2843@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0311191032090.11537@montezuma.fsmlabs.com>

On Wed, 19 November 2003 23:12:58 -0500, Zwane Mwaikambo wrote:
> On Wed, 19 Nov 2003, Sumit Pandya wrote:
> 
> > Hi Zwane,
> >     I'm sorry to bother you again. Following is output from
> > http://kernelnewbies.org/scripts/check-stack.sh
> 
> I think it'd really be easier to back out those patches one by one until 
> your messages stop happening. Otherwise i'm not quite sure which one is 
> really affecting you.

Agreed.  Still, tiny comments on the below.

> > 410 cdrom_number_of_slots
> > 410 cdrom_select_disc
> > 410 cdrom_slot_status
> > 444 cdrom_ioctl

Why do you use the mess from drivers/cdrom?  Unless you have one of
those old cdroms attached to your soundcard, better get rid of them.

> > 47c ide_unregister
> > 490 inflate_fixed
> > 524 inflate_dynamic
> > 5a8 huft_build

Old known problems, no bug reports about the ever.  Should be safe.

> > 73c sanitize_e820_map

This one is new to me.  Does it exist in plain 2.4.22 as well?


Anyway, backing out patches is the way to go.


Jörn

-- 
Happiness isn't having what you want, it's wanting what you have.
-- unknown

  reply	other threads:[~2003-11-20 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  7:28 Sumit Pandya
2003-11-19  8:47 ` Zwane Mwaikambo
2003-11-19 14:44   ` Sumit Pandya
2003-11-20  4:12     ` Zwane Mwaikambo
2003-11-20 10:05       ` Jörn Engel [this message]
2003-11-20 10:08 ` Jörn Engel

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=20031120100529.GA2843@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sumit@elitecore.com \
    --cc=zwane@arm.linux.org.uk \
    /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®