From: Tim Blechmann <tim@klingt.org>
To: "Leyendecker, Robert" <Robert.Leyendecker@lsi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: ext4: smp_processor_id() in preemptible
Date: Fri, 27 Nov 2009 11:32:38 +0100 [thread overview]
Message-ID: <4B0FAAC6.30906@klingt.org> (raw)
In-Reply-To: <8C8865ED624BB94F8FE50259E2B5C5B304593DAB98@palmail03.lsi.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
> I have similar crash, but probably different cause-vector, posted on this list, fedora bugzilla, rt-users but no response so far from anyone. Did you find any work around? I tried looking at smp code for hints on problem it looks like in my case it could be trying to reschedule work on different CPU at time of crash. However, I admit that I could be way, way off on that cause. In my case, if I hammer my network interface with packets while another app is reading packets, my host locks up and clients are reporting dest unreachables.
>
> I don't think I have the problem in non-rt kernel. Have you tried booting without smp support?
i haven't tried to reproduce it since then ... it occurred, when i was
doing some heavy io tasks ...
tim
--
tim@klingt.org
http://tim.klingt.org
Nothing exists until or unless it is observed. An artist is making
something exist by observing it. And his hope for other people is that
they will also make it exist by observing it. I call it 'creative
observation.' Creative viewing.
William S. Burroughs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-27 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 10:05 ext4: smp_processor_id() in preemptible Tim Blechmann
2009-11-26 16:53 ` Leyendecker, Robert
2009-11-27 10:32 ` Tim Blechmann [this message]
2009-11-29 3:02 ` Leyendecker, Robert
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=4B0FAAC6.30906@klingt.org \
--to=tim@klingt.org \
--cc=Robert.Leyendecker@lsi.com \
--cc=linux-ext4@vger.kernel.org \
--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