Bug#518802:

[Jonas Vejlin]

I can confirm this bug



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

Bug#494009: linux-2.6: are the ATI firmware-nonfree files available?

[Ben Hutchings]

On Fri, 2009-03-06 at 01:56 +1030, Arthur Marsh wrote:
> Package: linux-2.6
> Followup-For: Bug #494009
> 
> 
> I couldn't find any files containing ATI firmware at 
> http://ftp.debian.org/debian/pool/non-free/f/firmware-nonfree/
> 
> Are these files available anywhere?

They're in the Subversion repository for this package and will be in the
next release.  Note that the change to remove them from kernel images is
also unreleased.

Ben.



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

Bug#517771: USB_HIDDEV also needed in 2.6.28

[Ryan Tandy]

Please also enable this option in the 2.6.28 orion5x kernel.



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

Bug#519040: linux-headers-2.6.28-1-686: depends on linux-kbuild but not available

[Mark Niven]

Package: linux-headers-2.6.28-1-686
Severity: normal

Depends on linux-kbuild-2.6.28 which is still not available a week after 
the 2.6.28 kernel images. As a result the new kernel remains unusable 
for me as it is not possible (easy ?) to rebuild kernel modules for it.
I realise it is just a matter of time, but when? Or am I missing 
something else obvious? Thnak you.

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

Kernel: Linux 2.6.26-1-686 (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/bash

Versions of packages linux-headers-2.6.28-1-686 depends on:
ii  gcc-4.3   4.3.3-5The GNU C compiler
ii  linux-headers-2.6.28-1-common 2.6.28-1   Common header files for Linux 2.6.
pn  linux-kbuild-2.6.28(no description available)

linux-headers-2.6.28-1-686 recommends no packages.

linux-headers-2.6.28-1-686 suggests no packages.



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

Bug#519037: please include watchdog module for Geode in i386 kernels

[Stephen Gregory]

package: linux-image-2.6.26-1-486
version: 2.6.26+17
severity: minor
tags: patch

also package linux-image-2.6.26-1-686 version 2.6.26+17

Please enable the watchdog module for the AMD Geode processor. The
code is in the vanilla kernel in geodewdt.c. It is GPL. The config
option is GEODE_WDT=m. The patch below will add the option. 



--- linux-2.6-2.6.26/debian/config/i386/config.orig 2009-03-09 
19:32:58.0 -0400
+++ linux-2.6-2.6.26/debian/config/i386/config  2009-03-09 19:33:36.0 
-0400
@@ -1637,6 +1637,7 @@
 CONFIG_ADVANTECH_WDT=m
 CONFIG_ALIM1535_WDT=m
 CONFIG_ALIM7101_WDT=m
+CONFIG_GEODE_WDT=m
 CONFIG_SC520_WDT=m
 CONFIG_EUROTECH_WDT=m
 CONFIG_IB700_WDT=m




thank you

-- 
sg
--- linux-2.6-2.6.26/debian/config/i386/config.orig	2009-03-09 19:32:58.0 -0400
+++ linux-2.6-2.6.26/debian/config/i386/config	2009-03-09 19:33:36.0 -0400
@@ -1637,6 +1637,7 @@
 CONFIG_ADVANTECH_WDT=m
 CONFIG_ALIM1535_WDT=m
 CONFIG_ALIM7101_WDT=m
+CONFIG_GEODE_WDT=m
 CONFIG_SC520_WDT=m
 CONFIG_EUROTECH_WDT=m
 CONFIG_IB700_WDT=m

Bug#509992: Invalid bug

[Ioannis Ramfos]

Please close this bug as it was caused due to a bad RAM chip and is invalid. 
As it seems the kernel modules were always loaded at the same (bad) physical 
addresses and the same errors were repeated each time.

Sorry for the confusion.



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

[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #517421
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
#  * remote status changed: (?) -> NEW
usertags 517421 + status-NEW

# remote status report for #517421
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
#  * remote status changed: (?) -> NEW
usertags 517421 + status-NEW

# remote status report for #517421
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
#  * remote status changed: (?) -> NEW
usertags 517421 + status-NEW

# remote status report for #517421
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
#  * remote status changed: (?) -> NEW
usertags 517421 + status-NEW

# remote status report for #517193
#  * http://bugzilla.kernel.org/show_bug.cgi?id=12520
#  * remote status changed: (?) -> CLOSED
#  * remote resolution changed: (?) -> CODE-FIX
#  * closed upstream
tags 517193 + fixed-upstream
usertags 517193 + status-CLOSED resolution-CODE-FIX

# remote status report for #517421
#  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
#  * remote status changed: (?) -> NEW
usertags 517421 + status-NEW

# remote status report for #517892
#  * http://bugzilla.openvz.org/show_bug.cgi?id=974
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
forwarded 517892 http://bugzilla.openvz.org/show_bug.cgi?id=1205, 
merged-upstream: http://bugzilla.openvz.org/show_bug.cgi?id=974
tags 517892 + fixed-upstream
usertags 517892 + status-RESOLVED resolution-FIXED

thanks


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

Processed: [bts-link] source package linux-2.6

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #517421
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
> #  * remote status changed: (?) -> NEW
> usertags 517421 + status-NEW
Bug#517421: linux-image-2.6.28-1-686: Kernel log full of SKB BUG
There were no usertags set.
Usertags are now: status-NEW.
> # remote status report for #517421
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
> #  * remote status changed: (?) -> NEW
> usertags 517421 + status-NEW
Bug#517421: linux-image-2.6.28-1-686: Kernel log full of SKB BUG
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #517421
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
> #  * remote status changed: (?) -> NEW
> usertags 517421 + status-NEW
Bug#517421: linux-image-2.6.28-1-686: Kernel log full of SKB BUG
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #517421
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
> #  * remote status changed: (?) -> NEW
> usertags 517421 + status-NEW
Bug#517421: linux-image-2.6.28-1-686: Kernel log full of SKB BUG
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #517193
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=12520
> #  * remote status changed: (?) -> CLOSED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 517193 + fixed-upstream
Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64
Tags were: upstream
Tags added: fixed-upstream

> usertags 517193 + status-CLOSED resolution-CODE-FIX
Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64
There were no usertags set.
Usertags are now: resolution-CODE-FIX status-CLOSED.
> # remote status report for #517421
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=10996
> #  * remote status changed: (?) -> NEW
> usertags 517421 + status-NEW
Bug#517421: linux-image-2.6.28-1-686: Kernel log full of SKB BUG
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #517892
> #  * http://bugzilla.openvz.org/show_bug.cgi?id=974
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> forwarded 517892 http://bugzilla.openvz.org/show_bug.cgi?id=1205, 
> merged-upstream: http://bugzilla.openvz.org/show_bug.cgi?id=974
Bug#517892: linux-image-2.6.26-1-openvz-amd64: IPv6 tunnels through sit 
v4tunnels not possible
Forwarded-to-address changed from 
http://bugzilla.openvz.org/show_bug.cgi?id=1205 to 
http://bugzilla.openvz.org/show_bug.cgi?id=1205, merged-upstream: 
http://bugzilla.openvz.org/show_bug.cgi?id=974.

> tags 517892 + fixed-upstream
Bug#517892: linux-image-2.6.26-1-openvz-amd64: IPv6 tunnels through sit 
v4tunnels not possible
There were no tags set.
Tags added: fixed-upstream

> usertags 517892 + status-RESOLVED resolution-FIXED
Bug#517892: linux-image-2.6.26-1-openvz-amd64: IPv6 tunnels through sit 
v4tunnels not possible
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> 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

Re: lenny updates (netfilter)

[Kir Kolyshkin]

Kir Kolyshkin wrote:
I am currently checking all the ~80 patches that are not in openvz 
lenny kernel. Looks like most are really needed. Let me suggest some 
in a few emails I will send as a reply to this one.


Here is a set of netfilter patches, quite a few. Some are very critical 
(read security-related) since they fix various container/host isolation 
issues, others are to prevent kernel oopses...


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=8562975430153848dd817a050133b53adda96910
nf: fix use after free
Fix use after free error, found by internal testing. Not an ABI breaker.
Attached as 0010*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=fa7ac0b2423dc741cd7016565545abb8e36c4af4
nf: fix call to kmem_cache_destroy from VEs
Found by internal testing. Not an ABI breaker.
Attached as 0011*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=17b09e1de42db77743ea9ae3dfd3a910ac57ee71
conntrack: prevent double allocate/free of protos
Found by internal testing. Not an ABI breaker.
Attached as 0022*

http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=7d3f10fc5d8e268f7572cfdd2287c049bce3af7c
conntrack: prevent call register_pernet_subsys() from VE context
Found by internal audit. Not an ABI breaker.
Attached as 0023*

http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=482dd20be37f61b2f94e6b3f3de1c1b9b4f9e6f1
conntrack: prevent call nf_register_hooks() from VE context
Found by internal audit. Not an ABI breaker.
Attached as 0024*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=5fff3eb60f78acaadcae8562de5d3e6504f4d4f9
conntrack: adjust context during freeing
Found by internal audit. Not an ABI breaker.
Attached as 0029*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=3cb8bc3781889ade74c02840b2eb8ddafb6d39c5
netfilter: NAT: assign nf_nat_seq_adjust_hook from VE0 context only
Found by internal audit. Not an ABI breaker.
Attached as 0033*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=490910232ebe61f65e5e5c03b7286f11291b6092
netfilter: call nf_register_hooks from VE0 context only
Found by internal audit. Not an ABI breaker.
Attached as 0034*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=1acba8533b788e95c52f827d06d9629d672c80fc
netfilter: Fix NULL dereference in nf_nat_setup_info.
OpenVZ Bug #1051 (http://bugzilla.openvz.org/1051). Might be an ABI breaker.
Attached as 0047*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=b405aed753ac48a46e66cccfd0a37006fd11feb8
netfilter: Add check to the nat hooks
OpenVZ Bug #1051 (http://bugzilla.openvz.org/1051). Might be an ABI breaker.
Attached as 0048*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=b5e1f74cee5bc2c45bdca53a7218fb8de89215dd
netlink: Fix oops in netlink conntrack module
OpenVZ bug #788 (http://bugzilla.openvz.org/788)
Attached as 0053*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=09686c184a2cb815cbd5af500fe468311887d746
Free skb->nf_bridge in veth_xmit() and venet_xmit()
OpenVZ bug #1146 (http://bugzilla.openvz.org/1146)
Attached as 0066*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=
http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=
http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=

>From 8562975430153848dd817a050133b53adda96910 Mon Sep 17 00:00:00 2001
From: Vitaliy Gusev 
Date: Wed, 27 Aug 2008 19:36:28 +0400
Subject: [PATCH] nf: fix use after free

Fix use after free error: move freeing ve_nf_conntrack_l4proto_generic
to nf_ct_proto_generic_sysctl_cleanup().

Signed-off-by: Vitaliy Gusev 
Signed-off-by: Pavel Emelyanov 
---
 net/netfilter/nf_conntrack_proto.c |4 
 net/netfilter/nf_conntrack_proto_generic.c |2 ++
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/net/netfilter/nf_conntrack_proto.c 
b/net/netfilter/nf_conntrack_proto.c
index 49fc01f..67c53a7 100644
--- a/net/netfilter/nf_conntrack_proto.c
+++ b/net/netfilter/nf_conntrack_proto.c
@@ -358,8 +358,4 @@ void nf_conntrack_proto_fini(void)
/* free l3proto protocol tables */
for (i = 0; i < PF_MAX; i++)
kfree(ve_nf_ct_protos[i]);
-#ifdef CONFIG_VE_IPTABLES
-   if (!ve_is_super(get_exec_env()))
-   kfree(ve_nf_conntrack_l4proto_generic);
-#endif
 }
diff --git a/net/netfilter/nf_conntrack_proto_generic.c 
b/net/netfilter/nf_conntrack_proto_generic.c
index e65f9a7..24b0e29 100644
--- a/net/netfilter/nf_conntrack_proto_generic.c
+++ b/net/netfilter/nf_conntrack_proto_generic.c
@@ -163,6 +163,8 @@ void nf_ct_proto_generic_sysctl_cleanup(void)
kfree(ve_nf_conntrack_l4proto_generic->ctl_compat_table);
 #endif
kfree(ve_nf_conntrack_l4proto_generic->ctl_table);
+
+   kfree(ve_nf_conntrack_l4proto_generic);
}
 }
 EXPORT_SYMBOL(nf_ct_proto_generic_sysctl_cleanup);
-- 
1.6.0.6

>From fa7ac0b2423dc741cd7016565545abb8e36c4af4 Mon Sep 17 00:00:00 2001
From: Vitaliy Gusev 
Date: Wed, 27 A

Processed: severity of 518961 is important

[Debian Bug Tracking System]

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

> severity 518961 important
Bug#518961: linux-kbuild-2.6.26: Typo in modpost wrapper src/mod/modpost.c
Severity set to `important' from `serious'

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#519028: [linux-image-686] Broken dependency

[Mazen NEIFER]

Package: linux-image-686
Version: 2.6.26+17
Severity: serious

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

The description reads:

   This package depends on the latest binary image for Linux kernel on
   Pentium Pro/Celeron/Pentium II/Pentium III/Pentium 4 machines.

This package depends on linux-image-2.6.26-1-686 version 2.6.23-13 which is 
marked as obsolete while the latest kernel is packaged as 
linux-image-2.6.28-1-686 with version 2.6.28-1.

The linux-image-686 should no more depend on linux-image-2.6.26-1-686 bu on 
linux-image-2.6.28-1-686.

cheers,
Mazen,

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

Debian Release: squeeze/sid
  500 unstableftp.fr.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
linux-image-2.6.26-1-686| 2.6.26-13




signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: lenny updates (CPT patches)

[Kir Kolyshkin]

Looks like a few patches are already there, see below. Only 5 CPT 
patches are still left. If you need I can write a new email about CPT 
patches to avoid confusion.


Kir Kolyshkin wrote:

Kir Kolyshkin wrote:
Also, while I am at it... I am currently checking all the ~80 patches 
that are not in openvz lenny kernel. Looks like most are really 
needed. Let me suggest some in a few emails I will send as a reply to 
this one.


Checkpointing-related patches. Needed if we want working 
checkpointing/restart.


1. High-priority patches

http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=d588f384c7a326c049f27cf4d90b949a89c1fe94 


CPT: Use sock_create instead sock_create_kern
Puts sockets in correct net namespace. Pretty trivial, not an ABI 
breaker. Found by internal testing.

Attached as 0001*
Sorry, this one is already included. Harder to track since the patch was 
just added to the end of openvz.patch instead of creating a separate file.



http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=15ce7ef10f52493f94f5438d22a60a60e6bffdb0 


CPT: Fix memory corruption
Found by internal testing. Exports one more function (needed since 
cpt/rst can be build as modules) so can be an ABI breaker.

Attached as 0002*


Ditto.




http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=e744de05b10aeff8289c5d287ed92cbb0438426d 


CPT: Fixed checkpoint error due to skipped mm->exe_file dump
Needed due to changes in 2.6.26 kernel.Found by internal testing. 
Exports one more function so can be an ABI breaker.

Attached as 0006*


Ditto.





http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=6d18ba377cfa3e86ee830fe6a5fce52b8fd51039 


CPT: revert check on sk_reuse>1
This is fix for Debian bug #500645 (OpenVZ bug #1034).
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500645
Attached as 0038-CPT-revert-check-on-sk_reuse-1.patch



http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=029cecb45ceb652b0add04388fcaabe822e83660 


cpt: Make the proper check for sigmask
Trivial fix, not an ABI breaker. Fixes OpenVZ bug #1122
http://bugzilla.openvz.org/show_bug.cgi?id=1122


2. "Not sure those are needed" patches.

http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=ef2def76125ba8753042329df1ede57449de4609 


cpt: Ban fib trie
Pretty trivial. Not really needed if we make sure CONFIG_IP_FIB_TRIE 
is not set in openvz kernel .config, but shouldn't break anything.

Attached as 0012*


Ditto



http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=4fc3a18ab7c46e4bc375fa3ce59b7fb1b173f35b 


cpt: bump image version to VERSION_26
Needed to not confuse the user.
Attached as 0017*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=c00febbae95a18b264fd8ca72b8eef09ef28ae2e 


cpt: Make it module by default
CONFIG_VZ_CHECKPOINT was set to n by default in kernel config. Now 
since it's working we enable it.
Doesn't make much sense for Debian if we set CONFIG_VZ_CHECKPOINT 
explicitly.

Attached as 0019*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=281828bf90ea4e49bf5d8e777b1ec43972bf0949 


cpt: replace BUG_ON-s checking for sizeof-s with BUILD_BUG_ON
Those checks need to be done compile-time not runtime. Mostly needed 
for developers but won't hurt to include.

Attached as 0032*




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

Re: lenny updates (CPT patches)

[Kir Kolyshkin]

Kir Kolyshkin wrote:
Also, while I am at it... I am currently checking all the ~80 patches 
that are not in openvz lenny kernel. Looks like most are really 
needed. Let me suggest some in a few emails I will send as a reply to 
this one.


Checkpointing-related patches. Needed if we want working 
checkpointing/restart.


1. High-priority patches

http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=d588f384c7a326c049f27cf4d90b949a89c1fe94
CPT: Use sock_create instead sock_create_kern
Puts sockets in correct net namespace. Pretty trivial, not an ABI breaker. 
Found by internal testing.
Attached as 0001*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=15ce7ef10f52493f94f5438d22a60a60e6bffdb0
CPT: Fix memory corruption
Found by internal testing. Exports one more function (needed since cpt/rst can 
be build as modules) so can be an ABI breaker.
Attached as 0002*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=e744de05b10aeff8289c5d287ed92cbb0438426d
CPT: Fixed checkpoint error due to skipped mm->exe_file dump
Needed due to changes in 2.6.26 kernel.Found by internal testing. Exports one 
more function so can be an ABI breaker.
Attached as 0006*



http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=6d18ba377cfa3e86ee830fe6a5fce52b8fd51039
CPT: revert check on sk_reuse>1
This is fix for Debian bug #500645 (OpenVZ bug #1034).
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500645
Attached as 0038-CPT-revert-check-on-sk_reuse-1.patch



http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=029cecb45ceb652b0add04388fcaabe822e83660
cpt: Make the proper check for sigmask
Trivial fix, not an ABI breaker. Fixes OpenVZ bug #1122
http://bugzilla.openvz.org/show_bug.cgi?id=1122


2. "Not sure those are needed" patches.

http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=ef2def76125ba8753042329df1ede57449de4609
cpt: Ban fib trie
Pretty trivial. Not really needed if we make sure CONFIG_IP_FIB_TRIE is not set 
in openvz kernel .config, but shouldn't break anything.
Attached as 0012*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=4fc3a18ab7c46e4bc375fa3ce59b7fb1b173f35b
cpt: bump image version to VERSION_26
Needed to not confuse the user.
Attached as 0017*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=c00febbae95a18b264fd8ca72b8eef09ef28ae2e
cpt: Make it module by default
CONFIG_VZ_CHECKPOINT was set to n by default in kernel config. Now since it's 
working we enable it.
Doesn't make much sense for Debian if we set CONFIG_VZ_CHECKPOINT explicitly.
Attached as 0019*


http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=281828bf90ea4e49bf5d8e777b1ec43972bf0949
cpt: replace BUG_ON-s checking for sizeof-s with BUILD_BUG_ON
Those checks need to be done compile-time not runtime. Mostly needed for 
developers but won't hurt to include.
Attached as 0032*

>From d588f384c7a326c049f27cf4d90b949a89c1fe94 Mon Sep 17 00:00:00 2001
From: Vitaliy Gusev 
Date: Mon, 18 Aug 2008 15:10:15 +0400
Subject: [PATCH] CPT: Use sock_create instead sock_create_kern
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

sock_create_kern() uses init_net as default net namespace. Therefore
sockets and net devices are belonged to init_net, though must belong
to current net namespace.

Signed-off-by: Vitaliy Gusev 
Signed-off-by: Pavel Emelyanov 
---
 kernel/cpt/cpt_net.c|2 +-
 kernel/cpt/rst_net.c|2 +-
 kernel/cpt/rst_socket.c |8 
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/kernel/cpt/cpt_net.c b/kernel/cpt/cpt_net.c
index 373db60..78919d8 100644
--- a/kernel/cpt/cpt_net.c
+++ b/kernel/cpt/cpt_net.c
@@ -337,7 +337,7 @@ static int cpt_dump_route(struct cpt_context * ctx)
mm_segment_t oldfs;
char *pg;
 
-   err = sock_create_kern(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE, &sock);
+   err = sock_create(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE, &sock);
if (err)
return err;
 
diff --git a/kernel/cpt/rst_net.c b/kernel/cpt/rst_net.c
index b246ddb..c6be61a 100644
--- a/kernel/cpt/rst_net.c
+++ b/kernel/cpt/rst_net.c
@@ -202,7 +202,7 @@ int rst_restore_route(struct cpt_context *ctx)
if (err < 0)
return err;
 
-   err = sock_create_kern(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE, &sock);
+   err = sock_create(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE, &sock);
if (err)
return err;
 
diff --git a/kernel/cpt/rst_socket.c b/kernel/cpt/rst_socket.c
index d90488e..4963f34 100644
--- a/kernel/cpt/rst_socket.c
+++ b/kernel/cpt/rst_socket.c
@@ -268,13 +268,13 @@ static int open_socket(cpt_object_t *obj, struct 
cpt_sock_image *si,
cpt_object_t *fobj;
cpt_object_t *pobj = NULL;
 
-   err = sock_create_kern(si->cpt_family, si->cpt_type, si->cpt_protocol,
+   err = sock_create(si->cpt_family, si->cpt_type, si->cpt_protocol,
   &sock);
if (err)
 

Critical Temperature

[timo]

Hi people,

I have got the following problem: At random X is being closed by force
and the terminal says «critical temperature reached» and then some high
number around 150°C. At the next moment the computer turns off. That
problem occurs with linux 2.6.27 till 2.6.28 and does not occur with
linux 2.6.26. I have found only a few posts on google. How can I find
out whether this is a software or a hardware issue and what might the
cause be?


regards,
Timo




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

Bug#503097: Fix available for #503097

[Ola Lundqvist]

Hi Carlos

Fix is available for #503097 as part of a test build. Do you have
possibility to verify this one?

Built kernels for test are available here:
http://people.debian.org/~dannf/bugs/500876/

Best regards,

// Ola

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comAnnebergsslingan 37\
|  o...@debian.org   654 65 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---



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

Re: lenny updates

[Ola Lundqvist]

Hi Dann

I have to ask Kir about some of the things. Kir, please comment on the below.

On Mon, Mar 09, 2009 at 01:42:10PM -0600, dann frazier wrote:
[...]
> > > > #511165:
> > > > Patch exist for 2.6.24 and 2.6.26. Fix is available in
> > > > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=b5e1f74cee5bc2c45bdca53a7218fb8de89215dd
> > > > Not sure if this is an ABI breaker.
> > > 
> > > Seems straightforward, and shouldn't change the ABI. I'll commit it
> > > assuming my test build shows that.
> > 
> > This tells me that there is an easy way to check that. How is that done?
> > I assume some files are compared, but I can not find that in the debian 
> > directory (without building).
> 
> This is just based on looking at the patch - I don't see anything
> there that would change an exported symbol. Things to look for
> structure definition changes, or changes to exported function calls.
> Adding/removing includes can also have non-obvious effects.

Ok, I see.

> My test build did succeed, and this change has been committed.

Great.

> > > > #500876:
> > > > Fix available in:
> > > > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=777e8164ebf8a03e43511983cdec472f8691a8af
> > > > Problem is about to be verified. Regression tested without problems 
> > > > seen.
> > > 
> > > I couldn't reproduce this one (tried dual quad core intel server & a
> > > single quad core amd), but user claims this fixed the bug for me and I
> > > haven't seen any issues with this patch so its been committed.
> > 
> > I think you need to have a quad-core amd64 for this. But let us commit it
> > as it do not seem to hurt.
> 
> I tried on a quad-core/one socket amd64, but maybe it requires
> multiple sockets?

Or this is only occurs on selected boards. This kind of time critial faults can 
be
tricky.

> > > > #503097:
> > > > Reported as http://bugzilla.openvz.org/show_bug.cgi?id=930
> > > > Seems to be a duplicate of #500876 above.
> > > 
> > > Cool. If you think so, it might be good to have Carlos test one of
> > > these builds to verify:
> > >   http://people.debian.org/~dannf/bugs/500876/
> > 
> > Ok, I'll ask him at once.
> 
> Thanks!

Done now.

[...]
> come with a risk of regression, and its easier to regression test
> specific changes.
> 
> > > > #508773:
> > > > Patch available in http://bugzilla.openvz.org/show_bug.cgi?id=1054
> > > > Fix in 
> > > > http://git.openvz.org/?p=linux-2.6.24-openvz;a=commit;h=20bd90762d4df4a3c7c247b660c696bdd0a27709
> > > > Do not look like an ABI breaker to me.
> > > 
> > > Yep, definitely shouldn't break the ABI, and seems like a good
> > > candidate.
> > 
> > Good. Please tell if you want me to prepare some patch or check in 
> > something.
> 
> Patches that apply directly to kernel svn are certainly
> welcome. Normally, that should mean adding a changelog entry, a series
> file entry, and a new patch file.
> 
> This one is pretty trivial, so I'll go ahead and generate a changeset
> to commit - but it would be great if you could ensure that the
> snapshot builds get regression tested after they become available.

Ok, thanks. I'll promise to regression test soon after you tell me that the 
build
is complete.

> > > > #500145:
> > > > Forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1143
> > > > Marked as dupliate of http://bugzilla.openvz.org/show_bug.cgi?id=1067
> > > > Not solved yet.
> > > 
> > > ok
> > > 
> > > > #501985:
> > > > From: maximilian attems
> > > > the upstream nfs fixes are abi breakers and thus can't be integrated
> > > > at this point they will be for the first point release were abi
> > > > breaking will be allowed again.
> > > 
> > > What is the fix for this - does upstream openvz include it?
> > 
> > Yes it is found upstream. See the file
> > http://download.openvz.org/kernel/branches/2.6.26/current/patches/patch-chekhov.1-combined.gz
> > The current patch do not touch any nfs/ files and upstream does. The patch
> > now in use was not fully completed when it was incorporated by Maximilian.
> 
> I see - so we need to identify which additional changes are needed.
> http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=66ec7f7f493fb98e8baa6591e9225086ae640fb8
> http://git.openvz.org/?p=linux-2.6.26-openvz;a=commitdiff;h=39bb1ee59237272cd20e1f8696cefbd6a787cfc8
> 
> Is this severe enough to fix in a stable release? If we consider this
> a regression from etch (since kernel-patch-openvz supplied this), than
> maybe so. Is the risk of regression low? Well - these patches would
> only get applied on openvz kernels which currently don't support nfs
> at all so, assuming these changes are nfs-specific, risk should be
> low.

This is where I need to ask Kir. Kir do you know the answer to this question?

[...]

Best regards,

// Ola

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comAnnebergsslingan 37\
|  o...@debian.org   654 65 KARLSTAD|
|  http://inguza.com/ 

Bug#518995: kernel: RAM recognition

[pawel]

Package: kernel
Severity: normal

system don't recognize more than 895MB of system memory (physical) - i must 
install kernel with bigmem; when i've added next 
2GB RAM, system still have seen 895MB RAM


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

Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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

Processed: Re: Bug#518995: kernel: RAM recognition

[Debian Bug Tracking System]

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

> reassign 518995 linux-2.6
Bug#518995: kernel: RAM recognition
Warning: Unknown package 'kernel'
Bug reassigned from package `kernel' to `linux-2.6'.

> --
Stopping processing here.

Please contact me if you need assistance.

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


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

Re: lenny updates

[dann frazier]

On Mon, Mar 09, 2009 at 08:13:28PM +0100, Ola Lundqvist wrote:
> Hi Dann
> 
> On Sun, Mar 08, 2009 at 11:17:09PM -0600, dann frazier wrote:
> > On Tue, Mar 03, 2009 at 09:44:04PM +0100, Ola Lundqvist wrote:
> > > Hi Dann
> > > 
> > > You asked about the latest status and here it is.
> > > Please tell which ones you want me to fix for the next lenny release of 
> > > the kernel. I'll prepare
> > > a patch and regression test that version for you.
> > > 
> > > #510787:
> > > Refers to an other bug report that was not openvz specific. Should it be
> > > forwarded to an non-openvz version of the kernel or kept here?
> > 
> > I don't think it really matters - you can reassign to linux-2.6 if you
> > like though.
> 
> Done that now.
> 
> > > In any case I have added latest information to the report and told where
> > > the problem has been forwarded.
> > 
> > Thanks!
> > 
> > > #511165:
> > > Patch exist for 2.6.24 and 2.6.26. Fix is available in
> > > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=b5e1f74cee5bc2c45bdca53a7218fb8de89215dd
> > > Not sure if this is an ABI breaker.
> > 
> > Seems straightforward, and shouldn't change the ABI. I'll commit it
> > assuming my test build shows that.
> 
> This tells me that there is an easy way to check that. How is that done?
> I assume some files are compared, but I can not find that in the debian 
> directory (without building).

This is just based on looking at the patch - I don't see anything
there that would change an exported symbol. Things to look for
structure definition changes, or changes to exported function calls.
Adding/removing includes can also have non-obvious effects.

My test build did succeed, and this change has been committed.

> > > #500876:
> > > Fix available in:
> > > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=777e8164ebf8a03e43511983cdec472f8691a8af
> > > Problem is about to be verified. Regression tested without problems seen.
> > 
> > I couldn't reproduce this one (tried dual quad core intel server & a
> > single quad core amd), but user claims this fixed the bug for me and I
> > haven't seen any issues with this patch so its been committed.
> 
> I think you need to have a quad-core amd64 for this. But let us commit it
> as it do not seem to hurt.

I tried on a quad-core/one socket amd64, but maybe it requires
multiple sockets?

> > > #503097:
> > > Reported as http://bugzilla.openvz.org/show_bug.cgi?id=930
> > > Seems to be a duplicate of #500876 above.
> > 
> > Cool. If you think so, it might be good to have Carlos test one of
> > these builds to verify:
> >   http://people.debian.org/~dannf/bugs/500876/
> 
> Ok, I'll ask him at once.

Thanks!

> > (Tomorrow's snapshot builds should also include it)
> > 
> > > #505174:
> > > This is a request to go up to the latest version that includes fixes for
> > > all the ones in this mail that describe that there is a fix available.
> > > Unfortunatly there are ABI breakers...
> > 
> > Its probably a good idea to stick with specific issues/fixes now that
> > its a stable release.
> 
> Maybe so. The openvz development team has proven to provide quite well
> tested kernels. However the safer approach may still be to stick to the
> specific issues.

Yeah, I certainly don't mistrust the openvz team - but all changes
come with a risk of regression, and its easier to regression test
specific changes.

> > > #508773:
> > > Patch available in http://bugzilla.openvz.org/show_bug.cgi?id=1054
> > > Fix in 
> > > http://git.openvz.org/?p=linux-2.6.24-openvz;a=commit;h=20bd90762d4df4a3c7c247b660c696bdd0a27709
> > > Do not look like an ABI breaker to me.
> > 
> > Yep, definitely shouldn't break the ABI, and seems like a good
> > candidate.
> 
> Good. Please tell if you want me to prepare some patch or check in something.

Patches that apply directly to kernel svn are certainly
welcome. Normally, that should mean adding a changelog entry, a series
file entry, and a new patch file.

This one is pretty trivial, so I'll go ahead and generate a changeset
to commit - but it would be great if you could ensure that the
snapshot builds get regression tested after they become available.

> > > #500145:
> > > Forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1143
> > > Marked as dupliate of http://bugzilla.openvz.org/show_bug.cgi?id=1067
> > > Not solved yet.
> > 
> > ok
> > 
> > > #501985:
> > > From: maximilian attems
> > > the upstream nfs fixes are abi breakers and thus can't be integrated
> > > at this point they will be for the first point release were abi
> > > breaking will be allowed again.
> > 
> > What is the fix for this - does upstream openvz include it?
> 
> Yes it is found upstream. See the file
> http://download.openvz.org/kernel/branches/2.6.26/current/patches/patch-chekhov.1-combined.gz
> The current patch do not touch any nfs/ files and upstream does. The patch
> now in use was not fully completed when it was incorporated by Maximilian.

I see - so we need to identify which add

Re: lenny updates

[Ola Lundqvist]

Hi Dann

On Sun, Mar 08, 2009 at 11:17:09PM -0600, dann frazier wrote:
> On Tue, Mar 03, 2009 at 09:44:04PM +0100, Ola Lundqvist wrote:
> > Hi Dann
> > 
> > You asked about the latest status and here it is.
> > Please tell which ones you want me to fix for the next lenny release of the 
> > kernel. I'll prepare
> > a patch and regression test that version for you.
> > 
> > #510787:
> > Refers to an other bug report that was not openvz specific. Should it be
> > forwarded to an non-openvz version of the kernel or kept here?
> 
> I don't think it really matters - you can reassign to linux-2.6 if you
> like though.

Done that now.

> > In any case I have added latest information to the report and told where
> > the problem has been forwarded.
> 
> Thanks!
> 
> > #511165:
> > Patch exist for 2.6.24 and 2.6.26. Fix is available in
> > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=b5e1f74cee5bc2c45bdca53a7218fb8de89215dd
> > Not sure if this is an ABI breaker.
> 
> Seems straightforward, and shouldn't change the ABI. I'll commit it
> assuming my test build shows that.

This tells me that there is an easy way to check that. How is that done?
I assume some files are compared, but I can not find that in the debian 
directory (without building).

> > #500876:
> > Fix available in:
> > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=777e8164ebf8a03e43511983cdec472f8691a8af
> > Problem is about to be verified. Regression tested without problems seen.
> 
> I couldn't reproduce this one (tried dual quad core intel server & a
> single quad core amd), but user claims this fixed the bug for me and I
> haven't seen any issues with this patch so its been committed.

I think you need to have a quad-core amd64 for this. But let us commit it
as it do not seem to hurt.

> > #503097:
> > Reported as http://bugzilla.openvz.org/show_bug.cgi?id=930
> > Seems to be a duplicate of #500876 above.
> 
> Cool. If you think so, it might be good to have Carlos test one of
> these builds to verify:
>   http://people.debian.org/~dannf/bugs/500876/

Ok, I'll ask him at once.

> (Tomorrow's snapshot builds should also include it)
> 
> > #505174:
> > This is a request to go up to the latest version that includes fixes for
> > all the ones in this mail that describe that there is a fix available.
> > Unfortunatly there are ABI breakers...
> 
> Its probably a good idea to stick with specific issues/fixes now that
> its a stable release.

Maybe so. The openvz development team has proven to provide quite well
tested kernels. However the safer approach may still be to stick to the
specific issues.

> > #508773:
> > Patch available in http://bugzilla.openvz.org/show_bug.cgi?id=1054
> > Fix in 
> > http://git.openvz.org/?p=linux-2.6.24-openvz;a=commit;h=20bd90762d4df4a3c7c247b660c696bdd0a27709
> > Do not look like an ABI breaker to me.
> 
> Yep, definitely shouldn't break the ABI, and seems like a good
> candidate.

Good. Please tell if you want me to prepare some patch or check in something.

> > #500145:
> > Forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1143
> > Marked as dupliate of http://bugzilla.openvz.org/show_bug.cgi?id=1067
> > Not solved yet.
> 
> ok
> 
> > #501985:
> > From: maximilian attems
> > the upstream nfs fixes are abi breakers and thus can't be integrated
> > at this point they will be for the first point release were abi
> > breaking will be allowed again.
> 
> What is the fix for this - does upstream openvz include it?

Yes it is found upstream. See the file
http://download.openvz.org/kernel/branches/2.6.26/current/patches/patch-chekhov.1-combined.gz
The current patch do not touch any nfs/ files and upstream does. The patch
now in use was not fully completed when it was incorporated by Maximilian.

> > #494445:
> > There are a number of problems in this area. Fixes are available.
> > However some of them are ABI breakers.
> 
> The nf_conntrack_ipv6 module doesn't appear to be in 2.6.26-13. Maybe
> it was disabled because of this bug? At this point, turning it
> on/fixing probably falls into the category of a feature requests that
> doesn't enable hardware, so wouldn't have a sufficient severity (>=
> important).

True.

> > #500645:
> > Fix available in http://bugzilla.openvz.org/show_bug.cgi?id=1034
> > http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=6d18ba377cfa3e86ee830fe6a5fce52b8fd51039
> > I can not see that this is an ABI breaker, so it should be possibly to
> > apply this one without problem.
> 
> The patch itself certainly looks trivial enough - but the bug is only of
> severity "normal". If we think this actually deserves a >= important
> severity, we should bump the severity of the report.

Yes this one is really important. I'll change the severity now.

Best regards,

// Ola

> Thanks Ola!
> 
> -- 
> dann frazier
> 
> 

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comAnnebergsslingan 37\
|  o...@debian.org

Processed: reassign 510787

[Debian Bug Tracking System]

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

> reassign 510787 linux-2.6
Bug#510787: Closed #496188 appear again in 2.6.26-12 SID and Lenny
Bug reassigned from package `linux-image-2.6.26-1-openvz-amd64' to `linux-2.6'.

> severity 500645 important
Bug#500645: linux-image-2.6.26-1-openvz-686: OpenVZ checkpointing does not work
Severity set to `important' from `normal'

> 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

Bug#515508: linux-image-2.6.28-1-amd64: Microsoft Natural keyboard is not functioning

[Alex Dănilă]

Yup,
it solves it, and boots 15 sec. faster :) . Are there any grave problems 
(like fs corruption)?, because I would stick with this kernel.


Alex.

maximilian attems wrote:

can you please check 2.6.29-rc7 from trunk, see apt lines
http://wiki.debian.org/DebianKernel

  





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

Bug#518985: linux-image-2.6.28-1-amd64: module ath9k doesn't work

[Pierre Meurisse]

Package: linux-image-2.6.28-1-amd64
Version: 2.6.28-2~snapshot.12850
Severity: important

My wifi Intel-Atheros interface doesn't connect.

p...@co64sid~% sudo /etc/init.d/networking restart
Reconfiguring network interfaces...There is already a pid file
/var/run/dhclient.wlan0.pid with pid 4723
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:22:43:22:b8:de
Sending on   LPF/wlan0/00:22:43:22:b8:de
Sending on   Socket/fallback
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:22:43:22:b8:de
Sending on   LPF/wlan0/00:22:43:22:b8:de
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.


My /etc/network/interfaces :
# The loopback network interface
auto lo
iface lo inet loopback

# wifi
auto wlan0
iface wlan0 inet dhcp
pre-up /sbin/ifconfig wlan0 up  #   tried with and without that line
wpa-conf managed
wpa-ssid my_essid
# wpa-key-mgmt WPA-PSK
wpa-psk _my key_



I tried linux-image-2.6.29-rc7-amd64 too ; it doesn't work either.


The ethernet interface doesn't work with sis190 ; but works in 32 bits mode
( vmlinuz-2.6.28-1-686 )



ath9k works with ubuntu 8.10 on the same machine,
kernel vmlinuz-2.6.27-11-generic





-- Package-specific info:
** Version:
Linux version 2.6.28-1-amd64 (Debian 2.6.28-2~snapshot.12850) 
(wa...@debian.org) (gcc version 4.3.3 (GCC) ) #1 SMP Thu Feb 19 03:12:18 UTC 
2009

** Command line:
root=/dev/sda9 ro 

** Not tainted

** Kernel log:
[3.427710] sr 1:0:0:0: Attached scsi generic sg1 type 5
[3.468042] usb 1-1: new low speed USB device using ohci_hcd and address 4
[3.672422] usb 1-1: configuration #1 chosen from 1 choice
[3.675367] usb 1-1: New USB device found, idVendor=0461, idProduct=4d03
[3.675438] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[3.689828] usbcore: registered new interface driver hiddev
[3.706963] input: HID 0461:4d03 as 
/devices/pci:00/:00:03.0/usb1/1-1/1-1:1.0/input/input2
[3.721099] generic-usb 0003:0461:4D03.0001: input,hidraw0: USB HID v1.00 
Mouse [HID 0461:4d03] on usb-:00:03.0-1/input0
[3.721205] usbcore: registered new interface driver usbhid
[3.721272] usbhid: v2.6:USB HID core driver
[4.426616] device-mapper: uevent: version 1.0.3
[4.426789] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: 
dm-de...@redhat.com
[4.501291] PM: Starting manual resume from disk
[4.579190] kjournald starting.  Commit interval 5 seconds
[4.579275] EXT3-fs: mounted filesystem with ordered data mode.
[5.886655] udevd version 125 started
[6.149407] input: Power Button (FF) as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[6.180046] ACPI: Power Button (FF) [PWRF]
[6.180240] input: Power Button (CM) as 
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
[6.184903] ACPI: AC Adapter [AC0] (on-line)
[6.196099] ACPI: Power Button (CM) [PWRB]
[6.196437] input: Sleep Button (CM) as 
/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input5
[6.212051] ACPI: Sleep Button (CM) [SLPB]
[6.212270] input: Lid Switch as 
/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input6
[6.245574] ACPI: Lid Switch [LID]
[6.252454] ACPI: Battery Slot [BAT0] (battery present)
[6.275534] acpi device:19: registered as cooling_device2
[6.275744] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:15/device:16/input/input7
[6.296156] ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
[6.402081] asus-laptop: Asus Laptop Support version 0.42
[6.407538] asus-laptop:   X71SL model detected
[6.415365] asus-laptop: Brightness ignored, must be controlled by ACPI 
video driver
[6.415485] Registered led device: asus::mail
[6.415561] Registered led device: asus::touchpad
[6.785949] Linux video capture interface: v2.00
[7.276063] cfg80211: Using static regulatory domain info
[7.276141] cfg80211: Regulatory domain: US
[7.276205]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
max_eirp)
[7.276286]  (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm)
[7.

Bug#518467: linux-image-2.6.28-1-amd64: bluetooth mouse stutters since kernel upgrade

[maximilian attems]

On Mon, Mar 09, 2009 at 06:08:30PM +0100, pHilipp Zabel wrote:
> On Mon, Mar 9, 2009 at 1:04 PM, maximilian attems  wrote:
> > On Fri, 06 Mar 2009, pHilipp Zabel wrote:
> >
> >> On Fri, Mar 6, 2009 at 1:12 PM, Bastian Blank  wrote:
> >> > On Fri, Mar 06, 2009 at 12:41:25PM +0100, pHilipp Zabel wrote:
> >> >> ** Tainted: P M (17)
> >> >
> >> > You have a proprietary module loaded, we don't support kernels in this
> >> > state. Also the kernel logged machine checks, aka low level hardware
> >> > errors, which often shows serious hardware problems.
> >> >
> >> > Bastian
> >>
> >> I installed mcelog, changed the video driver from fglrx to vesa and
> >> rebooted, same result. (/var/log/mcelog is empty.)
> >>
> >
> > could you test if 2.6.29-rc7 trunk builds fix it for you:
> > see apt line http://wiki.debian.org/DebianKernel
> 
> The problem persists. 2.6.26-1 works, 2.6.28-1 and 2.6.29-rc7 don't.
> Here is a log of the evdev output and a hcidump. The delays already
> appear in the hcidump:
 
ok i see, please report upstream with this dump on bugzilla.kernel.org
and let us know the bug number.

thanks a lot for quick reaction

kind regards

-- 
maks



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

Bug#518467: linux-image-2.6.28-1-amd64: bluetooth mouse stutters since kernel upgrade

[pHilipp Zabel]

On Mon, Mar 9, 2009 at 1:04 PM, maximilian attems  wrote:
> On Fri, 06 Mar 2009, pHilipp Zabel wrote:
>
>> On Fri, Mar 6, 2009 at 1:12 PM, Bastian Blank  wrote:
>> > On Fri, Mar 06, 2009 at 12:41:25PM +0100, pHilipp Zabel wrote:
>> >> ** Tainted: P M (17)
>> >
>> > You have a proprietary module loaded, we don't support kernels in this
>> > state. Also the kernel logged machine checks, aka low level hardware
>> > errors, which often shows serious hardware problems.
>> >
>> > Bastian
>>
>> I installed mcelog, changed the video driver from fglrx to vesa and
>> rebooted, same result. (/var/log/mcelog is empty.)
>>
>
> could you test if 2.6.29-rc7 trunk builds fix it for you:
> see apt line http://wiki.debian.org/DebianKernel

The problem persists. 2.6.26-1 works, 2.6.28-1 and 2.6.29-rc7 don't.
Here is a log of the evdev output and a hcidump. The delays already
appear in the hcidump:

$ evdump /dev/input/event5
"Logitech Bluetooth Mouse"
1236346186.343760   EV_REL  REL_X   1
1236346186.343769   EV_SYN  SYN_REPORT  0
1236346186.371714   EV_REL  REL_X   2
1236346186.371716   EV_REL  REL_Y   2
1236346186.371721   EV_SYN  SYN_REPORT  0
1236346186.392694   EV_REL  REL_X   6
1236346186.392695   EV_REL  REL_Y   1
1236346186.392701   EV_SYN  SYN_REPORT  0
1236346186.416740   EV_REL  REL_X   11
1236346186.416743   EV_REL  REL_Y   3
1236346186.416747   EV_SYN  SYN_REPORT  0
1236346186.445663   EV_REL  REL_X   4
1236346186.445674   EV_SYN  SYN_REPORT  0
1236346186.467705   EV_REL  REL_X   8
1236346186.467712   EV_SYN  SYN_REPORT  0
1236346186.487680   EV_REL  REL_X   9
1236346186.487686   EV_SYN  SYN_REPORT  0
1236346186.503748   EV_REL  REL_X   19
1236346186.503755   EV_SYN  SYN_REPORT  0
1236346186.527674   EV_REL  REL_X   3
1236346186.527680   EV_SYN  SYN_REPORT  0
1236346186.591669   EV_REL  REL_X   100 <==
1236346186.591672   EV_REL  REL_Y   -2
1236346186.591676   EV_SYN  SYN_REPORT  0
1236346186.613657   EV_REL  REL_X   6
1236346186.613662   EV_SYN  SYN_REPORT  0
1236346186.641710   EV_REL  REL_X   11
1236346186.641713   EV_REL  REL_Y   -1
1236346186.641717   EV_SYN  SYN_REPORT  0
1236346186.672653   EV_REL  REL_X   4
1236346186.672659   EV_SYN  SYN_REPORT  0
1236346186.703653   EV_REL  REL_X   14
1236346186.703659   EV_SYN  SYN_REPORT  0
1236346186.717644   EV_REL  REL_X   2
1236346186.717649   EV_SYN  SYN_REPORT  0
1236346186.742692   EV_REL  REL_X   8
1236346186.742698   EV_SYN  SYN_REPORT  0
1236346186.760681   EV_REL  REL_X   6
1236346186.760684   EV_REL  REL_Y   -1
1236346186.760687   EV_SYN  SYN_REPORT  0
1236346186.777644   EV_REL  REL_X   6
1236346186.777649   EV_SYN  SYN_REPORT  0
1236346186.797634   EV_REL  REL_X   5
1236346186.797639   EV_SYN  SYN_REPORT  0
1236346186.837297   EV_REL  REL_X   6
1236346186.837302   EV_SYN  SYN_REPORT  0
1236346186.881666   EV_REL  REL_X   -1
1236346186.881671   EV_SYN  SYN_REPORT  0
1236346186.905627   EV_REL  REL_X   -2
1236346186.905633   EV_SYN  SYN_REPORT  0
1236346186.936625   EV_REL  REL_X   -8
1236346186.936628   EV_SYN  SYN_REPORT  0
1236346186.960664   EV_REL  REL_X   -3
1236346186.960669   EV_SYN  SYN_REPORT  0
1236346186.976653   EV_REL  REL_X   -7
1236346186.976658   EV_SYN  SYN_REPORT  0
1236346187.001618   EV_REL  REL_X   -9
1236346187.001619   EV_REL  REL_Y   1
1236346187.001626   EV_SYN  SYN_REPORT  0
1236346187.022603   EV_REL  REL_X   -105<==
1236346187.022604   EV_REL  REL_Y   6
1236346187.022607   EV_SYN  SYN_REPORT  0
1236346187.051709   EV_REL  REL_X   -9
1236346187.051724   EV_SYN  SYN_REPORT  0
1236346187.073604   EV_REL  REL_X   -31
1236346187.073608   EV_REL  REL_Y   1
1236346187.073611   EV_SYN  SYN_REPORT  0
1236346187.098610   EV_REL  REL_X   -4
1236346187.098616   EV_SYN  SYN_REPORT  0
1236346187.116595   EV_REL  REL_X   -18
1236346187.116599   EV_SYN  SYN_REPORT  0
1236346187.137648   EV_REL  REL_X   -22
1236346187.137654   EV_SYN  SYN_REPORT  0
1236346187.153597   EV_REL  REL_X   -29
1236346187.153603   EV_SYN  SYN_REPORT  0
1236346187.206568   EV_REL  REL_X   -90
1236346187.206572   EV_REL  REL_Y   6
1236346187.206575   EV_SYN  SYN_REPORT  0
1236346187.238583   EV_REL  REL_X   -2
1236346187.238588   EV_SYN  SYN_REPORT  0
1236346187.256643   EV_REL  REL_X   -3
1236346187.256649   EV_SYN  SYN_REPORT  0
1236346187.285596   EV_REL  REL_X   -3
1236346187.285603   EV_SYN  SYN_REPORT  0
1236346187.316555   EV_REL  REL_X   -2
1236346187.316559   EV_REL  REL_Y   -1
1236346187.316562   EV_SYN  SYN_REPORT  0
1236346187.333550   EV_R

Bug#518358: linux-image-2.6.28: iwlwifi: iwl3945 failed after suspend and no roaming

[maximilian attems]

On Mon, Mar 09, 2009 at 03:54:47PM +0100, Daniel wrote:
> maximilian attems a écrit :
> >On Fri, 06 Mar 2009, Daniel Huhardeaux wrote:
> >
> >  
> >>[...]
> >>
> >>
> >>>It change something from 2.6.28: when I ifdown wlan0 I can get ifup
> >>>working correctly without rmmod/modprobe iwl3945 module.
> >>>  
> >>Have to correct this: it's only working if I try to reconnect to the  
> >>_same_ AP. If I ifdown from one AP and try to ifup to another one, even  
> >>the new one being in BSS, it wont work: have to unload/reload iwl3945  
> >>module.
> >>
> >>-- 
> >>Daniel
> >>
> >
> >can you check against 2.6.29-rc7 trunk snapshot builds, see apt lines
> >http://wiki.debian.org/DebianKernel
> >  
> Report was done *against* the 2-6-29-rc7! You already ask me to install 
> it after opening the bug ;-)

the original submission says:
-- snipp
Package: linux-image-2.6.28-1-amd64
Version: 2.6.28-1
--

anyway if you can reproduce it with latest, please file upstream
on bugzilla.kernel.org with the dmesg, lscpi -vv info there
and let us know the bug nr.




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

Re: Processed: tagging 463402

[Olivier Berger]

Le lundi 09 mars 2009 à 13:57 +, Debian Bug Tracking System a écrit :
> Processing commands for cont...@bugs.debian.org:
> 
> > # Automatically generated email from bts, devscripts version 2.9.26etch2
> > tags 463402 + pending
> Bug#463402: smbfs: Crash when trying to mount remote cifs share
> Tags were: patch fixed-upstream
> Tags added: pending
> 

Out of curiosity, which target version for a fix do you foresee ?
stable's kernel ?

Thanks in advance.

Best regards,
-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


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

Bug#518961: linux-kbuild-2.6.26: Typo in modpost wrapper src/mod/modpost.c

[Jeff Hansen]

Package: linux-kbuild-2.6.26
Version: 2.6.26-3
Severity: serious
Justification: no longer builds from source


This typo actually causes other kernel modules which use KBUILD_EXTRA_SYMBOLS
to not build correctly.  The modpost process will exit with the error:
"Error: not ELF".

The KBUILD_EXTRA_SYMBOLS feature adds the argument "-e .../Module.symvers"
to the modpost argument list.  The "e" option requires an argument in the
standard Linux kernel modpost program, but Debian's mk_elfconfig-ish
modpost wrapper does not expect the "e" option to have an argument, thus
this "error" is detected.

To fix this bug, all that needs to be done is to add a ":" after the "e" in
the optstring argument of the modpost wrapper's getopt call.

Yes, I know it looks like I'm running a Fedora kernel on a Debian box, but
I'm actually just running a debootstrapped Debian on a Fedora box.
Nevertheless, I've confirmed this bug on a full-blown Debian box as well.

Attached is a patch to fix the bug:

-Jeff

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

Kernel: Linux 2.6.27.7-134.fc10.x86_64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-kbuild-2.6.26 depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries

linux-kbuild-2.6.26 recommends no packages.

linux-kbuild-2.6.26 suggests no packages.

-- no debconf information
--- ./src/mod/modpost.c.orig2009-03-09 15:01:26.0 +
+++ ./src/mod/modpost.c 2009-03-09 15:13:41.0 +
@@ -13,7 +13,7 @@
   int opt;
   FILE *file;
 
-  while ((opt = getopt (argc, argv, "acei:I:K:mM:o:sSw")) != -1)
+  while ((opt = getopt (argc, argv, "ace:i:I:K:mM:o:sSw")) != -1)
   { 
 switch(opt)
 {

Re: [Yaird-devel] Bug#518315: deprecation notice of mkinitramfs-kpkg

[Jonas Smedegaard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Mar 09, 2009 at 03:26:50PM +0100, maximilian attems wrote:
>On Mon, Mar 09, 2009 at 03:01:49PM +0100, Jonas Smedegaard wrote:
>[snipp]
>> 
>> It is true that yaird silently ignore some of the newer 
>> initramfs-tools extensions to the mkinitrd interface, but not the -t 
>> option which is now expected by linux-2.6 (see bug#518315).
>
>right so it is time to add it!

Time? What has time to do with it? Please provide reason!


>ubuntu doesn't use -t as they have takeover set in initramfs-tools by 
>default, thus probably it went unnoticed there.

So why don't you drop that option instead, if it is always forced?


>> mkinitrd provided a limited set of commands needed by kernels to 
>> automate generating ramdisks. This interface is what both 
>> initramfs-tools and yaird implemented and still used by 
>> kernel-package.
>> 
>> I believe that option caused problems in the past for initramfs-tools 
>> to have that option enabled by default, leading to the change in 0.53 
>> (or really 0.53c).
>> 
>> Why do recent linux-2.6 need to introduce the use of the -t option?
>
>read man update-initramfs -t section.

I did. It describes a feature of a generic tool, not about special 
needs of official Debian kernels.


>we want to be sure to really ship the latest modules, it has to be 
>reentrant.

Is that a different need for official kernels than other kernels?


  - Jonas


- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkm1OHAACgkQn7DbMsAkQLhCSACeNQjQ9LoAk8dTkD2uDYxRFmLB
QzwAn32y9tmr5Jv6aIO1tage4OFAlsxU
=4dT+
-END PGP SIGNATURE-


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

Bug#518315: Info received ([Yaird-devel] Bug#518315: deprecation notice of mkinitramfs-kpkg)

[Debian Bug Tracking System]

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Yaird Team 

If you wish to submit further information on this problem, please
send it to 518...@bugs.debian.org, as before.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


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


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

Bug#517241: Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work

[maximilian attems]

On Mon, Mar 09, 2009 at 12:01:55PM -0300, Ronaldo Reis Junior wrote:
> > could you check latest 2.6.28 sid snapshots or 2.6.29-rc7 builds
> > and see if it works there for you?
> > see apt lines http://wiki.debian.org/DebianKernel
> >
> 
> Hi,
> 
> I try this version of kernel and the songs remain the same, i.e. without 
> sound. No errors is found but no sound is showed. Do I have more tests to 
> apply on my machine to find the problem and help in diagnostic?
> 
> Thanks
> Ronaldo 

which version did you try, was it 2.6.29-rc7??

also if still applyable there please report upstream on 
https://bugtrack.alsa-project.org/alsa-bug/my_view_page.php


thanks

-- 
maks



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

Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work

[Ronaldo Reis Junior]

Em Seg 09 Mar 2009, maximilian attems escreveu:
> On Tue, 03 Mar 2009, Ronaldo Reis Junior wrote:
> > Hi,
> >
> > I have this sound card:
> >
> > 0:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
> > Controller (rev 03)
> > Subsystem: Dell Device 0233
> > Flags: bus master, fast devsel, latency 0, IRQ 21
> > Memory at f6adc000 (64-bit, non-prefetchable) [size=16K]
> > Capabilities: 
> > Kernel driver in use: HDA Intel
> > Kernel modules: snd-hda-intel
> >
> > Using the kernel 2.6.26 the sound work, but using the 2.6.28 the sound
> > dont work, but no errors are showed. The modules are the same, look:
>
> could you check latest 2.6.28 sid snapshots or 2.6.29-rc7 builds
> and see if it works there for you?
> see apt lines http://wiki.debian.org/DebianKernel
>
> thanks

Hi,

I try this version of kernel and the songs remain the same, i.e. without 
sound. No errors is found but no sound is showed. Do I have more tests to 
apply on my machine to find the problem and help in diagnostic?

Thanks
Ronaldo 

-- 
Isso é uma faca de dois legumes.
Vicente Mateus
--
> Prof. Ronaldo Reis Júnior
|  .''`. UNIMONTES/DBG/Lab. Ecologia Comportamental e Computacional
| : :'  : Campus Universitário Prof. Darcy Ribeiro, Vila Mauricéia
| `. `'` CP: 126, CEP: 39401-089, Montes Claros - MG - Brasil
|   `- Fone: (38) 3229-8192 | ronaldo.r...@unimontes.br | chrys...@gmail.com
| http://www.ppgcb.unimontes.br/lecc | ICQ#: 5692561 | LinuxUser#: 205366
--
Favor NÃO ENVIAR arquivos do Word ou Powerpoint
Prefira enviar em PDF, Texto, OpenOffice (ODF), HTML, or RTF.



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

Bug#517241: Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work

[Sam Morris]

On Mon, 2009-03-09 at 15:28 +0100, maximilian attems wrote:
> On Mon, Mar 09, 2009 at 01:50:11PM +, Sam Morris wrote:
> > I used version 2.6.28-2~snapshot.12968 and sound was still a bit screwed
> > up. There is now a Headphone slider that controls the volume separately
> > from the Master slider. Inserting headphones did disable the laptop's
> > speakers, but then if I muted and unmuted the Master channel, the
> > laptop's speakers came back to life even though the headphones were
> > still plugged in.
> > 
> 
> well this looks more like userland trouble to me,
> thus going to close unlike other call.

Sorry, I don't see how that is... what part of userspace is supposed to
listen to headphone insert/remove events?

> thanks for quick feedback!
-- 
Sam Morris 



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

Bug#518358: linux-image-2.6.28: iwlwifi: iwl3945 failed after suspend and no roaming

[Daniel]

maximilian attems a écrit :

On Fri, 06 Mar 2009, Daniel Huhardeaux wrote:

  

[...]



It change something from 2.6.28: when I ifdown wlan0 I can get ifup
working correctly without rmmod/modprobe iwl3945 module.
  
Have to correct this: it's only working if I try to reconnect to the  
_same_ AP. If I ifdown from one AP and try to ifup to another one, even  
the new one being in BSS, it wont work: have to unload/reload iwl3945  
module.


--
Daniel



can you check against 2.6.29-rc7 trunk snapshot builds, see apt lines
http://wiki.debian.org/DebianKernel
  
Report was done *against* the 2-6-29-rc7! You already ask me to install 
it after opening the bug ;-)

--
Daniel




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

Bug#517241: Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work

[maximilian attems]

On Mon, Mar 09, 2009 at 01:50:11PM +, Sam Morris wrote:
> I used version 2.6.28-2~snapshot.12968 and sound was still a bit screwed
> up. There is now a Headphone slider that controls the volume separately
> from the Master slider. Inserting headphones did disable the laptop's
> speakers, but then if I muted and unmuted the Master channel, the
> laptop's speakers came back to life even though the headphones were
> still plugged in.
> 

well this looks more like userland trouble to me,
thus going to close unlike other call.

thanks for quick feedback!



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

Re: deprecation notice of mkinitramfs-kpkg

[maximilian attems]

On Mon, Mar 09, 2009 at 03:01:49PM +0100, Jonas Smedegaard wrote:
[snipp]
> 
> It is true that yaird silently ignore some of the newer initramfs-tools 
> extensions to the mkinitrd interface, but not the -t option which is now 
> expected by linux-2.6 (see bug#518315).

right so it is time to add it!

ubuntu doesn't use -t as they have takeover set in initramfs-tools by
default, thus probably it went unnoticed there.
 
> mkinitrd provided a limited set of commands needed by kernels to 
> automate generating ramdisks. This interface is what both 
> initramfs-tools and yaird implemented and still used by kernel-package.
> 
> I believe that option caused problems in the past for initramfs-tools to 
> have that option enabled by default, leading to the change in 0.53 (or 
> really 0.53c).
> 
> Why do recent linux-2.6 need to introduce the use of the -t option?

read man update-initramfs -t section.
we want to be sure to really ship the latest modules, it has to be
reentrant.

kind regards

-- 
maks


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

Bug#516705: linux-image-2.6.26-1-686: Me too

[Olaf van der Spek]

Package: linux-image-2.6.26-1-686
Version: 2.6.26-13
Followup-For: Bug #516705

Hi,

I experience this issue as well:
Mar  9 15:02:31 router kernel: [53539.491257] :00:0b.0: tulip_stop_rxtx() 
failed (CSR5 0xf026 CSR6 0xb3862002)
Mar  9 15:02:37 router kernel: [53545.491052] :00:0b.0: tulip_stop_rxtx() 
failed (CSR5 0xf026 CSR6 0xb3862002)

It also occurs on a DSL gateway, although this is a fresh Lenny install. I'm 
not sure a reboot (with kexec-tools) fixes it.

Olaf

/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto br0
# iface eth0 inet static
iface br0 inet static
address 192.168.1.250
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
# dns-* options are implemented by the resolvconf package, if installed
bridge_ports all
dns-nameservers 192.168.1.254

-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (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 18:29:31 UTC 
2009

** Command line:
root=/dev/hda1 ro quiet

** Not tainted

** Kernel log:
[2.303048] NET: Registered protocol family 17
[2.303048] Using IPI No-Shortcut mode
[2.303048] registered taskstats version 1
[2.303048] rtc_cmos 00:04: setting system clock to 2009-03-09 14:07:35 UTC 
(1236607655)
[2.303843] Freeing unused kernel memory: 244k freed
[2.613666] thermal: Unknown symbol acpi_processor_set_thermal_limit
[3.098155] Uniform Multi-Platform E-IDE driver
[3.098177] ide: Assuming 33MHz system bus speed for PIO modes; override 
with idebus=xx
[3.106142] Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
[3.110776] tulip0:  EEPROM default media type Autosense.
[3.110788] tulip0:  Index #0 - Media 10baseT (#0) described by a 21142 
Serial PHY (2) block.
[3.110798] tulip0:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 
Serial PHY (2) block.
[3.110808] tulip0:  Index #2 - Media 100baseTx (#3) described by a 21143 
SYM PHY (4) block.
[3.110818] tulip0:  Index #3 - Media 100baseTx-FDX (#5) described by a 
21143 SYM PHY (4) block.
[3.116027] eth0: Digital DS21142/43 Tulip rev 65 at Port 0xec00, 
00:10:6f:02:39:a5, IRQ 19.
[3.146973] SCSI subsystem initialized
[3.156777] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[3.156850] 8139cp :00:12.0: This (id 10ec:8139 rev 10) is not an 8139C+ 
compatible chip
[3.156934] 8139cp :00:12.0: Try the "8139too" driver instead.
[3.164196] 8139too Fast Ethernet driver 0.9.28
[3.165589] eth1: RealTek RTL8139 at 0xe800, 00:02:44:52:fe:db, IRQ 19
[3.165598] eth1:  Identified 8139 chip type 'RTL-8100B/8139D'
[3.168444] PIIX4: IDE controller (0x8086:0x7111 rev 0x01) at  PCI slot 
:00:07.1
[3.168479] PIIX4: not 100% native mode: will probe irqs later
[3.168500] ide0: BM-DMA at 0xffa0-0xffa7
[3.168518] ide1: BM-DMA at 0xffa8-0xffaf
[3.168530] Probing IDE interface ide0...
[3.224748] usbcore: registered new interface driver usbfs
[3.224832] usbcore: registered new interface driver hub
[3.224912] usbcore: registered new device driver usb
[3.236824] USB Universal Host Controller Interface driver v3.0
[3.459199] hda: WDC WD200BB-60CVB0, ATA DISK drive
[3.795070] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[3.796206] hda: UDMA/33 mode selected
[3.797110] Probing IDE interface ide1...
[4.530671] hdc: LTN486S, ATAPI CD/DVD-ROM drive
[4.866514] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[4.866597] hdc: MWDMA2 mode selected
[4.866760] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[4.866838] ide1 at 0x170-0x177,0x376 on irq 15
[4.867291] aic7xxx :00:06.0: enabling device (0006 -> 0007)
[4.867309] PCI: No IRQ known for interrupt pin A of device :00:06.0. 
Probably buggy MP table.
[4.881402] aic7xxx: probe of :00:06.0 failed with error -16
[4.886415] PCI: No IRQ known for interrupt pin D of device :00:07.2. 
Probably buggy MP table.
[4.886415] uhci_hcd :00:07.2: Found HC with no IRQ.  Check BIOS/PCI 
:00:07.2 setup!
[4.886415] uhci_hcd :00:07.2: init :00:07.2 fail, -19
[4.934416] libata version 3.00 loaded.
[4.980731] hda: max request size: 128KiB
[4.986427] hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63
[4.986427] hda: cache flushes not supported
[4.986427]  hda: hda1 hda2 < hda5 >
[5.013844] hdc: ATAPI 48X CD-ROM drive, 120kB Cache
[5.013844] Uniform CD-ROM driver Revision: 3.20
[5.279364] PM: Starting manual resume from disk
[5.359358] kjournald starting.  Commit interval 5 seconds
[5.359358

Bug#500520: claims AC is unplugged when my battery reached 100% charge

[maximilian attems]

hello,

is this fixed in newer 2.6.28 linux images?

-- 
maks



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

Bug#328528: cpu-freq/user-guide.txt should mention Celeron

[maximilian attems]

please submit to bugzilla.kernel.org,
so that upstream gets notified.

thanks

-- 
maks



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

Processed: tagging 518900

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 518900 + pending
Bug#518900: ALSA: caiaq - Fix Oops with MIDI
Tags were: patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#515277: marked as done (r8169.c: incorrect RX dropped counter)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:20:12 +0100
with message-id <20090309142012.gv13...@stro.at>
and subject line Re: linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows 
erattic packets dropped (changes fast, always) from ifconfig
has caused the Debian Bug report #515073,
regarding r8169.c: incorrect RX dropped counter
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.)


-- 
515073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515073
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-8
Severity: normal

During a network session RX dropped counter shows great numbers.  All
the other things of the network are fine. The typical value of the
counter is  of the order of magnitude of 10^9, eg.,

$ /sbin/ifconfig eth0 | grep "RX packets"
RX packets:483 errors:0 dropped:3771247613 overruns:0 frame:0
$

The problem appears with the following network adapter:

$ lspci -nn -s 01:00.0
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
$

The same issue was mentioned with the kernel: `Linux 2.6.24-1-686' and
`RTL8111/8168B PCI Express Gigabit Ethernet controller' [1].

Francois Romieu suggested a patch [2] for `r8169.c' to solve the problem.

Please consider applying the patch to the Debian package.

[1] http://bugs.debian.org/497757
[2] https://kerneltrap.org/mailarchive/linux-netdev/2008/9/13/3288264/thread

Thanks,

Tatiana Kronberg


--- End Message ---
--- Begin Message ---
Version: 2.6.28-1

fixed in newer linux image.

thanks for report.

-- 
maks

--- End Message ---

Bug#515073: marked as done (linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows erattic packets dropped (changes fast, always) from ifconfig)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:20:12 +0100
with message-id <20090309142012.gv13...@stro.at>
and subject line Re: linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows 
erattic packets dropped (changes fast, always) from ifconfig
has caused the Debian Bug report #515073,
regarding linux-image-2.6.26-1-vserver-686: realtek r8139.ko shows erattic 
packets dropped (changes fast, always) from ifconfig
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.)


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

netbook:~# for a in {0..9} ; do ifconfig eth0|grep 'RX packets';sleep 0.01;done
  RX packets:10923 errors:0 dropped:1666757496 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1669188652 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1671339578 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1673867025 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1678176522 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1680628018 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1682748257 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1685294521 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1689635655 overruns:0 frame:0
  RX packets:10923 errors:0 dropped:1691597286 overruns:0 frame:0

This segment of the network is pretty quiet, but dropped packets are constantly 
counting.  Clearly a cosmetic bug imo, but someone using network monitoring 
might be unsetteled by what they think is a trend.

As for the kernel taint, I'm using the madwifi driver as the ath5k drivers 
don't operate on my hardware.
-- Package-specific info:
** Version:
Linux version 2.6.26-1-vserver-686 (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 
21:26:14 UTC 2009

** Command line:
root=/dev/mapper/netbook-root ro 

** Tainted: P (1)

** Kernel log:
[4.512789] usb 5-5: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[4.512789] usb 5-5: Product: USB 2.0 Camera
[4.512789] usb 5-5: Manufacturer: Sonix Technology Co., Ltd.
[4.538120] Clocksource tsc unstable (delta = -211289912 ns)
[4.558108] scsi 0:0:0:0: Direct-Access ATA  WDC WD1600BEVT-2 11.0 
PQ: 0 ANSI: 5
[4.594105] Driver 'sd' needs updating - please use bus_type methods
[4.595590] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[4.595590] sd 0:0:0:0: [sda] Write Protect is off
[4.595590] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[4.597628] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[4.598048] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[4.597710] sd 0:0:0:0: [sda] Write Protect is off
[4.597710] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[4.597724] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[4.597724]  sda: sda1 sda2 sda3 sda4 < sda5 >
[4.620872] sd 0:0:0:0: [sda] Attached SCSI disk
[4.986611] device-mapper: uevent: version 1.0.3
[4.986611] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: 
dm-de...@redhat.com
[   13.826146] PM: Starting manual resume from disk
[   13.876845] EXT3-fs: INFO: recovery required on readonly filesystem.
[   13.876845] EXT3-fs: write access will be enabled during recovery.
[   16.973826] kjournald starting.  Commit interval 5 seconds
[   16.977725] EXT3-fs: dm-1: orphan cleanup on readonly fs
[   16.977725] ext3_orphan_cleanup: deleting unreferenced inode 246715
[   17.011171] ext3_orphan_cleanup: deleting unreferenced inode 114626
[   17.011171] ext3_orphan_cleanup: deleting unreferenced inode 114611
[   17.011171] ext3_orphan_cleanup: deleting unreferenced inode 114294
[   17.020531] ext3_orphan_cleanup: deleting unreferenced inode 247374
[   17.025948] ext3_orphan_cleanup: deleting unreferenced inode 464247
[   17.039800] ext3_orphan_cleanup: deleting unreferenced inode 57012
[   17.049161] ext3_orphan_cleanup: deleting unreferenced inode 65171
[   17.063913] ext3_orphan_cleanup: deleting unreferenced inode 334680
[   17.063913] EXT3-fs: dm-1: 9 orphan inodes deleted
[   17.063913] EXT3-fs: recovery complete.
[   17.136264] EXT3-fs: mounted filesystem with ordered data mode.
[   19.109261] udevd version 125 started
[   20.087797] ACPI: WMI: Mapper loaded
[   20.203792] acer-wmi:

Bug#489608: marked as done (md: hung task timout during data check)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:19:14 +0100
with message-id <20090309141914.gu13...@stro.at>
and subject line Re: md: hung task timout during data check
has caused the Debian Bug report #489608,
regarding md: hung task timout during data check
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.)


-- 
489608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 2.6.4-2
Severity: normal

Hi 

I have started to received these errors in dmesg when the monthly array
check happens

[569708.399818] md: data-check of RAID array md0
[569708.399823] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[569708.399826] md: using maximum available idle IO bandwidth (but not
more than 20 KB/sec) for data-check.
[569708.399831] md: using 128k window, over a total of 979840 blocks.
[569708.411831] md: delaying data-check of md1 until md0 has finished
(they share one or more physical units)
[569708.414774] md: delaying data-check of md2 until md0 has finished
(they share one or more physical units)
[566995.265070] md: delaying data-check of md3 until md2 has finished
(they share one or more physical units)
[569708.414984] md: delaying data-check of md1 until md3 has finished
(they share one or more physical units)
[569708.414997] md: delaying data-check of md2 until md0 has finished
(they share one or more physical units)
[566995.265119] md: delaying data-check of md3 until md2 has finished
(they share one or more physical units)
[567006.347885] md: md0: data-check done.
[569721.828687] md: delaying data-check of md1 until md3 has finished
(they share one or more physical units)
[567006.369737] md: delaying data-check of md3 until md2 has finished
(they share one or more physical units)
[569721.828687] md: data-check of RAID array md2
[569721.828687] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[569721.828687] md: using maximum available idle IO bandwidth (but not
more than 20 KB/sec) for data-check.
[569721.828687] md: using 128k window, over a total of 1959808 blocks.
[567006.405012] RAID1 conf printout:
[567006.405012]  --- wd:2 rd:2
[567006.405012]  disk 0, wo:0, o:1, dev:sdb1
[567006.405012]  disk 1, wo:0, o:1, dev:sda1
[567027.013594] md: md2: data-check done.
[569749.143037] md: delaying data-check of md1 until md3 has finished
(they share one or more physical units)
[567027.032374] md: data-check of RAID array md3
[567027.032378] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[567027.032381] md: using maximum available idle IO bandwidth (but not
more than 20 KB/sec) for data-check.
[567027.032386] md: using 128k window, over a total of 964052544 blocks.
[569749.205917] RAID1 conf printout:
[569749.205917]  --- wd:2 rd:2
[569749.205917]  disk 0, wo:0, o:1, dev:sdb3
[569749.205917]  disk 1, wo:0, o:1, dev:sda3
[580719.308717] INFO: task md1_resync:30573 blocked for more than 120
seconds.
[580719.308726] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[580719.308729] md1_resyncD 80587a00 0 30573  2
[580719.308736]  81005136fdb0 0046 8815e800
802293e3
[580719.308747]  81004d502e40 8100529e29c0 81004d5030b0
00010001
[580719.308757]  0282 0003 81005136fdb0
8022be74
[580719.308766] Call Trace:
[580719.308808]  [] __wake_up_common+0x41/0x74
[580719.308820]  [] __wake_up+0x38/0x4e
[580719.308843]  [] :md_mod:md_do_sync+0x21d/0x92c
[580719.308850]  [] update_curr+0x44/0x6c
[580719.308858]  [] dequeue_entity+0x1a/0x83
[580719.308865]  [] __dequeue_entity+0x25/0x68
[580719.308874]  [] __switch_to+0x8d/0x2e6
[580719.308880]  [] hrtick_set+0x88/0xf7
[580719.308887]  [] autoremove_wake_function+0x0/0x2e
[580719.308909]  [] :md_mod:md_thread+0xd7/0xed
[580719.308928]  [] :md_mod:md_thread+0x0/0xed
[580719.308932]  [] kthread+0x47/0x74 

   
[580719.308939]  [] child_rip+0xa/0x12

   
[580719.308958]  [] kthread+0x0/0x74  

   
[580719.308963]  [] child_rip+0x0/0x12

   
[580719.308968] 

Processed: tagging 511165

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 511165 + pending
Bug#511165: linux-image-2.6.26-1-openvz-amd64: Kernel panic with nf_conntrack 
and FTP
Tags were: patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#499763: marked as done (linux-image-2.6.26-1-amd64: r8169 (network) not working on 2.6.26)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:16:30 +0100
with message-id <20090309141630.gs13...@stro.at>
and subject line Re: linux-image-2.6.26-1-amd64: r8169 (network) not working on 
2.6.26
has caused the Debian Bug report #499763,
regarding linux-image-2.6.26-1-amd64: r8169 (network) not working on 2.6.26
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.)


-- 
499763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499763
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-5
Severity: normal

Hi,

I tried upgrading my lenny box from 2.6.25 to 2.6.26 and it doesn't work
really well, especially from the network pov.

The box uses the r8169 module:

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI
Express Fast Ethernet controller (rev 02)

When booting the 2.6.26, I have:

[2.270265] r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded  
[2.270387] ACPI: PCI Interrupt :01:00.0[A] -> GSI 16 (level, low) -> 
IRQ 16
[2.270516] PCI: Setting latency timer of device :01:00.0 to 64
[2.270536] r8169 :01:00.0: unknown MAC (27a0)
[2.271261] eth0: RTL8169 at 0xc24de000, 00:1c:c0:47:d9:f8, XID 
24a0 IRQ 1276
[…]
[   17.253398] r8169: eth0: link up 
[   18.543748] IPv6 over IPv4 tunneling driver
[   18.543748] sit0: Disabled Privacy Extensions
[   18.896123] ip_tables: (C) 2000-2006 Netfilter Core Team
[   27.491415] eth0: no IPv6 routers present
[   41.362012] NETDEV WATCHDOG: eth0: transmit timed out
[   41.362081] [ cut here ]
[   41.362130] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xa6/0xfb()
[   41.362187] Modules linked in: iptable_filter ip_tables x_tables sit tunnel4 
ipv6 smsc47m1 smsc47m192 hwmon_vid loop psmouse iTCO_wdt i2c_i801 i2c_core  
serio_raw rng_core pcspkr button usbhid hid ff_memless usblp snd_hda_intel  
intel_agp snd_pcm snd_timer snd soundcore snd_page_alloc evdev ext3 jbd mbcache 
dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod piix ide_pci_generic
ide_core ata_piix ata_generic libata scsi_mod dock ehci_hcd uhci_hcd r8169  
thermal processor fan thermal_sys
[   41.365702] Pid: 0, comm: swapper Not tainted 2.6.26-1-amd64 #1
[   41.365702]
[   41.365702] Call Trace:
[   41.365702][] warn_on_slowpath+0x51/0x7a
[   41.365702]  [] dev_watchdog+0x0/0xfb
[   41.365702]  [] printk+0x4e/0x56
[   41.365702]  [] read_tsc+0x9/0x20
[   41.365702]  [] lock_timer_base+0x26/0x4b
[   41.365702]  [] __mod_timer+0xbd/0xcc
[   41.365702]  [] queue_delayed_work_on+0xb8/0xc8
[   41.365702]  [] dev_watchdog+0x0/0xfb
[   41.365702]  [] dev_watchdog+0xa6/0xfb
[   41.365702]  [] dev_watchdog+0x0/0xfb
[   41.365702]  [] run_timer_softirq+0x16a/0x1e2
[   41.365702]  [] __do_softirq+0x5c/0xd1
[   41.365702]  [] call_softirq+0x1c/0x28
[   41.365702]  [] do_softirq+0x3c/0x81
[   41.365702]  [] irq_exit+0x3f/0x83
[   41.365702]  [] smp_apic_timer_interrupt+0x8c/0xa4
[   41.365702]  [] mwait_idle+0x0/0x4d
[   41.365702]  [] apic_timer_interrupt+0x72/0x80
[   41.365702][] lapic_next_event+0x0/0x13
[   41.365702]  [] mwait_idle+0x41/0x4d
[   41.365702]  [] cpu_idle+0x89/0xb3
[   41.365702]
[   41.365702] ---[ end trace 6058d4309049ae83 ]---

Then, during all the session, I get:

[   96.170038] NETDEV WATCHDOG: eth0: transmit timed out
[   96.985210] r8169: eth0: link up
[  126.813323] NETDEV WATCHDOG: eth0: transmit timed out
[  127.30] r8169: eth0: link up 

and eth0 never transmit anything.

Rebooting under 2.6.25 works fine. I'm using the latest 2.6.26 in Lenny 
(2.6.26-5).

As it's a production server I can't easily test and do bisect test on this.

Cheers,
--
Yves-Alexis
-- Package-specific info:

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

Kernel: Linux 2.6.25-2-amd64 (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-1-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92j  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.26-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.26-1-amd64 suggests:
ii  grub-pc [grub]  1.96+20080724-10 GRand Unified Bootloader, version 
p

Re: deprecation notice of mkinitramfs-kpkg

[Jonas Smedegaard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Feb 16, 2009 at 03:06:05PM +0100, maximilian attems wrote:
>On Mon, Feb 16, 2009 at 02:45:51PM +0100, Jonas Smedegaard wrote:
>> On Mon, Feb 16, 2009 at 01:16:55PM +0100, maximilian attems wrote:
>> >this command is a kludge.
>> >it was added for kernel-package as some guy wanted still to use 
>> >initrd-tools. next initramfs-tools upload will emit a warning when 
>> >it is used.
>> >
>> >i'll change linux-2.6 trunk to properly call update-initramfs.
>> >as it already does for xen images.
>> 
>> Do I understand you correctly that you want to drop support not only 
>> for initrd-tools but generally for alternative ramdisk generators?
>
>no please reread.
>
>also latest yaird understands update-initramfs call syntax.

No, that is incorrect.

It is true that yaird silently ignore some of the newer initramfs-tools 
extensions to the mkinitrd interface, but not the -t option which is now 
expected by linux-2.6 (see bug#518315).

mkinitrd provided a limited set of commands needed by kernels to 
automate generating ramdisks. This interface is what both 
initramfs-tools and yaird implemented and still used by kernel-package.

I believe that option caused problems in the past for initramfs-tools to 
have that option enabled by default, leading to the change in 0.53 (or 
really 0.53c).

Why do recent linux-2.6 need to introduce the use of the -t option?


  - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkm1IU0ACgkQn7DbMsAkQLgfBQCfYindlEK1kt+GjGkhm8qHyIym
JKsAnAtw6QQsRYTBdRTQXi7f88h7ZWnD
=vTXn
-END PGP SIGNATURE-


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

Bug#498645: marked as done (initramfs-tools: Boot takes three minutes to finish (!))

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:14:37 +0100
with message-id <20090309141437.gr13...@stro.at>
and subject line Re: initramfs-tools: Boot takes three minutes to finish (!)
has caused the Debian Bug report #498645,
regarding initramfs-tools: Boot takes three minutes to finish (!)
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.)


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

After installing a lenny system today, it happened that the boot
process takes more than 3 minutes to finish. Needless to say, I first
believed it was frozen and didn't work at all. I was lucky to discover
(by accident) that it was a very long waiting time instead.

After a bit of investigation, it happened that this value, 180 seconds,
is the default timeout for "udevadm settle", according to udevadm(8).

Unfortunately, there is not a simple way to change this. First I tried
changing "udevadm settle" invocation in /etc/init.d/udev but this only
worked for linux images not using a ramdisk (I built several of those as
I first suspected to be a kernel problem).

What worked finally was to change "udevadm settle" invocation at

/usr/share/initramfs-tools/scripts/init-premount/udev

and then rebuilding the initramfs via dpkg-reconfigure linux-image-etc-etc.

While doing this I noticed that "udevadm settle" is called three times
in /usr/share/initramfs-tools/*. Two of them are wrapped via wait_for_udev()
from /usr/share/initramfs-tools/scripts/functions and they have 10 seconds
as the timeout value. The other one is the one I had to hardcode by hand.

To summarize: No matter how faulty my hardware might be (the boot
never took so long with etch), I don't think it is reasonable at all
that a user has to do this in order for the boot process not to take
more than three minutes.

Maybe every "udevadm settle" invocation should be wrapped via wait_for_udev(),
not just two of them. Or maybe this is a bug in udev for having such a long
waiting time. Feel free to reassign.

Note: I see this as a serious bug, but as I don't know the number of
people having this problem, I prefer not to use a severity at all.

Thanks.


--- End Message ---
--- Begin Message ---
Version: 2.6.28-1

linux-2.6 upstream added fixes,
thanks for report!

-- 
maks

--- End Message ---

Bug#497925: marked as done (linux-image-2.6.26-1-686: WARNING: at drivers/usb/serial/usb-serial.c:320 serial_write_room+0x41/0x4d [usbserial])

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:09:40 +0100
with message-id <20090309140940.gp13...@stro.at>
and subject line Re: linux-image-2.6.26-1-686: WARNING: at 
drivers/usb/serial/usb-serial.c:320 serial_write_room+0x41/0x4d [usbserial]
has caused the Debian Bug report #497925,
regarding linux-image-2.6.26-1-686: WARNING: at 
drivers/usb/serial/usb-serial.c:320 serial_write_room+0x41/0x4d [usbserial]
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.)


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

On my thinkpad x61s laptop, I get several times: 

WARNING: at drivers/usb/serial/usb-serial.c:320 serial_write_room+0x41/0x4d 
[usbserial]()

in dmesg after powercycling the Sierra Wireless MC8775 UMTS-card two
times. Scenario to reproduce:

[card is active after boot]

echo disable > /proc/acpi/ibm/wan

[ttyUSB0-2 disconnect, at second 112 in attached dmseg]

echo enable > /proc/acpi/ibm/wan

[ttyUSB0-2 connect, at second 182 in attached dmesg]
[normal ppp operation of card]

echo disable > /proc/acpi/ibm/wan

[ttyUSB0-2 disconnect, at second 217 in attached dmseg]

echo enable > /proc/acpi/ibm/wan

[ttyUSB0-2 connect, at second 226 in attached dmesg]

After this dmesg shows 16 warnings at usb-serial.c. Dispite the 
warnings, the UMTS-card seems to operate normal.

-- 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/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

-- debconf information excluded


--- End Message ---
--- Begin Message ---
Version: 2.6.28-1

fixed upstream in 4bd43f2c31848d751f63e8753cd2788d48fb5f30
this fixes are quite intrusive and never went to a stable series.
they will reach lenny with lenny+half kernel.

thanks for report!

-- 
maks

--- End Message ---

Bug#498593: marked as done (linux-image-2.6.26-1-amd64: No network traffic with intel 4965 N card connecting to N mode network)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 15:10:33 +0100
with message-id <20090309141033.gq13...@stro.at>
and subject line Re: linux-image-2.6.26-1-amd64: No network traffic with intel 
4965 N card connecting to N mode network
has caused the Debian Bug report #498593,
regarding linux-image-2.6.26-1-amd64: No network traffic with intel 4965 N card 
connecting to N mode network
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.)


-- 
498593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498593
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-4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hello,

When connecting with the 2.6.25 or 2.6.26 stcok kernel to my home N-mode
network, the DHCP request fails. I suspect somehow network transport is
not possible.
Connecting to my wireless at work (G) I have no problems. Included is a
snapshot form the kern.log and syslog files, please let me know what
other information I should send.
Thanks for your efforts.

Sjoerd


- -- Package-specific info:

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

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

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

linux-image-2.6.26-1-amd64 recommends no packages.

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

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

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

iEYEARECAAYFAkjI914ACgkQHKEdNPY5OOVdtACffaiWGNVPqfPjO8IDCy4cX1FY
QhwAoIatVvBUZyqRxQiR+/zqRDjWvKj5
=Klo+
-END PGP SIGNATURE-
Sep  1 20:46:46 laptop kernel: [  129.834816] ACPI: PCI Interrupt :0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Sep  1 20:46:46 laptop kernel: [  129.834965] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106)
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:radio
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:assoc
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:RX
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:TX
Sep  1 20:46:46 laptop kernel: [  130.059527] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  1 20:46:50 laptop kernel: [  133.645443] wlan0: Initial auth_alg=0
Sep  1 20:46:50 laptop kernel: [  133.645456] wlan0: authenticate with AP 00:1d:7e:ab:ac:66
Sep  1 20:46:50 laptop kernel: [  133.648162] wlan0: RX authentication from 00:1d:7e:ab:ac:66 (alg

Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work

[Sam Morris]

On Mon, 2009-03-09 at 13:13 +0100, maximilian attems wrote:
> On Tue, 03 Mar 2009, Ronaldo Reis Junior wrote:
> 
> > Hi,
> > 
> > I have this sound card:
> > 
> > 0:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
> > Controller (rev 03)
> > Subsystem: Dell Device 0233
> > Flags: bus master, fast devsel, latency 0, IRQ 21
> > Memory at f6adc000 (64-bit, non-prefetchable) [size=16K]
> > Capabilities: 
> > Kernel driver in use: HDA Intel
> > Kernel modules: snd-hda-intel
> > 
> > Using the kernel 2.6.26 the sound work, but using the 2.6.28 the sound dont 
> > work, but no errors are showed. The modules are the same, look:
> > 
> 
> could you check latest 2.6.28 sid snapshots or 2.6.29-rc7 builds
> and see if it works there for you?
> see apt lines http://wiki.debian.org/DebianKernel

I used version 2.6.28-2~snapshot.12968 and sound was still a bit screwed
up. There is now a Headphone slider that controls the volume separately
from the Master slider. Inserting headphones did disable the laptop's
speakers, but then if I muted and unmuted the Master channel, the
laptop's speakers came back to life even though the headphones were
still plugged in.

> 
> thanks
-- 
Sam Morris 



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

Bug#518315: Info received (deprecation notice of mkinitramfs-kpkg)

[Debian Bug Tracking System]

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Yaird Team 

If you wish to submit further information on this problem, please
send it to 518...@bugs.debian.org, as before.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.


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


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

Bug#488799: marked as done (linux-image-2.6.25-2-686: power button produces multiple events)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:59:36 +0100
with message-id <20090309135936.go13...@stro.at>
and subject line Re: linux-image-2.6.25-2-686: power button produces multiple 
events
has caused the Debian Bug report #488799,
regarding linux-image-2.6.25-2-686: power button produces multiple events
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.)


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


Pressing the power button produces two acpi events most of the time.
This makes using the event for something like hibernate quite difficult.

I do not see any particular pattern in the behaviour. Pressing the
power button usually produces two events but sometimes only one is
produced.


-- Package-specific info:
** Version:
Linux version 2.6.25-2-686 (Debian 2.6.25-5) (wa...@debian.org) (gcc version 
4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Thu Jun 12 16:26:30 UTC 
2008

** Command line:
root=/dev/mapper/nc4010-root ro video=radeonfb 

** Not tainted

** Kernel log:
[17910.246553]   .max_vruntime  : 0.01
[17910.246555]   .spread: 0.00
[17910.246557]   .spread0   : 0.00
[17910.246559]   .nr_running: 0
[17910.246561]   .load  : 0
[17910.246563]   .nr_spread_over: 0
[17910.246564] 
[17910.246565] cfs_rq
[17910.246567]   .exec_clock: 0.00
[17910.246569]   .MIN_vruntime  : 0.01
[17910.246571]   .min_vruntime  : 3462698.548046
[17910.246573]   .max_vruntime  : 0.01
[17910.246575]   .spread: 0.00
[17910.246577]   .spread0   : 0.00
[17910.246579]   .nr_running: 0
[17910.246581]   .load  : 0
[17910.246583]   .nr_spread_over: 0
[17910.246584] 
[17910.246585] cfs_rq
[17910.246587]   .exec_clock: 0.00
[17910.246589]   .MIN_vruntime  : 0.01
[17910.246591]   .min_vruntime  : 3462698.548046
[17910.246594]   .max_vruntime  : 0.01
[17910.246596]   .spread: 0.00
[17910.246598]   .spread0   : 0.00
[17910.246600]   .nr_running: 1
[17910.246601]   .load  : 1024
[17910.246603]   .nr_spread_over: 0
[17910.246606] 
[17910.246607] runnable tasks:
[17910.246608] task   PID tree-key  switches  prio 
exec-runtime sum-execsum-sleep
[17910.246610] 
--
[17910.246619] R s2disk 22175   2528841.509814   3575934   120  
 0   0   0.00   0.00
   0.00
[17910.246626] 
[17910.246643]  cifsd
[17910.246648] 
[17910.246650] Restarting tasks ... done.
[17910.433877] input: Power Button (FF) as /class/input/input29
[17910.466845] ACPI: Power Button (FF) [PWRF]
[17910.468782] input: Sleep Button (CM) as /class/input/input30
[17910.494842] ACPI: Sleep Button (CM) [C13C]
[17910.496740] input: Lid Switch as /class/input/input31
[17910.507008] ACPI: Lid Switch [C13B]
[17910.528340] ACPI: PCI Interrupt :00:12.2[C] -> Link [C0C6] -> GSI 10 
(level, low) -> IRQ 10
[17910.530299] ehci_hcd :00:12.2: EHCI Host Controller
[17910.530815] ehci_hcd :00:12.2: new USB bus registered, assigned bus 
number 3
[17910.532699] ehci_hcd :00:12.2: irq 10, io mem 0x9840
[17910.546804] ehci_hcd :00:12.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 
2004
[17910.548817] usb usb3: configuration #1 chosen from 1 choice
[17910.550663] hub 3-0:1.0: USB hub found
[17910.550770] hub 3-0:1.0: 5 ports detected
[17910.654991] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[17910.656851] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[17910.658510] usb usb3: Product: EHCI Host Controller
[17910.658764] usb usb3: Manufacturer: Linux 2.6.25-2-686 ehci_hcd
[17910.660542] usb usb3: SerialNumber: :00:12.2
[17911.998964] agpgart: Found an AGP 2.0 compliant device at :00:00.0.
[17911.999010] agpgart: Putting AGP V2 device at :00:00.0 into 4x mode
[17911.999083] agpgart: Putting AGP V2 device at :01:05.0 into 4x mode
[17920.195368]  CIFS VFS

Bug#418814: Xircom RE-100 network interface fails silently on Etch Netinst

[maximilian attems]

could we please have an update on any more recent kernels like 
version >= 2.6.26

upstream bug report seems to have lost track on the issue too.

thanks

-- 
maks



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

Bug#473800: marked as done (linux-image-2.6.24: Multiple "Reset high speed USB device using ehci_hcd" that sometimes crash the system)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:53:41 +0100
with message-id <20090309135341.gm13...@stro.at>
and subject line Re: linux-image-2.6.24: Multiple "Reset high speed USB device 
using ehci_hcd" that sometimes crash the system
has caused the Debian Bug report #473800,
regarding linux-image-2.6.24: Multiple "Reset high speed USB device using 
ehci_hcd" that sometimes crash 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.)


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

Package: linux-image-2.6.24-1-486
Version: 2.6.24-5
Severity: important

During data copy to/from USB disk or USB stick the USB device is often 
reset by the driver as below :


Mar 30 23:16:09 debian kernel: usb 4-4: reset high speed USB device 
using ehci_hcd and address 2
Mar 30 23:19:08 debian kernel: usb 4-4: reset high speed USB device 
using ehci_hcd and address 2


When it occurs more than 5/6 times during the data transmission the 
system may crash (nautilus becomes a zombie, pdflush and other related 
deamons are uninterruptible...) and I am forced to use the MagickSysKeys 
to reboot.


The problem is the same with linux-image-2.6.24-1-686 and many previous 
kernel versions actually.


lspci -v :

00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS645DX Host & 
Memory & AGP Controller (rev 01)

   Flags: bus master, medium devsel, latency 32
   Memory at e000 (32-bit, non-prefetchable) [size=128M]
   Capabilities: 
   Kernel driver in use: agpgart-sis
   Kernel modules: sis-agp

00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI 
bridge (AGP) (prog-if 00 [Normal decode])

   Flags: bus master, fast devsel, latency 32
   Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
   I/O behind bridge: 1000-1fff
   Memory behind bridge: dfe0-dfef
   Prefetchable memory behind bridge: bfc0-dfcf

00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL 
Media IO] (rev 14)

   Flags: bus master, medium devsel, latency 0

00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
   Flags: medium devsel
   I/O ports at 2000 [disabled] [size=32]
   Kernel driver in use: sis96x_smbus
   Kernel modules: i2c-sis96x

00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire 
Controller (prog-if 10 [OHCI])

   Subsystem: Unknown device 1631:7007
   Flags: bus master, medium devsel, latency 32, IRQ 11
   Memory at d000 (32-bit, non-prefetchable) [size=4K]
   Expansion ROM at dffc [disabled] [size=128K]
   Capabilities: 
   Kernel driver in use: firewire_ohci
   Kernel modules: firewire-ohci

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 
(prog-if 80 [Master])

   Subsystem: Unknown device 1631:5513
   Flags: bus master, medium devsel, latency 128
   [virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled] 
[size=8]
   [virtual] Memory at 03f0 (type 3, non-prefetchable) [disabled] 
[size=1]
   [virtual] Memory at 0170 (32-bit, non-prefetchable) [disabled] 
[size=8]
   [virtual] Memory at 0370 (type 3, non-prefetchable) [disabled] 
[size=1]

   I/O ports at ff00 [size=16]
   Kernel driver in use: SIS_IDE
   Kernel modules: sis5513

00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller 
(rev a0) (prog-if 00 [Generic])

   Subsystem: Unknown device 1631:3054
   Flags: bus master, medium devsel, latency 32, IRQ 9
   I/O ports at d000 [size=256]
   I/O ports at cc00 [size=128]
   Capabilities: 
   Kernel driver in use: Intel ICH Modem
   Kernel modules: snd-intel8x0m, 8250_pci

00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] 
AC'97 Sound Controller (rev a0)

   Subsystem: Unknown device 1631:200b
   Flags: bus master, medium devsel, latency 32, IRQ 9
   I/O ports at c800 [size=256]
   I/O ports at c400 [size=128]
   Capabilities: 
   Kernel driver in use: Intel ICH
   Kernel modules: snd-intel8x0

00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 
Controller (rev 0f) (prog-if 10 [OHCI])

   Subsystem: Unknown device 1631:7001
   Flags: bus master, medium devsel, latency 32, IRQ 9
   Memory at dfffe000 (32-bit, non-prefetchable) [size=4K]
   Kernel driver in use: ohci_hcd
   Kernel modules: ohci-hcd

00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 
Controller (rev 0f) (prog-if 10 [OHCI])

   Subsystem: Unknown device 1631:7001
   Flags: bus master, medium devsel, latency 32, IRQ 9
   Memory at dfffd000 (32-bit, non-prefetchable) [size=4K]
   Ke

Processed: tagging 463402

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 463402 + pending
Bug#463402: smbfs: Crash when trying to mount remote cifs share
Tags were: patch fixed-upstream
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: tagging 494308

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 494308 + pending
Bug#494308: binary firmware in drivers/net/e100.c
Tags were: pending lenny-ignore patch help
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: tagging 516709

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 516709 + pending
Bug#516709: huge /lib/modules directory, almost 3x size of 2.6.26
Tags were: pending
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: tagging 501152

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 501152 + pending
Bug#501152: binary firmware in drivers/net/starfire_firmware.h
Tags were: pending lenny-ignore patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#479114: marked as done (kernel memory mapping bug)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:55:46 +0100
with message-id <20090309135546.gn13...@stro.at>
and subject line Re: No sound on ATI Technologies Inc RV630/M76 audio device 
[Radeon HD 2600 Series] sound card
has caused the Debian Bug report #479114,
regarding kernel memory mapping bug
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.)


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

version: 2.6.22, 2.6.24

Attempting to install Lenny using netinstall.

The hardware:
MSI K9A2 CF mainboard w/AMD 790X chipset, AMI BIOS 2.61, Realtek 81xx
Gigabit Ethernet, Athlon X2 5400+, 2 X 1 GB Kingston DDR2 667. This bug
is identical using an ECS A780GM-A Black series mainboard with AMD 780G
chipset and the same AMI BIOS version 2.61.

Upon install I get the following error;
PCI: BIOS BUG: MCFG area at e000 is not E820-reserved
PCI: Not using MMCONFIG
PCI: Cannot allocate resource region 3 of device :00:00

Using 'installgui' configuration of Realtek Ethernet fails. Works with
normal install. This may be a seperate issue.

It appears that the kernel is not properly mapping memory. Booting
ubuntu 8.04 works fine. Memory is properly mapped and working fine. Same
with Mandriva live CD. Ran memtest and memory showed no problems.

I did manage to get lenny installed but the kernel only sees half of the
memory and the system is very sluggish.

Here is the output of 'dmesg | grep -i memory';

Freeing initrd memory: 6389k freed
Total HugeTLB memory allocated, 0
Freeing unused kernel memory: 324k freed
swsusp: Basic memory bitmaps created
swsusp: Basic memory bitmaps freed

Following is the output of 'dmesg';

reserved
system 00:0d: iomem range 0xe-0xf could not be reserved
system 00:0d: iomem range 0x10-0x7fff could not be reserved
system 00:0d: iomem range 0xfed45000-0x could not be reserved
PCI: Bridge: :00:02.0
  IO window: disabled.
  MEM window: fc00-fe9f
  PREFETCH window: d000-dfff
PCI: Bridge: :00:06.0
  IO window: e000-efff
  MEM window: fea0-feaf
  PREFETCH window: disabled.
PCI: Bridge: :00:14.4
  IO window: disabled.
  MEM window: feb0-febf
  PREFETCH window: disabled.
PCI: Setting latency timer of device :00:02.0 to 64
PCI: Setting latency timer of device :00:06.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 6389k freed
audit: initializing netlink socket (disabled)
audit(1209680603.628:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Boot video device is :01:00.0
PCI: Setting latency timer of device :00:02.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[:00:02.0:pcie00]
PCI: Setting latency timer of device :00:06.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[:00:06.0:pcie00]
isapnp: Scanning for PnP cards...
Switched to high resolution mode on CPU 0
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
EISA: Probing bus 0 at eisa.0
EISA: Detected 0 cards.
cpuidle: using governor ladder
cpuidle: using governor menu
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
registered taskstats version 1
Freeing unused kernel memory: 324k freed
input: AT Translated Set 2 keyboard as /class/input/input0
ACPI: duty_cycle spans bit 4
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
ACPI: PCI Interrupt :02:00.0[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device :02:00.0 to 64
eth0: RTL8168b/8111b at 0xf8826000, 00:1d:92:

Processed: tagging 447549

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 447549 + pending
Bug#447549: linux-2.6: orinoco.c printk messages flood terminal
Tags were: pending patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#451422: marked as done (pulseaudio: CPU time limit exhausted after resume)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:45:17 +0100
with message-id <20090309134517.gl13...@stro.at>
and subject line Re: pulseaudio: CPU time limit exhausted after resume
has caused the Debian Bug report #451422,
regarding pulseaudio: CPU time limit exhausted after resume
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.)


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

Package: pulseaudio
Version: 0.9.7-1
Severity: normal

After resuming (from suspend), pulseaudio crashes with the following 
message:


Soft CPU time limit exhausted, terminating.
Hard CPU time limit exhausted, terminating forcibly.

Note that this message only appears if pulseaudio is started from the 
prompt, although it crashes whether it is started from the prompt or on 
GNOME login.  This just started happening recently, so it might be due 
to the newer kernel that I'm running.


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

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pulseaudio depends on:
ii  adduser   3.105  add and remove users and groups
ii  libasound21.0.15-1   ALSA library
ii  libasyncns0   0.3-1  Asyncronous name service query lib
ii  libc6 2.7-0exp8  GNU C Library: Shared libraries
ii  libcap1   1:1.10-14  support for getting/setting POSIX.
ii  libdbus-1-3   1.1.1-3simple interprocess messaging syst
ii  libltdl3  1.5.24-1   A system independent dlopen wrappe
ii  liboil0.3 0.3.12-1   Library of Optimized Inner Loops
ii  libpulsecore4 0.9.7-1PulseAudio sound server core
ii  libsamplerate00.1.2-5audio rate conversion library
ii  libsndfile1   1.0.17-4   Library for reading/writing audio 
ii  libwrap0  7.6.dbs-14 Wietse Venema's TCP wrappers libra


Versions of packages pulseaudio recommends:
ii  libao-pulse   0.9.3-1libao PulseAudio driver
pn  libasound2-plugins (no description available)
ii  libgstreamer-plugins-pulse0.1 0.9.4-2PulseAudio plugin for GStreamer
ii  padevchooser  0.9.3-2PulseAudio Device Chooser
ii  paprefs   0.9.5-2PulseAudio Preferences
ii  pulseaudio-esound-compat  0.9.7-1PulseAudio ESD compatibility layer
ii  pulseaudio-module-hal 0.9.7-1HAL device detection module for Pu
ii  pulseaudio-module-x11 0.9.7-1X11 module for PulseAudio sound se

-- no debconf information

--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
a typesetting engine: http://crustytoothpaste.ath.cx/~bmc/code/thwack
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 2.6.26-1

fixed with newre alsa.

thanks for the report.

-- 
maks

--- End Message ---

Processed: tagging 447549

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 447549 + pending
Bug#447549: linux-2.6: orinoco.c printk messages flood terminal
Tags were: patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#427574: marked as done (linux-image-2.6.21-1-686: quickcam_messenger driver does not work)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:37:45 +0100
with message-id <20090309133745.gk13...@stro.at>
and subject line Re: linux-image-2.6.21-1-686: quickcam_messenger driver does 
not work
has caused the Debian Bug report #427574,
regarding linux-image-2.6.21-1-686: quickcam_messenger driver does not work
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.)


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

when I plug my webcam quickcam messenger and try to
use it (with xawtv for example), all I
get is a blank screen. The cam works perfectly with
the previous version of the kernel (2.6.18-4)


-- Package-specific info:

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

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

Versions of packages linux-image-2.6.21-1-686 depends
on:
ii  initramfs-tools [linux-initra 0.88   tools for
generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for
managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-20  Yet
Another mkInitRD

Versions of packages linux-image-2.6.21-1-686
recommends:
ii  libc6-i6862.5-9+b1   GNU C
Library: Shared libraries [i

-- debconf information excluded





  


___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com

--- End Message ---
--- Begin Message ---
Version: 2.6.26-1

this is said to have been fixed since then, thus closing.

-- 
maks

--- End Message ---

Bug#493479: marked as done (linux-image-2.6.26-1-amd64: 2.6.26-1 freezes soon after boot, a regression compared to 2.6.25-2)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:29:46 +0100
with message-id <20090309132946.gp3...@baikonur.stro.at>
and subject line Re: linux-image-2.6.26-1-amd64: 2.6.26-1 freezes soon after 
boot, a regression compared to 2.6.25-2
has caused the Debian Bug report #493479,
regarding linux-image-2.6.26-1-amd64: 2.6.26-1 freezes soon after boot, a 
regression compared to 2.6.25-2
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.)


-- 
493479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493479
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-1
Severity: critical
Justification: breaks the whole system


[NB:  I refer below to self-compiled kernels a bit, but this report IS
against the stock kernel.]

I saw that there is a push to get 2.6.26 into Lenny, so when
linux-source-2.6.26_2.6.26-1_all.deb became available I decided I should
try building kernels with it for my desktop and file server machines.

I have carefully crafted '.config' files for each machine, and only install
the Debian stock kernels as safety backups (in case of some major oversight
on my part).  I use 'make oldconfig' to ease the process of deciding about
config changes with each kernel release.

I have 3 machines running AMD Athlon 64 X2 dual core CPUs.  One is a
desktop machine, and the other 2 are recently-built, less-powerful machines
I will be using as servers.

On my desktop machine (running Sid) -- most of the kernel-relevant hardware
located on a Gigabyte GA-M59SLI-S5 motherboard -- the new custom kernel
built without error and ran perfectly.

On my fileserver machine (running Lenny) -- with a much different ECS
AMD790GM-M2 motherboard -- the custom kernel built without error, but
freezes soon after boot:  no panic/oops/segfault, no error message of any
kind.

I assumed I made a config error, because added new configs for RAID+LVM for
two 500GB drives I just purchased (and tested with 'badblocks') for a RAID1
array.  After several attempts to recompile, making slight, then drastic,
config changes hoping to just get it to boot, I decided to try the stock
kernel.

The stock kernel experiences the same freeze, without error messages.

When I discovered that, I wanted to be helpful and try to pin down a
specific configuration or other cause for the freeze.  I know that the
hardware is perfectly functional:  I am using it to write this bug report,
and it is running my own custom kernel built from Debian 2.6.25-7 sources.
The failure of the 2.6.26-1 kernel is some sort of regression against this
hardware.  (See below for the output of 'lspci -vv -nn'.)

On a personal note, I am currently on the path to learning how to program
for the Linux platform, and hope to learn enough to be able to package my
own self-written software for Debian.  Unfortunately, my background is with
another OS, and I have not (yet) learned how to track and pin down this
sort of bug using Linux development tools.  If you can give me clear enough
instructions, however, I am more than willing to dig into the source code
to try to locate the bug.  Possibly some well placed "printk" calls in
certain source files would help?

Without any of the proper debugging skills, I did attempt to learn the
cause of the freeze.  I doubt that anything I tried will be useful to you
folks, but I will report my findings Just In Case (TM):

1. Using GRUB to edit to "kernel" line, I added 
"debug earlyprink=vga initcall_debug loglevel=7" to my boot parameter
list.  Other than the "initcall_debug" parameter, I didn't notice much
effect -- I was hoping for some telltale message that would make it clear
what function was starting, but not finishing, when the system was locking
up.

A) On the stock kernel, each "calling" line was followed with a line
reporting a return value of 0, until the last call.  The last two lines of
output on the screen were:

calling inet_init+0x0/0x34a
NET: Registered protocol family 2

B) Think that the networking drivers were causing the freeze, I took my
last working '.config' for 2.6.25-7 and disabled CONFIG_NET, then ran 'make
oldconfig' for the 2.6.26-1 sources and built a kernel without networking
any support.  With the same debugging parameters on the GRUB "kernel" line
mentioned above, this was the last uncompleted initcall:

calling pci_init+0x0/0x2f

C) My guess about networking causing the problem was wrong, and it is not
clear that the PCI subsystem is causing the failure either.  Since this is
a dual core machine running an 

Bug#517347: linux-image-2.6.28-1-686 writing to swap disk

[maximilian attems]

On Fri, 27 Feb 2009, Jos van Wolput wrote:

> Package: linux-image-2.6.28-1-686
> Version: 2.6.28-1: i386 (debian/unstable)
> System: Debian/sid
> Processor: Intel Pentium M 1.70 GHz (Family 6 Model 13 Stepping 6)
> Memory: 995.30 MB physical, 494.15 MB virtual
>
> After upgrading  kernel 2.6.26-1-686 to 2.6.28-1-686 the system starts 
> writing to the swap disk while the physical memory is not fully used.
> After a quite short time of computing, the swap disk is full.
> This never happened with kernel 2.6.26 nor any other previous kernel. 
> Previously the swap disk was almost not used.
> The only change I did was uprading the linux-image.
>
> Best regards,
> Jos v. Wolput

can you try latest 2.6.28 snapshots and see if 2.6.28.7 fixed that?
see sid apt lines http://wiki.debian.org/DebianKernel

if not please try 2.6.29-rc7 from trunk and see how it goes there.
if that still does not fix it please report upstream on
bugzilla.kernel.org and let us know the bug nr.

thanks + kind regards

-- 
maks



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

Processed: tagging 502326

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.9.26etch2
> tags 502326 + pending
Bug#502326: linux-image-2.6.26-1-686: crash in iwl4965
Tags were: fixed-upstream upstream
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#518358: linux-image-2.6.28: iwlwifi: iwl3945 failed after suspend and no roaming

[maximilian attems]

On Fri, 06 Mar 2009, Daniel Huhardeaux wrote:

> [...]
>
> > It change something from 2.6.28: when I ifdown wlan0 I can get ifup
> > working correctly without rmmod/modprobe iwl3945 module.
>
> Have to correct this: it's only working if I try to reconnect to the  
> _same_ AP. If I ifdown from one AP and try to ifup to another one, even  
> the new one being in BSS, it wont work: have to unload/reload iwl3945  
> module.
>
> -- 
> Daniel

can you check against 2.6.29-rc7 trunk snapshot builds, see apt lines
http://wiki.debian.org/DebianKernel



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

Bug#515508: linux-image-2.6.28-1-amd64: Microsoft Natural keyboard is not functioning

[maximilian attems]

can you please check 2.6.29-rc7 from trunk, see apt lines
http://wiki.debian.org/DebianKernel




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

Processed: reassign 502326 to firmware-iwlwifi

[Debian Bug Tracking System]

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

> reassign 502326 firmware-iwlwifi
Bug#502326: linux-image-2.6.26-1-686: crash in iwl4965
Bug reassigned from package `linux-image-2.6.26-1-686' to `firmware-iwlwifi'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#483005: marked as done (linux-image-2.6.24-1-686: Sky2 driver's watchdog hangs vlans)

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 14:02:11 +0100
with message-id <20090309130211.gi13...@stro.at>
and subject line Re: linux-image-2.6.24-1-686: Sky2 driver's watchdog hangs 
vlans
has caused the Debian Bug report #483005,
regarding linux-image-2.6.24-1-686: Sky2 driver's watchdog hangs vlans
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.)


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

Note: I posted this bug to
http://bugzilla.kernel.org/show_bug.cgi?id=10693 because I think it is
a "generic" kernel bug, not specifically linked to Debian.  I suppose
here is the right place to post it.  Sorry for the double posting.

I configured multiple VLANs on eth1 (vlan161 to vlan166 + vlan170,
using /etc/network/interfaces).  Everything works fine for some time
(a few
minutes up to a few days), then for some unknown reason the sky2
driver suddenly hangs and restarts.  Unfortunately, the VLAN support
seems broken after sky2 restarts.  I get the following dmesg output:

May 13 14:07:42 wibox kernel: sky2 eth1: hung mac 0:124 fifo 195 (115:110)
May 13 14:07:42 wibox kernel: sky2 eth1: receiver hang detected
May 13 14:07:42 wibox kernel: sky2 eth1: disabling interface
May 13 14:07:42 wibox kernel: sky2 eth1: enabling interface
May 13 14:07:44 wibox kernel: sky2 eth1: Link is up at 100 Mbps, full
duplex, flow control rx
May 13 14:08:14 wibox kernel: sky2 eth1: rx length error: status
0x402300 length 64
May 13 14:08:14 wibox last message repeated 5 times
May 13 14:08:14 wibox kernel: sky2 eth1: rx length error: status
0x522100 length 82
May 13 14:08:14 wibox kernel: sky2 eth1: rx length error: status
0x402300 length 64
[...]

Steps to reproduce:
Configure some VLANs on a sky2-managed Gigabit Ethernet port, and
manage to get the sky2 driver to hang and automatically restart (I
don't know how to
force the sky2 driver to hang, I would just flow some trafic through
the VLANs for some time, but there is probably a better way).  You
will then see that VLAN tagged packets are dropped, but untagged
packets are ok.

My opinion:
Basically, it seems that everything is properly initialized, including
VLAN tags associated to each interface.  But if for some reason the
sky2 watchdog detects a hang, it restarts the interface, but it
forgets to set the VLANs again.  From then on, all packets received
are rejected because they are tagged and the sky2 driver excepts
untagged packets (hence the "rx length" error message).

Therefore, after any hang, the watchdog does not restart the interface
properly when VLAN tagging is used.

In sky2.c (line 2195), the error message "%s: rx length error: status
%#x length %d\n" is displayed only if (line 2177) length != count
(actual length different than expected length).  The VLAN ID bytes are
taken into account (on line 2151) like this:
#ifdef SKY2_VLAN_TAG_USED
/* Account for vlan tag */
if (sky2->vlgrp && (status & GMR_FS_VLAN))
count -= VLAN_HLEN;
#endif

In my error messages, I can read that the status is equal to 0x402300
or 0x522100, for example (see above), and therefore I known that
(status & GMR_FS_VLAN) is TRUE (GMR_FS_VLAN is equal to 1<<13).  Since
I get rx length errors, I believe that the count does not take into
account the VLAN header bytes, and I think that the only possibility
for this to happen is if sky2->vlgrp is NULL.

Apparently, sky2->vlgrp gets set properly upon driver initialization,
but it gets unset when the sky2 watchdog restarts the device.

sky2->vlgrp seems to be set only in function sky2_vlan_rx_register (on
line 1155).

And function sky2_vlan_rx_register gets called only in
sky2_init_netdev (on line 4011):
#ifdef SKY2_VLAN_TAG_USED
/* The workaround for FE+ status conflicts with VLAN tag
 * detection. */
if (!(sky2->hw->chip_id == CHIP_ID_YUKON_FE_P &&
  sky2->hw->chip_rev == CHIP_REV_YU_FE2_A0)) {
dev->features |= NETIF_F_HW_VLAN_TX | NETIF_F_HW_VLAN_RX;
dev->vlan_rx_register = sky2_vlan_rx_register;
}
#endif

So the solution might be to cut and paste this code from
sky2_init_netdev (which does not seem to be called when the sky2
watchdog restarts the device) into sky2_up (which is called both upon
initialization of the device, and when the watchdog restarts the
device)?

Thanks for your kind help!

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

Bug#475852: marked as done (xserver-xorg-input-synaptics: Synaptics touchpad completely stops working under gdm, xdm, kdm ... and X (gnome, openbox, kde...))

[Debian Bug Tracking System]

Your message dated Mon, 9 Mar 2009 13:59:49 +0100
with message-id <20090309125949.gh13...@stro.at>
and subject line Re: xserver-xorg-input-synaptics: Synaptics touchpad 
completely stops working under gdm, xdm, kdm ... and X (gnome, openbox, kde...)
has caused the Debian Bug report #475852,
regarding xserver-xorg-input-synaptics: Synaptics touchpad completely stops 
working under gdm, xdm, kdm ... and X (gnome, openbox, kde...)
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.)


-- 
475852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-input-synaptics
Version: 0.14.7~git20070706-2
Followup-For: Bug #461760

Hi,
this bug is present also on a HP Compaq 6720s laptop.

Here are the relevant bits of Xorg.0.log:

---8<---
(II) Synaptics touchpad driver version 0.14.6 (1406)
Synaptics Touchpad no synaptics event device found
(**) Option "Device" "/dev/psaux"
(**) Option "SHMConfig" "True"
(**) Option "HorizScrollDelta" "0"
Query no Synaptics: 6003C8
(EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device
(EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics Touchpad"
(II) UnloadModule: "synaptics"
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "SendCoreEvents" "true"
(**) Configured Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(==) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(**) Configured Mouse: Sensitivity: 1
(II) evaluating device (Configured Mouse)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
--->8---

The driver loads, but it can't find the hardware, thus it unloads. The mouse
that it configures is an USB mouse I'm using, since the touchpad isn't working
at all.


Here are some commands I gave:

---8<---
$ gsynaptics-init 
GSynaptics couldn't initialize.
You have to set 'SHMConfig' 'true' in Xorg.conf or XFree86.conf to use
GSynaptics
$ xinput list
"Virtual core keyboard" id=0[XKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Virtual core pointer"  id=1[XPointer]
Num_buttons is 32
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is 0
Max_value is -1
Resolution is 0
Axis 1 :
Min_value is 0
Max_value is -1
Resolution is 0
"Configured Mouse"  id=2[XExtensionPointer]
Num_buttons is 9
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 1
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 1
"Generic Keyboard"  id=3[XExtensionKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
$ synclient -l
Can't access shared memory area. SHMConfig disabled?
$
--->8---

I also tried downgrading Xorg to the lenny version, it didn't even start (I
don't know if the touchpad would've worked though).

Please *really* consider fixing this bug. Is it also present upstream?

Thanks,
David

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

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

Versions of packages xserver-xorg-input-synaptics depends on:
ii  libc6  2.7-10GNU C Library: Shared libraries
ii  libx11-6   2:1.1.4-1 X11 client-side library
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension librar
ii  libxi6 2:1.1.3-1 X11 Input extension library
ii  xserver-xorg-core  2:1.4.1~git20080131-3 Xorg X server - core server

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
patch got marked 

Bug#518344: [linux-source-2.6.28] hang on shutdown after acpid exiting

[maximilian attems]

On Thu, 05 Mar 2009, Brent S. Elmer wrote:

> Package: linux-source-2.6.28
> Version: 2.6.28-1
> Severity: normal
> 
> --- Please enter the report below this line. ---
> I am running a squeeze box except for I just built a 2.6.28 kernel from sid.
> When I shutdown while running the 2.6.28 kernel, the computer hangs 
> indefinitely.
> The last line that displays on the shutdown screen is acpid exiting.  I let 
> it sit for 
> 45 minutes and it never finished shutting down.  I have to power off the 
> computer.  When I power on the computer, 
> there don't appear to be any problems on startup.  If I boot to the old 
> 2.6.26 kernel I built and had been running 
> prior to the 2.6.28 kernel, the shutdown is fine.  I don't see any obvious 
> problems in the syslog.
> 
> I am running on an IBM Thinkpad T42p.
> 
> I built a 2.6.28 kernel for my desktop at home and have not noticed the 
> problem on shutdown.
> 

can you try latest snapshot, maybe 2.6.28.7 fixed that?
see sid apt lines http://wiki.debian.org/DebianKernel




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

Bug#517995: [linux-image-2.6.28-1-686] Intel sound dont work

[maximilian attems]

On Tue, 03 Mar 2009, Ronaldo Reis Junior wrote:

> Hi,
> 
> I have this sound card:
> 
> 0:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
> Controller (rev 03)
> Subsystem: Dell Device 0233
> Flags: bus master, fast devsel, latency 0, IRQ 21
> Memory at f6adc000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: 
> Kernel driver in use: HDA Intel
> Kernel modules: snd-hda-intel
> 
> Using the kernel 2.6.26 the sound work, but using the 2.6.28 the sound dont 
> work, but no errors are showed. The modules are the same, look:
> 

could you check latest 2.6.28 sid snapshots or 2.6.29-rc7 builds
and see if it works there for you?
see apt lines http://wiki.debian.org/DebianKernel

thanks



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

Bug#518467: linux-image-2.6.28-1-amd64: bluetooth mouse stutters since kernel upgrade

[maximilian attems]

On Fri, 06 Mar 2009, pHilipp Zabel wrote:

> On Fri, Mar 6, 2009 at 1:12 PM, Bastian Blank  wrote:
> > On Fri, Mar 06, 2009 at 12:41:25PM +0100, pHilipp Zabel wrote:
> >> ** Tainted: P M (17)
> >
> > You have a proprietary module loaded, we don't support kernels in this
> > state. Also the kernel logged machine checks, aka low level hardware
> > errors, which often shows serious hardware problems.
> >
> > Bastian
> 
> I installed mcelog, changed the video driver from fglrx to vesa and
> rebooted, same result. (/var/log/mcelog is empty.)
> 

could you test if 2.6.29-rc7 trunk builds fix it for you:
see apt line http://wiki.debian.org/DebianKernel



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

Bug#514292: linux-image-2.6.28-1-amd64: Bad page state in process 'emacs'

[maximilian attems]

On Thu, 26 Feb 2009, Luca Capello wrote:

> Should I report it upstream?  Any other hint to a possible solution?
> 
> PS, I have not reported other oops since my last mail because I switched
> back to linux-image-2.6.26-1-amd64_2.6.26-14~snapshot.12720: no oops at
> all with this version.

yes please report it on bugzilla.kernel.org and let us know the bug
number. latest snapshots have 2.6.28.7

you could also try 2.6.29-rc7 from snapshot if you can reproduce it there,
before?




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

Processed: severity of 518643 is important

[Debian Bug Tracking System]

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

> severity 518643 important
Bug#518643: linux-image-2.6.26-1-amd64: kvm host machine crashes with backtrace 
reference to kvm mmu call
Severity set to `important' from `important'

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: bug 517421 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10996

[Debian Bug Tracking System]

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

> forwarded 517421 http://bugzilla.kernel.org/show_bug.cgi?id=10996
Bug#517421: linux-image-2.6.28-1-686: Kernel log full of SKB BUG
Noted your statement that Bug has been forwarded to 
http://bugzilla.kernel.org/show_bug.cgi?id=10996.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: severity of 518643 is important

[Debian Bug Tracking System]

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

> severity 518643 important
Bug#518643: linux-image-2.6.26-1-amd64: kvm host machine crashes with backtrace 
reference to kvm mmu call
Severity set to `important' from `critical'

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: reassign 518315 to yaird

[Debian Bug Tracking System]

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

> reassign 518315 yaird
Bug#518315: linux-image-2.6.28-1-686: Installation: bad option given to yaird  
(-t)
Bug reassigned from package `linux-image-2.6.28-1-686' to `yaird'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Processed: severity of 518315 is grave

[Debian Bug Tracking System]

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

> severity 518315 grave
Bug#518315: linux-image-2.6.28-1-686: Installation: bad option given to yaird  
(-t)
Severity set to `grave' from `important'

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Equinox Festival - Lineup announced

[Raymond Salvatore Harmon]

[please post to lists and spread the word!]

FOR IMMEDIATE RELEASE:

Equinox Festival
equinoxfestival.org

Dates and Lineup announced!

June 12-14th London

More artists and speakers will be announced in the coming weeks!

ALL NEW WEBSITE with media links, artists/speaker bios, and ticket info.

The Equinox Festival, a 3 day media arts festival dedicated to
spiritual discovery and mystical tradition, will take place in London
June 12-14.

We are pleased to announce the following confirmed artists for this
years festival. Stay tuned for further development and surprise guests.



Music performance:

John Zorn
Æthenor
Adi Newton's T.A.G.C
Z'EV
Dieter Muh
Pietro Riparbelli- K11
Pestrepeller
Hati
Kinit Her

MORE TO COME IN THE FOLLOWING WEEKS

Ritual Performance:

Arktau Eos
Barry William Hale's NOKO
Raymond Salvatore Harmon



Lecture/Presentations:

Ralph Metzner
Erik Davis
David Beth
Edwin Pouncey
Paola Igliori
Masamba Fall
James Curcio
Carl Abrahamsson
Kendall Geers
Philip Farber
Aaron Gach
Matt Wiley

MORE TO COME IN THE FOLLOWING WEEKS

Films -

Paola Igliori
American Magus & The Seed of Joy

James Ferraro
Diminishing Shrine Recycles

Craig Baldwin
Mock Up On Mu

Harry Smith
Heaven and Earth Magic

Alejandro Jodorowsky
The Holy Mountain

Maya Deren
Ritual in Transfigured Time & Divine Horsemen: The Living
Gods of Haiti

Raymond Salvatore Harmon
YHVH & Tree of Knowledge/Tree of Life


MORE ARTISTS TO COME! SURPRISE GUESTS!

Tickets go on Sale March 20th via Wegottickets.com

more info at:
equinoxfestival.org



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

Bug#518921: i386 missing syscall detection is broken on amd64

[Anders Kaseorg]

Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-13
Tags: patch
Severity: important

Linux commit c09249f8d1b84344eca882547afdbffee8c09d14 in v2.6.29-rc4 fixes 
a bug that is completely breaking glibc's missing syscall detection for 
i386 binaries on x86_64.  This bug affects all kernels between v2.6.26 and 
v2.6.29-rc3.

One of the symptoms of this bug is that when i386 binaries compiled on 
newer systems use the popen() call, which attempts to detect the new 
pipe2() syscall in v2.6.27, the subprocess will output to a random file 
descriptor (typically stdout) instead of the pipe; see 
.  There are likely to be more and more 
problems as new syscalls get implemented.

I have verified that this patch applies on kernel 2.6.26 and fixes the 
problem.  Please apply it to the Debian kernel.


>From c09249f8d1b84344eca882547afdbffee8c09d14 Mon Sep 17 00:00:00 2001
From: Roland McGrath 
Date: Fri, 6 Feb 2009 18:15:18 -0800
Subject: [PATCH] x86-64: fix int $0x80 -ENOSYS return

One of my past fixes to this code introduced a different new bug.
When using 32-bit "int $0x80" entry for a bogus syscall number,
the return value is not correctly set to -ENOSYS.  This only happens
when neither syscall-audit nor syscall tracing is enabled (i.e., never
seen if auditd ever started).  Test program:

/* gcc -o int80-badsys -m32 -g int80-badsys.c
   Run on x86-64 kernel.
   Note to reproduce the bug you need auditd never to have started.  */

#include 
#include 

int
main (void)
{
  long res;
  asm ("int $0x80" : "=a" (res) : "0" (9));
  printf ("bad syscall returns %ld\n", res);
  return res != -ENOSYS;
}

The fix makes the int $0x80 path match the sysenter and syscall paths.

Reported-by: Dmitry V. Levin 
Signed-off-by: Roland McGrath 
---
 arch/x86/ia32/ia32entry.S |8 +---
 1 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
index 256b00b..5a0d76d 100644
--- a/arch/x86/ia32/ia32entry.S
+++ b/arch/x86/ia32/ia32entry.S
@@ -418,9 +418,9 @@ ENTRY(ia32_syscall)
orl   $TS_COMPAT,TI_status(%r10)
testl $_TIF_WORK_SYSCALL_ENTRY,TI_flags(%r10)
jnz ia32_tracesys
-ia32_do_syscall:   
cmpl $(IA32_NR_syscalls-1),%eax
-   ja  int_ret_from_sys_call   /* ia32_tracesys has set RAX(%rsp) */
+   ja ia32_badsys
+ia32_do_call:
IA32_ARG_FIXUP
call *ia32_sys_call_table(,%rax,8) # xxx: rip relative
 ia32_sysret:
@@ -435,7 +435,9 @@ ia32_tracesys:
call syscall_trace_enter
LOAD_ARGS32 ARGOFFSET  /* reload args from stack in case ptrace changed 
it */
RESTORE_REST
-   jmp ia32_do_syscall
+   cmpl $(IA32_NR_syscalls-1),%eax
+   ja  int_ret_from_sys_call   /* ia32_tracesys has set RAX(%rsp) */
+   jmp ia32_do_call
 END(ia32_syscall)
 
 ia32_badsys:
-- 
1.6.2-rc2.GIT




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

Re: lenny updates

[dann frazier]

On Tue, Mar 03, 2009 at 09:44:04PM +0100, Ola Lundqvist wrote:
> Hi Dann
> 
> You asked about the latest status and here it is.
> Please tell which ones you want me to fix for the next lenny release of the 
> kernel. I'll prepare
> a patch and regression test that version for you.
> 
> #510787:
> Refers to an other bug report that was not openvz specific. Should it be
> forwarded to an non-openvz version of the kernel or kept here?

I don't think it really matters - you can reassign to linux-2.6 if you
like though.

> In any case I have added latest information to the report and told where
> the problem has been forwarded.

Thanks!

> #511165:
> Patch exist for 2.6.24 and 2.6.26. Fix is available in
> http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=b5e1f74cee5bc2c45bdca53a7218fb8de89215dd
> Not sure if this is an ABI breaker.

Seems straightforward, and shouldn't change the ABI. I'll commit it
assuming my test build shows that.

> #500876:
> Fix available in:
> http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=777e8164ebf8a03e43511983cdec472f8691a8af
> Problem is about to be verified. Regression tested without problems seen.

I couldn't reproduce this one (tried dual quad core intel server & a
single quad core amd), but user claims this fixed the bug for me and I
haven't seen any issues with this patch so its been committed.

> #503097:
> Reported as http://bugzilla.openvz.org/show_bug.cgi?id=930
> Seems to be a duplicate of #500876 above.

Cool. If you think so, it might be good to have Carlos test one of
these builds to verify:
  http://people.debian.org/~dannf/bugs/500876/

(Tomorrow's snapshot builds should also include it)

> #505174:
> This is a request to go up to the latest version that includes fixes for
> all the ones in this mail that describe that there is a fix available.
> Unfortunatly there are ABI breakers...

Its probably a good idea to stick with specific issues/fixes now that
its a stable release.

> #508773:
> Patch available in http://bugzilla.openvz.org/show_bug.cgi?id=1054
> Fix in 
> http://git.openvz.org/?p=linux-2.6.24-openvz;a=commit;h=20bd90762d4df4a3c7c247b660c696bdd0a27709
> Do not look like an ABI breaker to me.

Yep, definitely shouldn't break the ABI, and seems like a good
candidate.

> #500145:
> Forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1143
> Marked as dupliate of http://bugzilla.openvz.org/show_bug.cgi?id=1067
> Not solved yet.

ok

> #501985:
> From: maximilian attems
> the upstream nfs fixes are abi breakers and thus can't be integrated
> at this point they will be for the first point release were abi
> breaking will be allowed again.

What is the fix for this - does upstream openvz include it?

> #494445:
> There are a number of problems in this area. Fixes are available.
> However some of them are ABI breakers.

The nf_conntrack_ipv6 module doesn't appear to be in 2.6.26-13. Maybe
it was disabled because of this bug? At this point, turning it
on/fixing probably falls into the category of a feature requests that
doesn't enable hardware, so wouldn't have a sufficient severity (>=
important).

> #500645:
> Fix available in http://bugzilla.openvz.org/show_bug.cgi?id=1034
> http://git.openvz.org/?p=linux-2.6.26-openvz;a=commit;h=6d18ba377cfa3e86ee830fe6a5fce52b8fd51039
> I can not see that this is an ABI breaker, so it should be possibly to
> apply this one without problem.

The patch itself certainly looks trivial enough - but the bug is only of
severity "normal". If we think this actually deserves a >= important
severity, we should bump the severity of the report.

Thanks Ola!

-- 
dann frazier


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