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

Newegg Daily Deals

Reply
 
Thread Tools
Old 06-12-07, 04:14 AM   #13
tytanick
Registered User
 
Join Date: Jun 2007
Posts: 53
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

hi,i have this NVRM error but tell me , is you but similar to mine (lagging in X)
check my post and watch 2 movies showing my problem:
http://www.nvnews.net/vbulletin/showthread.php?t=93134
tytanick is offline   Reply With Quote
Old 06-12-07, 06:27 AM   #14
Lithorus
Registered User
 
Lithorus's Avatar
 
Join Date: Sep 2004
Posts: 783
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Quote:
Originally Posted by jay8378
OK i started from scratch.
installed SuSe 10.2 x64 again.
As soon as i got into SuSe, i installed the latest driver from nvidias site released june 8th
i hope they release this driver in the ubuntu repo soon.
anyways.. i had to download nexuiz and manual install it and it ran great with --SLI=auto, no crash.
i re-ran it a few times still no crash.
I got swg running in wine.
it was all messed up and not playable but still no crash.
re-booted and re-tested, still fine.
So it has to be in the ubuntu/deb system somewhere.
I can run SLI in windows vista64 fine as well.
Nice that it somewhat works, but when you look at it a little more OpenSUSE 10.2 and Edgy have the similar kernel (2.6.18). Feisty uses 2.6.20, so it could simply be a 2.6.18 vs 2.6.20 issue. I beleive jokx reported that Edgy was working, but not Feisty. This would prove more his point.
Lithorus is offline   Reply With Quote
Old 06-12-07, 07:33 AM   #15
lloeki
Arch Linux
 
lloeki's Avatar
 
Join Date: Oct 2006
Posts: 122
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

so, did you people tried what zander suggested? it is a workaround against a regression in 2.6.20, and fixed some nasty texture corruption issue for me.
lloeki is offline   Reply With Quote
Old 06-12-07, 08:10 AM   #16
tytanick
Registered User
 
Join Date: Jun 2007
Posts: 53
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

i am using 2.6.21 kernel, and i still have this problem
tytanick is offline   Reply With Quote
Old 06-12-07, 09:13 AM   #17
Endperform
Nvidia Linux User
 
Join Date: May 2007
Location: Georgia, US
Posts: 3
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Quote:
Originally Posted by zander
Does the problem reproduce if you use a Linux kernel older than Linux 2.6.20 or a driver modified per these instructions: http://www.nvnews.net/vbulletin/show...3&postcount=15?
Yes, still experiencing random locks to this day. Upgraded to the latest driver, locked up again.
Endperform is offline   Reply With Quote
Old 06-12-07, 10:34 AM   #18
jay8378
Registered User
 
Join Date: Jun 2007
Posts: 23
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Quote:
Originally Posted by tytanick
hi,i have this NVRM error but tell me , is you but similar to mine (lagging in X)
check my post and watch 2 movies showing my problem:
http://www.nvnews.net/vbulletin/showthread.php?t=93134
sort've but way worse.
in kubuntu my system would lag so much the mouse would move only once about every 30 seconds. and would not respond to clicks.
in ubuntu x completely locks up. sometimes the mouse moves most the time it locks as well.
during these lockups i can still ssh in and run commands in both systems.
in top xorg is taking 100% cpu i try to stop gdm and kdm but is un responsive. killing it doesnt work.
when i issue "shutdown -r now" the screen usually gets corrupt and i have to hard reset it.
i think the underlying system has shutdown at this point though.
jay8378 is offline   Reply With Quote
Old 06-12-07, 10:49 AM   #19
jay8378
Registered User
 
Join Date: Jun 2007
Posts: 23
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Quote:
Originally Posted by Lithorus
Nice that it somewhat works, but when you look at it a little more OpenSUSE 10.2 and Edgy have the similar kernel (2.6.18). Feisty uses 2.6.20, so it could simply be a 2.6.18 vs 2.6.20 issue. I believe jokx reported that Edgy was working, but not Feisty. This would prove more his point.
Yes, i had SLI in edgy working and it was enabled by default, i think. Was along time ago. I know it was working because it was the first time i had seen the green HUD bars. SLI wasn't enabled by default in feisty. i think i had installed the driver manually in edgy. I tried that in feisty a with the 9755 driver with the same problem though


Quote:
Originally Posted by lloeki
so, did you people tried what zander suggested? it is a workaround against a regression in 2.6.20, and fixed some nasty texture corruption issue for me.
I might try this tonight.
jay8378 is offline   Reply With Quote
Old 06-13-07, 12:26 AM   #20
jay8378
Registered User
 
Join Date: Jun 2007
Posts: 23
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

ok i'm not sure if its the new driver or the function cpa flush but either way i think its fixed. ive rebooted a couple times and no crash yet. /crosses_fingers will post if i get another crash thanks for the help.
jay8378 is offline   Reply With Quote

Old 06-13-07, 05:32 AM   #21
tytanick
Registered User
 
Join Date: Jun 2007
Posts: 53
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

unfortunatley this tip doesnt work !!!!!!!!!
http://www.nvnews.net/vbulletin/show...3&postcount=15
i tested with kernel 2.6.19, this error:
NVRM: Xid (0001:00): 13, 0005 00000000 00008297 0000109c 43c1f783 00000010
NVRM: Xid (0001:00): 30, L1 -> L0
show up after 10 min of playing in 3d game, and after turning off game, this error still appear, and i have still those lags :


My problem is that : system just after fresh power on works fine: (watch this movie)
http://video.google.pl/videoplay?doc...59884532588654
And when i play for about 1-3h Silkroad Online in WINE (this is 3d game) whole kde LAGGING (see this video)
http://video.google.pl/videoplay?doc...18104841697092

so please NVIDIA CORPORATION FIX THIS BUG , because all users have it !
i am waiting for fixed driver, because i have 8500gt and nothing else than using beta bugged driver !
tytanick is offline   Reply With Quote
Old 06-13-07, 05:44 AM   #22
kriko
openSuSE11
 
kriko's Avatar
 
Join Date: Aug 2005
Location: Europe, Slovenia, Koper
Posts: 515
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Can anyone in this thread try something for me? I have this kind of errors, when using beryl with backingstore and this thing is reproducible, by opening beryl menu. So what I'm asking is to start Xorg with backingstore, so add:
Code:
  Option       "BackingStore" "True"
to Device section and restart Xorg. Start beryl-manager. Move your mouse to beryl-manager icon in system tray and right-click (so menu opens up). When you open menu, screen quickly flashes (it does some kind of graphic opereation - don't know what exactly) and a second later I get jerky desktop. Don't panic though, it can be fixed - just click on desktop (imagine you cursor, since it will be stuck) and the problem will be gone. After that remove backingstore line from xorg.conf.
Also I have 6600gt 128MB, so this might not occur on other graphic boards, kernel is 2.6.20-ck1 (no, it is not because of ck patch, it occurs even with stock suse kernel).

I hope I described above steps well, if in doubt, please ask. Meanwhile I'll try mentioned fix.
Thanks.
kriko is offline   Reply With Quote
Old 06-13-07, 10:44 AM   #23
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Forum threads based on specific Xid codes are unlikely to be a productive means of isolating or debugging potential driver bugs. An Xid code represents a class of problem, not a specific bug. 50 people could be seeing Xid:30, and they could potentially represent 50 completely different & unrelated bugs (and not even all NVIDIA driver bugs). Thus, asking NVIDIA to "fix this bug" is unfortunately not going to help anyone, as fixing one potential cause of Xid:30 could still leave the remaining 49 unfixed.

I'd strongly recommend that each person start a new thread after reviewing all of this forum's sticky posts, and provide detailed information on the problem that they're experiencing (in the latest released driver), detailed reproduction steps, and an nvidia-bug-report.log which captures the problem.
netllama is offline   Reply With Quote
Old 06-18-07, 12:56 PM   #24
pius
Registered User
 
Join Date: Jun 2007
Posts: 11
Default Re: NVRM: Xid (0001:00): 30, L1 -> L0 NOT FIXED YET !!!!!

Maybe I'm unaware of something but why don't you assign a code to the specific event instead?
If you can't deduce anything based on current logs it means that they're simply useless and they could be Shakespeare's quotes just as well.

No offence, but you require everyone to start a new thread and to send all those bug reports and for what? Just to hear that you don't know what's going on and that you can't reproduce it in your own environment?
I'm a software developer and I perfectly know that some bugs can appear in specific situations which would be nearly impossible to reproduce in testing.
That's why the support from users is so important. And you've got users who are willing to help you track those issues. So why not to let them (and to help them) do this?
Otherwise it's very unlikely this will ever be solved. People will just become more and more frustrated and they'll give up eventually.

BTW, I'm one of them:

Jun 18 16:52:58 sandy kernel: [41763.480725] NVRM: Xid (0001:00): 6, PE0002 180c 003b0030 0002d1a0 00000000 42948990
Jun 18 16:52:58 sandy kernel: [41763.481779] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:52:58 sandy kernel: [41763.550600] NVRM: Xid (0001:00): 6, PE0002 180c 003b0030 00000000 ffffffff 00006fd1
Jun 18 16:52:58 sandy kernel: [41763.551654] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:52:58 sandy kernel: [41763.589327] NVRM: Xid (0001:00): 6, PE0002 0000 beef4901 00000000 ffffffff 00000000
Jun 18 16:52:58 sandy kernel: [41763.590366] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:52:58 sandy kernel: [41763.628030] NVRM: Xid (0001:00): 6, PE0002 0000 beef4901 00000000 ffffffff 00000000
Jun 18 16:52:58 sandy kernel: [41763.629071] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:52:58 sandy kernel: [41763.666748] NVRM: Xid (0001:00): 6, PE0002 0000 beef4901 00000000 ffffffff 00000000
Jun 18 16:52:58 sandy kernel: [41763.667804] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:52:59 sandy kernel: [41763.711574] NVRM: Xid (0001:00): 6, PE0002 0000 beef4901 00000000 ffffffff 00000000
Jun 18 16:52:59 sandy kernel: [41763.712634] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:52:59 sandy kernel: [41763.750286] NVRM: Xid (0001:00): 6, PE0002 0000 beef4901 00000000 ffffffff 00000000
Jun 18 16:52:59 sandy kernel: [41763.751343] NVRM: Xid (0001:00): 30, L1 -> L0
Jun 18 16:53:07 sandy kernel: [41771.685216] NVRM: Xid (0001:00): 8, Channel 00000020
Jun 18 16:53:07 sandy kernel: [41771.686353] NVRM: Xid (0001:00): 30, L1 -> L0
pius 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


Similar Threads
Thread Thread Starter Forum Replies Last Post
NVRM: Xid while using chromium browser blekot NVIDIA Linux 2 06-26-12 01:29 PM
xorg locks-up with newest nvidia drivers w/ vdpau. theroot NVIDIA Linux 1 06-24-12 11:04 AM
Screen freeze NVRM: Xid error ciancaroll NVIDIA Linux 0 06-05-12 01:05 PM
Xorg hang with 100% cpu, any driver version, GTX275 bones_was_here NVIDIA Linux 20 05-23-12 09:49 AM
GTX 460M, Xorg 1.12, nvidia driver 295.49, linux 3.3.5-1-ARCH and NVRM Xid 44 elsifaka NVIDIA Linux 0 05-14-12 08:48 AM

All times are GMT -5. The time now is 11:29 AM.


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