Hmm, the CPU#0 stuck bits make this sound like perhaps a kernel issue,
but maybe -fglrx triggers it.
We have a newer fglrx in Hardy - would you mind re-testing and see if
the issue goes away? If not, could you attach a new Xorg.0.log and full
dmesg output?
** Changed in: linux-restricted-modules
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Sourcepackagename: xorg => linux-restricted-modules-2.6.24
--
System lockups when starting gdm with fglrx
https://bugs.launchpad.net/bugs/202244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: xorg (Ubuntu)
Sourcepackagename: None => xorg
--
System lockups when starting gdm with fglrx
https://bugs.launchpad.net/bugs/202244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
In kernel boot, fglrx says this:
[ 43.970529] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies,.
[ 44.122004] [fglrx] Maximum main memory to use for locked dma buffers: 1887 .
[ 44.129757] [fglrx] ASYNCIO init succeed!
[ 44.134040] [fglrx]
** Attachment added: "Xorg.0.log_fglrx_hang"
http://launchpadlibrarian.net/12673022/Xorg.0.log_fglrx_hang
--
System lockups when starting gdm with fglrx
https://bugs.launchpad.net/bugs/202244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
By the way: My system is a AMD64 3200+ with 2GB of ram and 2x160 gb hdd
(raid) + 1x160 gb. A Powercolor Radeon HD3850 512mb AGP is serving for
graphics.
--
System lockups when starting gdm with fglrx
https://bugs.launchpad.net/bugs/202244
You received this bug notification because you are a membe
