From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux 2.6.19 still crashing
Date: Mon, 04 Dec 2006 02:49:48 +0000 [thread overview]
Message-ID: <1165200588.9189.1.camel@monteirov> (raw)
In-Reply-To: <4571AFED.8060200@dungeon.inka.de>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi,
1st you should put this information on http://bugzilla.kernel.org/
(choose enter a new bug, may choose Category ACPI with component
config-interrupts ) for better organization, instead make your own bug
documentation.
The documentation is very good you should attach the same information
on bugzilla
your bug kept me the attention because on bad interrupts you have :
21: 100000 IO-APIC-fasteoi ohci1394
Exactly oops on 100000 interrupts, I had seen this before .
I have my bug on http://bugzilla.kernel.org/show_bug.cgi?id=6419
which one of the bugs looks like similar to yours.
So, You are saying with kernel 2.6.16.31 with xen 3.0.2, you don't have
this problem , I like to try it, how or where you build this Xenified
kernel ?
Thanks,
On Sat, 2006-12-02 at 17:55 +0100, Andreas Jellinghaus wrote:
> 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).
>
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-12-04 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 16:55 Andreas Jellinghaus
2006-12-04 2:49 ` Sergio Monteiro Basto [this message]
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=1165200588.9189.1.camel@monteirov \
--to=sergio@sergiomb.no-ip.org \
--cc=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
all inboxes | Powered by JetHome®