From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: 2.5.13 IDE and preemptible kernel problems
Date: Fri, 03 May 2002 16:57:18 +0200 [thread overview]
Message-ID: <3CD2A54E.2070404@evision-ventures.com> (raw)
In-Reply-To: <20020503173859.A1016@averell>
Uz.ytkownik Andi Kleen napisa?:
> Hi,
>
> When booting an preemptible kernel 2.5.13 kernel on x86-64 I get
> very quickly an scheduling in interrupt BUG. It looks like the
> preempt_count becomes 0 inside the ATA interrupt handler. This
> could happen when save_flags/restore_flags and friends are unmatched
> and you have too many flags restores in IDE.
Thank you for pointing out. I will re check it.
next prev parent reply other threads:[~2002-05-03 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 15:38 2.5.13 IDE and preemptible kernel problems Andi Kleen
2002-05-03 14:57 ` Martin Dalecki [this message]
2002-05-03 18:14 ` Linus Torvalds
2002-05-04 23:58 ` Martin Dalecki
2002-05-05 0:24 ` Martin Dalecki
2002-05-05 2:09 ` Linus Torvalds
2002-05-05 7:04 ` Tim Schmielau
[not found] ` <3CD4E1DC.9040704@linuxhq.com>
2002-05-05 15:13 ` Martin Dalecki
2002-05-06 16:01 ` Alan Cox
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=3CD2A54E.2070404@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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