public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: NiTr0 <nitr0-z9XQkeP78BxUq1AO9QMCaQ@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: i2c_smbus_write_block_data vs scheduled routine calls (add_timer) - kernel crash
Date: Tue, 04 Aug 2009 21:42:41 +0300	[thread overview]
Message-ID: <4A788121.8020601@seti.kr.ua> (raw)

I tried to improve voltage/FSB manipulation module for EeePC 
(http://code.google.com/p/eeepc-linux) - and I found that 
i2c_smbus_write_block_data will cause kernel panic when is called from 
function called by timer. I can't see kernel panic message because 
system print very long call trace. Also on EeePC there is no RS232 port 
- but I have USB->RS232 dongle, can it be used as terminal for debug 
messages?

All variables are declared as static, all data is prepared correctly - 
so IMHO trouble is outside of my driver.
There is a part of code:

static struct i2c_client eee_pll_smbus_client = {
        .adapter = NULL,
        .addr = 0x69,
        .flags = 0,
};
static char eee_pll_data[I2C_SMBUS_BLOCK_MAX];
static int eee_pll_datalen = 0;
.......................
        i2c_smbus_write_block_data(&eee_pll_smbus_client,0, 
eee_pll_datalen, eee_pll_data);

             reply	other threads:[~2009-08-04 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 18:42 NiTr0 [this message]
     [not found] ` <4A788121.8020601-z9XQkeP78BxUq1AO9QMCaQ@public.gmane.org>
2009-08-04 19:45   ` i2c_smbus_write_block_data vs scheduled routine calls (add_timer) - kernel crash Matthias Kaehlcke
2009-08-04 20:35   ` Mark Brown

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=4A788121.8020601@seti.kr.ua \
    --to=nitr0-z9xqkep78bxuq1ao9qmcaq@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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