public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
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 21:39:27 +0200	[thread overview]
Message-ID: <20090402193927.GA7106@nik-comp.linuxbox.cz> (raw)
In-Reply-To: <20090402130156.GQ8014@parisc-linux.org>

OK, now I understand, thanks for explaining...
unfortunately I'm now unable to reproduce the crash including backtrace, machine always
hangs completely without any error reported :(
I've setup netconsole logging and I'll wait if it crashes and report something during normal
usage.
I'll report if it happens.
thanks for Your time.
have a nice day
nik

On Thu, Apr 02, 2009 at 07:01:56AM -0600, Matthew Wilcox wrote:
> 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."
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2009-04-02 20:00 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
2009-04-02 19:39             ` Nikola Ciprich [this message]
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=20090402193927.GA7106@nik-comp.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