Ubuntu 13.10 x64 kernel 3.11.0-14-generic crash

Bug #1261744 reported by Evgeny Gridasov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

On a Dell Poweredge 720, Kubuntu 13.10 x64, LInux Kernel 3.11.0-14-generic, when setting /etc/sysctl.conf:
kernel.sched_autogroup_enabled=0
Kernel fails to boot. This error is 100% reproducible and when I comment out that line in sysctl.conf everything works fine.
The machine is 2x Xeon E2670 with 64GB of RAM, I've attached lspci output and also dmesg output during a normal boot.

It starts failing when it detects hard drives, right after it detected ixgbe network driver and when systemd starts to launch programs. If I boot it in safe mode with that option set to 0 and then choose resume in the menu, everything works fine. Apparently when systemd starts something that conflicts with the hard drive detection when autogroup_enabled=0.

I've attached screen shots from the KVM.
Please let me know if you need any other information.

Revision history for this message
Evgeny Gridasov (evgeny-gridasov) wrote :
affects: xubuntu-meta (Ubuntu) → linux-lts-saucy (Ubuntu)
summary: - Ubuntu 13.11 x64 kernel 3.11.0-14-generic crash
+ Ubuntu 13.10 x64 kernel 3.11.0-14-generic crash
Revision history for this message
Aaron Stone (sodabrew) wrote :

Could you test this again with 3.11.0-20 and report back if the problem persists or has been resolved?

Revision history for this message
penalvch (penalvch) wrote :

Evgeny Gridasov, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1261744
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: linux-lts-saucy (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.