On 12/20/2013 06:36 AM, Paul Walmsley wrote: > Hi Jean, > > On Thu, 19 Dec 2013, Jean Delvare wrote: > >> Adding Wei who added interrupt support to the lm90 driver, and moving >> to the appropriate list. > > Thanks for the speedy response and list correction. > >> On Thu, 19 Dec 2013 02:08:45 -0800, Paul Walmsley wrote: >>> Just FYI, the Tegra114 Dalmore board here reports an unhandled IRQ about >>> two minutes after boot: >>> >>> [ 120.950839] irq 308: nobody cared (try booting with the "irqpoll" option) > > ... > >>> [ 121.019825] handlers: >>> [ 121.022117] [<c0064408>] irq_default_primary_handler threaded >>> [<c0384764>] lm90_irq_thread >>> [ 121.030418] Disabling IRQ #308 >>> >>> This is on next-20131218. >> >> Which temperature chip is the Tegra114 Dalmore board using? > > It's an NCT72. > >> Is the interrupt shared with something else? > > Doesn't look like it. From /proc/interrupts: > > 308: 74181 0 0 0 GPIO 116 lm90 Hi, Paul When I developed it, my Dalmore board used GPIO 116 (GPIO_PO4) as interrupt line, but according to our downsttream kernel, there also have other Dalmore board used GPIO 190 (GPIO_PX6). So I think your problems was caused by it. Please try to change the interrupt line in dts file. Thanks. Wei. > > That's from shortly after boot. From successive 'cat's of > /proc/interrupts, I see that the interrupt count is increasing very > quickly. So something is definitely not right. > >> Is there any monitoring script, application or daemon polling for >> temperatures on this system? > > This is a totally quiet system, booted with 'init=/bin/bash' on the kernel > command line - nothing else running at all. > > regards > > - Paul > _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
