public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Homann <fexpop@onlinehome.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Andi Kleen <ak@suse.de>
Subject: Re: Regressions w.r.t. suspend behaviour in recent kernel versions
Date: Thu, 06 Sep 2007 00:51:50 +0200	[thread overview]
Message-ID: <46DF3306.7030608@onlinehome.de> (raw)
In-Reply-To: <20070905093605.ac755ce6.akpm@linux-foundation.org>

Andrew Morton wrote:
>> On Fri, 24 Aug 2007 14:42:55 +0200 Felix Homann <fexpop@onlinehome.de> wrote:
> 
> Nearly two weeks, zero replies.

Thanks for caring :-)

> 
>> Aug  9 00:22:13 jawaka kernel: EXT3-fs: mounted filesystem with ordered
>> data mode.
>> Aug  9 00:22:13 jawaka kernel: WARNING: at kernel/irq/resend.c:70
>> check_irq_resend()
> 
> I expect that got fixed in later kernels.

Yes, I've just tried 2.6.23-rc5-git1 and the warning has gone!


>> Without the nolapic option the kernel will panic when trying to suspend 
>> to disk.
> 
> A *large* number of people need noapic or nolapic to get Linux to work.

Even better, on 2.6.23-rc5-git1 I don't need nolapic anymore!


>> Here are the last lines of the kernel output:
>>
>> EIP: [<c01127fd> lapic_nmi_suspend+0x1d/0x30 ss:ESP 0068:c1ae3ec8
>> Kernel panic - not syncing: Attempted to kill init!
> 
> Are you able to provide us with more information about this bug? 

If you're still interested in more more information now that the bug has 
apparently been solved "en passant" I can take a photograph tomorrow. 
Please, let me know.

>> With more recent kernels the system will hang with 
>> "Suspending console(s)".
> 
> My Vaio reliably hangs at the same place with 2.6.23-rc4.  I'll bisect that
> next week sometime.  Hopefully the result of that effort will fix your bug.
>  Please test Linus's tree regularly and don't let us release 2.6.23 until
> it is fixed.

Great!


>> 3. Even with the 2.6.18 kernel sound won't work after suspending to ram. 
>> I don't know when this started, but I know that this has not been an 
>> issue in the past.
> 
> Please provide full details in a separate bug report.  Send that report to
> myself, linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@suse.cz> and
> Takashi Iwai <tiwai@suse.de>

I'll do that in the next couple of days.

Thanks again,

Felix


  reply	other threads:[~2007-09-05 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 12:42 Regressions w.r.t. suspend behaviour in recent kernel versions Felix Homann
2007-09-05 16:36 ` Andrew Morton
2007-09-05 22:51   ` Felix Homann [this message]
2007-09-06  1:01     ` 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=46DF3306.7030608@onlinehome.de \
    --to=fexpop@onlinehome.de \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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