Bug#576641: Can't open /scripts/functions, no backup of initrd made

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: initramfs-tools
Version: 0.94

Upgrade failed with

Setting up initramfs-tools (0.94) ...
Installing new version of config file /etc/kernel/postrm.d/initramfs-tools ...
Installing new version of config file /etc/kernel/postinst.d/initramfs-tools ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
Installing new version of config file 
/etc/initramfs-tools/update-initramfs.conf ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-3-amd64
W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
.: 4: Can't open /scripts/functions

AFAICS the postinst script made no backup of the old initrd.


Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAku60T8ACgkQUTlbRTxpHjdUCgCfV5IxNreOHuzQsyTNelG5cqWS
8esAn15QF0ex7uBW7xJ1AFOId8pWudSN
=8wd+
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bbad145.4070...@afaics.de

Bug#561203: threads and fork on machine with VIPT-WB cache

[NIIBE Yutaka]

John David Anglin wrote:
> It is interesting that in the case of the Debian bug that
> a thread of the parent process causes the COW break and thereby corrupts
> its own memory.  As far as I can tell, the fork'd child never writes
> to the memory that causes the fault.

Thanks for writing and testing a patch.

The case of #561203 is second scenario.  I think that this case is
relevant to VIVT-WB machine too (provided kernel does copy by kernel
address).

James Bottomley wrote:
> So this is going to be a hard sell because of the arch churn. There are,
> however, three ways to do it with the original signature.

Currently, I think that signature change would be inevitable for
ptep_set_wrprotect.

>  1. implement copy_user_highpage ... this allows us to copy through
> the child's page cache (which is coherent with the parent's
> before the cow) and thus pick up any cache changes without a
> flush

Let me think about this way.

Well, this would improve both cases of the first scenario of mine and
the second scenario.

But... I think that even if we would have copy_user_highpage which
does copy by user address, we need to flush at ptep_set_wrprotect.  I
think that we need to keep the condition: no dirty cache for COW page.

Think about third scenario of threads and fork:

(1) In process A, there are multiple threads, and a thread A-1 invokes
fork.  We have process B, with a different space identifier color.

(2) Another thread A-2 in process A runs while A-1 copies memory by
dup_mmap.  A-2 writes to the address  in a page.  Let's call
this page .

(3) We have dirty cache for  by A-2 at the time of
ptep_set_wrprotect of thread A-1.  Suppose that we don't flush
here.

(4) A-1 finishes copy, and sleeps.

(5) Child process B is waken up and sees old value at  in ,
through different cache line.  B sleeps.

(6) A-2 is waken up.  A-2 touches the memory again, breaks COW.  A-2
copies data on  to .  OK,  is
consistent with copy_user_highpage by user address.

Note that during this copy, the cache line of  by A-2 is
flushed out to .  It invokes another memory fault and COW
break.  (I think that this memory fault is unhealthy.)
Then, new value goes to  on  (when it's physically
tagged cache).

A-2 sleeps.

(7) Child process B is waken up.  When it accesses at , it sees new
value suddenly.


If we flush cache to  at ptep_set_wrprotect, this couldn't
occur.


*   *   *


I know that we should not do "threads and fork".  It is difficult to
define clean semantics.  Because another thread may touch memory while
a thread which does memory copy for fork, the memory what the child
process will see may be inconsistent.  For the child, a page might be
new, while another page might be old.

For VIVT-WB cache machine, I am considering a possibility for the
child process to have inconsistent memory even within a single page
(when we have no flush at ptep_set_wrprotect).

It will be needed for me to talk to linux-arch soon or later.
-- 



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bbabf23.1030...@fsij.org

Bug#576243: marked as done (linux-base postinst exits when no /etc/fstab in Debian live)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#576243: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #576243,
regarding linux-base postinst exits when no /etc/fstab in Debian live
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.)


-- 
576243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-base
Version: 2.6.33-1~experimental.2
Severity: important
Tags: sid

*** Please type your report below this line ***
When creating a Debian live system with live-helper, there is no file 
/etc/fstab for such a live system. However, the "$fstab->close();" in 
"/var/lib/dpkg/info/linux-base.postinst" will just exit in this case.

Please fix it. Thanks.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-4-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0] 1.5.30 Debian configuration 
management sy

ii  libapt-pkg-perl   0.1.24 Perl interface to libapt-pkg

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information excluded

--
Steven Shiau  
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-11_all.deb
linux-source-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-11_all.deb
linux-support-2.6.32-4_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-4_2.6.32-11_all.deb
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.de

Bug#574598: marked as done (openvz kernel doesn't work and spams into dmesg: NULL exec env (timr->it_process->ve_task_info.owner_env))

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#574598: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #574598,
regarding openvz kernel doesn't work and spams into dmesg: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
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.)


-- 
574598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-4-openvz-amd64
Severity: important
Version: 2.6.32-10

I installed on my desktop new version of vz-kernel to test.
But it works very unstable. Begining from booting it spams dmesg
messages:

[  482.069225] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  483.069224] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  484.069224] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  485.069221] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  486.069214] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  487.069224] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  488.069225] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  489.069223] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  490.069224] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  491.069232] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  492.069214] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)
[  493.069234] posix_timer_event: NULL exec env 
(timr->it_process->ve_task_info.owner_env)

and than it will hang up.

I was forced to downgrade my system downto linux-image-2.6.32-4-amd64.
I had no time to install any containers.
-- 
... mpd paused: Joe Dassin - Le Chateau De Sable

. ''`.   Dmitry E. Oboukhov
: :’  :   email: un...@debian.org jabber://un...@uvw.ru
`. `~’  GPGKey: 1024D / F8E26537 2006-11-21
  `- 1B23 D4F8 8EC0 D902 0555  E438 AB8C 00CF F8E2 6537


dmesg.gz
Description: Binary data


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_a

Bug#575056: marked as done (linux-2.6: libata based drivers migration script does not migrate /etc/crypttab)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#575056: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #575056,
regarding linux-2.6: libata based drivers migration script does not migrate 
/etc/crypttab
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.)


-- 
575056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-10
Severity: normal

Hi,

The migration to libata based drivers migration went very well when I upgraded
the kernel to 2.6.33-10, but the migration process forgot about /etc/crypttab
where my encrypted /home info is. After manually changing it, everything was OK.

The crypttab manual page does not say if cryptsetup supports UUID=, but
#445189 says so.

Thanks, feel free to ask for more info.

Alex


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-11_all.deb
linux-source-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-11_all.deb
linux-support-2.6.32-4_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-4_2.6.32-11_all.deb
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 575...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilia

Bug#573912: marked as done (linux-2.6: please enable ramzswap/compcache)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:13 +
with message-id 
and subject line Bug#573912: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #573912,
regarding linux-2.6: please enable ramzswap/compcache
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.)


-- 
573912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: consider enabling CONFIG_RAMZSWAP in 2.6.33+
Severity: wishlist

please consider setting CONFIG_RAMZSWAP (a.k.a. compcache), which enables a ram
based compressed swap device. i think it can be enabled as a module, but i'm
not sure.

this feature is very useful to thin clients, embedded devices, or other
environments with limited ram and no conventional swap device available.

live well,
  vagrant


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-11_all.deb
linux-source-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-11_all.deb
linux-support-2.6.32-4_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-4_2.6.32-11_all.deb
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 573...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 05 Apr 2010 20:31:15 +0200
Source: linux-2.6
B

Bug#575189: marked as done (NULL pointer dereference in linux-image-2.6.32-4-openvz-amd64)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#575189: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #575189,
regarding NULL pointer dereference in linux-image-2.6.32-4-openvz-amd64
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.)


-- 
575189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-4-openvz-amd64
Version: 2.6.32-10

After few seconds after boot in openvz contaiter, running verlihub
with nearby 100 TCP connections, I see in dmesg:
[ 4538.883509] BUG: unable to handle kernel NULL pointer dereference
at 0038
[ 4538.883563] IP: [] ub_page_charge+0x65/0xa2
[ 4538.883598] PGD 42b002067 PUD 42afb0067 PMD 0
[ 4538.883630] Oops:  [#1] SMP
[ 4538.883656] last sysfs file: /sys/devices/virtual/net/lo/operstate
[ 4538.883685] CPU 7
[ 4538.883707] Modules linked in: vzethdev vznetdev simfs vzdquota
vzmon vzdev xt_comment xt_tcpudp ipt_LOG xt_length xt_hl xt_tcpmss
xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp
ipt_REJECT ip_tables x_tables bonding ipmi_si ipmi_devintf
ipmi_msghandler snd_pcm psmouse i2c_i801 snd_timer container serio_raw
rng_core i2c_core snd soundcore snd_page_alloc joydev pcspkr evdev
i5k_amb ioatdma i5000_edac button dca processor edac_core shpchp
pci_hotplug ext3 jbd mbcache dm_mirror dm_region_hash dm_log
dm_snapshot dm_mod raid10 raid1 md_mod sg sr_mod cdrom sd_mod
crc_t10dif usbhid usb_storage hid ata_piix aic94xx libsas ata_generic
ehci_hcd uhci_hcd scsi_transport_sas libata scsi_mod usbcore nls_base
e1000e thermal fan thermal_sys [last unloaded: scsi_wait_scan]
[ 4538.884129] Pid: 3625, comm: verlihub Not tainted
2.6.32-4-openvz-amd64 #1 042test001 X7DBR-3
[ 4538.884180] RIP: 0010:[]  []
ub_page_charge+0x65/0xa2
[ 4538.884233] RSP: :88042b887c58  EFLAGS: 00010246
[ 4538.884269] RAX: 0001 RBX: 0001 RCX: 
[ 4538.884299] RDX: 12d0 RSI:  RDI: 
[ 4538.884329] RBP:  R08:  R09: 
[ 4538.884358] R10: 0f5d R11: 0002 R12: 
[ 4538.884388] R13: 12d0 R14:  R15: 0002
[ 4538.884419] FS:  7fec621566f0() GS:880011bc()
knlGS:
[ 4538.884465] CS:  0010 DS:  ES:  CR0: 80050033
[ 4538.884492] CR2: 0038 CR3: 00041842b000 CR4: 000406e0
[ 4538.884522] DR0:  DR1:  DR2: 
[ 4538.884552] DR3:  DR6: 0ff0 DR7: 0400
[ 4538.884583] Process verlihub (pid: 3625, veid=1233, threadinfo
88042b886000, task 88042a235000)
[ 4538.884631] Stack:
[ 4538.884651]  0001  
810bbe19
[ 4538.884688] <0> 88023c80  88042a235000
88042b887fd8
[ 4538.884739] <0> 0010 0050 1000
1080
[ 4538.884807] Call Trace:
[ 4538.884832]  [] ? __alloc_pages_nodemask+0x62e/0x6ad
[ 4538.884864]  [] ? new_slab+0x4b/0x228
[ 4538.884891]  [] ? __slab_alloc+0x1cc/0x388
[ 4538.884920]  [] ? pb_alloc+0x15/0x3a
[ 4538.884947]  [] ? pb_alloc+0x15/0x3a
[ 4538.884973]  [] ? kmem_cache_alloc+0x7f/0x138
[ 4538.885002]  [] ? pb_alloc+0x15/0x3a
[ 4538.885030]  [] ? handle_mm_fault+0x269/0x952
[ 4538.885060]  [] ? virtinfo_notifier_call+0x57/0xa1
[ 4538.885089]  [] ? __do_brk+0x253/0x35a
[ 4538.885118]  [] ? do_page_fault+0x266/0x282
[ 4538.885149]  [] ? page_fault+0x25/0x30
[ 4538.885175] Code: fa 66 0f 1f 44 00 00 be 00 10 00 00 c1 ea 16 48
89 ef 83 e2 01 48 d3 e6 e8 23 ff ff ff 85 c0 75 1f 48 89 df 57 9d 0f
1f 44 00 00 <49> 83 7c 24 38 00 74 04 0f 0b eb fe 49 89 6c 24 38 31 c0
eb 23
[ 4538.885365] RIP  [] ub_page_charge+0x65/0xa2
[ 4538.885395]  RSP 
[ 4538.885418] CR2: 0038
[ 4538.885670] ---[ end trace 5b3ccb8b85dfed82 ]---


I am using Lenny system, only 2 packages from Sid:
toothy:~# dpkg -l|grep linux-
ii  linux-base 2.6.32-10
 Linux image base package
ii  linux-image-2.6.32-4-openvz-amd64  2.6.32-10
 Linux 2.6.32 for 64-bit PCs, OpenVZ support


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  

Bug#575726: marked as done (linux-image-2.6-amd64: Kerneloops when wpa_supplicant terminated on 2.6.32 kernel with rt2860sta driver)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#575726: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #575726,
regarding linux-image-2.6-amd64: Kerneloops when wpa_supplicant terminated on 
2.6.32 kernel with rt2860sta driver
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.)


-- 
575726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-2.6-amd64
Version: 2.6.32+25
Severity: important

I'm not sure if this is the correct version (or package - may be 
wpa-supplicant?) to file against, but it affects all versions of the 
2.6.32 kernel that I've tried (including linux-image-2.6.32-4 in sid), and 
doesn't affect the 2.6.30 kernel.


Whenever wpa_supplicant is deactivated (whether by killing the process or 
during a normal shutdown) I am getting a kerneloops that prevents the 
computer from completing shutdown. Here is the relevant syslog output:


Mar 28 18:46:52 ernie wpa_supplicant[2800]: CTRL-EVENT-TERMINATING - signal 15 
received
Mar 28 18:46:52 ernie NetworkManager:   (wlan0): supplicant manager state:  
idle -> down
Mar 28 18:46:52 ernie NetworkManager:   (wlan0): device state change: 6 
-> 2 (reason 10)
Mar 28 18:46:52 ernie NetworkManager:   (wlan0): deactivating device 
(reason: 10).
Mar 28 18:46:52 ernie kernel: [ 1106.949270] BUG: unable to handle kernel 
paging request at 0001
Mar 28 18:46:52 ernie kernel: [ 1106.949283] IP: [<0001>] 
0x1
Mar 28 18:46:52 ernie kernel: [ 1106.949298] PGD 11e183067 PUD 0 
Mar 28 18:46:52 ernie kernel: [ 1106.949305] Oops: 0010 [#1] SMP 
Mar 28 18:46:52 ernie kernel: [ 1106.949312] last sysfs file: /sys/devices/pci:00/:00:14.4/uevent
Mar 28 18:46:52 ernie kernel: [ 1106.949319] CPU 0 
Mar 28 18:46:52 ernie kernel: [ 1106.949323] Modules linked in: ppdev lp sco bridge stp bnep rfcomm l2cap crc16 bluetooth rfkill nf_nat_ftp nf_conntrack_ftp nf_nat_irc nf_conntrack_irc ipt_LOG xt_limit xt_state xt_owner ipt_REDIRECT xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables powernow_k8 cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_conservative binfmt_misc fuse vboxdrv loop firewire_sbp2 snd_hda_codec_via snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_usb_audio snd_usb_lib snd_pcm snd_seq_midi snd_seq_midi_event usbhid hid uvcvideo snd_rawmidi snd_seq snd_hwdep videodev v4l1_compat v4l2_compat_ioctl32 rt2860sta(C) snd_timer snd_seq_device snd soundcore edac_core edac_mce_amd snd_page_alloc i2c_piix4 crc_ccitt shpchp i2c_core parport_pc pci_hotplug parport asus_atk0110 pcspkr evdev processor ext3 jbd mbcache dm_mod usb_storage ide_cd_mod sd_mod cdrom crc_t10dif ide_pci_generic ohci_hcd ata

_generic firewire_ohci ahci firewire
Mar 28 18:46:52 ernie kernel: _core libata ehci_hcd crc_itu_t atiixp ide_core 
r8169 mii scsi_mod usbcore nls_base button thermal fan thermal_sys [last 
unloaded: scsi_wait_scan]
Mar 28 18:46:52 ernie kernel: [ 1106.949476] Pid: 2800, comm: wpa_supplicant 
Tainted: G C 2.6.32-3-amd64 #1 System Product Name
Mar 28 18:46:52 ernie kernel: [ 1106.949483] RIP: 0010:[<0001>]  
[<0001>] 0x1
Mar 28 18:46:52 ernie kernel: [ 1106.949494] RSP: 0018:88011bcd3ca0  
EFLAGS: 00010246
Mar 28 18:46:52 ernie kernel: [ 1106.949499] RAX: 0001 RBX: 
c90011433000 RCX: 0002
Mar 28 18:46:52 ernie kernel: [ 1106.949505] RDX: 0f00 RSI: 
c10e4020 RDI: 88011fb450b8
Mar 28 18:46:52 ernie kernel: [ 1106.949511] RBP: c90011433000 R08: 
 R09: 8143b930
Mar 28 18:46:52 ernie kernel: [ 1106.949517] R10: 88011c27fc00 R11: 
0001 R12: c90011431000
Mar 28 18:46:52 ernie kernel: [ 1106.949523] R13:  R14: 
0005 R15: c90011433000
Mar 28 18:46:52 ernie kernel: [ 1106.949530] FS:  7f1288d3a6f0() 
GS:88000500() knlGS:
Mar 28 18:46:52 ernie kernel: [ 1106.949536] CS:  0010 DS:  ES:  CR0: 
8005003b
Mar 28 18:46:52 ernie kernel: [ 1106.949541] CR2: 0001 CR3: 
00011b91c000 CR4: 06f0
Mar 28 18:46:52 ernie kernel: [ 1106.949547] DR0:  DR1: 
 DR2: 
Mar 28 18:46:52 ernie kernel: [ 1106.949553] DR3:  DR6: 
0ff0 DR7: 0400
Mar 28 18:46:52 ernie kernel: [ 1106.949560] Process wpa_supplicant (pid: 2800, 
threadinf

Bug#574421: marked as done (FTBFS on sparc; missing I/O functions needed by nouveau driver)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#574421: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #574421,
regarding FTBFS on sparc; missing I/O functions needed by nouveau driver
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.)


-- 
574421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-10
Severity: important
Tags: patch
Justification: fails to build from source

The build failed with:

In file included from 
/build/buildd-linux-2.6_2.6.32-10-sparc-EFgEHg/linux-2.6-2.6.32/debian/build/source_sparc_none/drivers/gpu/drm/nouveau/nouveau_drv.c:30:
/build/buildd-linux-2.6_2.6.32-10-sparc-EFgEHg/linux-2.6-2.6.32/debian/build/source_sparc_none/drivers/gpu/drm/nouveau/nouveau_drv.h:
 In function 'nvchan_rd32':
/build/buildd-linux-2.6_2.6.32-10-sparc-EFgEHg/linux-2.6-2.6.32/debian/build/source_sparc_none/drivers/gpu/drm/nouveau/nouveau_drv.h:1193:
 error: implicit declaration of function 'ioread32be'
/build/buildd-linux-2.6_2.6.32-10-sparc-EFgEHg/linux-2.6-2.6.32/debian/build/source_sparc_none/drivers/gpu/drm/nouveau/nouveau_drv.h:
 In function 'nvchan_wr32':
/build/buildd-linux-2.6_2.6.32-10-sparc-EFgEHg/linux-2.6-2.6.32/debian/build/source_sparc_none/drivers/gpu/drm/nouveau/nouveau_drv.h:1199:
 error: implicit declaration of function 'iowrite32be'
make[9]: *** [drivers/gpu/drm/nouveau/nouveau_drv.o] Error 1
make[8]: *** [drivers/gpu/drm/nouveau] Error 2
make[7]: *** [drivers/gpu/drm] Error 2
make[6]: *** [drivers/gpu] Error 2
make[5]: *** [drivers] Error 2
make[5]: *** Waiting for unfinished jobs

This should be fixed by:

commit 1bff4dbb79a2bc0ee4881c8ea6a4fbed64ea6309
Author: David S. Miller 
Date:   Wed Mar 3 02:30:37 2010 -0800

sparc: Provide io{read,write}{16,32}be().

Ben.

-- System Information:
Debian Release: squeeze/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_am

Bug#569724: marked as done (Please support /etc/kernel/header_postinst.d directory)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:13 +
with message-id 
and subject line Bug#569724: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #569724,
regarding Please support /etc/kernel/header_postinst.d directory
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.)


-- 
569724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

it would be nice if linux-headers packages could run hooks files in 
/etc/kernel/header_postinst.d on postinst.

This is a partial fix for #560822, dkms package already installs
/etc/kernel/header_postinst.d/dkms, but it only used in Ubuntu.

Cheers,
Giuseppe.


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

iEYEARECAAYFAkt2/lgACgkQNxpp46476aqfSwCgmOa9MPbVhNTB798EUNltZCci
HCsAoIw7r59amYadKz0UZz6vqeud1gqF
=9bcP
-END PGP SIGNATURE-


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-11_all.deb
linux-source-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-11_all.deb
linux-support-2.6.32-4_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-4_2.6.32-11_all.deb
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 569...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpma

Bug#576213: marked as done (linux-image-2.6.32-3-686: ath5k stops working in AP mode after a few minutes)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#576213: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #576213,
regarding linux-image-2.6.32-3-686: ath5k stops working in AP mode after a few 
minutes
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.)


-- 
576213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-9
Severity: normal
Tags: patch


After running my wireless card (Atheros AR5414 chip) in AP mode using hostapd 
(0.6.10-2) I start getting the following messages and wireless networking stops 
working at all until I restart hostapd.

I found a related discussion where someone offers a patch that fixes the 
problem. I haven't tried this patch myself. Link to this discussion: 
http://comments.gmane.org/gmane.linux.kernel.wireless.general/47278


-- Package-specific info:
** Version:
Linux version 2.6.32-3-686 (Debian 2.6.32-9) (m...@debian.org) (gcc version 
4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Feb 25 06:14:20 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-686 
root=UUID=53675e72-a286-4a20-9a59-0f096d802d4f ro console=tty0 
console=ttyS0,9600n8 ide=nodma

** Not tainted

** Kernel log:
[80066.762653] ath5k phy0: no further txbuf available, dropping packet
[80076.838146] ath5k phy0: no further txbuf available, dropping packet
[80086.909500] ath5k phy0: no further txbuf available, dropping packet
[80096.984505] ath5k phy0: no further txbuf available, dropping packet
[80107.055860] ath5k phy0: no further txbuf available, dropping packet
[80117.131192] ath5k phy0: no further txbuf available, dropping packet
[80127.202707] ath5k phy0: no further txbuf available, dropping packet
[80137.277894] ath5k phy0: no further txbuf available, dropping packet
[80147.349390] ath5k phy0: no further txbuf available, dropping packet
[80157.420739] ath5k phy0: no further txbuf available, dropping packet
[80167.492073] ath5k phy0: no further txbuf available, dropping packet
[80177.563260] ath5k phy0: no further txbuf available, dropping packet
[80187.634595] ath5k phy0: no further txbuf available, dropping packet
[80197.705943] ath5k phy0: no further txbuf available, dropping packet
[80207.779226] ath5k phy0: no further txbuf available, dropping packet
[80217.848652] ath5k phy0: no further txbuf available, dropping packet
[80227.920641] ath5k phy0: no further txbuf available, dropping packet
[80238.006046] ath5k phy0: no further txbuf available, dropping packet
[80248.064224] ath5k phy0: no further txbuf available, dropping packet
[80258.139187] ath5k phy0: no further txbuf available, dropping packet
[80268.212775] ath5k phy0: no further txbuf available, dropping packet
[80278.281039] ath5k phy0: no further txbuf available, dropping packet
[80288.356484] ath5k phy0: no further txbuf available, dropping packet
[80298.427482] ath5k phy0: no further txbuf available, dropping packet
[80308.502877] ath5k phy0: no further txbuf available, dropping packet
[80318.574065] ath5k phy0: no further txbuf available, dropping packet
[80328.645561] ath5k phy0: no further txbuf available, dropping packet
[80338.716748] ath5k phy0: no further txbuf available, dropping packet
[80348.788083] ath5k phy0: no further txbuf available, dropping packet
[80358.859594] ath5k phy0: no further txbuf available, dropping packet
[80368.930943] ath5k phy0: no further txbuf available, dropping packet
[80379.002148] ath5k phy0: no further txbuf available, dropping packet
[80389.073758] ath5k phy0: no further txbuf available, dropping packet
[80399.144799] ath5k phy0: no further txbuf available, dropping packet
[80409.216152] ath5k phy0: no further txbuf available, dropping packet
[80419.291921] ath5k phy0: no further txbuf available, dropping packet
[80429.363263] ath5k phy0: no further txbuf available, dropping packet
[80439.434184] ath5k phy0: no further txbuf available, dropping packet
[80449.505682] ath5k phy0: no further txbuf available, dropping packet
[80459.581143] ath5k phy0: no further txbuf available, dropping packet
[80469.652369] ath5k phy0: no further txbuf available, dropping packet
[80479.727554] ath5k phy0: no further txbuf available, dropping packet
[80489.798905] ath5k phy0: no further txbuf available, dropping packet
[80499.870237] ath5k phy0: no further txbuf available, dropping packet
[80509.941587] ath5k phy0: no further txbuf available, dropping packet
[80520.012922] ath5k phy0: no further txbuf available, dropping packet
[80530.084275] ath5k phy0: no further txbuf a

Bug#576537: marked as done (Incorrect labels generated in /etc/fstab during PATA conversion)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#576537: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #576537,
regarding Incorrect labels generated in /etc/fstab during PATA conversion
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.)


-- 
576537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-base
Version: 2.6.32-10
Severity: normal

The conversion on my Thinkpad X31 seems to have generated incorrect
labels, which lead to the home partition not being mounted automatically:

This is the /etc/fstab which was generated:

# /etc/fstab: static file system information.
#
#
proc/proc   procdefaults0   0
# /dev/hda1   /   ext3defaults,errors=remount-ro 0   1
LABEL=\x2f   /   ext3defaults,errors=remount-ro 0   1
# /dev/hda6   /home   ext3defaults,noatime 0   2
LABEL=\x2fhome   /home   ext3defaults,noatime 0   2
# /dev/hda5   noneswapsw  0   0
UUID=0603958c-bb68-46df-940b-c562b9fdb4aa   noneswapsw  
0   0
/dev/fd0/media/floppy0  autorw,user,noauto  0   0
/dev/sda/stick  vfatrw,user,noauto  0   0

The labels itself seem correct:

r...@galadriel:~# e2label /dev/sda1
/
r...@galadriel:~# e2label /dev/sda6
/home
r...@galadriel:~#

I have no idea where "\x2f" instead of "/" is coming from?

Cheers,
Moritz

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-4-686 (SMP w/1 CPU core)
Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0] 1.5.30 Debian configuration management sy
ii  libapt-pkg-perl   0.1.24 Perl interface to libapt-pkg
ii  libuuid-perl  0.02-3+b1  Perl extension for using UUID inte

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
  linux-base/disk-id-manual:
  linux-base/disk-id-convert-plan-no-relabel: true
* linux-base/disk-id-convert-auto: true
* linux-base/disk-id-convert-plan: true


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64

Bug#574401: marked as done (udevadm trigger crashes system)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#574401: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #574401,
regarding udevadm trigger crashes system
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.)


-- 
574401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 151-2
Severity: critical
Justification: breaks the whole system

Having recently upgraded the computer in question to udev 151-2,
the system now fails to boot. It gets as far as starting udev,
then the screen goes blank and the system hangs until a hard reset.

I have tracked this down to the point in /etc/init.d/udev where
it calls the command 'udevadm trigger'. Commenting out this section
of the init script allows the system to boot normally.

If 'udevadm trigger' is run once the system is booted and running
normally it also crashes the system in the same manner (blank screen,
hard reset required).

The PC is a Foxconn 945S04 motherboard (Intel atom processor).
There are also a couple of SATA drives in the system, but that's
about it.

Unfortunately as the crash blanks and turns off the screen, I'm
unable to list any final error messages.

If there's any more information I can give that'll be of use,
please get in touch and I'll see what i can do.

Best regards
Dave Williams

-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 4
-rw-r--r-- 1 root root 817 Oct 27 14:02 70-persistent-net.rules

-- /sys/:
/sys/dev
/sys/devices/pci:00/:00:1d.0/usb2/2-0:1.0/usb_endpoint/usbdev2.1_ep81/dev
/sys/devices/pci:00/:00:1d.0/usb2/dev
/sys/devices/pci:00/:00:1d.0/usb2/usb_device/usbdev2.1/dev
/sys/devices/pci:00/:00:1d.0/usb2/usb_endpoint/usbdev2.1_ep00/dev
/sys/devices/pci:00/:00:1d.0/usbmon/usbmon2/dev
/sys/devices/pci:00/:00:1d.1/usb3/3-0:1.0/usb_endpoint/usbdev3.1_ep81/dev
/sys/devices/pci:00/:00:1d.1/usb3/dev
/sys/devices/pci:00/:00:1d.1/usb3/usb_device/usbdev3.1/dev
/sys/devices/pci:00/:00:1d.1/usb3/usb_endpoint/usbdev3.1_ep00/dev
/sys/devices/pci:00/:00:1d.1/usbmon/usbmon3/dev
/sys/devices/pci:00/:00:1d.2/usb4/4-0:1.0/usb_endpoint/usbdev4.1_ep81/dev
/sys/devices/pci:00/:00:1d.2/usb4/dev
/sys/devices/pci:00/:00:1d.2/usb4/usb_device/usbdev4.1/dev
/sys/devices/pci:00/:00:1d.2/usb4/usb_endpoint/usbdev4.1_ep00/dev
/sys/devices/pci:00/:00:1d.2/usbmon/usbmon4/dev
/sys/devices/pci:00/:00:1d.3/usb5/5-0:1.0/usb_endpoint/usbdev5.1_ep81/dev
/sys/devices/pci:00/:00:1d.3/usb5/dev
/sys/devices/pci:00/:00:1d.3/usb5/usb_device/usbdev5.1/dev
/sys/devices/pci:00/:00:1d.3/usb5/usb_endpoint/usbdev5.1_ep00/dev
/sys/devices/pci:00/:00:1d.3/usbmon/usbmon5/dev
/sys/devices/pci:00/:00:1d.7/usb1/1-0:1.0/usb_endpoint/usbdev1.1_ep81/dev
/sys/devices/pci:00/:00:1d.7/usb1/dev
/sys/devices/pci:00/:00:1d.7/usb1/usb_device/usbdev1.1/dev
/sys/devices/pci:00/:00:1d.7/usb1/usb_endpoint/usbdev1.1_ep00/dev
/sys/devices/pci:00/:00:1d.7/usbmon/usbmon1/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/block/sda/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/block/sda/sda1/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/block/sda/sda2/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/block/sda/sda3/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:0/1:0:0:0/bsg/1:0:0:0/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:1/1:0:1:0/block/sdb/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:1/1:0:1:0/block/sdb/sdb1/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:1/1:0:1:0/block/sdb/sdb2/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:1/1:0:1:0/block/sdb/sdb3/dev
/sys/devices/pci:00/:00:1f.2/host1/target1:0:1/1:0:1:0/bsg/1:0:1:0/dev
/sys/devices/platform/serial8250/tty/ttyS0/dev
/sys/devices/platform/serial8250/tty/ttyS1/dev
/sys/devices/platform/serial8250/tty/ttyS2/dev
/sys/devices/platform/serial8250/tty/ttyS3/dev
/sys/devices/pnp0/00:03/rtc/rtc0/dev
/sys/devices/virtual/block/dm-0/dev
/sys/devices/virtual/block/dm-1/dev
/sys/devices/virtual/block/dm-2/dev
/sys/devices/virtual/block/dm-3/dev
/sys/devices/virtual/block/md0/dev
/sys/devices/virtual/block/ram0/dev
/sys/devices/virtual/block/ram1/dev
/sys/devices/virtual/block/ram10/dev
/sys/devices/virtual/block/ram11/dev
/sys/devices/virtual/block/ram12/dev
/sys/dev

Bug#574630: marked as done (linux-base: postinst fails if udev's persistent-cd.rules has duplicates)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#574630: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #574630,
regarding linux-base: postinst fails if udev's persistent-cd.rules has 
duplicates
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.)


-- 
574630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-base
Version: 2.6.32-10
Severity: serious

Due to some old bug in udev, my /etc/udev/rules.d/70-persistent-cd.rules
had a number of duplicate rules (timestamp on the file suggests it might
have been #374539).  This leads to an error in linux-base.postinst:

Modification of non-creatable array value attempted, subscript -1 at 
/var/lib/dpkg/info/linux-base.postinst line 667,  line 12.
dpkg: error processing linux-base (--configure):
 subprocess installed post-installation script returned error exit status 9

After removing the duplicates from the rules file, installation worked
fine (but warned me that it left /dev/scd0 unchanged in fstab).

Cheers,
Julien

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii  libapt-pkg-perl   0.1.24 Perl interface to libapt-pkg
ii  libuuid-perl  0.02-3+b1  Perl extension for using UUID inte

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
* linux-base/disk-id-manual:
  linux-base/disk-id-convert-plan-no-relabel: true
* linux-base/disk-id-convert-auto: true
* linux-base/disk-id-convert-plan: true


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linu

Bug#574368: marked as done (FTBFS on alpha and hppa)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#574368: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #574368,
regarding FTBFS on alpha and hppa
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.)


-- 
574368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Severity: serious
Version: 2.6.32-10

failure seeems quite similar:
CC  kernel/trace/trace_clock.o
/build/buildd-linux-2.6_2.6.32-10-alpha-POBShR/linux-2.6-2.6.32/debian/build/source_alpha_none/kernel/trace/trace_clock.c:
In function 'trace_clock_local':
/build/buildd-linux-2.6_2.6.32-10-alpha-POBShR/linux-2.6-2.6.32/debian/build/source_alpha_none/kernel/trace/trace_clock.c:39:
error: implicit declaration of function 'raw_local_irq_save'
/build/buildd-linux-2.6_2.6.32-10-alpha-POBShR/linux-2.6-2.6.32/debian/build/source_alpha_none/kernel/trace/trace_clock.c:41:
error: implicit declaration of function 'raw_local_irq_restore'
make[7]: *** [kernel/trace/trace_clock.o] Error 1




--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-11_all.deb
linux-source-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-11_all.deb
linux-support-2.6.32-4_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-4_2.6.32-11_all.deb
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 574...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically

Bug#447575: marked as done (linux-image-2.6.22-2-686: Please enable CONFIG_FB_I810_GTF)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:13 +
with message-id 
and subject line Bug#447575: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #447575,
regarding linux-image-2.6.22-2-686: Please enable CONFIG_FB_I810_GTF
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.)


-- 
447575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.22-2-686
Version: 2.6.22-4
Severity: normal

Please enable option CONFIG_FB_I810_GTF in kernel config.
Without it i810fb can set refresh rates >60hz only with 640x480.

-- Package-specific info:
** Version:
Linux version 2.6.22-2-686 (Debian 2.6.22-4) (wa...@debian.org) (gcc version 
4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 
2007

** Not tainted

** Loaded modules:
Module  Size  Used by
tun10560  1 
i810fb 30652  1 
vgastate8256  1 i810fb
ipt_MASQUERADE  3616  1 
xt_helper   2752  1 
xt_MARK 2240  2 
ipt_LOG 5952  3 
nf_conntrack_ftp9664  0 
ipt_REDIRECT2048  3 
xt_limit2592  3 
xt_tcpudp   3072  139 
xt_state2432  3 
iptable_mangle  2784  1 
iptable_nat 7204  1 
nf_nat 17964  3 ipt_MASQUERADE,ipt_REDIRECT,iptable_nat
nf_conntrack_ipv4  17772  6 iptable_nat
nf_conntrack   60424  7 
ipt_MASQUERADE,xt_helper,nf_conntrack_ftp,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
nfnetlink   5752  3 nf_nat,nf_conntrack_ipv4,nf_conntrack
iptable_filter  2944  1 
ip_tables  12260  3 iptable_mangle,iptable_nat,iptable_filter
x_tables   14372  10 
ipt_MASQUERADE,xt_helper,xt_MARK,ipt_LOG,ipt_REDIRECT,xt_limit,xt_tcpudp,xt_state,iptable_nat,ip_tables
cls_route   6624  0 
cls_u32 7748  2 
cls_fw  5312  1 
sch_sfq 5664  11 
sch_htb16256  2 
rpcsec_gss_krb5 7976  0 
auth_rpcgss37408  3 rpcsec_gss_krb5
nfs   224428  0 
ipv6  236964  40 
nfsd  202800  17 
exportfs5472  1 nfsd
lockd  60456  3 nfs,nfsd
nfs_acl 3520  2 nfs,nfsd
sunrpc157852  16 
rpcsec_gss_krb5,auth_rpcgss,nfs,nfsd,lockd,nfs_acl
reiserfs  220320  4 
ext3  121224  6 
jbd55336  1 ext3
ext2   60232  1 
mbcache 8260  2 ext3,ext2
ide_cd 36416  0 
cdrom  32832  1 ide_cd
tsdev   7968  0 
pcspkr  3104  0 
snd_intel8x0   32124  0 
parport_pc 33796  0 
psmouse36016  0 
snd_ac97_codec 92836  1 snd_intel8x0
parport33960  1 parport_pc
ac97_bus2272  1 snd_ac97_codec
snd_pcm72324  2 snd_intel8x0,snd_ac97_codec
snd_timer  21028  1 snd_pcm
snd48324  4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore   7520  1 snd
snd_page_alloc  9512  2 snd_intel8x0,snd_pcm
serio_raw   6692  0 
i2c_i8018656  0 
rtc12856  0 
i2c_core   23552  1 i2c_i801
intel_agp  23188  1 
agpgart31912  2 i810fb,intel_agp
iTCO_wdt9924  0 
shpchp 31060  0 
pci_hotplug29184  1 shpchp
evdev   9312  0 
xfs   503128  2 
dm_mirror  20928  0 
dm_snapshot16516  0 
dm_mod 52160  25 dm_mirror,dm_snapshot
ide_disk   16512  8 
ata_generic 7556  0 
libata115664  1 ata_generic
scsi_mod  136620  1 libata
e100   33644  0 
8139too25536  0 
mii 5280  2 e100,8139too
uhci_hcd   22960  0 
usbcore   125096  2 uhci_hcd
piix8868  0 [permanent]
generic 4836  0 [permanent]
ide_core  113764  4 ide_cd,ide_disk,piix,generic
thermal13416  0 
processor  31016  1 thermal
fan 4836  0 

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge 
and Memory Controller Hub [8086:1130] (rev 04)
Subsystem: Siemens Nixdorf AG Unknown device [110a:005a]
 

Bug#574987: marked as done (linux-base fails install on lilo-based system)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#574987: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #574987,
regarding linux-base fails install on lilo-based system
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.)


-- 
574987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-base
Version: 2.6.32-10
Severity: important


I am assuming "linux-base" failing is a critical possibly
system-threatening bug - but I could easily be overestimating the
severity of this package failing.

Error setting debconf substitutions in linux-base/disk-id-manual:
Unsupported command "added" (full line was "Added Linux ? *") received
from confmodule. at /var/lib/dpkg/info/linux-base.postinst line 1317,
 line 10.

system is lilo-based.  The "Added Linux" is from a lilo update.  Grub
does NOT work on system.   I may test this further in the future -
system is on third motherboard and second set of hard drives.

full update of "lilo":
Warning: LBA32 addressing assumed
Warning: The initial RAM disk is too big to fit between the kernel and
  the 15M-16M memory hole.  It will be loaded in the highest memory as
  though the configuration file specified "large-memory" and it will
  be assumed that the BIOS supports memory moves above 16M.
Added Linux ? *
Warning: The initial RAM disk is too big to fit between the kernel and
  the 15M-16M memory hole.  It will be loaded in the highest memory as
  though the configuration file specified "large-memory" and it will
  be assumed that the BIOS supports memory moves above 16M.
Added LinuxOLD ?
3 warnings were issued.

-- System Information:
Debian Release: squeeze/sid
 APT prefers unstable
 APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-2-vserver-686 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0] 1.5.29 Debian configuration 
management sy

ii  libapt-pkg-perl   0.1.24 Perl interface to libapt-pkg
ii  libuuid-perl  0.02-3+b1  Perl extension for using 
UUID inte


linux-base recommends no packages.

linux-base suggests no packages.

-- debconf-show failed



--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd

Bug#576442: marked as done (linux-base: Migration to UUID forgets about mdadm.conf)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:14 +
with message-id 
and subject line Bug#576442: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #576442,
regarding linux-base: Migration to UUID forgets about mdadm.conf
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.)


-- 
576442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-base
Version: 2.6.33-1~experimental.4
Severity: important
Tags: experimental

Hi:

I tried the kernel in experimental and it nicely suggested and even
updated itself some config files to use UUIDs instead of device names.

---8<---
These configuration files will be updated:

/etc/fstab, /etc/udev/rules.d/70-persistent-cd.rules, 
/etc/initramfs-tools/conf.d/resume
--->8---

But it forgot to mention /etc/mdadm/mdadm.conf could be affected as
DEVICE line allows direct naming of devices which get a different name
in .33 (changing the line to "DEVICE partitions" should work). So
mentioning the mdadm file or even upgrading that line would be nice.

Thanks.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0] 1.5.30 Debian configuration management sy
ii  libapt-pkg-perl   0.1.24 Perl interface to libapt-pkg
ii  libuuid-perl  0.02-3+b1  Perl extension for using UUID inte

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
* linux-base/disk-id-manual:
  linux-base/disk-id-convert-plan-no-relabel: true
* linux-base/disk-id-convert-plan: true
* linux-base/disk-id-convert-auto: true


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_

Bug#559578: marked as done (eeepc-acpi-scripts: EeePC 701 freezes with garbled screen while booting)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:03:13 +
with message-id 
and subject line Bug#559578: fixed in linux-2.6 2.6.32-11
has caused the Debian Bug report #559578,
regarding eeepc-acpi-scripts: EeePC 701 freezes with garbled screen while 
booting
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.)


-- 
559578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eeepc-acpi-scripts
Version: 1.1.3
Severity: critical
Justification: Breaks whole system

After the upgrade to 1.1.3 my EeePC 701 4G freezes on shortly after
setting the console fonts with a garbled screen (no more readable,
looks like lines being out of sync or so). I have to power it off by
pressing the power button 4 seconds. No more ping, nothing. Due to the
garbled screen, I do not know if there was any kernel panic or so.

It does not happen if I:

* unplug the power supply (not very usable).
* boot with acpi=off (neither very helpful)
* downgrade to version 1.1.2 (did that :-)
* boot with init=/bin/bash (of course)

It does happen:

* independent of the kernel (tried 2.6.30, 2.6.31, 2.6.31 from grml,
  2.6.32)
* independent of the udev or console-setup versions (downgraded both
  to the versions in testing since I first suspected them)
* even when I boot into single user mode (and power supply is plugged
  in)
* as soon as I plug in the power supply (in case I had it unplugged on
  startup) the system freezes and garbles the screen, also if running
  under X.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'stable'), (500, 'testing'), (110, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages eeepc-acpi-scripts depends on:
ii  acpi-support-base 0.130-1scripts for handling base ACPI eve
ii  acpid 1.0.10-4   Advanced Configuration and Power I
ii  pm-utils  1.2.6.1-3  utilities and scripts for power ma

Versions of packages eeepc-acpi-scripts recommends:
ii  alsa-utils1.0.21-1   ALSA utilities

Versions of packages eeepc-acpi-scripts suggests:
ii  aosd-cat   0.2.5-1   an on screen display tool which us
ii  gnome-osd  0.12.2-1  OSD message framework for GNOME
ii  ttf-bitstream-vera 1.10-7The Bitstream Vera family of free 
ii  ttf-dejavu 2.30-1Metapackage to pull in ttf-dejavu-
ii  ttf-freefont   20090104-5Freefont Serif, Sans and Mono True
ii  ttf-liberation 1.05.2.20091019-4 Fonts with the same metrics as Tim

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-11

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-

Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686

[maximilian attems]

On Tue, 09 Mar 2010, Bruce Ward wrote:

> Hello Max.
> 
> Did you get the initramfs? I sent it 17 February.
> 
> Bruce

didn't see any trouble relevant modules are inside.

only thing that I remakred was splashy,
could you please purge that to have it out of the game?
and then update-initramfs of course.. ;)

why do you attempt to load "unix" in
/etc/initramfs-tools/modules

it is built in since very long.
although this shouldn't change the trouble..

don't get the " /bin/sleep:  not found" it is 
clearly in the initramfs. might be due a busybox bug,
which version of busybox are you running

dpkg -l busybox

thanks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406043739.ga3...@stro.at

linux-2.6_2.6.32-11_amd64.changes ACCEPTED

[Archive Administrator]

Accepted:
firmware-linux-free_2.6.32-11_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-11_all.deb
linux-2.6_2.6.32-11.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-11.diff.gz
linux-2.6_2.6.32-11.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-11.dsc
linux-base_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-base_2.6.32-11_all.deb
linux-doc-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-11_all.deb
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
linux-libc-dev_2.6.32-11_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-11_amd64.deb
linux-manual-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-11_all.deb
linux-patch-debian-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-11_all.deb
linux-source-2.6.32_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-11_all.deb
linux-support-2.6.32-4_2.6.32-11_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-4_2.6.32-11_all.deb
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  to main/l/linux-2.6/xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb


Override entries for your package:
firmware-linux-free_2.6.32-11_all.deb - optional kernel
linux-2.6_2.6.32-11.dsc - source devel
linux-base_2.6.32-11_all.deb - optional kernel
linux-doc-2.6.32_2.6.32-11_all.deb - optional doc
linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb - optional kernel
linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb - optional kernel
linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb - optional kernel
linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb - optional kernel
linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb - optional kernel
linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb - optional kernel
linux-libc-dev_2.6.32-11_amd64.deb - optional devel
linux-manual-2.6.32_2.6.32-11_all.deb - optional doc
linux-patch-debian-2.6.32_2.6.32-11_all.deb - optional kernel
linux-source-2.6.32_2.6.32-11_all.deb - optional kernel
linux-support-2.6.32-4_2.6.32-11_all.deb - optional devel
xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb - optional kernel

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 447575 503766 553024 559578 569034 569724 571305 573607 573912 
574348 574368 574401 574421 574526 574598 574630 574987 575056 575189 575726 
576213 576243 576442 576537 


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
Archive: http://lists.debian.org/e1nz0wt-0001rg...@ries.debian.org

Bug#568223: marked as done (hibernate to disk crashes the system)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:25:48 +0100
with message-id <1270527948.24287.161.ca...@localhost>
and subject line Re: Bug#568223: hibernate to disk crashes the system
has caused the Debian Bug report #568223,
regarding hibernate to disk crashes the system
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.)


-- 
568223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-5
Severity: critical

Justification for "critical": Crashes the complete system,
including unrelated software. If this kind of problem is
typically not considered as critical, please adjust.

With 2.6.30 hibernating to disk worked (most of the time, but
not always). With 2.6.32 the system crashes immediately when
trying to hibernate from Gnome and I have to switch off the
computer. How can I debug the problem? Are there any interesting
log files or useful shell commands?

-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-trunk-686 root=/dev/mapper/vg0-lv0 ro quiet

** Not tainted

** Kernel log:
[5.611015] sd 1:0:0:0: [sda] Write Protect is off
[5.611019] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[5.611042] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[5.611180]  sda:
[5.615167] ide-cd driver 5.00
[5.617025] ide-cd: hda: ATAPI 24X DVD-ROM DVD-R/RAM CD-R/RW drive, 2048kB 
Cache
[5.617031] Uniform CD-ROM driver Revision: 3.20
[5.638283]  sda1 sda2 sda3
[5.638551] sd 1:0:0:0: [sda] Attached SCSI disk
[5.839180] device-mapper: uevent: version 1.0.3
[5.839358] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
dm-de...@redhat.com
[8.684415] usb-storage: device scan complete
[8.686532] scsi 0:0:0:0: Direct-Access Generic  STORAGE DEVICE   9407 
PQ: 0 ANSI: 0
[8.688396] sd 0:0:0:0: [sdb] Attached SCSI removable disk
[   26.908953] atkbd.c: Unknown key pressed (translated set 2, code 0x83 on 
isa0060/serio0).
[   26.908958] atkbd.c: Use 'setkeycodes e003 ' to make it known.
[   51.845837] PM: Starting manual resume from disk
[   51.930463] kjournald starting.  Commit interval 5 seconds
[   51.930470] EXT3-fs: mounted filesystem with ordered data mode.
[   58.069378] udev: starting version 150
[   62.328333] ACPI: SSDT 7f687ee3 0027A (v01  PmRef  Cpu0Ist 3000 INTL 
20050624)
[   62.328878] ACPI: SSDT 7f687874 005EA (v01  PmRef  Cpu0Cst 3001 INTL 
20050624)
[   62.344371] input: PC Speaker as /devices/platform/pcspkr/input/input6
[   62.376259] Monitor-Mwait will be used to enter C-1 state
[   62.376287] Monitor-Mwait will be used to enter C-2 state
[   62.376294] Marking TSC unstable due to TSC halts in idle
[   62.376388] processor LNXCPU:00: registered as cooling_device2
[   62.376857] Switching to clocksource hpet
[   62.392296] ACPI: SSDT 7f68815d 000C8 (v01  PmRef  Cpu1Ist 3000 INTL 
20050624)
[   62.392620] ACPI: SSDT 7f687e5e 00085 (v01  PmRef  Cpu1Cst 3000 INTL 
20050624)
[   62.420363] processor LNXCPU:01: registered as cooling_device3
[   62.452139] ACPI: Battery Slot [BAT0] (battery present)
[   62.468115] ACPI: AC Adapter [ADP1] (on-line)
[   62.492107] ACPI: Battery Slot [BAT1] (battery absent)
[   62.512866] parport_pc 00:09: reported by Plug and Play ACPI
[   62.512928] parport0: PC-style at 0x378, irq 5 [PCSPP,TRISTATE]
[   62.684142] i801_smbus :00:1f.3: PCI INT C -> GSI 19 (level, low) -> IRQ 
19
[   62.684149] ACPI: I/O resource :00:1f.3 [0x1c00-0x1c1f] conflicts with 
ACPI region SMBI [0x1c00-0x1c0f]
[   62.707028] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   63.296264] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 
0xa04753/0x20
[   63.329932] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input7
[   63.753288] Linux video capture interface: v2.00
[   63.938493] HDA Intel :00:1b.0: enabling device (0104 -> 0106)
[   63.938503] HDA Intel :00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 
16
[   63.938546] HDA Intel :00:1b.0: setting latency timer to 64
[   64.216453] hda_codec: ALC262: BIOS auto-probing.
[   64.217467] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input8
[   64.270869] uvcvideo: Found UVC 1.00 device FO13FF-65-1 PC-CAM (05c8:0103)
[   64.275334] input: FO1

Processed: retitle 572618 to libata missing workaround for HPA overlapping normal partitions

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 572618 libata missing workaround for HPA overlapping normal partitions
Bug #572618 [linux-2.6] IDE core applies Host Protected Area where it was 
previously ignored
Bug #574795 [linux-2.6] Libata transition and HPA caused disk size truncation
Changed Bug title to 'libata missing workaround for HPA overlapping normal 
partitions' from 'IDE core applies Host Protected Area where it was previously 
ignored'
Changed Bug title to 'libata missing workaround for HPA overlapping normal 
partitions' from 'Libata transition and HPA caused disk size truncation'
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052917714319.transcr...@bugs.debian.org

Processed: tagging 576199

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 576199 - moreinfo
Bug #576199 [linux-2.6] linux-2.6: ATL1E does not longer work on EEE PC 900A
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052896312809.transcr...@bugs.debian.org

Bug#570364: Output LVDS gone on Intel Mobile 915GM

[Ben Hutchings]

On Mon, 2010-02-22 at 12:51 +, Ben Hutchings wrote:
> On Sun, 2010-02-21 at 15:15 +0100, Stefan Ott wrote: 
> > Hi!
> > 
> > On Sat, Feb 20, 2010 at 22:20, Ben Hutchings  wrote:
> > > On Thu, 2010-02-18 at 21:11 +0100, Stefan Ott wrote:
> > >> > Please test the current version, 2.6.32-8, which has many fixes for the
> > >> > i915 video driver.
> > >>
> > >> Thanks, I tried but I still get the same result (dmesg attached)
> > >
> > > Unfortunately the log you sent stops before the i915 driver is active.
> > > You will need to let the X server start (or attempt to start) before
> > > sending the log.
> > >
> > > However, I think this bug may be the same as
> > > , which we have a fix for.  You can build
> > > amd test a kernel with this fix by following the instructions at
> > > .
> > >   Use the distribution codename 'sid'.
> > 
> > Okay, I tried that but I still get the same problem, that is, unless I
> > boot with i915.modeset=0 (as mentioned in the other bug report). dmesg
> > outputs are available if you think they're relevant.
> 
> Please report this upstream at , under
> product 'DRI', component 'DRM/Intel'.  Attach the log
> 'dmesg.2.6.32-3-686' and the corresponding X server log.

Have you done this?  I forgot to say, let us know the bug number so we
can track it.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#563667: marked as done (kernel BUG at /build/buildd/linux-2.6-2.6.30/debian/build/source_amd64_none/net/core/skbuff.c:2540!)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:20:36 +0100
with message-id <1270527636.24287.158.ca...@localhost>
and subject line Re: kernel BUG at 
/build/buildd/linux-2.6-2.6.30/debian/build/source_amd64_none/net/core/skbuff.c:2540!
has caused the Debian Bug report #563667,
regarding kernel BUG at 
/build/buildd/linux-2.6-2.6.30/debian/build/source_amd64_none/net/core/skbuff.c:2540!
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.)


-- 
563667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---


Package: linux-image-2.6.30-2-amd64
Version: 2.6.30-8squeeze1
Severity: important

I have a server with some ethernet interfaces, and it's routing between
them:
02:00.0 Ethernet controller: Mellanox Technologies MT25448 [ConnectX EN 10GigE, 
PCIe 2.0 2.5GT/s] (rev a0)
03:00.0 Ethernet controller: Mellanox Technologies MT25448 [ConnectX EN 10GigE, 
PCIe 2.0 2.5GT/s] (rev a0)
05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection 
(rev 01)
05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection 
(rev 01)


Traffic flows between the 10g cards and the 1g card (only one of them is
used at this time), and from time to time I get a panic just like in the
subject line.

I've upgraded from the lenny kernel because oopses were much more frequent
with that (in fact, I could cause one with disabling tx checksumming on
the igb card and then routing 1 packet through the box (mlx4_en->igb)). I
don't know if this is related to the issue at hand, but I'm attaching the
log from that oops as well.


Best regards,
Matyas Koszik




[93087.728052] [ cut here ]
[93087.783188] kernel BUG at 
/build/buildd/linux-2.6-2.6.30/debian/build/source_amd64_none/net/core/skbuff.c:2540!
[93087.903799] invalid opcode:  [#1] SMP
[93087.952893] last sysfs file: 
/sys/devices/pci:00/:00:1e.0/:01:03.0/class
[93088.045479] CPU 0
[93088.069561] Modules linked in: drbd cn nfsd nfs lockd fscache nfs_acl 
auth_rpcgss sunrpc nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack 
iptable_filter ip_tables x_tables raid456 async_xor async_memcpy async_tx xor 
ipmi_devintf mlx4_en w83627hf hwmon_vid ipmi_si ipmi_msghandler loop snd_pcm 
snd_timer snd soundcore snd_page_alloc i2c_i801 i2c_core serio_raw pcspkr 
psmouse joydev evdev button processor xfs exportfs dm_mirror dm_region_hash 
dm_log dm_snapshot raid1 md_mod ses enclosure sd_mod crc_t10dif usb_storage 
usbhid hid ahci igb libata mptsas mptscsih mptbase scsi_transport_sas uhci_hcd 
ehci_hcd dca mlx4_core scsi_mod thermal fan thermal_sys dm_mod raid6_pq [last 
unloaded: scsi_wait_scan]
[93088.816583] Pid: 0, comm: swapper Not tainted 2.6.30-2-amd64 #1 X8DT3
[93088.893598] RIP: 0010:[]  [] 
skb_segment+0x116/0x4d3
[93088.990440] RSP: 0018:88002ba03a90  EFLAGS: 00010212
[93089.053963] RAX:  RBX: 0084 RCX: 88013ccb0c00
[93089.139282] RDX:  RSI: 00110bb3 RDI: 88011d388080
[93089.224601] RBP: 0b78 R08: 00150b00 R09: 8061cf20
[93089.309923] R10: 000e R11: 88011d388080 R12: 88011d388080
[93089.395243] R13: 88013d410008 R14: 0b50 R15: 88010dffedc0
[93089.480563] FS:  () GS:88002ba0() 
knlGS:
[93089.577302] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[93089.646014] CR2: 7fff5687df00 CR3: 00201000 CR4: 06e0
[93089.731335] DR0:  DR1:  DR2: 
[93089.816655] DR3:  DR6: 0ff0 DR7: 0400
[93089.901975] Process swapper (pid: 0, threadinfo 8062, task 
805be390)
[93089.998712] Stack:
[93090.022690]  9880ac00 0042 00841e41cc44 
0246
[93090.109255]  8801028ee658 00ffa02f8c1e  

[93090.198104]  004205a8 00420042 0001 
0042
[93090.289133] Call Trace:
[93090.318300]   <0> [] ? tcp_tso_segment+0x273/0x283
[93090.399677]  [] ? inet_gso_segment+0xdf/0x18e
[93090.470569]  [] ? skb_gso_segment+0x1b4/0x236
[93090.541462]  [] ? __nf_ct_deliver_cached_events+0x44/0x6d 
[nf_conntrack]
[93090.640379]  [] ? nf_ct_deliver_cached_events+0x39/0x45 
[nf_conntrack]
[93090.737221]  [] ? ipv4_confirm+0x11b/0x125 
[nf_conntrack_ipv4]
[93090.825759]  [] ? dev_hard_start_xmit+0x1b0/0x271
[93090.900804]  [] ? __qdisc_run+0xe2/0x1ed
[93090.966505]  [] ? dev_queue_xmit+0x230/0x32

Processed: tagging 566522

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 566522 - moreinfo
Bug #566522 [linux-2.6] linux-image-2.6.32-trunk-486: eth0 silently disapear 
after upgrading from 2.6.30 to 2.6.32-trunk (3c503)
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.12705277643277.transcr...@bugs.debian.org

Processed: tagging 551733

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 551733 moreinfo
Bug #551733 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: Cannot boot 
kernel 2.6.26-2-686
Added tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052938415695.transcr...@bugs.debian.org

Processed: tagging 570844

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 570844 - moreinfo
Bug #570844 [linux-2.6] System with AMD Turion m540 hangs while loading APIC
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.12705282417943.transcr...@bugs.debian.org

Processed: tagging 568557

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 568557 - moreinfo
Bug #568557 [linux-2.6] linux-image-2.6.32-2-amd64: keyboard and mouse lockup, 
system is still running (asus_atk0110?)
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.12705279985770.transcr...@bugs.debian.org

Bug#571761: linux-image-2.6.32-2-686: 2.6.32 required noapic on Acer Travelmate 430 where earlier kernels did not

[Ben Hutchings]

On Sat, 2010-02-27 at 22:32 +, Ben Hutchings wrote:
> On Sat, 2010-02-27 at 20:21 +, David Goodenough wrote:
> > Package: linux-2.6
> > Version: 2.6.32-8
> > Severity: important
> > 
> > 
> > With kernels up to 2.6.26 this ancient machine did not require any special 
> > kernel boot options, but with 2.6.32 
> > I need to add noapic to the kernel command in grub.
> > 
> > If I do not add noapic the kernel gets as far as the pcmcia socket and gets 
> > through that completely, and then hangs
> > competely - nothing works.
> > 
> > Looking in the 2.6.26 kernel dmesg just after the initialisation of the 
> > pcmcia socket there were messages about 
> > ACPI derived interrupts.  So I thought trying noapic was worth trying 
> > noapic, and now 2.6.32 boots normally.
> 
> ACPI and APIC are two entirely different technologies, although they are
> both involved in interrupt routing.
> 
> > This suggests that something has changed in the APIC handling for the old 
> > chip in the 430, for the worse. Of course
> > now manual intervention is required to make this machine boot.
> 
> Please report this upstream at  under
> product 'Platform Specific/Hardware', component 'i386'.  Attach the
> kernel logs for 2.6.32 with and without 'noapic' to the bug report.

Sorry, I don't know how I came up with that URL... please use the bug
tracker at !  Then, let us know the bug
number so we can track it.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Processed: closing 564833

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # submitter reported as fixed
> close 564833
Bug#564833: general: ipolldevd takes 30% CPU
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Иванов Михаил 


> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.12705277433084.transcr...@bugs.debian.org

Bug#576405: linux-image-2.6.26: Deadlock during combined NFS3/NFS4 use

[Ben Hutchings]

On Sun, 2010-04-04 at 21:20 +0100, Anton Ivanov wrote:
> On Sun, 2010-04-04 at 20:40 +0100, Ben Hutchings wrote:
> > On Sun, 2010-04-04 at 09:44 +0100, Anton Ivanov wrote:
> > > Package: linux-image-2.6.26
> > > Version: nfsfix.1
> > 
> > What does that version mean?  Have you applied your own patches?  Can
> > you reproduce this with an official kernel package?
> 
> That is a rather old "official" with only the NFS regression applied
> (the one I dug out a while back - bug 524199). It worked and I have not
> touched it since.

That fix was applied in a stable update some time ago.  You do not need
to use your own patched kernel version, and if you continue with that
version you will be missing security updates.

> That is just one machine on which I am observing it. I also see it on
> several other machines with:
> 
> 1. Latest "Official" - 486, 686
[...]

OK.  Next, can you test whether the kernel version in unstable
(linux-image-2.6.32-4-* version 2.6.32-10) or testing
(linux-image-2.6.32-3-* version 2.6.32-9) also has this bug?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Processed: tagging 575183

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 575183 - moreinfo
Bug #575183 [linux-image-2.6.32-4-xen-amd64] fails to boot on SGI C2108-F6 
server under Xen 3.4 hypervisor
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052873311320.transcr...@bugs.debian.org

Bug#562072: marked as done (general: computer freezes totally when i plug an usb key)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:16:15 +0100
with message-id <1270527375.24287.156.ca...@localhost>
and subject line Re: general: computer freezes totally when i plug an usb key
has caused the Debian Bug report #562072,
regarding general: computer freezes totally when i plug an usb key
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.)


-- 
562072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: general
Severity: critical
Justification: breaks the whole system



-- System Information:
Debian Release: squeeze/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

computer freezes totally when i plug an usb key
( keyboard desactivates,strange messages like "cpu_idle+0x50/0x91" or 
things like "notifier_call"...

and i dont know where to find a copy of the crash messages )
with a live cd (knoppix x86) no problem
performed a scan of the harddisk with the seagate utility:no problem 
detected

this problem has been lasting for several months

where can i find the file with the complete log?



--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#567435: marked as done (linux-image-2.6.32-trunk-686: address space collision)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:23:31 +0100
with message-id <1270527811.24287.159.ca...@localhost>
and subject line Re: linux-image-2.6.32-trunk-686: address space collision
has caused the Debian Bug report #567435,
regarding linux-image-2.6.32-trunk-686: address space collision
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.)


-- 
567435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-2.6
Version: 2.6.32-5
Justification: breaks the whole system
Severity: critical

After last "aptitude full-upgrade" the new kernel 
"linux-image-2.6.32-trunk-686" was installed on my Debian squeeze system.


But every time I boot from the refered new kernel, I see the following 
error message at the very beginning of the boot process:


"pci :02:05.0: BAR 6: address space collision on of device 
[0xfeaa-0xfeab]"


I also get that message by running the following command after booting:

dmesg | grep -i collision

After showing that message, the system boots apparently normal and I'm 
able to graphically login via Gnome or LXDE.


But, after using the system for some minutes (it varies... could be 10 
m, 30 m...) the system hangs completely, to the point that I can't even 
kill X server (even via Ctrl+Alt+Backspace or Alt+SysRq+K) or start 
another TTY console.

Also the "Num Lock" and "Caps Lock" lights on the keyboard start blinking.

So the only option is to turn off the computer by pressing the button on 
the computer case!


Note:
I have 2 other computers, with different hardware (different graphics 
card, etc), but they are also running Debian Squeeze and with similar 
installation and configuration.
On one of them I don't get this bug. On the other of them I get 
precisely this same bug.



-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) 
(gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010


** Command line:
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 root=/dev/mapper/hda2_crypt ro quiet

** Not tainted

** Kernel log:
[3.432218] usb usb4: Product: UHCI Host Controller
[3.43] usb usb4: Manufacturer: Linux 2.6.32-trunk-686 uhci_hcd
[3.432226] usb usb4: SerialNumber: :00:1d.2
[3.432332] usb usb4: configuration #1 chosen from 1 choice
[3.432383] hub 4-0:1.0: USB hub found
[3.432397] hub 4-0:1.0: 2 ports detected
[3.432473] uhci_hcd :00:1d.3: PCI INT A -> GSI 16 (level, low) 
-> IRQ 16

[3.432482] uhci_hcd :00:1d.3: setting latency timer to 64
[3.432488] uhci_hcd :00:1d.3: UHCI Host Controller
[3.432505] uhci_hcd :00:1d.3: new USB bus registered, assigned 
bus number 5

[3.432531] uhci_hcd :00:1d.3: irq 16, io base 0xef40
[3.432583] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[3.432588] usb usb5: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[3.432593] usb usb5: Product: UHCI Host Controller
[3.432597] usb usb5: Manufacturer: Linux 2.6.32-trunk-686 uhci_hcd
[3.432601] usb usb5: SerialNumber: :00:1d.3
[3.432721] usb usb5: configuration #1 chosen from 1 choice
[3.432772] hub 5-0:1.0: USB hub found
[3.432784] hub 5-0:1.0: 2 ports detected
[3.462019] SCSI subsystem initialized
[3.489580] libata version 3.00 loaded.
[3.510229] ide-cd driver 5.00
[3.514448] ide-gd driver 1.18
[3.514499] hda: max request size: 512KiB
[3.514926] hda: 234441648 sectors (120034 MB) w/2048KiB Cache, 
CHS=16383/255/63

[3.515068] hda: cache flushes supported
[3.515135]  hda:
[3.520090] ide-cd: hdc: ATAPI 48X DVD-ROM drive, 256kB Cache
[3.520099] Uniform CD-ROM driver Revision: 3.20
[3.520281]  hda1 hda2 hda3
[3.867258] device-mapper: uevent: version 1.0.3
[3.867692] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) 
initialised: dm-de...@redhat.com

[   21.534816] EXT4-fs (dm-0): mounted filesystem with ordered data mode
[   23.697805] udev: starting version 150
[   24.315218] input: PC Speaker as /devices/platform/pcspkr/input/input3
[   24.358559] processor LNXCPU:00: registered as cooling_device0
[   24.359031] processor LNXCPU:01: registered as cooling_device1
[   24.439641] i801_smbus :00:1f.3: PCI INT B -> GSI 17 (level, low) 
-> IRQ 17
[   24.451810] input: GenPS/2 Genius Mouse as 
/devices/platform/i8042/serio1/input/input4

[   24.499201] parport_pc 00:0a: reported by Plug and Play ACPI
[   24.499316] parport0: PC-style at 0x378 (0x778), irq 7 
[PCSPP,TRISTATE,EPP]

[ 

Bug#568625: marked as done (kde: KDE 4.3.4 Desktop crashes with Kernel 2.6.32-trunk-amd64)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:27:04 +0100
with message-id <1270528024.24287.162.ca...@localhost>
and subject line Re: kde: KDE 4.3.4 Desktop crashes with Kernel 
2.6.32-trunk-amd64
has caused the Debian Bug report #568625,
regarding kde: KDE 4.3.4 Desktop crashes with Kernel 2.6.32-trunk-amd64
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.)


-- 
568625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde
Version: KDE 4.3.4
Severity: grave
Justification: renders package unusable

After a recent apt-get dist-upgrade, KDE-Desktop would start, remain intact for 
some 4-5 seconds and crash utterly, leaving the screen with psychedelic random 
patterns.

Booting into squeeze with former kernel 2.6.30-2-amd64 makes the computer 
usable again.

Looks like a kernel problem.

Graphics come from Intel IGP G43 Chipset.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#570873: marked as done (linux-image-2.6.32-trunk-amd64: Using firewire hangs computer)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 05:32:27 +0100
with message-id <1270528347.24287.164.ca...@localhost>
and subject line Re: linux-image-2.6.32-trunk-amd64: Using firewire hangs 
computer
has caused the Debian Bug report #570873,
regarding linux-image-2.6.32-trunk-amd64: Using firewire hangs computer
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.)


-- 
570873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-5
Severity: critical
Justification: breaks the whole system

Pluging a camera, the fw1 device is created. Then, try using dvgrab, it starts 
de camera but not get video. After several tries, I see a dump in the shell and 
I get a kernel panic (the three leds of the keyborad blinks). The dump is los 
logged after reboot.

-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010

** Command line:
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-amd64 
root=/dev/mapper/volumenes--md1-sistema--64 ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[   17.781427] REISERFS (device dm-0): Removing [1165 46316 0x0 SD]..done
[   17.781452] REISERFS (device dm-0): Removing [1165 46237 0x0 SD]..done
[   17.781481] REISERFS (device dm-0): Removing [1165 40331 0x0 SD]..done
[   17.781523] REISERFS (device dm-0): Removing [1165 40282 0x0 SD]..done
[   17.781559] REISERFS (device dm-0): Removing [1165 29471 0x0 SD]..done
[   17.781588] REISERFS (device dm-0): Removing [1165 27603 0x0 SD]..done
[   17.781626] REISERFS (device dm-0): Removing [91519 659 0x0 SD]..done
[   17.781639] REISERFS (device dm-0): There were 9 uncompleted 
unlinks/truncates. Completed
[   18.207570] loop: module loaded
[   19.047002] kjournald starting.  Commit interval 5 seconds
[   19.047007] EXT3-fs warning: mounting unchecked fs, running e2fsck is 
recommended
[   19.088013] EXT3 FS on md0, internal journal
[   19.088016] EXT3-fs: recovery complete.
[   19.088020] EXT3-fs: mounted filesystem with ordered data mode.
[   20.379460] kjournald starting.  Commit interval 5 seconds
[   20.379475] EXT3-fs warning: mounting fs with errors, running e2fsck is 
recommended
[   20.392534] EXT3 FS on dm-4, internal journal
[   20.392537] EXT3-fs: recovery complete.
[   20.398860] EXT3-fs: mounted filesystem with ordered data mode.
[   20.842989] kjournald starting.  Commit interval 5 seconds
[   20.843002] EXT3-fs warning: maximal mount count reached, running e2fsck is 
recommended
[   20.843423] EXT3 FS on dm-2, internal journal
[   20.843425] EXT3-fs: recovery complete.
[   20.843642] EXT3-fs: mounted filesystem with ordered data mode.
[   20.906129] kjournald starting.  Commit interval 5 seconds
[   20.906138] EXT3-fs warning: maximal mount count reached, running e2fsck is 
recommended
[   20.906311] EXT3 FS on hdb1, internal journal
[   20.906313] EXT3-fs: recovery complete.
[   20.906434] EXT3-fs: mounted filesystem with ordered data mode.
[   20.993955] Adding 4194296k swap on /dev/mapper/volumenes--md1-swap.  
Priority:-1 extents:1 across:4194296k 
[   21.499592] r8169: eth0: link up
[   21.499600] r8169: eth0: link up
[   23.013653] eth2: link down
[   23.014111] ADDRCONF(NETDEV_UP): eth2: link is not ready
[   23.814312] fuse init (API version 7.13)
[   26.532974] ip_tables: (C) 2000-2006 Netfilter Core Team
[   26.558235] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   26.558449] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please 
use
[   26.558451] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module 
option or
[   26.558452] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[   32.153509] eth0: no IPv6 routers present
[   37.43] Bluetooth: Core ver 2.15
[   37.333583] NET: Registered protocol family 31
[   37.333585] Bluetooth: HCI device and connection manager initialized
[   37.333588] Bluetooth: HCI socket layer initialized
[   37.358243] Bluetooth: L2CAP ver 2.14
[   37.358245] Bluetooth: L2CAP socket layer initialized
[   37.623125] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   37.623128] Bluetooth: BNEP filters: protocol multicast
[   37.708359] Bridge firewalling registered
[   37.746467] Bluetooth: SCO (Voice Link) ver 0.6
[   37.746469] Bluetooth: SCO socket layer initialized
[   39.540230] lp0: using parport0 (interrupt-driven).
[   39.540626] lp1: using parport1 (polling).
[   39.544148] ppdev: user-space parallel port driver
[   39.6

Processed: tagging 551733

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 551733 - moreinfo
Bug #551733 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: Cannot boot 
kernel 2.6.26-2-686
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052734731592.transcr...@bugs.debian.org

Bug#576635: Unable to access an encrypted root partition after a failed resume

[Daniel Burrows]

Package: linux-image-2.6.32-3-amd64
Version: 2.6.32-9
Severity: important

  I set up unstable on a new laptop last week, using the same
configuration that I had on my last laptop: a single LVM physical
volume, encrypted (with the configuration created by the installer),
divided into two logical volumes, one for swap and one for the root
partition.  /boot, obviously, isn't on that partition.

  This morning, I tried to unhibernate the laptop for the second or
third time ever.  I entered my password and the screen blanked, but this
time I was unlucky and it didn't come back (I was starting to hope
hibernate would actually work ... oh well).  So after giving it a good
five minutes to do something, I finally just killed the power and
rebooted.

  After the reboot, the initrd wouldn't accept my encryption passphrase.
More specifically: it would unlock the partition, then announce that it
couldn't find a filesystem on the device.  I've booted the Squeeze live
CD on the laptop, and it appears that the initrd was correct.  I can
unlock the partition by hand, but pvdisplay insists that the unencrypted
device is not an LVM physical volume.  Nor does it appear to be a
filesystem of any normal sort.  I'm not sure what sort of horrible thing
happened to it at this point.

  I'm currently trying to hook the laptop in question up to the network
so I can grab an image of the block device for analysis, in the hope
that I can eventually figure out how to get my data off it (I'd like to
get a working system on the laptop soon so I can use it one the bus).
Obviously, I'd appreciate any suggestions you can give me with regard to
tracking down what happened and/or repairing the system.

  Daniel

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406040923.ga5...@emurlahn.burrows.local

Processed: tagging 556231

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 556231 - moreinfo
Bug #556231 [linux-2.6] linux-image-2.6.30-2-amd64: Resumed xfsdump on 
2.6.30-2-amd64 causes kernel panic
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052710429285.transcr...@bugs.debian.org

Bug#552299: forcedeth: nVidia MCP55 ethernet and forcedeth module - fails to connect

[Ben Hutchings]

On Tue, 2010-03-16 at 17:20 +0100, Romain DEGEZ wrote:
> I own a P5N32-E SLI Asus motherbord.
> 
> The bug is still present with 2.6.32-3-686 debian kernel

It looks like this bug is already known and worked around for a variant
of this motherboard.

Please send the output of
lspci -n
and
grep -s . 
/sys/class/dmi/id/{sys,product,chassis,bios,board}_{vendor,name,version}
so we can see how to detect this specific motherboard.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Re: Bug#576601: closed by Ben Hutchings (Re: Bug#576601: linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script)

[Ben Hutchings]

On Tue, 2010-04-06 at 00:55 -0300, Tom Cerul wrote:
> Yeah, that's one of the disadvantages of writing stable software.
> It'll just run for years without updates.  :)  Yup, I'm just going
> through etch to get to lenny.
> 
> I'm pretty sure it's just the one package. Here's the command and
> results. I ran it twice so the other packages wouldn't clutter up the
> results.

OK, I've now downloaded the binary package for myself, and sure enough
there is a preinst script, though I can't see how it gets there.  (I
only recently joined the kernel team so I'm not that familiar with how
older versions of the kernel packages were built.)

> *
> LinBox:/home/tom# aptitude install linux-image-2.6.18-6-686
> Reading package lists... Done
> Building dependency tree... Done
> Reading extended state information
> Initializing package states... Done
> Writing extended state information... Done
> Reading task descriptions... Done
> Building tag database... Done
> The following NEW packages will be installed:
>   linux-image-2.6.18-6-686
> 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0B/16.3MB of archives. After unpacking 48.0MB will be used.
> Writing extended state information... Done
> Preconfiguring packages ...
> (Reading database ... 100906 files and directories currently installed.)
> Unpacking linux-image-2.6.18-6-686 (from
> .../linux-image-2.6.18-6-686_2.6.18.dfsg.1-24_i386.deb) ...
> Ok, Aborting
[...]

It looks like you have set debconf to be non-interactive, and the kernel
preinst script is trying to ask you a question that you really do need
to answer.  Run 'dpkg-reconfigure debconf' to fix that.  Also check
whether the environment variable DEBIAN_FRONTEND is set, as that will
override the system default.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#534993: marked as done (System hangs at startup with lm-sensors installed)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:25:56 +0100
with message-id <1270524356.24287.116.ca...@localhost>
and subject line Re: System hangs at startup with lm-sensors installed
has caused the Debian Bug report #534993,
regarding System hangs at startup with lm-sensors installed
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.)


-- 
534993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lm-sensors
Version: 1:3.1.0-2
Severity: critical
Justification: breaks the whole system

The system hangs at startup with the message "Setting sensors limits"
when I boot kernel 2.6.30 from unstable, the installed 2.6.29 kernel and
lm-sensors causes no problems. /etc/modules contains only loop,
sensors-detect doesn't find any sensors.

sensors as root says:

acpitz-virtual-0
Adapter: Virtual device
temp1:   +49.0°C  (crit = +100.0°C)

On 2.6.29 sensors -s doesn't do anything visible, but I guess either
sensors or sensors -s must cause the hang.

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (900, 'stable'), (850, 'testing'), (800, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lm-sensors depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libsensors4   1:3.1.0-2  library to read temperature/voltag
ii  perl  5.10.0-19  Larry Wall's Practical Extraction 
ii  sed   4.1.5-6The GNU sed stream editor

lm-sensors recommends no packages.

Versions of packages lm-sensors suggests:
pn  i2c-tools  (no description available)
pn  read-edid  (no description available)
pn  sensord(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#505107: marked as done ([SPAM] udev: e100 does not work in Compaq ML350 G2)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:22:31 +0100
with message-id <1270524151.24287.110.ca...@localhost>
and subject line Re: [SPAM] udev: e100 does not work in Compaq ML350 G2
has caused the Debian Bug report #505107,
regarding [SPAM] udev: e100 does not work in Compaq ML350 G2
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.)


-- 
505107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 0.125-7
Severity: important

Driver e100 does not work for default NIC in Compaq ML350 G2 while 
eepro100 does.
Sadly, eepro100 is blacklisted in udev, which renders network unusable.
Commenting the blacklist (/etc/modprobe.d/blacklist) for eepro100 and 
adding eepro100 to /etc/modules fixes the problem.

Please do not hesitate to request more information about this problem.
I'm not sure I should not have registered this bug againt kernel package 
instead.

Regards

-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 56
-rw-r--r-- 1 root root 3586 2008-09-19 03:11 50-udev.rules
-rw-r--r-- 1 root root 1543 2008-09-19 03:11 60-persistent-input.rules
-rw-r--r-- 1 root root 4554 2008-09-19 03:11 60-persistent-storage.rules
-rw-r--r-- 1 root root 1582 2008-09-19 03:11 60-persistent-storage-tape.rules
-rw-r--r-- 1 root root  523 2008-09-19 03:11 60-persistent-v4l.rules
-rw-r--r-- 1 root root  394 2008-11-06 23:23 70-persistent-cd.rules
-rw-r--r-- 1 root root  385 2008-11-06 23:23 70-persistent-net.rules
-rw-r--r-- 1 root root  452 2008-09-19 03:11 75-cd-aliases-generator.rules
-rw-r--r-- 1 root root 3083 2008-09-19 03:11 75-persistent-net-generator.rules
-rw-r--r-- 1 root root 2282 2008-09-19 03:11 80-drivers.rules
-rw-r--r-- 1 root root 4247 2008-09-19 03:11 91-permissions.rules
-rw-r--r-- 1 root root  593 2008-09-19 03:11 95-late.rules

-- /sys/:
/sys/block/cciss!c0d0/cciss!c0d0p1/dev
/sys/block/cciss!c0d0/cciss!c0d0p2/dev
/sys/block/cciss!c0d0/cciss!c0d0p5/dev
/sys/block/cciss!c0d0/dev
/sys/block/dm-0/dev
/sys/block/dm-1/dev
/sys/block/dm-2/dev
/sys/block/fd0/dev
/sys/block/hda/dev
/sys/block/loop0/dev
/sys/block/loop1/dev
/sys/block/loop2/dev
/sys/block/loop3/dev
/sys/block/loop4/dev
/sys/block/loop5/dev
/sys/block/loop6/dev
/sys/block/loop7/dev
/sys/block/ram0/dev
/sys/block/ram10/dev
/sys/block/ram11/dev
/sys/block/ram12/dev
/sys/block/ram13/dev
/sys/block/ram14/dev
/sys/block/ram15/dev
/sys/block/ram1/dev
/sys/block/ram2/dev
/sys/block/ram3/dev
/sys/block/ram4/dev
/sys/block/ram5/dev
/sys/block/ram6/dev
/sys/block/ram7/dev
/sys/block/ram8/dev
/sys/block/ram9/dev
/sys/class/bsg/1:0:6:0/dev
/sys/class/input/input0/event0/dev
/sys/class/input/input1/event1/dev
/sys/class/input/input2/event2/dev
/sys/class/input/input3/event3/dev
/sys/class/input/input3/mouse0/dev
/sys/class/input/mice/dev
/sys/class/misc/cpu_dma_latency/dev
/sys/class/misc/device-mapper/dev
/sys/class/misc/hpet/dev
/sys/class/misc/network_latency/dev
/sys/class/misc/network_throughput/dev
/sys/class/misc/psaux/dev
/sys/class/misc/snapshot/dev
/sys/class/rtc/rtc0/dev
/sys/class/scsi_tape/nst0a/dev
/sys/class/scsi_tape/nst0/dev
/sys/class/scsi_tape/nst0l/dev
/sys/class/scsi_tape/nst0m/dev
/sys/class/scsi_tape/st0a/dev
/sys/class/scsi_tape/st0/dev
/sys/class/scsi_tape/st0l/dev
/sys/class/scsi_tape/st0m/dev
/sys/class/sound/timer/dev
/sys/class/usb_device/usbdev1.1/dev
/sys/class/usb_endpoint/usbdev1.1_ep00/dev
/sys/class/usb_endpoint/usbdev1.1_ep81/dev
/sys/devices/pci:00/:00:0f.2/usb1/dev

-- Kernel configuration:


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages udev depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  libc6 2.7-15 GNU C Library: Shared libraries
ii  libselinux1   2.0.65-5   SELinux shared libraries
ii  libvolume-id0 0.125-7libvolume_id shared library
ii  lsb-base  3.2-20 Linux Standard Base 3.2 init scrip

udev recommends no packages.

udev suggests no packages.

-- debconf information:
  udev/new_kernel_needed: false
  udev/reboot_needed:


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a di

Bug#448503: marked as done (NFS client problem - writing with group-access fails)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:15:23 +0100
with message-id <1270523723.24287.105.ca...@localhost>
and subject line Re: NFS client problem - writing with group-access fails
has caused the Debian Bug report #448503,
regarding NFS client problem - writing with group-access fails
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.)


-- 
448503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-5-686
Version: 2.6.18+6etch2
Severity: important

This is a re-opening of an error reported as Bug#448161
for the package
Package: nfs-common
Version: 1.0.10-6+etch.1
because its maintainer
("Steinar H. Gunderson" )
[thank you, I took your advice] told me that the nfs-common, and
nfs-utils package are the wrong address to turn to with nfs client
permission problems.

Thus I'm repeating the description here. I can also tell you,
that a 2.6.20-version (2.6.20-3), that I installed on some
machines does not(!) solve the problem (yet), should that be
of any help.

The sarge-systems that work run on kernels 2.6.8-4-686 (plain
from the Debian 'proposed update' repository, without
modification), and (self-compiled) 2.6.12-1-686 with an nfs-patch
to avoid an nfs cookie-sign-bit problem as it arises from SGI's
IRIX e.g. The patch in 2.6.12 is unrelated to the problem presented
here, as far as I can tell!

If I can be of any further help in this, please don't hesitate to
contact me.

Here's the problem itself:
When trying to alter/change/overwrite a file via nfs, that
the user doesn't own, but where the file belongs to and is
writeable by a group, that the user is in as his non-primary
group also, an I/O ("operation not permitted") error is reported
and the operation fails. This happens only, when trying to change
the file, pure access or reading works fine.

The nfs-protocol should be version 3, as the nfs-server is an
AIX v5.2 system.

The systems involved run on Debian v4.0 ('etch' and
'etch-proposed-updates').

Systems on 'sarge' and 'sarge-proposed-updates' worked and still
do flawlessly here, and raise no problem with respect to this
behaviour; nor do other Unix-variants. Only 'etch' seems to be
affected.

Thanks and greetings,
 Ruediger Oberhage


--- End Message ---
--- Begin Message ---
I'm closing this because the previous request to report the bug upstream
was never answered.  If this bug is still present in Linux 2.6.32
(currently in testing, unstable and backports) then please report it
upstream at  and let us know the bug
number.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#539844: marked as done (ath5k: ath5k and orinoco 802.11b/g pcmcia card works on i686 kernel but not bigmem version)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:26:50 +0100
with message-id <1270524410.24287.117.ca...@localhost>
and subject line Re: ath5k: ath5k and orinoco 802.11b/g pcmcia card works on 
i686 kernel but not bigmem version
has caused the Debian Bug report #539844,
regarding ath5k: ath5k and orinoco 802.11b/g pcmcia card works on i686 kernel 
but not bigmem version
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.)


-- 
539844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-686-bigmem
Version: 2.6.26-17lenny1
Severity: important
File: ath5k

Recently installed Debian 5 with latest i686 kernel(2.6.26-2-i686).  My 
wireless card(orinoco 802.11b/g pcmcia card) worked great.  Realized my 4gb of 
memory wasn't being fully utilized so installed the same version of the bigmem 
kernel(and headers, etc).  Rebooted into it and it gives the following error:
Aug 2 18:38:42 skynet kernel: [ 12.609417] ath5k_pci :04:00.0:
enabling device ( -> 0002)
Aug 2 18:38:42 skynet kernel: [ 12.609417] ath5k_pci :04:00.0:
registered as 'phy0'
Aug 2 18:38:42 skynet kernel: [ 12.912966] ath5k_pci: probe of
:04:00.0 failed with error -110

Tried the backports 2.6.30-bigmem and failed, but with a different error(radio 
not supported).

-- Package-specific info:

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

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

Versions of packages linux-image-2.6.26-2-686-bigmem 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-bigmem recommends:
ii  libc6-i6862.7-18 GNU C Library: Shared libraries [i

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

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


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#502845: linux-image-2.6.32-1-amd64 / open-iscsi amd64 login hang

[Ben Hutchings]

On Mon, 2010-02-15 at 21:19 +0100, Florian Lohoff wrote:
> On Thu, Feb 11, 2010 at 09:13:21PM +0100, Bastian Blank wrote:
> > On Thu, Feb 11, 2010 at 08:23:12PM +0100, Florian Lohoff wrote:
> > > Something _is_ broken - I am very successful building up 
> > > open-iscsi/iscsitarget
> > > pairs on i386 - as soon as the initiator (open-iscsi) is on amd64 the 
> > > login
> > > hangs forever ... No matter whether the target is on the same machine
> > > or on a different machine ...
> > 
> > Yes, it is. The iscsi_uevent structure defined in scsi/iscsi_if.h
> > suffers of the 64-bit-allignment-desease on i386.
> > 
> > Also please not that this interface is officialy _not_ exported.
> 
> So? What would be the correct state? Wontfix? Forwarded-UpStream?

If you want to get this fixed in the kernel then please report this
upstream at  or on an appropriate mailing
list.  If it's accepted as a real bug and fixed upstream then we can
backport the fix.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#516382: marked as done (linux-image-2.6.26-1-alpha-generic: tg3: incoming ssh fails with "Corrupted MAC on input")

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:24:00 +0100
with message-id <1270524240.24287.113.ca...@localhost>
and subject line Re: linux-image-2.6.26-1-alpha-generic: tg3: incoming ssh 
fails with "Corrupted MAC on input"
has caused the Debian Bug report #516382,
regarding linux-image-2.6.26-1-alpha-generic: tg3: incoming ssh fails with 
"Corrupted MAC on input"
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.)


-- 
516382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-alpha-generic
Version: 2.6.26-13
Severity: important

Hi,

After upgrading from etch to lenny, and booting the new kernel, I realized I 
couldn't login into the box anymore: ssh would consistently fail to connect 
with:

Corrupted MAC on input

It's reproducible across reboots. When I rebooted into 2.6.18, the problem 
vanished. I'm using a BCM 5701 (tg3 driver) GigE NIC.

Here's dmesg output with 2.6.18.dfsg.1-24:
tg3.c:v3.65 (August 07, 2006)
eth2: Tigon3 [partno(A6825-60101) rev 0105 PHY(5701)] (PCI:33MHz:64-bit) 
10/100/1000BaseT Ethernet 00:30:6e:49:c6:f0
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0] 
eth2: dma_rwctrl[76ff1b0f] dma_mask[64-bit]

And now with 2.6.26-13:
eth2: Tigon3 [partno(A6825-60101) rev 0105 PHY(5701)] (PCI:33MHz:64-bit) 
10/100/1000Base-T Ethernet 00:30:6e:49:c6:f0
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[0]
eth2: dma_rwctrl[76ff1b0f] dma_mask[64-bit]

I can't find anything special in the logs or dmesg, afaict.

HTH

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: alpha

Kernel: Linux 2.6.18-6-alpha-generic
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-alpha-generic 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

linux-image-2.6.26-1-alpha-generic recommends no packages.

Versions of packages linux-image-2.6.26-1-alpha-generic suggests:
ii  aboot  1.0~pre20040408-3 Linux bootloader for the SRM conso
pn  fdutils(no description available)
pn  linux-doc-2.6.26   (no description available)

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


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it 

Processed: tagging 545112, bug 545112 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=10935

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 545112 - moreinfo
Bug #545112 [linux-2.6] Firewire stack gets into a state where it cannot send 
to some devices
Removed tag(s) moreinfo.
> forwarded 545112 https://bugzilla.kernel.org/show_bug.cgi?id=10935
Bug #545112 [linux-2.6] Firewire stack gets into a state where it cannot send 
to some devices
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=10935'.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052488918133.transcr...@bugs.debian.org

Bug#515514: marked as done (linux-image-2.6.26-1-amd64: combination of kernel amd64 and 6G memory by using a lvm in a software raid creates a kernel panic)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:23:30 +0100
with message-id <1270524210.24287.112.ca...@localhost>
and subject line Re: linux-image-2.6.26-1-amd64: combination of kernel amd64 
and 6G memory by using a lvm in a software raid creates a kernel panic
has caused the Debian Bug report #515514,
regarding linux-image-2.6.26-1-amd64: combination of kernel amd64 and 6G memory 
by using a lvm in a software raid creates a kernel panic
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.)


-- 
515514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-13
Severity: critical
Justification: breaks the whole system

by copying data from one software raid device into annother a kernel panic 
comes up

newstorage
2 harddiscs wdc 750 ayps combined with software raid 1
into software raid lvm pv and into this ext3 filesystems

old storage
2 harddisks samsung 400 software raid1 into it ext3 file system nolvm

copying data from old stroage to new storage failed

i removed 2G memory so that there will be only 4 in the system and mounted the 
old filesystem as ext2 
and everything works fine.


it is a productive system so i will not test it any more with more than 4 G 
memory




-- Package-specific info:
** Version:
Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 
4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 
2009

** Command line:
root=/dev/mapper/vgcamelot-lvmRoot ro quiet

** Tainted: P (1)

** Kernel log:
[   10.062847] raid1: raid set md0 active with 2 out of 2 mirrors
[   10.062847] md: md2 stopped.
[   10.127932] md: bind
[   10.127932] md: bind
[   10.136134] raid1: raid set md2 active with 2 out of 2 mirrors
[   10.136134] md: md1 stopped.
[   10.211307] md: bind
[   10.211502] md: bind
[   10.218256] raid1: raid set md1 active with 2 out of 2 mirrors
[   10.290730] device-mapper: uevent: version 1.0.3
[   10.290730] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: 
dm-de...@redhat.com
[   10.303601] hda: No disk in drive
[   10.315661] hdb: No disk in drive
[   10.447604] PM: Starting manual resume from disk
[   10.475138] kjournald starting.  Commit interval 5 seconds
[   10.475138] EXT3-fs: mounted filesystem with ordered data mode.
[   11.683110] udevd version 125 started
[   12.233076] input: Power Button (FF) as /class/input/input4
[   12.291446] ACPI: Power Button (FF) [PWRF]
[   12.291515] input: Power Button (CM) as /class/input/input5
[   12.360070] ACPI: Power Button (CM) [PWRB]
[   12.488651] Bluetooth: Core ver 2.11
[   12.504653] NET: Registered protocol family 31
[   12.504653] Bluetooth: HCI device and connection manager initialized
[   12.504653] Bluetooth: HCI socket layer initialized
[   12.520836] Bluetooth: HCI USB driver ver 2.9
[   12.520836] usbcore: registered new interface driver hci_usb
[   12.520836] i801_smbus :00:1f.3: enabling device (0001 -> 0003)
[   12.520836] ACPI: PCI Interrupt :00:1f.3[C] -> GSI 18 (level, low) -> 
IRQ 18
[   12.576835] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[   12.576835] iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, 
TCOBASE=0x0860)
[   12.576835] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   12.586320] input: PC Speaker as /class/input/input6
[   12.656887] ISDN subsystem Rev: 
1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2 loaded
[   12.725594] pnp: the driver 'parport_pc' has been registered
[   12.725594] parport_pc 00:0b: reported by Plug and Play ACPI
[   12.725594] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
[   12.740129] HiSax: Linux Driver for passive ISDN cards
[   12.740129] HiSax: Version 3.5 (module)
[   12.740129] HiSax: Layer1 Revision 2.46.2.5
[   12.740129] HiSax: Layer2 Revision 2.30.2.4
[   12.740129] HiSax: TeiMgr Revision 2.20.2.3
[   12.740129] HiSax: Layer3 Revision 2.22.2.3
[   12.740129] HiSax: LinkLayer Revision 2.59.2.4
[   12.772128] hisax_isac: ISAC-S/ISAC-SX ISDN driver v0.1.0
[   12.822139] parport_pc 00:0b: driver attached
[   12.835092] hisax_fcpcipnp: Fritz!Card PCI/PCIv2/PnP ISDN driver v0.0.1
[   12.835092] HiSax: Card 1 Protocol EDSS1 Id=fcpcipnp0 (0)
[   12.835092] HiSax: DSS1 Rev. 2.32.2.3
[   12.835092] HiSax: 2 channels added
[   12.835092] HiSax: MAX_WAITING_CALLS added
[   12.835092] ACPI: PCI Interrupt :05:02.0[A] -> GSI 23 (level, low) -> 
IRQ 23
[   12.835092] hisax_fcpcipnp: found adapter Fritz!Card PCI v2 at :05:02.0
[   12.867092] pnp: the dr

Bug#531425: marked as done (base: Loss of ethernet connectivity (bmac ethernet driver) after random amount of time)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:25:27 +0100
with message-id <1270524327.24287.115.ca...@localhost>
and subject line Re: base: Loss of ethernet connectivity (bmac ethernet driver) 
after random amount of time
has caused the Debian Bug report #531425,
regarding base: Loss of ethernet connectivity (bmac ethernet driver) after 
random amount of time
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.)


-- 
531425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: important


Running Debian on a PowerBook G3 'WallStreet'. Using the bmac ethernet driver. 
Experiencing loss of ethernet 
connectivity (100% packet loss) after a random amount of time. Have tried 
running bmac as both in-kernel and as a 
module. Running as a module seems to lengthen the delay before loss of 
connectivity occurs.

I am clueless as to how to diagnose this problem and would appreciate any help.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.29
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#547881: marked as done (cpufreq: Deadlock when switching governor to userspace)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:36:20 +0100
with message-id <1270524980.24287.124.ca...@localhost>
and subject line Re: cpufreq: Deadlock when switching governor to userspace
has caused the Debian Bug report #547881,
regarding cpufreq: Deadlock when switching governor to userspace
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.)


-- 
547881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---


Package: linux-image-2.6.30-1-686
Version: 2.6.30-6
Severity: important


 Hi,

 Sometimes system loses access to /sys/devices/system/cpu/cpu0/cpufreq/
 and as a result changing of CPU frequency is not possible.
 Simple 'cat' hangs forever:
  4979 ?D  0:00 cat 
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
 In principle other programs work normally but reboot (or shutdown)
 does not complete. System hangs and I use Alt-SysRq to force reboot
 (otherwise fsck reports wrong unmount).

 I checked that kernel 2.6.26 does not have such a problem for me.

-- Package-specific info:
** Version:
Linux version 2.6.30-1-686 (Debian 2.6.30-6) (wa...@debian.org) (gcc version 
4.3.4 (Debian 4.3.4-1) ) #1 SMP Sat Aug 15 19:11:58 UTC 2009

** Command line:
auto BOOT_IMAGE=Linux ro root=303

** Not tainted

** Kernel log:
[  600.544138]  [] ? __switch_to+0x101/0x140
[  600.544149]  [] ? schedule+0x5/0x13
[  600.544158]  [] ? rwsem_down_failed_common+0x6c/0x7f
[  600.544169]  [] ? rwsem_down_write_failed+0x18/0x1f
[  600.544179]  [] ? call_rwsem_down_write_failed+0x6/0x8
[  600.544188]  [] ? down_write+0x12/0x13
[  600.544199]  [] ? lock_policy_rwsem_write+0x30/0x57
[  600.544208]  [] ? do_dbs_timer+0x48/0x253
[  600.544217]  [] ? __schedule+0x6ec/0x746
[  600.544227]  [] ? worker_thread+0x13c/0x1bd
[  600.544235]  [] ? do_dbs_timer+0x0/0x253
[  600.544246]  [] ? autoremove_wake_function+0x0/0x2d
[  600.544255]  [] ? worker_thread+0x0/0x1bd
[  600.544263]  [] ? kthread+0x42/0x67
[  600.544271]  [] ? kthread+0x0/0x67
[  600.544281]  [] ? kernel_thread_helper+0x7/0x10
[  600.544318] INFO: task powernowd:3590 blocked for more than 120 seconds.
[  600.544323] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  600.544329] powernowd D c04951c0 0  3590   3589
[  600.544338]  c19ca1c0 0082 f704f90c c04951c0 c04951c0 f704f8e0 c3eaf6d0 
c3eaf6d0
[  600.544353]  c3eaf884  36c6c0fe 3a0bc3e4 0009 c0121eff 002f5a0a 

[  600.544368]  c3eaf884 c3eaf884 0046 f7051fb4 c19ca784 0001  
f73b9e04
[  600.544382] Call Trace:
[  600.544391]  [] ? try_to_wake_up+0x1e1/0x1eb
[  600.544401]  [] ? schedule+0x5/0x13
[  600.544409]  [] ? schedule_timeout+0x14/0xbd
[  600.544419]  [] ? __wake_up+0x29/0x39
[  600.544428]  [] ? wait_for_common+0xb8/0x112
[  600.544436]  [] ? default_wake_function+0x0/0x8
[  600.56]  [] ? __cancel_work_timer+0xf5/0x13d
[  600.544454]  [] ? wq_barrier_func+0x0/0x8
[  600.544464]  [] ? cpufreq_governor_dbs+0x1c5/0x230
[  600.544475]  [] ? __blocking_notifier_call_chain+0x3f/0x49
[  600.544485]  [] ? __cpufreq_governor+0x64/0x94
[  600.544494]  [] ? __cpufreq_set_policy+0xc2/0x107
[  600.544504]  [] ? store_scaling_governor+0x1a0/0x1c8
[  600.544513]  [] ? handle_update+0x0/0x8
[  600.544526]  [] ? test_skcipher+0xaa/0x5f7
[  600.544535]  [] ? store_scaling_governor+0x0/0x1c8
[  600.544543]  [] ? store+0x42/0x5a
[  600.544553]  [] ? sysfs_write_file+0xb0/0xdd
[  600.544561]  [] ? sysfs_write_file+0x0/0xdd
[  600.544572]  [] ? vfs_write+0x7e/0xd6
[  600.544580]  [] ? sys_write+0x3c/0x63
[  600.544590]  [] ? sysenter_do_call+0x12/0x28
[  720.544364] INFO: task kondemand/0:181 blocked for more than 120 seconds.
[  720.544374] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  720.544381] kondemand/0   D 5601 0   181  2
[  720.544392]  c19ca1c0 0046 f704e4bc 5601 c04951c0 c011cc90 0009 
f704e490
[  720.544408]  f704e644   394c6b1e 0009 0004 004c4b40 
c19ca1c0
[  720.544423]  c0108c11 f704e644 c3cb26d0 f704e6c8  c0101fb2 c19c7f00 
c19ca1f8
[  720.544438] Call Trace:
[  720.544456]  [] ? update_curr+0x58/0x178
[  720.544469]  [] ? __switch_to_xtra+0x14a/0x173
[  720.544479]  [] ? __switch_to+0x101/0x140
[  720.544490]  [] ? schedule+0x5/0x13
[  720.544500]  [] ? rwsem_down_failed_common+0x6c/0x7f
[  720.544510]  [] ? rwsem_down_write_failed+0x18/0x1f
[  720.544520]  [] ? call_rwsem_down_write_failed+0x6/0x8
[  720.544529]  [] ? down_write+0x12/0x13
[  720.544540]  [] ? lock_policy_rwsem_write+

Bug#551624: marked as done (linux-image-2.6.30: btusb: 0a5c:2101 Broadcom USB in 'lsusb', but not in 'hcitool dev', regression from 2.6.30-6)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:37:03 +0100
with message-id <1270525023.24287.125.ca...@localhost>
and subject line Re: linux-image-2.6.30: btusb: 0a5c:2101 Broadcom USB in 
'lsusb', but not in 'hcitool dev', regression from 2.6.30-6
has caused the Debian Bug report #551624,
regarding linux-image-2.6.30: btusb: 0a5c:2101 Broadcom USB in 'lsusb', but not 
in 'hcitool dev', regression from 2.6.30-6
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.)


-- 
551624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.30-2-686
Version: 2.6.30-8
Severity: important
File: linux-image-2.6.30


"0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth" unusable, but works in 
linux-image-2.6.30-1-686=2.6.30-6.

It is not listed in 'hcitool dev' and not available from 'hciconfig' etc, but 
listed in lsusb.


-- Package-specific info:
** Version:
Linux version 2.6.30-2-686 (Debian 2.6.30-8) (wa...@debian.org) (gcc version 
4.3.4 (Debian 4.3.4-3) ) #1 SMP Sat Sep 26 01:16:22 UTC 2009

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.30-2-686 root=/dev/mapper/wind-root ro console=tty7 
quiet

** Not tainted

** Kernel log:
[6.657228]  (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[6.657238]  (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[6.657247]  (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm)
[6.778023] HDA Intel :00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 
16
[6.778081] HDA Intel :00:1b.0: setting latency timer to 64
[6.864107] hda_codec: Unknown model for ALC883, trying auto-probe from 
BIOS...
[6.864350] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input10
[7.072509] cfg80211: Calling CRDA for country: US
[7.359737] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[7.463003] input: ImExPS/2 Generic Explorer Mouse as 
/devices/platform/i8042/serio1/input/input11
[7.486988] phy0: Selected rate control algorithm 'minstrel'
[7.489013] Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
[7.781485] usb-storage: device scan complete
[7.783465] scsi 4:0:0:0: Direct-Access Generic- Multi-Card   1.00 
PQ: 0 ANSI: 0 CCS
[7.787881] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[9.181581] Adding 2097144k swap on /dev/mapper/wind-swap_1.  Priority:-1 
extents:1 across:2097144k 
[9.593021] EXT3 FS on dm-0, internal journal
[   11.258225] kjournald starting.  Commit interval 5 seconds
[   11.258556] EXT3 FS on sda1, internal journal
[   11.258573] EXT3-fs: mounted filesystem with ordered data mode.
[   11.292800] kjournald starting.  Commit interval 5 seconds
[   11.293211] EXT3 FS on dm-4, internal journal
[   11.293228] EXT3-fs: mounted filesystem with ordered data mode.
[   14.161661] r8169: eth0: link up
[   14.161682] r8169: eth0: link up
[   14.448310] r8169: eth0: link up
[   15.396139] Clocksource tsc unstable (delta = -71291356 ns)
[   25.212127] eth0: no IPv6 routers present
[   27.860816] usb 1-1.3: new high speed USB device using ehci_hcd and address 7
[   27.969261] usb 1-1.3: New USB device found, idVendor=05ac, idProduct=1301
[   27.969278] usb 1-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[   27.969290] usb 1-1.3: Product: iPod
[   27.969299] usb 1-1.3: Manufacturer: Apple
[   27.969308] usb 1-1.3: SerialNumber: 000A270011EC00A4
[   27.969628] usb 1-1.3: configuration #1 chosen from 2 choices
[   27.971304] scsi5 : SCSI emulation for USB Mass Storage devices
[   27.972578] usb-storage: device found at 7
[   27.972591] usb-storage: waiting for device to settle before scanning
[   32.972429] usb-storage: device scan complete
[   32.973111] scsi 5:0:0:0: Direct-Access AppleiPod 2.70 
PQ: 0 ANSI: 2
[   32.976185] sd 5:0:0:0: [sdc] 495616 2048-byte hardware sectors: (1.01 
GB/968 MiB)
[   32.976790] sd 5:0:0:0: [sdc] Write Protect is off
[   32.976812] sd 5:0:0:0: [sdc] Mode Sense: 64 00 00 08
[   32.976826] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[   32.979832] sd 5:0:0:0: [sdc] 495616 2048-byte hardware sectors: (1.01 
GB/968 MiB)
[   32.980427] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[   32.981617]  sdc:
[   32.991162] sd 5:0:0:0: [sdc] Attached SCSI removable disk
[   36.368578] Bluetooth: Core ver 2.15
[   36.368788] NET: Registered protocol family 31
[   36.368801] Bluetooth: HCI device and connection manager initialized
[   36.368815] Bluetooth: HCI socket layer initialized
[   36.391438] Blu

Processed: tagging 538158

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 538158 - moreinfo
Bug #538158 [linux-image-2.6.26-2-686-bigmem] BUG: soft lockup - CPU#5 stuck 
for 62s with 2.6.26-2-686-bigmem kernel
Removed tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052438415941.transcr...@bugs.debian.org

Bug#545112: dvgrab: does not work properly with Juju firewire stack

[Ben Hutchings]

I was just going through the list of kernel bugs, closing those with
longstanding requests for more information, and then I saw:

On Mon, 2010-01-11 at 16:36 +0100, Stefan Richter wrote:
> Ben,

Oops.  Not sure why I missed this.

> which one of your two controllers was initially affected?  ALi M5253 or
> Ricoh R5C832 or both?  Is the fact that you cannot reproduce the issue
> anymore true for both controllers?

I normally use the ALi M5253.

> If you happen to be able to reproduce the issue again on current
> kernels, please provide the dmesg from a failing session with debug
> logging switched on:
> # modprobe -r firewire-ohci
> # modprobe firewire-ohci debug=-1
> Then plug the camcorder in and start to capture.  Beware, the resulting
> log may be massive since it includes interrupts at 8 kHz frequency.
> 
> Note, there is an upstream bug with ALi controllers:  It does not work
> at all with firewire-ohci for several people, as it does not survive the
> second bus reset.  http://bugzilla.kernel.org/show_bug.cgi?id=10935

Well that is rather interesting.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#512339: marked as done (linux-image-2.6-amd64: Mplayer crash causes BUG: unable to handle kernel, NULL pointer dereference at 0000000000000000)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:23:02 +0100
with message-id <1270524182.24287.111.ca...@localhost>
and subject line Re: linux-image-2.6-amd64: Mplayer crash causes BUG: unable to 
handle kernel, NULL pointer dereference at 
has caused the Debian Bug report #512339,
regarding linux-image-2.6-amd64: Mplayer crash causes BUG: unable to handle 
kernel, NULL pointer dereference at 
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.)


-- 
512339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-2.6-amd64
Version: 2.6.26+17
Severity: important

An mplayer crash when playing specific files will trigger the kernel 
error message that will be described. From that moment on, a range of 
crashed/freezed processes can

be killed no more. Example of such unkillable processes:
29866 ?00:00:00 kaffeine
4005 ?00:00:00 gmplayer
4309 ?00:00:00 mplayer
2491 ?00:02:57 amarokapp 
4327 ?00:00:03 vlc 
I mark this as important as processes like Kaffeine and Amarok can no 
longer be started until a computer restart.

A file that makes MPlayer crash like that:
http://ruina.tam.cornell.edu/research/topics/bicycle_mechanics/JBike6_web_folder/JBike6_self_stable_files/bicycle_stability.mov
Playing this file will make other players crash, but not affecting the 
kernel like that.


The kernel message:
[45957.803729] BUG: unable to handle kernel NULL pointer dereference at 

[45957.803729] IP: [] 
:snd_hda_intel:get_alloc_hash+0x4f/0x71

[45957.803729] PGD b794f067 PUD b50ec067 PMD 0
[45957.803729] Oops: 0002 [1] SMP
[45957.803729] CPU 1
[45957.803729] Modules linked in: tcp_diag inet_diag rfcomm l2cap 
bluetooth autofs4 ipv6 acpi_cpufreq cpufreq_powersave cpufreq_stats 
cpufreq_userspace cpufreq_ondemand
cpufreq_conservative freq_table ext3 jbd mbcache fuse dm_snapshot 
dm_mirror dm_log dm_mod sbp2 loop arc4 ecb crypto_blkcipher iwl3945 
uvcvideo firmware_class mac80211
compat_ioctl32 videodev pcspkr psmouse v4l1_compat serio_raw iTCO_wdt 
cfg80211 video output snd_hda_intel snd_pcm_oss snd_mixer_oss battery 
asus_laptop snd_pcm ac
led_class joydev snd_timer snd_page_alloc snd_hwdep button snd intel_agp 
soundcore evdev reiserfs ide_cd_mod cdrom piix sd_mod ide_pci_generic 
ide_core usbhid hid
ff_memless ricoh_mmc sdhci mmc_core ohci1394 ieee1394 ata_generic ahci 
libata scsi_mod dock sky2 ehci_hcd uhci_hcd thermal processor fan 
thermal_sys

[45957.803729] Pid: 22606, comm: gmplayer Not tainted 2.6.26-1-amd64 #1
[45957.803729] RIP: 0010:[]  [] 
:snd_hda_intel:get_alloc_hash+0x4f/0x71

[45957.803729] RSP: 0018:810094893cd8  EFLAGS: 00210246
[45957.803729] RAX:  RBX:  RCX: 

[45957.803729] RDX: 0009 RSI:  RDI: 
00400010
[45957.803729] RBP: 8100be0458d0 R08:  R09: 

[45957.803729] R10:  R11: 802f2139 R12: 
0009
[45957.803729] R13: 0009 R14: 0001 R15: 
00030009
[45957.803729] FS:  7ff2a0521720() GS:8100bf69b9c0() 
knlGS:

[45957.803729] CS:  0010 DS:  ES:  CR0: 80050033
[45957.803729] CR2:  CR3: 6095c000 CR4: 
06a0
[45957.803729] DR0:  DR1:  DR2: 

[45957.803729] DR3:  DR6: 0ff0 DR7: 
0400
[45957.803729] Process gmplayer (pid: 22606, threadinfo 
810094892000, task 8100b50bd020)
[45957.803729] Stack:  0019  
0009 
[45957.803729]  8100be045800 a020999b 8100b4849000 
8100b4849050
[45957.803729]   0002  
a0209b06

[45957.803729] Call Trace:
[45957.803729]  [] ? 
:snd_hda_intel:snd_hda_codec_amp_read+0x34/0x62
[45957.803729]  [] ? 
:snd_hda_intel:snd_hda_mixer_amp_switch_get+0x8d/0xa9

[45957.803729]  [] ? :snd:snd_ctl_elem_read+0x81/0x97
[45957.803729]  [] ? :snd:snd_ctl_ioctl+0x315/0x745
[45957.803729]  [] ? vfs_ioctl+0x21/0x6b
[45957.803729]  [] ? do_vfs_ioctl+0x248/0x261
[45957.803729]  [] ? sys_ioctl+0x51/0x70
[45957.803729]  [] ? system_call_after_swapgs+0x8a/0x8f
[45957.803729]
[45957.803729]
[45957.803729] Code: 00 eb 10 0f b7 c3 48 8d 0c c2 44 39 21 74 33 66 8b 
59 06 66 83 fb ff 75 ea 48 8d bd 80 00 00 00 e8 2c ff ff ff 49 63 d5 48 
89 c1 <44> 89 20 66 c7

40 04 00 

Bug#522110: marked as done (BUG: soft lockup - CPU#3 stuck for 61s! (AMD Phenom 9600 Quad-Core))

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:25:02 +0100
with message-id <1270524302.24287.114.ca...@localhost>
and subject line Re: BUG: soft lockup - CPU#3 stuck for 61s! (AMD Phenom 9600 
Quad-Core)
has caused the Debian Bug report #522110,
regarding BUG: soft lockup - CPU#3 stuck for 61s! (AMD Phenom  9600 Quad-Core)
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.)


-- 
522110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.28
Version: 2.6.28-10.00.Custom
Severity: important

I'm having sporadic problems with a runaway processor core on an AMD
Phenom 9600 Quad-Core system. The system, which runs Lenny, will
sometimes stay up for almost a week and other times has to be rebooted
serveral times in one day.

When the system locks up, the load on processor core 4 (cpu#3) slowly
climbs to 100% and everything running on that core freezes.

The kernel usually responds to the Magic SysRq keys.

This package was locally compiled on a Lenny system using the source
package from Sid.

Here's a typical syslog extract:

Mar 31 14:19:54 stasis kernel: [11166.917503] BUG: soft lockup - CPU#3
  stuck for 61s! [events/3:18]
Mar 31 14:19:54 stasis kernel: [11166.917507] Modules linked in:
  tcp_diag inet_diag ppdev parport_pc lp parport autofs4 ipv6 nfsd
  exportfs nfs lockd nfs_acl fuse dm_snapshot dm_mirror dm_region_hash
  dm_log dm_mod rpcsec_gss_krb5 auth_rpcgss sunrpc it87 hwmon_vid eeprom
  loop sg snd_usb_audio snd_usb_lib snd_hwdep snd_seq_dummy snd_hda_intel
  snd_seq_oss snd_pcm_oss snd_mixer_oss snd_seq_midi psmouse snd_rawmidi
  pcspkr serio_raw snd_seq_midi_event snd_pcm snd_seq i2c_piix4
  snd_page_alloc i2c_core snd_timer snd_seq_device snd pwc evdev
  compat_ioctl32 soundcore usblp videodev v4l1_compat wmi button ext3 jbd
  mbcache raid10 raid1 md_mod usb_storage usbhid hid atiixp sd_mod
  crc_t10dif ide_pci_generic ide_core floppy aic7xxx scsi_transport_spi
  ata_generic ahci ohci_hcd ehci_hcd libata scsi_mod atl1 mii thermal
  processor fan thermal_sys
Mar 31 14:19:54 stasis kernel: [11166.917511] CPU 3:
Mar 31 14:19:54 stasis kernel: [11166.917511] Modules linked in:
  tcp_diag inet_diag ppdev parport_pc lp parport autofs4 ipv6 nfsd
  exportfs nfs lockd nfs_acl fuse dm_snapshot dm_mirror dm_region_hash
  dm_log dm_mod rpcsec_gss_krb5 auth_rpcgss sunrpc it87 hwmon_vid eeprom
  loop sg snd_usb_audio snd_usb_lib snd_hwdep snd_seq_dummy snd_hda_intel
  snd_seq_oss snd_pcm_oss snd_mixer_oss snd_seq_midi psmouse snd_rawmidi
  pcspkr serio_raw snd_seq_midi_event snd_pcm snd_seq i2c_piix4
  snd_page_alloc i2c_core snd_timer snd_seq_device snd pwc evdev
  compat_ioctl32 soundcore usblp videodev v4l1_compat wmi button ext3 jbd
  mbcache raid10 raid1 md_mod usb_storage usbhid hid atiixp sd_mod
  crc_t10dif ide_pci_generic ide_core floppy aic7xxx scsi_transport_spi
  ata_generic ahci ohci_hcd ehci_hcd libata scsi_mod atl1 mii thermal
  processor fan thermal_sys
Mar 31 14:19:54 stasis kernel: [11166.917511] Pid: 18, comm: events/3
  Not tainted 2.6.28 #1
Mar 31 14:19:54 stasis kernel: [11166.917511] RIP:
  0010:[]  []
smp_call_function_mask+0x19c/0x226
  Mar 31 14:19:54 stasis kernel: [11166.917511] RSP: 0018:88012ed9bc40
EFLAGS: 0202
Mar 31 14:19:54 stasis kernel: [11166.917511] RAX: 08fc RBX:
  0003 RCX: 
Mar 31 14:19:54 stasis kernel: [11166.917511] RDX: 08fc RSI:
  88012ed9bb90 RDI: 0246
Mar 31 14:19:54 stasis kernel: [11166.917511] RBP: 0003 R08:
  0008 R09: 0200
Mar 31 14:19:54 stasis kernel: [11166.917511] R10: 0008 R11:
  80221011 R12: 0014
Mar 31 14:19:54 stasis kernel: [11166.917511] R13: 80220678 R14:
  0003 R15: 88012c0eb5c0
Mar 31 14:19:54 stasis kernel: [11166.917511] FS:
  7faa85df96e0() GS:88012ed3bdc0() knlGS:f7910b90
Mar 31 14:19:54 stasis kernel: [11166.917511] CS:  0010 DS: 0018 ES:
  0018 CR0: 8005003b
Mar 31 14:19:54 stasis kernel: [11166.917511] CR2: 7f8beb322650 CR3:
  00201000 CR4: 06e0
Mar 31 14:19:54 stasis kernel: [11166.917511] DR0:  DR1:
   DR2: 
Mar 31 14:19:54 stasis kernel: [11166.917511] DR3:  DR6:
  0ff0 DR7: 0400
Mar 31 14:19:54 stasis kernel: [11166.917511] Call Trace:
Mar 31 14:19:54 stasis kernel: [11166.917511]  [] ?
  update_curr+0x4d/0x112
Mar 31 14:19:54 stasis kernel: [11166.9

Bug#542772: marked as done (hal: HAL deamon locks computer on boot, needs powercycling to recover)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 04:28:50 +0100
with message-id <1270524530.24287.118.ca...@localhost>
and subject line Re: hal: HAL deamon locks computer on boot, needs powercycling 
to recover
has caused the Debian Bug report #542772,
regarding hal: HAL deamon locks computer on boot, needs powercycling to recover
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.)


-- 
542772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hal
Version: 0.5.12~git20090406.46dc48-2
Severity: grave
Justification: renders package unusable


When init.d starts hald the computer stops dead and cannot
be booted. A power cycle is required to restart the machine.
It is only possible to use the computer with hald disabled.

The problem has happened on the 2.6.26 and 2.6.30 kernels.
When running the 2.6.18 kernel I can start hald, though it
does take an age to start.

This is only happening on an old Dell Inspiron 3500 notebook,
my more modern systems seem perfectly happy.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages hal depends on:
ii  acl  2.2.47-3Access control list utilities
ii  adduser  3.110   add and remove users and groups
ii  consolekit   0.3.0-3 framework for defining and trackin
ii  dbus 1.2.16-2simple interprocess messaging syst
ii  hal-info 20090716-1  Hardware Abstraction Layer - fdi f
ii  libc62.9-23  GNU C Library: Shared libraries
ii  libdbus-1-3  1.2.16-2simple interprocess messaging syst
ii  libdbus-glib 0.82-1  simple interprocess messaging syst
ii  libexpat12.0.1-4 XML parsing C library - runtime li
ii  libgcc1  1:4.4.1-1   GCC support library
ii  libglib2.0-0 2.20.4-1The GLib library of C routines
ii  libhal-stora 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share
ii  libhal1  0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share
ii  libpolkit2   0.9-4   library for accessing PolicyKit
ii  libsmbios2   2.0.3.dfsg-1Provide access to (SM)BIOS informa
ii  libstdc++6   4.4.1-1 The GNU Standard C++ Library v3
ii  libusb-0.1-4 2:0.1.12-13 userspace USB programming library
ii  libvolume-id 0.141-1 libvolume_id shared library
ii  lsb-base 3.2-23  Linux Standard Base 3.2 init scrip
ii  mount2.15.1~rc1-1Tools for mounting and manipulatin
ii  pciutils 1:3.1.3-2   Linux PCI Utilities
ii  pm-utils 1.2.5-4 utilities and scripts for power ma
ii  policykit0.9-4   framework for managing administrat
ii  udev 0.141-1 /dev/ and hotplug management daemo
ii  usbutils 0.84-1  Linux USB utilities

Versions of packages hal recommends:
ii  eject   2.1.5+deb1+cvs20081104-6 ejects CDs and operates CD-Changer
ii  libsmbios-bin   2.0.3.dfsg-1 Provide access to (SM)BIOS informa

Versions of packages hal suggests:
pn  gnome-device-manager   (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Closing due to lack of response.

This may have been fixed by the replacement of many old IDE drivers in
version 2.6.32-10.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: tagging 502845

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 502845 upstream
Bug #502845 [linux-2.6] open-iscsi: no login using amd64
Added tag(s) upstream.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052385313167.transcr...@bugs.debian.org

Processed: tagging 404951, owner 404951

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 404951 - moreinfo
Bug #404951 [linux-2.6] linux-2.6: sb1-bcm91250a kernel does not boot
Bug #466977 [linux-2.6] 2.6.24-1-sb1-bcm91250a mipsel hangs running init
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> owner 404951 aurel...@aurel32.net
Bug #404951 [linux-2.6] linux-2.6: sb1-bcm91250a kernel does not boot
Bug #466977 [linux-2.6] 2.6.24-1-sb1-bcm91250a mipsel hangs running init
Owner recorded as aurel...@aurel32.net.
Owner recorded as aurel...@aurel32.net.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127052341711062.transcr...@bugs.debian.org

Bug#576274: additional info

[maximilian attems]

On Mon, 05 Apr 2010, bugrep...@public-files.de wrote:

> I don't have hotkey-setup installed 

good.
 
> output of lscpi -vvv attached
> 
> Thanks for caring so much. I am still not entirely convinced that this
> is a genuine bug (which is why I waited so long reporting it), because
> the graphics chip in use (and the rest of the hardware) is so
> widespread, that I can't be the only Debian user experiencing this.
> 
> Malte

hmmm,
could you check against 2.6.32-11 should land next days in unstable?

also there is 2.6.33 in experimental, don't think it should make
a difference but better check.

thanks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406023652.gd7...@stro.at

Bug#501359: initramfs-tools: MODULES=dep does not like Xen virtual block devices

[maximilian attems]

tags 501359 moreinfo
stop

On Wed, 18 Feb 2009, Ian Campbell wrote:

> On Wed, 2009-02-18 at 01:01 +0100, maximilian attems wrote:
> > well also according to the /sys tree you posted [1] this seems
> > to be an error of xen-blkfront declaring itself as vbd module
> > in sys?
> 
> Could be, I don't really know how this sysfs stuff is supposed to work.
> 
> The module has several aliases:
> alias:  xenblk
> alias:  xen:vbd
> alias:  block-major-202-*
> but not just plain vbd. (Similarly xen-netfront has xen:vif etc but not
> plain vif). I guess it is the name of the entry
> under /sys/bus/xen/drivers which matters?
> 
> Weirdly under /sys/module/xen_fbfront/drivers/ there is xen:vbd
> -> .../bus/drivers/vbd, I'm not sure where that name comes from, it's
> not even the first alias.
> 
> (FYI I'm about to leave for a weeks travel, I'll hopefully be on email
> but not sure how often).

sorry for late reponse, 0.94 changed a bit the way sysfs is walked.
could you please check against it if MODULES=dep is fixed?

thanks

-- 
maks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406022332.gc7...@stro.at

Re: Working around bogus HPAs in libata

[Tejun Heo]

Hello,

On 04/06/2010 11:28 AM, Ben Hutchings wrote:
> If a system vendor puts its own name or model numbers on the disks it
> ships then I think the BIOS or other platform firmware can reasonably
> assume that it 'owns' and can write to the HPA on a disk with the
> vendor's identification.  (I wouldn't be at all surprised to find that
> some vendors take shortcuts though.)

I would be very surprised if no vendor took shortcuts.  :-)

>> Ah... I see, but let's fix that up too.  It could be worse to have
>> half working workaround than not working around at all.  I'll update
>> the patch once the currently pending HPA updates are in.
> 
> Oh, what are those?

The patch I posted is rolled up version which contained currently
pending HPA unlock on shrink patch.

  http://article.gmane.org/gmane.linux.ide/45662

> I want to apply some version of this fix in Debian soon so we can
> complete the transition to libata.  I would very much appreciate it if
> you could answer whether or not the multiple 'capacity change' messages
> may indicate a problem.

Multiple messages are probably sd doing revalidation of the device.  I
don't think it will cause any problem but I'll look into it later
today and let you know.

Thanks.

-- 
tejun


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bba9d83.2040...@kernel.org

Processed: Re: Bug#501359: initramfs-tools: MODULES=dep does not like Xen virtual block devices

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 501359 moreinfo
Bug #501359 [initramfs-tools] initramfs-tools: MODULES=dep does not like Xen 
virtual block devices
Ignoring request to alter tags of bug #501359 to the same tags previously set
> stop
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
Archive: 
http://lists.debian.org/handler.s.c.127052065822278.transcr...@bugs.debian.org

Bug#548148: initramfs-tools: add verbose debug output to run_scripts function

[maximilian attems]

tags 548148 moreinfo
stop

On Thu, 24 Sep 2009, Marc Haber wrote:
> 
> please consider adding the following obvious patch to
> initramfs-tools/scripts/functions:

sorry for the late reply, but had a pile to review and
0.94 is out now, so.
 
> --- functions.orig  2009-09-24 10:42:11.0 +0200
> +++ functions   2009-09-24 10:42:13.0 +0200
> @@ -207,6 +207,9 @@
> [ ! -d ${initdir} ] && return
> get_prereqs
> reduce_prereqs
> +   if [ "${verbose}" = "y" ]; then
> +   echo "Hook $initdir run list: $runlist"
> +   fi
> call_scripts
>  }
> 
> Unfortunately, this is untested since I couldn't figure out to
> actually have the verbose variable set. Giving "verbose" on the kernel
> command line doesn't seem to do it.

hmmm don't get what you want to debug here?

yes this sorting algo is very strange, but verbose output is
easily gained by passing -v to mkinitramfs or update-initramfs

 
> Greetings
> Marc

thanks for the patience.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406015209.gb7...@stro.at

Re: Working around bogus HPAs in libata

[Ben Hutchings]

On Tue, 2010-04-06 at 11:01 +0900, Tejun Heo wrote:
> Hello,
> 
> On 04/03/2010 06:57 AM, Ben Hutchings wrote:
> > Several distributions have turned on the switch by default.  As I said
> > previously, this turned out to be a bad idea.
> 
> Heh, yeah, I did that on openSUSE which was mandatory for backward
> compatibility because ide unlocked HPA by default (at least on
> openSUSE).  Do you know how common are these problem cases w/ default
> HPA unlocking?

No idea, but they look serious enough to worry about.

> Diddling with HPAs and writing stuff to disks from
> BIOS is generally a very bad idea because it means that switching BIOS
> options or attaching a hard drive to a different motherboard can lead
> to data corruption.

If a system vendor puts its own name or model numbers on the disks it
ships then I think the BIOS or other platform firmware can reasonably
assume that it 'owns' and can write to the HPA on a disk with the
vendor's identification.  (I wouldn't be at all surprised to find that
some vendors take shortcuts though.)

[...]
> > My test case also revealed a bug in the partition scanning retry:
> > partition 2 is an extended partition and wholly within the HPA, so the
> > extended partition table is not accessible until the HPA is disabled.
> > But it is not rescanned after the HPA is disabled.  However, this is is
> > consistent between IDE and libata drivers and will not be a regression
> > when making the transition.
> 
> Ah... I see, but let's fix that up too.  It could be worse to have
> half working workaround than not working around at all.  I'll update
> the patch once the currently pending HPA updates are in.

Oh, what are those?

I want to apply some version of this fix in Debian soon so we can
complete the transition to libata.  I would very much appreciate it if
you could answer whether or not the multiple 'capacity change' messages
may indicate a problem.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#548148: initramfs-tools: add verbose debug output to run_scripts function

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 548148 moreinfo
Bug #548148 [initramfs-tools] initramfs-tools: add verbose debug output to 
run_scripts function
Added tag(s) moreinfo.
> stop
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
Archive: 
http://lists.debian.org/handler.s.c.127051878914102.transcr...@bugs.debian.org

Re: Working around bogus HPAs in libata

[Tejun Heo]

Hello,

On 04/03/2010 06:57 AM, Ben Hutchings wrote:
> Several distributions have turned on the switch by default.  As I said
> previously, this turned out to be a bad idea.

Heh, yeah, I did that on openSUSE which was mandatory for backward
compatibility because ide unlocked HPA by default (at least on
openSUSE).  Do you know how common are these problem cases w/ default
HPA unlocking?  Diddling with HPAs and writing stuff to disks from
BIOS is generally a very bad idea because it means that switching BIOS
options or attaching a hard drive to a different motherboard can lead
to data corruption.

>> Does the following patch work as expected?
...
> So, this looks good, but I'm slightly disturbed by the multiple
> 'capacity change' messages when using libata.

I'll see where those multiple messages are coming from.

> Also, the warnings in ata_dev_revalidate() should not be shown when
> we are deliberately changing capacity.

Given that this is an ugly situation, I don't think it's a bad idea to
emit ugly messages.

> My test case also revealed a bug in the partition scanning retry:
> partition 2 is an extended partition and wholly within the HPA, so the
> extended partition table is not accessible until the HPA is disabled.
> But it is not rescanned after the HPA is disabled.  However, this is is
> consistent between IDE and libata drivers and will not be a regression
> when making the transition.

Ah... I see, but let's fix that up too.  It could be worse to have
half working workaround than not working around at all.  I'll update
the patch once the currently pending HPA updates are in.

Thanks.

-- 
tejun


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bba95f8.7070...@kernel.org

Bug#547365: fixed in initramfs-tools 0.94

[maximilian attems]

On Mon, 05 Apr 2010, Jonathan Nieder wrote:

> Debian Bug Tracking System wrote:
> 
> > #547365: "initramfs-tools -d -k foo" is not idempotent
> > 
> > It has been closed by maximilian attems .
> 
> Thanks.

sorry for the taken time, will try to be more on spot. ;)
 
> >  initramfs-tools (0.94) unstable; urgency=low
> >  .
> >* The "Litte Bang" release
> 
> Wow.  You can say that again.
> 
> >[ Bert Schulze ]
> >* initramfs-tools: support different compression tools in mkinitramfs.
> >  (closes: #533903)
> >* mkinitramfs: -c compression support / commandline override.
> >  (closes: #576429)
> 
> I was thinking of doing that, glad to see it got done already.

yep it is a cool feature.

there is still lots of work:
* excluding hooks list for admin
* better seperation for generation for remote boxes
 
> Looking forward to the next boot, :)
> Jonathan

thanks for your message!


-- 
maks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406012018.ga7...@stro.at

Bug#576601: closed by Ben Hutchings (Re: Bug#576601: linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script)

[Ben Hutchings]

On Mon, 2010-04-05 at 21:31 -0300, Tom Cerul wrote:
> Am trying to upgrade to lenny as per instructions on debian.org.
> 
> http://www.debian.org/releases/lenny/i386/release-notes/ch-about.en.html
> instructs "Please note that we only support and document upgrading
> from the previous release of Debian (in this case, the upgrade from
> 4.0). If you need to upgrade from older releases, we suggest you read
> previous editions of the release notes and upgrade to 4.0 first."

So you're upgrading from sarge, to etch, to lenny?  This generally
should work but since you've left it so late to upgrade most people will
have forgotten about the 'gotchas' and you won't get a lot of support
with the upgrade.

Any preinst script will be installed as
/var/lib/dpkg/info/.preinst.  However, the official kernel
packages for etch didn't use preinst scripts.  Are you sure the error
was in installation of linux-image-2.6.18-6-686 and not one of its
dependencies?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Processed: block 576603 with 576488

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 576603 with 576488
Bug #576603 [initramfs-tools] stay in sid to settle dust
Was not blocked by any bugs.
Added blocking bug(s) of 576603: 576488
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.1270517142965.transcr...@bugs.debian.org

Bug#576601: closed by Ben Hutchings (Re: Bug#576601: linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script)

[Tom Cerul]

Am trying to upgrade to lenny as per instructions on debian.org.

http://www.debian.org/releases/lenny/i386/release-notes/ch-about.en.html
instructs "Please note that we only support and document upgrading
from the previous release of Debian (in this case, the upgrade from
4.0). If you need to upgrade from older releases, we suggest you read
previous editions of the release notes and upgrade to 4.0 first."



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/s2g6d94ef7c1004051731r618640e9l656ff8675f3d4...@mail.gmail.com

Bug#576608: linux-base: "Invalid output format udev" during configuration

[Ben Hutchings]

On Mon, 2010-04-05 at 14:09 -0700, Ben Pfaff wrote:
> Package: linux-base
> Version: 2.6.32-10
> 
> During an upgrade that prompted me to replace device names by
> UUIDs in /etc/fstab, a few error messages were printed on the
> console:
> 
> Setting up linux-base (2.6.32-10) ...
> Invalid output format udev. Choose from value,
> device, list, or full
> Invalid output format udev. Choose from value,
> device, list, or full
> Invalid output format udev. Choose from value,
> device, list, or full
> Searching for GRUB installation directory ... found: /boot/grub
> Searching for default file ... found: /boot/grub/default
> Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-2.6.32-trunk-686
> Found kernel: /boot/vmlinuz-2.6.32-4-686
> Found kernel: /boot/vmlinuz-2.6.28-1-686
> Found kernel: /boot/vmlinuz-2.6.26-1-686
> Found kernel: /boot/vmlinuz-2.6.24-1-686
> Found kernel: /boot/vmlinuz-2.6.22-1-686
> Found kernel: /boot/vmlinuz-2.6.18-4-686
> Found kernel: /boot/vmlinuz-2.6.18-3-686
> Found kernel: /boot/vmlinuz-2.6.18-1-686
> Found kernel: /boot/vmlinuz-2.6.17-2-686
> Updating /boot/grub/menu.lst ... done
> 
> The upgrade did seem to complete smoothly but the error messages
> still seem a bit worrisome.

The upgrade script calls 'blkid' (part of the util-linux package) to get
information about the existing device labels and UUIDs.  This command
supports several different output formats but the 'udev' format works
best for us.  It looks like we need to depend on a recent version of
util-linux.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#522726: marked as done (kernel problem after a simple 'rm' command: RESERVE_SPACE(805) failed in function encode_lookup)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 01:04:41 +0100
with message-id <1270512281.24287.68.ca...@localhost>
and subject line Re: kernel problem after a simple 'rm' command: 
RESERVE_SPACE(805)  failed in function encode_lookup
has caused the Debian Bug report #522726,
regarding kernel problem after a simple 'rm' command: RESERVE_SPACE(805) failed 
 in function encode_lookup
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.)


-- 
522726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.0.10-6+etch.1
Severity: important

My very stable server crashed as a result of a 'rm' command in an
NFS-mounted home directory. The 'rm' command was a file name (with
newlines) but that file did not exist.

The NFS client and the NFS server were the same machine.

Surprisingly, this cause a big problem inside the Kernel - the stack
trace shows a large amount of NFS system calls.

Here is what I did and what I got in response:
alevc...@biocluster:~/.html/cellwall$ rm
'source_fasta_tair-v20080412-seq---_downloaded-2009-04-04
> source_fasta_tair-v20080412-pep---_downloaded-2009-04-04
> source_fasta_tair-v20080412-cds---_downloaded-2009-04-04
> source_fasta_tair-v20080412-cdna--_downloaded-2009-04-04
> source_fasta_tair-v20080229-igenic_downloaded-2009-04-04
> source_fasta_tair-v20080228-intron_downloaded-2009-04-04
> source_fasta_tigr-v6-0-all-seq_downloaded-2009-04-04
> source_fasta_tigr-v6-0-all-pep_downloaded-2009-04-04
> source_fasta_jgi-poptr-v1-1_prot--_downloaded-2009-04-04
> source_fasta_jgi-phypa-v1-1_trans-_downloaded-2009-04-04
> source_fasta_jgi-phypa-v1-1_prot--_downloaded-2009-04-04
> source_fasta_uniprot-v14-9-_tremb-_downloaded-2009-04-04
> source_fasta_uniprot-v14-9-_sprot-_downloaded-2009-04-04
> source_fasta_jgi-poptr-v1-1_trans-_downloaded-2009-04-04'
Segmentation fault

Message from sysl...@biocluster at Sat Apr  4 23:06:56 2009 ...
biocluster kernel: [ cut here ]

Message from sysl...@biocluster at Sat Apr  4 23:06:56 2009 ...
biocluster kernel: invalid opcode:  [1] SMP

Message from sysl...@biocluster at Sat Apr  4 23:06:56 2009 ...
biocluster kernel: invalid opcode:  [1] SMP

Message from sysl...@biocluster at Sat Apr  4 23:06:56 2009 ...
biocluster kernel: [ cut here ]


Here is what /var/log/messages showed immediately after:

Apr  4 22:39:40 biocluster -- MARK --
Apr  4 22:59:40 biocluster -- MARK --
Apr  4 23:06:56 biocluster kernel: RESERVE_SPACE(805) failed in
function encode_lookup
Apr  4 23:06:56 biocluster kernel: CPU 15
Apr  4 23:06:56 biocluster kernel: Modules linked in: tcp_diag
inet_diag nfsd exportfs button ac battery autofs4 ib_ipoib ipv6 nfs
lockd nfs_acl sunrpc quota_v1 ext2 ext3 jbd mbcache dm_snapshot
dm_mirror dm_mod qla2xxx mppVhba mppUpper sg rdma_ucm rdma_cm ib_cm
iw_cm ib_sa ib_addr ib_umad ib_ipath ib_uverbs mlx4_ib ib_mad ib_core
loop psmouse serio_raw i2c_i801 i2c_core shpchp pci_hotplug pcspkr
mlx4_core igb evdev xfs ide_cd cdrom ata_generic sd_mod ata_piix
libata piix generic ide_core ehci_hcd uhci_hcd firmware_class
scsi_transport_fc mptsas mptscsih mptbase e1000 scsi_transport_sas
scsi_mod thermal processor fan
Apr  4 23:06:56 biocluster kernel: Pid: 12459, comm: rm Not tainted
2.6.22-3-amd64 #1
Apr  4 23:06:56 biocluster kernel: RIP: 0010:[]
[] :nfs:encode_lookup+0x34/0x5c
Apr  4 23:06:56 biocluster kernel: RSP: 0018:81053e8b38d8  EFLAGS: 00010292
Apr  4 23:06:56 biocluster kernel: RAX: 0037 RBX:
031d RCX: 804afd28
Apr  4 23:06:56 biocluster kernel: RDX: 804afd28 RSI:
0092 RDI: 804afd20
Apr  4 23:06:56 biocluster kernel: RBP: 0325 R08:
804afd28 R09: 
Apr  4 23:06:56 biocluster kernel: R10: 0046 R11:
8100010ceb40 R12: 81070967edb0
Apr  4 23:06:56 biocluster kernel: R13: 810e2c4343a8 R14:
88408091 R15: 81070967edb0
Apr  4 23:06:56 biocluster kernel: FS:  2b5b8bc496e0()
GS:810f0463a6c0() knlGS:
Apr  4 23:06:56 biocluster kernel: CS:  0010 DS:  ES:  CR0:
8005003b
Apr  4 23:06:56 biocluster kernel: CR2: 00403940 CR3:
000b7e1ee000 CR4: 06e0
Apr  4 23:06:56 biocluster kernel: Process rm (pid: 12459, threadinfo
81053e8b2000, task 810c73dad020)
Apr  4 23:06:56 biocluster kernel: Stack:  810e2c4343a8
81053e8b3a38 81063849b884 884080f3
Apr  4 23:06:56 biocluster kernel:  81063849b8

Bug#576601: marked as done (linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script)

[Debian Bug Tracking System]

Your message dated Tue, 06 Apr 2010 01:08:31 +0100
with message-id <1270512511.24287.69.ca...@localhost>
and subject line Re: Bug#576601: linux-image-2.6.18-6-686: aptitude install 
fails. complains of error status 1 returned from preinst script
has caused the Debian Bug report #576601,
regarding linux-image-2.6.18-6-686: aptitude install fails. complains of error 
status 1 returned from preinst script
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.)


-- 
576601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-6-686
Severity: important

tried and failed to find preinst script even in source package. 
tried 486 version. same error. 

Thank you for your time

-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.19
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)


--- End Message ---
--- Begin Message ---
On Mon, 2010-04-05 at 18:18 -0400, Tom Cerul wrote:
> Package: linux-image-2.6.18-6-686
> Severity: important
> 
> tried and failed to find preinst script even in source package. 
> tried 486 version. same error. 

This is part of Debian 4.0 'etch', which is no longer supported.  Please
try Debian 5.0 'lenny'.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processing of linux-2.6_2.6.32-11_amd64.changes

[Archive Administrator]

linux-2.6_2.6.32-11_amd64.changes uploaded successfully to localhost
along with the files:
  linux-2.6_2.6.32-11.dsc
  linux-2.6_2.6.32-11.diff.gz
  linux-doc-2.6.32_2.6.32-11_all.deb
  linux-manual-2.6.32_2.6.32-11_all.deb
  linux-patch-debian-2.6.32_2.6.32-11_all.deb
  linux-source-2.6.32_2.6.32-11_all.deb
  linux-support-2.6.32-4_2.6.32-11_all.deb
  firmware-linux-free_2.6.32-11_all.deb
  linux-base_2.6.32-11_all.deb
  linux-image-2.6.32-4-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-common_2.6.32-11_amd64.deb
  linux-image-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-openvz-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-common-openvz_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-all_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-all-amd64_2.6.32-11_amd64.deb
  linux-libc-dev_2.6.32-11_amd64.deb
  linux-image-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-vserver-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-common-vserver_2.6.32-11_amd64.deb
  linux-image-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  xen-linux-system-2.6.32-4-xen-amd64_2.6.32-11_amd64.deb
  linux-headers-2.6.32-4-common-xen_2.6.32-11_amd64.deb

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1nywxq-0003h0...@ries.debian.org

fbcon initramfs

[maximilian attems]

initramfs-tools 0.94 due to dropping graphics won't load fbcon.
Ubuntu has a shaddy udev loading.

IRC some archs have fbcon not built in thus will need to adapt?

thanks for your input.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405151150.gc3...@stro.at

Re: Maintenance of nfs-kernel-server

[Ben Hutchings]

On Tue, 2010-04-06 at 09:17 +1000, Aníbal Monsalve Salazar wrote:
> On Mon, Apr 05, 2010 at 11:20:42PM +0100, Ben Hutchings wrote:
> >Here's the debdiff for the changes I'd like to make now.
> 
> I also have some changes here. I'll upload my changes together with your
> changes later. I'll let you know when. Please let me know if you have
> more changes.

The patch from #524255 could be applied.  Other than that, there are no
more obvious changes to make.  There is a new upstream version but I
didn't look at it yet.  Did you?

> >We should probably import nfs-utils into a VCS somewhere, but I'm not
> >sure how best to do that with a v3.0 package.
> 
> We could just keep the debian directory under git.

Ugh, please don't do that.  That means you end up needing two separate
repositories (upstream and Debian) and you can't really diff Debian
versions.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Bug#573460: Congrat,Winner of 250,000.00 Great British Pounds

[WNNS]

250,000.00 GBP has been awarded to you.Submit your
Name:Address:Age:Sexccupation:Tel:Country







-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1270506188.4bba62cc51...@webmail.xcelco.on.ca

Bug#522726: kernel problem after a simple 'rm' command: RESERVE_SPACE(805) failed in function encode_lookup

[Aleksandr Levchuk]

Hi Ben,

No, I haven't got a chance to check if the bug exists in newer version.
We changed our NFS server from Linux to OpenSolaris.

But it was a major problem. It re-occurred every time a user would
attempt a filesystem operation where the filename was very long (e.g.
500 characters). Any fs write operation (rm, create new file) would
cause the kernel panic.

The crash happened several times a year. In all cases it was when
someone would antecedently pass data instead of a filename to a peace
of code that expects filenames.

Alex


On Mon, Apr 5, 2010 at 3:45 PM, Ben Hutchings  wrote:
> On Sun, 2009-04-05 at 23:08 -0700, Aleksandr Levchuk wrote:
>> Package: nfs-kernel-server
>> Version: 1:1.0.10-6+etch.1
>> Severity: important
>>
>> My very stable server crashed as a result of a 'rm' command in an
>> NFS-mounted home directory. The 'rm' command was a file name (with
>> newlines) but that file did not exist.
> [...]
>
> Sorry for the delay in replying to this.  The nfs-kernel-server package
> only contains supporting scripts, but the bug is clearly in the kernel
> itself (linux-image-* packages).
>
> The system you reported this bug from was apparently running Linux
> 2.6.22.  I assume that is the same version in which you saw this bug.
> Have you seen the bug reoccur in any more recent kernel version?
>
> Ben.
>
> --
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.
>



-- 
-
Aleksandr Levchuk
Administrator of Bioinformatic Systems and Databases

Homepage: http://biocluster.ucr.edu/~alevchuk/
Cell Phone: (951) 368-0004
Lab Phone: (951) 905-5232

Institute for Integrative Genome Biology
University of California, Riverside
-



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/z2wa39d6f081004051613zb572914bu513cbf3e0e7a2...@mail.gmail.com

Bug#547365: fixed in initramfs-tools 0.94

[Jonathan Nieder]

Debian Bug Tracking System wrote:

> #547365: "initramfs-tools -d -k foo" is not idempotent
> 
> It has been closed by maximilian attems .

Thanks.

>  initramfs-tools (0.94) unstable; urgency=low
>  .
>* The "Litte Bang" release

Wow.  You can say that again.

>[ Bert Schulze ]
>* initramfs-tools: support different compression tools in mkinitramfs.
>  (closes: #533903)
>* mkinitramfs: -c compression support / commandline override.
>  (closes: #576429)

I was thinking of doing that, glad to see it got done already.

Looking forward to the next boot, :)
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405230129.ga5...@progeny.tock

Re: Maintenance of nfs-kernel-server

[Aníbal Monsalve Salazar]

On Mon, Apr 05, 2010 at 11:20:42PM +0100, Ben Hutchings wrote:
>Here's the debdiff for the changes I'd like to make now.

I also have some changes here. I'll upload my changes together with your
changes later. I'll let you know when. Please let me know if you have
more changes.

>We should probably import nfs-utils into a VCS somewhere, but I'm not
>sure how best to do that with a v3.0 package.

We could just keep the debian directory under git.


signature.asc
Description: Digital signature

Bug#576603: stay in sid to settle dust

[maximilian attems]

Package: initramfs-tools
Version: 0.94
Severity: serious

breaks cryptsetup for now thus should stay in sid,
until fixed cryptestup available.




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405221834.gm32...@baikonur.stro.at

Bug#576601: linux-image-2.6.18-6-686: aptitude install fails. complains of error status 1 returned from preinst script

[Tom Cerul]

Package: linux-image-2.6.18-6-686
Severity: important

tried and failed to find preinst script even in source package. 
tried 486 version. same error. 

Thank you for your time

-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.19
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405221818.6576.85049.report...@linbox

Processed: notfound 522726 in 2.6.22-3-amd64, found 522726 in 2.6.22-6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 522726 2.6.22-3-amd64
Bug #522726 [linux-2.6] kernel problem after a simple 'rm' command: 
RESERVE_SPACE(805) failed  in function encode_lookup
There is no source info for the package 'linux-2.6' at version '2.6.22-3-amd64' 
with architecture ''
Unable to make a source version for version '2.6.22-3-amd64'
Bug No longer marked as found in versions 2.6.22-3-amd64.
> # assumed
> found 522726 2.6.22-6
Bug #522726 [linux-2.6] kernel problem after a simple 'rm' command: 
RESERVE_SPACE(805) failed  in function encode_lookup
There is no source info for the package 'linux-2.6' at version '2.6.22-6' with 
architecture ''
Unable to make a source version for version '2.6.22-6'
Bug Marked as found in versions 2.6.22-6.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127050722519353.transcr...@bugs.debian.org

Processed: tagging 522726

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 522726 moreinfo
Bug #522726 [linux-2.6] kernel problem after a simple 'rm' command: 
RESERVE_SPACE(805) failed  in function encode_lookup
Added tag(s) moreinfo.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127050753121062.transcr...@bugs.debian.org

Bug#576608: linux-base: "Invalid output format udev" during configuration

[Ben Pfaff]

Package: linux-base
Version: 2.6.32-10

During an upgrade that prompted me to replace device names by
UUIDs in /etc/fstab, a few error messages were printed on the
console:

Setting up linux-base (2.6.32-10) ...
Invalid output format udev. Choose from value,
device, list, or full
Invalid output format udev. Choose from value,
device, list, or full
Invalid output format udev. Choose from value,
device, list, or full
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.32-trunk-686
Found kernel: /boot/vmlinuz-2.6.32-4-686
Found kernel: /boot/vmlinuz-2.6.28-1-686
Found kernel: /boot/vmlinuz-2.6.26-1-686
Found kernel: /boot/vmlinuz-2.6.24-1-686
Found kernel: /boot/vmlinuz-2.6.22-1-686
Found kernel: /boot/vmlinuz-2.6.18-4-686
Found kernel: /boot/vmlinuz-2.6.18-3-686
Found kernel: /boot/vmlinuz-2.6.18-1-686
Found kernel: /boot/vmlinuz-2.6.17-2-686
Updating /boot/grub/menu.lst ... done

The upgrade did seem to complete smoothly but the error messages
still seem a bit worrisome.

Thanks,

Ben.
-- 
Ben Pfaff 
http://benpfaff.org



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87iq8538uc@blp.benpfaff.org

Bug#576564: linux-image-2.6.32-3-686: ali5451 - no sound after resuming from suspend

[Mark Brown]

On Mon, Apr 05, 2010 at 07:49:23PM +0100, Ben Hutchings wrote:
> On Mon, 2010-04-05 at 20:00 +0300, Rami Autiom??ki wrote:

> > My laptop suspends and resumes find, but sound is not working after 
> > computer is
> > suspended and resumed. I compiled vanilla kernel 2.6.33.2 from kernel.org,
> > after suspending sound fails similarly with this kernel also. I can fix 
> > sound
> > by running as root "alsa force-reload" .

> This bug has apparently been known to the ALSA project for nearly 3
> years, but no-one is working on it:

> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=959
> (note, the SSL certificate for this site has expired; you will need to
> accept it temporarily)

> You can try adding your information there in case this get some
> attention from ALSA developers.  Unfortunately we will not be able to
> fix this without their help.

For ALSA bugs it's much more likely to be useful to report them upstream
by sending them to alsa-de...@alsa-project.org with a CC Takashi Iwai
 - the ALSA bug tracker is pretty much ignored by both
desktop and embedded ALSA developers these days (and we really should
shut it down, I'll try to remember to bring that up on the list soon).



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100405213421.gb22...@sirena.org.uk

Bug#522726: kernel problem after a simple 'rm' command: RESERVE_SPACE(805) failed in function encode_lookup

[Ben Hutchings]

On Sun, 2009-04-05 at 23:08 -0700, Aleksandr Levchuk wrote:
> Package: nfs-kernel-server
> Version: 1:1.0.10-6+etch.1
> Severity: important
> 
> My very stable server crashed as a result of a 'rm' command in an
> NFS-mounted home directory. The 'rm' command was a file name (with
> newlines) but that file did not exist.
[...]

Sorry for the delay in replying to this.  The nfs-kernel-server package
only contains supporting scripts, but the bug is clearly in the kernel
itself (linux-image-* packages).

The system you reported this bug from was apparently running Linux
2.6.22.  I assume that is the same version in which you saw this bug.
Have you seen the bug reoccur in any more recent kernel version?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Processed: reassign 522726 to linux-2.6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 522726 linux-2.6 2.6.22-3-amd64
Bug #522726 [nfs-kernel-server] kernel problem after a simple 'rm' command: 
RESERVE_SPACE(805) failed  in function encode_lookup
Bug reassigned from package 'nfs-kernel-server' to 'linux-2.6'.
Bug No longer marked as found in versions nfs-utils/1:1.0.10-6+etch.1.
Bug #522726 [linux-2.6] kernel problem after a simple 'rm' command: 
RESERVE_SPACE(805) failed  in function encode_lookup
There is no source info for the package 'linux-2.6' at version '2.6.22-3-amd64' 
with architecture ''
Unable to make a source version for version '2.6.22-3-amd64'
Bug Marked as found in versions 2.6.22-3-amd64.
> thanks
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
Archive: 
http://lists.debian.org/handler.s.c.127050720419087.transcr...@bugs.debian.org

Bug#562847: marked as done (gzip: stdout: No space left on device)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:52 +
with message-id 
and subject line Bug#519800: fixed in initramfs-tools 0.94
has caused the Debian Bug report #562847,
regarding gzip: stdout: No space left on device
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.)


-- 
562847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.93.4
Severity: wishlist
Tags: patch


I think, at least once You saw the message in subject. It is common
problem: the /boot directory placed on separate partition that should be
small. If there are more then one kernel, the disk space will be
necessarily exhausted, because new kernel version require more disk space
then old as usual. Turning off backup don't help because the old initrd
removed after the new one created. To solve this problem the backups should
be moved to separated directory and may be rotated. The old initrd should be
moved there or removed before the new one will be created. All this work is
done by script I have attached there. It is intended to be run before
update-initramfs, but there are no triggers to do this. Using
/etc/initramfs-tools/hooks don't help.  Please, add this functionality as
options in config file.


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-amd64 
root=UUID=06779e83-c998-4a4b-bb52-f4bac1ee226a ro vga=795

-- /proc/filesystems
ext3
fuseblk

-- lsmod
Module  Size  Used by
vboxnetflt  9898  0 
vboxnetadp  4177  0 
vboxdrv  1709830  2 vboxnetflt,vboxnetadp
i915  246815  1 
drm_kms_helper 18771  1 i915
drm   136351  3 i915,drm_kms_helper
i2c_algo_bit4225  1 i915
video  17333  1 i915
output  1692  1 video
ppdev   5030  0 
lp  7462  0 
kvm_intel  37600  0 
kvm   210696  1 kvm_intel
autofs420533  2 
fuse   49662  1 
tun10732  3 
bridge 39310  0 
stp 1440  1 bridge
coretemp4165  0 
snd_hda_codec_idt  42257  1 
snd_hda_intel  17851  0 
snd_hda_codec  52580  2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep   5220  1 snd_hda_codec
snd_pcm_oss32223  0 
snd_mixer_oss  12478  1 snd_pcm_oss
snd_pcm60263  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer  15406  1 snd_pcm
i2c_i8017510  0 
evdev   7336  14 
pcspkr  1699  0 
processor  29351  0 
i2c_core   15184  4 i915,drm,i2c_algo_bit,i2c_i801
snd44158  8 
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
iTCO_wdt7525  0 
parport_pc 18839  1 
parport27666  3 ppdev,lp,parport_pc
soundcore   4582  1 snd
snd_page_alloc  6105  2 snd_hda_intel,snd_pcm
ext3  105843  7 
jbd36621  1 ext3
mbcache 4970  1 ext3
sg 18600  3 
usbhid 31068  0 
sr_mod 12250  0 
hid62649  1 usbhid
cdrom  28615  1 sr_mod
sd_mod 29401  9 
crc_t10dif  1276  1 sd_mod
ata_generic 2983  0 
ahci   31430  10 
pata_marvell2597  0 
firewire_ohci  19324  0 
firewire_core  36288  1 firewire_ohci
crc_itu_t   1307  1 firewire_core
ide_pci_generic 2788  0 
ide_core   76242  1 ide_pci_generic
libata130935  3 ata_generic,ahci,pata_marvell
e1000e109583  0 
uhci_hcd   18377  0 
ehci_hcd   30322  0 
intel_agp  25441  1 
agpgart24733  3 drm,intel_agp
scsi_mod  121285  4 sg,sr_mod,sd_mod,libata
usbcore   121015  4 usbhid,uhci_hcd,ehci_hcd
nls_base6377  1 usbcore
button  4618  1 i915
thermal11610  0 
fan 3346  0 
thermal_sys11878  4 video,processor,thermal,fan

-- /etc/kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = no
#relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
#link_in_boot = no
postinst_hook = /usr/sbin/update-gru

Bug#534201: marked as done (/etc/elilo.conf not found)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:52 +
with message-id 
and subject line Bug#534201: fixed in initramfs-tools 0.94
has caused the Debian Bug report #534201,
regarding /etc/elilo.conf not found
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.)


-- 
534201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.62.6
Severity: serious

--- Please enter the report below this line. ---
Since the last update I did using synaptic, an errror occures starting it.

"
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
> correct the problem. 
> E: _cache->open() failed, please report.
"

The update worked out fine beside the lines listed above appeared at the
end of the update.

Running "dpkg --configure -a" the terminal says
"
> Setting up initramfs-tools (0.93.3) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools ...
> update-initramfs: Generating /boot/initrd.img-2.6.26-2-amd64
> dpkg: warning: obsolete option '--print-installation-architecture', please 
> use '--print-architecture' instead.
> elilo: /etc/elilo.conf: No such file or directory
> dpkg: subprocess installed post-installation script returned error exit 
> status 1
"

Thank you for your fine work!
Matthias Krüger
--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.26-2-amd64

Debian Release: squeeze/sid
  500 testing 141.76.2.4
  500 stable  security.debian.org
  500 stable  http.us.debian.org

--- Package information. ---
Depends   (Version) | Installed
===-+-==
libapt-inst-libc6.9-6-1.1   |
libapt-pkg-libc6.9-6-4.7|
libatk1.0-0 (>= 1.20.0) | 1.26.0-1
libc6(>= 2.3.4) | 2.9-12
libcairo2(>= 1.2.4) | 1.8.6-2+b1
libfontconfig1   (>= 2.4.0) | 2.6.0-3
libfreetype6 (>= 2.2.1) | 2.3.9-4.1
libgcc1(>= 1:4.1.1) | 1:4.4.0-5
libglade2-0(>= 1:2.6.1) | 1:2.6.4-1
libglib2.0-0(>= 2.16.0) | 2.20.1-2
libgtk2.0-0  (>= 2.8.0) | 2.16.1-2
libpango1.0-0   (>= 1.14.0) | 1.24.0-3+b1
libstdc++6   (>= 4.2.1) | 4.4.0-5
libvte9   (>= 1:0.19.4) | 1:0.20.1-1
libx11-6| 2:1.2.1-1
libxml2 (>= 2.6.27) | 2.7.3.dfsg-1
scrollkeeper| 0.3.14-16
hicolor-icon-theme  | 0.10-2


Recommends  (Version) | Installed
=-+-===
gksu  | 2.0.2-2+b1
deborphan | 1.7.28
libgnome2-perl| 1.042-2
menu  | 2.1.41


Suggests  (Version) | Installed
===-+-===
dwww| 1.11.1






--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.94

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.94.dsc
  to main/i/initramfs-tools/initramfs-tools_0.94.dsc
initramfs-tools_0.94.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.94.tar.gz
initramfs-tools_0.94_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.94_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 534...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated initramfs-tools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 05 Apr 2010 05:25:48 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.94
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: maximilian attems 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 415474 433708 465760 487409 506533 519800 523735 524534 525606 533903 
534201 535008 53

"Little Bang 0.94" initramfs-tools release

[maximilian attems]

Newer initramfs comes with lots of fixes and new features:

* Faster boot thanks to Ubuntu merged patches using pre-cached boot scripts.

* Support for several compression schemes as set in initramfs.conf or
  overridden by appropriate mkinitramfs call.

* Better MODULES=dep support /sys parsing (Still needs fixes for md).

* Hooks for out of linux-2.6 make deb-pkg generated linux-images.

* Call ipconfig with increasing timeouts to better fit with large scale
  clusters.

* Use BOOTIF mac address passed from gpxe in setup_networking.

* Out of the box support for devtmpfs. Hurra for devfs 2.0.

* Loading of the netconsole module together with the specified args,
  when netconsole is set as bootarg.

* Adds available, built network drivers in a dynamic way without need
  of hardcoded list.

* Smaller and thus faster MODULES=most generated initramfs due to
  kicking the video part out of generic initramfs.

git repo:
git clone git://git.debian.org/kernel/initramfs-tools.git

http view of it:
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary

thanks for everyone involved.

-- 
maks

PS shortlog follows

Anna Jonna Armannsdottir (1):
  configure_networking: Try repeatedly ipconfig with increasing timeout

Avi Rozen (1):
  mkinitramfs: add all usb storage devices

Ben Collins (1):
  update-initramfs: Default to not keep .bak backups

Ben Hutchings (2):
  copy_modules_dir: Take a list of exclusions after the base directory
  auto_add_modules: Copy all modules from net, excluding some subdirectories

Bert Schulze (1):
  mkinitramfs: -c compression support / commandline override

Colin Watson (2):
  mkinitramfs: Filter out looping or broken symlinks from the initramfs
  mkinitramfs: set initramfs root to 755

Ferenc Wagner (1):
  initramfs-tools: make the panic argument available in the rescue shell

Joey Hess (1):
  scripts/local: avoid mount -t unknown

Martin Michlmayr (1):
  MODULES=dep fix boot with MMC

Maximilian Gass (1):
  mkinitramfs: KEYMAP option fails to work due to missing keymap

Michael Prokop (2):
  Fix path to nfsroot.txt in documentation.
  hook-functions: Avoid firmware copy error.

Nikolaus Schulz (1):
  hook-functions: let dep_add_modules() recurse into lvm slave devices

Piotr Lewandowski (1):
  update-initramfs breaks if /etc/mtab is a symlink to /proc/mounts

Scott James Remnant (5):
  init: Mount devtmpfs on /dev
  mkinitramfs: Call depmod before packing the initramfs.
  init: load the netconsole module with netconsole bootarg
  init: mount /dev/pts as well as /dev
  mkinitramfs: generate pre-cached boot order file

Tormod Volden (1):
  blacklist boot hook write to /etc/modprobe.d/initramfs.conf

Vagrant Cascadian (1):
  configure_networking: support BOOTIF variable set by pxelinux

bert schulze (1):
  initramfs-tools: support different compression tools in mkinitramfs

maximilian attems (56):
  nuke thermal hooks
  create a klibc hook script
  Redefinde MODULES=most to not carry any fb driver per default.
  nuke kernelextras hook
  nuke framebuffer boot script
  Revert "hook-functions: Add hid_* modules."
  klibc remove zcat and gunzip
  move busybox addition to a hook script
  mkinitramfs fix comment
  hook-functions: Fix mounted /sys check for openvz container.
  initramfs-tools.8: fix boot example script to execute scripts/functions
  fix out-of-date-standards-version
  /etc/kernel hook script support newer kernel-package
  update-initramfs: allow -t takeover on delete
  /etc/kernel/postrm.d/i-t: use now takeover on delete
  Nuke useless unused dir.
  kernel hook scripts: Fix typo
  kernel hook scripts: add comments
  hook-funcitions: Only warn about missing firmware if /proc/modules exists
  mkinitramfs: Be opportunistic when calling modprobe thus showing errors
  copy_exec: Check if ldd is around
  scripts/local: Use blkid as backup fstype detection
  mkinitramfs: only copy modprobe conf files
  blacklist earlier at init-top stage
  scripts/local: fix blkid invocation
  init: export and unset BOOTIF
  init: rexport resume to reallow it's hardcoded usage
  update-initramfs: -d delete .bak file
  control: bump standards version without changes.
  control: Clean up Uploaders field
  switch from cdbs to debhelper 7
  update-initramfs: Stop second guessing lilo usage.
  mkinitramfs: allow to build initramfs for unmodular linux images
  initramfs.conf.5: document UMASK variable for sensitive initramfs
  update-initramfs: only run elilo if configured
  update-initramfs: fix previous elilo commit
  MODULES=DEP Use driver/module syfs attribute
  panic: quote variable
  MODULES=DEP: Check superblock on initramfs block
  Use ata_generic driver on all_generic_ide bootarg
  scripts/functions: add get_fstype() from scripts/loca

Bug#543568: marked as done (initramfs-tools: usb storage device not recognized at boot after upgrade to kernel 2.6.30)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:53 +
with message-id 
and subject line Bug#543568: fixed in initramfs-tools 0.94
has caused the Debian Bug report #543568,
regarding initramfs-tools: usb storage device not recognized at boot after 
upgrade to kernel 2.6.30
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.)


-- 
543568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.93.4
Severity: important
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


USB storage device is not recognized at boot after kernel upgrade.

It seems that the usb-storage module has been split into several mini 
modules, which are not copied to the initramfs image. 

In my case usb-storage.ko is copied but ums-cypress.ko is not copied.

I've attached a patch against hook-functions that fixes this, by using 
copy_modules_dir to copy all the modules in kernel/drivers/usb/storage,
instead of just usb-storage.

I've set the severity to important because my USB storage device also 
happens to be the boot device... 

Cheers,
Avi

- -- Package-specific info:
- -- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.30-1-686 root=/dev/mapper/afula-root ro rootdelay=10

- -- /proc/filesystems
ext3
fuseblk

- -- lsmod
Module  Size  Used by
binfmt_misc 7120  1 
ppdev   6348  0 
parport_pc 22420  0 
lp  8012  0 
parport31144  3 ppdev,parport_pc,lp
rfkill_input5272  0 
sco 8832  2 
bridge 39968  0 
stp 2112  1 bridge
bnep   10860  2 
rfcomm 30368  0 
l2cap  18120  6 bnep,rfcomm
bluetooth  47060  6 sco,bnep,rfcomm,l2cap
nfsd  204900  9 
lockd  57972  1 nfsd
nfs_acl 2640  1 nfsd
auth_rpcgss31416  1 nfsd
sunrpc163772  8 nfsd,lockd,nfs_acl,auth_rpcgss
exportfs3792  1 nfsd
powernow_k812260  0 
cpufreq_conservative 6256  0 
cpufreq_userspace   2768  0 
cpufreq_stats   3520  0 
cpufreq_powersave   1292  0 
fuse   47752  1 
loop   13324  0 
snd_hda_codec_conexant17164  1 
snd_hda_intel  22192  0 
snd_hda_codec  63580  2 snd_hda_codec_conexant,snd_hda_intel
snd_hwdep   6120  1 snd_hda_codec
snd_pcm_oss32232  0 
snd_mixer_oss  12368  1 snd_pcm_oss
snd_pcm62420  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
arc41560  2 
snd_seq_midi5688  0 
snd_rawmidi18596  1 snd_seq_midi
ecb 2368  2 
snd_seq_midi_event  6212  1 snd_seq_midi
snd_seq42436  2 snd_seq_midi,snd_seq_midi_event
snd_timer  17436  2 snd_pcm,snd_seq
snd_seq_device  6136  3 snd_seq_midi,snd_rawmidi,snd_seq
b43   108932  0 
snd49060  11 
snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore   6184  1 snd
rfkill  9668  3 rfkill_input,b43
rng_core3672  1 b43
i2c_nforce2 6448  0 
snd_page_alloc  8180  2 snd_hda_intel,snd_pcm
mac80211  142848  1 b43
i2c_core   20844  1 i2c_nforce2
joydev  8576  0 
cfg80211   6  2 b43,mac80211
k8temp  3984  0 
pcspkr  2104  0 
serio_raw   4560  0 
led_class   3852  1 b43
evdev   8028  12 
psmouse37528  0 
input_polldev   3588  1 b43
wmi 6184  0 
battery 6012  0 
processor  34504  1 powernow_k8
ac  2960  0 
button  5060  0 
ext3  107172  2 
jbd41036  1 ext3
mbcache 6924  1 ext3
sha256_generic 11216  0 
aes_i5868092  2 
aes_generic27436  1 aes_i586
cbc 3012  1 
dm_crypt   11092  1 
dm_snapshot21604  0 
ums_cypress 2888  0 
sd_mod 28748  4 
crc_t10dif  1632  1 sd_mod
usb_storage48472  3 ums_cypress
ide_cd_mod 24484  0 
cdrom  30316  1 ide_cd_mod
ide_pci_generic 3632  0 
ohci_hcd 

Bug#575154: marked as done (Incorrect assumes existance of /proc/modules)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:55 +
with message-id 
and subject line Bug#575154: fixed in initramfs-tools 0.94
has caused the Debian Bug report #575154,
regarding Incorrect assumes existance of /proc/modules
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.)


-- 
575154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92o

If the running kernel has had module support removed, you'll get a bunch
of errors of:
grep: /proc/modules: No such file or directory

The one place I found was in /usr/share/initramfs-tools/hook-functions,
the function manual_add_modules(). Looks like you need the "-s" option
to grep, or else redirect standard error.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| e...@gremlin.m5p.com PGP F6B23DE0 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0




--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.94

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.94.dsc
  to main/i/initramfs-tools/initramfs-tools_0.94.dsc
initramfs-tools_0.94.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.94.tar.gz
initramfs-tools_0.94_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.94_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 575...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated initramfs-tools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 05 Apr 2010 05:25:48 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.94
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: maximilian attems 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 415474 433708 465760 487409 506533 519800 523735 524534 525606 533903 
534201 535008 536195 541864 543568 545728 547365 548711 554873 559535 559619 
560266 561289 562561 565386 565416 567065 567189 568527 569033 570678 572858 
573761 574553 575154 575157 576429
Changes: 
 initramfs-tools (0.94) unstable; urgency=low
 .
   * The "Litte Bang" release
 .
   [ maximilian attems ]
   * Nuke kernelextras hooks.
   * Create a klibc hook script.
   * Redefinde MODULES=most to not carry any fb driver per default.
   * Nuke framebuffer boot script.
   * Revert "hook-functions: Add hid_* modules."
   * Move busybox addition to a hook script.
   * mkinitramfs fix comment.
   * hook-functions: Fix mounted /sys check for openvz container.
   * initramfs-tools.8: fix boot example script to execute.
 scripts/functions. (closes: #545728)
   * Fix out-of-date-standards-version.
   * /etc/kernel hook script support for make deb-pkg generated linux-images
 and kernel-package. (closes: #523735, #561289)
   * update-initramfs: allow -t takeover on delete.
   * /etc/kernel/postrm.d/i-t: use now takeover on delete.
 (closes: #524534, #547365, #559619)
   * Nuke useless unused dir.
   * kernel hook scripts: Fix typo, add comments.
   * hook-funcitions: Only warn about missing firmware if /proc/modules
 exists. (closes: #560266, #575154)
   * mkinitramfs: Be opportunistic when calling modprobe thus showing
 errors. (closes: #554873)
   * copy_exec: Check if ldd is around.
   * scripts/local: Use blkid as backup fstype detection. (closes: #568527)
   * mkinitramfs: only copy modprobe conf files. (closes: #506533)
   * blacklist earlier at init-top stage.
   * scripts/local: fix blkid invocation.
   * init: export and unset BOOTIF.
   * init: rexport resume to reallow it's hardcoded usage. (closes: #572858)
   * update-initramfs: -d delete .bak file. (closes: #559535)
   * control: bump standards version without changes.
   * control: Clean up Uploaders field.
   * switch from cdbs to debhelper 7.
   * update-initramfs: Stop second guessing lilo usage. (closes: #574553)
   * mkinitramfs: allo

Bug#533903: marked as done (initramfs-tools: support different compression tools in mkinitramfs)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:52 +
with message-id 
and subject line Bug#533903: fixed in initramfs-tools 0.94
has caused the Debian Bug report #533903,
regarding initramfs-tools: support different compression tools in mkinitramfs
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.)


-- 
533903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.93.3
Severity: wishlist


Current kernel versions support different decompression options for
kernel and initrd:

  CONFIG_DECOMPRESS_GZIP
  CONFIG_DECOMPRESS_BZIP2
  CONFIG_DECOMPRESS_LZMA

initramfs-tools currently supports gzip only. I'd like to see
support for bzip2 and lzma as well, as both of them provide better
compression (which is especially interesting for live systems).

IMHO the user should get gzip by default (if unset) but be able to
choose between gzip, bzip2 and lzma. Something like
COMPRESSION=[gzip|bzip2|lzma] in /etc/initramfs-tools/initramfs.conf
should provide that.

I plan to provide the according code for integration (though I'm
running out of time right now, so it might need a few days/weeks).
Please ACK my idea if that's in your interest. If have any special
configuration variable / implementation wishes please let me know.

regards,
-mika-


--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.94

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.94.dsc
  to main/i/initramfs-tools/initramfs-tools_0.94.dsc
initramfs-tools_0.94.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.94.tar.gz
initramfs-tools_0.94_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.94_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 533...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated initramfs-tools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 05 Apr 2010 05:25:48 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.94
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: maximilian attems 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 415474 433708 465760 487409 506533 519800 523735 524534 525606 533903 
534201 535008 536195 541864 543568 545728 547365 548711 554873 559535 559619 
560266 561289 562561 565386 565416 567065 567189 568527 569033 570678 572858 
573761 574553 575154 575157 576429
Changes: 
 initramfs-tools (0.94) unstable; urgency=low
 .
   * The "Litte Bang" release
 .
   [ maximilian attems ]
   * Nuke kernelextras hooks.
   * Create a klibc hook script.
   * Redefinde MODULES=most to not carry any fb driver per default.
   * Nuke framebuffer boot script.
   * Revert "hook-functions: Add hid_* modules."
   * Move busybox addition to a hook script.
   * mkinitramfs fix comment.
   * hook-functions: Fix mounted /sys check for openvz container.
   * initramfs-tools.8: fix boot example script to execute.
 scripts/functions. (closes: #545728)
   * Fix out-of-date-standards-version.
   * /etc/kernel hook script support for make deb-pkg generated linux-images
 and kernel-package. (closes: #523735, #561289)
   * update-initramfs: allow -t takeover on delete.
   * /etc/kernel/postrm.d/i-t: use now takeover on delete.
 (closes: #524534, #547365, #559619)
   * Nuke useless unused dir.
   * kernel hook scripts: Fix typo, add comments.
   * hook-funcitions: Only warn about missing firmware if /proc/modules
 exists. (closes: #560266, #575154)
   * mkinitramfs: Be opportunistic when calling modprobe thus showing
 errors. (closes: #554873)
   * copy_exec: Check if ldd is around.
   * scripts/local: Use blkid as backup fstype detection. (closes: #568527)
   * mkinitramfs: only copy modprobe conf files. (closes: #506533)
   * blacklist earlier at init-top stage.
   * scripts/local: fix blkid invocation.
   * init: export and unset BOOTIF.
   * init: rexport resume to reallow it's hardcoded usage. (closes: #572858

Bug#575157: marked as done (Calling `cpio` can produce error messages when working correctly)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:55 +
with message-id 
and subject line Bug#575157: fixed in initramfs-tools 0.94
has caused the Debian Bug report #575157,
regarding Calling `cpio` can produce error messages when working correctly
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.)


-- 
575157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92o
Severity: minor

Thankfully pretty harmless, despite the annoyance:
cpio: ./etc/udev/RCS: Cannot stat: No such file or directory

Looks like `/usr/sbin/mkinitramfs` is the culprit. In this case,
/etc/udev/RCS is a symbolic link to ../RCS


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| e...@gremlin.m5p.com PGP F6B23DE0 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0




--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.94

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.94.dsc
  to main/i/initramfs-tools/initramfs-tools_0.94.dsc
initramfs-tools_0.94.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.94.tar.gz
initramfs-tools_0.94_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.94_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 575...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated initramfs-tools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 05 Apr 2010 05:25:48 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.94
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: maximilian attems 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 415474 433708 465760 487409 506533 519800 523735 524534 525606 533903 
534201 535008 536195 541864 543568 545728 547365 548711 554873 559535 559619 
560266 561289 562561 565386 565416 567065 567189 568527 569033 570678 572858 
573761 574553 575154 575157 576429
Changes: 
 initramfs-tools (0.94) unstable; urgency=low
 .
   * The "Litte Bang" release
 .
   [ maximilian attems ]
   * Nuke kernelextras hooks.
   * Create a klibc hook script.
   * Redefinde MODULES=most to not carry any fb driver per default.
   * Nuke framebuffer boot script.
   * Revert "hook-functions: Add hid_* modules."
   * Move busybox addition to a hook script.
   * mkinitramfs fix comment.
   * hook-functions: Fix mounted /sys check for openvz container.
   * initramfs-tools.8: fix boot example script to execute.
 scripts/functions. (closes: #545728)
   * Fix out-of-date-standards-version.
   * /etc/kernel hook script support for make deb-pkg generated linux-images
 and kernel-package. (closes: #523735, #561289)
   * update-initramfs: allow -t takeover on delete.
   * /etc/kernel/postrm.d/i-t: use now takeover on delete.
 (closes: #524534, #547365, #559619)
   * Nuke useless unused dir.
   * kernel hook scripts: Fix typo, add comments.
   * hook-funcitions: Only warn about missing firmware if /proc/modules
 exists. (closes: #560266, #575154)
   * mkinitramfs: Be opportunistic when calling modprobe thus showing
 errors. (closes: #554873)
   * copy_exec: Check if ldd is around.
   * scripts/local: Use blkid as backup fstype detection. (closes: #568527)
   * mkinitramfs: only copy modprobe conf files. (closes: #506533)
   * blacklist earlier at init-top stage.
   * scripts/local: fix blkid invocation.
   * init: export and unset BOOTIF.
   * init: rexport resume to reallow it's hardcoded usage. (closes: #572858)
   * update-initramfs: -d delete .bak file. (closes: #559535)
   * control: bump standards version without changes.
   * control: Clean up Uploaders field.
   * switch from cdbs to debhelper 7.
   * update-initramfs: Stop second guessing lilo usage. (closes: #574553)
   * mkinitramfs: allow to build initramfs for unmodular linux images.
 (closes: 

Bug#565416: marked as done (update-initramfs: KEYMAP option fails to work due to missing /etc/console/boottime.kmap.gz)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:54 +
with message-id 
and subject line Bug#565416: fixed in initramfs-tools 0.94
has caused the Debian Bug report #565416,
regarding update-initramfs: KEYMAP option fails to work due to missing 
/etc/console/boottime.kmap.gz
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.)


-- 
565416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.93.4
Severity: normal



-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=//vmlinuz-2.6.32.2 root=/dev/mapper/system-root ro quiet

-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
savage 23189  3 
drm   105600  4 savage
af_packet  13690  2 
fuse   45273  1 
loop9647  0 
snd_via82xx15226  2 
gameport6081  1 snd_via82xx
snd_ac97_codec 78752  1 snd_via82xx
ac97_bus 682  1 snd_ac97_codec
snd_pcm_oss28704  0 
snd_mixer_oss  10053  1 snd_pcm_oss
snd_pcm46096  3 snd_via82xx,snd_ac97_codec,snd_pcm_oss
snd_timer  12834  1 snd_pcm
snd_page_alloc  4673  2 snd_via82xx,snd_pcm
snd_mpu401_uart 4119  1 snd_via82xx
snd_rawmidi12864  1 snd_mpu401_uart
i2c_viapro  4331  0 
snd_seq_device  3617  1 snd_rawmidi
snd32499  13 
snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
i2c_core   12156  2 drm,i2c_viapro
soundcore   3538  1 snd
evdev   5701  13 
processor  14514  0 
sha256_generic 10996  0 
ansi_cprng  2957  0 
krng 753  1 
chainiv 2462  1 
crypto_wq487  1 chainiv
rng 1135  3 ansi_cprng,krng,chainiv
aes_i5866784  2 
aes_generic25690  1 aes_i586
cbc 2262  1 
cryptomgr  81339  0 
crypto_hash 8340  2 sha256_generic,cryptomgr
aead3799  1 cryptomgr
pcompress825  1 cryptomgr
sd_mod 19558  2 
usbhid 13817  0 
hid50452  1 usbhid
usb_storage30309  1 
dm_crypt8651  1 
crypto_blkcipher7496  4 chainiv,cbc,cryptomgr,dm_crypt
crypto_algapi   8970  11 
ansi_cprng,krng,chainiv,aes_i586,aes_generic,cbc,cryptomgr,crypto_hash,aead,pcompress,crypto_blkcipher
ide_gd_mod 16851  3 
ide_cd_mod 20409  0 
cdrom  25399  1 ide_cd_mod
ata_generic 1987  0 
libata114717  1 ata_generic
scsi_mod   63334  3 sd_mod,usb_storage,libata
ide_pci_generic 1896  0 
uhci_hcd   16193  0 
ehci_hcd   27514  0 
via_agp 4580  1 
via82cxxx   4298  2 
button  3478  0 
agpgart18908  2 drm,via_agp
via_rhine  15038  0 
mii 2658  1 via_rhine
ide_core   63390  4 ide_gd_mod,ide_cd_mod,ide_pci_generic,via82cxxx
usbcore93544  4 usbhid,usb_storage,uhci_hcd,ehci_hcd
nls_base4681  1 usbcore
thermal 9370  0 
fan 1910  0 
thermal_sys 9294  3 processor,thermal,fan

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=y
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /etc/crypttab
# 
hda3_crypt  /dev/hda3   noneluks

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32.2 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii  cpio  2.10-1 GNU cpio -- a program to manage ar
ii  findutils 4.4.2-1utilities for finding files--find,
ii  klibc-utils   1.5.15-1   small utilities built with klibc f
ii 

Bug#535008: marked as done (configure_networking: support BOOTIF variable set by pxelinux)

[Debian Bug Tracking System]

Your message dated Mon, 05 Apr 2010 22:12:53 +
with message-id 
and subject line Bug#535008: fixed in initramfs-tools 0.94
has caused the Debian Bug report #535008,
regarding configure_networking: support BOOTIF variable set by pxelinux
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.)


-- 
535008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.93.3
Severity: wishlist
Tags: patch

when booting thin clients with multiple network cards, initramfs-tools/ipconfig
have a hard time figuring out which interface to use. attached is a patch which
sets DEVICE to the interface matching the mac address that pxelinux passes when
using the IPAPPEND 2 or 3 options.

diff --git a/scripts/functions b/scripts/functions
index 77de8f3..ec0ffd2 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -258,6 +258,19 @@ parse_numeric() {
 
 configure_networking()
 {
+
+   # pxelinux sets BOOTIF to a value based on the mac address of the 
network
+   # card used to PXE boot, so use this value for DEVICE rather than a
+   # hard-coded device name from initramfs.conf. this facilitates network
+   # booting when machines may have multiple network cards.
+   if [ -n "${BOOTIF}" ]; then
+   normal_mac=$(echo $BOOTIF | sed -e 's,^01-,,g' -e 's,-,:,g' | 
tr [a-z] [A-Z])
+   new_device=$(ifconfig -a | awk "/$normal_mac/"'{print $1}')
+   if [ -n "$new_device" ]; then
+   DEVICE="$new_device"
+   fi
+   fi
+
# networking already configured thus bail out
[ -n "${DEVICE}" ] && [ -e /tmp/net-"${DEVICE}".conf ] && return 0

 
live well,
  vagrant


--- End Message ---
--- Begin Message ---
Source: initramfs-tools
Source-Version: 0.94

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.94.dsc
  to main/i/initramfs-tools/initramfs-tools_0.94.dsc
initramfs-tools_0.94.tar.gz
  to main/i/initramfs-tools/initramfs-tools_0.94.tar.gz
initramfs-tools_0.94_all.deb
  to main/i/initramfs-tools/initramfs-tools_0.94_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 535...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated initramfs-tools 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 05 Apr 2010 05:25:48 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.94
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team 
Changed-By: maximilian attems 
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 415474 433708 465760 487409 506533 519800 523735 524534 525606 533903 
534201 535008 536195 541864 543568 545728 547365 548711 554873 559535 559619 
560266 561289 562561 565386 565416 567065 567189 568527 569033 570678 572858 
573761 574553 575154 575157 576429
Changes: 
 initramfs-tools (0.94) unstable; urgency=low
 .
   * The "Litte Bang" release
 .
   [ maximilian attems ]
   * Nuke kernelextras hooks.
   * Create a klibc hook script.
   * Redefinde MODULES=most to not carry any fb driver per default.
   * Nuke framebuffer boot script.
   * Revert "hook-functions: Add hid_* modules."
   * Move busybox addition to a hook script.
   * mkinitramfs fix comment.
   * hook-functions: Fix mounted /sys check for openvz container.
   * initramfs-tools.8: fix boot example script to execute.
 scripts/functions. (closes: #545728)
   * Fix out-of-date-standards-version.
   * /etc/kernel hook script support for make deb-pkg generated linux-images
 and kernel-package. (closes: #523735, #561289)
   * update-initramfs: allow -t takeover on delete.
   * /etc/kernel/postrm.d/i-t: use now takeover on delete.
 (closes: #524534, #547365, #559619)
   * Nuke useless unused dir.
   * kernel hook scripts: Fix typo, add comments.
   * hook-funcitions: Only warn about missing firmware if /proc/modules
 exists. (closes: #560266, #575154)
   * mkinitramfs: Be opportunistic when calling modprobe thus sho