From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: [PATCH] TX49 MFC0 bug workaround
Date: Tue, 07 Feb 2006 18:32:20 +0300 [thread overview]
Message-ID: <43E8BD84.60308@ru.mvista.com> (raw)
In-Reply-To: <20060203.112253.104030567.nemoto@toshiba-tops.co.jp>
Hello.
Atsushi Nemoto wrote:
>>>>>>On Fri, 03 Feb 2006 05:12:47 +0300, Sergei Shtylylov <sshtylyov@ru.mvista.com> said:
>
> sshtylyov> If I don't mistake, the offending code is in
> sshtylyov> local_irq_disable, local_irq_save, and local_irq_restore
> sshtylyov> macros. The effect would be a crash on any exception taken
> sshtylyov> once interrupts get disabled in a module (*and* that code
> sshtylyov> happens to fall on a page boundary)... nasty. :-(
... and yet worse: any external interrupts actually blocked from CPU
forever by Status.EXL set (which then will never be cleared after the errata
triggers).
> Right. And it can really happen.
> ---
> Atsushi Nemoto
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: [PATCH] TX49 MFC0 bug workaround
Date: Tue, 07 Feb 2006 18:32:20 +0300 [thread overview]
Message-ID: <43E8BD84.60308@ru.mvista.com> (raw)
Message-ID: <20060207153220.XwutJ9xxeq2tGnlMttuexHSa6r7qAxhUsZO7ZnJ88Kc@z> (raw)
In-Reply-To: <20060203.112253.104030567.nemoto@toshiba-tops.co.jp>
Hello.
Atsushi Nemoto wrote:
>>>>>>On Fri, 03 Feb 2006 05:12:47 +0300, Sergei Shtylylov <sshtylyov@ru.mvista.com> said:
>
> sshtylyov> If I don't mistake, the offending code is in
> sshtylyov> local_irq_disable, local_irq_save, and local_irq_restore
> sshtylyov> macros. The effect would be a crash on any exception taken
> sshtylyov> once interrupts get disabled in a module (*and* that code
> sshtylyov> happens to fall on a page boundary)... nasty. :-(
... and yet worse: any external interrupts actually blocked from CPU
forever by Status.EXL set (which then will never be cleared after the errata
triggers).
> Right. And it can really happen.
> ---
> Atsushi Nemoto
WBR, Sergei
next prev parent reply other threads:[~2006-02-07 15:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 16:34 [PATCH] TX49 MFC0 bug workaround Atsushi Nemoto
2006-02-02 16:38 ` Maciej W. Rozycki
2006-02-02 16:56 ` Ralf Baechle
2006-02-02 17:04 ` Atsushi Nemoto
2006-02-02 17:21 ` Atsushi Nemoto
2006-02-02 17:24 ` Ralf Baechle
2006-02-03 2:10 ` Atsushi Nemoto
2006-02-03 10:17 ` Maciej W. Rozycki
2006-02-03 14:44 ` Ralf Baechle
2006-02-06 9:36 ` Atsushi Nemoto
2006-02-06 23:22 ` Ralf Baechle
2006-02-03 2:26 ` Sergei Shtylylov
2006-02-03 2:50 ` Atsushi Nemoto
2006-02-02 16:46 ` Ralf Baechle
2006-02-02 18:46 ` Sergei Shtylylov
2006-02-02 22:11 ` Ralf Baechle
2006-02-03 1:17 ` Atsushi Nemoto
2006-02-03 2:12 ` Sergei Shtylylov
2006-02-03 2:22 ` Atsushi Nemoto
2006-02-07 15:32 ` Sergei Shtylylov [this message]
2006-02-07 15:32 ` Sergei Shtylylov
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=43E8BD84.60308@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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