Re: xen kernel features
On Thu, 2010-07-01 at 00:25 +0200, Bastian Blank wrote: On Wed, Jun 30, 2010 at 09:53:17PM +0100, Ian Campbell wrote: On Wed, 2010-06-30 at 20:58 +0200, Csillag Kristof wrote: - PCI passthru to PV guests does not work, because CONFIG_XEN_PCI_PASSTHROUGH is disabled in kernel config. I think this should be trivial to enable -- does any one on debian-kernel object to enabling it in trunk and sid branches? It have no effect, so no: | $ grep XEN_PCI_PASSTHROUGH -r * | arch/x86/xen/Kconfig:config XEN_PCI_PASSTHROUGH Oh right, the actual relevant option for pcifront support is CONFIG_PCI_XEN which is already enabled. Similarly for pciback the option is CONFIG_XEN_PCIDEV_BACKEND and is already enabled. So it looks like pci passthrough should just work already and XEN_PCI_PASSTHROUGH is some redundant option which doesn't do anything. Ian. -- Ian Campbell BOFH excuse #256: You need to install an RTFM interface. signature.asc Description: This is a digitally signed message part
Re: Re: xen kernel features
So it looks like pci passthrough should just work already and XEN_PCI_PASSTHROUGH is some redundant option which doesn't do anything. The dom0 part is indeed OK; now I see that the problem is in the domU. Unfortunately, current debian kernels I use for domUs (2.6.32-5-686-bigmem and 2.6.32-5-amd64) do not have the required XEN pcifront driver yet. Will try to boot -xen kernels on domU... Kristof -- 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/aanlktin8p7czxs6sbcf_evkejrrkfmasz9r3havd-...@mail.gmail.com
Bug#586554: update-initramfs fails to generate initrd.img-2.6.32-5-686 in Debian testing when upgrading from 0.96 to 0.97
* Alesh Slovak alesh.slo...@avasys.jp [Thu Jul 01, 2010 at 11:46:03AM +0900]: On 06/30/2010 07:25 PM, Michael Prokop wrote: We are working on new initramfs-tools version which should display the source of the problem then, I'll be investigating on the iscan issue in more detail as well and report back. Thanks to all for your help tracking this down. I've found the problem. It was indeed related to the fact that the new version of initramfs-tools runs the hook scripts under errexit. If the very last file that iscan's hook script checks for in DESTDIR doesn't exist, the `test -e` call fails and the script ends with a failed status even though nothing really went wrong. A simple `exit 0` on the last line fixes this. I'll try to get a fixed version of iscan-data out as soon as I can. Great, thanks for reporting back. I'll make sure users know which script fails so we can track and debug such issues easier. regards, -mika- signature.asc Description: Digital signature
Re: Re: Re: xen kernel features
OK, I can confirm that when booting -xen kernel on the domU (2.6.32-5-xen-686, to be specific), PCI passthru works as expected. -- 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/aanlktikigbg7wq8u8ysvx2qsrzidqo56owr90scgl...@mail.gmail.com
Bug#587754: linux-image-2.6.32-5-686-bigmem: dpkg failed dependency problems prevent configuration of linux-image
Package: linux-2.6 Version: 2.6.32-15 Severity: important apt-get upgrade fails. The kernel installation/upgrade throws the following error. dpkg: error processing linux-image-2.6.32-5-686-bigmem (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686-bigmem: linux-image-2.6-686-bigmem depends on linux-image-2.6.32-5-686-bigmem; however: Package linux-image-2.6.32-5-686-bigmem is not configured yet. dpkg: error processing linux-image-2.6-686-bigmem (--configure): -- Package-specific info: ** Version: Linux version 2.6.32-5-686-bigmem (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 05:38:08 UTC 2010 ** Command line: root=/dev/mapper/vg0-root ro ** Not tainted ** Kernel log: [8.397930] i2c /dev entries driver [9.068277] Adding 4194296k swap on /dev/mapper/vg0-swap. Priority:-1 extents:1 across:4194296k [ 10.862917] kjournald starting. Commit interval 5 seconds [ 10.863322] EXT3 FS on sda1, internal journal [ 10.863350] EXT3-fs: mounted filesystem with ordered data mode. [ 10.888701] kjournald starting. Commit interval 5 seconds [ 10.889126] EXT3 FS on dm-5, internal journal [ 10.889153] EXT3-fs: mounted filesystem with ordered data mode. [ 10.931411] kjournald starting. Commit interval 5 seconds [ 10.931806] EXT3 FS on dm-2, internal journal [ 10.933125] EXT3-fs: mounted filesystem with ordered data mode. [ 10.966933] kjournald starting. Commit interval 5 seconds [ 10.968622] EXT3 FS on dm-1, internal journal [ 10.969940] EXT3-fs: mounted filesystem with ordered data mode. [ 11.007384] kjournald starting. Commit interval 5 seconds [ 11.009139] EXT3 FS on dm-4, internal journal [ 11.010510] EXT3-fs: mounted filesystem with ordered data mode. [ 12.212180] e1000e :00:19.0: irq 24 for MSI/MSI-X [ 12.268116] e1000e :00:19.0: irq 24 for MSI/MSI-X [ 12.268303] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.012775] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 14.014442] :00:19.0: eth0: 10/100 speed: disabling TSO [ 14.016277] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 15.364493] fuse init (API version 7.13) [ 22.236487] Bluetooth: Core ver 2.15 [ 22.236526] NET: Registered protocol family 31 [ 22.236528] Bluetooth: HCI device and connection manager initialized [ 22.236530] Bluetooth: HCI socket layer initialized [ 22.304049] Bluetooth: L2CAP ver 2.14 [ 22.304051] Bluetooth: L2CAP socket layer initialized [ 22.308120] Bluetooth: RFCOMM TTY layer initialized [ 22.308123] Bluetooth: RFCOMM socket layer initialized [ 22.308125] Bluetooth: RFCOMM ver 1.11 [ 22.984577] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 22.984580] Bluetooth: BNEP filters: protocol multicast [ 23.020125] Bridge firewalling registered [ 23.192968] Bluetooth: SCO (Voice Link) ver 0.6 [ 23.192972] Bluetooth: SCO socket layer initialized [ 24.472507] eth0: no IPv6 routers present [ 191.529097] RPC: Registered udp transport module. [ 191.529100] RPC: Registered tcp transport module. [ 191.529102] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 191.554535] Slow work thread pool: Starting up [ 191.554566] Slow work thread pool: Ready [ 191.554603] FS-Cache: Loaded [ 191.600985] FS-Cache: Netfs 'nfs' registered for caching [ 191.617911] svc: failed to register lockdv1 RPC service (errno 97). [ 194.981510] CPU0 attaching NULL sched-domain. [ 194.981514] CPU1 attaching NULL sched-domain. [ 195.096123] CPU0 attaching sched-domain: [ 195.096126] domain 0: span 0-1 level MC [ 195.096129] groups: 0 1 [ 195.096133] CPU1 attaching sched-domain: [ 195.096135] domain 0: span 0-1 level MC [ 195.096137] groups: 1 0 [ 2050.016945] svc: failed to register lockdv1 RPC service (errno 97). [11041.298847] svc: failed to register lockdv1 RPC service (errno 97). [28168.325019] svc: failed to register lockdv1 RPC service (errno 97). [59893.007900] svc: failed to register lockdv1 RPC service (errno 97). [64097.377740] svc: failed to register lockdv1 RPC service (errno 97). [71519.292539] svc: failed to register lockdv1 RPC service (errno 97). [73320.314925] svc: failed to register lockdv1 RPC service (errno 97). [74823.724036] usb 8-2: new full speed USB device using uhci_hcd and address 2 [74823.897079] usb 8-2: New USB device found, idVendor=0421, idProduct=0208 [74823.897083] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [74823.897085] usb 8-2: Product: Nokia 5130c-2 [74823.897087] usb 8-2: Manufacturer: Nokia [74823.897181] usb 8-2: configuration #1 chosen from 1 choice [74823.976155] cdc_acm 8-2:1.1: ttyACM0: USB ACM device [74823.979177] usbcore: registered new interface driver cdc_acm [74823.979223] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters [74823.983475] NET:
Bug#587763: linux-image-2.6.32-5-amd64: scary messages from JBD when manipulating quotas on ext4
Package: linux-2.6 Version: 2.6.32-15 Severity: important Hi, here is how to reproduce this bug: 1. set up quotas on an ext4 filesystem 2. use edquota to change the quotas of some user Actual result: the kernel outputs this scary message: [ 399.792052] JBD: Spotted dirty metadata buffer (dev = sdb1, blocknr = 34816). There's a risk of filesystem corruption in case of system crash. Expected result: - no scary message - no filesystem corruption - changed quotas A patch has been proposed here: http://www.spinics.net/lists/linux-ext4/msg19302.html This bug has also been reported here: https://bugzilla.redhat.com/show_bug.cgi?id=578674 -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010 -- System Information: Debian Release: squeeze/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- 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/1277990992.2934.35.ca...@localhost
Bug#587754: linux-image-2.6.32-5-686-bigmem: dpkg failed dependency problems prevent configuration of linux-image
On Thu, Jul 01, 2010 at 06:00:00PM +0530, B. Raveendra Reddy wrote: apt-get upgrade fails. The kernel installation/upgrade throws the following error. dpkg: error processing linux-image-2.6.32-5-686-bigmem (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686-bigmem: linux-image-2.6-686-bigmem depends on linux-image-2.6.32-5-686-bigmem; however: Package linux-image-2.6.32-5-686-bigmem is not configured yet. dpkg: error processing linux-image-2.6-686-bigmem (--configure): This is not the complete output. You removed the important parts. Bastian -- Life and death are seldom logical. But attaining a desired goal always is. -- McCoy and Spock, The Galileo Seven, stardate 2821.7 -- 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/20100701141626.gb23...@wavehammer.waldi.eu.org
reviving xen-3.2 for testing?
Hi there, Since the current XEN 3.4 and XEN 4.0 in debian lack HVM support, but the XEN 3.2 packages has it, I was wondering how much work would it require to revive the old 3.2 packages, so that they can be installed in current testing/unstable? (They were perfectly fine until a few weeks ago; only the recent python upgrade made them uninstallable. I have been using it until yesterday.) So, as far as I can tell, all they need is some re-packaging. (And maybe some small python fixes, but I'm sure you know that better than me.) Thank you for your help: Kristof -- 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/4c2ca1c6.5000...@gmail.com
Bug#520468: Incorporate fixes for WUSB54GS support from 2.6.33
Hi This patch seems to have fixed it. Here are the results of my testing: kernel.org's 2.6.34: = with the usbnet-Set-parent-device-early-for-netdev_printk patch: Seems to work without any problems Debian's 2.6.34 from experimental: = with both patches: usbnet-Set-parent-device-early-for-netdev_printk rndis_host-Poll-status-channel-before-control-channel The module is loaded without any apparent problems. I get this on the syslog when I try to configure the device: # ifconfig wlan0 up Jun 30 16:09:00 C-5 kernel: [ 79.184493] rndis_wlan 2-2:1.0: wlan0: couldn't set packet filter: 000d NetworkManager also makes that line appear on syslog and doesn't seem to be able to configure it. = _only_ with usbnet-Set-parent-device-early-for-netdev_printk (rndis_host-Poll-status... removed) Seems to work without any problems. The attachment has a more complete syslog with the moment I plugged the device and NetworkManager tried to configure it. Best regards, Pitxyoki On Tue, Jun 29, 2010 at 2:18 AM, Ben Hutchings b...@decadent.org.uk wrote: (...) I think the attached patch will fix this. Please test it. # kernel.org 2.6.34 # with usbnet-Set-parent-device-early-for-netdev_printk.patch: Seems to work without any problems. Debian's 2.6.34-1~experimental.2 with both: - usbnet-Set-parent-device-early-for-netdev_printk.patch - rndis_host-Poll-status-channel-before-control-channel.patch Jun 30 16:08:59 C-5 kernel: [ 78.264019] usb 2-2: new full speed USB device using uhci_hcd and address 3 Jun 30 16:08:59 C-5 kernel: [ 78.443509] usb 2-2: New USB device found, idVendor=13b1, idProduct=000e Jun 30 16:08:59 C-5 kernel: [ 78.443516] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 30 16:08:59 C-5 kernel: [ 78.443521] usb 2-2: Product: Linksys Wireless-G USB Network Adapter with SpeedBooster Jun 30 16:08:59 C-5 kernel: [ 78.443525] usb 2-2: Manufacturer: Cisco-Linksys Jun 30 16:08:59 C-5 kernel: [ 78.443529] usb 2-2: SerialNumber: Jun 30 16:09:00 C-5 kernel: [ 78.515161] usbcore: registered new interface driver cdc_ether Jun 30 16:09:00 C-5 kernel: [ 78.655691] usbcore: registered new interface driver rndis_host Jun 30 16:09:00 C-5 kernel: [ 78.714723] cfg80211: Calling CRDA to update world regulatory domain Jun 30 16:09:00 C-5 kernel: [ 78.777501] rndis_wlan 2-2:1.0: (unregistered net_device): media disconnect Jun 30 16:09:00 C-5 NetworkManager: info Found wlan radio killswitch rfkill0 (at /sys/devices/pci:00/:00:1d.1/usb2/2-2/ieee80211/phy0/rfkill0) (driver unknown) Jun 30 16:09:00 C-5 kernel: [ 78.967795] rndis_wlan 2-2:1.0: wlan0: register 'rndis_wlan' at usb-:00:1d.1-2, Wireless RNDIS device, BCM4320a based, 00:12:17:a0:b9:7c Jun 30 16:09:00 C-5 kernel: [ 78.967837] usbcore: registered new interface driver rndis_wlan Jun 30 16:09:00 C-5 NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1d.1/usb2/2-2/2-2:1.0/net/wlan0, iface: wlan0) Jun 30 16:09:00 C-5 NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:1d.1/usb2/2-2/2-2:1.0/net/wlan0, iface: wlan0): no ifupdown configuration found. Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): driver supports SSID scans (scan_capa 0x01). Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): new 802.11 WiFi device (driver: 'rndis_wlan') Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): now managed Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): device state change: 1 - 2 (reason 2) Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): bringing up device. Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): preparing device. Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): deactivating device (reason: 2). Jun 30 16:09:00 C-5 kernel: [ 79.180877] ADDRCONF(NETDEV_UP): wlan0: link is not ready Jun 30 16:09:00 C-5 kernel: [ 79.184493] rndis_wlan 2-2:1.0: wlan0: couldn't set packet filter: 000d Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): supplicant interface state: starting - ready Jun 30 16:09:00 C-5 NetworkManager: info (wlan0): device state change: 2 - 3 (reason 42) Jun 30 16:09:00 C-5 wpa_supplicant[1451]: Failed to initiate AP scan. # ifconfig wlan0 up Jun 30 16:10:11 C-5 kernel: [ 150.019724] rndis_wlan 2-2:1.0: wlan0: couldn't set packet filter: 000d with: - usbnet-Set-parent-device-early-for-netdev_printk.patch and without: - rndis_host-Poll-status-channel-before-control-channel.patch Seems to work without any problems.
Bug#587014: screen brightness can't be modified on Panasonic S9
On Sun, Jun 27, 2010 at 03:14:44AM +0100, Ben Hutchings wrote: Harald, Nicolas Limare reported that the backlight control in panasonic-laptop is non-functional on the S9; see http://bugs.debian.org/587014. There's a kernel log attached to that bug report, but it doesn't show very much. Can you suggest how to investigate this? Could be a number of things. The output of acpidump would help. -- Matthew Garrett | mj...@srcf.ucam.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/20100701151622.ga1...@srcf.ucam.org
Re: [DRAFT] Policy for Linux kernel, initramfs, boot loader update process
On Wed, 30 Jun 2010 09:29:42 -0400 (EDT), Stephen Powell wrote: Since symlinks are not associated with any package in particular, and since they seem to have been designed for the convenience of historic boot loaders such as lilo and zipl, perhaps the best way to handle this is for the boot loader hook script, zz-whatever, to maintain the symlinks, if desired. As a matter of fact, I already have a hook script on hand that does this very thing, and with minor modifications will do nicely, I think. Right now, it unconditionally maintains the symlinks. To generalize it more, it could determine if symlinks already exist or not, and if so where, then maintain them where they are. If the symlinks don't exist, it won't create them. It could also be changed to determine if lilo or zipl is in use, based on the presence of the config file, and invoke the appropriate boot loader. Then, all the maintainer of the s390-tools package would have to do is to include it in the s390-tools package. And the maintainer of lilo could do the same. OK, I now have some templates to shoot at. /etc/kernel/postinst.d/zz-bootloader http://www.wowway.com/~zlinuxman/kernel/postinst.d/zz-bootloader /etc/kernel/postrm.d/zz-bootloader http://www.wowway.com/~zlinuxman/kernel/postrm.d/zz-bootloader These templates should work for both lilo and zipl, and they maintain the symbolic links, if they already exist. When doing an initial install (Debian installer), (1) the initial kernel must be installed first, then (2) the boot loader must be installed, then (3) the initial symlinks must be created (if lilo or zipl), then (4) dpkg-reconfigure or the boot loader installer (lilo or zipl) must be run. (Steps 2 and 3 could optionally be reversed or combined.) After that, the hook scripts will maintain the symbolic links as long as there is at least one installed kernel at all times. (Presumably one will never purge the running kernel!) In particular, /etc/kernel-img.conf is not examined to see if do_symlinks = yes is set. If symlinks are present, they will be maintained. If they are not, they will not be created. ... [discussion of initramfs-tools issues ] Since you're obviously very busy, I will submit a version of the initramfs-tools script which I believe will address all these issues. Then you can take pot shots at it. These are included here: /etc/kernel/postinst.d/initramfs-tools http://www.wowway.com/~zlinuxman/kernel/postinst.d/initramfs-tools /etc/kernel/postrm.d/initramfs-tools http://www.wowway.com/~zlinuxman/kernel/postrm.d/initramfs-tools For the boot loader hook to initramfs builders: /etc/initramfs/post-update.d/bootloader http://www.wowway.com/~zlinuxman/initramfs/post-update.d/bootloader (This last interface is not currently functional, of course.) How do they look? -- .''`. Stephen Powell : :' : `. `'` `- -- 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/1920933269.99141.1278000752640.javamail.r...@md01.wow.synacor.com
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #569012 (http://bugs.debian.org/569012) # * http://bugzilla.kernel.org/show_bug.cgi?id=15296 # * remote status changed: NEEDINFO - REJECTED # * remote resolution changed: (?) - INSUFFICIENT-DATA # * closed upstream tags 569012 + fixed-upstream Bug #569012 [linux-2.6] linux-image-2.6.32-1-amd64: Freezes and memory corruption Added tag(s) fixed-upstream. usertags 569012 - status-NEEDINFO Bug#569012: linux-image-2.6.32-1-amd64: Freezes and memory corruption Usertags were: status-NEEDINFO. Usertags are now: . usertags 569012 + status-REJECTED resolution-INSUFFICIENT-DATA Bug#569012: linux-image-2.6.32-1-amd64: Freezes and memory corruption There were no usertags set. Usertags are now: status-REJECTED resolution-INSUFFICIENT-DATA. # remote status report for #587149 (http://bugs.debian.org/587149) # * https://bugs.freedesktop.org/show_bug.cgi?id=28763 # * remote status changed: (?) - NEW usertags 587149 + status-NEW Bug#587149: xserver-xorg-video-nouveau: X segfault and kernel oops when displaying large images There were no usertags set. Usertags are now: status-NEW. thanks Stopping processing here. Please contact me if you need assistance. -- 587149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587149 569012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569012 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.127800206628901.transcr...@bugs.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #569012 (http://bugs.debian.org/569012) # * http://bugzilla.kernel.org/show_bug.cgi?id=15296 # * remote status changed: NEEDINFO - REJECTED # * remote resolution changed: (?) - INSUFFICIENT-DATA # * closed upstream tags 569012 + fixed-upstream usertags 569012 - status-NEEDINFO usertags 569012 + status-REJECTED resolution-INSUFFICIENT-DATA # remote status report for #587149 (http://bugs.debian.org/587149) # * https://bugs.freedesktop.org/show_bug.cgi?id=28763 # * remote status changed: (?) - NEW usertags 587149 + status-NEW 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/20100701163424.25564.10164.btsl...@merkel.debian.org
Bug#587789: linux-image-2.6-686: netfilters clamp-mss-to-pmtu sets bad MSS when non was set before
Package: linux-image-2.6-686 Version: 2.6.26+17+lenny1 Severity: important Hi, Netfilters clamp-mss-to-pmtu (as used in iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu) sets MSS in packets that had no MSS set before. So instead of sending packets of standard TCP MSS 536 Bytes to a host that didn't set a MSS at all, packets with a potentially higher MSS (like 1452 on my DSL connection) will be sent to that host. That might fail if the host only accepts packets with a MSS of 536 (like http://research.microsoft.com). If that host also doesn't send a ICMP fragmentation needed packet (like research.microsoft.com ...) the connection will fail. Clamp-mss-to-pmtu really shouldn't set a MSS if none was set before. RFC 879 says HOSTS MUST NOT SEND DATAGRAMS LARGER THAN 576 OCTETS UNLESS THEY HAVE SPECIFIC KNOWLEDGE THAT THE DESTINATION HOST IS PREPARED TO ACCEPT LARGER DATAGRAMS. This means that the standard MTU is 576 and the standard MSS 536 and any server not setting a MSS can expect to only receive packages with a MSS of 536 bytes. If the clamping sets a MSS 536 connections might fail. I stumbled upon this problem in debian bug #541658[1] ([iceweasel] cannot open research.microsoft.com - only worth reading for entertainment purposes) and, after that bug was closed, analysed it in my blog[2] until a friend of mine found out why the page loads when clamping mss to pmtu is disabled or restricted to a range (like with iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1400:1536 -j TCPMSS --clamp-mss-to-pmtu) but doesn't load with simple clamping. His really great and detailed analysation of the problem may be seen at [3]. He also looked into the kernel code (net/netfilter/xt_TCPMSS.c) and found the kind of contradicting comments Never increase MSS, even when setting it, as doing so results in problems for hosts that rely on MSS being set correctly. (line 93) and MSS Option not found ?! add it.. (line 116). So instead of just leaving a packet without MSS option untouched a new MSS, that might be much greater than the default 536, is set, even though the guy who wrote that seemed to be aware that MSS may not be increased. This bug most probably affects all kernel version from at least 2.6.26 (probably also much older versions) up to now. It seems like also some hardware-routers that probably use Linux are affected. Cheers, - Daniel -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.26-2-686 2.6.26-24 Linux 2.6.26 image on PPro/Celeron linux-image-2.6-686 recommends no packages. linux-image-2.6-686 suggests no packages. -- 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/20100701164335.20812.29648.report...@portroyal.horst.lan
Bug#587789: linux-image-2.6-686: netfilters clamp-mss-to-pmtu sets bad MSS when non was set before
Daniel Gibson wrote: Hi, Netfilters clamp-mss-to-pmtu (as used in iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu) sets MSS in packets that had no MSS set before. So instead of sending packets of standard TCP MSS 536 Bytes to a host that didn't set a MSS at all, packets with a potentially higher MSS (like 1452 on my DSL connection) will be sent to that host. That might fail if the host only accepts packets with a MSS of 536 (like http://research.microsoft.com). If that host also doesn't send a ICMP fragmentation needed packet (like research.microsoft.com ...) the connection will fail. Clamp-mss-to-pmtu really shouldn't set a MSS if none was set before. RFC 879 says HOSTS MUST NOT SEND DATAGRAMS LARGER THAN 576 OCTETS UNLESS THEY HAVE SPECIFIC KNOWLEDGE THAT THE DESTINATION HOST IS PREPARED TO ACCEPT LARGER DATAGRAMS. This means that the standard MTU is 576 and the standard MSS 536 and any server not setting a MSS can expect to only receive packages with a MSS of 536 bytes. If the clamping sets a MSS 536 connections might fail. I stumbled upon this problem in debian bug #541658[1] ([iceweasel] cannot open research.microsoft.com - only worth reading for entertainment purposes) and, after that bug was closed, analysed it in my blog[2] until a friend of mine found out why the page loads when clamping mss to pmtu is disabled or restricted to a range (like with iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 1400:1536 -j TCPMSS --clamp-mss-to-pmtu) but doesn't load with simple clamping. His really great and detailed analysation of the problem may be seen at [3]. He also looked into the kernel code (net/netfilter/xt_TCPMSS.c) and found the kind of contradicting comments Never increase MSS, even when setting it, as doing so results in problems for hosts that rely on MSS being set correctly. (line 93) and MSS Option not found ?! add it.. (line 116). So instead of just leaving a packet without MSS option untouched a new MSS, that might be much greater than the default 536, is set, even though the guy who wrote that seemed to be aware that MSS may not be increased. This bug most probably affects all kernel version from at least 2.6.26 (probably also much older versions) up to now. It seems like also some hardware-routers that probably use Linux are affected. Due to a bug of reportbug (I started it with reportbug -o /tmp/bug.txt to send the bug from my regular email-programm, but at the end the bug was sent by reportbug anyway) the report was sent prematurely and the links were missing.. [1] original bug report for iceweasel (not too helpful): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541658 [2] my blog entry analysing the bug: http://caedesnotes.wordpress.com/2010/06/30/bug-hunting-browsers-fail-to-load-research-microsoft-com/ [3] blog entry of a friend of mine who found the real cause: http://carnivore.it/2010/07/01/research.microsoft.com_-_mss_of_536_bytes Cheers, - Daniel -- 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/4c2cc777.80...@gmail.com
Re: Re: xen kernel features
Please check the archives for pkg-xen-devel mailing list on alioth. Someone is working on packaging the necessary qemu-dm, I think there are packages available for testing too. I think that's Thomas Goirand, and the package is available here: http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-4.0/ I have tried to recompile the package for current testing/sid, but it fails. --- make[1]: Entering directory `/root/hvm/xen-qemu-dm-4.0/src/xen-qemu-dm-4.0-4.0.0.patched/debian/build' CCqemu-nbd.o In file included from ./config-host.h:28, from ./qemu-common.h:33, from qemu-nbd.c:20: ./xen-config-host.h:22:23: error: blktaplib.h: No such file or directory make[1]: *** [qemu-nbd.o] Error 1 make[1]: Leaving directory `/root/hvm/xen-qemu-dm-4.0/src/xen-qemu-dm-4.0-4.0.0.patched/debian/build' make: *** [debian/stamps/build] Error 2 --- That is because libxen-dev doesn't ship blktaplib.h any more (#587305) because of some license incompatibilities and/or or unresolved technical problems. Until it is resolved, HVM support will have to wait. Unfortunately, this also kills VNC console for PV guests, too, among other things... :( Kristof Csillag -- 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/aanlktin6ulxqzw1vckfcfey5vw9fu9sc-v6yfnzp1...@mail.gmail.com
Processed: tagging 570350
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 570350 + pending Bug #570350 [linux-2.6] [chrome] linux-image-2.6.26-2-amd64: kernel BUG at kernel/exit.c:822! Bug #542115 [linux-2.6] [chrome] linux-image-2.6.26-2-686: kernel BUG at kernel/exit.c:822! Added tag(s) pending. Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 570350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570350 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.127803319119844.transcr...@bugs.debian.org
Processed: Re: aumix: pcm2 cannot be set and remains not seen by command
Processing commands for cont...@bugs.debian.org: reassign 582840 linux-2.6 Bug #582840 [aumix] aumix: pcm2 cannot be set and remains not seen by command Bug reassigned from package 'aumix' to 'linux-2.6'. Bug No longer marked as found in versions aumix/2.9.1-1. retitle 582840 PCM channel missing from OSS mixer API Bug #582840 [linux-2.6] aumix: pcm2 cannot be set and remains not seen by command Changed Bug title to 'PCM channel missing from OSS mixer API' from 'aumix: pcm2 cannot be set and remains not seen by command' thanks Stopping processing here. Please contact me if you need assistance. -- 582840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582840 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.127804213830053.transcr...@bugs.debian.org
Uploading linux-2.6 2.6.32-16
I intend to upload a new version of linux-2.6 this weekend, incorporating stable releases 2.6.32.16 and (for drm drivers) 2.6.33.6. This does not appear to require an ABI bump. Shout if there's anything I should wait for. 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#582840: aumix: pcm2 cannot be set and remains not seen by command
tag 582840 wontfix thanks OSS is deprecated in Linux. I recommend that you use a native ALSA utility such as alsamixer instead. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: aumix: pcm2 cannot be set and remains not seen by command
Processing commands for cont...@bugs.debian.org: tag 582840 wontfix Bug #582840 [linux-2.6] PCM channel missing from OSS mixer API Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 582840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582840 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.12780428511574.transcr...@bugs.debian.org
Bug#508685: linux-image-2.6.26-1-amd64: Cannot mute cx8800 v4l card
On Wed, Feb 17, 2010 at 20:56, Moritz Muehlenhoff j...@inutil.org wrote: On Thu, Aug 27, 2009 at 02:10:29AM +0200, Stefan Ott wrote: Does this still occur with more recent versions of the kernel? Yes, still happens on linux-image-2.6.30-1-amd64 Sorry for the late reply, this fell through the cracks :-/ The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers: http://bugzilla.kernel.org (Product: Drivers, Component: Video(Other)) The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Hi Sorry for my late reply this time, things are a little busy :) Anyway: yes, this still happens with 2.6.32-5-amd64 (and with vanilla 2.6.34). Should I go and report it upstream myself or are you going to do that? cheers -- Stefan Ott http://www.ott.net/ You are not Grey Squirrel? -- 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/aanlktinwmcmyntilbd8uxwqtliiesrixgr5kidjly...@mail.gmail.com
Bug#587754: linux-image-2.6.32-5-686-bigmem: dpkg failed dependency problems prevent configuration of linux-image
This is not the complete output. You removed the important parts. Bastian I am sorry. This is my first post. Here is the complete output. I am not able to install any kernel. I hope this will help you. - Setting up linux-image-2.6.32-5-686-bigmem (2.6.32-15) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686-bigmem This kernel does not seem to support TuxOnIce user interface, skipping... initrd.img(/boot/initrd.img-2.6.32-5-686-bigmem ) points to /boot/initrd.img-2.6.32-5-686-bigmem (/boot/initrd.img-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. vmlinuz(/boot/vmlinuz-2.6.32-5-686-bigmem ) points to /boot/vmlinuz-2.6.32-5-686-bigmem (/boot/vmlinuz-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. Running update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.32-5-686-bigmem (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686-bigmem: linux-image-2.6-686-bigmem depends on linux-image-2.6.32-5-686-bigmem; however: Package linux-image-2.6.32-5-686-bigmem is not configured yet. dpkg: error processing linux-image-2.6-686-bigmem (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.32-5-686-bigmem linux-image-2.6-686-bigmem Setting up linux-image-2.6.32-5-686-bigmem (2.6.32-15) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686-bigmem This kernel does not seem to support TuxOnIce user interface, skipping... initrd.img(/boot/initrd.img-2.6.32-5-686-bigmem ) points to /boot/initrd.img-2.6.32-5-686-bigmem (/boot/initrd.img-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. vmlinuz(/boot/vmlinuz-2.6.32-5-686-bigmem ) points to /boot/vmlinuz-2.6.32-5-686-bigmem (/boot/vmlinuz-2.6.32-5-686-bigmem) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686-bigmem.postinst line 400. Running update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.32-5-686-bigmem (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686-bigmem: linux-image-2.6-686-bigmem depends on linux-image-2.6.32-5-686-bigmem; however: Package linux-image-2.6.32-5-686-bigmem is not configured yet. dpkg: error processing linux-image-2.6-686-bigmem (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.32-5-686-bigmem linux-image-2.6-686-bigmem regards, ravi -- http://www.imsc.res.in B. Raveendra Reddy | email: r...@imsc.res.in The Institute of Mathematical Sciences | phone: (91)44-2254 3222 Chennai 600 113 |(91)44-2448 7845 (Res) India | fax : (91)44-2254 1586 -- 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/alpine.deb.1.10.1007020953270.3...@as100.imsc.res.in
