Bug#706129: reboot will fix this
This occurs because of commit 4189aa4ceebb1cd2b216d88980e35399e299c8c5, which was recently added to the kernel; it calls kill_bdev, which previous versions of the nbd driver didn't. This probably means you've upgraded your kernel package but haven't rebooted yet. If you do, this issue should go away. (Not closing the bug, since this is an ABI change, and presumably that means the kernel should bump its ABI version -- but I'm leaving that to kernel maintainers to decide) -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- 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/5178f955.2080...@debian.org
Bug#700333: Stack trace
On Mon, 22 Apr 2013, Thomas Gleixner wrote: With the patch below, the box should survive and we should see a Spurious HPET timer interrupt on HPET timer... entry in dmesg. That's a first workaround to confirm my theory. I'll look into the HPET code how we can avoid that at all. Looks like we can't do anything about that in the HPET code itself. Vitaliy, could you try that patch ? Thanks, tglx -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.LFD.2.02.1304251139340.21884@ionos
Bug#706129: reboot will fix this
On Thu, Apr 25, 2013 at 11:37:25 +0200, Wouter Verhelst wrote: This occurs because of commit 4189aa4ceebb1cd2b216d88980e35399e299c8c5, which was recently added to the kernel; it calls kill_bdev, which previous versions of the nbd driver didn't. This probably means you've upgraded your kernel package but haven't rebooted yet. If you do, this issue should go away. (Not closing the bug, since this is an ABI change, and presumably that means the kernel should bump its ABI version -- but I'm leaving that to kernel maintainers to decide) The ABI number gets bumped when a newer kernel stops being compatible with old modules, not the other way around. So I think this bug should be closed as invalid. Cheers, Julien signature.asc Description: Digital signature
Bug#706129: reboot will fix this
On 25-04-13 12:09, Julien Cristau wrote: On Thu, Apr 25, 2013 at 11:37:25 +0200, Wouter Verhelst wrote: This occurs because of commit 4189aa4ceebb1cd2b216d88980e35399e299c8c5, which was recently added to the kernel; it calls kill_bdev, which previous versions of the nbd driver didn't. This probably means you've upgraded your kernel package but haven't rebooted yet. If you do, this issue should go away. (Not closing the bug, since this is an ABI change, and presumably that means the kernel should bump its ABI version -- but I'm leaving that to kernel maintainers to decide) The ABI number gets bumped when a newer kernel stops being compatible with old modules, not the other way around. I thought as much, but wasn't sure. So I think this bug should be closed as invalid. In that case, I agree. -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. signature.asc Description: OpenPGP digital signature
Bug#706129: reboot will fix this
The reboot with 3.2.0-4-amd64 did not fix this problem for me. (I have tried it) Instead I have now downgraded to 3.2.0-3-amd64 and this works as workaround. -Original Message- From: Julien Cristau [mailto:jcris...@debian.org] Sent: Donnerstag, 25. April 2013 12:10 To: Wouter Verhelst; 706...@bugs.debian.org Cc: 706129-submit...@bugs.debian.org Subject: Bug#706129: reboot will fix this On Thu, Apr 25, 2013 at 11:37:25 +0200, Wouter Verhelst wrote: This occurs because of commit 4189aa4ceebb1cd2b216d88980e35399e299c8c5, which was recently added to the kernel; it calls kill_bdev, which previous versions of the nbd driver didn't. This probably means you've upgraded your kernel package but haven't rebooted yet. If you do, this issue should go away. (Not closing the bug, since this is an ABI change, and presumably that means the kernel should bump its ABI version -- but I'm leaving that to kernel maintainers to decide) The ABI number gets bumped when a newer kernel stops being compatible with old modules, not the other way around. So I think this bug should be closed as invalid. 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/5a6aeb9bdc30464ab050fd4fc5e4c0310502e...@g4w3300.americas.hpqcorp.net
Bug#706129: reboot will fix this
On Thu, Apr 25, 2013 at 10:40:00 +, Schumacher, Bernd wrote: The reboot with 3.2.0-4-amd64 did not fix this problem for me. (I have tried it) Show logs, then, because your initial report was with an out of date kernel image. Cheers, Julien signature.asc Description: Digital signature
Bug#706129: reboot will fix this
I have now rebooted. You are right no problem anymore. The only difference to a previous reboot, where this did not work, is, that I have done apt-get update/upgrade meanwhile. Thank you for helping. Please close the bug. -Original Message- From: Julien Cristau [mailto:jcris...@debian.org] Sent: Donnerstag, 25. April 2013 14:13 To: Schumacher, Bernd; 706...@bugs.debian.org Cc: 706...@bugs.debian.org; Wouter Verhelst; 706129-submit...@bugs.debian.org Subject: Re: Bug#706129: reboot will fix this On Thu, Apr 25, 2013 at 10:40:00 +, Schumacher, Bernd wrote: The reboot with 3.2.0-4-amd64 did not fix this problem for me. (I have tried it) Show logs, then, because your initial report was with an out of date kernel image. 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/5a6aeb9bdc30464ab050fd4fc5e4c0310502e...@g4w3300.americas.hpqcorp.net
Bug#685407: More information
linux-image-3.2.0-4-amd64 libnfsidmap2:amd64 0.25-4 amd64NFS idmapping library nfs-common 1:1.2.6-3 amd64 nfs-kernel-server 1:1.2.6-3 amd64support for NFS kernel server $ tail /var/log/syslog Apr 24 21:46:38 singapore kernel: [ 348.727292] NFS: directory html/xtronics contains a readdir loop.Please contact your server vendor. The file: contacts.htmler.htm has duplicate cookie 31 I'm not seeing any more recent debian kernels available other than trunk - and it breaks initramfs-tools: linux-image-3.8-trunk-amd64 : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed So I'm going to attempt the kernel patch.. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://secure.transtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Truth is mighty and will prevail. There is nothing wrong with this, except that it ain't so. --Mark Twain -- 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/51793b07.10...@xtronics.com
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #609846 (http://bugs.debian.org/609846) # Bug title: Toshiba Satellite battery not recognized by acpi # * http://bugzilla.kernel.org/show_bug.cgi?id=15707 # * remote status changed: ASSIGNED - RESOLVED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 609846 + fixed-upstream Bug #609846 [linux-2.6] Toshiba Satellite battery not recognized by acpi Added tag(s) fixed-upstream. usertags 609846 - status-ASSIGNED Usertags were: status-ASSIGNED. Usertags are now: . usertags 609846 + status-RESOLVED resolution-CODE-FIX There were no usertags set. Usertags are now: resolution-CODE-FIX status-RESOLVED. thanks Stopping processing here. Please contact me if you need assistance. -- 609846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609846 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.13669196813537.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 #609846 (http://bugs.debian.org/609846) # Bug title: Toshiba Satellite battery not recognized by acpi # * http://bugzilla.kernel.org/show_bug.cgi?id=15707 # * remote status changed: ASSIGNED - RESOLVED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 609846 + fixed-upstream usertags 609846 - status-ASSIGNED usertags 609846 + status-RESOLVED resolution-CODE-FIX 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/20130425194217.20574.13279.btsl...@sonntag.debian.org
Bug#706173: libata: errors with sil3826 port multiplier, needs same handling as sil3726
Package: src:linux Version: 3.2.41-2 Severity: important Tags: upstream patch When attaching an sil3826-based SATA port multiplier to a sil3132 controller (though this would also apply to any other controller supporting these port multipliers), many errors are produced and, if attached prior to booting and not hot-plugged, the boot process can be delayed for more than 10 minutes. It seems as though sil3826-based port multipliers have the same quirks as their predecessors based on sil3726, which required special handling in libata. There is a relevant bug report in the Red Hat bugzilla at https://bugzilla.redhat.com/show_bug.cgi?id=890237. The patch that fixes this problem for me was sent to the linux-ide mailing list in January 2013 and can be seen at http://marc.info/?l=linux-idem=135819729516871. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'stable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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 Versions of packages linux-image-3.2.0-4-amd64 depends on: ii debconf [debconf-2.0] 1.5.49 ii initramfs-tools [linux-initramfs-tool] 0.109 ii kmod9-2 ii linux-base 3.5 ii module-init-tools 9-2 Versions of packages linux-image-3.2.0-4-amd64 recommends: ii firmware-linux-free 3.2 Versions of packages linux-image-3.2.0-4-amd64 suggests: pn debian-kernel-handbook none ii grub-pc 1.99-26 pn linux-doc-3.2 none Versions of packages linux-image-3.2.0-4-amd64 is related to: pn firmware-atheros none pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimaxnone pn firmware-ipw2x00 none pn firmware-ivtv none pn firmware-iwlwifi none pn firmware-libertas none pn firmware-linux none ii firmware-linux-nonfree 0.36+wheezy.1 pn firmware-myricom none pn firmware-netxennone pn firmware-qlogicnone ii firmware-ralink0.36+wheezy.1 ii firmware-realtek 0.36+wheezy.1 ii xen-hypervisor-4.1-amd64 [xen-hypervisor] 4.1.4-2 -- debconf information excluded -- Joseph Spiros jos...@josephspiros.com +1 (440) 707-6855 -- 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/20130425204033.ga10...@hylia.us
Bug#706131: MegaRAID SAS 2108 (Dell PERC H700) FW in FAULT state with old BIOS
reassign 706131 release-notes tags 706131 + wheezy retitle 706131 [squeeze-wheezy regression] LSI MegaRAID SAS 2108 (aka Dell PERC H700 RAID) requires firmware update quit Hi, Bernhard Schmidt wrote: I'm quite sure we also booted Squeeze sucessfully on it, but I'm going to verify that. They had never received any firmware update, which made the main BIOS version 2.1.15 and the LSI BIOS 12.3. Wheezy (both RC1 and daily from April 22nd) could not be installed, because it did not detect any disk. dmesg showed this (typed from a screenshot, excuse any errors) megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011 megasas: 0x1000:0x0079:0x1028:0x1f17: bus 3:slot 0:func 0 megaraid_sas: :03:00.0: setting latency timer to 64 megasas: Waiting for FW to come to ready state megasas: FW in FAULT state!! [...] None of those workarounds listed in the bugs worked for us. After a 2-hour session upgrading all the firmware on the system (which bumped the BIOS to 6.something and LSI to 12.10) it worked just fine. Thanks for reporting. I'm reassigning this report to release-notes so we can get this documented. If you can think of some wording for section 4.5 or 5 of the release notes[1], that would be excellent. Hope that helps, Jonathan [1] http://www.debian.org/releases/wheezy/releasenotes -- 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/20130426044604.GA3262@elie.Belkin
Processed: Re: MegaRAID SAS 2108 (Dell PERC H700) FW in FAULT state with old BIOS
Processing commands for cont...@bugs.debian.org: reassign 706131 release-notes Bug #706131 [src:linux] linux-image-3.2.0-4-amd64: MegaRAID SAS 2108 (Dell PERC H700) FW in FAULT state with old BIOS Bug reassigned from package 'src:linux' to 'release-notes'. No longer marked as found in versions linux/3.2.41-2. Ignoring request to alter fixed versions of bug #706131 to the same values previously set tags 706131 + wheezy Bug #706131 [release-notes] linux-image-3.2.0-4-amd64: MegaRAID SAS 2108 (Dell PERC H700) FW in FAULT state with old BIOS Added tag(s) wheezy. retitle 706131 [squeeze-wheezy regression] LSI MegaRAID SAS 2108 (aka Dell PERC H700 RAID) requires firmware update Bug #706131 [release-notes] linux-image-3.2.0-4-amd64: MegaRAID SAS 2108 (Dell PERC H700) FW in FAULT state with old BIOS Changed Bug title to '[squeeze-wheezy regression] LSI MegaRAID SAS 2108 (aka Dell PERC H700 RAID) requires firmware update' from 'linux-image-3.2.0-4-amd64: MegaRAID SAS 2108 (Dell PERC H700) FW in FAULT state with old BIOS' quit Stopping processing here. Please contact me if you need assistance. -- 706131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706131 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.13669515797666.transcr...@bugs.debian.org
