linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: devzero@web.de
To: dgilbert@interlog.com
Cc: linux-scsi@vger.kernel.org,
	Smartmontools Mailing List
	<smartmontools-support@lists.sourceforge.net>,
	support@lsi.com
Subject: Re: fw: smartd crashing recent 2.6.32 kernel
Date: Wed, 27 Jan 2010 13:49:54 +0100	[thread overview]
Message-ID: <1115608744@web.de> (raw)

> Running 'smartd -r ioctl,1' from the command line might
> help us find which command it didn't like. That will
> send information to the log. If the crash truncates the
> log then add '-d' to the above invocation to dump debug
> information to the console. 

thanks!

here we go:

smartd -r ioctl,1 -d
smartd 5.39 2009-08-08 r2872~ [i686-pc-linux-gnu] (openSUSE RPM)
Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net

Opened configuration file /etc/smartd.conf
Drive: DEVICESCAN, implied '-a' Directive on line 26 of file /etc/smartd.conf
Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
glob(3) found no matches for pattern /dev/hd[a-t]
 [inquiry: 12 00 00 00 24 00 ]
  scsi_status=0x0, host_status=0x0, driver_status=0x0
  info=0x0  duration=0 milliseconds  resid=0
  status=0x0
Device: /dev/sda, opened
 [test unit ready: 00 00 00 00 00 00 ]
  scsi_status=0x0, host_status=0x0, driver_status=0x0
  info=0x0  duration=0 milliseconds  resid=0
  status=0x0
 [mode sense(6): 1a 00 1c 00 40 00 ]
Killed
[box freezed here]

>Information about the disks would be useful as well.

3x MAP 3367NC-V4 , 36GB -  2 Disks Raid1, 1 Disk Hotspare

> Does the megaraid controller have the latest firmware
> from LSI?

it didn`t (had 1F30) but it has 1F56 now. ( did an update with latest available from http://support.ts.fujitsu.com/Download/ShowDescription.asp?SoftwareGUID=873EAF12-50EA-4EB1-B48E-D8E9C9929EA4&OSID=BD62ED52-DB04-417E-8A72-A3BA96295B00&Status=True&Component=MegaRAID%20SCSI%20U320-1 ) 

problem still exists with the latest firmware.

regards
roland


> devzero@web.de wrote:
> > 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)
> 
> Roland,
> Running 'smartd -r ioctl,1' from the command line might
> help us find which command it didn't like. That will
> send information to the log. If the crash truncates the
> log then add '-d' to the above invocation to dump debug
> information to the console. Information about the disks
> would be useful as well.
> 
> Does the megaraid controller have the latest firmware
> from LSI?
> 
> https://bugzilla.novell.com/show_bug.cgi?id=573244
> 
> Doug Gilbert
> 
> 
> >> -----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
> 
> 


______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de

--
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-27 12:50 UTC|newest]

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

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=1115608744@web.de \
    --to=devzero@web.de \
    --cc=dgilbert@interlog.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).