mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Frédéric Riss" <frederic.riss@gmail.com>,
	"Linux Kernel list" <linux-kernel@vger.kernel.org>,
	"Linus Torvalds" <torvalds@osdl.org>,
	len.brown@intel.com
Subject: Re: 2.6.18 suspend regression on Intel Macs
Date: Tue, 10 Oct 2006 12:41:28 +0200	[thread overview]
Message-ID: <1160476889.3000.282.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061010103910.GD31598@elf.ucw.cz>

On Tue, 2006-10-10 at 12:39 +0200, Pavel Machek wrote:
> Hi!
> 
> > Well, I'm not sure it qualifies as a regression, because AFAIK no
> > official kernels can s2ram/resume Intel Macs correctly out of the box.
> ...
> 
> > There has already been some discussion about the SCI_EN ACPI control bit
> > not being set when the Mactel boxes come out of suspend to ram. 
> > http://marc.theaimsgroup.com/?l=linux-acpi&m=114957637501557&w=2
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=115005083610700&w=2
> > http://bugme.osdl.org/show_bug.cgi?id=6670
> > 
> > The symptom is:
> >     irq 9: nobody cared (try booting with the "irqpoll" option)
> >     Disabling IRQ #9
> > when the system comes out of sleep, making ACPI non-functional.
> > 
> > Two days after having released 2.6.17, Linus commited a fix for this
> > issue in his tree (commit 5603509137940f4cbc577281cee62110d4097b1b):
> 
> If fix was in 2.6.18-gitX, yes, that probably counts as a regression

"fix" for some value of the word.
The problem is that this is very much against the spec, and also quite
likely breaks a bunch of machines...

If we do this we probably should at least key this of some DMI
identification for the mac mini..



  reply	other threads:[~2006-10-10 10:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 18:19 Frédéric Riss
2006-10-10 10:39 ` Pavel Machek
2006-10-10 10:41   ` Arjan van de Ven [this message]
2006-10-10 10:49     ` Pavel Machek
2006-10-10 15:33     ` Linus Torvalds
2006-10-10 19:08       ` Frédéric Riss
2006-10-10 19:38         ` Arjan van de Ven
2006-10-10 19:46           ` Frédéric Riss
2006-10-10 19:50             ` Pavel Machek
2006-10-10 21:49               ` Linus Torvalds
2006-10-10 22:09                 ` Frédéric Riss
2006-10-10 23:53                   ` Linus Torvalds
2006-10-11  6:09                     ` Frédéric Riss
2006-10-11 13:16                     ` suspend debugging " Pavel Machek
2006-10-11  6:35                 ` Len Brown
2006-10-11 14:35                   ` Linus Torvalds
2006-10-10 21:28     ` Matthew Garrett
2006-10-11  6:37       ` Len Brown

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=1160476889.3000.282.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=frederic.riss@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@osdl.org \
    /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

all inboxes | Powered by JetHome®