I915: OOPSes on linux-3.14-rc7
On Fri, Mar 21, 2014 at 4:11 PM, Daniel Vetter wrote:
> On Fri, Mar 21, 2014 at 12:26:51PM +0100, Peter Senna Tschudin wrote:
>> On Thu, Mar 20, 2014 at 10:17 PM, Daniel Vetter wrote:
>> > On Thu, Mar 20, 2014 at 05:56:20PM +0100, Peter Senna Tschudin wrote:
>> >> When Fedora updated the Kernel package from 3.12 to 3.13 my notebook
>> >> stopped booting (Kernel freezes) when a 2560 x 1440 high res monitor
>> >> is attached. I have tried using 3.13.6 from kernel.org and the problem
>> >> persists. The problem can be partially solved by passing nomodeset to
>> >> Kernel which will make the Kernel to boot, but the screens never comes
>> >> to life. When using 3.14-rc7 it boots again, the screen works, but
>> >> with some oops messages.
>> >>
>> >> How can I help fixing this issue?
>> >>
>> >> I've reported te bug at:
>> >> https://bugzilla.redhat.com/show_bug.cgi?id=1072557
>> >
>> > For the oops message (well it's just a WARNING, a real oops would kill
>> > your driver for real) please file a bug report on bugs.freedesktop.org
>> > against dri -> drm (intel).
>> >
>> > The information we need is the full dmesg fore the entire boot when
>> > enabling drm.debug=0xe on the kernel cmdline.
>> It is attached.
>>
>> >
>> > For the boot hang you've reported on the redhat bz if you want to move it
>> > forward I suggest to do a reverse bisect betwen 3.13 and 3.14-rc7 to
>> > figure out which bug _fixed_ your problem and then tell me that. I'll
>> > submit it for backporting to stable kernels. Google should find you some
>> > nice howtos for reverse bisecting kerneels.
>> Thank you. I'll do that.
>
> It's an issue with our fastboot clock readout code. Please apply the below
> patch and add an updated dmesg (again with drm.debug=0xe) to your bug
> report.
The dmesg file is attached. Should I open a bug report at
bugs.freedesktop.org for this warning issue?
> -Daniel
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 7be5984431bb..3c0f8f095a6b 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -450,6 +450,8 @@ static void i9xx_clock(int refclk, intel_clock_t *clock)
> {
> clock->m = i9xx_dpll_compute_m(clock);
> clock->p = clock->p1 * clock->p2;
> + printk("p1 = %u, p2 = %u, n = %u\n", clock->p1, clock->p2,
> + clock->n);
> if (WARN_ON(clock->n + 2 == 0 || clock->p == 0))
> return;
> clock->vco = DIV_ROUND_CLOSEST(refclk * clock->m, clock->n + 2);
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Peter
-- next part --
A non-text attachment was scrubbed...
Name: dmesg.gz
Type: application/x-gzip
Size: 73573 bytes
Desc: not available
URL:
I915: OOPSes on linux-3.14-rc7
On Fri, Mar 21, 2014 at 12:26:51PM +0100, Peter Senna Tschudin wrote:
> On Thu, Mar 20, 2014 at 10:17 PM, Daniel Vetter wrote:
> > On Thu, Mar 20, 2014 at 05:56:20PM +0100, Peter Senna Tschudin wrote:
> >> When Fedora updated the Kernel package from 3.12 to 3.13 my notebook
> >> stopped booting (Kernel freezes) when a 2560 x 1440 high res monitor
> >> is attached. I have tried using 3.13.6 from kernel.org and the problem
> >> persists. The problem can be partially solved by passing nomodeset to
> >> Kernel which will make the Kernel to boot, but the screens never comes
> >> to life. When using 3.14-rc7 it boots again, the screen works, but
> >> with some oops messages.
> >>
> >> How can I help fixing this issue?
> >>
> >> I've reported te bug at:
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1072557
> >
> > For the oops message (well it's just a WARNING, a real oops would kill
> > your driver for real) please file a bug report on bugs.freedesktop.org
> > against dri -> drm (intel).
> >
> > The information we need is the full dmesg fore the entire boot when
> > enabling drm.debug=0xe on the kernel cmdline.
> It is attached.
>
> >
> > For the boot hang you've reported on the redhat bz if you want to move it
> > forward I suggest to do a reverse bisect betwen 3.13 and 3.14-rc7 to
> > figure out which bug _fixed_ your problem and then tell me that. I'll
> > submit it for backporting to stable kernels. Google should find you some
> > nice howtos for reverse bisecting kerneels.
> Thank you. I'll do that.
It's an issue with our fastboot clock readout code. Please apply the below
patch and add an updated dmesg (again with drm.debug=0xe) to your bug
report.
-Daniel
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 7be5984431bb..3c0f8f095a6b 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -450,6 +450,8 @@ static void i9xx_clock(int refclk, intel_clock_t *clock)
{
clock->m = i9xx_dpll_compute_m(clock);
clock->p = clock->p1 * clock->p2;
+ printk("p1 = %u, p2 = %u, n = %u\n", clock->p1, clock->p2,
+ clock->n);
if (WARN_ON(clock->n + 2 == 0 || clock->p == 0))
return;
clock->vco = DIV_ROUND_CLOSEST(refclk * clock->m, clock->n + 2);
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
I915: OOPSes on linux-3.14-rc7
On Thu, Mar 20, 2014 at 10:17 PM, Daniel Vetter wrote: > On Thu, Mar 20, 2014 at 05:56:20PM +0100, Peter Senna Tschudin wrote: >> When Fedora updated the Kernel package from 3.12 to 3.13 my notebook >> stopped booting (Kernel freezes) when a 2560 x 1440 high res monitor >> is attached. I have tried using 3.13.6 from kernel.org and the problem >> persists. The problem can be partially solved by passing nomodeset to >> Kernel which will make the Kernel to boot, but the screens never comes >> to life. When using 3.14-rc7 it boots again, the screen works, but >> with some oops messages. >> >> How can I help fixing this issue? >> >> I've reported te bug at: >> https://bugzilla.redhat.com/show_bug.cgi?id=1072557 > > For the oops message (well it's just a WARNING, a real oops would kill > your driver for real) please file a bug report on bugs.freedesktop.org > against dri -> drm (intel). > > The information we need is the full dmesg fore the entire boot when > enabling drm.debug=0xe on the kernel cmdline. It is attached. > > For the boot hang you've reported on the redhat bz if you want to move it > forward I suggest to do a reverse bisect betwen 3.13 and 3.14-rc7 to > figure out which bug _fixed_ your problem and then tell me that. I'll > submit it for backporting to stable kernels. Google should find you some > nice howtos for reverse bisecting kerneels. Thank you. I'll do that. > > Cheers, Daniel > >> >> drm related dmesg lines on linux-3.14-rc7: >> [1.602225] [drm] Initialized drm 1.1.0 20060810 >> [1.795184] [drm] Memory usable by graphics device = 2048M >> [1.860121] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >> [1.860124] [drm] Driver supports precise vblank timestamp query. >> [1.860259] vgaarb: device changed decodes: >> PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem >> [1.910948] [drm] GMBUS [i915 gmbus panel] timed out, falling back >> to bit banging on pin 3 >> [1.943111] [drm] Wrong MCH_SSKPD value: 0x16040307 >> [1.943117] [drm] This can cause pipe underruns and display issues. >> [1.943120] [drm] Please upgrade your BIOS to fix this. >> [2.192641] [drm:ironlake_disable_pch_transcoder] *ERROR* failed to >> disable transcoder A >> [2.454038] Console: switching to colour frame buffer device 170x48 >> [2.461511] i915 :00:02.0: fb0: inteldrmfb frame buffer device >> [2.461514] i915 :00:02.0: registered panic notifier >> [2.462577] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: >> no) >> [2.467139] acpi device:05: registered as cooling_device4 >> [2.467447] input: Video Bus as >> /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input9 >> [2.467696] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on >> minor 0 >> [3.709772] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off >> >> >> OOPSes on linux-3.14-rc7: >> WARNING: CPU: 3 PID: 124 at drivers/gpu/drm/i915/intel_display.c:450 >> i9xx_clock+0x81/0xb0 [i915]() >> Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video >> CPU: 3 PID: 124 Comm: systemd-udevd Not tainted 3.14.0-rc7 #1 >> Hardware name: TOSHIBA PORTEGE R830/Portable PC, BIOS Version 4.10 >> 01/08/2013 >> 0009 8804345f7818 8168e6d2 >> 8804345f7850 8108199d 88043787f6d8 0100 >> 0001d4c0 88043787f000 8804345f7860 >> Call Trace: >> [] dump_stack+0x45/0x56 >> [] warn_slowpath_common+0x7d/0xa0 >> [] warn_slowpath_null+0x1a/0x20 >> [] i9xx_clock+0x81/0xb0 [i915] >> [] i9xx_crtc_clock_get.isra.31+0x1d0/0x2c0 [i915] >> [] ironlake_get_pipe_config+0x209/0x2f0 [i915] >> [] intel_modeset_setup_hw_state+0xb4/0xc20 [i915] >> [] intel_modeset_gem_init+0x3d/0x50 [i915] >> [] i915_driver_load+0xc98/0xe10 [i915] >> [] drm_dev_register+0x7b/0x160 [drm] >> [] drm_get_pci_dev+0xa0/0x220 [drm] >> [] i915_pci_probe+0x3b/0x60 [i915] >> [] local_pci_probe+0x45/0xa0 >> [] pci_device_probe+0xd1/0x130 >> [] driver_probe_device+0x125/0x3a0 >> [] __driver_attach+0x93/0xa0 >> [] ? __device_attach+0x40/0x40 >> [] bus_for_each_dev+0x63/0xa0 >> [] driver_attach+0x1e/0x20 >> [] bus_add_driver+0x180/0x250 >> [] ? 0xa0146fff >> [] driver_register+0x64/0xf0 >> [] ? 0xa0146fff >> [] __pci_register_driver+0x4b/0x50 >> [] drm_pci_init+0x11a/0x130 [drm] >> [] ? 0xa0146fff >> [] i915_init+0x6a/0x6c [i915] >> [] do_one_initcall+0xd2/0x180 >> [] ? set_memory_nx+0x43/0x50 >> [] load_module+0x1bb6/0x2580 >> [] ? store_uevent+0x40/0x40 >> [] ? copy_module_from_fd.isra.47+0x121/0x180 >> [] SyS_finit_module+0x86/0xb0 >> [] system_call_fastpath+0x16/0x1b >> ---[ end trace 628c8f95ba351f1a ]--- >> >> WARNING: CPU: 3 PID: 124 at drivers/gpu/drm/i915/intel_display.c:450 >> i9xx_clock+0x81/0xb0 [i915]() >> Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video >> CPU: 3 PID: 124 Comm:
I915: OOPSes on linux-3.14-rc7
On Thu, Mar 20, 2014 at 05:56:20PM +0100, Peter Senna Tschudin wrote: > When Fedora updated the Kernel package from 3.12 to 3.13 my notebook > stopped booting (Kernel freezes) when a 2560 x 1440 high res monitor > is attached. I have tried using 3.13.6 from kernel.org and the problem > persists. The problem can be partially solved by passing nomodeset to > Kernel which will make the Kernel to boot, but the screens never comes > to life. When using 3.14-rc7 it boots again, the screen works, but > with some oops messages. > > How can I help fixing this issue? > > I've reported te bug at: > https://bugzilla.redhat.com/show_bug.cgi?id=1072557 For the oops message (well it's just a WARNING, a real oops would kill your driver for real) please file a bug report on bugs.freedesktop.org against dri -> drm (intel). The information we need is the full dmesg fore the entire boot when enabling drm.debug=0xe on the kernel cmdline. For the boot hang you've reported on the redhat bz if you want to move it forward I suggest to do a reverse bisect betwen 3.13 and 3.14-rc7 to figure out which bug _fixed_ your problem and then tell me that. I'll submit it for backporting to stable kernels. Google should find you some nice howtos for reverse bisecting kerneels. Cheers, Daniel > > drm related dmesg lines on linux-3.14-rc7: > [1.602225] [drm] Initialized drm 1.1.0 20060810 > [1.795184] [drm] Memory usable by graphics device = 2048M > [1.860121] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [1.860124] [drm] Driver supports precise vblank timestamp query. > [1.860259] vgaarb: device changed decodes: > PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem > [1.910948] [drm] GMBUS [i915 gmbus panel] timed out, falling back > to bit banging on pin 3 > [1.943111] [drm] Wrong MCH_SSKPD value: 0x16040307 > [1.943117] [drm] This can cause pipe underruns and display issues. > [1.943120] [drm] Please upgrade your BIOS to fix this. > [2.192641] [drm:ironlake_disable_pch_transcoder] *ERROR* failed to > disable transcoder A > [2.454038] Console: switching to colour frame buffer device 170x48 > [2.461511] i915 :00:02.0: fb0: inteldrmfb frame buffer device > [2.461514] i915 :00:02.0: registered panic notifier > [2.462577] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: no) > [2.467139] acpi device:05: registered as cooling_device4 > [2.467447] input: Video Bus as > /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input9 > [2.467696] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on > minor 0 > [3.709772] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off > > > OOPSes on linux-3.14-rc7: > WARNING: CPU: 3 PID: 124 at drivers/gpu/drm/i915/intel_display.c:450 > i9xx_clock+0x81/0xb0 [i915]() > Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video > CPU: 3 PID: 124 Comm: systemd-udevd Not tainted 3.14.0-rc7 #1 > Hardware name: TOSHIBA PORTEGE R830/Portable PC, BIOS Version 4.10 > 01/08/2013 > 0009 8804345f7818 8168e6d2 > 8804345f7850 8108199d 88043787f6d8 0100 > 0001d4c0 88043787f000 8804345f7860 > Call Trace: > [] dump_stack+0x45/0x56 > [] warn_slowpath_common+0x7d/0xa0 > [] warn_slowpath_null+0x1a/0x20 > [] i9xx_clock+0x81/0xb0 [i915] > [] i9xx_crtc_clock_get.isra.31+0x1d0/0x2c0 [i915] > [] ironlake_get_pipe_config+0x209/0x2f0 [i915] > [] intel_modeset_setup_hw_state+0xb4/0xc20 [i915] > [] intel_modeset_gem_init+0x3d/0x50 [i915] > [] i915_driver_load+0xc98/0xe10 [i915] > [] drm_dev_register+0x7b/0x160 [drm] > [] drm_get_pci_dev+0xa0/0x220 [drm] > [] i915_pci_probe+0x3b/0x60 [i915] > [] local_pci_probe+0x45/0xa0 > [] pci_device_probe+0xd1/0x130 > [] driver_probe_device+0x125/0x3a0 > [] __driver_attach+0x93/0xa0 > [] ? __device_attach+0x40/0x40 > [] bus_for_each_dev+0x63/0xa0 > [] driver_attach+0x1e/0x20 > [] bus_add_driver+0x180/0x250 > [] ? 0xa0146fff > [] driver_register+0x64/0xf0 > [] ? 0xa0146fff > [] __pci_register_driver+0x4b/0x50 > [] drm_pci_init+0x11a/0x130 [drm] > [] ? 0xa0146fff > [] i915_init+0x6a/0x6c [i915] > [] do_one_initcall+0xd2/0x180 > [] ? set_memory_nx+0x43/0x50 > [] load_module+0x1bb6/0x2580 > [] ? store_uevent+0x40/0x40 > [] ? copy_module_from_fd.isra.47+0x121/0x180 > [] SyS_finit_module+0x86/0xb0 > [] system_call_fastpath+0x16/0x1b > ---[ end trace 628c8f95ba351f1a ]--- > > WARNING: CPU: 3 PID: 124 at drivers/gpu/drm/i915/intel_display.c:450 > i9xx_clock+0x81/0xb0 [i915]() > Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video > CPU: 3 PID: 124 Comm: systemd-udevd Tainted: GW3.14.0-rc7 #1 > Hardware name: TOSHIBA PORTEGE R830/Portable PC, BIOS Version 4.10 > 01/08/2013 > 0009 8804345f7500 8168e6d2 > 8804345f7538
I915: OOPSes on linux-3.14-rc7
When Fedora updated the Kernel package from 3.12 to 3.13 my notebook stopped booting (Kernel freezes) when a 2560 x 1440 high res monitor is attached. I have tried using 3.13.6 from kernel.org and the problem persists. The problem can be partially solved by passing nomodeset to Kernel which will make the Kernel to boot, but the screens never comes to life. When using 3.14-rc7 it boots again, the screen works, but with some oops messages. How can I help fixing this issue? I've reported te bug at: https://bugzilla.redhat.com/show_bug.cgi?id=1072557 drm related dmesg lines on linux-3.14-rc7: [1.602225] [drm] Initialized drm 1.1.0 20060810 [1.795184] [drm] Memory usable by graphics device = 2048M [1.860121] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.860124] [drm] Driver supports precise vblank timestamp query. [1.860259] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.910948] [drm] GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3 [1.943111] [drm] Wrong MCH_SSKPD value: 0x16040307 [1.943117] [drm] This can cause pipe underruns and display issues. [1.943120] [drm] Please upgrade your BIOS to fix this. [2.192641] [drm:ironlake_disable_pch_transcoder] *ERROR* failed to disable transcoder A [2.454038] Console: switching to colour frame buffer device 170x48 [2.461511] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.461514] i915 :00:02.0: registered panic notifier [2.462577] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: no) [2.467139] acpi device:05: registered as cooling_device4 [2.467447] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input9 [2.467696] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [3.709772] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off OOPSes on linux-3.14-rc7: WARNING: CPU: 3 PID: 124 at drivers/gpu/drm/i915/intel_display.c:450 i9xx_clock+0x81/0xb0 [i915]() Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 3 PID: 124 Comm: systemd-udevd Not tainted 3.14.0-rc7 #1 Hardware name: TOSHIBA PORTEGE R830/Portable PC, BIOS Version 4.10 01/08/2013 0009 8804345f7818 8168e6d2 8804345f7850 8108199d 88043787f6d8 0100 0001d4c0 88043787f000 8804345f7860 Call Trace: [] dump_stack+0x45/0x56 [] warn_slowpath_common+0x7d/0xa0 [] warn_slowpath_null+0x1a/0x20 [] i9xx_clock+0x81/0xb0 [i915] [] i9xx_crtc_clock_get.isra.31+0x1d0/0x2c0 [i915] [] ironlake_get_pipe_config+0x209/0x2f0 [i915] [] intel_modeset_setup_hw_state+0xb4/0xc20 [i915] [] intel_modeset_gem_init+0x3d/0x50 [i915] [] i915_driver_load+0xc98/0xe10 [i915] [] drm_dev_register+0x7b/0x160 [drm] [] drm_get_pci_dev+0xa0/0x220 [drm] [] i915_pci_probe+0x3b/0x60 [i915] [] local_pci_probe+0x45/0xa0 [] pci_device_probe+0xd1/0x130 [] driver_probe_device+0x125/0x3a0 [] __driver_attach+0x93/0xa0 [] ? __device_attach+0x40/0x40 [] bus_for_each_dev+0x63/0xa0 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x180/0x250 [] ? 0xa0146fff [] driver_register+0x64/0xf0 [] ? 0xa0146fff [] __pci_register_driver+0x4b/0x50 [] drm_pci_init+0x11a/0x130 [drm] [] ? 0xa0146fff [] i915_init+0x6a/0x6c [i915] [] do_one_initcall+0xd2/0x180 [] ? set_memory_nx+0x43/0x50 [] load_module+0x1bb6/0x2580 [] ? store_uevent+0x40/0x40 [] ? copy_module_from_fd.isra.47+0x121/0x180 [] SyS_finit_module+0x86/0xb0 [] system_call_fastpath+0x16/0x1b ---[ end trace 628c8f95ba351f1a ]--- WARNING: CPU: 3 PID: 124 at drivers/gpu/drm/i915/intel_display.c:450 i9xx_clock+0x81/0xb0 [i915]() Modules linked in: i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 3 PID: 124 Comm: systemd-udevd Tainted: GW3.14.0-rc7 #1 Hardware name: TOSHIBA PORTEGE R830/Portable PC, BIOS Version 4.10 01/08/2013 0009 8804345f7500 8168e6d2 8804345f7538 8108199d 8804345f7608 0100 0001d4c0 880434076b18 8804345f7548 Call Trace: [] dump_stack+0x45/0x56 [] warn_slowpath_common+0x7d/0xa0 [] warn_slowpath_null+0x1a/0x20 [] i9xx_clock+0x81/0xb0 [i915] [] i9xx_crtc_clock_get.isra.31+0x1d0/0x2c0 [i915] [] ironlake_get_pipe_config+0x209/0x2f0 [i915] [] check_crtc_state+0x11e/0xc60 [i915] [] intel_modeset_check_state+0x2bb/0x7b0 [i915] [] ? ilk_wm_get_hw_state+0x1bc/0x2b0 [i915] [] intel_modeset_setup_hw_state+0x97e/0xc20 [i915] [] intel_modeset_gem_init+0x3d/0x50 [i915] [] i915_driver_load+0xc98/0xe10 [i915] [] drm_dev_register+0x7b/0x160 [drm] [] drm_get_pci_dev+0xa0/0x220 [drm] [] i915_pci_probe+0x3b/0x60 [i915] [] local_pci_probe+0x45/0xa0 [] pci_device_probe+0xd1/0x130 [] driver_probe_device+0x125/0x3a0 [] __driver_attach+0x93/0xa0 [] ?
