public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Sreenivas.Bagalkote@lsil.com, Sumant.Patro@lsil.com,
	jeff@garzik.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: megaraid_sas suspend ok, resume oops
Date: Tue, 29 Aug 2006 10:15:18 +0200	[thread overview]
Message-ID: <20060829081518.GD12257@kernel.dk> (raw)
In-Reply-To: <b6a2187b0608281004g30706834r96d5d24f85e82cc9@mail.gmail.com>

On Tue, Aug 29 2006, Jeff Chua wrote:
> Anyone working on suspend/resume for the Megaraid SAS RAID card?
> 
> This is on a DELL 2950.
> 
> Suspend/resume (to disk) has been running great on my IBM x60s, but
> when I tried the same kernel (2.6.18-rc4) on the DELL 2950, it
> suspended ok, but when resuming, the megaraid driver crashed.

And what exactly is your intention with this email? It can't be getting
the bug fixed, since there's exactly 0% information to help people doing
so :-)

IOW, provide the oops from the resume crash at least.

-- 
Jens Axboe


  parent reply	other threads:[~2006-08-29  8:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 17:04 megaraid_sas suspend ok, resume oops Jeff Chua
2006-08-28 21:55 ` Pavel Machek
2006-08-29  8:15 ` Jens Axboe [this message]
2006-08-29 12:22   ` Jeff Chua
2006-08-29 20:39     ` Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops) Pavel Machek
2006-08-31 17:05       ` Rafael J. Wysocki
2006-08-29 23:45     ` megaraid_sas suspend ok, resume oops Nigel Cunningham
2006-08-30  1:45       ` Jeff Chua
2006-08-30  2:30         ` Nigel Cunningham
2006-08-30  8:41           ` Jeff Chua
2006-08-30  8:54       ` Rafael J. Wysocki
2006-09-02 13:30         ` Dave Jones
2006-09-02 19:47           ` Rafael J. Wysocki
2006-09-02 20:10             ` Dave Jones

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=20060829081518.GD12257@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Sreenivas.Bagalkote@lsil.com \
    --cc=Sumant.Patro@lsil.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    /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