Processed: severity of 550898 is important
Processing commands for cont...@bugs.debian.org: # adding hw support justifies important severity severity 550898 important Bug #550898 [linux-image-2.6.26-2-s390x] DASD DIAG driver doesn't work for read-only minidisks (s390, s390x only) Severity set to 'important' from 'normal' 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 550898
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 550898 + pending Bug #550898 [linux-image-2.6.26-2-s390x] DASD DIAG driver doesn't work for read-only minidisks (s390, s390x only) Added tag(s) 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#465278: appletouch failure still present with linux-image-2.6.32-trunk-powerpc
Package: linux-2.6 Version: 2.6.32-1 Severity: normal All, I can confirm appletouch failure on resume is still an issue with current kernels. Mark -- Package-specific info: ** Version: Linux version 2.6.32-trunk-powerpc (Debian 2.6.32-1) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 Mon Dec 7 20:54:08 UTC 2009 ** Command line: root=/dev/hda3 ro ** Not tainted ** Kernel log: [ 89.923896] radeonfb :00:10.0: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b7) [ 89.923953] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x4 (was 0x0, writing 0x80084000) [ 89.923966] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x3 (was 0x0, writing 0x1000) [ 89.923979] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x1 (was 0x0, writing 0x6) [ 89.926085] ohci_hcd 0001:10:1b.0: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 89.926131] ohci_hcd 0001:10:1b.1: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 89.926178] ehci_hcd 0001:10:1b.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100012) [ 89.941872] radeonfb (:00:10.0): resuming from state: 2... [ 90.649704] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 90.649719] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 91.833675] eth0: resuming [ 91.898014] PHY ID: 4061e4, addr: 0 [ 93.162797] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 93.167860] adb: starting probe task... [ 93.169840] hda: UDMA/100 mode selected [ 93.172562] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 93.172701] hdc: MWDMA2 mode selected [ 93.192932] adb devices: [2]: 2 c4 [7]: 7 1f [ 93.197909] ADB keyboard at 2, handler 1 [ 93.197916] adb: finished probe task... [ 93.601673] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 93.645236] Restarting tasks ... done. [ 94.222604] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 94.222620] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 94.222729] [drm] Num pipes: 1 [ 108.373268] PM: Syncing filesystems ... done. [ 108.710960] [drm] Num pipes: 1 [ 109.035052] Freezing user space processes ... (elapsed 0.04 seconds) done. [ 109.078025] Freezing remaining freezable tasks ... (elapsed 0.61 seconds) done. [ 109.691113] Suspending console(s) (use no_console_suspend to debug) [ 109.730713] btusb_intr_complete: hci0 urb deadcb00 failed to resubmit (1) [ 109.731682] btusb_bulk_complete: hci0 urb deadc480 failed to resubmit (1) [ 109.732681] btusb_bulk_complete: hci0 urb deadcc80 failed to resubmit (1) [ 110.149261] eth0: suspending, WakeOnLan disabled [ 110.225768] radeonfb (:00:10.0): suspending for event: 2... [ 110.225829] agpgart-uninorth :00:0b.0: disabling AGP on device :00:10.0 [ 110.225863] agpgart-uninorth :00:0b.0: disabling AGP on bridge [ 110.725476] radeonfb :00:10.0: restoring config space at offset 0xc (was 0x0, writing 0x90020001) [ 110.725497] radeonfb :00:10.0: restoring config space at offset 0x6 (was 0x0, writing 0x9000) [ 110.725510] radeonfb :00:10.0: restoring config space at offset 0x5 (was 0x1, writing 0x401) [ 110.725522] radeonfb :00:10.0: restoring config space at offset 0x4 (was 0x8, writing 0x9808) [ 110.725534] radeonfb :00:10.0: restoring config space at offset 0x3 (was 0x0, writing 0xff08) [ 110.725547] radeonfb :00:10.0: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b7) [ 110.725603] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x4 (was 0x0, writing 0x80084000) [ 110.725616] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x3 (was 0x0, writing 0x1000) [ 110.725630] b43-pci-bridge 0001:10:12.0: restoring config space at offset 0x1 (was 0x0, writing 0x6) [ 110.727734] ohci_hcd 0001:10:1b.0: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 110.727780] ohci_hcd 0001:10:1b.1: restoring config space at offset 0x1 (was 0x210, writing 0x212) [ 110.727826] ehci_hcd 0001:10:1b.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100012) [ 110.743508] radeonfb (:00:10.0): resuming from state: 2... [ 111.451338] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [ 111.451353] radeonfb :00:10.0: putting AGP V2 device into 4x mode [ 112.635303] eth0: resuming [ 112.699648] PHY ID: 4061e4, addr: 0 [ 114.857567] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 114.862359] adb: starting probe task... [ 114.863318] hda: UDMA/100 mode selected [ 114.865972] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 114.866109] hdc: MWDMA2 mode selected [ 114.888174] adb devices: [2]: 2 c4 [7]: 7 1f [ 114.893168] ADB keyboard at 2, handler 1 [ 114.893176] adb: finished probe task... [
Re: scheduling 2.6.26-21
On Wed, Nov 25, 2009 at 01:32:01PM -0700, dann frazier wrote: On Tue, Nov 24, 2009 at 02:02:25PM -0700, dann frazier wrote: We have several pending changes, plus we need to merge in the latest DSAs. I'll plan on uploading tomorrow, so let me know if you have any changes pending that might need more time. The p-u processing isn't working at the moment, and there's no real point in uploading until it is - so I'm postponing.. p-u processing is going again, albeit manually, so I'd like to reschedule this for tomorrow. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562287: kdm/X crashs on first login
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: linux-2.6 Version: 2.6.32-2 Severity: important Hello, I have got the following setup: * two Debian Sid machines * One i686 and one amd64 * amd64 with fglrx and i686 with the free radeon driver (dri enabled) * KDE4 with kdm since Kernel 2.6.32-trunk, the first (successful) login with kdm fails. X/kdm restarts, the second login is fine. I can not find any crash logs in syslog, dmesg, Xorg.log, kdm.log and so on.. If I start my PC with 2.6.31, everything is fine again. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkszQUAACgkQ2XA5inpabMedeQCdEVEwg5zj2thgdxjP4Cdu/4xw jXkAnA9i+SbNl/uVb1Y5hF7bSksUpx58 =LcRZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562205: Found in version should be 2.6.32-1 + severity normal seems misleading
Found in version should be 2.6.32-1 not 2.6.32-2. Its the 2.6.32-1 kernel that has problem. Besides, If anyone can guaranty I will be able to fix my problem OK for normal, but so far, I'm still skeptical: without the mdt devices, I cannot flash any new kernel version. Modprobing the correct driver for the flash devices after boot is not sufficient... --eric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562287: Bug#562026: kdm cannot open ConsoleKit session on first login attempt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sergiy Yegorov schrieb: Hi. Really, it causes only with 2.6.32 kernel. So this report is wrong. Sorry, my mistake. Thu 24 Dec 2009 12:32:03 Patrick Matthäi wrote: Hi, I have just reported this issue against the linux-2.6 package (no bug number, yet). I have got the same on all my machines, but only with kernel 2.6.32. This is the bugnumber: #562287 - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkszbQMACgkQ2XA5inpabMeDEQCfXLRNGy6vKZbdbHWHdMRjcB4U BrwAmwTHfRyOhCnqAkRK2n1hs05FLbBT =yxtH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558237: Re: Bug#558237: linux-source-2.6.32: X with xserver-xorg-video-intel does not work any longer
Mike Hommey wrote: I have a similar problem, except i don't have any error message on VT or logs. The mouse cursor is static when it should be animated, and most of the screen is not updated. Some parts may end up being filled up some times. I had the exact same issue. Now (maybe after a linux-image package upgrade, but I am not sure) it changed into corrupted image: -black squares on text forms -black horizontal ~16px long lines around and lots of these messages [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung render error detected, EIR: 0x i915: Waking up sleeping processes [drm:i915_wait_request] *ERROR* i915_wait_request returns -5 (awaiting 2 at 1) I have KMS enables, but I had the same corrupted output even without it. ps: if you think this is an unrelated issue, please let me know and I'll file another bug. Thanks, Ludovico -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562205: linux-image-2.6.32-trunk-orion5x: Not more mtd device = impossible to flash new kernel
* Eric Valette eric.vale...@free.fr [2009-12-24 00:11]: Yes it is on a DNS 323. But how will this be fixed? Is it possible to recreate the mtd devices after having flashed a kernel without proper in kernel support? Or will you find a way to upload the drivers via correct modules and recreate the needed devices manually? It will be fixed in the next kernel upload. Most people don't run kernels from unstable so it will be fixed before the package moves to testing. If you run a stable from unstable, you have to expect breakage from time to time. If loading the module doesn't work, I see two possibilities to recover your machine: - maybe you can use kexec to execute a good kernel and then write it to flash. - use the serial console (as documented on my web page). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity #562046 wishlist Bug #562046 [linux-2.6] Please activate vmxnet3 as module Severity set to 'wishlist' from 'minor' 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
Processing of tgt_1.0.0-1_amd64.changes
tgt_1.0.0-1_amd64.changes uploaded successfully to localhost along with the files: tgt_1.0.0-1.dsc tgt_1.0.0.orig.tar.gz tgt_1.0.0-1.debian.tar.gz tgt_1.0.0-1_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562046: I mixed up everything
I think I mixed up everything in this bug. - vmxnet3 isn't used yet, I guess we'll have to wait for a new VMPlayer (or something else, I don't know if VirtualBox could you use it) - vmnet couldn't be built because of VMWare. We can make it build, there is lots of documentation outthere. So there is no need to rush ;-) Thanks -- Julien Wajsberg -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 560710
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 560710 + pending Bug #560710 [tgt] tgt-admin depeds on libconfig-general-perl Added tag(s) 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#560710: marked as done (tgt-admin depeds on libconfig-general-perl)
Your message dated Thu, 24 Dec 2009 16:02:44 + with message-id e1nnq9e-0007iq...@ries.debian.org and subject line Bug#560710: fixed in tgt 1:1.0.0-1 has caused the Debian Bug report #560710, regarding tgt-admin depeds on libconfig-general-perl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 560710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tgt Version: 1:0.9.11-1 Severity: normal tgt-admin use Config::General to analyze its configuration files /etc/tgt/targets.conf, without libconfig-general-perl installed, tgt-admin will throw error: Can't locate Config/General.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/sbin/tgt-admin line 13. BEGIN failed--compilation aborted at /usr/sbin/tgt-admin line 13. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tgt depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries tgt recommends no packages. tgt suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: tgt Source-Version: 1:1.0.0-1 We believe that the bug you reported is fixed in the latest version of tgt, which is due to be installed in the Debian FTP archive: tgt_1.0.0-1.debian.tar.gz to main/t/tgt/tgt_1.0.0-1.debian.tar.gz tgt_1.0.0-1.dsc to main/t/tgt/tgt_1.0.0-1.dsc tgt_1.0.0-1_amd64.deb to main/t/tgt/tgt_1.0.0-1_amd64.deb tgt_1.0.0.orig.tar.gz to main/t/tgt/tgt_1.0.0.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 560...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frederik Schüler f...@debian.org (supplier of updated tgt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 Dec 2009 16:34:17 +0100 Source: tgt Binary: tgt Architecture: source amd64 Version: 1:1.0.0-1 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Frederik Schüler f...@debian.org Description: tgt- Linux SCSI target user-space tools Closes: 560710 Changes: tgt (1:1.0.0-1) unstable; urgency=low . * New upstream release. - Drop GPL digest patch, upstream has other implementation. * Add dependency on libconfig-general-perl. (Closes: #560710) * Build iSER driver, too. Checksums-Sha1: b00bc501b3737deec18f56f0381c486b083e9697 1103 tgt_1.0.0-1.dsc 14ffbd426d2bd9e20b8cd05dbfd68f68eb6e63e2 303689 tgt_1.0.0.orig.tar.gz 43d1c082b4b924b5021fead47252d3dee858983c 4615 tgt_1.0.0-1.debian.tar.gz 15fe6d6bbea77fe080198b4475e2fe1326f4555f 193328 tgt_1.0.0-1_amd64.deb Checksums-Sha256: 9c2936503556ba3474e853accb2281f95105f3d8d84acd939e53b17c3929a644 1103 tgt_1.0.0-1.dsc a3291ac57c348363c08abaa3caf98ab7117bdd2d2121e78a345611203f679da1 303689 tgt_1.0.0.orig.tar.gz 588dc1cfbe88711eee8429efc0595ed380c444b695503c5c30ea43313ccc81d9 4615 tgt_1.0.0-1.debian.tar.gz db3bbcfea7fc42357269b58e1396982df8950ffd101997f6790b5ef5d600fbcc 193328 tgt_1.0.0-1_amd64.deb Files: f3860e3484cb61ccf193a44e474d3f86 1103 net optional tgt_1.0.0-1.dsc c83f05eda1e49f20cb714ea2a44eef2e 303689 net optional tgt_1.0.0.orig.tar.gz 19708573a0e276fad0d2a46747f611e4 4615 net optional tgt_1.0.0-1.debian.tar.gz d2b2002678e48bac91d40af7f2f704f8 193328 net optional tgt_1.0.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkszjMcACgkQ6n7So0GVSSBxfACghxOMzGUk8OjGYEDc/d4TsIUN tMMAn1lNFjRmQ0Ov0fAEenL/HuOtWtg1 =QZHe -END PGP SIGNATURE- ---End Message---
Bug#562205: linux-image-2.6.32-trunk-orion5x: Not more mtd device = impossible to flash new kernel
On 24/12/2009 16:14, Martin Michlmayr wrote: * Eric Valetteeric.vale...@free.fr [2009-12-24 00:11]: Yes it is on a DNS 323. But how will this be fixed? Is it possible to recreate the mtd devices after having flashed a kernel without proper in kernel support? Or will you find a way to upload the drivers via correct modules and recreate the needed devices manually? It will be fixed in the next kernel upload. Most people don't run kernels from unstable so it will be fixed before the package moves to testing. If you run a stable from unstable, you have to expect breakage from time to time. So you expect people to kill their machine to test for debian maintainers right? If nobody tests, you will not find the bug before it enters testing... Why don't you test on your own before uploading? We are not like on a PC where yo can always find a cdrom and a iso image to recover. If loading the module doesn't work, I see two possibilities to recover your machine: - maybe you can use kexec to execute a good kernel and then write it to flash. What is the correct procedure and what kernel is supposed to work? - use the serial console (as documented on my web page). So you advice people to do soldering and buying hardware parts. I'm rather disappointed by the lack of testing that has been done on this kernel. At least give some direction to fix the problem (kexec, correct kernel, ...) -- eric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Uploading kernel packages to unstable
On Wed, 2009-12-23 at 21:19 -0700, dann frazier wrote: On Thu, Dec 24, 2009 at 03:44:54AM +, Ben Hutchings wrote: I would like to upload linux-2.6 tomorrow, fixing the build failure on ia64 and a couple of security bugs. There should be no new binary packages. Any objections? (Dan, do you have vserver ready to add?) Yes, I do. I'll go ahead and commit it. If you do want to avoid new binary packages, feel free to revert before uploading. I'm now uploading with vserver included. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Bug#562205: linux-image-2.6.32-trunk-orion5x: Not more mtd device = impossible to flash new kernel
On 24/12/2009 16:47, Eric Valette wrote: If loading the module doesn't work, I see two possibilities to recover your machine: - maybe you can use kexec to execute a good kernel and then write it to flash. What is the correct procedure and what kernel is supposed to work? kexec -l /boot/vmlinuz-2.6.31-1-orion5x --append='root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none' --initrd=/boot/initrd.img-2.6.31-1-orion5x Unsupported machine type: armv5tel So I guess the kexec path is nearly dead or? -- eric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-2.6_2.6.32-3.diff.gz linux-2.6_2.6.32-3.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:26:47, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534964: marked as done (Please enable CONFIG_CGROUP_MEM_RES_CTLR)
Your message dated Fri, 25 Dec 2009 01:14:15 +0900 with message-id 200912241614.nbogefwl081...@www489.sakura.ne.jp and subject line Re: Bug#534964: Please enable CONFIG_CGROUP_MEM_RES_CTLR has caused the Debian Bug report #534964, regarding Please enable CONFIG_CGROUP_MEM_RES_CTLR to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 534964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.30-1 Hello, Please enable CONFIG_CGROUP_MEM_RES_CTLR option. Libvirt (LXC container driver) and lxc use this option. --- debian/config/config.orig 2009-06-28 14:45:12.0 +0900 +++ debian/config/config2009-06-28 14:45:31.988045531 +0900 @@ -2842,7 +2842,8 @@ CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y -# CONFIG_RESOURCE_COUNTERS is not set +CONFIG_RESOURCE_COUNTERS=y +CONFIG_CGROUP_MEM_RES_CTLR=y # CONFIG_SYSFS_DEPRECATED_V2 is not set CONFIG_RELAY=y CONFIG_UTS_NS=y Regards, -- Yoshito Komatsu ykoma...@akaumigame.org ---End Message--- ---BeginMessage--- On Mon, Jun 29, 2009 at 12:04:27AM +0900, Yoshito Komatsu wrote: Please enable CONFIG_CGROUP_MEM_RES_CTLR option. The documentation describes a large amount of overhead for this option. Please show why this does not produce serious tradeoffs for generic usage. Memcg's performance fix seems to be included in 2.6.33 and I close this bug once. New LXC HOW-TO https://lists.linux-foundation.org/pipermail/containers/2009-October/021616.html Thanks, -- Yoshito Komatsu ykoma...@akaumigame.org ---End Message---
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #535006 (http://bugs.debian.org/535006) # * http://bugzilla.kernel.org/show_bug.cgi?id=13648 # * remote status changed: (?) - NEW usertags 535006 + status-NEW Bug#535006: nfs-kernel-server: errors in dmesg There were no usertags set. Usertags are now: status-NEW. # remote status report for #535006 (http://bugs.debian.org/535006) # * http://bugzilla.kernel.org/show_bug.cgi?id=13648 # * remote status changed: (?) - NEW usertags 535006 + status-NEW Bug#535006: nfs-kernel-server: errors in dmesg Usertags were: status-NEW. Usertags are now: status-NEW. # remote status report for #535006 (http://bugs.debian.org/535006) # * http://bugzilla.kernel.org/show_bug.cgi?id=13648 # * remote status changed: (?) - NEW usertags 535006 + status-NEW Bug#535006: nfs-kernel-server: errors in dmesg Usertags were: status-NEW. Usertags are now: status-NEW. # remote status report for #541677 (http://bugs.debian.org/541677) # * http://bugzilla.kernel.org/show_bug.cgi?id=14101 # * remote status changed: NEEDINFO - REJECTED # * remote resolution changed: (?) - DOCUMENTED # * closed upstream tags 541677 + fixed-upstream Bug #541677 [linux-2.6] linux-image-2.6.30-1-amd64: sched_clock_cpu warning, then oops, then panic Added tag(s) fixed-upstream. usertags 541677 - status-NEEDINFO Bug#541677: linux-image-2.6.30-1-amd64: sched_clock_cpu warning, then oops, then panic Usertags were: status-NEEDINFO. Usertags are now: . usertags 541677 + status-REJECTED resolution-DOCUMENTED Bug#541677: linux-image-2.6.30-1-amd64: sched_clock_cpu warning, then oops, then panic There were no usertags set. Usertags are now: resolution-DOCUMENTED status-REJECTED. # remote status report for #561589 (http://bugs.debian.org/561589) # * http://bugzilla.kernel.org/show_bug.cgi?id=12577 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - CODE-FIX usertags 561589 + status-RESOLVED resolution-CODE-FIX Bug#561589: [Bug 12577] DualPoint TouchPad at isa0060/serio1/input0 lost sync There were no usertags set. Usertags are now: resolution-CODE-FIX status-RESOLVED. 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
Processed: tagging 552299
Processing commands for cont...@bugs.debian.org: tags 552299 moreinfo Bug #552299 [linux-image-2.6.26-2-686] forcedeth: nVidia MCP55 ethernet and forcedeth module - fails to connect Added tag(s) moreinfo. 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
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #535006 (http://bugs.debian.org/535006) # * http://bugzilla.kernel.org/show_bug.cgi?id=13648 # * remote status changed: (?) - NEW usertags 535006 + status-NEW # remote status report for #535006 (http://bugs.debian.org/535006) # * http://bugzilla.kernel.org/show_bug.cgi?id=13648 # * remote status changed: (?) - NEW usertags 535006 + status-NEW # remote status report for #535006 (http://bugs.debian.org/535006) # * http://bugzilla.kernel.org/show_bug.cgi?id=13648 # * remote status changed: (?) - NEW usertags 535006 + status-NEW # remote status report for #541677 (http://bugs.debian.org/541677) # * http://bugzilla.kernel.org/show_bug.cgi?id=14101 # * remote status changed: NEEDINFO - REJECTED # * remote resolution changed: (?) - DOCUMENTED # * closed upstream tags 541677 + fixed-upstream usertags 541677 - status-NEEDINFO usertags 541677 + status-REJECTED resolution-DOCUMENTED # remote status report for #561589 (http://bugs.debian.org/561589) # * http://bugzilla.kernel.org/show_bug.cgi?id=12577 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - CODE-FIX usertags 561589 + status-RESOLVED resolution-CODE-FIX thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562205: linux-image-2.6.32-trunk-orion5x: Not more mtd device = impossible to flash new kernel
On 24/12/2009 16:14, Martin Michlmayr wrote: - use the serial console (as documented on my web page). Just in case as I do not want to make a full reinstall. I have in /boot initrd.img-2.6.31-1-orion5x and vmlinuz-2.6.31-1-orion5x that works as it flashed the .32-1. How can I recreate correct uboot image from this? Reading flash-kernel, I can probably rewrite it to skip the mtd check but I would rather be sure that this will be understood by uboot rather using kermit and uboot command rather than writing it directly to mtd devices as it is done via a live system. -- eric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6_2.6.32-3_multi.changes
linux-2.6_2.6.32-3_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-3.dsc linux-2.6_2.6.32-3.diff.gz linux-support-2.6.32-trunk_2.6.32-3_all.deb linux-patch-debian-2.6.32_2.6.32-3_all.deb firmware-linux-free_2.6.32-3_all.deb linux-source-2.6.32_2.6.32-3_all.deb linux-doc-2.6.32_2.6.32-3_all.deb linux-manual-2.6.32_2.6.32-3_all.deb linux-headers-2.6.32-trunk-486_2.6.32-3_i386.deb linux-image-2.6.32-trunk-486_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-3_i386.deb linux-image-2.6.32-trunk-686_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-3_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-3_i386.deb linux-image-2.6.32-trunk-amd64_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-3_i386.deb linux-libc-dev_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-3_i386.deb linux-image-2.6.32-trunk-vserver-686_2.6.32-3_i386.deb linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-3_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-3_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562486: linux-2.6: please enable tomoyo
Package: linux-2.6 Severity: wishlist Hi, it would be nice to have tomoyo enabled, userspace tools are in the archive already. thanks, filippo -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561880: marked as done (inotify/hppa: Not assigning sequential ids as expected)
Your message dated Thu, 24 Dec 2009 13:19:41 -0800
with message-id 20091224211941.ga16...@jade.home
and subject line Re: Bug#561880: linux-image-2.6-parisc64: inotify_add_watch
does not give a unique watch descriptor
has caused the Debian Bug report #561880,
regarding inotify/hppa: Not assigning sequential ids as expected
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
561880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6-parisc64
Severity: important
Blocks: 558981
The attatched minimal test case shows these results:
on my i386 machine, it correctly gives two different numbers:
$ gcc test.c; ./a.out
First: 1
Second: 2
however on paer.debian.org (hppa):
$ gcc test.c; ./a.out
First: 1
Second: 1
Based on the manpage of inotify_add_watch, it sounds like the correct
behavior is to have different numbers. It seems that the author of
inotify-tools also interpreted it that way.
This bug is causing my package's tests to fail, which causes it to FTBFS:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558981
Cheers,
Ryan
--
_
Ryan Niebur
ryanrya...@gmail.com
#include sys/inotify.h
#include stdio.h
int main()
{
int fd, wd;
fd = inotify_init ();
wd = inotify_add_watch (fd,
test.c,
IN_OPEN | IN_CLOSE);
printf(First: %d\n, wd);
inotify_rm_watch(fd, wd);
wd = inotify_add_watch (fd,
a.out,
IN_OPEN | IN_CLOSE);
printf(Second: %d\n, wd);
inotify_rm_watch(fd, wd);
}
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
On Mon, Dec 21, 2009 at 01:02:14AM +, Ben Hutchings wrote:
On Sun, 2009-12-20 at 16:35 -0800, Ryan Niebur wrote:
Hi Ben,
thanks for the response.
On Mon, Dec 21, 2009 at 12:12:44AM +, Ben Hutchings wrote:
On Sun, 2009-12-20 at 15:46 -0800, Ryan Niebur wrote:
Package: linux-image-2.6-parisc64
Yes but which version?
the version that paer is running (apparently
linux-image-2.6.32-trunk-parisc64 2.6.32-1)
Wow, already? OK.
and whatever version peri is running.
Severity: important
Blocks: 558981
The attatched minimal test case shows these results:
on my i386 machine, it correctly gives two different numbers:
$ gcc test.c; ./a.out
First: 1
Second: 2
however on paer.debian.org (hppa):
$ gcc test.c; ./a.out
First: 1
Second: 1
Based on the manpage of inotify_add_watch, it sounds like the correct
behavior is to have different numbers. It seems that the author of
inotify-tools also interpreted it that way.
This bug is causing my package's tests to fail, which causes it to
FTBFS:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558981
I think the test case is broken; why should two watches that don't exist
at the same time have unique ids? You might as well test:
the manpage makes it sound like it should be unique for each
filename. and if the test case is broken, then I don't understand why
this only fails on hppa.
I'm saying there is no guarantee in the manual page about what order
watch ids will be assigned in, and that it is unreasonable to expect
unique to mean unique among all watches that ever existed for this
handle. The assignments could vary depending on the architecture or on
the phase of the moon. The test cases should not make any assertions
about them, other than that any two watches *that exist at the same
time* have different ids.
However, it does look like the implementation is intended to assign
sequential ids, so this may indicate a bug in the implementation. But
it shouldn't block you.
okay, thanks, I'll correct the tests.
Cheers,
Ryan
--
_
Ryan Niebur
ryanrya...@gmail.com
signature.asc
Description: Digital signature
---End Message---
