public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	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: Wed, 30 Aug 2006 09:45:31 +1000	[thread overview]
Message-ID: <1156895131.3232.25.camel@nigel.suspend2.net> (raw)
In-Reply-To: <b6a2187b0608290522vea22930y54ac39bfce3127f2@mail.gmail.com>

Hi.

On Tue, 2006-08-29 at 20:22 +0800, Jeff Chua wrote:
> On 8/29/06, Jens Axboe <axboe@kernel.dk> wrote:
> > 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.
> 
> The intend is to see if there's already someone working on, and if so,
> then it'll not be good to post oops that has already been taken care
> of. I'm trying not to send unnecessary info.
> 
> I'll try to get oops in the next few days when I get a chance.
> Currently traveling.
> 
> 
> Another point ... on IBM x60s notebook, setting ...
> 
>        High Memory Support (64GB)
>                CONFIG_HIGHMEM64G=y
>                CONFIG_RESOURCES_64BIT=y
>                CONFIG_X86_PAE=y
> 
> will cause resume to "REBOOT" sometimes (may be 6 out of 10).
> 
> I was trying to compile a kernel that would run both on the DELL with
> 16GB RAM, and on my IBM notebook with 2GB RAM.
> 
> But without 64 bit support, my notebook will suspend/resume many times
> without failing (with the 5 ahci patches from Pavel Machek)....

Neither swsusp (as far as I know) or suspend2 support CONFIG_HIGHMEM64G
at the moment, I'm afraid.

It's not impossible, we just haven't seen it as a priority worth putting
time into. Do you really have more than 4GB of RAM and want to suspend
to disk?

Regards,

Nigel


  parent reply	other threads:[~2006-08-29 23:45 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
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     ` Nigel Cunningham [this message]
2006-08-30  1:45       ` megaraid_sas suspend ok, resume oops 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=1156895131.3232.25.camel@nigel.suspend2.net \
    --to=ncunningham@linuxmail.org \
    --cc=Sreenivas.Bagalkote@lsil.com \
    --cc=Sumant.Patro@lsil.com \
    --cc=axboe@kernel.dk \
    --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