Do you still have this issue with the latest release of Ubuntu ?
** Changed in: linux-source-2.6.17 (Ubuntu)
Importance: Undecided = High
Status: Unconfirmed = Needs Info
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://bugs.launchpad.net/bugs/66500
You received this
Feisty boots fine on a Core2 machine. It's only Edgy and Dapper (and
probably earlier) that are completely broken.
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://bugs.launchpad.net/bugs/66500
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, I'm marking this as fixed. Thanks for answering.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Needs Info = Fix Released
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://bugs.launchpad.net/bugs/66500
You received this bug notification because you are a member
De-assigning from X, as per the bug reporter
** Changed in: xorg-server (Ubuntu)
Status: Unconfirmed = Rejected
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://bugs.launchpad.net/bugs/66500
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: Ubuntu
Sourcepackagename: None = linux-source-2.6.17
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
ACPI problem can be worked around by also using no_timer_check. I have checked
newer kernels (2.6.18 and 2.6.19-rc6) and none of those seems to be affected.
I'd recommend either back-porting the relevant patch or adding notsc
no_timer_check to the default boot options (is that possible?). From
Turns out the notsc kernel option solves the strange X problems. Machine
still crashes on any ACPI event though.
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It doesn't seem like it's an X server bug, please stop assigning it that
way.
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: xorg-server = None
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
Some additional info:
Dapper still crashes after a while. The difference with Edgy is that Dapper is
actually behaving normally before it crashes. I tried the Dapper kernel on
Edgy, and it works better -- about the same as normal Dapper -- so it's
probably a kernel bug. I also tried FC6 (2.6.18
** Changed in: Ubuntu
Sourcepackagename: None = xorg-server
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I confirm that the final release of Edgy for AMD64 is still totally
unusable on my machine. On the other hand, the 32-bit version doesn't
have any of these problems (have been running it for one week).
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
Unsure which package
** Changed in: xorg (Ubuntu)
Sourcepackagename: xorg = None
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Just summarising the info I have so far. I no longer think it's an X.Org bug.
It *looks* like it could be a kernel problem because it affects many things.
The result is that Edgy (beta and RC) is totally unusable on my machine,
crashing/hanging after a few minutes. Other than the crashes,
I have done some experiments with BIOS settings. Basically, the problem
seems to disappear when I disable the second core. If any Ubuntu
developer is interested in investigating the bug, please let me know as
soon as possible because I'll otherwise be reformatting the partition as
soon as FC6 is
Sorry, the problem doesn't disappear when I disable the second core, it
just takes 20 minutes for the machine to crash instead of 1-2 minutes.
Oh, and BTW the strange info in /proc/cpuinfo was simply due to cpufreq
changing the CPU frequency.
--
Bug on amd64 makes X server unusable in Edgy
15 matches
Mail list logo
