All of lore.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-scsi@vger.kernel.org
Cc: support@lsi.com
Subject: fw: smartd crashing recent 2.6.32 kernel
Date: Tue, 26 Jan 2010 23:01:07 +0100	[thread overview]
Message-ID: <1114886585@web.de> (raw)

maybe someone has a clue....!?

see https://bugzillafiles.novell.org/attachment.cgi?id=338427

that box seems to crash in megaraid_mbox driver as soon as smartd is starting - even with recent 2.6.32 kernel.

as this box will go into production between mid/end of february, i think that is not much time if there is something to fix (and then being tested/confirmed to be fixed)

regards
roland


> -----Ursprüngliche Nachricht-----
> Von: <devzero@web.de>
> Gesendet: 25.01.10 12:15:09
> An: smartmontools-support@lists.sourceforge.net
> Betreff: smartd crashing recent 2.6.32 kernel
> Hi, 
> 
> just wanted to let you know that smartd is crashing my system at late installation stage.
> 
> have opened novell bugticket #573244 ( https://bugzilla.novell.com/show_bug.cgi?id=573244 ) for this.
> 
> regards
> roland
> 


________________________________________________________________
Nur noch bis 31.01.2010: DSL Komplettpaket für 16,99 Euro/mtl.!*
http://produkte.web.de/go/02/

--
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

             reply	other threads:[~2010-01-26 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 22:01 devzero [this message]
2010-01-27  4:22 ` fw: smartd crashing recent 2.6.32 kernel Douglas Gilbert
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27 12:49 devzero

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=1114886585@web.de \
    --to=devzero@web.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=support@lsi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.