Bug#1027997: linux-image-6.0.0-6-amd64: netfilter (nft) tproxy broken on 6.0.0 kernel

Package: src:linux Version: 6.0.12-1 Severity: normal Dear Maintainer, tproxy support is working when booted to 5.10.0-20 kernel but not when booted to 6.0.0-6 kernel. Here are commands to reproduce: sudo nft add table ip kbohoneypot sudo nft add chain ip kbohoneypot alltraffic '{type filter ho

Bug#1011168: linux-image-5.17.0-2-amd64: rebooting KVM guest crashes kernel

I did 5 reboots of the guest followed by 5 complete shutdown/startup cycles of the guest. No kernel panics occurred. Based on how frequent the crashes were before, I would say thats a succesful test. -- Jon Doge Wrangler X(7): A program for managing terminal windows. See also screen(1) and tmux

Bug#1012100: linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and a kernel thread goes wild on Intel Xeon X3430

That dmesg output sounds a lot like bugs 1010916 and 1011168 and a Xeon X3430 CPU would be another older one that predates XSAVE. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011168#15 -- Jon Doge Wrangler X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Bug#1011168: linux-image-5.17.0-2-amd64: rebooting KVM guest crashes kernel

E5645 CPU that lacks XSAVE. And now that bug 1010916 has an updated backtrace attached its clear that it is the same issue as this one. -- Jon Doge Wrangler X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Bug#1011168: linux-image-5.17.0-2-amd64: rebooting KVM guest crashes kernel

0dif_generic ata_generic uhci_hcd ehci_pci megaraid_sas igb ata_piix ehci_hcd libata i2c_algo_bit dca crct10dif_pclmul crct10dif_common scsi_mod ptp i2c_i801 crc32_pclmul usbcore crc32c_intel i2c_smbus lpc_ich scsi_common usb_common pps_core [ 2257.706780] CR2: 0000000b -- Jon Doge Wran

Bug#1011168: linux-image-5.17.0-2-amd64: rebooting KVM guest crashes kernel

Package: src:linux Version: 5.17.6-1+b1 Severity: normal Dear Maintainer, I have a Debian Sid box running some KVM/QEMU guests and ever since the upgrade to 5.17 it is kernel panicing fairly reliably whenever I reboot the guest VMs on it. This is happening under both 5.17.3 and 5.17.6. [420450.

Bug#914491: linux-image-4.18.0-3-amd64: Please revert the STIBP patch from 4.18.20

Package: linux-image-4.18.0-3-amd64 Version: 4.18.20-1 Severity: normal Dear Maintainer, The recently uploaded 4.18.20 kernel package has the STIBP patch in it that has been reverted from the 4.9.140, 4.14.83, and 4.19.4 kernels upstream. There will never been an official revert for 4.18 because

Bug#849330: firmware-iwlwifi: intel 8260 does not work when using modfile /lib/firmware/iwlwifi-8000C-22.ucode and kernel 4.8

I just upgraded to the backported package... the same file was installed (iwlwifi-8000C-22.ucode), and after rebooting I do not have any problems anymore. Cheers, Jon On Thu, Jul 26, 2018 at 1:27 PM Ben Hutchings wrote: > Control: tag -1 moreinfo > > This firmware file was updated i

Bug#889487: linux-image-4.14.0-2-amd64: please enable CONFIG_X86_MCELOG_LEGACY

On Sun, Feb 04, 2018 at 01:03:59 +0100, Ben Hutchings wrote: > Control: severity -1 wishlist > Control: tag -1 wontfix > > On Sat, 2018-02-03 at 14:32 -0500, Jon wrote: > > Package: src:linux > > Version: 4.14.7-1 > > Severity: normal > > > > Please en

Bug#889487: linux-image-4.14.0-2-amd64: please enable CONFIG_X86_MCELOG_LEGACY

Package: src:linux Version: 4.14.7-1 Severity: normal Please enable CONFIG_X86_MCELOG_LEGACY so that /dev/mcelog exists again. It seems this functionality was seperated from CONFIG_X86_MCE in 4.12 and is not enabled by default. I don't see it explicitly set one way or another in the debian kernel

Bug#871646: linux-image-4.9.0-3-amd64: mmc0 / sdhci errors after inserting SDHC card with O2 Micro Device 8620 controller

Package: src:linux Version: 4.9.30-2+deb9u3 Severity: important Dear Maintainer, I am unable to insert an SD card and have it recognized by the kernel after upgrading from Debian 8. Prior to the upgrade, the SD card was recognized and worked flawlessly. * What led up to the situation? Insert

Bug#865311:

C programs which start a jvm using jni also segfault. This smells like fundamentally the same issue. I added a "me too" to debian bug 865746 (collectd), with links to info about the issue at Ubuntu - including a test program to reproduce. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865

Bug#849330: firmware-iwlwifi: intel 8260 does not work when using modfile /lib/firmware/iwlwifi-8000C-22.ucode and kernel 4.8

Package: firmware-iwlwifi Version: 20161130-2 Severity: important Hello Maintainer, Using a laptop with an intel 8260 wifi chip (HP Zbook 15 G3) and linux kernel 4.8, wifi does not work. This is a known problem; see https://bugs.archlinux.org/task/51271 It looks like the answer is that the debi

Bug#816067: linux-image-4.4.0-1-amd64: please enable CONFIG_RANDOMIZE_BASE

Package: src:linux Version: 4.4.2-3 Severity: wishlist Dear Maintainer, I'm aware that its not particularly strong and that the kernel leaks information like a colander, but now that its not compile time exclusive with CONFIG_HIBERNATION, can CONFIG_RANDOMIZE_BASE be turned on in the Debian kerne

Bug#783259: linux-image-3.16.0-4-amd64: Indicating ABI changes from upstream

aps do the same? Without the ability to do conditionals comparing numeric values both in Makefiles and within C, I am not sure how tell the two different kernels apart, and therefore am rather stuck. -- Jon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of &q

Bug#754852: nfs-utils: contains amd64 binaries (.o, .a, etc.)

Source: nfs-utils Version: 1:1.2.8-6 Severity: normal Hi folks, > $ pwd > /home/jon/tmp/nfs-utils-1.2.8 > $ find . -name '*.o' -o -name '*.a' | wc -l > 113 This is inherited from upstream's tarball and doesn't appear to be replicated in your git repos

Bug#740148: linux-image-3.12-1-amd64: kernel panic when entering sleep mode

On 02/27/2014 12:30 AM, Ben Hutchings wrote: Control: tag -1 moreinfo On Wed, 2014-02-26 at 12:00 +0100, Jon Jahren wrote: Package: src:linux Version: 3.12.9-1 Severity: important Hello! When entering sleep mode on this computer it will generate a kernel panic. This happens regardless of

Bug#740148: Further testing

I just tested the latest kernel from kernel.org (3.14-rc4) and the problem persists there as well with the same config from debians 3.12 kernel. I then tried removing the brcmsmac module before entering sleep mode and when I do that the computer wakes up as expected. So it seems there's an issu

Bug#740148: linux-image-3.12-1-amd64: kernel panic when entering sleep mode

Package: src:linux Version: 3.12.9-1 Severity: important Hello! When entering sleep mode on this computer it will generate a kernel panic. This happens regardless of whether I use the menu or close the lid on the unit. Attached is a log of the panic and I was asked to include these lines when sub

Linux 3.10.y packages for wheezy

is interested in the individual changes I made, but most of it is just boring backport work. I have attached the only two patches, one for "linux" and one for "linux-tools", I think might be of interest to the debian kernel team. Best regards Jon Severinsson [1] deb http://apt

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

I noticed in the last reply to this bug that the MegaRAID Storage Manager is suspect. I'm running Ubuntu with a 3.5.0-32 kernel and see this same behavior when using the MegaCli64 command line tool. I run this tool through cron each hour to grab the logs from the RAID controller and put them into s

Bug#687136: ; graphics corruption with Radeon 6570

/libdrm --branch debian-experimental cd libdrm debuild -b -i\.git Alternatively you could check out the "debian-unstable" branch instead and cherry pick just the above mentioned commit. In either case, install the relevant *.deb packages using "sudo dpkg -i ...". Make sure to

Bug#685782: linux-image-3.2.0-3-686-pae: Upgrading from 3.2.0-2 to 3.2.0-3 no longer boots using 3ware 9500S RAID card.

Package: src:linux Version: 3.2.23-1 Severity: important Hi, when upgrading from 3.2.0-2 to 3.2.0-3, my system no longer boots. I have a 3ware 9500S (Raid 5) card that is the primary boot disk. I also have a LSI MegaRaid (Raid 6) card that is a data disk, but the module loads early on 3.2.0-2 (i

Bug#596741: regression: CPU fan fast after resume: won't climb back down (patch from upstream)

On Thu, Apr 26, 2012 at 02:59:29PM -0500, Jonathan Nieder wrote: > Even easier is testing using the upstream source. It works like this: Thanks again for the detailed instructions. They really are a help. I was not aware this was possible for the debian flavours. Good stuff. > 2. Fetch point r

Bug#596741: patch from upstream

Hi Ben, On Sun, Apr 08, 2012 at 11:13:54PM +0100, Ben Hutchings wrote: > On Tue, 2012-04-03 at 09:17 +0100, Jon Dowland wrote: > > I tested a patch upstream and it solved the problem to me. I mailed it to > > the bug > > (but chose to use -quiet which I perhaps shouldn'

Bug#596741: patch from upstream

I tested a patch upstream and it solved the problem to me. I mailed it to the bug (but chose to use -quiet which I perhaps shouldn't have.) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive:

Bug#664855: linux-image-3.2.0-2-686-pae: Uhhuh. NMI received for unknown reason 31 on CPU 3. nmi_watchdog=0 fixes it

Package: linux-2.6 Version: 3.2.9-1 Severity: normal After upgrading to 3.2.0-2-688-pae (from 3.2.0-1-686-pae), I started getting tons of log messages: Mar 21 05:02:13 clementine kernel: [ 557.195949] Uhhuh. NMI received for unknown reason 31 on CPU 3. Mar 21 05:02:13 clementine kernel: [ 557

Bug#596741: Processed: Re: Processed: bug 596741 is not forwarded, tagging 596741, reassign 596741 to gnome-power-manager

On Fri, Jul 29, 2011 at 05:33:38PM +0200, Moritz Mühlenhoff wrote: > Does this still occur with more recent kernels? Sorry for the delay. Yes, it does, I'm running a 3.2-something kernel now, issue remains. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "

Bug#620059: nfs-kernel-server: This happens to me following uprade in the last week. What can I wind back to get round it?

Package: nfs-kernel-server Version: 1:1.2.3-1 Followup-For: Bug #620059 The fault shows up during boot. It appears to be mountd that fails. The modified script is because I added -d all to the rpc.mount options in an attempt to find out what was going wrong. It didn't help. rpcinfo -p shows this,

Bug#596741: Processed: Re: Processed: bug 596741 is not forwarded, tagging 596741, reassign 596741 to gnome-power-manager

m gone? Sorry for the delay, yep that is all that is needed to reproduce the problem, reassigning accordingly. -- Jon Dowland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive:

Bug#606853: Realtek RTL8111/8168B fails to load firmware patch

On Mon, 13 Dec 2010 12:20 +, "Ben Hutchings" wrote: > On Mon, 2010-12-13 at 10:05 +0100, Jon Black wrote: > > On Mon, 13 Dec 2010 02:11 +, "Ben Hutchings" > > wrote: > > > On Sun, 2010-12-12 at 13:51 +0100, Jon Black wrote: > > > [

Bug#606853: Realtek RTL8111/8168B fails to load firmware patch

On Mon, 13 Dec 2010 02:11 +, "Ben Hutchings" wrote: > On Sun, 2010-12-12 at 13:51 +0100, Jon Black wrote: > [...] > > The following output is from dmesg after running 'modprobe -r r8169; > > modprobe r8169': > > > > udev[76]: starting versio

Bug#606853: Realtek RTL8111/8168B fails to load firmware patch

Package: firmware-linux-nonfree Version: 0.27 I'm running a server which uses the Intel D510MO Fanless Dual Core Atom Mini-ITX Board. I initially installed Lenny and everything worked well, but decided to do a fresh install of Squeeze beta which is using kernel 2.6.32-5-686. During the installation

Bug#604416: linux-image-2.6.32-5-sparc64: Kernels >2.6.32 hang on boot at "Initializing cgroup subsys blkio

Package: linux-2.6 Version: 2.6.32-27 Severity: critical Tags: d-i upstream Justification: breaks the whole system Symptoms similar to https://partner-bugzilla.redhat.com/show_bug.cgi?format=multiple&id=603776 -- Package-specific info: ** Kernel log: boot messages should be attached ** Model inf

Bug#600939: I am not clear on why this is marked won't fix.

Ok, thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1010221420300.21...@orange.limedaley.com

Bug#600939: I am not clear on why this is marked won't fix.

I am not clear on why this is marked won't fix - is the upgrade path that I found that proper way to do it? e.g. Whenever the dkms build doesn't work due to kernel changes, uninstall virtualbox-ose-dkms, and then reinstall it, so it picks up the new changes? -- Jon

Bug#599768: closed by dann frazier (Bug#599768: fixed in linux-2.6 2.6.32-25)

reopen 599768 found 599768 2.6.32-25 thanks Wow -amazing response folks, I am truly impressed! Alas, -25 (i686 bigmem) doesn't cure this for me. I will try investigating in single user mode. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe".

Bug#599768: linux-image-2.6.32-5-686: backlight control fails after resume from suspend (toshiba r700-155)

Package: linux-2.6 Version: 2.6.32-23 Severity: normal As per subject. Toshiba Portege R700-155. Known issue, reported also There's a pm script on that thread which supposedly fixes this. It does not for me, but toshset is required, and itself

Bug#597576: linux-image-2.6.32-5-amd64: 2.6.32-23 still vulnerable to CVE-2010-3301

Package: linux-2.6 Version: 2.6.32-23 Justification: root security hole Severity: critical Tags: security The changelog says the CVE-2010-3301 was fixed in this update: * x86-64, compat (CVE-2010-3301): - Retruncate rax after ia32 syscall entry tracing - Test %rax for the syscall numbe

Bug#596741: regression: CPU fan fast after resume: won't climb back down

forwarded 596741 https://bugzilla.kernel.org/show_bug.cgi?id=18552 tags 596741 +upstream thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100915093145.ga26..

Bug#596741: regression: CPU fan fast after resume: won't climb back down

On Mon, Sep 13, 2010 at 08:22:22PM +0100, Jon Dowland wrote: > With 2.6.32-5-686, they never slow back down. My previous > kernel was vmlinuz-2.6.30-2-686, with which this did not > happen (same / with same package versions). Problem exists in pristine upstream 2.6.35.4 -- Jo

Bug#595964: Please cherry-pick patch to mount cgroupfs at /sys/fs/cgroup

* Michael Biebl wrote: > CCing Jon, as maintainer of libcgroup he might be interested in this > discussion. > > Am 07.09.2010 23:12, schrieb Bastian Blank: > > On Tue, Sep 07, 2010 at 10:54:04PM +0200, Michael Biebl wrote: > >> On 07.09.2010 22:41, Bastian Blank wrot

Bug#596741: regression: CPU fan fast after resume: won't climb back down

On Tue, Sep 14, 2010 at 07:43:17AM +0100, Jon Dowland wrote: > Yes - reproduced with 2.6.35-1~experimental.3 Bug not present in 2.6.31-2 (linux-image-2.6.31-1-686) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Co

Bug#596741: regression: CPU fan fast after resume: won't climb back down

On Tue, Sep 14, 2010 at 01:42:36AM +0100, Ben Hutchings wrote: > On Mon, 2010-09-13 at 20:22 +0100, Jon Dowland wrote: > > Package: linux-2.6 > > Version: 2.6.32-21 > > Severity: normal > > > > Hello, > > > > I suspend using gnome-power-manager

Bug#596741: regression: CPU fan fast after resume: won't climb back down

22:23 < bwh> Jon: Can you send a listing of /sys/class/thermal/ under the two kernel versions? j...@tchicaya:~/Desktop$ cat thermal-2.6.30-2-686 total 0 lrwxrwxrwx 1 root root 0 Sep 13 22:43 cooling_device0 -> ../../devices/virtual/thermal/cooling_device0 lrwxrwxrwx 1 ro

Bug#596741: regression: CPU fan fast after resume: won't climb back down

Package: linux-2.6 Version: 2.6.32-21 Severity: normal Hello, I suspend using gnome-power-manager or pm-suspend from pm-utils (same result). Traditionally on resume, my computer's fans run at what I assume is full speed (certainly faster/noiser than usual) for a brief period until userspace is a

Re: Bug#573349: ITP: libkcompat -- Linux kernel compatibility library for userspace applications

* Bastian Blank wrote: > On Wed, Mar 10, 2010 at 01:33:21PM -0500, Jon Bernard wrote: > > * License : LGPL 2.1 > > Please elaborate how a part of a GPL 2 licensed source (Linux kernel) > can be LGPL 2.1. The code is "compatible" in that it provides identic

Bug#471495: closed by maximilian attems (Bug#471495: fixed in linux-2.6 2.6.31-1~experimental.1)

Thanks for finally doing this; I had a response to Bastian queued up in my postponed folder but I hadn't got around to finishing it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

iwlwifi non-free?

AFAIK iwlwifi is an open source driver that was merged into the linux kernel v2.6.24 and Debian still needs 'firmware-iwlwifi' installed which is in the non-free repository. Am I missing something?

Bug#543398: linux-image-2.6.30-1-686: e100 is missing a dependency on linux-firmware

ne can reboot into an earlier kernel, that's how I fixed the problem (after several rounds of diagnosis). - Original Message ----- From: "dann frazier" To: "Jon Thackray" ; <543...@bugs.debian.org> Sent: Monday, August 24, 2009 8:27 PM Subject: Re: Bug#54339

Bug#543398: linux-image-2.6.30-1-686: e100 is missing a dependency on linux-firmware

Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: important In the 2.6.30 kernel, but not in 2.6.26, e100 depends on d101m_ucode.bin, from firmware-linux. The kernel package is not marked as depending on this. Consequently, if you reboot into your newly installed 2.6.30 kernel, your n

Bug#525072: initramfs-tools: update-initramfs failure resulted in broken dpkg and presumably unbootable system

27;s,^(.*)$,$1.conf' in /etc/modprobe.d to try and shut out Marco's annoying warning messages? Thank you for your help. -- Jon Dowland signature.asc Description: Digital signature

Bug#525072: initramfs-tools: update-initramfs failure resulted in broken dpkg and presumably unbootable system

nt daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- no debconf information -- Jon Dowland http://jmtd.net/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@list

Bug#518412: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]

d NOT being run > when the kernel is installed. This is the thing I'm trying to understand. That, and what I can really do in the absence of a time machine to change a former release :) Jon. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subjec

Bug#518412: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]

can "preserve for 5 years", etc. How does the old version know something is going to change? It doesn't and it can't. v3.4 will always be the same, and it won't change. The files changed slightly in v3.6, but v3.4 can never know about that. > P.S. Thanks a lot for your pr

Bug#518412: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]

On Thu, 2009-03-19 at 23:09 +0100, Frans Pop wrote: > On Thursday 19 March 2009, Jon Masters wrote: > > Yes, it was a bad idea of > > mine (perhaps) to change the existing file format and I've learned > > something, but it should only have affected for example that 3.

Bug#518412: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]

in use. Yes, it was a bad idea of mine (perhaps) to change the existing file format and I've learned something, but it should only have affected for example that 3.4 release you're using. Jon. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of &quo

Bug#518412: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]

t you would have been fine - you're talking lack of forward compatibility actually. Unless I'm missing something, in which case please clarify. I would like it also if you'd send me the generated files, distro info, etc. Jon. -- To UNSUBSCRIBE, email to debian-kernel-requ...@

Bug#407217: RTL-8169 multicast bug

On Thu, Jul 10, 2008 at 05:40:07PM +0300, Martin Michlmayr wrote: > Jon, so this also happened with 2.6.18? I believe so. I'm afraid I cannot confirm, if 2.6.18 was the default kernel for the version of debian installed when you first put up the n2100 pages a few years ago, then yes.

Bug#407217: RTL-8169 multicast bug (was Re: sky2 hang reproduced)

kernels: best way is to ensure your iface is not promisc, and run something like mt-daapd and see if after 30 minutes or so your share disappears from the network, and whether setting the iface to promisc fixes it. linux-image-2.6.25-2-iop32x is in the archive so I will try and install that. -

Bug#407217: reproduced

found 407217 2.6.24-4 thanks running linux-image-2.6.24-1-iop32x on that machine now (armel architecture) and the bug is definitely still there. -- Jon Dowland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#486433: please bring back prism54

esn't allow you to do master mode. Please do not disable it unless it doesn't work at all anymore. -- Jon DeVree "It's an ingenious solution to a problem that should never have existed in the first place." -James May, Top Gear -- To UNSUBSCRIBE, email to [EMAI

Bug#471344: reported in launchpad; fixed upstream

I've just checked out bluetooth-2.6 0e81a8ae37687845f7cdfa2adce14ea6a5f1dd34 and built ./drivers/bluetooth against the current kernel. The problem has gone away. -- Jon Dowland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#471495: linux-2.6: please add Vcs-* fields/headers to debian/control file

686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Jon Dowland ISS UNIX Team --- linux-2.6-2.6.24/debian/control~ 2008-03-18 14:44:05.0 + +++ linux-2.6-2.6.24/debian/control 2008-03-18 14:47:06.0 +

Bug#407217: closed by maximilian attems <[EMAIL PROTECTED]> (Re: avahi-daemon/mt-daapd disappear from network after ~1 hour)

ications with this driver. -- Jon Dowland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#464953: exploit hung my machine

ix on a Redhat Enterprise 5 machine at work and that hung similarly. The module solution Michael Holtz posted looks much safer. -- Jon Dowland ISS UNIX Team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#449320: kernel: not recognizing 8 cpu on ASUS two quad AMD 64FX74

Package: kernel Severity: important kernel 2.6.18-5-AMD64 #1 SMP sees physical 0 and 1, but only core 0 and 1 on each. I have two AMD 64FX74 quad core processors. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bi

Bug#441246: kernel: does not detect multiple cores in Core 2 Duo 6700

I've tried 2.6.22, and it behaves the same way as 2.6.21, ie /proc/cpuinfo says number of cores is 1. Sorry for the delay, I had to wait for a long job to complete. - Original Message - From: "maximilian attems" <[EMAIL PROTECTED]> To: "Jon Thackray&quo

Bug#441246: kernel: does not detect multiple cores in Core 2 Duo 6700

Package: kernel Version: 2.6.21-2-686-bigmem Severity: important -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.21-2-686-bigmem Locale: LANG=en_GB, LC_CTYPE=en_GB (charm

Bug#402876: [fuse-devel] FUSE not working on ARM? Hangs during stat64

lt fuse-2.6.1 from the tarball on sf.net and everything worked with that. I tried encfs and sshfs invocations that failed last time, both with the .so built in that source and also using the older .so in debian (2.5.3), all were fine. Thanks for your help, -- Jon Dowland -- To UNSUBSCRIBE, ema

Bug#377539: Summarizing our IRC session

We discussed this on IRC. Here's what we came up with. PnP support for nsc-ircc is new in 2.6.17. The dmesg log shows the following: nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3. nsc-ircc, chip->init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli)

Bug#353790: Bug is being fixed upstream

Hi, The linux-ide developers have worked with Silicon Image and found the cause and a real fix. Yay for open specifications! The fix is expected in version 2.6.16 or 17. See http://comments.gmane.org/gmane.linux.ide/8255 Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#353790: Progress

, 0x4379, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sil_3112_m15w }, I can see from the log that Seagate errata fix is enabled, and haven't seen any more lockups. This removes the last occurrence of sil_3112 in sil_pci_tbl. Regards Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "

Bug#353790: More info

there anything like hdparm for SATA? Regards Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#353790: linux-image-2.6.15-1-686: SATA lockups

hope you have suggestions on how to proceed with this problem. Regards Jon K Hellan lspci output: :00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4) :00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev a6) :00:01.1 SMBus: nVidia Corporation nForce3

how to use initrd command

I'm attempting to upgrade Debian 3.1 kernel version 2.4 to the latest 2.6 version. I understand I need to add a initrd command somewhere in this. How do I pass this command and when (a link to a document would be a big help). Thanks Jon

kernel upgrade error

od -m 660 /dev/null c 1 3. These returned an access denied on all the files. 1) how do I upgrade the kernel to the 2.6 stable version 2) can this be done using apt-get? or 3) can the above be fixed Thanks Jon L. Miller, ASE, CNS, CLS, MCNE, CCNA Director/Sr Systems Consultant MMT Networks Pt

Bug#336566: Same here

auto (fatal) Failed to create initrd image. Please advise if you need some particular info. Jon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: GCC version change / C++ ABI change

od reason to make it do so? The lifetime of the 2.4 kernel is undoubtably less than the GCC 3.x branch in distributions. Any attempt to port 2.4 to 4.0 would run the risk of introducing problems for no gain. -- Jon Dowland http://jon.dowland.name/ PGP fingerprint: 7032F238 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#306319: kernel-image-2.6.8-2-686-smp: e1000 driver does not work

Package: kernel-image-2.6.8-2-686-smp Version: 2.6.8-13 Severity: normal The e1000 kernel module when installed complains about old and new style parameter mismatches. When trying to invoke it via ifup, SIOCSIFADDR no such device errors occur. The card is an intel PRO1000GT card with the 82541 P

Bug#268208: kernel-image-2.6.8-1-686-smp: 2.6.8 smp kernel fails to gunzip initrd and hangs at APIC stage on i865

Jon Thackray writes: > maximilian attems writes: > > On Fri, 14 Jan 2005, Jon Thackray wrote: > > > > Content-Description: message body text > > > maximilian attems writes: > > > > On Thu, 13 Jan 2005, Jon Thackray wrote: > > > &g

Bug#268208: kernel-image-2.6.8-1-686-smp: 2.6.8 smp kernel fails to gunzip initrd and hangs at APIC stage on i865

maximilian attems writes: > On Fri, 14 Jan 2005, Jon Thackray wrote: > > Content-Description: message body text > > maximilian attems writes: > > > On Thu, 13 Jan 2005, Jon Thackray wrote: > > > > > > > System has Intel 865 MB, P4/3400, 2Gb

Bug#290418: kernel-image-2.6.5-1-686-smp: I have an SATA disc driven by this kernel which has acquired a large number of fsck errors

maximilian attems writes: > On Fri, 14 Jan 2005, Jon Thackray wrote: > > > Package: kernel-image-2.6.5-1-686-smp > > Severity: grave > > Justification: renders package unusable > > 2.6.5 is not a sarge kernel and month old, > it is not supported in an

Bug#268208: kernel-image-2.6.8-1-686-smp: 2.6.8 smp kernel fails to gunzip initrd and hangs at APIC stage on i865

maximilian attems writes: > On Fri, 14 Jan 2005, Jon Thackray wrote: > > Content-Description: message body text > > maximilian attems writes: > > > On Thu, 13 Jan 2005, Jon Thackray wrote: > > > > > > > System has Intel 865 MB, P4/3400, 2Gb

Bug#268208: kernel-image-2.6.8-1-686-smp: 2.6.8 smp kernel fails to gunzip initrd and hangs at APIC stage on i865

maximilian attems writes: > On Thu, 13 Jan 2005, Jon Thackray wrote: > > > System has Intel 865 MB, P4/3400, 2Gb RAM, five discs including > > one SCSI and one SATA. It worked fine with the 2.6.5 kernel, but the > > 2.6.8 kernel won't boot. > > did yo

Bug#290418: kernel-image-2.6.5-1-686-smp: I have an SATA disc driven by this kernel which has acquired a large number of fsck errors

Package: kernel-image-2.6.5-1-686-smp Severity: grave Justification: renders package unusable The system is an Intel 865 MB with video and networking. I have three PATA and one SATA disc. Despite the system not having had power fails or any hardware failures, the SATA disc has become badly corru

Bug#268208: kernel-image-2.6.8-1-686-smp: 2.6.8 smp kernel fails to gunzip initrd and hangs at APIC stage on i865

Package: kernel-image-2.6.8-1-686-smp Version: 2.6.8-10 Followup-For: Bug #268208 System has Intel 865 MB, P4/3400, 2Gb RAM, five discs including one SCSI and one SATA. It worked fine with the 2.6.5 kernel, but the 2.6.8 kernel won't boot. -- System Information: Debian Release: 3.1 APT prefers

Bug#274372: kernel-image-2.6.8-1-686: Block elevator bug when unmounting usb storage device

Package: kernel-image-2.6.8-1-686 Version: 2.6.8-3 Severity: normal This turned up in syslog when unmounting a usb stick. Oct 1 09:54:20 kuhaugen kernel: usb-storage: Error in device_reset: invalid state 0 Oct 1 09:55:22 kuhaugen kernel: [ cut here ] Oct 1 09:55:22 ku