[Lucid] Xorg server sometimes fails to start

Bug #584187 reported by Kai Krakow
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NULL Project
Invalid
Undecided
Unassigned
linux-restricted-modules-2.6.24 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

The Xorg server sometimes fails to start and only comes up in safe mode, telling that it was not able to initialize the graphics card or driver (I don't remember exactly). Choosing "restart now" in the offered options after waiting a few seconds fixes this, the Xorg server comes up with the correct driver loaded and fully functional.

I upgraded a production machine from 9.10 to 10.04 since Lucid is marked as LTS and I thought it would be nice step to a long-lasting stable system. Now different instabilities show up, one of it being this problem. The system needs to be used to print delivery forms and invoices for a food delivery service and the reduced (failsafe) graphics mode does not fit the POS system right. The system is shut down every evening and booted every late morning. This needs to be fixed asap.

Additional information:
Using nvidia proprietary drivers. My suspect is that upstart is just too fast with starting the x-server (it comes up after about 5-7 seconds after grub), and the nvidia kernel module is probably not yet loaded until then.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Moving to the Ubuntu bug tracker.

Note that the proprietary nvidia X drivers load the associated module themselves, so there's no chance of a race here

affects: upstart → null
Changed in null:
status: New → Invalid
Revision history for this message
Kai Krakow (hurikhan77) wrote :

So, to further debug this: What else could be the problem? Where should I look? Apparently I don't have remote access to the system in question, so looking into the issue may take some time on my side.

Revision history for this message
Daniel Stone (danielstone) wrote :

I noticed similar action when plymouth was changed to alternative

Revision history for this message
Kai Krakow (hurikhan77) wrote :
Revision history for this message
Kai Krakow (hurikhan77) wrote :
Revision history for this message
Kai Krakow (hurikhan77) wrote :

> Note that the proprietary nvidia X drivers load the
> associated module themselves, so there's no
> chance of a race here

Well, attached a log and it clearly says the kernel module failed... But I think this is a remnant of a more generic problem, as the other log shows (it fails despite no nvidia module involved - it's the failsafe session).

Revision history for this message
Kai Krakow (hurikhan77) wrote :

I suppose this has a similar cause than the current cups problem in upstart. So it may be a duplicate of #554172.

Revision history for this message
Kai Krakow (hurikhan77) wrote :

I request this being a duplicate of bug 554172.

Revision history for this message
bugbot (bugbot) wrote : linux-restricted-modules-2.6.24 is obsolete

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.

Changed in linux-restricted-modules-2.6.24 (Ubuntu):
status: New → Won't Fix
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.