Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0

Bug #1711298 reported by Stefan Bader on 2017-08-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Seth Forshee

Bug Description

Environment: Xen PV guest (64bit)

The 4.11.0-10 kernel did still boot. But after upgrading to the 4.12.0-11 kernel the following panic is observed:

[ 1.262361] device-mapper: uevent: version 1.0.3
[ 1.262465] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: <email address hidden>
[ 1.262581] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.262696] BUG: unable to handle kernel paging request at ffffc90040635060
[ 1.262719] IP: vlv2_plat_configure_clock+0x3b/0xa0
[ 1.262731] PGD ff805067
[ 1.262732] P4D ff805067
[ 1.262742] PUD fa93c067
[ 1.262752] PMD fa352067
[ 1.262761] PTE 0
[ 1.262771]
[ 1.262790] Oops: 0000 [#1] SMP
[ 1.262801] Modules linked in:
[ 1.262814] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.12.0-11-generic #12-Ubuntu
[ 1.262825] task: ffff8800fa39aa80 task.stack: ffffc90040628000
[ 1.262833] RIP: e030:vlv2_plat_configure_clock+0x3b/0xa0
[ 1.262840] RSP: e02b:ffffc9004062bb58 EFLAGS: 00010246
[ 1.262847] RAX: 0000000000000000 RBX: ffffc90040635060 RCX: 0000000002523fff
[ 1.262855] RDX: ffff8800fa39aa80 RSI: 0000000000000002 RDI: ffffffff81ff7340
[ 1.262862] RBP: ffffc9004062bb68 R08: 0000000000000067 R09: 00000000fff13000
[ 1.262870] R10: 0000000000007ff0 R11: 00003ffffffff000 R12: 0000000000000002
[ 1.262877] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1.262890] FS: 0000000000000000(0000) GS:ffff8800fac80000(0000) knlGS:0000000000000000
[ 1.262902] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.262908] CR2: ffffc90040635060 CR3: 0000000001e09000 CR4: 0000000000000660
[ 1.262917] Call Trace:
[ 1.262926] vlv2_plat_clk_probe+0x3f/0x70
[ 1.262936] platform_drv_probe+0x3b/0xa0
[ 1.262944] driver_probe_device+0x2ff/0x450
[ 1.262952] __device_attach_driver+0x83/0x100
[ 1.262959] ? __driver_attach+0xe0/0xe0
[ 1.262967] bus_for_each_drv+0x69/0xb0
[ 1.262974] __device_attach+0xdd/0x160
[ 1.262982] device_initial_probe+0x13/0x20
[ 1.262989] bus_probe_device+0x92/0xa0
[ 1.262997] device_add+0x451/0x690
[ 1.263003] platform_device_add+0x10d/0x270
[ 1.263012] ? set_debug_rodata+0x17/0x17
[ 1.263019] platform_device_register_full+0xfe/0x110
[ 1.263029] ? vlv2_plat_clk_init+0x19/0x19
[ 1.263036] vlv2_plat_clk_init+0x48/0x82
[ 1.263044] do_one_initcall+0x50/0x1a0
[ 1.263052] kernel_init_freeable+0x1bd/0x25f
[ 1.263060] ? rest_init+0x80/0x80
[ 1.263067] kernel_init+0xe/0x100
[ 1.263074] ret_from_fork+0x25/0x30
[ 1.263081] Code: 47 83 fe 02 41 89 f4 77 67 48 8b 05 00 1b d9 00 48 85 c0 74 48 c1 e7 02 48 63 ff 48 8d 1c 38 48 c7 c7 40 73 ff 81 e8 35 b5 16 00 <8b> 03 83 e0 fc 44 09 e0 89 03 48 c7 c7 40 73 ff 81 e8 5f af 16
[ 1.263138] RIP: vlv2_plat_configure_clock+0x3b/0xa0 RSP: ffffc9004062bb58
[ 1.263145] CR2: ffffc90040635060
[ 1.263157] ---[ end trace e3dd450c61676c8a ]---
[ 1.263177] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009

Stefan Bader (smb) wrote :

Modifying the boot config to boot the previous kernel allows to boot again.

Changed in linux (Ubuntu):
status: New → Confirmed
Stefan Bader (smb) wrote :

Still the same crash using a 4.13 kernel:

[ 1.251126] BUG: unable to handle kernel paging request at ffffc90040635060
[ 1.251144] IP: vlv2_plat_configure_clock+0x3b/0xa0
[ 1.251152] PGD ff805067
[ 1.251153] P4D ff805067
[ 1.251159] PUD fa93e067
[ 1.251166] PMD fa354067
[ 1.251172] PTE 0
[ 1.251178]
[ 1.251189] Oops: 0000 [#1] SMP
[ 1.251198] Modules linked in:
[ 1.251208] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.13.0-5-generic #6-Ubuntu
[ 1.251220] task: ffff8800fa39ac00 task.stack: ffffc90040628000
[ 1.251230] RIP: e030:vlv2_plat_configure_clock+0x3b/0xa0
[ 1.251239] RSP: e02b:ffffc9004062bb58 EFLAGS: 00010246
[ 1.251248] RAX: 0000000000000000 RBX: ffffc90040635060 RCX: 0000000002523fff
[ 1.251256] RDX: ffff8800fa39ac00 RSI: 0000000000000002 RDI: ffffffff81fe7dc0
[ 1.251265] RBP: ffffc9004062bb68 R08: 0000000000000067 R09: 00000000fff13000
[ 1.251273] R10: 0000000000007ff0 R11: 00003ffffffff000 R12: 0000000000000002
[ 1.251282] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1.251295] FS: 0000000000000000(0000) GS:ffff8800fac00000(0000) knlGS:0000000000000000
[ 1.251307] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.251315] CR2: ffffc90040635060 CR3: 0000000001e09000 CR4: 0000000000000660
[ 1.251324] Call Trace:
[ 1.251334] vlv2_plat_clk_probe+0x3f/0x70
[ 1.251345] platform_drv_probe+0x3b/0xa0
[ 1.251353] driver_probe_device+0x2ff/0x450
[ 1.251362] __device_attach_driver+0x83/0x100
[ 1.251371] ? __driver_attach+0xe0/0xe0
[ 1.251379] bus_for_each_drv+0x69/0xb0
[ 1.251387] __device_attach+0xdd/0x160
[ 1.251395] device_initial_probe+0x13/0x20
[ 1.251403] bus_probe_device+0x92/0xa0
[ 1.251411] device_add+0x448/0x680
[ 1.251420] platform_device_add+0x10d/0x270
[ 1.251430] ? set_debug_rodata+0x17/0x17
[ 1.251437] platform_device_register_full+0xfe/0x110
[ 1.251447] ? vlv2_plat_clk_init+0x19/0x19
[ 1.251456] vlv2_plat_clk_init+0x48/0x82
[ 1.251465] do_one_initcall+0x50/0x1a0
[ 1.251474] kernel_init_freeable+0x1ae/0x250
[ 1.251483] ? rest_init+0xc0/0xc0
[ 1.251491] kernel_init+0xe/0xfc
[ 1.251499] ret_from_fork+0x25/0x30
[ 1.251506] Code: 47 83 fe 02 41 89 f4 77 67 48 8b 05 f8 ea d8 00 48 85 c0 74 48 c1 e7 02 48 63 ff 48 8d 1c 38 48 c7 c7 c0 7d fe 81 e8 85 f4 17 00 <8b> 03 83 e0 fc 44 09 e0 89 03 48 c7 c7 c0 7d fe 81 e8 af ee 17
[ 1.251565] RIP: vlv2_plat_configure_clock+0x3b/0xa0 RSP: ffffc9004062bb58
[ 1.251573] CR2: ffffc90040635060
[ 1.251586] ---[ end trace 0b77e5f33603697e ]---

Stefan Bader (smb) wrote :

Crash is caused by parts of a staging driver which is supposed to enable Intel MIPI Cameras:
CONFIG_INTEL_ATOMISP -> drivers/staging/media/atomisp/clock

This is a new driver introduced in 4.12.

Stefan Bader (smb) wrote :

CONFIG_INTEL_ATOMISP -> drivers/staging/media/atomisp/platform/clock is the correct path.

Seth Forshee (sforshee) wrote :

This is a staging driver that can only be built into the kernel, and it's unconditionally registering a platform device for physical hw that may not be present. That is a bad behavior, so I've disabled this option until the driver is in better shape.

Changed in linux (Ubuntu):
assignee: nobody → Seth Forshee (sforshee)
importance: Undecided → High
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :
Download full text (13.1 KiB)

This bug was fixed in the package linux - 4.12.0-12.13

---------------
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
    - mm: ratelimit PFNs busy info message
    - mm: fix list corruptions on shmem shrinklist
    - futex: Remove unnecessary warning from get_futex_key
    - xtensa: fix cache aliasing handling code for WT cache
    - xtensa: mm/cache: add missing EXPORT_SYMBOLs
    - xtensa: don't limit csum_partial export by CONFIG_NET
    - xfs: Fix leak of discard bio
    - pinctrl: armada-37xx: Fix number of pin in south bridge
    - mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
    - mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
    - mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
    - iscsi-target: fix memory leak in iscsit_setup_text_cmd()
    - iscsi-target: Fix iscsi_np reset hung task during parallel delete
    - usb-storage: fix deadlock involving host lock and scsi_done
    - target: Fix node_acl demo-mode + uncached dynamic shutdown regression
    - fuse: initialize the flock flag in fuse_file on allocation
    - i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
    - nand: fix wrong default oob layout for small pages using soft ecc
    - mmc: mmc: correct the logic for setting HS400ES signal voltage
    - nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
    - drm/bridge: tc358767: fix probe without attached output node
    - drm/etnaviv: Fix off-by-one error in reloc checking
    - drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
    - USB: serial: option: add D-Link DWM-222 device ID
    - USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
    - USB: serial: pl2303: add new ATEN device id
    - usb: musb: fix tx fifo flush handling again
    - USB: hcd: Mark secondary HCD as dead if the primary one died
    - staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
    - iio: aspeed-adc: wait for initial sequence.
    - iio: accel: st_accel: add SPI-3wire support
    - iio: accel: bmc150: Always restore device to normal mode after suspend-
      resume
    - iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
    - iio: light: tsl2563: use correct event code
    - iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
      modifications"
    - staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
    - uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
    - firmware: fix batched requests - wake all waiters
    - firmware: fix batched requests - send wake up on failure on direct lookups
    - firmware: avoid invalid fallback aborts by using killable wait
    - block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet time
    - usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
    - usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
    - USB: Check for dropped connection before switching to full speed
    - usb: core: unlink urbs from the tail of the endpoint's urb_list
    - usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
    - usb:xhci:Add ...

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers