07ca:a815 af9015: random detection issue

Bug #998360 reported by FM33
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The dvb stick identified as af9015 in kernel log (or af9013 in kaffeine) regulary fails to be detected at system startup and need to be unplugged/replugged.

Log :

kernel: [ 4.458135] af9015: recv bulk message failed:-110
kernel: [ 4.458138] af9015: eeprom read failed:-1
kernel: [ 4.458146] dvb_usb_af9015: probe of 1-1.3:1.0 failed with error -1

After : replug :

kernel: [ 262.596415] usb 1-1.3: USB disconnect, device number 3
kernel: [ 264.620038] usb 1-1.3: new high-speed USB device number 6 using ehci_hcd
kernel: [ 264.717963] af9015: command failed:170
kernel: [ 265.081985] dvb-usb: found a 'AVerMedia AVerTV DVB-T Volar X' in cold state, will try to load a firmware
kernel: [ 265.084535] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
kernel: [ 265.152971] dvb-usb: found a 'AVerMedia AVerTV DVB-T Volar X' in warm state.
kernel: [ 265.153038] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
kernel: [ 265.153435] DVB: registering new adapter (AVerMedia AVerTV DVB-T Volar X)
kernel: [ 265.157163] af9013: firmware version:4.95.0.0
kernel: [ 265.163037] DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
kernel: [ 265.164757] MXL5005S: Attached at address 0xc6
kernel: [ 265.187937] Registered IR keymap rc-avermedia-m135a
kernel: [ 265.188048] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/rc/rc0/input12
kernel: [ 265.188170] rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/rc/rc0
kernel: [ 265.188176] dvb-usb: schedule remote query interval to 500 msecs.
kernel: [ 265.188180] dvb-usb: AVerMedia AVerTV DVB-T Volar X successfully initialized and connected.
kernel: [ 265.201289] input: AVerMedia A815 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input13

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-firmware-nonfree 1.11
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sat May 12 10:03:23 2012
Dependencies:

InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-firmware-nonfree
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2961 F.... pulseaudio
CasperVersion: 1.336
DistroRelease: Ubuntu 13.10
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130825)
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-3-generic N/A
 linux-backports-modules-3.11.0-3-generic N/A
 linux-firmware 1.113
RfKill:

Tags: saucy
Uname: Linux 3.11.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/23/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0119.2011.0523.1030
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67BL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10189-209
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0119.2011.0523.1030:bd05/23/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:

Revision history for this message
Andy Whitcroft (apw) wrote :

This does not appear to be a firmware related issue, we are failing to talk to the device at all. Moving to the kernel.

affects: linux-firmware-nonfree (Ubuntu) → linux (Ubuntu)
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 998360

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
Revision history for this message
FM33 (foxxm) wrote : Re: af9015: random detection issue

It doen't work :

fabien@fabien-desktop:~$ apport-collect 998360
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=hmMcLRQrsclKc3NhBtKL&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...
Aucun paquet ne correspond à linux.
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 718, in add_hooks_info
    symb['add_info'](self, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 45, in add_info
    match_error_messages(report)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 129, in match_error_messages
    if report['ProblemType'] == 'Package':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 499, in <lambda>
    GLib.idle_add(lambda: self.collect_info(on_finished=self.ui_update_view))
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 867, in collect_info
    icthread.exc_raise()
  File "/usr/lib/python2.7/dist-packages/apport/REThread.py", line 34, in run
    self._retval = self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 111, in thread_collect_info
    if report['ProblemType'] == 'Crash' and \
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: apport-issue
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
Revision history for this message
FM33 (foxxm) wrote :

I saw a new error message "af9015 "did not find the firmware file" and found a track here with google : http://forums.gentoo.org/viewtopic-t-906892-start-0.html
"Do you insert the device before or after the filesystem is mounted. If the driver is built-in and you insert it before the filesystem is mounted (read: the device is there at boot), it's impossible for it load the firmware, because it's on the yet-to-be-mounted filesystem."

but i don't know what to do to check is it is the problem, or how to change the moment when the firmware is loaded.

Schell (selim-t)
Changed in linux (Ubuntu):
status: Expired → Confirmed
penalvch (penalvch)
tags: added: needs-kernel-logs needs-upstream-testing
removed: apport-issue
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
FM33 (foxxm) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected saucy
description: updated
Revision history for this message
FM33 (foxxm) wrote : BootDmesg.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : CRDA.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : CurrentDmesg.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : Lspci.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : Lsusb.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : ProcEnviron.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : ProcInterrupts.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : ProcModules.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : PulseList.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : UdevDb.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : UdevLog.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : WifiSyslog.txt

apport information

Revision history for this message
FM33 (foxxm) wrote : Re: af9015: random detection issue

The problem is worst with latest (live) version : the device is never detected. Log :

[ 675.584695] usb 1-1.4: USB disconnect, device number 3
[ 678.086790] usb 1-1.4: new high-speed USB device number 6 using ehci-pci
[ 678.183739] usb 1-1.4: New USB device found, idVendor=07ca, idProduct=a815
[ 678.183744] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 678.183747] usb 1-1.4: Product: A815
[ 678.183749] usb 1-1.4: Manufacturer: AVerMedia
[ 678.183751] usb 1-1.4: SerialNumber: 301262900177000
[ 678.185869] usb 1-1.4: dvb_usb_af9015: command failed=170
[ 678.185876] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' error while loading driver (-5)
[ 678.185885] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully deinitialized and disconnected
[ 678.187838] input: AVerMedia A815 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input12
[ 678.188119] hid-generic 0003:07CA:A815.0005: input,hidraw0: USB HID v1.01 Keyboard [AVerMedia A815] on usb-0000:00:1a.0-1.4/input1

$ ls /dev/dvb
ls: cannot access /dev/dvb: No such file or directory

FM33 (foxxm)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.11.0-031100rc6
removed: needs-upstream-testing
Revision history for this message
FM33 (foxxm) wrote :

With the kernel 3.11.0-031100rc6 in precise, during my test the device was detected during the boot, but not after reconnection. Log :

[ 75.338931] usb 1-1.4: dvb_usb_v2: usb_bulk_msg() failed=-71
[ 75.338938] usb 1-1.4: dvb_usb_af9015: rc query failed=-71
[ 75.347640] usb 1-1.4: USB disconnect, device number 3
[ 75.359893] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully deinitialized and disconnected
[ 78.871812] usb 1-1.4: new high-speed USB device number 6 using ehci-pci
[ 78.968768] usb 1-1.4: New USB device found, idVendor=07ca, idProduct=a815
[ 78.968774] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 78.968777] usb 1-1.4: Product: A815
[ 78.968779] usb 1-1.4: Manufacturer: AVerMedia
[ 78.968781] usb 1-1.4: SerialNumber: 301262900177000
[ 78.970858] usb 1-1.4: dvb_usb_af9015: command failed=170
[ 78.970872] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' error while loading driver (-5)
[ 78.970881] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully deinitialized and disconnected
[ 78.972988] input: AVerMedia A815 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input13
[ 78.973343] hid-generic 0003:07CA:A815.0005: input,hidraw0: USB HID v1.01 Keyboard [AVerMedia A815] on usb-0000:00:1a.0-1.4/input1

When the device was detected, kaffeine detected it as a second device.

FM33 (foxxm)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-0160 kernel-bug-exists-upstream-v3.11-rc6 needs-upstream-testing
removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.11.0-031100rc6 needs-kernel-logs
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
FM33 (foxxm) wrote :

A web search led me to discover that the firmware provided with ubuntu is out of date, despite the fact that the most recent was released in 2010 :

$ md5sum /lib/firmware/dvb-usb-af9015.fw
dccbc92c9168cc629a88b34ee67ede7b /lib/firmware/dvb-usb-af9015.fw

$ md5sum dvb-usb-af9015*
dccbc92c9168cc629a88b34ee67ede7b dvb-usb-af9015(1).fw
4e0e7d65ab961d02fe5d5625c0393d47 dvb-usb-af9015(2).fw
f6c1dfb5c2c890b438771918d66ee2be dvb-usb-af9015(3).fw
532b8e1eabd3b4e9f8ca084b767e4470 dvb-usb-af9015(4).fw
5c2da8881b8be5161c7db8ef94711cf5 dvb-usb-af9015.fw ==> Most recent from http://palosaari.fi/linux/v4l-dvb/firmware/af9015//

Just replaced it and crossing fingers. I'll wait to check if it solves the issue before trying the (non downgradable) bios update.

Revision history for this message
FM33 (foxxm) wrote :

Bios update did not change anything.
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
BLH6710H.86A.0160.2012.1204.1156
12/04/2012

Kernel log :
[ 4.049085] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 16000000, was 12060000
[ 4.494265] af9015: recv bulk message failed:-110
[ 4.494271] af9015: eeprom read failed:-1
[ 4.494278] dvb_usb_af9015: probe of 1-1.4:1.0 failed with error -1
[ 4.494307] usbcore: registered new interface driver dvb_usb_af9015

tags: removed: bios-outdated-0160
Revision history for this message
FM33 (foxxm) wrote :

Re-tested it in saucy live. Works better than previous test : The device is detected after replug. With live CD, it is not detected during boot because linux-firmware-nonfree package is not installed by default.

[ 453.960379] usb 1-1.4: USB disconnect, device number 3
[ 455.760182] usb 1-1.4: new high-speed USB device number 6 using ehci-pci
[ 455.857280] usb 1-1.4: New USB device found, idVendor=07ca, idProduct=a815
[ 455.857285] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 455.857288] usb 1-1.4: Product: A815
[ 455.857290] usb 1-1.4: Manufacturer: AVerMedia
[ 455.857292] usb 1-1.4: SerialNumber: 301262900177000
[ 455.861018] usb 1-1.4: dvb_usb_v2: found a 'AVerMedia AVerTV DVB-T Volar X' in cold state
[ 455.861209] usb 1-1.4: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'
[ 455.861637] input: AVerMedia A815 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input12
[ 455.861949] hid-generic 0003:07CA:A815.0005: input,hidraw0: USB HID v1.01 Keyboard [AVerMedia A815] on usb-0000:00:1a.0-1.4/input1
[ 455.932471] usb 1-1.4: dvb_usb_v2: found a 'AVerMedia AVerTV DVB-T Volar X' in warm state
[ 456.328041] usb 1-1.4: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 456.328073] DVB: registering new adapter (AVerMedia AVerTV DVB-T Volar X)
[ 458.480749] i2c i2c-8: af9013: firmware version 4.95.0.0
[ 458.483739] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
[ 458.646792] MXL5005S: Attached at address 0xc6
[ 458.744571] Registered IR keymap rc-avermedia-m135a
[ 458.744672] input: AVerMedia AVerTV DVB-T Volar X as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/rc/rc0/input13
[ 458.744814] rc0: AVerMedia AVerTV DVB-T Volar X as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/rc/rc0
[ 458.744821] usb 1-1.4: dvb_usb_v2: schedule remote query interval to 500 msecs
[ 458.744826] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully initialized and connected

Revision history for this message
penalvch (penalvch) wrote :

FM33, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/ and advise on the results?

tags: added: latest-bios-0160
Revision history for this message
FM33 (foxxm) wrote :

I have re-tested with kernel 3.11.0-031100.201309021735_amd64
The issue seems still there. I will keep the kernel for the week and see more.
1st, The device was detected but not working properly,
2nd, After replug, it was not detected at all [error while loading driver (-5)],
3rd, After replug, it was detected and working properly.

Revision history for this message
penalvch (penalvch) wrote :

FM33, did this problem not occur in a release prior to Precise?

tags: added: kernel-bug-exists-upstream-v3.11
removed: kernel-bug-exists-upstream-v3.11-rc6 needs-upstream-testing
Revision history for this message
FM33 (foxxm) wrote :

I can't say it because this machine had precise for first OS.
It was working fine on the former machine with Ubuntu 11.10 and is still working on Mint Debian Ed with 3.2 kernel.
Former PC hardware : Motherboard Asus P5ND2SE, GPU Nvidia (with proprietary driver in Ubuntu and now Nouveau in LMDE). Can't tell more details about bios or gpu model for now because the PC needs repair.

Revision history for this message
FM33 (foxxm) wrote :

I confirm the issue is still there (following #28).

Revision history for this message
penalvch (penalvch) wrote :

FM33, for regression testing purposes, on the machine you originally reported with could you please test for this problem in Oneiric via http://old-releases.ubuntu.com/releases/oneiric/ and advise is reproducible?

summary: - af9015: random detection issue
+ 07ca:a815 af9015: random detection issue
Revision history for this message
FM33 (foxxm) wrote :

I tried with oneiric live on usb for more than 10 days without reproducing. I figured out that the issue pretty occur on colds boots (and resume from suspend/hibernate). I never had the issue again in precise while it was booted by restarting from oneiric. Then, after finishing the oneiric testings, when the problem occured in precise i tried to restart instead of unplugging and it worked too.

Then i ran new tests with latest saucy live : It never works, even unplugging several times. Logs & infos :

$ ls /dev/dvb
ls: cannot access /dev/dvb: No such file or directory

ubuntu@ubuntu:~$ dmesg | grep dvb
[ 109.692860] usbcore: registered new interface driver dvb_usb_af9015
[ 109.693191] usb 1-1.4: dvb_usb_af9015: command failed=170
[ 109.693193] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' error while loading driver (-5)
[ 109.693197] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully deinitialized and disconnected

ubuntu@ubuntu:~$ dmesg | tail -n 50
...
[ 278.691834] usb 1-1.4: USB disconnect, device number 3
[ 280.681194] usb 1-1.4: new high-speed USB device number 6 using ehci-pci
[ 280.778167] usb 1-1.4: New USB device found, idVendor=07ca, idProduct=a815
[ 280.778172] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 280.778175] usb 1-1.4: Product: A815
[ 280.778177] usb 1-1.4: Manufacturer: AVerMedia
[ 280.778180] usb 1-1.4: SerialNumber: 301262900177000
[ 280.780359] usb 1-1.4: dvb_usb_af9015: command failed=170
[ 280.780365] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' error while loading driver (-5)
[ 280.780374] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully deinitialized and disconnected
[ 280.782416] input: AVerMedia A815 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input12
[ 280.782701] hid-generic 0003:07CA:A815.0005: input,hidraw0: USB HID v1.01 Keyboard [AVerMedia A815] on usb-0000:00:1a.0-1.4/input1

ubuntu@ubuntu:~$ ls /lib/firmware/dvb-usb-af*
/lib/firmware/dvb-usb-af9015.fw

ubuntu@ubuntu:~$ dmesg | tail -n 15
...
[ 392.830748] usb 1-1.4: USB disconnect, device number 6
[ 394.565064] usb 1-1.4: new high-speed USB device number 7 using ehci-pci
[ 394.662039] usb 1-1.4: New USB device found, idVendor=07ca, idProduct=a815
[ 394.662044] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 394.662047] usb 1-1.4: Product: A815
[ 394.662049] usb 1-1.4: Manufacturer: AVerMedia
[ 394.662052] usb 1-1.4: SerialNumber: 301262900177000
[ 394.664157] usb 1-1.4: dvb_usb_af9015: command failed=170
[ 394.664163] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' error while loading driver (-5)
[ 394.664172] usb 1-1.4: dvb_usb_v2: 'AVerMedia AVerTV DVB-T Volar X' successfully deinitialized and disconnected
[ 394.666126] input: AVerMedia A815 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input13
[ 394.666406] hid-generic 0003:07CA:A815.0006: input,hidraw0: USB HID v1.01 Keyboard [AVerMedia A815] on usb-0000:00:1a.0-1.4/input1

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.11.0-8-generic #15-Ubuntu SMP Fri Sep 20 04:11:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

penalvch (penalvch)
tags: added: regression-releases
Revision history for this message
FM33 (foxxm) wrote :

The issue appeared between 3.1.2-030102 and 3.1.3-030103

Revision history for this message
penalvch (penalvch) wrote :

FM33, the next step is to fully commit bisect between 3.1.2-030102 and 3.1.3-030103, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Revision history for this message
FM33 (foxxm) wrote :

I ran this :
$ git log --oneline Ubuntu-3.1.2-030102..Ubuntu-3.1.3-030103
fatal: ambiguous argument 'Ubuntu-3.1.2-030102..Ubuntu-3.1.3-030103': unknown revision or path not in the working tree.

So i tried this :
git log Ubuntu-3.1.0-2.3..Ubuntu-3.2.0-1.1 | less
Working, but :
git log --oneline Ubuntu-3.1.0-2.3..Ubuntu-3.2.0-1.1 | wc
  11401 93126 705392

Is there a way to be more specific / doing this precisely for 3.1.2 to 3.1.3 ?

Revision history for this message
FM33 (foxxm) wrote :

I found a way to restrict the bisect to november 2011 according to the dates in http://kernel.ubuntu.com/~kernel-ppa/mainline/ but the build process fails because a 'debian" directory is missing.

$ git log --after 2011-11-01 --before 2011-11-30 > log_nov2011
$ git bisect start
$ git bisect good 45f74482a05df8aa9253ec0b228648cbad3dd7e8
$ git bisect bad a493f1a24a496711d96b91c4dc0a1bd35eb6954b
Bisecting: 5283 revisions left to test after this (roughly 12 steps)
[37be944a0270402f9cda291a930b0286f6dc92f5] Merge branch 'drm-core-next' of git://people.freedesktop.org/~airlied/linux

debian.master/changelog do not exist. Skipped this step

$ fakeroot debian/rules clean
/usr/bin/fakeroot: ligne 178: debian/rules: Aucun fichier ou dossier de ce type

I don't understand https://wiki.ubuntu.com/Kernel/KernelBisection#Why_did_the_folders_debian_and_debian.master_disappear.3F

Do i need to give up the idea of restricting to november 2011 changesets or is there a way around this ?

Revision history for this message
penalvch (penalvch) wrote :

FM33, it would be best to switch to bisecting the mainline kernel.

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
FM33 (foxxm)
Changed in linux (Ubuntu):
status: Expired → Incomplete
Revision history for this message
FM33 (foxxm) wrote :

I cannot reproduce with the mainline kernel.

Revision history for this message
penalvch (penalvch) wrote :

FM33, could you please test with Trusty via http://cdimage.ubuntu.com/daily-live/current/ and advise if this is reproducible?

Revision history for this message
arbor (a2843251) wrote :

Apparently this only happens when you plug in the dvb-t stick via a usb hub. Plugging it directly into a usb port works fine.

Revision history for this message
FM33 (foxxm) wrote :

Arbor,
I do not use any hub.

Christopher,
The issue is the same in 14.04 release (fresh install).

Revision history for this message
penalvch (penalvch) wrote :

FM33, when you switched to bisecting the mainline kernel, which commit was found to be the offending one?

tags: added: trusty
tags: added: regression-release
removed: regression-releases
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.