All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc/htb still hangs system.
Date: Thu, 19 Sep 2002 00:35:39 +0000	[thread overview]
Message-ID: <marc-lartc-103239580129043@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103238963124547@msgid-missing>

Tomasz Wrona wrote:
> I tried to find reason but without success. Bellow I mention some
> observed facts. Maybe someboty could advise or solve problem...

In case you want to try systematic debugging of HTB, you may find
tcsim useful. tcsim can be run under Electric Fence and under
Valgrind (http://developer.kde.org/~sewardj/).

It won't help you find race conditions and such, but spotting
odd side-effects of parameter changes may be well within its
capabilities.

Of course, a decent set of regression tests should also be
useful for future HTB development ...

Concerning the Oops you got: you should run it through ksymoops
(see Documentation/oops-tracing.txt in your kernel source tree).

If you don't want to type in the whole Oops text, you can also
get the location of individual symbols with

gdb your/kernel/dir/vmlinux
(gdb) info line *0xd093caa4
etc.

The most useful data is in the EIP and the call trace.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-09-19  0:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 22:52 [LARTC] tc/htb still hangs system Tomasz Wrona
2002-09-19  0:35 ` Werner Almesberger [this message]

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=marc-lartc-103239580129043@msgid-missing \
    --to=wa@almesberger.net \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.