public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Roger Luethi <rl@hellgate.ch>, Pavel Machek <pavel@ucw.cz>,
	Andrew Grover <andrew.grover@intel.com>,
	ACPI mailing list <acpi-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: S4bios support for 2.5.63
Date: Mon, 3 Mar 2003 12:31:53 +0100	[thread overview]
Message-ID: <20030303113153.GA18563@outpost.ds9a.nl> (raw)
In-Reply-To: <1046657290.8668.33.camel@laptop-linux.cunninghams>

On Mon, Mar 03, 2003 at 03:08:11PM +1300, Nigel Cunningham wrote:

> > The only thing that came up at the time was a suggestion to replace BUG_ON
> > with while (which I didn't try because I'd like to keep my data).
> 
> I'll see if I can find a solution.

A data point may be that at one point, swsusp did work just fine for me.
This was around 2.5.53, 2.5.54:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=20021227142032.GA6945%40outpost.ds9a.nl&rnum=1&prev=/groups%3Fq%3Dswsusp%2Bbert%2Bhubert%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3D20021227142032.GA6945%2540outpost.ds9a.nl%26rnum%3D1

I now use gcc 3.2.2 for compiling though. I've tried suspending a few times
with 2.5.63bk5 and I get the BUG every time, so it appears to be
deterministic and not racey.

Regards,

bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl                         Consulting

  reply	other threads:[~2003-03-03 11:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 21:13 S4bios support for 2.5.63 Pavel Machek
2003-02-27 14:13 ` [ACPI] " Ducrot Bruno
2003-03-04 13:23   ` Pavel Machek
2003-03-04 12:00     ` Ducrot Bruno
2003-03-02 13:31 ` bert hubert
2003-03-02 18:44   ` Nigel Cunningham
2003-03-02 20:21     ` bert hubert
2003-03-02 22:22       ` Alan Cox
2003-03-03  0:39       ` Roger Luethi
2003-03-03  2:08         ` [ACPI] " Nigel Cunningham
2003-03-03 11:31           ` bert hubert [this message]
2003-03-03 12:17             ` Roger Luethi
2003-03-03 12:23             ` Pavel Machek
2003-03-03 12:35               ` bert hubert
2003-03-03 12:41                 ` Pavel Machek
     [not found]                   ` <1046700474.3782.197.camel@localhost>
2003-03-03 14:30                     ` Roger Luethi
2003-03-03 22:06                       ` Nigel Cunningham
2003-03-03 23:39                         ` Roger Luethi
2003-03-04  0:36                           ` Nigel Cunningham
2003-03-04 10:43                             ` Roger Luethi
2003-03-04  9:12                         ` bert hubert
2003-03-03 15:11                   ` bert hubert
2003-03-03 16:40                     ` Alan Cox
2003-03-03 16:23                   ` P. Christeas
2003-03-03 16:28                   ` bert hubert
2003-03-03 14:25                 ` Alan Cox
2003-03-03 12:37               ` Roger Luethi
2003-03-03 14:09         ` Alan Cox
2003-03-03 14:37           ` [ACPI] " Ducrot Bruno

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=20030303113153.GA18563@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@clear.net.nz \
    --cc=pavel@ucw.cz \
    --cc=rl@hellgate.ch \
    /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