linux-kernel - Re: PROBLEM: BUG: unable to handle kernel paging request at ffff81013a612000

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]

Message-ID: <483AA746.3000501@trypill.org>
Date:	Mon, 26 May 2008 14:04:22 +0200
From:	Georges Toth <georges@...pill.org>
To:	Vegard Nossum <vegard.nossum@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: BUG: unable to handle kernel paging request at ffff81013a612000

Hi,

Vegard Nossum wrote:
> It seems that you have three proprietary modules loaded: vmnet, vmmon,
> and nvidia (identified by the (P) suffix in module list above).
> Especially the vmnet and vmmon modules which have been loaded forcibly
> (the F suffix).
>
> This means that it will be very hard for the mainline developers to
> debug your problem. Most likely your report will be ignored.
>
> I suggest starting your system without loading these kernel modules in
> the first place. Note: It is important that the modules are not loaded
> in the first place. Simply unloading them won't work, as the damage
> may have been done already. If you can reproduce the problem when
> these modules have not been loaded, then I am sure it will be
> inspected properly.
>
> If you cannot reproduce the problem, however, I would try to narrow
> down the problem by loading only one or the other of the modules, then
> contact the vendor(s) of the offending modules.
>
> The easiest way to prevent a module from loading at boot is to remove
> the corresponding .ko file from /lib/modules/<kernel-version>/. (But
> keep the original file if you want to move it back later.)
>   
As suggested I've removed all proprietary modules and am using the nv 
xorg module for now.
Should that bug occur again, I'll let you know :-).

Thanks

-- 
regards,

Georges Toth

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