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

Date:	Mon, 26 May 2008 13:21:01 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Georges Toth" <georges@...pill.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: BUG: unable to handle kernel paging request at ffff81013a612000

Hi,

On Mon, May 26, 2008 at 12:13 PM, Georges Toth <georges@...pill.org> wrote:
> Hi,
>
> Please CC me with any replies as I'm not subscribed to the list.
>
> I'm running a vanilla 2.6.25.4 kernel.
>
> I apparently hit a bug in the kernel.
> When the problem starts my system becomes very unstable, many programs crash
> others I can barely shut down correctly and a reboot fails.
>
> I've hit the problem once trying to do "echo disk > /sys/power/state" and
> another time while writing do the disk inside a vmware guest.
> And a couple of times it happened randomly, e.g. while converting some files
> to mp3's and writing them to a usb device.
>

Thanks for the report.

> BUG: unable to handle kernel paging request at ffff81013a612000
> IP: [<ffffffff8027391b>] __slab_alloc+0x24a/0x4f8
> PGD 8063 PUD d063 PMD 800040013a6001e3
> Oops: 000b [1] SMP
> CPU 0
> Modules linked in: vmnet(PF) vmmon(PF) vmblock pwc compat_ioctl32 videodev
> v4l1_compat snd_usb_audio snd_usb_lib snd_rawmidi snd_hwdep it87 hwmon_vid
> xts gf128mul dm_crypt bridge llc tun vfat fat usb_storage nvidia(P) i2c_i801
> snd_hda_intel
> Pid: 15862, comm: pdflush Tainted: PF        2.6.25.4 #5

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.)

Good luck.

Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/