Your message dated Sat, 02 Jun 2007 06:59:57 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-source-2.6.8 2.6.8-17
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Sat, 02 Jun 2007 06:59:55 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-m68k 2.6.8-5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 28 May 2007 23:06:26 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-ia64 2.6.8-15
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Mon, 28 May 2007 23:06:13 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-hppa 2.6.8-7
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 28 May 2007 23:06:28 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-s390 2.6.8-6
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 28 May 2007 23:06:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-alpha 2.6.8-17
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 28 May 2007 23:06:30 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-sparc 2.6.8-16
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Mon, 28 May 2007 23:06:09 +
with message-id [EMAIL PROTECTED]
and subject line Bug#349774: fixed in kernel-image-2.6.8-amd64 2.6.8-17
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Package: kernel-source-2.6.8
Version: 2.6.8-16sarge1
I'll file a bug for this usertag it dkt-pending-sarge-update.
--
dann frazier [EMAIL PROTECTED]
---BeginMessage---
On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote:
On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote:
Hi,
On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote:
On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote:
Hi,
The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
Apparently the fix was committed somewhere around 2.6.10, anyway we've
upgraded our stable box
On Wed, 2006-01-18 at 10:03 +, Stuart T. R. Rowan wrote:
On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote:
On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote:
Hi,
The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
Apparently the fix was
On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote:
Hi,
The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
Apparently the fix was committed somewhere around 2.6.10, anyway we've
upgraded our stable box to vanilla kernel 2.6.15.1 to work around this
issue -- no
Hi,
The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
Apparently the fix was committed somewhere around 2.6.10, anyway we've
upgraded our stable box to vanilla kernel 2.6.15.1 to work around this
issue -- no discarded packets at all now.
If there's gonna be an update to the
14 matches
Mail list logo
