| 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
| ||
|
Message-Id: <20080201191048.M59862@visp.net.lb> Date: Fri, 1 Feb 2008 21:15:07 +0200 From: "Denys Fedoryshchenko" <denys@...p.net.lb> To: Len Brown <lenb@...nel.org> Cc: linux-kernel@...r.kernel.org, wim@...ana.be Subject: Re: kernel panic on 2.6.24/iTCO_wdt not rebooting machine 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? -- Denys Fedoryshchenko Technical Manager Virtual ISP S.A.L. -- 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/
Powered by blists - more mailing lists