From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: linux-omap-open-source@linux.omap.com
Subject: SPI related oops
Date: Thu, 18 Jan 2007 20:44:58 +0100 [thread overview]
Message-ID: <85mz4gdsqt.fsf@orfeo.duckcorp.org> (raw)
Hi,
Since some time ago I was seeing a reboot as long as my n770 was
booting recent kernels from the omap git. Now, I found out that the
crash is due to a oops as soon as udev plays with the uevent file of the
spi master.
After some debugging, I found that the following commit is the culprit :
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=3bd0f6943520e459659d10f3282285e43d3990f1
Reverting it allows my kernel to boot but I think it's not a real
fix. Has someone seen a similar issue and has a fix for it ?
[ Also, I'm wondering why the spi_busnum_to_master() function exists
because grepping the current omap git tree gives 0 user... ]
Regards,
Arnaud
next reply other threads:[~2007-01-18 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 19:44 Arnaud Patard [this message]
2007-01-19 23:43 ` SPI related oops David Brownell
2007-01-20 13:09 ` Arnaud Patard
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=85mz4gdsqt.fsf@orfeo.duckcorp.org \
--to=arnaud.patard@rtp-net.org \
--cc=linux-omap-open-source@linux.omap.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