Bug#661860: Further Information

[Soren Stoutner]

I have some further information on this bug.

I compiled the out-of-tree vender driver available from
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8188CUS

and have been running it for the past several weeks.  This seemed to resolve 
the first problem listed in the original bug report:

1.  The adapter will periodically list no networks available.

It decreased the frequency of the second problem.

2.  The adapter will periodically list all network as having full signal 
strength (when they don't) but refuse to connect to any network.

Specifically, the it is less likely for distant networks to display with full 
signal strength.  However, it still had problems connecting to some networks, 
usually if the access point is more than 25 feet away.  It had no impact on 
signal strength, which remains much worse than the same hardware in Windows.

The third problem occurred once in the past two weeks, which is much less 
often then the daily occurrence with the kernel driver.

3.  After being connected to the network for 5-10 minutes, the adapter will 
suddenly disconnect and refuse to reconnect until rebooted.  This is often 
coupled with they symptoms listed in #2.

It continued to have the fourth problem, which is that after the plugging in 
the EDIMAX EW-7811, removing it and plugging in a HorneTek HT-H5DN8191 causes 
a kernel panic.

So the overall takeaway is that switching to the out-of-tree driver improves 
the situation, but there are still significant, mostly intermittent problems.  
It does not improve signal strength at all, which for some reason is much 
worse than in Windows.


-- 
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net
www.smallbusinesstech.net


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

Processing of linux-2.6_2.6.32-41squeeze2_multi.changes

[Debian FTP Masters]

linux-2.6_2.6.32-41squeeze2_multi.changes uploaded successfully to localhost
along with the files:
  linux-2.6_2.6.32-41squeeze2.dsc
  linux-2.6_2.6.32-41squeeze2.diff.gz
  linux-doc-2.6.32_2.6.32-41squeeze2_all.deb
  linux-manual-2.6.32_2.6.32-41squeeze2_all.deb
  linux-patch-debian-2.6.32_2.6.32-41squeeze2_all.deb
  linux-source-2.6.32_2.6.32-41squeeze2_all.deb
  linux-support-2.6.32-5_2.6.32-41squeeze2_all.deb
  firmware-linux-free_2.6.32-41squeeze2_all.deb
  linux-base_2.6.32-41squeeze2_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/e1scixl-gv...@franck.debian.org

linux-2.6_2.6.32-41squeeze2_i386.changes REJECTED

[Debian FTP Masters]

Reject Reasons:
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-all-i386_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-amd64_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(xen-linux-system-2.6.32-5-xen-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-xen-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-vserver-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-686-bigmem_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-openvz-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-686-bigmem_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-openvz-686-dbg_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-common-openvz_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-486_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-amd64_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-openvz-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-common_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-vserver-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-tools-2.6.32_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-486_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-common-xen_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-common-vserver_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-xen-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-xen-686-dbg_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-libc-dev_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-686_2.6.32-41squeeze2_i386.deb).
no source found for linux-2.6 2.6.32-41squeeze2 
(linux-headers-2.6.32-5-all_2.6.32-41squeeze2_i386.deb).

Notes:
Mapping stable-security to proposed-updates.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


-- 
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/e1scixb-dx...@franck.debian.org

Processing of linux-2.6_2.6.32-41squeeze2_i386.changes

[Debian FTP Masters]

linux-2.6_2.6.32-41squeeze2_i386.changes uploaded successfully to localhost
along with the files:
  linux-image-2.6.32-5-486_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-486_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-686_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-686_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-686-bigmem_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-686-bigmem_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-amd64_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-amd64_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-common_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-openvz-686_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-openvz-686-dbg_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-openvz-686_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-common-openvz_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-all_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-all-i386_2.6.32-41squeeze2_i386.deb
  linux-libc-dev_2.6.32-41squeeze2_i386.deb
  linux-tools-2.6.32_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-vserver-686_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-vserver-686_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-common-vserver_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-xen-686_2.6.32-41squeeze2_i386.deb
  linux-image-2.6.32-5-xen-686-dbg_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-xen-686_2.6.32-41squeeze2_i386.deb
  xen-linux-system-2.6.32-5-xen-686_2.6.32-41squeeze2_i386.deb
  linux-headers-2.6.32-5-common-xen_2.6.32-41squeeze2_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/e1scisz-ih...@franck.debian.org

Bug#665881: [3.1 -> 3.2.12 regression] module ath5k is blocking wlan-card

[Jonathan Nieder]

Hans-J. Ullrich wrote:
> Am Montag, 26. März 2012 schrieben Sie:

>>  - can you reproduce this without using wicd?  i.e.
>>
>>  install iw and iproute
>>  stop wicd
>>  ip link set wlan0 up
>>  iw dev wlan0 connect -w  key d:0:
>>  dhclient wlan0
>>
>>with
>>
>>  iw event -t
>>
>>running in another terminal to see if anything interesting happens.
>
> Yes, same problem without wicd! My system is configured, that I also can run 
> it 
> without wicd, but I am using wicd as it is more comfortable. But wicd indeed 
> is not really necessary. 

Does the event log say anything interesting?

What's most puzzling to me is that some people started experiencing
similar symptoms with 3.3-rc1 (and the regression range was reliable
and even bisectable).  Which is of course newer than the kernel you
are using.

If you can get full "dmesg" output from booting up and triggering the
problem, that would be useful.

Thanks again for the quick response, and sorry for the trouble.
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/20120326212701.GJ7599@burratino

Bug#665881: [3.1 -> 3.2.12 regression] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Montag, 26. März 2012 schrieben Sie:
> found 665881 linux-2.6/3.2.12-1
> quit
> 
> Hi Hans,
> 
Hi Jonathan,

> Hans wrote:
> > Package: linux-2.6
> > Severity: important
> 
> Thanks.  Please specify a version number next time.
> 
It is 3.2.0-2-amd64.

> [...]
> 
> > [  175.461616] ath5k phy0: gain calibration timeout (2462MHz)
> > [  175.462671] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> 
> Interesting.  I'd never seen this message before, but a search of
> the linux-wireless yielded some hits.
> 
> No great ideas from me.  So:
> 
>  - please boot without the virtualbox drivers to rule them out as
>a cause
> 

I did, but I got no success.

>  - does unloading the acer_wmi driver help?  (I wouldn't expect it
>to, but it seems worth a check.)
> 

No, it does not help.

>  - is "rfkill list" output as expected?
> 

This is the output: 

rfkill list
2: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no


Seems ok for me.

>  - you mentioned that with some earlier 3.2.y kernel you had similar
>problems, though there was a workaround.  May I assume that
>earlier kernels worked fine?  Of the kernels listed at
>, which is the
>newest version that works without problems?
> 

Yes, with kernel 3.1.X everything went fine. I did not downgrade at the moment, 
as I need this machine all the time and can not do much experiences during the 
day.

>  - please file a separate bug for the laptop with different hardware.
> 

Yes, I will do, when this problem is fixed and is still on the other machine. I 
just wanted to mention it, as it might also be, there is still a problem 
besides of ath5k.

>  - does this always happen right away or only in some circumstances?
>(e.g., after a suspend/resume)
> 

The problem is always happening.

>  - can you reproduce this without using wicd?  i.e.
> 
>   install iw and iproute
>   stop wicd
>   ip link set wlan0 up
>   iw dev wlan0 connect -w  key d:0:
>   dhclient wlan0
> 
>with
> 
>   iw event -t
> 
>running in another terminal to see if anything interesting happens.
> 


Yes, same problem without wicd! My system is configured, that I also can run it 
without wicd, but I am using wicd as it is more comfortable. But wicd indeed 
is not really necessary. 

> Vaguely reminiscent of https://bugzilla.kernel.org/show_bug.cgi?id=16436
> but that bug has a different regression range which makes it not a great
> match.  So I look forward to some clues to narrow this down.
> 
I checked the bugreport, and yes, those error messages are very similar to 
mine, except mine are starting at boot time. So the reason for my bug can not 
be powermanagement (I think)

> Hope that helps,
> Jonathan

I hope it, too. :))

Hans





--
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/201203262242.58579.hans.ullr...@loop.de

Bug#665881: [3.1 -> 3.2.12 regression] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Montag, 26. März 2012 schrieben Sie:
> Hans-J. Ullrich wrote:
> > It is 3.2.0-2-amd64.
> 
> Thanks.  Did you mean this to be a private reply?
> 

Oops, no it was a mistake by me. Sent it again, please don't wonder.
> To save a round-trip: the above is just a part of the package name
> rather than its version number.  You can get the version number of
> the installed kernel with
> 
>   dpkg-query -W linux-image-$(uname -r)

dpkg-query: Warnung: Parsen der Datei »/var/lib/dpkg/available«, nahe Zeile 
614272 Paket »cnews«:
 Fehler in Versionszeichenkette »cr.g7-40.4«: Versionsnummer beginnt nicht mit 
einer Ziffer
linux-image-3.2.0-2-amd64   3.2.12-1


> 
> and of the running kernel by looking for the string in parentheses in
> 
>   cat /proc/version
> 
> output.

Sorry!

Hans




--
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/201203262244.59242.hans.ullr...@loop.de

Processed: Re: [3.1 -> 3.2.12 regression] module ath5k is blocking wlan-card

[Debian Bug Tracking System]

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

> found 665881 linux-2.6/3.2.12-1
Bug #665881 [linux-2.6] linux-image-3.2.0-2-amd64: module ath5k is blocking 
wlan-card
Marked as found in versions linux-2.6/3.2.12-1.
> quit
Stopping processing here.

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

Bug#665881: [3.1 -> 3.2.12 regression] module ath5k is blocking wlan-card

[Jonathan Nieder]

found 665881 linux-2.6/3.2.12-1
quit

Hi Hans,

Hans wrote:

> Package: linux-2.6
> Severity: important

Thanks.  Please specify a version number next time.

[...]
> [  175.461616] ath5k phy0: gain calibration timeout (2462MHz)
> [  175.462671] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Interesting.  I'd never seen this message before, but a search of
the linux-wireless yielded some hits.

No great ideas from me.  So:

 - please boot without the virtualbox drivers to rule them out as
   a cause

 - does unloading the acer_wmi driver help?  (I wouldn't expect it
   to, but it seems worth a check.)

 - is "rfkill list" output as expected?

 - you mentioned that with some earlier 3.2.y kernel you had similar
   problems, though there was a workaround.  May I assume that
   earlier kernels worked fine?  Of the kernels listed at
   , which is the
   newest version that works without problems?

 - please file a separate bug for the laptop with different hardware.

 - does this always happen right away or only in some circumstances?
   (e.g., after a suspend/resume)

 - can you reproduce this without using wicd?  i.e.

install iw and iproute
stop wicd
ip link set wlan0 up
iw dev wlan0 connect -w  key d:0:
dhclient wlan0

   with

iw event -t

   running in another terminal to see if anything interesting happens.

Vaguely reminiscent of https://bugzilla.kernel.org/show_bug.cgi?id=16436
but that bug has a different regression range which makes it not a great
match.  So I look forward to some clues to narrow this down.

Hope that helps,
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/20120326200250.GH7599@burratino

linux-tools_3.3-1~experimental.1_multi.changes ACCEPTED into experimental

[Debian FTP Masters]

Accepted:
linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
  to main/l/linux-tools/linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
linux-tools-3.3_3.3-1~experimental.1_i386.deb
  to main/l/linux-tools/linux-tools-3.3_3.3-1~experimental.1_i386.deb
linux-tools_3.3-1~experimental.1.debian.tar.gz
  to main/l/linux-tools/linux-tools_3.3-1~experimental.1.debian.tar.gz
linux-tools_3.3-1~experimental.1.dsc
  to main/l/linux-tools/linux-tools_3.3-1~experimental.1.dsc
linux-tools_3.3.orig.tar.gz
  to main/l/linux-tools/linux-tools_3.3.orig.tar.gz


Changes:
linux-tools (3.3-1~experimental.1) experimental; urgency=low
 .
  * New upstream release candidate
  * linux-kbuild: debian/control: Set Multi-Arch: foreign
  * linux-tools: Build perf on alpha and hppa (Closes: #664834)


Override entries for your package:
linux-kbuild-3.3_3.3-1~experimental.1_i386.deb - optional devel
linux-tools-3.3_3.3-1~experimental.1_i386.deb - optional devel
linux-tools_3.3-1~experimental.1.dsc - source devel

Announcing to debian-experimental-chan...@lists.debian.org
Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 664834 


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/e1scft3-0001g3...@franck.debian.org

Bug#665881: linux-image-3.2.0-2-amd64: module ath5k is blocking wlan-card

[Hans]

Package: linux-2.6
Severity: important

Dear Maintainers,

I am running debian/testing. After a kernel update (3.1.0 -> 3.2.0) I cannot 
get any wireless connection now. First of all, I thought, it was wicd, but 
it looks like kernel module ath5k is the problem. As you can see in the log, 
ath5k is spamming the log with a lot of 
calibration errors. Unloading ath5k is stopping these, reloading it let them 
appear again. 

Everything began with a chnage to a 3.2.0-kernel. A prior version of the 3.2.0 
kernel (I believe it was 3.2.0-1-amd64) let
me get access to the wlan-hardware, when I shutdown the notebook and put it 10 
seconds completely from power. Then wireless 
worked as usual. A reboot did not solve the problem, after a reboot, wlan did 
not work again because the hardware was blocked.
I had to put power off again.

With the latest kernel, this trick does not work any more. Oh, and I checked my 
hardware with a livefile linux (knoppix), everything
is working fine with it.

Just a hint: I am using another netbook, which is using the newer kernel module 
"ath9k", which is the successor of ath5k.
On this netbook I get a similar problem, which might be caused by the same 
reason: wicd cannot be initialised, ath9k is loaded, 
but after a few seconds suddenly everything is working again. I think, this is 
a problem by ath9k, as it appears at the same time, I 
changed the kernel version.

I also downgraded to a prior version of wicd, to exclude, that the problem is 
caused by wicd - with no success.
So I think, the problem is indeed caused by the kernel (or its module 
ath5k/ath9k). 

You shall know, I am using still WEP, but that should not matter, as there are 
no accesspoints seen at all.
The device "wlan0" is existent (ifconfig is showing me), I see an IP address of 
it, but ping to the gateway is 
getting no response. 

Well, I hope, I gave you enough information. Below you see all my hardware 
information. This time I followed your advice, to 
put the message above the log! Sorry, for the last time, when I put it below.
 
Please feel free to ask for any further information. Any help is very 
apreciated.

Kind regards

Hans-J. Ullrich   


-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.12-1) (debian-kernel@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Tue Mar 20 18:36:37 UTC 2012

** Command line:
root=UUID=f2f57267-0289-412c-9f9b-e8702e8b7010 ro quiet vga=791

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

** Kernel log:
[  175.461616] ath5k phy0: gain calibration timeout (2462MHz)
[  175.462671] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  190.960145] usb 3-1: USB disconnect, device number 3
[  192.560051] usb 3-1: new low-speed USB device number 4 using ohci_hcd
[  192.772077] usb 3-1: New USB device found, idVendor=093a, idProduct=2510
[  192.772226] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  192.772373] usb 3-1: Product: USB OPTICAL MOUSE
[  192.772465] usb 3-1: Manufacturer: PIXART
[  192.785879] input: PIXART USB OPTICAL MOUSE as 
/devices/pci:00/:00:02.0/usb3/3-1/3-1:1.0/input/input16
[  192.786708] generic-usb 0003:093A:2510.0003: input,hidraw0: USB HID v1.11 
Mouse [PIXART USB OPTICAL MOUSE] on usb-:00:02.0-1/input0
[  222.805639] vboxpci: IOMMU not found (not registered)
[  223.597826] ath5k phy0: gain calibration timeout (2412MHz)
[  224.086320] ath5k phy0: gain calibration timeout (2417MHz)
[  224.580417] ath5k phy0: gain calibration timeout (2422MHz)
[  225.062294] ath5k phy0: gain calibration timeout (2427MHz)
[  225.545978] ath5k phy0: gain calibration timeout (2432MHz)
[  226.030884] ath5k phy0: gain calibration timeout (2437MHz)
[  226.514112] ath5k phy0: gain calibration timeout (2442MHz)
[  226.998787] ath5k phy0: gain calibration timeout (2447MHz)
[  227.486546] ath5k phy0: gain calibration timeout (2452MHz)
[  227.979644] ath5k phy0: gain calibration timeout (2457MHz)
[  229.405832] net_ratelimit: 2 callbacks suppressed
[  229.408114] ath5k phy0: gain calibration timeout (2472MHz)
[  229.858757] ath5k phy0: gain calibration timeout (2462MHz)
[  231.090546] ath5k phy0: gain calibration timeout (2412MHz)
[  231.577707] ath5k phy0: gain calibration timeout (2417MHz)
[  232.071690] ath5k phy0: gain calibration timeout (2422MHz)
[  232.175223] forcedeth :00:0a.0: eth0: link down
[  232.557712] ath5k phy0: gain calibration timeout (2427MHz)
[  232.562684] forcedeth :00:0a.0: eth0: link down
[  233.045454] ath5k phy0: gain calibration timeout (2432MHz)
[  233.374515] ehci_hcd :00:02.1: PCI INT B disabled
[  233.377040] ehci_hcd :00:02.1: PME# enabled
[  233.392312] ohci_hcd :00:04.0: PCI INT A disabled
[  233.394584] ohci_hcd :00:04.0: PME# enabled
[  233.408286] ehci_hcd :00:04.1: PCI INT B disabled
[  233.410488] ehci_hcd :00:04.1: PME# enabled
[  233.529885] ath5k phy0: gain calibration timeout (2437MHz)
[  23

Processed: found 647741 in 3.2.12-1

[Debian Bug Tracking System]

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

> found 647741 3.2.12-1
Bug #647741 [linux-2.6] linux-image-3.0.0-2-amd64: UI sometimes freezes for 
several seconds, with a disk access
There is no source info for the package 'linux-2.6' at version '3.2.12-1' with 
architecture ''
Unable to make a source version for version '3.2.12-1'
Marked as found in versions 3.2.12-1.
> thanks
Stopping processing here.

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

Bug#664834: marked as done (linux-tools: please build perf utils on Alpha.)

[Debian Bug Tracking System]

Your message dated Mon, 26 Mar 2012 19:20:37 +
with message-id 
and subject line Bug#664834: fixed in linux-tools 3.3-1~experimental.1
has caused the Debian Bug report #664834,
regarding linux-tools: please build perf utils on Alpha.
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.)


-- 
664834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-tools
Version: 3.2.7-2
Severity: wishlist
User: debian-al...@lists.debian.org
Usertags: alpha
X-Debbugs-CC: debian-al...@lists.debian.org

Could we have the perf tools built on Alpha please.  For some reason
they are not in the linux-tools package, whereas they are for other
arches.  Performance hardware event support for EV67/68 CPUs is in the
kernel and it would be nice to be able to use the perf tools on those
CPUs.  FWIW, I did do a "make" within the tools/perf directory of the
source package and the tools built successfully.

Thanks,
Michael.


--- End Message ---
--- Begin Message ---
Source: linux-tools
Source-Version: 3.3-1~experimental.1

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

linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
  to main/l/linux-tools/linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
linux-tools-3.3_3.3-1~experimental.1_i386.deb
  to main/l/linux-tools/linux-tools-3.3_3.3-1~experimental.1_i386.deb
linux-tools_3.3-1~experimental.1.debian.tar.gz
  to main/l/linux-tools/linux-tools_3.3-1~experimental.1.debian.tar.gz
linux-tools_3.3-1~experimental.1.dsc
  to main/l/linux-tools/linux-tools_3.3-1~experimental.1.dsc
linux-tools_3.3.orig.tar.gz
  to main/l/linux-tools/linux-tools_3.3.orig.tar.gz



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 664...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Mar 2012 23:15:59 +
Source: linux-tools
Binary: linux-kbuild-3.3 linux-tools-3.3
Architecture: i386 source
Version: 3.3-1~experimental.1
Distribution: experimental
Urgency: low
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 664834
Description: 
 linux-kbuild-3.3 - Kbuild infrastructure for Linux 3.3
 linux-tools-3.3 - Performance analysis tools for Linux 3.3
Changes: 
 linux-tools (3.3-1~experimental.1) experimental; urgency=low
 .
   * New upstream release candidate
   * linux-kbuild: debian/control: Set Multi-Arch: foreign
   * linux-tools: Build perf on alpha and hppa (Closes: #664834)
Checksums-Sha1: 
 83e62fee6dfef6cdb4c1e4da3f0393213aecbb29 2220 
linux-tools_3.3-1~experimental.1.dsc
 7049f6cb591ed4c7fdc8f92cef5c5f5f3d927fd9 9269881 linux-tools_3.3.orig.tar.gz
 02b721594622779e960660394fcf5642773088d3 18043 
linux-tools_3.3-1~experimental.1.debian.tar.gz
 7e6722d447fb09239bfa7cb852772b15715bb2c7 233810 
linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
 79de57ab735c035966b99b5f196761b4f88d4903 401750 
linux-tools-3.3_3.3-1~experimental.1_i386.deb
Checksums-Sha256: 
 b4868402203cb2a6395ac548d76750e9d4c6e84e554969f43338087e624aaa6f 2220 
linux-tools_3.3-1~experimental.1.dsc
 5672446f7312b63ed21ed58f8a7e705dba1524072d6317f02f1bcdb52981598d 9269881 
linux-tools_3.3.orig.tar.gz
 51718f965fa6bde5dfad87ab818f78181db2dcde4778ddbb88575de1bb962bfc 18043 
linux-tools_3.3-1~experimental.1.debian.tar.gz
 a9e61c96f2e8db1aeba4296e25a1b5842f4535625bba998a8c5bb842319864ba 233810 
linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
 47b1b2a6e2d00a003ba3c7bc34be3e89e5adf0547958c2d32352ba3a35bf 401750 
linux-tools-3.3_3.3-1~experimental.1_i386.deb
Files: 
 d2e0e638f0c9e56fd249582b05c492a4 2220 devel optional 
linux-tools_3.3-1~experimental.1.dsc
 69f0550e56ceb33677d06928102b78b9 9269881 devel optional 
linux-tools_3.3.orig.tar.gz
 b0b85069b53cac11bdfb8e1b68af6683 18043 devel optional 
linux-tools_3.3-1~experimental.1.debian.tar.gz
 3d2347172a14a8ad754c437bd53a5d1a 233810 devel optional 
linux-kbuild-3.3_3.3-1~experimental.1_i386.deb
 17ee0ed14880de806999456896f2ec4e 401750 devel optional 
linux-tools-3.3_3.3-1~experimental.1_i386.deb

-BE

Processed: Re: lvcreate: sending ioctl 1261 to a partition!

[Debian Bug Tracking System]

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

> # apparently I can't spell.  Thanks to the BTS for catching it.
> merge 656899 665850
Bug #656899 [src:linux-2.6] mdadm: sending ioctl 1261 to a partition warnings 
in kernel log with kernel 3.2
Bug #665850 [src:linux-2.6] lvcreate: sending ioctl 1261 to a partition!
Marked as found in versions linux-2.6/2.6.32-41 and linux-2.6/3.2.1-1.
Added tag(s) upstream and confirmed.
Bug #656899 [src:linux-2.6] mdadm: sending ioctl 1261 to a partition warnings 
in kernel log with kernel 3.2
Marked as found in versions linux-2.6/2.6.26-29.
Merged 656899 665850
> tags 656899 + pending
Bug #656899 [src:linux-2.6] mdadm: sending ioctl 1261 to a partition warnings 
in kernel log with kernel 3.2
Bug #665850 [src:linux-2.6] lvcreate: sending ioctl 1261 to a partition!
Added tag(s) pending.
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#659378: the nouveau driver does not work at all with my machine (information about resolution of the problem)

[Jonathan Nieder]

Panayiotis Karabassis wrote:
> On 03/26/2012 12:57 PM, Jonathan Nieder wrote:
>> Panayiotis Karabassis wrote:

>>> that I purged the nvidia driver and removed my /etc/X11/xorg.conf. I
>>> attach the problematic xorg.conf.
>>
>> Nice.  If you make this file /etc/X11/xorg.conf again, do you get
>> the same problems again?
>
> Do you mean make it with Xorg -configure?

What I meant to ask is if you can reproduce the old problem, for
example by downgrading the kernel using a version from
http://snapshot.debian.org/ or by putting some appropriate incantation
in xorg.conf.  If you can't, then I'm fine with just closing this and
letting it remain a mystery for now.

What is your current kernel version?  (/proc/version should say, in
parentheses after the word "Debian".)  What other upgrades happened
between the non-working state and the working state?  (/var/log/dpkg.log*
or the aptitude or APT logs might help in determining that.)

[...]
> BTW, since glxinfo outputs Direct rendering: yes and the nouveau module
> is listed in lsmod, that confirms that the nouveau driver is in use, right?

I am using the fbdev driver now and have "direct rendering: yes".  See
http://dri.freedesktop.org/wiki/glxinfo for what this means.

The easiest way to see what xorg video driver you are using is probably

grep _drv /var/log/Xorg.0.log

> One more thing, when I turned on the screen today (already running
> system), there was some graphic corruption: black areas that went on and
> off, and I had to restart the xserver.

If you can reproduce this new problem, then a report would be valuable
(against xserver-xorg-video-nouveau or xserver-xorg-video-fbdev to
start, presumably).

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/20120326174412.GD7599@burratino

Processed (with 2 errors): Re: lvcreate: sending ioctl 1261 to a partition!

[Debian Bug Tracking System]

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

> severity 665850 minor
Bug #665850 [linux-2.6] lvcreate: sending ioctl 1261 to a partition!
Severity set to 'minor' from 'normal'
> reassign 665850 src:linux-2.6 2.6.26-29
Bug #665850 [linux-2.6] lvcreate: sending ioctl 1261 to a partition!
Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'.
No longer marked as found in versions 2.6.26-29.
Ignoring request to alter fixed versions of bug #665850 to the same values 
previously set
Bug #665850 [src:linux-2.6] lvcreate: sending ioctl 1261 to a partition!
Marked as found in versions linux-2.6/2.6.26-29.
> merge 656788 665850
Bug #656788 [pdns-server] pdns: bind backend patch to handle smallcaps RRs
Unable to merge bugs because:
severity of #665850 is 'minor' not 'normal'
package of #665850 is 'src:linux-2.6' not 'pdns-server'
Failed to merge 656788: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2104880)', 
'requester', 'Jonathan Nieder ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<20120326171013.GC7599@burratino>', 'request_subject', ...) called at 
/usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871

> # * Add longterm release 2.6.32.56, including:
> tags 656788 + pending
Failed to alter tags of Bug 656788: failed to get lock on 
/org/bugs.debian.org/spool/lock/656788 -- Unable to lock 
/org/bugs.debian.org/spool/lock/656788 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579.
Unable to lock /org/bugs.debian.org/spool/lock/656788 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 579. at 
/usr/local/lib/site_perl/Debbugs/Common.pm line 597
Debbugs::Common::filelock('/org/bugs.debian.org/spool/lock/656788') 
called at /usr/local/lib/site_perl/Debbugs/Status.pm line 209
Debbugs::Status::read_bug('bug', 656788, 'lock', 1) called at 
/usr/local/lib/site_perl/Debbugs/Status.pm line 464
Debbugs::Status::lock_read_all_merged_bugs('bug', 656788) called at 
/usr/local/lib/site_perl/Debbugs/Control.pm line 3604
Debbugs::Control::__begin_control('remove', 0, 'add', 1, 
'request_replyto', 'Jonathan Nieder ', 'transcript', 
'GLOB(0x2104880)', 'bug', ...) called at 
/usr/local/lib/site_perl/Debbugs/Control.pm line 623
Debbugs::Control::set_tag('transcript', 'GLOB(0x2104880)', 'requester', 
'Jonathan Nieder ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<20120326171013.GC7599@burratino>', 'request_subject', ...) called at 
/usr/lib/debbugs/service line 812
eval {...} called at /usr/lib/debbugs/service line 805

> quit
Stopping processing here.

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

Bug#665850: lvcreate: sending ioctl 1261 to a partition!

[Jonathan Nieder]

severity 665850 minor
reassign 665850 src:linux-2.6 2.6.26-29
merge 656788 665850
# * Add longterm release 2.6.32.56, including:
tags 656788 + pending
quit

Hi Ross,

Ross Boylan wrote:

> Aside from the noise there doesn't seem to be a problem.  If anyone
> can confirm this is harmless, I'd love to know it (and it would be
> fine to downgrade severity in that case).

Yep, it's cosmetic.

[...]
> Possibly related to
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656899

These are the same problem and due to the same patch.  I believe it
is fixed by

 v3.3-rc1~60 ("dm: do not forward ioctls from logical volumes to the
 underlying device", 2012-01-12)

which is part of v3.2.2 (hence current sid kernels) and upstream
v2.6.32.56 (hence the next squeeze kernel).  Confirmation would be
welcome.

Sorry for the regression.

Sincerely,
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/20120326171013.GC7599@burratino

Processed: Re: patch for bug #661558: kernel oops when adding a bitmap to a raid1 md device

[Debian Bug Tracking System]

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

> # regression
> severity 661558 important
Bug #661558 [linux-2.6] linux-image-3.2.0-1-amd64: kernel oops when adding a 
bitmap to a raid1 md device
Severity set to 'important' from 'normal'
> quit
Stopping processing here.

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

Bug#661558: patch for bug #661558: kernel oops when adding a bitmap to a raid1 md device

[Jonathan Nieder]

# regression
severity 661558 important
quit

Hi Flavio,

Flavio Stanchina wrote:

> Here's a patch from Neil Brown that fixes this bug:

Quick update: the patches in question

  4474ca42e257 md/bitmap: ensure to load bitmap when creating via sysfs
  c744a65c1e2d md: don't set md arrays to readonly on shutdown

have been applied upstream and queued for inclusion in 3.2.14 and 3.3.1.
The former is only relevant in >= 2.6.35 kernels, while the latter
might also need to be applied to squeeze (it's not clear to me from a
quick glance).

Thanks for the pointers. 

Sincerely,
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/20120326164641.GA15269@burratino

[bts-link] source package linux-2.6

[bts-link-upstream]

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

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

# remote status report for #632734 (http://bugs.debian.org/632734)
# Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
#  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
#  * remote status changed: NEEDINFO -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 632734 + fixed-upstream
usertags 632734 - status-NEEDINFO
usertags 632734 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #632734 (http://bugs.debian.org/632734)
# Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
#  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
#  * remote status changed: NEEDINFO -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 632734 + fixed-upstream
usertags 632734 - status-NEEDINFO
usertags 632734 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #632734 (http://bugs.debian.org/632734)
# Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
#  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
#  * remote status changed: NEEDINFO -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 632734 + fixed-upstream
usertags 632734 - status-NEEDINFO
usertags 632734 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #632734 (http://bugs.debian.org/632734)
# Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
#  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
#  * remote status changed: NEEDINFO -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 632734 + fixed-upstream
usertags 632734 - status-NEEDINFO
usertags 632734 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #649304 (http://bugs.debian.org/649304)
# Bug title: linux-image-3.1.0-1-686-pae:  needed for 
686-pae kernels
#  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
#  * remote status changed: NEEDINFO -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 649304 + fixed-upstream
usertags 649304 - status-NEEDINFO
usertags 649304 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #661558 (http://bugs.debian.org/661558)
# Bug title: linux-image-3.2.0-1-amd64: kernel oops when adding a bitmap to a 
raid1 md device
#  * http://bugzilla.kernel.org/show_bug.cgi?id=42954
#  * remote status changed: NEEDINFO -> RESOLVED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 661558 + fixed-upstream
usertags 661558 - status-NEEDINFO
usertags 661558 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE

# remote status report for #659363 (http://bugs.debian.org/659363)
# Bug title: Hibernate freezes on HP dc7900 with Linux 3.2 (regression)
#  * https://bugzilla.redhat.com/show_bug.cgi?id=785384
#  * remote status changed: (?) -> ASSIGNED
usertags 659363 + status-ASSIGNED

thanks


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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #632734 (http://bugs.debian.org/632734)
> # Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in 
> syslog
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
> #  * remote status changed: NEEDINFO -> RESOLVED
> #  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
> #  * closed upstream
> tags 632734 + fixed-upstream
Bug #632734 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel boots but OOPs 
found in syslog
Bug #627019 [linux-2.6] linux-image-2.6.39-rc7-686-pae: several kernel hangs 
before geting to login
Bug #630031 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel boots, but dmesg 
contains kernel bug trace
Bug #631597 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel fails to boot 
after reboot
Bug #649304 [linux-2.6] linux-image-3.1.0-1-686-pae:  needed 
for 686-pae kernels
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 632734 - status-NEEDINFO
Bug#632734: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
Usertags were: status-NEEDINFO.
Usertags are now: .
> usertags 632734 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE
Bug#632734: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
There were no usertags set.
Usertags are now: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
> # remote status report for #632734 (http://bugs.debian.org/632734)
> # Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in 
> syslog
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
> #  * remote status changed: NEEDINFO -> RESOLVED
> #  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
> #  * closed upstream
> tags 632734 + fixed-upstream
Bug #632734 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel boots but OOPs 
found in syslog
Bug #627019 [linux-2.6] linux-image-2.6.39-rc7-686-pae: several kernel hangs 
before geting to login
Bug #630031 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel boots, but dmesg 
contains kernel bug trace
Bug #631597 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel fails to boot 
after reboot
Bug #649304 [linux-2.6] linux-image-3.1.0-1-686-pae:  needed 
for 686-pae kernels
Ignoring request to alter tags of bug #632734 to the same tags previously set
Ignoring request to alter tags of bug #627019 to the same tags previously set
Ignoring request to alter tags of bug #630031 to the same tags previously set
Ignoring request to alter tags of bug #631597 to the same tags previously set
Ignoring request to alter tags of bug #649304 to the same tags previously set
> usertags 632734 - status-NEEDINFO
Bug#632734: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
Usertags were: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
Usertags are now: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
> usertags 632734 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE
Bug#632734: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
Usertags were: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
Usertags are now: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
> # remote status report for #632734 (http://bugs.debian.org/632734)
> # Bug title: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in 
> syslog
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=38262
> #  * remote status changed: NEEDINFO -> RESOLVED
> #  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
> #  * closed upstream
> tags 632734 + fixed-upstream
Bug #632734 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel boots but OOPs 
found in syslog
Bug #627019 [linux-2.6] linux-image-2.6.39-rc7-686-pae: several kernel hangs 
before geting to login
Bug #630031 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel boots, but dmesg 
contains kernel bug trace
Bug #631597 [linux-2.6] linux-image-2.6.39-2-686-pae: Kernel fails to boot 
after reboot
Bug #649304 [linux-2.6] linux-image-3.1.0-1-686-pae:  needed 
for 686-pae kernels
Ignoring request to alter tags of bug #632734 to the same tags previously set
Ignoring request to alter tags of bug #627019 to the same tags previously set
Ignoring request to alter tags of bug #630031 to the same tags previously set
Ignoring request to alter tags of bug #631597 to the same tags previously set
Ignoring request to alter tags of bug #649304 to the same tags previously set
> usertags 632734 - status-NEEDINFO
Bug#632734: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
Usertags were: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE.
Usertags are now: status-RESO

Bug#665850: lvcreate: sending ioctl 1261 to a partition!

[Ross Boylan]

Package: linux-2.6
Version: 2.6.26-29
Severity: normal

Since I applied the following updates

[UPGRADE] base-files 5lenny10 -> 5lenny11
[UPGRADE] libapr1 1.2.12-5+lenny4 -> 1.2.12-5+lenny5
[UPGRADE] libapr1-dev 1.2.12-5+lenny4 -> 1.2.12-5+lenny5
[UPGRADE] libpq-dev 8.3.16-0lenny1 -> 8.3.17-0lenny1
[UPGRADE] libpq5 8.3.16-0lenny1 -> 8.3.17-0lenny1
[UPGRADE] linux-headers-2.6.26-2-686 2.6.26-27 -> 2.6.26-29
[UPGRADE] linux-headers-2.6.26-2-common 2.6.26-27 -> 2.6.26-29
[UPGRADE] linux-image-2.6.26-2-686 2.6.26-27 -> 2.6.26-29
[UPGRADE] linux-libc-dev 2.6.26-27 -> 2.6.26-29
# also postgres and xpdf

I get many messages
lvcreate: sending ioctl 1261 to a partition!
when I create snapshots each night.  I have rebooted since the
upgrade.  I create 7 snapshots, 2 of which are encrypted.

Aside from the noise there doesn't seem to be a problem.  If anyone
can confirm this is harmless, I'd love to know it (and it would be
fine to downgrade severity in that case).

Other possible causes: I may have extended an lvm partition on the
same day the messages started; perhaps if the extension went to a new
disk it could trigger some lvm bug.  But the volume of messages
suggests every snapshot is affected, and no previous extension has
caused trouble.  Also, I'm running a Debian testing chroot.  Since the
errors are clearly associated with the snapshots on the host system,
this also seems unlikely.  This bug reports, the snapshotting, and the
logs are all from the host.

Possibly related to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656899 and
https://bugzilla.kernel.org/show_bug.cgi?id=42694.  Both of those are
3.2 kernels, but the upgrade presumably had some backported fixes.


Key parts of snapshot script:
/sbin/lvcreate -L400M -s -n root2_raw_snap daisy/root2_raw
/sbin/cryptsetup --key-file key00 luksOpen /dev/daisy/root2_raw_snap root2_snap
/bin/mkdir -p /snap/
/bin/mount /dev/mapper/root2_snap /snap/
/sbin/lvcreate -L5G -s -n home_snap daisy/home
/bin/mkdir -p /snap/home
/bin/mount /dev/mapper/daisy-home_snap /snap/home
/sbin/lvcreate -L2G -s -n usr_snap daisy/usr
/bin/mkdir -p /snap/usr
/bin/mount /dev/mapper/daisy-usr_snap /snap/usr
/sbin/lvcreate -L10G -s -n var_snap daisy/var
/bin/mkdir -p /snap/var
/bin/mount /dev/mapper/daisy-var_snap /snap/var
/sbin/lvcreate -L3G -s -n local_snap daisy/local
/bin/mkdir -p /snap/usr/local
/bin/mount /dev/mapper/daisy-local_snap /snap/usr/local
/sbin/lvcreate -L100M -s -n cyrlib_snap daisy/cyrlib
/bin/mkdir -p /snap/var/lib/cyrus
/bin/mount /dev/mapper/daisy-cyrlib_snap /snap/var/lib/cyrus
/sbin/lvcreate -L16G -s -n cyrspool3_raw_snap daisy/cyrspool3_raw
/sbin/cryptsetup --key-file key01 luksOpen /dev/daisy/cyrspool3_raw_snap 
cyrspool3_snap
/bin/mkdir -p /snap/var/spool/cyrus
/bin/mount /dev/mapper/cyrspool3_snap /snap/var/spool/cyrus

-- Package-specific info:
** Version:
Linux version 2.6.26-2-686 (Debian 2.6.26-29) (da...@debian.org) (gcc version 
4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Sun Mar 4 22:19:19 UTC 
2012

** Command line:
root=/dev/mapper/root2 ro vga=0x346 rootdelay=30 

** Tainted: P (1)
 * Proprietary module has been loaded.
** Kernel log:
[553181.841955] ext3_orphan_cleanup: deleting unreferenced inode 79957
[553181.848309] ext3_orphan_cleanup: deleting unreferenced inode 79958
[553181.848718] ext3_orphan_cleanup: deleting unreferenced inode 79959
[553181.848718] ext3_orphan_cleanup: deleting unreferenced inode 79956
[553181.848718] ext3_orphan_cleanup: deleting unreferenced inode 79951
[553181.854463] ext3_orphan_cleanup: deleting unreferenced inode 79954
[553181.859315] ext3_orphan_cleanup: deleting unreferenced inode 79975
[553181.859346] ext3_orphan_cleanup: deleting unreferenced inode 79974
[553181.860658] ext3_orphan_cleanup: deleting unreferenced inode 79972
[553181.860719] ext3_orphan_cleanup: deleting unreferenced inode 79968
[553181.860719] ext3_orphan_cleanup: deleting unreferenced inode 79967
[553181.860719] ext3_orphan_cleanup: deleting unreferenced inode 79900
[553181.860719] ext3_orphan_cleanup: deleting unreferenced inode 79952
[553181.860719] ext3_orphan_cleanup: deleting unreferenced inode 79949
[553181.860719] ext3_orphan_cleanup: deleting unreferenced inode 80033
[553181.871834] ext3_orphan_cleanup: deleting unreferenced inode 80032
[553181.872718] ext3_orphan_cleanup: deleting unreferenced inode 80031
[553181.872718] ext3_orphan_cleanup: deleting unreferenced inode 80047
[553181.872718] ext3_orphan_cleanup: deleting unreferenced inode 80046
[553181.872718] ext3_orphan_cleanup: deleting unreferenced inode 80045
[553181.872718] ext3_orphan_cleanup: deleting unreferenced inode 80044
[553181.872718] ext3_orphan_cleanup: deleting unreferenced inode 80043
[553181.872831] ext3_orphan_cleanup: deleting unreferenced inode 80042
[553181.872867] ext3_orphan_cleanup: deleting unreferenced inode 80041
[553181.872903] ext3_orphan_cleanup: deleting unreferenced inode 80040
[553181.872939] ext3_orphan_cleanup: deleting unreferenced inod

Bug#665835: linux-image-3.2.0-1-amd64: copying huge file to a slow USB flash disk stalls the system

[Michal Suchanek]

Package: linux-2.6
Version: 3.2.6-1
Severity: normal


Hello,

I was trying to copy an iso image to a rather lame Emgeton brand USB
stick (using factory FAT format on the stick).

While doing so after some time most applications become unresponsive.

I can log in on the console, local xterms work, xscreensaver and window
manager works, xterms showing remote session and firefox are stalled (no
screen updates), and so is gkrellm and kvm.

I don't see anything releavant in the log.

The load on the system as shown with atop is very light except for the
flash drive which is 100% busy.


-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.2-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Wed Feb 1 08:56:58 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 
root=UUID=3b8f6a64-5899-462a-aec0-6ddefd878ecf ro fbcon=rotate:3 quiet

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

** Kernel log:
[4140240.021049] usb 3-2.1: New USB device strings: Mfr=1, Product=3, 
SerialNumber=0
[4140240.021052] usb 3-2.1: Product: USB Productivity Option Keyboard( has the 
hub in # 1 )
[4140240.021054] usb 3-2.1: Manufacturer: Lite-On Technology
[4140240.031290] input: Lite-On Technology USB Productivity Option Keyboard( 
has the hub in # 1 ) as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.0/input/input892
[4140240.031446] generic-usb 0003:04B3:301B.037B: input,hidraw0: USB HID v1.10 
Keyboard [Lite-On Technology USB Productivity Option Keyboard( has the hub in # 
1 )] on usb-:00:1a.0-2.1/input0
[4140240.036094] input: Lite-On Technology USB Productivity Option Keyboard( 
has the hub in # 1 ) as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.1/input/input893
[4140240.036200] generic-usb 0003:04B3:301B.037C: input,hidraw1: USB HID v1.10 
Device [Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 
)] on usb-:00:1a.0-2.1/input1
[4140240.109047] usb 3-2.2: new low-speed USB device number 92 using uhci_hcd
[4140240.247043] usb 3-2.2: New USB device found, idVendor=046d, idProduct=c063
[4140240.247047] usb 3-2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[4140240.247050] usb 3-2.2: Product: DELL USB Laser Mouse
[4140240.247053] usb 3-2.2: Manufacturer: DELL
[4140240.265276] input: DELL DELL USB Laser Mouse as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.2/3-2.2:1.0/input/input894
[4140240.265476] generic-usb 0003:046D:C063.037D: input,hidraw2: USB HID v1.10 
Mouse [DELL DELL USB Laser Mouse] on usb-:00:1a.0-2.2/input0
[4140272.360038] usb 3-2: USB disconnect, device number 90
[4140272.360042] usb 3-2.1: USB disconnect, device number 91
[4140272.492114] usb 3-2.2: USB disconnect, device number 92
[4140272.832021] usb 3-2: new full-speed USB device number 93 using uhci_hcd
[4140272.992050] usb 3-2: unable to read config index 0 descriptor/all
[4140272.992056] usb 3-2: can't read configurations, error -71
[4140273.048043] hub 3-0:1.0: unable to enumerate USB device on port 2
[4140273.584026] usb 3-2: new full-speed USB device number 95 using uhci_hcd
[4140273.648041] hub 3-0:1.0: unable to enumerate USB device on port 2
[4140274.128014] usb 3-2: new full-speed USB device number 96 using uhci_hcd
[4140274.305051] usb 3-2: New USB device found, idVendor=04b3, idProduct=301a
[4140274.305054] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[4140274.305056] usb 3-2: Product: USB 1.1 2port downstream low power hub
[4140274.305058] usb 3-2: Manufacturer: Lite-On Technology
[4140274.313073] hub 3-2:1.0: USB hub found
[4140274.314047] hub 3-2:1.0: 3 ports detected
[4140274.593055] usb 3-2.1: new full-speed USB device number 97 using uhci_hcd
[4140274.741051] usb 3-2.1: New USB device found, idVendor=04b3, idProduct=301b
[4140274.741055] usb 3-2.1: New USB device strings: Mfr=1, Product=3, 
SerialNumber=0
[4140274.741058] usb 3-2.1: Product: USB Productivity Option Keyboard( has the 
hub in # 1 )
[4140274.741061] usb 3-2.1: Manufacturer: Lite-On Technology
[4140274.751301] input: Lite-On Technology USB Productivity Option Keyboard( 
has the hub in # 1 ) as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.0/input/input895
[4140274.751460] generic-usb 0003:04B3:301B.037E: input,hidraw0: USB HID v1.10 
Keyboard [Lite-On Technology USB Productivity Option Keyboard( has the hub in # 
1 )] on usb-:00:1a.0-2.1/input0
[4140274.756110] input: Lite-On Technology USB Productivity Option Keyboard( 
has the hub in # 1 ) as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.1/input/input896
[4140274.756202] generic-usb 0003:04B3:301B.037F: input,hidraw1: USB HID v1.10 
Device [Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 
)] on usb-:00:1a.0-2.1/input1
[4140274.829056] usb 3-2.2: new low-speed USB device number 98 using uhci_hcd
[4140274.967050] usb 3-2.2: New USB device found, idVendor=046d, idProduct=c063
[4140274.967054] usb 3-2.2: New USB device

Bug#659378: the nouveau driver does not work at all with my machine (configurations work)

[Panayiotis Karabassis]

Hey,

Some more information, both the xorg.conf I attached and the one
generated by Xorg (without any changes) work, except that the one I
attached starts the Xserver in a very low resolution. The situation is
the same under Xen, i.e. it works.

On 03/26/2012 01:17 PM, Panayiotis Karabassis wrote:
> On 03/26/2012 12:57 PM, Jonathan Nieder wrote:
>> Panayiotis Karabassis wrote:
>>> On 03/26/2012 02:36 AM, Jonathan Nieder wrote:
  What kernel are you using these days?  What
 kernel-side graphics driver?  What userspace graphics stack?
>>> It is the latest kernel in Wheezy 3.2.0-2-amd64. It is the nouveau
>>> driver, and gnome-shell that are working together.
>>>
 Do you know how the issue got resolved?
>>> I am not sure if it is the updates that got this working, or the fact
>>> that I purged the nvidia driver and removed my /etc/X11/xorg.conf. I
>>> attach the problematic xorg.conf.
>> Nice.  If you make this file /etc/X11/xorg.conf again, do you get
>> the same problems again?
> 
> Do you mean make it with Xorg -configure? It creates three Device
> sections, with nouveau, visa and fbdev drivers, three Monitor sections,
> and three Screen sections. If I remove fbdev and visa, with the
> corresponding Monitor and Screen sections, the xserver does not start.
> When I get home, I will test whether it is the existence of the file
> alone that causes the xserver not to start. I will also test again with
> the xorg.conf I sent you, just in case.
> 
> BTW, since glxinfo outputs Direct rendering: yes and the nouveau module
> is listed in lsmod, that confirms that the nouveau driver is in use, right?
> 
> One more thing, when I turned on the screen today (already running
> system), there was some graphic corruption: black areas that went on and
> off, and I had to restart the xserver.
> 
>> Thanks for the update.
>> Jonathan
> Thanks,
> Panayiotis


-- 
Best regards,
Panayiotis Karabassis



-- 
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/4f706cd2.3060...@gmail.com

Bug#659378: the nouveau driver does not work at all with my machine (information about resolution of the problem)

[Panayiotis Karabassis]

On 03/26/2012 12:57 PM, Jonathan Nieder wrote:
> Panayiotis Karabassis wrote:
>> On 03/26/2012 02:36 AM, Jonathan Nieder wrote:
>>>  What kernel are you using these days?  What
>>> kernel-side graphics driver?  What userspace graphics stack?
>> It is the latest kernel in Wheezy 3.2.0-2-amd64. It is the nouveau
>> driver, and gnome-shell that are working together.
>>
>>> Do you know how the issue got resolved?
>> I am not sure if it is the updates that got this working, or the fact
>> that I purged the nvidia driver and removed my /etc/X11/xorg.conf. I
>> attach the problematic xorg.conf.
> Nice.  If you make this file /etc/X11/xorg.conf again, do you get
> the same problems again?

Do you mean make it with Xorg -configure? It creates three Device
sections, with nouveau, visa and fbdev drivers, three Monitor sections,
and three Screen sections. If I remove fbdev and visa, with the
corresponding Monitor and Screen sections, the xserver does not start.
When I get home, I will test whether it is the existence of the file
alone that causes the xserver not to start. I will also test again with
the xorg.conf I sent you, just in case.

BTW, since glxinfo outputs Direct rendering: yes and the nouveau module
is listed in lsmod, that confirms that the nouveau driver is in use, right?

One more thing, when I turned on the screen today (already running
system), there was some graphic corruption: black areas that went on and
off, and I had to restart the xserver.

> Thanks for the update.
> Jonathan
Thanks,
Panayiotis



-- 
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/4f70422c.6070...@gmail.com

Bug#659378: the nouveau driver does not work at all with my machine (information about resolution of the problem)

[Jonathan Nieder]

Panayiotis Karabassis wrote:
> On 03/26/2012 02:36 AM, Jonathan Nieder wrote:

>>  What kernel are you using these days?  What
>> kernel-side graphics driver?  What userspace graphics stack?
>
> It is the latest kernel in Wheezy 3.2.0-2-amd64. It is the nouveau
> driver, and gnome-shell that are working together.
>
>> Do you know how the issue got resolved?
>
> I am not sure if it is the updates that got this working, or the fact
> that I purged the nvidia driver and removed my /etc/X11/xorg.conf. I
> attach the problematic xorg.conf.

Nice.  If you make this file /etc/X11/xorg.conf again, do you get
the same problems again?

Thanks for the update.
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/20120326095702.GB7599@burratino

Bug#659378: the nouveau driver does not work at all with my machine (information about resolution of the problem)

[Panayiotis Karabassis]

On 03/26/2012 02:36 AM, Jonathan Nieder wrote:
> Hi,
>
> Panayiotis Karabassis wrote:
>
>> [Subject: Bug#659378: issue resolved]
> Please keep in mind that this appears as email in a crowded inbox,
> so the subject link can be a good place to put valuable context.
>
>> This issue is resolved for me.
> The body, too. ;-)
You are right, sorry, I was lazy. :-)
>  What kernel are you using these days?  What
> kernel-side graphics driver?  What userspace graphics stack?
It is the latest kernel in Wheezy 3.2.0-2-amd64. It is the nouveau
driver, and gnome-shell that are working together.
> Do you know how the issue got resolved?
I am not sure if it is the updates that got this working, or the fact
that I purged the nvidia driver and removed my /etc/X11/xorg.conf. I
attach the problematic xorg.conf.
>   Since this is a
> bug tracker rather than a support forum, that would be valuable
> information to us so we can ensure squeeze has the same fix if
> needed and that we do not introduce regressions in the future.
>
> Thanks for the update,
> Jonathan
Let me know if you need more information.

Thanks,
Panayiotis
Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0"
EndSection

Section "Extensions"
Option "Composite" "enable"
EndSection

Section "Files"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "Unknown"
HorizSync   28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nouveau"
VendorName "NVIDIA Corporation"
BoardName  "GeForce GT 440"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
SubSection "Display"
Depth   24
EndSubSection
EndSection

Bug#658728: patch_realtek: no more sound on HP Compaq dx2200 MT

[Jonathan Nieder]

A. Costa wrote:
> Jonathan Nieder  wrote:

>> The "Auto-Mute Mode" setting persists across reboots...
>
> Aha, I'd (mistakenly) believed the opposite.  Does an "Auto-Mute Mode" 
> setting also persist between kernel upgrades?

Yes, as long as both kernels offer the control.

>> ...See /etc/init.d/alsa-utils for details.
>
> OK, so where does that init script store its persistent 'mute' mode
> state?  That's what should be compared between kernels and bootups I'd
> suppose.

Sure, but that mechanism works, so it has nothing to do with this bug.
;-)

Here are two ways to check whether the patch_realtek bug is fixed.
Either one is sufficient.

 A. Check if the "auto-mute mode" control is offered by alsamixer -c0.
In a working kernel, if it is offered, then it should have the
following effect:

 - if auto-mute mode is disabled, sound is output to speakers
   regardless of whether headphones are plugged in

 - if auto-mute mode is enabled, sound is output to speakers if
   and only if headphones are not plugged in

If it is not offered, then sound should be output to speakers
if and only if headphones are not plugged in, just as though
the auto-mute mode control were offered and set to "on".

 B. Check if rebooting from a broken kernel to the current one cures
the silent output.  That is:

1. Boot a broken kernel and enable the "auto-mute mode" control,
   so output is inappropriately suppressed.

2. Boot into the kernel to be tested.  If output is still silent
   regardless of the "alsamixer -c0" volume control setting, it
   is broken.  If output is present, it is fixed.

Thanks for your help,
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/20120326070358.GA7599@burratino