All of lore.kernel.org
 help / color / mirror / Atom feed
From: j.w.r.degoede@hhs.nl (Hans de Goede)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] new abituguru driver in mm kernel
Date: Sun, 09 Jul 2006 17:11:33 +0000	[thread overview]
Message-ID: <44B138C5.6060705@hhs.nl> (raw)
In-Reply-To: <ce9ef0d90607041146t6837a584x68d1ab7e528139ea@mail.gmail.com>



Sunil Kumar wrote:
> Ok, now another problem. Some of the times the module loads fine during
> bootup but sensors reports that
> 
> $ sensors
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and libsensors
> was compiled with sysfs support!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> 
> If I rmmod abituguru and modprobe it again, it works. I will rebuild the
> module and see if it helps.
> 
> The fallout of this is that gkrellm forgets about my sensors permanently. I
> have to re-enable them and re-assign the labels etc....:(
> 

Yes, this is because the module loads, but the driver part of it doesn't
(new driver model, where drivers can be registered without actually
handling any devices, so they can be bound to hotplug devices lateR).


The driver part probably fails to load because it happens to run into
those errors you report during the initialisation fase. Strange though
as during init it retries all things 3 times, which goes to show that
indeed your uGuru is unwilling to talk for a while, as seen before with
early uGurus, what motherboard do you have. Lemme gues one out of this
list? : AI7, KV8-MAX3, AN7


Regards,

Hans




> Thanks,
> -Sunil
> 
> On 7/9/06, Sunil Kumar < devsku at gmail.com> wrote:
>>
>> they always occurr in a bunch but they are scattered all over time,
>> sometimes disappearing for many hours and then returning.
>>
>>
>> On 7/9/06, Hans de Goede < j.w.r.degoede at hhs.nl> wrote:
>> >
>> >
>> >
>> > Sunil Kumar wrote:
>> > > Hi Hans,
>> > >
>> > > I am seeing these messages in the dmesg:
>> > >
>> > > abituguru: timeout exceeded waiting for ready state
>> > > abituguru: timeout exceeded waiting for ready state
>> > > abituguru: timeout exceeded waiting for read state (bank: 34, sensor:
>> > 15)
>> > > abituguru: CMD reg does not hold 0xAC after ready command
>> > > abituguru: timeout exceeded waiting for read state (bank: 38, sensor:
>> > 2)
>> > > abituguru: timeout exceeded waiting for ready state
>> > >
>> >
>> > Hmm, were these messages close together in time, or now and then a
>> > message?
>> >
>> > > I am not sure if they are related to a freeze I saw today. My machine
>> > > wasn't
>> > > being used and when I came back, it was frozen.
>> >
>> > I seriously doubt the freeze and these messages are related. The uGuru
>> > only uses 2 io ports todo all communication with the outside. So
>> reading
>> >
>> > the ports doesn't always get you the same register there is a sortoff
>> > network protocol which you speak over the ports. These messages mean
>> > that the uGuru failed to response within a reasonable time. Unfortunate
>> > on some uGuru's this is quite normal. It seems the older the
>> > Motherboard, the more often this happens (iow the buggier the uGuru
>> > firmware).
>> >
>> > Regards,
>> >
>> > Hans
>> >
>>
>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


  parent reply	other threads:[~2006-07-09 17:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 18:46 [lm-sensors] new abituguru driver in mm kernel Sunil Kumar
2006-07-04 20:10 ` Stephen Cormier
2006-07-05  6:38 ` Hans de Goede
2006-07-05 16:35 ` Sunil Kumar
2006-07-05 17:37 ` Jean Delvare
2006-07-05 17:41 ` Hans de Goede
2006-07-05 17:44 ` Hans de Goede
2006-07-05 20:11 ` Hans de Goede
2006-07-05 20:16 ` Sunil Kumar
2006-07-06  1:09 ` Sunil Kumar
2006-07-06  1:24 ` Stephen Cormier
2006-07-08 23:03 ` Sunil Kumar
2006-07-09  8:16 ` Hans de Goede
2006-07-09 14:44 ` Sunil Kumar
2006-07-09 16:41 ` Sunil Kumar
2006-07-09 17:11 ` Hans de Goede [this message]
2006-07-09 17:30 ` Sunil Kumar
2006-07-09 20:32 ` Hans de Goede
2006-07-09 20:54 ` Sunil Kumar
2006-07-10  4:33 ` Hans de Goede
2006-07-11  4:43 ` Sunil Kumar
2006-07-14 19:15 ` Hans de Goede
2006-07-14 19:33 ` Sunil Kumar
2006-07-14 19:43 ` Hans de Goede
2006-07-14 19:50 ` Sunil Kumar
2006-07-15  0:52 ` Sunil Kumar
2006-07-19  4:35 ` Hans de Goede
2006-07-19 20:34 ` Sunil Kumar
2006-07-19 22:42 ` Sunil Kumar
2006-07-19 23:02 ` Sunil Kumar
2006-07-20  5:23 ` Sunil Kumar
2006-07-20  7:54 ` Hans de Goede
2006-07-20 14:37 ` Sunil Kumar
2006-07-20 17:13 ` Sunil Kumar
2006-07-20 17:14 ` Sunil Kumar
2006-07-21  6:10 ` Hans de Goede
2006-07-21 16:15 ` Sunil Kumar
2006-07-25  3:27 ` Sunil Kumar
2006-07-26 14:30 ` Hans de Goede
2006-07-26 18:32 ` Sunil Kumar
2006-07-26 20:43 ` Hans de Goede
2006-07-27  0:48 ` Sunil Kumar
2006-07-27  8:19 ` Hans de Goede
2006-07-27 14:31 ` Sunil Kumar
2006-07-27 14:44 ` Hans de Goede
2006-07-27 16:07 ` Sunil Kumar
2006-08-01  4:01 ` Hans de Goede
2006-08-25 23:13 ` Sunil Kumar

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=44B138C5.6060705@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --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.