Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Oct 2015 22:27:05 +0300
From:      Arto Pekkanen <isoa@kapsi.fi>
To:        freebsd-x11@freebsd.org
Subject:   Re: Testing the new i915 driver
Message-ID:  <24fa3cba31bb8ef5594bde422bce5d09@kapsi.fi>
In-Reply-To: <CAPyFy2D=N=TdoQHn=rTd9ThXdxvLCWS2BcN-HTfw9vb4y9SDag@mail.gmail.com>
References:  <5615A42C.3080908@FreeBSD.org> <CAPyFy2D=N=TdoQHn=rTd9ThXdxvLCWS2BcN-HTfw9vb4y9SDag@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I get the same error as you, and have reported this earlier. I also 
included text core dump as attachment in the message.

How did you manage to paste the dmesg text here? Is there are way to 
attach dmesg on the generated core dump? After my laptop panicked, the 
only thing I could do was take a shot of the dmesg with a camera.

Ed Maste kirjoitti 13.10.2015 22:18:
> On 7 October 2015 at 23:01, Jean-Sébastien Pédron 
> <dumbbell@freebsd.org> wrote:
>> 
>> Hi!
>> 
>> Some people asked for details about how to test the update of the i915
>> kernel driver. The current status and instructions are now on the
>> dedicated wiki article:
>> https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linux%203.8
> 
> On my Sandy Bridge laptop I get the following panic when loading the 
> module:
> 
> info: [drm] Initialized drm 1.1.0 20060810
> drmn0: <Intel SandyBridge (M)> on vgapci0
> info: [drm] Memory usable by graphics device = 2048M
> info: [drm] MTRR allocation failed.  Graphics performance may suffer.
> iicbus0: <Philips I2C bus> on iicbb0 addr 0xff
> iic0: <I2C generic I/O> on iicbus0
> iic1: <I2C generic I/O> on iicbus1
> iicbus2: <Philips I2C bus> on iicbb1 addr 0x0
> iic2: <I2C generic I/O> on iicbus2
> iic3: <I2C generic I/O> on iicbus3
> iicbus4: <Philips I2C bus> on iicbb2 addr 0x0
> iic4: <I2C generic I/O> on iicbus4
> iic5: <I2C generic I/O> on iicbus5
> iicbus6: <Philips I2C bus> on iicbb3 addr 0x0
> iic6: <I2C generic I/O> on iicbus6
> iic7: <I2C generic I/O> on iicbus7
> iicbus8: <Philips I2C bus> on iicbb4 addr 0x0
> iic8: <I2C generic I/O> on iicbus8
> iic9: <I2C generic I/O> on iicbus9
> iicbus10: <Philips I2C bus> on iicbb5 addr 0x0
> iic10: <I2C generic I/O> on iicbus10
> iic11: <I2C generic I/O> on iicbus11
> info: [drm] MSI enabled 1 message(s)
> info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> info: [drm] Driver supports precise vblank timestamp query.
> info: [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit
> banging on pin 5
> 
> 
> Fatal trap 9: general protection fault while in kernel mode
> cpuid = 1; apic id = 01
> instruction pointer     = 0x20:0xffffffff80a52ad0
> stack pointer           = 0x28:0xfffffe011a7490c0
> frame pointer           = 0x28:0xfffffe011a7490e0
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 694 (kldload)
> [ thread pid 694 tid 100099 ]
> Stopped at      device_delete_child+0x10:       movq    0x30(%rbx),%rsi
> db> bt
> Tracing pid 694 tid 100099 td 0xfffff8000ac3b000
> device_delete_child() at device_delete_child+0x10/frame 
> 0xfffffe011a7490e0
> device_delete_child() at device_delete_child+0x21/frame 
> 0xfffffe011a749100
> intel_sdvo_ddc_proxy_detach() at
> intel_sdvo_ddc_proxy_detach+0x2b/frame 0xfffffe011a749120
> device_detach() at device_detach+0x6f/frame 0xfffffe011a749140
> device_delete_child() at device_delete_child+0x2f/frame 
> 0xfffffe011a749160
> intel_sdvo_init() at intel_sdvo_init+0x848/frame 0xfffffe011a749240
> intel_modeset_init() at intel_modeset_init+0x96a/frame 
> 0xfffffe011a749290
> i915_driver_load() at i915_driver_load+0xca5/frame 0xfffffe011a749410
> drm_get_pci_dev() at drm_get_pci_dev+0x436/frame 0xfffffe011a749470
> drm_attach_helper() at drm_attach_helper+0x13f/frame 0xfffffe011a7494c0
> i915_attach() at i915_attach+0x53/frame 0xfffffe011a7494d0
> device_attach() at device_attach+0x41d/frame 0xfffffe011a749530
> bus_generic_driver_added() at bus_generic_driver_added+0x96/frame
> 0xfffffe011a749550
> devclass_driver_added() at devclass_driver_added+0x7d/frame 
> 0xfffffe011a749590
> devclass_add_driver() at devclass_add_driver+0x144/frame 
> 0xfffffe011a7495d0
> module_register_init() at module_register_init+0xb0/frame 
> 0xfffffe011a749600
> linker_load_module() at linker_load_module+0xc8e/frame 
> 0xfffffe011a749930
> kern_kldload() at kern_kldload+0xa7/frame 0xfffffe011a749970
> sys_kldload() at sys_kldload+0x5b/frame 0xfffffe011a7499a0
> amd64_syscall() at amd64_syscall+0x2de/frame 0xfffffe011a749ab0
> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe011a749ab0
> --- syscall (304, FreeBSD ELF64, sys_kldload), rip = 0x80086b20a, rsp
> = 0x7fffffffe678, rbp = 0x7fffffffeba0 ---
> _______________________________________________
> freebsd-x11@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org"

-- 
Arto Pekkanen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24fa3cba31bb8ef5594bde422bce5d09>