Re: Request: Enable Symbols for Lenovo Thinkpad P14s Gen4 (AMD)

Salvatore Bonaccorso writes: > On Mon, Dec 11, 2023 at 06:36:39PM -0500, Michael T. Kloos wrote: > >> Copy that. > > Michael, sorry I lost you. What do you mean? That's an ack from before packet radio :-) https://en.wiktionary.org/wiki/copy_that Bjørn

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

Salvatore Bonaccorso writes: > AFAIK there is no commit upstream with fixes tag on that commit. But > Bjorn suspects that might be the suspicious commit introducing the > issue. Yes, I noticed that, so I could very well be wrong... But it stood out as the only change to any x86 IOAPIC stuff

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

Guy Durrieu writes: > > [ 0.117782] Kernel panic — not syncing: timer doesn’t work through > Interrupt- > remapped I0-APIC > [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 > Debian > 6.1.20-1 > [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming

Bug#1022022: New btusb hardware IDs (MT7922, MT7921, others)

Chris Hofstaedtler writes: > * Diederik de Haas [221019 00:07]: >> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote: >> > it appears quite some new btusb hardware was released recently. >> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c: >> >

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

Hank Barta writes: > ** Kernel log: > [ 723.735217] mmc0: sdhci: Timeout: 0x | Int stat: 0x00018000 > [ 723.741743] mmc0: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003 > [ 723.748270] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x0001 > [ 723.754797] mmc0: sdhci: Caps:

Bug#1010365: linux: failure to boot on Raspberry Pi Compute Module 4 (black screen)

Cyril Brulebois writes: > Cyril Brulebois (2022-04-29): >> > I'll try and pinpoint when it broke using the various intermediary >> > versions: >> > >> > - 5.17~rc3-1~exp1 >> >> The first attempt was sufficient: it breaks as early as that version. > > Using the same base image as before, and

Re: Problem: USB Ethernet PCI-E card does not work with kernel 5.10.0-11-amd64

Flacusbigotis writes: > The kernel logs indicating issues in Bullseye include a warning of a "host > failure" by xhci_hcd, and several write/read errors by the ax88179 ethernet > driver/module for the card, as follows: > > Feb 22 17:22:53 server1 kernel: [1.380198] xhci_hcd :1c:00.0:

Bug#1002465: /boot/vmlinuz-5.10.0-10-amd64: btusb: CSR clone fails with "debugfs: File 'dut_mode' in directory 'hci1' already present!"

Package: src:linux Version: 5.10.84-1 Severity: normal File: /boot/vmlinuz-5.10.0-10-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just got a couple of CSR clones of a type I haven't tried before. Unfortunately they fail with the error message: "debugfs: File 'dut_mode' in directory

Re: Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners

Martin-Éric Racine writes: >> [1] https://wiki.debian.org/DeviceDatabase/USB YUCK! That is fundamentally flawed. It is so misleading that it is harmful. Could someone with Wiki access pleaase delete that page? Bjørn

Bug#990868: lenovo T460 Shutdown Problem

Faustin Lammler writes: > Hi! > I seem to have the same problem on my T460s and it is impossible to > suspend the laptop (lid close or systemctl suspend). > > As far as I can remember, the problem appeared with kernel 5 branch (bpo > on buster). > > At that time I did not wanted to open a bug

Re: Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002

Heiner Kallweit writes: > A number of Gigabyte boards from ~2009 have broken BIOS support, resulting in > the PHY > reporting an invalid PHY ID. Realtek / Gigabyte don't release errata > information, > therefore there's not much that can be done. In bugzilla.kernel.org you can > find >

Bug#965074: Patches to make multicast proccesing on CDC NCM drivers

Santiago Ruano Rincón writes: > El 02/09/20 a las 17:45, Greg KH escribió: >> On Wed, Sep 02, 2020 at 03:27:28PM +0200, Santiago Ruano Rincón wrote: >> >> > This: >> > >> > 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6 >> > e10dcb1b6ba714243ad5a35a11b91cc14103a9a9 >> >

Bug#969365: USB-C dock lacks multicast Ethernet functionality (so IPv6 is broken)

"Santiago R.R." writes: > The patches proposed by Miguel Rodríguez have been merged upstream, and > are part of 5.9-rc1 now. C.f. commits: > 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6 > e10dcb1b6ba714243ad5a35a11b91cc14103a9a9 > e506addeff844237d60545ef4f6141de21471caf >

Bug#965074: cdc_ncm: ethernet multicast traffic is filtered out

FWIW, I made an attempt resubmitting these patches since it looked like I was part of the problem back in 2018 ;-) I'd CCed you, and would appreciate it if you could test the series. I don't have any cdc_ncm devices with multicast filter support AFAIK. Bjørn

Bug#964480: linux: ath9k (USB) broken in upstresm linux 5.7.3 after commit 6602f080cb

Juergen writes: > In 5.7 reverting 6602f080cb is known to fix the problem, but it hasn't yet > been > analyzed by an expert, therefore I'd like to report my findings to perhaps get > an expert interested:-) > > At least one problem is in function ath9k_hif_usb_reg_in_cb(). In the call to >

Bug#949020: linux-image-5.6.0-2-amd64: Lenovo poweroff/suspend failure

Package: src:linux Followup-For: Bug #949020 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just confirming that this issue is still present, causing a terrible user experience when upgrading from Buster to Bullseye on a Lenovo laptop. Verified on a 4th Gen Thinkpad X1 Carbon. Setting

Bug#961459: linux-signed-arm64: option that might support raspberry pi 4 usb

Rob Browning writes: > If I get a chance and figure out how, I can try to build a local kernel > with that option and test it, or I could fairly quickly test any version > uploaded somewhere like experimental. I have done this, and verified that the USB ports work if CONFIG_PCIE_BRCMSTB is

Bug#961130: ethtool can read DOM values

Ben Hutchings writes: > On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: >> Package: ethtool >> Version: 1:4.19-1 >> Severity: important >> The command ethtool -m is unable to read the transceiver DOM values. > > Again, this is a driver or hardware issue, not a bug in ethtool. > > [...]

Bug#960702: ethtool -m values change when output is redirected

"Yannis Aribaud" writes: > Package: ethtool > Version: 1:4.19-1 > Severity: important > I'm facing a very strange behavior. The command ethtool -m report the > transceiver DOM values correctly, but when the command output is redirected > to an other program, values change to somthing else.

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Bjørn Mork writes: > Note that I found that I had to remove the cma=xx option raspi-firmware > wants to put into the cmdline.txt. This messed up mailbox access to the > firmware, and took several drivers/devices with it in the fall. Don't > think the SD card was one one them. But

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Lucas Nussbaum writes: > On 09/05/20 at 20:44 +0200, Bjørn Mork wrote: >> Please enable CONFIG_PCIE_BRCMSTB on arm64. >> >> The Raspberry Pi 4 has a VL805 xhci controller connected to the >> PCIe bus on the SoC. All USB ports are connected to this controller. >>

Bug#960129: linux-image-5.6.0-1-arm64: please enable CONFIG_PCIE_BRCMSTB in the arm64 kernel for Raspberry Pi 4

Package: src:linux Version: 5.6.7-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Please enable CONFIG_PCIE_BRCMSTB on arm64. The Raspberry Pi 4 has a VL805 xhci controller connected to the PCIe bus on the SoC. All USB ports are connected to this

Re: initramfs-tools_0.136_source.changes ACCEPTED into unstable

Debian FTP Masters writes: >* [835d584] mkinitramfs: Copy modules.builtin.bin into initramfs > (Closes: #948257) It's a bit depressing to see bugs hidden under the carpet instead of solved. But whatever. If you prefer adding a bug in mkinitramfs instead of fixing the problem, then I

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Pierrick CHANTEUX writes: > This bug resulted in complete system breakage and I couldn't boot > anymore (systemd failing to load Kernel modules). I can guarantee that > this isn't only cosmetic. > > I believe this isn't related to initramfs-tools, because downgrading > kmod and libkmod2 from

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Bjørn Mork writes: > Marco d'Itri writes: > >> Control: severity -1 normal >> Control: tags -1 patch >> Control: reassign -1 initramfs-tools >> >> On Jan 06, crvi wrote: >> >>>* What outcome did you expect instead? >>> >>

Re: Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Marco d'Itri writes: > Control: severity -1 normal > Control: tags -1 patch > Control: reassign -1 initramfs-tools > > On Jan 06, crvi wrote: > >>* What outcome did you expect instead? >> >> Successful ramfs generation > Do you have any reason to believe that the initrfamfs was not

Bug#926261: closed by Ben Hutchings (Re: Bug#926261: linux-image-4.19.0-4-amd64: fan continiously spinning above 6900 RPM after resume on lenovo carbon x1 thinkpad with isa adap

Not going to argue against this being a firmware bug. I'm sure that is true. But Linux must deal with buggy firmware. Else it cannot run on any real system :-) And this bug (or at least the bad effect on Linux) is a regression introduced by commit c3a696b6e8f8 ("ACPI / EC: Use busy polling

Re: why is the build so complex ?

"Enrico Weigelt, metux IT consult" writes: > while trying to build a debian kernel w/ some minor config changes > (actually, just need the gpio keyboard modules), Can't help with answers to your questions, but i believe I can help with this task. It's as simple as $ git clone

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

Bjørn Mork writes: > Given this, there is an extremely suspicious commit added in v4.18.20: > > 06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for > gen4/gen5") > > I do have an old laptop with an affected chipset generation, and > verifie

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

Ben Hutchings writes: > On Mon, 2018-12-03 at 23:08 +0100, TS wrote: > >> Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to >> unstable. This issue here seems not to be wide spread, or reproducible? > > Hard to tell. There are a few people that reported the same

Bug#906593: Crash with intel 8265

Hugo Mercier writes: > It seems I have a similar problem on a Thinkpad X1 4th generation. So, since I also run Debian sid on one of those, and haven't got any issues, I thought I would compare firmware versions etc > $ lspci -v > 04:00.0 Network controller: Intel Corporation Wireless 8265 /

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

Phil writes: > Hi, I hope you're all doing well. > > Shall we/I maybe reopen a new issue? I believe so. I am almost sure we fixed the original memset BUG in cdc_ncm_fill_tx_frame. Or at least one of them... So you are probably seeing another issue if you still have problems with that fix in

Re: linux_4.17.3-1_multi.changes ACCEPTED into unstable, unstable

Debian FTP Masters writes: > - cdc_ncm: avoid padding beyond end of skb I believe this fixes https://bugs.debian.org/893393 , but I have no way to verify it. Bjørn

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

This issue should be fixed by commit 49c2c3f246e2 ("cdc_ncm: avoid padding beyond end of skb") which has been backported to v4.17.3, v4.16.18 and v4.14.52. Please check again with one of those kernel versions (or newer). I see now that the fix doesn't apply cleanly to v4.9 stable due to

Bug#897572: urandom hang in early boot

Ben Hutchings writes: > On Tue, 2018-05-08 at 11:12 +1200, Ben Caradoc-Davies wrote: >> On 08/05/18 05:34, Laurent Bigonville wrote: >> > Apparently it's also happening for other applications that are starting >> > later during the boot like GDM. >> > Somebody has reported

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

Горбешко Богдан writes: > vboxdrv(O) > binder_linux(O) > ashmem_linux(O) Can you reproduce the problem without these modules loaded? AFAICS there is no way the only memset in cdc_ncm can be called with crashing input parameters. Unless something is scribbling over the

Bug#871639: NULL pointer dereference in reset_common_ring+0xc3/0x170 [i915]

Package: src:linux Version: 4.9.30-2+deb9u3 Severity: normal File: /boot/vmlinuz-4.9.0-3-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've been having issues with the i915 driver ever since I got this Skylake laptop. The GPU is hanging every now and then. But the error handling has

Bug#864878: /boot/vmlinuz-4.9.0-3-amd64: Please enable CONFIG_HPFS_FS as a module

Package: src:linux Version: 4.9.30-2 Severity: wishlist File: /boot/vmlinuz-4.9.0-3-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, it's hard to claim this is important to me since I haven't noticed it was gone until today. But could you please re-enable CONFIG_HPFS_FS unless

Re: [PATCH initramfs-tools 0/9] Fix resume device configuration

Ben Hutchings writes: > The change in version 0.128 to wait for the resume device to appear > uncovered a number of systems for which the resume device is not > properly configured. In fact, systems with swap partitions that > are never available at boot could not be

Bug#859641: Please increase USBIP_VHCI_HC_PORTS and USBIP_VHCI_NR_HCS

Steve McIntyre writes: > In Linaro we're making a lot of use of USB-over-IP devices these days > for our testing lab. We've hit a (very small!) limit defined in kernel > config for the number of virtual host controllers and the ports > allowed per controller. > > Currently

Re: LED on keyboard

Jan Niggemann writes: > I'm building a 4.8.15 kernel (which is working great) for my Thinkpad > T460s. What bothers me, is that I can't get the LEDs on the F1 and F4 > key working ((F1=mute, F4=mic on/off). I checked CONFIG_ directives > that seem relevant to me, but - well, I'm

Bug#850064: /boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send related to bridge port link changes

OK, this looks like a known v4.8 stable regression, caused by the backport of commit 5d41ce29e3b9 ("net: icmp6_send should use dst dev to determine L3 domain") introduced in v4.8.10. Should be fixed by commit 79dc7e3f1cd3 ("net: handle no dst on skb in icmp6_send") as soon as Debian moves to v4.9

Bug#850064: /boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send related to bridge port link changes

The first crash dumps were from my console, which was overwritten by the later boot process and therefore incomplete. Should have dug up the complete logs from the console server in the first place.. Anyways, here are the complete stack traces: [509753.194825] ixgbe :02:00.0 uplink: NIC

Bug#850064: /boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send related to bridge port link changes

Package: src:linux Version: 4.8.11-1 Severity: important File: /boot/vmlinuz-4.8.0-2-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I just had two crashes in a row in icmp6_send while rebooting a switch in the other end of one of the br0 bridge ports. Both crash dumps

Bug#832458: linux-image-4.6.0-0.bpo.1-amd64: Please enable SND_SOC_INTEL_BYT_MAX98090_MACH, needed for some Baytrail devices

Ben Hutchings writes: > On Mon, 2016-07-25 at 13:10 -0600, Ivan M wrote: >> Package: src:linux >> Version: 4.6.3-1~bpo8+1 >> Severity: normal >> >> Dear Maintainer, >> >> Please enable CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH=m - it is >> necessary for audio on certain

Bug#833918: linux: Please enable cdc_ncm and cdc_mbim in d-i to support 'Dell 4-in-1 Adapter' Ethernet

John Paul Adrian Glaubitz writes: > This adapter uses the cdc_ncm/cdc_mbim kernel modules which are currently > being disabled for > debian-installer as those were suspected to be used by modems only [2], which > is not the > case, however. cdc_mbim is

Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing

Ben Hutchings <b...@decadent.org.uk> writes: > On Wed, 2016-04-20 at 20:51 +0200, Bjørn Mork wrote: >> Ben Hutchings <b...@decadent.org.uk> writes: >> >> > >> > Our upstream is linux-firmware.git, not a hundred vendor web sites. >> > Fran

Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing

Ben Hutchings writes: > Our upstream is linux-firmware.git, not a hundred vendor web sites. > Frankly I'm quite sick of the iwlwifi maintainers thinking their > firmware is special and should be distributed differently from every. Huh? I always though they sent a pull

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Ben Hutchings <b...@decadent.org.uk> writes: > On Mon, 2016-04-11 at 09:55 +0200, Bjørn Mork wrote: >> Ben Hutchings <b...@decadent.org.uk> writes: >> > >> > On Sun, 2016-04-10 at 11:15 -0700, Vagrant Cascadian wrote: >> > > >> > &

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Ben Hutchings writes: > On Sun, 2016-04-10 at 11:15 -0700, Vagrant Cascadian wrote: >> It works for the most part, but floods syslog with messages: >> >> [501966.870273] net_ratelimit: 35702 callbacks suppressed >> [501966.875438] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

Ben Hutchings <b...@decadent.org.uk> writes: > On Wed, 2016-04-06 at 16:51 +0200, Bjørn Mork wrote: >> Antonis Christofides <anth...@itia.ntua.gr> writes: >> >> > >> > Apr  5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel >&g

Bug#820176: 3.16.7-ckt25-1: BUG: unable to handle kernel paging request (when connecting a USB device)

Antonis Christofides writes: > Apr 5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel > paging request at eba40a800380 > Apr 5 13:32:47 thames kernel: [86003.994005] IP: [] > kfree+0x76/0x220 .. > Apr 5 13:32:47 thames kernel: [86003.994679] Call

Bug#820061: linux-image-amd64: kernel hangs since debian 8.4

Benoît Tonnerre writes: > Apr 4 18:52:55 pci003-01 kernel: [ 79.329223] RIP: > 0010:[] > [] radeon_fence_ref+0xd/0x50 [radeon] > Apr 4 18:52:55 pci003-01 kernel: [ 79.330192] RSP: 0018:88003639fb18 > EFLAGS: 00010292 > Apr 4 18:52:55 pci003-01 kernel: [ 79.331154]

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

Bug#764263: linux-image-3.16-2-amd64: WARNING at drivers/base/firmware_class.c:1109 _request_firmware+0x521/0xaf0() [btusb?]

Ben Hutchings b...@decadent.org.uk writes: On Mon, 2014-10-06 at 20:15 +0200, Julien Cristau wrote: Package: src:linux Version: 3.16.3-2 Severity: normal Hi, I get the following trace in my kernel log, which I don't think I've seen in pre-3.16 versions: Sep 29 19:12:49 betterave

Re: Enabling MBIM in Debian

Ben Hutchings b...@decadent.org.uk writes: Starting with linux version 3.8.2-1~experimental.1 we've included the new cdc_mbim driver for MBIM (Mobile Broadband Interface Model). Newer modems support both NCM or MBIM, but only one at a time, selected by the kernel drivers. For compatibility

Re: Bug#753816: [systemd] Broken audio

Michael Biebl bi...@debian.org writes: Be aware that systemd-modules-load does *not* read module parameters from /etc/modules. You'll need to set them via a /etc/modprobe.d/ file. Hmm... Is that considered a bug, or is it just the way things are going to be? The modules(5) man page from the

Re: Netconsole scripts for Debian

Pavel Odintsov pavel.odint...@gmail.com writes: Hello! At now I configure netconsole dynamically and got network configuration from ip route command. For getting netconsole server MAC address I use arping to it. But I can generate modprobe configuration file with current configuration and

Re: Netconsole scripts for Debian

Ritesh Raj Sarraf r...@debian.org writes: On 06/17/2014 03:00 PM, Pavel Odintsov wrote: Hello, folks! I'm prepared and thoroughly tested scripts for managing netconsole kernel facility in Debian 6/7. Netconsole facility is very useful for debugging kernel bugs. These scripts are

Bug#730065: document new_id interface

Geert Stappers stapp...@stappers.nl writes: Package: debian-kernel-handbook Version: 1.0.15 Severity: wishlist Op 2013-11-17 om 12:28 schreef Bastian Blank: snip/ Also you want to use new_id interface[1] if possible. Bastian [1]: /sys/class/usb/drivers/*/new_id

Bug#728535: which size increment to expect

Geert Stappers stapp...@stappers.nl writes: Op 2013-11-17 om 11:15 schreef Geert Stappers: Op 2013-11-17 om 10:55 schreef Geert Stappers: Edit on the kernel module source file, to add USB ID. Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger

Bug#729801: linux-image-3.10-3-amd64: kernel module i2c-hid does not exist

Ben Hutchings b...@decadent.org.uk writes: Can I compile the module by my own or can it be integrated into Debian? You might be able to compile the module but I can't provide simple instructions for this. Since this is a simple driver with few dependencies, it seems to be as simple as 1)

Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)

Petter Reinholdtsen p...@hungry.com writes: I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp. A similar device is mentioned in URL:

Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)

Steve Cotton st...@s.cotton.clara.co.uk writes: On Tue, Oct 15, 2013 at 14:08 +0200, Petter Reinholdtsen wrote: Dear Maintainer, I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001

Bug#723761: irq 16: nobody cared errors for the mptsas driver

Marco d'Itri m...@linux.it writes: Package: src:linux Version: 3.2.46-1+deb7u1 Severity: normal This is an IBM x3250 server. At boot time I get: [7.160384] scsi2 : ioc0: LSISAS1064E B1, FwRev=0110h, Ports=1, MaxQ=511, IRQ=16 [7.184758] mptsas: ioc0: attaching sata device:

Bug#721005: linux: sierra Gobi 3000 WWAN no longer works

Christoph Anton Mitterer cales...@scientia.net writes: I'm having a Fujitsu Lifebook E782 which has some Sierra Gobi 3000 UMTS modem in it. For many years it simply used to work perfectly, but a year ago or so it already stopped working (i.e. wasn't detected anymore by the kernel)... but

Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation

Shannon Dealy de...@deatech.com writes: I have not seen this problem or any of the other iwl instabilities in a long time, however, I have been running with these option lines disabling 11n functionality in order to achieve that stability: options iwlagn 11n_disable50=1 options

Bug#719623: linux-image-3.10-2-amd64: kernel panic on inserting DVB-T stick

...@gmail.com Reference: http://bugs.debian.org/719623 Cc: Mauro Carvalho Chehab m.che...@samsung.com Signed-off-by: Bjørn Mork bj...@mork.no --- drivers/media/common/siano/smsdvb-main.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/media/common/siano/smsdvb-main.c b

Bug#717005: firmware-iwlwifi: Missing iwlwifi-3160-6.ucode and iwlwifi-7260-6.ucode

Ben Hutchings b...@decadent.org.uk writes: These files are for firmware ABI version 6, which apparently was never released. There are firmware files for these chips with ABI version 7. I'll add that firmware and update the driver so that's what it expects. Thanks for doing that. It's not

Bug#714754: firmware-iwlwifi: please include iwlwifi-7260-7.ucode and iwlwifi-3160-7.ucode

Package: firmware-iwlwifi Version: 0.38 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The new Intel 7260 and 3160 cards require new firmware. Patch is available upstream: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/109724 Please add. Thanks, Bjørn - --

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

Tomasz Figa tomasz.f...@gmail.com writes: Seeing from your posts you don't have any knowledge on how Linux kernel development works and even on how Allwinner's cooperation with our community looks (and seem to be completely closed to our effort of showing you the reality), so I'm not sure

Bug#710883: /boot/vmlinuz-3.2.0-4-amd64: iptables PREROUTING match on bridge VLAN interfaces stopped working between 2.6.32 and 3.2

Package: src:linux Version: 3.2.41-2+deb7u2 Severity: minor File: /boot/vmlinuz-3.2.0-4-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Intercepting http traffic entering VLAN tagged on a bridge interface stopped working after upgrading from Squeeze to Wheezy. I assume

Bug#681092: linux-image-3.2.0-3-686-pae: Sierra WWAN modem not functioning

Hello, do you still have this problem? I was looking at your log and the USB serial changes introduced around the time you hit this, and one of the suspicious patches seem to be mine... This looks very wrong: [3.075097] usbcore: registered new interface driver usbserial [3.075139] USB

Bug#703356: megasas: Failed to alloc kernel SGL buffer for IOCTL (ref.#688198)

Jean-Francois Chevrette jf.cr...@gmail.com writes: Package: src:linux Version: 3.2.39-2 Severity: important (first time submiting to a bug report, sorry if I missed anything) We are still affected by bug #688198 Yes, I see that it was closed after applying a related bugfix. But as I

Bug#703356: megasas: Failed to alloc kernel SGL buffer for IOCTL (ref.#688198)

Jean-Francois Chevrette jf.cr...@gmail.com writes: On Tue, Mar 19, 2013 at 4:21 AM, Bjørn Mork bj...@mork.no wrote: Maybe we can get some ideas about why this fails if you describe the conditions you experience the problem under. This server is running Xen 4.1 and a single VM. Nothing fancy

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

Ben Hutchings b...@decadent.org.uk writes: On Thu, 2013-02-28 at 11:31 +0100, Bjørn Mork wrote: Anyone able to spot the missing INIT_WORK()'s? Based on the I915_HAS_HOTPLUG(dev) test, I assume that leaving the first one out was intentional. But the second one cannot be left out

Bug#701953: initramfs-tools: Missing modules prevent passphrase entry with usb keyboard

Ben Caradoc-Davies ben.caradoc-dav...@csiro.au writes: Package: initramfs-tools Version: 0.109 Severity: critical Justification: breaks the whole system Others will have to decide on that, but it seems a bit high to me. This is an experimental kernel and you do hopefully not try to install

Bug#701869: linux-image-3.8-trunk-amd64: Please enable CONFIG_USB_NET_CDC_MBIM - new driver for Mobile Broadband modems

Package: src:linux Version: 3.8-1~experimental.1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, could you please enable this driver in 3.8 and later? bjorn@nemi:~$ grep MBIM /boot/config-3.8-trunk-amd64 # CONFIG_USB_NET_CDC_MBIM is not set It supports CDC MBIM

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

of upstream commit c2798b19bac2538393fc932bfbe59807a4734b3e failed to initialize the error_work struct for gen2 hardware, resulting in hitting a BUG in kernel/workqueue.c if/when the interrupt handler tried to queue error handling work. Signed-off-by: Bjørn Mork bj...@mork.no --- drivers/gpu/drm/i915

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

Just an additional note. I'll soon shut up now. I went looking at mainline, trying to find out why this bug never hit anyone there. And that's because it was implicitly fixed by this later commit in the same series as the backported gen2 fix: commit 8b2e326dc7c5aa6952c88656d04d0d81fd85a6f8

Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt

Kubo Hiroshi h-k...@geisya.or.jp writes: Hi. Do the functions 'i8xx_irq_handler' and 'queue_work_on' always appear in the call trace? I can't remember. If I encounter the problem again, I will check it. After the last reply, I encountered the same problems twice. In the both problems,

Bug#700572: initramfs-tools: The ehci-hcd module has been split into ehci-pci + ehci-hcd in Linux v3.8

Package: initramfs-tools Version: 0.98.8 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Linux v3.8 changes the name of the PCI ehci driver from ehci-hcd to ehci-pci. Ref commit adfa79d1c06a32650332930ca4c488ca570b3407 Author: Alan Stern st...@rowland.harvard.edu

Bug#699237: Huawei E220 does not work under Debian Wheezy

T hex...@gmail.com writes: Reloading module with: modprobe usbserial vendor=0x12d1 product=0x1003 Probably unrelated to your problem, but... You should not do that. This device is mode-switched by the usb-storage driver and handled in modem mode by the option driver. Forcing the generic

Bug#688198: megasas: Failed to alloc kernel SGL buffer for IOCTL - Possible regression from 2.6.32.41~3

-Transfer-Encoding: 8bit commit 98cb7e44 ([SCSI] megaraid_sas: Sanity check user supplied length before passing it to dma_alloc_coherent()) introduced a memory leak. Memory allocated for entries following zero length SGL entries will not be freed. Signed-off-by: Bjørn Mork bj...@mork.no --- drivers/scsi

Bug#688198: megasas: Failed to alloc kernel SGL buffer for IOCTL - Possible regression from 2.6.32.41~3

Todd Fleisher t...@fleetstreetops.com writes: I get this periodically (seemingly random - but usually once it starts happening it sticks around for a while, then disappears only to return later) when I'm using LSI's MegaCli64 utility. When the kernel logs the error the MegaCli64 command

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

Steinar Bang s...@dod.no writes: Ben Hutchings b...@decadent.org.uk: Please send a readable photograph of this text. The problem occurred for the third time, and I couldn't find the camera, so I'm typing in what's shown on the console. This time it had happened while the macine was sitting

Bug#692225: [3.2-3.6.4 regression] screen starts to flicker after suspend-to-disk

Jonathan Nieder jrnie...@gmail.com writes: Hi Bjørn, Sebastian Ramacher wrote[1]: I've recently upgrade from 3.2 to 3.6. Since the upgrade after resuming from supsend-to-disk the screen starts to flicker and the kernel log contains the following traceback: [ 4730.108047] [

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

Per Foreby p...@foreby.se writes: On 2012-10-01 23:29, Jonathan Nieder wrote: Per Foreby wrote: The debug logging from drm isn't forwarded via netconsole, so I suppose it isn't supposed to? Oh, that's because of the console_loglevel setting[1]. You can change it by running dmesg -n 8 (or

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

Per Foreby p...@foreby.se writes: On 2012-10-02 00:45, Bjørn Mork wrote: I believe the bug is in the dmesg utility. It should shift all values by one. Setting dmesg -n debug will currently log all messages with a level *higher* than debug. You're probably right about the bug. I don't know

Bug#684881: linux-image-3.2.0-3-amd64: increasing hardware compatibility: enable firmware-less support for e100

Package: src:linux Version: 3.2.21-3 Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello kernel team! I understand you plan at least one more kernel version before wheezy. Please consider backporting 8b0d2f9 net: e100: ucode is optional in some cases currently

Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

Julien Cristau jcris...@debian.org writes: On Fri, Jul 27, 2012 at 02:39:14 +0100, Wookey wrote: A way to confirm if the slowkeys feature is currently engaged would allow me to confirm this more directly next time.

Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

Vincent Lefevre vinc...@vinc17.net writes: I've finally found the solution: # apt-get install xkbset $ xkbset -a Thanks. That's useful. But I found an even better solution: apt-cache search xdm (install one of the alternatives) apt-get purge gdm3 This has the extra bonus that

Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

Vincent Lefevre vinc...@vinc17.net writes: On 2012-07-20 08:58:57 +0200, Vincent Lefevre wrote: So, it would seem that some part of the system would enable SlowKeys in my back for one of the keyboards (I recall that when this happens while I'm using the USB keyboard, only the USB keyboard is

Bug#682063: firmware-iwlwifi: Version 0.36 breaks firmware loading

Sylvestre Ledru sylves...@debian.org writes: Package: firmware-iwlwifi Version: 0.36 Severity: important Hello, With the version 0.36 of firmware-iwlwifi fails to load the iwlagn module with the error: Jul 19 08:39:23 pomegues kernel: [ 1241.775811] iwlagn :01:00.0: request for

Re: [PATCH] scripts/package/builddeb: upgrade to current practices

maximilian attems m...@stro.at writes: Jonathan already answered it, saying that firmwares are put in versioned dir. Just use git to look it up, easy: ~/src/linux-next (master %=)$ git log scripts/package/builddeb 6607ddadf93d19c7f64139f1475c342152f39fe5 But..but.. won't that prevent

Re: [PATCH] scripts/package/builddeb: upgrade to current practices

Martin-Éric Racine martin-eric.rac...@iki.fi writes: Does the kernel look for modules in versioned, then non-versioned directories, in that order? More importantly, does it even attempt looking in the versioned directory at all? /lib/udev/firmware.agent does this:

Bug#670241: Updated qmi_wwan backport based on v3.2.19, including new device IDs from v3.5-rc1

block 670241 by 681912 thanks Please don't implement this just yet. The ModemManager version in wheezy may choke on the ports provided by the new driver. Ref https://bugzilla.redhat.com/show_bug.cgi?id=835153 I've opened a bug against ModemManager requesting the addition of the upstream

Bug#670241: Updated qmi_wwan backport based on v3.2.19, including new device IDs from v3.5-rc1

Ben Hutchings b...@decadent.org.uk writes: On Tue, Jul 17, 2012 at 08:01:24PM +0200, Bjørn Mork wrote: Feel free to close this bug with a wontfix if you like. After all, the qmi_wwan driver will never be very useful in wheezy, given that the modemmanager package is frozen on a version too

Bug#681418: debugfs is a big security hole

Ben Hutchings b...@decadent.org.uk writes: I would like to address this by backporting this feature: commit d6e486868cde585842d55ba3b6ec57af090fc343 Author: Ludwig Nussel ludwig.nus...@suse.de Date: Wed Jan 25 11:52:28 2012 +0100 debugfs: add mode, uid and gid options and then

Re: cdc_ether, Huawei E173u-2, wrong MAC address of packets vs wwan0

Marcin Szewczyk marcin.szewc...@wodny.org writes: On Wed, Jun 13, 2012 at 07:58:18PM +0200, Bjørn Mork wrote: Marcin Szewczyk marcin.szewc...@wodny.org writes: When using RNDIS wwan0 interface has MAC address 02:50:f3:00:00:00 while packets coming from Internet have destination MAC address

  1   2   >