From: Richard Mortimer <richm@oldelvet.org.uk>
To: sparclinux@vger.kernel.org
Subject: Re: oops
Date: Mon, 28 Feb 2005 22:47:52 +0000 [thread overview]
Message-ID: <1109630872.30346.16.camel@duncow> (raw)
In-Reply-To: <DA6197CAE190A847B662079EF7631C0656FC67@OEKAW2EXVS03.hbi.ad.harman.com>
I'm not sure on what is causing it but looking at the Ooops it seems
like there is some form of memory/register corruption.
Feb 28 08:17:54 oekalux08 kernel: CPU[1]: local_irq_count[0]
irqs_running[0]
Feb 28 08:17:54 oekalux08 kernel: TSTATE: 0000000011f09605 TPC:
000000000044fba8 TNPC: 000000000044fbac Y: 01800000 Tainted: P
The offending instruction is
Code; 000000000044fba8 <remove_wait_queue+8/60>
c: ce 6a 00 00 ldstub [ %o0 ], %g7
and %o0 contains o0: 50535943484f2050 which looks suspiciously like
ASCII ("PSYCHO P"). So it looks like PCI and the Psycho device is
somehow implicated.
Richard
On Mon, 2005-02-28 at 09:04 +0100, Jurzitza, Dieter wrote:
> Dear listmembers,
> any ideas, comments on this? The only thing I actually did was running xosview from *userland* and I can crash my system within a very short time.
> U60@360 MHz, SMP, Kernel 2.4.29-SMP.
> Thanks for any efforts in advance,
> take care
>
>
>
>
> Dieter Jurzitza
>
>
--
Richard Mortimer <richm@oldelvet.org.uk>
next prev parent reply other threads:[~2005-02-28 22:47 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 8:04 oops Jurzitza, Dieter
2005-02-28 22:47 ` Richard Mortimer [this message]
[not found] <1aee86c7-27f2-ee81-9669-8a49aa521dfd@lockie.ca>
2020-06-23 17:28 ` oops James
-- strict thread matches above, loose matches on Subject: below --
2019-05-31 3:50 Oops Alex Elder
2007-02-18 15:47 OOPS Menny Hamburger
2007-01-09 13:34 Oops Gerd Hoffmann
2007-01-09 22:46 ` Oops Jeremy Fitzhardinge
2007-01-10 8:16 ` Oops Gerd Hoffmann
2007-01-10 10:29 ` Oops Gerd Hoffmann
2007-01-10 13:05 ` Oops Gerd Hoffmann
2007-01-10 20:07 ` Oops Jeremy Fitzhardinge
2007-01-10 23:52 ` Oops Chris Wright
2007-01-10 23:53 ` Oops Jeremy Fitzhardinge
2007-01-11 8:13 ` Oops Gerd Hoffmann
2007-01-11 8:11 ` Oops Gerd Hoffmann
2007-01-11 15:45 ` Oops Gerd Hoffmann
2007-01-11 17:41 ` Oops Chris Wright
2007-01-12 8:24 ` Oops Gerd Hoffmann
2007-01-12 2:53 ` Oops Rusty Russell
2007-01-12 4:23 ` Oops Chris Wright
2007-01-12 8:31 ` Oops Gerd Hoffmann
2007-01-10 20:06 ` Oops Jeremy Fitzhardinge
2007-01-10 21:44 ` Oops Jeremy Fitzhardinge
2007-01-11 14:12 ` Oops Gerd Hoffmann
2007-01-11 19:56 ` Oops Jeremy Fitzhardinge
2007-01-10 19:38 ` Oops Jeremy Fitzhardinge
2006-04-26 15:15 oops Alex Orlov
2006-04-26 16:29 ` oops Erik Mouw
2006-03-05 20:53 Oops Iain William Wiseman
2005-08-16 21:49 Oops David F Barrera
2005-08-16 21:52 ` Oops Jerone Young
2004-01-06 4:51 OOPs Nick
2004-01-11 13:50 ` OOPs Carsten Grohmann
2003-12-12 17:45 oops Cristiano De Michele
2003-11-01 8:30 Oops Mark Hindley
2003-06-29 21:58 oops Greg Stark
2003-03-09 21:52 oops Thomas Kaeding
2003-02-06 21:51 Oops Gregory Stark
2002-11-25 10:51 oops Tomasz Wrona
2002-11-25 10:35 oops Tomasz Wrona
[not found] <45F949D73F69D41198B00004AC2513FB03D5B6CD@mad00mp3.dot.state.wi.us>
2002-06-18 14:55 ` oops Russell Coker
2002-06-18 19:47 ` oops Eric Johnson
2002-06-18 21:11 ` oops Russell Coker
[not found] <Pine.GSO.4.33.0206171425590.12900-100000@raven>
2002-06-17 18:52 ` oops Russell Coker
[not found] ` <E17KXrd-0001En-00@avocet.mail.pas.earthlink.net>
2002-06-19 5:35 ` oops Russell Coker
2002-06-16 15:52 oops Russell Coker
2002-01-25 11:23 Oops Philipp Matthias Hahn
2001-11-27 13:46 Oops Mark Hindley
2001-08-21 22:36 Oops Rob McPeak
2001-05-18 16:42 Oops Andreas Bergen
[not found] <mailman.989407980.15158.linux-kernel2news@redhat.com>
2001-05-09 17:16 ` oops Pete Zaitcev
2001-05-09 19:18 ` oops Terry Shull
2001-05-09 15:33 oops Terry Shull
2001-05-05 20:43 oops Bial Attila
2001-03-20 15:08 OOPS Mircea Damian
2001-03-09 15:42 Oops Sherman Stebbins
2001-01-19 18:00 oops mkloppstech
2001-01-21 21:18 ` oops David Woodhouse
2000-11-14 16:46 oops Bill Triplett
1999-09-15 5:45 Oops Dagan Sgiath
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=1109630872.30346.16.camel@duncow \
--to=richm@oldelvet.org.uk \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.