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 this
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 S
Tomasz Figa
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 if you are the rig
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
- -- Sys
Ben Hutchings 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 clear to me whether
7f 10 e8 79 92
[ 846.863906] RIP [] smsdvb_onresponse+0x264/0xa86 [smsdvb]
[ 846.863906] RSP
Reported-by: Johannes Rohr
Reference: http://bugs.debian.org/719623
Cc: Mauro Carvalho Chehab
Signed-off-by: Bjørn Mork
---
drivers/media/common/siano/smsdvb-main.c |3 ++-
1 file changed, 2 in
Shannon Dealy 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 iwlwifi 11n_disa
Christoph Anton Mitterer 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 it came back
> s
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 request whenever they felt
Ben Hutchings writes:
> On Wed, 2016-04-20 at 20:51 +0200, Bjørn Mork wrote:
>> Ben Hutchings writes:
>>
>> >
>> > Our upstream is linux-firmware.git, not a hundred vendor web sites.
>> > Frankly I'm quite sick of the iwlwifi maintainers thinki
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 these are defaulting to
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 configured correctly,
> othe
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 the
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 bec
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 foll
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 Lin
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
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 missing something
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 modem-only. cdc_ncm is not.
The reason y
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 Baytrail hardware.
>>
>> (I
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 / 82
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 *symptom
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
> verified that
"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 https://github.c
Горбешко Богдан 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
driver's data.
Bjørn
tags 402447 patch
thanks
I believe the problem really is bad logic in pci_set_power_state(),
making it fail if the device doesn't support PM and a driver
1) saves power_state,
2) wakes up and does something, and
3) then reset to the saved state.
I've reported this upstream along with a patc
The feedback from the netdev list is that this should be fixed in the
PCI subsystem instead. Attached is a suggested patch against the
current stable kernel source (2.6.18.dfsg.1-12etch1).
Bjørn
--- linux-source-2.6.18/drivers/pci/pci.c.orig 2006-09-20 05:42:06.0 +0200
+++ linux-source
Filippo Giunchedi <[EMAIL PROTECTED]> writes:
> On Thu, May 10, 2007 at 09:48:55PM +0200, Bjjjrn Mork wrote:
>> The feedback from the netdev list is that this should be fixed in the
>> PCI subsystem instead. Attached is a suggested patch against the
>> current stable kernel source (2.6.18.dfsg.1-1
Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lm78 hwmon stopped working after upgrading from Sarge (kernel-image-2.6.8-3-686
version 2.6.8-16sarge6) to Etch (linux-image-2.6.18-3-686 version 2.6.18-7).
The system is an Asus P
Package: linux-image-2.6.24-1-686
Version: 2.6.24-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Card has been working for quite a while using madwifi and the same access
points. Usually at
maximum speed (54Mbits/s). With ath5k I could barely get it to associate, and
the rate
maximilian attems <[EMAIL PROTECTED]> writes:
> how is 2.6.25 in unstable doing? installs just fine in Testing.
Looks really good! I've barely tested it so far, but it does look
promising. Specifically: The two problems reported in this bug seem to
be gone. DHCP works. Auto speed negotiation
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 an issue on IRC where G
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
unrela
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
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 pl
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
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 o
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:
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:
>> > https://git.kernel.
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
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: xHCI
Leith Bade writes:
> Also, has a public version of the MT7981 Reference Manual been published?
> Google only finds me a pirated partial copy on Scribd. This will be needed
> to get all the memory locations for the DTS file, otherwise we will need to
> steal them from the DTS files in the Mediatek
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
>
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
sin
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
> workaro
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 rep
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
Ben Hutchings 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 ker
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 h
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 controller.
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.
>>
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.
"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.
AF
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.
>
> [...]
>
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 enabl
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 intel_iom
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
> usb_f
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
"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
> 0226009ce0f6089f9b31211f7a2
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
>> > e506addeff844237d60545ef4f6141de
Ritesh Raj Sarraf 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 inspired
Pavel Odintsov 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 integrate it to
Michael Biebl 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 kmod package sti
Ben Hutchings 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 with current use
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 mode
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 generate
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?
>>>
>
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 vers
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
Marco d'Itri 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: fw_
Petter Reinholdtsen 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 http://bugs.d
Steve Cotton 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 Device 010: ID
Ben Hutchings 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) get a recent k
Geert Stappers writes:
> Package: debian-kernel-handbook
> Version: 1.0.15
> Severity: wishlist
>
> Op 2013-11-17 om 12:28 schreef Bastian Blank:
>>
>> Also you want to use new_id interface[1] if possible.
>>
>> Bastian
>>
>> [1]: /sys/class/usb/drivers/*/new_id
>> http://www.ha19.no/us
Geert Stappers 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 du
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] RAX: 0
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 Trace:
> Apr 5 13:32:
Ben Hutchings writes:
> On Wed, 2016-04-06 at 16:51 +0200, Bjørn Mork wrote:
>> Antonis Christofides writes:
>>
>> >
>> > Apr 5 13:32:47 thames kernel: [86003.993994] BUG: unable to handle kernel
>> > paging request at eba40a800380
>> &g
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 been dropped
>>
>> It
Ben Hutchings writes:
> On Mon, 2016-04-11 at 09:55 +0200, Bjørn Mork wrote:
>> 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 mes
I am sorry, but I'm afraid my previous analysis in this bug report is
completely wrong.
The kernel image maintainer scripts are not supposed to run lilo
directly. They trigger an initramfs update, and that should in turn
cause lilo to run after it's finished. The initramfs update must do
this r
Just to add another data point, lilo failed to run again for me too on
the 2.6.26-19lenny1 upgrade. Even after working on the previous kernel
upgrade!
I'm now totally lost wrt what triggers this bug...
To summarize:
2.6.26-17lenny2 => 2.6.26-19
lilo OK
2.6.26-19 => 2.6.26-19lenny1
li
I just noticed this bug report, and couldn't let be commenting...
I believe "buried in ddp.c" is a little unprecise. ddp.c implements the
EtherTalk Link Access Protocol (ELAP). See the header of
net/appletalk/ddp.c:
* DDP:An implementation of the AppleTalk DDP protocol for
*
Patrik Schindler writes:
> Good point. But Token Ring Card drivers already exist, even if there
> is likely not a very much bigger demand. :-)
Well, they do exist but they are probably going away too. I don't see
anyone really interested in hacking on them, so they are staying just as
long as t
This is probably answered somewhere, but I just can't find it right now:
what are the actual requirements for including a firmware which is
distributed from kernel.org in the Debian package firmware-linux-nonfree?
The reason I ask is because I was a bit surprised to find that my
edgeport usb seria
Ben Hutchings writes:
> Instead of complaining about a decision which was taken by the project
> several years ago, perhaps you could talk to Edgeport about fixing the
> licence (bug #548745).
You're of course perfectly right. Sorry about the rant. I've opened a
support case with Digi Internat
clone 575207 -1
retitle -1
severity -1 wishlist
found -1 2.6.32-10
tags 575207 + patch
thanks
Fladischer Michael writes:
> [8.172997] DVB: registering new adapter (TT-Budget S2-1600 PCI)
> [8.209018] adapter has MAC addr = 00:d0:5c:cc:a7:29
> [8.328665] Intel ICH :00:1f.5: PCI I
39] IP: [] dvb_frontend_detach+0x4/0x67 [dvb_core]
Ref http://bugs.debian.org/575207
Signed-off-by: Bjørn Mork
Cc: sta...@kernel.org
Cc: 575...@bugs.debian.org
---
This patch should apply cleanly to 2.6.32, 2.6.33, 2.6.34-rc2 and with an
offset to git://linuxtv.org/v4l-dvb.git
Please apply to all o
Just a FYI for those noticing this bug report: There are excellent
instructions on how to build a linux-kbuild-2.6.33 package yourself on
http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage#Thestoryoflinux-kbuild-2.6
Something like the attached hack is necessary due to changes in
sc
Hello,
I am aware of the policy stated on
http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines
and that this in general means that new features/drivers are rejected.
I still would like to ask for an exception: The "mantis" DVB driver was
included in upstream version 2.6.33. This driver is
Ben Hutchings writes:
> On Sat, 2010-04-10 at 21:21 +0200, Bjørn Mork wrote:
>> Hello,
>>
>> I am aware of the policy stated on
>> http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines
>> and that this in general means that new features/drivers are
Matteo Cypriani writes:
> I'm currently adopting the fdutils package, and looking at the bug list, I
> found that it has a RC bug (#548434) that seems not related to him but to the
> kernel (this problem exist with several programs when trying to access floppy
> drives).
> It is forwarded to h
Hello,
you may want to note that adding stable 2.6.32.13 will close #575207 (or
so I hope :-). See
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;h=65f202ba
It would be nice if the accompanying wishlist bug #575223 (enabling
CONFIG_DVB_STV090x) was fixed as well so that thi
Ben Hutchings writes:
> We rely on the kernel build configuration mechanism to select the
> frontend and tuner modules associated with a controller driver (such as
> budget), rather than explicitly enabling them. Currently, enabling
> budget does not also enable stv090x. I have included a fix f
Ben Hutchings writes:
> On Sat, 2010-04-10 at 21:21 +0200, Bjørn Mork wrote:
>
>> Do you think an exception may be possible for this driver? If so, I can
>> prepare a patch proposal for review.
>
> Please do. Also, report this as a bug.
I understand that the kern
Ben Hutchings writes:
> On Wed, 2010-06-02 at 10:39 +0200, Bjørn Mork wrote:
>
>> I am still unsure about the preferred way to provide such a driver
>> patch. The first version attached to the bug was just a copy of the
>> upstream version with the necessary modification
controls
as "Digital Beep" and create analog beep controls for mentioned node.
Signed-off-by: Jaroslav Kysela
Signed-off-by: Bjørn Mork
---
sound/pci/hda/patch_analog.c | 19 ---
1 files changed, 16 insertions(+), 3 deletions(-)
diff --git a/sound/pci/hda/patch_ana
Mark Hymers writes:
> On Tue, 15, Jun, 2010 at 01:44:45AM +0100, Ben Hutchings spoke thus..
>
>> > @@ -610,7 +610,7 @@
>> >for (i = 0; i < serial->num_ports; i++) {
>> >port = serial->port[i];
>> >if (!port->interrupt_in_urb) {
>> > - dbg("%s: No interr
Jeff Carr writes:
> Is there a way to pull down newer versions of the kernels? I put sid
> on a new laptop, but the wireless is flaky. It's of course worth
> trying newer kernels with something like this. I'd try the stock deb
> packages if there was a apt repository for them.
It's in experiment
Steve Langasek writes:
>> Comments/Problems:
>> Trying to boot the Debian 5.0 netboot install image fails to detect CD
>> and/or network card (DE422). It boots up to the install screen just fine,
>> but without CD/network card support unable to install base system. (scsi
>> controller- aha1742 (e
1 - 100 of 187 matches
Mail list logo
