Bug 18300 - NV11 Locks Up On Xorg Initialization
Summary: NV11 Locks Up On Xorg Initialization
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-29 23:51 UTC by Evan Goers
Modified: 2009-03-07 04:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
kern.log (202.84 KB, application/x-gzip)
2008-10-29 23:54 UTC, Evan Goers
no flags Details
lspci (434 bytes, application/x-gzip)
2008-10-29 23:54 UTC, Evan Goers
no flags Details
syslog (16.67 KB, application/x-gzip)
2008-10-29 23:55 UTC, Evan Goers
no flags Details
Xorg.0.log (3.49 KB, application/x-gzip)
2008-10-29 23:55 UTC, Evan Goers
no flags Details
kern.log (915.28 KB, text/plain)
2008-10-30 01:23 UTC, Evan Goers
no flags Details
lspci (1.09 KB, text/plain)
2008-10-30 01:24 UTC, Evan Goers
no flags Details
syslog (102.85 KB, application/octet-stream)
2008-10-30 01:24 UTC, Evan Goers
no flags Details
Xorg.0.log (11.89 KB, text/plain)
2008-10-30 01:25 UTC, Evan Goers
no flags Details
kern.log (93.07 KB, text/plain)
2008-10-30 02:10 UTC, Evan Goers
no flags Details
Xorg.0.log (14.13 KB, text/plain)
2008-10-30 02:11 UTC, Evan Goers
no flags Details
Xorg log (44.11 KB, text/x-log)
2009-03-04 02:33 UTC, Paul Ezvan
no flags Details
Patch (414 bytes, patch)
2009-03-04 02:40 UTC, Stephane Marchesin
no flags Details | Splinter Review
kernel.log (163.72 KB, text/x-log)
2009-03-04 05:39 UTC, Paul Ezvan
no flags Details

Description Evan Goers 2008-10-29 23:51:30 UTC
On my laptop(a Dell Inspiron 2650), running Ubuntu 8.10 Intrepid Ibex, Xorg locks up the entire system when I use the nouveau drivers. I have followed the UbuntuPackages guide with no compilation errors for drm-modules. The screen turns black when Xorg starts and stays that way. Keyboard and mouse are unresponsive and I cannot even SSH into the laptop. I assume the laptop has locked up and is completely unresponsive at this point.

I have attached kern.log, syslog, Xorg.0.log, and lspci output.
Comment 1 Evan Goers 2008-10-29 23:54:16 UTC
Created attachment 19948 [details]
kern.log
Comment 2 Evan Goers 2008-10-29 23:54:45 UTC
Created attachment 19949 [details]
lspci
Comment 3 Evan Goers 2008-10-29 23:55:01 UTC
Created attachment 19950 [details]
syslog
Comment 4 Evan Goers 2008-10-29 23:55:19 UTC
Created attachment 19951 [details]
Xorg.0.log
Comment 5 Evan Goers 2008-10-30 01:23:05 UTC
Created attachment 19953 [details]
kern.log

Non-gzipped reupload.
Comment 6 Evan Goers 2008-10-30 01:24:09 UTC
Created attachment 19954 [details]
lspci

Non-gzipped reupload.
Comment 7 Evan Goers 2008-10-30 01:24:45 UTC
Created attachment 19955 [details]
syslog

Non-gzipped reupload.
Comment 8 Evan Goers 2008-10-30 01:25:16 UTC
Created attachment 19956 [details]
Xorg.0.log

Non-gzipped reupload.
Comment 9 Evan Goers 2008-10-30 02:10:54 UTC
Created attachment 19957 [details]
kern.log
Comment 10 Evan Goers 2008-10-30 02:11:30 UTC
Created attachment 19958 [details]
Xorg.0.log
Comment 11 Stuart Bennett 2009-01-13 15:56:02 UTC
(--) NOUVEAU(0): VideoRAM: 8192 kBytes

and

(EE) EXA(0): ExaDriverRec::offScreenBase must be <= ExaDriverRec::memorySize

are the critical things here.  You seem to only have 8Mb VRAM, which really isn't very much (the driver at present tends to assume more, probably a minimum of 16Mb).  Do you know if we are detecting the correct amount?

I don't think the GeForce2 Go uses host memory, but if it does it may be worth checking if the system bios has an option to increase the amount available to the card.
Comment 12 Evan Goers 2009-01-13 17:58:48 UTC
The BIOS does not give me the option to modify the videoram, or anything related. It is the basic Dell BIOS with limited configuration options.

The Geforce2Go in the laptop does indeed have 8MB of ram. It is being detected correctly. For what it's worth, NVIDIA's proprietary driver works just fine, as well as the NV driver, with a desktop resolution of 1024x768(games crawl at this resolution, however).
Comment 13 Stuart Bennett 2009-01-13 19:26:20 UTC
Looking again at the log provided (apologies for missing this bug when it was first filed), I note it's picking up a 1360x1360 virtual resolution, which at 32 bits per pixel will use 7.6M of ram for the display with very little left over, irrespective of the fact that nouveau tries to use only half the detected amount for the display, and 7.6M clearly doesn't fit in 4M.

I'd suggest removing any line in the xorg.conf setting a large virtual size, or indeed, anything else suggesting the server display a 1360 wide image.  This should cause it to use try to use a 1024x1024 virtual by default (the xserver makes it square for rotation purposes) -- if you don't need rotation, add the line `Virtual 1024 768' in xorg.conf under the depth 24 "display" subsection (in the "screen" section) for an even smaller memory footprint.  Finally, you might try setting DefaultDepth 16 in xorg.conf which should use half as much memory and so fit, but may be less stable (less tested), and will look worse.

If something's unclear here, attaching your current xorg.conf may help.
Comment 14 Evan Goers 2009-01-14 19:55:56 UTC
I have not actually used nouveau in a very long time, but I do remember my xorg.conf not having a "Virtual" line at all. I have since moved to Debian(from Ubuntu), but I could probably try reinstalling the driver again and testing it. Basically, I don't have the xorg.conf I used to use.

I will try testing again.
Comment 15 Evan Goers 2009-01-20 19:29:21 UTC
Ok, after some testing, changing the virtual line to "Virtual 1024 768" or changing the Depth to 16 doesn't seem to work. I still get the same old black screen and unusable system.
Comment 16 Stuart Bennett 2009-01-20 21:04:25 UTC
Thanks for re-testing.  If you've still got it, attaching your Xorg.0.log (or Xorg.0.log.old) of the attempt would help determine if it's still the memory issue or something else.
Comment 17 Paul Ezvan 2009-03-04 02:31:03 UTC
I get also a similar problem with a NV11DDR. The bios indicates 32 Mb of VRAM at startup, also confirmed in Xorg.log, so it may not be due to low vram amount.

Here are the logs :

messages.log:
Mar  4 12:04:29 hera init: Switching to runlevel: 5
Mar  4 12:04:29 hera agpgart-sis 0000:00:00.0: AGP 2.0 bridge
Mar  4 12:04:29 hera agpgart-sis 0000:00:00.0: putting AGP V2 device into 4x mode
Mar  4 12:04:29 hera nouveau 0000:01:00.0: putting AGP V2 device into 4x mode
Mar  4 12:04:29 hera [drm] Allocating FIFO number 0
Mar  4 12:04:29 hera [drm] nouveau_fifo_alloc: initialised FIFO 0
Mar  4 12:04:29 hera [drm] Allocating FIFO number 1
Mar  4 12:04:29 hera [drm] nouveau_fifo_alloc: initialised FIFO 1
Mar  4 12:04:30 hera [drm] PFIFO_CACHE_ERROR - Ch 1/4 Mthd 0x0180 Data 0x00000000

lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:09.0 Ethernet controller: Asix Electronics Corporation AX88141 Fast Ethernet Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV11DDR [GeForce2 MX200] (rev b2)

Xorg.0.log attached.
Comment 18 Paul Ezvan 2009-03-04 02:33:09 UTC
Created attachment 23506 [details]
Xorg log
Comment 19 Stephane Marchesin 2009-03-04 02:40:52 UTC
Created attachment 23507 [details] [review]
Patch
Comment 20 Stephane Marchesin 2009-03-04 02:41:32 UTC
Btw, please don't trim kernel logs next time, as this could hide relevant information.
Comment 21 Paul Ezvan 2009-03-04 05:38:26 UTC
With the patch id doesn't work either.
However, I got some new messages in kernel.log (also I tried without starting kdm but with startx).
The logfile is attached below.
Comment 22 Paul Ezvan 2009-03-04 05:39:00 UTC
Created attachment 23512 [details]
kernel.log
Comment 23 Stephane Marchesin 2009-03-05 23:59:50 UTC
Can you retry with current git of everything ?
Comment 24 Paul Ezvan 2009-03-06 06:21:15 UTC
The problem has disappeared with current git version !
Comment 25 Stephane Marchesin 2009-03-06 06:22:57 UTC
Good. Do you still ahve the patch on the DDX or not ?
Comment 26 Paul Ezvan 2009-03-06 07:05:57 UTC
No, it is the unpatched git version.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.