From: Andrew Morton <akpm@osdl.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [patch] properly stop devices before poweroff
Date: Sat, 30 Apr 2005 09:47:48 +0000 [thread overview]
Message-ID: <20050430024748.19d44a8d.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0504290734220.30771@montezuma.fsmlabs.com>
Zwane Mwaikambo <zwane@arm.linux.org.uk> wrote:
>
> On Fri, 29 Apr 2005, Andrew Morton wrote:
>
> > Pavel Machek <pavel@ucw.cz> wrote:
> > >
> > >
> > > Without this patch, Linux provokes emergency disk shutdowns and
> > > similar nastiness. It was in SuSE kernels for some time, IIRC.
> > >
> >
> > With this patch when running `halt -p' my ia64 Tiger (using
> > tiger_defconfig) gets a stream of badnesses in iosapic_unregister_intr()
> > and then hangs up.
> >
> > Unfortunately it all seems to happen after the serial port has been
> > disabled because nothing comes out. I set the console to a squitty font
> > and took a piccy. See
> > http://www.zip.com.au/~akpm/linux/patches/stuff/dsc02505.jpg
> >
> > I guess it's an ia64 problem. I'll leave the patch in -mm for now.
>
> Could you cat /proc/interrupts during runtime?
CPU0 CPU1 CPU2 CPU3
28: 0 0 0 0 LSAPIC cpe_poll
29: 0 0 0 0 LSAPIC cmc_poll
30: 0 0 0 0 IO-SAPIC-level cpe_hndlr
31: 0 0 0 0 LSAPIC cmc_hndlr
34: 19 0 0 0 IO-SAPIC-edge ide0
39: 0 0 0 0 IO-SAPIC-level acpi
48: 382 0 0 0 IO-SAPIC-level eth0
49: 0 2835 0 0 IO-SAPIC-level ioc0
50: 0 0 29 0 IO-SAPIC-level ioc1
51: 0 0 0 0 IO-SAPIC-level uhci_hcd:usb1
52: 51 0 0 0 IO-SAPIC-level uhci_hcd:usb2
232: 0 0 0 0 LSAPIC mca_rdzv
238: 0 0 0 0 LSAPIC perfmon
239: 122785 128748 129310 130523 LSAPIC timer
240: 0 0 0 0 LSAPIC mca_wkup
254: 29 77 101 102 LSAPIC IPI
ERR: 0
> It looks like the device
> being suspended never went through pci_device_enable() (e.g. ethernet
> interface wasn't up). It's harmless right now.
Everything's up. Perhaps we're trying to disable devices more than once?
next prev parent reply other threads:[~2005-04-30 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050421111346.GA21421@elf.ucw.cz>
2005-04-29 13:18 ` [patch] properly stop devices before poweroff Andrew Morton
2005-04-29 13:36 ` Zwane Mwaikambo
2005-04-30 9:47 ` Andrew Morton [this message]
2005-04-30 13:40 ` Pavel Machek
2005-05-01 19:09 ` Kenji Kaneshige
2005-05-01 19:57 ` Pavel Machek
2005-05-01 22:16 ` Adam Belay
2005-05-16 7:56 ` Andrew Morton
2005-05-19 12:43 ` Kenji Kaneshige
2005-07-27 21:14 ` Luck, Tony
2005-07-26 19:02 Luck, Tony
2005-07-26 19:10 ` Andrew Morton
2005-07-27 0:14 ` tony.luck
2005-07-27 0:23 ` Andrew Morton
2005-07-27 7:40 ` Pavel Machek
2005-07-28 1:37 ` Kenji Kaneshige
2005-07-28 1:41 ` Andrew Morton
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=20050430024748.19d44a8d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=zwane@arm.linux.org.uk \
/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