Linux Kernel acting weirdly

[Samuel Bushi]

Lately the booting has been troublesome. These are the things that are happening randomly:
-It boots up normally
-It shows up a kernel panic saying that it tried to read/write outside of some hd(0)
-Grub Menu might not even load and the notebook just beeps continuously. This occurs mostly when I restart after a Kernel-Panic-hang.
-It restarts and I end up back at the grub menu.

I tried installing linux-generic-lts-vivid. The first boot-up was OK but the pointer was missing (It was still there, but not visible). After that, the problem returned. The random part is getting skewed and the occurrence of the 2nd error is increasing.

Updated BIOS, no change:
8DCN40WW
10/24/2014

=====FIXED=====
kernel-fixed-upstream
kernel-fixed-upstream-4.1.0

WORKAROUND: Use 3.13.0-53-generic kernel in Advanced options for Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-55-generic 3.13.0-55.92
ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
Uname: Linux 3.13.0-54-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: blumonkey 2442 F.... pulseaudio
 /dev/snd/controlC1: blumonkey 2442 F.... pulseaudio
CRDA:
 country IN:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5735 - 5835 @ 40), (N/A, 20)
CurrentDesktop: Unity
Date: Sat Jun 20 15:11:36 2015
HibernationDevice: RESUME=UUID=bd3ea4d3-f75a-4ca5-9be7-4d36551a8fb0
InstallationDate: Installed on 2015-02-20 (120 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 20287
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-54-generic root=UUID=5a4d10f5-4e18-4315-bca6-fca9cc5a4803 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-54-generic N/A
 linux-backports-modules-3.13.0-54-generic N/A
 linux-firmware 1.127.12
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DCN38WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: 31900059STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Z510
dmi.modalias: dmi:bvnLENOVO:bvr8DCN38WW:bd11/28/2013:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510:
dmi.product.name: 20287
dmi.product.version: Lenovo IdeaPad Z510
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

We would like to review the details of the panic. Do you have a screen shot, digital image or the text details of the panic that you could provide?

[Samuel Bushi (samuelsbushi)]

The error message:

error: attempt to read or write outside of disk `hd0`.

Press any key to continue...

This is followed by a page that says something like Kernel Panic = not syncing: VFS : Unable to mount root fs on unknown block hd(0, 0)
Along with some other text, and the system sorta hangs there.

I will try to get a screenshot ASAP

[Samuel Bushi (samuelsbushi)]

Here is the screenshot.

[penalvch (penalvch)]

Samuel Bushi, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Samuel Bushi (samuelsbushi)]

Guys, it is day-3 no more errors. I think it is safe to mark this as fixed.

[penalvch (penalvch)]

Samuel Bushi, the next step is to fully reverse commit bisect from kernel 3.13 to 4.1 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

[Launchpad Janitor (janitor)]

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