From: Andreas Sundstrom <sunkan@zappa.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.6.8 and ingress scheduling
Date: Sun, 15 Aug 2004 10:43:02 +0200 [thread overview]
Message-ID: <411F2216.50103@zappa.cx> (raw)
> hello,
>
> the last line (filter add) in the "wondershaper" script does sth. to the
> kernel, that lets it panic on receiving network packets.
>
> now, if I could capture the trace, that was great... nothing is on disk,
> its also more than fits on the screen, and no scrollback exists.
>
> please cc answers/questions,
>
> regards,
>
> peter
[...]
I can confirm that I have this problem too.
If anyone want me to try a patch just let me know.
/Andreas Sundstrom
next reply other threads:[~2004-08-15 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 8:43 Andreas Sundstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-14 17:52 [OOPS] 2.6.8 and ingress scheduling lkml
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=411F2216.50103@zappa.cx \
--to=sunkan@zappa.cx \
--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