orinoco.c: Error -110 writing Tx descriptor to BAP

Bug #14621 reported by Frederik Dannemare
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Debian)
Fix Released
Unknown
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

I'm actually using Kubuntu here, but this is hardly a Kubuntu-specific issue, so I didn't add Kubuntu as Keyword.

High net load using a Netgear MA311 wlan pcmcia card with the orinoco/hermes module effectively results in a DOS
on my entire system. It is easily reproducible. All I have to do is, for example, to wget a big file (couple
hundred MB or more) from another host on my LAN.

The wlan card can't keep up, it seems:

Mar 27 23:36:05 localhost kernel: eth2: error -110 reading frame. Frame dropped.
Mar 27 23:36:05 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost last message repeated 88 times
Mar 27 23:36:06 localhost kernel: eth2: Error -110 wridescriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost last message repeated 2 times
Mar 27 23:36:06 localhost kernel: hermes @ IO 0x100: Error -16 issuing command.
Mar 27 23:36:06 localhost kernel: hermes @ IO 0x100: Error -16 issuing command.
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descrdescriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP

An *insane* amount of these above lines get written to syslog; up to one hundred lines per second.

top - 00:34:53 up 32 min, 2 users, load average: 4.39, 3.00, 1.58
Tasks: 74 total, 4 running, 70 sleeping, 0 stopped, 0 zombie
Cpu(s): 2.6% us, 5.2% sy, 0.7% ni, 0.0% id, 0.0% wa, 0.0% hi, 91.5% si
Mem: 516244k total, 451616k used, 64628k free, 39624k buffers
Swap: 658624k total, 0k used, 658624k free, 280944k cached

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 6106 root 16 0 1552 380 316 R 39.0 0.1 1:24.56 dd
 7865 syslog 35 10 1740 740 620 R 15.1 0.1 0:25.69 syslogd
 6150 root 15 0 90028 21m 2952 S 7.4 4.3 0:41.77 Xorg
 6108 klog 15 0 2408 1464 436 S 6.6 0.3 0:27.17 klogd
 7609 frederik 16 0 27156 14m 11m S 6.6 2.8 0:28.03 kicker
 7899 frederik 17 0 2080 1044 820 R 3.1 0.2 0:02.39 top
    2 root 39 19 0 0 0 R 2.8 0.0 0:07.16 ksoftirqd/0
 7889 frederik 16 0 26920 14m 11m S 1.7 2.9 0:06.93 konsole
 7617 frederik 16 0 20736 11m 9560 S 0.9 2.2 0:02.80 kcpuload
 6570 hal 16 0 7120 5656 1636 S 0.6 1.1 0:02.40 hald
[...]

The process at fault is, in other words, PID 6106:

frederik@bart:~$ ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 00:02 ? 00:00:00 init [2]
root 2 1 0 00:02 ? 00:00:13 [ksoftirqd/0]
root 3 1 0 00:02 ? 00:00:00 [events/0]
root 4 3 0 00:02 ? 00:00:00 [khelper]
root 22 3 0 00:02 ? 00:00:00 [kacpid]
root 131 3 0 00:02 ? 00:00:00 [kblockd/0]
root 166 3 0 00:02 ? 00:00:00 [pdflush]
root 167 3 0 00:02 ? 00:00:00 [pdflush]
root 169 3 0 00:02 ? 00:00:00 [aio/0]
root 168 1 0 00:02 ? 00:00:00 [kswapd0]
root 756 1 0 00:02 ? 00:00:00 [kseriod]
root 1125 1 0 00:02 ? 00:00:00 [kjournald]
root 1152 1 0 00:02 ? 00:00:00 udevd
root 2225 1 0 00:02 ? 00:00:00 [khpsbpkt]
root 4024 1 0 00:03 ? 00:00:00 [khubd]
root 5334 1 0 00:03 ? 00:00:00 [pccardd]
root 5343 1 0 00:03 ? 00:00:00 [pccardd]
root 5453 1 0 00:03 ? 00:00:00 [knodemgrd_0]
root 5612 3 0 00:03 ? 00:00:00 [ipw2100/0]
root 6106 1 8 00:03 ? 00:03:16 /bin/dd bs 1 if /proc/kmsg of /var/run/klogd/kmsg
klog 6108 1 2 00:03 ? 00:00:57 /sbin/klogd -P /var/run/klogd/kmsg
root 6136 1 0 00:03 ? 00:00:00 /usr/bin/kdm
root 6150 6136 3 00:03 ? 00:01:17 /usr/X11R6/bin/X -nolisten tcp :0 vt7
-auth /var/run/xauth/A:0-gIwO5E
root 6191 6136 0 00:03 ? 00:00:00 -:0
root 6496 1 0 00:03 ? 00:00:00 /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket
102 6558 1 0 00:03 ? 00:00:00 /usr/bin/dbus-daemon-1 --system
hal 6570 1 0 00:03 ? 00:00:02 /usr/sbin/hald --drop-privileges
[...]

Not sure if there is much you can do about the orinoco part in this (although I don't remember seeing this
behavior with Sarge), but it would be nice if it didn't cause the system to go haywire and become extremely
unresponsive due to the huge amount of logging.

Thank you for a great distro,
Frederik Dannemare

CVE References

Revision history for this message
Frederik Dannemare (frederik) wrote :
Download full text (5.0 KiB)

I'm actually using Kubuntu here, but this is hardly a Kubuntu-specific issue, so I didn't add Kubuntu as Keyword.

High net load using a Netgear MA311 wlan pcmcia card with the orinoco/hermes module effectively results in a DOS
on my entire system. It is easily reproducible. All I have to do is, for example, to wget a big file (couple
hundred MB or more) from another host on my LAN.

The wlan card can't keep up, it seems:

Mar 27 23:36:05 localhost kernel: eth2: error -110 reading frame. Frame dropped.
Mar 27 23:36:05 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost last message repeated 88 times
Mar 27 23:36:06 localhost kernel: eth2: Error -110 wridescriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost last message repeated 2 times
Mar 27 23:36:06 localhost kernel: hermes @ IO 0x100: Error -16 issuing command.
Mar 27 23:36:06 localhost kernel: hermes @ IO 0x100: Error -16 issuing command.
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descrdescriptor to BAP
Mar 27 23:36:06 localhost kernel: eth2: Error -110 writing Tx descriptor to BAP

An *insane* amount of these above lines get written to syslog; up to one hundred lines per second.

top - 00:34:53 up 32 min, 2 users, load average: 4.39, 3.00, 1.58
Tasks: 74 total, 4 running, 70 sleeping, 0 stopped, 0 zombie
Cpu(s): 2.6% us, 5.2% sy, 0.7% ni, 0.0% id, 0.0% wa, 0.0% hi, 91.5% si
Mem: 516244k total, 451616k used, 64628k free, 39624k buffers
Swap: 658624k total, 0k used, 658624k free, 280944k cached

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 6106 root 16 0 1552 380 316 R 39.0 0.1 1:24.56 dd
 7865 syslog 35 10 1740 740 620 R 15.1 0.1 0:25.69 syslogd
 6150 root 15 0 90028 21m 2952 S 7.4 4.3 0:41.77 Xorg
 6108 klog 15 0 2408 1464 436 S 6.6 0.3 0:27.17 klogd
 7609 frederik 16 0 27156 14m 11m S 6.6 2.8 0:28.03 kicker
 7899 frederik 17 0 2080 1044 820 R 3.1 0.2 0:02.39 top
    2 root 39 19 0 0 0 R 2.8 0.0 0:07.16 ksoftirqd/0
 7889 frederik 16 0 26920 14m 11m S 1.7 2.9 0:06.93 konsole
 7617 frederik 16 0 20736 11m 9560 S 0.9 2.2 0:02.80 kcpuload
 6570 hal 16 0 7120 5656 1636 S 0.6 1.1 0:02.40 hald
[...]

The process at fault is, in other words, PID 6106:

frederik@bart:~$ ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 00:02 ? 00:00:00 init [2]
root 2 1 0 00:02 ? 00:00:13 [ksoftirqd/0]
root 3 1 0 00:02 ? 00:00:00 [events/0]
root 4 3 0 00:02 ? 00:00:00 [khelper]
root 22 3 0 00:02 ? 00:00:00 [kacpid]
root ...

Read more...

Revision history for this message
Frederik Dannemare (frederik) wrote :

Another person has reported the same problem to Debian's BTS.

<http://bugs.debian.org/291684>

In here the bug submitter states that version 0.15rc2 of the orinoco driver solves his problems. I'll see if I can find
time to confirm this.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sat, 22 Jan 2005 12:32:52 +0100
From: Georg Wittenburg <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: orinoco.c: Error -110 writing Tx descriptor to BAP

Package: kernel-source-2.6.10
Version: 2.6.10-4
Severity: important

Hi,

I'm seeing the "Error -110 writing Tx descriptor to BAP" bug as
described in FAQ at http://ozlabs.org/people/dgibson/dldwd/ about once
every other day. orinoco.c prints to the syslog at such a rate, that the
system becomes completely unresponsive and I have to reboot. The lspci
output for the chip is:

0000:02:0b.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset (rev 01)
        Subsystem: AMBIT Microsystem Corp.: Unknown device 0201
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV-
 VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 9
 Region 0: Memory at e0500000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Updating to version 0.15rc2 of the driver (which the author considers
stable but doesn't have time to submit to mainline) fixes the problem.
Including the new driver in testing is probably too much hassle, but
maybe it's worthwhile for stable.

Regards,
   Georg

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-gw1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-source-2.6.10 depends on:
ii binutils 2.15-5 The GNU assembler, linker and bina
ii bzip2 1.0.2-1 A high-quality block-sorting file
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities

-- no debconf information

Revision history for this message
Frederik Dannemare (frederik) wrote :

Hooray! Success. I can confirm that my problem goes away with 0.15rc1 [1] (0.15rc2 failed to compile here). With 0.15rc1 I
just did a successful wget of a 700MB big file.

Hence, no NIC lockup and system haywire this time - although I did get roughly one thousand of these in my log:
"kernel: eth2: Information frame lost."
but that is probably just due to the lousy wireless signal I have here?

[1]http://ozlabs.org/people/dgibson/dldwd/

Revision history for this message
Frederik Dannemare (frederik) wrote :

Patch attached. Applies to linux-source-2.6.10 (2.6.10-31).

Diff generated with source files from <http://ozlabs.org/people/dgibson/dldwd/orinoco-0.15rc1.tar.gz>.

Tarball checked against signature file <http://ozlabs.org/people/dgibson/dldwd/orinoco-0.15rc1.tar.gz.sig>
and validates against author's key imported from subkeys.pgp.net (cannot say if the imported key is actually valid,
though).

frederik@bart:/usr/src/linux-source-2.6.10$ zcat ~/orinoco-0.15rc1.diff.gz | patch -p0
patching file drivers/net/wireless/airport.c
patching file drivers/net/wireless/firmware.h
patching file drivers/net/wireless/firmware_class.c
patching file drivers/net/wireless/hermes.c
patching file drivers/net/wireless/hermes.h
patching file drivers/net/wireless/hermes_rid.h
patching file drivers/net/wireless/kcompat.h
patching file drivers/net/wireless/orinoco.c
patching file drivers/net/wireless/orinoco.h
patching file drivers/net/wireless/orinoco_cs.c
patching file drivers/net/wireless/orinoco_nortel.c
patching file drivers/net/wireless/orinoco_pci.c
patching file drivers/net/wireless/orinoco_plx.c
patching file drivers/net/wireless/orinoco_tmd.c
patching file drivers/net/wireless/spectrum_cs.c
patching file drivers/net/wireless/userhermes.c

Did a test drive:
cp /boot/config-2.6.10-5-386 .config
make oldconfig
fakeroot make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version -neworinoco kernel_image
sudo dpkg -i ../kernel-image-2.6.10-neworinoco_10.00.Custom_i386.deb

Have been running the kernel all day. The updated orinoco/hermes code works well.
Please consider reviewing and applying the patch, as I believe many will otherwise get bitten by the "Error -110 writing
Tx descriptor to BAP".

I have set status to PENDINGUPLOAD. Please undo, if you dislike the generated patch.

Revision history for this message
Frederik Dannemare (frederik) wrote :

Created an attachment (id=1905)
Updates orinoco/hermes stuff to the newer and better 0.15rc1

Revision history for this message
Frederik Dannemare (frederik) wrote :

This is getting unbearable. It's worse than I initially though.

Couple days ago I went back (for various reasons) to the standard (2.6.10-5-386) kernel from my custom 2.6.10 with the
patch I have already added to this report.

Further testing with transfers as small as 100MB on three different laptops and one stationary machine reveals that all
systems become unusable (ksoftirqd is going nuts on the CPU + see former comments from me) and must be rebooted. This even
happens when I limit (scp -l) xfer speed to roughly 120KB.

Please - when time allows it - review the attached patch and consider applying. I can only image that *anybody* who's using
the current orinoco driver and doing big file transfers will have their systems DOS'ed.

Thanks,

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

Inflating the severity will bring you nowhere. Hoary has been released and this
bug will
be fixes with new orinoco drivers as soon as the development for breezy will start.

Fabio

Revision history for this message
Frederik Dannemare (frederik) wrote :

(In reply to comment #7)
> Inflating the severity will bring you nowhere.

But you don't think this bug is a major issue? Well, nothing I can do about that.

I'm very familiar with Debian BTS and I'm perfectly aware that inflating severity of bugs just for the
cause of creating more visibility of the report is not the way to go - but the reason for bringing up
this very report to major is simply not to be found there.

I brought it up to major since I became aware, through further testing, that the problem shows its ugly
face even on /very/ low xfer rates. It just sucks and I'm simply unable to live with the standard Ubuntu
kernels on all my wlan machines. :(

> Hoary has been released and this bug will
> be fixes with new orinoco drivers as soon as the development for breezy will start.

Sounds good. Thanks for the update.

Revision history for this message
Jack Wasey (jackwasey) wrote :

I only have the problem using the 2.6.10-686 ubuntu packaged kernel; 2.6.10-386
seems to work fine.

i use a netgear ma401 pcmcia card.

Revision history for this message
Ben Collins (ben-collins) wrote :

Assuming fixed in breezy.

Revision history for this message
In , Simon Horman (horms) wrote : Fixed in NMU of linux-2.6 2.6.13-1
Download full text (18.4 KiB)

tag 222374 + fixed
tag 289810 + fixed
tag 291684 + fixed
tag 304387 + fixed
tag 316809 + fixed
tag 317787 + fixed
tag 320042 + fixed
tag 320366 + fixed
tag 323724 + fixed
tag 328324 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 6 Oct 2005 15:45:21 +0900
Source: linux-2.6
Binary: linux-image-sun3 linux-headers-2.6.13-1-itanium-smp linux-image-2.6.13-1-footbridge linux-headers-2.6.13-1-footbridge linux-headers-2.6.13-1-mckinley-smp linux-image-2.6.13-1-bvme6000 linux-image-2.6-footbridge linux-image-2.6-amd64-generic linux-headers-2.6-64-smp kernel-image-2.6-686-smp linux-headers-2.6-atari linux-image-2.6.13-1-amiga kernel-image-2.6-386 linux-headers-2.6-s390 linux-image-2.6.13-1-hp linux-image-2.6.13-1-64 linux-image-2.6.13-1-powerpc-smp linux-image-mvme16x linux-image-itanium linux-image-2.6-amd64-k8-smp linux-headers-2.6.13 linux-image-2.6-rpc linux-image-2.6-s390 linux-image-q40 linux-image-2.6.13-1-64-smp linux-headers-2.6-sparc64-smp linux-headers-2.6.13-1-sun3 linux-headers-2.6-mvme147 linux-headers-2.6.13-1-itanium linux-image-footbridge kernel-image-2.6-itanium-smp linux-headers-2.6-686-smp linux-image-atari linux-headers-2.6.13-1-alpha-smp linux-image-2.6-q40 kernel-image-2.6-k7-smp linux-headers-2.6.13-1-powerpc-smp linux-headers-2.6.13-1-amiga linux-headers-2.6.13-1-sparc64-smp linux-image-2.6.13-1-s390 linux-headers-2.6.13-1-amd64-generic linux-headers-2.6-apus linux-image-2.6.13-1-ixp4xx linux-headers-2.6.13-1-sparc64 linux-image-2.6.13-1-itanium-smp linux-image-s390 linux-image-apus linux-image-2.6.13-1-alpha-generic linux-image-2.6-itanium linux-headers-2.6.13-1-powerpc64 linux-headers-2.6.13-1-mac linux-image-amd64-k8-smp linux-image-2.6.13-1-mckinley linux-source-2.6.13 linux-headers-2.6.13-1-amd64-k8-smp linux-doc-2.6.13 linux-headers-2.6.13-1-amd64-k8 linux-headers-2.6-amd64-generic linux-image-2.6-mckinley-smp linux-image-2.6.13-1-sparc64-smp linux-image-amiga linux-image-2.6-k7 linux-image-2.6.13-1-rpc linux-image-mckinley-smp linux-image-2.6.13-1-itanium linux-image-em64t-p4-smp linux-headers-2.6.13-1-s3c2410 linux-image-2.6-powerpc linux-headers-2.6-s3c2410 linux-image-2.6-hp linux-image-sparc64-smp linux-headers-2.6.13-1-32-smp linux-headers-2.6.13-1-hp kernel-image-2.6-mckinley linux-image-powerpc-smp linux-headers-2.6-itanium-smp kernel-image-2.6-power3 linux-headers-2.6.13-1-64 linux-image-2.6-64-smp kernel-image-2.6-powerpc linux-headers-2.6-32 linux-image-2.6.13-1-sun3 kernel-image-2.6-generic linux-headers-2.6-mvme16x linux-image-2.6-alpha-generic linux-headers-2.6-amd64-k8-smp linux-image-2.6-em64t-p4 linux-image-32 linux-headers-2.6-powerpc linux-image-hp linux-headers-2.6-em64t-p4-smp kernel-image-powerpc-smp linux-headers-2.6-sparc64 linux-headers-2.6.13-1-s390 linux-image-powerpc64 linux-headers-2.6-hp linux-headers-2.6.13-1-386 linux-headers-2.6-powerpc64 linux-image-2.6.13-1-686 linux-headers-2.6.13-1-apus linux-image-2.6.13-1-em64t-p4 linux-image-2.6-apus linux-headers-2.6.13-1-686-smp linux-image-2.6.13-1-powerpc64 linux-headers-2.6-mac linux-headers-2.6-32-...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (18.7 KiB)

Message-Id: <email address hidden>
Date: Fri, 07 Oct 2005 15:46:01 -0700
From: Simon Horman <email address hidden>
To: <email address hidden>
Cc: Simon Horman <email address hidden>, Debian Kernel Team <email address hidden>
Subject: Fixed in NMU of linux-2.6 2.6.13-1

tag 222374 + fixed
tag 289810 + fixed
tag 291684 + fixed
tag 304387 + fixed
tag 316809 + fixed
tag 317787 + fixed
tag 320042 + fixed
tag 320366 + fixed
tag 323724 + fixed
tag 328324 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 6 Oct 2005 15:45:21 +0900
Source: linux-2.6
Binary: linux-image-sun3 linux-headers-2.6.13-1-itanium-smp linux-image-2.6.13-1-footbridge linux-headers-2.6.13-1-footbridge linux-headers-2.6.13-1-mckinley-smp linux-image-2.6.13-1-bvme6000 linux-image-2.6-footbridge linux-image-2.6-amd64-generic linux-headers-2.6-64-smp kernel-image-2.6-686-smp linux-headers-2.6-atari linux-image-2.6.13-1-amiga kernel-image-2.6-386 linux-headers-2.6-s390 linux-image-2.6.13-1-hp linux-image-2.6.13-1-64 linux-image-2.6.13-1-powerpc-smp linux-image-mvme16x linux-image-itanium linux-image-2.6-amd64-k8-smp linux-headers-2.6.13 linux-image-2.6-rpc linux-image-2.6-s390 linux-image-q40 linux-image-2.6.13-1-64-smp linux-headers-2.6-sparc64-smp linux-headers-2.6.13-1-sun3 linux-headers-2.6-mvme147 linux-headers-2.6.13-1-itanium linux-image-footbridge kernel-image-2.6-itanium-smp linux-headers-2.6-686-smp linux-image-atari linux-headers-2.6.13-1-alpha-smp linux-image-2.6-q40 kernel-image-2.6-k7-smp linux-headers-2.6.13-1-powerpc-smp linux-headers-2.6.13-1-amiga linux-headers-2.6.13-1-sparc64-smp linux-image-2.6.13-1-s390 linux-headers-2.6.13-1-amd64-generic linux-headers-2.6-apus linux-image-2.6.13-1-ixp4xx linux-headers-2.6.13-1-sparc64 linux-image-2.6.13-1-itanium-smp linux-image-s390 linux-image-apus linux-image-2.6.13-1-alpha-generic linux-image-2.6-itanium linux-headers-2.6.13-1-powerpc64 linux-headers-2.6.13-1-mac linux-image-amd64-k8-smp linux-image-2.6.13-1-mckinley linux-source-2.6.13 linux-headers-2.6.13-1-amd64-k8-smp linux-doc-2.6.13 linux-headers-2.6.13-1-amd64-k8 linux-headers-2.6-amd64-generic linux-image-2.6-mckinley-smp linux-image-2.6.13-1-sparc64-smp linux-image-amiga linux-image-2.6-k7 linux-image-2.6.13-1-rpc linux-image-mckinley-smp linux-image-2.6.13-1-itanium linux-image-em64t-p4-smp linux-headers-2.6.13-1-s3c2410 linux-image-2.6-powerpc linux-headers-2.6-s3c2410 linux-image-2.6-hp linux-image-sparc64-smp linux-headers-2.6.13-1-32-smp linux-headers-2.6.13-1-hp kernel-image-2.6-mckinley linux-image-powerpc-smp linux-headers-2.6-itanium-smp kernel-image-2.6-power3 linux-headers-2.6.13-1-64 linux-image-2.6-64-smp kernel-image-2.6-powerpc linux-headers-2.6-32 linux-image-2.6.13-1-sun3 kernel-image-2.6-generic linux-headers-2.6-mvme16x linux-image-2.6-alpha-generic linux-headers-2.6-amd64-k8-smp linux-image-2.6-em64t-p4 linux-image-32 linux-headers-2.6-powerpc linux-image-hp linux-headers-2.6-em64t-p4-smp kernel-image-powerpc-smp linux-headers-2.6-sparc64 linux-headers-2.6.13-1-s390 linux-image-powerpc6...

Revision history for this message
In , Martin Michlmayr (tbm) wrote : kernel

reassign 289810 linux-2.6
reassign 291684 linux-2.6
reassign 317787 linux-2.6
reassign 320366 linux-2.6
reassign 304387 linux-2.6

--
Martin Michlmayr
http://www.cyrius.com/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 12 Nov 2005 20:38:18 +0000
From: Martin Michlmayr <email address hidden>
To: <email address hidden>
Subject: kernel

reassign 289810 linux-2.6
reassign 291684 linux-2.6
reassign 317787 linux-2.6
reassign 320366 linux-2.6
reassign 304387 linux-2.6

--
Martin Michlmayr
http://www.cyrius.com/

Revision history for this message
In , Sven Luther (sven-luther) wrote : Closing all those bug reports, as they where erroneously labeled closed-in-NMU.

As subject says.

Friendly,

Sven Luther

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 11 Jan 2006 13:16:35 +0100
From: Sven Luther <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Closing all those bug reports, as they where erroneously labeled closed-in-NMU.

As subject says.

Friendly,

Sven Luther

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.