From: Georges Toth <georges@trypill.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: BUG: unable to handle kernel paging request at ffff81013a612000
Date: Mon, 26 May 2008 14:04:22 +0200 [thread overview]
Message-ID: <483AA746.3000501@trypill.org> (raw)
In-Reply-To: <19f34abd0805260421o363f61c3r9682d3c6a38056f8@mail.gmail.com>
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
prev parent reply other threads:[~2008-05-26 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 10:13 PROBLEM: BUG: unable to handle kernel paging request at ffff81013a612000 Georges Toth
2008-05-26 11:21 ` Vegard Nossum
2008-05-26 12:04 ` Georges Toth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483AA746.3000501@trypill.org \
--to=georges@trypill.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.