Only when using kernel parameter init=/sbin/e4rat-preload kernel panics when updating libc6

[Redmar]

Every time I update ubuntu 13.10 using sudo aptitude update && sudo aptitude safe-upgrade, my pc freezes with a kernel panic: trying to kill init. The error code is 0000ff00. So far this has happened 4 or 5 times, always when installing updates.

WORKAROUND: Use default kernel parameters (e.g. remove init=/sbin/e4rat-preload ).

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-3-generic 3.10.0-3.12
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: trijntje 1699 F.... pulseaudio
Date: Fri Jul 19 11:46:13 2013
InstallationDate: Installed on 2012-11-01 (259 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal" - Build i386 LIVE Binary 20121018-21:07
Lsusb:
 Bus 001 Device 002: ID 0402:7675 ALi Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer AOD257
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-3-generic root=UUID=f2496972-ed3a-4a43-a55c-4eaa002cf2be ro verbose init=/sbin/e4rat-preload
RelatedPackageVersions:
 linux-restricted-modules-3.10.0-3-generic N/A
 linux-backports-modules-3.10.0-3-generic N/A
 linux-firmware 1.112
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-06-15 (33 days ago)
dmi.bios.date: 10/21/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE06_PT
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrV1.15:bd10/21/2011:svnAcer:pnAOD257:pvrV1.15:rvnAcer:rnJE06_PT:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: AOD257
dmi.product.version: V1.15
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Redmar, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Joseph Salisbury (jsalisbury)]

Also, can you get a screen capture or digital photo of the panic?

[penalvch (penalvch)]

Redmar, thank you for testing the mainline kernel. The next step would be to find the earliest upstream kernel version that fixed your problem (reverse mainline kernel version bisect). Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Redmar (redmar)]

Looks like a correction is in order, I just had a kernel panic while running the mainline kernel. While the problem always occurs while updating, it does not occur on every update, so it's hard to reproduce.

I've typed over the exact error messages I get on screen when it happens:

[ 595.024498] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000ff00
[ 595.024498]
[ 595.024760] drm_kms_helper: panic occurred, switching back to text console

[penalvch (penalvch)]

Redmar, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/ ?

[Redmar (redmar)]

It looks like the panic only occurs when updating libc6. I found this out because usually after the panic, I run 'sudo dpkg --configure -a' and I can continue the update, but since the last panic dpkg starts by configuring libc6, and then the panic occurs again. So at this point, the panic is 100% reproducable, but I cannot install any new software. If there is any way to collect more information about the panic, please tell me. If not, I'll re-install ubuntu and try the mainline rc3 kernel.

[Redmar (redmar)]

I cannot install any new software, since dpkg got interrupted mid-upgrade and calling 'dpkg --configure -a' triggers the kernel panic. I've been trying to reproduce the panic on a fresh install of the daily build on an external drive, but so far without success.

[penalvch (penalvch)]

Redmar, did this problem not occur in a release prior to Saucy?

[Redmar (redmar)]

No, this problem did not occur before I upgraded to Saucy.

[Redmar (redmar)]

I was just able to reproduce the problem by using e4rat instead of ureadahead, and installing updates which included libc6.

:$cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic root=UUID=11fd08db-f2a5-45bc-8daf-7baa813ba410 ro quiet splash init=/sbin/e4rat-preload vt.handoff=7

[penalvch (penalvch)]

Redmar, if you remove all non-default kernel parameters (ex. init=/sbin/e4rat-preload) is this problem still reproducible?

[Redmar (redmar)]

This problem is only reproducable while using init=/sbin/e4rat-preload.

[Redmar (redmar)]

Is this still a valid bug report? e4rat is not available from the ubuntu repository.

[Etienne F-L (eflavoie)]

Hello,

I have the same issue and I don't have e4rat. I started the upgrade with "update-manager -d" The update dowloaded the packages and started installing them but I got the kernel panic and the upgrade stopped. Now I can't install/remove any packages because running the dpkg --configure -a takes me back to the freeze. I don't have any special boot parameters. I'm using grub 0.97 since I've been upgrading this machine since 5.04.

[penalvch (penalvch)]

Etienne F-L, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[alien (nalex2004)]

13.10, default boot parameters, kernel panic during upgrades (drm_kms_helper), after reboot dpkg --configure -a and then apt-get install -f. Work good until next upgrade.

[penalvch (penalvch)]

alien, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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

[mporten (mathias-porten)]

I had the same problem and managed to solve by following steps:
- edit with admin rights /etc/default/grub: remove the "init part" from GRUB_CMDLINE_LINUX_DEFAULT line
- sudo update-grub
- reboot
- try sudo dpkg --configure -a again, libc6 should be installed without kernel panic

With this steps, e4rat is not enabled any more.

[Launchpad Janitor (janitor)]

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