Summary: | Kernel lockup when starting second X on MGA G200 | ||
---|---|---|---|
Product: | xorg | Reporter: | Sitsofe Wheeler <sitsofe> |
Component: | Driver/mga | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | high | CC: | dri-devel |
Version: | 7.0.0 | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Sitsofe Wheeler
2006-06-10 03:32:24 UTC
xorg.conf: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=130386 Xorg.0.log from a working X https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=130387 The last message in /var/log/message before the lockup are the following: Jun 2 09:38:02 platinum kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. Jun 2 09:38:02 platinum kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode Jun 2 09:38:02 platinum kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode Jun 2 09:38:02 platinum kernel: [drm] Initialized card for AGP DMA. Jun 2 09:38:14 platinum kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. Jun 2 09:38:14 platinum kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode Jun 2 09:38:14 platinum kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode Jun 2 09:38:14 platinum kernel: [drm] Initialized card for AGP DMA. Jun 2 09:38:58 platinum ntpd[1790]: synchronized to LOCAL(0), stratum 10 Jun 2 09:38:58 platinum ntpd[1790]: kernel time sync disabled 0041 cc'ing dri-devel list on the advice of Mike Harris in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193854 Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. I no longer have access to this hardware (and haven't for years). Resolve INVALID? Let's close this INVALID. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.