Bug#552610: modinfo: could not find module /lib/modules/2.6.31-1-amd64//lib/modules/2.6.31-1-amd64/kernel/sound/core/snd.ko

2009-10-28 Thread Stepan Golosunov
Package: linux-2.6 Version: 2.6.31-1 Severity: important When installing on lenny, linux-image-2.6.31-1-amd64 generates lots of warnings with wrong modules paths. Looks like firmware check is not working. Распаковывается пакет linux-image-2.6.31-1-amd64 (из файла

Re: [Pkg-xen-devel] oldschool xen kernel on sid

2009-10-28 Thread Thomas Goirand
Bastian Blank wrote: On Tue, Oct 27, 2009 at 10:32:52PM +0100, Bastian Blank wrote: On Tue, Oct 27, 2009 at 10:05:45PM +0100, Thomas Schwinge wrote: Bastian, is any of your Xen dom0 work available somewhere? Yes. http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test. The xen utils are

Re: [Pkg-xen-devel] oldschool xen kernel on sid

2009-10-28 Thread Bastian Blank
On Wed, Oct 28, 2009 at 02:22:49PM +0800, Thomas Goirand wrote: Would this kernel work as a dom0 in Lenny? No. It needs a newer hypervisor. Can you also provide the source package so I can recompile it with the Lenny gcc/libs? The patch is there. You can apply it on the

Re: Building vanilla kernel .debs

2009-10-28 Thread David Woodhouse
On Tue, 2009-10-27 at 20:40 +0100, maximilian attems wrote: hello David, I have a question on howto ship firmware build out of make deb-pkg in linux-2.6. On Mon, 26 Oct 2009, Ben Hutchings wrote: On Mon, 2009-10-26 at 21:27 +0100, Marc Haber wrote: Hi, Is it a feature

Bug#552296: acknowledged by developer (closing 552296)

2009-10-28 Thread Xan
On Mon, 2009-10-26 at 14:40 +0100, Pierre Maziere wrote: It seems that the update switched the /dev/sda and /dev/sdb which explains the freeze during the boot sequence. I switched the usb plugs and everything is now back to normal. sorry for the noise You should not expect that USB disks

Re: Debian Kernel Group Meeting

2009-10-28 Thread Pasi Kärkkäinen
On Tue, Oct 27, 2009 at 07:56:20PM +0100, Bastian Blank wrote: On Tue, Oct 27, 2009 at 08:13:27PM +0200, Pasi Kärkkäinen wrote: pv_ops dom0 patches will require more maintenance than the forward-ports though.. since it's not yet feature-complete, and will have many patches and fixes still..

Processed: tagging 552422

2009-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 552422 + pending Bug #552422 [linux-2.6] linux-2.6 2.6.31-1 FTBFS on mipsel Added tag(s) pending. End of message, stopping processing here. Please contact me if you

Bug#514260: linux-image-2.6.26-1-amd64: kernel does not support multiple, not similarm soundcards

2009-10-28 Thread Olaf Zevenboom
Hi Ben, Thanks for the reply. Situation is as follows: my motherboard has an onboard soundcard. I own several PCI card soundcards. I tried them all, all to the same result. If I have besides the onboard card one PCI soundcard in the system (so 2 soundcards in total) the sound system does not give

Re: Building vanilla kernel .debs

2009-10-28 Thread Marc Haber
On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need for it -- the firmware should live in /lib/firmware. If there are incompatible versions of firmware, then they'll have a different filename and can co-exist. This is, however, a challenge

Re: Building vanilla kernel .debs

2009-10-28 Thread Marc Haber
On Wed, Oct 28, 2009 at 10:17:52AM +, David Woodhouse wrote: On Wed, 2009-10-28 at 10:48 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need for it -- the firmware should live in /lib/firmware. If there

Re: Building vanilla kernel .debs

2009-10-28 Thread David Woodhouse
On Wed, 2009-10-28 at 10:48 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need for it -- the firmware should live in /lib/firmware. If there are incompatible versions of firmware, then they'll have a different

Re: Building vanilla kernel .debs

2009-10-28 Thread David Woodhouse
On Wed, 2009-10-28 at 11:31 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 10:17:52AM +, David Woodhouse wrote: On Wed, 2009-10-28 at 10:48 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need for it -- the

Re: RFC: Bug handling policy

2009-10-28 Thread Andres Salomon
Hi Ben, Ack on everything below. Some comments are below. On Sat, 17 Oct 2009 17:14:54 +0100 Ben Hutchings b...@decadent.org.uk wrote: I've drafted a policy based on what I believe to be best practice. Please comment - is anything wrong, or anything missing? I also left some questions in

Bug#515741: please test p-u kernel

2009-10-28 Thread dann frazier
There is a potential fix for this issue in the 2.6.26-20 kernel in proposed-updates. Can someone who has seen this issue please verify the fix? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Re: RFC: Bug handling policy

2009-10-28 Thread Berni Elbourn
Andres Salomon wrote: 2. Severities Many submitters believe that their bug meets one of the following criteria for high severity. We interpret them as follows and will downgrade as appropriate: 'critical: makes unrelated software on the system (or the whole system) break...' The bug must

Re: Building vanilla kernel .debs

2009-10-28 Thread maximilian attems
On Wed, 28 Oct 2009, Marc Haber wrote: On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need for it -- the firmware should live in /lib/firmware. If there are incompatible versions of firmware, then they'll have a different filename and

Bug#552696: could not find module /lib/modules/2.6.31-1-amd64//lib/modules/2.6.31-1-amd64/...

2009-10-28 Thread Stepan Golosunov
Package: linux-2.6 Version: 2.6.31-1 Severity: important When installing on lenny, linux-image-2.6.31-1-amd64 generates lots of warnings with wrong modules paths. Looks like firmware check is not working. Распаковывается пакет linux-image-2.6.31-1-amd64 (из файла

Re: RFC: Bug handling policy

2009-10-28 Thread Andres Salomon
On Wed, 28 Oct 2009 19:38:49 + Berni Elbourn be...@elbournb.fsnet.co.uk wrote: Andres Salomon wrote: 2. Severities Many submitters believe that their bug meets one of the following criteria for high severity. We interpret them as follows and will downgrade as appropriate:

Bug#552296: acknowledged by developer (closing 552296)

2009-10-28 Thread Bastian Blank
On Tue, Oct 27, 2009 at 01:24:58PM +0100, Xan wrote: Ben, it's a bug. At least formally. Maybe, but not in the kernel. The kernel never documented this values to be stable. A capricious swap between harddrives that hangs the system it's a bug I think,

Bug#552706: BUG: soft lockup - CPU#0 stuck for 61s! - :nfs:nfs_access_cache_shrinker

2009-10-28 Thread Bernd Zeimetz
Package: linux-2.6 Version: 2.6.26-19 Severity: important We get the following backtrace way too often, it repeats for all CPUs, but I'm pasting it only once here. [633582.838114] BUG: soft lockup - CPU#0 stuck for 61s! [init:1] [633582.838114] Modules linked in: nfs lockd nfs_acl sunrpc ipip

Re: [Pkg-xen-devel] oldschool xen kernel on sid

2009-10-28 Thread Thomas Schwinge
Hello! On Wed, Oct 28, 2009 at 12:43:00AM +0100, I wrote: 10.jpg: fstype vg0-boole-root (ext3); mount /dev/mapper/vg0-boole--root /root (failed -- no such file or directory?!). I just noticed in linux-image-2.6.31-1-xen-amd64_2.6.31-1_amd64.deb's /boot/config-2.6.31-1-xen-amd64 file:

Bug#537305: Still present in 2.6.30-2

2009-10-28 Thread Robert Jacobs
I recently tried installing and rebooting into 2.6.30-2 on this machine -- the problem with dropping blocks of audio is still present. (This also happens on my desktop, which is an athlon-tbird with a snd-cmipci) Thanks, Robert Jacobs -- To UNSUBSCRIBE, email to

Processed: tagging 552465

2009-10-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 552465 + pending Bug #552465 [linux-2.6] r8169 does not work correctly for RTL8111 Added tag(s) pending. End of message, stopping processing here. Please contact me

Bug#552810: initramfs-tools: Localtime not set during initramfs boot leading to wrong fsck.ext4 errors

2009-10-28 Thread ed . gomez
Package: initramfs-tools Version: 0.93.4 Severity: important *** Please type your report below this line *** After a power grid problem in my neighborhood, my workstation rebooted and detected problems in the ext4 LVM volumes. It appears that after a manual fsck.ext4, these problems were

Possible problems in your Debian packages

2009-10-28 Thread DDPOMail robot
This is an automated mail. These mails are sent twice a month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail === linux-2.6: = There are 26 unfixed security issue(s), please fix them. See

Bug#523735: please consider supporting the experimental kernel-package out of the box

2009-10-28 Thread Michal Suchanek
Package: initramfs-tools As I understand it this hook script that is being pached was up to now essentially equivalent to the command 'true'. It would detect if the kernel installed is an official Debian kernel or a kernel-package kernel and then do nothing in both cases because the kernels

Bug#535008: configure_networking: support BOOTIF variable set by pxelinux

2009-10-28 Thread Gabor Gombas
Hi, aolMee too!/aol It'd be really nice to have this integrated. To add something constructive, mdadm, and lvm2 scripts already use sed without checking for it or making sure that it is available, so the use of sed should not be a problem. cryptsetup also uses sed but it at least forces

Bug#552987: linux-image-2.6.30-2-686-bigmem: intel i810 module is not found by Xorg

2009-10-28 Thread Adda Rathbone
Package: linux-image-2.6.30-2-686-bigmem Version: 2.6.30-8 Severity: normal If you use the linux 2.6.30 bigmem kernel with an intel graphic driver (i810) Xorg does not find/use the intel driver. I don't think this is an xorg issue, because if I start the normal 2.6.30 kernel everything is fine.