linux-kernel - Re: kernel panic on 2.6.24/iTCO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200802011539.08393.lenb@kernel.org>
Date:	Fri, 1 Feb 2008 15:39:08 -0500
From:	Len Brown <lenb@...nel.org>
To:	"Denys Fedoryshchenko" <denys@...p.net.lb>
Cc:	linux-kernel@...r.kernel.org, wim@...ana.be
Subject: Re: kernel panic on 2.6.24/iTCO_wdt not rebooting machine

On Friday 01 February 2008 14:15, Denys Fedoryshchenko wrote:
> 
> On Fri, 1 Feb 2008 12:11:41 -0500, Len Brown wrote
> > 
> > What do you see if you build with CONFIG_HIGH_RES_TIMERS=n
> > 
> > Does it work better if you boot with "acpi=off"?
> > if yes, how about with just pnpacpi=off?
> > 
> > thanks,
> > -Len
> 
> It is not very easy to test. About bug - most probably it is related to third 
> party ESFQ patch, i will drop it and then test more properly when i will be 
> able to make watchdog work fine. But more important i notice - that iTCO_wdt 
> is not working at all. I think hrtimers doesn't change anything on that.
> About testing, i cannot take even small risk now(and near 3-5 days) by 
> changing kernel options, i set now maximum available set of watchdogs, cause 
> there is noone to maintain server, area is unreachable because of snow and 
> bad weather.
> 
> Do you think reasonable to try acpi / pnpacpi with iTCO_wdt to make it work? 
> Maybe just registers addresses or way how TCO watchdog activated changed on 
> this chipset?

yes, i'm wondering if the changes in IO resource reservations
in the PNPACPI layer are interfering with the native driver.

unfortunately, if you boot with acpi=off or pnpacpi=off, you may
run into other, unrelated, issues (or not).

one way to isolate the problem is if you revert these two lines
from their 2.6.24 values to their 2.6.23 values by applying this patch:
---
diff --git a/include/linux/pnp.h b/include/linux/pnp.h
index 2a6d62c..16b46aa 100644
--- a/include/linux/pnp.h
+++ b/include/linux/pnp.h
@@ -13,8 +13,8 @@
 #include <linux/errno.h>
 #include <linux/mod_devicetable.h>
 
-#define PNP_MAX_PORT		40
-#define PNP_MAX_MEM		12
+#define PNP_MAX_PORT		8
+#define PNP_MAX_MEM		4
 #define PNP_MAX_IRQ		2
 #define PNP_MAX_DMA		2
 #define PNP_NAME_LEN		50
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/