From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Jeff Garzik <jeff@garzik.org>,
LKML <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Len Brown <len.brown@intel.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: pcibios_scanned needs to be set in ACPI? (was Re: 2.6.25-rc5: Reported regressions from 2.6.24)
Date: Wed, 12 Mar 2008 16:16:01 -0700 [thread overview]
Message-ID: <20080312231601.GB24820@kroah.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0803121553070.3557@woody.linux-foundation.org>
On Wed, Mar 12, 2008 at 04:02:57PM -0700, Linus Torvalds wrote:
>
>
> On Wed, 12 Mar 2008, Greg KH wrote:
> >
> > What happend in .25-rc was that we now catch these kinds of problems
> > (watching for duplicate kobjects to be registered and such.) So this
> > might have always been happening, but no warning was ever produced.
>
> It's not the warning that worries me. It's the apparent oops (keyboard
> leds blinking?) at shutdown/poweroff!
It oopses at shutdown? I thought this was originally reported as a
"will not power off" which for a while was attributed to the cpufreq fix
that went into -rc2 or -rc3.
I didn't realize there was an oops, sorry.
> > The reason we aren't shutting down is also due to the way kobjects now
> > work. If you don't clean up properly, they linger around and something
> > on the shutdown path (I haven't figured that out yet) doesn't want to
> > stop the machine.
>
> .. and that's my issue! We're too late in the game to try to figure things
> out and leave things hanging. The patch broke something, it needs to be
> fixed or reverted. It's been going on too long.
>
> I think it should have been reverted probably two weeks ago already. We
> can re-apply it early in the 2.6.26 series, and then try to fix it right.
>
> Since there is at least a patch worth trying now, I'll hold off reverting
> it and wait for Guennardi to test the patch, but the fact is, we shouldn't
> have a known-broken kernel for several weeks, when there is a known fix
> for it in reverting a single commit!
>
> We have _way_ too many regressions as it is. Regressions are bad. Ones
> that have known causes and haven't been fixed in three weeks are
> unacceptable.
Sorry, I thought this was just a warning at boot time.
It would be interesting to see if reverting the pci_bus patch did
anything about the fact that we register the root PCI bus through two
different methods.
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-12 23:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 23:14 2.6.25-rc5: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-03-11 0:40 ` Jeff Garzik
2008-03-11 1:05 ` Rafael J. Wysocki
2008-03-11 2:15 ` Linus Torvalds
2008-03-11 3:00 ` Andrew Morton
2008-03-11 8:28 ` Ingo Molnar
2008-03-11 18:57 ` Jeff Garzik
2008-03-11 22:41 ` Rafael J. Wysocki
2008-03-12 20:01 ` Linus Torvalds
2008-03-12 20:32 ` Greg KH
2008-03-12 21:27 ` pcibios_scanned needs to be set in ACPI? (was Re: 2.6.25-rc5: Reported regressions from 2.6.24) Greg KH
2008-03-12 21:38 ` Greg KH
2008-03-12 22:25 ` Linus Torvalds
2008-03-12 22:54 ` Greg KH
2008-03-12 23:09 ` Linus Torvalds
2008-03-13 4:48 ` Greg KH
2008-03-13 5:44 ` Greg KH
2008-03-13 6:24 ` Yinghai Lu
2008-03-13 10:07 ` Guennadi Liakhovetski
2008-03-13 10:06 ` Guennadi Liakhovetski
2008-03-13 15:32 ` Greg KH
2008-03-12 21:41 ` Len Brown
2008-03-12 22:20 ` Linus Torvalds
2008-03-12 22:34 ` Greg KH
2008-03-12 23:02 ` Linus Torvalds
2008-03-12 23:16 ` Greg KH [this message]
2008-03-12 23:32 ` Guennadi Liakhovetski
2008-03-12 23:37 ` Greg KH
2008-03-12 23:35 ` Linus Torvalds
2008-03-12 23:17 ` Guennadi Liakhovetski
2008-03-12 23:37 ` Linus Torvalds
2008-03-12 23:47 ` Guennadi Liakhovetski
2008-03-17 19:20 ` 2.6.25-rc5: Reported regressions from 2.6.24 Jeff Garzik
2008-03-11 12:22 ` Stefan Richter
2008-03-11 13:04 ` Adrian Bunk
2008-03-17 21:28 ` Thomas Meyer
2008-03-19 9:15 ` Stefan Richter
2008-03-12 22:12 ` Christian Kujau
2008-03-12 23:01 ` Rafael J. Wysocki
2008-03-13 5:03 ` David Chinner
2008-03-13 21:12 ` Rafael J. Wysocki
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=20080312231601.GB24820@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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