Panic in i915 kernel module on boot #48
Comments
|
Just updated to 4.16.2-552.native, it's still there [ 1.407126] ------------[ cut here ]------------ |
|
This is an old bug that we've been on and off tracking since over a year. We can't do much more than to note that this is an upstream kernel issue and the best way to report this is to the Intel Gfx Driver maintainers. https://github.com/torvalds/linux/blob/master/MAINTAINERS#L7051 |
|
And it seems to have disappeared with 4.16.3-553.native |
|
Reopening as it seems to be happening again. I have opened a defect as directed with the Intel GFX team: https://bugs.freedesktop.org/show_bug.cgi?id=106237 |
|
The Intel GFX group provided some debug kernel params for additional diagnostics. The messages are supposed to be retrieved through dmesg. [ 0.190165] pci_bus 0000:00: root bus resource [mem 0xdf800000-0xfeafffff window] |
|
bump maintainers are still looking for further information as to how to get earlier dmesg info. |
|
That seems a bit odd I wonder with the debug options our dmesg buffer just isn't long enough. Do you normally see the dmesg output truncated without those options? (I don't have a system where this truncation happens) |
|
dmesg is still truncated - does yours begin at 0 and contain the kernel params? |
|
[ 0.000000] Linux version ... is the first line. The next line is the kernel command line in full. |
|
I'm at a loss, is there a way for me to increase the buffer? |
|
Try adding log_buf_len=4M to the kernel command line. You can create a file in /etc/kernel/cmdline.d/logbuf.conf with that in it and then run sudo clr-boot-manager update. |
|
perfect |
|
@omkhar Still seeing this issue (and have you been able to get the log to show what you needed)? |
|
@omkhar saw you closed fdo bug. Is this still a concern for you? Are you using newer kernel, i.e. 4.17-x? |
|
No longer seeing the defect, please close. Will open if it reappears.
…-oa
On Jun 19, 2018, at 7:35 PM, Daniel Charles ***@***.***> wrote:
@omkhar saw you closed fdo bug. Is this still a concern for you? Are you using newer kernel, i.e. 4.17-x?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Closing: No longer seeing. |
Kernel 4.16.2-551.native running on baremetal
[ 1.405712] ------------[ cut here ]------------
[ 1.405713] RPM wakelock ref not held during HW access
[ 1.405731] WARNING: CPU: 1 PID: 177 at ../drivers/gpu/drm/i915/intel_drv.h:1813 gen8_write32+0x1e7/0x240
[ 1.405732] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4(+) nf_nat nf_conntrack ipt_REJECT iptable_filter iptable_mangle iptable_raw iptable_security ip_tables intel_spi_platform intel_spi spi_nor mtd snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core i2c_i801 igb(+) snd_pcm snd shpchp lpc_ich soundcore
[ 1.405756] CPU: 1 PID: 177 Comm: clr_power Not tainted 4.16.2-551.native #1
[ 1.405757] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Q3XXG4-P, BIOS 5.6.5 09/19/2016
[ 1.405760] RIP: 0010:gen8_write32+0x1e7/0x240
[ 1.405761] RSP: 0018:ffff98ce411ebd60 EFLAGS: 00010246
[ 1.405764] RAX: 0000000000000000 RBX: 000000000e000000 RCX: 0000000000000000
[ 1.405765] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 1.405766] RBP: 000000000000a008 R08: 0000000000000000 R09: 0000000000000000
[ 1.405767] R10: 0000000000000000 R11: 0000000000000000 R12: ffff907a54010000
[ 1.405768] R13: ffff907a54014d30 R14: 0000000000000004 R15: ffff907a511fefa8
[ 1.405770] FS: 00007f1c82753500(0000) GS:ffff907a5f500000(0000) knlGS:0000000000000000
[ 1.405772] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.405773] CR2: 00000000019a8448 CR3: 0000000211272004 CR4: 00000000000606e0
[ 1.405774] Call Trace:
[ 1.405780] gen6_set_rps+0x173/0x1a0
[ 1.405784] i915_min_freq_set+0x9d/0xf0
[ 1.405788] simple_attr_write+0xbc/0xe0
[ 1.405792] full_proxy_write+0x4e/0x80
[ 1.405796] __vfs_write+0x21/0x160
[ 1.405800] ? SyS_newfstat+0x29/0x40
[ 1.405803] ? _cond_resched+0x14/0x40
[ 1.405806] vfs_write+0xac/0x1a0
[ 1.405809] SyS_write+0x3d/0xa0
[ 1.405812] do_syscall_64+0x69/0x1a0
[ 1.405815] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 1.405818] RIP: 0033:0x7f1c82671f14
[ 1.405819] RSP: 002b:00007ffdd5e36018 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 1.405821] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f1c82671f14
[ 1.405822] RDX: 0000000000000004 RSI: 00000000019a7430 RDI: 0000000000000003
[ 1.405823] RBP: 00000000019a7430 R08: 00007f1c82753500 R09: 00007f1c826cdf20
[ 1.405825] R10: 00000000019a7010 R11: 0000000000000246 R12: 00000000019af510
[ 1.405826] R13: 0000000000000004 R14: 00007f1c827492a0 R15: 00007f1c82748760
[ 1.405827] Code: 0f 87 a7 fe ff ff e9 f0 fe ff ff 80 3d f2 72 f0 00 00 0f 85 63 fe ff ff 48 c7 c7 20 d7 47 8b c6 05 de 72 f0 00 01 e8 69 f4 8a ff <0f> 0b e9 49 fe ff ff b9 01 00 00 00 31 d2 89 ee 48 89 04 24 4c
[ 1.405866] ---[ end trace de493c822de9904a ]---
The text was updated successfully, but these errors were encountered: