From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Kernel hangs with i2c-i801 driver?
Date: Sat, 10 Dec 2005 09:14:30 +0000 [thread overview]
Message-ID: <439A9C76.6080906@sh.cvut.cz> (raw)
In-Reply-To: <20051123100021.GA29473@oden.homeip.net>
Hello all
> The simple drawings didn't have either pin names or numbers so I wrote
> back to GBT support asking for this additional piece of information.
>
> Now, assuming that we have this piece of information, how would we use
> it? I guess we could disable that GPIO somehow, but that fix is very
> specific to this motherboard... Isn't it likely that other motherboard
> would need some similar patch to prevent this kind of issue?
Yes this is verys specific to this motherboard, question is
1) why the SMI is generated when setting limits?
(Possible answer like Yuan suggested that the fans limit are above zero? (and readings are 0)
But this whould mean that actually writing to registeters will somehow do SMI which is I must admit strange
Unfortunately I'm very busy this weeks so I dont have much time left to dig in the chip dumps.
Perhaps someone else could spot why the SMI is generated?
2) why it hangs
> I guess what I'm wondering is, is it hard to support the SMI
> functionality and would that be a more generic solution that would
> make the kernel survive the SMI? Or is the issue rather with a GPIO
> setup as an interrupt triggering an interrupt for which there is no
> handler installed?
SMI is a very special interrupt. It is completly transparent to operating system. When
SMI will come it will switch the processor to so called System Management Mode.
It is similar to real mode but limited to small piece of memory. Even you cant find
the SMM routine in memory because it its "hidden" bellow the video RAM (0x0A0000) (ususally)
If this routine has a bug it will hang...
You can spot the SMI only by measuring clock in system. You wont notice if smi ever occured.
(SMI is rather anoying for realtime stuff on x86)
Lets try:
Generate the SMI from other source than the fans limits (if it hangs too)
Then we will know if the complete handler is wrong or only parts.
Also are you using HIGHMEM support in kernel? I guess this might be right reason why it fails
(Due to 4MB PAE)
If so please disable and try all stuff again. If it wont freeze we spot the bug.
So what to do:
1) why is SMI generated when writing limits?
2) if SMI fan event is specific to hang or any other SMI will hang too.
3) what about highmem?
Regards
Rudolf
next prev parent reply other threads:[~2005-12-10 9:14 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 11:01 [lm-sensors] Kernel hangs with i2c-i801 driver? Daniel Nilsson
2005-11-23 13:18 ` Jean Delvare
2005-11-23 14:12 ` Daniel Nilsson
2005-11-23 14:17 ` Keith
2005-11-23 15:24 ` Henrique de Moraes Holschuh
2005-11-23 15:52 ` Jean Delvare
2005-11-23 15:53 ` Keith
2005-11-23 16:06 ` Keith
2005-11-23 16:22 ` Jean Delvare
2005-11-23 18:53 ` Henrique de Moraes Holschuh
2005-11-23 20:02 ` Henrique de Moraes Holschuh
2005-11-23 22:36 ` Jean Delvare
2005-11-24 2:58 ` Henrique de Moraes Holschuh
2005-11-25 17:51 ` Mark M. Hoffman
2005-11-25 17:54 ` Mark M. Hoffman
2005-11-25 20:52 ` Rudolf Marek
2005-11-26 8:54 ` Daniel Nilsson
2005-11-26 10:36 ` Jean Delvare
2005-11-28 13:32 ` Jean Delvare
2005-11-28 18:50 ` Daniel Nilsson
2005-11-28 20:07 ` Daniel Nilsson
2005-11-29 16:26 ` Jean Delvare
2005-11-30 23:11 ` Rudolf Marek
2005-12-01 22:29 ` Daniel Nilsson
2005-12-02 9:58 ` Rudolf Marek
2005-12-03 20:57 ` Daniel Nilsson
2005-12-05 8:19 ` Rudolf Marek
2005-12-05 11:16 ` Ymu
2005-12-05 18:41 ` Daniel Nilsson
2005-12-06 2:10 ` Ymu
2005-12-07 8:20 ` Daniel Nilsson
2005-12-07 9:59 ` Ymu
2005-12-07 11:08 ` Henrique de Moraes Holschuh
2005-12-07 20:06 ` Daniel Nilsson
2005-12-08 7:46 ` Ymu
2005-12-08 21:22 ` Jean Delvare
2005-12-09 2:10 ` Henrique de Moraes Holschuh
2005-12-09 2:47 ` Ymu
2005-12-09 6:06 ` Daniel Nilsson
2005-12-09 12:26 ` Henrique de Moraes Holschuh
2005-12-10 9:14 ` Rudolf Marek [this message]
2005-12-13 22:06 ` Daniel Nilsson
2005-12-15 19:15 ` Daniel Nilsson
2005-12-16 11:59 ` Henrique de Moraes Holschuh
2005-12-16 19:59 ` Rudolf Marek
2005-12-29 17:04 ` Daniel Nilsson
2005-12-29 17:49 ` Rudolf Marek
2006-01-07 12:54 ` Daniel Nilsson
2006-01-07 20:42 ` Rudolf Marek
2006-01-08 14:31 ` Daniel Nilsson
2006-01-11 20:31 ` Daniel Nilsson
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=439A9C76.6080906@sh.cvut.cz \
--to=r.marek@sh.cvut.cz \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.