Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 09-07-11, 04:10 AM   #1
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & drivers

Dear List,

I am starting a new thread, but please see this one for very similar issues (I do not have a zotac mobo, and yet I have exactly the same kernel oops to worry about):

http://www.nvnews.net/vbulletin/showthread.php?t=162538

I have of course attached the nvidia-bug-report.log, but here are some pertinent details.

I've tried Ubuntu 10.04 and 11.04 and Debian 6.0 (squeeze), the latter with both the stable kernel (2.6.32) and the "official" backport of 2.6.39. I can compile and install both the certified 260- and 280-versions of NVIDIA drivers (both directly off nvidia.com and the debian way using dkms) without glitches. modprobe loads the nvidia module without issues:

Code:
$ lsmod | grep nvidia
nvidia              11483630  4 
i2c_core               23766  3 nvidia,fschmd,i2c_i801
Every single time I start X or let GDM do the same, I end up with a black/blank screen, and an unresponsive keyboard (no Ctrl-Alt-F1 to get back to console). I can ssh into the machine and have, like others such as in the thread quoted above, found that the problem is a kernel OOPS upon linking to (?) NVRM. This is the relevant portion of kern.log

Code:
Sep  7 10:01:24 isis kernel: [70461.603348] BUG: unable to handle kernel paging request at ffffc90007d95000
Sep  7 10:01:24 isis kernel: [70461.603352] IP: [<ffffffffa042c479>] _nv022575rm+0x127/0x202 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603453] PGD c1f415067 PUD 61f875067 PMD c060e9067 PTE 0
Sep  7 10:01:24 isis kernel: [70461.603456] Oops: 0000 [#1] SMP 
Sep  7 10:01:24 isis kernel: [70461.603457] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video Driver/uevent
Sep  7 10:01:24 isis kernel: [70461.603459] CPU 12 
Sep  7 10:01:24 isis kernel: [70461.603460] Modules linked in: parport_pc ppdev bridge lp parport stp bnep rfcomm bluetooth rfkill acpi_cpufreq mperf cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_userspace binfmt_misc fuse loop firewire_sbp2 snd_hda_codec_hdmi nvidia(P) snd_hda_codec_realtek tpm_infineon snd_hda_intel snd_hda_codec snd_hwdep fschmd i2c_i801 tpm_tis tpm tpm_bios ipmi_si i7core_edac snd_pcm edac_core psmouse snd_seq i2c_core snd_timer ipmi_msghandler snd_seq_device evdev serio_raw pcspkr snd container wmi processor soundcore snd_page_alloc thermal_sys button ext4 mbcache jbd2 crc16 dm_mod raid1 raid0 md_mod sd_mod crc_t10dif usbhid hid usb_storage uas sg sr_mod cdrom uhci_hcd ahci libahci libata mptsas firewire_ohci firewire_core crc_itu_t mptscsih mptbase scsi_transport_sas scsi_mod r8169 ehci_hcd mii usbcore [last unloaded: scsi_wait_scan]
Sep  7 10:01:24 isis kernel: [70461.603496] 
Sep  7 10:01:24 isis kernel: [70461.603498] Pid: 4383, comm: Xorg Tainted: P           O 2.6.39-bpo.2-amd64 #1 FUJITSU                          CELSIUS R670-2                /D2618-C1
Sep  7 10:01:24 isis kernel: [70461.603501] RIP: 0010:[<ffffffffa042c479>]  [<ffffffffa042c479>] _nv022575rm+0x127/0x202 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603567] RSP: 0018:ffff880604fbf978  EFLAGS: 00010206
Sep  7 10:01:24 isis kernel: [70461.603568] RAX: 00000000000000b9 RBX: ffffc90007d94f47 RCX: 000000000000001e
Sep  7 10:01:24 isis kernel: [70461.603570] RDX: 000000000000010c RSI: ffffc90007d94000 RDI: ffffffff81623fe0
Sep  7 10:01:24 isis kernel: [70461.603571] RBP: ffff88060529f108 R08: 00003ffffffff000 R09: ffff880000000000
Sep  7 10:01:24 isis kernel: [70461.603573] R10: 0000000000000296 R11: 00000000df7bb000 R12: ffff880605976800
Sep  7 10:01:24 isis kernel: [70461.603574] R13: 00000000df7baf47 R14: 00000000df7baf47 R15: 0000000000000000
Sep  7 10:01:24 isis kernel: [70461.603576] FS:  00007f495fc3c700(0000) GS:ffff88061fcc0000(0000) knlGS:0000000000000000
Sep  7 10:01:24 isis kernel: [70461.603578] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep  7 10:01:24 isis kernel: [70461.603579] CR2: ffffc90007d95000 CR3: 0000000604303000 CR4: 00000000000006e0
Sep  7 10:01:24 isis kernel: [70461.603580] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep  7 10:01:24 isis kernel: [70461.603582] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Sep  7 10:01:24 isis kernel: [70461.603583] Process Xorg (pid: 4383, threadinfo ffff880604fbe000, task ffff88060444d6a0)
Sep  7 10:01:24 isis kernel: [70461.603585] Stack:
Sep  7 10:01:24 isis kernel: [70461.603586]  ffff880605976000 ffff880605976800 ffff880605976000 ffff880606302000
Sep  7 10:01:24 isis kernel: [70461.603589]  000000000000001e ffffffffa042c7d4 ffff8806066ca000 ffff8806066ca000
Sep  7 10:01:24 isis kernel: [70461.603592]  ffff880606302000 ffffffffa04279f8 ffff8806066ca000 ffff880606302000
Sep  7 10:01:24 isis kernel: [70461.603595] Call Trace:
Sep  7 10:01:24 isis kernel: [70461.603660]  [<ffffffffa042c7d4>] ? _nv022591rm+0x76/0x9e [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603724]  [<ffffffffa04279f8>] ? _nv022548rm+0xcf/0x301 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603788]  [<ffffffffa0427cd5>] ? _nv022598rm+0xab/0x174 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603851]  [<ffffffffa0427dee>] ? _nv022547rm+0x50/0x5d [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603916]  [<ffffffffa042ea5d>] ? _nv022539rm+0x6e/0x78 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.603997]  [<ffffffffa0a43134>] ? _nv019309rm+0x69/0x121 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604076]  [<ffffffffa0a430b2>] ? _nv019323rm+0xe8/0x101 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604150]  [<ffffffffa046b421>] ? _nv004632rm+0x68/0x1f4 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604290]  [<ffffffffa0809387>] ? _nv015073rm+0x176/0x4c3 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604430]  [<ffffffffa0807eeb>] ? _nv015366rm+0xe9/0x165 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604491]  [<ffffffffa03f2748>] ? _nv015546rm+0xd/0x12 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604570]  [<ffffffffa0a42e79>] ? _nv002297rm+0x19d/0x28a [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604648]  [<ffffffffa0a43ee8>] ? _nv002291rm+0x4a5/0x684 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604727]  [<ffffffffa0a4ac84>] ? rm_init_adapter+0x9e/0x1b6 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604804]  [<ffffffffa0a6be47>] ? nv_kern_open+0x56f/0x708 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604809]  [<ffffffff810fe37c>] ? deactivate_super+0x3c/0x3c
Sep  7 10:01:24 isis kernel: [70461.604812]  [<ffffffff810fe6fe>] ? chrdev_open+0x12a/0x148
Sep  7 10:01:24 isis kernel: [70461.604814]  [<ffffffff810fe5d4>] ? cdev_put+0x1a/0x1a
Sep  7 10:01:24 isis kernel: [70461.604816]  [<ffffffff810fa46d>] ? __dentry_open+0x180/0x297
Sep  7 10:01:24 isis kernel: [70461.604818]  [<ffffffff81103537>] ? dget+0x12/0x1e
Sep  7 10:01:24 isis kernel: [70461.604821]  [<ffffffff81105bd1>] ? do_last+0x449/0x543
Sep  7 10:01:24 isis kernel: [70461.604823]  [<ffffffff811071c1>] ? path_openat+0xc6/0x317
Sep  7 10:01:24 isis kernel: [70461.604827]  [<ffffffff8110f5c1>] ? inode_change_ok+0x92/0x109
Sep  7 10:01:24 isis kernel: [70461.604829]  [<ffffffff8110f48a>] ? setattr_copy+0x98/0xd7
Sep  7 10:01:24 isis kernel: [70461.604831]  [<ffffffff811074df>] ? do_filp_open+0x2c/0x75
Sep  7 10:01:24 isis kernel: [70461.604833]  [<ffffffff8110fd94>] ? alloc_fd+0x69/0x10b
Sep  7 10:01:24 isis kernel: [70461.604835]  [<ffffffff810fa1b8>] ? do_sys_open+0x61/0xe8
Sep  7 10:01:24 isis kernel: [70461.604838]  [<ffffffff81339392>] ? system_call_fastpath+0x16/0x1b
Sep  7 10:01:24 isis kernel: [70461.604839] Code: 55 14 48 89 c6 4c 89 ef 41 ff 94 24 88 02 00 00 48 89 c3 48 85 c0 0f 84 b3 00 00 00 b8 00 00 00 00 48 83 7d 08 00 76 12 8b 55 2c <0f> b6 0c 03 00 4d 2b 48 ff c0 48 39 c2 77 f1 80 7d 2b 00 75 7c 
Sep  7 10:01:24 isis kernel: [70461.604855] RIP  [<ffffffffa042c479>] _nv022575rm+0x127/0x202 [nvidia]
Sep  7 10:01:24 isis kernel: [70461.604919]  RSP <ffff880604fbf978>
Sep  7 10:01:24 isis kernel: [70461.604920] CR2: ffffc90007d95000
Sep  7 10:01:24 isis kernel: [70461.604922] ---[ end trace fd4da73e7b31f3c8 ]---
Other similar posts on other forums have indicated a possible ldd-bug (binutils). However, I'm certain I'm linking with the bdf-variant, not gold:

Code:
$ ls -l /usr/bin/ld*
lrwxrwxrwx 1 root root       6 Sep  5 13:50 /usr/bin/ld -> ld.bfd
-rwxr-xr-x 1 root root  555184 Jan 25  2011 /usr/bin/ld.bfd
-rwxr-xr-x 1 root root 2066024 Jan 25  2011 /usr/bin/ld.gold
-rwxr-xr-x 1 root root    5271 Jan 23  2011 /usr/bin/ldd
My system details are in the log, but just to be explicit... My system is a Fujitsu R670-2 (12 x Xeon 5660, 12x4GB RAM) with a Fujitsu D2618-C1 motherboard (Intel 5520 chipset) and a single Tesla C2070 (no other GPU's installed).

I'd like to reiterate that I run into the same issue on several distros running several combinations of kernel, Xorg, and nvidia.ko.

I hope this is sufficient to help debug the problem, and that indeed a solution may soon be available... As you may have guessed from the presence of the C2070, nouveau is just not an option.

Best regards,

Chris
Attached Files
File Type: gz nvidia-bug-report.log.gz (40.4 KB, 67 views)
bailey.cj is offline   Reply With Quote
Old 09-07-11, 07:57 AM   #2
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Dear all,

For completeness, I've just done a fresh install of debian wheezy (testing, snapshot 06 Sep 11) with the 3.0 kernel and whatnot. The end result is the same: kernel oops on startx leaving me with a rather costly brick of a CUDA workstation.

I've attached the bug.log for this wheezy-crash as well.

Anyone else out there with this problem? I find it hard to believe this would be specific to the zotac and fujitsu mobo's discussed on this list?

Cheers,

/Chris
Attached Files
File Type: gz wheezy-06Sep-nvidia-bug-report.log.gz (42.4 KB, 53 views)
bailey.cj is offline   Reply With Quote
Old 09-08-11, 05:22 AM   #3
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

What is Video BIOS in /proc/driver/nvidia/gpus/0/information and your display model?
sandipt is offline   Reply With Quote
Old 09-09-11, 07:49 AM   #4
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Dear sandipt

Thank you for taking the time to take a look at this! Here's the output you asked for:

Code:
# cat /proc/driver/nvidia/gpus/0/information 
Model: 		 Tesla C2070
IRQ:   		 30
Video BIOS: 	 ??.??.??.??.??
Card Type: 	 PCI-E
DMA Size: 	 32 bits
DMA Mask: 	 0xffffffff
Bus Location: 	 0000:07.00.0
I'm intrigued by the fact that you asked what my Video BIOS version was, and to find that obviously this has not been detected!

Edit: Display model is Fujitsu P27T-6 IPS.

One symptom I've forgotten to mention is the boot process stalls (for 180 seconds) during the phase "Waiting for /dev to be fully populated". Following those 3 mins, the system continues init normally. I can see in the logs that this happens during NVRM loading the nvidia module:

Code:
# cat /var/log/kern.log
 --- SNIP ----
Sep  9 09:33:56 isis kernel: [   25.211451] device-mapper: uevent: version 1.0.3
Sep  9 09:33:56 isis kernel: [   25.211557] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
 --- SNIP ----
Sep  9 09:33:56 isis kernel: [   26.576448] IPMI System Interface driver.
Sep  9 09:33:56 isis kernel: [   26.576483] ipmi_si 0000:09:00.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
Sep  9 09:33:56 isis kernel: [   26.576485] ipmi_si: Trying PCI-specified kcs state machine at i/o address 0x4c00, slave address 0x0, irq 19
Sep  9 09:33:56 isis kernel: [   26.623992] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Sep  9 09:33:56 isis kernel: [   26.896291] nvidia: module license 'NVIDIA' taints kernel.
Sep  9 09:33:56 isis kernel: [   26.896293] Disabling lock debugging due to kernel taint
Sep  9 09:33:56 isis kernel: [   27.301922] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
Sep  9 09:33:56 isis kernel: [   27.303030] HDA Intel 0000:00:1b.0: setting latency timer to 64
Sep  9 09:33:56 isis kernel: [   27.395624] hda_codec: ALC663: BIOS auto-probing.
Sep  9 09:33:56 isis kernel: [   27.397170] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
Sep  9 09:33:56 isis kernel: [   27.460407] nvidia 0000:07:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30
Sep  9 09:33:56 isis kernel: [   27.460412] nvidia 0000:07:00.0: setting latency timer to 64
Sep  9 09:33:56 isis kernel: [   27.460415] vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Sep  9 09:33:56 isis kernel: [   27.462049] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 PDT 2011
Sep  9 09:33:56 isis kernel: [  206.331264] Adding 48631728k swap on /dev/md1.  Priority:-1 extents:1 across:48631728k 
Sep  9 09:33:56 isis kernel: [  206.571002] loop: module loaded
The module appears loaded, and the devices present:

Code:
# lsmod | grep nv
nvidia              11475905  0 
i2c_core               15835  2 nvidia,i2c_i801
# 
# ls -l /dev/nvidia*
crw-rw---- 1 root video 195,   0 Sep  9 09:33 /dev/nvidia0
crw-rw---- 1 root video 195, 255 Sep  9 09:33 /dev/nvidiactl
Does any of this help diagnose the problem? It seems it may have something to do with udev, no? I ran across this in other contexts, but have failed to understand what it may mean in mine.

I sure hope you can help me figure this one out!

Sincerely,

Chris

Last edited by bailey.cj; 09-09-11 at 08:28 AM. Reason: added display model
bailey.cj is offline   Reply With Quote
Old 09-12-11, 02:22 AM   #5
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Actually I need Video BIOS information . Please check in nvidia-settings > GPU page to get that.
sandipt is offline   Reply With Quote
Old 09-12-11, 03:49 AM   #6
artem
Registered User
 
Join Date: Jun 2006
Posts: 710
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

bailey.cj

Use nvclock to dump your GPU bios, zip it, and attach the resulting file here.
artem is offline   Reply With Quote
Old 09-12-11, 08:34 AM   #7
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Thanks sandipt and artem for your posts. Recall that I can't start X on the machine, so I couldn't simly run nvidia-settings.

I compiled nvclock 0.8b4 with the following results:

Code:
# /opt/local/bin/nvclock -i
It seems your card isn't officialy supported in NVClock yet.
The reason can be that your card is too new.
If you want to try it anyhow [DANGEROUS], use the option -f to force the setting(s).
NVClock will then assume your card is a 'normal', it might be dangerous on other cards.
Also please email the author the pci_id of the card for further investigation.
[Get that value using the -i option].

# ./nvclock -i -f
-- General info --
Card: 		Unknown Nvidia card
Architecture: 	GC0 A3
PCI id: 	0x0
GPU clock: 	-2147483.750 MHz
Bustype: 	PCI

-- Memory info --
Amount: 	0 MB
Type: 		128 bit SDR
Clock: 		-2147483.750 MHz
Not good... This combined with the strange stall during boot indicates that the card is not properly detected, right? But where on earth am I tripping here. I've installed a dozen NV-boards on as many rigs without any issues like this...

Here's a repost of the beginning of the kernel dump associated with trying to start X (and hence presumably hit the nvidia.ko for the first time; the use counts jumps from 0 to 4 according to lsmod):

Code:
Sep 12 14:49:05 isis kernel: [ 3354.395552] BUG: unable to handle kernel paging request at ffffc90006169000
Sep 12 14:49:05 isis kernel: [ 3354.395559] IP: [<ffffffffa02c5479>] _nv022575rm+0x127/0x202 [nvidia]
Sep 12 14:49:05 isis kernel: [ 3354.395679] PGD 61fc28067 PUD c1fc01067 PMD c1dc2a067 PTE 0
Sep 12 14:49:05 isis kernel: [ 3354.395681] Oops: 0000 [#1] SMP 
vers/NVIDIA ACPI Video Driver/uevent
Sep 12 14:49:05 isis kernel: [ 3354.395683] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video Driver/uevent
There's that udev-related event again... Are there perhaps any kernel mods I could try to get this card properly detected and loaded?

Best,

Chris
bailey.cj is offline   Reply With Quote
Old 09-13-11, 08:41 AM   #8
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

We can add Centos 6.0 to the list of no-go's

Driver installation (280.13) proceeds fine (I followed the instructions here: http://linux.xvx.cz/2011/01/nvidia-p...ers-and-rhel6/), but starting X (init 5) leads to a core dump and automatic reboot.

I'm not familiar enough with Centos to be able to figure out what's going on there, but just before I get dumped out, I can see the NVRM module trying to load itself in /var/log/messages.

This seems to be some rather fundamental incompatibility between my hardware, the linux kernel and NVIDIA's drivers. Given that the nouveau drivers do allow graphics output, it cannot be the Tesla card per se that's defunct here. To be sure, I also tested the rig with a Quadro FX 380. nouveau drivers worked OK, NVIDIA drivers led to the crash/kernel oops.

I see from the other thread that some issues were detected on the Zotac board I originally mentioned as an analogous situation to mine. Any chance there might be some parallels here...?

Any ideas/suggestions are warmly welcomed!

/Chris
bailey.cj is offline   Reply With Quote

Old 09-19-11, 03:47 AM   #9
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Hi there,

I realize that given the apparent hardware-level issues I'm having, my troubles may have more to do with the kernel than with NVIDIA's drivers. I would really appreciate any pointers anyone might have on how to proceed.

On linux 2.6.32-71.29.1.el6.x86_64 (Centos 6.0) I get this in the logs

Code:
# modprobe nvidia
Sep 19 10:28:19 isis kernel: nvidia 0000:07:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30
Sep 19 10:28:19 isis kernel: vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=none,decodes=none:owns=io+mem
Sep 19 10:28:19 isis kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 PDT 2011
One thing I noticed that I seem to be missing this line (found by googling for keywords):

Code:
[   11.874730] nvidia 0000:01:00.0: setting latency timer to 64
I'm drawing a blank here, please point me in a direction if you can see one!

Best,

Chris
bailey.cj is offline   Reply With Quote
Old 10-07-11, 03:14 AM   #10
frenchy2k1
Registered User
 
Join Date: Aug 2002
Location: San Jose, CA
Posts: 449
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

hi bailey,

if the problem is still ongoing (2 weeks since last message), 2 development:
- drivers have fixed the problem on the zotac boards, but as it was chipset related (NV79/NV7A), it seems unlikely to help.
- if you need to dump the bios of your c2070, you could do a USB stick boot with nvflash and get your bios this way:
* create a DOS usb boot
* load nvflash DOS on it ( http://www.techpowerup.com/downloads...5.100.0.1.html )
* execute nvflash --save c2070.rom
* zip and attach that rom file here
__________________
As the universe is curved, there cannot be a straight answer...
frenchy2k1 is offline   Reply With Quote
Old 10-10-11, 06:27 AM   #11
bailey.cj
Registered User
 
Join Date: Sep 2011
Posts: 9
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Hi Frenchy,

I was actually hoping that this statement in the change log for 285.05.09 would have been my savior:

"Fixed a bug causing a Linux kernel BUG when retrieving CPU information on some systems."

But alas, it's not: still same kernel crash as before (gone back to Debian 6.0 stable, 2.6.32). I'm not sure why the ION/Zotac/NV7x-issue would apply to me, but I guess I'll keep my fingers crossed for that. Can't say I'm hopeful, though.

Thanks for the tips on getting a BIOS dump out of the card. I'll try it next time I feel like approaching that morass.

To the NVidia-guys presumably out there: Care to comment on what might be going on here? Give me something to work with, please!

/Chris
bailey.cj is offline   Reply With Quote
Old 10-31-11, 09:11 AM   #12
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: startx causes kernel OOPS on Fujitsu D2618-C1 mobo, debian, many kernels & driver

Can somebody try by disabling 'Hyperthreading' in SBIOS ?
sandipt is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 07:46 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.