Bug 2609 - [SugarBay] X server fails to start
Summary: [SugarBay] X server fails to start
Status: VERIFIED NOTABUG
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-configuration (show other bugs)
Version: 1.3.1
Hardware: x86 x86_64
: High enhancement
Target Milestone: 1.3 M2
Assignee: Tom Zanussi
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-06-14 15:40 UTC by Laurentiu Serban
Modified: 2012-07-09 20:28 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
X log (6.84 KB, application/octet-stream)
2012-06-14 16:42 UTC, Laurentiu Serban
no flags Details
X log 1 (6.84 KB, application/octet-stream)
2012-06-14 16:42 UTC, Laurentiu Serban
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Laurentiu Serban 2012-06-14 15:40:16 UTC
X Server fails to start on SugarBay board.

The system used is a Dell Vostro 460 MT
Comment 1 Laurentiu Serban 2012-06-14 15:41:26 UTC
The build used was the output of 13/06/2012 autobuilder
Comment 2 Saul Wold 2012-06-14 16:19:56 UTC
could be a dup of 2608, need backtrace or console output.
Comment 3 Tom Zanussi 2012-06-14 16:37:57 UTC
This is due I think to using random off-the-shelf hardware.  We haven't
seen problems on any of the customer reference boards - I just did a
build and boot of master last night, and everything worked fine -
networking and X included.

I think the solution is that the Romania team needs to get customer
reference boards for testing, just like PRC has.

If we want to actually support this hardware, we can do that - we'll just need to address the differences in the BSP.  For now, I'll assume that's what's wanted here and mark it as an enhancement.  If that's not the case, please close this (if you think there really is a problem, you can make your image available to either me or PRC who have customer reference boards that we can test on until you get yours).
Comment 4 Laurentiu Serban 2012-06-14 16:42:04 UTC
Created attachment 586 [details]
X log
Comment 5 Laurentiu Serban 2012-06-14 16:42:22 UTC
Created attachment 587 [details]
X log 1
Comment 6 Darren Hart 2012-06-14 20:22:58 UTC
What was the decision on this bug? Close as WILL_NOT_FIX or NOT_A_BUG and open a new bug to support a new machine?
Comment 7 Tom Zanussi 2012-06-14 20:28:06 UTC
(In reply to comment #6)
> What was the decision on this bug? Close as WILL_NOT_FIX or NOT_A_BUG and
> open a new bug to support a new machine?

That makes sense to me, but I'll let the originator do that...
Comment 8 Tom Zanussi 2012-06-15 19:55:43 UTC
As per Darren's suggestion, closing this as NOTABUG - if it's desired that we support the Dell Vostro 460 MT, we can open a new bug specifically for that.
Comment 9 Laurentiu Serban 2012-07-09 20:28:44 UTC
Setting this to verified