From: bert hubert <ahu@ds9a.nl>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Roger Luethi <rl@hellgate.ch>,
Troels Haugboelle <troels_h@astro.ku.dk>,
Pavel Machek <pavel@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: S4bios support for 2.5.63
Date: Tue, 4 Mar 2003 10:12:54 +0100 [thread overview]
Message-ID: <20030304091254.GA16556@outpost.ds9a.nl> (raw)
In-Reply-To: <1046729210.1850.8.camel@laptop-linux.cunninghams>
On Tue, Mar 04, 2003 at 11:06:50AM +1300, Nigel Cunningham wrote:
> You were hitting the BUG_ON before swsusp was even trying to write the
> image?!! That is interesting! Since count_and_copy is first called post
> driver suspend in the current version, perhaps they are somehow related.
Sure, I get this too:
It now says (copied by hand):
freeing memory: .....................|
(this 'freeing' takes ages, around 30 seconds, while in progress, the disk
light blinks every once in a while, perhaps each time while a dot is being
printed)
syncing disks
suspending devices
suspending device c0418bcc
suspending devices
suspending device c0418bcc
suspending: hda ------------------[ cut here
trace back:
device_susp()
drivers_susp()
do_software_susp()
This happens, I think, from here in kernel/suspend.c:
/* Called from process context */
static int drivers_suspend(void)
{
device_suspend(4, SUSPEND_NOTIFY);
device_suspend(4, SUSPEND_SAVE_STATE);
device_suspend(4, SUSPEND_DISABLE);
...
I think the problem occurs on the second call, SUSPEND_SAVE_STATE:
static int idedisk_suspend(struct device *dev, u32 state, u32 level)
{
ide_drive_t *drive = dev->driver_data;
printk("Suspending device %p\n", dev->driver_data);
/* I hope that every freeze operation from the upper levels have
* already been done...
*/
if (level != SUSPEND_SAVE_STATE)
return 0;
/* set the drive to standby */
printk(KERN_INFO "suspending: %s ", drive->name);
do_idedisk_standby(drive);
drive->blocked = 1;
BUG_ON (HWGROUP(drive)->handler); // <----- this BUGs
return 0;
}
Regards,
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl Consulting
next prev parent reply other threads:[~2003-03-04 9:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 21:13 S4bios support for 2.5.63 Pavel Machek
2003-02-27 14:13 ` [ACPI] " Ducrot Bruno
2003-03-04 13:23 ` Pavel Machek
2003-03-04 12:00 ` Ducrot Bruno
2003-03-02 13:31 ` bert hubert
2003-03-02 18:44 ` Nigel Cunningham
2003-03-02 20:21 ` bert hubert
2003-03-02 22:22 ` Alan Cox
2003-03-03 0:39 ` Roger Luethi
2003-03-03 2:08 ` [ACPI] " Nigel Cunningham
2003-03-03 11:31 ` bert hubert
2003-03-03 12:17 ` Roger Luethi
2003-03-03 12:23 ` Pavel Machek
2003-03-03 12:35 ` bert hubert
2003-03-03 12:41 ` Pavel Machek
[not found] ` <1046700474.3782.197.camel@localhost>
2003-03-03 14:30 ` Roger Luethi
2003-03-03 22:06 ` Nigel Cunningham
2003-03-03 23:39 ` Roger Luethi
2003-03-04 0:36 ` Nigel Cunningham
2003-03-04 10:43 ` Roger Luethi
2003-03-04 9:12 ` bert hubert [this message]
2003-03-03 15:11 ` bert hubert
2003-03-03 16:40 ` Alan Cox
2003-03-03 16:23 ` P. Christeas
2003-03-03 16:28 ` bert hubert
2003-03-03 14:25 ` Alan Cox
2003-03-03 12:37 ` Roger Luethi
2003-03-03 14:09 ` Alan Cox
2003-03-03 14:37 ` [ACPI] " Ducrot Bruno
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=20030304091254.GA16556@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--cc=pavel@suse.cz \
--cc=rl@hellgate.ch \
--cc=troels_h@astro.ku.dk \
/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;
as well as URLs for NNTP newsgroup(s).