From: "davor emard" <davoremard@gmail.com>
To: "Lee Revell" <rlrevell@joe-job.com>
Cc: "Olaf Hering" <olh@suse.de>, "Con Kolivas" <kernel@kolivas.org>,
linux-kernel@vger.kernel.org
Subject: Re: SMP HT + USB2.0 crash
Date: Mon, 5 Jun 2006 13:47:23 +0200 [thread overview]
Message-ID: <beee72200606050447q49bdaed1m7b5ac54b51f564db@mail.gmail.com> (raw)
In-Reply-To: <beee72200606042334l7f6b63e6jd2156d5dffb3da4b@mail.gmail.com>
HI
I downloaded memtest86 iso image and let it running. I passed
1st battery of tests and continues. I'm pretty sure it will keep
pass those test without anyerrors, after all memories there
are 2x512MB samsung and for this machine I was choosing
ram's recommended by the manufacturer this motherboard.
Regarding nvidia, I don't like their binary policy but I may
tell you that both intel 925XE machines can run indefinitely
(for days even months until I reinstall new kernel)
each with a lot of simultaneous openGL with nvidia on 2 monitors
in dual head, dvb receiving over usb (here I mean USB 1.1 only)
firewire traffic, SPDIF output, ethernet traffic on both interfaces
and all that
through enabled SMP, PREEMPT and PREEMPT BIG_KERNEL_LOCK
and it is not going to crash.
As soon as I enable EHCI there it comes.
Otherwise I have option to use EHCI and don't use SMP
but not them both.
On 6/5/06, davor emard <davoremard@gmail.com> wrote:
> HI
>
> Due to popular demand I'm mailing the recent crash
> captured with serial cable on 2.6.16.19 on intel 925X
> triggered with SMP + USB2.0 combination.
>
> Here we got it, it's pretty random and useless for
> tracking the real problem so please don't blame
> software demux in DVB core just becaise it randomly
> crashed there - only thing that matters is that a800
> terrestroal receiver was running in USB 2.0 mode in
> order to generate enough usb2.0 traffic
> to trigger SMP+EHCI bug.
>
> I contributed myself to the dvb software demux code
> and it runs stable with it's demux core part almost
> unchanged for 2 years.
>
> If I remove EHCI and run a800 in USB 1.1 mode everything
> can run stable for any amount of time.
>
>
next prev parent reply other threads:[~2006-06-05 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 10:22 davor emard
2006-06-04 11:42 ` Con Kolivas
2006-06-04 14:29 ` davor emard
2006-06-04 14:54 ` Olaf Hering
2006-06-04 15:09 ` davor emard
2006-06-04 17:10 ` Lee Revell
2006-06-05 6:34 ` davor emard
2006-06-05 11:47 ` davor emard [this message]
2006-06-05 15:15 ` davor emard
2006-06-04 14:58 ` davor emard
2006-06-04 16:06 ` Alistair John Strachan
2006-06-04 16:11 ` davor emard
2006-06-04 16:23 ` davor emard
2006-06-04 16:30 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2006-06-04 10:19 davor emard
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=beee72200606050447q49bdaed1m7b5ac54b51f564db@mail.gmail.com \
--to=davoremard@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=rlrevell@joe-job.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
all inboxes | Powered by JetHome®