Bug #370287 “skge module stops transmitting” : Bugs : linux package : Ubuntu

DM (denism-inbox) on 2009-05-01

visibility:

public → private

Brian Murray (brian-murray) on 2009-05-01

tags:	added: bitesize
affects:	linux-ports-meta (Ubuntu) → linux (Ubuntu)

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2009-05-01:

#1

Hi DM,

I've marked this bug as public rather than private. Additionally, I'll try to notify the kernel team of this upstream fix, thanks for including it in the report. Additionally, the upcoming Karmic 9.10 kernel will automatically have this patch as it's already.

visibility:	private → public
Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged
Changed in linux (Ubuntu Jaunty):
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

DM (denism-inbox) wrote on 2009-05-02: Re: [Bug 370287] Re: skge module stops transmitting

#2

Download full text (3.2 KiB)

Please remove my email in the bottom of description of the bug. I did not found how to modify the desctiption after bug was sent. This is why I made it private :)

-----Original Message-----
From: Leann Ogasawara <email address hidden>
To: <email address hidden>
Date: Fri, 01 May 2009 23:18:51 -0000
Subject: [Bug 370287] Re: skge module stops transmitting

> Hi DM,
>
> I've marked this bug as public rather than private. Additionally, I'll
> try to notify the kernel team of this upstream fix, thanks for including
> it in the report. Additionally, the upcoming Karmic 9.10 kernel will
> automatically have this patch as it's already.
>
> ** Visibility changed to: Public
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: New => Triaged
>
> ** Also affects: linux (Ubuntu Jaunty)
> Importance: Undecided
> Status: New
>
> ** Changed in: linux (Ubuntu Jaunty)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu Jaunty)
> Status: New => Triaged
>
> --
> skge module stops transmitting
> https://bugs.launchpad.net/bugs/370287
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Triaged
> Status in linux in Ubuntu Jaunty: Triaged
>
> Bug description:
> i have DLink 530T (1Gb ethenet card). skge is driver for it. but since update to ubuntu 9.04 (full reinstall). some times it stops transmitting packets (and not back to work). ifconfig eth1 shows that rx is changing but tx is not. pings are not going... the card on the internet port, so i lost internet periodically.
> the `save` commands that help me to return it to work is
> #modprobe -r skge && modprobe skge && service networking restart
> but after a few times i run it skge breaks work as described above in a few seconds after `save` command. and only computer restart helps.
>
> it looks like this from changelog for 2.6.29.2 (skge disables the TX queue):
>
> commit 9fc79ab9a371b45166d80ef18411ea47cf8e3195
> Author: Michal Schmidt <email address hidden>
> Date: Tue Apr 14 15:16:55 2009 -0700
>
> skge: fix occasional BUG during MTU change
>
> upstream commit: d119b3927994e3d620d6adb0dd1ea6bf24427875
>
> The BUG_ON(skge->tx_ring.to_use != skge->tx_ring.to_clean) in skge_up()
> was sometimes observed when setting MTU.
>
> skge_down() disables the TX queue, but then reenables it by mistake via
> skge_tx_clean().
> Fix it by moving the waking of the queue from skge_tx_clean() to the
> other caller. And to make sure start_xmit is not in progress on another
> CPU, skge_down() should call netif_tx_disable().
>
> The bug was reported to me by Jiri Jilek whose Debian system sometimes
> failed to boot. He tested the patch and the bug did not happen anymore.
>
> Signed-off-by: Michal Schmidt <email address hidden>
> Acked-by: Stephen Hemminger <email address hidden>
> Signed-off-by: David S. Miller <email address hidden>
> Signed-off-by: Chris Wright <email address hidden>
>
> please include it in your main kernel branch ASAP (netwo...

Please remove my email in the bottom of description of the bug. I did not found how to modify the desctiption after bug was sent. This is why I made it private :)

-----Original Message-----
From: Leann Ogasawara <leann.ogasawara@canonical.com>
To: denism@inbox.ru
Date: Fri, 01 May 2009 23:18:51 -0000
Subject: [Bug 370287] Re: skge module stops transmitting

> Hi DM,
> 
> I've marked this bug as public rather than private.  Additionally, I'll
> try to notify the kernel team of this upstream fix, thanks for including
> it in the report.  Additionally, the upcoming Karmic 9.10 kernel will
> automatically have this patch as it's already.
> 
> ** Visibility changed to: Public
> 
> ** Changed in: linux (Ubuntu)
>    Importance: Undecided => Medium
> 
> ** Changed in: linux (Ubuntu)
>        Status: New => Triaged
> 
> ** Also affects: linux (Ubuntu Jaunty)
>    Importance: Undecided
>        Status: New
> 
> ** Changed in: linux (Ubuntu Jaunty)
>    Importance: Undecided => Medium
> 
> ** Changed in: linux (Ubuntu Jaunty)
>        Status: New => Triaged
> 
> -- 
> skge module stops transmitting
> https://bugs.launchpad.net/bugs/370287
> You received this bug notification because you are a direct subscriber
> of the bug.
> 
> Status in "linux" source package in Ubuntu: Triaged
> Status in linux in Ubuntu Jaunty: Triaged
> 
> Bug description:
> i have DLink 530T (1Gb ethenet card). skge is driver for it. but since update to ubuntu 9.04 (full reinstall). some times it stops transmitting packets (and not back to work). ifconfig eth1 shows that rx is changing but tx is not. pings are not going... the card on the internet port, so i lost internet periodically.
> the `save` commands that help me to return it to work is
> #modprobe -r skge && modprobe skge && service networking restart
> but after a few times i run it skge breaks work as described above in a few seconds after `save` command. and only computer restart helps.
> 
> it looks like this from changelog for 2.6.29.2 (skge disables the TX queue):
> 
> commit 9fc79ab9a371b45166d80ef18411ea47cf8e3195
> Author: Michal Schmidt <mschmidt@redhat.com>
> Date:   Tue Apr 14 15:16:55 2009 -0700
> 
>     skge: fix occasional BUG during MTU change
>     
>     upstream commit: d119b3927994e3d620d6adb0dd1ea6bf24427875
>     
>     The BUG_ON(skge->tx_ring.to_use != skge->tx_ring.to_clean) in skge_up()
>     was sometimes observed when setting MTU.
>     
>     skge_down() disables the TX queue, but then reenables it by mistake via
>     skge_tx_clean().
>     Fix it by moving the waking of the queue from skge_tx_clean() to the
>     other caller. And to make sure start_xmit is not in progress on another
>     CPU, skge_down() should call netif_tx_disable().
>     
>     The bug was reported to me by Jiri Jilek whose Debian system sometimes
>     failed to boot. He tested the patch and the bug did not happen anymore.
>     
>     Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
>     Acked-by: Stephen Hemminger <shemminger@vyatta.com>
>     Signed-off-by: David S. Miller <davem@davemloft.net>
>     Signed-off-by: Chris Wright <chrisw@sous-sol.org>
> 
> please include it in your main kernel branch ASAP (network breaks)
> my email: denism@inbox.ru
>

Revision history for this message

Ike Panhc (ikepanhc) wrote on 2009-05-14:

#3

Just click the "Update description / tags" under the descriptions, then you can modify the description

description:

updated

Revision history for this message

Ike Panhc (ikepanhc) wrote on 2009-05-28:

#4

Hi DM,

I merge the commit from upstream and have the image at http://people.ubuntu.com/~ikepanhc/lp370287/

Could you help me try if it works fine with your hardware or not.

Changed in linux (Ubuntu Jaunty):
assignee:	nobody → Ike Panhc (ikepanhc)
status:	Triaged → In Progress

Revision history for this message

DM (denism-inbox) wrote on 2009-05-30:

#5

Download full text (4.6 KiB)

Hi Ike,

I am using amd64 version. Also 2.6.29.3/4 was tried from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . It look like problem is still exist in main line. the main info as I understend searching in the Internet is

May 30 01:24:38 pnz-ubuntu kernel: [11181.136046] skge 0000:03:07.0: PCI error cmd=0x117 status=0x22b0
May 30 01:24:38 pnz-ubuntu kernel: [11181.136080] skge 0000:03:07.0: unable to clear error (so ignoring them)

It is in each log. the other log (but from 2.6.29.4)
May 30 01:24:57 pnz-ubuntu kernel: [11200.804805] ------------[ cut here ]------------
May 30 01:24:57 pnz-ubuntu kernel: [11200.804814] WARNING: at /home/kernel-ppa/mainline/build/net/sched/sch_generic.c:226 dev_watchdog+0x211/0x220()
May 30 01:24:57 pnz-ubuntu kernel: [11200.804819] Hardware name: System Product Name
May 30 01:24:57 pnz-ubuntu kernel: [11200.804822] NETDEV WATCHDOG: eth1 (skge): transmit timed out
May 30 01:24:57 pnz-ubuntu kernel: [11200.804826] Modules linked in: nf_nat_ftp nf_conntrack_ftp vboxnetflt vboxdrv tun video output nfsd nfs lockd nfs_acl auth_rpcgss sunrpc xfs exportfs lp parport xt_state xt_multiport iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables psmouse i2c_piix4 k8temp r8168 serio_raw pcspkr skge usbhid raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear
May 30 01:24:57 pnz-ubuntu kernel: [11200.804889] Pid: 0, comm: swapper Not tainted 2.6.29-02062904-generic #02062904
May 30 01:24:57 pnz-ubuntu kernel: [11200.804893] Call Trace:
May 30 01:24:57 pnz-ubuntu kernel: [11200.804897] <IRQ> [<ffffffff802519bc>] warn_slowpath+0xdc/0x110
May 30 01:24:57 pnz-ubuntu kernel: [11200.804916] [<ffffffff8024902f>] ? enqueue_task_fair+0x4f/0x60
May 30 01:24:57 pnz-ubuntu kernel: [11200.804925] [<ffffffff80240dc0>] ? enqueue_task+0x50/0x60
May 30 01:24:57 pnz-ubuntu kernel: [11200.804934] [<ffffffff8026e26a>] ? sched_clock_cpu+0xba/0x130
May 30 01:24:57 pnz-ubuntu kernel: [11200.804940] [<ffffffff8022be1e>] ? read_hpet+0xe/0x10
May 30 01:24:57 pnz-ubuntu kernel: [11200.804948] [<ffffffff8027133a>] ? getnstimeofday+0x4a/0xe0
May 30 01:24:57 pnz-ubuntu kernel: [11200.804954] [<ffffffff8026c20a>] ? ktime_get_ts+0x4a/0x60
May 30 01:24:57 pnz-ubuntu kernel: [11200.804963] [<ffffffff8041271f>] ? strlcpy+0x4f/0x70
May 30 01:24:57 pnz-ubuntu kernel: [11200.804969] [<ffffffff8027133a>] ? getnstimeofday+0x4a/0xe0
May 30 01:24:57 pnz-ubuntu kernel: [11200.804976] [<ffffffff805b9fe1>] dev_watchdog+0x211/0x220
May 30 01:24:57 pnz-ubuntu kernel: [11200.804983] [<ffffffff8027555e>] ? tick_dev_program_event+0x3e/0xc0
May 30 01:24:57 pnz-ubuntu kernel: [11200.804989] [<ffffffff80275645>] ? tick_program_event+0x25/0x30
May 30 01:24:57 pnz-ubuntu kernel: [11200.804994] [<ffffffff8026c38b>] ? hrtimer_interrupt+0x11b/0x180
May 30 01:24:57 pnz-ubuntu kernel: [11200.805001] [<ffffffff805b9dd0>] ? dev_watchdog+0x0/0x220
May 30 01:24:57 pnz-ubuntu kernel: [11200.805008] [<ffffffff8025c8a3>] run_timer_softirq+0x1a3/0x220
May 30 01:24:57 pnz-ubuntu kernel: [11200.805016] [<ffffffff80257b8d>] __do_softirq+0x9d/0x150
May 30 01:24:57 pnz-ubuntu kernel: [11200.805024] [<fffff...

Hi Ike,

I am using amd64 version. Also 2.6.29.3/4 was tried from http://kernel.ubuntu.com/~kernel-ppa/mainline/ . It look like problem is still exist in main line. the main info as I understend searching in the Internet is

May 30 01:24:38 pnz-ubuntu kernel: [11181.136046] skge 0000:03:07.0: PCI error cmd=0x117 status=0x22b0
May 30 01:24:38 pnz-ubuntu kernel: [11181.136080] skge 0000:03:07.0: unable to clear error (so ignoring them)

It is in each log. the other log (but from 2.6.29.4)
May 30 01:24:57 pnz-ubuntu kernel: [11200.804805] ------------[ cut here ]------------
May 30 01:24:57 pnz-ubuntu kernel: [11200.804814] WARNING: at /home/kernel-ppa/mainline/build/net/sched/sch_generic.c:226 dev_watchdog+0x211/0x220()
May 30 01:24:57 pnz-ubuntu kernel: [11200.804819] Hardware name: System Product Name
May 30 01:24:57 pnz-ubuntu kernel: [11200.804822] NETDEV WATCHDOG: eth1 (skge): transmit timed out
May 30 01:24:57 pnz-ubuntu kernel: [11200.804826] Modules linked in: nf_nat_ftp nf_conntrack_ftp vboxnetflt vboxdrv tun video output nfsd nfs lockd nfs_acl auth_rpcgss sunrpc xfs exportfs lp parport xt_state xt_multiport iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables psmouse i2c_piix4 k8temp r8168 serio_raw pcspkr skge usbhid raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear
May 30 01:24:57 pnz-ubuntu kernel: [11200.804889] Pid: 0, comm: swapper Not tainted 2.6.29-02062904-generic #02062904
May 30 01:24:57 pnz-ubuntu kernel: [11200.804893] Call Trace:
May 30 01:24:57 pnz-ubuntu kernel: [11200.804897]  <IRQ>  [<ffffffff802519bc>] warn_slowpath+0xdc/0x110
May 30 01:24:57 pnz-ubuntu kernel: [11200.804916]  [<ffffffff8024902f>] ? enqueue_task_fair+0x4f/0x60
May 30 01:24:57 pnz-ubuntu kernel: [11200.804925]  [<ffffffff80240dc0>] ? enqueue_task+0x50/0x60
May 30 01:24:57 pnz-ubuntu kernel: [11200.804934]  [<ffffffff8026e26a>] ? sched_clock_cpu+0xba/0x130
May 30 01:24:57 pnz-ubuntu kernel: [11200.804940]  [<ffffffff8022be1e>] ? read_hpet+0xe/0x10
May 30 01:24:57 pnz-ubuntu kernel: [11200.804948]  [<ffffffff8027133a>] ? getnstimeofday+0x4a/0xe0
May 30 01:24:57 pnz-ubuntu kernel: [11200.804954]  [<ffffffff8026c20a>] ? ktime_get_ts+0x4a/0x60
May 30 01:24:57 pnz-ubuntu kernel: [11200.804963]  [<ffffffff8041271f>] ? strlcpy+0x4f/0x70
May 30 01:24:57 pnz-ubuntu kernel: [11200.804969]  [<ffffffff8027133a>] ? getnstimeofday+0x4a/0xe0
May 30 01:24:57 pnz-ubuntu kernel: [11200.804976]  [<ffffffff805b9fe1>] dev_watchdog+0x211/0x220
May 30 01:24:57 pnz-ubuntu kernel: [11200.804983]  [<ffffffff8027555e>] ? tick_dev_program_event+0x3e/0xc0
May 30 01:24:57 pnz-ubuntu kernel: [11200.804989]  [<ffffffff80275645>] ? tick_program_event+0x25/0x30
May 30 01:24:57 pnz-ubuntu kernel: [11200.804994]  [<ffffffff8026c38b>] ? hrtimer_interrupt+0x11b/0x180
May 30 01:24:57 pnz-ubuntu kernel: [11200.805001]  [<ffffffff805b9dd0>] ? dev_watchdog+0x0/0x220
May 30 01:24:57 pnz-ubuntu kernel: [11200.805008]  [<ffffffff8025c8a3>] run_timer_softirq+0x1a3/0x220
May 30 01:24:57 pnz-ubuntu kernel: [11200.805016]  [<ffffffff80257b8d>] __do_softirq+0x9d/0x150
May 30 01:24:57 pnz-ubuntu kernel: [11200.805024]  [<ffffffff8021391c>] call_softirq+0x1c/0x30
May 30 01:24:57 pnz-ubuntu kernel: [11200.805030]  [<ffffffff80214d76>] do_softirq+0x56/0xa0
May 30 01:24:57 pnz-ubuntu kernel: [11200.805036]  [<ffffffff8025769b>] irq_exit+0x7b/0x90
May 30 01:24:57 pnz-ubuntu kernel: [11200.805042]  [<ffffffff80214e46>] do_IRQ+0x86/0x100
May 30 01:24:57 pnz-ubuntu kernel: [11200.805048]  [<ffffffff80213093>] ret_from_intr+0x0/0x29
May 30 01:24:57 pnz-ubuntu kernel: [11200.805051]  <EOI>  [<ffffffff8022da46>] ? native_safe_halt+0x6/0x10
May 30 01:24:57 pnz-ubuntu kernel: [11200.805063]  [<ffffffff802741f6>] ? clockevents_notify+0x36/0x90
May 30 01:24:57 pnz-ubuntu kernel: [11200.805069]  [<ffffffff8021999e>] ? default_idle+0x2e/0x50
May 30 01:24:57 pnz-ubuntu kernel: [11200.805074]  [<ffffffff80219a17>] ? c1e_idle+0x57/0x130
May 30 01:24:57 pnz-ubuntu kernel: [11200.805082]  [<ffffffff8068b9f1>] ? atomic_notifier_call_chain+0x11/0x20
May 30 01:24:57 pnz-ubuntu kernel: [11200.805088]  [<ffffffff80210e13>] ? cpu_idle+0x53/0xa0
May 30 01:24:57 pnz-ubuntu kernel: [11200.805095]  [<ffffffff806839f0>] ? start_secondary+0xa0/0xc0
May 30 01:24:57 pnz-ubuntu kernel: [11200.805100] ---[ end trace 9edf5ff949058d5e ]---

also skge oops on rather high load of storage system and network. Also i played with iommu (amd gart, soft) - nothing helps. Config: MB Asus m3a78 (amd700 + sb750) amd х2 4880+ and 8Gb mem (small home server for internet, file storage and VMs, also shares repos for provider network segment)

Revision history for this message

Ike Panhc (ikepanhc) wrote on 2009-06-01:

#6

Hi DM,

I check the source code of v2.6.29.3. Unfortunately it contains the commit.

Thanks for your response.

I will read the log you attach and see if there is any hint with it

Revision history for this message

Ike Panhc (ikepanhc) wrote on 2009-06-15:

#7

Hi DM,

I can not tell anything from the dmesg.

Anyway, I will keep an eye on upstream for solutions

Revision history for this message

Ike Panhc (ikepanhc) wrote on 2009-07-14:

#8

There is still nothing looks like solutions at upstream. I will still keep an eye on it.

I leave this bug in case if there is anyone know the answer

Changed in linux (Ubuntu Jaunty):
assignee:	Ike Panhc (ikepanhc) → nobody
status:	In Progress → Triaged

Revision history for this message

enedene (enedene) wrote on 2009-11-15:

#9

I just bought this card yesterday D-LINK DGE-530T revision 11. I use Karmic Koala.
The card gets detected, module skge loaded, I can setup a static ip but it doesn't work.

lspci | grep -i ethernet gives:
01:06.0 Ethernet controller: D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev 11) (rev 11)

I did a little research and it seems that module sk98lin should be used. I downloaded the drivers for Marvell Yukon 88E8001 chipset which this card uses from:
http://www.skd.de/e_en/support/driver_searchresults.html?navanchor=10013&term=typ.treiber+bs.Linux+produkt.SK-9821V2.0&produkt=produkt.SK-9821V2.0&typ=typ.treiber&system=bs.Linux

In attachment you can find the install.log where you can see what went wrong.

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-05-16:

#10

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Revision history for this message

Mickaël LE CABELLEC (mickael-lecabellec) wrote on 2010-10-29:

#11

Hi,

I've the problem on a machine with this configuration:
- Motherboard: GA-MA790GPT-UD3H
- uname: Linux cnoss0001 2.6.24-28-server #1 SMP Wed Aug 25 14:46:03 UTC 2010 x86_64 GNU/Linux

/var/log/kern.log
--------------------------------------------
Oct 29 11:05:22 cnoss0001 kernel: [247080.250554] skge 0000:03:07.0: PCI error cmd=0x7 status=0x22b0
Oct 29 11:05:22 cnoss0001 kernel: [247080.250571] skge 0000:03:07.0: unable to clear error (so ignoring them)
Oct 29 11:06:52 cnoss0001 kernel: [247169.427017] NETDEV WATCHDOG: eth1: transmit timed out
Oct 29 11:10:32 cnoss0001 kernel: [247388.874889] NETDEV WATCHDOG: eth1: transmit timed out
Oct 29 11:14:02 cnoss0001 kernel: [247598.347865] NETDEV WATCHDOG: eth1: transmit timed out
Oct 29 11:16:47 cnoss0001 kernel: [247762.933776] NETDEV WATCHDOG: eth1: transmit timed out
Oct 29 11:19:27 cnoss0001 kernel: [247922.532231] NETDEV WATCHDOG: eth1: transmit timed out
--------------------------------------------

Changed in linux (Ubuntu Jaunty):
status:	Triaged → New

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2011-07-18: Closing unsupported series nomination.

#12

This bug was nominated against a series that is no longer supported, ie jaunty. The bug task representing the jaunty nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Jaunty):
status:	New → Won't Fix

Revision history for this message

penalvch (penalvch) wrote on 2013-09-09:

#13

DM, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-11-08:

#14

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Ubuntu
linux package

skge module stops transmitting

Bug Description

Duplicates of this bug

Other bug subscribers

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned
	Jaunty	Won't Fix	Medium	Unassigned

Ubuntulinux package

skge module stops transmitting

Bug Description

Duplicates of this bug

Other bug subscribers

Remote bug watches

Ubuntu
linux package