Bug#633722: task jsvc:7903 blocked for more than 120 seconds
Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-35 Hi, the system keep logging messages like the following one. Is this something I should report here? Is there any action I should do? The process jsvc is a tomcat55 instance, the one shipped by Debian. Thanks, Giuseppe Jul 13 08:52:46 agenzia-f07 kernel: [432397.142910] INFO: task jsvc:7903 blocked for more than 120 seconds. Jul 13 08:52:46 agenzia-f07 kernel: [432397.142946] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jul 13 08:52:46 agenzia-f07 kernel: [432397.142990] jsvc D 0 7903 7894 0x0002 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143023] 88007f3654c0 0082 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143073] 88000382fc00 7c7a1c78 f9e0 880037aebfd8 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143123] 00015780 00015780 880037844db0 8800378450a8 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143173] Call Trace: Jul 13 08:52:46 agenzia-f07 kernel: [432397.143204] [a015626b] ? dm_table_unplug_all+0x3b/0x8f [dm_mod] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143236] [8110d294] ? sync_buffer+0x0/0x40 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143264] [812f736a] ? io_schedule+0x73/0xb7 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143290] [8110d2cf] ? sync_buffer+0x3b/0x40 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143317] [812f7755] ? __wait_on_bit_lock+0x3f/0x84 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143345] [8110d294] ? sync_buffer+0x0/0x40 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143371] [812f7805] ? out_of_line_wait_on_bit_lock+0x6b/0x77 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143401] [81064c7c] ? wake_bit_function+0x0/0x23 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143430] [a0174030] ? do_get_write_access+0x6f/0x40f [jbd] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143460] [8110c86a] ? __getblk+0x26/0x29a Jul 13 08:52:46 agenzia-f07 kernel: [432397.143486] [810678d6] ? hrtimer_try_to_cancel+0x3a/0x43 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143516] [a01743f2] ? journal_get_write_access+0x22/0x33 [jbd] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143549] [a01953b3] ? __ext3_journal_get_write_access+0x1e/0x47 [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143596] [a018919d] ? ext3_reserve_inode_write+0x3e/0x75 [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143641] [a01891f5] ? ext3_mark_inode_dirty+0x21/0x3c [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143672] [a0189347] ? ext3_dirty_inode+0x63/0x7b [ext3] Jul 13 08:52:46 agenzia-f07 kernel: [432397.143701] [811075f5] ? __mark_inode_dirty+0x25/0x14a Jul 13 08:52:46 agenzia-f07 kernel: [432397.143730] [810feb47] ? file_update_time+0x101/0x130 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143759] [810ca8fd] ? do_wp_page+0x6cd/0x707 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143787] [8100f6ed] ? __switch_to+0x1d6/0x297 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143815] [810cc331] ? handle_mm_fault+0x7aa/0x80f Jul 13 08:52:46 agenzia-f07 kernel: [432397.143843] [81016529] ? read_tsc+0xa/0x20 Jul 13 08:52:46 agenzia-f07 kernel: [432397.143870] [812faa96] ? do_page_fault+0x2e0/0x2fc Jul 13 08:52:46 agenzia-f07 kernel: [432397.143898] [812f8935] ? page_fault+0x25/0x30 -- 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/1310541872.4632.137.camel@scarafaggio
Bug#631945: HFSC warning issue
Through serveral days my friend has done some tests with kernels 2.6.39.x 2.6.39.1, 2.6.39.2 and 2.6.39.3 are still affected. 2.6.39 (debian version 2.6.39-1 from http://snapshot.debian.org/binary/?cat=l) works for several hours without triggering the bug. If it persist for some hours more we will bisect 2.6.39 and 2.6.39.1 and try to find the related patch. -- 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/1282b78c.566ec172.4e1d63a9.af...@o2.pl
Bug#619034: Bug found in multiple kernels
On Wed, 2011-07-13 at 02:51 +0100, Ben Hutchings wrote: On Tue, 2011-07-12 at 13:05 +0200, Svante Signell wrote: .. Where can I report upstream? You already did (alsa-de...@alsa-project.org) and you were requested to do a bisection between Linux 2.6.32 and 2.6.37. You can find binary packages of some of the intermediate versions on http://snapshot.debian.org/package/linux-2.6/. ON, now I have made the bisection: 2.6.33-1~experimental.5 works OK, however with the address space collision warning reported earlier. 2.6.34-1~experimental.1 shows the same problems ar later kernels. Do you need dmesg output or anything else to make progress? -- 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/1310552121.2599.4.ca...@amd64.my.own.domain
Bug#633738: ip6_tunnel: kernel BUG at net_namespace.c:497
Package: linux-2.6 Version: 2.6.32-35 Severity: important Tags: squeeze If have the following in my /etc/network/interfaces file: auto iptv-foobar iface iptv-foobar inet static address 169.254.0.2 netmask 255.255.255.255 pointopoint 169.254.0.3 pre-upmodprobe ip6_tunnel pre-upip -6 tunnel add iptv-foobar mode ipip6 remote 2001:db8:1::1 local 2001:db8:2::1 ttl 64 post-down ip tunnel del iptv-foobar upip link set iptv-foobar multicast on upsysctl -q net.ipv4.conf.iptv-foobar.rp_filter=0 upsysctl -q net.ipv4.conf.iptv-foobar.forwarding=0 It seems when ip6_tunnel is loaded, I get the following BUG: [ 33.135714] kernel BUG at /build/buildd-linux-2.6_2.6.32-35-armel-66FbPF/linux-2.6-2.6.32/debian/build/source_armel_none/net/core/net_namespace.c:497! [ 33.149340] Unable to handle kernel NULL pointer dereference at virtual address [ 33.157485] pgd = df31 [ 33.160204] [] *pgd=1f0a4031, *pte=, *ppte= [ 33.166643] Internal error: Oops: 817 [#1] [ 33.170756] last sysfs file: /sys/module/ipv6/initstate [ 33.176003] Modules linked in: ip6_tunnel(+) tunnel6 bonding ipv6 iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables dm_mod hmac xgifb(C) sata_mv fb ehci_hcd sha1_generic cfbcopyarea libata mv_cesa usbcore cfbimgblt scsi_mod mv643xx_eth aes_generic libphy inet_lro cfbfillrect nls_base [ 33.207618] CPU: 0Tainted: G C (2.6.32-5-kirkwood #1) [ 33.213831] PC is at __bug+0x1c/0x28 [ 33.217418] LR is at __bug+0x18/0x28 [ 33.221012] pc : [c002b7f8]lr : [c002b7f4]psr: 6013 [ 33.221018] sp : df333ee8 ip : 987a fp : 0001cf00 [ 33.232555] r10: bf24d338 r9 : df332000 r8 : dfb716c0 [ 33.237805] r7 : c043af08 r6 : r5 : r4 : c03d0a34 [ 33.244362] r3 : r2 : c03b4d2c r1 : 6013 r0 : 00a0 [ 33.250921] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 33.258088] Control: 0005317f Table: 1f31 DAC: 0015 [ 33.263860] Process modprobe (pid: 482, stack limit = 0xdf332270) [ 33.269982] Stack: (0xdf333ee8 to 0xdf334000) [ 33.274364] 3ee0: c03d0a34 c02397ec c03d0a34 c043af08 dfb716c0 [ 33.282588] 3f00: c043af08 bf24d3d0 dfb71840 c03d0a34 bf24f734 c043af08 [ 33.290811] 3f20: 40156000 c03d0a34 c023942c bf24f734 bf252000 c03d0a48 40156000 [ 33.299033] 3f40: c02395c0 bf252000 bf25200c c002734c [ 33.307256] 3f60: 56bc bf24f744 40156000 bf24f744 40156000 [ 33.315479] 3f80: c0028048 c00738ec dfb71300 dfb20a80 0001b038 0001b070 [ 33.323702] 3fa0: 0080 c0027ea0 0001b070 40156000 56bc 0001cfb0 [ 33.331925] 3fc0: 0001b070 0080 0001b038 0001cf00 [ 33.340149] 3fe0: 0001cfb0 be8f395c b720 400ee1d4 6010 40156000 [ 33.348380] [c002b7f8] (__bug+0x1c/0x28) from [c02397ec] (net_assign_generic+0x3c/0xbc) [ 33.356789] [c02397ec] (net_assign_generic+0x3c/0xbc) from [bf24d3d0] (ip6_tnl_init_net+0x98/0x19c [ip6_tunnel]) [ 33.367378] [bf24d3d0] (ip6_tnl_init_net+0x98/0x19c [ip6_tunnel]) from [c023942c] (register_pernet_operations+0x40/0xf4) [ 33.378658] [c023942c] (register_pernet_operations+0x40/0xf4) from [c02395c0] (register_pernet_device+0x20/0x54) [ 33.389240] [c02395c0] (register_pernet_device+0x20/0x54) from [bf25200c] (ip6_tunnel_init+0xc/0x84 [ip6_tunnel]) [ 33.399915] [bf25200c] (ip6_tunnel_init+0xc/0x84 [ip6_tunnel]) from [c002734c] (do_one_initcall+0x6c/0x1e4) [ 33.410062] [c002734c] (do_one_initcall+0x6c/0x1e4) from [c00738ec] (sys_init_module+0xc0/0x1f0) [ 33.419241] [c00738ec] (sys_init_module+0xc0/0x1f0) from [c0027ea0] (ret_fast_syscall+0x0/0x28) [ 33.428333] Code: e1a01000 e59f000c eb0a2ec7 e3a03000 (e5833000) [ 33.434502] ---[ end trace bf87ce5c849aaa8e ]--- Segmentation fault Failed to bring up iptv-shironeko. This is a regression as I was able to do all this with earlier kernels; definately 2.6.32-34squeeze1. Cheers -- Package-specific info: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Tue Jun 14 23:05:32 UTC 2011 ** Command line: console=ttyS1,115200=panic=10 ubi.mtd=root kw_openrd_init_uart1=232 root=ubi0:rootfs rootfstype=ubifs rw ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Model information Processor : Feroceon 88FR131 rev 1 (v5l) Hardware: Marvell OpenRD Ultimate Board Revision: ** Loaded modules: Module Size Used by ext4 288561 1 mbcache 4860 1 ext4 jbd2 64191 1 ext4
Bug#633024: initramfs-tools: Race condition when root filesystem is on a LV and mdadm array
On Mon, 11 Jul 2011, Rain Maker wrote: - The rootdelay=X option does as advertised: Also it adds time to scsi device to settle before calling mdadm or lvm thus excluding potential races.. In this situation, I seem to need a delay between assembling mdadm and activating the VG's. sure this *is* the recommended workaround for such races. such timing bugs occure in many different linux subsystems. - scsi_mod.scan=sync does not introduce any visual delay, but doesn't help me either. of course as no scsi disks are involved. - I've also tried a couple of break= commands, but there doesn't seem to be a breakpoint between mdadm and LVM. the breaks only help to debug stuff inbetween aka for manual interaction. so false critic. Thank you for the suggestion. thank you. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110712203618.gd31...@stro.at
Processed: tagging 628374
Processing commands for cont...@bugs.debian.org: tags 628374 + pending Bug #628374 [initramfs-tools] initramfs-tools: Recent changes to hooks break busybox in initrd Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 628374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628374 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.131055602126067.transcr...@bugs.debian.org
Bug#633747: /lib/modules/2.6.39-2-686-pae/kernel/drivers/net/wireless/rt2x00/rt61pci.ko: ralink wifi rt61pci not working in 2.6.39-2-686-pae
Package: linux-2.6 Version: 2.6.39-2 Severity: normal File: /lib/modules/2.6.39-2-686-pae/kernel/drivers/net/wireless/rt2x00/rt61pci.ko In 2.6.39-686-pae kernel, the ralink wifi pci card isn't working, while in a 2.6.38 it is. $ lspci | grept ralink 32:0b:00.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g $ lsmod | grept rt 23:rt61pci22168 0 24:rt2x00pci 12683 1 rt61pci 25:rt2x00lib 28634 2 rt61pci,rt2x00pci 26:mac80211 164606 2 rt2x00pci,rt2x00lib 27:cfg80211 107076 2 rt2x00lib,mac80211 28:eeprom_93cx6 12423 1 rt61pci 92:crc_itu_t 12331 2 rt61pci,firewire_core $ modinfo rt61pci filename: /lib/modules/2.6.39-2-686-pae/kernel/drivers/net/wireless/rt2x00/rt61pci.ko license:GPL firmware: rt2661.bin firmware: rt2561s.bin firmware: rt2561.bin description:Ralink RT61 PCI PCMCIA Wireless LAN driver. version:2.3.0 author: http://rt2x00.serialmonkey.com srcversion: 12A0A8B7A10EAE6E53E404A alias: pci:v1814d0401sv*sd*bc*sc*i* alias: pci:v1814d0302sv*sd*bc*sc*i* alias: pci:v1814d0301sv*sd*bc*sc*i* depends:rt2x00lib,rt2x00pci,eeprom_93cx6,crc-itu-t intree: Y vermagic: 2.6.39-2-686-pae SMP mod_unload modversions 686 parm: nohwcrypt:Disable hardware encryption. (bool) -- Package-specific info: ** Version: Linux version 2.6.39-2-686-pae (Debian 2.6.39-2) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Wed Jun 8 11:33:14 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-2-686-pae root=UUID=8fe7010b-ba34-4eb0-9a7a-d5343f670dba ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [7.813374] yenta_cardbus :06:05.0: Socket status: 3006 [7.813384] yenta_cardbus :06:05.0: pcmcia: parent PCI bridge window: [io 0x2000-0x2fff] [7.813388] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x2000-0x2fff: excluding 0x2000-0x20ff 0x2400-0x24ff 0x2800-0x28bf [7.820049] yenta_cardbus :06:05.0: pcmcia: parent PCI bridge window: [mem 0xf000-0xf5ff] [7.820054] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf000-0xf5ff: excluding 0xf000-0xf41f [7.820072] yenta_cardbus :06:05.0: pcmcia: parent PCI bridge window: [mem 0xd400-0xd7ff pref] [7.820077] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd400-0xd7ff: excluding 0xd400-0xd7ff [7.823408] yenta_cardbus :0a:09.0: CardBus bridge found [1025:0098] [7.823433] yenta_cardbus :0a:09.0: Using CSCINT to route CSC interrupts to PCI [7.823436] yenta_cardbus :0a:09.0: Routing CardBus interrupts to PCI [7.823444] yenta_cardbus :0a:09.0: TI: mfunc 0x01321b22, devctl 0x66 [7.859985] [drm] Initialized drm 1.1.0 20060810 [8.000602] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04713/0x204000/0x0 [8.053076] yenta_cardbus :0a:09.0: ISA IRQ mask 0x0cf8, PCI irq 20 [8.053082] yenta_cardbus :0a:09.0: Socket status: 3820 [8.053087] pci_bus :0a: Raising subordinate bus# of parent bus (#0a) from #0b to #0e [8.053098] yenta_cardbus :0a:09.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff] [8.053104] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3000-0x3fff: excluding 0x3000-0x30ff 0x3400-0x34ff [8.060036] yenta_cardbus :0a:09.0: pcmcia: parent PCI bridge window: [mem 0xd020-0xd02f] [8.060041] pcmcia_socket pcmcia_socket1: cs: memory probe 0xd020-0xd02f: excluding 0xd020-0xd020 [8.060061] yenta_cardbus :0a:09.0: pcmcia: parent PCI bridge window: [mem 0xd800-0xdbff pref] [8.060065] pcmcia_socket pcmcia_socket1: cs: memory probe 0xd800-0xdbff: excluding 0xd800-0xdbff [8.060185] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input10 [8.205631] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [8.205638] i915 :00:02.0: setting latency timer to 64 [8.206941] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [8.206945] [drm] Driver supports precise vblank timestamp query. [8.383538] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding nothing: probe failed. [8.383612] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding nothing: probe failed. [8.383657] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: excluding nothing: probe failed. [8.383696] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: excluding nothing: probe failed. [8.383740] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xf [8.383776] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: excluding 0xa000-0xa0ff [8.383811]
kernel 2.6.39 chipset r8192e
Hi, it seems that there is a regression since the *.39 and this driver. (R8192e_pci) The connection to my network works correctly but impossible to update my system or navigate to internet like if i'm not connected... I tried with the 2.6.32 kernel and it works at 100%... I use firmware-realtek. Which log i must to post to help you? Thanks, berillions PS: woorks totally with kernel 2.6.38 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/CAGib1vc9awVS+3NsfPPaLKCNeEx_MYnNt=ga+xrmg8hg8wl...@mail.gmail.com
Bug#633766: /lib/modules/2.6.39-2-686-pae/kernel/drivers/net/wireless/rtlwifi/rtl8192cu/rtl8192cu.ko: belink usb wifi tongle rtl8192cu not working in 2.6.39-2-686-pae
Package: linux-2.6 Version: 2.6.39-2 Severity: normal File: /lib/modules/2.6.39-2-686-pae/kernel/drivers/net/wireless/rtlwifi/rtl8192cu/rtl8192cu.ko the belkin wifi tongle based on the rtl8192cu chip isn't working in 2.6.39-2-686-pae, while in 2.6.38 it was... $ modinfo rtl8192cu filename: /lib/modules/2.6.39-2-686-pae/kernel/drivers/net/wireless/rtlwifi/rtl8192cu/rtl8192cu.ko firmware: rtlwifi/rtl8192cufw.bin description:Realtek 8192C/8188C 802.11n USB wireless license:GPL author: Larry Fingerlarry.fin...@lwfinger.net author: Ziv Huang ziv_hu...@realtek.com author: Georgia geor...@realtek.com alias: usb:v7392p7822d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pAB2Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p330Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3309d*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3307d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p8178d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p8178d*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp0056d*dc*dsc*dp*ic*isc*ip* alias: usb:v0586p341Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v3359p13D3d*dc*dsc*dp*ic*isc*ip* alias: usb:v3358p13D3d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7811d*dc*dsc*dp*ic*isc*ip* alias: usb:v20F4p648Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pED17d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pAB2Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3308d*dc*dsc*dp*ic*isc*ip* alias: usb:v103Cp1629d*dc*dsc*dp*ic*isc*ip* alias: usb:v0EB0p9071d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0052d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p8189d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p8188d*dc*dsc*dp*ic*isc*ip* alias: usb:v06F8pE033d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp1102d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp817Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp817Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8177d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8754d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp817Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp817Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp817Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp817Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8177d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8176d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8170d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8191d*dc*dsc*dp*ic*isc*ip* depends:rtlwifi,mac80211,rtl8192c-common,usbcore intree: Y vermagic: 2.6.39-2-686-pae SMP mod_unload modversions 686 $ lsmod | grept rtl Bus 001 Device 003: ID 050d:1102 Belkin Components $ lsmod | grept rtl 10:rtl8192cu 73595 0 11:rtl8192c_common43386 1 rtl8192cu 12:rtlwifi66279 1 rtl8192cu 13:mac80211 164606 2 rtl8192cu,rtlwifi 14:cfg80211 107076 2 rtlwifi,mac80211 86:usbcore99225 8 rtl8192cu,rtlwifi,gspca_vc032x,gspca_main,usbhid,uhci_hcd,ehci_hcd -- Package-specific info: ** Version: Linux version 2.6.39-2-686-pae (Debian 2.6.39-2) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Wed Jun 8 11:33:14 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-2-686-pae root=UUID=8fe7010b-ba34-4eb0-9a7a-d5343f670dba ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [8.053082] yenta_cardbus :0a:09.0: Socket status: 3820 [8.053087] pci_bus :0a: Raising subordinate bus# of parent bus (#0a) from #0b to #0e [8.053098] yenta_cardbus :0a:09.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff] [8.053104] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3000-0x3fff: excluding 0x3000-0x30ff 0x3400-0x34ff [8.060036] yenta_cardbus :0a:09.0: pcmcia: parent PCI bridge window: [mem 0xd020-0xd02f] [8.060041] pcmcia_socket pcmcia_socket1: cs: memory probe 0xd020-0xd02f: excluding 0xd020-0xd020 [8.060061] yenta_cardbus :0a:09.0: pcmcia: parent PCI bridge window: [mem 0xd800-0xdbff pref] [8.060065] pcmcia_socket pcmcia_socket1: cs: memory probe 0xd800-0xdbff: excluding 0xd800-0xdbff [8.060185] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input10 [8.205631] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [8.205638] i915 :00:02.0: setting latency timer to 64 [8.206941] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [8.206945] [drm] Driver supports precise vblank timestamp query. [8.383538] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding nothing: probe failed. [8.383612] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding nothing: probe failed. [8.383657] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: excluding
Bug#627655: linux-image-2.6.39-1-686-pae: missing NFS4.1 / pNFS support
Hi Ben, On Monday 23 May 2011 18:48:56 Ben Hutchings wrote: [wishlist: NFS-4.1 / pNFS support] Anyway, I have no objection to enabling this unless it is likely to cause regressions for other NFS users. Is there any news on enabling NFS v4.1? Can I do anything to help? Cheers, Paul. -- 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/201107131527.39897.paul.mil...@desy.de
Bug#619034: Boot problem due to PCI core, x86 mm or ACPI/BIOS
Svante Signell wrote: ON, now I have made the bisection: 2.6.33-1~experimental.5 works OK, however with the address space collision warning reported earlier. 2.6.34-1~experimental.1 shows the same problems ar later kernels. Do you need dmesg output or anything else to make progress? Would it be possible to bisect between those versions, to find the exact change that introduced this problem? It works like this: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git $ cd linux-2.6 $ git bisect start v2.6.34 v2.6.33 Git checks out a version half-way between. So: $ make localmodconfig; # minimal configuration $ make deb-pkg; # builds a .deb # dpkg -i ../whatever.deb; reboot $ git bisect good; # if it works $ git bisect bad; # if it shows the same problem $ git bisect skip; # if another problem makes it impossible to test Then: $ make silentoldconfig; # reuse configuration $ make deb-pkg; # build a .deb # dpkg -i ../whatever.deb; reboot $ git bisect good / bad / skip ... rinse and repeat until it shows the first bad commit ... If the gitk package is installed, you can use git bisect visualize at any point to see the regression range narrowing. The point of this exercise is to find out what subsystem in particular broke. For more information on git bisect, see [1] if interested. Thanks for reporting, and sorry for the trouble. Jonathan [1] http://www.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html -- 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/20110713163347.GA747@elie
Re: Next upload to unstable
Ben Hutchings b...@decadent.org.uk schrieb: --=-Wk45Ah+XpS5md1taqRO7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable There are some security fixes in 2.6.39.3 but I'm not sure how important they are. Dann, Moritz, any opinion? If they're not that important then let's wait for 2.6.39-3 to transition to testing (which should happen on Thursday) before making another upload. It's just one new issue, most of the fixes from 2.6.39.3 have been applied to 2.6.39-3 before. Let's migrate 3.6.39 to testing first. Cheers, Moritz -- 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/slrnj1rp7r.3f9@inutil.org
Bug#631187: Kernel panics when removing external hard drive
On Wed, 2011-07-13 at 22:03 +1000, Linh Nguyen wrote: Hello Alexander, How are you? I came across your post http://lists.debian.org/debian-kernel/2011/06/msg00580.html detailing similar issue as to what I am experiencing. Every time I unmount a portable HDD (normal USB sticks are fine), i get a kernel panic the the power/level is deprecated; use power/control instead error message. Despite my extensive googling, i've not been able to find a solution. I was wondering whether or not you have solved your issue. Cheers. :) Sincerely, L Sorry, I've got no solution either. Since this is kind of a low-priority bug for me, I'm fine with manually unmounting (using umount or some GUI) my external drive before removing it. My current plan is to wait for 3.0 and then maybe do a git bisect if it's not fixed by then. However, you should check out the Debian bug report[1], the Ubuntu bug report[2] and the upstream bug report[3], maybe you'll find something there. Best regards Alexander Kurtz [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631187 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793796 [3] https://bugzilla.kernel.org/show_bug.cgi?id=38842 signature.asc Description: This is a digitally signed message part
