Bug#682233: (no subject)
I think this commit is somehow related to that problem: commit 14216561e164671ce147458653b1fea06a4ada1e Author: James Bottomley jbottom...@parallels.com Date: Wed Jul 25 23:55:55 2012 +0400 [SCSI] Fix 'Device not ready' issue on mpt2sas This is a particularly nasty SCSI ATA Translation Layer (SATL) problem. SAT-2 says (section 8.12.2) if the device is in the stopped state as the result of processing a START STOP UNIT command (see 9.11), then the SATL shall terminate the TEST UNIT READY command with CHECK CONDITION status with the sense key set to NOT READY and the additional sense code of LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED; mpt2sas internal SATL seems to implement this. The result is very confusing standby behaviour (using hdparm -y). If you suspend a drive and then send another command, usually it wakes up. However, if the next command is a TEST UNIT READY, the SATL sees that the drive is suspended and proceeds to follow the SATL rules for this, returning NOT READY to all subsequent commands. This means that the ordering of TEST UNIT READY is crucial: if you send TUR and then a command, you get a NOT READY to both back. If you send a command and then a TUR, you get GOOD status because the preceeding command woke the drive. This bit us badly because -- 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/5056d21b.6060...@gmail.com
Bug#687853: linux-image-3.2.0-3-amd64: Fan speed freezes, and hotkeys stop working. Laptop Lenovo Thinkpad L512 (2597AB2)
without fglrx too most thus not what information it is not displayed in syslog -- evol mail -- 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/5056d2ab.2070...@gmail.com
Bug#687927: firmware-realtek: Missing rtl8411-1.fw and rtl8402-1.fw
Package: firmware-realtek Version: 0.36 Severity: normal I have an Intel D525MW motherboard (Atom) with a Realtek integrated network card. It doesn't work with the current kernel from testing: linux-image-3.2.0-3-amd64 (3.2.23-1) It doesn't print anything special in the syslog: # dmesg | grep r8169 [1.495121] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [1.495181] r8169 :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.495243] r8169 :01:00.0: setting latency timer to 64 [1.495354] r8169 :01:00.0: irq 44 for MSI/MSI-X [1.496836] r8169 :01:00.0: eth0: RTL8168e/8111e at 0xc933, e0:69:95:69:91:6c, XID 0c20 IRQ 44 [1.496849] r8169 :01:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] But doing ifup eth0 does nothing: no network, no errors. Today i've installed the Debian kernel reported here, from experimental and i think it reports the culprit of the problem: - a curses window report that a required firmware is missing: r8169: rtl_nic/rtl_nic_rtl8411-1.fw, rtl_nic/rtl_nic_rtl8402-1.fw - a message before update-grup repeat the concept saying: update-initramfs: Generating /boot/initrd.img-3.5-trunk-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.5-trunk-amd64 /boot/vmlinuz-3.5-trunk-amd64 Ben, i see that in july you made a commit in the upstream rtl_nic/rtl8402-1.fw. Maybe you know why these firmware are not included in this non-free package. Are there known problem with these? Are they not yet included in the mainline kernel? Cesare. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-realtek depends on no packages. firmware-realtek recommends no packages. Versions of packages firmware-realtek suggests: ii initramfs-tools0.107 ii linux-image-3.2.0-3-486 [linux-image] 3.2.23-1 ii linux-image-3.2.0-3-amd64 [linux-image]3.2.23-1 ii linux-image-3.5-trunk-amd64 [linux-image] 3.5.2-1~experimental.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120917082816.11726.20947.report...@aika.internal.bernispa.com
Bug#636797: Followup on debian bug #636797
Hi, I got the following OOPS on 2.6.32-41 (Linux version 2.6.32-5-amd64 (Debian 2.6.32-41) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 16 16:22:28 UTC 2012). The machine runs Mysql, it's a dedicated database server with pretty high IO load. The oops is hard to read because it was captured via netconsole, but the crash is a divide by zero error in find_busiest_group, like the original report. So this doesn't seem to be fixed in -41. Would upgrading to -45 help? Regards, Ronald. Sep 11 13:24:17 db03 [9141932.763480] divide error: [#1] Sep 11 13:24:17 db03 SMP Sep 11 13:24:17 db03 Sep 11 13:24:17 db03 [9141932.763584] last sysfs file: /sys/devices/platform/host2/session1/target2:0:0/2:0:0:5/state Sep 11 13:24:17 db03 [9141932.763673] CPU 4 Sep 11 13:24:17 db03 Sep 11 13:24:17 db03 [9141932.763701] Modules linked in: Sep 11 13:24:17 netconsole Sep 11 13:24:17 configfs Sep 11 13:24:17 btrfs Sep 11 13:24:17 zlib_deflate Sep 11 13:24:17 libcrc32c Sep 11 13:24:17 ufs Sep 11 13:24:17 qnx4 Sep 11 13:24:17 hfsplus Sep 11 13:24:17 hfs Sep 11 13:24:17 minix Sep 11 13:24:17 ntfs Sep 11 13:24:17 vfat Sep 11 13:24:17 msdos Sep 11 13:24:17 fat Sep 11 13:24:17 jfs Sep 11 13:24:17 xfs Sep 11 13:24:17 exportfs Sep 11 13:24:17 reiserfs Sep 11 13:24:17 ext2 Sep 11 13:24:17 ext4 Sep 11 13:24:17 jbd2 Sep 11 13:24:17 crc16 Sep 11 13:24:17 sd_mod Sep 11 13:24:17 crc_t10dif Sep 11 13:24:17 crc32c Sep 11 13:24:17 ib_iser Sep 11 13:24:17 rdma_cm Sep 11 13:24:17 ib_cm Sep 11 13:24:17 iw_cm Sep 11 13:24:17 ib_sa Sep 11 13:24:17 ib_mad Sep 11 13:24:17 ib_core Sep 11 13:24:17 ib_addr Sep 11 13:24:17 iscsi_tcp Sep 11 13:24:17 libiscsi_tcp Sep 11 13:24:17 libiscsi Sep 11 13:24:17 scsi_transport_iscsi Sep 11 13:24:17 ipmi_devintf Sep 11 13:24:17 acpi_cpufreq Sep 11 13:24:17 loop Sep 11 13:24:17 snd_pcm Sep 11 13:24:17 snd_timer Sep 11 13:24:17 ipmi_si Sep 11 13:24:17 radeon Sep 11 13:24:17 hpilo Sep 11 13:24:17 ttm Sep 11 13:24:17 drm_kms_helper Sep 11 13:24:17 ipmi_msghandler Sep 11 13:24:17 drm Sep 11 13:24:17 i2c_algo_bit Sep 11 13:24:17 i2c_core Sep 11 13:24:17 snd Sep 11 13:24:17 soundcore Sep 11 13:24:17 snd_page_alloc Sep 11 13:24:17 hpwdt Sep 11 13:24:17 pcspkr Sep 11 13:24:17 psmouse Sep 11 13:24:17 serio_raw Sep 11 13:24:17 container Sep 11 13:24:17 evdev Sep 11 13:24:17 power_meter Sep 11 13:24:17 processor Sep 11 13:24:17 button Sep 11 13:24:17 ext3 Sep 11 13:24:17 jbd Sep 11 13:24:17 mbcache Sep 11 13:24:17 dm_mod Sep 11 13:24:17 sg Sep 11 13:24:17 usbhid Sep 11 13:24:17 sr_mod Sep 11 13:24:17 hid Sep 11 13:24:17 cdrom Sep 11 13:24:17 ata_generic Sep 11 13:24:17 uhci_hcd Sep 11 13:24:17 ata_piix Sep 11 13:24:17 ehci_hcd Sep 11 13:24:17 hpsa Sep 11 13:24:17 libata Sep 11 13:24:17 usbcore Sep 11 13:24:17 nls_base Sep 11 13:24:17 thermal Sep 11 13:24:17 cciss Sep 11 13:24:17 bnx2 Sep 11 13:24:17 e1000e Sep 11 13:24:17 scsi_mod Sep 11 13:24:17 thermal_sys Sep 11 13:24:17 [last unloaded: scsi_wait_scan] Sep 11 13:24:17 db03 Sep 11 13:24:17 db03 [9141932.764377] Pid: 16396, comm: mysqld Tainted: GW 2.6.32-5-amd64 #1 ProLiant DL360 G6 Sep 11 13:24:17 db03 [9141932.764428] RIP: 0010:[810453e8] Sep 11 13:24:17 [810453e8] find_busiest_group+0x97a/0xa4e Sep 11 13:24:17 db03 [9141932.764492] RSP: 0018:880073b29b88 EFLAGS: 00010006 Sep 11 13:24:17 db03 [9141932.764524] RAX: 0010 RBX: 0010 RCX: Sep 11 13:24:17 db03 [9141932.764592] RDX: RSI: 0400 RDI: Sep 11 13:24:17 db03 [9141932.764661] RBP: 0400 R08: 000a R09: 813c71cc Sep 11 13:24:17 db03 [9141932.764711] R10: 7f43e1e99200 R11: 880073b29ec8 R12: 88000548fa20 Sep 11 13:24:17 db03 [9141932.764760] R13: 88000548fae0 R14: 00015700 R15: Sep 11 13:24:17 db03 [9141932.764810] FS: 7f43dd757700() GS:88000548() knlGS: Sep 11 13:24:17 db03 [9141932.764861] CS: 0010 DS: ES: CR0: 80050033 Sep 11 13:24:17 db03 [9141932.764892] CR2: 7f4426793000 CR3: 00011c1ee000 CR4: 06e0 Sep 11 13:24:17 db03 [9141932.764942] DR0: DR1: DR2: Sep 11 13:24:17 db03 [9141932.764991] DR3: DR6: 0ff0 DR7: 0400 Sep 11 13:24:17 db03 [9141932.765041] Process mysqld (pid: 16396, threadinfo 880073b28000, task 88011bd2dbd0) Sep 11 13:24:17 db03 [9141932.765092] Stack: Sep 11 13:24:17 db03 [9141932.765115] 00015788 Sep 11 13:24:17 00015780 Sep 11 13:24:17 0008 Sep 11 13:24:17 00015780 Sep 11 13:24:17 db03 Sep 11 13:24:17 db03 [9141932.765162] 0 Sep 11 13:24:17 00015780 Sep 11 13:24:17 00015780 Sep 11 13:24:17 Sep 11 13:24:17 88000544fbf0 Sep 11 13:24:17 db03 Sep 11
Processed: Re: Bug#687929: bug report: your system had a kernel failure
Processing commands for cont...@bugs.debian.org: reassign 687929 src:linux Bug #687929 [kernel-image] bug report: your system had a kernel failure Warning: Unknown package 'kernel-image' Bug reassigned from package 'kernel-image' to 'src:linux'. Ignoring request to alter found versions of bug #687929 to the same values previously set Ignoring request to alter fixed versions of bug #687929 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 687929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687929 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.134787288424289.transcr...@bugs.debian.org
Bug#687515: Coredumped after wakeup from suspend, mentioning ifconfig
Hello Ben, thanks for taking the time to look into this. This special bug has happened alltogether two times. The one time I have reported this and a day later (friday). Then I upgraded net-tools to unstable since this was mentioned in the bugreport. After that I had this coredump no more. But it is only two days since then this is not finally, I guess. For configuring the network I use wicd-client. I only have xfce installed on this machine, so wicd-client is about the only usable gui for configuring wlan. I had a similar problem with this machine, again related to suspend. Don't know if it is related or not, but I'll describe it anyway. When putting the machine to sleep via closing the lid then every two days or so the machine used to freeze instead of going to sleep. I then had to reopen the lid and was presented with an unresponsive X-windows. Mouse was working, keyboard was almost dead except the commands like switching to console. Had to press ctrl-alt-f1 to reboot. I've described this in http://forums.debian.net/viewtopic.php?f=5t=83462;. At this time I had KDE running on the machine, which I then removed and switched to xfce. Which did not help. Then I configured the energy settings so that pressing the power-button performed the suspend to ram. Since then I no longer have the problem of freezing before suspend. But now the coredump after wakeup appeared. Sort of trading cholera for measles... Since this seems to be related to networking: I often use different wlan networks. So it can happen that I put the maching to sleep when connected with wlan a, resume when wlan a is no longer present. Or I put it to sleep and at the same time turn of my own mobile hotspot, so wlan is disappearing at this moment. Anyway, if there is anything I can do then contact me. Yours, Gunnar -- 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/5056f0bf.1080...@gunnarstahl.org
Bug#685360: Logitech USB keyboard broken with Linux 3.2 (regression from 3.1)
On Mon, Sep 17, 2012 at 12:57:06PM +0200, Jiri Kosina wrote: On Wed, 12 Sep 2012, Nestor Lopez Casado wrote: Take a look at this thread ... where a patch was published ... https://bugs.launchpad.net/ubuntu/+bug/958174 Your issue may come from the same problem. I will get back to you next week. I am OOO until monday. So, what is the progress here, please? Nestor, Josip? There is no progress because for some reason I did not receive Nestor's previous e-mail; I'll try to test it this week. -- 2. That which causes joy or happiness. -- 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/20120917110008.ga16...@entuzijast.net
Bug#679545: [RFC/PATCH] ia64, SR870, EFI bug breaks ata_piix, uninitialized ICH4 IDE EXBAR mem resource
My only disagreement here would be putting it in the ia64 paths. If someone does the same for x86-32 (and this is EFI so it'll presumbly smell the same on all platforms) then we'll want the same. Better I think to generically catch the 0/0 case. Alan -- 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/20120917115619.13d3a...@pyramind.ukuu.org.uk
Bug#648811: DRBD+OCFS2: general protection fault: 0000 [#1] SMP
Hi, I can confirm a bug. I tried DRBD (two primaries) with OCFS2 too. It seems I hit a very similar bug after I did a reboot renamed nodes and did mount ocfs2 by hand. Two identical nodes boot1 and boot2 guests on libvirt/KVM (different irons): Linux boot1 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux i linux-image-2.6.32-5-amd642.6.32-45 Linux 2.6.32 for 64-bit PCs Virtuals have configured ttyS0 console (both attached), so I cutpaste what was on the consoles: == boot1 == [ 9985.562785] general protection fault: [#1] SMP [ 9985.563235] last sysfs file: /sys/fs/o2cb/interface_revision [ 9985.563707] CPU 0 [ 9985.563893] Modules linked in: ocfs2 quota_tree drbd lru_cache cn nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs loop snd_pcm snd_timer snd soundcore snd_page_alloc psmouse virtio_balloon button serio_raw pcspkr processor evdev i2c_piix4 i2c_core ext4 mbcache jbd2 crc16 dm_mod ata_generic virtio_blk ata_piix uhci_hcd ehci_hcd 8139too libata floppy thermal thermal_sys virtio_pci virtio_ring virtio 8139cp mii usbcore nls_base scsi_mod [last unloaded: scsi_wait_scan] [ 9985.566703] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 Bochs [ 9985.566703] RIP: 0010:[8129eb2e] [8129eb2e] fib_get_table+0x2b/0x3a [ 9985.566703] RSP: 0018:880001803bb8 EFLAGS: 00010286 [ 9985.566703] RAX: 8801 RBX: 880001803c20 RCX: 880001803c20 [ 9985.566703] RDX: c3f000ff53f000ff RSI: 00fe RDI: 816d35b0 [ 9985.566703] RBP: 880001803cd0 R08: 816d35b0 R09: 011fa8c0 [ 9985.566703] R10: 0002 R11: R12: 88001f9d0480 [ 9985.566703] R13: R14: 880001803c20 R15: 88001f9d04f8 [ 9985.566703] FS: () GS:88000180() knlGS: [ 9985.566703] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 9985.566703] CR2: 018c9808 CR3: 1dd98000 CR4: 06f0 [ 9985.566703] DR0: DR1: DR2: [ 9985.566703] DR3: DR6: 0ff0 DR7: 0400 [ 9985.566703] Process swapper (pid: 0, threadinfo 8142e000, task 814891f0) [ 9985.566703] Stack: [ 9985.566703] 812a427e 88001f9db000 880001803cd0 [ 9985.566703] 0 8125e1b1 8800182371a8 880001803c90 0002 [ 9985.566703] 0 ffea 011fa8c0 8800181b1000 880018057800 [ 9985.566703] Call Trace: [ 9985.566703] IRQ [ 9985.566703] [812a427e] ? fib4_rule_action+0x35/0x54 [ 9985.566703] [8125e1b1] ? fib_rules_lookup+0x89/0xc3 [ 9985.566703] [812a4474] ? fib_lookup+0x2d/0x3d [ 9985.566703] [8103a311] ? enqueue_task+0x5f/0x68 [ 9985.566703] [81271d9f] ? ip_route_input+0x59e/0xcbf [ 9985.566703] [8104a45a] ? try_to_wake_up+0x289/0x29b [ 9985.566703] [8106504b] ? autoremove_wake_function+0x9/0x2e [ 9985.566703] [8103aa06] ? __wake_up_common+0x44/0x72 [ 9985.566703] [810ad4e8] ? cpupri_set+0x10c/0x135 [ 9985.566703] [81295e3e] ? arp_process+0x20f/0x60b [ 9985.566703] [a00737fb] ? cp_rx_poll+0x2d8/0x3bd [8139cp] [ 9985.566703] [8125039f] ? net_rx_action+0xae/0x1c9 [ 9985.566703] [81053d6f] ? __do_softirq+0xdd/0x1a6 [ 9985.566703] [81011cac] ? call_softirq+0x1c/0x30 [ 9985.566703] [8101322b] ? do_softirq+0x3f/0x7c [ 9985.566703] [81053bdf] ? irq_exit+0x36/0x76 [ 9985.566703] [81012922] ? do_IRQ+0xa0/0xb6 [ 9985.566703] [810114d3] ? ret_from_intr+0x0/0x11 [ 9985.566703] EOI [ 9985.566703] [8102c584] ? native_safe_halt+0x2/0x3 [ 9985.566703] [8101758d] ? default_idle+0x34/0x51 [ 9985.566703] [8100fe97] ? cpu_idle+0xa2/0xda [ 9985.566703] [8151c140] ? early_idt_handler+0x0/0x71 [ 9985.566703] [8151ccdd] ? start_kernel+0x3dc/0x3e8 [ 9985.566703] [8151c3b7] ? x86_64_start_kernel+0xf9/0x106 [ 9985.566703] Code: 85 f6 b8 fe 00 00 00 0f 44 f0 48 89 f0 83 e0 01 48 c1 e0 03 48 03 87 f0 01 00 00 48 8b 10 eb 03 48 8b 12 48 85 d2 75 03 31 c0 c3 39 72 10 48 8b 02 0f 18 08 48 89 d0 75 e7 c3 48 8b 42 10 48 85 [ 9985.566703] RIP [8129eb2e] fib_get_table+0x2b/0x3a [ 9985.566703] RSP 880001803bb8 [ 9985.594195] ---[ end trace 49c80a52371bee10 ]--- [ 9985.594581] Kernel panic - not syncing: Fatal exception in interrupt [ 9985.595102] Pid: 0, comm: swapper Tainted: G D2.6.32-5-amd64 #1 [ 9985.595650] Call Trace: [ 9985.595857] IRQ [812faf69] ? panic+0x86/0x143 [ 9985.596356] [81011673] ? apic_timer_interrupt+0x13/0x20 [ 9985.596869] [811b89f1] ? vgacon_cursor+0x0/0x140 [ 9985.597342]
Re: Squeeze point release (6.0.6)
Hi, ok, given the replies, let's settle on this: On Fri, Sep 07, 2012 at 09:43:03PM +0200, Philipp Kern wrote: * Sep 29/30: ok from RT side We still need a press officer for somewhen in the evening to send out the announcement, feedback from -live and a note from -kernel if there's still a change staged for the next point release. p-u-NEW will close on the weekend of Sep 22nd/23rd (barring any breakage induced by the ftp-master meeting ;-). Kind regards Philipp Kern signature.asc Description: Digital signature
Re: Squeeze point release (6.0.6)
On Mon, Sep 17, 2012 at 03:58:13PM +0200, Philipp Kern wrote: ok, given the replies, let's settle on this: On Fri, Sep 07, 2012 at 09:43:03PM +0200, Philipp Kern wrote: * Sep 29/30: ok from RT side We still need a press officer for somewhen in the evening to send out the announcement, feedback from -live and a note from -kernel if there's still a change staged for the next point release. That should be read as let's settle for Sep 29. Kind regards Philipp Kern signature.asc Description: Digital signature
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #653292 (http://bugs.debian.org/653292) # Bug title: nfs exclusive lock does not work anymore after openvz kernel version : 2.6.32-35squeeze1 # * http://bugzilla.openvz.org/show_bug.cgi?id=2122 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 653292 + fixed-upstream Bug #653292 [linux-2.6] nfs exclusive lock does not work anymore after openvz kernel version : 2.6.32-35squeeze1 Added tag(s) fixed-upstream. usertags 653292 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 653292 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 653292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653292 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.134789966131526.transcr...@bugs.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #653292 (http://bugs.debian.org/653292) # Bug title: nfs exclusive lock does not work anymore after openvz kernel version : 2.6.32-35squeeze1 # * http://bugzilla.openvz.org/show_bug.cgi?id=2122 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 653292 + fixed-upstream usertags 653292 - status-NEW usertags 653292 + status-RESOLVED resolution-FIXED 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/20120917163413.30994.37720.btsl...@sonntag.debian.org
Re: Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD
On Thu, Sep 13, 2012 at 02:58:25PM +0200, Borislav Petkov wrote: Here's the script, let me know how it goes: Here's a more correct version. I'm not saying yours won't work based on the rdmsr and setpci output on your box, but here's a version which should pay attention to one other workaround and work on all K8s. HTH. -- #!/bin/bash # assuming a single CPU system nb_cfg=0xc001001f ht_tr_ctl=0x68 val=0x$(rdmsr $nb_cfg) # revert E131 workaround val=$(( $val ~(1 20) )) val=$(( $val | (1 32) )) val=$(printf 0x%08x $val) wrmsr $nb_cfg $val val=0x$(setpci -s 18.0 $ht_tr_ctl.l) # clear bits [22:21] val=$(( $val ~( 0x3 21) )) val=$(( $val | (1 21) )) val=$(printf 0x%08x $val) setpci -s 18.0 $ht_tr_ctl.l=$val echo Erratum 169 workaround applied. -- -- Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach GM: Alberto Bozzo Reg: Dornach, Landkreis Muenchen HRB Nr. 43632 WEEE Registernr: 129 19551 -- 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/20120917172345.gh13...@aftab.osrc.amd.com
Bug#679545: [RFC/PATCH] ia64, SR870, EFI bug breaks ata_piix, uninitialized ICH4 IDE EXBAR mem resource
On Sun, Sep 16, 2012 at 10:39 AM, Stephan Schreiber i...@fs-driver.org wrote: [0.065516] pci :00:1f.1: [8086:24cb] type 0 class 0x000101 [0.065530] pci :00:1f.1: reg 10: [io 0x-0x0007] [0.065541] pci :00:1f.1: reg 14: [io 0x-0x0003] [0.065552] pci :00:1f.1: reg 18: [io 0x-0x0007] [0.065563] pci :00:1f.1: reg 1c: [io 0x-0x0003] [0.065574] pci :00:1f.1: reg 20: [io 0x1000-0x100f] [0.065585] pci :00:1f.1: reg 24: [mem 0x-0x03ff] ... [1.640965] libata version 3.00 loaded. [1.641656] ata_piix :00:1f.1: version 2.13 [1.641671] ata_piix :00:1f.1: device not available (can't reserve [mem 0x-0x03ff]) [1.641747] ata_piix: probe of :00:1f.1 failed with error -22 ... lspci -vvxxx reports: 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corporation Device 3404 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 0 Region 0: I/O ports at 01f0 [size=8] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at 1000 [size=16] 00: 86 80 cb 24 05 00 80 02 02 8a 01 01 00 00 00 00 10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 20: 01 10 00 00 00 00 00 00 00 00 00 00 86 80 04 34 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 I agree that we should have a generic way to do this rather than an ia64-specific way. In this case you have EFI, but the same thing could happen with BIOS. The firmware left the memory BAR at 0x24 cleared (0x), but it also left the MEM bit in the command register disabled. So it seems like a Linux bug that we're trying to use that zero address from the BAR. If the firmware left the MEM or IO decode enable bit cleared, why would we assume it put anything useful in the corresponding BARs? What would break if we paid attention to the command register enables in the PCI core and just cleared the resource flags for MEM BARs if the MEM-decode bit was off, and those for IO BARs if the IO-decode bit was off? I don't know much of the ancient history here, so maybe there's a good reason why this works the way it currently does. Bjorn -- 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/CAErSpo6j==2_HsLrMsJ30SFZkG6q_JqrcKe=xma1woy4c_i...@mail.gmail.com
Bug#687997: linux-2.6: First line on boot gives me this message: ata1.00: failed to resume link (SControl 0) , but on the kernel log everithing is recognized right without errors so i think is a minor
Package: linux-2.6 Severity: minor -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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/20120917230002.2046.23312.report...@itk.openbsd.opengoku.ath.cx
Bug#687997: marked as done (linux-2.6: First line on boot gives me this message: ata1.00: failed to resume link (SControl 0) , but on the kernel log everithing is recognized right without errors so i
Your message dated Tue, 18 Sep 2012 04:33:52 +0100 with message-id 1347939232.4836.18.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#687997: linux-2.6: First line on boot gives me this message: ata1.00: failed to resume link (SControl 0) , but on the kernel log everithing is recognized right without errors so i think is a minor issue. has caused the Debian Bug report #687997, regarding linux-2.6: First line on boot gives me this message: ata1.00: failed to resume link (SControl 0) , but on the kernel log everithing is recognized right without errors so i think is a minor issue. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 687997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: minor -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Closing, this is not a useful bug report. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#687853: linux-image-3.2.0-3-amd64: Fan speed freezes, and hotkeys stop working. Laptop Lenovo Thinkpad L512 (2597AB2)
On Mon, 2012-09-17 at 11:15 +0400, evol wrote: 16.09.2012 22:12, Ben Hutchings пишет: On Sun, 2012-09-16 at 21:32 +0400, Igor wrote: [...] Please test withou the fglrx driver installed. Ben. without fglrx too most thus not what information it is not displayed in syslog I don't understand what you're saying. If you uninstall fglrx and reboot, does the same problem happen again? Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
