Xorg hangs randomly with nVidia drivers.

Bug #36511 reported by Bandit
This bug report is a duplicate of:  Bug #13530: nvidia-glx crashes/lockups. Edit Remove
14
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.15 (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Xorg hangs randomly since the last update (24Mar2006).

VideoCard = Gigabyte nVidia FX5500 AGP8x 256MB-DDR 128bit.
Motherboard = Biostar K8M800-M7A VIA chipset.
Xorg= 7.0.0-0ubuntu25
nVidia = 1.0.8178+2.6.15.7-3

Ubuntu Dapper 64bit Flight5 (latest updates as of 24Mar06)

There doesnt seem to be a real way to reproduce the effect other then just using the system. It seems very random and no one certain applicatio or process cuases the hang. Most of the time a Ctrl-Alt-Bckspce will kick you back to the GDM.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Do you overclock either your BIOS or your video card? Do the hangs occur while you are in the middle of typing something or when you go away for a few minutes? Is there anything mentioned in dmesg after a hang?

Revision history for this message
Bandit (bandit) wrote :

I do not overclock. Both the video card and the rest of the system is running at default speeds.

The lock up can happen no matter what your doing.
I have even had xorg lockup while downloading a file and no one using the system at that time.

The lock up does not occure if the system is idle and no one is running any applications on the screen.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Is there anything in the output of the
dmesg
after a hang (you will have to ctrl-alt-bs then re-login) that looks related to your card?

Revision history for this message
Bandit (bandit) wrote :
Download full text (22.6 KiB)

bandit@stardust:~$ dmesg
[4294667.296000] Linux version 2.6.15-19-386 (buildd@rothera) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu3)) #1 PREEMPT Mon Mar 20 16:46:02 UTC 2006
[4294667.296000] BIOS-provided physical RAM map:
[4294667.296000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[4294667.296000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[4294667.296000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[4294667.296000] BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)
[4294667.296000] BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
[4294667.296000] BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
[4294667.296000] BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
[4294667.296000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[4294667.296000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[4294667.296000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[4294667.296000] 1150MB HIGHMEM available.
[4294667.296000] 896MB LOWMEM available.
[4294667.296000] found SMP MP-table at 000f3620
[4294667.296000] On node 0 totalpages: 524000
[4294667.296000] DMA zone: 4096 pages, LIFO batch:0
[4294667.296000] DMA32 zone: 0 pages, LIFO batch:0
[4294667.296000] Normal zone: 225280 pages, LIFO batch:31
[4294667.296000] HighMem zone: 294624 pages, LIFO batch:31
[4294667.296000] DMI 2.3 present.
[4294667.296000] ACPI: RSDP (v000 VIAK8M ) @ 0x000f7720
[4294667.296000] ACPI: RSDT (v001 VIAK8M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x7fee3040
[4294667.296000] ACPI: FADT (v001 VIAK8M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x7fee30c0
[4294667.296000] ACPI: MADT (v001 VIAK8M AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x7fee8440
[4294667.296000] ACPI: DSDT (v001 VIAK8M AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
[4294667.296000] ACPI: PM-Timer IO Port: 0x4008
[4294667.296000] ACPI: Local APIC address 0xfee00000
[4294667.296000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[4294667.296000] Processor #0 15:12 APIC version 16
[4294667.296000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[4294667.296000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[4294667.296000] IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
[4294667.296000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[4294667.296000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[4294667.296000] ACPI: IRQ0 used by override.
[4294667.296000] ACPI: IRQ2 used by override.
[4294667.296000] ACPI: IRQ9 used by override.
[4294667.296000] Enabling APIC mode: Flat. Using 1 I/O APICs
[4294667.296000] Using ACPI (MADT) for SMP configuration information
[4294667.296000] Allocating PCI resources starting at 80000000 (gap: 7ff00000:7ed00000)
[4294667.296000] Built 1 zonelists
[4294667.296000] Kernel command line: root=/dev/sda1 ro quiet splash
[4294667.296000] mapped APIC to ffffd000 (fee00000)
[4294667.296000] mapped IOAPIC to ffffc000 (fec00000)
[4294667.296000] Initializing CPU#0
[4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes)
[4294667.296000] ...

Revision history for this message
John Simpkins (onerobot) wrote : Kernel.log attached

I've been having this exact same problem, only using different drivers. My problems surfaced at about the same time, and my kern.log looks very similar, with the same ide errors and misaligned pointers. My system crashes every 30 minutes or so and seems directly related to the amount of ide activity.

Changed in linux-restricted-modules-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

John:

Which graphics card and drivers do you have? If it's a completely different chipset that would suggest the bug is elsewhere.

John, Bandit:
The only real commonality that I can see that you both seem to running AMD64s on Via motherboards (which doesn't really narrow down the search space that far). In both cases does the caps lock light stop working? Also are things any more stable if you boot WITHOUT quiet splash and WITH noapic ?

Revision history for this message
Rick Delashmit (wyrd) wrote :

I appear to have this same bug - I get infrequent random lockups, but can also reliably reproduce it when shutting down intensive 3d apps. I get the same result without quiet splash and with noapic, on the Dapper beta. Caps lock light stops working, mouse and keyboard have no visible effect.

Graphics card: eVga Geforce 6200, AGP 8X, 256MB
Xorg: 7.0.0-0ubuntu29
Nvidia driver supplied by linux-restricted-modules-2.6.15-20-amd64-generic
Motherboard: Asus K8N-E Deluxe, nForce3 chipset.

If there is any additional information I can supply which may help, please let me know.

Revision history for this message
Bandit (bandit) wrote : Re: [Bug 36511] Re: Xorg hangs randomly with nVidia drivers.

The problem was so bad I had to remove Dapper off my PC. But I have
tried the same things are Rick. Sometimes my mouse wold keep working
something everything locked up. I studied every piece of documentation
on Xorg and nothing seems to correct the issue.
The whole extreme lock-ups started on the kernel that was released just
before I posted this bug. Before that it was very stable.
I suspect the problem falls on using the AGPart and would be better
corrected having a seperate kernel compiled for nVidia users using the
NVagp module in the kernel.

On Sat, 2006-04-22 at 18:20 +0000, Rick Delashmit wrote:
> I appear to have this same bug - I get infrequent random lockups, but can also reliably reproduce it when shutting down intensive 3d apps. I get the same result without quiet splash and with noapic, on the Dapper beta. Caps lock light stops working, mouse and keyboard have no visible effect.
>
> Graphics card: eVga Geforce 6200, AGP 8X, 256MB
> Xorg: 7.0.0-0ubuntu29
> Nvidia driver supplied by linux-restricted-modules-2.6.15-20-amd64-generic
> Motherboard: Asus K8N-E Deluxe, nForce3 chipset.
>
> If there is any additional information I can supply which may help, please let me know.
>

Revision history for this message
Alexandre Otto Strube (surak) wrote :

There are similar reports for ati and via video boards... perhaps the problem is elsewhere?

Revision history for this message
Rick Delashmit (wyrd) wrote :

I traced through my reproducable case, and that hang in particular is as a result of audio shutdown calls, not graphics related at all.

Revision history for this message
Bandit (bandit) wrote :

Mine still are video related. I had all system sounds shut off.
On Sun, 2006-04-23 at 16:39 +0000, Rick Delashmit wrote:
> I traced through my reproducable case, and that hang in particular is as
> a result of audio shutdown calls, not graphics related at all.
>

Revision history for this message
artson (artson) wrote :

Processor AMD 64 2000
BIOS Phoenix Technologies, LTD ASUS A8V-E SE ACPI
Video NVIDIA GeForce 6200 TurboCache 256 megs
Realtek AC'97 Audio for VIA (R) Audio Controller
2 Gigs of Ram

Using Kubuntu 6.06 Live. Initially I thought it was a Firefox problem as I was using it on the first hang. Firefox IS flakey on this version, by the way. Sometimes it will not start at all.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Unclear where the problem is; clearing source package field

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

Adam do you happen to know if this is still an issue?

Revision history for this message
Alan Rae (ailean) wrote :

I have had problems with this on the x86 version of dapper. Crtl+Alt+Del doesn't fix it - I have to bring up a terminal and restart all graphical processes. I usually just reboot for speed. It is more likely to happen while videos are playing.

I can't reproduce the bug.

Revision history for this message
Bandit (bandit) wrote :

I have two nVidia cards. Leadtek FX5200 128MB, AGP and a Gigabyte FX5500 256MB AGP. Using both video cards I experience the lock ups, I have even had this problem on my older AMD XP2400+ system and my newer AMD64 system.
Replacing the video cards with a Radeon 9200 eliminated the Xorg lock ups.
The error is defently cuased by something in the AGP art module built into the kernel. Research into this problem seems to point that replacing the standard AGP art module in the kernel with the nvAGP art module fixes the issue. I have not yet confirmed this my self but it seems to be a good place to start looking.

Cheers....

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.