public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Lawrence Walton <lawrence@the-penguin.otak.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unkillable process dselect 2.6.15-rc1 and 2.6.15-rc1-mm1
Date: Sat, 31 Dec 2005 15:54:57 +0100	[thread overview]
Message-ID: <20051231145457.GK3811@stusta.de> (raw)
In-Reply-To: <20051118063734.GA1769@the-penguin.otak.com>

On Thu, Nov 17, 2005 at 10:37:34PM -0800, Lawrence Walton wrote:

> Hi

Hi Lawrence,

> I have a system that has processes that can't be or even zombied. Most
> easily triggered by dpkg. but "make clean" in the Linux source seems to
> cause it too.
> 
> Seems related to SCSI and a root XFS file system. No oops but I did get
> a call trace. Not sure if it's generically a SCSI thing or specific to
> my card.
> 
> lspci says it's a AIC-7892A.
> 
> Question comments patches are welcome.

Is this issue still present in 2.6.15-rc7?
2.6.14 was OK?

Please sent the output of "dmesg -s 1000000" for both a working and a 
non-working kernel if it's still present in 2.6.15-rc7.

> BTW I've put other bugs in the bugzilla not related to this one, and
> received what I would characterize as deafening silence. Should I
> bother?
>...

Unfortunately, our bug handling is worse than it should be.

The Bugzilla is still a good place to prevent a bug from being 
completely forgotten.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-12-31 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18  6:37 unkillable process dselect 2.6.15-rc1 and 2.6.15-rc1-mm1 Lawrence Walton
2005-12-31 14:54 ` Adrian Bunk [this message]
2005-12-31 19:10   ` Lawrence Walton
2006-01-01  1:28     ` Adrian Bunk

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=20051231145457.GK3811@stusta.de \
    --to=bunk@stusta.de \
    --cc=lawrence@the-penguin.otak.com \
    --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