Bug#677164: [3.2.17-1 - 3.2.18-1 regression] Wacom tablet in Thinkpad x220t not working
notfound 677164 3.2.17-1 found 677164 linux-2.6/3.2.18-1 found 677164 linux-2.6/3.2.19-1 found 677164 linux-2.6/3.4.1-1~experimental.1 # regression severity 677164 important quit Hi Nils, Nils Kanning wrote: the wacom tablet in my Thinkpad x220t stopped working after the update of linux-image-3.2.0-2-amd64 from version 3.2.17 to 3.2.18 (and 3.2.19). The same problem also occurs with linux-image-3.4-trunk-amd64 (version 3.4.1-1~experimental.1). With these kernels I experience the following behavior: lsusb recognizes my tablet as Bus 002 Device 004: ID 056a:00e6 Wacom Co., Ltd lsusb -t gives Port 5: Dev 4, If 0, Class=HID, Driver=, 12M instead of the expected Port 5: Dev 4, If 0, Class=HID, Driver=wacom, 12M and consequently the device does not work. Oh, dear. Thanks for reporting it. Please attach full dmesg output from booting an affected kernel. Many thanks, Jonathan -- 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/20120612010340.GA3259@burratino
Processed: Re: [3.2.17-1 - 3.2.18-1 regression] Wacom tablet in Thinkpad x220t not working
Processing commands for cont...@bugs.debian.org: notfound 677164 3.2.17-1 Bug #677164 [linux-2.6] linux-image-3.2.0-2-amd64: Wacom tablet in Thinkpad x220t not working after update from version 3.2.17 to 3.2.18 (and above) There is no source info for the package 'linux-2.6' at version '3.2.17-1' with architecture '' Unable to make a source version for version '3.2.17-1' No longer marked as found in versions 3.2.17-1. found 677164 linux-2.6/3.2.18-1 Bug #677164 [linux-2.6] linux-image-3.2.0-2-amd64: Wacom tablet in Thinkpad x220t not working after update from version 3.2.17 to 3.2.18 (and above) Marked as found in versions linux-2.6/3.2.18-1. found 677164 linux-2.6/3.2.19-1 Bug #677164 [linux-2.6] linux-image-3.2.0-2-amd64: Wacom tablet in Thinkpad x220t not working after update from version 3.2.17 to 3.2.18 (and above) Marked as found in versions linux-2.6/3.2.19-1. found 677164 linux-2.6/3.4.1-1~experimental.1 Bug #677164 [linux-2.6] linux-image-3.2.0-2-amd64: Wacom tablet in Thinkpad x220t not working after update from version 3.2.17 to 3.2.18 (and above) Marked as found in versions linux-2.6/3.4.1-1~experimental.1. # regression severity 677164 important Bug #677164 [linux-2.6] linux-image-3.2.0-2-amd64: Wacom tablet in Thinkpad x220t not working after update from version 3.2.17 to 3.2.18 (and above) Severity set to 'important' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 677164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677164 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.13394630341785.transcr...@bugs.debian.org
Bug#677173: linux-image-3.2.0-2-amd64: after some time, the USB keyboard no longer works
Package: linux-2.6 Version: 3.2.19-1 Severity: normal I have a USB keyboard attached to my laptop, and I use it as the main keyboard. I was using it, and suddenly it no longer worked at all (for instance, xev didn't report any event). The device was still seen by /lib/udev/findkeyboards and by lsusb. And the laptop keyboard was still working. I had to unplug the keyboard and plug it in again so that keys worked again (I also had to log out and log in again to make special keys work, due to some X window bug I think). I've had this problem twice: now and a week ago. Never before, AFAIK. -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.19-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Fri Jun 1 17:49:08 UTC 2012 ** Command line: root=/dev/mapper/xvii-root ro quiet ** Not tainted ** Kernel log: [ 14.021601] [drm] No driver support for vblank timestamp query. [ 14.280735] [drm] nouveau :01:00.0: allocated 1920x1200 fb: 0x31, bo 8801173ca400 [ 14.280811] fbcon: nouveaufb (fb0) is primary device [ 14.350522] dell_wmi: Received unknown WMI event (0x11) [ 14.350911] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 15.635824] Console: switching to colour frame buffer device 180x56 [ 15.638782] fb0: nouveaufb frame buffer device [ 15.638784] drm: registered panic notifier [ 15.638790] [drm] Initialized nouveau 0.0.16 20090420 for :01:00.0 on minor 0 [ 15.659407] dell_wmi: Received unknown WMI event (0x11) [ 15.673207] Linux media interface: v0.10 [ 15.685220] Linux video capture interface: v2.00 [ 15.696289] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_0.3M (0c45:63f8) [ 15.710556] input: Laptop_Integrated_Webcam_0.3M as /devices/pci:00/:00:1a.7/usb1/1-6/1-6:1.0/input/input12 [ 15.710642] usbcore: registered new interface driver uvcvideo [ 15.710643] USB Video Class driver (1.1.1) [ 16.083118] snd_hda_intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 16.083183] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X [ 16.083214] snd_hda_intel :00:1b.0: setting latency timer to 64 [ 16.125200] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input13 [ 16.133558] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input14 [ 16.134192] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 16.134256] input: HDA Intel Line-out as /devices/pci:00/:00:1b.0/sound/card0/input16 [ 16.134322] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input17 [ 18.103663] EXT3-fs (dm-1): using internal journal [ 18.827458] loop: module loaded [ 19.740703] Adding 9928700k swap on /dev/mapper/xvii-swap_1. Priority:-1 extents:1 across:9928700k [ 45.752208] RPC: Registered named UNIX socket transport module. [ 45.752211] RPC: Registered udp transport module. [ 45.752212] RPC: Registered tcp transport module. [ 45.752214] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 45.844166] FS-Cache: Loaded [ 45.941845] FS-Cache: Netfs 'nfs' registered for caching [ 45.961493] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 46.428063] fuse init (API version 7.17) [ 49.421265] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input18 [ 61.767196] Bluetooth: Core ver 2.16 [ 61.767214] NET: Registered protocol family 31 [ 61.767216] Bluetooth: HCI device and connection manager initialized [ 61.767219] Bluetooth: HCI socket layer initialized [ 61.767221] Bluetooth: L2CAP socket layer initialized [ 61.767225] Bluetooth: SCO socket layer initialized [ 61.819402] Bluetooth: RFCOMM TTY layer initialized [ 61.819407] Bluetooth: RFCOMM socket layer initialized [ 61.819408] Bluetooth: RFCOMM ver 1.11 [ 62.319024] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 62.319027] Bluetooth: BNEP filters: protocol multicast [ 62.358534] lp: driver loaded but no devices found [ 62.528985] ppdev: user-space parallel port driver [ 67.500114] ip_tables: (C) 2000-2006 Netfilter Core Team [ 69.942284] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 69.996104] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 69.996701] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 71.684922] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 71.684927] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 71.685425] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 72.730118] device eth0 entered promiscuous mode [ 81.944042] eth0: no IPv6 routers present [ 82.731861] device eth0 left promiscuous mode [ 87.840697] colord[3180]: segfault at 8 ip 0040bc6d sp 7fff52e38460 error 4 in colord[40+2] [ 105.682555] dell_wmi: Received unknown WMI event (0x11) [ 136.408062] CE: hpet increased min_delta_ns to 20113 nsec [99913.293662] usb 8-3.3: USB disconnect, device number 4
Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
Hi, Vincent Lefevre wrote: I have a USB keyboard attached to my laptop, and I use it as the main keyboard. I was using it, and suddenly it no longer worked at all (for instance, xev didn't report any event). The device was still seen by /lib/udev/findkeyboards and by lsusb. And the laptop keyboard was still working. I had to unplug the keyboard and plug it in again so that keys worked again (I also had to log out and log in again to make special keys work, due to some X window bug I think). I've had this problem twice: now and a week ago. Never before, AFAIK. Peculiar. Do you have a kernel log from when this happened? Can you attach lsusb -v output describing your keyboard in its normal state? Thanks for writing and sorry for the trouble, Jonathan -- 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/20120612023929.GB3259@burratino
Bug#677164: [3.2.17-1 - 3.2.18-1 regression] Wacom tablet in Thinkpad x220t not working
Nils Kanning wrote: After going back to version 3.2.17 of linux-image-3.2.0-2-amd64 everything works again. The tablet also works with kernel 3.4.2 from kernel.org. Ah, very useful. If you apply the seven patches features/all/wacom/0020-Input-wacom-add-basic-Intuos5-support.patch features/all/wacom/0021-Input-wacom-add-Intuos5-Touch-Ring-ExpressKey-suppor.patch features/all/wacom/0022-Input-wacom-add-Intuos5-Touch-Ring-LED-support.patch features/all/wacom/0023-Input-wacom-add-Intuos5-multitouch-sensor-support.patch features/all/wacom/0024-Input-wacom-retrieve-maximum-number-of-touch-points.patch features/all/wacom/0025-Input-wacom-add-0xE5-MT-device-support.patch features/all/wacom/0026-Input-wacom-return-proper-error-if-usb_get_extra_des.patch (aka 9fee619505bd Input: wacom - add basic Intuos5 support f860e581fd47 Input: wacom - add Intuos5 Touch Ring/ExpressKey support 9b5b95dd516a Input: wacom - add Intuos5 Touch Ring LED support ae584ca47328 Input: wacom - add Intuos5 multitouch sensor support f393ee2b814e Input: wacom - retrieve maximum number of touch points 1963518b9b1b Input: wacom - add 0xE5 (MT device) support a882c932a628 Input: wacom - return proper error if usb_get_extra_descriptor() fails ) to the upstream source, does that reproduce the problem, too? -- 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/20120612024854.GC3259@burratino
Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST
Eugen Dedu wrote: Here it is: another freeze during resume, with kernel 3.3 too. Thanks for the quick feedback. (As a reminder to myself, the message is BUG: unable to handle kernel paging request at fff(lens flare) IP: [810514c7] kthread_data+0x7/0xc PGD 1607067 PUD 1608067 PMD 0 Oops: [#2] SMP CPU 0 [...] Code: 3f 48 c1 e5 03 48 c1 e0 06 48 8d b0 50 54 40 81 29 ee e8 62 c0 00 00 81 4b 14 00 00 00 04 41 59 5b 5d c3 48 8b 87 a0 02 00 00 48 8b 40 f8 c8 48 3b 3d 95 43 72 00 75 08 0f bf 87 6a 06 00 00 [...] Fixing recursive fault but reboot is needed! Call trace involves trying to handle a page fault in led_trigger_unregister, called by power_supply_unregister, called by acpi_battery_notify. The first oops looks similar but scrolled off the screen. This is a 3.3.y kernel with virtualbox modules loaded.) Ideas for moving forward: - please attach: - full dmesg output from a normal boot - acpidump output - see Documentation/power/basic-pm-debugging.txt from [1] or the kernel-doc-3.2 package. Does suspend-to-disk work? Do pm_test modes work? Are any warnings shown at suspend time that can be captured using a serial console or netconsole with no_console_suspend? Does unloading the battery module before suspend avoid trouble? Hope that helps, Jonathan [1] http://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt -- 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/20120612040259.GB8366@burratino
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux_3.2.20-1.debian.tar.xz linux_3.2.20-1.dsc linux_3.2.20.orig.tar.xz This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:19:40, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon (running on host franck.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/e1sdxtw-0008dc...@franck.debian.org
Bug#664767: Brcmsmac driver woes, possible regression?
El 2012-06-10 a las 17:49 -0500, Jonathan Nieder escribió: This kernel was running fine the whole Saturday but today I had another reconnect (network-manager asked for the password which I had to reconfirm). I'm attaching the full syslog for this pacthed kernel. The reconnect happened at night (22:00 or so). Thanks. You first reported this against 3.2.9-1. Were you using some earlier 3.2.y kernel without trouble before? Mmmm, this is something I can still try (an earlier working kernel). As per my comment #167 [1], candidates could be lower versions starting from 3.2.4-1, which according to the snapshot [2] could be: 3.2.2-1 (source: linux-2.6 3.2.2-1) 3.2.1-2 (source: linux-2.6 3.2.1-2) 3.2.1-1 (source: linux-2.6 3.2.1-1) Will do on these these -time permitting- and report here. Thanks for reminding me this second line of investigation :-) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767#167 [2] http://snapshot.debian.org/binary/linux-image-3.2.0-1-686-pae/ Gretings, -- Camaleón -- 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/20120611063014.ga4...@stt008.linux.site
Processing of linux_3.2.20-1_multi.changes
linux_3.2.20-1_multi.changes uploaded successfully to localhost along with the files: linux_3.2.20-1.dsc linux_3.2.20.orig.tar.xz linux_3.2.20-1.debian.tar.xz linux-support-3.2.0-2_3.2.20-1_all.deb linux-source-3.2_3.2.20-1_all.deb linux-doc-3.2_3.2.20-1_all.deb linux-manual-3.2_3.2.20-1_all.deb Greetings, Your Debian queue daemon (running on host franck.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/e1sdyhm-0002ov...@franck.debian.org
linux_3.2.20-1_multi.changes is NEW
linux-doc-3.2_3.2.20-1_all.deb to main/l/linux/linux-doc-3.2_3.2.20-1_all.deb linux-manual-3.2_3.2.20-1_all.deb to main/l/linux/linux-manual-3.2_3.2.20-1_all.deb linux-source-3.2_3.2.20-1_all.deb to main/l/linux/linux-source-3.2_3.2.20-1_all.deb linux-support-3.2.0-2_3.2.20-1_all.deb to main/l/linux/linux-support-3.2.0-2_3.2.20-1_all.deb (new) linux_3.2.20-1.debian.tar.xz optional kernel (new) linux_3.2.20-1.dsc optional kernel (new) linux_3.2.20.orig.tar.xz optional kernel Changes: linux (3.2.20-1) unstable; urgency=low . * The Confused? You Won't Be release . * New upstream stable update: http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.20 - cifs: fix oops while traversing open file list (try #4) - mm/fork: fix overflow in vma length when copying mmap on clone - mm: fix faulty initialization in vmalloc_init() - x86, amd, xen: Avoid NULL pointer paravirt references - ext4: force ro mount if ext4_setup_super() fails - ext4: disallow hard-linked directory in ext4_lookup - ext4: add missing save_error_info() to ext4_error() - ALSA: usb-audio: fix rate_list memory leak - Bluetooth: btusb: typo in Broadcom SoftSailing id (Closes: #674565) - ipv4: Do not use dead fib_info entries. - ipv4: fix the rcu race between free_fib_info and ip_route_output_slow - l2tp: fix oops in L2TP IP sockets for connect() AF_UNSPEC case - btree: fix tree corruption in btree_get_prev() - asix: allow full size 8021Q frames to be received (Closes: #676545) - ext4: don't trash state flags in EXT4_IOC_SETFLAGS - ext4: fix the free blocks calculation for ext3 file systems w/ uninit_bg . [ Ben Hutchings ] * Rename source package to 'linux' (Closes: #636010) * Convert source package format to 3.0 (quilt) - Convert patch system to quilt, except for the 'orig' patch series - Use xz compression for upstream and Debian tarballs - README.source: Update description of patch system to match current usage - linux-patch-debian: Remove; it is no longer necessary for GPL compliance and does not work with our current patch management * linux-image: Change package name for bugs to 'src:linux' (Closes: #644198) * DFSG: video: Remove nvidiafb and rivafb, which include apparently obfuscated code (Closes: #383481, #609615). The nouveau driver supports all the same hardware, aside from RIVA 128 (NV3). * udeb: Add udf-modules containing UDF filesystem module (Closes: #613972) * [mipsel/loongson2f] linux-image: Recommend libc6-loongson2f (Closes: #629410) * Build-Depend on kmod or module-init-tools, not just the latter * test-patches: Recognise the rt featureset automatically * udeb: Build-Depend on kernel-wedge = 2.84; this allows us to list modules as required even if they are built-in in some configurations * filter: Allow to create sk-unattached filters * proc: Backport hidepid mount option from Linux 3.4 (Closes: #669028) * NFSv4: Reduce the footprint of the idmapper (Closes: #657078) * [i386] thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE (Closes: #676360) * linux-source: Add single patch for each featureset * [x86] Enable CRASH_DUMP, PROC_VMCORE (Closes: #623177) * media/dvb: Enable DVB_DDBRIDGE as module (Closes: #676952) * net: sock: validate data_len before allocating skb in sock_alloc_send_pskb() (CVE-2012-2136) * macvtap: zerocopy: fix offset calculation when building skb * macvtap: zerocopy: fix truesize underestimation * macvtap: zerocopy: put page when fail to get all requested user pages * macvtap: zerocopy: set SKBTX_DEV_ZEROCOPY only when skb is built successfully * macvtap: zerocopy: validate vectors before building skb (CVE-2012-2119) * KVM: Fix buffer overflow in kvm_set_irq() (CVE-2012-2137) . [ Bastian Blank ] * [s390/s390x,s390x/s390x] Build debugging symbols. Override entries for your package: linux-doc-3.2_3.2.20-1_all.deb - optional doc linux-manual-3.2_3.2.20-1_all.deb - optional doc linux-source-3.2_3.2.20-1_all.deb - optional kernel linux-support-3.2.0-2_3.2.20-1_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 383481 609615 613972 623177 629410 636010 644198 657078 669028 674565 676360 676545 676952 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- 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/e1sdyql-0002xw...@franck.debian.org
Bug#677016: linux-image-3.3.0-trunk-amd64: Freeze with error message upon resume
Package: linux-2.6 Version: 3.3.6-1~experimental.1 Severity: important Dear Maintainer, Very often (each 2-10 times) kernel freezes with an error message upon resuming from suspend to ram. Here is the message: kobject_add_internal failed for BATO with -EEXIST, don't try to register things with the same name in the same directory 3.2 version of the kernel freezes at suspend too, but as far as I noticed with another error message, something like infinite recursion. I can get it if needed. 3.1 freezes too. In fact, I have been having freezes at suspend since 3.0 or 2.6.39, while before suspend was working perfectly. Thank you, Eugen Dedu http://eugen.dedu.free.fr -- Package-specific info: ** Version: Linux version 3.3.0-trunk-amd64 (Debian 3.3.6-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Fri May 18 14:52:13 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.3.0-trunk-amd64 root=UUID=0efdb302-9d8b-4eeb-9102-f18c3fa8d2f0 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [5.181589] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input13 [5.181658] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input14 [5.181726] input: HDA Intel Dock Line Out as /devices/pci:00/:00:1b.0/sound/card0/input15 [5.328972] usb 3-1: New USB device found, idVendor=0a5c, idProduct=4500 [5.328977] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.328980] usb 3-1: Product: BCM2046B1 [5.328983] usb 3-1: Manufacturer: Broadcom [5.332042] hub 3-1:1.0: USB hub found [5.333963] hub 3-1:1.0: 3 ports detected [5.399113] dell_wmi: Received unknown WMI event (0x11) [5.432910] EXT4-fs (sda1): re-mounted. Opts: (null) [5.479747] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [5.516848] loop: module loaded [5.576036] usb 5-1: new full-speed USB device number 2 using uhci_hcd [5.755781] usb 5-1: New USB device found, idVendor=0a5c, idProduct=5800 [5.755784] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [5.755786] usb 5-1: Product: 5880 [5.755788] usb 5-1: Manufacturer: Broadcom Corp [5.755790] usb 5-1: SerialNumber: 0123456789ABCD [5.755884] usb 5-1: config 0 descriptor?? [5.779928] WARNING! power/level is deprecated; use power/control instead [6.008035] usb 6-2: new low-speed USB device number 2 using uhci_hcd [6.181162] usb 6-2: New USB device found, idVendor=1c4f, idProduct=0003 [6.181166] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.181168] usb 6-2: Product: Usb Mouse [6.181170] usb 6-2: Manufacturer: SIGMACHIP [6.214501] input: SIGMACHIP Usb Mouse as /devices/pci:00/:00:1d.0/usb6/6-2/6-2:1.0/input/input16 [6.214955] generic-usb 0003:1C4F:0003.0001: input,hidraw0: USB HID v1.10 Mouse [SIGMACHIP Usb Mouse] on usb-:00:1d.0-2/input0 [6.215191] usbcore: registered new interface driver usbhid [6.215193] usbhid: USB HID core driver [6.257976] usb 3-1.1: new full-speed USB device number 3 using uhci_hcd [6.379983] usb 3-1.1: New USB device found, idVendor=413c, idProduct=8157 [6.379987] usb 3-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [6.387223] input: HID 413c:8157 as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0/input/input17 [6.387385] generic-usb 0003:413C:8157.0002: input,hidraw1: USB HID v1.11 Keyboard [HID 413c:8157] on usb-:00:1a.0-1.1/input0 [6.461990] usb 3-1.2: new full-speed USB device number 4 using uhci_hcd [6.586981] usb 3-1.2: New USB device found, idVendor=413c, idProduct=8158 [6.586984] usb 3-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [6.595258] input: HID 413c:8158 as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0/input/input18 [6.595376] generic-usb 0003:413C:8158.0003: input,hidraw2: USB HID v1.11 Mouse [HID 413c:8158] on usb-:00:1a.0-1.2/input0 [6.721433] vboxdrv: Found 2 processor cores. [6.722037] vboxdrv: fAsync=0 offMin=0x1ac offMax=0x5188 [6.722098] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [6.722100] vboxdrv: Successfully loaded version 4.1.16_Debian (interface 0x0019). [6.786523] vboxpci: IOMMU not found (not registered) [6.945982] usb 3-1.3: new full-speed USB device number 5 using uhci_hcd [7.078974] usb 3-1.3: New USB device found, idVendor=413c, idProduct=8156 [7.078979] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [7.078982] usb 3-1.3: Product: Dell Wireless 370 Bluetooth Mini-card [7.078985] usb 3-1.3: Manufacturer: Dell Computer Corp [7.101675] Bluetooth: Core ver 2.16 [7.101700] NET: Registered protocol family 31 [7.101701] Bluetooth: HCI device and connection manager initialized [7.101704] Bluetooth: HCI socket layer
sid kernel slower than squeeze
Hi, I'm curious if there are debug settings enabled in the unstable kernel which might cause it to run slower than released kernels, and if so, what those settings might be so I can recompile and test, to eliminate it. I'm running on a Dell Inspiron 630m laptop, with 1gig of RAM, running the Gnome3 desktop. It is a pretty fresh sid install, upgraded from a Squeeze CD install. I haven't installed any fancy video drivers it's pretty stock. When I run the sid 3.2.x kernel, light browsing and typing in a terminal window can keep the CPU at 50% consistently. Sometimes it hovers around 90%. If I run the old Squeeze kernel, 2.6.32, which is still on here from the upgrade, it can idle down to about 12% to maybe 25%. Strangely, there is no one process that is taking up so much power. It seems to be a kernel level thing. The extra cpu activity really causes the machine to run hot, so much so that it is unpleasant to use. I don't know why just changing the kernel can affect this. I'm running stock squeeze and sid kernels. If I can provide debug information to help track this down, please let me know. Thanks, - Chris -- 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/20120611072053.ga8...@foursquare.net
Bug#677049: [trivial] please don't hardcode /bin/sleep path
Package: initramfs-tools Version: 0.106 Severity: wishlist Two scripts in initramfs-tools currently hardcodes path to sleep as /bin/sleep, because busybox sleep (which were used when busybox is in used) didn't accept fractional secounds. Fractional secounds are accepted by busybox sleep since version 1:1.18.5-1, so it is safe now to stop hardcoding the path. Thanks, /mjt -- 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/20120611102105.32626.49417.reportbug@gandalf.local
Bug#676360: [Xen-devel] [PATCH] thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE\
- Original Message - On Thu, Jun 07, 2012 at 11:00:33PM +0200, Andrea Arcangeli wrote: In the x86 32bit PAE CONFIG_TRANSPARENT_HUGEPAGE=y case while holding the mmap_sem for reading, cmpxchg8b cannot be used to read pmd contents under Xen. So instead of dealing only with consistent pmdvals in pmd_none_or_trans_huge_or_clear_bad() (which would be conceptually simpler) we let pmd_none_or_trans_huge_or_clear_bad() deal with pmdvals where the low 32bit and high 32bit could be inconsistent (to avoid having to use cmpxchg8b). nods The only guarantee we get from pmd_read_atomic is that if the low part of the pmd was found null, the high part will be null too (so the pmd will be considered unstable). And if the low part of the pmd is found stable later, then it means the whole pmd was read atomically (because after a pmd is stable, neither MADV_DONTNEED nor page faults can alter it anymore, and we read the high part after the low part). In the 32bit PAE x86 case, it is enough to read the low part of the pmdval atomically to declare the pmd as stable and that's true for THP and no THP, furthermore in the THP case we also have a barrier() that will prevent any inconsistent pmdvals to be cached by a later re-read of the *pmd. Nice. Andrew, any chane you could test this patch on the affected Xen hypervisors? Was it as easy to reproduce this on a RHEL5 (U1?) hypervisor or is it really only on Linode and Amazon EC2? Originally, I was able to reproduce the issue easily with a RHEL5 host. Now, with this patch it's fixed. Drew -- 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/4728e392-7130-4967-aa79-8da12f929...@zmail17.collab.prod.int.phx2.redhat.com
Processed: reassign 573483 to src:linux-tools, reassign 548021 to src:linux-tools
Processing commands for cont...@bugs.debian.org: reassign 573483 src:linux-tools Bug #573483 [linux-kbuild-2.6] linux-kbuild-2.6: please upload 2.6.33 to experimental Bug reassigned from package 'linux-kbuild-2.6' to 'src:linux-tools'. Ignoring request to alter found versions of bug #573483 to the same values previously set Ignoring request to alter fixed versions of bug #573483 to the same values previously set reassign 548021 src:linux-tools Bug #548021 [linux-kbuild-2.6] linux-kbuild-2.6: needs building instructions Bug reassigned from package 'linux-kbuild-2.6' to 'src:linux-tools'. Ignoring request to alter found versions of bug #548021 to the same values previously set Ignoring request to alter fixed versions of bug #548021 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 548021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548021 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 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.1339410933389.transcr...@bugs.debian.org
Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST
Hi, Eugen Dedu wrote: Very often (each 2-10 times) kernel freezes with an error message upon resuming from suspend to ram. Here is the message: kobject_add_internal failed for BATO with -EEXIST, don't try to register things with the same name in the same directory Please attach a log or photograph of this in context. 3.2 version of the kernel freezes at suspend too, but as far as I noticed with another error message, something like infinite recursion. I can get it if needed. This would be useful, too. 3.1 freezes too. In fact, I have been having freezes at suspend since 3.0 or 2.6.39, while before suspend was working perfectly. Good to know. We don't support kernels other than 2.6.32.y, 3.2.y, and 3.4.y at the moment (and 3.2.y is most interesting since it is what will be part of wheezy), but it's useful to know when the problem first arrived. Hope that helps, Jonathan -- 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/2012063124.GA21302@burratino
Processed: Re: resume failure: kobject_add_internal failed for BAT0 with -EEXIST
Processing commands for cont...@bugs.debian.org: # regression severity 677016 important Bug #677016 [linux-2.6] linux-image-3.3.0-trunk-amd64: Freeze with error message upon resume Ignoring request to change severity of Bug 677016 to the same value. End of message, stopping processing here. Please contact me if you need assistance. -- 677016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677016 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.133941491321569.transcr...@bugs.debian.org
Re: sid kernel slower than squeeze
On Mon, 2012-06-11 at 03:20 -0400, Chris Frey wrote: Hi, I'm curious if there are debug settings enabled in the unstable kernel which might cause it to run slower than released kernels, and if so, what those settings might be so I can recompile and test, to eliminate it. No. I'm running on a Dell Inspiron 630m laptop, with 1gig of RAM, running the Gnome3 desktop. It is a pretty fresh sid install, upgraded from a Squeeze CD install. I haven't installed any fancy video drivers it's pretty stock. When I run the sid 3.2.x kernel, light browsing and typing in a terminal window can keep the CPU at 50% consistently. Sometimes it hovers around 90%. If I run the old Squeeze kernel, 2.6.32, which is still on here from the upgrade, it can idle down to about 12% to maybe 25%. Strangely, there is no one process that is taking up so much power. It seems to be a kernel level thing. There have been some changes in CPU accounting recently which some people say cause the CPU usage to be overstated when the system is mostly idle. But that wouldn't explain: The extra cpu activity really causes the machine to run hot, so much so that it is unpleasant to use. I don't know why just changing the kernel can affect this. I'm running stock squeeze and sid kernels. If I can provide debug information to help track this down, please let me know. Get a list of CPU usage according to standard CPU accounting: $ top -b -n 1 top.log Get more detail by running perf (from linux-tools-3.2): # perf record -a sleep 10 # perf report --stdio perf.report Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part
Bug#677016: resume failure: kobject_add_internal failed for BAT0 with -EEXIST
On 11/06/12 13:31, Jonathan Nieder wrote: Hi, Eugen Dedu wrote: Very often (each 2-10 times) kernel freezes with an error message upon resuming from suspend to ram. Here is the message: kobject_add_internal failed for BATO with -EEXIST, don't try to register things with the same name in the same directory Please attach a log or photograph of this in context. All the screen was black, and the above message at the top. 3.2 version of the kernel freezes at suspend too, but as far as I noticed with another error message, something like infinite recursion. I can get it if needed. This would be useful, too. I will give it to you this evening, I have it on my camera at home. 3.1 freezes too. In fact, I have been having freezes at suspend since 3.0 or 2.6.39, while before suspend was working perfectly. Good to know. We don't support kernels other than 2.6.32.y, 3.2.y, and 3.4.y at the moment (and 3.2.y is most interesting since it is what will be part of wheezy), but it's useful to know when the problem first arrived. If you think that the above two informations are not sufficiently informative, I will make tests with older kernels to see which one introduced the problem. Just tell me. -- Eugen -- 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/4fd5f1c5.5030...@pu-pm.univ-fcomte.fr
Bug#636697: initramfs-tools: no way to include library modules for libraries installed in multiarch path
Hi, Michal Suchanek wrote (05 Aug 2011 12:08:37 GMT) : At the very least the libc nss modules are required in intramfs to get dns lookup for netbooting. Splashscreen solutions like plymouth might need some of the graphics rendering modules. I think it would be useful to mark as blocked by this bug the ones that demonstrate the (very real!) need for a good solution to the described problem. This simple additional function in hook-functions should allow initramfs hooks to install loadable modules effortlessly. I suggest attaching a patch against the current initramfs-tools package, making it clear if whether it was actually tested OK, and then tags + patch. (I would understand if the package maintainers did not feel should allow to be very confidence inspiring.) -- 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/85ehpmq80s@boum.org
Bug#677049: [trivial] please don't hardcode /bin/sleep path
On Mon, Jun 11, 2012 at 14:21:05 +0400, Michael Tokarev wrote: Package: initramfs-tools Version: 0.106 Severity: wishlist Two scripts in initramfs-tools currently hardcodes path to sleep as /bin/sleep, because busybox sleep (which were used when busybox is in used) didn't accept fractional secounds. Fractional secounds are accepted by busybox sleep since version 1:1.18.5-1, so it is safe now to stop hardcoding the path. It's not safe without Breaks on older busybox (or Depends on the newer one). Cheers, Julien -- 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/20120611154524.ga32...@radis.cristau.org
Bug#677049: [trivial] please don't hardcode /bin/sleep path
On 11.06.2012 19:45, Julien Cristau wrote: On Mon, Jun 11, 2012 at 14:21:05 +0400, Michael Tokarev wrote: Two scripts in initramfs-tools currently hardcodes path to sleep as /bin/sleep, because busybox sleep (which were used when busybox is in used) didn't accept fractional secounds. Fractional secounds are accepted by busybox sleep since version 1:1.18.5-1, so it is safe now to stop hardcoding the path. It's not safe without Breaks on older busybox (or Depends on the newer one). Yes it's not safe, I know. I tried to understand whenever a versioned Recommends does the trick (there's already a versioned recommends in initramfs-tools against busybox), and, later, what does a versioned recommends _does_, or a Breaks is needed instead. So from a trivial change in one package it turned into a bit less trivial question about the package relationship. /mjt -- 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/4fd61a23.4080...@msgid.tls.msk.ru
linux_3.2.20-1_multi.changes ACCEPTED into unstable
Accepted: linux-doc-3.2_3.2.20-1_all.deb to main/l/linux/linux-doc-3.2_3.2.20-1_all.deb linux-manual-3.2_3.2.20-1_all.deb to main/l/linux/linux-manual-3.2_3.2.20-1_all.deb linux-source-3.2_3.2.20-1_all.deb to main/l/linux/linux-source-3.2_3.2.20-1_all.deb linux-support-3.2.0-2_3.2.20-1_all.deb to main/l/linux/linux-support-3.2.0-2_3.2.20-1_all.deb linux_3.2.20-1.debian.tar.xz to main/l/linux/linux_3.2.20-1.debian.tar.xz linux_3.2.20-1.dsc to main/l/linux/linux_3.2.20-1.dsc linux_3.2.20.orig.tar.xz to main/l/linux/linux_3.2.20.orig.tar.xz Changes: linux (3.2.20-1) unstable; urgency=low . * The Confused? You Won't Be release . * New upstream stable update: http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.20 - cifs: fix oops while traversing open file list (try #4) - mm/fork: fix overflow in vma length when copying mmap on clone - mm: fix faulty initialization in vmalloc_init() - x86, amd, xen: Avoid NULL pointer paravirt references - ext4: force ro mount if ext4_setup_super() fails - ext4: disallow hard-linked directory in ext4_lookup - ext4: add missing save_error_info() to ext4_error() - ALSA: usb-audio: fix rate_list memory leak - Bluetooth: btusb: typo in Broadcom SoftSailing id (Closes: #674565) - ipv4: Do not use dead fib_info entries. - ipv4: fix the rcu race between free_fib_info and ip_route_output_slow - l2tp: fix oops in L2TP IP sockets for connect() AF_UNSPEC case - btree: fix tree corruption in btree_get_prev() - asix: allow full size 8021Q frames to be received (Closes: #676545) - ext4: don't trash state flags in EXT4_IOC_SETFLAGS - ext4: fix the free blocks calculation for ext3 file systems w/ uninit_bg . [ Ben Hutchings ] * Rename source package to 'linux' (Closes: #636010) * Convert source package format to 3.0 (quilt) - Convert patch system to quilt, except for the 'orig' patch series - Use xz compression for upstream and Debian tarballs - README.source: Update description of patch system to match current usage - linux-patch-debian: Remove; it is no longer necessary for GPL compliance and does not work with our current patch management * linux-image: Change package name for bugs to 'src:linux' (Closes: #644198) * DFSG: video: Remove nvidiafb and rivafb, which include apparently obfuscated code (Closes: #383481, #609615). The nouveau driver supports all the same hardware, aside from RIVA 128 (NV3). * udeb: Add udf-modules containing UDF filesystem module (Closes: #613972) * [mipsel/loongson2f] linux-image: Recommend libc6-loongson2f (Closes: #629410) * Build-Depend on kmod or module-init-tools, not just the latter * test-patches: Recognise the rt featureset automatically * udeb: Build-Depend on kernel-wedge = 2.84; this allows us to list modules as required even if they are built-in in some configurations * filter: Allow to create sk-unattached filters * proc: Backport hidepid mount option from Linux 3.4 (Closes: #669028) * NFSv4: Reduce the footprint of the idmapper (Closes: #657078) * [i386] thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE (Closes: #676360) * linux-source: Add single patch for each featureset * [x86] Enable CRASH_DUMP, PROC_VMCORE (Closes: #623177) * media/dvb: Enable DVB_DDBRIDGE as module (Closes: #676952) * net: sock: validate data_len before allocating skb in sock_alloc_send_pskb() (CVE-2012-2136) * macvtap: zerocopy: fix offset calculation when building skb * macvtap: zerocopy: fix truesize underestimation * macvtap: zerocopy: put page when fail to get all requested user pages * macvtap: zerocopy: set SKBTX_DEV_ZEROCOPY only when skb is built successfully * macvtap: zerocopy: validate vectors before building skb (CVE-2012-2119) * KVM: Fix buffer overflow in kvm_set_irq() (CVE-2012-2137) . [ Bastian Blank ] * [s390/s390x,s390x/s390x] Build debugging symbols. Override entries for your package: linux-doc-3.2_3.2.20-1_all.deb - optional doc linux-manual-3.2_3.2.20-1_all.deb - optional doc linux-source-3.2_3.2.20-1_all.deb - optional kernel linux-support-3.2.0-2_3.2.20-1_all.deb - optional devel linux_3.2.20-1.dsc - source kernel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 383481 609615 613972 623177 629410 636010 644198 657078 669028 674565 676360 676545 676952 Thank you for your contribution to Debian. -- 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/e1se7j2-0007ar...@franck.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 #594149 (http://bugs.debian.org/594149) # Bug title: linux-image-2.6.32-5-amd64: Lid switch correct every other time; suspend every other lid close; Samsung N150-11 netbook # * http://bugzilla.kernel.org/show_bug.cgi?id=17081 # * remote status changed: REJECTED - REOPENED # * remote resolution changed: INSUFFICIENT-DATA - (?) usertags 594149 - status-REJECTED resolution-INSUFFICIENT-DATA usertags 594149 + status-REOPENED # remote status report for #627372 (http://bugs.debian.org/627372) # Bug title: linux-image-2.6.38-2-686: Console turns black during boot # * https://bugs.freedesktop.org/show_bug.cgi?id=44156 # * remote status changed: NEEDINFO - ASSIGNED usertags 627372 - status-NEEDINFO usertags 627372 + status-ASSIGNED # remote status report for #627372 (http://bugs.debian.org/627372) # Bug title: linux-image-2.6.38-2-686: Console turns black during boot # * https://bugs.freedesktop.org/show_bug.cgi?id=44156 # * remote status changed: NEEDINFO - ASSIGNED usertags 627372 - status-NEEDINFO usertags 627372 + status-ASSIGNED 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/20120611181101.1288.35086.btsl...@busoni.debian.org
Bug#676360: [Xen-devel] [PATCH] thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE\
Hi, On Mon, Jun 11, 2012 at 03:27:38PM -0400, Konrad Rzeszutek Wilk wrote: Nice. Andrew, any chane you could test this patch on the affected Xen hypervisors? Was it as easy to reproduce this on a RHEL5 (U1?) hypervisor or is it really only on Linode and Amazon EC2? Originally, I was able to reproduce the issue easily with a RHEL5 host. Now, with this patch it's fixed. OK, so Tested-by: Andrew Jones.. and from my perspective it looks good - so Acked-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com Thanks for testing and reviews. Andrea, any chance you can respin this patch and send it to Linus for 3.5 please? Andrew merged it in -mm last Friday, so I would expect it to go upstream soon through the -mm flow (I assume everyone has been rightfully waiting a bit of time for testing and reviews to be sure). Andrea -- 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/20120611194113.gh3...@redhat.com
Bug#676360: [Xen-devel] [PATCH] thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE\
Nice. Andrew, any chane you could test this patch on the affected Xen hypervisors? Was it as easy to reproduce this on a RHEL5 (U1?) hypervisor or is it really only on Linode and Amazon EC2? Originally, I was able to reproduce the issue easily with a RHEL5 host. Now, with this patch it's fixed. OK, so Tested-by: Andrew Jones.. and from my perspective it looks good - so Acked-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com Andrea, any chance you can respin this patch and send it to Linus for 3.5 please? -- 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/20120611192738.gm14...@phenom.dumpdata.com
Processed: Re: linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module)
Processing commands for cont...@bugs.debian.org: reassign 674565 src:linux-2.6 linux-2.6/3.2.18-1 Bug #674565 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module) Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. No longer marked as found in versions 3.2.18-1. No longer marked as fixed in versions linux/3.2.20-1. Bug #674565 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6] linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module) Marked as found in versions linux-2.6/3.2.18-1. fixed 674565 linux/3.2.20-1 Bug #674565 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6] linux-image-3.2.0-2-amd64: Bluetooth activation failed (btusb module) Marked as fixed in versions linux/3.2.20-1. End of message, stopping processing here. Please contact me if you need assistance. -- 674565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674565 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.133944725624721.transcr...@bugs.debian.org
Processed: Re: linux-image-3.2.0-0.bpo.2-686-pae: ASIX usb net driver broken with 8021Q frames
Processing commands for cont...@bugs.debian.org: reassign 676545 src:linux linux-2.6/3.2.18-1 Bug #676545 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] linux-image-3.2.0-0.bpo.2-686-pae: ASIX usb net driver broken with 8021Q frames Bug reassigned from package 'linux-2.6' to 'src:linux'. Warning: Unknown package 'src:linux' Warning: Unknown package 'src:linux' No longer marked as found in versions 3.2.18-1~bpo60+1. Warning: Unknown package 'src:linux' Warning: Unknown package 'src:linux' No longer marked as fixed in versions linux/3.2.20-1. Warning: Unknown package 'src:linux' Bug #676545 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] linux-image-3.2.0-0.bpo.2-686-pae: ASIX usb net driver broken with 8021Q frames Warning: Unknown package 'src:linux' Marked as found in versions linux-2.6/3.2.18-1. Warning: Unknown package 'src:linux' fixed 676545 linux/3.2.20-1 Bug #676545 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] linux-image-3.2.0-0.bpo.2-686-pae: ASIX usb net driver broken with 8021Q frames Warning: Unknown package 'src:linux' Marked as fixed in versions linux/3.2.20-1. Warning: Unknown package 'src:linux' End of message, stopping processing here. Please contact me if you need assistance. -- 676545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676545 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.133944731025129.transcr...@bugs.debian.org
Processed: Re: [linux-2.6] Please rename source to linux
Processing commands for cont...@bugs.debian.org: reassign 636010 src:linux linux-2.6/3.0.0-1 Bug #636010 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] [linux-2.6] Please rename source to linux Bug reassigned from package 'linux-2.6' to 'src:linux'. Warning: Unknown package 'src:linux' Warning: Unknown package 'src:linux' Ignoring request to alter found versions of bug #636010 to the same values previously set Warning: Unknown package 'src:linux' Warning: Unknown package 'src:linux' No longer marked as fixed in versions linux/3.2.20-1. Warning: Unknown package 'src:linux' Bug #636010 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] [linux-2.6] Please rename source to linux Warning: Unknown package 'src:linux' Marked as found in versions linux-2.6/3.0.0-1. Warning: Unknown package 'src:linux' fixed 636010 linux/3.2.20-1 Bug #636010 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] [linux-2.6] Please rename source to linux Warning: Unknown package 'src:linux' Marked as fixed in versions linux/3.2.20-1. Warning: Unknown package 'src:linux' End of message, stopping processing here. Please contact me if you need assistance. -- 636010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636010 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.133944737025421.transcr...@bugs.debian.org
Re: sid kernel slower than squeeze
Hi Ben, Thanks for the tips. In watching the uptime on the 3.2.0 machine, I've noticed that it's like a wave, on an approximate cycle of a minute, sometimes more, where the load dips to 0.16 or so, and then quickly spikes to 0.50 and sometimes 0.80, with very little load otherwise. Below is the top output from the machine, running kernel 3.2.0. You can see that the trailing load number is about 0.57. The lowest I've seen that number is 0.49. On the 2.6.32 kernel, after waiting about 15 minutes, it drops to about 0.10, and would probably go lower in time. top - 17:16:51 up 34 min, 5 users, load average: 0.32, 0.48, 0.57 Tasks: 114 total, 1 running, 113 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.8 us, 0.8 sy, 0.0 ni, 81.3 id, 16.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 1025856 total, 632808 used, 393048 free,22924 buffers KiB Swap: 530428 total,0 used, 530428 free, 448052 cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 3669 root 20 0 4492 1216 956 R 6.2 0.1 0:00.01 top 1 root 20 0 2256 704 604 S 0.0 0.1 0:00.98 init 2 root 20 0 000 S 0.0 0.0 0:00.00 kthreadd 3 root 20 0 000 S 0.0 0.0 0:00.18 ksoftirqd/0 6 root rt 0 000 S 0.0 0.0 0:00.00 migration/0 7 root rt 0 000 S 0.0 0.0 0:00.00 watchdog/0 8 root 0 -20 000 S 0.0 0.0 0:00.00 cpuset 9 root 0 -20 000 S 0.0 0.0 0:00.00 khelper 10 root 20 0 000 S 0.0 0.0 0:00.00 kdevtmpfs 11 root 0 -20 000 S 0.0 0.0 0:00.00 netns 12 root 20 0 000 S 0.0 0.0 0:00.00 sync_supers 13 root 20 0 000 S 0.0 0.0 0:00.00 bdi-default 14 root 0 -20 000 S 0.0 0.0 0:00.00 kintegrityd 15 root 0 -20 000 S 0.0 0.0 0:00.00 kblockd 17 root 20 0 000 S 0.0 0.0 0:00.00 khungtaskd 18 root 20 0 000 S 0.0 0.0 0:00.00 kswapd0 19 root 25 5 000 S 0.0 0.0 0:00.00 ksmd 20 root 39 19 000 S 0.0 0.0 0:00.00 khugepaged 21 root 20 0 000 S 0.0 0.0 0:00.00 fsnotify_mark 22 root 0 -20 000 S 0.0 0.0 0:00.00 crypto 25 root 20 0 000 S 0.0 0.0 0:00.80 kworker/0:2 99 root 0 -20 000 S 0.0 0.0 0:00.00 firewire 100 root 20 0 000 S 0.0 0.0 0:00.00 khubd 137 root 0 -20 000 S 0.0 0.0 0:00.00 ata_sff 138 root 20 0 000 S 0.0 0.0 0:00.00 kworker/u:1 147 root 20 0 000 S 0.0 0.0 0:00.01 scsi_eh_0 148 root 20 0 000 S 0.0 0.0 0:00.20 scsi_eh_1 149 root 20 0 000 S 0.0 0.0 0:00.02 kworker/u:2 179 root 20 0 000 S 0.0 0.0 0:00.08 kjournald 305 root 20 0 2908 1468 732 S 0.0 0.1 0:00.11 udevd 412 root 20 0 2904 1204 460 S 0.0 0.1 0:00.00 udevd 413 root 20 0 2904 1152 412 S 0.0 0.1 0:00.00 udevd 445 root 0 -20 000 S 0.0 0.0 0:00.00 kpsmoused 447 root 0 -20 000 S 0.0 0.0 0:00.00 cfg80211 450 root 0 -20 000 S 0.0 0.0 0:00.00 r852 452 root 0 -20 000 S 0.0 0.0 0:00.00 kmemstick 453 root 20 0 000 S 0.0 0.0 0:00.00 r592_io 486 root 0 -20 000 S 0.0 0.0 0:00.00 hd-audio0 1801 root 20 0 28048 1632 1028 S 0.0 0.2 0:00.15 rsyslogd 1836 root 20 0 000 S 0.0 0.0 0:00.03 flush-8:0 1837 messageb 20 0 3812 1856 880 S 0.0 0.2 0:00.81 dbus-daemon 1862 root 20 0 1852 596 484 S 0.0 0.1 0:00.00 acpid 1887 root 20 0 26640 5424 4556 S 0.0 0.5 0:00.45 NetworkManager 1917 root 20 0 24276 3928 2768 S 0.0 0.4 0:00.79 polkitd 1921 root 20 0 6848 2696 2196 S 0.0 0.3 0:00.03 modem-manager 1924 root 20 0 5792 2568 2184 S 0.0 0.3 0:00.08 wpa_supplicant 1932 root 20 0 17984 2852 2416 S 0.0 0.3 0:00.02 gdm3 1961 root 20 0 5164 3036 1312 S 0.0 0.3 0:00.00 dhclient 1965 avahi 20 0 3124 1440 1208 S 0.0 0.1 0:00.07 avahi-daemon 1966 avahi 20 0 3124 428 216 S 0.0 0.0 0:00.00 avahi-daemon 1985 root 20 0 20308 3720 3088 S 0.0 0.4 0:00.03 gdm-simple-slav 1994 root 20 0 4456 1360 1164 S 0.0 0.1 0:00.00 bluetoothd 2004 root 10 -10 000 S 0.0 0.0 0:00.00 krfcommd 2049 root 20 0 58724 8828 4520 S 0.0 0.9 0:03.46 Xorg 2051 root 20 0 3812 924 744 S 0.0 0.1 0:00.00 cron 2233 root 20 0 6440 1592 1152 S 0.0 0.2 0:00.00 sshd
Bug#677157: initramfs-tools: root=/dev/nfs mostly useless due to BOOT=local being defined in initramfs.conf
Package: initramfs-tools Version: 0.106 Severity: normal Tags: patch Specifying root=/dev/nfs doesn't really do anything without also either specifying boot=nfs or changing BOOT= in initramfs.conf: /dev/nfs) [ -z ${BOOT} ] BOOT=nfs ;; At which point, you could just as well not specify root=/dev/nfs at all. This breaks the historical method for network booting with nfsroot with the kernel arguments: ip=dhcp root=/dev/nfs I guess the check to make sure BOOT wasn't already set was changed in order to fix putting boot= anywhere in the boot commandline: http://bugs.debian.org/453294 But it seems to me the correct thing to do in that case would be to specify boot=live after root=/dev/nfs... since the order of the argument processing matters, rather than preferring the result of one argument over another. Alternately/Additionally, why is BOOT=local defined in initramfs.conf at all? What about only setting BOOT=local if $BOOT is undefined, after all the argument processing is done: diff --git a/conf/initramfs.conf b/conf/initramfs.conf index abc231b..995d455 100644 --- a/conf/initramfs.conf +++ b/conf/initramfs.conf @@ -53,7 +53,7 @@ COMPRESS=gzip # nfs - Boot using an NFS drive as the root of the drive. # -BOOT=local +#BOOT=local # # DEVICE: ... diff --git a/init b/init index cbd22e2..7e54a73 100755 --- a/init +++ b/init @@ -186,6 +186,11 @@ for x in $(cat /proc/cmdline); do esac done +if [ -z ${BOOT} ]; then + # Default to BOOT=local if no boot script defined. + BOOT=local +fi + if [ -n ${noresume} ]; then export noresume unset resume live well, vagrant -- 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/20120611222455.GV2630@talon.fglan
Bug#676453: linux-image-3.2.0-2-amd64: pmount hangs while mounting an external USB disk partition
Here is more information as requested by Ben Hutchings: This is after executing pmount /dev/sdb1 backups and sync echo l /proc/sysrq-trigger: [168534.533936] SysRq : Show backtrace of all active CPUs [168534.533942] sending NMI to all CPUs: [168534.533947] NMI backtrace for cpu 0 [168534.533950] CPU 0 [168534.533952] Modules linked in: nls_utf8 udf usb_storage xhci_hcd tun acpi_cpufreq mperf cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_userspace parport_pc ppdev lp parport bnep rfcomm uinput deflate zlib_deflate ctr twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common camellia serpent blowfish_generic blowfish_x86_64 blowfish_common cast5 des_generic cbc cryptd aes_x86_64 aes_generic xcbc rmd160 sha512_generic sha256_generic sha1_ssse3 sha1_generic hmac crypto_null af_key fuse nf_conntrack_ftp nf_conntrack loop dm_crypt dm_mod uvcvideo videodev v4l2_compat_ioctl32 media btusb bluetooth usbhid hid snd_hda_codec_hdmi nvidia(P) snd_hda_codec_conexant arc4 snd_hda_intel mxm_wmi snd_hda_codec snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hwdep snd_pcm_oss sr_mod snd_mixer_oss psmouse snd_seq cdrom i7core_edac snd_pcm snd_seq_device evdev pcspkr serio_raw edac_core iwlwifi thinkpad_acpi battery ac power_supply video snd_page_alloc nvram i2c_i801 ma c80211 snd_timer iTCO_wdt firewire_ohci iTCO_vendor_support cfg80211 ehci_hcd wmi snd sdhci_pci firewire_core sdhci button crc_itu_t e1000e rfkill processor usbcore mmc_core soundcore i2c_core usb_common ext4 crc16 jbd2 mbcache sd_mod crc_t10dif ahci libahci libata scsi_mod thermal thermal_sys [last unloaded: xhci_hcd] [168534.534077] [168534.534081] Pid: 31334, comm: mount Tainted: P O 3.2.0-2-amd64 #1 LENOVO 4389A97/4389A97 [168534.534087] RIP: 0010:[810bc23e] [810bc23e] put_page_testzero+0x7/0x13 [168534.534098] RSP: 0018:880093b479e0 EFLAGS: 0202 [168534.534101] RAX: 0003 RBX: eaf4f200 RCX: 880038d97e98 [168534.534105] RDX: 880038d97e98 RSI: RDI: eaf4f200 [168534.534109] RBP: R08: eaf4f200 R09: 0022 [168534.534112] R10: 88012e2bee20 R11: 88012e2bee20 R12: 880050cd7298 [168534.534116] R13: 880050cd7158 R14: aea85701 R15: 880050cd7080 [168534.534121] FS: () GS:880137c0(0063) knlGS:f7534750 [168534.534124] CS: 0010 DS: 002b ES: 002b CR0: 8005003b [168534.534128] CR2: f730cfe0 CR3: 98245000 CR4: 06f0 [168534.534131] DR0: DR1: DR2: [168534.534135] DR3: DR6: 0ff0 DR7: 0400 [168534.534139] Process mount (pid: 31334, threadinfo 880093b46000, task 88012e2bee20) [168534.534142] Stack: [168534.534145] 810bcb25 eaf4f200 8111aeca 0001 [168534.534152] 15d50ae0 0004 880093b46000 15d50ae0 [168534.534158] eaf4f200 880050cd7298 880050cd7080 [168534.534164] Call Trace: [168534.534169] [810bcb25] ? put_page+0x18/0x27 [168534.534176] [8111aeca] ? __find_get_block_slow+0x120/0x136 [168534.534182] [8111b9a9] ? __find_get_block+0x9b/0x17b [168534.534188] [810b316a] ? find_lock_page+0x29/0x4a [168534.534193] [8111b854] ? init_page_buffers.isra.16+0x3c/0x8e [168534.534197] [8111bb57] ? __getblk+0xce/0x212 [168534.534202] [8111bcd7] ? __bread+0x6/0x67 [168534.534210] [a1108c3c] ? udf_read_tagged+0x29/0x113 [udf] [168534.534218] [a1107422] ? udf_check_anchor_block+0x6e/0xf5 [udf] [168534.534225] [a11075a2] ? udf_scan_anchors+0xf9/0x158 [udf] [168534.534233] [a110781c] ? udf_load_vrs+0x21b/0x2b9 [udf] [168534.534240] [a11078ba] ? udf_load_vrs+0x2b9/0x2b9 [udf] [168534.534247] [a1107a8a] ? udf_fill_super+0x1d0/0x4d6 [udf] [168534.534257] [81120d95] ? set_blocksize+0x2f/0x94 [168534.534263] [810fa8f1] ? mount_bdev+0x13a/0x187 [168534.534268] [810fb142] ? mount_fs+0x61/0x147 [168534.534275] [8110e166] ? vfs_kern_mount+0x5f/0x99 [168534.534281] [8110e550] ? do_kern_mount+0x49/0xd8 [168534.534285] [8110fbc1] ? do_mount+0x660/0x6c6 [168534.534290] [8110f4d3] ? copy_mount_options+0xc3/0x126 [168534.534296] [8112fa37] ? compat_sys_mount+0x1b1/0x1ec [168534.534303] [8134c3f0] ? sysenter_dispatch+0x7/0x2e [168534.534306] Code: 66 90 66 90 c3 9c 58 66 66 90 66 90 48 89 c2 fa 66 66 90 66 66 90 48 89 d0 c3 f0 80 0f 20 c3 f0 80 0f 40 c3 8b 47 1c f0 ff 4f 1c 0f 94 c0 84 c0 0f 95 c0 0f b6 c0 c3 48 89 f8 48 89 f7 f0 80 60 [168534.534353] Call Trace: [168534.534357] [810bcb25] ? put_page+0x18/0x27 [168534.534362] [8111aeca] ? __find_get_block_slow+0x120/0x136 [168534.534367] [8111b9a9] ?