Bug#522415: firmware-nonfree: please create a mother package for all firmware
On Samstag, 4. April 2009, maximilian attems wrote: > and here comes a fsf purist :P wanting better usability. > as i told you this will be anyway the tendancy > as all newer firmware will land in f-linux. eparse. hint: te bts aint sms, ya ca use pr0per inglish. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#509199: installation-reports: Intel 82574L network card isn't supported by installation kernel (i486) nor i686 kernel
Processing commands for cont...@bugs.debian.org: > reassign 509199 linux-2.6 Bug#509199: installation-reports: Intel 82574L network card isn't supported by installation kernel (i486) nor i686 kernel Bug reassigned from package `installation-reports' to `linux-2.6'. > 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 521016
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26etch2 > tags 521016 + pending Bug#521016: [mips] llseek regression introduced by syscall wrapping There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522415: firmware-nonfree: please create a mother package for all firmware
On Sat, Apr 04, 2009 at 01:00:27AM +0200, Holger Levsen wrote: > installed but not the firmware), so a depends would work. > > I'd prefer a all-firmwarez meta-package though, which _recommends_ all binary > packages build from the firmware-nonfree source package :-) > > (recommends are installed per default in lenny.) and here comes a fsf purist :P wanting better usability. as i told you this will be anyway the tendancy as all newer firmware will land in f-linux. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522472: eeepc-laptop: report brightness control events via the input layer
Package: linux-2.6 Version: 2.6.29-1 Severity: wishlist Tags: patch The attached patch maps the brightness control events to one of two keys, either KEY_BRIGHTNESSDOWN or KEY_BRIGHTNESSUP, as needed. Some mapping has to be done due to the fact that the BIOS reports them as + ; the selection is done according to the sign of the change in brightness (if this is 0, no keypress is reported). This was prompted by the following posting to debian-eeepc-devel: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2009-April/002001.html and has been sent upstream: http://patchwork.kernel.org/patch/16215/ -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output *more* particulate pollutants. BUFFER AGAINST GLOBAL WARMING. I cut down trees, I eat my lunch, I go to the lavatory. 2.6.29-eee-brightness-key.patch Description: Binary data
Bug#522415: firmware-nonfree: please create a mother package for all firmware
Hi, On Samstag, 4. April 2009, maximilian attems wrote: > no this is not possible due to license differences. > ipwX needs a click through, but there will be soon unification > as bnx2 will land in firmware-linux and so on.. huh? you need to accept the ipwX licence anyway (else the package will be installed but not the firmware), so a depends would work. I'd prefer a all-firmwarez meta-package though, which _recommends_ all binary packages build from the firmware-nonfree source package :-) (recommends are installed per default in lenny.) regards, Holger signature.asc Description: This is a digitally signed message part.
Bug#522415: firmware-nonfree: please create a mother package for all firmware
On Fri, Apr 03, 2009 at 04:49:49PM +0200, Xavier Bestel wrote: > Package: firmware-nonfree > Severity: wishlist > > > Hi, > > would it be possible to create an umbrella package which would depend on all > firmware-* packages, so every new firmware package would be installed > automatically ? no this is not possible due to license differences. ipwX needs a click through, but there will be soon unification as bnx2 will land in firmware-linux and so on.. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522452: linux-image-2.6.26-1-xen-686: reboot/shutdown of domU never finish, stay in status shutdown ---s--
Package: linux-image-2.6.26-1-xen-686 Version: 2.6.26-13lenny2 Severity: normal http://www.nabble.com/xm-shutdown-doesn%27t-work-on-debian-lenny-td22308315.html http://www.nabble.com/Domain-status-after-shutdown-command:s---td15565767.html http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1326 This is a problem if "dom0-cpus" in /etc/xen/xend-config.sxp is not set to 0. So if the dom0 number of cpu is limited (I had it set to 1). After setting dom0-cpus back to 0 and dom0 reboot (xend restart was not enough) the reboots/shutdows of domU-s worked fine again. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (700, 'stable'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (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 Versions of packages linux-image-2.6.26-1-xen-686 depends on: ii initramfs-tools 0.93.1 tools for generating an initramfs pn linux-modules-2.6.26-1-xen-68 (no description available) Versions of packages linux-image-2.6.26-1-xen-686 recommends: ii libc6-xen 2.9-4 GNU C Library: Shared libraries [X Versions of packages linux-image-2.6.26-1-xen-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 (no description available) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509733:
I can confirm this bug as well on Intel x3100 graphics. Also, there seems to be some confusion here between xorg and xserver-xorg-core: The problematic package is xserver-xorg-core. Lenny: 1.4.2-10 Squeeze: 1.4.2-11 Sid: 1.4.2-11 Experimental: 1.5.99.902-1 xorg is the one with the 7.x versions.
Bug#522421: Upgrading initramfs-tools makes unable to connect using dhcp
Package: initramfs-tools Version: 0.93.1 Severity: normal I'm just upgrade this package from v0.93 and when I restart the system, the connection was missing; I'm sure that this is the problem because this is the only package that I upgrade. I'm trying to fix it but noithing works. Thanks. -- Package-specific info: -- /proc/cmdline root=/dev/hda1 ro quiet -- /proc/filesystems ext3 -- lsmod Module Size Used by ppdev 6468 0 lp 8164 0 ipv6 235300 24 loop 12748 0 snd_via82xx20664 1 gameport 10700 1 snd_via82xx snd_via82xx_modem 10120 0 snd_ac97_codec 88484 2 snd_via82xx,snd_via82xx_modem ac97_bus1728 1 snd_ac97_codec snd_pcm_oss32800 0 snd_mixer_oss 12320 1 snd_pcm_oss snd_pcm62596 4 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss snd_mpu401_uart 6368 1 snd_via82xx snd_seq_dummy 2660 0 snd_seq_oss24992 0 snd_seq_midi5728 0 snd_rawmidi18496 2 snd_mpu401_uart,snd_seq_midi snd_seq_midi_event 6432 2 snd_seq_oss,snd_seq_midi snd_seq41456 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event pcspkr 2432 0 snd_timer 17800 2 snd_pcm,snd_seq snd_seq_device 6380 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd45604 14 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device snd_page_alloc 7816 3 snd_via82xx,snd_via82xx_modem,snd_pcm i2c_viapro 6836 0 soundcore 6368 1 snd i2c_core 19828 1 i2c_viapro via686a11948 0 button 6096 0 parport_pc 22500 1 parport30988 3 ppdev,lp,parport_pc shpchp 25528 0 pci_hotplug23460 1 shpchp via_agp 7744 1 agpgart28776 1 via_agp evdev 8000 3 ext3 105512 3 jbd39444 1 ext3 mbcache 7108 1 ext3 usbhid 35904 0 hid33184 1 usbhid ff_memless 4392 1 usbhid ide_cd_mod 27652 0 cdrom 30176 1 ide_cd_mod ide_disk 10496 6 uhci_hcd 18672 0 ide_pci_generic 3908 0 [permanent] dmfe 16536 0 ata_generic 4676 0 libata140384 1 ata_generic scsi_mod 129356 1 libata dock8304 1 libata floppy 47716 0 tulip 44064 0 ehci_hcd 28428 0 usbcore 118160 4 usbhid,uhci_hcd,ehci_hcd via82cxxx 6948 0 [permanent] ide_core 96168 4 ide_cd_mod,ide_disk,ide_pci_generic,via82cxxx thermal15228 0 processor 32576 2 thermal fan 4164 0 thermal_sys10856 3 thermal,processor,fan -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=es_MX.UTF-8, LC_CTYPE=es_MX.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: di cpio 2.9.90-3 GNU cpio -- a program to manage ar ii findutils 4.4.0-3utilities for finding files--find, di klibc-utils 1.5.15-1 small utilities built with klibc f di module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo di udev 0.125-7/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: di busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- no debconf information *** /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp *** /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
Bug#522415: firmware-nonfree: please create a mother package for all firmware
Package: firmware-nonfree Severity: wishlist Hi, would it be possible to create an umbrella package which would depend on all firmware-* packages, so every new firmware package would be installed automatically ? Thanks, Xav -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
Processed: tagging 521691
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26etch2 > tags 521691 + pending Bug#521691: fails to reach network a short time after boot There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
On Thursday 02 April 2009 01:57:43 am Tom Rathborne wrote: > On Wed, Apr 01, 2009 at 05:39:59PM -0400, Tom Rathborne wrote: > > I commented out the junk in fs/dcache.c and the kernel compiled. :) > > > > I will send you the sysrq-D info next time I get the bug! > > Oops ... now OpenVZ won't start! > > magrathea:~# vzctl start 101 > Starting VE ... > MOUNTING > VE is mounted > Error: kernel does not support user resources. Please, rebuild with > CONFIG_USER_RESOURCE=y VE start failed > UNMOUNTING > VE is unmounted > > I do not see a "CONFIG_USER_RESOURCE is not set" in .config, > and if I add 'CONFIG_USER_RESOURCE=y' then 'make menuconfig' reports: > .config:3953:warning: trying to assign nonexistent symbol USER_RESOURCE > > I did find a couple of references to it: > ./net/ipv4/tcp.c:#ifdef CONFIG_USER_RESOURCE > ./net/ipv4/tcp_timer.c:#ifdef CONFIG_USER_RESOURCE > but it looks like those should be CONFIG_BEANCOUNTERS. > > So ... what do I do next? It seems like this bug only happens with > OpenVZ processes, but OpenVZ will not start without > CONFIG_BEANCOUNTERS! Ok, switching off CONFIG_BEANCOUNTERS was a bad idea ;( I will prepare patch to fix beancounter warning in one-two days and send to you. Thanks a lot of for your efforts! Vitaliy Gusev -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#495673: linux-image-2.6.26-1-686: confirm same bug for 2.6.26-1-686 and 2.6.29-1-686
Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal d -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 18:29:31 UTC 2009 ** Command line: root=/dev/sda1 ro quiet ** Tainted: P W (513) ** Kernel log: [53138.664383] FAT: Directory bread(block 97642) failed [53138.664389] FAT: Directory bread(block 97643) failed [53138.664396] FAT: Directory bread(block 97644) failed [53138.664401] FAT: Directory bread(block 97645) failed [53138.664406] FAT: Directory bread(block 97646) failed [53138.664411] FAT: Directory bread(block 97647) failed [53138.664416] FAT: Directory bread(block 97648) failed [53138.664421] FAT: Directory bread(block 97649) failed [53138.664426] FAT: Directory bread(block 97650) failed [53138.664430] FAT: Directory bread(block 97651) failed [53138.664435] FAT: Directory bread(block 97652) failed [53138.664440] FAT: Directory bread(block 97653) failed [53138.664445] FAT: Directory bread(block 97654) failed [53138.664449] FAT: Directory bread(block 97655) failed [53138.664454] FAT: Directory bread(block 97656) failed [53138.664459] FAT: Directory bread(block 97657) failed [53138.664464] FAT: Directory bread(block 97658) failed [53138.664471] FAT: Directory bread(block 97659) failed [53138.664477] FAT: Directory bread(block 97660) failed [53138.664484] FAT: Directory bread(block 97661) failed [53138.664490] FAT: Directory bread(block 97662) failed [53138.664497] FAT: Directory bread(block 97663) failed [53138.664503] FAT: Directory bread(block 97664) failed [53138.664509] FAT: Directory bread(block 97665) failed [53138.664516] FAT: Directory bread(block 97666) failed [53138.664522] FAT: Directory bread(block 97667) failed [53138.664528] FAT: Directory bread(block 97668) failed [53138.664535] FAT: Directory bread(block 97669) failed [53138.664642] FAT: Directory bread(block 97638) failed [53138.664648] FAT: Directory bread(block 97639) failed [53138.664652] FAT: Directory bread(block 97640) failed [53138.664657] FAT: Directory bread(block 97641) failed [53138.664662] FAT: Directory bread(block 97642) failed [53138.664667] FAT: Directory bread(block 97643) failed [53138.664672] FAT: Directory bread(block 97644) failed [53138.664677] FAT: Directory bread(block 97645) failed [53138.664682] FAT: Directory bread(block 97646) failed [53138.664687] FAT: Directory bread(block 97647) failed [53138.664694] FAT: Directory bread(block 97648) failed [53138.664700] FAT: Directory bread(block 97649) failed [53138.664706] FAT: Directory bread(block 97650) failed [53138.664713] FAT: Directory bread(block 97651) failed [53138.664719] FAT: Directory bread(block 97652) failed [53138.664726] FAT: Directory bread(block 97653) failed [53138.664732] FAT: Directory bread(block 97654) failed [53138.664738] FAT: Directory bread(block 97655) failed [53138.664745] FAT: Directory bread(block 97656) failed [53138.664751] FAT: Directory bread(block 97657) failed [53138.664758] FAT: Directory bread(block 97658) failed [53138.664764] FAT: Directory bread(block 97659) failed [53138.664771] FAT: Directory bread(block 97660) failed [53138.664777] FAT: Directory bread(block 97661) failed [53138.664783] FAT: Directory bread(block 97662) failed [53138.664788] FAT: Directory bread(block 97663) failed [53138.664793] FAT: Directory bread(block 97664) failed [53138.664798] FAT: Directory bread(block 97665) failed [53138.664802] FAT: Directory bread(block 97666) failed [53138.664807] FAT: Directory bread(block 97667) failed [53138.664812] FAT: Directory bread(block 97668) failed [53138.664817] FAT: Directory bread(block 97669) failed [53138.664836] EXT3-fs error (device sdc7): ext3_find_entry: reading directory #2 offset 0 [53138.665076] Buffer I/O error on device sdc7, logical block 0 [53138.665083] lost page write due to I/O error on sdc7 [53138.665123] EXT3-fs error (device sdc3): ext3_find_entry: reading directory #2 offset 0 [53138.665146] Buffer I/O error on device sdc3, logical block 0 [53138.665149] lost page write due to I/O error on sdc3 [53138.665163] EXT3-fs error (device sdc3): ext3_find_entry: reading directory #2 offset 0 [53138.665179] Buffer I/O error on device sdc3, logical block 0 [53138.665181] lost page write due to I/O error on sdc3 [53138.665199] EXT3-fs error (device sdc2): ext3_find_entry: reading directory #2 offset 0 [53138.665214] Buffer I/O error on device sdc2, logical block 0 [53138.665220] lost page write due to I/O error on sdc2 [53138.665250] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #2 offset 0 [53138.665263] Buffer I/O error on device sdc1, logical block 0 [53138.665265] lost page write due to I/O error on sdc1 [53318.019614] usb 1-6: USB disconnect, address 6 [54326.893765] usb 1-6: new high speed USB device using ehci_hcd and address 7 [54327.036639] usb 1-6: configuration #1 chosen from 2 choices [54327.037640] scsi9 : SCSI emu
Bug#509613: linux-image-2.6-openvz-amd64: kernel oops on net device reconfiguration
Hi, I was having problems with linux-image-2.6.26-1-openvz-amd64 that seem very similar to this. If I tried starting/rebooting any VE after creating any NAT iptables rules, I got a NULL pointer dereference followed by OOPSes just as the VE's network interfaces came up. I've attached the relevant kernel output in case anyone should experience the same. I tried the patch from Lars Hanke, as well as several others from the OpenVZ git repository, all to no avail. I very much appreciated the instructions for patching/rebuilding a Debian-packaged kernel though. However, I tried lenny-proposed-updates as suggested by Dann Frazier and installed linux-image-2.6.26-2-openvz-amd64 and I'm very pleased to say my problem has been fixed. Many thanks to all involved! Regards, -- Steven Chamberlain ste...@pyro.eu.org [0.00] Linux version 2.6.26-1-openvz-amd64 (Debian 2.6.26-13lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Mar 13 19:02:24 UTC 2009 [0.00] Command line: root=/dev/hda7 ro [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f400 (usable) [0.00] BIOS-e820: 0009f400 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1fff (usable) [0.00] BIOS-e820: 1fff - 1fff3000 (ACPI NVS) [0.00] BIOS-e820: 1fff3000 - 2000 (ACPI data) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fec0 - 0001 (reserved) [0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used [0.00] Entering add_active_range(0, 256, 131056) 1 entries of 3200 used [0.00] max_pfn_mapped = 1048576 [0.00] init_memory_mapping [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7880, 0014 (r0 Nvidia) [0.00] ACPI: RSDT 1FFF3040, 0034 (r1 Nvidia AWRDACPI 42302E31 AWRD 0) [0.00] ACPI: FACP 1FFF30C0, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD 0) [0.00] ACPI: DSDT 1FFF3180, 6360 (r1 NVIDIA AWRDACPI 1000 MSFT 10E) [0.00] ACPI: FACS 1FFF, 0040 [0.00] ACPI: SRAT 1FFF9600, 00A0 (r1 AMDHAMMER 1 AMD 1) [0.00] ACPI: MCFG 1FFF9700, 003C (r1 Nvidia AWRDACPI 42302E31 AWRD 0) [0.00] ACPI: APIC 1FFF9540, 007C (r1 Nvidia AWRDACPI 42302E31 AWRD 0) [0.00] SRAT: PXM 0 -> APIC 0 -> Node 0 [0.00] SRAT: PXM 0 -> APIC 1 -> Node 0 [0.00] SRAT: Node 0 PXM 0 0-a [0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used [0.00] SRAT: Node 0 PXM 0 10-2000 [0.00] Entering add_active_range(0, 256, 131056) 1 entries of 3200 used [0.00] NUMA: Allocated memnodemap from b000 - b480 [0.00] NUMA: Using 20 for the hash shift. [0.00] Bootmem setup node 0 -1fff [0.00] NODE_DATA [b480 - 0001047f] [0.00] bootmap [00011000 - 00014fff] pages 4 [0.00] early res: 0 [0-fff] BIOS data page [0.00] early res: 1 [6000-7fff] TRAMPOLINE [0.00] early res: 2 [20-66a817] TEXT DATA BSS [0.00] early res: 3 [1fd9c000-1ffdfe3e] RAMDISK [0.00] early res: 4 [9f400-f] BIOS reserved [0.00] early res: 5 [8000-afff] PGTABLE [0.00] early res: 6 [b000-b47f] MEMNODEMAP [0.00] [e200-e27f] PMD -> [81000120-8100019f] on node 0 [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 131056 [0.00] On node 0 totalpages: 130959 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 1234 pages reserved [0.00] DMA zone: 2701 pages, LIFO batch:0 [0.00] DMA32 zone: 1984 pages used for memmap [0.00] DMA32 zone: 124976 pages, LIFO batch:31 [0.00] Normal zone: 0 pages used for memmap [0.00] Movable zone: 0 pages used for memmap [0.00] Nvidia board detected. Ignoring ACPI timer override. [0.00] If you got timer trouble try acpi_use_timer_override [0.00] ACPI: PM-Timer IO Port: 0x4008 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [
Processed: tagging 521535
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26etch2 > tags 521535 + pending Bug#521535: [PATCH] [linux-modules-extra-2.6] Please add batmand-gateway modules Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 514611
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26etch2 > tags 514611 + pending Bug#514611: [linux-modules-extra-2.6] Please add batman-adv modules Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 508541 redhat-cluster-source Bug#508541: redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB Bug reassigned from package `redhat-cluster-modules-2.6.26-1-686-bigmem' to `redhat-cluster-source'. > reassign 498207 tp-smapi-source Bug#498207: does not load on 2.6.26-1-openvz-amd64 Bug reassigned from package `tp-smapi-modules-2.6.26-1-openvz-amd64' to `tp-smapi-source'. > reassign 507725 squashfs-source Bug#507725: squashfs-modules-2.6-686: please enable SquashFS 1.0 support Bug reassigned from package `squashfs-modules-2.6-686' to `squashfs-source'. > 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
