| 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: <201209240652.q8O6qWGf012411.zacglen.com@localhost> Date: Mon, 24 Sep 2012 16:52:32 +1000 From: yvahk-xreary@...glen.net To: dan.carpenter@...cle.com Cc: dheitmueller@...nellabs.com, linux-kernel@...r.kernel.org, mijhail.moreyra@...il.com, stoth@...nellabs.com Subject: Re: Freeze or Oops on recent kernels > >HINT: We only care about the very most recent kernel. If you can >take a photo of the stack trace, then file a bug report and attach >the .jpg. > After a bit of experimentation my guess is that is is all about bad Intel DX58SO2 motherboard. And my guess is that it has something to do with memory mapping during an interrupt. Don't know much about memory mapping but I suspect that something quite fundamental goes wrong with this motherboard only. Exact same type of oops also happens with a PCIe RS232 serial card. Trouble is that one tends to select hardware for stability so that means slightly older hardware and hopefully fewer bugs. Unfortunately latest hardware may not be supported by older more stable kernels, and it also wont be well supported by newer kernels. Worse still, everything lasts less than a year with manufacturers getting away with vandalistic change of sockets or connectors or chipsets just to achieve more sales, and new bugs. This constant cycle of pointless change doesn't seem to be heading anywhere in particular. John W -- 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