linux-kernel - Re: [GIT PATCH] driver core merge for 3.3

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] [day] [month] [year] [list]

Date:	Fri, 13 Jan 2012 20:03:04 +0100
From:	Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] driver core merge for 3.3

Kay Sievers <kay.sievers@...y.org> writes:

> On Fri, Jan 13, 2012 at 02:11, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>> Hmm. I think this is the cause of one of the suspend/resume problems I'm seeing:
>>
>>   Device 'machinecheck3' does not have a releae() function, it is
>> broken and must be fixed
>>
>> that's the WARN_ON() in drivers/base/core.c (line 192), and it comes
>> from disable_nonboot_cpus() doing the whole device_unregister() thing.
>>
>> Afaik, it's arch/x86/kernel/cpu/mcheck/mce.c.
>
> I guess this kind of warning just did not exist for the old sysdev
> devices. The 'machinecheck' devices are DEFINE_PER_CPU(struct device,
> mce_device) devices, so we will probably just add a dummy release
> function, which might not fix the problem you are seeing.
>
> Maybe you can check if the suspend problem goes away if you disable
> CONFIG_X86_MCE?

Hello,

three days ago I also reported about a suspend/resume problem and
disabling CONFIG_X86_MCE also helps on my machine, although I did not see
the above warning in my logs.

Dirk
--
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/