mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Roger Larsson <roger.larsson@norran.net>
Cc: "'Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
	"'David Hinds'" <dahinds@users.sourceforge.net>
Subject: Re: UPD: "do_IRQ: near stack overflow" when inserting CF disk
Date: Fri, 12 Dec 2003 18:38:02 +0100	[thread overview]
Message-ID: <20031212173802.GK6112@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200312121652.23036.roger.larsson@norran.net>

On Fri, 12 December 2003 16:52:22 +0100, Roger Larsson wrote:
> 
> I get these three printouts when inserting a compact flash disk
> (SuSE Linux 2.4.21-144-smp) - is the stack intentionally this fit?
> or is it an unexpected code path?
> 
> I have had other interrupt related problems, it usually locks up :-(
> This time I run with "nosmp noapic"
> 
> The ide-cs is now forced to use irq 3 (When running noapic others
> seems busy... with apic and using irq 6 or 10 computer has
> locked up...)
> 
> I will try irq 3 without one of the options to see if the computer still
> survives...
> 
> - new data -
> 
> Easier said than done - they require each other!
> But I noticed that reducing 'stackwarn' and 'stackdefer'
> to under the level warned about helps (might be luck)
> 
> Summary:
>   Some routines allocate to much stack: validate_cis?
> 	several subtypes in the union cisparse_t are quite
> 	big (>250 bytes)
>   This eats stack (to much?) or only close enough to
>   trigger 'stackdefer' which might stress the drivers SMPness?

Can you send me your .config?  I'd like to run checkstack on it and
see what other functions in your trace consume too much stack.
David's patch shoundn't shave off more than 2k, so either my estimate
is wrong or there are more hungry wolves in your list.

Jörn

-- 
Beware of bugs in the above code; I have only proved it correct, but
not tried it.
-- Donald Knuth

      parent reply	other threads:[~2003-12-12 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 15:52 Roger Larsson
2003-12-12 16:59 ` David Hinds
2003-12-12 17:38 ` Jörn Engel [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=20031212173802.GK6112@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dahinds@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.larsson@norran.net \
    /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®