From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jos van der Ende <seraph@xs4all.nl>
Cc: Matthew Wilcox <matthew@wil.cx>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev
Date: Wed, 02 Apr 2008 10:49:19 -0500 [thread overview]
Message-ID: <1207151359.3082.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20080402160920.dc219007.seraph@xs4all.nl>
On Wed, 2008-04-02 at 16:09 +0200, Jos van der Ende wrote:
> Finally, bisecting is done. :-)
Thanks for doing this ... we'd never have found it by looking at the
driver code ...
> Well, it took more reboots than a typical Windows XP installation (and
> thank the heavens for my Sparc64 cross compiler on my Core 2 Duo), but
> this seems to be the culprit:
>
> 5a606b72a4309a656cd1a19ad137dc5557c4b8ea is first bad commit
Reading the code for this, it seems that something fiddled with the
IRQ_DISABLED or IRQ_PENDING flags when it came time for the ->eoi() so
the gem interrupt is always held pending (because it's never ended).
Since the sym2 is on interrupts 16 and 17 and gem on 11 (and the
descriptors are separate entities in the irq_desc array) I can't really
see how sym2 would be doing this.
James
next prev parent reply other threads:[~2008-04-02 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10374-10286@http.bugzilla.kernel.org/>
2008-04-01 8:15 ` [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev Andrew Morton
2008-04-01 8:58 ` Jos van der Ende
2008-04-01 14:11 ` James Bottomley
2008-04-01 14:47 ` Jos van der Ende
2008-04-01 19:05 ` Jos van der Ende
2008-04-01 20:19 ` James Bottomley
2008-04-01 20:57 ` Jos van der Ende
2008-04-01 21:14 ` James Bottomley
2008-04-01 22:30 ` Jos van der Ende
2008-04-02 10:29 ` Jos van der Ende
2008-04-02 12:06 ` Matthew Wilcox
2008-04-02 14:09 ` Jos van der Ende
2008-04-02 15:49 ` James Bottomley [this message]
2008-04-02 16:06 ` Jos van der Ende
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=1207151359.3082.36.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=seraph@xs4all.nl \
--cc=sparclinux@vger.kernel.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