From: Hugang <hugang@soulinfo.com>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] Linux-2.6.1 suspend/resume
Date: Mon, 26 Jan 2004 12:16:31 +0800 [thread overview]
Message-ID: <20040126121632.70097914@localhost> (raw)
In-Reply-To: <20040126022540.315c4f8c@argon.inf.tu-dresden.de>
On Mon, 26 Jan 2004 02:25:40 +0100
"Udo A. Steinberg" <us15@os.inf.tu-dresden.de> wrote:
> [<c02fc028>] usb_hcd_pci_resume+0x38/0x90
> [<c023ac54>] pci_device_resume+0x24/0x30
> [<c028a3e7>] resume_device+0x27/0x30
> [<c028a424>] dpm_resume+0x34/0x60
> [<c028a469>] device_resume+0x19/0x30
> [<c01337e9>] drivers_resume+0x39/0x40
> [<c0133aba>] do_magic_resume_2+0x5a/0xe0
> [<c0133ad2>] do_magic_resume_2+0x72/0xe0
> [<c03576af>] do_magic+0x11f/0x130
> [<c0133cfb>] do_software_suspend+0x6b/0x90
> [<c02538e6>] acpi_system_write_sleep+0xb3/0xcd
> [<c0253833>] acpi_system_write_sleep+0x0/0xcd
> [<c0150398>] vfs_write+0xd8/0x140
> [<c01504b2>] sys_write+0x42/0x70
> [<c0109387>] syscall_call+0x7/0xb
>
> bad: scheduling while atomic!
> Call Trace:
> [<c011a7d3>] schedule+0x563/0x570
> [<c0356e7d>] pci_read+0x3d/0x50
> [<c0125ff3>] schedule_timeout+0x63/0xc0
> [<c0125f80>] process_timeout+0x0/0x10
> [<c02387b3>] pci_set_power_state+0xd3/0x160
> [<c02a3708>] e100_resume+0x28/0x70
> [<c023ac54>] pci_device_resume+0x24/0x30
I think if you can let usb, e100 as module, before suspend rmmod it,
resume will be ok.
pls try.
thanks.
--
Hu Gang / Steve
Linux Registered User 204016
GPG Public Key: http://soulinfo.com/~hugang/HuGang.asc
next prev parent reply other threads:[~2004-01-26 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 1:25 [OOPS] Linux-2.6.1 suspend/resume Udo A. Steinberg
2004-01-26 1:48 ` Nigel Cunningham
2004-01-26 4:16 ` Hugang [this message]
2004-01-26 8:35 ` Udo A. Steinberg
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=20040126121632.70097914@localhost \
--to=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=us15@os.inf.tu-dresden.de \
/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