Florian Lohoff wrote:
Opened a bug in the Kernel Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=53101
Thanks! If I have any more questions, I'll ask them upstream.
Ciao,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe.
Thanks Ben, not sure how I missed 660425 the first time around.
On Wed, 2013-01-23 at 14:50 +, Ben Hutchings wrote:
On Tue, 2013-01-22 at 10:15 +0100, Mattias Eriksson wrote:
Hi!
I have switched back to the current stable kernel in squeeze, 2.6.32-46,
since I need the
machine to
Subject was: Re: fsync() on read-only RAID triggers BUG
On 27.01.2013 17:39, Christoph Hellwig wrote:
On Sat, Jan 26, 2013 at 07:44:40PM +, Ben Hutchings wrote:
I applied this on top of 3.2.37 and it certainly fixes the crash.
However I wonder whether fsync() should fail or should
Package: src:linux
Version: 3.2.35-2
Severity: normal
Dear Maintainer,
I'm experiencing what seems to be a kernel bug with read-only remounting
of a bind mount (creating a read-only bind mount). After running the
following commands, both /foo/dir_ro *and* /foo/dir become read-only:
mount
On 28.01.2013 11:32, Sebastian Riemer wrote:
O.K., then I hope Neil applies the attached patch. I've changed the
return value to success.
This is also something for linux-stable and should apply to many kernel
versions without an issue.
I've tried to race with continuous fsyncs against
self-compiled version of
http://people.debian.org/~jcristau/wheezy-drm34/
with headers
uptime 1day 11 hours (24 hours running)
tested:
Intel(R) Core(TM) i5-3450
Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
7 Series/C210 Series Chipset Family High Definition Audio Controller
On Sun, 27 Jan 2013 14:10:49 +, Jules Villard wrote:
On Sun, 27 Jan 2013 12:52:26 +, Ben Hutchings wrote:
On Sun, 2013-01-27 at 12:37 +, Jules Villard wrote:
Package: src:linux
Version: 3.2.35-2
Severity: normal
Dear Maintainer,
I hit a few BUGs at the end of
Le samedi 12 janvier 2013 à 21:54 +0100, Vincent Blut a écrit :
Le lundi 07 janvier 2013 à 23:55 +0100, Vincent Blut a écrit :
Le samedi 05 janvier 2013 à 17:25 +0100, Julien Cristau a écrit :
On Fri, Jan 4, 2013 at 17:13:35 +0100, Julien Cristau wrote:
Processing control commands:
reassign -1 mount
Bug #699157 [src:linux] linux-image-3.2.0-4-amd64: mount -o remount, ro on bind
mount causes source filesystem to become read-only
Bug reassigned from package 'src:linux' to 'mount'.
No longer marked as found in versions linux/3.2.35-2.
Ignoring
Control: reassign -1 mount
On Mon, 2013-01-28 at 04:37 -0600, Zev Weiss wrote:
Package: src:linux
Version: 3.2.35-2
Severity: normal
Dear Maintainer,
I'm experiencing what seems to be a kernel bug with read-only remounting
of a bind mount (creating a read-only bind mount). After
#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #698821 (http://bugs.debian.org/698821)
# Bug title: linux-image-3.2.0-4-amd64:
Please refer to the relevant history at the bottom of this email.
Summary for debian-release:
1. We have AMD and Intel microcode update packages in Wheezy and also in
stable-backports. These packages have been available for a reasonable
amount of time (~two months for AMD, ~three months
I'd like to report success with my HP EliteBook 8560w sporting an nVidia
GF106 video card and the 3.2.0-4.drm-amd64 kernel. The stock 3.2.35-2
kernel image results in a black screen once KMS kicks in and I've been
following the linux-image trunk packages from experimental instead. The
On Mon, Jan 28, 2013 at 03:07:58PM -0200, Henrique de Moraes Holschuh wrote:
[...]
2. Uptake of these packages was low, and only picked up a bit after an
announcement to some Debian MLs. However, once they started being
recommended by the linux-firmware-nonfree packages in Wheeze, there
Package: src:linux
Version: 3.7.3-1~experimental.1
Severity: important
Dear Maintainer,
after updating the linux-image-3.7-trunk-amd64 from
3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting,
the tools ps, pgrep and pkill (package procps) are always segfaulting:
=== Begin ===
Hi Sascha,
Sascha Silbe wrote:
after updating the linux-image-3.7-trunk-amd64 from
3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting,
the tools ps, pgrep and pkill (package procps) are always segfaulting:
Just to check: if you downgrade to 3.7.1 again, do the segfaults go
Processing commands for cont...@bugs.debian.org:
unarchive 611954
Bug #611954 {Done: Ben Hutchings b...@decadent.org.uk} [firmware-realtek]
installation-reports: broken installation on RTL8111-8168B
Unarchived Bug 611954
reopen 611954 !
Bug #611954 {Done: Ben Hutchings b...@decadent.org.uk}
I have recently recreated this bug when trying to netinstall wheezy from
pxe.
DHCP fails when trying to get ip-address during install. This applies to
squeeze as well as wheezy.
DHCP works during installation for lenny.
-- System information:
Debian Release: 7.0
Linux 3.2.0-4-amd64 #1 SMP
On Mon, 2013-01-28 at 13:39 +0100, Sebastian Riemer wrote:
On 28.01.2013 11:32, Sebastian Riemer wrote:
O.K., then I hope Neil applies the attached patch. I've changed the
return value to success.
This is also something for linux-stable and should apply to many kernel
versions
19 matches
Mail list logo
