Eihän tämä nyt vaan ole toinen viime viikonloppuna huutamistani kahdesta kammasta? Olen maksanutkin ne jo, muttet ole vastannut sähköpostiviestiini, eikä tuotetteita ole kuulunut. Kyseessä siis kohde numero 222291336.
Sumana: Thanks. I’m fairly new here and to Git in general, so I’d rather not, but it’s fine by me if Pranav wants to.
It’s a deal! Nähdään pikkujouluna.
Most of the problems (”freezing”) seen by the user would probably fall under Bug #994306, which I’ve now witnessed on this system. The one I reported above is different, and apparently much rarer in occurrence.
”heistä toisen (sen joka ei ole Marginaali-Jani)”
Enpä arvannutkaan olevani näin etuoikeuttu harvinaisuus. Olin aivan kuvitellut sinulle kokonaisen blogituttavuuksien verkoston, jonka kanssa vietät myöskin IRL-sosiaalista elämää.
Vastaavastihan minä en ole sinun lisäksesi tavannut kuin kaksi naisblogaajaa. (Eikä minulla ole heidän kanssaan edes lapsia, ikävä kyllä.) Mutta minähän olen epäsosiaalisuuttani pyrkinytkin korostamaan, etenkin blogatessani.
Ai niin, paitsi kävinhän minä silloin siellä joulumiitissä. Mutta siis spesifisiä tapaamisia jos ajatellaan.
Steps to reproduce:
1. $ chromium-browser –temp-profile # just to rule out custom configuration
2. Go to youtube.com/html5, opt in to html5
3. Go to http://www.youtube.com/watch_popup?v=-JryxdydOj0&vq=480
What happens:
The tab goes Aw, Snap! and dmesg says ”chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser”.
What I expect to happen:
I haven’t bothered to check how it should behave, but at least it shouldn’t crash.
Additional information:
Seems to happen with both chromium-codecs-ffmpeg and chromium-codecs-ffmpeg-extra (from Medibuntu) alike.
I’m attaching a backtrace. I did my best with it, but I’ll readily admit I have no idea of its value. Please do advise me if I more -dbg packages or something else is needed.
Wind buntu, have you by any chance opted in to YouTube’s HTML5 programme (see the bottom of page at [1])? I’ve found Chromium is all too eager to crash with WebM, which is the video format used in YouTube’s HTML5 experiment.
It’s not limited to WebM though, there are issues with YouTube videos without HTML5 enabled as well.
*[1] http://www.youtube.com/html5
Mitä japsi-tv:tä katselit, netitsekö? Minä katson joskus Seebitiä ja aina muistaessani QVC:tä.
Ahem. It now looks like non-pae + wistron doesn’t work either. But this looks more like a configuration issue on my part, I’ll have to investigate it further. It still doesn’t freeze or anything, it’s just that the wireless doesn’t go online.
Luis, there actually was a BIOS upgrade available from Fujitsu [1], thanks for prompting me to look! I flashed the latest revision S0Z in (it was S0U until now), but unfortunately this didn’t change the behavior at issue here. (There was no mention of the wireless in manufacturer’s changelog either, but those are often incomplete anyway.)
*[1] http://download.ts.fujitsu.com/download/ShowDescription.asp?SoftwareGUID=1968BB6F-7819-4C8C-A488-BAA44C111F7C
Thanks for commenting, Luis. I booted with noexec=off a couple of times with 3.2.0-24-pae, but it didn’t seem to change anything, i.e. the boot still (seemingly) froze when wistron_btns was enabled.
I was unaware of fsam7400 prior to this, so I tried that too, instead of wistron_btns. With fsam7400, the -pae kernel boots fine here even without noexec=off, apart from a ”Waiting for network” , and the wireless network never coming up (can’t bring it up from the desktop either). So here, at least, the noexec=off workaround isn’t needed with fsam7400, though it isn’t much good wrt the wireless either.
To reiterate: the only way currently to have this system boot with the wireless working is to have wistron_btns enabled and to use a non-pae kernel.
I should mention that I’ve upgraded the laptop to Quantal.
I should also mention that Precise’s mainstream installation media refused to boot on the laptop. I believe the message was ”This kernel requires the following features not present on the CPU: pae”. This despite the fact that the -pae kernels, once a system has been installed, *do* boot and work just fine, albeit not with wistron_btns loaded. So currently I’m unsure whether the CPU actually supports pae or not.