Low screen resolution and no networking after kernel update

[Jurrian Fahner]

After kernel update yesterday, a reboot was requested.
After reboot the screen resolution was set to 800x600 and the network manager didn't show any network adapters.

When I boot with the kernel image "4.2.0-16", everything works as expected. This is a good work around until the problems are fixed.
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jurrian 2983 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-08 (186 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U4E/540U4E
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic.efi.signed root=UUID=cfe2ffc8-1e9d-4b7f-ae34-8e3f292e7f5a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-17-generic N/A
 linux-backports-modules-4.2.0-17-generic N/A
 linux-firmware 1.149.1
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-17-generic x86_64
UpgradeStatus: Upgraded to wily on 2015-10-25 (16 days ago)
UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/21/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04ACM.055.130321.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP530U4E-K01NL
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ACM.055.130321.dg:bd03/21/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U4E/540U4E:pvrP04ACM:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U4E-K01NL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 530U4E/540U4E
dmi.product.version: P04ACM
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.3 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-unstable/

[penalvch (penalvch)]

Jurrian Fahner, could you please boot into a working kernel and then please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1513767

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[Jurrian Fahner (jurrian-fahner)]

apport information

[penalvch (penalvch)]

Jurrian Fahner, the next step is to fully reverse commit bisect from kernel 4.2 to 4.3 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. 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.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Jurrian Fahner (jurrian-fahner)]

Christopher, what I learned from testing is the following:
- 4.2.0-16-generic -> good kernel
- 4.2.0-17-generic -> defect kernel
- 4.2.0-18-generic -> good kernel

Is this enough detail to continue?
Or do I need to build the commits between 4.2.0-16-generic and 4.2.0-17-generic?
How do I identify the commits between these two versions?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]