[agl-discussions] Kernel Panic
vishnu Tadepalli
vishnu.tvrprasad at gmail.com
Fri Feb 9 17:50:58 UTC 2018
Looks like the partitions are not created on eMMC.
On Fri, Feb 9, 2018 at 11:48 AM, <
automotive-discussions-request at lists.linuxfoundation.org> wrote:
> Send automotive-discussions mailing list submissions to
> automotive-discussions at lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.linuxfoundation.org/mailman/listinfo/
> automotive-discussions
>
> or, via email, send a message with subject or body 'help' to
> automotive-discussions-request at lists.linuxfoundation.org
>
> You can reach the person managing the list at
> automotive-discussions-owner at lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of automotive-discussions digest..."
>
>
> Today's Topics:
>
> 1. Kernel Panic. (Maksim Sisov)
> 2. Re: Kernel Panic. (Lo?c)
> 3. Re: Kernel Panic. (Stephen Lawrence)
> 4. Re: Kernel Panic. (Maksim Sisov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 09 Feb 2018 17:12:26 +0200
> From: Maksim Sisov <msisov at igalia.com>
> To: automotive-discussions at lists.linuxfoundation.org
> Subject: [agl-discussions] Kernel Panic.
> Message-ID: <357b346f1a8aefbe245d05e31130265e at igalia.com>
> Content-Type: text/plain; charset=US-ASCII
>
> Hi!
>
> I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3
> board. But for some reason I got kernel panic when I booted my board.
>
> The error is the following:
>
> [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or
> unknown-block(179,1): error -6
> [ 2.590933] Please append a correct "root=" boot option; here are the
> available partitions:
> [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver:
> mmcblk
> [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245]
> (driver?)
> [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918]
> (driver?)
> [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591]
> (driver?)
> [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(179,1)
> [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
> 4.9.0-yocto-standard #1
> [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 (DT)
> [ 2.648098] Call trace:
> [ 2.650563] [<ffff0000080883d0>] dump_backtrace+0x0/0x1a0
> [ 2.655988] [<ffff000008088584>] show_stack+0x14/0x20
> [ 2.661065] [<ffff00000837e3e4>] dump_stack+0x94/0xb8
> [ 2.666142] [<ffff0000081675d4>] panic+0x110/0x278
> [ 2.670959] [<ffff000008e41134>] mount_block_root+0x184/0x25c
> [ 2.677963] [<ffff000008e41328>] mount_root+0x11c/0x134
> [ 2.684417] [<ffff000008e4147c>] prepare_namespace+0x13c/0x184
> [ 2.691476] [<ffff000008e40d70>] kernel_init_freeable+0x224/0x248
> [ 2.698797] [<ffff0000089cb578>] kernel_init+0x10/0x100
> [ 2.705241] [<ffff000008082e80>] ret_from_fork+0x10/0x50
> [ 2.711762] SMP: stopping secondary CPUs
> [ 2.716897] Kernel Offset: disabled
> [ 2.721585] Memory Limit: none
> [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block(179,1)
>
> I've checked the env, and they looked ok for me. Am I missing something?
>
>
> => printenv
> baudrate=115200
> bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro
> rootfstype=ext4
> bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
> bootdelay=3
> fdt_high=0xffffffffffffffff
> initrd_high=0xffffffffffffffff
> load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb
> load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
> stderr=serial
> stdin=serial
> stdout=serial
> ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04)
>
> Environment size: 459/131068 bytes
>
> Best regards,
> Maksim
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 9 Feb 2018 16:14:40 +0100
> From: Lo?c Collignon [ IoT.bzh ] <loic.collignon at iot.bzh>
> To: Maksim Sisov <msisov at igalia.com>
> Cc: automotive-discussions at lists.linuxfoundation.org
> Subject: Re: [agl-discussions] Kernel Panic.
> Message-ID:
> <CAKV7wd0WVnmtu2M_bEZ7NHLVSzGKxZCL9-u0cP9_Lbk+
> pyCC_w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi!
> mmcblk1p1 is for situation where you have the kingfisher extension board.
> Try to change it to mmcblk0p1, when you use only the M3.
>
> Regards,
> Lo?c Collignon [IoT.bzh]
>
> 2018-02-09 16:12 GMT+01:00 Maksim Sisov <msisov at igalia.com>:
>
> > Hi!
> >
> > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3
> > board. But for some reason I got kernel panic when I booted my board.
> >
> > The error is the following:
> >
> > [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or
> > unknown-block(179,1): error -6
> > [ 2.590933] Please append a correct "root=" boot option; here are the
> > available partitions:
> > [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver:
> > mmcblk
> > [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245]
> > (driver?)
> > [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918]
> > (driver?)
> > [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591]
> > (driver?)
> > [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root fs
> > on unknown-block(179,1)
> > [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
> > 4.9.0-yocto-standard #1
> > [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 (DT)
> > [ 2.648098] Call trace:
> > [ 2.650563] [<ffff0000080883d0>] dump_backtrace+0x0/0x1a0
> > [ 2.655988] [<ffff000008088584>] show_stack+0x14/0x20
> > [ 2.661065] [<ffff00000837e3e4>] dump_stack+0x94/0xb8
> > [ 2.666142] [<ffff0000081675d4>] panic+0x110/0x278
> > [ 2.670959] [<ffff000008e41134>] mount_block_root+0x184/0x25c
> > [ 2.677963] [<ffff000008e41328>] mount_root+0x11c/0x134
> > [ 2.684417] [<ffff000008e4147c>] prepare_namespace+0x13c/0x184
> > [ 2.691476] [<ffff000008e40d70>] kernel_init_freeable+0x224/0x248
> > [ 2.698797] [<ffff0000089cb578>] kernel_init+0x10/0x100
> > [ 2.705241] [<ffff000008082e80>] ret_from_fork+0x10/0x50
> > [ 2.711762] SMP: stopping secondary CPUs
> > [ 2.716897] Kernel Offset: disabled
> > [ 2.721585] Memory Limit: none
> > [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> > root fs on unknown-block(179,1)
> >
> > I've checked the env, and they looked ok for me. Am I missing something?
> >
> >
> > => printenv
> > baudrate=115200
> > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro
> > rootfstype=ext4
> > bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
> > bootdelay=3
> > fdt_high=0xffffffffffffffff
> > initrd_high=0xffffffffffffffff
> > load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb
> > load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
> > stderr=serial
> > stdin=serial
> > stdout=serial
> > ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04)
> >
> > Environment size: 459/131068 bytes
> >
> > Best regards,
> > Maksim
> > _______________________________________________
> > automotive-discussions mailing list
> > automotive-discussions at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/
> automotive-discussions
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.linuxfoundation.org/pipermail/automotive-
> discussions/attachments/20180209/d462ebec/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 9 Feb 2018 15:46:51 +0000
> From: Stephen Lawrence <stephen.lawrence at renesas.com>
> To: Maksim Sisov <msisov at igalia.com>
> Cc: "automotive-discussions at lists.linuxfoundation.org"
> <automotive-discussions at lists.linuxfoundation.org>
> Subject: Re: [agl-discussions] Kernel Panic.
> Message-ID:
> <HK2PR0601MB20207E16B51DF83EAFD6CB2792F20 at HK2PR0601MB2020.
> apcprd06.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi
>
> > -----Original Message-----
> > From: automotive-discussions-bounces at lists.linuxfoundation.org
> > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On
> > Behalf Of Maksim Sisov
> > Sent: 09 February 2018 15:12
> > To: automotive-discussions at lists.linuxfoundation.org
> > Subject: [agl-discussions] Kernel Panic.
> >
> > Hi!
> >
> > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3
> > board. But for some reason I got kernel panic when I booted my board.
> >
>
> [snip]
>
> > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro
>
> I'm not familiar with the AGL image setup but should it be rw, not ro?
>
> Regards
>
> Steve
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 09 Feb 2018 18:48:45 +0200
> From: Maksim Sisov <msisov at igalia.com>
> To: Lo?c Collignon [ IoT.bzh ] <loic.collignon at iot.bzh>
> Cc: automotive-discussions at lists.linuxfoundation.org
> Subject: Re: [agl-discussions] Kernel Panic.
> Message-ID: <8fa1c61b15b81a8a154db83b537d0f98 at igalia.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi!
>
> On 09.02.2018 17:14, Lo?c Collignon [ IoT.bzh ] wrote:
> > Hi!
> > mmcblk1p1 is for situation where you have the kingfisher extension
> > board.
> >
> > Try to change it to mmcblk0p1, when you use only the M3.
>
> Thanks! It helped!
>
> Regards,
> Maksim
> >
> > Regards,
> > Lo?c Collignon [IoT.bzh]
> > 2018-02-09 16:12 GMT+01:00 Maksim Sisov <msisov at igalia.com>:
> >
> >> Hi!
> >>
> >> I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3
> >> board. But for some reason I got kernel panic when I booted my
> >> board.
> >>
> >> The error is the following:
> >>
> >> [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or
> >> unknown-block(179,1): error -6
> >> [ 2.590933] Please append a correct "root=" boot option; here are
> >> the
> >> available partitions:
> >> [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver:
> >> mmcblk
> >> [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245]
> >> (driver?)
> >> [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918]
> >> (driver?)
> >> [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591]
> >> (driver?)
> >> [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root
> >> fs
> >> on unknown-block(179,1)
> >> [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
> >> 4.9.0-yocto-standard #1
> >> [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796
> >> (DT)
> >> [ 2.648098] Call trace:
> >> [ 2.650563] [<ffff0000080883d0>] dump_backtrace+0x0/0x1a0
> >> [ 2.655988] [<ffff000008088584>] show_stack+0x14/0x20
> >> [ 2.661065] [<ffff00000837e3e4>] dump_stack+0x94/0xb8
> >> [ 2.666142] [<ffff0000081675d4>] panic+0x110/0x278
> >> [ 2.670959] [<ffff000008e41134>] mount_block_root+0x184/0x25c
> >> [ 2.677963] [<ffff000008e41328>] mount_root+0x11c/0x134
> >> [ 2.684417] [<ffff000008e4147c>] prepare_namespace+0x13c/0x184
> >> [ 2.691476] [<ffff000008e40d70>] kernel_init_freeable+0x224/0x248
> >> [ 2.698797] [<ffff0000089cb578>] kernel_init+0x10/0x100
> >> [ 2.705241] [<ffff000008082e80>] ret_from_fork+0x10/0x50
> >> [ 2.711762] SMP: stopping secondary CPUs
> >> [ 2.716897] Kernel Offset: disabled
> >> [ 2.721585] Memory Limit: none
> >> [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to
> >> mount
> >> root fs on unknown-block(179,1)
> >>
> >> I've checked the env, and they looked ok for me. Am I missing
> >> something?
> >>
> >> => printenv
> >> baudrate=115200
> >> bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro
> >> rootfstype=ext4
> >> bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
> >> bootdelay=3
> >> fdt_high=0xffffffffffffffff
> >> initrd_high=0xffffffffffffffff
> >> load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb
> >> load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
> >> stderr=serial
> >> stdin=serial
> >> stdout=serial
> >> ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04)
> >>
> >> Environment size: 459/131068 bytes
> >>
> >> Best regards,
> >> Maksim
> >> _______________________________________________
> >> automotive-discussions mailing list
> >> automotive-discussions at lists.linuxfoundation.org
> >>
> > https://lists.linuxfoundation.org/mailman/listinfo/
> automotive-discussions
> >> [1]
> >
> >
> >
> > Links:
> > ------
> > [1] https://lists.linuxfoundation.org/mailman/listinfo/
> automotive-discussions
>
>
> ------------------------------
>
> _______________________________________________
> automotive-discussions mailing list
> automotive-discussions at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
>
>
> End of automotive-discussions Digest, Vol 61, Issue 15
> ******************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/automotive-discussions/attachments/20180209/f72647b9/attachment-0001.html>
More information about the automotive-discussions
mailing list