failure to boot impish daily (no boot in 65 mins)

Bug #1930884 reported by Chris Guiver
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
syslinux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Lubuntu impish daily; QA-test on

- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

this is a slightly newer higher-end box than last few boots; one of which appeared to boot slowly but it's taking ages with just a blinking cursor... 10 mins & no progress, 12-18 mins approx & I've given up..

** expected result

In 10-15 minutes I expect a LIVE ISO to boot (esp. before 30 mins)

** actual result

nothing but blinking cursor after grub appeared

(I want to go to bed, so I didn't wait my usual 30-60 mins, so I could re-try and time it more accurately...)

Boot earlier tonight appeared slower on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
which prompted me to test on this box, but boot appeared normal on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

I've tested impish far less than prior releases, but a slow boot on this box is unexpected...

--

Additional notes:

The system was booted again 2nd time on same box; it booted in ~6-14 mins (I was typing this and failed to stop the phone's stopwatch app that was timing boot, nor notice when boot actually completed)

The system was booted again 3rd time on same box; it failed to complete boot in 36 mins when I gave up.

The slow boot times on some boxes of hirsute/impish (1929029) make it harder to detect slower boots.. but this box was never tagged with https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342.

This box is used daily; so expectation is no issues.

Tags: iso-testing
Revision history for this message
Chris Guiver (guiverc) wrote :

incomplete... need to explore further (was this just a fluke)

next boot was done ?? (faster anyway; I was typing this & thus didn't stop the timer sorry!!!)

I needed to file for iso.qa.ubuntu.com to fail test.

Changed in syslinux (Ubuntu):
status: New → Incomplete
Chris Guiver (guiverc)
Changed in syslinux (Ubuntu):
status: Incomplete → New
Chris Guiver (guiverc)
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1930884

tags: added: iso-testing
Revision history for this message
Brian Murray (brian-murray) wrote :

Chris - isn't this similar to bug 1922342?

Changed in syslinux (Ubuntu):
status: New → Incomplete
Revision history for this message
Chris Guiver (guiverc) wrote :

@Brian - it maybe that very issue (why I mentioned the bug in the description & likely wrote as if it was) but for it to be that issue, the box has to eventually boot..

feels similar yes, but still different..
I didn't want to leave the box on overnight (I thought about; it'd have answered the boot question)

I'm writing an updated lubuntu daily now (mkusb/live; yesterday was mkusb/clone as I recall) for testing..

I also plan to zsync my ubuntu ISO & try that.. I'll give it an hour to boot today.. so I hope to have more info by this arvo.

Chris Guiver (guiverc)
summary: - failure to boot impish daily (or too slow; i gave up ~15 mins in..)
+ failure to boot impish daily (no boot in 65 mins)
Revision history for this message
Chris Guiver (guiverc) wrote (last edit ):

New Lubuntu daily attempting to boot on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)
stop watch started at grub/lubuntu as I hit enter..

today's Lubuntu daily was written with mkusb/LIVE (yesterdays was mkusb/CLONE I believe)

75mins on the stopwatch and I'll FAIL this test at that mark...
cursor is still blinking top left corner, no change..

I don't believe it's a lubuntu issue.. ; switching to boot today's ubuntu daily on box)

Changed in syslinux (Ubuntu):
status: Incomplete → New
Revision history for this message
Chris Guiver (guiverc) wrote (last edit ):

Ubuntu Desktop boots good on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

(http://iso.qa.ubuntu.com/qatracker/milestones/424/builds/231660/testcases/1303/results)
ISO was written using GNOME-disks (recovery)

at ~2 mins 19 the maybe-ubiquity TRY/INSTALL question appeared & was asking which..
by ~3 mins 2 secs the desktop appeared stable

Lubuntu ISO (comment #5) was also tested on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
- hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
Timings can be noted on http://iso.qa.ubuntu.com/qatracker/milestones/424/builds/231678/testcases/1303/results/ but these were 2 mins + change.. to boot (reasonable I believe)

(I'm wondering if I need to rule out mkusb involvement next)

Revision history for this message
Chris Guiver (guiverc) wrote (last edit ):

Current Lubuntu daily was written to media using

`sudo dd bs=4M oflag=sync status=progress of=/dev/sdb if=/de2900/lubuntu_64/impish-desktop-amd64.iso`

and that boots normally... with desktop up & visible within 6 mins anyway (I forgot to look at clock; too busy picking up mouth from floor..)

This maybe is issue with MKUSB ?? and not a Ubuntu syslinux anyway... back to INCOMPLETE.

(( mkusb/clone should have worked normally... was I mistaken & used mkusb/live? something is missing here.. but I didn't record write method on iso.qa.ubu which is my most accurate record ))

Changed in syslinux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in syslinux (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.