[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#878403: linux-image-4.13.0-1-686-pae (and prior version!) crashes at boot



Package: src:linux
Version: 4.13.4-1
Severity: important

Dear Maintainer,

the latest kernel version crashes at boot, when the intel drm module is loaded (this is, what I think is doing). 

Whilst on kernel 4.12.0-2-686-pae there was only a non destructive crash information, the latest version makes the computer unuable, as the text console is either not readable, and when it is starting X, only one half of the screen is seen.

This bugreport is written when running kernel 4.12.0-2-686-pae, and below I attach you the warning text, I got at boot (the one, which is not destructable). I hope, it will clear, what is happening. This is the warning at boot:

-----------------------  start ------------------------

Oct  2 08:42:04 localhost kernel: [   22.275700] ------------[ cut here ]------------
Oct  2 08:42:04 localhost kernel: [   22.275725] WARNING: CPU: 0 PID: 119 at /build/linux-JOV0NV/linux-4.12.13/drivers/gpu/drm/drm_atomic_helper.c:842 drm_atomic_helper_update_legacy_modeset_state+0x1f0/0x210 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.275728] Modules linked in: ath9k_hw ath mac80211 sg lpc_ich mfd_core cfg80211 snd_hda_codec_realtek rng_core snd_hda_codec_generic snd_hda_intel i915 shpchp snd_hda_codec snd_hda_core snd_hwdep drm_kms_helper snd_pcm_oss eeepc_laptop(+) snd_mixer_oss sparse_keymap rfkill snd_pcm snd_timer battery drm ac i2c_algo_bit snd video soundcore button wmi acpi_cpufreq gspca_sn9c20x gspca_main v4l2_common videodev media atl1 mii parport_pc ppdev lp parport loop ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache ecb lrw gf128mul algif_skcipher af_alg raid10 uas usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod dm_crypt dm_mod crypto_simd cryptd aes_i586 sd_mod psmouse ahci libahci libata scsi_mod
Oct  2 08:42:04 localhost kernel: [   22.275849]  ehci_pci uhci_hcd ehci_hcd usbcore usb_common atl1c thermal
Oct  2 08:42:04 localhost kernel: [   22.275869] CPU: 0 PID: 119 Comm: kworker/u4:2 Not tainted 4.12.0-2-686-pae #1 Debian 4.12.13-1
Oct  2 08:42:04 localhost kernel: [   22.275872] Hardware name: ASUSTeK Computer INC. \x931005HAG\x94/1005HAG, BIOS 0401    03/02/2010
Oct  2 08:42:04 localhost kernel: [   22.275883] Workqueue: events_unbound async_run_entry_fn
Oct  2 08:42:04 localhost kernel: [   22.275888] task: f65c9480 task.stack: f65ee000
Oct  2 08:42:04 localhost kernel: [   22.275904] EIP: drm_atomic_helper_update_legacy_modeset_state+0x1f0/0x210 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.275906] EFLAGS: 00010246 CPU: 0
Oct  2 08:42:04 localhost kernel: [   22.275911] EAX: f5db9000 EBX: f5df9300 ECX: f5df1a80 EDX: f5678e00
Oct  2 08:42:04 localhost kernel: [   22.275915] ESI: 00000000 EDI: 00000000 EBP: f5e31c00 ESP: f65efc54
Oct  2 08:42:04 localhost kernel: [   22.275918]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Oct  2 08:42:04 localhost kernel: [   22.275923] CR0: 80050033 CR2: b76208d0 CR3: 3566a820 CR4: 000006f0
Oct  2 08:42:04 localhost kernel: [   22.275926] Call Trace:
Oct  2 08:42:04 localhost kernel: [   22.276071]  ? intel_atomic_commit_tail+0xa65/0xe70 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276084]  ? pick_next_task_fair+0x4f4/0x5c0
Oct  2 08:42:04 localhost kernel: [   22.276132]  ? intel_atomic_commit+0x393/0x490 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276277]  ? _cond_resched+0x2a/0x40
Oct  2 08:42:04 localhost kernel: [   22.276414]  ? intel_atomic_commit+0x393/0x490 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276447]  ? drm_atomic_commit+0x37/0x40 [drm]
Oct  2 08:42:04 localhost kernel: [   22.276463]  ? restore_fbdev_mode+0x14b/0x270 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276477]  ? drm_fb_helper_restore_fbdev_mode_unlocked+0x24/0x70 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276490]  ? drm_fb_helper_set_par+0x27/0x5b [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276620]  ? intel_fbdev_set_par+0x12/0x50 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276629]  ? fbcon_init+0x53d/0x580
Oct  2 08:42:04 localhost kernel: [   22.276637]  ? visual_init+0xb8/0x110
Oct  2 08:42:04 localhost kernel: [   22.276643]  ? do_bind_con_driver+0x15c/0x330
Oct  2 08:42:04 localhost kernel: [   22.276650]  ? do_take_over_console+0x108/0x170
Oct  2 08:42:04 localhost kernel: [   22.276657]  ? do_fbcon_takeover+0x55/0xb0
Oct  2 08:42:04 localhost kernel: [   22.276665]  ? notifier_call_chain+0x4b/0x70
Oct  2 08:42:04 localhost kernel: [   22.276672]  ? __blocking_notifier_call_chain+0x2e/0x50
Oct  2 08:42:04 localhost kernel: [   22.276679]  ? blocking_notifier_call_chain+0xe/0x20
Oct  2 08:42:04 localhost kernel: [   22.276685]  ? register_framebuffer+0x1df/0x330
Oct  2 08:42:04 localhost kernel: [   22.276702]  ? drm_fb_helper_initial_config+0x26c/0x420 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276830]  ? intel_fbdev_initial_config+0x13/0x30 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276836]  ? async_run_entry_fn+0x30/0x150
Oct  2 08:42:04 localhost kernel: [   22.276843]  ? process_one_work+0x135/0x2f0
Oct  2 08:42:04 localhost kernel: [   22.276850]  ? worker_thread+0x39/0x3a0
Oct  2 08:42:04 localhost kernel: [   22.276856]  ? kthread+0xd7/0x110
Oct  2 08:42:04 localhost kernel: [   22.276862]  ? process_one_work+0x2f0/0x2f0
Oct  2 08:42:04 localhost kernel: [   22.276867]  ? kthread_create_on_node+0x30/0x30
Oct  2 08:42:04 localhost kernel: [   22.276874]  ? ret_from_fork+0x19/0x24
Oct  2 08:42:04 localhost kernel: [   22.276878] Code: 88 f0 01 00 00 0f b7 52 26 89 90 f4 01 00 00 eb d3 8d 76 00 8d bc 27 00 00 00 00 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 <0f> ff e9 7e fe ff ff 89 f6 8d bc 27 00 00 00 00 0f ff e9 18 ff
Oct  2 08:42:04 localhost kernel: [   22.276984] ---[ end trace b2c434140b39c81f ]---


---------------------------------  end -------------------------------------

At the moment I have to get back to the old kernel, as the latst is not usable. I can not tzell, if this apears on 64-bit systems, too, mine is a 32-bit system (EEEPC 1005 HGO).

Thank you for any help and your work.

Best regards

Hans

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.12.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.13.0-1-686-pae depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod                                    24-1
ii  linux-base                              4.5

Versions of packages linux-image-4.13.0-1-686-pae recommends:
ii  firmware-linux-free  3.4
ii  irqbalance           1.1.0-2.3

Versions of packages linux-image-4.13.0-1-686-pae suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.03+dfsg-14.1
ii  grub-pc                 2.02-2
pn  linux-doc-4.13          <none>

Versions of packages linux-image-4.13.0-1-686-pae is related to:
ii  firmware-amd-graphics     20170823-1
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
ii  firmware-linux-nonfree    20170823-1
ii  firmware-misc-nonfree     20170823-1
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
ii  firmware-realtek          20170823-1
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information


Reply to: