Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no camera at 3.12 #434

Closed
oklitz opened this issue Nov 16, 2013 · 7 comments
Closed

no camera at 3.12 #434

oklitz opened this issue Nov 16, 2013 · 7 comments
Assignees
@popcornmix

Comments

@oklitz
Copy link

oklitz commented Nov 16, 2013

Hello !

When I boot with 3.12 dmesg:
[ 0.000000] vc_cma: dma_declare_contiguous(11800000,d400000) failed

and raspivid says:

mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: camera component couldn't be enabled
mmal: main: Failed to create camera component
mmal: Failed to run camera app. Please check for firmware updates

when i'm running 3.10.18 its all OK !
just changing the kernel, and no changes on config files

need more info ?

mfg Marco Oklitz
@crashmaster1
Copy link

Hello Marco,
i agree.
Never before the cam has worked with experimental kernel versions (not only 3.12).
3.10.18 comes from the official branch, this works.
I would also appreciate to see it working with the latest test versions . ;)
greets, cm1

@JamesH65
Copy link
Contributor

Weird. Never seen problems like this - are you using any odd HW attached to your PI's?

@moonman
Copy link

moonman commented Nov 17, 2013

The important clue is this line: [ 0.000000] vc_cma: dma_declare_contiguous(11800000,d400000) failed

XBMC does not start because of this too.

@crashmaster1
Copy link

I only use wlan (8192cu) and raspicam on Model A but nothing else.

And i want to mention:
The RPi has two i2c busses, the cam works with bus 0 but "i2cdetect -y 0" shows:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 
50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 
70: 70 71 72 73 74 75 76 77

Very strange !

There should be lots of dashes like on bus 1 (i2cdetect -y 1):

      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

@crashmaster1
Copy link

It's me again ;)
I spent some time to find this bug now.

1wire (w1_gpio) in kernel versions >= 3.10 destroys the bus 0 structure of i2c (see my comment above).
This is a reason why raspicam doesn't work. If you don't need 1wire don't load this module and it will work fine. I opened a new thread for this.

@marco:
I guess you don't use 1wire and don't load the modules, so this is not your problem.
But check your config.txt. I commented:

# cma_lwm=...
# cma_hwm=...
# cma_offline_start=...

Now i have no "vc_cma: dma_declare_contiguous(11800000,d400000) failed" anymore and the cam works fine!

@ghost ghost assigned popcornmix Nov 18, 2013
@JamesH65
Copy link
Contributor

Dom, I've assigned this to you - bit out of my realm of expertise.

@JamesH65 JamesH65 mentioned this issue Nov 18, 2013
Closed
@notro notro mentioned this issue Dec 29, 2014
Closed
@popcornmix
Copy link
Collaborator

I believe this is resolved now. Reopen if needed.

davet321 pushed a commit to davet321/rpi-linux that referenced this issue Sep 30, 2015
@gregkh
blk-mq: fix buffer overflow when reading sysfs file of 'pending'
c4ae1ec 
commit 596f5aa upstream.

There may be lots of pending requests so that the buffer of PAGE_SIZE
can't hold them at all.

One typical example is scsi-mq, the queue depth(.can_queue) of
scsi_host and blk-mq is quite big but scsi_device's queue_depth
is a bit small(.cmd_per_lun), then it is quite easy to have lots
of pending requests in hw queue.

This patch fixes the following warning and the related memory
destruction.

[  359.025101] fill_read_buffer: blk_mq_hw_sysfs_show+0x0/0x7d returned bad count^M
[  359.055595] irq event stamp: 15537^M
[  359.055606] general protection fault: 0000 [raspberrypi#1] PREEMPT SMP DEBUG_PAGEALLOC ^M
[  359.055614] Dumping ftrace buffer:^M
[  359.055660]    (ftrace buffer empty)^M
[  359.055672] Modules linked in: nbd ipv6 kvm_intel kvm serio_raw^M
[  359.055678] CPU: 4 PID: 21631 Comm: stress-ng-sysfs Not tainted 4.2.0-rc5-next-20150805 raspberrypi#434^M
[  359.055679] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011^M
[  359.055682] task: ffff8802161cc000 ti: ffff88021b4a8000 task.ti: ffff88021b4a8000^M
[  359.055693] RIP: 0010:[<ffffffff811541c5>]  [<ffffffff811541c5>] __kmalloc+0xe8/0x152^M

Signed-off-by: Ming Lei <ming.lei@canonical.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
popcornmix pushed a commit that referenced this issue Oct 1, 2015
@gregkh
blk-mq: fix buffer overflow when reading sysfs file of 'pending'
1af9777 
commit 596f5aa upstream.

There may be lots of pending requests so that the buffer of PAGE_SIZE
can't hold them at all.

One typical example is scsi-mq, the queue depth(.can_queue) of
scsi_host and blk-mq is quite big but scsi_device's queue_depth
is a bit small(.cmd_per_lun), then it is quite easy to have lots
of pending requests in hw queue.

This patch fixes the following warning and the related memory
destruction.

[  359.025101] fill_read_buffer: blk_mq_hw_sysfs_show+0x0/0x7d returned bad count^M
[  359.055595] irq event stamp: 15537^M
[  359.055606] general protection fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC ^M
[  359.055614] Dumping ftrace buffer:^M
[  359.055660]    (ftrace buffer empty)^M
[  359.055672] Modules linked in: nbd ipv6 kvm_intel kvm serio_raw^M
[  359.055678] CPU: 4 PID: 21631 Comm: stress-ng-sysfs Not tainted 4.2.0-rc5-next-20150805 #434^M
[  359.055679] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011^M
[  359.055682] task: ffff8802161cc000 ti: ffff88021b4a8000 task.ti: ffff88021b4a8000^M
[  359.055693] RIP: 0010:[<ffffffff811541c5>]  [<ffffffff811541c5>] __kmalloc+0xe8/0x152^M

Signed-off-by: Ming Lei <ming.lei@canonical.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
popcornmix pushed a commit that referenced this issue Aug 15, 2020
@jpbrucker @borkmann
selftests/bpf: Fix cgroup sockopt verifier test
55b2442 
Since the BPF_PROG_TYPE_CGROUP_SOCKOPT verifier test does not set an
attach type, bpf_prog_load_check_attach() disallows loading the program
and the test is always skipped:

 #434/p perfevent for cgroup sockopt SKIP (unsupported program type 25)

Fix the issue by setting a valid attach type.

Fixes: 0456ea1 ("bpf: Enable more helpers for BPF_PROG_TYPE_CGROUP_{DEVICE,SYSCTL,SOCKOPT}")
Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com>
Link: https://lore.kernel.org/bpf/20200710150439.126627-1-jean-philippe@linaro.org
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@popcornmix popcornmix

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@moonman @popcornmix @JamesH65 @oklitz @crashmaster1