From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: linux-kernel@vger.kernel.org
Subject: linux 2.6.19 still crashing
Date: Sat, 02 Dec 2006 17:55:09 +0100 [thread overview]
Message-ID: <4571AFED.8060200@dungeon.inka.de> (raw)
my msi s270 laptop. but all vanilla kernel I ever tried do
that, also the debian and ubuntu kernel are instable too.
But: xen 3.0.2 plus xen'ified linux 2.6.16.31 are rock solid.
any idea what the issue could be? I'm running 64bit kernel,
64bit userland (plus some 32bit apps), and the cpu is a turion
mt-40 (sempron users seem to not have this problem).
I documented all details, config files, dmesg, /proc/interrupts,
lspci -vvv and xorg log file at
http://www.megawiki.org/wiki/S270Crashing
I can also mail you all those files (didn't want to spam
linux-kernel with a huge mail), and provide any other information
that can help, try patches or command line options, or different
compile options or whatever you can suggest.
Thanks for your help!
Regards, Andreas
next reply other threads:[~2006-12-02 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 16:55 Andreas Jellinghaus [this message]
2006-12-04 2:49 ` linux 2.6.19 still crashing Sergio Monteiro Basto
2006-12-04 7:35 ` Andreas Jellinghaus
2006-12-04 15:28 ` 100000 interrupts problem " Sergio Monteiro Basto
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=4571AFED.8060200@dungeon.inka.de \
--to=aj@dungeon.inka.de \
--cc=linux-kernel@vger.kernel.org \
/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