b3nmore, the next step is to fully reverse commit bisect from kernel 4.4
to 4.8-rc3 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
Please note, finding adjacent kernel versions is not fully commit
bisecting.
Also, the kernel release names are irrelevant for the purposes of
bisecting.
It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.
Thank you for your help.
** Tags added: kernel-fixed-upstream-4.8-rc3 needs-reverse-bisect
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1618903
Title:
System crashes after resume from hibernate
Status in linux package in Ubuntu:
Incomplete
Bug description:
kernels 4.4 crash reliably after almost every resume from hibernate.
One system log I could save reported:
Aug 31 15:24:37 yo sshd[2620]: Server listening on :: port 810.
Aug 31 15:24:40 yo kernel: general protection fault: 0000 [#2] SMP
Aug 31 15:24:40 yo kernel: Modules linked in: binfmt_misc usblp joydev
input_leds eeepc_wmi intel_rapl asus_wmi x86_pkg_temp_thermal sparse_
Aug 31 15:24:40 yo kernel: CPU: 3 PID: 3355 Comm: xfsettingsd Tainted: G
D 4.4.0-36-generic #55-Ubuntu
Aug 31 15:24:40 yo kernel: Hardware name: ASUS All Series/B85M-G, BIOS 2501
07/22/2015
Aug 31 15:24:40 yo kernel: task: ffff880211bfa940 ti: ffff880211970000
task.ti: ffff880211970000
Aug 31 15:24:40 yo kernel: RIP: 0010:[<ffffffff8182c33f>]
[<ffffffff8182c33f>] down_write+0x1f/0x40
Aug 31 15:24:40 yo kernel: RSP: 0018:ffff880211973dd0 EFLAGS: 00010246
Aug 31 15:24:40 yo kernel: RAX: 00e7000000e60028 RBX: 00e7000000e60028 RCX:
0000000000000000
Aug 31 15:24:40 yo kernel: RDX: ffffffff00000001 RSI: ffffffff81a11c80 RDI:
00e7000000e60028
Aug 31 15:24:40 yo kernel: RBP: ffff880211973dd8 R08: ffff88021fb9a920 R09:
ffff8800c2fe5d48
Aug 31 15:24:40 yo kernel: R10: ffff88021fdf6000 R11: 0000000000000000 R12:
ffff8800c9b78960
Aug 31 15:24:40 yo kernel: R13: ffff8800c2fe5d48 R14: 00e7000000e60028 R15:
00e7000000e60000
Aug 31 15:24:40 yo kernel: FS: 00007fafccda9a80(0000)
GS:ffff88021fb80000(0000) knlGS:0000000000000000
Aug 31 15:24:40 yo kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 31 15:24:40 yo kernel: CR2: 0000560ce357cad8 CR3: 0000000214802000 CR4:
00000000001406e0
Aug 31 15:24:40 yo kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
Aug 31 15:24:40 yo kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
Aug 31 15:24:40 yo kernel: Stack:
Aug 31 15:24:40 yo kernel: ffff8800c97ec000 ffff880211973eb8
ffffffff8107fc4f 0000000010cc8d00
Aug 31 15:24:40 yo kernel: 0000000000000000 00007fafccda9d50
0000000001200011 ffff8800c2fe5278
Aug 31 15:24:40 yo kernel: ffff8800c2fe5280 ffff8800c2fe5268
ffff8800c97ec068 ffff8802111fb128
Aug 31 15:24:40 yo kernel: Call Trace:
Aug 31 15:24:40 yo kernel: [<ffffffff8107fc4f>] copy_process+0x14ff/0x1ae0
Aug 31 15:24:40 yo kernel: [<ffffffff810803c0>] _do_fork+0x80/0x360
Aug 31 15:24:40 yo kernel: [<ffffffff81080749>] SyS_clone+0x19/0x20
Aug 31 15:24:40 yo kernel: [<ffffffff8182dfb2>]
entry_SYSCALL_64_fastpath+0x16/0x71
Aug 31 15:24:40 yo kernel: Code: 1f 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
00 00 55 48 89 e5 53 48 89 fb e8 ae dd ff ff 48 ba 01 00 00 00
Aug 31 15:24:40 yo kernel: RIP [<ffffffff8182c33f>] down_write+0x1f/0x40
Aug 31 15:24:40 yo kernel: RSP <ffff880211973dd0>
Aug 31 15:24:41 yo kernel: ---[ end trace 864859008364d4cd ]---
Aug 31 15:24:44 yo systemd[3136]: Time has been changed
Currently I've removed the intel xorg package to exclude some gpu
crashes, but this does not seem to have any influence, so I guess it
is really a kernel bug.
Previous kernels under trusty resumed flawlessly up to 4.2 (lts-wily),
4.4 (lts-xenial) also produced system hangs after resume.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: kiran 3378 F.... pulseaudio
/dev/snd/controlC0: kiran 3378 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Aug 31 15:32:06 2016
HibernationDevice: RESUME=UUID=5ea8b83e-6f6f-4e44-98f6-45ade2c2d6c3
InstallationDate: Installed on 2013-11-16 (1019 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64
(20131016)
IwConfig:
lo no wireless extensions.
p2p1 no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic
root=UUID=4fee8160-326f-4688-a0d9-22e158e70f45 ro quiet
RelatedPackageVersions:
linux-restricted-modules-4.4.0-36-generic N/A
linux-backports-modules-4.4.0-36-generic N/A
linux-firmware 1.157.3
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-08-20 (10 days ago)
dmi.bios.date: 07/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-G
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618903/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
