[Pkg-fglrx-devel] Bug#554847: Bug#554847: Hopefully the correct logs now.
Patrick Matthäi
pmatthaei at debian.org
Wed Nov 25 17:49:34 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Friedrich Delgado Friedrichs schrieb:
> Ok, I have more information for you.
>
> The most relevant part first:
>
> The system locks up quickly after starting X. In fact it's so quickly,
> that there were no changes on a filesystem that's mounted
> asynchronously.
Your mtrr from Linux is crashing. fglrx uses them:
Nov 24 21:50:35 abrasax kernel: [ 0.000000] Call Trace:
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dadb>] ?
generic_get_mtrr+0xbf/0xf9
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dadb>] ?
generic_get_mtrr+0xbf/0xf9
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff80242373>] ?
warn_slowpath_common+0x77/0xa3
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff802423fb>] ?
warn_slowpath_fmt+0x51/0x59
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff804b5a23>] ?
_spin_unlock_irqrestore+0xd/0xe
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dbe7>] ?
mtrr_wrmsr+0x1c/0x49
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021ddec>] ?
get_fixed_ranges+0x71/0x98
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dbe7>] ?
mtrr_wrmsr+0x1c/0x49
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dcab>] ?
prepare_set+0x97/0x9d
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dd04>] ?
post_set+0x53/0x60
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff80655f8b>] ?
get_mtrr_state+0x2eb/0x2f6
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8021dadb>] ?
generic_get_mtrr+0xbf/0xf9
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff804b3a4c>] ?
printk+0x4e/0x5a
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff80656b61>] ?
mtrr_trim_uncached_memory+0x91/0x311
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff80655afb>] ?
mtrr_bp_init+0x1b0/0x1d3
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8065fc35>] ?
early_gart_iommu_check+0x9b/0x287
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff80652870>] ?
setup_arch+0x41f/0x95b
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8066776a>] ?
cgroup_init_subsys+0x10d/0x116
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8064e140>] ?
early_idt_handler+0x0/0x71
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8064e96b>] ?
start_kernel+0x83/0x386
Nov 24 21:50:35 abrasax kernel: [ 0.000000] [<ffffffff8064e3b7>] ?
x86_64_start_kernel+0xf9/0x106
Nov 24 21:50:35 abrasax kernel: [ 0.000000] ---[ end trace
4eaa2a86a8e2da22 ]---
Kernel developers do not like it if non-free modules are linked in, so
that's bad, but it looks as fglrx is not the bad boy here.
May you retest it with 2.6.31?
- --
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
E-Mail: pmatthaei at debian.org
patrick at linux-dev.org
Comment:
Always if we think we are right,
we were maybe wrong.
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAksNbi4ACgkQ2XA5inpabMc3+QCaAvJT+M0guIP4I4KL1wix+ala
WygAn1qPav8xxj3hyctQlVpIS4JHbm2W
=ex45
-----END PGP SIGNATURE-----
More information about the Pkg-fglrx-devel
mailing list