On 08/04/2012 11:00 PM, Tobias Gasser wrote: > as you can read, i couldnt'wait... > > --enable-sna made it even worse! > > after little more then 5 minutes, the speaker made a single beep and the > system hung - this time not even the mouse could be moved... > > included you can find the xorg-log and dmesg output. > in the dmesg is a call trace, i thought dmesg is empied after reboot, > but i guess i was wrong... > > thanks > tobias >
Hm. Your kernel seems to be screwed up. Also, one tip. "dmesg" shows kmsg output for currently running kernel. It also gets logged into kern.log, so you will likely find information there. Now, I see this in your dmesg output: vesafb: mode is 1280x1024x32, linelength=5120, pages=0 vesafb: scrolling: redraw vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0 vesafb: framebuffer at 0xc0000000, mapped to 0xf8900000, using 5120k, total 5120k Console: switching to colour frame buffer device 160x64 fb0: VESA VGA frame buffer device This could be one of the problems. I'd disable it. Intel card should be fb0. I don't remember seeing info about your machine. Is it a PC or Laptop? If it is Laptop, which Vendor and Model? Whatever it is, it does not have filled DMI data since kernel shows them as "To be filled by OEM". Lazy bastards. Also, there is kernel panic as soon as udev starts. udevd[1097]: starting version 182 ------------[ cut here ]------------ ------------[ cut here ]------------ WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0xa4/0xd0() Hardware name: To Be Filled By O.E.M. empty IPI mask Modules linked in: Pid: 1127, comm: udevd Not tainted 3.4.7-test #1 Call Trace: [<c1028298>] ? warn_slowpath_common+0x78/0xb0 [<c101b3e4>] ? default_send_IPI_mask_logical+0xa4/0xd0 [<c101b3e4>] ? default_send_IPI_mask_logical+0xa4/0xd0 [<c1028363>] ? warn_slowpath_fmt+0x33/0x40 [<c101b3e4>] ? default_send_IPI_mask_logical+0xa4/0xd0 [<c1019d6d>] ? native_send_call_func_ipi+0x3d/0x60 [<c10622a4>] ? smp_call_function_many+0x174/0x220 [<c10de500>] ? __wait_on_buffer+0x30/0x30 [<c10de500>] ? __wait_on_buffer+0x30/0x30 [<c106237f>] ? on_each_cpu_mask+0x2f/0x60 [<c10dda30>] ? mark_buffer_async_write+0x10/0x10 [<c106242f>] ? on_each_cpu_cond+0x7f/0x90 [<c10de500>] ? __wait_on_buffer+0x30/0x30 [<c10ddf13>] ? invalidate_bh_lrus+0x23/0x30 [<c10e38b5>] ? kill_bdev+0x15/0x30 [<c10e436f>] ? __blkdev_put+0x4f/0x180 [<c1306601>] ? mutex_lock+0x11/0x40 [<c10bc16c>] ? fput+0xec/0x230 [<c10b8756>] ? filp_close+0x46/0x70 [<c10bad8c>] ? sys_read+0x3c/0x70 [<c10b8a94>] ? sys_close+0x54/0x90 [<c1308a94>] ? sysenter_do_call+0x12/0x26 ---[ end trace b8e4d0519b405383 ]--- I am unsure what causes it. There is another further down. microcode: CPU5 sig=0x206a7, pf=0x2, revision=0x14 WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0xa4/0xd0() Hardware name: To Be Filled By O.E.M. empty IPI mask Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek firewire_ohci firewire_core drm_kms_helper ehci_hcd(+) drm usbcore r8169 i2c_algo_bit usb_common crc_itu_t intel_agp(+) sr_mod intel_gtt psmouse 8250_pnp agpgart cdrom microcode(+) serio_raw pcspkr i2c_i801 firmware_class 8250 serial_core rtc_cmos snd_hda_intel snd_hda_codec snd_pcm snd_page_alloc snd_timer snd soundcore evdev Pid: 1128, comm: udevd Tainted: G W 3.4.7-test #1 Call Trace: [<c1028298>] ? warn_slowpath_common+0x78/0xb0 [<c101b3e4>] ? default_send_IPI_mask_logical+0xa4/0xd0 [<c101b3e4>] ? default_send_IPI_mask_logical+0xa4/0xd0 [<c1028363>] ? warn_slowpath_fmt+0x33/0x40 [<c101b3e4>] ? default_send_IPI_mask_logical+0xa4/0xd0 [<c1019d6d>] ? native_send_call_func_ipi+0x3d/0x60 [<c10622a4>] ? smp_call_function_many+0x174/0x220 [<c10de500>] ? __wait_on_buffer+0x30/0x30 [<c10de500>] ? __wait_on_buffer+0x30/0x30 [<c106237f>] ? on_each_cpu_mask+0x2f/0x60 [<c10dda30>] ? mark_buffer_async_write+0x10/0x10 [<c106242f>] ? on_each_cpu_cond+0x7f/0x90 [<c10de500>] ? __wait_on_buffer+0x30/0x30 [<c10ddf13>] ? invalidate_bh_lrus+0x23/0x30 [<c10e38b5>] ? kill_bdev+0x15/0x30 [<c10e436f>] ? __blkdev_put+0x4f/0x180 [<c1306601>] ? mutex_lock+0x11/0x40 [<c10bc16c>] ? fput+0xec/0x230 [<c10b8756>] ? filp_close+0x46/0x70 [<c10bad8c>] ? sys_read+0x3c/0x70 [<c10b8a94>] ? sys_close+0x54/0x90 [<c1308a94>] ? sysenter_do_call+0x12/0x26 ---[ end trace b8e4d0519b405384 ]--- And then nearly at the end, I see this, and I don't know what it means i915 0000:00:02.0: setting latency timer to 64 mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining [drm] MTRR allocation failed. Graphics performance may suffer. There's also something about Vesa, as I mentioned earlier: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver fbcon: inteldrmfb (fb1) is primary device fbcon: Remapping primary device, fb1, to tty 1-63 And after that I see: fb1: inteldrmfb frame buffer device drm: registered panic notifier No ACPI video bus found [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 This could mean buggy BIOS as the hardware might be relatively new. I would check for a BIOS upgrade at (lazy) vendor's site. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
