linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Process in D state (was Re: 2.6.0-test5-mm2)
Date: Sat, 20 Sep 2003 15:34:36 -0400	[thread overview]
Message-ID: <200309201534.36362.rob@landley.net> (raw)
In-Reply-To: <20030914234843.20cea5b3.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

2.6.0-test4 was pretty solid for me.  My main gripe was the weird key repeat 
problem I've mentioned before (where sometimes a key up event will get missed 
or delayed for no apparent reason, happens about twice an hour in normal 
laptop usage).

I upgraded to 2.6.0-test5, but USB didn't work (I bought a scanner), so I 
tried -mm2 and USB is back and happy.

But, twice in a row now I've made this happen:

 1391 pts/1    S      0:00 /bin/bash
 1419 pts/1    S      0:00 /bin/sh ./build.sh
 1423 pts/1    S      0:00 /bin/bash 
/home/landley/pending/newfirmware/make-stat
 1447 pts/1    D      0:04 tar xvjf 
/home/landley/pending/newfirmware/base/linux
 1448 pts/1    S      0:37 bzip2 -d

All I have to do is run my script, it tries to extract the kernel tarball, and 
tar hangs in D state.

How do I debug this?  (Is there some way to get the output of Ctrl-ScrLk to go 
to the log instead of just the console?  My system isn't currently hung, it's 
just got a process that is.  This process being hung prevents my partitions 
from being unmounted on shutdown, which is annoying.)

Other miscelanous bugs: cut and paste only works some of the time (it pastes 
blanks other times, dunno if this was -test5 or -mm2; it worked fine in 
-test4).

The key repeat problem is still there, although still highly intermittent.

The boot hung enabling swap space once.  I don't know why.  (Init was already 
running and everything...)

Rob

[landley@localhost landley]$ cat /proc/modules
orinoco_cs 6472 1 - Live 0xcc06f000
orinoco 39908 1 orinoco_cs, Live 0xcc07c000
hermes 7744 2 orinoco_cs,orinoco, Live 0xcc06c000

[landley@localhost landley]$ cat /proc/version
Linux version 2.6.0-test5-mm2 (landley@localhost.localdomain) (gcc version 
3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #2 Fri Sep 19 00:35:46 EDT 2003


[-- Attachment #2: config.bz2 --]
[-- Type: application/x-bzip2, Size: 5251 bytes --]

  parent reply	other threads:[~2003-09-20 19:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15  6:48 2.6.0-test5-mm2 Andrew Morton
2003-09-15 14:19 ` 2.6.0-test5-mm2 Claas Langbehn
2003-09-15 14:34 ` 2.6.0-test5-mm2 Luiz Capitulino
2003-09-15 16:59   ` 2.6.0-test5-mm2 Arnaldo Carvalho de Melo
2003-09-15 17:19 ` 2.6.0-test5-mm2 Felipe Alfaro Solana
2003-09-17 19:48   ` 2.6.0-test5-mm2 Sam Ravnborg
2003-09-15 19:26 ` 2.6.0-test5-mm2 Marek Habersack
2003-09-15 19:24   ` 2.6.0-test5-mm2 Andrew Morton
2003-09-16  2:02 ` 2.6.0-test5-mm2 Ramón Rey Vicente
2003-09-16 10:23   ` 2.6.0-test5-mm2 Felipe Alfaro Solana
2003-09-17 13:51 ` 2.6.0-test5-mm2 Sean Neakums
2003-09-20 19:34 ` Rob Landley [this message]
2003-09-20 21:49   ` Process in D state (was Re: 2.6.0-test5-mm2) Andrew Morton
2003-09-21 18:30     ` Rob Landley
2003-09-21 20:30     ` Rob Landley

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=200309201534.36362.rob@landley.net \
    --to=rob@landley.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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