Processed: severity of 528028 is important

2009-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 528028 important
Bug#528028: BUG: Bad page state in process md?_resync pfn:hex
Severity set to `important' from `critical'


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: tagging 528094

2009-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 528094 pending
Bug#528094: smc911x - smc91x
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#528173: linux-image-2.6.26-2-686: using xorg do not honour SWCursor (is ok with 2.6.18)

2009-05-11 Thread Leonardo
Package: linux-image-2.6.26-2-686
Version: 2.6.26-15
Severity: normal

Updating to lenny xorg stopped to work.
rienstalling it it changed is autodetection from vesa to openchrome drivers
(this coukd be acceptable, since these are specific for that chipset)
but on the other part it stopped working, since cursor handling is incorrect, 
leaving tail and resetting to background image on passing on a non-focused 
window.
I added SW cursor but unable to let it work.
booting with 2.6.18 from etch it WORKS OK, both with openchrome and with vesa, 
either with or without swcursor.
video board is: 
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE 
[Chrome 9] (rev 11)


-- Package-specific info:

-- System Information:
Debian Release: 5.0.1
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-5-686 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-2-686 depends on:
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.26-2-686 recommends:
ii  libc6-i6862.7-18 GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.26-2-686 suggests:
ii  grub   0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26   none(no description available)

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#528176: [linux-image-2.6-686] linux-image-2.6-686 fails to configure (unable to create initrd image)

2009-05-11 Thread Davide Alberani
Package: linux-image-2.6-686
Version: 2.6.29+19
Severity: serious

--- Please enter the report below this line. ---

The post-installation script for the 2.6.29 kernel fails,
leaving the package not cofigured.

Looks like both update-initramfs and mkinitrd.yaird are
called with wrong arguments (respectively -m and -t).

I have installed initramfs-tools 0.93.2 and yard 0.0.13-5.

Below, the error:


# dpkg --configure -a
Setting up linux-image-2.6.29-2-686 (2.6.29-4) ...
Running depmod.
Running update-initramfs.
Other valid candidates: update-initramfs mkinitrd.yaird
/usr/sbin/update-initramfs: illegal option -- m
Usage: /usr/sbin/update-initramfs [OPTION]...

Options:
 -k [version]   Specify kernel version or 'all'
 -c Create a new initramfs
 -u Update an existing initramfs
 -d Remove an existing initramfs
 -t Take over a custom initramfs with this one
 -b Set alternate boot directory
 -v Be verbose
 -h This message

update-initramfs failed to create initrd image.
Running mkinitrd.yaird.
Other valid candidates: update-initramfs mkinitrd.yaird
mkinitrd.yaird: invalid option -- 't'
Terminating...
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.29-2-686 (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-2.6-686:
 linux-image-2.6-686 depends on linux-image-2.6.29-2-686; however:
  Package linux-image-2.6.29-2-686 is not configured yet.
dpkg: error processing linux-image-2.6-686 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.29-2-686
 linux-image-2.6-686



--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.29-1-686

Debian Release: squeeze/sid
  900 unstablewww.debian-multimedia.org 
  900 unstabledebian.fastbull.org 
  500 testing dl.google.com 
  500 sid www.lamaresh.net 
1 experimentaldebian.fastbull.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
linux-image-2.6.29-2-686| 2.6.29-4


Package's Recommends field is empty.

Package's Suggests field is empty.




-- 
Davide Alberani davide.alber...@gmail.com [GPG KeyID: 0x465BFD47]
http://erlug.linux.it/~da/



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: severity of 528176 is important

2009-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 528176 important
Bug#528176: [linux-image-2.6-686] linux-image-2.6-686 fails to configure 
(unable to create initrd image)
Severity set to `important' from `serious'


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#528176: [linux-image-2.6-686] linux-image-2.6-686 fails to configure (unable to create initrd image)

2009-05-11 Thread maximilian attems
On Mon, May 11, 2009 at 10:19:42AM +0200, Davide Alberani wrote:
 Package: linux-image-2.6-686
 Version: 2.6.29+19
 Severity: serious

set to important, highly overblown as usual..
 
 --- Please enter the report below this line. ---
 
 The post-installation script for the 2.6.29 kernel fails,
 leaving the package not cofigured.
 
 Looks like both update-initramfs and mkinitrd.yaird are
 called with wrong arguments (respectively -m and -t).
 
 I have installed initramfs-tools 0.93.2 and yard 0.0.13-5.
 
 Below, the error:
 
 
 # dpkg --configure -a
 Setting up linux-image-2.6.29-2-686 (2.6.29-4) ...
 Running depmod.
 Running update-initramfs.
 Other valid candidates: update-initramfs mkinitrd.yaird
 /usr/sbin/update-initramfs: illegal option -- m
 Usage: /usr/sbin/update-initramfs [OPTION]...
 
 Options:
  -k [version]   Specify kernel version or 'all'
  -c Create a new initramfs
  -u Update an existing initramfs
  -d Remove an existing initramfs
  -t Take over a custom initramfs with this one
  -b Set alternate boot directory
  -v Be verbose
  -h This message
 
 update-initramfs failed to create initrd image.
 Running mkinitrd.yaird.
 Other valid candidates: update-initramfs mkinitrd.yaird
 mkinitrd.yaird: invalid option -- 't'
 Terminating...
 mkinitrd.yaird failed to create initrd image.
 Failed to create initrd image.
 dpkg: error processing linux-image-2.6.29-2-686 (--configure):
  subprocess post-installation script returned error exit status 1
 dpkg: dependency problems prevent configuration of linux-image-2.6-686:
  linux-image-2.6-686 depends on linux-image-2.6.29-2-686; however:
   Package linux-image-2.6.29-2-686 is not configured yet.
 dpkg: error processing linux-image-2.6-686 (--configure):
  dependency problems - leaving unconfigured
 Errors were encountered while processing:
  linux-image-2.6.29-2-686
  linux-image-2.6-686
 

post output of
cat /etc/kernel-img.conf



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



[OpenVZ] 2.6.26-2-openvz-amd64: fails to stop VE

2009-05-11 Thread Cedric Jeanneret
Hello,

I'm just bumping into a strange behaviour of kernel 2.6.26-2-openvz-amd64 :
when doing a simple vzctl stop veid, it times out, and crashes with:

Stopping container ...
Unable to stop container: operation timed out
Container is currently running. Stop it first.
Hostname (FQDN) of the new VE : Check DNS entry for  failed, abort !

It's a bit... annoying, as you can guess.
Here are some informations [ask me if you want more] :

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 5.0.1 (lenny)
Release:5.0.1
Codename:   lenny


dpkg -l | grep vz
ii  linux-image-2.6.26-2-openvz-amd64   2.6.26-15
ii  vzctl   3.0.23-1dso1
ii  vzdump  1.0-2
ii  vzprocps2.0.11-1dso2
ii  vzquota 3.0.12-1dso1

uname -a
Linux aconcagua 2.6.26-2-openvz-amd64 #1 SMP Fri Mar 27 05:10:50 UTC 2009 
x86_64 GNU/Linux

vzlist :
vzlist 
  CTID  NPROC STATUS  IP_ADDR HOSTNAME
  1034  0 running -   toto-dev
  1070 49 running -   toto-demo
[ some more VEs]

We have another server with another kernel (2.6.18-92.1.18.el5.028stab060.2, 
alienized from RPM latest stable release), and there it's working fine.

Any input is welcome.


Regards,

C. Jeanneret


PS: I posted this on debian-kernel AND deb...@ovz, as I don't know if this 
problem is kernel specific, or if tools don't fit to this kernel. I didn't find 
bugs on openvz' bugtracker for now.

-- 
Cédric Jeanneret |  System Administrator
021 619 10 32|  Camptocamp SA
cedric.jeanne...@camptocamp.com  |  PSE-A / EPFL


signature.asc
Description: PGP signature


Bug#528176: [linux-image-2.6-686] linux-image-2.6-686 fails to configure (unable to create initrd image)

2009-05-11 Thread Davide Alberani
On May 11, maximilian attems m...@stro.at wrote:

  Severity: serious
 
 set to important, highly overblown as usual..

Probably, but it prevents the usability of the kernel...

 post output of
 cat /etc/kernel-img.conf

Here it is:


# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
do_initrd=yes
do_bootloader=no
mkimage=/usr/sbin/mkcramfs %s %s




HTH,
-- 
Davide Alberani davide.alber...@gmail.com [GPG KeyID: 0x465BFD47]
http://erlug.linux.it/~da/



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processing of linux-modules-extra-2.6_2.6.29-4_i386.changes

2009-05-11 Thread Archive Administrator
linux-modules-extra-2.6_2.6.29-4_i386.changes uploaded successfully to localhost
along with the files:
  linux-modules-extra-2.6_2.6.29-4.dsc
  linux-modules-extra-2.6_2.6.29-4.tar.gz
  aufs-modules-2.6.29-2-486_2.6.29+0+20090302-4_i386.deb
  aufs-modules-2.6-486_2.6.29-4_i386.deb
  batman-adv-modules-2.6.29-2-486_2.6.29+0.1-4_i386.deb
  batman-adv-modules-2.6-486_2.6.29-4_i386.deb
  batmand-gateway-modules-2.6.29-2-486_2.6.29+0.3.1-4_i386.deb
  batmand-gateway-modules-2.6-486_2.6.29-4_i386.deb
  drbd8-modules-2.6.29-2-486_2.6.29+8.3.1-4_i386.deb
  drbd8-modules-2.6-486_2.6.29-4_i386.deb
  loop-aes-modules-2.6.29-2-486_2.6.29+3.2f-4_i386.deb
  loop-aes-modules-2.6-486_2.6.29-4_i386.deb
  lzma-modules-2.6.29-2-486_2.6.29+4.43-4_i386.deb
  lzma-modules-2.6-486_2.6.29-4_i386.deb
  nilfs2-modules-2.6.29-2-486_2.6.29+2.0.12-4_i386.deb
  nilfs2-modules-2.6-486_2.6.29-4_i386.deb
  speakup-modules-2.6.29-2-486_2.6.29+3.0.3+git20090404.dfsg.1-4_i386.deb
  speakup-modules-2.6-486_2.6.29-4_i386.deb
  tp-smapi-modules-2.6.29-2-486_2.6.29+0.40-4_i386.deb
  tp-smapi-modules-2.6-486_2.6.29-4_i386.deb
  virtualbox-ose-modules-2.6.29-2-486_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-modules-2.6-486_2.6.29-4_i386.deb
  virtualbox-ose-guest-modules-2.6.29-2-486_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-guest-modules-2.6-486_2.6.29-4_i386.deb
  aufs-modules-2.6.29-2-686_2.6.29+0+20090302-4_i386.deb
  aufs-modules-2.6-686_2.6.29-4_i386.deb
  batman-adv-modules-2.6.29-2-686_2.6.29+0.1-4_i386.deb
  batman-adv-modules-2.6-686_2.6.29-4_i386.deb
  batmand-gateway-modules-2.6.29-2-686_2.6.29+0.3.1-4_i386.deb
  batmand-gateway-modules-2.6-686_2.6.29-4_i386.deb
  drbd8-modules-2.6.29-2-686_2.6.29+8.3.1-4_i386.deb
  drbd8-modules-2.6-686_2.6.29-4_i386.deb
  loop-aes-modules-2.6.29-2-686_2.6.29+3.2f-4_i386.deb
  loop-aes-modules-2.6-686_2.6.29-4_i386.deb
  lzma-modules-2.6.29-2-686_2.6.29+4.43-4_i386.deb
  lzma-modules-2.6-686_2.6.29-4_i386.deb
  nilfs2-modules-2.6.29-2-686_2.6.29+2.0.12-4_i386.deb
  nilfs2-modules-2.6-686_2.6.29-4_i386.deb
  speakup-modules-2.6.29-2-686_2.6.29+3.0.3+git20090404.dfsg.1-4_i386.deb
  speakup-modules-2.6-686_2.6.29-4_i386.deb
  tp-smapi-modules-2.6.29-2-686_2.6.29+0.40-4_i386.deb
  tp-smapi-modules-2.6-686_2.6.29-4_i386.deb
  virtualbox-ose-modules-2.6.29-2-686_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-modules-2.6-686_2.6.29-4_i386.deb
  virtualbox-ose-guest-modules-2.6.29-2-686_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-guest-modules-2.6-686_2.6.29-4_i386.deb
  aufs-modules-2.6.29-2-686-bigmem_2.6.29+0+20090302-4_i386.deb
  aufs-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  batman-adv-modules-2.6.29-2-686-bigmem_2.6.29+0.1-4_i386.deb
  batman-adv-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  batmand-gateway-modules-2.6.29-2-686-bigmem_2.6.29+0.3.1-4_i386.deb
  batmand-gateway-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  drbd8-modules-2.6.29-2-686-bigmem_2.6.29+8.3.1-4_i386.deb
  drbd8-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  loop-aes-modules-2.6.29-2-686-bigmem_2.6.29+3.2f-4_i386.deb
  loop-aes-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  lzma-modules-2.6.29-2-686-bigmem_2.6.29+4.43-4_i386.deb
  lzma-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  nilfs2-modules-2.6.29-2-686-bigmem_2.6.29+2.0.12-4_i386.deb
  nilfs2-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  speakup-modules-2.6.29-2-686-bigmem_2.6.29+3.0.3+git20090404.dfsg.1-4_i386.deb
  speakup-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  tp-smapi-modules-2.6.29-2-686-bigmem_2.6.29+0.40-4_i386.deb
  tp-smapi-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  virtualbox-ose-modules-2.6.29-2-686-bigmem_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  virtualbox-ose-guest-modules-2.6.29-2-686-bigmem_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-guest-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  aufs-modules-2.6.29-2-amd64_2.6.29+0+20090302-4_i386.deb
  aufs-modules-2.6-amd64_2.6.29-4_i386.deb
  batman-adv-modules-2.6.29-2-amd64_2.6.29+0.1-4_i386.deb
  batman-adv-modules-2.6-amd64_2.6.29-4_i386.deb
  batmand-gateway-modules-2.6.29-2-amd64_2.6.29+0.3.1-4_i386.deb
  batmand-gateway-modules-2.6-amd64_2.6.29-4_i386.deb
  drbd8-modules-2.6.29-2-amd64_2.6.29+8.3.1-4_i386.deb
  drbd8-modules-2.6-amd64_2.6.29-4_i386.deb
  loop-aes-modules-2.6.29-2-amd64_2.6.29+3.2f-4_i386.deb
  loop-aes-modules-2.6-amd64_2.6.29-4_i386.deb
  lzma-modules-2.6.29-2-amd64_2.6.29+4.43-4_i386.deb
  lzma-modules-2.6-amd64_2.6.29-4_i386.deb
  nilfs2-modules-2.6.29-2-amd64_2.6.29+2.0.12-4_i386.deb
  nilfs2-modules-2.6-amd64_2.6.29-4_i386.deb
  speakup-modules-2.6.29-2-amd64_2.6.29+3.0.3+git20090404.dfsg.1-4_i386.deb
  speakup-modules-2.6-amd64_2.6.29-4_i386.deb
  tp-smapi-modules-2.6.29-2-amd64_2.6.29+0.40-4_i386.deb
  tp-smapi-modules-2.6-amd64_2.6.29-4_i386.deb
  virtualbox-ose-modules-2.6.29-2-amd64_2.6.29+2.2.2-dfsg-4_i386.deb
  virtualbox-ose-modules-2.6-amd64_2.6.29-4_i386.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to 

Processing of linux-modules-nonfree-2.6_2.6.29-2_i386.changes

2009-05-11 Thread Archive Administrator
linux-modules-nonfree-2.6_2.6.29-2_i386.changes uploaded successfully to 
localhost
along with the files:
  linux-modules-nonfree-2.6_2.6.29-2.dsc
  linux-modules-nonfree-2.6_2.6.29-2.tar.gz
  fglrx-modules-2.6.29-2-486_2.6.29+9-4-2_i386.deb
  fglrx-modules-2.6-486_2.6.29-2_i386.deb
  fglrx-modules-2.6.29-2-686_2.6.29+9-4-2_i386.deb
  fglrx-modules-2.6-686_2.6.29-2_i386.deb
  fglrx-modules-2.6.29-2-686-bigmem_2.6.29+9-4-2_i386.deb
  fglrx-modules-2.6-686-bigmem_2.6.29-2_i386.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



linux-modules-extra-2.6_2.6.29-4_i386.changes is NEW

2009-05-11 Thread Debian Installer
aufs-modules-2.6-486_2.6.29-4_i386.deb
  to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-486_2.6.29-4_i386.deb
aufs-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-686-bigmem_2.6.29-4_i386.deb
aufs-modules-2.6-686_2.6.29-4_i386.deb
  to pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-686_2.6.29-4_i386.deb
aufs-modules-2.6-amd64_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6-amd64_2.6.29-4_i386.deb
(new) aufs-modules-2.6.29-2-486_2.6.29+0+20090302-4_i386.deb optional kernel
Stackable unification filesystem for Linux 2.6.29 on x86
 This package provides the Stackable unification filesystem modules for the
 Linux kernel version 2.6.29 on x86 and compatible machines.
 .
 Aufs is a stackable unification filesystem such as Unionfs, which unifies
 several directories and provides a merged single directory.
(new) aufs-modules-2.6.29-2-686-bigmem_2.6.29+0+20090302-4_i386.deb optional 
kernel
Stackable unification filesystem for Linux 2.6.29 on PPro/Celeron/PII/PIII/P4
 This package provides the Stackable unification filesystem modules for the
 Linux kernel version 2.6.29 on Pentium Pro/Celeron/Pentium II/Pentium
 III/Pentium 4 with 4-64G RAM machines.
 .
 Aufs is a stackable unification filesystem such as Unionfs, which unifies
 several directories and provides a merged single directory.
(new) aufs-modules-2.6.29-2-686_2.6.29+0+20090302-4_i386.deb optional kernel
Stackable unification filesystem for Linux 2.6.29 on PPro/Celeron/PII/PIII/P4
 This package provides the Stackable unification filesystem modules for the
 Linux kernel version 2.6.29 on Pentium Pro/Celeron/Pentium II/Pentium
 III/Pentium 4 machines.
 .
 Aufs is a stackable unification filesystem such as Unionfs, which unifies
 several directories and provides a merged single directory.
(new) aufs-modules-2.6.29-2-amd64_2.6.29+0+20090302-4_i386.deb optional kernel
Stackable unification filesystem for Linux 2.6.29 on AMD64
 This package provides the Stackable unification filesystem modules for the
 Linux kernel version 2.6.29 on all 64bit single- and multiprocessor AMD
 and Intel machines.
 .
 Aufs is a stackable unification filesystem such as Unionfs, which unifies
 several directories and provides a merged single directory.
batman-adv-modules-2.6-486_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batman-adv-modules-2.6-486_2.6.29-4_i386.deb
batman-adv-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batman-adv-modules-2.6-686-bigmem_2.6.29-4_i386.deb
batman-adv-modules-2.6-686_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batman-adv-modules-2.6-686_2.6.29-4_i386.deb
batman-adv-modules-2.6-amd64_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batman-adv-modules-2.6-amd64_2.6.29-4_i386.deb
(new) batman-adv-modules-2.6.29-2-486_2.6.29+0.1-4_i386.deb optional kernel
B.A.T.M.A.N. on Layer 2 for Linux 2.6.29 on x86
 This package provides the B.A.T.M.A.N. on Layer 2 modules for the Linux
 kernel version 2.6.29 on x86 and compatible machines.
 .
 This package contains the set of loadable kernel modules for the Layer 2
 Mesh B.A.T.M.A.N.
(new) batman-adv-modules-2.6.29-2-686-bigmem_2.6.29+0.1-4_i386.deb optional 
kernel
B.A.T.M.A.N. on Layer 2 for Linux 2.6.29 on PPro/Celeron/PII/PIII/P4
 This package provides the B.A.T.M.A.N. on Layer 2 modules for the Linux
 kernel version 2.6.29 on Pentium Pro/Celeron/Pentium II/Pentium
 III/Pentium 4 with 4-64G RAM machines.
 .
 This package contains the set of loadable kernel modules for the Layer 2
 Mesh B.A.T.M.A.N.
(new) batman-adv-modules-2.6.29-2-686_2.6.29+0.1-4_i386.deb optional kernel
B.A.T.M.A.N. on Layer 2 for Linux 2.6.29 on PPro/Celeron/PII/PIII/P4
 This package provides the B.A.T.M.A.N. on Layer 2 modules for the Linux
 kernel version 2.6.29 on Pentium Pro/Celeron/Pentium II/Pentium
 III/Pentium 4 machines.
 .
 This package contains the set of loadable kernel modules for the Layer 2
 Mesh B.A.T.M.A.N.
(new) batman-adv-modules-2.6.29-2-amd64_2.6.29+0.1-4_i386.deb optional kernel
B.A.T.M.A.N. on Layer 2 for Linux 2.6.29 on AMD64
 This package provides the B.A.T.M.A.N. on Layer 2 modules for the Linux
 kernel version 2.6.29 on all 64bit single- and multiprocessor AMD and
 Intel machines.
 .
 This package contains the set of loadable kernel modules for the Layer 2
 Mesh B.A.T.M.A.N.
batmand-gateway-modules-2.6-486_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batmand-gateway-modules-2.6-486_2.6.29-4_i386.deb
batmand-gateway-modules-2.6-686-bigmem_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batmand-gateway-modules-2.6-686-bigmem_2.6.29-4_i386.deb
batmand-gateway-modules-2.6-686_2.6.29-4_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/batmand-gateway-modules-2.6-686_2.6.29-4_i386.deb
batmand-gateway-modules-2.6-amd64_2.6.29-4_i386.deb
  to 

linux-modules-nonfree-2.6_2.6.29-2_i386.changes is NEW

2009-05-11 Thread Debian Installer
fglrx-modules-2.6-486_2.6.29-2_i386.deb
  to 
pool/non-free/l/linux-modules-nonfree-2.6/fglrx-modules-2.6-486_2.6.29-2_i386.deb
fglrx-modules-2.6-686-bigmem_2.6.29-2_i386.deb
  to 
pool/non-free/l/linux-modules-nonfree-2.6/fglrx-modules-2.6-686-bigmem_2.6.29-2_i386.deb
fglrx-modules-2.6-686_2.6.29-2_i386.deb
  to 
pool/non-free/l/linux-modules-nonfree-2.6/fglrx-modules-2.6-686_2.6.29-2_i386.deb
(new) fglrx-modules-2.6.29-2-486_2.6.29+9-4-2_i386.deb optional non-free/kernel
Display driver for AMD/ATI Radeon and FireGL graphics cards modules for Linux 
2.6.29 on x86
 This package provides the Display driver for AMD/ATI Radeon and FireGL
 graphics cards modules for the Linux kernel version 2.6.29 on x86 and
 compatible machines.
 .
 The AMD/ATI display driver supports graphic cards based on the r5xx and
 r6xx chipsets.
(new) fglrx-modules-2.6.29-2-686-bigmem_2.6.29+9-4-2_i386.deb optional 
non-free/kernel
Display driver for AMD/ATI Radeon and FireGL graphics cards modules for Linux 
2.6.29 on PPro/Celeron/PII/PIII/P4
 This package provides the Display driver for AMD/ATI Radeon and FireGL
 graphics cards modules for the Linux kernel version 2.6.29 on Pentium
 Pro/Celeron/Pentium II/Pentium III/Pentium 4 with 4-64G RAM machines.
 .
 The AMD/ATI display driver supports graphic cards based on the r5xx and
 r6xx chipsets.
(new) fglrx-modules-2.6.29-2-686_2.6.29+9-4-2_i386.deb optional non-free/kernel
Display driver for AMD/ATI Radeon and FireGL graphics cards modules for Linux 
2.6.29 on PPro/Celeron/PII/PIII/P4
 This package provides the Display driver for AMD/ATI Radeon and FireGL
 graphics cards modules for the Linux kernel version 2.6.29 on Pentium
 Pro/Celeron/Pentium II/Pentium III/Pentium 4 machines.
 .
 The AMD/ATI display driver supports graphic cards based on the r5xx and
 r6xx chipsets.
linux-modules-nonfree-2.6_2.6.29-2.dsc
  to 
pool/non-free/l/linux-modules-nonfree-2.6/linux-modules-nonfree-2.6_2.6.29-2.dsc
linux-modules-nonfree-2.6_2.6.29-2.tar.gz
  to 
pool/non-free/l/linux-modules-nonfree-2.6/linux-modules-nonfree-2.6_2.6.29-2.tar.gz
Changes: linux-modules-nonfree-2.6 (2.6.29-2) unstable; urgency=low
 .
  * Bumping to abiname 2.6.29-2.


Override entries for your package:
fglrx-modules-2.6-486_2.6.29-2_i386.deb - optional non-free/kernel
fglrx-modules-2.6-686-bigmem_2.6.29-2_i386.deb - optional non-free/kernel
fglrx-modules-2.6-686_2.6.29-2_i386.deb - optional non-free/kernel
linux-modules-nonfree-2.6_2.6.29-2.dsc - source non-free/kernel

Announcing to debian-devel-chan...@lists.debian.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#528176: [linux-image-2.6-686] linux-image-2.6-686 fails to configure (unable to create initrd image)

2009-05-11 Thread maximilian attems
On Mon, May 11, 2009 at 12:36:59PM +0200, Davide Alberani wrote:
 On May 11, maximilian attems m...@stro.at wrote:
 
   Severity: serious
  
  set to important, highly overblown as usual..
 
 Probably, but it prevents the usability of the kernel...

right the usability :)
it would be serious if it wouldn't be installable
on X boxes where X is a nr  1000
 
  post output of
  cat /etc/kernel-img.conf
 
 Here it is:
 
 
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 do_initrd=yes
 do_bootloader=no
 mkimage=/usr/sbin/mkcramfs %s %s

grr looks good, so no idea on a quick look.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

2009-05-11 Thread martin f krafft
also sprach Tony Godshall t...@of.net [2009.05.11.1819 +0200]:
  retitle 526525 amd64 kernel cannot find bnx2 PCI device base address
 
 Um.  BNX2 is the network card?  WTF does it have to do with being able
 to mount and boot off RAID in 64-bit mode only?

I don't know, but your attitude does not make me want to help you
further.

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

-- 
 .''`.   martin f. krafft madd...@d.o  Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
sobald man über niveau spricht
 ist man längst darüber hinweg.
  -- thomas krafft


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)


Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

2009-05-11 Thread Tony Godshall
On Sat, May 9, 2009 at 12:35 AM, martin f krafft madd...@debian.org wrote:
 retitle 526525 amd64 kernel cannot find bnx2 PCI device base address

Um.  BNX2 is the network card?  WTF does it have to do with being able
to mount and boot off RAID in 64-bit mode only?

 also sprach Tony Godshall t...@of.net [2009.05.09.0117 +0200]:
  If you cannot boot, append break=mount to the kernel line, and at
  the initramfs prompt, type
 
   rm /etc/mdadm/mdadm.conf
   /scripts/local-top/mdadm
   ctrl-d
 
  and then fix the initramfs.

 I'm not interested in deleting mdadm.conf or taking any other steps
 that might break the existing functionality.

 I considered it a necessary step in my analysis, but if you prefer
 to do things your way, it's your system. Note that I would have
 never proposed anything that made permanent changes without adequate
 warning.

rm /etc/mdadm.conf ?  Maybe mv.  Anyhow, I'm giving more info below
and am open to suggestions on how to acquire more.

 I'm not reporting this bug because I must have an amd64 kernel-
 like I said, the 686 and 686bigmem kernels are working.
 I initiated this bug to help get the amd64 version of the kernel
 (or mdadm?) fixed.  I'm interested in steps that will help fix the
 packages, not manually work around its flaws.

 Then please provide all the necessary infos. mdadm works perfectly
 fine with amd64 kernels. I think your problem is that the kernel
 doesn't initialise the drives you're using properly, so mdadm
 doesn't find them when trying to assemble.

 You will have to make sure the kernel sees your drives. From what
 you've allowed me to see, I can conclude that this is not a RAID
 problem.

Please find below my mdadm.conf.

I assume the dmesg output would be useful but I'm not sure how to
capture that in the initramfs environment.

Let me know what else comprises the necessary infos I have failed to provide.

# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST system

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=4
UUID=1cdfc35d:237af2b8:58db9480:16165906

# This file was auto-generated on Mon, 27 Apr 2009 02:47:01 -0700
# by mkconf $Id$

Best Regards.
Please keep in touch.
This is unedited.
P-)

 --
  .''`.   martin f. krafft madd...@d.o      Related projects:
 : :'  :  proud Debian developer               http://debiansystem.info
 `. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems

 fashions have done more harm than revolutions.
                                                        -- victor hugo

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)

 iEYEARECAAYFAkoFMkEACgkQIgvIgzMMSnUk5ACfcRDawcJVFhpm2RqdxehK64Mv
 +10An3TllsHOk1io8ho4e8nW4CxlUGZL
 =jHa4
 -END PGP SIGNATURE-





--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

2009-05-11 Thread martin f krafft
also sprach Tony Godshall t...@of.net [2009.05.11.1843 +0200]:
 I filed the report because I want to see Debian work great on all
 configurations, with all CPUs, with all RAID configurations, off the
 bat, without tweaking.  And I'm trying to do what small part I can.
 With the limited access to the equipment I have.

As I said before, this is not a RAID problem. RAID works no
different on amd64 than it does on i386.

 I'm trying to help, and you tell me to delete config files, you
 don't bother to read key parts of my report, and you talk about my
 attitude when I notice a bad rename.

I told you to delete a file in an initrd image copied to RAM,
because I suspected your UUIDs to have gotten out of sync.

Which part of your report didn't I read?

What bad rename are you talking about?

 Please find attached screenshots of boot with
 /etc/mdadm/mdadm.conf removed out of the way.

No screenshot attached. Also, note that I didn't ask you to remove
the file from the disk, but I asked you to remove the file from the
command line you see when initramfs fails to mount the rootfs. Sorry
if that wasn't clear.

If you want to get an idea of what relevant information is, please
run

  /usr/share/bug/mdadm/script 31

as root and post the output.

-- 
 .''`.   martin f. krafft madd...@d.o  Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
life moves pretty fast. if you don't stop and look around once in
 a while, you could miss it.
 -- ferris bueller


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)


Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

2009-05-11 Thread Tony Godshall
Did I say I was looking for help?

As I said before, I am fine running with a 32 bit kernel.

I filed the report because I want to see Debian work great on all
configurations, with all CPUs, with all RAID configurations, off the
bat, without tweaking.  And I'm trying to do what small part I can.
With the limited access to the equipment I have.

I'm trying to help, and you tell me to delete config files, you don't
bother to read key parts of my report, and you talk about my attitude
when I notice a bad rename.

My attitude?  Wow.  Look in the mirror.

Anyhow, back to work.  I'd appreciate any assistance anyone, Martin or
others, can provide toward getting the amd64 kernel working well on
machines like the Dell T610.

Please find attached screenshots of boot with /etc/mdadm/mdadm.conf
removed out of the way.

Also, here's output of lspci -v, in case it helps (booted under 686smp
kernel, not the problematic amd64 kernel)

# lspci -v
00:00.0 Host bridge: Intel Corporation QuickPath Architecture I/O Hub
to ESI Port (rev 13)
Subsystem: Dell Device 0237
Flags: fast devsel, IRQ 15
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable-
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting ?
Capabilities: [150] Access Controls ?
Capabilities: [160] Vendor Specific Information ?

00:01.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub
PCI Express Root Port 1 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: da00-ddff
Capabilities: [40] Subsystem: Dell Device 0237
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting ?
Capabilities: [150] Access Controls ?
Capabilities: [160] Vendor Specific Information ?
Kernel driver in use: pcieport-driver
Kernel modules: shpchp

00:03.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub
PCI Express Root Port 3 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Capabilities: [40] Subsystem: Dell Device 0237
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting ?
Capabilities: [150] Access Controls ?
Capabilities: [160] Vendor Specific Information ?
Kernel driver in use: pcieport-driver
Kernel modules: shpchp

00:04.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub
PCI Express Root Port 4 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Capabilities: [40] Subsystem: Dell Device 0237
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting ?
Capabilities: [150] Access Controls ?
Kernel driver in use: pcieport-driver
Kernel modules: shpchp

00:05.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub
PCI Express Root Port 5 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=06, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: df10-df2f
Capabilities: [40] Subsystem: Dell Device 0237
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting ?
Capabilities: [150] Access Controls ?
Kernel driver in use: pcieport-driver
Kernel modules: shpchp

00:07.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub
PCI Express Root Port 7 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
Capabilities: [40] Subsystem: Dell Device 0237
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3

Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

2009-05-11 Thread Tony Godshall
On Mon, May 11, 2009 at 9:55 AM, martin f krafft madd...@debian.org wrote:
 also sprach Tony Godshall t...@of.net [2009.05.11.1843 +0200]:
 I filed the report because I want to see Debian work great on all
 configurations, with all CPUs, with all RAID configurations, off the
 bat, without tweaking.  And I'm trying to do what small part I can.
 With the limited access to the equipment I have.

 As I said before, this is not a RAID problem. RAID works no
 different on amd64 than it does on i386.

Fine.  It's not a RAID issue.  Did I argue otherwise?

 I'm trying to help, and you tell me to delete config files, you
 don't bother to read key parts of my report, and you talk about my
 attitude when I notice a bad rename.

 I told you to delete a file in an initrd image copied to RAM,
 because I suspected your UUIDs to have gotten out of sync.

I understand now.

 Which part of your report didn't I read?

The bit about where I made it clear I didn't care that much if it
worked for me but rather that I was reporting to make Debian better.
I.e. I'm not asking you to help me, I'm trying to help Debian and
Linux.

 What bad rename are you talking about?

The bug as a networking (bnx2) bug.  That's the point where you
apparently just read WTF? and, whoop, flamethrower on, attitude!

 Please find attached screenshots of boot with
 /etc/mdadm/mdadm.conf removed out of the way.

 No screenshot attached.

Yeah, :-/   Check the followup email sent about 60 seconds later.

 Also, note that I didn't ask you to remove
 the file from the disk, but I asked you to remove the file from the
 command line you see when initramfs fails to mount the rootfs. Sorry
 if that wasn't clear.

I understand now.

 If you want to get an idea of what relevant information is, please
 run

  /usr/share/bug/mdadm/script 31

 as root and post the output.

Well, like you say, it's not a RAID issue, so I don't see how it's
relevant.  But OK, here goes...

# cat t
--- mount output
/dev/md0 on / type ext3 (rw,noatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)

--- mdadm.conf
no mdadm.conf file.

--- /proc/mdstat:
Personalities : [raid1]
md0 : active raid1 sda2[0] sdd2[3] sdc2[2] sdb2[1]
  291009344 blocks [4/4] []

unused devices: none

--- /proc/partitions:
major minor  #blocks  name

   8 0  292968750 sda
   8 11951866 sda1
   8 2  291009442 sda2
   816  292968750 sdb
   8171951866 sdb1
   818  291009442 sdb2
   832  292968750 sdc
   8331951866 sdc1
   834  291009442 sdc2
   848  292968750 sdd
   8491951866 sdd1
   850  291009442 sdd2
   9 0  291009344 md0

--- initrd.img-2.6.26-2-686-bigmem:
30579 blocks
sbin/mdadm
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/raid10.ko
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/multipath.ko
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/raid456.ko
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/md-mod.ko
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/raid0.ko
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/raid1.ko
lib/modules/2.6.26-2-686-bigmem/kernel/drivers/md/linear.ko
scripts/local-top/mdadm

--- /proc/modules:
dm_mod 46952 0 - Live 0xf8a0b000
raid1 18784 1 - Live 0xf89c8000
md_mod 67804 2 raid1, Live 0xf89d8000

--- /var/log/syslog:

--- volume detail:
/dev/sda2:
  Magic : a92b4efc
Version : 00.90.00
   UUID : 1cdfc35d:237af2b8:58db9480:16165906
  Creation Time : Mon Apr 20 16:42:49 2009
 Raid Level : raid1
  Used Dev Size : 291009344 (277.53 GiB 297.99 GB)
 Array Size : 291009344 (277.53 GiB 297.99 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0


Update Time : Mon May 11 10:11:19 2009
  State : active
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
   Checksum : fdc5cbbe - correct
 Events : 15


  Number   Major   Minor   RaidDevice State
this 0   820  active sync   /dev/sda2

   0 0   820  active sync   /dev/sda2
   1 1   8   181  active sync   /dev/sdb2
   2 2   8   342  active sync   /dev/sdc2
   3 3   8   503  active sync   /dev/sdd2
--
/dev/sdb2:
  Magic : a92b4efc
Version : 00.90.00
   UUID : 1cdfc35d:237af2b8:58db9480:16165906
  Creation Time : Mon Apr 20 16:42:49 2009
 Raid Level : raid1
  Used Dev Size : 291009344 (277.53 GiB 297.99 GB)
 Array Size : 291009344 (277.53 GiB 297.99 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

Update Time : Mon May 11 10:11:19 2009

Processing of linux-2.6_2.6.18.dfsg.1-24etch2_powerpc.changes

2009-05-11 Thread Archive Administrator
linux-2.6_2.6.18.dfsg.1-24etch2_powerpc.changes uploaded successfully to 
ftp.upload.debian.org
along with the files:
  linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-all-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc-smp_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc-smp_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc-miboot_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc-miboot_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-prep_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-prep_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-vserver-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-vserver-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-vserver-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-vserver-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processing of linux-2.6_2.6.18.dfsg.1-24etch2_powerpc.changes

2009-05-11 Thread Archive Administrator
linux-2.6_2.6.18.dfsg.1-24etch2_powerpc.changes uploaded successfully to 
localhost
along with the files:
  linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-all-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc-smp_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc-smp_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc-miboot_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc-miboot_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-prep_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-prep_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-vserver-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-vserver-powerpc_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-image-2.6.18-6-vserver-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb
  linux-headers-2.6.18-6-vserver-powerpc64_2.6.18.dfsg.1-24etch2_powerpc.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

2009-05-11 Thread Tony Godshall
...
 Sorry. We got off on a bad start. I'll review your stuff tomorrow
 and then let's start afresh.

OK

 By the time you get dumped into the busybox prompt during initramfs
 time, are /dev/sd[abcd] present?

They are *not*.  That would seem to be the nub of the problem.  No
base partitions, thus no RAID.  Good, thanks, that's progress.  Might
be good for md to report that that a little better (see screenshot).
Oh, duh, I moved /etc/mdadm/mdadm.conf out of the way.  So it doesn't
even know I have a RAID until it autodetects it, right?  Oh, wait, in
this initramfs environment there is an /etc/mdadm/mdadm.conf, and it
shows UUID and the 4-way RAID1.  What, so the /etc/mdadm/mdadm.conf
inside the initrd is not from the kernel package but was built
locally?  Didn't realize that.

Perhaps if I could figure out how to grab the dmesg output from
initramfs environment, I could then compare the amd64 kernel output to
the 686-bigmem kernel output... :-/



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#514292: marked as done (linux-image-2.6.28-1-amd64: Bad page state in process 'emacs')

2009-05-11 Thread Debian Bug Tracking System

Your message dated Mon, 11 May 2009 21:50:07 +0200
with message-id 87r5yvl8r4@gismo.pca.it
and subject line Re: Bug#514292: linux-image-2.6.28-1-amd64: Bad page state in 
process 'emacs'
has caused the Debian Bug report #514292,
regarding linux-image-2.6.28-1-amd64: Bad page state in process 'emacs'
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
514292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.28-1-amd64
Version: 2.6.28-1~experimental.1~snapshot.12674
Severity: important

Hello!

I hope it is OK to report bugs in the unofficial kernels to the official
Debian BTS, please correct me if I am wrong.

This afternoon, I was moving a mail from my IMAP mailbox to the local
disk with Gnus on Emacs [1] when the machine froze, with the attached
messages on the screen.  FYI, I have never experienced it with other
kernels, both official from the Debian archive or unofficial from
http://kernel-archive.buildserver.net .

In case I am wrong and the bug is indeed in Emacs, feel free to close
it, I will submit a new one to the Emacs BTS.

FWIW, this is not the first problem I have with 2.6.28 [2].  Moreover,
it seems the temperature problem I experienced in the past with previous
kernels are still there [3].

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://emacs.orebokech.com/
[2] http://bugs.debian.org/514109
[3] http://thread.gmane.org/gmane.linux.acpi.devel/37230

-- Package-specific info:
** Version:
Linux version 2.6.28-1-amd64 (Debian 2.6.28-1~experimental.1~snapshot.12674) 
(wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 
4.1.2-23+1)) #1 SMP Wed Feb 4 15:57:36 UTC 2009

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.28-1-amd64 root=/dev/mapper/vggismo-lvroot ro panic=10 
vga=792 splash

** Not tainted

** Kernel log:
[see the attached extract from syslog instead]

** Loaded modules:
Module  Size  Used by
iptable_filter  7296  0 
xt_tcpudp   7552  0 
ipt_MASQUERADE  7296  0 
iptable_nat 9988  0 
nf_nat 23956  2 ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4  18840  3 iptable_nat,nf_nat
nf_conntrack   73488  4 
ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4
nf_defrag_ipv4  6400  1 nf_conntrack_ipv4
ip_tables  21264  2 iptable_filter,iptable_nat
x_tables   25480  4 xt_tcpudp,ipt_MASQUERADE,iptable_nat,ip_tables
cdc_ether   9728  0 
usbnet 21000  1 cdc_ether
mii 9728  1 usbnet
usb_storage   100800  0 
i915   61704  2 
drm   105184  3 i915
ppdev  11784  0 
parport_pc 31784  0 
lp 14724  0 
parport42160  3 ppdev,parport_pc,lp
rfcomm 39328  3 
hid_dell6912  0 
hid_pl  7936  0 
hid_cypress 7296  0 
hid_zpff7552  0 
hid_gyration7168  0 
hid_bright  6784  0 
hid_sony7552  0 
hid_samsung 7040  0 
hid_microsoft   8452  0 
hid_tmff8448  0 
hid_monterey6912  0 
hid_ezkey   6656  0 
hid_apple  11392  0 
hid_a4tech  7424  0 
hid_logitech   14080  0 
usbhid 37312  6 
hid_dell,hid_pl,hid_zpff,hid_bright,hid_tmff,hid_logitech
ff_memless  9352  4 hid_pl,hid_zpff,hid_tmff,hid_logitech
hid_cherry  6912  0 
hid_sunplus 6784  0 
hidp   19584  2 
hid_petalynx7424  0 
hid_belkin  7040  0 
hid_chicony 7040  0 
hid45120  22 
hid_dell,hid_pl,hid_cypress,hid_zpff,hid_gyration,hid_bright,hid_sony,hid_samsung,hid_microsoft,hid_tmff,hid_monterey,hid_ezkey,hid_apple,hid_a4tech,hid_logitech,usbhid,hid_cherry,hid_sunplus,hidp,hid_petalynx,hid_belkin,hid_chicony
l2cap  25088  14 rfcomm,hidp
bluetooth  61988  5 rfcomm,hidp,l2cap
ipv6  20  22 
acpi_cpufreq   12176  1 
cpufreq_conservative11400  0 
cpufreq_ondemand   11792  1 
cpufreq_powersave   5888  0 
pci_slot9352  0 
cpufreq_userspace   7812  0 
sbs17808  0 
sbshc  10368  1 sbs
cpufreq_stats   8964  0 
freq_table  9088  3 acpi_cpufreq,cpufreq_ondemand,cpufreq_stats
input_polldev   8592  0 
container   8192  0 
wmi 

Processed: Re: Bug#528268: linux-image-2.6.29-1-amd64: sensor driver error

2009-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 528268 linux-2.6
Bug#528268: linux-image-2.6.29-1-amd64: sensor driver error
Warning: Unknown package 'linux-image-2.6.29-1-amd64'
Bug reassigned from package `linux-image-2.6.29-1-amd64' to `linux-2.6'.

 --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



linux-2.6.24_2.6.24-6~etchnhalf.8etch1_amd64.changes ACCEPTED

2009-05-11 Thread Debian Installer

Accepted:
linux-2.6.24_2.6.24-6~etchnhalf.8etch1.diff.gz
  to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8etch1.diff.gz
linux-2.6.24_2.6.24-6~etchnhalf.8etch1.dsc
  to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8etch1.dsc
linux-doc-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
  to pool/main/l/linux-2.6.24/linux-doc-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
linux-headers-2.6.24-etchnhalf.1-all-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb
  to 
pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb
linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8etch1_amd64.deb
  to 
pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8etch1_amd64.deb
linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb
  to 
pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb
linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8etch1_amd64.deb
  to 
pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8etch1_amd64.deb
linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb
  to 
pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb
linux-manual-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
  to 
pool/main/l/linux-2.6.24/linux-manual-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
  to 
pool/main/l/linux-2.6.24/linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
linux-source-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
  to 
pool/main/l/linux-2.6.24/linux-source-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8etch1_all.deb
  to 
pool/main/l/linux-2.6.24/linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8etch1_all.deb
linux-tree-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb
  to 
pool/main/l/linux-2.6.24/linux-tree-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb


Override entries for your package:
linux-2.6.24_2.6.24-6~etchnhalf.8etch1.dsc - optional devel
linux-doc-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb - optional doc
linux-headers-2.6.24-etchnhalf.1-all-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb 
- optional devel
linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8etch1_amd64.deb - 
optional devel
linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb - 
optional devel
linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8etch1_amd64.deb - 
optional devel
linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch1_amd64.deb - 
optional admin
linux-manual-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb - optional doc
linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb - optional devel
linux-source-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb - optional devel
linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8etch1_all.deb - optional 
devel
linux-tree-2.6.24_2.6.24-6~etchnhalf.8etch1_all.deb - optional devel

Announcing to debian-chan...@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



linux-2.6_2.6.18.dfsg.1-24etch2_i386.changes ACCEPTED

2009-05-11 Thread Debian Installer

Accepted:
linux-2.6_2.6.18.dfsg.1-24etch2.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24etch2.diff.gz
linux-2.6_2.6.18.dfsg.1-24etch2.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24etch2.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
linux-headers-2.6.18-6-486_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-486_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24etch2_i386.deb
linux-headers-2.6.18-6_2.6.18.dfsg.1-24etch2_i386.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-486_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-486_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-k7_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-k7_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-manual-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
  to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 
pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch2_i386.deb
linux-patch-debian-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
  to 
pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
linux-source-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
  to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
linux-support-2.6.18-6_2.6.18.dfsg.1-24etch2_all.deb
  to pool/main/l/linux-2.6/linux-support-2.6.18-6_2.6.18.dfsg.1-24etch2_all.deb
linux-tree-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
  to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18.dfsg.1-24etch2_all.deb
xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch2_i386.deb
  to 

Bug#435134: marked as done (linux-image-2.6.22-1-alpha-smp: various modules cannot be loaded)

2009-05-11 Thread Debian Bug Tracking System

Your message dated Mon, 11 May 2009 23:29:57 +0200
with message-id 20090511212957.ga31...@galadriel.inutil.org
and subject line Re: linux-image-2.6.22-1-alpha-smp: various modules cannot be 
loaded
has caused the Debian Bug report #435134,
regarding linux-image-2.6.22-1-alpha-smp: various modules cannot be loaded
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
435134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.22-1-alpha-smp
Version: 2.6.22-2
Severity: normal

The kernel boots, but various kernel modules cannot be loaded.  Notables:

module xfs: Relocation (type 17) overflow vs per_cpu__xfsstats
module ipv6: Relocation (type 17) overflow vs section 32

Peter

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: alpha
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.22-1-alpha-smp depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85g  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo

linux-image-2.6.22-1-alpha-smp recommends no packages.

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  
linux-image-2.6.22-1-alpha-smp/postinst/old-system-map-link-2.6.22-1-alpha-smp: 
true
  linux-image-2.6.22-1-alpha-smp/postinst/bootloader-error-2.6.22-1-alpha-smp:
  linux-image-2.6.22-1-alpha-smp/postinst/kimage-is-a-directory:
  linux-image-2.6.22-1-alpha-smp/preinst/elilo-initrd-2.6.22-1-alpha-smp: true
  
linux-image-2.6.22-1-alpha-smp/postinst/create-kimage-link-2.6.22-1-alpha-smp: 
true
  
linux-image-2.6.22-1-alpha-smp/prerm/removing-running-kernel-2.6.22-1-alpha-smp:
 true
  
linux-image-2.6.22-1-alpha-smp/preinst/overwriting-modules-2.6.22-1-alpha-smp: 
true
  linux-image-2.6.22-1-alpha-smp/preinst/bootloader-initrd-2.6.22-1-alpha-smp: 
true
  
linux-image-2.6.22-1-alpha-smp/postinst/depmod-error-initrd-2.6.22-1-alpha-smp: 
false
  linux-image-2.6.22-1-alpha-smp/postinst/old-initrd-link-2.6.22-1-alpha-smp: 
true
  linux-image-2.6.22-1-alpha-smp/preinst/initrd-2.6.22-1-alpha-smp:
  linux-image-2.6.22-1-alpha-smp/preinst/abort-overwrite-2.6.22-1-alpha-smp:
  linux-image-2.6.22-1-alpha-smp/postinst/depmod-error-2.6.22-1-alpha-smp: false
  linux-image-2.6.22-1-alpha-smp/preinst/lilo-has-ramdisk:
  
linux-image-2.6.22-1-alpha-smp/preinst/failed-to-move-modules-2.6.22-1-alpha-smp:
  linux-image-2.6.22-1-alpha-smp/preinst/abort-install-2.6.22-1-alpha-smp:
  
linux-image-2.6.22-1-alpha-smp/preinst/already-running-this-2.6.22-1-alpha-smp:
  
linux-image-2.6.22-1-alpha-smp/postinst/bootloader-test-error-2.6.22-1-alpha-smp:
  
linux-image-2.6.22-1-alpha-smp/prerm/would-invalidate-boot-loader-2.6.22-1-alpha-smp:
 true
  
linux-image-2.6.22-1-alpha-smp/postinst/old-dir-initrd-link-2.6.22-1-alpha-smp: 
true
  linux-image-2.6.22-1-alpha-smp/preinst/lilo-initrd-2.6.22-1-alpha-smp: true

---End Message---
---BeginMessage---
Version: 2.6.26-1

On Sat, May 09, 2009 at 02:41:32PM -0700, Gabriele Gorla wrote:
 Package: linux-image-2.6.26-2-alpha-smp
 Followup-For: Bug #435134
 
 I have not noticed any module loading issues with current lenny
 kernels (either generic or smp).
 
 In particular xfs and ipv6 load just fine.

Thanks, marking as closed.

Cheers,
Moritz

---End Message---


Re: Bug#463860: lenny+half (Re: Bug#463860: any chance to see this fixed in .26 in lenny?

2009-05-11 Thread dann frazier
On Thu, May 07, 2009 at 06:47:13PM +0200, Moritz Muehlenhoff wrote:
 On 2009-05-07, maximilian attems m...@stro.at wrote:
  On Thu, May 07, 2009 at 02:25:25PM +0200, Holger Levsen wrote:
  
   i would have been happier to push the soon to come 2.6.30 for lenny+half,
   but that looks impossible due to the multiple security support
   that our team currently has to handle going from
   oldstable 2.6.18 and 2.6.24, stable 2.6.26 and of course
   the easy 2.6.29 in sid.
  
  hm, so do you think lenny+half will not happen or how should I understand 
  that? I assume it will not be much easier once .30 is in sid, because 2 
  months later, there will be .31 in sid and you'd have to take care for 5 
  kernel versions again?!
 
  the point is that lenny+half is delayed up until manpower is freed
  by no longer supporting the etch linux-2.6 images.
  that contradicts somehow the lenny+half intention as by that time
  typicaly squeeze starts to get mass installed.
 
 Support for etch+half was limited to three months, so ends by 14th
 May.

My understanding/expectation was that etchnhalf support would
terminate at the same time as etch - and I don't think we communicated
anything to the contrary to our users:

 - http://lists.debian.org/debian-announce/2008/msg3.html
 - http://www.debian.org/releases/etch/etchnhalf

Personally, I view the nhalf release as a way to make an old release
viable for a longer period of time - letting change-adverse users
avoid a mass upgrade when they really just need newer hardware. This
class of user isn't looking to migrate to the newest stable release -
they want to stay exactly where they are for as long as they
(reasonable and securely) can. So, for this class of users, the
availability of a usable squeeze isn't really relevant, other than as
a ticking clock for the end of etch support.

I of course realize that there are other classes of users that may
benefit from an 'nhalf' release (e.g., those who just want latest
stable to work on their hardware), but I'd always assumed this
change-adverse crowd would be the most significant percentage, and
therefore the crowd we'd want to target. Now that etchnhalf has been
out a while, it would be great if we could collect some meaningful
data here..

-- 
dann frazier


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org