Internal Error Oops - Undefined Instruction 0 #1 Preempt
Sign in Pricing Blog Support Search GitHub This repository Watch 547 Star 3,214 Fork 1,778 raspberrypi/linux Code Issues 193 Pull requests 23 Projects 0 Wiki Pulse Graphs New issue kernel oops: undefined instruction #32 Closed emmanueltouzery opened this Issue Jun 3, 2012 · 13 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 3 participants emmanueltouzery commented Jun 3, 2012 This in on a self-compiled kernel, but on your source with just a minor patch which was already accepted on kernel.org. the kernel i built is 94fbbc4, i just added this tiny patch from the upstream kernel: torvalds/linux@9ab2393 i also use the latest firmware, 87a04c0. I'm using the 192Mb configuration. I compiled the kernel on ubuntu 12.04. Here is the kernel.img i'm booting on: http://dl.dropbox.com/u/22600720/rpi/kernel.img and the .config file I used: http://dl.dropbox.com/u/22600720/rpi/.config Compared to the default .config i have added I2C and pvrusb2 and such drivers. I'm plugging a Hauppage HVR-1900 on the pi for TV recording. The problem occured after about 1h 10 minutes of recording from the device. Concretely it means streaming ~1Mb/s from the USB to the SD card. The CPU is relatively OK when doing that, like at 15%. Because I have seen frame drops doing that, I am using two processes for the recording, one of which runs at realtime scheduling priority, using that flywheel program described there: http://www.isely.net/pipermail/pvrusb2/2011-March/003037.html So after about 1h I get that kernel error. I have had that same problem several times now, the previous time with the same kernel but the original firmware that came with the debian image, but then I didn't get a log in the kern.log, unlike this time. and here is the full stack trac
ARM: Print BUG instead of undefined instruction on BUG_ON() Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] The ARM kernel uses undefined instructions to implement BUG/BUG_ON(). This leads to problems where people don't read one line above the Oops message and see the "kernel BUG at ..." message and so they wrongly assume the kernel has hit an undefined instruction. Instead of printing: Internal error: Oops https://github.com/raspberrypi/linux/issues/32 - undefined instruction: 0 [#1] PREEMPT SMP print Internal error: Oops - BUG: 0 [#1] PREEMPT SMP This should prevent people from thinking the BUG_ON was an undefined instruction when it was actually intentional. Cc: Simon Glass
Board index The team Delete all board cookies All times are UTC
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Raspberry Pi Questions Tags Users Badges Unanswered Ask Question _ Raspberry Pi Stack Exchange is a question and answer site for users and developers of hardware and software for Raspberry Pi. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Boot error (PREEMPT ARM) and screen freeze up vote 0 down vote favorite I had used and tested my RPi B+ almost 2 months ago, with different TVs (via HDMI and AV), and it worked without any problem. Today, I wanted to test my RPi B+ again (after 2 months of not using it) with a brand new Samsung TV via HDMI. I get the following error during boot: [ 1.794149] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT ARM [ 1.801348] Modules linked in [ 1.804467] CPU: 0 PID: 1713401189 Comm: ed [ 1.804467] Not tainted 3.12.28+ #709 When I power on the RPi B+, the logo appear on TV, but then those errors come and it freezes. Cycling the power solves the problem sometimes and it boots successfully. But that error (and screen freeze) happens in 50% of boot times. What shall I do !? boot kernel share|improve this question asked Apr 14 '15 at 8:26 Omid1989 2681218 1 Try do diagnose the problem. Does it still work with the earlier working displays? –joan Apr 14 '15 at 8:36 add a comment| 1 Answer 1 active oldest votes up vote -4 down vote Make sure your SD card is inserted and/or not damaged share|improve this answer answered Jul 29 '15 at 0:29 di9it 1 1 While this is generally good