On Tue, May 23, 2017 at 09:01:05PM -0700, Guenter Roeck wrote: > On 05/23/2017 01:08 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.70 release. > > There are 103 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Thu May 25 20:08:25 UTC 2017. > > Anything received after that time might be too late. > > > > Early feedback: All x86_64 images are crashing. Let me know if you need me to bisect. > > Guenter > > --- > > ... > EXT4-fs (sda): re-mounted. Opts: errors=remount-ro,data=ordered > BUG: unable to handle kernel paging request at 0000000000002280 > IP: [<ffffffff81451115>] process_echoes+0x15/0x70 > PGD da68067 PUD d991067 PMD 0 > Oops: 0000 [#1] PREEMPT SMP > Modules linked in: > CPU: 0 PID: 400 Comm: bootlogd Not tainted 4.4.70-rc1-yocto-standard+ #1 > Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.10.1-0-g8891697-prebuilt.qemu-project.org 04/01/2014 > task: ffff88000d159bc0 ti: ffff88000d230000 task.ti: ffff88000d230000 > RIP: 0010:[<ffffffff81451115>] [<ffffffff81451115>] process_echoes+0x15/0x70 > RSP: 0018:ffff88000d233d50 EFLAGS: 00000202 > RAX: ffff88000dd950d8 RBX: 0000000000000000 RCX: 0000000000000007 > RDX: ffff88000dd4a400 RSI: ffff88000d91b700 RDI: ffff88000dd95000 > RBP: ffff88000d233d68 R08: 00007ffffffff000 R09: ffff88000eeb91c8 > R10: 00007fffc9dc3f70 R11: 0000000000000246 R12: 0000000000000007 > R13: 0000000000603574 R14: 0000000000000007 R15: ffff88000d91b700 > FS: 00007f973601b700(0000) GS:ffff88000fc00000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 0000000000002280 CR3: 000000000d953000 CR4: 00000000003406f0 > Stack: > ffff88000dd95000 0000000000000007 0000000000603574 ffff88000d233df0 > ffffffff814515b7 0000004100000022 ffff88000d91b700 ffff88000dd950d8 > ffff88000dd4a400 ffff88000d91b700 0000000000000000 ffff88000d159bc0 > Call Trace: > [<ffffffff814515b7>] n_tty_write+0x97/0x4e0 > [<ffffffff8108e710>] ? __wake_up_sync+0x20/0x20 > [<ffffffff8144dae6>] tty_write+0x1a6/0x2d0 > [<ffffffff81451520>] ? n_tty_open+0xe0/0xe0 > [<ffffffff8117d6e8>] __vfs_write+0x28/0xe0 > [<ffffffff81077145>] ? preempt_count_add+0x85/0xd0 > [<ffffffff81199abe>] ? __fd_install+0x5e/0x110 > [<ffffffff81199969>] ? __alloc_fd+0xc9/0x180 > [<ffffffff8117dcff>] ? rw_verify_area+0x4f/0xe0 > [<ffffffff8117df3a>] vfs_write+0x9a/0x170 > [<ffffffff8117ea96>] SyS_write+0x46/0xb0 > [<ffffffff8172db17>] entry_SYSCALL_64_fastpath+0x12/0x66 > Code: 8b 40 48 48 85 c0 74 07 55 48 89 e5 ff d0 5d c3 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 8b 9f 80 02 00 00 <48> 8b 83 80 22 00 00 48 39 43 28 74 3a 4c 8d ab b0 22 00 00 49 > RIP [<ffffffff81451115>] process_echoes+0x15/0x70 > RSP <ffff88000d233d50> > CR2: 0000000000002280 > ---[ end trace cec672c0d4b54e81 ]--- > Kernel panic - not syncing: Fatal exception > Kernel Offset: disabled > ---[ end Kernel panic - not syncing: Fatal exception Yes, bisection would be great, if you can do it. I would blame the only tty patch in the release, tty-prevent-ldisc-drivers-from-re-using-stale-tty-fields.patch, but that would be odd. Oops, nope, that would be it, the merge happened badly, I applied a chunk in the wrong place, ugh. Let me go fix that patch up now... greg k-h