On Sat, 2011-04-30 at 17:34 +0100, Ben Hutchings wrote:
Ian, should we apply the backport from
64141da587241301ce8638cc945f8b67853156ec to squeeze for bug #613634 et
al?
It's already in SVN for 2.6.32-34, seems to be in the changelog twice
even, once closing #614400 and then again closing
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 613658 + pending
Bug #613658 [linux-2.6] Please enable SQUASHFS_XZ et al for =2.6.38-rc1.
Added tag(s) pending.
End of message, stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 624505 + pending
Bug #624505 [linux-2.6] linux-image-2.6.38-2-amd64: easycap.ko module not
enabled
Ignoring request to alter tags of bug #624505 to the same tags
On 30/04/11 06:11, Jonathan Nieder wrote:
Two corrupt-EDID/dmesg-spam puzzles for you. Seems to be a
regression, though I'm not sure from when.
I have a Benq Product Name FP241W manufactured February 2007 Revision
B4-125 and used to use the DVI input. The EDID data in the DVI input
suddenly
On Sun, 2011-05-01 at 12:33 +0100, Ian Campbell wrote:
On Sat, 2011-04-30 at 17:34 +0100, Ben Hutchings wrote:
Ian, should we apply the backport from
64141da587241301ce8638cc945f8b67853156ec to squeeze for bug #613634 et
al?
It's already in SVN for 2.6.32-34, seems to be in the changelog
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial breakage of the screens occur with 2.6.38?
If so, you may want to try fixing your EDID info has explained in a
similar bug report[1], but be careful, it may cause more harm if
something goes
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-31
I've got a huge file server with about 3.5 TByte disk space (reiserfs),
64 GByte RAM and 2 quadcore CPUs. Trying to copy (rsync) about 2 TByte
data to this disk it takes a few minutes, the load goes up to 6 or
higher, then there is this
On -10.01.-28163 20:59, LN2 wrote:
Package: xserver-xorg-video-intel
Version: 2:2.13.0-6
Severity: important
The latest update to debian squeeze seems to have introduced the Bug reported
here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550942 .
(Upstream bug report can be found here
Package: linux-2.6
Version: 2.6.32-33
Severity: important
Since Linux 2.6.32 the following updates have been made to storage and
network drivers that might be used during installation. The list is
based on the Kernel Newbies list and may be incomplete. I have
excluded CAN and WAN drivers as
Package: linux-base
Version: 3.2
Severity: minor
Tags: patch
$ linux-version --help | head -n1
Usage: $0 compare VERSION1 OP VERSION2
It should be linux-version instead of $0.
--
Jakub Wilk
diff --git a/bin/linux-version b/bin/linux-version
--- a/bin/linux-version
+++ b/bin/linux-version
@@
On Sun, 2011-05-01 at 18:25 +0200, Harald Dunkel wrote:
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-31
I've got a huge file server with about 3.5 TByte disk space (reiserfs),
64 GByte RAM and 2 quadcore CPUs. Trying to copy (rsync) about 2 TByte
data to this disk it takes a few
On Sun, 2011-05-01 at 19:02 +0200, Jakub Wilk wrote:
Package: linux-base
Version: 3.2
Severity: minor
Tags: patch
$ linux-version --help | head -n1
Usage: $0 compare VERSION1 OP VERSION2
It should be linux-version instead of $0.
That's weird; I really thought I had seen it working!
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 624795 + pending
Bug #624795 [linux-base] linux-base: $0 in linux-version help
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if
On Sat, 2011-04-30 at 21:41 +0100, Adam D. Barratt wrote:
On Mon, 2011-04-25 at 17:37 +0100, Ben Hutchings wrote:
On Mon, 2011-04-25 at 17:35 +0100, Adam D. Barratt wrote:
On Wed, 2011-04-13 at 12:57 +0100, Ben Hutchings wrote:
I think there's still a Xen regression (since 2.6.32-31) to
Processing commands for cont...@bugs.debian.org:
block 624794 with 574523
Bug #624794 [linux-2.6] Missing support for various storage and network devices
Was not blocked by any bugs.
Added blocking bug(s) of 624794: 574523
thanks
Stopping processing here.
Please contact me if you need
[Sorry for the duplicate mail sent earlier to debian-kernel]
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial breakage of the screens occur with 2.6.38?
If so, you may want to try fixing your EDID info has explained in a
similar bug
On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
[Sorry for the duplicate mail sent earlier to debian-kernel]
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial breakage of the screens occur with 2.6.38?
If so, you may want to try
Processing commands for cont...@bugs.debian.org:
block 624794 with 609191
Bug #624794 [linux-2.6] Missing support for various storage and network devices
Was blocked by: 574523
Added blocking bug(s) of 624794: 609191
thanks
Stopping processing here.
Please contact me if you need assistance.
--
Le dimanche 01 mai 2011 à 16:51 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
[Sorry for the duplicate mail sent earlier to debian-kernel]
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
On Dom 01 May 2011 17:26:42 Thibaut Girka escribió:
[snip]
My bad, overlooked it since Stuart uses nouveau. However, it might be
related nonetheless (and might be a completely different issue as well).
Did your monitor fail right after an upgrade?
Yes, but I failed to check the versions of
On 01/05/11 22:26, Thibaut Girka wrote:
Anyway, I'd be really interested to hear from Stuart Pook: his story
sounds exactly like mine.
I'm not sure exactly what to say. My screen/PC died on about 23 February. At that time it
would not even show BIOS messages. I started to try and understand
Processing commands for cont...@bugs.debian.org:
retitle 525717 cpu soft lockup - freeze
Bug #525717 [linux-2.6] report bug
Changed Bug title to 'cpu soft lockup - freeze' from 'report bug'
tags 525717 moreinfo
Bug #525717 [linux-2.6] cpu soft lockup - freeze
Added tag(s) moreinfo.
thanks
Le dimanche 01 mai 2011 à 17:47 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
[snip]
Did you mean the patch to tell dri to forget about bad checksums? If so, I
already tried it and worked fine.
If you are talking about something else, please give me some link :-)
I'm not talking
On Dom 01 May 2011 18:09:27 Thibaut Girka escribió:
[snip]
I'm not talking about ignoring broken EDIDs, but about actually fixing
them[1].
This is clearly not my problem. I have two monitors, both the same brand and
model. One is connected to the VGA output and the other one on the DVI. No
On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@decadent.org.uk wrote:
On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote:
I run what I imagine is a fairly unusual disk setup on my laptop,
consisting of:
ssd - raid1 - dm-crypt - lvm - ext4
I use the raid1 as a
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-5squeeze
Severity: normal
I installed Debian squeeze (linux-image-2.6.32-5-amd64) and I get
segfaulting randomly (every 10-30 minutes) when I run a gamesserver.This
problem appears on two computers where I installed amd64
kernel.Computers
On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote:
On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@decadent.org.uk
wrote:
On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote:
I run what I imagine is a fairly unusual disk setup on my laptop,
consisting of:
Your message dated Mon, 02 May 2011 01:05:07 +0100
with message-id 1304294707.2833.115.camel@localhost
and subject line Re: Bug#624840: linux-image-2.6.32-5-amd64: error 4 in
ld-2.11.2.so
has caused the Debian Bug report #624840,
regarding linux-image-2.6.32-5-amd64: error 4 in ld-2.11.2.so
to be
Package: nfs-common
Version: 1:1.2.2-4
Severity: normal
Hello,
The manpage for rpc.idmapd lists the -d, -U and -G options as being
valid for rpc.idmapd. However, trying to use the -d option gives the
following error:
% sudo /usr/sbin/rpc.idmapd -vvv -f -d localdomain
rpc.idmapd: the -d, -U,
On Mon, 02 May 2011 01:00:57 +0100 Ben Hutchings b...@decadent.org.uk wrote:
On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote:
On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@decadent.org.uk
wrote:
On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote:
I
On 05/01/2011 08:00 PM, Ben Hutchings wrote:
On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote:
Hi, Ben. Can you explain why this is not expected to work? Which part
exactly is not expected to work and why?
Adding another type of disk controller (USB storage versus whatever
On Sun, 2011-05-01 at 20:42 -0400, Daniel Kahn Gillmor wrote:
On 05/01/2011 08:00 PM, Ben Hutchings wrote:
On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote:
Hi, Ben. Can you explain why this is not expected to work? Which part
exactly is not expected to work and why?
On Mon, 02 May 2011 02:04:18 +0100, Ben Hutchings b...@decadent.org.uk wrote:
On Sun, 2011-05-01 at 20:42 -0400, Daniel Kahn Gillmor wrote:
So far as I'm aware, the RAID may stop working, but without loss of data
that's already on disk.
What exactly does RAID may stop working mean? Do you
} -Original Message-
} From: linux-raid-ow...@vger.kernel.org [mailto:linux-raid-
} ow...@vger.kernel.org] On Behalf Of NeilBrown
} Sent: Sunday, May 01, 2011 8:22 PM
} To: Ben Hutchings
} Cc: Jameson Graef Rollins; 624...@bugs.debian.org; linux-
} r...@vger.kernel.org
} Subject: Re:
affects 624343 debian-installer
thanks
I note that debian-installer happily creates LVM-over-RAID and
dmcrypt-over-RAID setups (and lvm-over-dmcrypt-over-RAID setups, for
that matter), and provides no warnings to the admin that these RAiD
setups may not be re-syncable in the face of hardware
On 05/01/2011 08:22 PM, NeilBrown wrote:
However if there is another layer in between md and the filesystem - such as
dm - then there can be problem.
There is no mechanism in the kernl for md to tell dm that things have
changed, so dm never changes its configuration to match any change in the
Processing commands for cont...@bugs.debian.org:
affects 624343 debian-installer
Bug #624343 [linux-2.6] linux-image-2.6.38-2-amd64: frequent message bio too
big device md0 (248 240) in kern.log
Added indication that 624343 affects debian-installer
thanks
Stopping processing here.
Please
37 matches
Mail list logo
