Re: fstab update for persistent device names

2007-07-27 Thread dann frazier
On Fri, Jul 27, 2007 at 10:24:19AM +0200, maximilian attems wrote: > On Fri, Jul 27, 2007 at 09:23:37AM +0200, Andreas Barth wrote: > > * Bastian Blank ([EMAIL PROTECTED]) [070726 11:40]: > > > For the libata-pata support we need to change fstab on several arches to > > > not break all systems whic

Re: fstab update for persistent device names

2007-07-27 Thread Steve Langasek
On Thu, Jul 26, 2007 at 07:42:20PM +0200, Bastian Blank wrote: > > For 4), we could either try and incorporate all config file knowledge > > in the utility, or provide a hook system by which we make a name map > > available but each package is responsible for doing its own > > renaming. The latter

Bug#424661: usblp unusable (connect/disconnect) on 2.6.21 / 2.6.22

2007-07-27 Thread Jeremy Lainé
I am seeing a problem similar to the one described in bug #424661, my USB printer (Samsung ML-2010) is constantly connecting / disconnecting when running kernels 2.6.21 or 2.6.22. It works absolutely fine with 2.6.18. The logs show a strange pattern of disconnect/reconnect exactly every 30s, I

Re: 2.6.22 - broken on ia64 and mipsel

2007-07-27 Thread dann frazier
On Fri, Jul 27, 2007 at 09:55:27PM +0200, Martin Michlmayr wrote: > * Bastian Blank <[EMAIL PROTECTED]> [2007-07-24 17:21]: > > 2.6.22 is currently broken on ia64 and mipsel. > > - mipsel: broken config. > > I fixed this in trunk a while ago, but I just commited it to the sid > branch as well. -3

Scheduling 2.6.22-3

2007-07-27 Thread Bastian Blank
Hi folks I'd like to schedule 2.6.22-3 for tomorrow, it should fix ia64 and mipsel and is complete than. Bastian -- You can't evaluate a man by logic alone. -- McCoy, "I, Mudd", stardate 4513.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Tro

Re: 2.6.22 - broken on ia64 and mipsel

2007-07-27 Thread Martin Michlmayr
* Bastian Blank <[EMAIL PROTECTED]> [2007-07-24 17:21]: > 2.6.22 is currently broken on ia64 and mipsel. > - mipsel: broken config. I fixed this in trunk a while ago, but I just commited it to the sid branch as well. -3 can be released now as far as I'm concerned. -- Martin Michlmayr http://www.

Bug#434904: linux-image-2.6.22-1-sparc64: sbus drivers not autoloaded, boot fails

2007-07-27 Thread Meelis Roos
Subject: linux-image-2.6.22-1-sparc64: sbus drivers not autoloaded, boot fails Package: linux-image-2.6.22-1-sparc64 Version: 2.6.22-2 Severity: important *** Please type your report below this line *** I upgraded linux-image-2.6.21-1-sparc64 to 2.6.22-1-sparc64 on my SBus-only Sun Ultra 1. It app

Bug#422819: And another trace

2007-07-27 Thread Carsten Leonhardt
A guest (2 vcpus) was to be rebooted, then the host hung itself up: Jul 27 12:46:45 kernel: --- [cut here ] - [please bite here ] - Jul 27 12:46:45 kernel: Kernel BUG at drivers/xen/core/evtchn.c:481 Jul 27 12:46:45 kernel: invalid opcode: [1] SMP Jul 27 12:46:45 kern

Bug#410807: XEN hangs on xm create

2007-07-27 Thread Vogler, Hartmut
Hi, i'm running Debian etch on a HP Proliant DL580 and i need to get the system productiv. If i run a "xm create" sometimes i get the kernel messages: kernel: kernel BUG at drivers/xen/core/evtchn.c:481! kernel: invalid opcode: [#1] kernel: SMP kernel: CPU:4 kernel: EIP is at retrigger+

Bug#434551: reassign to libraw1394

2007-07-27 Thread Holger Levsen
Hi, shouldnt this bug get reassigned to libraw1394? regards, Holger pgpA23TWcwc2D.pgp Description: PGP signature

Processed: severity of 434867 is important

2007-07-27 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > severity 434867 important Bug#434867: linux-image-2.6.18-4-686: 2.6.18.dfsg.1-12etch2 hangs on boot after "USB disconnect" Severity set to `important' from `critical' > End of messa

Bug#434867: linux-image-2.6.18-4-686: 2.6.18.dfsg.1-12etch2 hangs on boot after "USB disconnect"

2007-07-27 Thread Alexander Myodov
Package: linux-image-2.6.18-4-686 Severity: critical Justification: breaks the whole system After "aptitude upgrade"-ing the computer, which caused the 2.6.18.dfsg.1-12etch2 of linux-image-2.6.18-4-686 to be installed, the computer freezes on boot somewhere after initializing the USB. Previously

Bug#401035: asking upstream with more details

2007-07-27 Thread Mikko Rapeli
http://bugzilla.kernel.org/show_bug.cgi?id=8816 To summarize: Drive size changes between Debian kernels 2.6.8-4 and 2.6.10-1 due stroke being enabled by default. Kernels after 2.6.13-1 probe the last sector when propably looking for partitions and the drive fails silently and loudly after 2.6.16-

Bug#408809: marked as done (please add armel support)

2007-07-27 Thread Debian Bug Tracking System
Your message dated Fri, 27 Jul 2007 11:51:54 +0300 with message-id <[EMAIL PROTECTED]> and subject line please add armel support has caused the attached Bug report 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 responsib

Re: fstab update for persistent device names

2007-07-27 Thread maximilian attems
On Thu, 26 Jul 2007, Bastian Blank wrote: > On Thu, Jul 26, 2007 at 10:47:00AM -0600, dann frazier wrote: > > > > - /dev/disk/by-uuid: UUID of filesystem. Maybe we want the uuid of md > > > devices also? > > Do all filesystems support UUID? > > No. which don't? afair the ubuntu transition ha

Re: fstab update for persistent device names

2007-07-27 Thread maximilian attems
On Fri, Jul 27, 2007 at 09:23:37AM +0200, Andreas Barth wrote: > * Bastian Blank ([EMAIL PROTECTED]) [070726 11:40]: > > For the libata-pata support we need to change fstab on several arches to > > not break all systems which uses them. > > > > We need to decide which arches needs this rewrite now

Re: fstab update for persistent device names

2007-07-27 Thread Goswin von Brederlow
dann frazier <[EMAIL PROTECTED]> writes: > On Thu, Jul 26, 2007 at 07:42:20PM +0200, Bastian Blank wrote: >> On Thu, Jul 26, 2007 at 10:47:00AM -0600, dann frazier wrote: >> > > We need to decide which arches needs this rewrite now and which value >> > > should be filed in. >> > And also, how shou

Re: fstab update for persistent device names

2007-07-27 Thread Andreas Barth
* Bastian Blank ([EMAIL PROTECTED]) [070726 11:40]: > For the libata-pata support we need to change fstab on several arches to > not break all systems which uses them. > > We need to decide which arches needs this rewrite now and which value > should be filed in. I'd like to ask you to postpone s