public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Schrangl <schrangl-hi6Y0CQ0nG0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Bad: scheduling while atomic!
Date: Fri, 2 Apr 2004 11:49:28 +0200	[thread overview]
Message-ID: <200404021149.29165.schrangl@gmx.net> (raw)
In-Reply-To: <20040401150739.GC8091-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>

Am Donnerstag, 1. April 2004 17:07 schrieb Stefan Seyfried:
> On Thu, Apr 01, 2004 at 08:46:01AM +0200, Lukas Schrangl wrote:
> > 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
>
> i need to unload bcm4400 before suspend (swsusp, ACPI S4) and reinsert
> after resume, otherwise resume fails. Maybe the same is true for S3.

The problem was enabling both preemptible kernel and MCE. Using only one of 
them everything works, even if b44 is inserted and Local APIC enabled.
Only usb makes problems:
On wakeup I get something like
"Badness in usb/hcd/....c"
and a call trace. Will try to resolve that problem (maybe unloading usbmodules 
works, haven't had time to try yet).
After resume, I am not able to use usb anymore (even unloading/realoading 
doesn't work).
And ACPI- poweroff does not work anymore. When shutting down I can read:
"The system will be haltet immediately.
acpi_power_off called"
or something the like, but no nothing happens; i poweroff manually. On 
"normal" shutdowns (when not having resumed from S4) I don't get the msg 
"acpi_power_off called" and it powers off.
Should I write a bug report because of the preempt/MCE problem and/or the APIC 
error which seems not to have any influence?

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

  parent reply	other threads:[~2004-04-02  9:49 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
     [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 [this message]
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=200404021149.29165.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