All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
	Valdis.Kletnieks@vt.edu, sfrench@us.ibm.com,
	castet.matthieu@free.fr, greg@kroah.com, vojtech@suse.cz,
	dtor_core@ameritech.net
Subject: Re: 2.6.14-mm1
Date: Fri, 11 Nov 2005 16:50:27 +0500	[thread overview]
Message-ID: <43748583.9050105@ums.usu.ru> (raw)
In-Reply-To: <437472DA.4090001@linuxfromscratch.org>

I wrote:

> I wrote:
>
>> Note that unlike with the previous kernels, the huge traffic is not 
>> reported on the ppp0 interface.
>
>
>
> I was wrong. There are two failure modes, one with huge traffic and 
> one without. Attached is a sample tcpdump of the failure mode with the 
> huge traffic. If you know how to capture data going through the serial 
> port, I will do this also.

I was wrong again. There is only one failure mode, with apparent huge 
traffic, but that traffic doesn't appear immediately after the keyboard 
bug. One more note: if a key is pressed when the bug manifests itself, 
it autorepeats in X indefinitely.

An archive that contains both the tcpdump and pppdump of the bug is 
available at:

http://ums.usu.ru/~patrakov/bad-dump.tar.bz2

Taken with commands:

pppd call motiv record ppp0.pppdump nodetach
tcpdump -i ppp0 -s 0 -w ppp0.tcpdump

Then irrelevant tails that consist of repeating packets were cut off by 
hand.

-- 
Alexander E. Patrakov

  parent reply	other threads:[~2005-11-11 11:52 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  2:24 2.6.14-mm1 Andrew Morton
2005-11-07  3:25 ` 2.6.14-mm1 Christoph Hellwig
2005-11-07  6:12   ` 2.6.14-mm1 Andrew Morton
2005-11-07  6:34     ` 2.6.14-mm1 Herbert Xu
2005-11-07  3:30 ` 2.6.14-mm1 Christoph Hellwig
2005-11-07 12:18   ` 2.6.14-mm1 Roman Zippel
2005-11-07 17:02     ` 2.6.14-mm1 Christoph Hellwig
2005-11-07 17:23       ` 2.6.14-mm1 Roman Zippel
2005-11-07 12:41   ` 2.6.14-mm1 Geert Uytterhoeven
2005-11-07  4:04 ` 2.6.14-mm1 Brice Goglin
2005-11-07  4:10 ` 2.6.14-mm1 Reuben Farrelly
2005-11-07  6:07   ` 2.6.14-mm1 Andrew Morton
2005-11-07  8:24   ` 2.6.14-mm1 Benoit Boissinot
2005-11-07  9:54 ` 2.6.14-mm1 Reuben Farrelly
2005-11-07 10:09   ` 2.6.14-mm1 Andrew Morton
2005-11-07 10:26     ` 2.6.14-mm1 Neil Brown
2005-11-07 10:37       ` 2.6.14-mm1 Andrew Morton
2005-11-07 10:44         ` 2.6.14-mm1 Reuben Farrelly
2005-11-07 18:52           ` 2.6.14-mm1 Andrew Morton
2005-11-07 19:27             ` 2.6.14-mm1 Alan Stern
2005-11-07 19:27               ` 2.6.14-mm1 Alan Stern
2005-11-07 21:43             ` 2.6.14-mm1 J.A. Magallon
2005-11-08  0:07               ` 2.6.14-mm1 J.A. Magallon
2005-11-08 14:21             ` 2.6.14-mm1 James Bottomley
2005-11-09  0:30               ` 2.6.14-mm1 Reuben Farrelly
2005-11-07 12:00 ` 2.6.14-mm1 Jiri Slaby
2005-11-07 15:04   ` 2.6.14-mm1 Dustin Kirkland
2005-11-07 15:11     ` 2.6.14-mm1 Jiri Slaby
2005-11-07 16:15 ` 2.6.14-mm1 Alexander E. Patrakov
2005-11-07 19:52   ` 2.6.14-mm1 Andrew Morton
2005-11-07 20:07     ` 2.6.14-mm1 Greg KH
2005-11-07 20:30       ` 2.6.14-mm1 Dmitry Torokhov
2005-11-07 20:21     ` 2.6.14-mm1 Valdis.Kletnieks
2005-11-07 20:40       ` 2.6.14-mm1 Dmitry Torokhov
2005-11-07 20:46       ` 2.6.14-mm1 Andrew Morton
2005-11-11  9:32         ` 2.6.14-mm1 Alexander E. Patrakov
     [not found]           ` <437472DA.4090001@linuxfromscratch.org>
2005-11-11 11:50             ` Alexander E. Patrakov [this message]
2005-11-07 17:37 ` 2.6.14-mm1: drivers/pci/hotplug/: namespace clashes Adrian Bunk
2005-11-07 18:41   ` Rajesh Shah
2005-11-07 20:03     ` Adrian Bunk
2005-11-07 21:37       ` Rajesh Shah
2005-11-07 21:10 ` 2.6.14-mm1: Why is USB_LIBUSUAL user-visible? Adrian Bunk
2005-11-07 21:52   ` Greg KH
2005-11-07 22:26     ` [linux-usb-devel] " Alan Stern
2005-11-07 22:28       ` Greg KH
2005-11-08  0:47         ` [-mm patch] USB_LIBUSUAL shouldn't be user-visible Adrian Bunk
2005-11-09 22:28           ` Greg KH
2005-11-10  6:41             ` Pete Zaitcev
2005-11-10 10:56               ` Adrian Bunk
2005-11-10 23:46                 ` Greg KH
2005-11-11  2:09                   ` Adrian Bunk
2005-11-11  6:13                     ` Greg KH
2005-11-11  9:31                     ` Pete Zaitcev
2005-11-10 12:11               ` Reuben Farrelly
2005-11-11  9:14           ` Pete Zaitcev
2005-11-07 23:34   ` 2.6.14-mm1: Why is USB_LIBUSUAL user-visible? Pete Zaitcev
2005-11-07 22:28 ` 2.6.14-mm1 - cpufreq build problem Rafael J. Wysocki
2005-11-08  4:36 ` [-mm patch] __deprecated_for_modules the lookup_hash() prototype Adrian Bunk
2005-11-10 13:07 ` 2.6.14-mm1 Serge Hallyn
     [not found]   ` <OFE00FE25C.725B5669-ON872570B5.0066EFF0-862570B5.00679646@us.ibm.com>
2005-11-11 17:59     ` 2.6.14-mm1 Serge Hallyn
2005-11-14 17:05       ` 2.6.14-mm1 Greg KH
2005-11-12  0:31 ` 2.6.14-mm1 Michal Piotrowski
2005-11-12  0:51   ` 2.6.14-mm1 Andrew Morton
2005-11-12  1:30     ` 2.6.14-mm1 Michal Piotrowski
2005-11-12  1:47       ` 2.6.14-mm1 Andrew Morton
2005-11-12 18:00         ` 2.6.14-mm1 Michal Piotrowski
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07  2:24 2.6.14-mm1 Andrew Morton

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=43748583.9050105@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=castet.matthieu@free.fr \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@us.ibm.com \
    --cc=vojtech@suse.cz \
    /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.