public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: 2.6.11-rc3-mm1: softlockup and suspend/resume
Date: Sun, 6 Feb 2005 20:15:56 +0100	[thread overview]
Message-ID: <200502062015.56458.rjw@sisk.pl> (raw)
In-Reply-To: <20050205190700.GA2323@elte.hu>

Hi,

On Saturday, 5 of February 2005 20:07, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > > I've attached a patch for touch_softlockup_watchdog() below - but i think
> > > what we really need is another mechanism. I'm wondering what the primary
> > > reason for the lockup-detection is - did swsuspend stop the the softlockup
> > > threads? 
> > 
> > If my understanding is correct, the time between suspend (ie the
> > creation of the image) and resume (ie the resotration of the image) is
> > considered as spent in the kernel, so it triggers softlockup as soon
> > as its threads are woken up (is that correct, Pavel?).
> 
> ah, ok. Could you try my patch and add touch_softlockup_watchdog() to
> the resume code (before interrupts are re-enabled)?

I did:

--- /home/rafael/tmp/kernel/testing/linux-2.6.11-rc3-mm1/kernel/power/swsusp.c	2005-02-05 20:57:03.000000000 +0100
+++ linux-2.6.11-rc3-mm1/kernel/power/swsusp.c	2005-02-06 19:07:39.000000000 +0100
@@ -871,6 +869,7 @@
 	restore_processor_state();
 	restore_highmem();
 	device_power_up();
+	touch_softlockup_watchdog();
 	local_irq_enable();
 	return error;
 }

and it still complains, but the call trace is now different:

BUG: soft lockup detected on CPU#0!
Feb  6 19:50:02 albercik kernel:
Feb  6 19:50:03 albercik kernel: Modules linked in: snd_seq snd_seq_device usbserial parport_pc lp parport thermal processor fan button battery ac snd_pc
m_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd soundcore snd_page_alloc ipt_TOS ipt_LOG ipt_limit ipt_pkttype af_packet ipt_state
ipt_REJECT iptable_mangle iptable_filter ip6table_mangle ip_nat_ftp iptable_nat ip_conntrack_ftp ip_conntrack ip_tables ip6table_filter ip6_tables ipv6 p
cmcia binfmt_misc joydev sg st sd_mod sr_mod scsi_mod ide_cd cdrom ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core sk98lin usbhid ehci_hcd i2c_
nforce2 i2c_core ohci_hcd dm_mod evdev
Feb  6 19:50:05 albercik kernel: Pid: 8679, comm: do_acpi_sleep Not tainted 2.6.11-rc3-mm1
Feb  6 19:50:07 albercik kernel: RIP: 0010:[<ffffffff802b6dd8>] <ffffffff802b6dd8>{acpi_ut_find_allocation+50}
Feb  6 19:50:11 albercik kernel: RSP: 0000:ffff81000d8af818  EFLAGS: 00000202
Feb  6 19:50:14 albercik kernel: RAX: ffff81001c91fa80 RBX: ffff8100123caeb0 RCX: ffff8100123caeb0
Feb  6 19:50:16 albercik kernel: RDX: ffff81001ed73878 RSI: ffff8100123caeb0 RDI: 0000000000000000
Feb  6 19:50:17 albercik kernel: RBP: ffffffff803ea5b8 R08: 00000000000021e7 R09: ffffffff803f478a
Feb  6 19:50:19 albercik kernel: R10: 000000000000ffff R11: 000000000000ffff R12: ffffffff803ea6b9
Feb  6 19:50:21 albercik kernel: R13: ffffffff00000400 R14: 0000000000000246 R15: 00000000000021e7
Feb  6 19:50:22 albercik kernel: FS:  00002aaaab28b800(0000) GS:ffffffff80567800(0000) knlGS:0000000000000000
Feb  6 19:50:24 albercik kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Feb  6 19:50:25 albercik kernel: CR2: 00002aaaaac4e642 CR3: 000000000d876000 CR4: 00000000000006e0
Feb  6 19:50:27 albercik kernel:
Feb  6 19:50:28 albercik kernel: Call Trace:<ffffffff802b6db3>{acpi_ut_find_allocation+13} <ffffffff802b6e8f>{acpi_ut_track_allocation+169}
Feb  6 19:50:28 albercik kernel:        <ffffffff802b71ed>{acpi_ut_callocate_and_track+95}
Feb  6 19:50:29 albercik kernel:        <ffffffff802b7259>{acpi_ut_acquire_from_cache+62} <ffffffff802b8a22>{acpi_ut_create_generic_state+17}
Feb  6 19:50:32 albercik kernel:        <ffffffff8029901f>{acpi_ds_result_stack_push+42} <ffffffff80299100>{acpi_ds_create_walk_state+152}
Feb  6 19:50:37 albercik kernel:        <ffffffff802b8e2d>{acpi_ut_create_thread_state+106}
Feb  6 19:50:39 albercik kernel:        <ffffffff802afb08>{acpi_ps_delete_parse_tree+113} <ffffffff802aea13>{acpi_ps_complete_this_op+476}
Feb  6 19:50:39 albercik kernel:        <ffffffff802af194>{acpi_ps_parse_loop+1897} <ffffffff802988f8>{acpi_ds_delete_walk_state+297}
Feb  6 19:50:41 albercik kernel:        <ffffffff802af5da>{acpi_ps_parse_aml+237} <ffffffff802b0266>{acpi_psx_execute+546}
Feb  6 19:50:42 albercik kernel:        <ffffffff802a5d77>{acpi_ex_enter_interpreter+114} <ffffffff802aae99>{acpi_ns_execute_control_method+260}
Feb  6 19:50:44 albercik kernel:        <ffffffff802aafb3>{acpi_ns_evaluate_by_handle+249}
Feb  6 19:50:45 albercik kernel:        <ffffffff802ab2de>{acpi_ns_evaluate_relative+400} <ffffffff802b3b2a>{acpi_rs_set_srs_method_data+250}
Feb  6 19:50:45 albercik kernel:        <ffffffff80176f90>{check_poison_obj+48} <ffffffff802b2687>{acpi_set_current_resources+122}

Greets,
Rafael


-- 
- 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-02-06 19:22 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 18:33 2.6.11-rc3-mm1 Andrew Morton
2005-02-04 20:11 ` [patch] 2.6.11-rc3-mm1: fix swsusp with gcc 3.4 Adrian Bunk
2005-02-04 21:51   ` Rafael J. Wysocki
2005-02-05  9:32     ` Pavel Machek
2005-02-04 20:44 ` 2.6.11-rc3-mm1 (compile stats) John Cherry
2005-02-04 21:13   ` Andrew Morton
     [not found]     ` <1107553914.14618.12.camel@cherrypit.pdx.osdl.net>
2005-02-04 23:31       ` John Cherry
2005-02-04 21:08 ` Add changelog entries for bk-trees? Sam Ravnborg
2005-02-04 22:17 ` 2.6.11-rc3-mm1 Sean Neakums
2005-02-04 23:57   ` 2.6.11-rc3-mm1 Benjamin Herrenschmidt
2005-02-05  0:05     ` 2.6.11-rc3-mm1 Sean Neakums
2005-02-05  0:16       ` 2.6.11-rc3-mm1 Benjamin Herrenschmidt
2005-02-05  0:54         ` 2.6.11-rc3-mm1 Bartlomiej Zolnierkiewicz
2005-02-05 10:48           ` 2.6.11-rc3-mm1 Sean Neakums
2005-02-05 22:35             ` 2.6.11-rc3-mm1 Benjamin Herrenschmidt
2005-02-04 23:50 ` 2.6.11-rc3-mm1: device_resume() hangs on Athlon64 Rafael J. Wysocki
2005-02-05  6:35 ` bk-usb is now safe (was 2.6.11-rc3-mm1) Greg KH
2005-02-05  8:47 ` 2.6.11-rc3-mm1 : can't insmod dm-mod Laurent Riffard
2005-02-05 11:26   ` Andrew Morton
2005-02-05 13:25     ` Laurent Riffard
2005-02-05 16:29     ` Christoph Hellwig
2005-02-05 20:03       ` Al Viro
2005-02-05 12:23 ` 2.6.11-rc3-mm1 William Lee Irwin III
2005-02-05 12:44 ` 2.6.11-rc3-mm1: kobject_register fails for processor on Athlon64 Rafael J. Wysocki
2005-02-05 13:11 ` 2.6.11-rc3-mm1: softlockup and suspend/resume Rafael J. Wysocki
2005-02-05 14:35   ` Ingo Molnar
2005-02-05 14:48     ` Rafael J. Wysocki
2005-02-05 19:07       ` Ingo Molnar
2005-02-06 19:15         ` Rafael J. Wysocki [this message]
2005-02-07  8:57           ` Ingo Molnar
2005-02-07 12:53             ` Rafael J. Wysocki
2005-02-08 11:04               ` Ingo Molnar
2005-02-09 16:35                 ` Rafael J. Wysocki
2005-02-10  0:22                   ` 2.6.11-rc3-mm1: softlockup and suspend/resume [update] Rafael J. Wysocki
2005-02-05 19:48       ` 2.6.11-rc3-mm1: softlockup and suspend/resume Pavel Machek
2005-02-05 19:47     ` Pavel Machek
2005-02-05 18:10 ` 2.6.11-rc3-mm1 Rogério Brito
2005-02-05 18:43   ` 2.6.11-rc3-mm1 Jurriaan
2005-02-05 22:28     ` 2.6.11-rc3-mm1 Rogério Brito
2005-02-05 22:45 ` irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1) Rogério Brito
2005-02-05 22:48   ` Rogério Brito
2005-02-06  2:36   ` William Park
2005-02-06  9:07     ` Rogério Brito
2005-02-12 22:21   ` William Park
2005-02-12 22:47     ` Rogério Brito
2005-02-12 23:21       ` William Park
2005-02-12 23:50         ` Rogério Brito
2005-02-13  1:41           ` William Park
2005-02-13 16:37             ` Rogério Brito
2005-02-13 16:56             ` Rogério Brito
2005-02-13 18:49             ` [Partially solved] " Rogério Brito
2005-02-06 10:07 ` 2.6.11-rc3-mm1 Peter Osterlund
2005-02-06 10:33   ` 2.6.11-rc3-mm1 Benjamin Herrenschmidt
2005-02-06 12:14     ` 2.6.11-rc3-mm1 Peter Osterlund
2005-02-06 21:22       ` 2.6.11-rc3-mm1 Peter Osterlund
2005-02-07 17:22         ` 2.6.11-rc3-mm1 Robert Love
2005-02-08 23:08           ` 2.6.11-rc3-mm1 Peter Osterlund
2005-02-06 12:30     ` 2.6.11-rc3-mm1 Joseph Fannin
2005-02-09  3:58 ` 2.6.11-rc3-mm1 Marcos D. Marado Torres
2005-02-09  4:54   ` 2.6.11-rc3-mm1 Andrew Morton
2005-02-09  8:55     ` 2.6.11-rc3-mm1 Barry K. Nathan
2005-02-09  5:00   ` 2.6.11-rc3-mm1 Zwane Mwaikambo
2005-02-10  4:12   ` 2.6.11-rc3-mm1 Andrew Morton
2005-02-10  4:32     ` 2.6.11-rc3-mm1 Barry K. Nathan
2005-02-09  5:59 ` 2.6.11-rc3-mm1: two oops on startup Clemens Schwaighofer
2005-02-09  6:09   ` Andrew Morton
2005-02-09  6:14     ` Clemens Schwaighofer

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=200502062015.56458.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    /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