From: yvahk-xreary@zacglen.net
To: dan.carpenter@oracle.com
Cc: dheitmueller@kernellabs.com, linux-kernel@vger.kernel.org,
mijhail.moreyra@gmail.com, stoth@kernellabs.com
Subject: Re: Freeze or Oops on recent kernels
Date: Mon, 24 Sep 2012 16:52:32 +1000 [thread overview]
Message-ID: <201209240652.q8O6qWGf012411.zacglen.com@localhost> (raw)
In-Reply-To: <20120924063641.GB28937@mwanda>
>
>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
next prev parent reply other threads:[~2012-09-24 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 11:24 Freeze or Oops on recent kernels yvahk-xreary
2012-09-24 6:36 ` Dan Carpenter
2012-09-24 6:52 ` yvahk-xreary [this message]
2012-09-24 8:55 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201209240652.q8O6qWGf012411.zacglen.com@localhost \
--to=yvahk-xreary@zacglen.net \
--cc=dan.carpenter@oracle.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mijhail.moreyra@gmail.com \
--cc=stoth@kernellabs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox