Re: DME1737 not recognized

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le Wednesday 17 September 2014 à 06:24 -0700, Guenter Roeck a écrit :
> On 09/17/2014 03:23 AM, Jean Delvare wrote:
> > For a better long-term solution, I need to check if irq = 255 is any
> > special, maybe it means that interrupt is not available or something and
> > we shouldn't even try to request it.
> >
> Looks suspiciously like a bad (uninitialized ?) interrupt number to me.

Apparently this was discussed previously:

https://lkml.org/lkml/2013/2/18/115

but the discussion ultimately resulted in a USB-specific quirk, which
won't help us at all in this specific case.

Scott, can you please provide the output of:
# /sbin/lspci -vvv -s 00:1f.3
# cat /proc/interrupts

Maybe it will reveal something interesting...

-- 
Jean Delvare
SUSE L3 Support


_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux