linux-kernel - Re: [PCI] duplicate sysfs symbols getting registered in current git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080225202546.GA8893@kroah.com>
Date:	Mon, 25 Feb 2008 12:25:46 -0800
From:	Greg KH <greg@...ah.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PCI] duplicate sysfs symbols getting registered in current git

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?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/