| 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
| ||
|
Date: Tue, 27 Feb 2007 07:46:39 +0100 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: David Woodhouse <dwmw2@...radead.org>, linuxppc-dev@...abs.org, LKML <linux-kernel@...r.kernel.org>, Milton Miller <miltonm@....com> Subject: Re: Make sure we populate the initroot filesystem late enough > USB controller issues? We used to have these really hard-to-debug problems > with the USB controller being active and having had the BIOS set up the > command queues etc. Really subtle. It's why we now have PCI quirks for > shutting up (most) USB controllers very early. On powermacs or powerbooks, the USB controller is shut down by the firmware when we call the "quiesce" OF call from prom_init.c, which happens before the kernel relocates itself to 0 and takes over memory. Unless we fucked up something in there, I wouldn't expect that to be the cause. > If there is some USB controller that we miss, or that sets up its command > chain to some unexpected area (so that USB is active and corrupting memory > even very early on), that could explain it. Did we setup the OHCI controller when the crash happen ? Maybe we broke something subtle in the USB stack ? Ben. - 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