Fallo en el kernel 2.6.38
Hola,
Sabeis a que puede ser debido el mensaje de fallo en el kernel
2.6.38-5-bpo que os indico a continuación:
Kernel failure message 1:
------------[ cut here ]------------
WARNING: at /build/buildd-linux-2.6_2.6.38-5~bpo60+1-i386-B7LqDK/linux-2.6-2.6.38/debian/build/source_i386_none/drivers/gpu/drm/radeon/radeon_fence.c:248
radeon_fence_wait+0x251/0x2d7 [radeon]()
Hardware name: iMac5,1
GPU lockup (waiting for 0x0000083B last fence id 0x00000836)
Modules linked in: hid_magicmouse nls_utf8 isofs nls_cp437 udf vfat
fat hidp acpi_cpufreq mperf cpufreq_conservative cpufreq_powersave
cpufreq_userspace cpufreq_stats parport_pc ppdev lp parport sco bridge
stp bnep rfcomm l2cap nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs
binfmt_misc fuse ssb mmc_core pcmcia pcmcia_core loop firewire_sbp2
snd_hda_codec_idt snd_hda_intel btusb bluetooth rfkill radeon
snd_hda_codec snd_hwdep snd_pcm ttm snd_seq snd_timer drm_kms_helper
snd_seq_device drm i2c_algo_bit applesmc power_supply snd
input_polldev button processor video soundcore snd_page_alloc i2c_i801
rng_core i2c_core isight_firmware ndiswrapper(O) pcspkr tpm_tis tpm
tpm_bios thermal_sys hid_apple evdev usb_storage uas usbhid hid ext4
mbcache jbd2 crc16 sg sr_mod cdrom sd_mod crc_t10dif ata_generic
uhci_hcd ata_piix libata ehci_hcd scsi_mod usbcore firewire_ohci
firewire_core sky2 crc_itu_t nls_base [last unloaded: scsi_wait_scan]
Pid: 1340, comm: Xorg Tainted: P W O 2.6.38-bpo.2-686 #1
Call Trace:
[<c102fa51>] ? warn_slowpath_common+0x6a/0x7b
[<f8523b4d>] ? radeon_fence_wait+0x251/0x2d7 [radeon]
[<c102fac8>] ? warn_slowpath_fmt+0x28/0x2c
[<f8523b4d>] ? radeon_fence_wait+0x251/0x2d7 [radeon]
[<c1044d66>] ? autoremove_wake_function+0x0/0x29
[<f82844bf>] ? ttm_bo_wait+0xad/0x135 [ttm]
[<f853505d>] ? radeon_bo_wait+0x5e/0x7c [radeon]
[<f85350a2>] ? radeon_gem_wait_idle_ioctl+0x27/0x50 [radeon]
[<f82affa4>] ? drm_ioctl+0x224/0x2d5 [drm]
[<f853507b>] ? radeon_gem_wait_idle_ioctl+0x0/0x50 [radeon]
[<c10a3b97>] ? handle_pte_fault+0x2c5/0x80f
[<c11458f8>] ? prio_tree_insert+0x150/0x1cc
[<f82afd80>] ? drm_ioctl+0x0/0x2d5 [drm]
[<c10c8fb4>] ? do_vfs_ioctl+0x494/0x4df
[<c10a7483>] ? mmap_region+0x328/0x3fb
[<c10c9043>] ? sys_ioctl+0x44/0x64
[<c1002f1f>] ? sysenter_do_call+0x12/0x28
---[ end trace 4d111c5bd88900e9 ]---
Lo cierto es que la actualización a kernel 3.1.- pae me está trayendo
mas problemas que ni la porra, por eso mantengo el 2.6.38, pero
resulta que ahora este me empieza a dar también.
Un saludo
--
Octavio Ávalos
Reply to: