mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: clepple@ghz.cc, linux-kernel@vger.kernel.org
Subject: Re: [REPOST] "apm: suspend: Unable to enter requested state" after 2.5.31 (incl. 2.6.0testX)
Date: Thu, 31 Jul 2003 01:16:51 +1000	[thread overview]
Message-ID: <20030731011651.618aba1e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1059576198.8041.46.camel@dhcp22.swansea.linux.org.uk>

On 30 Jul 2003 15:43:18 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> On Mer, 2003-07-30 at 02:05, Stephen Rothwell wrote:
> > > It might be 0x00009300, it might be set already, or it might be some other
> > > effect thats breaking your laptop of course
> > 
> > The 0 above initialises the base and limit parts of the descriptor and
> > should be zero as it is filled in later (or should be).
> 
> I thought the descriptor bits came in the first long word and the 16bit
> base/limit in the second ?

Not according to my book ... parts of the base and limit are spread around
in the second long word.

The 2.4 version of this is static in arch/i386/kernel/head.S and looks
like this:

        .quad 0x0040920000000000        /* 0x40 APM set up for bad BIOS's */

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

      reply	other threads:[~2003-07-30 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 14:50 Charles Lepple
2003-07-29 15:07 ` Alan Cox
2003-07-29 16:05   ` Charles Lepple
2003-07-29 18:10     ` Alan Cox
2003-07-30  1:05       ` Stephen Rothwell
2003-07-30  1:38         ` Charles Lepple
2003-07-30  2:21           ` Stephen Rothwell
2003-07-30 16:48             ` [REPOST] "apm: suspend: Unable to enter requested state" after2.5.31 " Charles Lepple
2003-07-30 14:43         ` [REPOST] "apm: suspend: Unable to enter requested state" after 2.5.31 " Alan Cox
2003-07-30 15:16           ` Stephen Rothwell [this message]

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=20030731011651.618aba1e.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=clepple@ghz.cc \
    --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

all inboxes | Powered by JetHome®