Bug#600356: luks + usbkeyboard: cannot type passphrase
Package: linux-2.6 Version: 2.6.32-23 Severity: normal Tags: squeeze Hi, on one box I have problems with kernels newer than 2.6.26-2: I cannot type the luks passphrase to boot. I manually added usbcore, uhci_hcd, ehci_hcd and usbhid to /etc/initramfs-tools/modules to see if the modules were not loaded despite MODULES=most in /etc/initramfs-tools/initramfs.conf. The last lines I can read on the screen (please excuse typos) are: usb 2.6: new log speed USB device using ohce_hcd and address 4 usb 2-6: New USB device found, idVendor=946d, idProduct=c30a usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-6: Product: Logitech USB Keyboard usb 2-6: Manufacturer: Logitech usb 2-6: configuration #1 chosen from 1 choice usbcore: registerd new interface driver hiddev usbhid 2-3:1.9: couldn't find an interrupt endpoint input: PS/2+USB Mouse as /devices/pc:00/:00:02./usb2/2-5:1.0/input/input1 gerneric-usb 0003:1267:0213:0001: input,hidraw0: USB HID v1.11 Mouse [OS/2+USB Mouse] on usb-:00:02.0-5/input0 usbcore: registerred new interface driver usbhid usbhid: v2.6: v2.6:USB HID core driver Begin: Loading essential drivers ... done. Begin: Runnin /scritps/init-premount ... done. Begin: Mounting root file system ... Begin: runnin /scripts/local-top ... Begin: Loading md: raid1 personality registered for level 1 Success: loaded module raid1. done. [ md stuff for the raid ...] Unlocking the disk /dev/md2 (md2_crypt) Enter passpharse: yours Martin -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-23) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-3) ) #1 SMP Fri Sep 17 21:50:19 UTC 2010 -- 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/20101016112613.21479.65243.report...@liberty.vie.wuertele.net
Processed: tagging 600356
Processing commands for cont...@bugs.debian.org: tags 600356 - squeeze Bug #600356 [linux-2.6] luks + usbkeyboard: cannot type passphrase Removed tag(s) squeeze. thanks Stopping processing here. Please contact me if you need assistance. -- 600356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600356 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.128722893416902.transcr...@bugs.debian.org
Processed: reassign 600356 to initramfs-tools
Processing commands for cont...@bugs.debian.org: reassign 600356 initramfs-tools Bug #600356 [linux-2.6] luks + usbkeyboard: cannot type passphrase Bug reassigned from package 'linux-2.6' to 'initramfs-tools'. Bug No longer marked as found in versions 2.6.32-23. thanks Stopping processing here. Please contact me if you need assistance. -- 600356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600356 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.12872326993081.transcr...@bugs.debian.org
Bug#600356: Acknowledgement (luks + usbkeyboard: cannot type passphrase)
reassign 600356 linux-2.6 thanks I really think this is a bug in the kernel. I forcefully put all required modules in the initramfs to demonstrate that the bug is not in loading the modules but in the result. My guess is it has something todo with usbhid 2-3:1.9: couldn't find an interrupt endpoint but my knowledge of the kernel is quite limited. Yours Martin -- 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/20101016130311.gb4...@anguilla.debian.or.at
Processed: reassign 600356 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 600356 linux-2.6 2.6.32-23 Bug #600356 [initramfs-tools] luks + usbkeyboard: cannot type passphrase Bug reassigned from package 'initramfs-tools' to 'linux-2.6'. Bug #600356 [linux-2.6] luks + usbkeyboard: cannot type passphrase There is no source info for the package 'linux-2.6' at version '2.6.32-23' with architecture '' Unable to make a source version for version '2.6.32-23' Bug Marked as found in versions 2.6.32-23. End of message, stopping processing here. Please contact me if you need assistance. -- 600356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600356 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.128723451313834.transcr...@bugs.debian.org
Bug#599351: Caused by libdrm
I've done some testing on these bugs. After 599351, I moved back to
Linux 2.6.32-5-amd64, at which time I filed 599496 (because a very
similar problem occurred). I had installed libdrm{2,-intel1}
2.4.22~pre(something) and reverting back to 2.4.21-1~squeeze3 fixed the
problem.
I need to do some more testing to see if 2.4.22-1 will work properly,
and also whether 599351 disappears on 2.6.36-rc5 with the older libdrm
(or 2.4.22-1). Regardless of the results, neither of these bugs should
be closed, since the kernel should not allow processes to hang on syscalls
regardless of the data passed. Cloning 599351 to libdrm would be fine
with me.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
Bug#600384: dm-crypt: please backport support for plain64 IV
Package: linux-2.6 Version: 2.6.32-25 Severity: important Please backport commit 61afef614b013ee1b767cdd10325acae1db1f4d2 dm crypt: add plain64 iv from upstream. It should be a clean cherry-pick. Without it, Debian squeeze users might not be able to use dm-crypt volumes created on newer kernels using *-xts-plain64, nor will be able to create such volumes. Using plain for IVs on block devices with more than 2^32 blocks will cause the same IV to be used twice due to roll-over. This is not a good thing, although it might be not bad enough to matter much (or it could be a terrible problem. Someone who groks crypto for real would have to answer that). One cannot fix the plain IV to not warp at 2^32, or data after the roll-over point becomes unreadable on any already-existing devices. Thus, the only solution was to add a new IV (plain64). For devices smaller than 2^32 512 byte blocks, plain and plain64 are equivalent. Userspace and docs are already beggining to tell users to use aes-xts-plain64 and not aes-xts-plain. They will use them in their portable HDs, possibly on other distros, and then will not be able to read them back in squeeze. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32.23 (SMP w/8 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20101016165729.32565.38223.report...@khazad-dum2.khazad-dum.debian.net
Bug#583968: xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled
Patch seems to be http://article.gmane.org/gmane.comp.video.dri.devel/48108 Yes this patch works. It's been applied upstream since version 2.6.35. Could this be backported to squeeze's kernel? I have been using the patch on vanilla kernels 2.6.32, 2.6.33, 2.6.34 and 2.6.35 successfully. Thanks Andres -- 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/aanlktinyvavebjzxcbptw0a1otcov16t-4ejr4vot...@mail.gmail.com
Debian 5.0.6 Kernel 2.6.26-2-openvz-amd64 dmesg /var/log/messages normal?
Hi, we are running abount eigth HP Blade servers with the official openvz kernel from the debian repository. On this blades we are faced with a LOT of those messages. This messages are logged in dmesg and also in /var/log/messages. This hardware is useing the bnx2x chipset. The exactly same setup but running as vmware virtual machine is not logging those messages. The system is running stable but I would like to ask what this messages are kind of? Maybe a combination of bnx2x firmware and vzeth? Regards Mario Output of /var/log/messages: Oct 16 20:20:34 atlxvz30223 kernel: [215041.520059] [ cut here ] Oct 16 20:20:34 atlxvz30223 kernel: [215041.520064] WARNING: at net/core/dev.c:1440 skb_gso_segment+0x88/0x1ae() Oct 16 20:20:34 atlxvz30223 kernel: [215041.520067] Modules linked in: vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT ip_tables x_tables mptctl mptbase sg ipmi_devintf ipv6 bonding loop ipmi_si ipmi_msghandler usbhid hid psmouse hpilo ff_memless snd_pcm serio_raw pcspkr snd_timer snd soundcore snd_page_alloc container button bnx2x firmware_class libcrc32c zlib_inflate evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod cciss scsi_mod uhci_hcd ehci_hcd thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] Oct 16 20:20:34 atlxvz30223 kernel: [215041.520115] Pid: 0, comm: swapper Tainted: GW 2.6.26-2-openvz-amd64 #1 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520118] Oct 16 20:20:34 atlxvz30223 kernel: [215041.520119] Call Trace: Oct 16 20:20:34 atlxvz30223 kernel: [215041.520122] IRQ [80234e10] warn_on_slowpath+0x51/0x7a Oct 16 20:20:34 atlxvz30223 kernel: [215041.520143] [803cb4ec] nf_iterate+0x41/0x7d Oct 16 20:20:34 atlxvz30223 kernel: [215041.520149] [803b0c72] skb_gso_segment+0x88/0x1ae Oct 16 20:20:34 atlxvz30223 kernel: [215041.520155] [803b0f17] dev_hard_start_xmit+0x17f/0x28d Oct 16 20:20:34 atlxvz30223 kernel: [215041.520162] [803b3b44] dev_queue_xmit+0x1f0/0x2b4 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520169] [803d163d] ip_rcv_finish+0x3a1/0x3c4 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520175] [803d1c30] ip_rcv+0x26e/0x2c3 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520182] [803b08f5] netif_receive_skb+0x3d8/0x455 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520194] [a00db063] :bnx2x:bnx2x_rx_int+0xd13/0x1755 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520208] [803c5060] tc_ctl_tfilter+0x12b/0x4d4 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520231] [a00e8063] :bnx2x:bnx2x_poll+0xce/0x203 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520238] [8024abdd] hrtimer_get_next_event+0x9b/0xab Oct 16 20:20:34 atlxvz30223 kernel: [215041.520244] [803b2e2a] net_rx_action+0xab/0x1da Oct 16 20:20:34 atlxvz30223 kernel: [215041.520251] [80239fe5] __do_softirq+0x96/0x15c Oct 16 20:20:34 atlxvz30223 kernel: [215041.520259] [8020d40c] call_softirq+0x1c/0x28 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520264] [8020f58c] do_softirq+0x3c/0x81 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520268] [80239f09] irq_exit+0x81/0xc7 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520272] [8020f7ec] do_IRQ+0xb9/0xd9 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520278] [8020c5ad] ret_from_intr+0x0/0x19 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520281] EOI [a000c26d] :processor:acpi_idle_enter_bm+0x2b3/0x327 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520300] [80271eed] rcu_needs_cpu+0x32/0x41 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520307] [8039f514] cpuidle_idle_call+0x7a/0xb2 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520312] [8039f49a] cpuidle_idle_call+0x0/0xb2 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520316] [8020adb7] cpu_idle+0x8e/0xb8 Oct 16 20:20:34 atlxvz30223 kernel: [215041.520328] Oct 16 20:20:34 atlxvz30223 kernel: [215041.520331] ---[ end trace e56ecebdb1614647 ]---
Processed: tagging 583968, fixed 583968 in 2.6.35~rc6-1~experimental.1
Processing commands for cont...@bugs.debian.org: tags 583968 + fixed-upstream Bug #583968 [linux-2.6] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled Bug #588601 [linux-2.6] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. fixed 583968 2.6.35~rc6-1~experimental.1 Bug #583968 [linux-2.6] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled Bug #588601 [linux-2.6] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled There is no source info for the package 'linux-2.6' at version '2.6.35~rc6-1~experimental.1' with architecture '' Unable to make a source version for version '2.6.35~rc6-1~experimental.1' Bug Marked as fixed in versions 2.6.35~rc6-1~experimental.1. Bug Marked as fixed in versions 2.6.35~rc6-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 583968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583968 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.128725517322490.transcr...@bugs.debian.org
Processed: closing 597725
Processing commands for cont...@bugs.debian.org: close 597725 2.6.32-23 Bug#597725: linux-image-2.6.32-5-amd64: Errors resuming from suspend after upgrade from .32-3 to .32-5 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.6.32-23, send any further explanations to Jordan Metzmeier jor...@linuxgen.com thanks Stopping processing here. Please contact me if you need assistance. -- 597725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597725 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.128725548124136.transcr...@bugs.debian.org
Re: Debian 5.0.6 Kernel 2.6.26-2-openvz-amd64 dmesg /var/log/messages normal?
On Sat, 2010-10-16 at 20:37 +0200, Mario Kleinsasser wrote: Hi, we are running abount eigth HP Blade servers with the official openvz kernel from the debian repository. On this blades we are faced with a LOT of those messages. This messages are logged in dmesg and also in /var/log/messages. This hardware is useing the bnx2x chipset. The exactly same setup but running as vmware virtual machine is not logging those messages. The system is running stable but I would like to ask what this messages are kind of? Maybe a combination of bnx2x firmware and vzeth? This looks like the result of a combination of LRO (aka TPA) and bridging. LRO should be disabled automatically on interfaces that have bridging or forwarding enabled, but there is nothing to stop you enabling it again. 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#571035: [Upgraded to latest squeeze] Machine unbootable with ata_generic [Was: [Daily built 23. Aug 2010] Kernel freezes at boot]
Hello, We have updated kernel version in installer and I would like to ask you to give it a try. Please try http://people.debian.org/~joeyh/d-i/images/20101016-16:05/netboot/mini.iso Thanks in advance, -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/aanlktimeziprzjrkoc_t+t=xt_ytgzj-tjtnaybgj...@mail.gmail.com
Bug#600075: linux-image-2.6.32-5-686: Usb work led to the blocking other tasks
Package: linux-2.6 Version: 2.6.32-24 Severity: important Hi! This bug is present in 32bit kernel to. I test it on laptop Acer TravelMate 370. This kernel (...32-24) used for enable acceleration on i855GM video card. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-24) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Sep 30 03:56:23 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=UUID=fb7b94e1-1837-4fe1-b96d-82c1d51241bb ro quiet ** Not tainted ** Kernel log: [ 8587.946986] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 8598.072056] eth0: no IPv6 routers present [ 8632.305881] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 8632.370210] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1 [ 8632.416300] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1 [ 8642.772245] eth0: no IPv6 routers present [ 8732.308094] usb 2-1: new low speed USB device using uhci_hcd and address 2 [ 8732.476068] usb 2-1: New USB device found, idVendor=1d57, idProduct=32b9 [ 8732.476080] usb 2-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 8732.476090] usb 2-1: Product: 2.4G Receiver [ 8732.476390] usb 2-1: configuration #1 chosen from 1 choice [ 8733.003289] usbcore: registered new interface driver hiddev [ 8733.01] input: 2.4G Receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input8 [ 8733.021347] generic-usb 0003:1D57:32B9.0001: input,hidraw0: USB HID v1.10 Mouse [2.4G Receiver] on usb-:00:1d.0-1/input0 [ 8733.021395] usbcore: registered new interface driver usbhid [ 8733.025700] usbhid: v2.6:USB HID core driver [10790.948068] usb 1-2: new high speed USB device using ehci_hcd and address 3 [10791.083790] usb 1-2: New USB device found, idVendor=13fe, idProduct=3100 [10791.083802] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10791.083811] usb 1-2: Product: Patriot Memory [10791.083818] usb 1-2: Manufacturer: [10791.083825] usb 1-2: SerialNumber: 07A31D00174ED3B7 [10791.085183] usb 1-2: configuration #1 chosen from 1 choice [10791.202803] Initializing USB Mass Storage driver... [10791.203619] scsi2 : SCSI emulation for USB Mass Storage devices [10791.204384] usbcore: registered new interface driver usb-storage [10791.204388] USB Mass Storage support registered. [10791.210399] usb-storage: device found at 3 [10791.210403] usb-storage: waiting for device to settle before scanning [10796.208267] usb-storage: device scan complete [10796.234630] scsi 2:0:0:0: Direct-Access Patriot Memory PMAP PQ: 0 ANSI: 0 CCS [10796.853986] sd 2:0:0:0: [sdb] 31309824 512-byte logical blocks: (16.0 GB/14.9 GiB) [10796.857475] sd 2:0:0:0: [sdb] Write Protect is off [10796.857487] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 [10796.857495] sd 2:0:0:0: [sdb] Assuming drive cache: write through [10796.865591] sd 2:0:0:0: [sdb] Assuming drive cache: write through [10796.865604] sdb: sdb1 [10796.887278] sd 2:0:0:0: [sdb] Assuming drive cache: write through [10796.887293] sd 2:0:0:0: [sdb] Attached SCSI removable disk [10813.688647] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [11232.365266] usb 1-2: USB disconnect, address 3 [11257.592062] usb 1-2: new high speed USB device using ehci_hcd and address 4 [11257.727875] usb 1-2: New USB device found, idVendor=13fe, idProduct=3100 [11257.727887] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [11257.727896] usb 1-2: Product: Patriot Memory [11257.727903] usb 1-2: Manufacturer: [11257.727910] usb 1-2: SerialNumber: 07A31D00174ED3B7 [11257.731278] usb 1-2: configuration #1 chosen from 1 choice [11257.732254] scsi3 : SCSI emulation for USB Mass Storage devices [11257.732676] usb-storage: device found at 4 [11257.732683] usb-storage: waiting for device to settle before scanning [11262.734210] usb-storage: device scan complete [11262.760434] scsi 3:0:0:0: Direct-Access Patriot Memory PMAP PQ: 0 ANSI: 0 CCS [11263.408549] sd 3:0:0:0: [sdb] 31309824 512-byte logical blocks: (16.0 GB/14.9 GiB) [11263.412257] sd 3:0:0:0: [sdb] Write Protect is off [11263.412262] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00 [11263.412265] sd 3:0:0:0: [sdb] Assuming drive cache: write through [11263.419447] sd 3:0:0:0: [sdb] Assuming drive cache: write through [11263.419459] sdb: sdb1 [11263.440829] sd 3:0:0:0: [sdb] Assuming drive cache: write through [11263.440842] sd 3:0:0:0: [sdb] Attached SCSI removable disk [11273.964107] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [11521.016186] INFO: task dpkg:10383 blocked for more than 120 seconds. [11521.016197] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [11521.016206] dpkg D c2004d58 0 10383 10365 0x [11521.016221] ef264000 00200086 0002 c2004d58 c1419100 c1419100 0167 [11521.016241] ef2641bc c2008100
Re: Debian 5.0.6 Kernel 2.6.26-2-openvz-amd64 dmesg /var/log/messages normal?
On Sat, 2010-10-16 at 20:04 +0100, Ben Hutchings wrote: On Sat, 2010-10-16 at 20:37 +0200, Mario Kleinsasser wrote: Hi, we are running abount eigth HP Blade servers with the official openvz kernel from the debian repository. On this blades we are faced with a LOT of those messages. This messages are logged in dmesg and also in /var/log/messages. This hardware is useing the bnx2x chipset. The exactly same setup but running as vmware virtual machine is not logging those messages. The system is running stable but I would like to ask what this messages are kind of? Maybe a combination of bnx2x firmware and vzeth? This looks like the result of a combination of LRO (aka TPA) and bridging. LRO should be disabled automatically on interfaces that have bridging or forwarding enabled, but there is nothing to stop you enabling it again. Actually, that automatic behaviour was only added in Linux 2.6.27. So you need to disable LRO manually, either using ethtool or the bnx2x module parameter disable_tpa. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 583968
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 583968 + pending Bug #583968 [linux-2.6] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled Bug #588601 [linux-2.6] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled Added tag(s) pending. Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 583968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583968 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.12872734137765.transcr...@bugs.debian.org
Bug#600384: dm-crypt: please backport support for plain64 IV
On Sat, 2010-10-16 at 13:57 -0300, Henrique de Moraes Holschuh wrote: Package: linux-2.6 Version: 2.6.32-25 Severity: important Please backport commit 61afef614b013ee1b767cdd10325acae1db1f4d2 dm crypt: add plain64 iv from upstream. It should be a clean cherry-pick. Without it, Debian squeeze users might not be able to use dm-crypt volumes created on newer kernels using *-xts-plain64, nor will be able to create such volumes. Using plain for IVs on block devices with more than 2^32 blocks will cause the same IV to be used twice due to roll-over. This is not a good thing, although it might be not bad enough to matter much (or it could be a terrible problem. Someone who groks crypto for real would have to answer that). [...] The original author explains in https://partner-bugzilla.redhat.com/show_bug.cgi?id=600295: the plain IV restarts and opens device to watermarking attack (two sectors shares the same IV, you can manipulate with the second if you know content of the first). This seems to justify an update on the grounds of security, not to mention compatiblity. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 600384
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 600384 + pending Bug #600384 [linux-2.6] dm-crypt: please backport support for plain64 IV Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 600384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600384 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.128727426512161.transcr...@bugs.debian.org
Processed: tagging 600305
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 600305 + pending Bug #600305 [linux-image-2.6.32-5-amd64] linux-image-2.6.32-5-amd64: MacBookPro 7, 1 mcp89 sata link reset fails, no disks detected during install process Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 600305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600305 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.128727714623322.transcr...@bugs.debian.org
Bug#598493: nfs-exports does not work after reboot
On Fri, 2010-10-15 at 21:47 +0200, Petter Reinholdtsen wrote: [Oliver Joa] now it seems to work. I added the following line in /etc/init.d/nfs-kernel-server: ### BEGIN INIT INFO ... # Should-Start: bind9 ... ### END INIT INFO I believe it is better to use $named instead of bind9. To work with any local DNS service. :) Except that nothing appears to provide $named yet. 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#600299: linux-image-2.6.32-5-openvz-amd64: Openvz kernels appear to log unitialised memory to the console with log_buf_len=XX
On Fri, 2010-10-15 at 18:00 +0100, Tim Small wrote: Package: linux-2.6 Version: 2.6.32-23 Severity: normal When passing log_buf_len=2M to the kernel, the kernel logs nulls, or other aparently unitialised RAM to the console, and netconsole. Any increase in log_buf_len will result in disaster, since OpenVZ will continue using the old buffer pointer with the new length! Please can you test this patch, following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. --- a/kernel/printk.c +++ b/kernel/printk.c @@ -198,6 +198,9 @@ spin_lock_irqsave(logbuf_lock, flags); log_buf_len = size; log_buf = new_log_buf; +#ifdef CONFIG_VE + ve0.log_buf = log_buf; +#endif offset = start = min(con_start, log_start); dest_idx = 0; @@ -354,9 +357,9 @@ if (ve_log_buf == NULL) goto out; count = len; + spin_lock_irq(logbuf_lock); if (count ve_log_buf_len) count = ve_log_buf_len; - spin_lock_irq(logbuf_lock); if (count ve_logged_chars) count = ve_logged_chars; if (do_clear) signature.asc Description: This is a digitally signed message part
Processed: tagging 600299
Processing commands for cont...@bugs.debian.org: tags 600299 + moreinfo patch Bug #600299 [linux-2.6] linux-image-2.6.32-5-openvz-amd64: Openvz kernels appear to log unitialised memory to the console with log_buf_len=XX Added tag(s) moreinfo and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 600299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600299 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.128727868129229.transcr...@bugs.debian.org
Processed: tagging 599768
Processing commands for cont...@bugs.debian.org: tags 599768 - patch Bug #599768 [linux-2.6] linux-image-2.6.32-5-686: backlight control fails after resume from suspend (toshiba r700-155) Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 599768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599768 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.128727873529660.transcr...@bugs.debian.org
Bug#600286: linux-image-2.6.32-5-amd64: atl1c driver hangs after NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out
On Fri, 2010-10-15 at 16:34 +0200, Niels Möller wrote:
Package: linux-2.6
Version: 2.6.32-23
Severity: important
*** Please type your report below this line ***
My wired network interface stops working (not able to transmit any
packets, I think, but it might be reception which is broken. Anyway,
ping to hosts on the local network results in a No route to host error,
which means that sending or receiving arp packets fail).
[...]
It has hanged in this way twice today, each time after I did two things
which might be related:
1. I sent some large packets (tcp over ipv4 over ethernet) of size up to
roughly 2 bytes and at a rate close to the links capacity of
100Mbit/s. One such packet, displayed by tcpdump:
13:58:15.872214 00:26:9e:b3:2f:3b (oui Unknown) 00:11:25:85:b0:1a (oui
Unknown), ethertype IPv4 (0x0800), length 22790: 192.168.1.135.47058
192.168.1.108.4711: Flags [.], seq 1079380:1102104, ack 1, win 32, options
[nop,nop,TS val 19304579 ecr 1030215], length 22724
I have no idea why the kernel sent such large packets. According to
ifconfig eth0, the MTU is 1500 bytes. Is it supposed to work like
that, or is this another bug?
[...]
This driver and hardware implement TCP Segmentation Offload (TSO), which
means the kernel can provide oversized pseudo-packets that are turned
into multiple packets on the wire.
I did notice a later bug fix to this driver which might possibly address
the bug you're seeing. Please can you test the attached patch,
following the instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
From: Jie Yang jie.y...@atheros.com
Date: Tue, 27 Oct 2009 22:31:19 -0700
Subject: [PATCH] atl1c: duplicate atl1c_get_tpd
commit 678b77e265f6d66f1e68f3d095841c44ba5ab112 upstream.
remove duplicate atl1c_get_tpd, it may cause hardware to send wrong packets.
Signed-off-by: Jie Yang jie.y...@atheros.com
Signed-off-by: David S. Miller da...@davemloft.net
---
drivers/net/atl1c/atl1c_main.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/net/atl1c/atl1c_main.c b/drivers/net/atl1c/atl1c_main.c
index 1372e9a..3b8801a 100644
--- a/drivers/net/atl1c/atl1c_main.c
+++ b/drivers/net/atl1c/atl1c_main.c
@@ -1981,8 +1981,6 @@ static void atl1c_tx_map(struct atl1c_adapter *adapter,
else {
use_tpd = atl1c_get_tpd(adapter, type);
memcpy(use_tpd, tpd, sizeof(struct atl1c_tpd_desc));
- use_tpd = atl1c_get_tpd(adapter, type);
- memcpy(use_tpd, tpd, sizeof(struct atl1c_tpd_desc));
}
buffer_info = atl1c_get_tx_buffer(adapter, use_tpd);
buffer_info-length = buf_len - mapped_len;
--
1.7.1
signature.asc
Description: This is a digitally signed message part
Processed: tagging 600286
Processing commands for cont...@bugs.debian.org: tags 600286 + moreinfo patch Bug #600286 [linux-2.6] linux-image-2.6.32-5-amd64: atl1c driver hangs after NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out Added tag(s) moreinfo and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 600286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600286 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.1287279515606.transcr...@bugs.debian.org
Bug#600423: linux-2.6: too many open files
Package: linux-2.6 Severity: serious We will hit a build failure soon as the total number of patch applications and removals approaches 1024. Ben. Forwarded Message From: Thorsten Glaser t...@mirbsd.de To: Ben Hutchings b...@decadent.org.uk Cc: Bastian Blank wa...@mirbsd.org Subject: linux-2.6: too many open files Date: Wed, 13 Oct 2010 19:13:24 + (UTC) Hi, I'm trying to build the sid kernel plus smarenka’s patches which you reverted and ran into “too many open files”: patches.py has try: fp = file(os.path.join(home, 'series', i)) ret.append(PatchSeries(i, home, fp)) except IOError: pass In IPython, I get: In [41]: fp Out[41]: open file '/home/tg/linux-2.6-2.6.32/debian/patches/series/24+m68k.1', mode 'r' at 0x8e005a0 In [42]: PatchSeries(i, home, fp) --- IOError Traceback (most recent call last) /home/tg/linux-2.6-2.6.32/ipython console in module() /home/tg/linux-2.6-2.6.32/debian/lib/python/debian_linux/patches.pyc in __init__(self, name, root, fp) IOError: [Errno 24] Too many open files: '/home/tg/linux-2.6-2.6.32/debian/patches/bugfix/m68k/fp/0030-Update-for-m68k-Add-support-for-EARLY_PRINTK-on-MVM.patch' I found out that ulimit -n defaulting to 1024 is too small to handle this because that code insists on keeping all file pointers open. Just so you know… bye, //mirabilos -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt signature.asc Description: This is a digitally signed message part
Processed: tagging 600423
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 600423 + pending Bug #600423 [linux-2.6] linux-2.6: too many open files Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 600423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600423 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.12872812508036.transcr...@bugs.debian.org
Bug#598493: nfs-exports does not work after reboot
[Ben Hutchings] Except that nothing appears to provide $named yet. How strange. At least powerdns and bind should provide it. See /etc/insserv.conf*. Happy hacking, -- Petter Reinholdtsen -- 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/20101017043247.gc23...@login2.uio.no
Bug#600430: linux-2.6: genorig.py does not handle 4-part tarball versions (e.g. 2.6.7.8)
Source: linux-2.6 Version: 2.6.32-23 Severity: normal Since several years back, kernel.org has provided linux tarballs with both 3 part (e.g. 2.6.35) and 4 part (e.g. 2.6.35.7) version numbers in their filenames. But if genorig.py is run with a 4-part versioned tarball such as linux-2.6.35.7.tar.bz2 it will barf about not recognizing the filename. Confusingly, the script source code supports a file naming with an extra dashed revision, as convention NOT used by kernel.org, even though the instructions clearly say users should use the script only with the upstream tarballs. Please fix this or change the instructions in README.source to warn users that they MUST download a base tarball and a patch (e.g. linux-2.6.35.tar.bz2 and patch-2.6.25.6.whatever) and pass those to the script. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32jbj3.4-47 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Chroot: squeeze chroot running on a lenny system -- 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/20101017043935.8899.83193.report...@jbj3.i.jbohm.dk
Bug#600432: linux-2.6: debian/bin/genorig.py not marked as executable
Source: linux-2.6 Version: 2.6.32-23 Severity: normal In the specified squeeze version of this package (2.6.32-23), debian/README.source tells the user to run debian/bin/genorig.py. Unfortunately, that file is not marked as executable in the freshly unpacked source package, requiring the user to go off-script and manually chmod ug+x the file before proceeding with the instructions in README.source. P.S. If some of this is from another package used in preparing the kernel source package, README.source fails to mention that key fact, so I will assume that bugs in README.source and the scripts it references belong to the source package containing said README.source file. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32jbj3.4-47 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Chroot: This is a chroot squeeze environment on a lenny system -- 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/20101017042824.8555.79083.report...@jbj3.i.jbohm.dk
Re: Debian 5.0.6 Kernel 2.6.26-2-openvz-amd64 dmesg /var/log/messages normal?
On Sun, Oct 17, 2010 at 1:47 AM, Ben Hutchings b...@decadent.org.uk wrote: On Sat, 2010-10-16 at 20:04 +0100, Ben Hutchings wrote: On Sat, 2010-10-16 at 20:37 +0200, Mario Kleinsasser wrote: Hi, we are running abount eigth HP Blade servers with the official openvz kernel from the debian repository. On this blades we are faced with a LOT of those messages. This messages are logged in dmesg and also in /var/log/messages. This hardware is useing the bnx2x chipset. The exactly same setup but running as vmware virtual machine is not logging those messages. The system is running stable but I would like to ask what this messages are kind of? Maybe a combination of bnx2x firmware and vzeth? This looks like the result of a combination of LRO (aka TPA) and bridging. LRO should be disabled automatically on interfaces that have bridging or forwarding enabled, but there is nothing to stop you enabling it again. Actually, that automatic behaviour was only added in Linux 2.6.27. So you need to disable LRO manually, either using ethtool or the bnx2x module parameter disable_tpa. Ben. Many thanks for your answer! I will set the module parameter within the next few days. If it resolvs the problem I will give feedback here. Thats why I like the Debian community! Mario. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
