Bug#286915: kernel-image-2.6.9-9-amd64-k8: 32 bit Alsa utilities do not work against 64 bit kernel

2004-12-22 Thread Paul Wagland
Package: kernel-image-2.6.9-9-amd64-k8 Version: 2.6.9-4 Severity: important When trying to start or use alsa I get the following errors: ioctl32(alsactl:4613): Unknown cmd fd(3) cmd(80045500){00} arg(d85c) on /dev/snd/controlC0 ioctl32(alsactl:5672): Unknown cmd fd(3) cmd(80045500){00} arg(f

Bug#285430: Patch for mkinitrd and the a100u2w

2004-12-22 Thread Seth Mattinen
Here's a patch that fixed the mkinitrd script in my case and allowed it to successfully build an image with the a100u2w module: --- mkinitrd2004-12-22 14:31:35.0 -0800 +++ mkinitrd-a100 2004-12-22 14:30:15.0 -0800 @@ -516,5 +516,6 @@ s/^GV

kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes UNACCEPT

2004-12-22 Thread Debian Installer
Rejected: Rejected: kernel-image-power3-smp_2.6.9-2_powerpc.deb: old version (100) in unstable >= new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb: old version (2.6.9-3) in unstable >= new version (2.6.9-2) targeted at unstable. Rejected:

Re: Problem with XFS and/or VM deadlock in 2.6.8

2004-12-22 Thread Lennart Sorensen
On Wed, Dec 22, 2004 at 06:21:03PM +, Christoph Hellwig wrote: > All this should be fixed in 2.6.10-rc3. The XFS code in Debian's 2.6.8 > is very much out of data and has various problems, but 2.6.8 is already > really old and the various required core code changes make it hard to > backport t

Re: Problem with XFS and/or VM deadlock in 2.6.8

2004-12-22 Thread Christoph Hellwig
On Wed, Dec 22, 2004 at 09:16:00AM -0500, Lennart Sorensen wrote: > I have been having trouble with the filesystem apparently locking up on > a P4 2.8GHz HT machine (1GB ram, dual 120G SATA in raid1 with LVM on > top). > > It locks up when I try and delete a lot of small files at once. > Yesterday

Re: Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

2004-12-22 Thread Greg Folkert
On Wed, 2004-12-22 at 01:23 -0800, Marc Singer wrote: > On Wed, Dec 22, 2004 at 03:39:32PM +0900, Horms wrote: > > I took a breif look at initrd and for reference have included > > how it handles mdadm below. I think that the important bit > > is that it passes not only the md device but its compon

Blank console text with kernel 2.6.8 and 2.6.9

2004-12-22 Thread Guy Roussin
Hi, I want to upgrade my debian SID/kernel 2.4 to kernel 2.6. If i use kernel-image-2.6.x : no problem, but, if i build my own kernel (from debian source), i loose konsoles text (Alt F1 - F6) ! During the boot process, just after the line "Calculating modules dependencies ...", the screen becomes b

Bug#284356: SONAME bumping and d-i

2004-12-22 Thread Horms
Hi, I have put together the packages that I would like to upload as kernel-source-2.4.27 2.4.27-7 and kernel-image-2.4.27-i386 2.4.27-7. This includes increasing the SONAME to 2. Could anyone who is interesetd please take a look. http://debian.vergenet.net/pending/ Andreas, let me know when you

Bug#286803: kernel-source-2.6.9: Kind of a memory leak in kernel 2.6?

2004-12-22 Thread Thiemo Seufer
MySQL Development wrote: [snip] > The problem is that this did not work out. Every time when I run a make on a > MySQL source tree, I "loose" some of my memory. More specifically spoken, the > amount of memory, called "Active" increases, while "Cached" decreases (names > are taken from /proc/meminf

Bug#286803: kernel-source-2.6.9: Kind of a memory leak in kernel 2.6?

2004-12-22 Thread MySQL Development
Package: kernel-source-2.6.9 Version: 2.6.9-3 Severity: normal Hi. I do not even know if this is a bug. I can only say that the kernel does not behave according to my expectations. The problem is not easy to explain, nor easy to reproduce. I'll try to explain with increasing detail. Stop to read w

Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

2004-12-22 Thread Marc Singer
On Wed, Dec 22, 2004 at 03:39:32PM +0900, Horms wrote: > I took a breif look at initrd and for reference have included > how it handles mdadm below. I think that the important bit > is that it passes not only the md device but its component > devices to mdadm -A (--assemble). It seems to me that as

Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

2004-12-22 Thread Marc Singer
On Wed, Dec 22, 2004 at 03:39:32PM +0900, Horms wrote: > On Tue, Dec 21, 2004 at 10:15:54AM -0800, Marc Singer wrote: > > On Mon, Dec 20, 2004 at 02:52:50AM +0100, Goswin von Brederlow wrote: > > > Marc Singer <[EMAIL PROTECTED]> writes: > > > > > > > On running mdadm --assemble /dev/md0 > > > > >

Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

2004-12-22 Thread Marc Singer
On Wed, Dec 22, 2004 at 03:39:32PM +0900, Horms wrote: > > Still, I wonder about the ioctl errors that I see with fdisk. > > I took a breif look at initrd and for reference have included > how it handles mdadm below. I think that the important bit > is that it passes not only the md device but its

Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

2004-12-22 Thread Horms
On Tue, Dec 21, 2004 at 10:15:54AM -0800, Marc Singer wrote: > On Mon, Dec 20, 2004 at 02:52:50AM +0100, Goswin von Brederlow wrote: > > Marc Singer <[EMAIL PROTECTED]> writes: > > > > > On running mdadm --assemble /dev/md0 > > > > > > mdadm[4247]: segfault at 002c rip 0804b1