kernel-handbook_1.0.13_multi.changes ACCEPTED into unstable

2012-06-16 Thread Debian FTP Masters



Accepted:
debian-kernel-handbook_1.0.13_all.deb
  to main/k/kernel-handbook/debian-kernel-handbook_1.0.13_all.deb
kernel-handbook_1.0.13.dsc
  to main/k/kernel-handbook/kernel-handbook_1.0.13.dsc
kernel-handbook_1.0.13.tar.gz
  to main/k/kernel-handbook/kernel-handbook_1.0.13.tar.gz


Changes:
kernel-handbook (1.0.13) unstable; urgency=low
 .
  * Note that removed firmware is still packaged; suggested by Karl Goetz
  * Remove documentation of linux-tree package, removed in squeeze
  * Remove documentation of linux-patch-debian package, obsoleted by
packaging changes and redundant with snapshot.debian.org
  * Remove documentation of version-specific /etc/modules files, which are
no longer supported
  * Use 3.x version numbers and current flavour and featureset names in
examples
  * Refer to the linux source package rather than linux-2.6
  * Remove outdated advice to try disabling ACPI and IRQ routing options
  * Remove an unnecessary version qualification
  * Update explanation of source directories for quilted linux package
  * Update example orig tarball names to indicate xz compression
  * Update hooks policy description
- Debian 6.0 release is now in the past
- initramfs-tools is no longer special
- squeeze+1 has a name and number
  * Note that official Linux kernel packages will use only 2 version
components in wheezy+1


Override entries for your package:
debian-kernel-handbook_1.0.13_all.deb - extra doc
kernel-handbook_1.0.13.dsc - source doc

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


Thank you for your contribution to Debian.


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



Processing of kernel-handbook_1.0.13_multi.changes

2012-06-16 Thread Debian FTP Masters
kernel-handbook_1.0.13_multi.changes uploaded successfully to localhost
along with the files:
  kernel-handbook_1.0.13.dsc
  kernel-handbook_1.0.13.tar.gz
  debian-kernel-handbook_1.0.13_all.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/e1sg84x-0003xw...@franck.debian.org



Bug#677828: Intel Centrino 6200 require rmmod & modprobe to work properly

2012-06-16 Thread Patrik Dufresne
Package: firmware-iwlwifi
Version: 0.35

I lost connectivity with my wifi connection. To fix it, I need to
unload and reload the module named 'iwlwifi' with rmmod and modprobe.

Step to reproduce:
1. Open the laptop, and open a user session.
2. The network manager is connecting automatically to the network. At
this point, my connection is working as expected.


3. After some period of time, while browsing the web I don't get any
respond from the server.
4. Doing a ping to google.com give me an error :Destination Host Unreachable
5. Doing a ping to 192.168.14.1 (this is my router) also give me :
Destination Host Unreachable
6. The network manager mark the wireless still connected. Turning
on/off the wifi, doesn't fix the problem. Changing the wireless
network doesn't fix the problem.

7. Running rmmod iwlwifi followed by modprobe iwlwifi fix the problem.

Patrik Dufresne



-- 
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/CAJ=kj5zMmLQ=0L9n7YiqFsj61im02z5HY0LwxgxsPAL=2wb...@mail.gmail.com



firmware-free_3.1_i386.changes ACCEPTED into unstable

2012-06-16 Thread Debian FTP Masters



Accepted:
firmware-free_3.1.dsc
  to main/f/firmware-free/firmware-free_3.1.dsc
firmware-free_3.1.tar.gz
  to main/f/firmware-free/firmware-free_3.1.tar.gz
firmware-linux-free_3.1_all.deb
  to main/f/firmware-free/firmware-linux-free_3.1_all.deb


Changes:
firmware-free (3.1) unstable; urgency=low
 .
  * Update to linux-support 3.2.0-2
- Remove build-dependency, as this is only used when preparing the
  source package (Closes: #629730)
  * Add isci parameter blob
  * Add makefiles and scripts for av7110, dsp56k and keyspan_pda firmware
  * debian/control: Set Multi-Arch: foreign to allow for installation
of foreign linux-image packages
  * Add firmware for ITL USB-DUXsigma
  * Set the upstream homepage URL to the current gitweb page for
linux-firmware.git
  * Update initramfs on installation, since it may need to include the
firmware for 3c574_cs, 3c589_cs, isci or pcnet_cs (Closes: #555949)


Override entries for your package:
firmware-free_3.1.dsc - source kernel
firmware-linux-free_3.1_all.deb - optional kernel

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 555949 629730 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1sg6el-0001rv...@franck.debian.org



Processing of firmware-free_3.1_i386.changes

2012-06-16 Thread Debian FTP Masters
firmware-free_3.1_i386.changes uploaded successfully to localhost
along with the files:
  firmware-free_3.1.dsc
  firmware-free_3.1.tar.gz
  firmware-linux-free_3.1_all.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/e1sg6c1-00014d...@franck.debian.org



Bug#629730: marked as done (firmware-free: FTBFS: build-dependency not installable: linux-support-2.6.38-1)

2012-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Jun 2012 03:32:49 +
with message-id 
and subject line Bug#629730: fixed in firmware-free 3.1
has caused the Debian Bug report #629730,
regarding firmware-free: FTBFS: build-dependency not installable: 
linux-support-2.6.38-1
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.)


-- 
629730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firmware-free
Version: 3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110607 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> ┌──┐
> │ Install firmware-free build dependencies (apt-based resolver)   
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-firmware-free-dummy : Depends: linux-support-2.6.38-1 
> but it is not installable
> E: Broken packages

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/06/07/firmware-free_3_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Source: firmware-free
Source-Version: 3.1

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

firmware-free_3.1.dsc
  to main/f/firmware-free/firmware-free_3.1.dsc
firmware-free_3.1.tar.gz
  to main/f/firmware-free/firmware-free_3.1.tar.gz
firmware-linux-free_3.1_all.deb
  to main/f/firmware-free/firmware-linux-free_3.1_all.deb



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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated firmware-free 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: Sun, 17 Jun 2012 04:19:31 +0100
Source: firmware-free
Binary: firmware-linux-free
Architecture: source all
Version: 3.1
Distribution: unstable
Urgency: low
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description: 
 firmware-linux-free - Binary firmware for various drivers in the Linux kernel
Closes: 555949 629730
Changes: 
 firmware-free (3.1) unstable; urgency=low
 .
   * Update to linux-support 3.2.0-2
 - Remove build-dependency, as this is only used when preparing the
   source package (Closes: #629730)
   * Add isci parameter blob
   * Add makefiles and scripts for av7110, dsp56k and keyspan_pda firmware
   * debian/control: Set Multi-Arch: foreign to allow for installation
 of foreign linux-image packages
   * Add firmware for ITL USB-DUXsigma
   * Set the upstream homepage URL to the current gitweb page for
 linux-firmware.git
   * Update initramfs on installation, since it may need to include the
 firmware for 3c574_cs, 3c589_cs, isci or pcnet_cs (Closes: #555949)
Checksums-Sha1: 
 d98cf6188d048aa57a64067f45fc606e436b7dae 1787 firmware-free_3.1.dsc
 acb0ccd3f01bf4e6d3489d29c54aca68e1bb4d28 56243 firmware-free_3.1.tar.gz
 cc5bc17d28d7bf7fe107bc79bc66ae68de9a491d 10508 firmware-linux-free_3.1_all.deb
Checksums-Sha256: 
 ee574922ac8a8201681053a39e87fc9187bff2ac1d1ca4f

Bug#555949: marked as done (does not trigger a rebuild of the initramfs)

2012-06-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Jun 2012 03:32:49 +
with message-id 
and subject line Bug#555949: fixed in firmware-free 3.1
has caused the Debian Bug report #555949,
regarding does not trigger a rebuild of the initramfs
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.)


-- 
555949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-linux-free
Version: 2.6.31-1
Severity: normal

Installing a firmware package should trigger a rebuild of all initramfs.

-- 
ciao,
Marco


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: firmware-free
Source-Version: 3.1

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

firmware-free_3.1.dsc
  to main/f/firmware-free/firmware-free_3.1.dsc
firmware-free_3.1.tar.gz
  to main/f/firmware-free/firmware-free_3.1.tar.gz
firmware-linux-free_3.1_all.deb
  to main/f/firmware-free/firmware-linux-free_3.1_all.deb



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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated firmware-free 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: Sun, 17 Jun 2012 04:19:31 +0100
Source: firmware-free
Binary: firmware-linux-free
Architecture: source all
Version: 3.1
Distribution: unstable
Urgency: low
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description: 
 firmware-linux-free - Binary firmware for various drivers in the Linux kernel
Closes: 555949 629730
Changes: 
 firmware-free (3.1) unstable; urgency=low
 .
   * Update to linux-support 3.2.0-2
 - Remove build-dependency, as this is only used when preparing the
   source package (Closes: #629730)
   * Add isci parameter blob
   * Add makefiles and scripts for av7110, dsp56k and keyspan_pda firmware
   * debian/control: Set Multi-Arch: foreign to allow for installation
 of foreign linux-image packages
   * Add firmware for ITL USB-DUXsigma
   * Set the upstream homepage URL to the current gitweb page for
 linux-firmware.git
   * Update initramfs on installation, since it may need to include the
 firmware for 3c574_cs, 3c589_cs, isci or pcnet_cs (Closes: #555949)
Checksums-Sha1: 
 d98cf6188d048aa57a64067f45fc606e436b7dae 1787 firmware-free_3.1.dsc
 acb0ccd3f01bf4e6d3489d29c54aca68e1bb4d28 56243 firmware-free_3.1.tar.gz
 cc5bc17d28d7bf7fe107bc79bc66ae68de9a491d 10508 firmware-linux-free_3.1_all.deb
Checksums-Sha256: 
 ee574922ac8a8201681053a39e87fc9187bff2ac1d1ca4f5f8b6bf49d2b34ec1 1787 
firmware-free_3.1.dsc
 449808f08846da968b6033a13912f9bed7832a6e9fcd064a0161fcf5a0b87314 56243 
firmware-free_3.1.tar.gz
 b7d938dd25bee94ae496bcdb8fe6f2f12814abc4f2fd63ab6276e0a16ac6c548 10508 
firmware-linux-free_3.1_all.deb
Files: 
 68fbd45b3275a9e2c462a4539fc9108e 1787 kernel optional firmware-free_3.1.dsc
 8f111229d121f447a4b6ea58cb897e00 56243 kernel optional firmware-free_3.1.tar.gz
 603ccc0414e3c125130a5127f36446a7 10508 kernel optional 
firmware-linux-free_3.1_all.deb

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

iQIVAwUBT91Onee/yOyVhhEJAQqz4Q/+PUAvOHe0wP/Y2RiiZX6R2p9y8Zu/Q0Cb
VwYZ+Y0FkpRy7QeNOU2p58FHa2vS+63RxtvCplhOuR1ukrRBTsvSpVjmyDiobppa
BdxT5xLyE+AnXZud3lEFX9ATQEXkKbDMZnTcCT/siICmn7oMRc5HyrbWgmyJp6wI
hyOPS0KLwxS3RbPWadVW+Pkn0nSSeUB0WpBavX258/GXxPd6DeSs5i2ZZ/V2gExX
DANeJvWiPJOSl9rIMvw7UJWdIB2uw7eGyB2nNhyPG12XDZD/aD5g0rbDPqI5w/MR
wYWnAst0G1hX+G5tKlT10pmbGvM03wuR8gOkqeVdYNlYeqEGjRabU/s4SiP8Y7k6
aqbEh1PJr8FkBmSu3NKS8LfNVXpl7GTjxs+VYpXwUgmx7Wf+33W/MuuhNo7f6fCJ
CgRHrENYIQmhkA0W50+1JU8Ler7ssKgJ0H4wSeGQI6Rr4Llostp+gvJTsXHr6IaT
kSgYHzkZJjdo2E++QpBH1f1PjDzcPQwaZxfSVjpyCnUUVWDtqmdGdan9kHruxcfw
SpIiYy8L0/MPt2kxZY1CpZ/K4ZUK5y6FW4jPlV5yXQTqEmLUx16KJ/dm/iFvoPbZ
7/ZGoVk3GPk+l8EowpYcUaf+s8Q2OoUOzE1nNyTz+vHEctbRUYDeiz92aaaW9Z2P
ixdq4uJzmkk=
=7Mz3
-END PGP SIGNATURE-


--- End Message ---


Processed: tagging 555949

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 555949 + pending
Bug #555949 [firmware-linux-free] does not trigger a rebuild of the initramfs
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
555949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555949
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.133990317415812.transcr...@bugs.debian.org



Processed: severity of 635840 is wishlist

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 635840 wishlist
Bug #635840 [firmware-free] Missing firmware for carl9170 driver
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
635840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635840
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.133990270514603.transcr...@bugs.debian.org



Processed: fixed 574564 in firmware-free/3

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 574564 firmware-free/3
Bug #574564 [firmware-linux-free] firmware-linux-free: non pertinent NEWS file
Marked as fixed in versions firmware-free/3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
574564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574564
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.133990262913677.transcr...@bugs.debian.org



Processed: tagging 629730

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 629730 + pending
Bug #629730 [src:firmware-free] firmware-free: FTBFS: build-dependency not 
installable: linux-support-2.6.38-1
Ignoring request to alter tags of bug #629730 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
629730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629730
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.133989171531838.transcr...@bugs.debian.org



Bug#673496: [lenny -> squeeze regression] wifi broken (?) (Re: Bug#673496: It's alive, Jim.)

2012-06-16 Thread Paul Zimmerman




- Original Message -
Jonathan Nieder  wrote:

>Do I understand correctly that when you say "the machine recognizes
> it again" at [1] you are talking about the squeeze kernel, then?

Yes, the standard i386 Squeeze kernel is what I have been using. Trying
to use the backported kernel from Wheezy runs into the freeze-up
problem I described. It could not get an IP address even once in many,
many tries with the whatever kernel was current in March, But now, it 
works just fine every time. That's very odd consistency for "unreliable" 
hardware.

I wonder if the original submitter of bug 604613 is still using the same 
machine with Squeeze, and has also found the bug resolved?




-- 
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/1339888196.55075.yahoomail...@web162603.mail.bf1.yahoo.com



Processed: Re: firmware-free: FTBFS: build-dependency not installable: linux-support-2.6.38-1

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 629730 + pending
Bug #629730 [src:firmware-free] firmware-free: FTBFS: build-dependency not 
installable: linux-support-2.6.38-1
Added tag(s) pending.
> # letting version tracking do its work
> tags 629730 - wheezy sid
Bug #629730 [src:firmware-free] firmware-free: FTBFS: build-dependency not 
installable: linux-support-2.6.38-1
Removed tag(s) sid and wheezy.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
629730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629730
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.133988763613564.transcr...@bugs.debian.org



Bug#629730: firmware-free: FTBFS: build-dependency not installable: linux-support-2.6.38-1

2012-06-16 Thread Jonathan Nieder
tags 629730 + pending
# letting version tracking do its work
tags 629730 - wheezy sid
quit

Ben Hutchings wrote:

> We should possibly split that package to avoid this busy-work, since
> firmware-free has no requirement for the version-specific data in that
> package.

Fixed in r18679:

 * Update to linux-support 3.2.0-1
   - Remove build-dependency, as this is only used when preparing the
 source package



-- 
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/20120616225956.GA17725@burratino



Bug#675302: [Bug 50571] nouveau crashes with GeForce GT 520

2012-06-16 Thread Gedalya

On 6/13/2012 9:43 PM, bugzilla-dae...@freedesktop.org wrote:

If you can find the fix by bisecting, that would make me very happy.



I hope I got it all right, I tried to be very careful...


$ git bisect bad
4cbb0f8d2b06c72aae3552ff1a0a57814c6ce7d2 is the first bad commit
commit 4cbb0f8d2b06c72aae3552ff1a0a57814c6ce7d2
Author: Ben Skeggs 
Date:   Mon Mar 12 15:23:44 2012 +1000

drm/nvd0/disp: disconnect encoders before reprogramming them

Signed-off-by: Ben Skeggs 

:04 04 4648bcf9d08c294fdb7ef76343e6f89e3cc2fe24 
2c31aa85ebf6c6f3b96fc6e91934a895bb42c0a3 M  drivers



$ git bisect log
# bad: [f8f5701bdaf9134b1f90e5044a82c66324d2073f] Linux 3.5-rc1
# good: [c16fa4f2ad19908a47c63d8fa436a1178438c7e7] Linux 3.3
git bisect start 'v3.5-rc1' 'v3.3' '--' 'drivers/gpu/drm/nouveau'
# bad: [4a206ffc0bfe8e8c3fc0468a052f5b0bb625a57b] drm/nouveau: oops, 
create m2mf for nvd9 too

git bisect bad 4a206ffc0bfe8e8c3fc0468a052f5b0bb625a57b
# good: [7d3a766b6aa4e293e72bfd6add477f05ac7fdf5a] drm/nouveau/pm: init 
only after display subsystem has been created

git bisect good 7d3a766b6aa4e293e72bfd6add477f05ac7fdf5a
# bad: [f1377998eede7a8caa124fcf6a589b02c9e2bac7] drm/nouveau: add 
userspace fallback hints.

git bisect bad f1377998eede7a8caa124fcf6a589b02c9e2bac7
# good: [c11dd0da5277596d0ccdccb745b273d69a94f2d7] drm/nouveau/pm: fix 
oops if chipset has no pm support at all

git bisect good c11dd0da5277596d0ccdccb745b273d69a94f2d7
# good: [6e83fda2c055f17780b2feef404f06803a49a261] drm/nvd0/disp: 
initial implementation of displayport

git bisect good 6e83fda2c055f17780b2feef404f06803a49a261
# good: [3488c57b983546e6bf4c9e0bfd0f7f2a1292267a] drm/nvd0/disp: move 
syncs/magic setup to or mode_set

git bisect good 3488c57b983546e6bf4c9e0bfd0f7f2a1292267a
# bad: [2f5394c3ed573de2ab18cdac503b8045cd16ac5e] drm/nouveau: map first 
page of mmio early and determine chipset earlier

git bisect bad 2f5394c3ed573de2ab18cdac503b8045cd16ac5e
# bad: [4cbb0f8d2b06c72aae3552ff1a0a57814c6ce7d2] drm/nvd0/disp: 
disconnect encoders before reprogramming them

git bisect bad 4cbb0f8d2b06c72aae3552ff1a0a57814c6ce7d2




--
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/4fdd0eeb.9060...@gedalya.net



Bug#677164: [3.2.17-1 -> 3.2.18-1 regression] Wacom tablet in Thinkpad x220t not working

2012-06-16 Thread Jonathan Nieder
tags 677164 + upstream
quit

Nils Kanning wrote:

> I built the kernel from the git repository as you described. The tablet
> does not work. 

Ah, ok.  Let's take this upstream.



-- 
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/20120616223956.GA27070@burratino



Bug#629730: Ping - FTBFS

2012-06-16 Thread Arne Wichmann
This RC bug is patched but unfixed for more than a year now. Is there any
plan to change this?

cu

AW
-- 
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (a...@linux.de)


signature.asc
Description: Digital signature


Bug#677813: firmware-linux-nonfree: missing firmware for Radeon Pitcairn GPU

2012-06-16 Thread Frederik Himpe
Package: firmware-linux-nonfree
Version: 0.36
Severity: wishlist

I'm using Linux 3.5 git with a Radeon HD 7850 graphics card. The radeon kernel
module in Linux 3.5 needs the pitcairn firmware files to load correctly. These
can be downloaded from http://people.freedesktop.org/~agd5f/radeon_ucode/



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

Kernel: Linux 3.5.0-rc2+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-tools0.106
ii  linux-image-3.2.0-2-amd64 [linux-image]3.2.20-1
ii  linux-image-3.4-trunk-amd64 [linux-image]  3.4.1-1~experimental.1
ii  linux-image-3.5.0-rc2+ [linux-image]   1

-- 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/20120616220612.4976.16311.reportbug@piranha.localdomain



Bug#668547: linux-image-3.2.0-2-686-pae: spammed by cfg80211 : Calling CRDA to update world regulatory domain

2012-06-16 Thread Olivier Berger
Hi.

Olivier Berger  writes:

> As you can see from this logs excerpts, I get spammed by cfg80211 in kernel 
> logs every 5 seconds or so :-(
>
> This tends to be filling up /var, if not paying attention.
>
> I guess there must be something wrong somewhere...
>

I've just commented out the previous line in
/etc/modprobe.d/cfg80211.conf that used to set : options cfg80211
ieee80211_regdom="EU"

Then, I restarted... and tada ! the messages are gone :-)

# iw reg get
country 00:
(2402 - 2472 @ 40), (3, 20)
(2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
(2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
(5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
(5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
# iw reg set FR
root@inf-8657:~# iw reg get
country FR:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS

All seems much better now :-)

Who's the faulty one ?

Hope this helps.

Best regards,
-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)



-- 
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/87ipeqc3ta@inf-8657.int-evry.fr



Re: [Ksummit-2012-discuss] [ATTEND] Kernel summit - bwh

2012-06-16 Thread Josh Boyer
On Sat, Jun 16, 2012 at 12:44:18AM +0100, Ben Hutchings wrote:
> As a member of the Debian kernel team and maintainer of the 3.2.y stable
> series, I'm interested in discussing things like:
> 
> - Ensuring that distributions can enable new features with minimal
>   impact to those who don't use them
> - User documentation for new features (that aren't syscalls)
> - Process for backporting and re-testing bug fixes
> - Forwarding and tracking of bugs from distributions to upstream
> - Choosing kernel versions for distributions and 'longterm' stable
>   branches
> - Early detection of bugs (static checking, test suites, more compiler
>   diagnostics...)

I'd very much like to discuss all of that.

> Also:
> 
> - Maintenance of linux-firmware, and (if I haven't dealt with it by
>   then) getting rid of the firmware directory

This as well, though it might be small enough to do in a hallway track.

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/20120616193233.gc28...@zod.bos.redhat.com



Re: Bug#676921: ITP: amd64-microcode -- Processor microcode firmware for AMD CPUs

2012-06-16 Thread Daniel Baumann
sounds all very reasonable to me, thanks Henrique.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
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/4fdcd513.6010...@progress-technologies.net



Re: Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD

2012-06-16 Thread Borislav Petkov
On Sat, Jun 16, 2012 at 12:14:14PM +0200, Thomas Schwinge wrote:
> Hi!
> 
> After many others that played with no problems, I just tried playing
> Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly
> up-to-date Debian GNU/Linux testing system.
> 
> $ uname -a
> Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 
> GNU/Linux
> 
> ... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.
> 
> While "loading" the CD in Rhythmbox, after a few seconds the kernel
> crashed.  I rebooted, tried again, and it crashed again.  At
>  you
> can find the panic message (low resolution, sorry), pointing to the
> SCSI/ATA code.

Let me guess: AMD K8?

Also, can I get /proc/cpuinfo please?

Thanks.

-- 
Regards/Gruss,
Boris.


-- 
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/20120616181008.gb20...@liondog.tnic



Bug#677760: O: mkvmlinuz -- create a kernel to boot a PowerPC machine from Open Firmware

2012-06-16 Thread Ana Guerrero
Package: wnpp
Severity: normal

The current maintainers of mkvmlinuz, Sven Luther and Aur�lien G�r�me
are apparently not active anymore.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: mkvmlinuz
Binary: mkvmlinuz
Version: 35
Priority: optional
Section: devel
Maintainer: Debian Kernel Team 
Build-Depends: docbook-to-man, debhelper (>= 4.1.16), po-debconf, gcc-multilib 
[ppc64]
Architecture: powerpc ppc64
Standards-Version: 3.8.0
Format: 1.0
Directory: pool/main/m/mkvmlinuz
Files:
 c7529c542b47d0231f62264dd3fce7e6 990 mkvmlinuz_35.dsc
 b5973b8084cd251313184e414de2af17 58814 mkvmlinuz_35.tar.gz
Uploaders: Sven Luther , Aur�lien G�R�ME 
Vcs-Browser: http://svn.debian.org/wsvn/kernel/dists/trunk/utils/mkvmlinuz/
Vcs-Svn: svn://svn.debian.org/svn/kernel/dists/trunk/utils/mkvmlinuz/
Checksums-Sha1:
 1ac23dec7f56ae9b1c487f885cf398a24174aca0 990 mkvmlinuz_35.dsc
 be1a39f8a507a9ab43a762aa8da5b2584f81f68e 58814 mkvmlinuz_35.tar.gz
Checksums-Sha256:
 d11c8a7dfe3b39cd13c3d0bb3b3c0d14f5aac032402dbf113f9f94f5000fb3ae 990 
mkvmlinuz_35.dsc
 6d728726a323c7e446b4eacb58e7051a9876ccc777351dfd05067f348e97d0ad 58814 
mkvmlinuz_35.tar.gz

Package: mkvmlinuz
Priority: optional
Section: devel
Installed-Size: 304
Maintainer: Debian Kernel Team 
Architecture: powerpc
Version: 35
Depends: bash (>= 3), binutils, debconf | debconf-2.0, libc6 (>= 2.7-1)
Filename: pool/main/m/mkvmlinuz/mkvmlinuz_35_powerpc.deb
Size: 70024
MD5sum: 31656e098416cb934b06dcccf99b775e
SHA1: eac6c62c3bbf743269983bfcf0d78877039ce138
SHA256: 6064a7aa859ec549d0adcdb4e148af8e008b8450be04542adf49d53d73cc9405
Description: create a kernel to boot a PowerPC machine from Open Firmware
 This little program takes a PowerPC Linux kernel as an uncompressed
 ELF image file (usually called vmlinux or such) and adds boot code
 and possibly a ramdisk to create a compressed kernel image that
 can be booted directly from Open Firmware, thus eliminating the
 need for a second-stage bootloader such as yaboot or quik. This is
 especially useful on PowerPC sub-architectures which do not have a
 bootloader at all, but may also come in handy for install kernels,
 netboot systems, and the like.
Tag: admin::boot, admin::kernel, implemented-in::c, implemented-in::shell, 
interface::commandline, role::program, scope::utility




--
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/20120616182749.ga10...@pryan.ekaia.org



Re: Bug#676921: ITP: amd64-microcode -- Processor microcode firmware for AMD CPUs

2012-06-16 Thread Henrique de Moraes Holschuh
On Tue, 12 Jun 2012, Daniel Baumann wrote:
> On 06/12/2012 06:04 PM, Henrique de Moraes Holschuh wrote:
> > I don't care as long as nobody is going to get in the way of an
> > urgency=high upload of firmware-nonfree to stable-proposed-updates or
> > stable-updates.
> 
> there have been updates of firmware-* packages in the past and more
> recently for squeeze too, so i don't think that's a problem.
> 
> > Well, the amd64-microcode has not cleared NEW yet.  How should we proceed?
> 
> in my personal opinion, i'd prefere having it integrated into
> firmware-nonfree. but it's not my call but the kernel team to decide.

Ok, I've looked into firmware-nonfree.

The intel and amd64 microcode packages are not simple static data-drop
packages (next upload of amd64-microcode will add the required postinst
bits).

They have to:

1. Issue sysfs commands to refresh running microcode and update the
initramfs when updated/installed.

2. Ensure that the microcode module and processor microcode will be added
to the initramfs.

This doesn't integrate automatically with firmware-nonfree right now, and I
really don't have the time to add support to figure out everything in
firmware-nonfree and add these operations to firmware-nonfree right before
the freeze, while I have 95% of that work already done and tested for the
intel-microcode and amd64-microcode packages.  I am just waiting the
amd64-microcode package to get past NEW to upload the required changes to
intel-microcode.

So, please approve the amd64-microcode package ASAP.  I will make sure to
provide a forward migration path to get both Intel and AMD64 microcodes
integrated in firmware-nonfree for at least amd64-microcode, and if we get
to a concensus that it makes sense to do so, also for intel-microcode.
But I'd really prefer to defer that work to post-freeze.

For Wheezy, we can just add suggests or recommends to firmware non-free for
the amd64 and i386 arches, pointing to "intel-firmware | amd64-firmware".

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
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/20120616180842.ga32...@khazad-dum.debian.net



Bug#677727: linux-image-3.4-trunk-686-pae: lirc / devinput remote control, only avery second keypress is recognised vs. sids 3.2 kernel where everything is ok

2012-06-16 Thread Ben Hutchings
On Sat, 2012-06-16 at 16:26 +0200, Michael Schmitt wrote:
> Package: linux-2.6
> Version: 3.4.1-1~experimental.1
> Severity: normal
> 
> Dear Maintainers,
> 
> with the current kernel from experimental only every second keypress is
> recognized on my ir remote control. Reboot to kernel 3.2 from sid, all back to
> normal.
> I have no idea how the kernel could be responsible there... ok, a weird bug in
> the responsible kernel module for the remote, but somehow I doubt that.
> 
> If you need any lirc configs or logfiles give me a note, as right now I don't
> think my lirc config does help much here.

It looks like you're using the mceusb driver, which hasn't been changed
between these versions.  So this is presumably due to a change in the
core remote control code.

Could you test the attached patch, following the instructions at
?

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus
From 81c813bb7eba803f619e617f325c3820972d3d52 Mon Sep 17 00:00:00 2001
From: Ben Hutchings 
Date: Sat, 16 Jun 2012 17:32:08 +0100
Subject: [PATCH] Revert "[media] rc/ir-raw: use kfifo_rec_ptr_1 instead of
 kfifo"

This reverts commit df1caa587aa526f73d07abf85ebab88d0fd754ec.
---
 drivers/media/rc/rc-core-priv.h |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/media/rc/rc-core-priv.h b/drivers/media/rc/rc-core-priv.h
index 96f0a8b..b72f858 100644
--- a/drivers/media/rc/rc-core-priv.h
+++ b/drivers/media/rc/rc-core-priv.h
@@ -35,7 +35,7 @@ struct ir_raw_event_ctrl {
 	struct list_head		list;		/* to keep track of raw clients */
 	struct task_struct		*thread;
 	spinlock_t			lock;
-	struct kfifo_rec_ptr_1		kfifo;		/* fifo for the pulse/space durations */
+	struct kfifo			kfifo;		/* fifo for the pulse/space durations */
 	ktime_tlast_event;	/* when last event occurred */
 	enum raw_event_type		last_type;	/* last event type */
 	struct rc_dev			*dev;		/* pointer to the parent rc_dev */
-- 
1.7.10



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


Bug#388453: marked as done (fails to handle interrupt)

2012-06-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Jun 2012 17:19:02 +0100
with message-id <1339863542.4942.180.ca...@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#388453: fails to handle interrupt
has caused the Debian Bug report #388453,
regarding fails to handle interrupt
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.)


-- 
388453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-via
Version: 1:0.1.33.2-3
Severity: minor

When starting the X server, the kernel spits out the following message:

Sep 20 10:02:59 arrow kernel: [drm] Initialized drm 1.0.1 20051102
Sep 20 10:02:59 arrow kernel: ACPI: PCI Interrupt :01:00.0[A] -> GSI 16 
(level, low) -> IRQ 201
Sep 20 10:02:59 arrow kernel: [drm] Initialized via 2.7.4 20051116 on minor 0
Sep 20 10:02:59 arrow kernel: agpgart: Found an AGP 3.0 compliant device at 
:00:00.0.
Sep 20 10:02:59 arrow kernel: agpgart: Xorg tried to set rate=x12. Setting 
to AGP3 x8 mode.
Sep 20 10:02:59 arrow kernel: agpgart: Putting AGP V3 device at 
:00:00.0 into 8x mode
Sep 20 10:02:59 arrow kernel: agpgart: Putting AGP V3 device at 
:01:00.0 into 8x mode
Sep 20 10:03:00 arrow kernel: irq 201: nobody cared (try booting with the 
"irqpoll" option)
Sep 20 10:03:00 arrow kernel:  [] __report_bad_irq+0x2b/0x69
Sep 20 10:03:00 arrow kernel:  [] note_interrupt+0x176/0x1a7
Sep 20 10:03:00 arrow kernel:  [] handle_IRQ_event+0x20/0x4c
Sep 20 10:03:00 arrow kernel:  [] __do_IRQ+0x65/0x91
Sep 20 10:03:00 arrow kernel:  [] do_IRQ+0x1d/0x2a
Sep 20 10:03:00 arrow kernel:  [] common_interrupt+0x1a/0x20
Sep 20 10:03:00 arrow kernel:  [] default_idle+0x2b/0x53
Sep 20 10:03:00 arrow kernel:  [] cpu_idle+0x3f/0x57
Sep 20 10:03:00 arrow kernel:  [] start_kernel+0x291/0x293
Sep 20 10:03:00 arrow kernel: handlers:
Sep 20 10:03:00 arrow kernel: [] 
(via_driver_irq_handler+0x0/0x148 [via])
Sep 20 10:03:00 arrow kernel: Disabling IRQ #201

However, the X server works well (so far).

Also, the X server mentions an unknown card ID to report:

(EE) VIA(0): Unknown Card-Ids (1631|D007), report this to the driver 
maintainer ASAP

xorg.conf and Xorg.0.log attached.

Ciao.Vincent.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages xserver-xorg-video-via depends on:
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  libdrm2  2.0.1-1 Userspace interface to kernel DRM 
ii  xserver-xorg-core1:1.0.2-9   X.Org X server -- core server

xserver-xorg-video-via recommends no packages.

-- no debconf information
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/share/fonts/X11/75dpi/:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load"bitma

Re: Linux features for wheezy

2012-06-16 Thread Maarten Lankhorst
Hey,

Op 16-06-12 14:18, Julien Cristau schreef:
> On Sat, Jun 16, 2012 at 14:16:46 +0200, Sven Joachim wrote:
>
>> Should we upload xserver-xorg-video-nouveau to unstable and wait for
>> complaints?  The version in sid is unusable anyway[1] :-/, so breaking
>> acceleration for some users might not be such a big deal.
>>
> Yes, that's kind of what I'm thinking.  Let's do that.
>
> Cheers,
> Julien
Would prefer it if the 2 patches I put on top of experimental be included too, 
it has a exa fix for rendering on pre-nv50 cards.

~Maarten


-- 
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/4fdc997a.5020...@canonical.com



Bug#677727: linux-image-3.4-trunk-686-pae: lirc / devinput remote control, only avery second keypress is recognised vs. sids 3.2 kernel where everything is ok

2012-06-16 Thread Michael Schmitt
Package: linux-2.6
Version: 3.4.1-1~experimental.1
Severity: normal

Dear Maintainers,

with the current kernel from experimental only every second keypress is
recognized on my ir remote control. Reboot to kernel 3.2 from sid, all back to
normal.
I have no idea how the kernel could be responsible there... ok, a weird bug in
the responsible kernel module for the remote, but somehow I doubt that.

If you need any lirc configs or logfiles give me a note, as right now I don't
think my lirc config does help much here.

regards
Michael



-- Package-specific info:
** Version:
Linux version 3.4-trunk-686-pae (Debian 3.4.1-1~experimental.1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP 
Wed Jun 6 15:11:31 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.4-trunk-686-pae 
root=UUID=a6f2436e-3ce5-411a-b013-0c345db5cf50 ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[   47.500683] IR LIRC bridge handler initialized
[   47.540454] Bluetooth: Core ver 2.16
[   47.540454] NET: Registered protocol family 31
[   47.540454] Bluetooth: HCI device and connection manager initialized
[   47.540454] Bluetooth: HCI socket layer initialized
[   47.540454] Bluetooth: L2CAP socket layer initialized
[   47.540454] Bluetooth: SCO socket layer initialized
[   47.590889] usbcore: registered new interface driver btusb
[   47.636053] mceusb 2-8:1.0: Registered FIC eHome Infrared Transceiver with 
mce emulator interface version 1
[   47.636059] mceusb 2-8:1.0: 2 tx ports (0x1 cabled) and 2 rx sensors (0x1 
active)
[   47.636140] usbcore: registered new interface driver mceusb
[   49.497914] kvm: Nested Virtualization enabled
[   51.735525] Adding 1951804k swap on /dev/md1.  Priority:-1 extents:1 
across:1951804k 
[   52.240161] scsi_verify_blk_ioctl: 104 callbacks suppressed
[   52.240166] mdadm: sending ioctl 1261 to a partition!
[   52.240170] mdadm: sending ioctl 1261 to a partition!
[   52.324368] EXT3-fs (md2): using internal journal
[   53.013612] loop: module loaded
[   53.043855] mdadm: sending ioctl 800c0910 to a partition!
[   53.043860] mdadm: sending ioctl 800c0910 to a partition!
[   53.043869] mdadm: sending ioctl 1261 to a partition!
[   53.043872] mdadm: sending ioctl 1261 to a partition!
[   53.049907] mdadm: sending ioctl 1261 to a partition!
[   53.049912] mdadm: sending ioctl 1261 to a partition!
[   53.050304] mdadm: sending ioctl 1261 to a partition!
[   53.050307] mdadm: sending ioctl 1261 to a partition!
[   56.858772] kjournald starting.  Commit interval 5 seconds
[   56.920109] EXT3-fs (md0): using internal journal
[   56.920114] EXT3-fs (md0): mounted filesystem with ordered data mode
[   57.932062] usb 1-1: new high-speed USB device number 7 using ehci_hcd
[   58.065315] usb 1-1: New USB device found, idVendor=0cf3, idProduct=7015
[   58.065320] usb 1-1: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
[   58.065324] usb 1-1: Product: UB95
[   58.065327] usb 1-1: Manufacturer: ATHEROS
[   58.065329] usb 1-1: SerialNumber: 12345
[   58.400248] cfg80211: Calling CRDA to update world regulatory domain
[   58.608067] usb 1-1: ath9k_htc: Firmware htc_7010.fw requested
[   58.608144] usbcore: registered new interface driver ath9k_htc
[   58.827307] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 72992
[   58.15] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 45 credits
[   59.015800] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
[   59.015804] ath: EEPROM regdomain: 0x809c
[   59.015807] ath: EEPROM indicates we should expect a country code
[   59.015810] ath: doing EEPROM country->regdmn map search
[   59.015812] ath: country maps to regdmn code: 0x52
[   59.015815] ath: Country alpha2 being used: CN
[   59.015817] ath: Regpair used: 0x52
[   59.236055] ieee80211 phy0: Atheros AR9287 Rev:2
[   59.236966] Registered led device: ath9k_htc-phy0
[   59.485046] cfg80211: World regulatory domain updated:
[   59.485051] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   59.485056] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   59.485060] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   59.485064] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   59.485068] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   59.485071] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   59.485323] cfg80211: Calling CRDA for country: CN
[   59.500271] cfg80211: Regulatory domain changed to country: CN
[   59.500276] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   59.500280] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm)
[   59.500283] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (N/A, 3000 
mBm)
[   59.724226] udevd[421]: renamed network interface wlan0 to wlan2
[   60.009

Bug#388453: fails to handle interrupt

2012-06-16 Thread Vincent Zweije
On Fri, Feb 13, 2009 at 03:42:22PM +0100, Vincent Zweije wrote:

||  And unfortunately, it's there in the trunk snapshot as well.

||  [   31.787940] [drm] Initialized drm 1.1.0 20060810
||  [   31.811084] pci :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
||  [   31.811244] [drm] Initialized via 2.11.1 20070202 on minor 0
||  [   31.843844] agpgart-amd64 :00:00.0: AGP 3.0 bridge
||  [   31.843861] agpgart: Xorg tried to set rate=x12. Setting to AGP3 x8 mode.
||  [   31.843868] agpgart-amd64 :00:00.0: putting AGP V3 device into 8x 
mode
||  [   31.843930] pci :01:00.0: putting AGP V3 device into 8x mode
||  [   32.318292] irq 16: nobody cared (try booting with the "irqpoll" option)
||  [   32.318299] Pid: 2514, comm: debtorrent-clie Not tainted 2.6.28-1-686 #1
||  [   32.318302] Call Trace:
||  [   32.318311]  [] __report_bad_irq+0x24/0x69
||  [   32.318316]  [] __report_bad_irq+0x2b/0x69
||  [   32.318320]  [] note_interrupt+0xed/0x131
||  [   32.318324]  [] handle_IRQ_event+0x23/0x51
||  [   32.318328]  [] handle_fasteoi_irq+0x86/0xaa
||  [   32.318332]  [] do_IRQ+0x67/0x7c
||  [   32.318336]  [] common_interrupt+0x23/0x28
||  [   32.318338] handlers:
||  [   32.318339] [] (via_driver_irq_handler+0x0/0x13d [via])
||  [   32.318350] Disabling IRQ #16

The problem has disappeared. Don't know when, haven't checked the PC in
a long time.

The new log is also mussing the line:

agpgart: Xorg tried to set rate=x12. Setting to AGP3 x8 mode.

so maybe it was Xorg after all.

Log attached.

From my part, this can probably be closed.

Vincent.

[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.0-2-686-pae (Debian 3.2.19-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP 
Fri Jun 1 18:56:14 UTC 2012
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009f800 (usable)
[0.00]  BIOS-e820: 0009f800 - 000a (reserved)
[0.00]  BIOS-e820: 000f - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 1bff (usable)
[0.00]  BIOS-e820: 1bff - 1bff3000 (ACPI NVS)
[0.00]  BIOS-e820: 1bff3000 - 1c00 (ACPI data)
[0.00]  BIOS-e820: fec0 - fec01000 (reserved)
[0.00]  BIOS-e820: fee0 - fee01000 (reserved)
[0.00]  BIOS-e820:  - 0001 (reserved)
[0.00] NX (Execute Disable) protection: active
[0.00] DMI 2.3 present.
[0.00] DMI: Packard Bell NEC 000/K8M800-8237, BIOS 
1.0v 06/24/2005
[0.00] e820 update range:  - 0001 (usable) 
==> (reserved)
[0.00] e820 remove range: 000a - 0010 (usable)
[0.00] last_pfn = 0x1bff0 max_arch_pfn = 0x100
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-C7FFF write-protect
[0.00]   C8000-CBFFF uncachable
[0.00]   CC000-D3FFF write-back
[0.00]   D4000-E uncachable
[0.00]   F-F write-through
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 00 mask FFE000 write-back
[0.00]   1 base 001C00 mask FFFC00 uncachable
[0.00]   2 base 00D000 mask FFF800 write-combining
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[0.00] found SMP MP-table at [c00f5a50] f5a50
[0.00] initial memory mapped : 0 - 01a0
[0.00] Base memory trampoline at [c009b000] 9b000 size 16384
[0.00] init_memory_mapping: -1bff
[0.00]  00 - 20 page 4k
[0.00]  20 - 001be0 page 2M
[0.00]  001be0 - 001bff page 4k
[0.00] kernel direct mapping tables up to 1bff @ 19fa000-1a0
[0.00] RAMDISK: 1aaa8000 - 1b4f1000
[0.00] ACPI: RSDP 000f76e0 00014 (v00 VIAK8 )
[0.00] ACPI: RSDT 1bff3000 0002C (v01 VIAK8  AWRDACPI 42302E31 AWRD 
01010101)
[0.00] ACPI: FACP 1bff3040 00074 (v01 VIAK8  AWRDACPI 42302E31 AWRD 
01010101)
[0.00] ACPI: DSDT 1bff30c0 045DC (v01 VIAK8  AWRDACPI 1000 MSFT 
010C)
[0.00] ACPI: FACS 1bff 00040
[0.00] ACPI: APIC 1bff76c0 0005A (v01 VIAK8  AWRDACPI 42302E31 AWRD 
01010101)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] 0MB HIGHMEM available.
[0.00] 447MB LOWMEM available.
[0.00]   mapped low ram: 0 - 1bff
[0.00]   low ram: 0 - 1bff
[0.00] Zone PFN

Re: Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD

2012-06-16 Thread Ben Hutchings
On Sat, 2012-06-16 at 12:14 +0200, Thomas Schwinge wrote:
> Hi!
> 
> After many others that played with no problems, I just tried playing
> Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly
> up-to-date Debian GNU/Linux testing system.
> 
> $ uname -a
> Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 
> GNU/Linux
> 
> ... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.
> 
> While "loading" the CD in Rhythmbox, after a few seconds the kernel
> crashed.  I rebooted, tried again, and it crashed again.  At
>  you
> can find the panic message (low resolution, sorry), pointing to the
> SCSI/ATA code.
> 
> Are there any such known issues?  Does the panic message give any clue
> already, or would you want me to reproduce that with debugging symbols,
> etc.?

Your computer is broken; Machine Check Exception indicates a hardware
fault.  The other text at the top of the screen may help to identify
which component is at fault.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus


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


Bug#677690: marked as done (linux-image-3.2.0-1-powerpc64: Kernel space errno ERESTARTNOHAND escaping into user space)

2012-06-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Jun 2012 14:37:33 +0100
with message-id <1339853853.4942.173.ca...@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#677690: linux-image-3.2.0-1-powerpc64: Kernel space 
errno ERESTARTNOHAND escaping into user space
has caused the Debian Bug report #677690,
regarding linux-image-3.2.0-1-powerpc64: Kernel space errno ERESTARTNOHAND 
escaping into user space
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.)


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

Compiling GHC (Glorious Haskell compiler) from the HEAD of the
git sources.

The GHC runtime is quite sophisticated and has a green threads
implementation a little like that of the JVM.

During compile of one particular file, the complier stalls in a
state where its consuming < 1% of CPU and < 1% of memory. Running
strace on the compile job, I find that when the compile stalls I
get the following strace output:

   rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
   pause() = ? ERESTARTNOHAND (To be restarted)
   --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
   sigreturn() = ? (mask now [])
   pause() = ? ERESTARTNOHAND (To be restarted)
   --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
   sigreturn() = ? (mask now [])
   pause() = ? ERESTARTNOHAND (To be restarted)
   --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---

that continues until I kill the process.

This problem is 100% deterministic and repeatable. Every time I
try to compile this one particlar file I end up with the same
stall.

A bit of googling tells me that ERESTARTNOHAND is supposedly a kernel
level errno that is not supposed to escape into userland. See:

https://lkml.org/lkml/2011/12/23/117

I logged a bug on the GHC bug tracker as well:

http://hackage.haskell.org/trac/ghc/ticket/6167



-- Package-specific info:
** Version:
Linux version 3.2.0-1-powerpc64 (Debian 3.2.7-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP 
Wed Feb 29 02:37:41 UTC 2012

** Command line:
root=UUID=dbcc8080-7bc6-496c-8506-b0b99408b35a ro ramdisk_size=8192 

** Not tainted

** Kernel log:
[9.749689] [drm] nouveau :0a:00.0: mem timing table length unknown: 14
[9.749788] i2c i2c-5: wf_smu_sat: attach_adapter method is deprecated
[9.749796] i2c i2c-5: Please use another way to instantiate your i2c_client
[9.749808] i2c i2c-5: wf_lm75: attach_adapter method is deprecated
[9.749815] i2c i2c-5: Please use another way to instantiate your i2c_client
[9.749825] i2c i2c-5: wf_max6690: attach_adapter method is deprecated
[9.749833] i2c i2c-5: Please use another way to instantiate your i2c_client
[9.768777] [drm] nouveau :0a:00.0: 1 available performance level(s)
[9.768793] [drm] nouveau :0a:00.0: 0: core 300MHz shader 300MHz memory 
500MHz fanspeed 100%
[9.768815] [drm] nouveau :0a:00.0: c: core 300MHz shader 300MHz memory 
500MHz
[9.769244] nouveau :0a:00.0: Using 32-bit DMA via iommu
[9.769342] [TTM] Zone  kernel: Available graphics memory: 5278624 kiB.
[9.769350] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB.
[9.769361] [TTM] Initializing pool allocator.
[9.769398] [drm] nouveau :0a:00.0: Detected 256MiB VRAM
[9.789577] [drm] nouveau :0a:00.0: 512 MiB GART (aperture)
[9.793299] [drm] nouveau :0a:00.0: Detected TMDS transmitter: sil164
[9.827652] sil164 5-0038: Detected device 1:6.0
[9.836263] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[9.836272] [drm] No driver support for vblank timestamp query.
[9.836304] [drm] nouveau :0a:00.0: Setting dpms mode 3 on vga encoder 
(output 0)
[9.836316] [drm] nouveau :0a:00.0: Setting dpms mode 3 on tmds encoder 
(output 1)
[9.836326] [drm] nouveau :0a:00.0: Setting dpms mode 3 on vga encoder 
(output 2)
[9.836337] [drm] nouveau :0a:00.0: Setting dpms mode 3 on tmds encoder 
(output 3)
[9.836347] [drm] nouveau :0a:00.0: Setting dpms mode 3 on TV encoder 
(output 4)
[9.856261] i2c i2c-6: wf_smu_sat: attach_adapter method is deprecated
[9.856269] i2c i2c-6: Please use another way to instantiate your i2c_client
[9.856281] i2c i2c-6: wf_lm75: attach_adapter method is deprecated
[9.856288] i2c i2c-6: Please use another way to instantiate yo

Re: Bug#677638: laptop-mode-tools: Breaks wired network when running on battery

2012-06-16 Thread Ben Hutchings
On Sat, 2012-06-16 at 14:52 +0530, Ritesh Raj Sarraf wrote:
> Added Ben and the Debian Kernel Team
> 
> 
> On Saturday 16 June 2012 07:29 AM, Guillem Jover wrote:
> >> On Friday 15 June 2012 09:27 PM, Guillem Jover wrote:
> >>> > > Since some time now (I only sat down to track it down pretty recently,
> >>> > > but this has going on for probably a year or more), laptop-mode-tools
> >>> > > has broken the wired network (e1000e) whenever I unplug the laptop 
> >>> > > from
> >>> > > the wall power.
> >>> > >
> >>> > > The culprit is BATT_THROTTLE_ETHERNET=1 in
> >>> > > «/etc/laptop-mode/conf.d/ethernet.conf».
> >>> > >
> >>> > > This turns the working ethernet device from this state:
> >>> > >
> >>> > > ,---
> >>> > > # ethtool eth0
> >>> > > Settings for eth0:
> >>> > > Supported ports: [ TP ]
> >>> > > Supported link modes:   10baseT/Half 10ba
> >>> > > 100baseT/Half 100baseT/Full
> >>> > > 1000baseT/Full 
> >>> > > Supported pause frame use: No
> >>> > > Supports auto-negotiation: Yes
> >>> > > Advertised link modes:  10baseT/Half 10ba
> >>> > > 100baseT/Half 100baseT/Full
> >>> > > 1000baseT/Full 
> >>> > > Advertised pause frame use: No
> >>> > > Advertised auto-negotiation: Yes
> >>> > > Speed: 100Mb/s
> >>> > > Duplex: Full
> >>> > > Port: Twisted Pair
> >>> > > PHYAD: 2
> >>> > > Transceiver: internal
> >>> > > Auto-negotiation: on
> >>> > > MDI-X: on
> >>> > > Supports Wake-on: pumbg
> >>> > > Wake-on: g
> >>> > > Current message level: 0x0001 (1)
> >>> > >drv
> >>> > > Link detected: yes
> >>> > > `---
> >>> > >
> >>> > > To this non-working state:
> >>> > >
> >>> > > ,---
> >>> > > # ethtool eth0
> >>> > > Settings for eth0:
> >>> > > Supported ports: [ TP ]
> >>> > > Supported link modes:   10baseT/Half 10ba
> >>> > > 100baseT/Half 100baseT/Full
> >>> > > 1000baseT/Full 
> >>> > > Supported pause frame use: No
> >>> > > Supports auto-negotiation: Yes
> >>> > > Advertised link modes:  10baseT/Half 10ba
> >>> > > 100baseT/Half 100baseT/Full
> >>> > > 1000baseT/Full 
> >>> > > Advertised pause frame use: No
> >>> > > Advertised auto-negotiation: Yes
> >>> > > Speed: Unknown!
> >>> > > Duplex: Unknown! (255)
> >>> > > Port: Twisted Pair
> >>> > >   PHYAD: 2
> >>> > > Transceiver: internal
> >>> > > Auto-negotiation: on
> >>> > > MDI-X: Unknown
> >>> > > Supports Wake-on: pumbg
> >>> > > Wake-on: d
> >>> > > Current message level: 0x0001 (1)
> >>> > >drv
> >>> > > Link detected: no
> >>> > > `---
> >>> > >
> >>> > > If I set BATT_THROTTLE_ETHERNET to 0, then everything works as before.
> >>> > >
> >>> > > I don't think this setting should be enabled by default if it might
> >>> > > cause this type of breakage, even if it ends up being a driver
> >>> > > problem.
> >> > 
> >> > This is the first report on this behavior.
> >> > From your logs, it shows that when switched to battery, nothing is set
> >> > correct. Neither the speed, nor the Link.
> >> > 
> >> > Could you please set DEBUG=1 in the ethernet module only, and then see
> >> > if it can provide more information on what is failing?
> >> > 
> >> > e1000e must be a common driver supporting multiple Intel chipsets. I
> >> > have no problem setting the default to 0, but like I said, this is the
> >> > first time I've heard of this behavior.
> > I've tracked it further down to «ethtool -s eth0 autoneg off», which
> > totally messes up the network device. I've tested this with 3.2, 3.3
> > and 3.4 kernels, all are affected. I'll try to check later on with
> > earlier kernels to see if something changes.

Turning off autonegotiation is a totally fucking stupid thing to do.
But, that said, both the above reports have it turned on.

(The right thing to do is leave autonegotiation on but only advertise
the speed you want.  Also, coming soon to ethtool: Energy Efficient
Ethernet settings.)

> > It might be related to the PCIe controller, ACPI setup, the PM settings,
> > or the driver itself, I've got some error messages on dmesg about the
> > driver being unable to read from PHY registers and also about Hardware
> > Errors, but then I've seen several instances of that on google, so I
> > don't think it's really a hardware problem, as those have changed over
> > time with different kernels.
> 
> Since this happens with 3.2 also, I have pulled in the kernel team.
> Perhaps they have some information.

I rarely use wired networking on my lap

Re: Linux features for wheezy

2012-06-16 Thread Julien Cristau
On Sat, Jun 16, 2012 at 14:16:46 +0200, Sven Joachim wrote:

> Should we upload xserver-xorg-video-nouveau to unstable and wait for
> complaints?  The version in sid is unusable anyway[1] :-/, so breaking
> acceleration for some users might not be such a big deal.
> 
Yes, that's kind of what I'm thinking.  Let's do that.

Cheers,
Julien


-- 
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/20120616121856.gi12...@radis.cristau.org



Re: Linux features for wheezy

2012-06-16 Thread Sven Joachim
On 2012-06-04 20:42 +0200, Julien Cristau wrote:

> On Sat, Jun  2, 2012 at 23:47:03 +0100, Ben Hutchings wrote:
>
>> Some hardware support; this can still be done after the freeze but the
>> sooner the better:
>> 
>> - [armhf] omapdrm driver
>> - [x86] gma500 support for new chips
>> - [x86] i915 improvements in Ivy Bridge support
>> - radeon support for new chips
>> - NVMe driver
>> - tg3 support for 57766 chip
>> - ipheth support for iPhone 4S
>> - DRM/KMS driver for DisplayLink
>> - qmi_wwan driver (#670241)
>> 
> We'll probably also need some nouveau updates to (at least) update to
> the 1.0.0 ABI,

See commit ace77b6b1304 in xserver-xorg-video-nouveau for the reason:

--8<---cut here---start->8---
commit ace77b6b1304826f4004bde23809b55d476b0615
Author: Ben Skeggs 
Date:   Tue May 29 21:21:57 2012 +1000

disable fermi accel on 0.0.16 interface

Kepler accel support broke some assumption made by the older kernel
interface, and Fermi shares the same code.  It can't work (without
some annoying hacks anyway) with the 0.0.16 kernel anymore.

diff --git a/src/nv_dma.c b/src/nv_dma.c
index 3b75ca9..1757f4d 100644
--- a/src/nv_dma.c
+++ b/src/nv_dma.c
@@ -36,6 +36,12 @@ NVInitDma(ScrnInfoPtr pScrn)
int size, ret;
void *data;
 
+   if (pNv->dev->drm_version < 0x0100 && pNv->dev->chipset >= 0xc0) {
+   xf86DrvMsg(pScrn->scrnIndex, X_ERROR,
+  "Fermi acceleration not supported on old kernel\n");
+   return FALSE;
+   }
+
if (pNv->Architecture < NV_ARCH_C0) {
data = &nv04_data;
size = sizeof(nv04_data);
--8<---cut here---end--->8---

> I haven't had time to look at this at all, but I think
> Maarten had a backport at
> http://people.canonical.com/~mlankhorst/drm-abi-patches.tgz

Note that this is actually an uncompressed tar archive.

I wonder what happens if, during the wheezy+1 release cycle, the Nouveau
DDX or the mesa driver starts depending on other features present in
Linux 3.4 but not in Maarten's patchset.

> but doesn't have the hw to test them.

We need someone with a Fermi card that is supported (i.e. there is
working microcode) by Linux 3.2.

Should we upload xserver-xorg-video-nouveau to unstable and wait for
complaints?  The version in sid is unusable anyway[1] :-/, so breaking
acceleration for some users might not be such a big deal.

Cheers,
   Sven


1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675161


-- 
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/87aa03bgep@turtle.gmx.de



Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD

2012-06-16 Thread Thomas Schwinge
Hi!

After many others that played with no problems, I just tried playing
Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly
up-to-date Debian GNU/Linux testing system.

$ uname -a
Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 
GNU/Linux

... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.

While "loading" the CD in Rhythmbox, after a few seconds the kernel
crashed.  I rebooted, tried again, and it crashed again.  At
 you
can find the panic message (low resolution, sorry), pointing to the
SCSI/ATA code.

Are there any such known issues?  Does the panic message give any clue
already, or would you want me to reproduce that with debugging symbols,
etc.?


Grüße,
 Thomas


pgpt7m0FZdY6X.pgp
Description: PGP signature


Processed: Re: 3.2.19-1: after some time, the USB keyboard no longer works

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 677173 src:linux 3.2.20-1
Bug #677173 [linux-2.6] linux-image-3.2.0-2-amd64: after some time, the USB 
keyboard no longer works
Bug reassigned from package 'linux-2.6' to 'src:linux'.
No longer marked as found in versions 3.2.19-1 and 3.2.20-1.
Ignoring request to alter fixed versions of bug #677173 to the same values 
previously set
Bug #677173 [src:linux] linux-image-3.2.0-2-amd64: after some time, the USB 
keyboard no longer works
Marked as found in versions linux/3.2.20-1.
> found 677173 linux-2.6/3.2.19-1
Bug #677173 [src:linux] linux-image-3.2.0-2-amd64: after some time, the USB 
keyboard no longer works
Marked as found in versions linux-2.6/3.2.19-1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
677173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677173
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.13398409029275.transcr...@bugs.debian.org



Re: Bug#677638: laptop-mode-tools: Breaks wired network when running on battery

2012-06-16 Thread Ritesh Raj Sarraf
Added Ben and the Debian Kernel Team


On Saturday 16 June 2012 07:29 AM, Guillem Jover wrote:
>> On Friday 15 June 2012 09:27 PM, Guillem Jover wrote:
>>> > > Since some time now (I only sat down to track it down pretty recently,
>>> > > but this has going on for probably a year or more), laptop-mode-tools
>>> > > has broken the wired network (e1000e) whenever I unplug the laptop from
>>> > > the wall power.
>>> > >
>>> > > The culprit is BATT_THROTTLE_ETHERNET=1 in
>>> > > «/etc/laptop-mode/conf.d/ethernet.conf».
>>> > >
>>> > > This turns the working ethernet device from this state:
>>> > >
>>> > > ,---
>>> > > # ethtool eth0
>>> > > Settings for eth0:
>>> > > Supported ports: [ TP ]
>>> > > Supported link modes:   10baseT/Half 10ba
>>> > > 100baseT/Half 100baseT/Full
>>> > > 1000baseT/Full 
>>> > > Supported pause frame use: No
>>> > > Supports auto-negotiation: Yes
>>> > > Advertised link modes:  10baseT/Half 10ba
>>> > > 100baseT/Half 100baseT/Full
>>> > > 1000baseT/Full 
>>> > > Advertised pause frame use: No
>>> > > Advertised auto-negotiation: Yes
>>> > > Speed: 100Mb/s
>>> > > Duplex: Full
>>> > > Port: Twisted Pair
>>> > > PHYAD: 2
>>> > > Transceiver: internal
>>> > > Auto-negotiation: on
>>> > > MDI-X: on
>>> > > Supports Wake-on: pumbg
>>> > > Wake-on: g
>>> > > Current message level: 0x0001 (1)
>>> > >drv
>>> > > Link detected: yes
>>> > > `---
>>> > >
>>> > > To this non-working state:
>>> > >
>>> > > ,---
>>> > > # ethtool eth0
>>> > > Settings for eth0:
>>> > > Supported ports: [ TP ]
>>> > > Supported link modes:   10baseT/Half 10ba
>>> > > 100baseT/Half 100baseT/Full
>>> > > 1000baseT/Full 
>>> > > Supported pause frame use: No
>>> > > Supports auto-negotiation: Yes
>>> > > Advertised link modes:  10baseT/Half 10ba
>>> > > 100baseT/Half 100baseT/Full
>>> > > 1000baseT/Full 
>>> > > Advertised pause frame use: No
>>> > > Advertised auto-negotiation: Yes
>>> > > Speed: Unknown!
>>> > > Duplex: Unknown! (255)
>>> > > Port: Twisted Pair
>>> > > PHYAD: 2
>>> > > Transceiver: internal
>>> > > Auto-negotiation: on
>>> > > MDI-X: Unknown
>>> > > Supports Wake-on: pumbg
>>> > > Wake-on: d
>>> > > Current message level: 0x0001 (1)
>>> > >drv
>>> > > Link detected: no
>>> > > `---
>>> > >
>>> > > If I set BATT_THROTTLE_ETHERNET to 0, then everything works as before.
>>> > >
>>> > > I don't think this setting should be enabled by default if it might
>>> > > cause this type of breakage, even if it ends up being a driver
>>> > > problem.
>> > 
>> > This is the first report on this behavior.
>> > From your logs, it shows that when switched to battery, nothing is set
>> > correct. Neither the speed, nor the Link.
>> > 
>> > Could you please set DEBUG=1 in the ethernet module only, and then see
>> > if it can provide more information on what is failing?
>> > 
>> > e1000e must be a common driver supporting multiple Intel chipsets. I
>> > have no problem setting the default to 0, but like I said, this is the
>> > first time I've heard of this behavior.
> I've tracked it further down to «ethtool -s eth0 autoneg off», which
> totally messes up the network device. I've tested this with 3.2, 3.3
> and 3.4 kernels, all are affected. I'll try to check later on with
> earlier kernels to see if something changes.
> 
> It might be related to the PCIe controller, ACPI setup, the PM settings,
> or the driver itself, I've got some error messages on dmesg about the
> driver being unable to read from PHY registers and also about Hardware
> Errors, but then I've seen several instances of that on google, so I
> don't think it's really a hardware problem, as those have changed over
> time with different kernels.

Since this happens with 3.2 also, I have pulled in the kernel team.
Perhaps they have some information.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System



signature.asc
Description: OpenPGP digital signature


Processed: Re: 3.2.19-1: after some time, the USB keyboard no longer works

2012-06-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 677173 3.2.20-1
Bug #677173 [linux-2.6] linux-image-3.2.0-2-amd64: after some time, the USB 
keyboard no longer works
There is no source info for the package 'linux-2.6' at version '3.2.20-1' with 
architecture ''
Unable to make a source version for version '3.2.20-1'
Marked as found in versions 3.2.20-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
677173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677173
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.133983802926030.transcr...@bugs.debian.org



Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

2012-06-16 Thread Vincent Lefevre
found 677173 3.2.20-1
thanks

Hi,

This has just occurred again with 3.2.20-1.

On 2012-06-13 00:33:16 -0500, Jonathan Nieder wrote:
> I assume the X log does not say anything interesting, either, and

No, nothing in the X log.

> that even after switching to a VT the keyboard does not work when
> this happens?

I haven't tried (I'll try next time, as I can switch to a VT from the
laptop keyboard). I doubt there is anything specific to X, though (in
particular since the laptop keyboard still works while the USB keyboard
doesn't).

> Since I'm out of ideas and I can't think of any Debian-specific
> patch that would be relevant, I'd suggest contacting
> linux-in...@vger.kernel.org for hints.  They might be able to help you
> get a trace with usbmon (of Documentation/usb/usbmon.txt fame), for
> example.

I'll do that.

Thanks,

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



--
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/20120616091254.ge4...@xvii.vinc17.org



Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d

2012-06-16 Thread Jonathan Nieder
Martin-Éric Racine wrote:

> Yup, this issue returns every now and then on the exact same host
> (which was recently migrated from Ubuntu to Debian, now that Ubuntu
> stopped supporting anything older than non-PAE 686 hardware), whenever
> someone touches the inode code again. The nice thing, this time, is
> that it has become non-fatal; the kernel simply reports the oops and
> continues operating.

Thanks for the background.  That would have indeed been useful context
in the original report (though perhaps it had been long enough since
the last appearance that you had forgotten).

If I have any more questions, I'll ask them upstream.

Thanks,
Jonathan



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



Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d

2012-06-16 Thread Martin-Éric Racine
2012/6/16 Ben Hutchings :
> On Fri, 2012-06-15 at 22:37 +0300, Martin-Éric Racine wrote:
>> Hi Jonathan,
>>
>> 2012/6/15 Jonathan Nieder :
>> > Hi Martin-Éric,
>> >
>> > Martin-Éric Racine wrote:
>> >
>> >> I'm not sure if it's too early to report on kernel 3.4 or not, but
>> >> here it goes:
>> >
>> > Any package uploaded to the archive is open for bug reports. :)
>> >
>> > Could you send the full "oops" trace, starting at the first BUG line?
>> > (It should include the text "Not tainted".)  Even better would be full
>> > "dmesg" output from booting and reproducing the bug.
>>
>> Here's the dmesg output at bootup, right after the first few oopses
>> have started to appear.
>
> The kernel is trying to free an inode and using an ACL pointer that
> should presumably be 0x (special value for ACL not in memory)
> but is instead 0xb4ff.  This memory corruption could be a software
> bug (e.g. use after free) or a hardware fault.
>
> What was the last working kernel version on this system?

3.2.0-19 (or whatever 486 kernel is in Testing) is what's normally
running on this one.



--
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/capzxpqcn42h4ypn_xghz4cvhxvdazhbtanpkksvxjnzanv1...@mail.gmail.com



Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d

2012-06-16 Thread Martin-Éric Racine
2012/6/16 Jonathan Nieder :
> Jonathan Nieder wrote:
>
>> By the way, searching for that particular address yields the following
>> interesting result.  (Nothing else recent, alas.)
>
> Better link:
>
>  https://bugzilla.kernel.org/show_bug.cgi?id=13941

Yup, this issue returns every now and then on the exact same host
(which was recently migrated from Ubuntu to Debian, now that Ubuntu
stopped supporting anything older than non-PAE 686 hardware), whenever
someone touches the inode code again. The nice thing, this time, is
that it has become non-fatal; the kernel simply reports the oops and
continues operating.



--
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/CAPZXPQcsOE=E_KNsbfu_0Vfm4Q00+7xD=U+bP_3H941gJs�q...@mail.gmail.com



Bug#677164: [3.2.17-1 -> 3.2.18-1 regression] Wacom tablet in Thinkpad x220t not working

2012-06-16 Thread Jonathan Nieder
Hi Nils,

Nils Kanning wrote:

> 0001:
>
> The tablet does not work, see also dmesg_0001. I had to press ctrl+c
> during booting at [12.00] and lsusb -t gives
> 1-1.3:1.0: No such file or directory
> (and then hangs)

This is 0024 from the earlier list:

  f393ee2b814e Input: wacom - retrieve maximum number of touch points
   from the HID usage table when it is supported

I'll look at it more closely.  (Probably I introduced a bug while
backporting it.)

> 0002:
>
> I could not apply the patch:

Are you trying to apply this patch alone or on top of 0001?  Only the
latter is supposed to work.

[...]
> "Sometimes" this configuration really works. But most of the times it
> does not and I have to press ctrl+c at [12.00] (see
> dmesg_20-24_fail). Again lsusb -t gives
> 1-1.3:1.0: No such file or directory
> (and hangs)
>
> (I'm sorry for "sometimes" and "most of the times" ...)

No, thanks much for these details.  It's very helpful.

[...]
> [2.961552] Linux video capture interface: v2.00
> [2.962940] [ cut here ]
> [2.962988] kernel BUG at mm/slab.c:505!
> [2.963036] invalid opcode:  [#1] SMP 
> [2.963157] CPU 2 
> [2.963195] Modules linked in: videobuf2_core videodev media 
> ghash_clmulni_intel(+) cdc_acm(+) cdc_ncm(+) cdc_wdm wacom(+) usbnet 
> snd_seq_midi mii aesni_intel aes_x86_64 aes_generic cryptd snd_seq_midi_event 
> snd_rawmidi snd_seq microcode(+) snd_seq_device snd_timer i915(+) iwlwifi 
> drm_kms_helper psmouse snd drm mac80211 tpm_tis i2c_i801 serio_raw pcspkr 
> evdev iTCO_wdt tpm i2c_algo_bit acpi_cpufreq iTCO_vendor_support cfg80211 ac 
> i2c_core soundcore mperf rfkill wmi tpm_bios battery power_supply video 
> button processor ext4 crc16 jbd2 mbcache usbhid hid sd_mod crc_t10dif ahci 
> libahci libata ehci_hcd scsi_mod thermal thermal_sys e1000e usbcore sdhci_pci 
> sdhci mmc_core usb_common [last unloaded: scsi_wait_scan]
> [2.965891] 
> [2.965932] Pid: 579, comm: modprobe Not tainted 3.4.2-amd64 #1 LENOVO 
> 42992QG/42992QG
> [2.966079] RIP: 0010:[]  [] 
> virt_to_cache+0x1b/0x23
> [2.966193] RSP: :88021204fcf8  EFLAGS: 00010046
> [2.966251] RAX: ea00073a6800 RBX: 880210b0020c RCX: 
> 040b
> [2.966312] RDX: 0200 RSI: 880211e11c80 RDI: 
> 880210b0020c
> [2.966375] RBP: 0286 R08: 88021204e000 R09: 
> 002e
> [2.966435] R10: 7fffcdeb8770 R11: 88020fcf0c40 R12: 
> a04029cd
> [2.966497] R13: 005a R14: 0001 R15: 
> 88020ec71c00
> [2.966560] FS:  7ff356606700() GS:88021e28() 
> knlGS:
> [2.966631] CS:  0010 DS:  ES:  CR0: 8005003b
> [2.966686] CR2: 00403228 CR3: 0002127d4000 CR4: 
> 000407e0
> [2.966743] DR0:  DR1:  DR2: 
> 
> [2.966801] DR3:  DR6: 0ff0 DR7: 
> 0400
> [2.966860] Process modprobe (pid: 579, threadinfo 88021204e000, task 
> 8802111e36d0)
> [2.966933] Stack:
> [2.966990]  88021204e000 810ef84e  
> 880210b4b080
> [2.967214]  880210011400 a04029cd 880210011400 
> 88020165
> [2.967433]  88021388 0202 88020002 
> 88020fce0800
> [2.967657] Call Trace:
> [2.967713]  [] ? kfree+0x50/0x6c
> [2.967775]  [] ? wacom_probe+0x52c/0x957 [wacom]
> [2.967845]  [] ? usb_probe_interface+0xf2/0x15d 
> [usbcore]

That's

BUG_ON(!PageSlab(page))

in page_get_cache() and represents a free of an invalid pointer (for
example a double free).  Thanks again.  More tomorrow.

Good night,
Jonathan



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