From: Tony Lindgren <tony@atomide.com>
To: Charles Lepple <clepple@ghz.cc>
Cc: Pasi Savolainen <pasi.savolainen@hut.fi>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] amd76x_pm on 2.6.0-test9 cleanup
Date: Tue, 4 Nov 2003 13:17:57 -0800 [thread overview]
Message-ID: <20031104211757.GG1042@atomide.com> (raw)
In-Reply-To: <FF494619-0F09-11D8-A943-003065DC6B50@ghz.cc>
* Charles Lepple <clepple@ghz.cc> [031104 13:05]:
> On Tuesday, November 4, 2003, at 03:21 PM, Pasi Savolainen wrote:
>
> >* Tony Lindgren <tony@atomide.com> [031104 21:24]:
> >>I have problem where my S2460 goes into sleep for a while if compiled
> >>in,
> >>but this does not happen when loaded as module.
> >
> >Could you have some AMD_76X -define left over? I skimmed through MP &
> >MPX AMD documents, but found nothing incriminating.
> >Could it be ACPI doing it's things with S -states? (it does check for
> >SMP, but does report S -states as supported). And if ACPI isn't
> >enabled, could you toggle it on, or vice-versa.
>
> I wonder if the initialization code puts the chipset to sleep as it is
> setting up the stopgrant control bits?
>
> Here's a wild hypothesis: module loads, twiddles the registers, and the
> chipset enters sleep mode. In certain cases, enough interrupts are
> unmasked that the next interrupt wakes the chipset up, and things
> continue on their merry way. In other cases, it takes an ACPI interrupt
> (which, in my case, has not been initialized, since my BIOS evidently
> doesn't officially support ACPI C states) to wake things up (e.g. from
> a front-panel button).
Yeah, that makes sense.
> FWIW, I just found this in the dmesg output:
>
> irq 9: nobody cared!
> Call Trace:
> [<c010b7ba>] __report_bad_irq+0x2a/0x90
> [<c010b8ac>] note_interrupt+0x6c/0xa0
> [<c010bbdb>] do_IRQ+0x15b/0x190
> [<c0109d88>] common_interrupt+0x18/0x20
> [<e10ac26d>] amd76x_smp_idle+0x0/0xba [amd76x_pm]
> [<e10ac302>] amd76x_smp_idle+0x95/0xba [amd76x_pm]
> [<c0106f63>] cpu_idle+0x33/0x40
> [<c0120f04>] printk+0x164/0x1d0
>
> handlers:
> [<c01ebeb3>] (acpi_irq+0x0/0x16)
> Disabling IRQ #9
>
> Interestingly enough, I guess the 'button' module has claimed IRQ 9,
> since I have this in /proc/interrupts:
>
> 9: 5013 94989 IO-APIC-edge acpi
>
> Well, I'm officially confused :-)
Is your ACPI button a module too? Maybe load ACPI button first, then
amd76x_pm?
Tony
next prev parent reply other threads:[~2003-11-04 21:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 0:22 [PATCH] amd76x_pm on 2.6.0-test9 cleanup Tony Lindgren
2003-11-04 18:41 ` john stultz
2003-11-04 19:15 ` Tony Lindgren
2003-11-04 19:44 ` Charles Lepple
2003-11-04 20:05 ` Tony Lindgren
2003-11-04 20:52 ` Charles Lepple
2003-11-04 22:38 ` Charles Lepple
2003-11-04 23:11 ` Tony Lindgren
2003-11-04 23:46 ` Pasi Savolainen
2003-11-04 20:21 ` Pasi Savolainen
2003-11-04 20:55 ` Tony Lindgren
2003-11-04 20:57 ` john stultz
2003-11-04 21:14 ` Tony Lindgren
2003-11-14 11:56 ` Pasi Savolainen
2003-11-04 21:01 ` Charles Lepple
2003-11-04 21:17 ` Tony Lindgren [this message]
2003-11-05 19:42 ` Felix Maibaum
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=20031104211757.GG1042@atomide.com \
--to=tony@atomide.com \
--cc=clepple@ghz.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=pasi.savolainen@hut.fi \
/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).