Bug#767064: firmware-iwlwifi: Where did iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode go?
Package: firmware-iwlwifi Version: 0.43 Severity: wishlist User: debian-...@lists.debian.org Usertags: debian-edu When installing Debian Edu Jessie on a Thinkpad X200, we provide all the firmware debs available from ftp.debian.org in /firmware/ on the ISO. Yet a question show up asking for more firmware, as the files iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode are missing. In the changelog for firmware-iwlwifi I find that iwlwifi-5000-1.ucode was added in version 0.15 to close bug #497717. I find no similar comment about the iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode files. Were they ever part of this firmware package? What happened with the iwlwifi-5000-1.ucode file? Is it possible to reinsert it, and perhaps also add the two other requested files? -- Happy hacking Peter Reinholdtsen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2fl61f4k2pq@diskless.uio.no
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
Just for the record, I believe this is a firmware bug in the Intel SSD 520 180GB disks used by Lenovo, causing the disks to lock up under heavy load. Perhaps this bug should be closed, or tagged as wontfix, or something else? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2fl38a8jvwt@diskless.uio.no
Bug#767088: /boot/vmlinuz-3.16-3-amd64: Please add backported iwlwifi firmware debugging features
Package: src:linux Version: 3.16.5-1 Severity: wishlist File: /boot/vmlinuz-3.16-3-amd64 Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is it possible to get the iwlwifi firmware debugging feature from v3.17 into the Jessie kernel? Emmanuel has provided a v3.16 backport patch series here: http://www.spinics.net/lists/linux-wireless/msg128672.html This feature is useful when debugging/reporting problems related to the driver/firmware interface. Having the feature in the Jessie kernel can save Debian end users from having to upgrade the kernel just to report iwlwifi firmware bugs. Thanks, Bjørn - -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 2776LEG product_version: ThinkPad X301 chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: 6EET55WW (3.15 ) board_vendor: LENOVO board_name: 2776LEG board_version: Not Available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Lenovo Device [17aa:20e0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 28 Region 0: Memory at f000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) Subsystem: Lenovo Device [17aa:20e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at f040 (64-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) Subsystem: Lenovo Device [17aa:20e6] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx+ Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f0826800 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) Subsystem: Lenovo Device [17aa:20ee] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 30 Region 0: Memory at f060 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f0625000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 1840 [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo Device [17aa:20f0] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 20 Region 4: I/O ports at 1860 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo Device [17aa:20f0] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort-
Bug#767064: marked as done (firmware-iwlwifi: Where did iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode go?)
Your message dated Tue, 28 Oct 2014 12:35:41 + with message-id 1414499741.16849.39.ca...@decadent.org.uk and subject line Re: Bug#767064: firmware-iwlwifi: Where did iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode go? has caused the Debian Bug report #767064, regarding firmware-iwlwifi: Where did iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode go? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-iwlwifi Version: 0.43 Severity: wishlist User: debian-...@lists.debian.org Usertags: debian-edu When installing Debian Edu Jessie on a Thinkpad X200, we provide all the firmware debs available from ftp.debian.org in /firmware/ on the ISO. Yet a question show up asking for more firmware, as the files iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode are missing. In the changelog for firmware-iwlwifi I find that iwlwifi-5000-1.ucode was added in version 0.15 to close bug #497717. I find no similar comment about the iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode files. Were they ever part of this firmware package? What happened with the iwlwifi-5000-1.ucode file? Is it possible to reinsert it, and perhaps also add the two other requested files? -- Happy hacking Peter Reinholdtsen ---End Message--- ---BeginMessage--- On Tue, 2014-10-28 at 09:39 +0100, Petter Reinholdtsen wrote: Package: firmware-iwlwifi Version: 0.43 Severity: wishlist User: debian-...@lists.debian.org Usertags: debian-edu When installing Debian Edu Jessie on a Thinkpad X200, we provide all the firmware debs available from ftp.debian.org in /firmware/ on the ISO. Yet a question show up asking for more firmware, as the files iwlwifi-5000-1.ucode, iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode are missing. In the changelog for firmware-iwlwifi I find that iwlwifi-5000-1.ucode was added in version 0.15 to close bug #497717. I find no similar comment about the iwlwifi-5000-3.ucode and iwlwifi-5000-4.ucode files. Were they ever part of this firmware package? What happened with the iwlwifi-5000-1.ucode file? Is it possible to reinsert it, and perhaps also add the two other requested files? The second number in the filename is the API version and the driver usually supports a range of different versions. It will request the highest version it supports; then if that fails it will sequentially request earlier versions. I try to include only the highest version that stable, testing and unstable kernels will request. There is no need to add any others. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#767130: Suspend/sleep causes my laptop to never wake up, lose data
Package: linux-image-amd64 Version: 3.16-2-amd64 Severity: critical When I close the lid on my laptop, it goes to sleep (suspend). When I open it up, the system never wakes up, which equals to system crash and data loss. Hardware: Toshiba Portege Z30 Ultrabook, Intel Core i7 4600U DMI decode: http://pastebin.com/30Jhfr77 lspci -v: http://pastebin.com/sBWXCGjM The problem could be upower, or kernel itself. This bug makes Debian a non-functional on this laptop. Sadly I can't use Debian 7.0 Wheezy on it, due to lack of Ethernet drivers. I am using Debian GNU/Linux 8.0 Jessie BETA, kernel Linux version 3.16-2-amd64 Debian 3.16.3-2 (2014-09-20) -- -Alexey Eromenko Technologov, 28.Oct.2014. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOJ6w=HGmif8gcUJHu5iwr0qO5gwZNMLhR9a-CoHuOpy4=0...@mail.gmail.com
Bug#767130: marked as done (Suspend/sleep causes my laptop to never wake up, lose data)
Your message dated Tue, 28 Oct 2014 16:57:22 + with message-id 1414515442.16849.44.ca...@decadent.org.uk and subject line Re: Bug#767130: Suspend/sleep causes my laptop to never wake up, lose data has caused the Debian Bug report #767130, regarding Suspend/sleep causes my laptop to never wake up, lose data to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-amd64 Version: 3.16-2-amd64 Severity: critical When I close the lid on my laptop, it goes to sleep (suspend). When I open it up, the system never wakes up, which equals to system crash and data loss. Hardware: Toshiba Portege Z30 Ultrabook, Intel Core i7 4600U DMI decode: http://pastebin.com/30Jhfr77 lspci -v: http://pastebin.com/sBWXCGjM The problem could be upower, or kernel itself. This bug makes Debian a non-functional on this laptop. Sadly I can't use Debian 7.0 Wheezy on it, due to lack of Ethernet drivers. I am using Debian GNU/Linux 8.0 Jessie BETA, kernel Linux version 3.16-2-amd64 Debian 3.16.3-2 (2014-09-20) -- -Alexey Eromenko Technologov, 28.Oct.2014. ---End Message--- ---BeginMessage--- On Tue, 2014-10-28 at 18:35 +0200, Alexey Eromenko wrote: Package: linux-image-amd64 Version: 3.16-2-amd64 This is not a real version number. Use 'reportbug linux-image-3.16-2-amd64' to open a bug report against the right package. Severity: critical When I close the lid on my laptop, it goes to sleep (suspend). When I open it up, the system never wakes up, which equals to system crash and data loss. Same happens if your battery runs out. Sorry, but we cannot accept that every kernel crash is 'critical', because then we would never release Debian. Please use severity 'important' for your new bug report. Hardware: Toshiba Portege Z30 Ultrabook, Intel Core i7 4600U DMI decode: http://pastebin.com/30Jhfr77 lspci -v: http://pastebin.com/sBWXCGjM [...] You should use attachments not pastebins. But when you report against the correct package, your report will automatically include this information. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#767147: (no subject)
Subject: linux-image-3.2.0-4-amd64: Problems with Kworld 'PCI Analog TV Card Lite' Package: src:linux Version: 3.2.63-2 Severity: normal Dear Maintainer, I am trying to setup Kworld 'PCI Analog TV Card Lite' so I can use it as a fm tuner. Chips on the card are the same with the chips listed on this page: http://linuxtv.org/wiki/index.php/Kworld_PCI_Analog_TV_Card_Lite except for PCI Bridge which is: SAA7134HL. Card is not listed in Documentation/video4linux/CARDLIST.saa7134, and is not recognised by the kernel. I have added file in /etc/modprobe.d/ which contains exactly one line: options saa7134 card=153 tuner=61 With this line card and tuner are recognised by the kernel, but I have problems with listening to the radio. I am using saa7134-alsa module for grabbing the sound from the PCI bus. When I am listening to the radio with mplayer I get one of two error messages: 1) Cache empty, consider increasing -cache and/or -cache-min. [performance issue] 2) Error reading audio: Broken pipe ALSA xrun!!! (at least 1414426681501.283 ms long) Recovered from cross-run, some frames may be left out! After that there are gaps in the sound coming from the card. I get this messages randomly, but usually one is replaced with the other after reboot. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=c30a54c1-14f3-4ccd-87cc-122399a74a60 ro quiet video=vesafb:ywrap,mtrr:3 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [5.013445] udevd[401]: starting version 175 [5.203735] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 [5.203741] ACPI: Power Button [PWRB] [5.203797] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [5.203801] ACPI: Power Button [PWRF] [5.289152] iTCO_vendor_support: vendor-support=0 [5.296645] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [5.296723] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [5.312961] ACPI: Requesting acpi_cpufreq [5.628478] input: PC Speaker as /devices/platform/pcspkr/input/input4 [5.658302] Linux media interface: v0.10 [5.662734] IR NEC protocol handler initialized [5.698657] Linux video capture interface: v2.00 [5.800442] IR RC5(x) protocol handler initialized [5.830146] IR RC6 protocol handler initialized [5.863075] IR JVC protocol handler initialized [5.872753] IR Sony protocol handler initialized [6.021604] saa7130/34: v4l2 driver version 0, 2, 17 loaded [6.021653] saa7134[0]: found at :04:02.0, rev: 1, irq: 17, latency: 32, mmio: 0xfbdff000 [6.021662] saa7134[0]: subsystem: 17de:7126, board: Kworld Plus TV Analog Lite PCI [card=153,insmod option] [6.021680] saa7134[0]: board init: gpio is c04078 [6.037034] IR MCE Keyboard/mouse protocol handler initialized [6.044496] lirc_dev: IR Remote Control driver registered, major 250 [6.051236] IR LIRC bridge handler initialized [6.059436] Registered IR keymap rc-kworld-plus-tv-analog [6.059522] input: saa7134 IR (Kworld Plus TV Anal as /devices/pci:00/:00:1c.3/:03:00.0/:04:02.0/rc/rc0/input5 [6.059565] rc0: saa7134 IR (Kworld Plus TV Anal as /devices/pci:00/:00:1c.3/:03:00.0/:04:02.0/rc/rc0 [6.087300] nvidia: module license 'NVIDIA' taints kernel. [6.087304] Disabling lock debugging due to kernel taint [6.172159] nvidia :01:00.0: setting latency timer to 64 [6.172163] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [6.172224] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 [6.207098] saa7134[0]: i2c eeprom 00: de 17 26 71 10 28 ff ff ff ff ff ff ff ff ff ff [6.207109] saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207119] saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207128] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207137] saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207146] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207155] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207164] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207173] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207182] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207191] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.207200] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [
Processed: linux-image-3.16-3-amd64: OpenCL doesn't work on Intel GPU
Processing control commands: affects -1 beignet Bug #767148 [src:linux] linux-image-3.16-3-amd64: OpenCL doesn't work on Intel GPU Added indication that 767148 affects beignet tags -1 fixed-upstream Bug #767148 [src:linux] linux-image-3.16-3-amd64: OpenCL doesn't work on Intel GPU Added tag(s) fixed-upstream. -- 767148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b.14145208094865.transcr...@bugs.debian.org
Bug#767148: linux-image-3.16-3-amd64: OpenCL doesn't work on Intel GPU
Package: src:linux Version: 3.16.5-1 Severity: important Control: affects -1 beignet Control: tags -1 fixed-upstream X-Debbugs-CC: s...@debian.org,pkg-opencl-de...@lists.alioth.debian.org In current jessie, beignet (OpenCL for Intel GPUs, 0.8-1.1) is non-functional: $ sudo apt-get install beignet python3-pyopencl $ python3 beignet_test.py python3: /tmp/buildd/beignet-0.8/src/intel/intel_gpgpu.c:427: intel_gpgpu_check_binded_buf_address: Assertion `gpgpu-binded_buf[i]-offset != 0' failed. Aborted It had previously worked in Ubuntu 14.04 (beignet 0.8-1, linux 3.13.0) on the same hardware (i5-3230M). (beignet isn't in Wheezy.) beignet's upstream documentation [0] says this is a known issue with 3.15/3.16 kernels and suggested the workaround $ sudo sh -c echo -n 0 /sys/module/i915/parameters/enable_cmd_parser which made it work, but the description [1] suggests this will break some OpenGL functionality and might be a security risk. This is fixed upstream by [2]; I haven't yet tried this. [0] http://www.freedesktop.org/wiki/Software/Beignet/ [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/i915_cmd_parser.c [2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/i915_cmd_parser.c?id=c9224faa59c3071ecfa2d4b24592f4eb61e57069 -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=UUID=1ebca590-0a18-44f5-8d75-f96f5ca7c36e ro quiet ** Not tainted ** Kernel log: [ 27.077954] ACPI Warning: SystemIO range 0x0530-0x053f conflicts with OpRegion 0x0500-0x057f (\GPXX) (20140424/utaddress-258) [ 27.077959] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 27.077961] ACPI Warning: SystemIO range 0x0500-0x052f conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20140424/utaddress-258) [ 27.077965] ACPI Warning: SystemIO range 0x0500-0x052f conflicts with OpRegion 0x0500-0x057f (\GPXX) (20140424/utaddress-258) [ 27.077970] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 27.077972] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 27.248942] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 27.284399] toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler [ 27.284453] toshiba_bluetooth: Re-enabling Toshiba Bluetooth [ 27.502477] [drm] Memory usable by graphics device = 2048M [ 27.502492] [drm] Replacing VGA console driver [ 27.502508] checking generic (b000 408000) vs hw (b000 1000) [ 27.502512] fb: switching to inteldrmfb from simple [ 27.502568] Console: switching to colour dummy device 80x25 [ 27.524376] i915 :00:02.0: irq 43 for MSI/MSI-X [ 27.524393] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 27.524394] [drm] Driver supports precise vblank timestamp query. [ 27.524506] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 27.565932] fbcon: inteldrmfb (fb0) is primary device [ 27.582152] wmi: Mapper loaded [ 27.694480] Bluetooth: Core ver 2.19 [ 27.694494] NET: Registered protocol family 31 [ 27.694495] Bluetooth: HCI device and connection manager initialized [ 27.694501] Bluetooth: HCI socket layer initialized [ 27.694502] Bluetooth: L2CAP socket layer initialized [ 27.694509] Bluetooth: SCO socket layer initialized [ 27.833463] usbcore: registered new interface driver btusb [ 27.907603] cfg80211: Calling CRDA to update world regulatory domain [ 27.951039] EFI Variables Facility v0.08 2004-May-17 [ 27.959345] pstore: Registered efi as persistent store backend [ 28.248411] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0). [ 28.248413] atkbd serio0: Use 'setkeycodes 7c keycode' to make it known. [ 28.279982] input: PC Speaker as /devices/platform/pcspkr/input/input14 [ 28.377421] Console: switching to colour frame buffer device 170x48 [ 28.380569] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 28.380570] i915 :00:02.0: registered panic notifier [ 28.401883] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 28.401985] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input15 [ 28.402061] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 28.402441] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X [ 28.421461] ath: phy0: ASPM enabled: 0x43 [ 28.421465] ath: EEPROM regdomain: 0x6a [ 28.421466] ath: EEPROM indicates we should expect a direct regpair map [
Re: Bug#767042: [jessie daily 2014-10-27] [armhf] Installation report: LeMaker Banana Pi - problems with autoloading the realtek ethernet PHY driver module
On Mon, Oct 27, 2014 at 11:54:47PM +, Ben Hutchings wrote: On Tue, 2014-10-28 at 00:18 +0100, Cyril Brulebois wrote: Cc+=debian-kernel@ for input since I seem to recall having seen PHY drivers (including in a realtek context) being mentioned lately, at least on IRC, maybe on list as well. I don't understand this. Karsten Merker mer...@debian.org (2014-10-27): [...] [ 73.104782] libphy: stmmac: probed [ 73.104812] eth0: No PHY found i.e. the correct ethernet MAC driver (stmmac) gets loaded automatically, but the necessary PHY driver (realtek) does not. [...] [ 499.392561] libphy: stmmac: probed [ 499.392592] eth0: PHY ID 001cc915 at 0 IRQ POLL (stmmac-0:00) active [ 499.392604] eth0: PHY ID 001cc915 at 1 IRQ POLL (stmmac-0:01) and the ethernet interface works. The kernel version used in this installer build is 3.16.5-1. $ modinfo -F alias realtek mdio:???111001100100100010101 mdio:???111001100100100010010 In hex those are 1cc915 and 1cc912. (The 11 most significant bits are unspecified.) So modprobe certainly should find this module when requested by phylib. I have retried the installation today and tried something I had not done yesterday: just rmmod and directly afterwards modprobe the stmmac module. This results in the realtek PHY module getting auto-loaded, so the modprobe mechanism seems to work correctly there, but the question remains why this does not happen upon the first loading of the stmmac module. A protocol from d-i: No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list. -- start shell ~ # lsmod Module Size Used by stmmac 73442 0 nls_utf81170 2 nls_cp437 4767 1 loop 16202 2 isofs 31318 1 vfat9621 1 fat52693 1 vfat ext4 485433 0 crc16 1146 1 ext4 mbcache 8210 1 ext4 jbd2 88199 1 ext4 sg 20824 0 sd_mod 38535 2 crc_t10dif 1041 1 sd_mod crct10dif_common1159 1 crc_t10dif usb_storage41751 1 ahci_sunxi 2652 0 libahci_platform4679 1 ahci_sunxi libahci23069 1 libahci_platform libata161761 3 libahci,libahci_platform,ahci_sunxi ohci_platform 4062 0 ohci_hcd 37591 1 ohci_platform scsi_mod 175644 4 sg,usb_storage,libata,sd_mod ehci_platform 4526 0 phy_sun4i_usb 4216 4 ehci_hcd 64373 1 ehci_platform sunxi_mmc 10557 0 ~ # dmesg | tail -8 [ 31.558145] ISO 9660 Extensions: RRIP_1991A [ 77.839161] stmmaceth 1c5.ethernet: no reset control found [ 77.839194] Ring mode enabled [ 77.839202] No HW DMA feature register supported [ 77.839210] Normal descriptors [ 77.839217] TX Checksum insertion supported [ 77.844560] libphy: stmmac: probed [ 77.844589] eth0: No PHY found ~ # rmmod stmmac ~ # modprobe stmmac ~ # dmesg | tail -8 [ 330.112850] stmmaceth 1c5.ethernet: no reset control found [ 330.112883] Ring mode enabled [ 330.112891] No HW DMA feature register supported [ 330.112898] Normal descriptors [ 330.112905] TX Checksum insertion supported [ 330.140101] libphy: stmmac: probed [ 330.140139] eth0: PHY ID 001cc915 at 0 IRQ POLL (stmmac-0:00) active [ 330.140150] eth0: PHY ID 001cc915 at 1 IRQ POLL (stmmac-0:01) ~ # lsmod Module Size Used by realtek 1563 0 stmmac 73442 0 nls_utf81170 2 nls_cp437 4767 1 loop 16202 2 isofs 31318 1 vfat9621 1 fat52693 1 vfat ext4 485433 0 crc16 1146 1 ext4 mbcache 8210 1 ext4 jbd2 88199 1 ext4 sg 20824 0 sd_mod 38535 2 crc_t10dif 1041 1 sd_mod crct10dif_common1159 1 crc_t10dif usb_storage41751 1 ahci_sunxi 2652 0 libahci_platform4679 1 ahci_sunxi libahci23069 1 libahci_platform libata161761 3 libahci,libahci_platform,ahci_sunxi ohci_platform 4062 0 ohci_hcd 37591 1 ohci_platform scsi_mod 175644 4 sg,usb_storage,libata,sd_mod ehci_platform 4526 0 phy_sun4i_usb 4216 4 ehci_hcd 64373 1 ehci_platform sunxi_mmc 10557 0 As udev is *not* involved in loading MDIO PHY drivers (NIC drivers expect them to be bound synchronously) it isn't easy to monitor what's going on. You could replace modprobe with a script that logs its arguments to a file before calling the real modprobe. That should tell us
Bug#711592: jessie kernel
Hi, Any chance this could be fixed for jessie release? -- Valentin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141029005435.ga9...@gavran.carpriv.carnet.hr
