From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: pomac@vapor.com
Cc: Arjan van de Ven <arjan@infradead.org>,
woho@woho.de, Stephen Hemminger <shemminger@osdl.org>,
Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, Pavel Volkovitskiy <int@mtx.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert sky2 to 0.13a
Date: Mon, 27 Feb 2006 19:50:30 +0100 [thread overview]
Message-ID: <440349F6.5020606@gmx.net> (raw)
In-Reply-To: <1141001028.23375.14.camel@localhost>
Ian Kumlien schrieb:
> On Sun, 2006-02-26 at 23:38 +0100, Carl-Daniel Hailfinger wrote:
>
>>Ian Kumlien schrieb:
>>
>>>I also saw some oddities... portage stopped working, i dunno if this can
>>>be MSI related or so, else something is trashing memory in a very
>>>special way =P
>>
>>Yes, 0.15 causes memory corruption even if MSI is disabled.
>
>
> So if i run with iommu=forced or what the hell the option is called i
> should be able to catch these trashings?
>
> I also found it odd that it was only python that suffered... Starting
> large and long running C apps worked just fine.
For me, it was usually timer list corruption during boot (50% probability)
or unidentified lockups (probably also timer list corruption) after a few
minutes of operation (40% probability).
Sample Oops message:
Unable to handle kernel NULL pointer dereference at 00000008
rip: run_timer_softirq+322
process udev
Call trace:
__do_softirq+68
call_softirq+30
do_softirq+46
do_IRQ+61
ret_from_intr+0
EOI
Regards,
Carl-Daniel
next prev parent reply other threads:[~2006-02-27 18:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 0:54 [PATCH] Revert sky2 to 0.13a Carl-Daniel Hailfinger
2006-02-26 2:03 ` Stephen Hemminger
2006-02-26 2:42 ` Ian Kumlien
2006-02-26 8:57 ` Wolfgang Hoffmann
2006-02-26 15:00 ` Ian Kumlien
2006-02-26 15:47 ` Arjan van de Ven
2006-02-26 16:13 ` Ian Kumlien
2006-02-26 22:38 ` Carl-Daniel Hailfinger
2006-02-27 0:43 ` Ian Kumlien
2006-02-27 18:50 ` Carl-Daniel Hailfinger [this message]
2006-02-26 18:13 ` Wolfgang Hoffmann
2006-02-26 22:31 ` Wolfgang Hoffmann
2006-02-26 23:03 ` Wolfgang Hoffmann
2006-02-27 16:00 ` Stephen Hemminger
2006-02-27 16:38 ` Wolfgang Hoffmann
2006-02-27 17:18 ` Stephen Hemminger
2006-02-27 17:48 ` Wolfgang Hoffmann
2006-02-27 18:27 ` Ian Kumlien
2006-02-27 18:38 ` Jeff Garzik
2006-02-26 15:28 ` Ian Kumlien
2006-02-26 2:25 ` Ian Kumlien
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=440349F6.5020606@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=arjan@infradead.org \
--cc=int@mtx.ru \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pomac@vapor.com \
--cc=shemminger@osdl.org \
--cc=woho@woho.de \
/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;
as well as URLs for NNTP newsgroup(s).