linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Luethi <rl@hellgate.ch>
To: Troels Haugboelle <troels_h@astro.ku.dk>
Cc: Pavel Machek <pavel@suse.cz>, bert hubert <ahu@ds9a.nl>,
	Nigel Cunningham <ncunningham@clear.net.nz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: S4bios support for 2.5.63
Date: Mon, 3 Mar 2003 15:30:06 +0100	[thread overview]
Message-ID: <20030303143006.GA1289@k3.hellgate.ch> (raw)
In-Reply-To: <1046700474.3782.197.camel@localhost>

[removed ACPI mailing list from cc:]

On Mon, 03 Mar 2003 15:07:54 +0100, Troels Haugboelle wrote:
> just to add my experience. Maybe it helps. I haven't been able to get
> swsusp working on any 2.4.x kernel until i did an
>     hdparm -u1 /dev/hda
> now the strange thing: I tried to turn on the frame buffer device and
> it started chrashing again until i did
>     hdparm -u0 /dev/hda
> Before I tried using suspend in 2.5.x with varying success. Now
> everything runs like a charm. Without unmask irq's first the kernel
> dumped
> with either a kernel BUG statement or a fault in ide-disk.c

Not sure I follow all of your story but I can confirm that hdparm -u1
successfully gets me to the kernel panic due to highmem support still
lacking -- i.e. way beyond the BUG_ON() I've been hitting. So it looks
like you found a good work-around.

FWIW I'm using reiserfs, too. Two harddisks, ALi chipset.

Roger

  parent reply	other threads:[~2003-03-03 14:20 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
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 [this message]
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=20030303143006.GA1289@k3.hellgate.ch \
    --to=rl@hellgate.ch \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@clear.net.nz \
    --cc=pavel@suse.cz \
    --cc=troels_h@astro.ku.dk \
    /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).