kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #21119
[Bug 1237392] Re: kernels following version 3.8.0-27 do not start
The kernel you proposed to install, I installed. It produces pretty much the same behaviour. So I guess it is not solved upstream.
I cannot change the status to "kernel-bug-exists-upstream", it is not part of the options. So I changed it to confirmed.
Hopefully you can change the status properly.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1237392
Title:
kernels following version 3.8.0-27 do not start
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
All kernel updates on ubuntu following kernel 3.8.0-27 result in an
empty screen with no indication of startup, no response to the
keyboard. I can only start up using kernel version 3.8.0-27-generic.
All following numbers (up to and including 3.8.0-31-generic) do not
result in a running system. Also, the display no message at all when
starting up (after grub).
I checked the logfiles with "grep -n "Linux version 3.8.0-" *" and
found only 27 to be logged, nothing for the other kernels. I am at a
loss how to continue.
I am running the most recent version of Ubuntu server.
Two days ago I reinstalled Ubuntu with essentially the same result.
The installation kernel version 3.8.0-19 works fine. The updated
kernel 3.8.0-31 does not work.
The following is the situation:
When I let the machine start on itself I get no output at all.
When I manually tell ubuntu to start the most recent kernel, I get 2 lines:
"Loading Linux-3.8.0-31-generic ..." "Loading initial ramdisk ..."
that's it.
When I manually start the recovery kernel, I get a lot of
information. Finally it drops to a terminal and indicates it could not
load the LVM partition /dev/mapper/Server-Root. This is why I never
see any result in my message or dmesg on disk.
The problem seems to be with the Areca Raid controller. It does a
reset of the scsi bus eh until it finally gives up and drops to a
terminal. A while after the system goes berserk with messages of non
responding scsi bus.
As I cannot reach my harddisk, is there a way to find out what is
wrong? Why does everything work fine up to and including kernel 27 and
starts to malfunction after that? Did the Areca software change in
some way?
P.S. When I start kernel version 3.8.0-19, everything works fine.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubuntu-release-upgrader-core 1:0.192.13
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CrashDB: ubuntu
Date: Wed Oct 9 14:53:03 2013
InstallationDate: Installed on 2013-10-07 (1 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions