| Summary: | web2 segfaults - can't start up on SugarBay | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Tom Zanussi <tom.zanussi> |
| Component: | core | Assignee: | Edwin Zhai <edwin.zhai> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | dexuan.cui, kevin.tian, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 1.0 M4 | ||
| Hardware: | Other | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Tom Zanussi
2011-02-02 21:37:54 UTC
Hi Tom, Just now Edwin and I tested the bug On SugerBay using http://viggo.jf.intel.com/~tzanussi/yocto/misc/poky-image-sato-live-sugarbay-20110211082154.hddimg.bz2 (from the file name, I think the file was built In Feb 11?) and we didn't find any segfault. Maybe somebody has fixed the bug?? mark it WORKSFORME, as latest image seems to work. Tom, could you pls. confirm it? Thanks, I just built the latest sugarbay and can't verify this, because now the web app itself is gone. (In reply to comment #3) > I just built the latest sugarbay and can't verify this, because now the web app > itself is gone. RP disabled webkit due to the long time of building @ 9d7aa109. So maybe you need revert this commit to verify it. Thanks, edwin CC RP, Should we disable web-webkit and webkit-gtk for a long time? If so, we can close this low priority bug without bothering TOM to try. Thanks, edwin (In reply to comment #4) > (In reply to comment #3) > > I just built the latest sugarbay and can't verify this, because now the web app > > itself is gone. > > RP disabled webkit due to the long time of building @ 9d7aa109. > > So maybe you need revert this commit to verify it. > > Thanks, > edwin I reverted this and tried again with code from 2/18 (commit 8048b714cd57c89aecfac438af3c7094a770fb9b) and am still seeing the segfault after starting the browser. (In reply to comment #6) > I reverted this and tried again with code from 2/18 (commit > 8048b714cd57c89aecfac438af3c7094a770fb9b) and am still seeing the segfault > after starting the browser. Tom, I'll try to build on my side, pls. tell me your changeset. Thanks, edwin also Tom could you share your image some places? that way Edwin can also take a look... (In reply to comment #8) > also Tom could you share your image some places? that way Edwin can also take a > look... Here's the image with 9d7aa109 reverted and that segfaults for me: http://viggo.jf.intel.com/~tzanussi/yocto/misc/poky-image-sato-live-sugarbay-20110222183817.hddimg.bz2 (In reply to comment #9) > (In reply to comment #8) > > also Tom could you share your image some places? that way Edwin can also take a > > look... > Here's the image with 9d7aa109 reverted and that segfaults for me: > http://viggo.jf.intel.com/~tzanussi/yocto/misc/poky-image-sato-live-sugarbay-20110222183817.hddimg.bz2 Let's reopen the bug. We'll try the new img. (In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > also Tom could you share your image some places? that way Edwin can also take a > > > look... > > Here's the image with 9d7aa109 reverted and that segfaults for me: > > http://viggo.jf.intel.com/~tzanussi/yocto/misc/poky-image-sato-live-sugarbay-20110222183817.hddimg.bz2 > Let's reopen the bug. We'll try the new img. Hi Tom, Unfortunately, we still can't reproduce the issue with this new img... :-( Any special steps we missed? -- we just used dd to write your .hddimg file into a U-disk and booted our SugarBay from it. Or, we don't have the exactly same type of host as yours??? The info of our SugarBay host is: Sugar Bay Internal Eng Beta Sandy Bridge C0 / Cougar Point B0 Los Lunas SCPT CRB Fab A (In reply to comment #11) > (In reply to comment #10) > > (In reply to comment #9) > > > (In reply to comment #8) > > > > also Tom could you share your image some places? that way Edwin can also take a > > > > look... > > > Here's the image with 9d7aa109 reverted and that segfaults for me: > > > http://viggo.jf.intel.com/~tzanussi/yocto/misc/poky-image-sato-live-sugarbay-20110222183817.hddimg.bz2 > > Let's reopen the bug. We'll try the new img. > > Hi Tom, > Unfortunately, we still can't reproduce the issue with this new img... :-( > Any special steps we missed? -- we just used dd to write your .hddimg file into > a U-disk and booted our SugarBay from it. > > Or, we don't have the exactly same type of host as yours??? > > The info of our SugarBay host is: > > Sugar Bay Internal Eng Beta > Sandy Bridge C0 / Cougar Point B0 > Los Lunas SCPT CRB Fab A Hi, There are no special steps required other than what you did. My hardware is more recent than yours apparently. Here's the information from my hw: Intel desktop board 01 scpt_crb Los Lunas CRB Fab Id 1 Sandy Bridge i7 3400Mhz Stepping D2 / Cougar Point Stepping 03 (B1 Stepping) It's strange that hw would matter for something like this. I can see if it happens on another 64-bit machine e.g. the Jasper Forest... (In reply to comment #12) > Hi, > > There are no special steps required other than what you did. My hardware is > more recent than yours apparently. Here's the information from my hw: > > Intel desktop board 01 > scpt_crb > Los Lunas CRB Fab Id 1 > Sandy Bridge i7 3400Mhz Stepping D2 / Cougar Point Stepping 03 (B1 Stepping) > > It's strange that hw would matter for something like this. > > I can see if it happens on another 64-bit machine e.g. the Jasper Forest... Tom, before I dd the img, I used dd if=/dev/zero of=/dev/sdg bs=1M count=512 to flush the header of the usb disk. Sometimes, probably cause troubles without it. |