{"action":"closed","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/606","repository_url":"https://api.github.com/repos/raspberrypi/firmware","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/606/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/606/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/606/events","html_url":"https://github.com/raspberrypi/firmware/issues/606","id":157350411,"number":606,"title":"Kernel Panic on fedora","user":{"login":"sedrubal","id":5571650,"avatar_url":"https://avatars.githubusercontent.com/u/5571650?v=3","gravatar_id":"","url":"https://api.github.com/users/sedrubal","html_url":"https://github.com/sedrubal","followers_url":"https://api.github.com/users/sedrubal/followers","following_url":"https://api.github.com/users/sedrubal/following{/other_user}","gists_url":"https://api.github.com/users/sedrubal/gists{/gist_id}","starred_url":"https://api.github.com/users/sedrubal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sedrubal/subscriptions","organizations_url":"https://api.github.com/users/sedrubal/orgs","repos_url":"https://api.github.com/users/sedrubal/repos","events_url":"https://api.github.com/users/sedrubal/events{/privacy}","received_events_url":"https://api.github.com/users/sedrubal/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-28T18:09:45Z","updated_at":"2016-05-31T10:25:31Z","closed_at":"2016-05-31T10:25:31Z","body":"I did [this instructions](https://fedoraproject.org/wiki/Raspberry_Pi) to install Fedora on Raspberry PI. But even on the first boot there is a kernel panic. I tried `Fedora 23` and `Fedora 24 Beta` and `raspberry firmware 1.20160506` (with kernel 4.4.9) and current master (with kernel 4.4.11). It didn't changed anything.\r\n\r\nAfter 3 seconds after mounting root readonly and devtmpfs:\r\n\r\n```kernel\r\n[...]\r\nFreeing unused kernel memory: 300K (c07bb000 - c081a000)\r\n[...]\r\nhub 1-1:1.0 3 ports detected\r\nKernel panic - not syncing: Attempted to kill init! exitcode=0x00000004\r\n\r\nCPU: 0 PID: 1 Comm: init Not tainted 4.4.9+ #884\r\nHardware name: BCM2708\r\n[<c0016c9c>] (unwind_backtrace) from [<c0013c20>] (show_stack+0x20/0x24)\r\n[<c0013c20>] (show_stack) from [<c02e319c>] (dump_stack+0x20/0x28)\r\n[<c02e319c>] (dump_stack) from [<c00d7040>] (panic+0x8c/0x1f4)\r\n[<c00d7040>] (panic) from [<c00243c8>] (do_exit+0x4c/0xc0)\r\n[<...>] (do_exit) ...\r\n[<...>] (do_group_exit) ...\r\n[<...>] (get_signal) ...\r\n[<...>] (do_signal) ...\r\n[<...>] (do_work_pending) ...\r\n---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004]\r\n```\r\n\r\nI did set `SELINUX=0` and touched `/.autorelabel` but I think it seems not to be a SELinux problem..."}}
{"actor":{"display_login":"popcornmix"}}