linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
To: Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org>
Cc: linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: New bug?
Date: Wed, 19 Feb 2014 08:45:29 +0100	[thread overview]
Message-ID: <CAMuHMdUTVAey=9rmU0xRomEomBk1erMoH-jnu8Szg=OcZWbLog@mail.gmail.com> (raw)
In-Reply-To: <1392795133.984411895-P0ORxJMC3jVsdVUOrk1QfQ@public.gmane.org>

On Wed, Feb 19, 2014 at 8:32 AM, Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org> wrote:
> During testing functions transfer_one(), stumbled upon an error.
> I'm using kernel 3.13, so I had to apply a patch from upstream
> (spi: core: Fix transfer failure when master->transfer_one returns positive value).
> After applying all becomes normal with probing, but where did the error
> "Unable to handle kernel NULL pointer dereference" ?
> Did someone have similar bugs?
>
> Thanks.
>
> spi_master spi0: failed to transfer one message from queue: 1
> 74x164 spi0.1: Failed writing: 1
> 74x164: probe of spi0.1 failed with error 1
> Unable to handle kernel NULL pointer dereference at virtual address 00000020
> CAN device driver interface
> pgd = c0024000
> [00000020] *pgd=00000000
> Internal error: Oops: 63c11805 [#1] PREEMPT ARM
> CPU: 0 PID: 22 Comm: spi0 Not tainted 3.13.3 #1
> task: c396b260 ti: c396e000 task.ti: c396e000
> PC is at spi_pump_messages+0x150/0x194

Have you applied other patches from upstream?

E.g. e120cc0dcf2880a4c5c0a6cb27b655600a1cfa1d introduced a NULL
pointer dereference, with got fixed by
1f802f8249a0da536877842c43c7204064c4de8b.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-02-19  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  7:32 New bug? Alexander Shiyan
     [not found] ` <1392795133.984411895-P0ORxJMC3jVsdVUOrk1QfQ@public.gmane.org>
2014-02-19  7:45   ` Geert Uytterhoeven [this message]
     [not found]     ` <CAMuHMdUTVAey=9rmU0xRomEomBk1erMoH-jnu8Szg=OcZWbLog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-19 11:20       ` Alexander Shiyan
     [not found]         ` <1392808849.211941090-PR9Oqn8FVc1sdVUOrk1QfQ@public.gmane.org>
2014-02-19 11:46           ` Mark Brown
2014-02-19 12:06           ` Geert Uytterhoeven
     [not found]             ` <CAMuHMdVBY7M=dkegw_3pQ7yFSLLEe2T6pXidY=eL7oiYAXXoPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-20 19:51               ` Geert Uytterhoeven

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='CAMuHMdUTVAey=9rmU0xRomEomBk1erMoH-jnu8Szg=OcZWbLog@mail.gmail.com' \
    --to=geert-td1emuhucqxl1znqvxdv9g@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shc_work-JGs/UdohzUI@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).