From: Lukas Schrangl <schrangl-hi6Y0CQ0nG0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Bad: scheduling while atomic!
Date: Thu, 1 Apr 2004 08:46:01 +0200 [thread overview]
Message-ID: <200404010846.02216.schrangl@gmx.net> (raw)
In-Reply-To: <20040331135925.GF28355-+XVqjN4+fIJfbCVcMT5z6Ydd74u8MsAO@public.gmane.org>
Am Mittwoch, 31. März 2004 15:59 schrieb Tomasz Ciolek:
> I get the same error with suspend to disk on a Fujitsu P2120. Ali 1535
> chipset is the common bit...
>
> Whats the network card you use?
>
Broadcom BCM 4401
> Tomasz Ciolek
>
> On Wed, Mar 31, 2004 at 11:07:02AM +0200, Lukas Schrangl wrote:
> > Am Mittwoch, 31. M?rz 2004 10:54 schrieb Lukas Schrangl:
> > > Hi!
> > >
> > > I've been trying to get S4 working for several weeks now using kernel
> > > 2.6.4 and it still does not work.
> > > Going to sleep with "echo -n 4 > /proc/acpi/sleep" works - but i get
> > > some APIC error (don't know exactly - can't read that fast).
> > > When powering on again it first start normal, but then there is an
> > > endless loop displaying "Bad: Scheduling while atomic!" and a call
> > > trace again and again very fast. I can only hard- poweroff my computer.
> > > Disabling local APIC does not help.
> > >
> > > S3 does not wake up either (fan and hd spin up and then silence). Once,
> > > with minimal kernel configuration I managed to get a picture again on
> > > the screen, showing the same "Bad: Scheduling while atomic!" thing.
> > >
> > > Maybe someone can help me getting S4 working!
> > > Lukas
> >
> > I forgot:
> > ALi M1533 Chipset
> > ATI IGP 320M Northbridge
> > Ahlon XP 2500+ Northbridge
> > SuSE 9.0
> > Kernel 2.6.4
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
> > _______________________________________________
> > Acpi-devel mailing list
> > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > https://lists.sourceforge.net/lists/listinfo/acpi-devel
Lukas
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
next prev parent reply other threads:[~2004-04-01 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 8:54 Bad: scheduling while atomic! Lukas Schrangl
[not found] ` <200403311054.55536.schrangl-hi6Y0CQ0nG0@public.gmane.org>
2004-03-31 9:07 ` Lukas Schrangl
[not found] ` <200403311107.02570.schrangl-hi6Y0CQ0nG0@public.gmane.org>
2004-03-31 13:59 ` Tomasz Ciolek
[not found] ` <20040331135925.GF28355-+XVqjN4+fIJfbCVcMT5z6Ydd74u8MsAO@public.gmane.org>
2004-04-01 6:46 ` Lukas Schrangl [this message]
[not found] ` <200404010846.02216.schrangl-hi6Y0CQ0nG0@public.gmane.org>
2004-04-01 15:07 ` Stefan Seyfried
[not found] ` <20040401150739.GC8091-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2004-04-02 9:49 ` Lukas Schrangl
2004-04-01 8:17 ` Pavel Machek
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=200404010846.02216.schrangl@gmx.net \
--to=schrangl-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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