aMule unable to connect to kad 3.13.0-71

Bug #1525598 reported by Pablo Merighi
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The last kernel update: linux-image-3.13.0-71-generic makes aMule unable to connect to kad
Description: Ubuntu 14.04.3 LTS
Release: 14.04
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pablo 3879 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
InstallationDate: Installed on 2014-03-25 (627 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-71-generic N/A
 linux-backports-modules-3.13.0-71-generic N/A
 linux-firmware 1.127.19
RfKill:

Tags: trusty
Uname: Linux 3.13.0-71-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 09/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: N68-S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1525598

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Pablo Merighi (pablomerighi) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Pablo Merighi (pablomerighi) wrote : BootDmesg.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : CRDA.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : IwConfig.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : Lspci.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : ProcEnviron.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : ProcModules.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : PulseList.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : UdevDb.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : UdevLog.txt

apport information

Revision history for this message
Pablo Merighi (pablomerighi) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
Pablo Merighi (pablomerighi) wrote :

unable to run this command,
apport-collect 1525598

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this issue go away by booting into the prior kernel version?

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: regression-update
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pablo Merighi (pablomerighi) wrote :

Yes Joseph,
 booting with 3.13.0-68-generic
aMule Kad connections are working Ok

penalvch (penalvch)
tags: added: bios-outdated-2.10
Revision history for this message
Pablo Merighi (pablomerighi) wrote :

Bios updated but the issue is still there
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
P2.10
04/21/2010

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Pablo Merighi, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-2.10
removed: bios-outdated-2.10
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
mars (mars-29200) wrote :

Hi here,
I just try the 3.13.11-031311ckt32-generic kernel and the problem is not fixed.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11-ckt32-trusty/

what can I do more than just installing kernels and testing to help ?

Regards,
Mars

Revision history for this message
penalvch (penalvch) wrote :

mars, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Andrea Amoroso (heiko81) wrote :

I can confirm that booting with kernel 3.13.0-68-generic i can connect to kad network. I can't with following versions. I'm on Ubuntu 14.04.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.