From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: crash unrelated to sym53c8xx
Date: Thu, 2 Apr 2009 14:59:54 +0200 [thread overview]
Message-ID: <20090402125954.GD9784@develbox.linuxbox.cz> (raw)
In-Reply-To: <20090402124924.GP8014@parisc-linux.org>
> Yes, that's somewhat more useful ... the tail of the stack trace in the
> photo indicates this isn't (at least directly) a bug in the sym53c8xx
> driver. Can you get the rest of the crash message? netconsole might
> help here if you don't have a serial console.
OK, I'll try to get the whole message using IPMI console.
I'll post it in ~2 hours...
> 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 :)
next prev parent reply other threads:[~2009-04-02 12:59 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 [this message]
2009-04-02 13:01 ` Matthew Wilcox
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=20090402125954.GD9784@develbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--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