Bug 216690 - kernel-xen panic when installing nvidia drivers (building kernel module)
kernel-xen panic when installing nvidia drivers (building kernel module)
Status: CLOSED CANTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
5.0
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Rik van Riel
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-21 10:45 EST by Erik Bussink
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-11-21 12:21:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Erik Bussink 2006-11-21 10:45:55 EST
Description of problem:

While trying to evaluate RHEL Desktop (Client + WS + Virtualization) on a system
with a nvidia graphic card, the nvidia driver (NVIDIA-Linux-x86_64-1.0-9629-
pkg2.run) needs to be installed (requirement is kernel-xen-devel). 
While installing the nvidia driver, at the end of the building kernel module, 
the kernel-xen panics.

Version-Release number of selected component (if applicable):

kernel-xen-2.6.18-1.2747.el5.x86_64.rpm
kernel-xen-devel-2.6.18-1.2747.el5.x86_64.rpm

How reproducible:
Every attempt to install the nvidia driver

Steps to Reproduce:
1. boot into kernel-xen
2. start ./NVIDIA-Linux-x86_64-1.0-9629-pkg2.run
3. starts building kernel module
  
Actual results:


Process udevd (pid); 4922, theadinfo ffff88005b7be000, task fff8000
Stack: ffffffff80222b53 ffff880000ccfec0 08800000000000 0000000000
 ffffffff80210a53 ffffffff805a6800 000000000001040 0000000000
 ffff880000ccfec0 ffffffff805a683c
Call Trace:
 <IRQ> [<ffffffff80222b53>] smp_call_function_interrupt+0x4f/0x75
[<ffffffff80210a53>] handle_IRQ_event+0x2d/0x60
[<ffffffff802a82d3>] __do_IRQ+0xa4/0x105
[<ffffffff80287b7f>] _local_bh_enable+0x61/0xc5
[<ffffffff8038da52>] do_IRQ+0xe7/0xf5
[<ffffffff8038da52>] evtchn_do_upcall+0x86/0xe0
[<ffffffff8025cc8a>] do_hypervisor_callback+0x1e/0x2c
<EOI>  [<ffffffff8025da7c>] copy_page+0x50/0xe4
[<ffffffff80210ed9>] do_wp_page+0x35c/0x584
[<ffffffff8020961d>] __handle_mm_fault+0xe63/0xf12
[<ffffffff80260729>] _spin_lock_irqsave+0x9/0x14
[<ffffffff80263008>] do_page_fault+0xe48/0x11dc
[<ffffffff8025cb8f>] error_exit+0x0/0x6e


Code: 0f 22 c0 0f 0 0f 20 e6 49 89 f0 41 81 e8 80 00 00 00 74 08
RIP   [<ffffffff888b5e21>] :nvidia:__nv_setup_pat_entries+0x11/0x7
 RSP  <ffff880000cfbeb0>
 <0>Kernel panic - not syncing: Fatal execption



Expected results:

Smooth installation of nvidia driver.

Additional info:
Comment 1 Rik van Riel 2006-11-21 10:58:11 EST
Is this an open source nvidia driver, or the proprietary driver?
Comment 2 Erik Bussink 2006-11-21 12:09:17 EST
It's the proprietary client NVIDIA-Linux-x86_64-1.0-9629-pkg2.run.
Comment 3 Rik van Riel 2006-11-21 12:21:36 EST
As I do not have the source code to their driver, I will not be able to fix it.

Sorry.

Note You need to log in before you can comment on or make changes to this bug.