From: Greg KH <greg@kroah.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PCI] duplicate sysfs symbols getting registered in current git
Date: Mon, 25 Feb 2008 13:14:17 -0800 [thread overview]
Message-ID: <20080225211417.GA20505@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802252130410.19416@axis700.grange>
On Mon, Feb 25, 2008 at 09:31:22PM +0100, Guennadi Liakhovetski wrote:
> On Mon, 25 Feb 2008, Greg KH wrote:
>
> > On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote:
> > > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote:
> > >
> > > > On Tue, 19 Feb 2008, Greg KH wrote:
> > > >
> > > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
> > > > > > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2
> > > > > > getting the following warnings (with a bit of context):
> > > > >
> > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at boot
> > > > > time from this?
> > > >
> > > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as
> > > > unpacked, as it would have to be sent to the list, is 408K big. Will see
> > > > what Greg says.
> > >
> > > Actually, the most annoying problem with post 2.6.24 kernels on this
> > > machine is, that the system doesn't power off or reboot any more. And
> > > seeing other reports, where the reason for not powering down was unfreed
> > > kobjects, maybe this is the problem here too?
> >
> > If you have cpufreq enabled, that should solve this problem after the
> > 2.6.24-rc3 kernel release. Have you tried that version?
>
> Did you mean 25-rc3?
Sorry, yes :)
> But no, I do not have cpufreq enabled.
Then I suggest filing a new bug report so it doesn't get lost.
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-25 21:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 20:52 [PCI] duplicate sysfs symbols getting registered in current git Guennadi Liakhovetski
2008-02-20 6:38 ` Greg KH
2008-02-25 12:43 ` Guennadi Liakhovetski
2008-02-25 18:15 ` Guennadi Liakhovetski
2008-02-25 20:25 ` Greg KH
2008-02-25 20:31 ` Guennadi Liakhovetski
2008-02-25 21:14 ` Greg KH [this message]
2008-02-25 22:03 ` Guennadi Liakhovetski
2008-02-25 22:21 ` Greg KH
2008-02-26 20:16 ` Greg KH
2008-02-27 11:24 ` Guennadi Liakhovetski
2008-02-27 11:27 ` Guennadi Liakhovetski
2008-02-27 11:47 ` Cornelia Huck
2008-02-27 12:33 ` Guennadi Liakhovetski
2008-02-27 13:21 ` Cornelia Huck
2008-02-27 13:46 ` Guennadi Liakhovetski
2008-02-27 14:38 ` Cornelia Huck
2008-02-27 11:39 ` Guennadi Liakhovetski
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=20080225211417.GA20505@kroah.com \
--to=greg@kroah.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.