Bug#566726: config
# # Automatically generated make config: don't edit # Linux kernel version: 2.6.32-20100124 # Sun Jan 24 19:22:46 2010 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_OUTPUT_FORMAT="elf32-i386" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y CONFIG_X86_32_LAZY_GS=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_TREE_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=32 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # CONFIG_GROUP_SCHED is not set # CONFIG_CGROUPS is not set # CONFIG_SYSFS_DEPRECATED_V2 is not set CONFIG_RELAY=y CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set # CONFIG_IPC_NS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_NET_NS is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_EVENT_PROFILE=y # CONFIG_PERF_COUNTERS is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y CONFIG_COMPAT_BRK=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_OPROFILE=y # CONFIG_OPROFILE_IBS is not set # CONFIG_OPROFILE_EVENT_MULTIPLEX is not set CONFIG_HAVE_OPROFILE=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_DMA_API_DEBUG=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set # CONFIG_SLOW_WORK is not set CONFIG_HAVE_GENERIC_DMA_COHERENT=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 # CONFIG_MODULES is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_LBDAF=y # CONFIG_BLK_DEV_BSG is not set # CONFIG_BLK_DEV_INTEGRITY is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_FREEZER=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y # CONFIG_SPARSE_IRQ is not set CONFIG_X86_MPPARSE=y # CONFIG_X86_BIGSMP is not set CONFIG_X86_EXTENDED_PLATFORM=y # CONFIG_X86_ELAN is not set # CONFIG_X86_MRST is not set # CONFIG_X86_RDC321X is not set # CONFIG_X86_32_NON_STANDARD is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=
"25 de janeiro - Aniversário de São Paulo"
Caso não visualize esse email adequadamente acesse este link http://cjf.mkt9.com/ver_mensagem.php?id=H|506|21446|124602795261937700 Se você não deseja mais receber nossos e-mails, cancele sua inscrição através do link http://cjf.mkt9.com/admin/sair.php?id=21446|506|0&uid=124602795261937700
Bug#566727: linux-image-2.6.32 missing memory cgroup controllers
On Sun, 24 Jan 2010, Brian Kroth wrote: > Package: linux-image-2.6.32-trunk-amd64 > Version: 2.6.32-5 > Severity: wishlist > > Support for memory cgroups controllers are not included in the new > 2.6.32 kernel. This would be nice say for putting limits on a how much > memory a group of VMs can use. > > I believe the following two options need to be enabled in the kernel: > CONFIG_RESOURCE_COUNTERS > CONFIG_CGROUP_MEM_RES_CTLR > > Here's some more info: > > # dpkg -l | grep linux-image-2.6.32 > ii linux-image-2.6.32-trunk-amd64 2.6.32-5 Linux 2.6.32 for 64-bit > PCs > > # uname -a > Linux oberon 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 > GNU/Linux > > # cat /proc/cgroups > #subsys_namehierarchy num_cgroups enabled > cpuset 0 1 1 > ns 0 1 1 > cpu 11 8 1 > cpuacct 11 8 1 > devices 11 8 1 > freezer 0 1 1 > net_cls 0 1 1 > > # cat /etc/debian_version > squeeze/sid > > See Also: > http://berrange.com/personal/diary/2009/12/using-cgroups-with-libvirt-and-lxckvm > > Let me know if you need any more info. > > Thanks, > Brian see ongoing discussions about lxc flavour, you might want to jump in. current conclusion is that we might enable aboves, but disable it on boot with modprobe.conf to not get overheads for the generic linux images. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
On Mon, 25 Jan 2010, Luk Claes wrote: > Ben Hutchings wrote: > > There have been 2 upstream stable updates and one more (2.6.32.6) is due > > early this week. As usual, these include some security fixes. > > Therefore I propose to upload with the changes from 2.6.32.6 once that's > > released. > > > > (Still no stable ABI, sorry.) > > If the ABI changed the package name will change, right? Will it become > trunk2? no, trunk has no ABI guarantee. you can bet that each upload has a different one. once libata is used and the configs all set we can go for stable numbering. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
On Mon, Jan 25, 2010 at 11:48:04AM +0100, maximilian attems wrote: > On Mon, 25 Jan 2010, Luk Claes wrote: > > Ben Hutchings wrote: > > > There have been 2 upstream stable updates and one more (2.6.32.6) is due > > > early this week. As usual, these include some security fixes. > > > Therefore I propose to upload with the changes from 2.6.32.6 once that's > > > released. > > > > > > (Still no stable ABI, sorry.) > > If the ABI changed the package name will change, right? Will it become > > trunk2? > no, trunk has no ABI guarantee. > you can bet that each upload has a different one. > once libata is used and the configs all set we can go for stable > numbering. Sorry, but your package is in testing now. Please bump the ABI number in whatever why you want, but you should. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Processed: Re: Bug#566356: mount ntfs external hard disk on usb port for read only
Processing commands for cont...@bugs.debian.org: > reassign 566356 linux-2.6 Bug #566356 [mount] mount ntfs external hard disk on usb port for read only Bug reassigned from package 'mount' to 'linux-2.6'. Bug No longer marked as found in versions util-linux/2.16.2-0. > -- 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#566356: mount ntfs external hard disk on usb port for read only
reassign 566356 linux-2.6 -- On Sat, Jan 23, 2010 at 12:03:14PM +0530, gnath wrote: > using external hard disk formatted with ntfs on usb port gives > read only mode. Can use or play with files on EHD without write/create. > > use additional flashdisk/pendrive with vfat on another usb port with rw > permission The nearly certain situation here is that CONFIG_NTFS_RW is not set in the kernel config, resulting in the kernel doing read-only mode when mounting an NTFS filesystem, regardless of where it comes from. lamont -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 561552
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 561552 + pending Bug #561552 [linux-2.6] linux-image-2.6.32-trunk-amd64: [agp/drm] agp + dri unavailable with testing X.org 1.6.5 Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken
> "JY" == Jie Yang writes: JY> Anders Boström wrote: >> Cc: b...@decadent.org.uk; net...@vger.kernel.org; >> 565...@bugs.debian.org; Xiong Huang >> Subject: Re: Bug#565404: linux-image-2.6.26-2-amd64: atl1e: >> TSO is broken >> One strange observation is that I can only reproduce this >> problem when transmitting data from a NFS-server using TCP >> with Atheros AR8121/AR8113/AR8114. >> >> I've tried to reproduce the problem using test-programs, like >> nttcp and netpipe, without any success. One observation is >> that the test-programs *only* generates 1500 bytes >> IP-packets. When the NFS-server sends data, a sequence of >> 1500 bytes IP-packets are generated, ending with a shorter >> packet. And this last packet in the sequence has 1500 in the >> IP-header length field, but is shorter. >> JY> following is my test cese, JY> a nfs server server with ar8131chip, device id 1063. export /tmp/ dir as the nfs share directory, JY> the client, mount the server_ip:/tmp to local dir /mnt/nfs, ust a python script to write and read data on the JY> /mnt/nfs/testnfs.log. it works fine. OK, the device-ID in our NFS-server is 1026, rev. b0. So it is possible that the problem is specific to that chip/version. JY> Can you give me some advice on how to reproduce this bug?? The only suggestion I have is to try to find a board with a 1026-chip on it. My test-case is just copy of a 1 Gbyte file from the NFS-server to /dev/null , after making sure that the file isn't cached on the client by reading huge amounts of other data. / Anders -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566727: linux-image-2.6.32 missing memory cgroup controllers
maximilian attems 2010-01-25 11:51: > see ongoing discussions about lxc flavour, you might want to jump in. Sure, where can I find it? > current conclusion is that we might enable aboves, > but disable it on boot with modprobe.conf to not get overheads > for the generic linux images. That would be great. Thanks, Brian signature.asc Description: Digital signature
Bug#566727: linux-image-2.6.32 missing memory cgroup controllers
Hello, > Sure, where can I find it? http://lists.debian.org/debian-kernel/2010/01/msg00577.html Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions| http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
Philipp Kern wrote: > On Mon, Jan 25, 2010 at 11:48:04AM +0100, maximilian attems wrote: >> On Mon, 25 Jan 2010, Luk Claes wrote: >>> Ben Hutchings wrote: There have been 2 upstream stable updates and one more (2.6.32.6) is due early this week. As usual, these include some security fixes. Therefore I propose to upload with the changes from 2.6.32.6 once that's released. (Still no stable ABI, sorry.) >>> If the ABI changed the package name will change, right? Will it become >>> trunk2? >> no, trunk has no ABI guarantee. >> you can bet that each upload has a different one. >> once libata is used and the configs all set we can go for stable >> numbering. > > Sorry, but your package is in testing now. Please bump the ABI number in > whatever why you want, but you should. I guess this means that the next version is no candidate for the release unless it gets a stable ABI (versioning) and should block the kernel from migrating for the time being? Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: > I guess this means that the next version is no candidate for the release > unless it gets a stable ABI (versioning) and should block the kernel > from migrating for the time being? > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, so I'm not sure what difference blocking the next one makes. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534880: SLES11 Xen patches
Hello, Debian Lenny linux-image-2.6.26-2-xen uses an early snapshot of Novell SLES11 patches, so I guess someone would have to go through the SLES11 kernel-xen patches and see what has changed.. I believe SLES11 Xen patches have numerous bugfixes compared to what is in Lenny. ftp://ftp.suse.com/pub/projects/kernel/kotd/SLE11_BRANCH/src/ http://www.gitorious.org/opensuse/kernel-source/commits/SLE11_BRANCH -- Pasi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
Julien Cristau wrote: > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: > >> I guess this means that the next version is no candidate for the release >> unless it gets a stable ABI (versioning) and should block the kernel >> from migrating for the time being? >> > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, > so I'm not sure what difference blocking the next one makes. As always, what reaches testing is a candidate for stable when no better version comes along. Cheers Luk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
* Julien Cristau (jcris...@debian.org) [100125 19:27]: > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: > > > I guess this means that the next version is no candidate for the release > > unless it gets a stable ABI (versioning) and should block the kernel > > from migrating for the time being? > > > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, > so I'm not sure what difference blocking the next one makes. That our testing users don't have to life with strange error messages they wouldn't get if the abi would be bumped properly. Cheers, Andi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: lxc linux image flavour
Marco d'Itri wrote: > On Jan 24, maximilian attems wrote: [] >> On the negative side it doesn't have yet checkpointing support >> and not all net/ has netns support yet. > It's not just that, AFAIK there is no match for many of the > user_beancounters features (especially the accounting part) and e.g. > lack of the equivalent of "vzctl enter" is a critical issue for my > applications. Accounting is done in cgroups. Not as flexible as in openvz, but it works. As of `vzctl enter', there's something very similar, but it requires to have getty (or similar) running on ttyN in guest. Probably not what you want. > While I am happy to see better support for lxc in Debian, it does not > look like an openvz replacement yet. It doesn't, indeed. Both has their own bad and good sides. The main "good" about lxc is that it's in the standard kernel, and kernel components are ready (maybe modulo some features like freezing/migration). Openvz, linux-vserver, other things - all require quite intrusive patches, which complicating support tasks alot. /mjt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
On Mon, Jan 25, 2010 at 08:02:31PM +0100, Andreas Barth wrote: > * Julien Cristau (jcris...@debian.org) [100125 19:27]: > > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: > > > > > I guess this means that the next version is no candidate for the release > > > unless it gets a stable ABI (versioning) and should block the kernel > > > from migrating for the time being? > > > > > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, > > so I'm not sure what difference blocking the next one makes. > > That our testing users don't have to life with strange error messages > they wouldn't get if the abi would be bumped properly. OK, maybe we should start numbering ABIs with this next version. Ben. -- Ben Hutchings Every program is either trivial or else contains at least one bug -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
On Mon, Jan 25, 2010 at 20:02:31 +0100, Andreas Barth wrote: > * Julien Cristau (jcris...@debian.org) [100125 19:27]: > > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: > > > > > I guess this means that the next version is no candidate for the release > > > unless it gets a stable ABI (versioning) and should block the kernel > > > from migrating for the time being? > > > > > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, > > so I'm not sure what difference blocking the next one makes. > > That our testing users don't have to life with strange error messages > they wouldn't get if the abi would be bumped properly. > Yeah, that sounds oh so much more important than getting proper testing for the kernel we're going to release with. Or than getting (security and otherwise) bugs fixed quickly. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Uploading linux-2.6
* Ben Hutchings (b...@decadent.org.uk) [100125 20:14]: > On Mon, Jan 25, 2010 at 08:02:31PM +0100, Andreas Barth wrote: > > * Julien Cristau (jcris...@debian.org) [100125 19:27]: > > > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote: > > > > > > > I guess this means that the next version is no candidate for the release > > > > unless it gets a stable ABI (versioning) and should block the kernel > > > > from migrating for the time being? > > > > > > > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either, > > > so I'm not sure what difference blocking the next one makes. > > > > That our testing users don't have to life with strange error messages > > they wouldn't get if the abi would be bumped properly. > > OK, maybe we should start numbering ABIs with this next version. I'd appreciate that very much. Cheers, Andi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: lxc linux image flavour
On Mon, Jan 25, 2010 at 12:26:42AM +, Marco d'Itri wrote: > Actually I meant "vzctl exec" so this is not even close: I need to > change the context of a running process. Hu? "vzctl exec" does a fork and an exec. Please enlighten me where the support you want is actually implemented. Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, "Elaan of Troyius", stardate 4372.5 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551312: Unitech barcode fix from linux-next git
Package: linux-2.6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Linux-next commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 contains a fix for this bug. I'd really appreciate it if you'd cherry-pick this for 2.6.32 (which I understand squeeze is going to release with). The diff is dead simple: it just removes the blacklist lines. http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=4bb950806f10bc3e249dd34375b4a4d6bfc0 - -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (130, 'unstable'), (120, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkteFekACgkQ+z+IwlXqWf5EogCfZoScCCiKA2+JGIzwIwX6fQwv /D8An3jC1MYG9sYlo7kiqvR01ebpgerQ =8cpE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: lxc linux image flavour
On Sun, 24 Jan 2010, Suno Ano wrote: > Bastian> Please describe the _kernel_ improvements over the normal > Bastian> images. Most of it is already enabled in the default images > Bastian> and does not warrant for an extra image. > > As you can see from http://sunoano.pastebin.com/m4b5380dc , line 29, > Cgroup memory controller is not. This setting is mandatory if you want > to control the available memory per containers and the like. IMO most > folks would want that, if just to make sure their local sandbox does not > go wild for some reason, thus eating up all memory. if we want to ennable it for the default image, we need a benchmark test of obvious stuff like fork()/exit to check that it didn't degrade. if results are in the noise of the relevant benchmark we can shipp it indeed in linux-2.6 without the need of a special featureset. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: lxc linux image flavour
On Sun, Jan 24, 2010 at 06:19:02PM +0100, Suno Ano wrote: > As you can see from http://sunoano.pastebin.com/m4b5380dc , line 29, > Cgroup memory controller is not. This setting is mandatory if you want > to control the available memory per containers and the like. It is not mandantory for the system. > Bastian> The description reads like it is possible to enable/disable > Bastian> the overhead on boot time. Please elaborate. > Nope, it has to be enabled at build-time. http://lxc.teegra.net Please show this on the source. Bastian -- Yes, it is written. Good shall always destroy evil. -- Sirah the Yang, "The Omega Glory", stardate unknown -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551312: [PATCH] HID: remove TENX iBuddy from blacklist
This was commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 upstream.
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
From 4bb950806f10bc3e249dd34375b4a4d6bfc0 Mon Sep 17 00:00:00 2001
From: Jiri Kosina
Date: Wed, 23 Dec 2009 14:13:46 +0100
Subject: [PATCH] HID: remove TENX iBuddy from blacklist
There were multiple reports which indicate that vendor messed up horribly
and the same VID/PID combination is used for completely different devices,
some of them requiring the blacklist entry and other not.
Remove the blacklist entry for this combination of VID/PID completely, and let
the user decide and unbind the driver via sysfs eventually, if needed. Proper
fix would be fixing the vendor.
References:
http://lkml.org/lkml/2009/2/10/434
http://bugzilla.kernel.org/show_bug.cgi?id=13411
Signed-off-by: Jiri Kosina
---
drivers/hid/hid-core.c |2 --
drivers/hid/hid-ids.h |4
2 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 056384c..116a346 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1662,8 +1662,6 @@ static const struct hid_device_id hid_ignore_list[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_PANJIT, 0x0004) },
{ HID_USB_DEVICE(USB_VENDOR_ID_PHILIPS, USB_DEVICE_ID_PHILIPS_IEEE802154_DONGLE) },
{ HID_USB_DEVICE(USB_VENDOR_ID_POWERCOM, USB_DEVICE_ID_POWERCOM_UPS) },
- { HID_USB_DEVICE(USB_VENDOR_ID_TENX, USB_DEVICE_ID_TENX_IBUDDY1) },
- { HID_USB_DEVICE(USB_VENDOR_ID_TENX, USB_DEVICE_ID_TENX_IBUDDY2) },
{ HID_USB_DEVICE(USB_VENDOR_ID_VERNIER, USB_DEVICE_ID_VERNIER_LABPRO) },
{ HID_USB_DEVICE(USB_VENDOR_ID_VERNIER, USB_DEVICE_ID_VERNIER_GOTEMP) },
{ HID_USB_DEVICE(USB_VENDOR_ID_VERNIER, USB_DEVICE_ID_VERNIER_SKIP) },
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index b009fd6..064c09a 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -406,10 +406,6 @@
#define USB_VENDOR_ID_SUNPLUS 0x04fc
#define USB_DEVICE_ID_SUNPLUS_WDESKTOP 0x05d8
-#define USB_VENDOR_ID_TENX 0x1130
-#define USB_DEVICE_ID_TENX_IBUDDY1 0x0001
-#define USB_DEVICE_ID_TENX_IBUDDY2 0x0002
-
#define USB_VENDOR_ID_THRUSTMASTER 0x044f
#define USB_VENDOR_ID_TOPMAX 0x0663
--
1.6.6
signature.asc
Description: This is a digitally signed message part
Re: lxc linux image flavour
On Jan 25, Bastian Blank wrote: > On Mon, Jan 25, 2010 at 12:26:42AM +, Marco d'Itri wrote: > > Actually I meant "vzctl exec" so this is not even close: I need to > > change the context of a running process. > Hu? "vzctl exec" does a fork and an exec. Please enlighten me where the > support you want is actually implemented. It does, but it does not have to. :-) It is not documented anywhere and as usual the Parallels developers are less than helpful, but you can use setluid(2) to associate the caller with a beancounter and then an IOCTL on /dev/vzctl to move it in a container. I used this in libpam_vz, which with some careful planning allows multiple contexts to share a lot of stuff (with a decent unionfs even most of the file system). http://ftp.linux.it/pub/People/md/libpam-vz/ -- ciao, Marco signature.asc Description: Digital signature
Processed: tagging 566547
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 566547 + pending Bug #566547 [linux-2.6] linux-image-2.6.32-trunk-amd64: Segmentation fault during halt Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#565404: linux-image-2.6.26-2-amd64: atl1e: TSO is broken
Anders Boström wrote: >> IP-header length field, but is shorter. > >> > JY> following is my test cese, > > JY> a nfs server server with ar8131chip, device id 1063. > export /tmp/ dir as the nfs share directory, JY> the client, > mount the server_ip:/tmp to local dir /mnt/nfs, ust a python > script to write and read data on the JY> > /mnt/nfs/testnfs.log. it works fine. > > OK, the device-ID in our NFS-server is 1026, rev. b0. So it > is possible that the problem is specific to that chip/version. oops, its my mistake in writing, my case is 1026 device ID > > JY> Can you give me some advice on how to reproduce this bug?? > > The only suggestion I have is to try to find a board with a > 1026-chip on it. > > My test-case is just copy of a 1 Gbyte file from the > NFS-server to /dev/null , after making sure that the file > isn't cached on the client by reading huge amounts of other data. > just to check, if the kernel version is 2.6.26-2 ?? Best wishes jie -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 508877 to src:linux-2.6, reassign 536099 to src:linux-2.6, forcibly merging 536099 508877
Processing commands for cont...@bugs.debian.org: > reassign 508877 src:linux-2.6 Bug #508877 [linux-image-2.6.26-1-amd64] linux-image-2.6.26-1-amd64: invalid opcode: [1] SMP Bug reassigned from package 'linux-image-2.6.26-1-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.26-11. > reassign 536099 src:linux-2.6 Bug #536099 [linux-image-2.6.26-2-amd64] ntfs: kernel BUG at fs/ntfs/inode.c:339! invalid opcode: [1] SMP Bug reassigned from package 'linux-image-2.6.26-2-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.26-17. > forcemerge 536099 508877 Bug#536099: ntfs: kernel BUG at fs/ntfs/inode.c:339! invalid opcode: [1] SMP Bug#508877: linux-image-2.6.26-1-amd64: invalid opcode: [1] SMP Forcibly Merged 508877 536099. > 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: found 536099 in 2.6.26-17
Processing commands for cont...@bugs.debian.org: > found 536099 2.6.26-17 Bug #536099 [src:linux-2.6] ntfs: kernel BUG at fs/ntfs/inode.c:339! invalid opcode: [1] SMP Bug #508877 [src:linux-2.6] linux-image-2.6.26-1-amd64: invalid opcode: [1] SMP Bug Marked as found in versions linux-2.6/2.6.26-17. Bug Marked as found in versions linux-2.6/2.6.26-17. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
On Sun, 2010-01-24 at 17:51 -0800, Mike Castle wrote: > ii debconf 1.5.28 > Debian configuration management system > ii debconf-i18n 1.5.28 > full internationalization support for debcon > > > Configured to use dialog > > ii dialog > 1.1-20080819-1 Displays user-friendly dialog boxes from > she It appears that the 'dialog' front-end to debconf actually uses 'whiptail' if it is installed, which it is on the systems I tried. After I removed whiptail, debconf used the dialog program and although I did not see this exact behaviour I did see some odd formatting, which I was able to correct. This should be fixed in the next upload. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Processed: tagging 566539
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 566539 + pending Bug #566539 [linux-2.6] linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566522: i'm say i'm noob :(
On Sun, 2010-01-24 at 23:52 +0100, Piotr Skólski wrote: > After thrid line (pathing using debian script) > > chmod +x debian/bin/gencontrol.py > debian/bin/gencontrol.py > Traceback (most recent call last): > File "debian/bin/gencontrol.py", line 331, in > Gencontrol()() > File "debian/bin/gencontrol.py", line 14, in __init__ > self.process_changelog() > File "debian/bin/gencontrol.py", line 305, in process_changelog > (distribution, version)) > RuntimeError: Can't upload to unstable with a version of 2.6.32-5a~test > make: *** [debian/control-real] Error 1 > > I don't know what i can do now, i'm go sleep then. > Good Night :* Oops, that's a bug in the test-patches script. Please continue with these commands which will work around that: rm -r linux-2.6-2.6.32 dpkg-source -x linux-2.6_2.6.32-5.dsc cd linux-2.6-2.6.32 sed -i '1s/unstable/UNRELEASED/' debian/changelog bash debian/bin/test-patches -f 486 -s none ../0001-3c503-Fix-IRQ-probing.patch Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
I do not have whiptail installed (saw no sense in having both dialog and whiptail installed). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
