From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Ohad Ben-Cohen <ohad@wizery.com>, Tero Kristo <t-kristo@ti.com>,
linux-omap mailing list <linux-omap@vger.kernel.org>
Subject: linux-next problems
Date: Thu, 12 Jan 2012 17:38:09 +0200 [thread overview]
Message-ID: <1326382689.1896.12.camel@deskari> (raw)
[-- Attachment #1: Type: text/plain, Size: 3507 bytes --]
Hi,
I was trying to compile linux-next for OMAP, but it doesn't compile with
the default configs.
drivers/remoteproc/remoteproc_rpmsg.c: In function 'rp_find_vq':
drivers/remoteproc/remoteproc_rpmsg.c:100:6: warning: passing argument 7 of 'vring_new_virtqueue' from incompatible pointer type
include/linux/virtio_ring.h:168:19: note: expected 'void (*)(struct virtqueue *)' but argument is of type 'const char *'
drivers/remoteproc/remoteproc_rpmsg.c:100:6: error: too few arguments to function 'vring_new_virtqueue'
include/linux/virtio_ring.h:168:19: note: declared here
make[2]: *** [drivers/remoteproc/remoteproc_rpmsg.o] Error 1
and
arch/arm/mach-omap2/prm_common.c:27:25: fatal error: mach/system.h: No such file or directory
compilation terminated.
Fixing those, I was able to boot Blaze, but I saw this:
[ 2.296905] mmc0: new high speed MMC card at address 0001
[ 2.304199] mmcblk0: mmc0:0001 SEM08G 7.39 GiB
[ 2.309326] mmcblk0boot0: mmc0:0001 SEM08G partition 1 1.00 MiB
[ 2.315826] mmcblk0boot1: mmc0:0001 SEM08G partition 2 1.00 MiB
[ 2.329925] mmcblk0: unknown partition table
[ 2.338195] mmcblk0boot1: unknown partition table
[ 2.343811] BUG: key de7aeef4 not in .data!
[ 2.343811] ------------[ cut here ]------------
[ 2.353057] WARNING: at kernel/lockdep.c:2986 sysfs_add_file_mode+0x84/0xe8()
[ 2.360534] Modules linked in:
[ 2.363800] [<c001b634>] (unwind_backtrace+0x0/0xf0) from [<c00424ec>] (warn_slowpath_common+0x4c
/0x64)
[ 2.373657] [<c00424ec>] (warn_slowpath_common+0x4c/0x64) from [<c0042520>] (warn_slowpath_null+0
x1c/0x24)
[ 2.383789] [<c0042520>] (warn_slowpath_null+0x1c/0x24) from [<c0167128>] (sysfs_add_file_mode+0x
84/0xe8)
[ 2.393829] [<c0167128>] (sysfs_add_file_mode+0x84/0xe8) from [<c0391234>] (mmc_add_disk+0xb4/0x1
00)
[ 2.403442] [<c0391234>] (mmc_add_disk+0xb4/0x100) from [<c03918b0>] (mmc_blk_probe+0x27c/0x2c8)
[ 2.412658] [<c03918b0>] (mmc_blk_probe+0x27c/0x2c8) from [<c03855d4>] (mmc_bus_probe+0x18/0x1c)
[ 2.421874] [<c03855d4>] (mmc_bus_probe+0x18/0x1c) from [<c02af6d8>] (driver_probe_device+0x98/0x
1a0)
[ 2.431579] [<c02af6d8>] (driver_probe_device+0x98/0x1a0) from [<c02adfd0>] (bus_for_each_drv+0x5
c/0x88)
[ 2.441528] [<c02adfd0>] (bus_for_each_drv+0x5c/0x88) from [<c02af570>] (device_attach+0x98/0xbc)
[ 2.450836] [<c02af570>] (device_attach+0x98/0xbc) from [<c02aedac>] (bus_probe_device+0x88/0xac)
[ 2.450836] [<c02aedac>] (bus_probe_device+0x88/0xac) from [<c02ad0cc>] (device_add+0x538/0x60c)
[ 2.469360] [<c02ad0cc>] (device_add+0x538/0x60c) from [<c038591c>] (mmc_add_card+0xb8/0x1bc)
[ 2.469360] [<c038591c>] (mmc_add_card+0xb8/0x1bc) from [<c0387ff0>] (mmc_attach_mmc+0xdc/0x1d0)
[ 2.487518] [<c0387ff0>] (mmc_attach_mmc+0xdc/0x1d0) from [<c0385118>] (mmc_rescan+0x230/0x45c)
[ 2.496612] [<c0385118>] (mmc_rescan+0x230/0x45c) from [<c005b444>] (process_one_work+0x18c/0x4e4
)
[ 2.506042] [<c005b444>] (process_one_work+0x18c/0x4e4) from [<c005df9c>] (worker_thread+0x174/0x
378)
[ 2.513153] [<c005df9c>] (worker_thread+0x174/0x378) from [<c0062ac8>] (kthread+0x90/0x9c)
[ 2.520935] [<c0062ac8>] (kthread+0x90/0x9c) from [<c0014e04>] (kernel_thread_exit+0x0/0x8)
[ 2.533172] ---[ end trace 27dad9159f211429 ]---
On OMAP3 Overo, I didn't get any errors, but the console (usb one) was
very unresponsive, impossible to use. Ssh terminal to the device worked
fine, though.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-01-12 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 15:38 Tomi Valkeinen [this message]
2012-01-12 15:58 ` linux-next problems Ohad Ben-Cohen
2012-01-12 16:05 ` Tomi Valkeinen
2012-01-12 16:11 ` Ohad Ben-Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1326382689.1896.12.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=t-kristo@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox