date:20120130

Le lundi 30 janvier 2012 à 12:51 +0300, Denis Kirjanov a écrit :
 I'll check this out. After kernel.org was cracked I've missed
 @kernel.org mail account.


At first glance, start_tx() is racy against TX completion.

It does :

if (np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 1 
!netif_queue_stopped(dev)) {
/* do nothing */
} else {
netif_stop_queue (dev);
}

So it can call netif_stop_queue() while TX completion handler did a
cleanup of all queued packets right before.


Note intr_handler() doesnt hold the queue spinlock when it does :

if (netif_queue_stopped(dev) 
np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 4) {
/* The ring is no longer full, clear busy flag. */
netif_wake_queue (dev);
}





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327918447.2288.24.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC

Bug#657963: Problem after nfs-common upgrade

2012-01-30 Thread Nicolas Hennion

Package: nfs-common
Version: 1:1.2.2-4squeeze2
Severity: important

After a system upgrade (apt-get update  apt-get upgrade), i have the 
following 
message on my Debian Squeeze Server:

===
sudo apt-get upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
1 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer [O/n] ? O
Paramétrage de nfs-common (1:1.2.2-4squeeze2) ...
insserv: Service portmap has to be enabled to start service nfs-common
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg : erreur de traitement de nfs-common (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
configured to not write apport reports
  Des erreurs ont été rencontrées pendant 
l'exécution :
 nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
===

Any idea ?

Nicolas

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.112+nmu2   add and remove users and groups
ii  initscripts 2.88dsf-13.1 scripts for initializing and shutt
ii  libc6   2.11.3-2 Embedded GNU C Library: Shared lib
ii  libcap2 1:2.19-3 support for getting/setting POSIX.
ii  libcomerr2  1.41.12-4stable1 common error description library
ii  libevent-1.4-2  1.4.13-stable-1  An asynchronous event notification
ii  libgssapi-krb5-21.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - k
ii  libgssglue1 0.1-4mechanism-switch gssapi library
ii  libk5crypto31.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - C
ii  libkrb5-3   1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries
ii  libnfsidmap20.23-2   An nfs idmapping library
ii  librpcsecgss3   0.19-2   allows secure rpc communication us
ii  libwrap07.6.q-19 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  netbase 4.45 Basic TCP/IP networking system
ii  portmap 6.0.0-2  RPC port mapper
ii  ucf 3.0025+nmu1  Update Configuration File: preserv

nfs-common recommends no packages.

nfs-common suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120130094901.8256.80357.report...@frodo.nicolargo.com

Bug#657963:

2012-01-30 Thread Nicolas Hennion

Solved by using the following commands:

# dpkg-reconfigure portmap
# apt-get upgrade

___
*
Avant donc que d'écrire, apprenez à penser.
-+- Nicolas Boileau, Art poétique -+-
*

Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

Le lundi 30 janvier 2012 à 11:14 +0100, Eric Dumazet a écrit :
 Le lundi 30 janvier 2012 à 12:51 +0300, Denis Kirjanov a écrit :
  I'll check this out. After kernel.org was cracked I've missed
  @kernel.org mail account.
 
 
 At first glance, start_tx() is racy against TX completion.
 
 It does :
 
 if (np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 1 
 !netif_queue_stopped(dev)) {
 /* do nothing */
 } else {
 netif_stop_queue (dev);
 }
 
 So it can call netif_stop_queue() while TX completion handler did a
 cleanup of all queued packets right before.
 
 
 Note intr_handler() doesnt hold the queue spinlock when it does :
 
 if (netif_queue_stopped(dev) 
 np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 4) {
 /* The ring is no longer full, clear busy flag. */
 netif_wake_queue (dev);
 }
 

So I would try following patch :

 drivers/net/ethernet/dlink/sundance.c |   12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/drivers/net/ethernet/dlink/sundance.c 
b/drivers/net/ethernet/dlink/sundance.c
index 28a3a9b..c671a6c 100644
--- a/drivers/net/ethernet/dlink/sundance.c
+++ b/drivers/net/ethernet/dlink/sundance.c
@@ -1099,11 +1099,13 @@ start_tx (struct sk_buff *skb, struct net_device *dev)
tasklet_schedule(np-tx_tasklet);
 
/* On some architectures: explicitly flush cache lines here. */
-   if (np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 1 
-   !netif_queue_stopped(dev)) {
-   /* do nothing */
-   } else {
-   netif_stop_queue (dev);
+   if (np-cur_tx - np-dirty_tx = TX_QUEUE_LEN - 1) {
+   unsigned long flags;
+
+   spin_lock_irqsave(np-lock, flags);
+   if (np-cur_tx - np-dirty_tx = TX_QUEUE_LEN - 1)
+   netif_stop_queue(dev);
+   spin_unlock_irqrestore(np-lock, flags);
}
if (netif_msg_tx_queued(np)) {
printk (KERN_DEBUG





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327919763.2288.26.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC

Bug#605090: Linux 3.2 in wheezy

2012-01-30 Thread Brad Spengler

 Indeed. Brad, I'm not sure if you received the initial mail, so if you
 have any comment???

It looks like there were quite a few messages I wasn't involved in ;)  

Regarding minimizing the patchset, we do that already where we see 
opportunities to do so.  We used to carry a large constifying patch 
which has now been replaced with a gcc plugin.  Likewise with the kernel 
stack clearing feature.

As far as gutting the patch for whatever features someone not involved 
in the project thinks are the only ones necessary (I saw a few posts 
in the thread asking for that) -- I don't think it's a good idea and 
I'm not interested at all in assisting that.

If we're going to be in the business of telling other people what to do 
with their free time, might I suggest that Debian improve its userland 
hardening so that it's not in last place?  As a Debian user myself, I
can assure you that no one cares about a miniscule performance hit from
PIE on i386 in su/passwd.  There's no reason not to have these privilege
boundaries hardened -- and very disappointing for us as 
MPROTECT/ASLR/GRKERNSEC_BRUTEFORCE would have provided an effective 
deterrent against exploitation of the /proc/pid/mem vuln were it not
for distros' userland hardening being asleep on the job.  That failure
will continue to bite users.

Frankly it makes more sense for me to offer .debs myself than to deal 
with a bureaucracy and non-standard kernel in Debian.  It contains 
who-knows-what extra code, and I doubt anyone looked at any of it to see if 
it allows for some way to leak information I prevent against a vanilla 
kernel, or a way to bypass any other existing protection.  There's more 
to security (a whole-system concept) than just the ripping of individual 
features.

-Brad


signature.asc
Description: Digital signature

Re: [Debian] Re: Possible support for openvz also in the next version of stable

2012-01-30 Thread Alexander Gerasiov

Mon, 30 Jan 2012 12:14:56 +0400
Kirill Kolyshkin k...@parallels.com wrote:

 Seems to be the best course of action, given the circumstances.
Guys, how are you planning to care with this?
Package rhel kernels in deb or support actual debian kernels with openvz
patches?

As for me, I'm interested in debian openvz kernels, and it's really sad
that kernel team don't want to provide -openvz flavor in wheezy. (As I
understood the core point is lack of support from Parallels in porting
openvz patches to actual long term kernel.)


 
 Pavel Emelyanov xe...@parallels.com wrote:
 
 
 On 01/28/2012 04:17 PM, Ola Lundqvist wrote:
  Hi Ben and Pavel
 
  Thanks a lot. Then I think I know the way forward. We will create a
  repository (either on debian.net or keep the one on openvz.org) and
  put the kernels there. I will document this in the vzctl and vzquota
  packages to give further instructions.
 
  Pavel, do this sounds good to you.
 
 Yup! Kir, what do you think?
 
  Best regards,
 
  // Ola
 
 Thanks,
 Pavel
 
 ___
 Debian mailing list
 deb...@openvz.org
 https://openvz.org/mailman/listinfo/debian


-- 
Best regards,
 Alexander GQ Gerasiov

 Contacts:
 e-mail:g...@cs.msu.su Jabber:  g...@jabber.ru
 Homepage:  http://gq.net.ru ICQ: 7272757
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120130171338.74d7cd75@desktopvm.lvknet

Re: [Debian] Re: Possible support for openvz also in the next version of stable

2012-01-30 Thread Ola Lundqvist


Hi Alexander

Quoting Alexander Gerasiov g...@debian.org:

Mon, 30 Jan 2012 12:14:56 +0400
Kirill Kolyshkin k...@parallels.com wrote:


Seems to be the best course of action, given the circumstances.

Guys, how are you planning to care with this?
Package rhel kernels in deb or support actual debian kernels with openvz
patches?


It will be rhel kernels in deb format. I'm going to test out some aspects
to see what kind of obstacles we can face. I'm personally using a  
setup that is heavily based on things that may be debian specific. I'm  
running root system on lvm on cryptfs or root on lvm on raid. It would  
be good if that still works fine.



As for me, I'm interested in debian openvz kernels, and it's really sad
that kernel team don't want to provide -openvz flavor in wheezy. (As I
understood the core point is lack of support from Parallels in porting
openvz patches to actual long term kernel.)


Yes you are right. This is the core point. Unfortunatly this is the situation.

Best regards,

// Ola





Pavel Emelyanov xe...@parallels.com wrote:


On 01/28/2012 04:17 PM, Ola Lundqvist wrote:
 Hi Ben and Pavel

 Thanks a lot. Then I think I know the way forward. We will create a
 repository (either on debian.net or keep the one on openvz.org) and
 put the kernels there. I will document this in the vzctl and vzquota
 packages to give further instructions.

 Pavel, do this sounds good to you.

Yup! Kir, what do you think?

 Best regards,

 // Ola

Thanks,
Pavel

___
Debian mailing list
deb...@openvz.org
https://openvz.org/mailman/listinfo/debian



--
Best regards,
 Alexander GQ Gerasiov

 Contacts:
 e-mail:g...@cs.msu.su Jabber:  g...@jabber.ru
 Homepage:  http://gq.net.ru ICQ: 7272757
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1






--
 --- 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
Archive: 
http://lists.debian.org/20120130143251.19701m1r11m5a...@webmail.inguza.net

Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

On Mon, 2012-01-30 at 11:14 +0100, Eric Dumazet wrote:
 Le lundi 30 janvier 2012 à 12:51 +0300, Denis Kirjanov a écrit :
  I'll check this out. After kernel.org was cracked I've missed
  @kernel.org mail account.
 
 
 At first glance, start_tx() is racy against TX completion.
 
 It does :
 
 if (np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 1 
 !netif_queue_stopped(dev)) {
 /* do nothing */
 } else {
 netif_stop_queue (dev);
 }
 
 So it can call netif_stop_queue() while TX completion handler did a
 cleanup of all queued packets right before.

Yes, I spotted that.  But no descriptors are pushed to the hardware
here; that's done in the driver's TX tasklet.  Although... maybe that
can run immediately when scheduled from here?  I've never had to deal
with tasklets so I really don't know their semantics.

Ben.

 Note intr_handler() doesnt hold the queue spinlock when it does :
 
 if (netif_queue_stopped(dev) 
 np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 4) {
 /* The ring is no longer full, clear busy flag. */
 netif_wake_queue (dev);
 }
 
 
 

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Re: Linux 3.2 in wheezy

On Mon, 2012-01-30 at 11:05 +0100, Yves-Alexis Perez wrote:
 (adding few CC:s to keep track on the bug)
 
 On dim., 2012-01-29 at 21:26 +, Ben Hutchings wrote:
  On Sun, 2012-01-29 at 20:57 +0100, Yves-Alexis Perez wrote:
   On dim., 2012-01-29 at 18:22 +, Ben Hutchings wrote:
Featuresets
---

The only featureset provided will be 'rt' (realtime), currently built
for amd64 only.  If there is interest in realtime support for other
architectures, we may be able to add that.  However, we do need to
consider the total time taken to build binary packages for each
architecture.

If there are particular container features that should be enabled or
backported to provide a useful replacement for OpenVZ or VServer,
please let us know.  We cannot promise that these will all be enabled
but we need to know what is missing. 
   
   So in the end what are the reasons for not trying the grsecurity
   featureset? #605090 lacks any reply from the kernel team since quite a
   while, and especially after answers were provided to question asked.
  
  You already know the main reason:
   Feature-wise, Brad Sprengler and the PaX team still add stuff, like the
   gcc plugins or hardening features like symbols hiding, fix bugs (for
   example in RBAC code), while few of them reach mainline.
  
  I realise that the mainline Linux developers have sometimes been
  unreasonably resistant to these changes and I'm not intending to assign
  blame for this.  But practically this means that we have to either carry
  the featureset indefinitely or disappoint users by removing it in a
  later release.  (See the complaints about removing OpenVZ in wheezy
  despite 4 years' advance notice of this.)
 
 I understand this, and I still see the grsec featureset as a valuable
 project. Indeed, reducing the diff wrt. upstream in Debian kernel is an
 important goal (especially considering the time involvement).
 
 Now, I still think having a hardened Debian kernel inside the
 distribution is helpful
[...]

I agree and I would like to see hardening of *all* our configurations,
where the performance cost is not too much.  That's going to protect all
our users rather than just people who seek out a special paranoid
configuration.

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Re: Linux 3.2 in Debian 7.0

2012-01-30 Thread Tim Gardner


On 01/29/2012 08:46 PM, Ben Hutchings wrote:

Greg,

We've decided to go with Linux 3.2 for the next Debian stable release,
so we'll be interested in a 3.2.y longterm series.  I believe there was
a volunteer from Ubuntu to look after that once you've had enough of it,
but I seem to have lost the relevant mail.

Ben.



Hi Ben - that email thread never really bottomed out on _who_ would be 
the 3.2 stable maintainer, though I expect it will be someone on my 
team. Here is the thread:


http://www.gossamer-threads.com/lists/linux/kernel/1475904

rtg
--
Tim Gardner tim.gard...@canonical.com


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f26a4fd.8030...@canonical.com

Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

Le lundi 30 janvier 2012 à 14:05 +, Ben Hutchings a écrit :

 Yes, I spotted that.  But no descriptors are pushed to the hardware
 here; that's done in the driver's TX tasklet.  Although... maybe that
 can run immediately when scheduled from here?  I've never had to deal
 with tasklets so I really don't know their semantics.

Thats probable on SMP ...





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327933736.2288.41.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC

Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

On Mon, 2012-01-30 at 15:28 +0100, Eric Dumazet wrote:
 Le lundi 30 janvier 2012 à 14:05 +, Ben Hutchings a écrit :
 
  Yes, I spotted that.  But no descriptors are pushed to the hardware
  here; that's done in the driver's TX tasklet.  Although... maybe that
  can run immediately when scheduled from here?  I've never had to deal
  with tasklets so I really don't know their semantics.
 
 Thats probable on SMP ...

The bug report is for a UP system running a kernel built with
SMP-alternatives.

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

Le lundi 30 janvier 2012 à 14:41 +, Ben Hutchings a écrit :
 On Mon, 2012-01-30 at 15:28 +0100, Eric Dumazet wrote:
  Le lundi 30 janvier 2012 à 14:05 +, Ben Hutchings a écrit :
  
   Yes, I spotted that.  But no descriptors are pushed to the hardware
   here; that's done in the driver's TX tasklet.  Although... maybe that
   can run immediately when scheduled from here?  I've never had to deal
   with tasklets so I really don't know their semantics.
  
  Thats probable on SMP ...
 
 The bug report is for a UP system running a kernel built with
 SMP-alternatives.

Hmm, TX _completion_ is not run from tasklet but hardware IRQ, this is
why I added the spin_lock_irqsave().


Tasklet fires the TX, but hardware IRQ does the TX completion part.

This driver is ... interesting :)







-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327935455.2297.5.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC

Processed: Re: ncpfs: Causes kernel tracelog with kernel 2.6.38

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

 severity 623212 important
Bug #623212 [ncpfs] ncpfs: Causes kernel tracelog with kernel 2.6.38
Severity set to 'important' from 'grave'

 reassign 623212 src:linux-2.6 2.6.38-3
Bug #623212 [ncpfs] ncpfs: Causes kernel tracelog with kernel 2.6.38
Bug reassigned from package 'ncpfs' to 'src:linux-2.6'.
Bug No longer marked as found in versions ncpfs/2.2.6-8.
Bug #623212 [src:linux-2.6] ncpfs: Causes kernel tracelog with kernel 2.6.38
Bug Marked as found in versions linux-2.6/2.6.38-3.
 tags 623212 + moreinfo
Bug #623212 [src:linux-2.6] ncpfs: Causes kernel tracelog with kernel 2.6.38
Added tag(s) moreinfo.
 quit
Stopping processing here.

Please contact me if you need assistance.
-- 
623212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623212
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
Archive: 
http://lists.debian.org/handler.s.c.13279358763124.transcr...@bugs.debian.org

Re: Linux 3.2 in wheezy

2012-01-30 Thread Roland Mas

Ben Hutchings, 2012-01-29 18:22:05 + :

[...]

 Featuresets
 ---

 The only featureset provided will be 'rt' (realtime), currently built
 for amd64 only.  If there is interest in realtime support for other
 architectures, we may be able to add that.  However, we do need to
 consider the total time taken to build binary packages for each
 architecture.

  I would like to second the suggestion for also enabling rt for i386.
My rationale is that this would allow for smooth audio (low latency and
no clicks) on existing hardware.  Upgrading the hardware to something
more modern (and amd64) would probably lead to good audio without
needing rt; I guess it makes as much sense to enable it on i386, where
it's really going to make a difference, as on amd64, where it may not be
needed for this particular use case.

Roland.

[Not subscribed to -kernel, please Cc: me on replies; I'll try to check
the archives from time to time though.]
-- 
Roland Mas

Bee There Orr Bee A Rectangular Thyng!
  -- in Soul Music (Terry Pratchett)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/87ehuhfcv8@mirexpress.internal.placard.fr.eu.org

Bug#656476: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

Le lundi 30 janvier 2012 à 15:57 +0100, Eric Dumazet a écrit :

 Hmm, TX _completion_ is not run from tasklet but hardware IRQ, this is
 why I added the spin_lock_irqsave().
 
 
 Tasklet fires the TX, but hardware IRQ does the TX completion part.
 
 This driver is ... interesting :)
 

Oh well, we also must make sure we held np-lock in TX completion when
doing our test to eventually call netif_wake_queue(), I missed it was
released too early.

here is a more complete patch.

diff --git a/drivers/net/ethernet/dlink/sundance.c 
b/drivers/net/ethernet/dlink/sundance.c
index 28a3a9b..d5e9472 100644
--- a/drivers/net/ethernet/dlink/sundance.c
+++ b/drivers/net/ethernet/dlink/sundance.c
@@ -1099,11 +1099,13 @@ start_tx (struct sk_buff *skb, struct net_device *dev)
tasklet_schedule(np-tx_tasklet);
 
/* On some architectures: explicitly flush cache lines here. */
-   if (np-cur_tx - np-dirty_tx  TX_QUEUE_LEN - 1 
-   !netif_queue_stopped(dev)) {
-   /* do nothing */
-   } else {
-   netif_stop_queue (dev);
+   if (np-cur_tx - np-dirty_tx = TX_QUEUE_LEN - 1) {
+   unsigned long flags;
+
+   spin_lock_irqsave(np-lock, flags);
+   if (np-cur_tx - np-dirty_tx = TX_QUEUE_LEN - 1)
+   netif_stop_queue(dev);
+   spin_unlock_irqrestore(np-lock, flags);
}
if (netif_msg_tx_queued(np)) {
printk (KERN_DEBUG
@@ -1242,8 +1244,8 @@ static irqreturn_t intr_handler(int irq, void 
*dev_instance)
hw_frame_id = ioread8(ioaddr + TxFrameId);
}
 
+   spin_lock(np-lock);
if (np-pci_dev-revision = 0x14) {
-   spin_lock(np-lock);
for (; np-cur_tx - np-dirty_tx  0; np-dirty_tx++) {
int entry = np-dirty_tx % TX_RING_SIZE;
struct sk_buff *skb;
@@ -1267,9 +1269,7 @@ static irqreturn_t intr_handler(int irq, void 
*dev_instance)
np-tx_ring[entry].frag[0].addr = 0;
np-tx_ring[entry].frag[0].length = 0;
}
-   spin_unlock(np-lock);
} else {
-   spin_lock(np-lock);
for (; np-cur_tx - np-dirty_tx  0; np-dirty_tx++) {
int entry = np-dirty_tx % TX_RING_SIZE;
struct sk_buff *skb;
@@ -1286,7 +1286,6 @@ static irqreturn_t intr_handler(int irq, void 
*dev_instance)
np-tx_ring[entry].frag[0].addr = 0;
np-tx_ring[entry].frag[0].length = 0;
}
-   spin_unlock(np-lock);
}
 
if (netif_queue_stopped(dev) 
@@ -1294,6 +1293,7 @@ static irqreturn_t intr_handler(int irq, void 
*dev_instance)
/* The ring is no longer full, clear busy flag. */
netif_wake_queue (dev);
}
+   spin_unlock(np-lock);
/* Abnormal error summary/uncommon events handlers. */
if (intr_status  (IntrPCIErr | LinkChange | StatsMax))
netdev_error(dev, intr_status);





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327936900.2297.7.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC

Bug#657963: Problem after nfs-common upgrade

On Mon, 2012-01-30 at 15:01 +, Ben Hutchings wrote:
[...]
 Anyway, you must enable portmap if you need an NFS client:
 update-rc.d portmap defaults

Sorry, that should be:
update-rc.d portmap enable

 or disable nfs-common if you don't:
 update-rc.d nfs-common disable

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Bug#657963: Problem after nfs-common upgrade

On Mon, 2012-01-30 at 10:49 +0100, Nicolas Hennion wrote:
 Package: nfs-common
 Version: 1:1.2.2-4squeeze2
 Severity: important
 
 After a system upgrade (apt-get update  apt-get upgrade), i have the 
 following 
 message on my Debian Squeeze Server:
 
 ===
 sudo apt-get upgrade
 Lecture des listes de paquets... Fait
 Construction de l'arbre des dépendances   
 Lecture des informations d'état... Fait
 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
 1 partiellement installés ou enlevés.
 Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
 Souhaitez-vous continuer [O/n] ? O
 Paramétrage de nfs-common (1:1.2.2-4squeeze2) ...
 insserv: Service portmap has to be enabled to start service nfs-common
 insserv: exiting now!
 update-rc.d: error: insserv rejected the script header
[...]

This probably means you have disabled portmap, which means your service
configuration is broken.  However, when I tried that I saw a different
error message.

Anyway, you must enable portmap if you need an NFS client:
update-rc.d portmap defaults
or disable nfs-common if you don't:
update-rc.d nfs-common disable

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Bug#657963: marked as done (Problem after nfs-common upgrade)

Your message dated Mon, 30 Jan 2012 15:04:47 +
with message-id 1327935887.5400.454.camel@deadeye
and subject line Re: Bug#657963:
has caused the Debian Bug report #657963,
regarding Problem after nfs-common upgrade
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.)


-- 
657963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nfs-common
Version: 1:1.2.2-4squeeze2
Severity: important

After a system upgrade (apt-get update  apt-get upgrade), i have the 
following 
message on my Debian Squeeze Server:

===
sudo apt-get upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
1 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer [O/n] ? O
Paramétrage de nfs-common (1:1.2.2-4squeeze2) ...
insserv: Service portmap has to be enabled to start service nfs-common
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg : erreur de traitement de nfs-common (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
configured to not write apport reports
  Des erreurs ont été rencontrées pendant 
l'exécution :
 nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
===

Any idea ?

Nicolas

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.112+nmu2   add and remove users and groups
ii  initscripts 2.88dsf-13.1 scripts for initializing and shutt
ii  libc6   2.11.3-2 Embedded GNU C Library: Shared lib
ii  libcap2 1:2.19-3 support for getting/setting POSIX.
ii  libcomerr2  1.41.12-4stable1 common error description library
ii  libevent-1.4-2  1.4.13-stable-1  An asynchronous event notification
ii  libgssapi-krb5-21.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - k
ii  libgssglue1 0.1-4mechanism-switch gssapi library
ii  libk5crypto31.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - C
ii  libkrb5-3   1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries
ii  libnfsidmap20.23-2   An nfs idmapping library
ii  librpcsecgss3   0.19-2   allows secure rpc communication us
ii  libwrap07.6.q-19 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  netbase 4.45 Basic TCP/IP networking system
ii  portmap 6.0.0-2  RPC port mapper
ii  ucf 3.0025+nmu1  Update Configuration File: preserv

nfs-common recommends no packages.

nfs-common suggests no packages.

-- no debconf information


---End Message---
---BeginMessage---
On Mon, 2012-01-30 at 11:27 +0100, Nicolas Hennion wrote:
 Solved by using the following commands:
 
 
 # dpkg-reconfigure portmap
 # apt-get upgrade

OK, closing.

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Re: Linux 3.2 in wheezy

2012-01-30 Thread Peter Samuelson


[Brad Spengler]
 Frankly it makes more sense for me to offer .debs myself than to deal
 with a bureaucracy and non-standard kernel in Debian.  It contains
 who-knows-what extra code, and I doubt anyone looked at any of it to
 see if it allows for some way to leak information I prevent against a
 vanilla kernel, or a way to bypass any other existing protection.

I hope you aren't complaining that the Debian kernel team doesn't
include your patch, and also complaining that Debian kernel team
includes too many patches, in the same email.

Probably that isn't what you tried to say, but that's kinda what it
sounded like.

Peter


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120130154049.ga2...@p12n.org

Bug#657302: problem fixed for my laptop

2012-01-30 Thread flyingnu

fixed for my laptop with that patch 
https://bugzilla.kernel.org/show_bug.cgi?id=42588#c44


Thanks for the help



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f26c61d.2000...@gmx.com

Bug#657302: [3.1.8 - 3.2.1 regression] No more sound

2012-01-30 Thread Jonathan Nieder

tags 657302 + upstream patch moreinfo
forwarded 657302 https://bugzilla.kernel.org/show_bug.cgi?id=42588
quit

flyingnu wrote:

 fixed for my laptop with that patch
 https://bugzilla.kernel.org/show_bug.cgi?id=42588#c44

Thanks!  Here's a copy for convenience.

Not part of linux-next yet.
From: Takashi Iwai ti...@suse.de
Date: Wed, 25 Jan 2012 09:55:46 +0100
Subject: [PATCH 1/3] ALSA: hda - Fix silent output on ASUS A6Rp

commit 3b25eb690e8c7424eecffe1458c02b87b32aa001 upstream.

The refactoring of Realtek codec driver in 3.2 kernel caused a
regression for ASUS A6Rp laptop; it doesn't give any output.
The reason was that this machine has a secret master mute (or EAPD)
control via NID 0x0f VREF.  Setting VREF50 on this node makes the
sound working again.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=42588

Cc: sta...@kernel.org [v3.2+]
Signed-off-by: Takashi Iwai ti...@suse.de
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
 sound/pci/hda/patch_realtek.c |   10 ++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 1d07e8fa2433..9a63a193fc07 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5223,6 +5223,7 @@ static const struct hda_amp_list alc861_loopbacks[] = {
 /* Pin config fixes */
 enum {
 	PINFIX_FSC_AMILO_PI1505,
+	PINFIX_ASUS_A6RP,
 };
 
 static const struct alc_fixup alc861_fixups[] = {
@@ -5234,9 +5235,18 @@ static const struct alc_fixup alc861_fixups[] = {
 			{ }
 		}
 	},
+	[PINFIX_ASUS_A6RP] = {
+		.type = ALC_FIXUP_VERBS,
+		.v.verbs = (const struct hda_verb[]) {
+			/* node 0x0f VREF seems controlling the master output */
+			{ 0x0f, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_VREF50 },
+			{ }
+		},
+	},
 };
 
 static const struct snd_pci_quirk alc861_fixup_tbl[] = {
+	SND_PCI_QUIRK(0x1043, 0x1393, ASUS A6Rp, PINFIX_ASUS_A6RP),
 	SND_PCI_QUIRK(0x1734, 0x10c7, FSC Amilo Pi1505, PINFIX_FSC_AMILO_PI1505),
 	{}
 };
-- 
1.7.9.858.gffe840.dirty

From: Takashi Iwai ti...@suse.de
Date: Thu, 26 Jan 2012 15:56:16 +0100
Subject: [PATCH 2/3] ALSA: hda - Fix silent output on Haier W18 laptop

commit b3a81520bd37a28f77cb0f7002086fb14061824d upstream.

The very same problem is seen on Haier W18 laptop with ALC861 as seen
on ASUS A6Rp, which was fixed by the commit 3b25eb69.
Now we just need to add a new SSID entry pointing to the same fixup.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=42656

Cc: sta...@kernel.org [v3.2+]
Signed-off-by: Takashi Iwai ti...@suse.de
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
 sound/pci/hda/patch_realtek.c |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 9a63a193fc07..5f03c4019312 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5247,6 +5247,7 @@ static const struct alc_fixup alc861_fixups[] = {
 
 static const struct snd_pci_quirk alc861_fixup_tbl[] = {
 	SND_PCI_QUIRK(0x1043, 0x1393, ASUS A6Rp, PINFIX_ASUS_A6RP),
+	SND_PCI_QUIRK(0x1584, 0x2b01, Haier W18, PINFIX_ASUS_A6RP),
 	SND_PCI_QUIRK(0x1734, 0x10c7, FSC Amilo Pi1505, PINFIX_FSC_AMILO_PI1505),
 	{}
 };
-- 
1.7.9.858.gffe840.dirty

From: Takashi Iwai ti...@suse.de
Date: Mon, 30 Jan 2012 10:54:08 +0100
Subject: [PATCH 3/3] ALSA: hda - Apply 0x0f-VREF fix to all ASUS laptops with
 ALC861/660

It turned out that other ASUS laptops require the similar fix to
enable the VREF on the pin 0x0f for the secret output amp, not only
ASUS A6Rp.  Moreover, it's required even when the pin is being used
as the output.  Thus, writing a fixed value doesn't work always.

This patch applies the VREF-fix for all ASUS laptops with ALC861/660
in a fixup function that checks the current value and turns on only
the VREF value no matter whether input or output direction is set.

The automute function is modified as well to keep the pin VREF upon
muting/unmuting via pin-control; otherwise the pin VREF is reset at
plugging/unplugging a jack.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=42588

Cc: sta...@kernel.org [v3.2+]
Signed-off-by: Takashi Iwai ti...@suse.de
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
 sound/pci/hda/patch_realtek.c |   43 +---
 1 files changed, 35 insertions(+), 8 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 5f03c4019312..76055bcfe924 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -176,6 +176,7 @@ struct alc_spec {
 	unsigned int detect_lo:1;	/* Line-out detection enabled */
 	unsigned int automute_speaker_possible:1; /* there are speakers and either LO or HP */
 	unsigned int automute_lo_possible:1;	  /* there are line outs and HP */
+	unsigned int keep_vref_in_automute:1; /* Don't clear VREF in automute */
 
 	/* other flags */
 	unsigned int no_analog :1; /* digital I/O only */
@@ -519,13 +520,24 @@ static void

Processed: Re: [3.1.8 - 3.2.1 regression] No more sound

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

 tags 657302 + upstream patch moreinfo
Bug #657302 [linux-2.6] linux-image-3.2.0-1-amd64: No more sound
Added tag(s) upstream, moreinfo, and patch.
 forwarded 657302 https://bugzilla.kernel.org/show_bug.cgi?id=42588
Bug #657302 [linux-2.6] linux-image-3.2.0-1-amd64: No more sound
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=42588'.
 quit
Stopping processing here.

Please contact me if you need assistance.
-- 
657302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657302
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
Archive: 
http://lists.debian.org/handler.s.c.132794300724396.transcr...@bugs.debian.org

Bug#656792: linux-image-3.2.0-1-amd64: kernel does not boot since 3.1 under a (strange) Xen anymore

2012-01-30 Thread Christoph Anton Mitterer

Hey...


On Sat, 2012-01-28 at 20:53 +, Ben Hutchings wrote:
Can you try again, in case you remember wrongly?
 I tried,... setting it to most doesn't help.


I assume it is not possible for you to interact with the shell that the
 initramfs runs after failing to mount the root filesystem?
 Unfortunately it always requires manual intervention by the ISP
(yeah I know, this sucks).




On Sat, 2012-01-28 at 22:48 +, Ian Campbell wrote:
 One way to tell would be to add xen_emul_unplug=never to your kernel
 command line to prevent this happening and see if it boots with
 emulated devices ok.
This did the trick :) *my hero* ;)

I now even get a correctly detected Xen:
Hypervisor detected: Xen HVM
...
Booting paravirtualized kernel on Xen HVM


 If this has happened then you
 will see messages like:
Xen Platform PCI: I/O protocol version ...
...
Blkfront and the Xen platform PCI driver have  been compiled for this 
 kernel: unplug emulated disks.
 very early on.
I cannot tell whether these occured _without_ xen_emul_unplug=never...
but _with_ xen_emul_unplug=never (and the then booting kernel 3.2) it
does not show up in dmesg.


 If this turns out to be the case then I would recommend arranging for
 the initramfs to contain the xen blkfront driver and removing that
 option again so you end up using the PV drivers (which are much fast
 than emulated).
Well at least that module is not automatically loaded now (even outside
the initramfs).
And /sys/block/sda/device/driver is something
like ../ ... ../bus/scsi/drivers/sd .
So you think, just adding xen-blkfront to the initramfs, and removeing
the parameter will work?
Or do I have to explicitly modporbe it in the initramfs, given that it's
apparently not auto-loaded?


 This is normally already the case with the default
 initramfs tools configuration.
They're not included automatically



Thanks to both of you for your help so far.

Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#656792: linux-image-3.2.0-1-amd64: kernel does not boot since 3.1 under a (strange) Xen anymore

2012-01-30 Thread Ian Campbell

On Mon, 2012-01-30 at 19:24 +0100, Christoph Anton Mitterer wrote:

  If this turns out to be the case then I would recommend arranging for
  the initramfs to contain the xen blkfront driver and removing that
  option again so you end up using the PV drivers (which are much fast
  than emulated).
 Well at least that module is not automatically loaded now (even outside
 the initramfs).
 And /sys/block/sda/device/driver is something
 like ../ ... ../bus/scsi/drivers/sd .

If it exists then PV device will be called xvda not sda.

Also the PV device will not appear or load unless you allow the emulated
device to unplug.

If you do unplug then you won't get the emulated device discovered or
that driver loaded.

The two devices are mutually exclusive because it is dangerous for your
data to have two devices backing onto the same backend, especially since
that happens without guest kernel visibility.

 So you think, just adding xen-blkfront to the initramfs, and removeing
 the parameter will work?
 Or do I have to explicitly modporbe it in the initramfs, given that it's
 apparently not auto-loaded?

I don't know enough about how the initramfs loads modules to be able to
say for sure but I'm, pretty sure this will just work.

In a default initramfs-tools configuration and with LABEL/UUID/LVM based
root=[0] you should be able to flip between emulated and pv devices only
by adding and removing xen_emul_unplug from the command line (or
equivalently by adding or removing the xen platform pci device from the
guest configuration).

Ian.

[0] this is due to the sd vs xvd naming. if you use e.g. root=/dev/sdX
then that won't work.

-- 
Ian Campbell

A complex system that works is invariably found to have evolved from a simple
system that worked.
-- John Gall, _Systemantics_




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327949132.26983.286.ca...@zakaz.uk.xensource.com

Bug#654434: marked as done (Kernel doesn't hibernate, instead you end up on a black screen)

Your message dated Mon, 30 Jan 2012 19:59:16 +0100
with message-id 20120130185916.ga8...@vip.manty.net
and subject line Solved also on 3.2
has caused the Debian Bug report #654434,
regarding Kernel doesn't hibernate, instead you end up on a black screen
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.)


-- 
654434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.1.5-1
Severity: normal

Hi!

This happens to me on three different machines, it happens with different
kernels and doesn't happen all the times but only sometimes.

The typical behaviour is that you get the two first lines of kernel's output
when going to hibernate, which are:

Looking for splash system... none
s2disk: Snapshotting system

then typically I see something like a mode change (screen gets black and
then comes back with those two lines and s2disk continues to output
messages) but when it fails the screen gets black and doesn't come back.  At
this state you can type (computer is not frozen) and see what you type but
pressing Ctrl+C or Ctrl+Z doesn't do anything, not even Ctrl+Alt+Del.  It
even happens that sometimes if you wait for a while it will get out of the
black screen and get back to where you were before trying to hibernate.

Two of the computers are running testing, and one is running unstable, all
three computers are running linux-image-3.1.0-1-amd64 and I started to
experiment this on 3.1.4-1, I have tested this also on 3.2.0 rc4, rc6 and
rc7 the problem is still there, in fact I have one of the machines (a lenovo
desktop which runs testing) downgraded to 3.1.1-1 and it hibernates ok and
if I get it to 3.2.0rc7 then it fails all the time, the other machines are
more difficult to get to fail but also tend to fail more on the 3.2.0 RCs.

I have uswsusp installed on all of them so I was suspecting a bad behaviour
of it when used with recent kernels, so I uninstalled it on the lenovo and
tested again with 3.2.0 rc7 and it failed as well.

Is there any info I can add to help debugging this?

What follows is the info of one of the machines I'm seeing this on, a
Compaq Presario C760EM which runs testing.

-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.5-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-7) ) #1 SMP Sun Dec 11 20:36:41 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 
root=UUID=046e2800-818f-447c-a9ef-0a5beb51de0c ro ipv6.disable=1 quiet

** Not tainted

** Kernel log:
[ 4409.146679] snd_hda_intel :00:1b.0: setting latency timer to 64
[ 4409.146741] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X
[ 4409.146794] uhci_hcd :00:1d.0: setting latency timer to 64
[ 4409.146824] usb usb2: root hub lost power or was reset
[ 4409.146840] uhci_hcd :00:1d.1: setting latency timer to 64
[ 4409.146867] usb usb3: root hub lost power or was reset
[ 4409.146880] uhci_hcd :00:1d.2: setting latency timer to 64
[ 4409.146907] usb usb4: root hub lost power or was reset
[ 4409.146923] ehci_hcd :00:1d.7: setting latency timer to 64
[ 4409.146940] usb usb1: root hub lost power or was reset
[ 4409.150840] ehci_hcd :00:1d.7: cache line size of 64 is not supported
[ 4409.150861] ata_piix :00:1f.1: PCI INT B - GSI 19 (level, low) - IRQ 19
[ 4409.150867] ata_piix :00:1f.1: setting latency timer to 64
[ 4409.150893] ahci :00:1f.2: setting latency timer to 64
[ 4409.151847] pci :00:1e.0: setting latency timer to 64
[ 4409.151869] 8139too :02:01.0: eth0: link down
[ 4409.152539] sd 2:0:0:0: [sda] Starting disk
[ 4409.240571] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial 
brightness
[ 4409.320415] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered 
out
[ 4409.320418] ata1.00: ACPI cmd ef/03:22:00:00:00:a0 (SET FEATURES) filtered 
out
[ 4409.352291] ata1.00: configured for MWDMA2
[ 4409.496065] usb 1-6: reset high speed USB device number 2 using ehci_hcd
[ 4409.640033] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 4409.640568] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[ 4409.641142] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[ 4409.641147] ata3.00: configured for UDMA/100
[ 4409.723135] PM: restore of devices complete after 585.081 msecs
[ 4409.736408] ath0: deauthenticated from 00:80:5a:22:55:68 (Reason: 6)
[ 4409.736546] snapshot_ioctl: ioctl '4004330c' is deprecated and will be 
removed soon, update your suspend-to-disk utilities
[ 4409.736549] Restarting tasks

Bug#657302: [3.1.8 - 3.2.1 regression] No more sound

2012-01-30 Thread Jonathan Nieder

tags 657302 - moreinfo
quit

Jonathan Nieder wrote:

 Thanks!  Here's a copy for convenience.

 Not part of linux-next yet.

It's in the sound tree now (for-next branch).  So now the series is

 3b25eb690e8c ALSA: hda - Fix silent output on ASUS A6Rp
 b3a81520bd37 ALSA: hda - Fix silent output on Haier W18 laptop
 31150f2327cb ALSA: hda - Apply 0x0f-VREF fix to all ASUS laptops with
  ALC861/660



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120130194617.GA29037@burratino

Re: Linux 3.2 in wheezy

2012-01-30 Thread Moritz Mühlenhoff

Ben Hutchings b...@decadent.org.uk schrieb:
 But practically this means that we have to either carry
 the featureset indefinitely or disappoint users by removing it in a
 later release.  (See the complaints about removing OpenVZ in wheezy
 despite 4 years' advance notice of this.)

That's not really comparable: Dropping a virtualisation flavour
leaves people with OS guests they can no longer operate, while
dropping grsec at a later point only makes them fall back to standard
Linux security (if we set GRKERNSEC_NO_RBAC=y)

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnjidtsd.5q0@inutil.org

Re: Linux 3.2 in Debian 7.0

2012-01-30 Thread Greg KH

On Mon, Jan 30, 2012 at 03:46:29AM +, Ben Hutchings wrote:
 Greg,
 
 We've decided to go with Linux 3.2 for the next Debian stable release,
 so we'll be interested in a 3.2.y longterm series.  I believe there was
 a volunteer from Ubuntu to look after that once you've had enough of it,
 but I seem to have lost the relevant mail.

I will not be handing any stable/longterm maintance over to anyone who
does not have a _lot_ of kernel community experience, so that seems to
rule out just about all Ubuntu developers at this point in time from
what I can tell.

As I think this will be a Debian/Ubuntu thing only, I don't know if
keeping the kernel.org version around for any length of time is really
going to help much out here, do you?

thanks,

greg k-h


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120130195138.ga10...@kroah.com

Bug#622325: linux-image-2.6.38-2-orion5x: Problem With I2C

2012-01-30 Thread Roman Mamedov

On Mon, 23 Jan 2012 14:27:50 -0600
Jonathan Nieder jrnie...@gmail.com wrote:

 Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
 repeated START between messages in xfer) as Guenter suggested?

I have finally managed to do that, and indeed, this problem is solved by
rolling-back that commit. The same problem was observed with the current
vanilla 3.2.2, and only after the roll-back it started working fine:

root@mahou:~# uname -a
Linux mahou 3.2.2orion5x-rm1+ #3 Mon Jan 30 19:29:49 YEKT 2012 armv5tel 
GNU/Linux

root@mahou:~# sensors
g760a-i2c-0-3e
Adapter: mv64xxx_i2c adapter
fan1:4681 RPM

lm75-i2c-0-48
Adapter: mv64xxx_i2c adapter
temp1:+42.0°C  (high = +80.0°C, hyst = +75.0°C)

No errors in dmesg.

-- 
With respect,
Roman

~~~
Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free.


signature.asc
Description: PGP signature

Re: Linux 3.2 in Debian 7.0

2012-01-30 Thread Josh Boyer

On Mon, Jan 30, 2012 at 3:04 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Mon, Jan 30, 2012 at 11:51:38AM -0800, Greg KH wrote:
On Mon, Jan 30, 2012 at 03:46:29AM +, Ben Hutchings wrote:
Greg,

We've decided to go with Linux 3.2 for the next Debian stable release,
so we'll be interested in a 3.2.y longterm series. I believe there was
a volunteer from Ubuntu to look after that once you've had enough of it,
but I seem to have lost the relevant mail.

I will not be handing any stable/longterm maintance over to anyone who
does not have a _lot_ of kernel community experience, so that seems to
rule out just about all Ubuntu developers at this point in time from
what I can tell.

As I think this will be a Debian/Ubuntu thing only, I don't know if
keeping the kernel.org version around for any length of time is really
going to help much out here, do you?

There is no connection between Debian and Ubuntu kernel packages,
unlike many other packages that are co-maintained or copied between
the distributions. So it is valuable to have a distinct upstream
branch as the basis for our respective Linux kernel packages.

A longterm 3.2.y branch might also be useful for Fedora 16, though
the Fedora maintainers may prefer to carry on updating to newer
mainline releases.

Iffy on whether Fedora would use it. If anything, it would be more useful for
Fedora 15 than Fedora 16. We'll likely rebase F16 to 3.3 as soon as 3.3.1 is
released.

I do appreciate the thoughts though. Once we get closer to a 3.3 rebase, we
might revisit.

josh

--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CA+5PVA4rC6Oa9-49K6LNSMqBz=y-kcjup_+wfh0pj0v7-rx...@mail.gmail.com

Processed: Re: linux-image-2.6.38-2-orion5x: Problem With I2C

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

 # Roman Mamedov wrote:
 #  On Mon, 23 Jan 2012 14:27:50 -0600
 #  Jonathan Nieder jrnie...@gmail.com wrote:
 #
 #  Were you able to try backing out eda6bee6c7 (i2c-mv64xxx: send
 #  repeated START between messages in xfer) as Guenter suggested?
 # 
 #  I have finally managed to do that, and indeed, this problem is solved by
 #  rolling-back that commit. The same problem was observed with the current
 #  vanilla 3.2.2
 tags 622325 + upstream patch moreinfo
Bug #622325 [linux-2.6] linux-image-2.6.38-2-orion5x: Problem With I2C
Added tag(s) upstream, moreinfo, and patch.
 # approximating
 found 622325 linux-2.6/3.2.1-2
Bug #622325 [linux-2.6] linux-image-2.6.38-2-orion5x: Problem With I2C
Bug Marked as found in versions linux-2.6/3.2.1-2.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
622325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622325
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
Archive: 
http://lists.debian.org/handler.s.c.132795733329939.transcr...@bugs.debian.org

Bug#658029: Missing hid-logitech-dj.ko

2012-01-30 Thread Vadim Solomin

Package: initramfs-tools
Version: 0.99
Tags: patch

Initramfs for the 3.2 linux kernels doesn't include hid-logitech-dj module, 
rendering certain Logitech keyboards unusable. Patch attached.

-- 
Vadim Solomin
--- hook-functions.orig	2011-05-13 13:56:12.0 +0400
+++ hook-functions	2012-01-31 00:58:58.26037 +0400
@@ -406,9 +406,9 @@
 	case ${1:-} in
 	base)
 		for x in ehci-hcd ohci-hcd uhci-hcd usbhid xhci xhci-hcd \
-		hid-apple hid-cherry hid-logitech hid-microsoft hid-sunplus \
-		btrfs ext2 ext3 ext4 ext4dev isofs jfs nfs reiserfs udf xfs \
-		af_packet atkbd i8042 virtio_pci; do
+		hid-apple hid-cherry hid-logitech hid-logitech-dj \
+		hid-microsoft hid-sunplus btrfs ext2 ext3 ext4 ext4dev isofs \
+		jfs nfs reiserfs udf xfs af_packet atkbd i8042 virtio_pci; do
 			manual_add_modules ${x}
 		done
 	;;

Processed: Re: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x10000100

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

 # might not be the same bug, but it's my best guess for now
 merge 657612 657526
Bug#657526: linux-image-3.2.0-1-686-pae crashes after 50+ seconds
Bug#657612: linux-image-3.2.0-1-amd64: scheduling while atomic: 
swapper/2/0/0x1100
Merged 657526 657612.

 tags 657612 + patch moreinfo
Bug #657612 [linux-2.6] linux-image-3.2.0-1-amd64: scheduling while atomic: 
swapper/2/0/0x1100
Bug #657526 [linux-2.6] linux-image-3.2.0-1-686-pae crashes after 50+ seconds
Added tag(s) moreinfo and patch.
Added tag(s) moreinfo and patch.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
657612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657612
657526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657526
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
Archive: 
http://lists.debian.org/handler.s.c.13279582915397.transcr...@bugs.debian.org

Re: Bug#605090: Linux 3.2 in wheezy

2012-01-30 Thread Yves-Alexis Perez

On lun., 2012-01-30 at 14:08 +, Ben Hutchings wrote:
 On Mon, 2012-01-30 at 11:05 +0100, Yves-Alexis Perez wrote:
  (adding few CC:s to keep track on the bug)
  
  On dim., 2012-01-29 at 21:26 +, Ben Hutchings wrote:
   On Sun, 2012-01-29 at 20:57 +0100, Yves-Alexis Perez wrote:
On dim., 2012-01-29 at 18:22 +, Ben Hutchings wrote:
 Featuresets
 ---
 
 The only featureset provided will be 'rt' (realtime), currently built
 for amd64 only.  If there is interest in realtime support for other
 architectures, we may be able to add that.  However, we do need to
 consider the total time taken to build binary packages for each
 architecture.
 
 If there are particular container features that should be enabled or
 backported to provide a useful replacement for OpenVZ or VServer,
 please let us know.  We cannot promise that these will all be enabled
 but we need to know what is missing. 

So in the end what are the reasons for not trying the grsecurity
featureset? #605090 lacks any reply from the kernel team since quite a
while, and especially after answers were provided to question asked.
   
   You already know the main reason:
Feature-wise, Brad Sprengler and the PaX team still add stuff, like the
gcc plugins or hardening features like symbols hiding, fix bugs (for
example in RBAC code), while few of them reach mainline.
   
   I realise that the mainline Linux developers have sometimes been
   unreasonably resistant to these changes and I'm not intending to assign
   blame for this.  But practically this means that we have to either carry
   the featureset indefinitely or disappoint users by removing it in a
   later release.  (See the complaints about removing OpenVZ in wheezy
   despite 4 years' advance notice of this.)
  
  I understand this, and I still see the grsec featureset as a valuable
  project. Indeed, reducing the diff wrt. upstream in Debian kernel is an
  important goal (especially considering the time involvement).
  
  Now, I still think having a hardened Debian kernel inside the
  distribution is helpful
 [...]
 
 I agree and I would like to see hardening of *all* our configurations,
 where the performance cost is not too much.  That's going to protect all
 our users rather than just people who seek out a special paranoid
 configuration.

So I think it's perfectly clear that nor Debian nor Grsecurity are
really interested in Debian shipping a Grsecurity kernel.

I find that sad, because I do think there are users of both which would
benefit from that, and not only people who seek out a special paranoid
configuration.

Anyway, I'll keep updating the current setup for interested people, but
without any interest from either party, that definitely looks like a
dead end.

Regards,
-- 
Yves-Alexis


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

Bug#644747: marked as done (linux-image-3.0.0-2-amd64: udev doesn't create /dev/sr0, /dev/cdrom)

Your message dated Mon, 30 Jan 2012 15:26:59 -0600
with message-id 20120130212658.GA1770@burratino
and subject line Re: udev doesn't create /dev/sr0, /dev/cdrom
has caused the Debian Bug report #644747,
regarding linux-image-3.0.0-2-amd64: udev doesn't create /dev/sr0, /dev/cdrom
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.)


-- 
644747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.0.0-5
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropiate ***

   * What led up to the situation?   I noticed that it didn't mount the
CDROM.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?   I added the entry cdrom in /etc/modules.
   * What was the outcome of this action?   The module cdrom gets loaded
but /dev/sr0 is not created.
   * What outcome did you expect instead?   I thought /dev/sr0 would be
created.

*** End of the template - remove these lines ***



-- Package-specific info:
** Version:
Linux version 3.0.0-2-amd64 (Debian 3.0.0-5) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-9) ) #1 SMP Fri Oct 7 20:48:45 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.0.0-2-amd64 
root=UUID=2237ebe0-15cb-40db-bed9-d4f5ff052689 ro single

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   20.693330] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 
22
[   20.693453] HDA Intel :00:1b.0: irq 43 for MSI/MSI-X
[   20.693483] HDA Intel :00:1b.0: setting latency timer to 64
[   20.722960] [drm] Initialized drm 1.1.0 20060810
[   20.761966] [drm] radeon kernel modesetting enabled.
[   20.762056] radeon :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[   20.762113] radeon :01:00.0: setting latency timer to 64
[   20.762231] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 
0x1682:0x3036).
[   20.762312] [drm] register mmio base: 0xFE62
[   20.762366] [drm] register mmio size: 131072
[   20.762535] ATOM BIOS: CEDAR
[   20.762651] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[   20.762712] radeon :01:00.0: GTT: 512M 0x4000 - 
0x5FFF
[   20.762773] mtrr: type mismatch for e000,1000 old: write-back new: 
write-combining
[   20.762832] [drm] Detected VRAM RAM=1024M, BAR=256M
[   20.762886] [drm] RAM width 64bits DDR
[   20.763001] [TTM] Zone  kernel: Available graphics memory: 2019946 kiB.
[   20.763055] [TTM] Initializing pool allocator.
[   20.763119] [drm] radeon: 1024M of VRAM memory ready
[   20.763173] [drm] radeon: 512M of GTT memory ready.
[   20.763232] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   20.763285] [drm] Driver supports precise vblank timestamp query.
[   20.763367] radeon :01:00.0: irq 44 for MSI/MSI-X
[   20.763371] radeon :01:00.0: radeon: using MSI.
[   20.763445] [drm] radeon: irq initialized.
[   20.763499] [drm] GART: num cpu pages 131072, num gpu pages 131072
[   20.763803] [drm] Loading CEDAR Microcode
[   21.031946] radeon :01:00.0: WB enabled
[   21.048146] [drm] ring test succeeded in 1 usecs
[   21.048272] [drm] radeon: ib pool ready.
[   21.048369] [drm] ib test succeeded in 0 usecs
[   21.048426] failed to evaluate ATIF got AE_BAD_PARAMETER
[   21.048747] [drm] Radeon Display Connectors
[   21.048802] [drm] Connector 0:
[   21.048857] [drm]   DisplayPort
[   21.048910] [drm]   HPD1
[   21.048964] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 
0x643c
[   21.049025] [drm]   Encoders:
[   21.049076] [drm] DFP1: INTERNAL_UNIPHY1
[   21.049129] [drm] Connector 1:
[   21.049180] [drm]   HDMI-A
[   21.049231] [drm]   HPD2
[   21.049282] [drm]   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 
0x646c
[   21.049340] [drm]   Encoders:
[   21.049391] [drm] DFP2: INTERNAL_UNIPHY1
[   21.049444] [drm] Connector 2:
[   21.049495] [drm]   DVI-I
[   21.049546] [drm]   HPD4
[   21.049598] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 
0x644c
[   21.049655] [drm]   Encoders:
[   21.049707] [drm] DFP3: INTERNAL_UNIPHY
[   21.049759] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   21.526754] [drm] Radeon display connector DP-1: No monitor connected or 
invalid EDID
[   21.536508] [drm] Radeon display connector HDMI-A-1: No monitor connected or 
invalid EDID
[   21.588899] [drm] Radeon display connector DVI-I-1: Found valid EDID
[   21.589018] [drm] Internal thermal controller without fan

Bug#657497: nfs-common: Exec permission denied

2012-01-30 Thread Jakub Krajewski

Hello,

Thanks for your response, I'll try to address all questions in one message.

@dE.: This Squeeze NFS server have been working great for more than a year and 
always with custom kernel. More 
to say I have not changed anything there.

About permissions - files are owned by root and mounted by root on the client. 
It is my home server and home 
workstation. So nothing mission critical. :)

@Ben: 
nfs-common 1.2.5-3:
/proc/mounts:
imperator:/usr/src/linux/ /usr/src/linux-imperator nfs 
rw,nosuid,nodev,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3
 
0 0

/etc/mtab:
imperator:/usr/src/linux/ /usr/src/linux-imperator nfs 
rw,nosuid,nodev,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3
 
0 0

nfs-common 1.2.5-4:
/proc/mounts:
imperator:/usr/src/linux/ /usr/src/linux-imperator nfs 
rw,nosuid,nodev,noexec,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3
 
0 0

/etc/mtab:
imperator:/usr/src/linux/ /usr/src/linux-imperator nfs 
rw,nosuid,nodev,noexec,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.3,mountvers=3,mountport=42837,mountproto=udp,local_lock=none,addr=192.168.1.3
 
0 0

Looks like with 1.2.5-4 there is noexec flag present (even though I have put 
exec flag in /etc/fstab, when I 
remove it - it is the same however).

If you need any other data, please ask. :)

Best regards,
-- 
Jakub Krajewski



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201201302317.16310.ja...@krajewski.org

Processed: Re: [squeeze] system freeze with usb 3.0 devices attached

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

 tags 596528 + moreinfo
Bug #596528 [linux-2.6] linux-image-2.6.32-5-amd64: system freeze with usb 3.0 
devices attached
Added tag(s) moreinfo.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
596528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596528
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
Archive: 
http://lists.debian.org/handler.s.c.13279618432233.transcr...@bugs.debian.org

Processed: Re: Connections fail on first attempt

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

 tags 658052 - squeeze sid
Bug #658052 [libc6] Connections fail on first attempt
Removed tag(s) sid and squeeze.
 reassign 657812 libc6
Bug #657812 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] 
Connections fail on first attempt
Bug reassigned from package 'linux-2.6' to 'libc6'.
Bug No longer marked as found in versions 2.6.32-41.
 forcemerge 658052 657812
Bug#658052: Connections fail on first attempt
Bug#657812: Connections fail on first attempt
Forcibly Merged 657812 658052.


End of message, stopping processing here.

Please contact me if you need assistance.
-- 
658052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658052
657812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657812
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
Archive: 
http://lists.debian.org/handler.s.c.13279669916007.transcr...@bugs.debian.org

Processed: Re: Re: udev doesn't create /dev/sr0, /dev/cdrom

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

 tags 644747 - moreinfo
Bug #644747 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6] 
linux-image-3.0.0-2-amd64: udev doesn't create /dev/sr0, /dev/cdrom
Removed tag(s) moreinfo.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
644747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644747
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
Archive: 
http://lists.debian.org/handler.s.c.132797892217089.transcr...@bugs.debian.org

Bug#644747: marked as done (linux-image-3.0.0-2-amd64: udev doesn't create /dev/sr0, /dev/cdrom)

Your message dated Mon, 30 Jan 2012 20:59:47 -0600
with message-id 20120131025947.GA9163@burratino
and subject line Re: Re: udev doesn't create /dev/sr0, /dev/cdrom
has caused the Debian Bug report #644747,
regarding linux-image-3.0.0-2-amd64: udev doesn't create /dev/sr0, /dev/cdrom
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.)


-- 
644747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.0.0-5
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropiate ***

   * What led up to the situation?   I noticed that it didn't mount the
CDROM.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?   I added the entry cdrom in /etc/modules.
   * What was the outcome of this action?   The module cdrom gets loaded
but /dev/sr0 is not created.
   * What outcome did you expect instead?   I thought /dev/sr0 would be
created.

*** End of the template - remove these lines ***



-- Package-specific info:
** Version:
Linux version 3.0.0-2-amd64 (Debian 3.0.0-5) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-9) ) #1 SMP Fri Oct 7 20:48:45 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.0.0-2-amd64 
root=UUID=2237ebe0-15cb-40db-bed9-d4f5ff052689 ro single

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   20.693330] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 
22
[   20.693453] HDA Intel :00:1b.0: irq 43 for MSI/MSI-X
[   20.693483] HDA Intel :00:1b.0: setting latency timer to 64
[   20.722960] [drm] Initialized drm 1.1.0 20060810
[   20.761966] [drm] radeon kernel modesetting enabled.
[   20.762056] radeon :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[   20.762113] radeon :01:00.0: setting latency timer to 64
[   20.762231] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 
0x1682:0x3036).
[   20.762312] [drm] register mmio base: 0xFE62
[   20.762366] [drm] register mmio size: 131072
[   20.762535] ATOM BIOS: CEDAR
[   20.762651] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[   20.762712] radeon :01:00.0: GTT: 512M 0x4000 - 
0x5FFF
[   20.762773] mtrr: type mismatch for e000,1000 old: write-back new: 
write-combining
[   20.762832] [drm] Detected VRAM RAM=1024M, BAR=256M
[   20.762886] [drm] RAM width 64bits DDR
[   20.763001] [TTM] Zone  kernel: Available graphics memory: 2019946 kiB.
[   20.763055] [TTM] Initializing pool allocator.
[   20.763119] [drm] radeon: 1024M of VRAM memory ready
[   20.763173] [drm] radeon: 512M of GTT memory ready.
[   20.763232] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   20.763285] [drm] Driver supports precise vblank timestamp query.
[   20.763367] radeon :01:00.0: irq 44 for MSI/MSI-X
[   20.763371] radeon :01:00.0: radeon: using MSI.
[   20.763445] [drm] radeon: irq initialized.
[   20.763499] [drm] GART: num cpu pages 131072, num gpu pages 131072
[   20.763803] [drm] Loading CEDAR Microcode
[   21.031946] radeon :01:00.0: WB enabled
[   21.048146] [drm] ring test succeeded in 1 usecs
[   21.048272] [drm] radeon: ib pool ready.
[   21.048369] [drm] ib test succeeded in 0 usecs
[   21.048426] failed to evaluate ATIF got AE_BAD_PARAMETER
[   21.048747] [drm] Radeon Display Connectors
[   21.048802] [drm] Connector 0:
[   21.048857] [drm]   DisplayPort
[   21.048910] [drm]   HPD1
[   21.048964] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 
0x643c
[   21.049025] [drm]   Encoders:
[   21.049076] [drm] DFP1: INTERNAL_UNIPHY1
[   21.049129] [drm] Connector 1:
[   21.049180] [drm]   HDMI-A
[   21.049231] [drm]   HPD2
[   21.049282] [drm]   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 
0x646c
[   21.049340] [drm]   Encoders:
[   21.049391] [drm] DFP2: INTERNAL_UNIPHY1
[   21.049444] [drm] Connector 2:
[   21.049495] [drm]   DVI-I
[   21.049546] [drm]   HPD4
[   21.049598] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 
0x644c
[   21.049655] [drm]   Encoders:
[   21.049707] [drm] DFP3: INTERNAL_UNIPHY
[   21.049759] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   21.526754] [drm] Radeon display connector DP-1: No monitor connected or 
invalid EDID
[   21.536508] [drm] Radeon display connector HDMI-A-1: No monitor connected or 
invalid EDID
[   21.588899] [drm] Radeon display connector DVI-I-1: Found valid EDID
[   21.589018] [drm] Internal thermal controller without

Bug#658067: Device ID missing from Firmware-Ralink

2012-01-30 Thread Matt Harrison

Package:  Firmware-Ralink
Version:  All

My Wireless USB Adapter's ID is not listed in the firmware-ralink
package in Stable, Testing, and Sid.

LSUSB Output:
Bus 001 Device 004: ID 1737:0078 Linksys WUSB100 v2 RangePlus Wireless
Network Adapter [Ralink RT3070]

In Squeeze I have to perform the following workaround to get the device to work:
echo 'install rt2870sta modprobe --ignore-install rt2870sta ;
/bin/echo 1737 0078  /sys/bus/usb/drivers/rt2870/new_id' | tee
/etc/modprobe.d/rt2870sta.conf
modprobe -rf rt2870sta
modprobe rt2870sta
echo rt2870sta | tee -a /etc/modules

I am currently using Debian Stable 6.04 AMD64
Kernel Version:  2.6.32-5-amd64

As I said, this problem also occurs with the firmware-ralink package
in Testing and Sid, however the workaround provided does not work in
anything but Stable.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CA+CmQZRM_-NpgJ44G9eJL0WKwgJoNg=sl4skqfyzgygr8r_...@mail.gmail.com

Bug#657497: nfs-common: Exec permission denied

On Mon, 2012-01-30 at 23:17 +0100, Jakub Krajewski wrote:
[...]
 Looks like with 1.2.5-4 there is noexec flag present (even though I have put 
 exec flag in /etc/fstab, when I 
 remove it - it is the same however).

 If you need any other data, please ask. :)

Sorry, I forgot to ask: what is the full entry for this mount in
/etc/fstab?

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


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

Bug#656642: marked as done ([INTL:da] Danish translation of the debconf templates linux-latest-2.6)

Your message dated Tue, 31 Jan 2012 04:32:27 +
with message-id e1rs5on-0002on...@franck.debian.org
and subject line Bug#656642: fixed in linux-latest 43
has caused the Debian Bug report #656642,
regarding [INTL:da] Danish translation of the debconf templates linux-latest-2.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

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


-- 
656642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-latest-2.6
Severity: wishlist
Tags: l10n patch

Please include the attached Danish linux-latest-2.6 translations.

joe@pc:~/over/debian/linux-latest-2.6$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 3 oversatte tekster.

bye
Joe


da.po
Description: Binary data
---End Message---
---BeginMessage---
Source: linux-latest
Source-Version: 43

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

linux-doc-2.6_3.2+43_all.deb
  to main/l/linux-latest/linux-doc-2.6_3.2+43_all.deb
linux-doc_3.2+43_all.deb
  to main/l/linux-latest/linux-doc_3.2+43_all.deb
linux-headers-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-486_3.2+43_i386.deb
linux-headers-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-686-pae_3.2+43_i386.deb
linux-headers-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-amd64_3.2+43_i386.deb
linux-headers-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-486_3.2+43_i386.deb
linux-headers-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-686-pae_3.2+43_i386.deb
linux-headers-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-amd64_3.2+43_i386.deb
linux-image-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-486_3.2+43_i386.deb
linux-image-2.6-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-bigmem_3.2+43_i386.deb
linux-image-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-pae_3.2+43_i386.deb
linux-image-2.6-686_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686_3.2+43_i386.deb
linux-image-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-amd64_3.2+43_i386.deb
linux-image-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-486_3.2+43_i386.deb
linux-image-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686-bigmem_3.2+43_i386.deb
linux-image-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686-pae_3.2+43_i386.deb
linux-image-686_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686_3.2+43_i386.deb
linux-image-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-amd64_3.2+43_i386.deb
linux-latest_43.dsc
  to main/l/linux-latest/linux-latest_43.dsc
linux-latest_43.tar.gz
  to main/l/linux-latest/linux-latest_43.tar.gz
linux-source-2.6_3.2+43_all.deb
  to main/l/linux-latest/linux-source-2.6_3.2+43_all.deb
linux-source_3.2+43_all.deb
  to main/l/linux-latest/linux-source_3.2+43_all.deb
linux-tools-2.6_3.2+43_all.deb
  to main/l/linux-latest/linux-tools-2.6_3.2+43_all.deb
linux-tools_3.2+43_all.deb
  to main/l/linux-latest/linux-tools_3.2+43_all.deb
xen-linux-system-2.6-xen-686_3.2+43_i386.deb
  to main/l/linux-latest/xen-linux-system-2.6-xen-686_3.2+43_i386.deb
xen-linux-system-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/xen-linux-system-686-pae_3.2+43_i386.deb
xen-linux-system-amd64_3.2+43_i386.deb
  to main/l/linux-latest/xen-linux-system-amd64_3.2+43_i386.deb



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

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

Debian distribution maintenance software
pp.
Ben Hutchings b...@decadent.org.uk (supplier of updated linux-latest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 Jan 2012 03:10:26 +
Source: linux-latest
Binary: linux-source linux-source-2.6 linux-doc linux-doc-2.6 linux-tools 
linux-tools-2.6 linux-image-alpha-generic linux-image-2.6-alpha-generic 
linux-headers-alpha-generic linux-headers-2.6-alpha-generic 
linux-image-alpha-smp linux-image-2.6-alpha-smp linux-headers-alpha-smp 
linux-headers-2.6-alpha-smp linux-image-alpha-legacy 
linux-image-2.6-alpha-legacy

Bug#657386: marked as done (linux-latest-2.6: [INTL:it] debconf Italian translation)

Your message dated Tue, 31 Jan 2012 04:32:27 +
with message-id e1rs5on-0002oq...@franck.debian.org
and subject line Bug#657386: fixed in linux-latest 43
has caused the Debian Bug report #657386,
regarding linux-latest-2.6: [INTL:it] debconf Italian translation
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.)


-- 
657386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-latest-2.6
Severity: normal

Dear Maintainer,
 this is just to send you the Italian translation of linux-latest-2.6 
po-debconf translation.

Bye
Stefano

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

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
# debconf templates for linux-latest-2.6; translation into Italian
# Copyright 2012 Stefano Canepa s...@linux.it
# This file is distributed under the same license as the linux-latest-2.6
# package.
#
msgid 
msgstr 
Project-Id-Version: linux-latest-2.6 VERSION\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2011-07-24 16:15+0200\n
PO-Revision-Date: 2012-01-08 17:35+0100\n
Last-Translator: Stefano Canepa s...@linux.it\n
Language-Team: Italian t...@lists.linux.it\n
Language: it\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid This system requires a different kernel configuration
msgstr Questo sistema necessita di una configurazione differente del kernel

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid 
Debian's '686' kernel configuration has been replaced by the '686-pae' 
configuration, which uses PAE (Physical Address Extension).  However, the 
CPU in this system does not support PAE.
msgstr La configurazione del kernel '686' di Debian è stata sostituita dalla 
configurazione '686-pae', che fa uso di PAE (Physical Address Extension). 
Tuttavia, la CPU in questo sistema non supporta PAE.

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid 
You should install linux-image-486 and remove linux-image-686 and/or linux-
image-2.6-686 if they are currently installed.
msgstr Si dovrebbe installare linux-image-486 e rimuovere linux-image-686 e/o 
linux-image-2.6-686 se sono attualmente installati.
---End Message---
---BeginMessage---
Source: linux-latest
Source-Version: 43

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

linux-doc-2.6_3.2+43_all.deb
  to main/l/linux-latest/linux-doc-2.6_3.2+43_all.deb
linux-doc_3.2+43_all.deb
  to main/l/linux-latest/linux-doc_3.2+43_all.deb
linux-headers-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-486_3.2+43_i386.deb
linux-headers-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-686-pae_3.2+43_i386.deb
linux-headers-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-amd64_3.2+43_i386.deb
linux-headers-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-486_3.2+43_i386.deb
linux-headers-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-686-pae_3.2+43_i386.deb
linux-headers-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-amd64_3.2+43_i386.deb
linux-image-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-486_3.2+43_i386.deb
linux-image-2.6-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-bigmem_3.2+43_i386.deb
linux-image-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-pae_3.2+43_i386.deb
linux-image-2.6-686_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686_3.2+43_i386.deb
linux-image-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-amd64_3.2+43_i386.deb
linux-image-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-486_3.2+43_i386.deb
linux-image-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686-bigmem_3.2+43_i386.deb
linux-image-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686-pae_3.2+43_i386.deb
linux-image-686_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686_3.2+43_i386.deb
linux-image-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-amd64_3.2+43_i386.deb
linux-latest_43.dsc
  to main/l/linux-latest/linux-latest_43.dsc
linux-latest_43.tar.gz
  to

Bug#654681: marked as done ([INTL:es] Spanish debconf template translation for linux-latest-2.6)

Your message dated Tue, 31 Jan 2012 04:32:26 +
with message-id e1rs5om-0002oh...@franck.debian.org
and subject line Bug#654681: fixed in linux-latest 43
has caused the Debian Bug report #654681,
regarding [INTL:es] Spanish debconf template translation for linux-latest-2.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

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


-- 
654681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-latest-2.6
Version: 41
Severity: wishlist
Tags: l10n patch

Spanish debconf translation attached.
# linux-latest-2.6 po-debconf translation to Spanish
# Copyright (C) 2012 Software in the Public Interest
# This file is distributed under the same license as the linux-latest-2.6 package.
#
# Changes:
# - Initial translation
# Slime Siabef slimesiabef.deb...@gmail.com, 2012
#
# - Updates
#
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid 
msgstr 
Project-Id-Version: linux-latest-2.6_39\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2011-07-24 16:15+0200\n
PO-Revision-Date:\n
Last-Translator: Slime Siabef slimesiabef.deb...@gmail.com\n
Language-Team: Debian Spanish debian-l10n-span...@lists.debian.org\n
Language: \n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Poedit-Language: Spanish\n

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid This system requires a different kernel configuration
msgstr El sistema requiere una configuración diferente del núcleo.

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid Debian's '686' kernel configuration has been replaced by the '686-pae' configuration, which uses PAE (Physical Address Extension).  However, the CPU in this system does not support PAE.
msgstr La configuración del núcleo «686» de Debian ha sido reemplazada por la configuración «686-pae», que utiliza PAE (Extensión de dirección física). Sin embargo, la CPU del sistema no lo soporta.

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid You should install linux-image-486 and remove linux-image-686 and/or linux-image-2.6-686 if they are currently installed.
msgstr Se debería instalar linux-image-486 y eliminar linux-image-686 y/o linux-image-2.6-686 si estuviesen instalados.

---End Message---
---BeginMessage---
Source: linux-latest
Source-Version: 43

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

linux-doc-2.6_3.2+43_all.deb
  to main/l/linux-latest/linux-doc-2.6_3.2+43_all.deb
linux-doc_3.2+43_all.deb
  to main/l/linux-latest/linux-doc_3.2+43_all.deb
linux-headers-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-486_3.2+43_i386.deb
linux-headers-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-686-pae_3.2+43_i386.deb
linux-headers-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-amd64_3.2+43_i386.deb
linux-headers-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-486_3.2+43_i386.deb
linux-headers-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-686-pae_3.2+43_i386.deb
linux-headers-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-amd64_3.2+43_i386.deb
linux-image-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-486_3.2+43_i386.deb
linux-image-2.6-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-bigmem_3.2+43_i386.deb
linux-image-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-pae_3.2+43_i386.deb
linux-image-2.6-686_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686_3.2+43_i386.deb
linux-image-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-amd64_3.2+43_i386.deb
linux-image-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-486_3.2+43_i386.deb
linux-image-686-bigmem_3.2+43_i386.deb
  to

Bug#654354: marked as done ([INTL:es] Spanish debconf template translation for linux-latest-2.6)

Your message dated Tue, 31 Jan 2012 04:32:26 +
with message-id e1rs5om-0002oh...@franck.debian.org
and subject line Bug#654681: fixed in linux-latest 43
has caused the Debian Bug report #654681,
regarding [INTL:es] Spanish debconf template translation for linux-latest-2.6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

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


-- 
654681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-latest-2.6
Version:
Severity: wishlist
Tags: l10n patch
# linux-latest-2.6 po-debconf translation to Spanish
# Copyright (C) 2012 Software in the Public Interest
# This file is distributed under the same license as the linux-latest-2.6 package.
#
# Changes:
# - Initial translation
# Slime Siabef slimesiabef.deb...@gmail.com, 2012
#
# - Updates
#
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid 
msgstr 
Project-Id-Version: linux-latest-2.6_39\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2011-07-24 16:15+0200\n
PO-Revision-Date:\n
Last-Translator: Slime Siabef slimesiabef.deb...@gmail.com\n
Language-Team: Debian Spanish debian-l10n-span...@lists.debian.org\n
Language: \n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Poedit-Language: Spanish\n

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid This system requires a different kernel configuration
msgstr El sistema requiere una configuración diferente del núcleo.

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid Debian's '686' kernel configuration has been replaced by the '686-pae' configuration, which uses PAE (Physical Address Extension).  However, the CPU in this system does not support PAE.
msgstr La configuración del núcleo «686» de Debian ha sido reemplazada por la configuración «686-pae», que utiliza PAE (Extensión de dirección física). Sin embargo, la CPU del sistema no lo soporta.

#. Type: error
#. Description
#: ../linux-image-686.templates:1001
msgid You should install linux-image-486 and remove linux-image-686 and/or linux-image-2.6-686 if they are currently installed.
msgstr Se debería instalar linux-image-486 y eliminar linux-image-686 y/o linux-image-2.6-686 si estuviesen instalados.

---End Message---
---BeginMessage---
Source: linux-latest
Source-Version: 43

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

linux-doc-2.6_3.2+43_all.deb
  to main/l/linux-latest/linux-doc-2.6_3.2+43_all.deb
linux-doc_3.2+43_all.deb
  to main/l/linux-latest/linux-doc_3.2+43_all.deb
linux-headers-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-486_3.2+43_i386.deb
linux-headers-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-686-pae_3.2+43_i386.deb
linux-headers-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-2.6-amd64_3.2+43_i386.deb
linux-headers-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-486_3.2+43_i386.deb
linux-headers-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-686-pae_3.2+43_i386.deb
linux-headers-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-headers-amd64_3.2+43_i386.deb
linux-image-2.6-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-486_3.2+43_i386.deb
linux-image-2.6-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-bigmem_3.2+43_i386.deb
linux-image-2.6-686-pae_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686-pae_3.2+43_i386.deb
linux-image-2.6-686_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-686_3.2+43_i386.deb
linux-image-2.6-amd64_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-2.6-amd64_3.2+43_i386.deb
linux-image-486_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-486_3.2+43_i386.deb
linux-image-686-bigmem_3.2+43_i386.deb
  to main/l/linux-latest/linux-image-686-bigmem_3.2+43_i386.deb

Processing of linux-latest_43_multi.changes

2012-01-30 Thread Debian FTP Masters

linux-latest_43_multi.changes uploaded successfully to localhost
along with the files:
  linux-latest_43.dsc
  linux-latest_43.tar.gz
  linux-doc_3.2+43_all.deb
  linux-image-686_3.2+43_i386.deb
  linux-source_3.2+43_all.deb
  linux-image-2.6-686_3.2+43_i386.deb
  linux-tools_3.2+43_all.deb
  linux-image-686-bigmem_3.2+43_i386.deb
  linux-doc-2.6_3.2+43_all.deb
  linux-source-2.6_3.2+43_all.deb
  linux-image-2.6-686-bigmem_3.2+43_i386.deb
  linux-tools-2.6_3.2+43_all.deb
  xen-linux-system-2.6-xen-686_3.2+43_i386.deb
  linux-image-486_3.2+43_i386.deb
  linux-image-2.6-486_3.2+43_i386.deb
  linux-headers-486_3.2+43_i386.deb
  linux-headers-2.6-486_3.2+43_i386.deb
  linux-image-686-pae_3.2+43_i386.deb
  linux-image-2.6-686-pae_3.2+43_i386.deb
  linux-headers-686-pae_3.2+43_i386.deb
  linux-headers-2.6-686-pae_3.2+43_i386.deb
  xen-linux-system-686-pae_3.2+43_i386.deb
  linux-image-amd64_3.2+43_i386.deb
  linux-image-2.6-amd64_3.2+43_i386.deb
  linux-headers-amd64_3.2+43_i386.deb
  linux-headers-2.6-amd64_3.2+43_i386.deb
  xen-linux-system-amd64_3.2+43_i386.deb

Greetings,

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1rs5gy-00018l...@franck.debian.org

Processed: reassign 658067 to src:linux-2.6