linux-2.6_2.6.26-15lenny2_i386.changes REJECTED
=== Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529785: it seems the bluetooth stack issues originate in a kernel regression
Hello, I am not yet 100% sure what happens for others, but in my case I narrowed down the problem to the kernel. The 2.6.26 kernels seem to work fine for me, but none of the later kernels do. Daniel, what kernel version did you use when you stopped experiencing problems in squeeze? What kernel are you running now? Does the bluetooth stack work properly after a hibernate/resume cycle with any kernel later than 2.6.26? -- Regards, EddyP = Imagination is more important than knowledge A.Einstein signature.asc Description: OpenPGP digital signature
Bug#529785: it seems the bluetooth stack issues originate in a kernel regression
On Sat, 13 Jun 2009, Eddy Petrișor wrote: Hello, I am not yet 100% sure what happens for others, but in my case I narrowed down the problem to the kernel. The 2.6.26 kernels seem to work fine for me, but none of the later kernels do. Daniel, what kernel version did you use when you stopped experiencing problems in squeeze? What kernel are you running now? Does the bluetooth stack work properly after a hibernate/resume cycle with any kernel later than 2.6.26? did you try 2.6.30? see trunk apt lines http://wiki.debian.org/DebianKernel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532908: initramfs-tools: initrd image not created on custom kernels
On Fri, 12 Jun 2009, Ritesh Raj Sarraf wrote: Package: initramfs-tools Version: 0.93.2 Severity: important I haven't verified on Debian shipped kernels, but when installing my custom kernel, initramfs-tools didn't create an initrd image for the same. I had to boot through the previous kernel and manually create the initrd image. Ritesh this is due to changes of kernel-package and nobody stepped up yet to provide the correct hook script /etc/kernel/, see kernel-package docs and initramfs-tools bug report. could close away but will merge with aboves report on time.. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Applying e1000e patch to the Debian 2.6.26 kernel
Ben Hutchings wrote: We normally backport specific bug fixes and small changes to support new hardware, rather than updating drivers completely. Some driver changes will depend on core changes in the kernel. (Lenny and a half)? I don't know when that will be released, but it will use an entirely new kernel version. Do I still have a chance to have it included anytime soon in Debian? Because that's the goal... It's really an annoying problem for us. It's a large patch combining cleanup and functional changes, which is always hard to review. Please instead identify which of the following changes between 2.6.26 and 2.6.27 are needed: 95b866d e1000e: Fix incorrect debug warning [...] a5136e2 e1000e: allow VLAN devices to use TSO and TCP CSUM offload I've put these individual changes in http://womble.decadent.org.uk/tmp/e1000e-patches/ so you don't need to use git to generate them. Ben. Thanks a lot for the effort to put this all online for me. I got them downloaded already locally, you can cleanup and delete these from your web server if you want. I can try the patches one by one, but that can take a long long time if I have to recompile a full kernel package each time. What do you think is the best approach for me to make quick tests? Just do a make modules_install from the linux-source-2.6.26 folder (taken from the linux-source-2.6 package), test, apply another patch, test, etc. ? Also, what's your suggestion to test all this? Make a dichotomy test, applying half of the patches, then 1/4, etc. until I can isolate what patch(es) are needed? That's my first idea, and shouldn't take too long if I can compile the e1000e module only and not the full kernel. Thanks for your help, Thomas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Please comsider adding a fscache fix for 2.6.30
Heyho! Could you please consider the patch in http://bugzilla.kernel.org/show_bug.cgi?id=13469 to fix fscache? Without it, fscache immediately oopsed and disabled itself. The patch is from fscache author David Howells, and I'm running it successfully on my system on top of 2.6.30-1~experimental.1~snapshot.13794. cheers -- vbi -- Development costs of average proprietary and free software don't differ radically because the methods are pretty much the same. The huge difference lies in the way the developers try to recoup their costs, not in the costs they have to compensate. -- Florian Weimer on debian-security signature.asc Description: This is a digitally signed message part.
Re: Applying e1000e patch to the Debian 2.6.26 kernel
On Sat, Jun 13, 2009 at 10:57:10PM +0800, Thomas Goirand wrote: Ben Hutchings wrote: We normally backport specific bug fixes and small changes to support new hardware, rather than updating drivers completely. Some driver changes will depend on core changes in the kernel. (Lenny and a half)? I don't know when that will be released, but it will use an entirely new kernel version. Do I still have a chance to have it included anytime soon in Debian? Because that's the goal... It's really an annoying problem for us. 5.0.2 should release very soon, but there's time for 5.0.3. It's a large patch combining cleanup and functional changes, which is always hard to review. Please instead identify which of the following changes between 2.6.26 and 2.6.27 are needed: 95b866d e1000e: Fix incorrect debug warning [...] a5136e2 e1000e: allow VLAN devices to use TSO and TCP CSUM offload I've put these individual changes in http://womble.decadent.org.uk/tmp/e1000e-patches/ so you don't need to use git to generate them. Ben. Thanks a lot for the effort to put this all online for me. I got them downloaded already locally, you can cleanup and delete these from your web server if you want. I can try the patches one by one, but that can take a long long time if I have to recompile a full kernel package each time. What do you think is the best approach for me to make quick tests? Just do a make modules_install from the linux-source-2.6.26 folder (taken from the linux-source-2.6 package), test, apply another patch, test, etc. ? You shouldn't need to recompile the whole kernel every time - just do it once, then run make again after each patch application/removal. Also, what's your suggestion to test all this? Make a dichotomy test, applying half of the patches, then 1/4, etc. until I can isolate what patch(es) are needed? That's my first idea, and shouldn't take too long if I can compile the e1000e module only and not the full kernel. What is the problem you are seeing w/ the existing 2.6.26 kernel? I didn't see any explicit support for new hardware in these changesets, so I'm guessing the driver already loads but fails? The failure mode might give us a hint. Thanks for your help, Thomas -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Applying e1000e patch to the Debian 2.6.26 kernel
Forwarded Message From: Ben Hutchings b...@decadent.org.uk To: Thomas Goirand tho...@goirand.fr Subject: Re: Applying e1000e patch to the Debian 2.6.26 kernel Date: Sat, 13 Jun 2009 16:26:32 +0100 On Sat, 2009-06-13 at 22:57 +0800, Thomas Goirand wrote: Ben Hutchings wrote: We normally backport specific bug fixes and small changes to support new hardware, rather than updating drivers completely. Some driver changes will depend on core changes in the kernel. (Lenny and a half)? I don't know when that will be released, but it will use an entirely new kernel version. Do I still have a chance to have it included anytime soon in Debian? Because that's the goal... It's really an annoying problem for us. Unfortunately you have just missed the cut-off for stable update 5.0.2, but there may be an update to stable-proposed-updates soon after, which you could then add to your APT sources. Alternately you can build and install e1000e separately from e1000.sf.net. It's a large patch combining cleanup and functional changes, which is always hard to review. Please instead identify which of the following changes between 2.6.26 and 2.6.27 are needed: 95b866d e1000e: Fix incorrect debug warning [...] a5136e2 e1000e: allow VLAN devices to use TSO and TCP CSUM offload I've put these individual changes in http://womble.decadent.org.uk/tmp/e1000e-patches/ so you don't need to use git to generate them. Ben. Thanks a lot for the effort to put this all online for me. You're welcome. It's actually really easy to extract a patch series like this from git. I got them downloaded already locally, you can cleanup and delete these from your web server if you want. I can try the patches one by one, but that can take a long long time if I have to recompile a full kernel package each time. You won't. What do you think is the best approach for me to make quick tests? Just do a make modules_install from the linux-source-2.6.26 folder (taken from the linux-source-2.6 package), test, apply another patch, test, etc. ? Once you've configured and built the kernel once, it should be as simple as: patch -p1 some-patch make # will rebuild just e1000e rmmod e1000e insmod drivers/net/e1000e/e1000e.ko Also, what's your suggestion to test all this? Make a dichotomy test, applying half of the patches, then 1/4, etc. until I can isolate what patch(es) are needed? That's my first idea, and shouldn't take too long if I can compile the e1000e module only and not the full kernel. A lot of them are just formatting changes or adaptation to API changes, and can immediately be discounted. Then you could do what you suggest (this is commonly called bisection, not dichotomy) over the remainder. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#503292: linux-latest-2.6: new dummy images for Samsung S3C-based devices
retitle 503292 linux-latest-2.6: new dummy images for Samsung s3c24xx devices thanks Hi there! Cc:ing the pkg-fso-maint@ mailing list as well as the debian-arm@ one: please keep cc:ed at least pkg-fso-maint@ (if you do so, no need to cc: me, I read that list). FYI, I recently asked for the status of Openmoko support in upstream Linux kernel: http://thread.gmane.org/gmane.comp.handhelds.openmoko.kernel/9955 On Fri, 24 Oct 2008 15:39:05 +0200, Luca Capello wrote: For the other kernel flavors these packages are provided by linux-latest-2.6: I'm not here to ask for these dummy packages right now. On the contrary, since I'm going to add them to the linux-2.6-openmoko source package [4], for $OPENMOKO I'd like to use a name which *maybe* will be the same linux-latest-2.6 will provide in future (thus avoiding hardcoded package dependencies). I thought about the -s3c suffix, because both Openmoko models (GTA01, Neo 1973 [5] and GTA02, Neo FreeRunner [6]) use a Samsung SoC from the S3C family (2410 and 2442, respectively). Would this be a good option in the long term? I found a more detailed list of the different ARM processors [7], specifically for the Samsung SoC ones: * ARM920T: S3C2410, S3C2440, S3C2442 and S3C2443 * ARM926EJS: S3C2412, S3C2413, S3C2416 and S3C2450 * ARM1176EJS: S3C6400 and S3C6410 According to linux/Documentation/arm/Samsung-S3C24XX/Overview.txt: The Samsung S3C24XX range of ARM9 System-on-Chip CPUs are supported by the 's3c2410' architecture of ARM Linux. Currently the S3C2410, S3C2412, S3C2413, S3C2440, S3C2442 and S3C2443 devices are supported. Indeed, both GTA01 and GTA02 are supported by the s3c2410 architecture (linux/arch/arm/mach-s3c2410 and linux/arch/arm/mach-s3c2440), thus I guess a better suffix would be -s3c2410 (I changed the bug title to reflect this). I do not know how much performance we gain with an Openmoko-optimised kernel. In this case we can simply use the -openmoko suffix. As a final note, it seems there are incompatible kernel options for GTA01 and GTA02 [8], thus maybe a common kernel would never be possible. I have not tried to build a common kernel for GTA01 and GTA02 yet [9], nevertheless, my first question stands. Thx, bye, Gismo / Luca Footnotes: [1] http://lists.linuxtogo.org/pipermail/smartphones-kernel/2008-October/13.html [2] http://wiki.debian.org/Teams/DebianFSO [3] http://lists.linuxtogo.org/pipermail/smartphones-kernel/2008-October/07.html [4] http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git;a=summary [5] http://wiki.openmoko.org/wiki/GTA01 [6] http://wiki.openmoko.org/wiki/GTA02 [7] http://elinux.org/Processors [8] http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-April/001400.html [9] http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-June/001601.html pgptJaiNyByB0.pgp Description: PGP signature
Processed: Re: Bug#503292: linux-latest-2.6: new dummy images for Samsung S3C-based devices
Processing commands for cont...@bugs.debian.org: retitle 503292 linux-latest-2.6: new dummy images for Samsung s3c24xx devices Bug#503292: linux-latest-2.6: new dummy images for Samsung S3C-based devices Changed Bug title to `linux-latest-2.6: new dummy images for Samsung s3c24xx devices' from `linux-latest-2.6: new dummy images for Samsung S3C-based devices'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529222: Bug remains in 0.93.3
On Fri, 2009-06-12 at 23:21 +0200, maximilian attems wrote: why do you have elilo installed? Sorry I don't know why I have elilo installed. I don't even know what it does. I was able to purge it without any dependency problems reported: # dpkg --purge elilo (Reading database ... 231745 files and directories currently installed.) Removing elilo ... Purging configuration files for elilo ... Processing triggers for man-db ... After removing elilo the issue is resolved: # dpkg --configure -a Setting up initramfs-tools (0.93.3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.26-2-686 Nice catch. I would have never thought to do that. Thanks for the help. I don't know how this bug should be handled but removing elilo is a reasonable work-around for me. please post output of dpkg -l elilo Before removal of elilo it reported: # dpkg -l elilo Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii elilo 3.10-1 Bootloader for systems using EFI-based firmw signature.asc Description: This is a digitally signed message part
Bug#529785: it seems the bluetooth stack issues originate in a kernel regression
maximilian attems napsal(a): On Sat, 13 Jun 2009, Eddy Petrișor wrote: Hello, I am not yet 100% sure what happens for others, but in my case I narrowed down the problem to the kernel. The 2.6.26 kernels seem to work fine for me, but none of the later kernels do. Daniel, what kernel version did you use when you stopped experiencing problems in squeeze? What kernel are you running now? Does the bluetooth stack work properly after a hibernate/resume cycle with any kernel later than 2.6.26? did you try 2.6.30? see trunk apt lines http://wiki.debian.org/DebianKernel I now run 2.6.29.4 and it looks like that bluetooth work after suspend/resume. Dan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 529785
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 529785 + pending Bug#529785: [regression] the entire bluetooth stack needs a restart after resume There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529222: Bug remains in 0.93.3
On Sat, 13 Jun 2009, Don Pellegrino wrote: Sorry I don't know why I have elilo installed. I don't even know what it does. I was able to purge it without any dependency problems reported: # dpkg --purge elilo (Reading database ... 231745 files and directories currently installed.) Removing elilo ... Purging configuration files for elilo ... Processing triggers for man-db ... After removing elilo the issue is resolved: had assumed so. # dpkg --configure -a Setting up initramfs-tools (0.93.3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.26-2-686 Nice catch. I would have never thought to do that. Thanks for the help. I don't know how this bug should be handled but removing elilo is a reasonable work-around for me. well having randomly installed non configured bootloaders is known to have bad results. before initramfs-tools was checking elilo with a wrong path, thus it never got noticed. nice greetings -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-modules-contrib-2.6_2.6.29-1_i386.changes ACCEPTED
Accepted: linux-modules-contrib-2.6_2.6.29-1.dsc to pool/contrib/l/linux-modules-contrib-2.6/linux-modules-contrib-2.6_2.6.29-1.dsc linux-modules-contrib-2.6_2.6.29-1.tar.gz to pool/contrib/l/linux-modules-contrib-2.6/linux-modules-contrib-2.6_2.6.29-1.tar.gz rt73-modules-2.6-486_2.6.29-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6-486_2.6.29-1_i386.deb rt73-modules-2.6-686-bigmem_2.6.29-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6-686-bigmem_2.6.29-1_i386.deb rt73-modules-2.6-686_2.6.29-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6-686_2.6.29-1_i386.deb rt73-modules-2.6-amd64_2.6.29-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6-amd64_2.6.29-1_i386.deb rt73-modules-2.6.29-2-486_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6.29-2-486_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb rt73-modules-2.6.29-2-686-bigmem_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6.29-2-686-bigmem_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb rt73-modules-2.6.29-2-686_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6.29-2-686_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb rt73-modules-2.6.29-2-amd64_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb to pool/contrib/l/linux-modules-contrib-2.6/rt73-modules-2.6.29-2-amd64_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb Override entries for your package: linux-modules-contrib-2.6_2.6.29-1.dsc - optional contrib/kernel rt73-modules-2.6-486_2.6.29-1_i386.deb - optional contrib/kernel rt73-modules-2.6-686-bigmem_2.6.29-1_i386.deb - optional contrib/kernel rt73-modules-2.6-686_2.6.29-1_i386.deb - optional contrib/kernel rt73-modules-2.6-amd64_2.6.29-1_i386.deb - optional contrib/kernel rt73-modules-2.6.29-2-486_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb - optional contrib/kernel rt73-modules-2.6.29-2-686-bigmem_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb - optional contrib/kernel rt73-modules-2.6.29-2-686_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb - optional contrib/kernel rt73-modules-2.6.29-2-amd64_2.6.29+1.0.3.6-cvs20090424-dfsg1-1_i386.deb - optional contrib/kernel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532906: linux-image-2.6.26-2-amd64: Unable to handle kernel paging request
On Fri, 2009-06-12 at 12:24 -0400, Arnout Boelens wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 Severity: normal Every once I a while I get kernel oops on one of my computers and find the following messages back in my syslog: With a similar Call Trace or different? [...] ** Tainted: P (1) [...] Can you reproduce this without the nvidia module loaded? Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#532906: linux-image-2.6.26-2-amd64: Unable to handle kernel paging request
On Fri, 2009-06-12 at 12:24 -0400, Arnout Boelens wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 Severity: normal Every once I a while I get kernel oops on one of my computers and find the following messages back in my syslog: Jun 12 10:42:03 yama kernel: [848178.269002] BUG: unable to handle kernel paging request at 2f467780 Jun 12 10:42:03 yama kernel: [848178.269002] IP: [2f467780] [...] Jun 12 10:42:03 yama kernel: [848178.269002] Call Trace: Jun 12 10:42:03 yama kernel: [848178.269002] [a031f9ab] ? :sunrpc:rpcauth_lookup_credcache+0xae/0x1e9 [...] That corresponds to this line in rpcauth_lookup_credcache(): if (!entry-cr_ops-crmatch(acred, entry, flags)) The function pointer entry-cr_ops-crmatch has turned out not to be a valid function address, and since entry-cr_ops should be pointing to a static constant structure which cannot itself be corrupted this suggests that *entry has somehow been corrupted. There is an upstream change that might deal with this issue, but I'm not convinced that it's related: commit 5f707eb429e2c98dfd564ffbbd9f536bf493d869 Author: Trond Myklebust trond.mykleb...@netapp.com Date: Tue Oct 28 15:21:42 2008 -0400 SUNRPC: Fix potential race in put_rpccred() Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#517449: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds)
On Thu, 2009-06-11 at 10:17 +0100, Berni Elbourn wrote: Hai Zaar wrote: On Wed, Jun 3, 2009 at 5:12 AM, Ben Hutchingsb...@decadent.org.uk wrote: You found some scheduling changes made post-2.6.28 which seemed to deal with this bug. However, that cannot be the full story because they are modifying code which was added after 2.6.26. The attached patch combines a bug fix made between 2.6.26 and .28 with most of the changes you identified. Based on my reading of commit messages and discussion, I think this makes a coherent set of changes. However there have been many other changes to the scheduler in this time and I cannot say for sure whether any of those are also required as I do not have any great knowledge of it. Please try rebuilding the lenny kernel (linux-source-2.6.26) with this patch applied and report whether it fixes the bug for you. Thank you for response! I've applied the patch to most recent lenny kernel and booted it. If in two weeks the problem does not occur, I will assume that the bug is gone (I will let you know). Thanks again! Is this for Dom0? I have two systems suffering this pain...and the silence on the Debian kernel lists to my offers to help test the patch is deafening. ;-) There are some patches mentioned here for 2.6.26 and also mention of 2.6.29. I am sorry because I can not get Google to tell me how Debian Xen kernels are patched and built :-( See http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage How does one build something like xen-linux-system-2.6.26-custom-xen-amd64 with those patches? That's actually a metapackage - it depends on the dom0 kernel and hypervisor, but doesn't contain any code. There's no need to rebuild it. Also assuming the fixes are already included in 2.6.29how should I build a Debian xen-linux-system-2.6.29-custom-xen-amd64? They are, but there are many other changes in 2.6.29 so it wouldn't be a valid test. I am familiar with make-kpkg... I'm not sure you can use that for Xen kernels. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#524300: linux-image-2.6.26-2-686: cannot turn wireless RF on/off on Asus U3S notebook when asus_acpi module is loaded
On Thu, 2009-06-04 at 23:31 -0400, John Brier wrote: FWIW I have reinstalled Lenny since this original report and I get seemingly different behavior. It's still not quite right.. I can't control the wireless indicator, it shows off, but it works anyway. I can't change the status even when I unload asus_acpi. I'm not on the system now so I'll have to try later. How can I try this 2.6.28-1 kernel? I don't see it in testing or unstable. Try the 2.6.29 kernel in unstable. I closed as version 2.6.28-1 because that's the first Debian package version with the fix. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#532562: linux-image-2.6.26-2-versatile: Kernel panics randomly while using apt-get
Axel Allende Lira escreveu: Hi there. I managed to track the error while doing a removal for orphaned packages. Here's the log: r...@terrier:/home/axel# deborphan libart-2.0-2 libgnomecups1.0-1 libgnomeprint2.2-data libaiksaurus-1.2-data libgail-common r...@terrier:/home/axel# apt-get remove `deborphan` Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto [0.00] sym0: unexpected disconnect lsi_scsi: error: Reselect with pending DMA [0.00] Unable to handle kernel NULL pointer dereference at virtual address 0358 [0.00] pgd = c7f4c000 [0.00] [0358] *pgd=07f4b031, *pte=, *ppte= [0.00] Internal error: Oops: 17 [#1] [0.00] Modules linked in: nls_utf8 isofs zlib_inflate udf nls_base crc_itu_t smc91x psmouse ext3 jbd mbcache sg sr_mod cdrom sd_mod sym53c8xx scsi_transport_spi scsi_mod [0.00] CPU: 0Not tainted (2.6.26-2-versatile #1) [0.00] PC is at sym_interrupt+0x968/0x18d8 [sym53c8xx] [0.00] LR is at sym_interrupt+0x348/0x18d8 [sym53c8xx] [0.00] pc : [bf033854]lr : [bf033234]psr: 8113 [0.00] sp : c7247e38 ip : c7247e38 fp : c7247e9c [0.00] r10: c0850c00 r9 : ffd00084 r8 : 0001 [0.00] r7 : bf03d640 r6 : r5 : ffd0 r4 : 000b [0.00] r3 : 000a r2 : 002c r1 : r0 : [0.00] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [0.00] Control: 00093177 Table: 07f4c000 DAC: 0015 [0.00] Process apt-get (pid: 1770, stack limit = 0xc7246268) [0.00] Stack: (0xc7247e38 to 0xc7248000) [0.00] 7e20:c7247e5c c7247e48 [0.00] 7e40: bf000604 bf000558 205d3030 c7c11800 c7247e74 c7247e60 bf02e6bc bf0005e8 [0.00] 7e60: c085cbc0 c7247e94 c7247e78 bf0322a4 c0850c00 bf03d640 [0.00] 7e80: 001b 000258f0 c7246000 bec95e24 c7247ebc c7247ea0 bf02e8e4 bf032ef8 [0.00] 7ea0: c7247ecc c086c2c0 c7247edc c7247ec0 c006f934 bf02e8a8 [0.00] 7ec0: c02897f8 001b c7247fb0 bec95e38 c7247ef4 c7247ee0 c0071250 c006f8fc [0.00] 7ee0: 001b c02897f8 c7247f14 c7247ef8 c0024048 c00711c8 bf000540 [0.00] 7f00: f114 0001 c7247f7c c7247f18 c00246b4 c002400c 001b c7246000 [0.00] 7f20: c02bbba0 2113 0010 c02897f8 000a bec95e38 000258f0 c7246000 [0.00] 7f40: bec95e24 c7247f7c c7247f80 c7247f60 c0047680 c00472cc 2113 [0.00] 7f60: c7246000 001b c02897f8 c7247f8c c7247f80 c0047680 c0047290 [0.00] 7f80: c7247fac c7247f90 c002404c c0047648 403a4064 f114 0001 [0.00] 7fa0: c7247fb0 c00248a4 c002400c 00026760 404f1000 408715e0 003b [0.00] 7fc0: 0001 bec95e30 bec95e38 000258f0 400d7b1c bec95e24 0d20 [0.00] 7fe0: 003b bec95d08 4005f36c 4005f36c 8010 [0.00] Backtrace: [0.00] [bf032eec] (sym_interrupt+0x0/0x18d8 [sym53c8xx]) from [bf02e8e4] (sym53c8xx_intr+0x48/0x74 [sym53c8xx]) [0.00] [bf02e89c] (sym53c8xx_intr+0x0/0x74 [sym53c8xx]) from [c006f934] (handle_IRQ_event+0x44/0x84) [0.00] r6: r5: r4:c086c2c0 [0.00] [c006f8f0] (handle_IRQ_event+0x0/0x84) from [c0071250] (handle_level_irq+0x94/0xec) [0.00] r7:bec95e38 r6:c7247fb0 r5:001b r4:c02897f8 [0.00] [c00711bc] (handle_level_irq+0x0/0xec) from [c0024048] (__exception_text_start+0x48/0x64) [0.00] r5:c02897f8 r4:001b [0.00] [c0024000] (__exception_text_start+0x0/0x64) from [c00246b4] (__irq_svc+0x34/0xa0) [0.00] Exception stack(0xc7247f18 to 0xc7247f60) [0.00] 7f00:001b c7246000 [0.00] 7f20: c02bbba0 2113 0010 c02897f8 000a bec95e38 000258f0 c7246000 [0.00] 7f40: bec95e24 c7247f7c c7247f80 c7247f60 c0047680 c00472cc 2113 [0.00] r6:0001 r5:f114 r4: [0.00] [c0047284] (__do_softirq+0x0/0xd4) from [c0047680] (irq_exit+0x44/0x4c) [0.00] r6: r5:c02897f8 r4:001b [0.00] [c004763c] (irq_exit+0x0/0x4c) from [c002404c] (__exception_text_start+0x4c/0x64) [0.00] [c0024000] (__exception_text_start+0x0/0x64) from [c00248a4] (__irq_usr+0x44/0xa0) [0.00] Exception stack(0xc7247fb0 to 0xc7247ff8) [0.00] 7fa0: 00026760 404f1000 408715e0 003b [0.00] 7fc0: 0001 bec95e30 bec95e38 000258f0 400d7b1c bec95e24 0d20 [0.00] 7fe0: 003b bec95d08 4005f36c 4005f36c 8010 [0.00] r6:0001 r5:f114 r4: [0.00] Code: e1a01000 e5932000 e59f06fc ea2f (e5963358) [0.00] Kernel panic - not syncing: Fatal exception in interrupt Qemu also
Removal of rt73-modules
Daniel, The Ralink legacy drivers previously maintained at serialmonkey.com have now been completely abandoned in favour of the rewritten drivers included in the kernel. I am trying to discourage people from using the legacy drivers and to report bugs on the kernel if the replacement drivers don't work for them. So, as further discouragement, I would like to get rid of the rt73-modules binary packages. As these are the only binaries now built by linux-modules-contrib-2.6 I think that means removing that source package too. Do you see any problem with this? Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Processed: tagging 524699
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 524699 + pending Bug#524699: e1000e: random kernel oopses There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 506964
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 506964 + pending Bug#506964: linux-image-2.6.26-1-686: radeonfb suspend/resume for Acer Travelmate 29X Tags were: pending patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 521553
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 521553 + pending Bug#521553: Staging drivers contain non-free firmware Tags were: pending Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 524699
Processing commands for cont...@bugs.debian.org: tags 524699 pending Bug#524699: e1000e: random kernel oopses Tags were: pending Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Removal of rt73-modules
Ben Hutchings wrote: So, as further discouragement, I would like to get rid of the rt73-modules binary packages. is it enough if this happens for 2.6.30? by linux-modules-contrib-2.6 I think that means removing that source package too. Do you see any problem with this? no; the conglomeration package has to stay. there will be other contrib modules for the next uploads. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
