• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 17 replies
  • Subscribers 136 subscribers
  • Views 18060 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Samsung Chromebook; Serious stability issues when following graphics and compute guide

John Chadwick

Brief version: How can I debug my Chromebook woes when trying to run kernel-next with the Mali drivers?

I followed this guide: Graphics and Compute Development on Samsung Chromebook It worked, but I'm left with an incredibly unstable system. I'm running a Samsung Chromebook, model number SNOW FREMONT A-E 0878.

A list of stability issues so far:

  • Most importantly, all of the MMC bus seems to give out rather soon after booting up, no matter what. All I/O starts to fail and after a while of waiting I see messages from the kernel reporting timeouts on the MMC bus, and then the system gets locked up.
  • VT1 will typically start to get flooded with something like "udevd[187]: timeout: killing '/sbin/modprobe -bv sdio:c00v02DFd912A' [262]" until it eventually locks up or throws a kernel panic message.
  • The system will often run long enough to actually let me do something. I can connect to wifi, but briefly after doing so, I will usually see the mwifiex_sdio driver hit a time out, followed by a card reset, at which point the device disappears from the system.
  • Sometimes it doesn't even boot. It just stops during the upstart sequence, before any of the other VTs are created, and then it eventually throws some sort of kernel panic. The actual kernel panic message is pushed off screen by the remainder of the data.

I'm even sure there's more, but for now that should give a good idea of what's up: ridiculous instability. I might be able to throw the image on a USB drive and use a USB wifi adapter and skate by some of this, but that's really not a sufficient solution. Given that and the incredible unlikeliness that anyone here has already had or is having this issue, I'd really like it if someone could tell me how to debug these issues as I don't have any clue how to approach it. I have a bit of familiarity with the Linux kernel and a ton with C, but not a darn clue how I'd go about debugging Linux running on a Chromebook.

Hope this is related enough to be discussed here - I certainly don't know where else to discuss problems with this guide.

Parents
  • 0

    Good, glad to hear it's not just me.  I had the same mmc issue which I reported but didn't get any response.  Note that I'm using chrubuntu on my internal mmc, not the sd-card version.  I kind of diverged from the official instructions as described in the previous link.

    I was planning, if I had time, to look at the kernel to see what subsequent patches to dw_mci_pre_dma_transfer were made to kernel-next to see if this was fixed that arm isn't including.

    I didn't notice those udev errors btw, though I was more focused on "why is the mmc dying all of a sudden".   Given the instability of the mmc, I wonder if fixing this might fix some of the other errors...

    I only had wifi working for like a second before everything died horribly.  Most of the time, it's not working at all... although my chrubuntu setup wasn't initially even loading all the necessary modules so that accounts for part of it...

    Anyhoo... if you're on IRC and want to talk through it, I'm "fattire" on freenode.

Reply
  • 0

    Good, glad to hear it's not just me.  I had the same mmc issue which I reported but didn't get any response.  Note that I'm using chrubuntu on my internal mmc, not the sd-card version.  I kind of diverged from the official instructions as described in the previous link.

    I was planning, if I had time, to look at the kernel to see what subsequent patches to dw_mci_pre_dma_transfer were made to kernel-next to see if this was fixed that arm isn't including.

    I didn't notice those udev errors btw, though I was more focused on "why is the mmc dying all of a sudden".   Given the instability of the mmc, I wonder if fixing this might fix some of the other errors...

    I only had wifi working for like a second before everything died horribly.  Most of the time, it's not working at all... although my chrubuntu setup wasn't initially even loading all the necessary modules so that accounts for part of it...

    Anyhoo... if you're on IRC and want to talk through it, I'm "fattire" on freenode.

Children
No data