[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49E7BD64.7060507@garzik.org>
Date: Thu, 16 Apr 2009 19:21:08 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Ingo Molnar <mingo@...e.hu>
CC: Dmitry Adamushko <dmitry.adamushko@...il.com>,
Peter Oruba <peter.oruba@....com>, amd64-microcode@...64.org,
Andreas Herrmann <andreas.herrmann3@....com>,
LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: microcode driver newly spews warnings
Ingo Molnar wrote:
> * Dmitry Adamushko <dmitry.adamushko@...il.com> wrote:
>
>> 2009/4/15 Jeff Garzik <jeff@...zik.org>:
>>> Ingo Molnar wrote:
>>>> (added Cc:s)
>>>>
>>>> * Jeff Garzik <jeff@...zik.org> wrote:
>>>>
>>>>> Jeff Garzik wrote:
>>>>>> Kernel: 2.6.30-rc1-00306-g8371f87
>>>>>> Hardware: ICH10 x86-64
>>>>>>
>>>>>> This is a regression from 2.6.29. Microcode spews the following WARNING
>>>>>> multiple times during boot:
>>>>>>
>>>>>>> ------------[ cut here ]------------
>>>>>>> WARNING: at fs/sysfs/group.c:138 sysfs_remove_group+0xeb/0xf0()
>>>>>>> Hardware name: sysfs group ffffffffa0209700 not found for
>>>>>>> kobject 'cpu0'
>>>
>>> Update: Regression occurs in 2.6.30-rc2.
>>>
>>> I've now reproduced this on ICH9/Core2 as well as ICH10/Nahelem.
>> Hi,
>>
>>
>> the following patch should eliminate the problem (and revert to
>> the old behavior that was altered by Rusty's patch).
>
> Jeff, did this do the trick for you?
Yes -- but I worry about keeping sysfs files around too long?
Jeff
--
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/
Powered by blists - more mailing lists