Kernel Panic on startx (vchiq_get_state bcm2835_audio_open)


2 posts
by buddymoore » Sat Jan 05, 2013 2:36 am
I'll try to quickly summarize what I've done for context before I go into the problem:

1. Downloaded and wrote 2012-12-16-wheezy-raspbian.zip to SD card from here:
http://www.raspberrypi.org/downloads

2. Recompiled the 3.2.27 kernel using /proc/config.gz from the image above, but adding CONFIG_USB_STORAGE_CYPRESS_ATACB=y so I could root partition from my USB disk
http://elinux.org/RPi_Kernel_Compilation

3. Wrote the wheezy image to a USB disk, changed cmdline.txt to point to root=/dev/sda1, changed /etc/fstab to point to /dev/sda1 for / and updated raspbi-config to expand /dev/sda1 instead of /dev/mmc...

4. Installed MATE and ran it IAW these steps:
http://www.raspbian.org/RaspbianMate

Here's where I hit problems. Kernel panic when I startx. Here's the output from X, and as much info as I could get before the panic:
Code: Select all
Jan  5 02:01:13 raspberrypi kernel: [  210.918328] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.918851] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.919371] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.919891] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.920411] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.920931] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.921455] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.921987] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.922514] vchiq_get_state: g_state.remote->initialised != 1 (0)
Jan  5 02:01:13 raspberrypi kernel: [  210.923037] vchiq: vchiq_initialise: videocore not initialized
Jan  5 02:01:13 raspberrypi kernel: [  210.923037]
Jan  5 02:01:13 raspberrypi kernel: [  210.932179] Unable to handle kernel paging request at virtual address 715f7995
Jan  5 02:01:13 raspberrypi kernel: [  210.956540] pgd = d6ad0000


And a bit more information from the kernel after it dies:
Image

I don't have much appreciable kernel debugging experience, and I've only got minimal cross-compile/"eccentric" linux install experience. I know my way around, so I'm happy to provide more information if that helps, but I'm mostly interested in understand what exactly went wrong and why.

Any ideas, how to continue debugging this?
Posts: 7
Joined: Fri Jan 04, 2013 2:31 am
by buddymoore » Sun Jan 13, 2013 9:47 am
I figured out what happened. I accidentally skipped a step when installing my custom kernel. It is a classic newbie mistake, but for future reference, here is a (mostly) concise roadmap of what I did to get to a working MATE install on an ums-cypress USB root filesystem:

1. Write Raspbian image to SD card
2. Boot Raspbian from SD card
3. Write Raspbian image to USB disk
4. Get RPI kernel source
5. Get RPI tools
6. Get RPI firmware (this is the step that Hexxeh caches in rpi-update as it takes a while)
7. Pull /proc/config.gz from running RPI for kernel config
8. Compile kernel
9. Compress kernel
10. Copy kernel to SD card
11. Copy modules to SD card
12. Copy firmware to SD card (including /opt/vc -- the step I originally forgot)
13. Install MATE according to documentation in original post
Posts: 7
Joined: Fri Jan 04, 2013 2:31 am