public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Lopes <alvieboy@alvie.com>
To: Alvaro Lopes <alvieboy@alvie.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: UPDATE - Re: System temporary freeze (but network layer) while blanking CD-RW w/ ide-scsi [2.4.14 and 2.4.16 w/preempt]
Date: 29 Nov 2001 18:22:22 +0000	[thread overview]
Message-ID: <1007058142.1837.0.camel@dwarf> (raw)
In-Reply-To: <3C065182.3090909@alvie.com>
In-Reply-To: <3C065182.3090909@alvie.com>

Well, did some sysrq show tasks while blanking and found processes
locked (D) in:

sleep_on()
wait_on_buffer()
lock_page()
___wait_on_page()


I issued a ^C to cdrecord but blanking kept on. System resumed normal
operation after end of blanking.

BTW I'm using ReiserFS .

Álvaro


On Qui, 2001-11-29 at 15:17, Alvaro Lopes wrote:
> Hi all
> 
> This is very weird. A few days ago I started blanking a CD-RW with a
> HP9500 IDE drive and after five seconds or so the system froze. I was
> still able to ping it and SNAT worked properly too. All services (X,
> ssh, smtp) stopped and were almost fully inacessible (I was still able
> to see some applets working on X, but no more) and when it finished
> blanking, system came back to normal as if nothing had happended.
> 
> At the time I thought it might be a 2.4.14 issue.
> 
> Today I repeated the test with 2.4.16 w/ preemption patch. The same
> thing happened. This time I was running a 'vmstat 1':
> 
> ....
> ....
> ....
>    0  4  1  50524   3932   2984  46168   0   0     0     0  102   151   0   0 100
>    0  4  1  50524   3932   2984  46168   0   0     0     0  102   154   0   0 100
>    0  4  1  50524   3928   2984  46168   0   0     0     0  101   149   0   0 100
>    0  4  1  50524   3928   2984  46168   0   0     0     0  101   154   0   0 100
>    1  4  1  50524   3928   2984  46168   0   0     0     0  101   150   0   0 100
>    0  4  1  50524   3928   2984  46168   0   0     0     0  102   151   0   0 100
>    0  4  1  50524   3924   2984  46168   0   0     0     0  101   156   0   0 100
>    0  4  1  50524   3924   2984  46168   0   0     0     0  101   152   0   0 100
>    0  4  1  50524   3924   2984  46168   0   0     0     0  102   155   0   0 100
>    0  4  1  50524   3924   2984  46168   0   0     0     0  101   150   0   0 100
>    0  4  1  50524   3916   2984  46168   0   0     0     0  101   150   0   0 100
>    0  4  1  50524   3916   2984  46168   0   0     0     0  101   151   0   0 100
> 
> when it got here, system froze.... and then:
> 
>    1  5  1  50584   4216  2820  44996 2348 296 3032  348 113506 165193   0   0 100
>    1  4  1  50572  11416   3192  37112 348   0   668   596  319  1243   4   3  93
>    1  1  0  50552  11468   3520  37420   0   0   308   492  315   794   6   3  91
>    1  0  0  50552  11068   3544  37596   0   0   168     4  127  9301  65   6  29
>    1  0  0  50552  11064   3544  37596   0   0     0     0  104   652  75   0  25
>    2  0  0  50552  11064   3544  37596   0   0     0     0  102   604  75   0  25
>    1  0    procs                      memory    swap          io     system
>      cpu
>    r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
>    1  0  1  50552  10992   3616  37596   0   0     0   140  154   721  75   1  25
>    2  0  0  50552  10992   3616  37596   0   0     0    32  118   679  75   0  25
>    1  0  0  50552  10988   3616  37596   0   0     0     0  101   610  75   0  25
>    1  0  0  50552  10988   3616  37596   0   0     0     0  102   602  74   0  26
>    0  0  0  50552  10104   3652  37664 220   0   308     0  139   741  47   1  52
>    0  0  0  50552  10104   3652  37664   0   0     0     0  107   491   0   0 100
>    0  0  0  50552  10012   3744  37664   0   0     0   160  155   598   1   0  99
>    0  0  0  50552  10320   3744  37704  32   0    84     0  181  1078  18   2  80
>    0  0  0  50552  10284   3780  37704   0   0     0    44  250   834   1   2  97
> 
> 
> What is happening here ?  Any clues ???
> 
> Álvaro Lopes
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2001-11-29 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 15:17 System temporary freeze (but network layer) while blanking CD-RW w/ ide-scsi [2.4.14 and 2.4.16 w/preempt] Alvaro Lopes
2001-11-29 18:22 ` Alvaro Lopes [this message]
2001-11-29 18:30   ` UPDATE - " Jens Axboe

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=1007058142.1837.0.camel@dwarf \
    --to=alvieboy@alvie.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