On Tue, Feb 18, 2025 at 03:11:08PM +0100, Salvatore Bonaccorso wrote:
> > Microsoft has observed that the 5.10.y kernels in bullseye are susceptible
> > to crashes due to race conditions in the NVME/PCI subsystem. See below for
> > a representative kernel log. The problem appears most frequently
Source: linux
Version: 5.10.223-1
Severity: important
Tags: upstream patch
X-Debbugs-Cc: debian-cl...@lists.debian.org, jaboutb...@microsoft.com
Microsoft has observed that the 5.10.y kernels in bullseye are susceptible
to crashes due to race conditions in the NVME/PCI subsystem. See below for
a
On Sun, Dec 22, 2024 at 04:30:06PM +0100, Chris Hofstaedtler wrote:
> > Hi kernel team. Per the earlier discussion in this bug, please raise
> > the priority of linux-sysctl-defaults to important in order to ensure
> > that it's present by default in typical Debian installations.
>
> > diff --git
ch is also an argument for it being harmless to include. 🤷)
Hi kernel team. Per the earlier discussion in this bug, please raise
the priority of linux-sysctl-defaults to important in order to ensure
that it's present by default in typical Debian installations.
Patch is attached.
Thanks
noah
Control: severity -1 important
Control: affects -1 iputils-ping
On Tue, Oct 15, 2024 at 07:04:51PM +0300, sergio wrote:
> please call `sysctl -p /usr/lib/sysctl.d/50-default.conf` after installation
+1 Not doing so is leading to confusing/broken behavior during
upgrades. By deferring the applic
On Mon, May 27, 2024 at 03:37:08PM +0200, Emanuele Rocca wrote:
> > So we have the problem that the Debian cloud kernel supports some, but
> > not all, of the devices our shared users need, and we’re not sure of
> > the right way to solve that. We wondered if we should switch the
> > images to the
On Fri, May 17, 2024 at 05:34:57PM +0200, Bastian Blank wrote:
> > > how do I change this?
> > You install the non-cloud kernel.
>
> The cloud kernel is limited in scope. And the decision was that not
> everything you can do on platforms is in scope.
To clarify the scope a bit, historically the
On Wed, Apr 03, 2024 at 06:26:46PM +0200, Paul Menzel wrote:
> Sorry, I have the feeling we talk past each other. I do not want to create
> an initrd. I want to boot *without* an initrd, and the only missing piece is
> building VIRTIO_BLK into the Linux kernel.
>
> Ubuntu also builds this into the
On Wed, Sep 07, 2022 at 07:37:45AM +0200, Alexander Wirt wrote:
> > > Now that buster is LTS and no longer officially supported, should the
> > > -backports pocket be closed? AFAIK, buster just receives the security
> > > uploads by the -security pocket and shouldn't have -backports open
> > > anym
On Sat, Mar 19, 2022 at 10:41:39AM +0100, Salvatore Bonaccorso wrote:
> > >From the upstream discussion on the linux-pci mailing list [*]:
> >
> > > Yes. My understanding is that the issue is because AWS is using older
> > > versions of Xen. They are in the process of updating their fleet to a
> >
>From the upstream discussion on the linux-pci mailing list [*]:
> Yes. My understanding is that the issue is because AWS is using older
> versions of Xen. They are in the process of updating their fleet to a
> newer version of Xen so the change introduced with Stefan's commit
> isn't an issue any
Control: reassign -1 src:linux
Control: forcemerge 1006346 -1
On Sat, Mar 12, 2022 at 01:21:23AM +, Reilly Brogan wrote:
> I bisected this issue and it was introduced in kernel 5.10.88 as commit
> e5949933f313c9e2c30ba05b977a047148b5e38c "PCI/MSI: Mask MSI-X vectors
> only on success", thus pr
Control: reassign -1 src:linux
Control: tags -1 + upstream
> Amazon EC2 instance types with Enhanced Networking use the ixgbevf.ko
> driver. The current AMIs successfully probe the ixgbevf driver and spawn
> dhclient as expected, but dhclient appears to never receive a lease. Older
> AMIs do wor
On Fri, Feb 26, 2021 at 06:58:50PM +0100, Vincent Blut wrote:
> > > I think the distinction is that the other packages that tweak sysctl
> > > values don't claim to be doing so on behalf of the kernel team. If
> > > the
> > > kernel team is responsible for the values being set, then the
> > > sett
On Tue, Apr 13, 2021 at 11:36:11AM +0200, Bastian Blank wrote:
> > > Where was that discussed?
> > It was discussed in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759
> > , with responses from both Ben and Noah.
>
> As this is incomplete at best, I intend to revert that change.
>
> O
On Wed, Mar 03, 2021 at 05:35:42PM +0100, Louis Bouchard wrote:
> Thank you for the quick update. I just want to mention that this makes the
> Debian Buster cloud image unusable for any VM with more than 64 cpus.
Is it the number of physical cores that matters, rather than the SMT
threads? Becaus
On Wed, Jan 27, 2021 at 12:57:07PM +, Wookey wrote:
> Current arm hardware such as graviton2 (AWS arm64 hardware) has
> 'Coherent Mesh Network' interconnect (between components in a
> soc). It's important that support for this is built in the kernel so
> it can be used.
>
> This requires CONFI
On Wed, Jan 20, 2021 at 11:39:16PM +0100, Vincent Blut wrote:
> > We could do that. However, in the past (earlier in this bug, even) it's
> > been pointed out that other packages should not be responsible for
> > setting kernel policies, so changes like this should be the
> > responsibility of the
Control: tags -1 + patch
A proposed patch is at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/309
On Wed, Jan 20, 2021 at 10:22:16PM +0100, Vincent Blut wrote:
> My proposal would differ from yours though in that it would not touch the
> kernel
> configuration but would instead consist in patching procps to provide a
> configuration file (let's say default_qdisc.conf) to set the value of the
>
On Sun, Jan 17, 2021 at 10:29:44PM -0300, Ivan Baldo wrote:
> Â Â Â I think we want the mq qdisc to distribute the load between cores, to
> support very high speed network cards or too slow CPUs.
Yep, you're right. Though it's not about CPU cores, but about tx queues
on the NIC hardware.
> Â Â Â Also
On Thu, Apr 23, 2020 at 03:34:06PM -0700, Matt Taggart wrote:
> #890343 was originally opened against systemd asking to install the upstream
> systemd sysctl.d/50-default.conf file that sets:
>
> net.core.default_qdisc = fq_codel
>
> As explained in #950701 (and the systemd debian changelog) the
> Thanks. Pending currently with the ongoing rebase in the v4.19.y
> series in
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/295 .
>
> Just we need to check if this warrants a regression update issued
> earlier via stable-updates.
If possible, I'd vote for an release via stable-up
Package: src:linux
Version: 4.19.160-2
Severity: important
Tags: upstream fixed-upstream
Control: fixed -1 5.9.15-1
Control: fixed -1 5.10~rc7-1~exp1
Control: found -1 5.9.11-1
Opening a bug for visibility. Arguably this could be Severity: grave given
that memory corruption can lead to data loss.
Package: src:linux
Version: 5.9.11-1
Severity: wishlist
Per discussion in the recent cloud-team meeting, there are several
additional modules that can be disabled in the cloud kernel. The
proposed candidates for removal is below; please feel free to critique
specific entries if you think there's
On Sun, Nov 22, 2020 at 03:53:32PM -0800, Flavio Veloso Soares wrote:
> Unfortunately, I couldn't find many comprehensive benchmarks of kernel
> CONFIG_PREEMPT* options. The one at
>
> [1]https://www.codeblueprint.co.uk/2019/12/23/linux-preemption-latency-throughput.html
> seems to be very tho
Control: tags -1 + patch
I've submitted a merge request containing a proposed fix at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/268
Tested in an arm64 KVM environment with steal time reporting; validated
its behavior against that of the sid kernel.
On Wed, Sep 02, 2020 at 06:09:46PM -0700, Jonathan Nieder wrote:
> > Subject: src:linux: none
>
> It looks like you forgot to include a subject line?
*sigh* Computers are hard.
> The relevant series is a4b28f5c6798 (Merge remote-tracking branch
> 'kvmarm/kvm-arm64/stolen-time' into kvmarm-master
Package: src:linux
Version: 4.19.132-1
Severity: important
Tags: buster
When used in virtual machine environments, Linux on amd64 is able to report
"steal time" to the guest. This functionality has been supported by Linux
on amd64 for years, but was only added to arm64 with Linux 5.5.
As Debian
On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote:
> > > Could you please enable CONFIG_F2FS_FS in the cloud kernel?
> > [...]
> >
> > What makes you think f2fs will be commonly used in cloud deployments?
> >
> I don't know that it will be, but as it supports encryption and compressi
Control: tags -1 + patch
MR available at https://salsa.debian.org/kernel-team/linux/-/merge_requests/263
Package: src:linux
Version: 4.19.132-1
Severity: important
Tags: buster
Buster fails to fully initialize the hardware on AWS arm64 bare-metal
instances (e.g. m6g.metal). The issue is fixed with the patch series from
https://lore.kernel.org/linux-arm-kernel/20190615002359.29577-2-b...@kernel.crash
On Thu, Apr 23, 2020 at 03:34:06PM -0700, Matt Taggart wrote:
> fq_codel is better in every way than pfifo_fast and I am unaware of any
> reason why it would not be a better default. (but don't trust me, ask the
> kernel networking experts)
Isn't CAKE supposed to be even better than fq_codel, incl
On Tue, Apr 14, 2020 at 02:06:30PM +0100, Simon John wrote:
> Package: src:linux
> Version: 5.5.13-2
>
> Booting into 5.5 on Sid gives me no audio out via HDMI.
>
HDMI audio seems fixed for me with 5.5.17, recently uploaded to
unstable. Is it better for you?
On Tue, Apr 14, 2020 at 02:06:30PM +0100, Simon John wrote:
> Booting into 5.5 on Sid gives me no audio out via HDMI.
I can confirm similar HDMI audio breakage with 5.5.13 on a Thinkpad X1
Carbon (gen2) with the following audio devices:
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio
Control: tags -1 + patch
Proposed fix for buster at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/229
Control: severity -1 important
Raising this to Important. The lack of a KSM is a regression from the
generic kernel that is impacting the usefulness of this kernel build in
the environment in which it's intended to be used. This should get
fixed in buster.
On Sat, Apr 04, 2020 at 10:17:20AM +0200, Thomas Goirand wrote:
> > The first two bugs are about nested virtualization. I like the idea of
> > deciding to support that or not. I don't know much about nested virt,
> > so I don't have a strong opinion. It seems pretty widely supported on
> > our p
On Wed, Apr 01, 2020 at 03:15:37PM -0400, Noah Meyerhans wrote:
> There are open bugs against the cloud kernel requesting that
> configuration options be turned on there. [1][2][3]
> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952108
> 2. https://bugs.debian.org/cgi-bin/b
On Thu, Apr 02, 2020 at 10:55:16AM -0700, Ross Vandegrift wrote:
> I don't think just saying "yes" automatically is the best approach. But
> I'm not sure we can come up with a clear set of rules. Evaluating the
> use cases will involve judgment calls about size vs functionality. I
> guess I thin
For buster, we generate a cloud kernel for amd64. For sid/bullseye,
we'll also support a cloud kernel for arm64. At the moment, the cloud
kernel is the only used in the images we generate for Microsoft Azure
and Amazon EC2. It's used in the GCE images we generate as well, but
I'm not sure anybod
On Mon, Mar 30, 2020 at 10:33:24AM +0200, Vincent Bernat wrote:
> >> Please consider adding kernel module '9p' to the cloud image. It is
> >> impossible to passthrough filesystem from hypervisor with the current cloud
> >> image and there are no additional packages to install it. The only way that
Package: src:linux
Version: 4.19.98-1
Severity: wishlist
Owner: no...@debian.org
Relaying a request on behalf of an Amazon EC2 customer. The generic
kernel enables CONFIG_KSM, but the cloud kernel disables this. The
customer makes extensive use of KSM features in EC2 and would like to
request th
On Fri, Mar 06, 2020 at 09:44:26AM +0100, João Mikos wrote:
> Reflecting about what you said the default kernel might indeed not be
> the best place to enable this, but maybe the cloud kernel could be a
> good candidate instead. Official support for Firecracker might be a
> stretch, especially due
On Thu, Mar 05, 2020 at 10:31:37PM +0100, João Mikos wrote:
> I am experimenting with running a Debian Buster microVM under the
> Firecracker hypervisor, using a stock Debian kernel (converted to
> vmlinux format) and an initrd.img file. When booting the microVM with
> this setup, I receive the fol
On Sun, Feb 23, 2020 at 12:28:53AM -0800, Josh Triplett wrote:
> The normal Debian kernel configuration has CONFIG_VHOST_SCSI enabled,
> but the cloud configuration does not seem to have it enabled. Please
> enable CONFIG_VHOST_SCSI=m on the cloud configuration as well.
Out of curiosity, where is
On Tue, Feb 04, 2020 at 03:48:32PM -0800, Josh Triplett wrote:
> I would suggest testing on a c5.large. t2 and t3 have shared CPUs, so
> they have less consistent boot time. c5.large is about the same cost as
> t3.large, but will have far more consistent performance.
Performance definitely seems t
Before optimizations:
$ systemd-analyze
Startup finished in 7.828s (kernel) + 22.332s (userspace) = 30.161s
graphical.target reached after 20.312s in userspace
With optimizations:
$ systemd-analyze
Startup finished in 1.968s (kernel) + 6.536s (userspace) = 8.504s
graphical.target reached after
On Mon, Jan 20, 2020 at 04:38:55PM -0800, Josh Triplett wrote:
> Following up on this, here's a simplified list of optimizations for the
> cloud variant in one place, taking into account the previous reply.
> Would it help to get this in the form of a patch or MR on
> https://salsa.debian.org/kerne
Control: tags -1 + patch
Proposed solution submitted as
https://salsa.debian.org/kernel-team/linux/merge_requests/202
On Thu, Jan 09, 2020 at 02:00:01PM -0500, Noah Meyerhans wrote:
> The 5.4 kernel currently in sid does not experience this lack of
> entropy. It has been suggested that upstream commit 50ee7529ec45
> ("random: try to actively add entropy rather than passively wait for
> it")
On Thu, Jul 11, 2019 at 09:42:17AM -0400, Michael J. Redd wrote:
> > The release notes for buster do mention this issue and provide a
> > link to:
> >
> > https://wiki.debian.org/BoottimeEntropyStarvation
> >
> > which has your Haveged solution as one of its suggestions.
> >
>
> D'oh! Serve
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: important
See the thread at
https://lists.debian.org/debian-cloud/2020/01/threads.html#00013 for
some context.
When launching arm64 VMs on Amazon EC2, a lack of entropy at boot
results in the full boot process taking several minutes, when t
On Tue, Nov 26, 2019 at 10:07:45AM +0100, Andreas Heinlein wrote:
>
> I noticed that linux-image-amd64 is currently missing in buster-backports
> since a few days. I guess this is because the signed kernel images are not
> available yet. Still, linux-headers-amd64 exists in buster backports and
Proposed fixes for unstable and stable (respectively) are at:
https://salsa.debian.org/kernel-team/linux/merge_requests/179
https://salsa.debian.org/kernel-team/linux/merge_requests/178
Proposed implementation in
https://salsa.debian.org/kernel-team/linux/merge_requests/172
Package: src:linux
Version: 4.19.67-2
ENA is an ethernet adaptor used on Amazon EC2 cloud instances. Upstream
has recently merged a number of bug fixes and enhancements, and it would
be nice to have these available in stable.
Specific upstream changesets that I'm interested in are:
https://lore
On Fri, Sep 27, 2019 at 01:15:29PM -0700, Flavio Veloso wrote:
> Since linux-image-cloud-* packages are created for cloud environments --
> read: servers which do not need desktop-level responsiveness --, wouldn't it
> be beneficial to build the kernels with CONFIG_HZ set to 100?
For what it's wor
On Fri, Jan 04, 2019 at 06:57:21AM +0100, Salvatore Bonaccorso wrote:
> > LD vmlinux.o
> > MODPOST vmlinux.o
> > GEN .version
> > CHK include/generated/compile.h
> > UPD include/generated/compile.h
> > CC init/version.o
> > LD init/built-in.o
> > ./drivers/f
Control: tags -1 + patch
Merge request for Linux 4.9 (stretch):
https://salsa.debian.org/kernel-team/linux/merge_requests/81
Control: tags -1 + patch
Merge request: https://salsa.debian.org/kernel-team/linux/merge_requests/80
Package: src:linux
Version: 4.9.130-2
Severity: wishlist
Tags: stretch
Amazon recently announced arm64-based EC2 instances. These instances rely on
PCI_HOTPLUG functionality to support attach/detach of resources such as
ethernet interfaces and block devices. PCI_HOTPLUG is enabled for arm64 in
bus
Package: src:linux
Severity: important
ENA is an ethernet adaptor used on Amazon EC2 cloud instances. Version 2.0.2 of
the ENA driver was added to the mainline kernel as of version 4.20. This
version includes fixes for various bugs, some of which result in kernel panics,
and is needed in order to
On Tue, Nov 27, 2018 at 09:50:17AM -0800, Jakub Kicinski wrote:
> > > Please see https://salsa.debian.org/kernel-team/linux/merge_requests/72
> >
> > Ugh. We cannot currently package bpftool in Debian. There are several
> > GPLv2-only files in its source tree, and it links unconditionally
> > agai
On Mon, Nov 19, 2018 at 11:34:26PM -0800, Noah Meyerhans wrote:
> Please see https://salsa.debian.org/kernel-team/linux/merge_requests/72
Ugh. We cannot currently package bpftool in Debian. There are several
GPLv2-only files in its source tree, and it links unconditionally
against the GP
On Fri, Apr 20, 2018 at 02:07:40PM +0200, Simon Horman wrote:
> I would like to request packaging of bpftool which has been
> included in upstream Linux tree since v4.15-rc1. I expect this can
> be done in a similar manner to the way that perf, also present in
> the upstream Linux kernel tree, is p
On Fri, Apr 20, 2018 at 02:07:40PM +0200, Simon Horman wrote:
> I would like to request packaging of bpftool which has been
> included in upstream Linux tree since v4.15-rc1. I expect this can
> be done in a similar manner to the way that perf, also present in
> the upstream Linux kernel tree, is p
Submitted the patch in more complete form at
https://salsa.debian.org/kernel-team/linux/merge_requests/68
Package: linux-image-4.18.0-1-cloud-amd64
Version: 4.18.8-1
Severity: wishlist
Tags: patch
Control: affects -1 cloud.debian.org
The cloud variant of the kernel packages does not currently enable
CONFIG_ENA_ETHERNET, meaning it is not able to drive the network hardware
on modern AWS instances.
A p
On Fri, Dec 15, 2017 at 08:03:51PM +0100, Bastian Blank wrote:
> > > We at credativ are responsible for maintaining the Azure cloud images.
> > > We got asked by Microsoft to explore the possibilities of introducing a
> > > specialised Linux image for this plattform into Debian. The main
> > > enh
On Sun, Aug 27, 2017 at 04:16:50PM +0200, Thomas Goirand wrote:
> Basically, the only thing that I want to see is a specific config for
> that kernel, nothing else. Otherwise, it's going to be too much
> maintenance work. Indeed, it should *not* be a different source upload,
> that's too much work
On Mon, Aug 28, 2017 at 01:31:31AM +0100, Ben Hutchings wrote:
> > OTOH, the list of required modules may be small enough for us to
> > enumerate the ones we need for booting in /etc/initramfs-tools/modules.
>
> ...and then you could use MODULES=list. initramfs-tools will still
> follow module st
On Sat, Aug 26, 2017 at 05:18:45PM +0100, Ben Hutchings wrote:
> > Thomas, can you elaborate why you think this a good idea? Is this about
> > boot time of the kernel image? The thing I really do not want to have is
> > additional kernel source uploads to the archive for just those cloud
> > kernel
On Tue, Dec 29, 2015 at 11:39:46AM -0800, Noah Meyerhans wrote:
> > Dec 28 13:20:42 amarth racoon: ERROR: recvmsg (Resource temporarily
> > unavailable)
> > Dec 28 13:20:42 amarth racoon: ERROR: failed to receive isakmp packet at
> > isakmp.c:238: Resource temporarily u
On Mon, Dec 28, 2015 at 03:22:52PM -0800, Noah Meyerhans wrote:
> Following the recent kernel security update, racoon(8) from ipsec-tools
> can no longer negotiate an IPSec security association with an ipv6 peer.
> IPv4 does not appear affected.
>
> Racoon logs the following:
&g
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u1
Severity: normal
Following the recent kernel security update, racoon(8) from ipsec-tools
can no longer negotiate an IPSec security association with an ipv6 peer.
IPv4 does not appear affected.
Racoon logs the following:
Dec 28 13:20:42 amarth raco
On Thu, May 12, 2011 at 04:43:22PM -0700, Stephen Hemminger wrote:
> > > There were two more follow on commits in stable related to this.
> > > I recommend merging 2.6.38.6 which includes these.
> >
> > The problem still exists in the current 2.6.38.6. Backing out 5f1c356a
> > still solves the pr
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
> There were two more follow on commits in stable related to this.
> I recommend merging 2.6.38.6 which includes these.
The problem still exists in the current 2.6.38.6. Backing out 5f1c356a
still solves the problem there.
I have
On Tue, May 10, 2011 at 01:42:49PM +0100, Ben Hutchings wrote:
> > > This is pretty weird. Debian version 2.6.38-3 has a few bridging
> > > changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
> > > would cause this.
> >
> > I have apparently filed the bug against the wrong ve
On Tue, May 10, 2011 at 03:38:44AM +0100, Ben Hutchings wrote:
> This is pretty weird. Debian version 2.6.38-3 has a few bridging
> changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
> would cause this.
I have apparently filed the bug against the wrong version of Debian's
ke
Package: linux-2.6
Version: 2.6.38-3
Severity: normal
Hi. I've got a system that hosts several kvm virtual hosts. The VMs
access the network via tap devices bridged with a physical interface.
After upgrading to linux-image-2.6.38-2-amd64_2.6.38-4, I noticed that
the virtualhosts were not autoconf
On Sun, Nov 29, 2009 at 02:15:41PM -0600, Manoj Srivastava wrote:
> Perhaps you should consider making the script just create a
> ./fstab.new file, and not overwriting /etc/fstab? makes it easier to
> test the script out without altering current setup.
Keeping a copy of the original fil
On Mon, Oct 26, 2009 at 09:04:04PM +, Steve Gane wrote:
> I'm trying to use the linux-headers-2.6.29-bpo.2-686 package from
> Lenny/backports, but aptitude says it depends on linux-kbuild-2.6.29,
> which is not available in Lenny, or Lenny backports, or Squeeze.
(This question should have
On Fri, Oct 23, 2009 at 05:08:15PM +0200, maximilian attems wrote:
> you still didn't read or get my question:
> Who will maintain the chosen pvops patch for the Squeeze lifetime?
>
> yes, this is the part of the work:
> * backward port important fixes, securtiy patches
> * read bug reports, decip
On Fri, Oct 23, 2009 at 04:43:31PM +0200, maximilian attems wrote:
> > If this is the case, and if we assume that pv-ops xen support is
> > eventually included upstream (which certainly appears to be the goal),
> > why the deprecation notice?
>
> who stepped to properly maintain the patch in the c
On Fri, Oct 23, 2009 at 11:06:55AM +0200, Bastian Blank wrote:
> > > > xen dom 0
> > > > +
> > Are you basing your patch on the PV-ops tree or on one of the SuSE
> > forward ports? Based on your recent posts to xen-devel I had assumed the
> > former but Ben's initial post suggested perhaps
On Thu, Aug 20, 2009 at 10:47:56PM +0200, advocatux wrote:
> Yep, I know I can add "ipv6.disable=1" in /boot/grub/menu.lst but this
> method doesn't work always, it depends on which 2.6.30 kernel version
> you're running.
So this bug was closed when 2.6.30 was uploaded to unstable, no? We're
not
Package: linux-image-2.6.30-1-686
Version: 2.6.30-1
Severity: normal
While trying to debug X issues similar to #524340, I ran "modprobe -r
915", which resulted in the following kernel oops:
[ 2417.824670] [drm] Module unloaded
[ 2417.872150] BUG: unable to handle kernel NULL pointer dereference a
On Wed, May 13, 2009 at 12:35:47PM +0200, Francis Debord wrote:
> I got a AMD Geode NX 1700, also know as AMD-AthlonXP-Mobile with
> Multiprocessorsupport (an unlocked Athlon / thouroughbred II) on PCCHips
> M848A Motherboard.
>
> When an other sad i686-kernel is working fine and will say i am l
On Thu, Apr 16, 2009 at 04:21:10PM -0400, Michael S. Gilbert wrote:
>
> i think that any flaw that allows an attacker to elevate his pwnage from
> root to hidden should always be considered a grave security issue.
Your argument sounds like the one used by RIAA, MPAA etc, based on the
DMCA's anti-
On Thu, Apr 16, 2009 at 11:55:05AM -0400, Michael S. Gilbert wrote:
> as seen in recent articles and discussions, the linux kernel is
> currently vulnerable to rootkit attacks via the /dev/mem device. one
> article [1] mentions that there is an existing patch for the problem,
> but does not link t
On Wed, Feb 25, 2009 at 11:27:56PM +, Orlando Agostinho wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-13
> Followup-For: Bug #505174
Why is the is a followup for 505174? It doesn't seem at all related.
>
> I have vmware workstation 6.5 running in WIN XP. After, installed
> d
On Tue, Jan 13, 2009 at 02:03:10PM +0100, Oliver Bock wrote:
> I'd like to know the current status of this bug as the root cause got
> fixed upstream apparently. Is the fixed microcode already scheduled for
> integration into "firmware-iwlwifi" already?
The bug still occurs in linux-image-2.6.26
On Tue, Jan 13, 2009 at 04:24:03PM -0600, Michael Ekstrand wrote:
> > I have tried to get a netconsole running, but so far have had no
> > success. If I can get a crash with debug=1 this afternoon, I'll post
> > any additional info it yields; otherwise, I'll try either the updated
> > firmware or
On Mon, Jan 12, 2009 at 12:01:11PM -0600, Michael Ekstrand wrote:
> For some time now, I have been experiencing kernel panics (system
> frozen, caps lock LED blinking) when using my Intel 4965AGN wireless
> card (in a Thinkpad R61). I have only noticed the problems when
> connected to my school's
On Sat, Nov 29, 2008 at 01:57:12AM +0100, Moritz Muehlenhoff wrote:
> > I can also confirm (2) that given the provided firmware by Zhu Yi the
> > issue is fixed on the same 2.6.27.7 kernel I built and talked about
> > before (1) for Lenny, using the iwl4965 driver.
> >
> > 1: http://bugs.debian.or
tags 502326 + upstream
thanks
This is bug
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703
signature.asc
Description: Digital signature
I've now confirmed that this crash will happen with 2.6.27.3 as well. :(
I'll see about pursuing this with upstream.
signature.asc
Description: Digital signature
Instability has gotten bad enough that I'm trying a homegrown 2.6.27.3
image. Uptime is approaching 20 hours, all with wireless active, and no
sign of trouble, but it's way too soon to tell if it really made a
difference...
noah
signature.asc
Description: Digital signature
And of course, the bug report should have mentioned iwl4965, not 3945.
Retitled accordingly.
noah
signature.asc
Description: Digital signature
1 - 100 of 101 matches
Mail list logo
