From: Matthew Wilcox <matthew@wil.cx>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: crash unrelated to sym53c8xx
Date: Thu, 2 Apr 2009 07:01:56 -0600 [thread overview]
Message-ID: <20090402130156.GQ8014@parisc-linux.org> (raw)
In-Reply-To: <20090402125954.GD9784@develbox.linuxbox.cz>
On Thu, Apr 02, 2009 at 02:59:54PM +0200, Nikola Ciprich wrote:
> > There's a few reasons this warning hasn't been fixed yet:
> >
> > - It only appears on module unload. Most people don't unload sym53c8xx.
> > - The problem that it's warning about is only a problem on ARM.
> > There's not a huge userbase of ARM users with sym53c8xx cards.
> > - Fixing it requires a fairly large rewrite of how sym2 manages its
> > memory. I've done about half the work required, but I've basically
> > run out of interest.
> Hmm, maybe I don't understand what You mean by ARM, but it's i686 machine,
> not arm (actually it's opteron, but running i686 OS).
> but if it's reallu harmless, I don't have that big problem with it. only the crashes
> really worry me :)
The warning is there on x86 to warn us that we're doing something that
will cause problems on ARM.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-04-02 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 7:54 sym53c8xx: WARNING on module unload, crashes on further usage Nikola Ciprich
2009-04-02 11:23 ` Matthew Wilcox
2009-04-02 12:26 ` Nikola Ciprich
2009-04-02 12:28 ` Nikola Ciprich
2009-04-02 12:49 ` crash unrelated to sym53c8xx Matthew Wilcox
2009-04-02 12:59 ` Nikola Ciprich
2009-04-02 13:01 ` Matthew Wilcox [this message]
2009-04-02 19:39 ` Nikola Ciprich
2009-04-08 8:30 ` Nikola Ciprich
2009-04-08 8:42 ` FUJITA Tomonori
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=20090402130156.GQ8014@parisc-linux.org \
--to=matthew@wil.cx \
--cc=extmaillist@linuxbox.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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