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
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 su
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 bo
#
# 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 r
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
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 sing
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.o
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
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;
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.
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 kern
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.
Lo
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 awa
13 matches
Mail list logo
