All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Jenkins <aj504@student.cs.york.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 suspend-to-disk bug (during resume)
Date: Thu, 20 Jan 2005 10:19:24 +0100	[thread overview]
Message-ID: <200501201019.24378.rjw@sisk.pl> (raw)
In-Reply-To: <1106210985l.8224l.0l@linux>

On Thursday, 20 of January 2005 09:49, Alan Jenkins wrote:
> On 20/01/05 08:48:02, Alan Jenkins wrote:
> I have noticed a similar message, and so has someone else on the list:
> 
> http://groups-beta.google.com/group/fa.linux.kernel/browse_thread/thread/1bfcbbca2d508bb3/cb69d674510d215a?q=%22bad:+scheduling+while+atomic!%22+suspend&_done=%2Fgroup%2Ffa.linux.kernel%2Fsearch%3Fgroup%3Dfa.linux.kernel%26q%3D%22bad:+scheduling+while+atomic!%22+suspend%26qt_g%3D1%26searchnow%3DSearch+this+group%26&_doneTitle=Back+to+Search&&d#cb69d674510d215a
> 
> I have an asrock motherboard with an sis chipset.
> SiS seems to be the common factor.  I think its something general about
> the chipset.  My messages seem to involve the network card, the sound
> card and the i8042 (ps/2 port) controller:

Have you tried to boot with "pci=routeirq" or/and "noapic"?

Greets,
RJW


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-01-20  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1106210882.7975.9.camel@linux.site>
2005-01-20  8:49 ` 2.6.9 suspend-to-disk bug (during resume) Alan Jenkins
2005-01-20  9:19   ` Rafael J. Wysocki [this message]
2005-01-21  9:45     ` Alan Jenkins
2005-01-20 14:58   ` Pavel Machek
2005-01-21  9:08     ` Alan Jenkins
2005-01-21 10:39       ` Pavel Machek
2005-01-21 13:18         ` Alan Jenkins
2004-10-24 13:13 andreoli

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=200501201019.24378.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=aj504@student.cs.york.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.