public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	len.brown@intel.com, linux-pm@osdl.org,
	linux-acpi@vger.kernel.org,
	Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
	Adrian Bunk <bunk@stusta.de>,
	Martin Lorenz <martin@lorenz.eu.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc3: known unfixed regressions (v3)
Date: Tue, 31 Oct 2006 23:15:38 +0200	[thread overview]
Message-ID: <20061031211538.GC6866@mellanox.co.il> (raw)
In-Reply-To: <Pine.LNX.4.64.0610300953150.25218@g5.osdl.org>

Quoting r. Linus Torvalds <torvalds@osdl.org>:
> Subject: Re: 2.6.19-rc3: known unfixed regressions (v3)
> 
> 
> 
> On Mon, 30 Oct 2006, Jun'ichi Nomura wrote:
> > 
> > Please revert the patch. I'll fix the wrong error handling.
> > 
> > I'm not sure reverting the patch solves the ACPI problem
> > because Michael's kernel seems not having any user of
> > bd_claim_by_kobject.
> 
> Yeah, doing a grep does seem to imply that there is no way that those 
> changes could matter.
> 
> Michael, can you double-check? I think Jun'ichi is right - in your kernel, 
> according to the config posted on bugzilla, I don't think there should be 
> a single caller of bd_claim_by_disk, since CONFIG_MD is disabled.

I double-checked, and of course you are right - the issues resurfaced after some
more use, even with the patch reverted.  I've written some scripts that do some
compiles from scratch, and suspend/resume several times.  Plan to try bi-secting
with that and see what that will come up with.

OTOH, from the discussion it seems just randomly pointing a finger at a patch
has uncovered some bugs - so maybe we should do this a bit more :)


-- 
MST

  parent reply	other threads:[~2006-10-31 21:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061029231358.GI27968@stusta.de>
2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
2006-10-30 15:27   ` Martin Lorenz
2006-10-30 16:17   ` Jun'ichi Nomura
2006-10-30 16:32     ` Michael S. Tsirkin
2006-10-30 17:20       ` Jun'ichi Nomura
2006-10-30 17:54         ` Michael S. Tsirkin
2006-10-30 16:44     ` Linus Torvalds
2006-10-30 17:34       ` Jun'ichi Nomura
2006-10-30 18:16         ` Linus Torvalds
2006-10-30 18:35           ` Adrian Bunk
2006-10-30 19:00             ` Michael S. Tsirkin
2006-10-30 19:06             ` Hugh Dickins
2006-10-31 12:47             ` Martin Lorenz
2006-10-30 18:58           ` Michael S. Tsirkin
2006-10-31 21:15           ` Michael S. Tsirkin [this message]
2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
2006-11-01  3:15     ` Len Brown
2006-11-01  5:11       ` Ernst Herzberg
2006-11-01  5:26         ` Linus Torvalds
2006-11-01  5:54           ` Michael S. Tsirkin
2006-11-01  6:16             ` Linus Torvalds
2006-11-01 17:25               ` Andi Kleen
2006-11-01 18:12                 ` Michael S. Tsirkin
2006-11-01 18:25                 ` Linus Torvalds
2006-11-01 19:33                   ` Michael S. Tsirkin
2006-11-01 19:44                     ` Linus Torvalds
2006-11-01 19:34                   ` Andi Kleen
2006-11-01 19:52                     ` Linus Torvalds
2006-11-01 21:15                       ` Andi Kleen
2006-11-01 22:35               ` Bill Davidsen
2006-11-01  6:18             ` Michael S. Tsirkin
2006-11-01  9:33               ` Pavel Machek
2006-11-01 12:02                 ` Michael S. Tsirkin
2006-11-01 17:17               ` Andi Kleen
2006-11-01 13:50           ` Stefan Seyfried
2006-11-01 16:36     ` Hugh Dickins
2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
2006-11-04 13:51       ` Hugh Dickins
2006-11-04 14:04       ` Russell King
2006-11-05  6:23         ` Adrian Bunk
2006-11-17  1:53       ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg

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=20061031211538.GC6866@mellanox.co.il \
    --to=mst@mellanox.co.il \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=martin@lorenz.eu.org \
    --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