10de:0ca3 (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed

Bug #1077616 reported by itsjustarumour
120
This bug affects 26 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Random hard locks on fresh installs of Ubuntu 12.10 (64 bit), requiring hard reboot. Keyboard is unresponsive, and unable to Ctrl+Alt+F5 etc. This happens with any Desktop environment (GNOME, Cinnamon, KDE). Using NVidia GT240 with NVidia binary blob. This appears to be no pattern to when this happens - can be using any application. Happens several times per day.

With Nouveau my system usually freezes within a couple of minutes of logging in.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.51 Tue Sep 18 17:16:56 PDT 2012
 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Nov 11 11:38:46 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current-updates, 304.51, 3.5.0-16-generic, x86_64: installed
 nvidia-current-updates, 304.51, 3.5.0-17-generic, x86_64: installed
 nvidia-current-updates, 304.51, 3.5.0-18-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: CardExpert Technology Device [10b0:0401]
InstallationDate: Installed on 2012-10-01 (40 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120930)
MachineType: System manufacturer P5Q3 DELUXE
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=227be926-89cc-48ce-ac13-7a10a38896b3 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q3 DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1702:bd12/11/2008:svnSystemmanufacturer:pnP5Q3DELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q3 DELUXE
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

@ Christopher - I have subscribed you as you suggested.

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

Heres a couple more Xorg.0.log.old files from two other times I got this crash. I enclosed them as they contain slightly different lines at the end which might help further.

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

Just by way of a summary, this seems to be the crucial bit in the Xorg.0.log.old file when I see this bug:

[ 350.227] (II) XKB: reuse xkmfile /var/lib/xkb/server-D7D71B388B2C7FE139492B8952A9E555752EC018.xkm
[ 4184.940] (II) XKB: reuse xkmfile /var/lib/xkb/server-D7D71B388B2C7FE139492B8952A9E555752EC018.xkm
[ 6116.466] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00008500, 0x0000d1bc)
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f463752bac6]
(EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7f463750ceab]
(EE) 2: /usr/bin/X (0x7f4637383000+0x6a492) [0x7f46373ed492]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f46305d4000+0x5f34) [0x7f46305d9f34]
(EE) 4: /usr/bin/X (0x7f4637383000+0x936c7) [0x7f46374166c7]
(EE) 5: /usr/bin/X (0x7f4637383000+0xbce38) [0x7f463743fe38]
(EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f46366a9000+0xfcb0) [0x7f46366b8cb0]
(EE) 7: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f4630c9e000+0x8ebed) [0x7f4630d2cbed]
(EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f4630c9e000+0x8fb44) [0x7f4630d2db44]
(EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f4630c9e000+0x10832b) [0x7f4630da632b]
(EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f4630c9e000+0xcacc2) [0x7f4630d68cc2]
(EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f4630c9e000+0x59757c) [0x7f463123557c]
(EE) 12: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f4630c9e000+0x5651c9) [0x7f46312031c9]
(EE) 13: /usr/bin/X (BlockHandler+0x44) [0x7f46373dcbf4]
(EE) 14: /usr/bin/X (WaitForSomething+0x114) [0x7f4637528e74]
(EE) 15: /usr/bin/X (0x7f4637383000+0x557a1) [0x7f46373d87a1]
(EE) 16: /usr/bin/X (0x7f4637383000+0x4456a) [0x7f46373c756a]
(EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f463532e76d]
(EE) 18: /usr/bin/X (0x7f4637383000+0x448ad) [0x7f46373c78ad]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
[ 6123.466] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00008500, 0x0000d1bc)
[ 6123.466] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 6123.467] [mi] EQ processing has resumed after 57 dropped events.
[ 6123.467] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.

bugbot (bugbot)
affects: xorg (Ubuntu) → nvidia-graphics-drivers (Ubuntu)
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

Still getting this same problem with the experimental NVidia driver (310.14-0ubuntu2) from the Ubuntu repository.

Revision history for this message
penalvch (penalvch) wrote :

itsjustarumour, this crash is reproducible with all of the following drivers available correct:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-experimental-310

As well, is this reproducible using nouveau?

summary: - (EE) [mi] EQ overflowing. Additional events will be discarded until
- existing events are processed
+ 10de:0ca3 (EE) [mi] EQ overflowing. Additional events will be discarded
+ until existing events are processed
Changed in nvidia-graphics-drivers (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
rinaldo (rinaldo-forte) wrote :

using nouveau this crash is not repoducible.
thank you

Revision history for this message
penalvch (penalvch) wrote :

rinaldo, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org team (maintainers of nvidia-graphics-drivers), Ubuntu Bug Control team, and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

@Christopher M. Penalver (penalvch) - apologies for the delay in replying. I can confirm that I'm still seeing this bug, and I've experienced it with all three of the NVidia drivers that you refer to. Unfortunately I can't say of its a problem or not with the Nouveau driver, as Nouveau doesn't work well with my graphics card (GT240) - with Nouveau my system usually freezes within a couple of minutes of logging in due to a completely separate problem, so it may be that with Nouveau there just isn't enough time for this bug to manifest itself...

Revision history for this message
penalvch (penalvch) wrote :

itsjustarumour, thank you for your response. Could you please test for this in Raring via http://cdimage.ubuntu.com/daily-live/current/ ? Please also comment if nouveau is usable via Raring.

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

@Christopher M. Penalver (penalvch) - unfortunately due to current work and studying pressures, and the fact this is my production/work machine, I won't have time to do that. Can anyone else subscribed to this thread, perhaps someone who has already downloaded and installed the Raring Alpha, offer some help?

Changed in nvidia-graphics-drivers (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

@Christopher M. Penalver (penalvch) - Hi, OK, I've now had chance to set up Raring 13.04.

I can confirm that this bug still exists on the latest Raring 13.04 Alpha daily build (64 bit), with NVidia drivers.

(From enclosed Xorg.conf file):

(EE) [mi] EQ overflow continuing. 400 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f19d96cff46]
(EE) 1: /usr/bin/X (0x7f19d9527000+0x6a492) [0x7f19d9591492]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f19d255d000+0x5f34) [0x7f19d2562f34]
(EE) 3: /usr/bin/X (0x7f19d9527000+0x936f7) [0x7f19d95ba6f7]
(EE) 4: /usr/bin/X (0x7f19d9527000+0xbce68) [0x7f19d95e3e68]
(EE) 5: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f19d884d000+0xfbd0) [0x7f19d885cbd0]
(EE) 6: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f19d2bf4000+0x7f90b) [0x7f19d2c7390b]
(EE) 7: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f19d2bf4000+0x81245) [0x7f19d2c75245]
(EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f19d2bf4000+0xf7833) [0x7f19d2ceb833]
(EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f19d2bf4000+0x54baa5) [0x7f19d313faa5]
(EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f19d2bf4000+0x54c738) [0x7f19d3140738]
(EE) 11: /usr/bin/X (0x7f19d9527000+0x133ccd) [0x7f19d965accd]
(EE) 12: /usr/bin/X (0x7f19d9527000+0x1239c8) [0x7f19d964a9c8]
(EE) 13: /usr/bin/X (miCompositeRects+0x8a) [0x7f19d964aaca]
(EE) 14: /usr/bin/X (0x7f19d9527000+0x12b7e5) [0x7f19d96527e5]
(EE) 15: /usr/bin/X (0x7f19d9527000+0x55b71) [0x7f19d957cb71]
(EE) 16: /usr/bin/X (0x7f19d9527000+0x4465a) [0x7f19d956b65a]
(EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f19d76b8ea5]
(EE) 18: /usr/bin/X (0x7f19d9527000+0x449a1) [0x7f19d956b9a1]
(EE)

Revision history for this message
penalvch (penalvch) wrote :

itsjustarumour, thank you for testing Raring with the nvidia-graphics-drivers. Did nouveau provide a WORKAROUND for you?

tags: added: raring
Changed in nvidia-graphics-drivers (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

@Christopher M Penalver - hi, I've been trying out the latest daily Raring 13.04 build with the Nouveau driver. As with all five previous versions of Ubuntu I've had installed on this machine, it makes my system rather unstable (using NVidia GT215/GT240 graphics card btw) resulting in hard reboots being required within minutes of loading the Desktop.

Whether this is related to the the bug using the NVidia binary blob I can't say, as I'm not seeing much in the log files that means anything to me. The "end-user experience" however is identical - the screen locks up, keyboard and mouse become unresponsive, I (usually) can't ctrl+alt+F5 etc, meaning I have to do a cold reboot via the on/off button.

The only clues I can see right now are in the syslog file - I've attached the latest example for this crash.

In this case, my machine was on for 19 minutes before the crash. I believe things started to go wrong at 00:58:19, and then at 00:58:51 I get:

"Feb 10 00:58:51 COOLERMASTER kernel: [ 1506.331437] nouveau E[ DRM] GPU lockup - switching to software fbcon"

Unfortunately, I can't really offer any more than that at this stage...

Revision history for this message
penalvch (penalvch) wrote :

itsjustarumour, thank you for testing nouveau in Raring. Did this problem not occur in a release prior to Quantal?

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

@Christopher M Penalver - no, the bug as reported on this same machine with same hardware did not exist in any releases prior to Quantal (its had everything installed on it from Lucid 10.04 onwards, which all worked fine before Quantal).

penalvch (penalvch)
tags: added: regression-release
Changed in nvidia-graphics-drivers (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
Jean-Paul Argudo (jean-paul) wrote :

Hi there,

Suffered this bug too for MONTHS now.

I found something that allowed to me to avoid a DAILY crash + hard reboot as described before here.

First, I upgraded my X.org to:

$ X -version

X.Org X Server 1.13.1.901 (1.13.2 RC 1)
Release Date: 2013-01-03
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-32-xen x86_64 Ubuntu
Current Operating System: Linux deiphobe 3.7.0-7-generic #15-Ubuntu SMP Sat Dec 15 16:34:25 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.7.0-7-generic root=/dev/mapper/deiphobe-root ro quiet splash
Build Date: 04 January 2013 11:17:34AM
xorg-server 2:1.13.1.901+git20130104+server-1.13-branch.3a8c618a-0ubuntu0ricotz~quantal (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.28.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.

TO have this I subscribed to the "xorg-edgers-ppa-quantal" ppa:

$ cat /etc/apt/sources.list.d/xorg-edgers-ppa-quantal.list
deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu quantal main
deb-src http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu quantal main

I also installed FROM this repository version 313 :
$ dpkg -l | grep nvidia
ii libkwinnvidiahack4 4:4.9.4-0ubuntu0.2 amd64 library used by nvidia cards for the KDE window manager
ii nvidia-313 313.18-0ubuntu1~xedgers~quantal2 amd64 NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-settings-313 313.18-0ubuntu1~xedgers~quantal1 amd64 Tool for configuring the NVIDIA graphics driver

(I was using the .sh stuff downloaded directly from nvidia.com, including betas and such.....).

I also had updates of the flash stuf in my firefox and.

TADAAA just ONE crash in 2 weeks now... Pfewwww

I read somewhere our bug could be related to VDPAU in older X.org :-/ (unsure...)

But now, no more blue man problem in youtube videos thanks to this, and without any mms.cfg hack:

$ cat /etc/adobe/mms.cfg
#EnableLinuxHWVideoDecode=1
#OverrideGPUValidation=true

(all commented)....

I suggest people with this same problem do the same thing as me and test...

AND the one crash I had "just" killed my X and then restarted it... Like I did to have my problem solved before (ssh to the crashed 100% cpu X.org on my station, kill -9 X, etc....)

hope this helps! !

PS: I have GTX 560 Ti x 2 in SLI mode / Xinerama on 3 24" screens / kubuntu 12.10

Revision history for this message
Pete Eby (relative-prime) wrote :

As a note, over in OpenSuse 12.2 land I'm seeing this same issue, with this same card (GT240, device ID 10de:0ca3)

https://forums.opensuse.org/english/get-technical-help-here/applications/480831-xorg-high-cpu-usage-sluggish-performance-fresh-install-4.html

Sometimes I see the EQ overflow errors in Xorg log, but not other times.

Looked for a newer vbios for the GT240, but only found the same version I had

http://www.techpowerup.com/vgabios/64154/EVGA.GT240.512.091114.html

Revision history for this message
Jean-Paul Argudo (jean-paul) wrote :

Hi there,

I think I talked too fast here... I have this morning another crash, like before: X frozen, the mouse can hardly survive in one of the 3 screens I have in xinerama, but nothing more...

Had to ssh to the box and kill -9 the X process to recover my station.

I attach the Xorg.0.20130213.log here

Revision history for this message
penalvch (penalvch) wrote :

Jean-Paul Argudo, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org team , Ubuntu Bug Control team, and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message
Bumblebeebat (bumblebeebat) wrote :

This bug affects me too. I can only play about 5 or 10 minutes of Bastion (via steam) before the whole computer freezes. A very very important bug to fix considering the possible influx of new users interested in trying steam. This bug makes the system seem very unstable and down right un-usable.

Thanks for looking into this.

Revision history for this message
penalvch (penalvch) wrote :

Bumblebeebat, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org team , Ubuntu Bug Control team, and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

description: updated
penalvch (penalvch)
tags: added: needs-upstream-testing
Revision history for this message
penalvch (penalvch) wrote :

itsjustarumour, could you please test for this in the newest upstream release via http://www.nvidia.com/Download/index.aspx?lang=en-us ?

Changed in nvidia-graphics-drivers (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Incomplete → Expired
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

This bug, or something very similar, has still been happening with the latest Ubuntu-supplied NVidia drivers, although only rarely (previously it was several times per day). I'm currently testing with the newest upstream release as requested by Christopher M Penalver in #26.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Expired → Incomplete
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

OK, sorry but I jumped the gun slightly there. Unfortunately I am *not* testing the lastest upstream NVidia driver on 13.04 as suggested in #26, as it won't install on my system (and yes, I have followed the README instructions exactly from http://uk.download.nvidia.com/XFree86/Linux-x86_64/310.40/README/installdriver.html). I'm not prepared to take any more risks of knackering my system by manually hacking xorg.conf files etc, as this is my ***production machine*** and I need it for getting real work done!

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

OK, managed to get the latest upstream NVidia driver installed on a different machine. I can confirm this bug does still exist in latest Raring 13.04 Beta (64 bit).

Bryce Harrington (bryce)
Changed in nvidia-graphics-drivers (Ubuntu):
status: Incomplete → New
Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

Just confirming that, 2 days before the official release of Ubuntu 13.04 Raring, I'm still getting this bug at least a couple of times every day. 64-bit, fully updated, with any NVidia driver that I try.

(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f4583c57476]
(EE) 1: /usr/bin/X (0x7f4583aa7000+0x6d472) [0x7f4583b14472]
(EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f457c699000+0x5f44) [0x7f457c69ef44]
(EE) 3: /usr/bin/X (0x7f4583aa7000+0x96927) [0x7f4583b3d927]
(EE) 4: /usr/bin/X (0x7f4583aa7000+0xc0328) [0x7f4583b67328]
(EE) 5: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4582baa000+0xfbd0) [0x7f4582bb9bd0]
(EE) 6: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f457cd30000+0x7f9eb) [0x7f457cdaf9eb]
(EE) 7: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f457cd30000+0x80f34) [0x7f457cdb0f34]
(EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f457cd30000+0xf657b) [0x7f457ce2657b]
(EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f457cd30000+0x544cad) [0x7f457d274cad]
(EE) 10: /usr/bin/X (0x7f4583aa7000+0x137bd0) [0x7f4583bdebd0]
(EE) 11: /usr/bin/X (ValidateGC+0x24) [0x7f4583b122c4]
(EE) 12: /usr/bin/X (0x7f4583aa7000+0x12adcc) [0x7f4583bd1dcc]
(EE) 13: /usr/bin/X (miCompositeRects+0x8a) [0x7f4583bd1f7a]
(EE) 14: /usr/bin/X (0x7f4583aa7000+0x132c95) [0x7f4583bd9c95]
(EE) 15: /usr/bin/X (0x7f4583aa7000+0x58ac1) [0x7f4583affac1]
(EE) 16: /usr/bin/X (0x7f4583aa7000+0x4757a) [0x7f4583aee57a]
(EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f45817f7ea5]
(EE) 18: /usr/bin/X (0x7f4583aa7000+0x478c1) [0x7f4583aee8c1]
(EE)
[ 7234.493] [mi] Increasing EQ size to 1024 to prevent dropped events.
[ 7234.493] [mi] EQ processing has resumed after 223 dropped events.
[ 7234.493] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :
Download full text (3.7 KiB)

Updated to 13.04 final today. After rebooting and logging in for the first time, it took 12 minutes for this bug to occur, requiring a hard reboot. Not good.

Heres the relevant bit of the xorg.conf file:

(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f90734fc476]
(EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7f90734dd78b]
(EE) 2: /usr/bin/X (0x7f907334c000+0x6d472) [0x7f90733b9472]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f906bf3e000+0x5f44) [0x7f906bf43f44]
(EE) 4: /usr/bin/X (0x7f907334c000+0x96927) [0x7f90733e2927]
(EE) 5: /usr/bin/X (0x7f907334c000+0xc0328) [0x7f907340c328]
(EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f907244f000+0xfbd0) [0x7f907245ebd0]
(EE) 7: (vdso) (0x7fff529fe000+0x70c) [0x7fff529fe70c]
(EE) 8: (vdso) (__vdso_gettimeofday+0x161) [0x7fff529fed01]
(EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0xf25fe) [0x7f906c6c75fe]
(EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0x811b5) [0x7f906c6561b5]
(EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0xd33cf) [0x7f906c6a83cf]
(EE) 12: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0xce440) [0x7f906c6a3440]
(EE) 13: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0xceb70) [0x7f906c6a3b70]
(EE) 14: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0x80ebb) [0x7f906c655ebb]
(EE) 15: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0xf657b) [0x7f906c6cb57b]
(EE) 16: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f906c5d5000+0x544cad) [0x7f906cb19cad]
(EE) 17: /usr/bin/X (0x7f907334c000+0x137bd0) [0x7f9073483bd0]
(EE) 18: /usr/bin/X (ValidateGC+0x24) [0x7f90733b72c4]
(EE) 19: /usr/bin/X (miCompositeRects+0x19a) [0x7f907347708a]
(EE) 20: /usr/bin/X (0x7f907334c000+0x132c95) [0x7f907347ec95]
(EE) 21: /usr/bin/X (0x7f907334c000+0x58ac1) [0x7f90733a4ac1]
(EE) 22: /usr/bin/X (0x7f907334c000+0x4757a) [0x7f907339357a]
(EE) 23: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f907109cea5]
(EE) 24: /usr/bin/X (0x7f907334c000+0x478c1) [0x7f90733938c1]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
[ 1544.893] (EE) NVIDIA(0): Failed to initialize DMA.
[ 1544.893] (EE) NVIDIA(0): *** Aborting ***
[ 1544.893] (EE) NVIDIA(0): Error recovery failed.
[ 1544.893] (EE) NVIDIA(0): *** Aborting ***
[ 1544.893]
Fatal server error:
[ 1544.893] Failed to recover from error!
[ 1544.893]
[ 1544.893] (EE)
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 1544.893] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1544.893] (EE)
[ 1544.894] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 1544.894] [mi] EQ processing has resumed after 57 dropped events.
[ 1544.894] [mi] This may be caused my a misbehaving driver monopolizing the server's ...

Read more...

penalvch (penalvch)
tags: removed: needs-upstream-testing
tags: added: crash
Revision history for this message
schaefi (info-e) wrote :

Hi
I think I have a very similar bug with a Radeon graphics card:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178846

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
Revision history for this message
Bart (bart-schelstraete) wrote :

I'm having exactly the same problem, but with Intel graphics card
It started to happen after the upgrade to raring.

--
(EE)
(EE) [mi] EQ overflow continuing. 500 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb76dcf79]
(EE) 1: /usr/bin/X (mieqEnqueue+0xf8) [0xb76bb5b8]
(EE) 2: /usr/bin/X (0xb752f000+0x54335) [0xb7583335]
(EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb75c001b]
(EE) 4: /usr/bin/X (xf86PostMotionEvent+0xaa) [0xb75c026a]
(EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb572c000+0x3fa8) [0xb572ffa8]
(EE) 6: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb572c000+0x61c1) [0xb57321c1]
(EE) 7: /usr/bin/X (0xb752f000+0x80121) [0xb75af121]
(EE) 8: /usr/bin/X (0xb752f000+0xac173) [0xb75db173]
(EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb750c400]
(EE) 10: (vdso) (__kernel_vsyscall+0x10) [0xb750c424]
(EE) 11: /lib/i386-linux-gnu/libc.so.6 (ioctl+0x19) [0xb71e90c9]
(EE) 12: /usr/lib/i386-linux-gnu/libdrm.so.2 (drmIoctl+0x34) [0xb73fc9d4]
(EE) 13: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb6e1a000+0x35497) [0xb6e4f497]
(EE) 14: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb6e1a000+0x366af) [0xb6e506af]
(EE) 15: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb6e1a000+0x5f1e2) [0xb6e791e2]
(EE) 16: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb6e1a000+0x72c32) [0xb6e8cc32]
(EE) 17: /usr/bin/X (BlockHandler+0x49) [0xb7571469]
(EE) 18: /usr/bin/X (WaitForSomething+0xfa) [0xb76da14a]
(EE) 19: /usr/bin/X (0xb752f000+0x3ddbe) [0xb756cdbe]
(EE) 20: /usr/bin/X (0xb752f000+0x2b535) [0xb755a535]
(EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb711a935]
(EE) 22: /usr/bin/X (0xb752f000+0x2b909) [0xb755a909]
(EE)
[540369.989] (EE) intel(0): Detected a hung GPU, disabling acceleration.
[540369.989] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg.
[540369.989] [mi] Increasing EQ size to 512 to prevent dropped events.
[540369.989] [mi] EQ processing has resumed after 523 dropped events.
[540369.989] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
--

Revision history for this message
Luís Nabais (luisnabais) wrote :
Download full text (6.2 KiB)

I'm having exactly the same issue, in a HP ProBook 6460b laptop, with Intel HD 3000 integrated graphics.

Here is my xorg log where is the error:

[ 6447.678] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 6447.678] (II) intel(0): switch to mode 1600x900 on crtc 3 (pipe 0)
[ 6447.692] (II) intel(0): EDID vendor "LGD", prod id 596
[ 6447.692] (II) intel(0): Printing DDC gathered Modelines:
[ 6447.692] (II) intel(0): Modeline "1600x900"x0.0 107.80 1600 1648 1680 1920 900 903 908 936 +hsync -vsync (56.1 kHz eP)
[ 6447.916] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 6449.981] (II) config/udev: Adding input device DELL Laser Mouse (/dev/input/event4)
[ 6449.981] (**) DELL Laser Mouse: Applying InputClass "evdev pointer catchall"
[ 6449.981] (II) Using input driver 'evdev' for 'DELL Laser Mouse'
[ 6449.981] (**) DELL Laser Mouse: always reports core events
[ 6449.981] (**) evdev: DELL Laser Mouse: Device: "/dev/input/event4"
[ 6449.981] (--) evdev: DELL Laser Mouse: Vendor 0x461 Product 0x4d51
[ 6449.982] (--) evdev: DELL Laser Mouse: Found 9 mouse buttons
[ 6449.982] (--) evdev: DELL Laser Mouse: Found scroll wheel(s)
[ 6449.982] (--) evdev: DELL Laser Mouse: Found relative axes
[ 6449.982] (--) evdev: DELL Laser Mouse: Found x and y relative axes
[ 6449.982] (II) evdev: DELL Laser Mouse: Configuring as mouse
[ 6449.982] (II) evdev: DELL Laser Mouse: Adding scrollwheel support
[ 6449.982] (**) evdev: DELL Laser Mouse: YAxisMapping: buttons 4 and 5
[ 6449.982] (**) evdev: DELL Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 6449.982] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input17/event4"
[ 6449.982] (II) XINPUT: Adding extended input device "DELL Laser Mouse" (type: MOUSE, id 9)
[ 6449.982] (II) evdev: DELL Laser Mouse: initialized for relative axes.
[ 6449.982] (**) DELL Laser Mouse: (accel) keeping acceleration scheme 1
[ 6449.982] (**) DELL Laser Mouse: (accel) acceleration profile 0
[ 6449.982] (**) DELL Laser Mouse: (accel) acceleration factor: 2.000
[ 6449.982] (**) DELL Laser Mouse: (accel) acceleration threshold: 4
[ 6449.982] (II) config/udev: Adding input device DELL Laser Mouse (/dev/input/mouse0)
[ 6449.982] (II) No input driver specified, ignoring this device.
[ 6449.982] (II) This device may have been added with another device file.
[ 6654.470] (II) intel(0): EDID vendor "LGD", prod id 596
[ 6654.470] (II) intel(0): Printing DDC gathered Modelines:
[ 6654.470] (II) intel(0): Modeline "1600x900"x0.0 107.80 1600 1648 1680 1920 900 903 908 936 +hsync -vsync (56.1 kHz eP)
[ 6654.946] (II) intel(0): switch to mode 1600x900 on crtc 3 (pipe 0)
[ 6654.978] (II) intel(0): switch to mode 1920x1080 on crtc 5 (pipe 1)
[ 6655.169] (II) intel(0): switch to mode 1600x900 on crtc 3 (pipe 0)
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f483ed13476]
(EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7f483ecf478b]
(EE) 2: /usr/bin/X (0x7f483eb63000+0x6d472) [0x7f483ebd0472]
(EE) ...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Bart / Luís Nabais, if you have a bug in Ubuntu, the Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad request you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message
Luís Nabais (luisnabais) wrote :

Christopher M. Penalver, I thought I already sent the bug report, however it seems I didn't. That issue happened again a few minutes ago. After hard resetting the computer again, I reported the bug using ubuntu-bug as you requested.

Thanks a lot

Revision history for this message
itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount) wrote :

So - I reported this bug over 7 months ago, and no sign at all of any progress? And its only ranked as "medium"? Surely it should be at the very minimum marked as "high", or even "critical".

This bug, causing hard reboots to be required mutilple times every single day, creates a Ubuntu system that in the real world is unusable for day-to-day work.

This bug was also reported on the NVidia Developer Forum 3 months ago btw, and it hasn't even been looked at there either.

https://devtalk.nvidia.com/default/topic/537302/both-screens-black-xorg-at-100-cpu-overflow-errors-in-xorg-0-log-nvidia-driver-310-14-quadro-fx/#3821607

The signs for a successful resolution/fix, it seems, are not good.

From my personal experience, NVidia proprietary support for Ubuntu is still unacceptably poor for my graphics card, as it was for my graphics card before that, and the one before that.

Nouveau? Even worse, as it was for my previous graphics card, and the one before that. A totally unusable system, hard locking within around 40 seconds of desktop loading. All bugs reported elsewhere, some going back almost 4 years, not a single one ever addressed or fixed.

After 8 years, and after countless hours, days and sometimes weeks of trying to put something *back* into Ubuntu, its business and its community, with a sense of huge sadness I've finally reached the point where I feel any further effort I put in is effort wasted. I had great hopes for Ubuntu, but I feel I can't live in self-denial any more. Ubuntu, for me at least, has been a failed experiment - and I have now lost all faith that that will ever change.

Ubuntu, it appears, is never going to provide me with a stable operating system that meets my needs. Its quality and reliability are too woefully inadequate compared to its propritary competitors (MS Windows, OSX, Android). It doesn't matter what component is to "blame" for that, the end-user experience is the same - unacceptably poor.

As such, I'm moving to one of Ubuntu's competitors, and its time for to close my Launchpad account.

Revision history for this message
penalvch (penalvch) wrote :
Changed in nvidia-graphics-drivers (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Konstantin (hi-angel-z) wrote :

I don't really know is it bug of nvidia. Sometimes I have the same problem on my radeon(last was a few minutes ago), so it could be Xorg's problem.

Revision history for this message
penalvch (penalvch) wrote :

Constantine, if you have a bug in Ubuntu, the Ubuntu X.Org team, Ubuntu Bug Control, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message
Brenton Fletcher (i-u) wrote :

I am seeing this same bug on an AMD chipset in quantal under heavy CPU load.

Christopher, before you send your obviously automated response, I have just reported this bug (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1210397); I'm sure having many duplicate bug reports that are all the same issue will help greatly to those resolving it</sarcasm>

Christopher, in the 8 months since this issue was reported, you have done nothing except provide semi-automated replies to people. The replies you have given are not in any way targeted or helpful for those attempting to resolve this issue, and additionally your replies make it appear that the bug is actually being triaged and dealt with, where it is obviously not been dealt with in any way.

Your replies have even driven the bug reporter to completely stop using Ubuntu; yet your _only_ response is to mark the bug as Invalid, an action that is itself wrong, as the bug still stands, even if the reporter has deleted their account.

It would have been better if you had made literally no comments or actions on this ticket; then, at least, someone who actually cares about the bug might have become involved.

I know that my account is new, and so I will probably be dismissed out of hand as another troll or clueless noob; the fact that I have been using Ubuntu as my daily OS continually since May 2010, and that I am a professional software developer, and that I care deeply about Ubuntu and it's goals should give some lie to that.

I do not rise to make these sorts of accusations lightly, however in this case I believe they are warranted.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Brenton Fletcher, if you have a bug in Ubuntu, the Ubuntu X.Org team (maintainers of nvidia-graphics-drivers), Ubuntu Bug Control, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org team, Ubuntu Bug Control team, and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Saha (smirta) wrote :

I recreate the same bug with "ubuntu-bug xorg" command. See https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1222791

Revision history for this message
linas (linasvepstas) wrote :

Please also see https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1097178

These Xorg errors seem to be a side-effect of X hanging in uninteruptible sleep, in the kernel: i.e. a nouveau kernel module issue. At least for me. See the bug I just quoted for details.

Revision history for this message
penalvch (penalvch) wrote :

linas, thank you for your comment. Unfortunately, as this bug report is closed, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

To post a comment you must log in.