linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@mipsys.com>
To: Mario Scarpa <m.scarpa@mondonet.net>,
	LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: seemingly random lock-up with kernel 2.2.17p7
Date: Wed, 5 Jul 2000 17:43:02 +0200	[thread overview]
Message-ID: <20000705154302.13586@mailhost.mipsys.com> (raw)
In-Reply-To: <396353DD.7F1C5E7A@mondonet.net>


>I've got a lombard (400MHz, 64MB) and had precisly the same
>behaviour: I was playing some MP3s (mpg123 under X 3.3.6-8
>debianPPC) and the system just crashed two times this morning;
>coz I tried to ping it from another machine and coz I tried
>to shut X down but everything was failing (definitively a system
>crash I would say)...
>Another brick in the wall...the MP3 I was listening this morning
>where both on a CDROM and on a HD and yesterday, just doing a lot
>of HD traffic (moving around some huge dirs) I had another lock;
>it doesn't happen so often (would say never)...could it be something
>related to the IDE driver ? Kernel here 's 2.2.17pre7 rsynced
>from linuxcare.

Thinking about it... you may have triggered a threading kernel bug that
was fixed very recently in mmap (and sounds usually uses mmap a lot, X too).

I'll post a new kernel that has this fix today or tomorrow, let's see if
it corrects your problem.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-05 15:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 13:36 seemingly random lock-up with kernel 2.2.17p7 Gwyn Judd
2000-07-05 13:45 ` Michel Dänzer
2000-07-05 13:57   ` Gwyn Judd
2000-07-05 20:13     ` Magic SysRq key [was Re: seemingly random lock-up with kernel 2.2.17p7] phandel
     [not found] ` <Pine.SGI.4.21.0007050845550.10655-100000@rainbow.uchicago.edu>
2000-07-05 14:03   ` seemingly random lock-up with kernel 2.2.17p7 Gwyn Judd
2000-07-05 14:10     ` Michel Dänzer
2000-07-05 14:17       ` Gwyn Judd
2000-07-05 14:47         ` me
2000-07-05 15:00           ` Michel Dänzer
2000-07-05 15:27           ` Mario Scarpa
2000-07-05 15:43             ` Benjamin Herrenschmidt [this message]
     [not found]     ` <l03130300b58a3be9712a@[209.122.247.91]>
2000-07-06 22:17       ` Fixing dead Xservcfers (was Re: seemingly random lock-up with kernel 2.2.17p7) Gwyn Judd
2000-07-05 14:26 ` seemingly random lock-up with kernel 2.2.17p7 Benjamin Herrenschmidt
2000-07-05 14:36   ` Michel Dänzer
  -- strict thread matches above, loose matches on Subject: below --
2000-07-05 14:18 Iain Sandoe

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=20000705154302.13586@mailhost.mipsys.com \
    --to=benh@mipsys.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=m.scarpa@mondonet.net \
    /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).