vivid master-next kernel: intel driver fails at startup on Dell Inc. Inspiron 1545

Bug #1455575 reported by Aaron Peromsik on 2015-05-15
This bug report is a duplicate of:  Bug #1453593: [gm45] 3.19.0-17 freeze. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Timo Aaltonen

Bug Description

I built 3.19.0-18 from master-next (commit ccb645c) and my Dell 1545 boots, but X doesn't run. I was able to SSH to the machine and find this in dmesg output:

[ 18.128077] ------------[ cut here ]------------
[ 18.128117] kernel BUG at /home/aaron/work/kernel/build/drivers/gpu/drm/i915/intel_display.c:11705!
[ 18.128163] invalid opcode: 0000 [#1] SMP
[ 18.128197] Modules linked in: arc4 b43 dell_wmi uvcvideo bcma gpio_ich sparse_keymap mac80211 dell_laptop dcdbas i8k snd_hda_codec_idt snd_hda_codec_generic cfg80211 videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common i915 videodev snd_hda_intel media coretemp snd_hda_controller joydev snd_hda_codec serio_raw snd_hwdep snd_pcm snd_seq_midi lpc_ich drm_kms_helper snd_seq_midi_event drm snd_rawmidi snd_seq snd_seq_device snd_timer shpchp snd i2c_algo_bit soundcore wmi mac_hid video cuse parport_pc ppdev lp parport autofs4 hid_generic usbhid hid ums_realtek uas usb_storage psmouse ahci sky2 libahci ssb
[ 18.128735] CPU: 1 PID: 272 Comm: plymouthd Not tainted 3.19.0-18-generic #18
[ 18.128771] Hardware name: Dell Inc. Inspiron 1545 /0G848F, BIOS A13 10/23/2009
[ 18.128814] task: ffff8800d7dbebf0 ti: ffff88011a2f8000 task.ti: ffff88011a2f8000
[ 18.128851] RIP: 0010:[<ffffffffc04d1fa8>] [<ffffffffc04d1fa8>] intel_primary_plane_disable+0xe8/0xf0 [i915]
[ 18.128933] RSP: 0018:ffff88011a2fbb78 EFLAGS: 00010246
[ 18.128963] RAX: ffffffffc051df40 RBX: ffff8800d6713b90 RCX: ffff8800d7ef0000
[ 18.128999] RDX: 0000000080000000 RSI: 0000000000000297 RDI: ffff8800366c5c00
[ 18.129034] RBP: ffff88011a2fbb98 R08: 0000000000000001 R09: ffff88011a2fbb0c
[ 18.129069] R10: 0000000000000297 R11: 0000000000001e85 R12: ffff8800d6713800
[ 18.129104] R13: 0000000000000000 R14: ffff8800d6713800 R15: ffff880119c02000
[ 18.129140] FS: 00007f1c049b2740(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
[ 18.129184] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 18.129213] CR2: 00007f68e43c7000 CR3: 000000011a2f5000 CR4: 00000000000407e0
[ 18.129248] Stack:
[ 18.129263] 0000000000000002 ffff8800d6713b90 0000000000000002 0000000000000001
[ 18.129318] ffff88011a2fbc78 ffffffffc04d52ff 0000031600000308 0000000000000000
[ 18.129373] 0000003c00000000 ffff880119c01000 ffff8800d6713b60 ffffffffffffffea
[ 18.129428] Call Trace:
[ 18.129465] [<ffffffffc04d52ff>] __intel_set_mode+0x8df/0xb70 [i915]
[ 18.129518] [<ffffffffc04dbf4b>] intel_crtc_set_config+0xc0b/0xfe0 [i915]
[ 18.129574] [<ffffffffc0352ac6>] drm_mode_set_config_internal+0x66/0x100 [drm]
[ 18.129618] [<ffffffffc03c3298>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper]
[ 18.129661] [<ffffffffc03c5309>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper]
[ 18.129730] [<ffffffffc04e947e>] intel_fbdev_restore_mode+0x1e/0x50 [i915]
[ 18.129788] [<ffffffffc050e28e>] i915_driver_lastclose+0xe/0x20 [i915]
[ 18.129830] [<ffffffffc0345cde>] drm_lastclose+0x2e/0x150 [drm]
[ 18.129872] [<ffffffffc0346130>] drm_release+0x330/0x520 [drm]
[ 18.129906] [<ffffffff811f6617>] __fput+0xe7/0x250
[ 18.129933] [<ffffffff811f67ce>] ____fput+0xe/0x10
[ 18.129961] [<ffffffff81093e27>] task_work_run+0xb7/0xf0
[ 18.129992] [<ffffffff81014ff7>] do_notify_resume+0x97/0xb0
[ 18.130026] [<ffffffff817cb16f>] int_signal+0x12/0x17
[ 18.130055] Code: 00 00 48 8b 3b 48 8d b3 88 00 00 00 e8 a2 e1 ff ff e9 69 ff ff ff 0f 1f 44 00 00 31 ff eb aa 0f 1f 40 00 31 ff eb 88 0f 1f 40 00 <0f> 0b 66 0f 1f 44 00 00 66 66 66 66 90 55 41 01 c9 48 89 e5 41
[ 18.130438] RIP [<ffffffffc04d1fa8>] intel_primary_plane_disable+0xe8/0xf0 [i915]
[ 18.130502] RSP <ffff88011a2fbb78>
[ 18.130523] ---[ end trace 7037451fb494950a ]---

The machine works fine with 3.19.0-16, which I built with one extra commit for bug 1448942. Since that fix has since been merged in master-next I was trying to test a newer kernel to see when I can get back out of the business of building my own. My first try failed due to a hang that was later fixed by commit 1ece1db, and my second try left me here.

tags: added: kernel-da-key vivid
Changed in linux (Ubuntu):
importance: Undecided → High

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1455575

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Joseph Salisbury (jsalisbury) wrote :

This could be a duplicate of bug 1453593

Can you test the kernel at:
http://koti.kapsi.fi/~tjaalton/gm45

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Timo Aaltonen (tjaalton) wrote :

try +bis3

Timo Aaltonen (tjaalton) wrote :

ping?

Timo Aaltonen (tjaalton) wrote :

could you please test the packages from http://koti.kapsi.fi/~tjaalton/gm45 so that we could be sure this is a dupe of 1453593

Timo Aaltonen (tjaalton) on 2015-05-18
Changed in linux (Ubuntu):
assignee: nobody → Timo Aaltonen (tjaalton)
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers