Process (mozilla) in 'D' state (down_w)

Process (mozilla) in 'D' state (down_w)

Post by Athanasiu » Sat, 14 Apr 2001 16:00:11



   Seems like anytime I first startup mozilla I end up with something
like:

ps afx | grep mozilla
  680 ttyp6    S      0:00              |       \_ grep mozilla
  660 tty1     S      0:00              \_ /bin/sh /other2/mozilla/run-mozilla.sh
  664 tty1     S      0:01                  \_ ./mozilla-bin
  665 tty1     S      0:00                      \_ ./mozilla-bin
  666 tty1     S      0:00                          \_ ./mozilla-bin
  667 tty1     S      0:00                          \_ ./mozilla-bin
  670 tty1     D      0:00                          \_ ./mozilla-bin

  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
040   513   670   665   9   0 19500 12028 down_w D   tty1       0:00 ./mozilla-b

And I can't get that D-state process to budge or die in any way.  I end
up with an fsck of the device the binary is on next reboot due to
unclean umount.  Attaching strace or gdb never works, just hangs, so
about the only useful info I can give (nothing in dmesg or kern.log):



670 (mozilla-bin) D 665 499 459 1025 459 64 0 0 0 0 0 0 0 0 9 0 0 0 32526 19968000 3007 4294967295 134512640 134550420 3221223560 3204446832 1076277629 0 0 4096 0 3222297777 0 0 33 0

3007 3007 2143 11 0 2996 864

Name:   mozilla-bin
State:  D (disk sleep)
Pid:    670
PPid:   665
TracerPid:      0
Uid:    513     513     513     513
Gid:    1000    1000    1000    1000
FDSize: 32
Groups: 1000 5 6 7 20 21 22 24 25 26 29 30 34 39 40 41 60 100 1001 1003
VmSize:    19500 kB
VmLck:         0 kB
VmRSS:     12028 kB
VmData:     3424 kB
VmStk:        64 kB
VmExe:        40 kB
VmLib:     14420 kB
SigPnd: 0000000000000000
SigBlk: 0000000080000000
SigIgn: 8000000000001000
SigCgt: 0000000380000000
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000

   I'll sometime if I can remember to run mozilla with a strace -f -ff
-o file to see if it gives any more useful info.  I'll be updating to
2.4.3-ac5 in the next hour or so anyway (currently on plain vanilla
2.4.3).
   If anyone has any other ideas/suggestions/pointers to info about how
to get more information as to what the process is 'doing' and how it got
there I'd be grateful.

-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
           "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

Process (mozilla) in 'D' state (down_w)

Post by Athanasiu » Mon, 16 Apr 2001 19:20:04



>    Seems like anytime I first startup mozilla I end up with something
> like:
[snip]
>    I'll sometime if I can remember to run mozilla with a strace -f -ff
> -o file to see if it gives any more useful info.  I'll be updating to
> 2.4.3-ac5 in the next hour or so anyway (currently on plain vanilla
> 2.4.3).

   Ok, this seems to be gone in 2.4.3-ac5.  Three reboots, first two I
ran mozilla as strace -f -ff -o mozilla-strace mozilla and got no
D-state process, this third one I just ran it as normal from my fvwm2
menus and it's also working fine.

-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
           "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Another report of mozilla in D state, related to the 'uninterruptible sleep' thread

Second time around, I didn't evoke any interest the first time.

I reported it back on Mar/27.  It is still an almost daily problem
requiring a reboot.  Mozilla gets stuck in down_write_failed.  This time
I'm sure it's not reiser's fault.

# uname -r
2.4.3-pre8

mozilla-bin  D C781849C     0 21055      1        (NOTLB)         20611
 Call Trace: [<ff000000>] [<ff000000>] [<ff000000>]
[leaf_copy_items+121/252]
   [leaf_paste_in_buffer+239/672] [leaf_cut_from_buffer+486/984]
   [leaf_cut_from_buffer+863/984] [balance_leaf+8645/9544]
   [balance_leaf+9225/9544] [leaf_item_bottle+916/1260]
   [balance_leaf+9505/9544] [balance_leaf+9225/9544]
   [leaf_item_bottle+916/1260] [balance_leaf+9505/9544] [<f0000000>]
   [bin_search_in_dir_item+58/196] [leaf_copy_items+121/252]
   [leaf_paste_in_buffer+239/672] [<d086f044>]
   [flush_commit_list+66/908] [flush_journal_list+531/944]
   [free_list_bitmaps+30/60] [reiserfs_unlink+167/460]
   [posix_lock_file+526/1232] [empty_bad_page+3213/4096]
   [empty_bad_page+2717/4096] [fib_flag_trans+35/60]
   [empty_bad_pte_table+3363/4096]

If someone is actually interested, it'd be neat to get this fixed.

-d

--
  There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
  The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. GDB question.

3. Process stuck in 'D' "schedule_timeout" state with 2.5.73-mm1

4. occasional problems with my NCSA httpd server: please help!

5. Remotely rebooting a machine with state 'D' processes, how?

6. FreeBSD + dial-on-demand

7. How to change a process state to 'run' again?

8. watchdog timer on SBC

9. 'eject' process stuck in "D" state

10. NOW have 'D-state' processes in 2.4.17 !!!

11. processes state 'D'

12. What's 'side effects' of Ksh built-ins?

13. 'top' output -> High CPU consumption when thread is in 'sleep' state