Xorg crashed with SIGFPE in Phw770_ProgramMemoryTimingParameters() happens when I change the user without logging out the active user

Bug #470444 reported by Accorte
76
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

It is not possible to change the user when another user is still logged in using a gui, terminal sessions are not affected.
I had this bug on Jaunty and still have it on Karmic.
I'm using a ATI HD4890 with a well running fglrx driver.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Nov 2 12:04:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
MachineType: System manufacturer System Product Name
NonfreeKernelModules: fglrx
Package: xserver-xorg-core 2:1.6.4-2ubuntu4 [modified: usr/lib/xorg/modules/extensions/libdri.so usr/lib/xorg/modules/extensions/libglx.so]
ProcCmdLine: root=UUID=258a027a-8976-4f1b-807b-a97136106834 ro quiet splash
ProcCmdline: /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-7vkkOI/database -nolisten tcp
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
Signal: 8
SourcePackage: xorg-server
StacktraceTop:
 Phw770_ProgramMemoryTimingParameters ()
 ?? ()
 PHM_DispatchTable ()
 PHM_SetPowerStateDeferrable ()
 ?? ()
Title: Xorg crashed with SIGFPE in Phw770_ProgramMemoryTimingParameters()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

dmi.bios.date: 06/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78T-E
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.:bvr1604:bd06/05/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
fglrx:
 Nov 2 10:48:48 Shogun kernel: [ 2456.517603] [fglrx:fireglAsyncioIntDisableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to disable interrupt source ff000035
 Nov 2 10:48:48 Shogun kernel: [ 2456.545784] [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to enable interrupt source ff000035
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-generic

Revision history for this message
Accorte (accorte) wrote :
visibility: private → public
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug report is public and visible to everyone but I noticed that it has an attachment named 'CoreDump.gz'. It is possible that this contains sensitive information so I've set it back to private.

visibility: public → private
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #449069, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
Francis De Brabandere (francisdb) wrote :

What happened to the bug of wich this one is a duplicate? We are having the same issue here at work with non x64 hardware. I usually lock the screen in the evening and since 2 days when trying to log in in the morning X is frozen.

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.