Bug#605090: Updated patch
On Tue, Jan 18, 2011 at 06:32:50PM +0100, Yves-Alexis Perez wrote: I've started working on 2.6.37 since Brad Sprengler recently released the grsecurity patch for that kernel. Is there VCS or is this just a code drop without information about changes? I was not even able to find older patches. Who does code reviews without that information? The patch includes several modifications to selinux and random other parts. Why are they not merged? Please show that they have been submitted at least. Initial packaging for linux-grsec-base is at http://git.debian.org/?p=collab-maint/linux-grsec-base.git;a=summary if needed. Why is this not part of the patch below? Currently the patch only includes informations for i386 and amd64. Please state your intentions about other architectures. + [ Yves-Alexis Perez ] + * Add a grsecurity featureset. *nitpick* the patch calls it Grsecurity. Index: debian/config/featureset-grsec/config === --- debian/config/featureset-grsec/config (revision 0) +++ debian/config/featureset-grsec/config (revision 0) @@ -0,0 +1,152 @@ +CONFIG_DEBUG_STRICT_USER_COPY_CHECKS=y Please show why this should not be enabled globaly. +CONFIG_DEBUG_RODATA=y x86 specific and default on. Bastian -- It would be illogical to kill without reason. -- Spock, Journey to Babel, stardate 3842.4 -- 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/20110126080308.gb27...@wavehammer.waldi.eu.org
Bug#607879: System hangs up with mmap.c:873!
This *is* explained on the page I pointed you at. Sorry for being a *blind* newbie... After building the linux-base package I was able to install the patched linux- image package. The system I am trying to build with live-build also needs the linux-headers package because of some dkms packages. Unfortunately, there is again a dependency problem: # dpkg -i linux-headers-2.6.32-5-686_2.6.32-30a~test_i386.deb (Reading database ... 166017 files and directories currently installed.) Preparing to replace linux-headers-2.6.32-5-686 2.6.32-30a~test (using linux- headers-2.6.32-5-686_2.6.32-30a~test_i386.deb) ... Unpacking replacement linux-headers-2.6.32-5-686 ... dpkg: dependency problems prevent configuration of linux-headers-2.6.32-5-686: linux-headers-2.6.32-5-686 depends on linux-headers-2.6.32-5-common (= 2.6.32-30a~test); however: Version of linux-headers-2.6.32-5-common on system is 2.6.32-30. dpkg: error processing linux-headers-2.6.32-5-686 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-2.6.32-5-686 Unfortunately, I could not find any information about this issue on the page you pointet me at. Fortunately, after some trial and error, I successfully built a linux-headers-2.6.32-5-common_2.6.32-30a~test package with the following two commands: export UPSTREAMVERSION=2.6.32-5 fakeroot make -f debian/rules.real binary-arch-featureset Is this the right way? Best regards Ronny -- 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/201101261104.10803.ronny.stand...@gmx.net
Bug#599615: linux-image-2.6.32-5-xen-686: kernel BUG at /buildd/buildd-linux-2.6_2.6.32-24-i386-JPvGSk/linux-2.6-2.6.32/debi an/build/source_i386_xen/drivers/md/md.c: 6192!
I think that I have the same problem with 2.6.32-5-xen-amd64 (2.6.32-30). When I try to reboot the server: Jan 26 10:48:18 cc kernel: [43467.083492] [ cut here ] Jan 26 10:48:18 cc kernel: [43467.083526] kernel BUG at /build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linu x-2.6-2.6.32/debian/build/source_amd64_xen/drivers/md/md.c:6195! Jan 26 10:48:18 cc kernel: [43467.083584] invalid opcode: [#1] SMP Jan 26 10:48:18 cc kernel: [43467.083618] last sysfs file: /sys/hypervisor/version/minor Jan 26 10:48:18 cc kernel: [43467.083647] CPU 6 Jan 26 10:48:18 cc kernel: [43467.083673] Modules linked in: ext2 act_police cls_flow cls_fw cls_u32 sch_htb sch_hfsc sch_ingress sch_sfq xt_time xt_connlimit xt_realm iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_tproxy_core xt_tcpmss xt_pkttype xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY iptable_nat nf_nat iptable_mangle nfnetlink ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ip Jan 26 10:48:18 cc kernel: v4 xt_state nf_conntrack xt_physdev ip6table_filter ip6_tables xen_evtchn xenfs ccm ecb sha512_generic xfrm_user ah6 ah4 esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4 xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm_ipcomp xfrm6_tunnel tunnel6 acpi_cpufreq cpufreq_userspace iptable_filter cpufreq_stats ip_tables cpufreq_powersave openvswitch_mod rng_core x_tables cpufreq_conservative deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic cbc aes_x86_64 aes_generic xcbc rmd160 sha256_generic sha1_generic hmac crypto_null af_key ext3 jbd mbcache loop snd_pcm snd_timer snd soundcore snd_page_alloc i2c_i801 pcspkr psmouse i2c_core serio_raw evdev xfs exportfs dm_mod processor thermal_sys acpi_processor raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 md_mod sata_nv sata_sil sata_via 3w_9xxx 3w_ sd_mod crc_t10dif ahci r81 Jan 26 10:48:18 cc kernel: 69 uhci_hcd mii libata ehci_hcd scsi_mod usbcore nls_base [last unloaded: scsi_transport_iscsi] Jan 26 10:48:18 cc kernel: [43467.085090] Pid: 2993, comm: xenstored Tainted: P 2.6.32-5-xen-amd64 #1 MS-7522 Jan 26 10:48:18 cc kernel: [43467.085139] RIP: e030:[a00c1e08] [a00c1e08] md_write_start+0x1d/0x15c [md_mod] Jan 26 10:48:18 cc kernel: [43467.085200] RSP: e02b:8801c5ce98f8 EFLAGS: 00010246 Jan 26 10:48:18 cc kernel: [43467.085229] RAX: 0001 RBX: 8801ecea3400 RCX: 12c0675c Jan 26 10:48:18 cc kernel: [43467.085261] RDX: RSI: 88014a4a8180 RDI: 8801ecea3400 Jan 26 10:48:18 cc kernel: [43467.085294] RBP: 8801ecea3400 R08: R09: 00ff Jan 26 10:48:18 cc kernel: [43467.085326] R10: 8100ecf2 R11: 003f R12: 00ff Jan 26 10:48:18 cc kernel: [43467.085359] R13: 8801ec7511a0 R14: 88014a4a8180 R15: 8801ec799240 Jan 26 10:48:18 cc kernel: [43467.085394] FS: 7f91f689a700() GS:88000abbf000() knlGS: Jan 26 10:48:18 cc kernel: [43467.085444] CS: e033 DS: ES: CR0: 8005003b Jan 26 10:48:18 cc kernel: [43467.085473] CR2: 00618d50 CR3: 0001c5cb2000 CR4: 2660 Jan 26 10:48:18 cc kernel: [43467.085506] DR0: DR1: DR2: Jan 26 10:48:18 cc kernel: [43467.085539] DR3: DR6: 0ff0 DR7: 0400 Jan 26 10:48:18 cc kernel: [43467.085571] Process xenstored (pid: 2993, threadinfo 8801c5ce8000, task 8801c8233880) Jan 26 10:48:18 cc kernel: [43467.085621] Stack: Jan 26 10:48:18 cc kernel: [43467.085643] 0006 8801c8233b78 000100a4a915 Jan 26 10:48:18 cc kernel: [43467.085686] 0 0040 fffe 0021 8801ecea3400 Jan 26 10:48:18 cc kernel: [43467.085751] 0 00ff a00db12c Jan 26 10:48:18 cc kernel: [43467.085834] Call Trace: Jan 26 10:48:18 cc kernel: [43467.085863] [a00db12c] ? make_request+0x2e/0x7aa [raid1] Jan 26 10:48:18 cc kernel: [43467.085897] [812c0cf8] ? unix_poll+0x0/0x8d Jan 26 10:48:18 cc kernel: [43467.085928] [8100e63d] ? xen_force_evtchn_callback+0x9/0xa Jan 26
Bug#605090: Updated patch
First, thanks for your comments. I'm replying to both mails at once. On mer., 2011-01-26 at 08:25 +0100, Bastian Blank wrote: On Tue, Jan 18, 2011 at 06:32:50PM +0100, Yves-Alexis Perez wrote: Index: debian/config/i386/grsec/defines === --- debian/config/i386/grsec/defines(revision 0) +++ debian/config/i386/grsec/defines(revision 0) @@ -0,0 +1,9 @@ +[base] +flavours: + 686 No new non-pae image. Ok. In fact it's a good idea anyway because having PAE on means we have NX which makes it easier for Grsecurity. + amd64 Why? Because people using 64bit kernels on i386 might still want a grsec variant. +[grsec] +flavours: + i386 + amd64 What is this? I didn't really find the syntax for the “defines” files so I looked at the others ones and xen has that [xen] section but maybe it's only used internall by xen feature set. Will remove and check it doesn't break anything. Index: debian/config/i386/defines === --- debian/config/i386/defines (revision 16824) +++ debian/config/i386/defines (working copy) @@ -3,6 +3,7 @@ openvz vserver xen + grsec This was a sorted list. Fixed. Index: debian/config/featureset-grsec/config === --- debian/config/featureset-grsec/config (revision 0) +++ debian/config/featureset-grsec/config (revision 0) @@ -0,0 +1,152 @@ +# Disable XEN for UDEREF support +CONFIG_XEN=n Nope. Disabling core stuff needs more information. As the comment says, this is because UDEREF conflicts with XEN. The help for the Kconfig option says: config PAX_MEMORY_UDEREF bool Prevent invalid userland pointer dereference depends on X86 !UML_X86 !XEN select PAX_PER_CPU_PGD if X86_64 help By saying Y here the kernel will be prevented from dereferencing userland pointers in contexts where the kernel expects only kernel pointers. This is both a useful runtime debugging feature and a security measure that prevents exploiting a class of kernel bugs. The tradeoff is that some virtualization solutions may experience a huge slowdown and therefore you should not enable this feature for kernels meant to run in such environments. Whether a given VM solution is affected or not is best determined by simply trying it out, the performance impact will be obvious right on boot as this mechanism engages from very early on. A good rule of thumb is that VMs running on CPUs without hardware virtualization support (i.e., the majority of IA-32 CPUs) will likely experience the slowdown. I was assuming people wanting a grsec kernel would prefer having UDEREF than XEN, but we might as well use the more conservative approach and keep XEN enabled (and UDEREF disabled) and wait for feedback from users. If bugreports are reported asking for UDEREF we can still revisite that later. Index: debian/config/featureset-grsec/defines === --- debian/config/featureset-grsec/defines (revision 0) +++ debian/config/featureset-grsec/defines (revision 0) @@ -0,0 +1,8 @@ +[description] +part-short-grsec: Grsecurity and PaX protection This is already too long. What would be a good limit? Would “Grsecurity protection” work? As I understand it it's added to the short description of the various packages for that featureset so the total should be kept under 80 chars. Looking at other featureset we could go for “Grsecurity support” but I'm not sure it makes much sense. +[image] +depends: linux-grsec-base,, paxctl Why is paxctl necessary? Also syntax error. PAX security features will enforce W^X mmap() (RANDMMAP), which some application don't like (for example browsers with JIT javascript engines). If one wants to use those application she has to disable it on the executable itself, which is done using paxctl (which can be used to enable/disable other protection type at runtime). It's not strictly a dependency so it can be demoted to Recommends (or moved to linux-grsec-base only) if you prefer. Syntax error is fixed. --- debian/config/amd64/grsec/config(revision 0) +++ debian/config/amd64/grsec/config(revision 0) @@ -0,0 +1,5 @@ +# +# PaX +# +CONFIG_PAX_PER_CPU_PGD=y +CONFIG_TASK_SIZE_MAX_SHIFT=42 Remove, no real settings here. What do you mean by “real” settings? PAX_PER_CPU_PGD is enabled by UDEREF and TASK_SIZE_MAX_SHIFT is set to 42 on amd64 because of how it has been implemented without segmentation. More info can be found there: http://grsecurity.net/pipermail/grsecurity/2010-April/001024.html Due to the performances concerns, I've decided to keep UDEREF and
Bug#506540: /usr/sbin/update-initramfs: update-initramfs miss symlink Possible missing firmware tigon
Package: initramfs-tools Severity: normal File: /usr/sbin/update-initramfs miss symlink to the original tigon firmware installed during the debian installation added by usb stick resolve trouble by adding the missing link -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 8.5M Jan 26 12:40 /boot/initrd.img-2.6.32-5-686 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=965c0c14-ce59-45cb-98b1-f4125f965fe8 ro quiet -- resume RESUME=UUID=0a07b1a4-7a8d-448c-a56c-e61f524bca23 -- /proc/filesystems ext4 -- lsmod Module Size Used by md_mod 67345 0 loop9765 0 snd_intel8x0 19595 0 snd_ac97_codec 79148 1 snd_intel8x0 nouveau 314892 1 ttm33386 1 nouveau ac97_bus 710 1 snd_ac97_codec drm_kms_helper 18309 1 nouveau snd_pcm47226 2 snd_intel8x0,snd_ac97_codec drm 112088 3 nouveau,ttm,drm_kms_helper i2c_algo_bit3497 1 nouveau snd_timer 12258 1 snd_pcm usbhid 28008 0 snd34375 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer parport_pc 15799 0 soundcore 3450 1 snd psmouse44657 0 evdev 5609 4 rng_core2178 0 hid50893 1 usbhid i2c_i8016462 0 parport22554 1 parport_pc snd_page_alloc 5045 2 snd_intel8x0,snd_pcm i2c_core 12696 5 nouveau,drm_kms_helper,drm,i2c_algo_bit,i2c_i801 shpchp 21220 0 pci_hotplug18065 1 shpchp pcspkr 1207 0 serio_raw 2916 0 processor 26327 0 button 3598 1 nouveau ext4 257803 4 mbcache 3762 1 ext4 jbd2 56155 1 ext4 crc16 1027 1 ext4 sg 15968 0 sr_mod 10770 0 cdrom 26487 1 sr_mod sd_mod 25977 7 crc_t10dif 1012 1 sd_mod ata_generic 2067 0 tg388273 0 ata_piix 17736 5 thermal 9206 0 libata115753 2 ata_generic,ata_piix uhci_hcd 16057 0 floppy 40923 0 libphy 11638 1 tg3 thermal_sys 9378 2 processor,thermal ehci_hcd 27851 0 scsi_mod 101429 4 sg,sr_mod,sd_mod,libata usbcore98453 5 usbhid,uhci_hcd,ehci_hcd nls_base4541 1 usbcore -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : unused devices: none -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup keymap klibc mdadm thermal udev -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-4 GNU cpio -- a program to manage ar ii findutils 4.4.2-1+b1 utilities for finding files--find, ii klibc-utils 1.5.20-1 small utilities built with klibc f ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii udev 164-3 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.17.1-8 Tiny utilities for small and embed Versions of packages initramfs-tools suggests: ii bash-completion 1:1.2-3programmable completion for the ba -- no debconf information -- 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/20110126132512.16642.29669.report...@sparkle.etincelles.homelinux.org
Bug#506540: /usr/sbin/update-initramfs: update-initramfs miss symlink Possible missing firmware tigon
tags 506540 moreinfo stop On Wed, Jan 26, 2011 at 02:25:12PM +0100, tekmans wrote: Package: initramfs-tools Severity: normal File: /usr/sbin/update-initramfs miss symlink to the original tigon firmware installed during the debian installation added by usb stick resolve trouble by adding the missing link could you be more concrete and tell how this symlink /lib/firmware looks like, aka ls -l of it, thanks. -- 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/20110126133527.ga21...@vostochny.stro.at
Processed: Re: Bug#506540: /usr/sbin/update-initramfs: update-initramfs miss symlink Possible missing firmware tigon
Processing commands for cont...@bugs.debian.org: tags 506540 moreinfo Bug #506540 [initramfs-tools] initramfs-tools - Always dereferences symlinks Added tag(s) moreinfo. stop Stopping processing here. Please contact me if you need assistance. -- 506540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506540 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.12960489821734.transcr...@bugs.debian.org
Bug#605090: Updated patch
On Wed, Jan 26, 2011 at 01:29:14PM +0100, Yves-Alexis Perez wrote: On mer., 2011-01-26 at 08:25 +0100, Bastian Blank wrote: On Tue, Jan 18, 2011 at 06:32:50PM +0100, Yves-Alexis Perez wrote: +# Disable XEN for UDEREF support As the comment says, this is because UDEREF conflicts with XEN. The help for the Kconfig option says: And why does it conflict with XEN? The documentation does not provide any specific pointers. From my view it is easy, it have to run on my test environments that features heavy virtualization of different types. +part-short-grsec: Grsecurity and PaX protection This is already too long. What would be a good limit? Would “Grsecurity protection” work? Should be okay. +depends: linux-grsec-base,, paxctl Why is paxctl necessary? Also syntax error. It's not strictly a dependency so it can be demoted to Recommends (or moved to linux-grsec-base only) if you prefer. Okay. +++ debian/config/amd64/grsec/config (revision 0) Remove, no real settings here. What do you mean by “real” settings? PAX_PER_CPU_PGD is enabled by UDEREF and TASK_SIZE_MAX_SHIFT is set to 42 on amd64 because of how it has been implemented without segmentation. Real settings can be modified by the user, this two can't. On mer., 2011-01-26 at 09:03 +0100, Bastian Blank wrote: On Tue, Jan 18, 2011 at 06:32:50PM +0100, Yves-Alexis Perez wrote: I've started working on 2.6.37 since Brad Sprengler recently released the grsecurity patch for that kernel. Is there VCS or is this just a code drop without information about changes? I was not even able to find older patches. Who does code reviews without that information? No there is no VCS unfortunately. You will need a git repository in the future. So please start with it. The patch includes several modifications to selinux and random other parts. Why are they not merged? Please show that they have been submitted at least. As I already pointed out on the first mail, Brad Sprengler has already said he wasn't interested in upstreaming stuff. What Brad wants or don't want is irrelevant here. While the patch policy for the main kernel is rather strict, other featuresets can incorporate more changes. However this is no free ticket to push anything into it. There is an upstreaming effort for some specific bits (like the https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#Upstream Hardening I already gave). Please explain how this is related to Grsecurity. The selinux-specific part are related to the effort to make function pointers structures read-only (or do you have other specific parts in mind?). Everything that is not directly related to Grsecurity or PaX. And there is a lot. http://git.debian.org/?p=collab-maint/linux-grsec-base.git;a=summary if needed. Why is this not part of the patch below? The grsec.conf was attached to the initial bug report. As there is no easy way to ship an external file in the linux-image, I was told it'd be a better idea to make an external package and that helps because I can do the user creation there and add a README. External _binary_ package, not source package. +CONFIG_DEBUG_STRICT_USER_COPY_CHECKS=y Please show why this should not be enabled globaly. Good point, it should. I'll make a separated bug report. No need for a bug. +CONFIG_DEBUG_RODATA=y Fixed. The current patch even marks it as broken. Bastian -- Beam me up, Scotty, there's no intelligent life down here! -- 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/20110126135443.ga1...@wavehammer.waldi.eu.org
Bug#506540: /usr/sbin/update-initramfs: update-initramfs miss symlink Possible missing firmware tigon
tags 506540 moreinfo stop On Wed, Jan 26, 2011 at 02:25:12PM +0100, tekmans wrote: Package: initramfs-tools Severity: normal File: /usr/sbin/update-initramfs miss symlink to the original tigon firmware installed during the debian installation added by usb stick resolve trouble by adding the missing link could you be more concrete and tell how this symlink /lib/firmware looks like, aka ls -l of it, thanks. I was installing mdadm, sample output below update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3 ls -l /lib/firmware/tigon/ lrwxrwxrwx 1 root root 32 26 janv. 12:40 tg3.bin - /lib/firmware/tigon/tg3_tso5.bin -rwxr-xr-x 1 root root 3884 14 oct. 2009 tg3_tso5.bin lrwxrwxrwx 1 root root 32 26 janv. 12:40 tg3_tso.bin - /lib/firmware/tigon/tg3_tso5.bin Original tigon added during the debian installation was tg3_tso5.bin, and the link were hadded by myself. Followed by apt-get install --reinstall mdadm, and complete without W: Possible missing firmware I hope, it'll be helpful -- 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/ac9badd03d8b1bd566cead9c923f7d0d.squir...@webmail.no-log.org
Bug#506540: /usr/sbin/update-initramfs: update-initramfs miss symlink Possible missing firmware tigon
On Wed, Jan 26, 2011 at 04:23:24PM +0100, ~ tekmans ~ wrote: I was installing mdadm, sample output below update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3 tg3 stipulates it needs all the thre firmware files: MODULE_FIRMWARE(FIRMWARE_TG3); MODULE_FIRMWARE(FIRMWARE_TG3TSO); MODULE_FIRMWARE(FIRMWARE_TG3TSO5); update-initramfs can't know that the last one is enough for this hardware. ls -l /lib/firmware/tigon/ lrwxrwxrwx 1 root root 32 26 janv. 12:40 tg3.bin - /lib/firmware/tigon/tg3_tso5.bin -rwxr-xr-x 1 root root 3884 14 oct. 2009 tg3_tso5.bin lrwxrwxrwx 1 root root 32 26 janv. 12:40 tg3_tso.bin - /lib/firmware/tigon/tg3_tso5.bin so this looks like special tricking, just properly apt-get install firmware-linux-nonfree I hope, it'll be helpful currently I think your box hasn't installed the relevant package and thus is non-standard. I wouldn't see this a bug. So unless convinced otherwise, will close. -- 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/20110126155315.gc21...@vostochny.stro.at
Bug#611126: Failure on boot during initrd script execution
reassign 611126 linux-2.6 stop # linux-2.6 boot panic On Tue, 25 Jan 2011, Pascal BERNARD wrote: Package: initramfs-tools Version: 0.98.7 I have some kernel panic upon boot, or the init script stops and asks for root login. All my partitions are on lvm/md, including / where boot/kernel resides. This is not an initramfs-tools bug as it has long handed over things to init. I am on testing with linux-image-2.6.32-5-amd64 2.6.32-30 at the moment. I have reported this problem on grub-pc (#593648), but I must say that the same grub works with a kernel on a standard partition. I noticed that if I stop grub for a minute (eg by pretending editing an entry before booting), there is no more problem. Is it an issue with data not flushed on disk ? My raid is a soft (linux) raid0. Please find some screen shots attached. Did that box ever work? Is that breakage recent? Please run memcheck on it for at least 24 hours. also please follow up with reportbug to gather the linux-2.6 related info like lspci dmesg and so on.. so on the box: reporbug -N bugnr thank you. -- maks -- 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/20110126170851.gl5...@stro.at
Processed: Re: Bug#611126: Failure on boot during initrd script execution
Processing commands for cont...@bugs.debian.org: reassign 611126 linux-2.6 Bug #611126 [initramfs-tools] Failure on boot during initrd script execution Bug #611127 [initramfs-tools] Boot fails during initrd script execution Bug reassigned from package 'initramfs-tools' to 'linux-2.6'. Bug reassigned from package 'initramfs-tools' to 'linux-2.6'. Bug No longer marked as found in versions initramfs-tools/0.98.7. Bug No longer marked as found in versions initramfs-tools/0.98.7. stop Stopping processing here. Please contact me if you need assistance. -- 611126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611126 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.129606173728724.transcr...@bugs.debian.org
Re: Bug#568088: cdrom: Debian does not boot right after installation
reassign 568088 linux-2.6 2.6.26-21 severity 568088 important tag 568088 moreinfo kthxbye On Mon, Feb 1, 2010 at 22:46:28 +0100, Volodymyr Shcherbyna wrote: Package: cdrom Severity: critical Justification: breaks the whole system After installation of debian 5.0.3 x64 the OS does not boot. If I load kernel with noapic nolapic acpi=off ide=nodma it works. Should you have any questions about my configuration does not hesitate to ask ;) On Tue, Feb 2, 2010 at 12:40:32 +0100, Volodymyr Shcherbyna wrote: I was able to isolate the issue. My system freezes and only acpi=off makes it possible to boot. My system configuration is: Asus P5QL Pro Intel Core 2 Quad 2.5 Ghz I used latest stable netinstaller for 5.0.3 Debian, x64. Does this still occur? If yes, can you provide kernel logs? At which point in the boot does the system hang? Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#568088: cdrom: Debian does not boot right after installation
Processing commands for cont...@bugs.debian.org: reassign 568088 linux-2.6 2.6.26-21 Bug #568088 [cdrom] cdrom: Debian does not boot right after installation Bug reassigned from package 'cdrom' to 'linux-2.6'. Bug #568088 [linux-2.6] cdrom: Debian does not boot right after installation There is no source info for the package 'linux-2.6' at version '2.6.26-21' with architecture '' Unable to make a source version for version '2.6.26-21' Bug Marked as found in versions 2.6.26-21. severity 568088 important Bug #568088 [linux-2.6] cdrom: Debian does not boot right after installation Severity set to 'important' from 'critical' tag 568088 moreinfo Bug #568088 [linux-2.6] cdrom: Debian does not boot right after installation Added tag(s) moreinfo. kthxbye Stopping processing here. Please contact me if you need assistance. -- 568088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568088 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.129606198729985.transcr...@bugs.debian.org
Re: Bug#607368: Please decide how kernel ABI should be managed
On Sun, Dec 19, 2010 at 19:30:58 +0100, Julien BLACHE wrote: I think it would be best if this matter would be decided upon before the release of Squeeze, or not too long after it, so as to avoid further breakages in early kernel updates for Squeeze. We're getting close to the squeeze release. Is the technical committee going to reach a decision on this? Cheers, Julien signature.asc Description: Digital signature
Bug#611126: Yes, this is recent
The box is running for years now. Using grub-pc with the kernel on a lvm/md partition is more recent, but the bug is much more recent. Maybe a month or so. I will configure exim so that I can use reportbug for a full report. Pascal -- 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/1296065001.2831.6.camel@moraes.localdomain
Bug#605090: Updated patch
Hi, On Wed, Jan 26, 2011 at 01:29:14PM +0100, Yves-Alexis Perez wrote: Due to the performances concerns, I've decided to keep UDEREF and KERNEXEC disabled on amd64 for now anyway, so those will disappear (independently of the i386 decision). This doesn't seem like a good idea. The bulk of heavy-duty kernel hardening is with KERNEXEC and UDEREF. If someone is interested in speed, they can choose i386. But if someone wants a hardened kernel and amd64, they should have the option. I'd leave those on for both. -Kees -- Kees Cook@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/20110126180715.gb4...@outflux.net
Possible bug in kernel 2.6.37
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I'm not sure this is neither the right place, nor the right way to introduce my problem, but I've only small kernel knowledge. Please excuse me if I'm wrong. I'm using 2 Debian Squeeze Xen Dom0 servers. Those 2 servers provide PCI passthrough for a network card. The idea is to filter network trafic inside dedicated domU instead of having dom0 directly connected on the network. For my tests, I choose Debian Squeeze with 2.6.37 kernel from experimental. Here are the results: - - Debian Squeeze 32bits + 32bits 2.6.37 kernel: incoming packets larger than 128 bytes are blocked somewhere. - - Debian Squeeze 32bits + 64bits 2.6.37 kernel: everything works fine. - - Debian Squeeze 64bits + 64bits 2.6.37 kernel: everything works fine. My first thought was I discovered a bug in Xen PCI passthrough code. I exchange some mails on xen-devel mailing list about it, mostly with Konrad Rzeszutek Wilk. He asked me to do many tests which did not help to diagnose the problem. Then he suggest me to change memory allocated to domU from 256mb to 512mb. That solved my problem. Now, I don't know exactly what I shall do. Any help will be appreciated, Regards, Jean Baptiste Favre -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1Afb8ACgkQM2eZoKJfKd3Y/QCgtMm2sTTj3VL/0hyPkMoP8my4 2lEAoKy13l/NiQBscuzCNmlgLc4aHfur =HIsl -END PGP SIGNATURE- -- 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/4d407dbf.6040...@jbfavre.org
Bug#605090: Updated patch
On mer., 2011-01-26 at 14:54 +0100, Bastian Blank wrote: On Wed, Jan 26, 2011 at 01:29:14PM +0100, Yves-Alexis Perez wrote: On mer., 2011-01-26 at 08:25 +0100, Bastian Blank wrote: On Tue, Jan 18, 2011 at 06:32:50PM +0100, Yves-Alexis Perez wrote: +# Disable XEN for UDEREF support As the comment says, this is because UDEREF conflicts with XEN. The help for the Kconfig option says: And why does it conflict with XEN? The documentation does not provide any specific pointers. From my view it is easy, it have to run on my test environments that features heavy virtualization of different types. UDEREF and KERNEXEC makes intensive use of segmentation and tune some low level stuff like the linker and thus breaks assumptions on which XEN counts. +++ debian/config/amd64/grsec/config(revision 0) Remove, no real settings here. What do you mean by “real” settings? PAX_PER_CPU_PGD is enabled by UDEREF and TASK_SIZE_MAX_SHIFT is set to 42 on amd64 because of how it has been implemented without segmentation. Real settings can be modified by the user, this two can't. I still don't get it. I had the impression that debian/config/arch/featureset/config role was to override debian/config/featureset-featureset/config with arch-specific config items. On mer., 2011-01-26 at 09:03 +0100, Bastian Blank wrote: On Tue, Jan 18, 2011 at 06:32:50PM +0100, Yves-Alexis Perez wrote: I've started working on 2.6.37 since Brad Sprengler recently released the grsecurity patch for that kernel. Is there VCS or is this just a code drop without information about changes? I was not even able to find older patches. Who does code reviews without that information? No there is no VCS unfortunately. You will need a git repository in the future. So please start with it. I was kind-of waiting for the git linux-2.6 transition. I contacted Ben Hutchings about his linux-2.6 tree on git.debian.org but he told me to rather directly request to join the alioth project and don't wait for the transition to happen. The patch includes several modifications to selinux and random other parts. Why are they not merged? Please show that they have been submitted at least. As I already pointed out on the first mail, Brad Sprengler has already said he wasn't interested in upstreaming stuff. What Brad wants or don't want is irrelevant here. While the patch policy for the main kernel is rather strict, other featuresets can incorporate more changes. However this is no free ticket to push anything into it. There is an upstreaming effort for some specific bits (like the https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#Upstream Hardening I already gave). Please explain how this is related to Grsecurity. Well, as the page explains, this is about upstreaming a lot of kernel and userland protections provided by Grsecurity: NX, ASLR, symbols hiding... The selinux-specific part are related to the effort to make function pointers structures read-only (or do you have other specific parts in mind?). Everything that is not directly related to Grsecurity or PaX. And there is a lot. The patch is only about Grsecurity and PaX protection. But while PaX is mostly about memory protection, Grsecurity has multiple features: * the RBAC system * chroot protection * info leak reduction * arbitrary code execution prevention (both in kernel and in userland) and that means it const-ify function pointers, it forces struct initialization etc. As said in the first mail, the Grsecurity patches usually cherry-picks security bugfixes which are not yet in a released kernel. As the kernel teams already do it, I remove those bits from the grsecurity patch. In 2.6.37 there's no need for that yet but I do it for the 2.6.32 I'm tracking too. http://git.debian.org/?p=collab-maint/linux-grsec-base.git;a=summary if needed. Why is this not part of the patch below? The grsec.conf was attached to the initial bug report. As there is no easy way to ship an external file in the linux-image, I was told it'd be a better idea to make an external package and that helps because I can do the user creation there and add a README. External _binary_ package, not source package. I have to admit I don't know how to integrate a new binary package like this using the existing linux-2.6 source package, but I'm not at all opposed to include it in order to keep things at the same place. But does the linux-2.6 architecture permits that? +CONFIG_DEBUG_STRICT_USER_COPY_CHECKS=y Please show why this should not be enabled globaly. Good point, it should. I'll make a separated bug report. No need for a bug. Ok. +CONFIG_DEBUG_RODATA=y Fixed. The current patch even marks it as broken. Yeah, right. PaX enforces itself readonly stuff (which is why it adds a lot of const stuff)
Bug#611216: linux-2.6 - New monitor chip: w83795
Package: linux-2.6 Version: 2.6.32-30 Severity: important Please add support for new monitor chip w83795. Bastian -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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/20110126212010.11420.34954.report...@wavehammer.waldi.eu.org
Re: I can hear audio CD (in console) with kernel 2.6.30 but not with 2.6.32-5-686 (squeeze)
Problem solved. I just added at the bottom of the file /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=acer Sorry to have disturbed the list kernel-debian. -- Gérard -- 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/20110126214824.GA5102@mauritiusGA
Bug#611099: Sporadic failure to resume from hibernation on Msi wind u100
Thank you for prompt answer. I removed VirtualBox, same result. Any thoughts? -- С наилучшими пожеланиями, Спицын Андрей. -- Best regards, Andrey Spitsyn. В Срд, 26/01/2011 в 08:57 +1000, Ben Hutchings пишет: On Tue, 2011-01-25 at 17:38 +0300, Спицын Андрей wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: normal Laptop fails to wake after second or third hibernation. It's just reboot with no errors. Msi wind u100. I tryed recovery mode - same result. I tryed 2.6.32-3-686 (recovery mode) it works. It's happend after last update. [...] Try removing or disabling VirtualBox. Ben. -- 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/1296081195.2781.26.ca...@wind.gear
Bug#605090: Updated patch
On Tue, 18 Jan 2011, Yves-Alexis Perez wrote: Kernel team, what do you think? Could the patches be merged against trunk? Config might still need some reviewing but that can be done once people start testing the packages. What follows is my personal view, in short what I miss most is an assessement of the involved cost of this specific feature branch. first of all merging a patch that deviates from mainline for an eternety and shows zero interest of upstream merging is not a good candidate. You get longterm plenty of cost versus allmost no benefit. I'm quite unsure that this patch benefits Debian. From a distant past look it was in fact quite untastefull. The second trouble is that I question your understanding of this patch. (viewing the way you answered waldi's questions). Third beside security theatre what is gained by it? Fourth why not invest the time for Wheezy and have finally the mainline and security backed SELinux ready. This seems like a much better time investment. Fifth the ninties are over, an upstream that still doesn't use an VSC seems very untrustworthy. happy hacking -- maks -- 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/20110126232927.gm5...@stro.at
Bug#506540: /usr/sbin/update-initramfs: update-initramfs miss symlink Possible missing firmware tigon
On Wed, 2011-01-26 at 16:23 +0100, ~ tekmans ~ wrote: tags 506540 moreinfo stop On Wed, Jan 26, 2011 at 02:25:12PM +0100, tekmans wrote: Package: initramfs-tools Severity: normal File: /usr/sbin/update-initramfs miss symlink to the original tigon firmware installed during the debian installation added by usb stick resolve trouble by adding the missing link could you be more concrete and tell how this symlink /lib/firmware looks like, aka ls -l of it, thanks. I was installing mdadm, sample output below update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3 ls -l /lib/firmware/tigon/ lrwxrwxrwx 1 root root 32 26 janv. 12:40 tg3.bin - /lib/firmware/tigon/tg3_tso5.bin -rwxr-xr-x 1 root root 3884 14 oct. 2009 tg3_tso5.bin lrwxrwxrwx 1 root root 32 26 janv. 12:40 tg3_tso.bin - /lib/firmware/tigon/tg3_tso5.bin [...] Are you *trying* to break your network card? 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
Bug#611234: linux-image-2.6.32-5-xen-amd64: enable CONFIG_XEN_PCI_PASSTHROUGH
Package: linux-2.6 Version: 2.6.32-30 Severity: wishlist CONFIG_XEN_PCI_PASSTHROUGH is not enabled by default in this kernel. It would be nice to change that. Thanks, Ward. -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 05:46:49 UTC 2011 ** Command line: placeholder root=UUID=1ab080f3-e10c-45aa-91c9-a339c384e3b6 ro ** Tainted: W (512) * Taint on warning. ** Kernel log: [3.794986] md: bindsda3 [3.797518] raid1: raid set md1 active with 2 out of 2 mirrors [3.797662] md1: detected capacity change from 0 to 20479934464 [3.800146] md1: unknown partition table [3.856035] md: md2 stopped. [3.858805] md: bindsdb4 [3.859160] md: bindsda4 [3.863825] raid1: raid set md2 active with 2 out of 2 mirrors [3.863967] md2: detected capacity change from 0 to 2047934464 [3.866534] md2: unknown partition table [3.877599] device-mapper: uevent: version 1.0.3 [3.878230] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [3.943448] PM: Starting manual resume from disk [3.943583] PM: Resume from partition 9:2 [3.943585] PM: Checking hibernation image. [3.944852] PM: Error -22 checking image file [3.944855] PM: Resume from disk failed. [3.982004] kjournald starting. Commit interval 5 seconds [3.982017] EXT3-fs: mounted filesystem with ordered data mode. [4.831936] udev[631]: starting version 164 [4.955670] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [4.955855] ACPI: Power Button [PWRB] [4.956082] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [4.956238] ACPI: Power Button [PWRF] [5.161516] EDAC MC: Ver: 2.1.0 Jan 12 2011 [5.166756] EDAC amd64_edac: Ver: 3.2.0 Jan 12 2011 [5.167301] EDAC amd64: ECC is enabled by BIOS. [5.167887] EDAC amd64: ECC is enabled by BIOS. [5.168156] EDAC amd64: ECC is enabled by BIOS. [5.168415] EDAC amd64: ECC is enabled by BIOS. [5.168739] EDAC MC: F10h CPU detected [5.168799] input: PC Speaker as /devices/platform/pcspkr/input/input5 [5.168847] EDAC amd64: f10_probe_valid_hardware() This machine is running with DDR3 memory. This is not currently supported. DCHR0=0x3f48090d DCHR1=0x3f48090d [5.168856] EDAC amd64:Contact 'amd64_edac' module MAINTAINER to help add support. [5.177119] piix4_smbus :00:14.0: SMBus Host Controller at 0xb00, revision 0 [5.462701] Error: Driver 'pcspkr' is already registered, aborting... [5.815025] md: md3 stopped. [5.816108] md: bindsdb5 [5.816383] md: bindsda5 [5.824049] raid1: raid set md3 active with 2 out of 2 mirrors [5.824266] md3: detected capacity change from 0 to 181553878016 [5.831727] md3: unknown partition table [6.464490] Adding 128k swap on /dev/md2. Priority:-1 extents:1 across:128k [6.665853] EXT3 FS on md1, internal journal [6.810947] loop: module loaded [6.985043] mlx4_ib: Mellanox ConnectX InfiniBand driver v1.0-ofed1.5.2 (August 4, 2010) [8.335417] ib_srp: ASYNC event= 11 on device= mlx4_0 [8.383296] ib_srp: ASYNC event= 17 on device= mlx4_0 [8.390935] ib_srp: ASYNC event= 9 on device= mlx4_0 [8.537955] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [8.539734] ADDRCONF(NETDEV_UP): eth0: link is not ready [8.546073] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [9.468062] Event-channel device installed. [9.646168] alloc irq_desc for 4230 on node -1 [9.646173] alloc kstat_irqs on node -1 [9.646264] alloc irq_desc for 4229 on node -1 [9.646268] alloc kstat_irqs on node -1 [9.646808] XENBUS: Unable to read cpu state [9.647231] XENBUS: Unable to read cpu state [9.647566] XENBUS: Unable to read cpu state [9.647902] XENBUS: Unable to read cpu state [9.648354] XENBUS: Unable to read cpu state [9.648761] XENBUS: Unable to read cpu state [9.649151] XENBUS: Unable to read cpu state [9.649442] XENBUS: Unable to read cpu state [9.649718] XENBUS: Unable to read cpu state [9.650034] XENBUS: Unable to read cpu state [9.650315] XENBUS: Unable to read cpu state [9.650588] XENBUS: Unable to read cpu state [9.650875] XENBUS: Unable to read cpu state [9.651152] XENBUS: Unable to read cpu state [9.651585] XENBUS: Unable to read cpu state [9.652000] XENBUS: Unable to read cpu state [ 11.207121] Bridge firewalling registered [ 11.653335] ADDRCONF(NETDEV_UP): peth0: link is not ready [ 14.552581] igb: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 14.558686] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready [ 14.720974] device peth0 entered promiscuous mode [ 14.764960] eth0: port 1(peth0) entering forwarding state [ 15.326131] ADDRCONF(NETDEV_UP): peth1: link is not ready [ 24.600059]
Bug#611234: linux-image-2.6.32-5-xen-amd64: enable CONFIG_XEN_PCI_PASSTHROUGH
On Wed, Jan 26, 2011 at 10:03:38PM -0500, Ward Vandewege wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: wishlist CONFIG_XEN_PCI_PASSTHROUGH is not enabled by default in this kernel. It would be nice to change that. Or, I guess, not - I see now that this option is no longer used. Sorry for the noise. Thanks, Ward. -- 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/20110127031505.ga4...@countzero.vandewege.net
Processed: closing 611234
Processing commands for cont...@bugs.debian.org: close 611234 Bug#611234: linux-image-2.6.32-5-xen-amd64: enable CONFIG_XEN_PCI_PASSTHROUGH 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Ward Vandewege w...@jhvc.com thanks Stopping processing here. Please contact me if you need assistance. -- 611234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611234 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.1296102842816.transcr...@bugs.debian.org
