Boot failure after check disk

Bug #651711 reported by peterzay
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

The PC is powered off. A USB thumb drive (ext4) is plugged in. The PC is powered up. Check disk is launched and completes. The screen goes black with one line of error at the top:

(process:335): GLib-WARNING ***: getpwuid_r(): failed due to unknown user id (0)

The PC hangs. To recover, the power button is depressed 5 seconds.

The problem is not reproducible.

This problem was reported twice to package linux but launchpad failed.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: indicator-applet-session 0.3.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
Architecture: i386
Date: Wed Sep 29 21:55:00 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-applet

Revision history for this message
peterzay (peterzay) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi peterzay,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
peterzay (peterzay) wrote :

Jeremy,

My PC is a production machine. I can't experiment with kernel versions. I don't have enough RAM to test with VirtualBox.

Besides, the bug is not reproducible with my kernel version. Why would you expect to reproduce it with some other version?

I would suggest you analyze the code for the conditions that give rise to the error message and build unit test scenarios around those conditions.

If you need any further hardware details, let me know.

Revision history for this message
peterzay (peterzay) wrote :

I just got this bug again but with process:331

Revision history for this message
peterzay (peterzay) wrote :

Clarification: I just got this bug again but with process:331 and no check disk, just a cold boot.

Revision history for this message
peterzay (peterzay) wrote :

I just got this bug again but with process:362 and no check disk, just a cold boot.

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.