Hello Joao, IIRC we had that kind of error after a reboot. It seemed to come from an error in deviced but I'm not 100% sure.
It should not raise that error with the official Common 2015 Q2. BR José (from vcation... what explains the delay) 2015-07-06 21:40 GMT+02:00 Joao Marinho Assis <[email protected]>: > Hi José, > > I tried with 2 different builds to start the minimal image, but they > always give me this error: > > [ 0.454224] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 0.454319] sd 0:0:0:0: [sda] 1824688 512-byte logical blocks: (934 > MB/890 MiB) > [ 0.454363] sd 0:0:0:0: [sda] Write Protect is off > [ 0.454379] sd 0:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [ 0.458727] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM > 2.0. PQ: 0 ANSI: 5 > [ 0.461225] scsi 1:0:0:0: Attached scsi generic sg1 type 5 > [ 0.463854] sda: unknown partition table > [ 0.465275] sd 0:0:0:0: [sda] Attached SCSI disk > [ 0.466329] VFS: Cannot open root device "sda1" or unknown-block(8,1): > error -6 > [ 0.467695] Please append a correct "root=" boot option; here are the > available partitions: > [ 0.473829] 0800 912344 sda driver: sd > [ 0.474940] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,1) > [ 0.475691] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > 3.14.28+ltsi-25.5-common-x86_64-default #1 > [ 0.475691] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS > Bochs 01/01/2011 > [ 0.475691] 0000000000000000 ffff88003e057df8 ffffffff8154a64b > ffffffff8183f052 > [ 0.475691] ffff88003e057e78 ffffffff81549793 3830002000000010 > ffff88003e057e88 > [ 0.475691] ffff88003e057e20 ffffffff815499af ffff88003e057e90 > 0000000000000006 > [ 0.475691] Call Trace: > [ 0.475691] [<ffffffff8154a64b>] dump_stack+0x4d/0x6f > [ 0.475691] [<ffffffff81549793>] panic+0xbe/0x1bf > [ 0.475691] [<ffffffff815499af>] ? printk+0x4a/0x52 > [ 0.475691] [<ffffffff81ae0268>] mount_block_root+0x296/0x2a5 > [ 0.475691] [<ffffffff81ae02ca>] mount_root+0x53/0x56 > [ 0.475691] [<ffffffff81ae0404>] prepare_namespace+0x137/0x16f > [ 0.475691] [<ffffffff81adfef8>] kernel_init_freeable+0x1f5/0x205 > [ 0.475691] [<ffffffff81546c49>] ? rest_init+0x7d/0x7d > [ 0.475691] [<ffffffff81546c52>] kernel_init+0x9/0xd5 > [ 0.475691] [<ffffffff8154fe3c>] ret_from_fork+0x7c/0xb0 > [ 0.475691] [<ffffffff81546c49>] ? rest_init+0x7d/0x7d > [ 0.475691] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation > range: 0xffffffff80000000-0xffffffff9fffffff) > > Do you know what that might be? > > I tried tizen-common_20150507.1 and tizen-common_20150630.1, both have the > same issue. > > Thanks very much, > Joao Assis > > > -----Original Message----- > From: Dev [mailto:[email protected]] On Behalf Of José Bollo > Sent: quinta-feira, 7 de maio de 2015 06:02 > To: 'Tizen Dev' > Subject: [Dev] running tizen common minimal x86_64 using qemu > > Hi all, > > For your information, there is now an image minimal that can be run using > qemu. > > See the below link for more details > > https://wiki.tizen.org/wiki/Emulator#Tizen:Common_minimal_on_qemu > > Best regards > José Bollo > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > > >
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
