Lockup during boot with latest 14.10 and 14.04 LTS

[Alexander]

A little more than a week ago, this as well as a similar other machine pulled in some updates and then refused to boot under 14.04 LTS. Since I thought the bug might have been fixed in 14.10, I did a fresh install last Friday which worked fine, until the system pulled in the then current updates and again refused to boot.

There's nothing to be seen in the boot logs, but I managed to take a screenshot of the stack trace.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-28-generic 3.16.0-28.38
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic i686
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: masterbrain 1936 F.... lxpanel
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
CurrentDesktop: LXDE
Date: Thu Dec 18 13:43:11 2014
HibernationDevice: RESUME=UUID=f198c9ef-f424-44f5-b1c6-9823d480c688
InstallationDate: Installed on 2014-12-12 (5 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 4146:ba63 USBest Technology
 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: System Manufacturer System Name
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=243c4539-2cd0-4676-a538-b77dc045f68f ro recovery nomodeset
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-28-generic N/A
 linux-backports-modules-3.16.0-28-generic N/A
 linux-firmware 1.138
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2003
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS P4PE-X ACPI BIOS Revision 1004
dmi.board.name: P4PE-X
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4PE-XACPIBIOSRevision1004:bd05/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4PE-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Will the system boot if you select the prior kernel version, which would be the one used during the install?

[Alexander (alexander-klein-deactivatedaccount)]

No, booting older kernels doesn't work either. What usually does work, however, is to boot any kernel in recovery mode and then hit "resume" in the recovery menu. Booting this way, graphics will look a bit jaggy, and two CIFS mounts will be missing. I vaguely suspect that the problem may be related to the CIFS mounts, but haven't been able to confirm it, so far.

Unfortunately, all of this happens before the netconsole will start transmitting messages to the machine which does the logging, so I'll be glad for any hints what I might do to defer the crash until later in the boot process.

[Alexander (alexander-klein-deactivatedaccount)]

Available kernels on the machine are:

3.16.0-23-generic (probably the installation kernel)
3.16.0-28-generic

I did a two further experiments, namely:

Comment out the two CIFS-entries in fstab -> no effect
Disable swap, since it's the last line before the stack trace -> no effect

[Alexander (alexander-klein-deactivatedaccount)]

Thanks, but unfortunately, upgrading to the latest BIOS had not effect whatsoever.

[Alexander (alexander-klein-deactivatedaccount)]

Voilà:

ASUS P4PE-X ACPI BIOS Revision 1007
11/10/2003

It's the latest BIOS to be found on ASUS' website.

[penalvch (penalvch)]

Alex, to see if this is already resolved in a later release, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Alexander (alexander-klein-deactivatedaccount)]

I just tried the respective image. Booting from the DVD worked fine, however the installer crashed, so I don't know what would happen later on.

Do you think it might be useful to go back to 14.04, install just the base system, pull in the current upgrades and then add packages one by one, rebooting after every install until the problem occurs?

[penalvch (penalvch)]

Alex, it would be useful to start with 14.04 to see if this is a regression from there.

[Alexander (alexander-klein-deactivatedaccount)]

A fresh install of today's daily-live/current did not show any particular problems, so the bug may have gone away in the meantime.

[penalvch (penalvch)]

Alexander, would you need a backport to a release prior to Vivid?

[Alexander (alexander-klein-deactivatedaccount)]

Christopher, I think, I will just try the recent 14.04.2 point-release and see what happens . Maybe the bug has already disappeared there, too.

[Heike Harnack (h-harnack)]

Hi Community,

please find someone to translate:
Ich habe das gleiche Problem. Ich habe Lubuntu 14.04 und lade immer neue Sachen bzw. automatische Updates. Dadurch habe ich 'praktisch' 14.10. Sehe ich das richtig, das ich eine neue/alte BIOS Software brauche? Eine Zeit lang hatte ich diese Meldung nicht, dann kam sie die letzte Zeit wieder.

Errors:
{{{
CRDA
 Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
CurrentDmesg
 [ 45.342902] init: plymouth-upstart-bridge main process ended, respawning
 [ 47.399552] init: plymouth-stop pre-start process (1242) terminated with status 1
 [102.250957] FAT-fs (sdc1); Volume was not properly umounted. Some data may be corrupt. Please run fsck.
 [102.463818] FAT-fs (sdb1); Volume was not properly umounted. Some data may be corrupt. Please run fsck.
}}}
run fsck:
{{{
XXX@YYY:~$ sudo fsck
[sudo] password for XXX: ***
fsck von util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/mapper/lubuntu--vg-root ist mounted.
e2fsck: Fortsetzung nicht möglich, breche ab.
...
XXX@YYY:~$ fsck -yv
fsck von util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
/dev/mapper/lubuntu--vg-root ist mounted.

WARNUNG!!! Das Dateisystem ist eingehängt, Wenn Sie fortfahren, ***WERDEN***
Sie ***SCHWERWIEGENDE*** Schäden am Dateisystem verursachen.

Wirklich fortfahren<n>? nein
Prüfung abgebrochen.
}}}
Die Fehlermeldung zur Datei/Verzeichnis 'iw' habe ich öfter. Was fehlt denn da? Wieso soll ich fsck starten und das gibt dann eine Warnung raus, es besser zu lassen? Kann mir mal einer dieses Fachchinesisch (bzw. englisch) übersetzen? Gibt es noch andere Optionen zu fsck, mit denen ich das aufrufe?

Thanks for help
Heike

[penalvch (penalvch)]

Heike Harnack, it would help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Alexander (alexander-klein-deactivatedaccount)]

I think the problem Heike Harnack described might have been triggered by something else. In particular, the system seems to get stuck due to unclean FAT-filesystems (Windows, Thumb Drives?) being mounted, which are supposedly not mounted to /. Just issuing a sudo fsck will, of course, also try to fsck the root-filesystem already gone RW with the usual dire consequences.

The whole thin might be fixed by

sudo umount /dev/sdb1
sudo umount /dev/sdc1

sudo fsck /dev/sdb1
sudo fsck /dev/sdc1

and then rebooting the system. BUT be sure to save valuable data from the media being checked beforehand, because you never know…

Translation/Übersetzung:

Ich denke, dass das Problem, das Heike Harnack beschrieb, vielleicht von einer anderen Ursache ausgelöst wird. Insbesondere scheint das System beim Einhängen unsauber ausgehängter FAT-Dateisysteme (Windows, USB-Sticks?) hängen zu bleiben, die vermutlich nicht als / eingehängt sind. Nur ein sudo fsck zu starten, wird natürlich auch versuchen, das Hauptdateisystem zu testen, das zu diesem Zeitpunkt schon beschreibbar ist, mit den üblichen schlimmen Folgen.

Das ganze Problem könnte sich vielleicht beheben lassen durch:

sudo umount /dev/sdb1
sudo umount /dev/sdc1

sudo fsck /dev/sdb1
sudo fsck /dev/sdc1

und danach das System neu starten. ABER sichern Sie vorher wertvolle Daten von den zu überprüfenden Medien, denn man weiß ja nie…

[Launchpad Janitor (janitor)]

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