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

[Jonathan Nieder]

Hi,

A. Costa wrote:

> Hmm.  Recheck with 3.2.0-1.  Reboot with that...
>
>   % cat /proc/version 
>   Linux version 3.2.0-1-686-pae (Debian 3.2.7-1) 
> (debian-kernel@lists.debian.org) (gcc version 4.6.2 (Debian 4.6.2-14) ) #1 
> SMP Wed Feb 29 01:18:56 UTC 2012
>
> No, sound works there too.

Sure, but is the auto-mute mode control shown by "amixer -c0
controls", and is sound suppressed even with no headphones plugged in
when auto-mute is enabled?  (If so, then the bug is still present.  If
you are wondering why the results are different from before, see
alsactl(1).)



-- 
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/20120317052051.GA16428@burratino

Processed: Re: linux-2.6: Tell reportbug to use src:linux-2.6

[Debian Bug Tracking System]

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

> severity 644198 wishlist
Bug #644198 [src:linux-2.6] linux-2.6: Tell reportbug to use src:linux-2.6
Severity set to 'wishlist' from 'normal'
> found 644198 linux-2.6/3.2.10-1
Bug #644198 [src:linux-2.6] linux-2.6: Tell reportbug to use src:linux-2.6
Marked as found in versions linux-2.6/3.2.10-1.
> tags 644198 + moreinfo
Bug #644198 [src:linux-2.6] linux-2.6: Tell reportbug to use src:linux-2.6
Added tag(s) moreinfo.
> quit
Stopping processing here.

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

Bug#644198: linux-2.6: Tell reportbug to use src:linux-2.6

[Jonathan Nieder]

severity 644198 wishlist
found 644198 linux-2.6/3.2.10-1
tags 644198 + moreinfo
quit

Hi,

Kurt Roeckx wrote:

> Can you please chang the bug control file to use:
> Submit-As: src:linux-2.6
> instead of the current:
> Submit-As: linux-2.6

What would be the benefit?  Any downsides?

Curious,
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/20120317002700.GA524@burratino

Bug#587538: marked as done (lshw is provoking a system crash on a sun sparc T1000 machine)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2012 19:21:46 -0500
with message-id <20120317002146.GA465@burratino>
and subject line Re: lshw is provoking a system crash on a sun sparc T1000 
machine
has caused the Debian Bug report #587538,
regarding lshw is provoking a system crash on a sun sparc T1000 machine
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.)


-- 
587538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lshw
Version: 02.13-2
Severity: Critical

When I invoke lshw on a sunfire T1000 machine the system crashes and
it drops to the {ok} prompt.

machine:~# lshw
[  646.549492] SUN4V-DTLB: Error at TPC[f7d08134], tl 1
[  646.549676] SUN4V-DTLB: TPC<0xf7d0813c>
[  646.549776] SUN4V-DTLB: O7[31de0]
[  646.549870] SUN4V-DTLB: O7<0x31de8>
[  646.549966] SUN4V-DTLB: vaddr[f7f4c000] ctx[bc1]
pte[980e0610] error[2]
Program terminated
{1} ok
{1} ok

Here is some more information about the system:

machine:~# uname -a
Linux machine 2.6.26-2-sparc64-smp #1 SMP Wed May 12 21:24:38 UTC 2010
sparc64 GNU/Linux

machine:~# cat /etc/debian_version
5.0.4

Will provide you with more info on demand.

Best,
Ivaylo Ganchev


--- End Message ---
--- Begin Message ---
Jonathan Nieder wrote:
> Ivaylo Ganchev wrote:

>> When I invoke lshw on a sunfire T1000 machine the system crashes and
>> it drops to the {ok} prompt.
>
> That's no good.  Could you find out what system call is causing this,
> using strace?

Closing due to lack of response, but if you get more information on
this we'd be happy to revisit it.

--- End Message ---

Bug#586029: udev: 3ware 8006 RAID controller gets a new controller, ID on each reboot

[Jonathan Nieder]

More details from private correspondence:

etch - bug not present
squeeze - bug present
2.6.37 - bug not present
3.0 - bug present
later versions - who knows?  But presumably they alternate. :)

So as you suggested the real bug might be in udev or elsewhere.



-- 
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/20120317001907.GC325@burratino

Processed: Re: udev: 3ware 8006 RAID controller gets a new controller, ID on each reboot

[Debian Bug Tracking System]

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

> tags 586029 = unreproducible
Bug #586029 [linux-2.6] udev: 3ware 8006 RAID controller gets a new controller 
ID on each reboot
Added tag(s) unreproducible; removed tag(s) moreinfo.
> quit
Stopping processing here.

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

Bug#586029: udev: 3ware 8006 RAID controller gets a new controller, ID on each reboot

[Jonathan Nieder]

tags 586029 = unreproducible
quit

Jonathan Nieder wrote:

> I guess some more basic questions are warranted before spending time
> on it:
>
>  - do you still have access to this hardware?

Oh, now I remember.  The answer was "no"[1]. :)

Sorry for the noise.  Marking accordingly so I don't forget again.
Jonathan

[1] private reply



-- 
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/20120317001421.GB325@burratino

Bug#586133: Boot process pauses indefinitely waiting for keyboard activity

[Jonathan Nieder]

Jonathan Nieder wrote:
> Bob Freemer wrote:

>> The kernel pauses waiting for any keyboard input early* in the boot
>> process.
>
> Is your keyboard connected by USB, PS/2, or some other port?  (Well,
> the relevant thing is probably that it triggers an interrupt, but it
> can't hurt to ask anyway.)
>
>> * The pause first happens after the following lines in the kernel log:
>> [1.352116] usb 1-2: new high speed USB device using ehci_hcd and address 
>> 3
>> [1.372150] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
>> [1.372206] usb usb7: New USB device strings: Mfr=3, Product=2, 
>> SerialNumber=1
>> [1.372270] usb usb7: Product: OHCI Host Controller
>> [1.372323] usb usb7: Manufacturer: Linux 2.6.32-5-amd64 ohci_hcd
>> [1.372378] usb usb7: SerialNumber: :00:14.5
>> [1.372490] usb usb7: configuration #1 chosen from 1 choice
>> [1.372567] hub 7-0:1.0: USB hub found
>> [PAUSE HAPPENS HERE -> I PRESSED SHIFT AFTER ABOUT 12 SECONDS]
>> [   14.302853] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>
> Thanks for a nice report.
>
> Interesting.  Does this still happen with a current squeeze or sid
> kernel?  (The only packages from outside squeeze you should need in
> order to test the latter are initramfs-tools and linux-base.)
>
> Please attach full "dmesg" output from a successful boot.
[...]
> One more test: is the behavior any different if you supply idle=mwait on
> the kernel command line?

Ping.  Are you still interested in pursuing this?  (If the answer
is "no", that's fine, but please do let us know so we can stop
tracking it.)

Looks like a fun 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/20120317001110.GA325@burratino

Bug#586029: udev: 3ware 8006 RAID controller gets a new controller, ID on each reboot

[Jonathan Nieder]

Hi again,

Jonathan Nieder wrote:
> Patrick Matthäi wrote:

>> looks like a real (fixed) bug:
>>
>> 1) in the past (etch times) it does not happen
>> 2) With squeeze and some more kernel versions + the issue occurs
>> 3) Now - with 2.6.37 (maybe also with 2.6.36, just notified it now) it
>> isn't changing on each reboot again and again
>
> I have not looked into this, but here are some quick questions anyway.
>
>  - is this reproducible with current squeeze kernels? (I assume it is)
>  - can you bisect a little to narrow down the range to search for the
>fix, using kernels from snapshot.debian.org?

I guess some more basic questions are warranted before spending time
on it:

 - do you still have access to this hardware?
 - if so, if we come up with patches against squeeze to fix this,
   would you be interested in testing them?

Sorry for the trouble and the slow response.
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/20120317000655.GA302@burratino

Bug#585625: Switch to i915/KMS leaves console unusable

[Jonathan Nieder]

Jonathan Nieder wrote:
> Bastian Blank wrote:
 
>> I tried to switch to inteldrmfb aka KMS with the following commands:
>> | rmmod i915
>> | modprobe i915 modeset=1
>>
>> After that, the console was black, without even a cursor. The same also
>> seems to happen if it is loaded with this setting on startup. The only
>> way to recover the console is to start the xserver and switch back.
>
> Do current squeeze kernels do this?  And do current sid kernels
> reliably not do it?

Sorry, a more basic question first.

Bastian Blank wrote:

> sys_vendor: Hewlett-Packard
> product_name: HP Compaq 6910p
> product_version: F.0B
> chassis_vendor: Hewlett-Packard
> chassis_version: 
> bios_vendor: Hewlett-Packard
> bios_version: 68MCU Ver. F.0B
> board_vendor: Hewlett-Packard
> board_name: 30BE
> board_version: KBC Version 68.32

Do you still have access to this hardware?

Curious,
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/20120317000321.GA32744@burratino

Bug#584314: base: System freezes at random time after Resume from Suspend (Regression)

[Jonathan Nieder]

Jonathan Nieder wrote:

> To recap, this bug is about symptoms of memory corruption after
> suspending to disk on an Acer Aspire 5610, which uses (I think)
> the 945GM express chipset.

This should have read "after suspending to RAM".  Sorry for the
nonsense.



-- 
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/20120316235953.GA32730@burratino

Processed: Re: base: System freezes at random time after Resume from Suspend (Regression)

[Debian Bug Tracking System]

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

> affects 584314 + xserver-xorg-video-intel
Bug #584314 [linux-2.6] base: System freezes at random time after Resume from 
Suspend (Regression)
Added indication that 584314 affects xserver-xorg-video-intel
> quit
Stopping processing here.

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

Bug#584314: base: System freezes at random time after Resume from Suspend (Regression)

[Jonathan Nieder]

affects 584314 + xserver-xorg-video-intel
quit

Hi,

Thanks again for your work on this bug so far.

To recap, this bug is about symptoms of memory corruption after
suspending to disk on an Acer Aspire 5610, which uses (I think)
the 945GM express chipset.

Lenny and wheezy worked fine; it is only the squeeze kernel that
has this problem.

Searching through kernels from snapshot.debian.org, you found
that it was introduced between 2.6.36 and 2.6.37-rc4.  (Nicely
done.)

Andreas Berger wrote:

> ok, i narrowed it down, but it is:
>
> found: linux-image-2.6.36-trunk-686, version 2.6.36-1~experimental.1
> not found: linux-image-2.6.37-rc4-686,   version 2.6.37~rc4-1~experimental.1

Unfortunately there are a lot of interesting patches in that range,
so we will probably need a little more data to track this down.  So
I suggested:

 - trying suspend-to-disk (with

echo disk >/sys/power/state

   ) and seeing if that reproduces the same trouble

 - suspending from single-user mode (kernel params "single debug")
   or from an initramfs shell (kernel param "break=top") to see if
   the same problem occurs even if the i915 driver is not loaded
   yet when the suspend/hibernate happens

Other ideas would be welcome, too.  I'd be happy to get this fixed in
squeeze.

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/20120316235216.GA32646@burratino

Processed: Re: Kernel exceptions in ext3/journal subsystem

[Debian Bug Tracking System]

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

> # Christoph Egger wrote:
> #
> # > Last time it died in the middle of an apt-cache call which doesn't
> # > (as far as I understand it) do any (u)mounts.
> tags 583686 - moreinfo
Bug #583686 [linux-2.6] Kernel exceptions in ext3/journal subsystem
Removed tag(s) moreinfo.
>
End of message, stopping processing here.

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

Bug#583653: xserver-xorg-video-radeon: 15x-slower performance regression in KMS mode for 2D operations

[Jonathan Nieder]

Jonathan Nieder wrote:
> Sylvain Beucler wrote:
>> On Sun, Jun 06, 2010 at 10:33:54PM +0200, Sylvain Beucler wrote:

>>> The test runs at 65FPS with radeon.agpmode=-1 (~3-4x faster than
>>> without this option, but ~4-5x slower than without KMS).
>>
>> On 2.6.34-1-686 (from experimental) the test runs at 150 FPS.
>> It's better though still 2x slower.
>
> Hm, how do 3.1.y kernels do?

Ping?  If you don't have access to this hardware or no longer are
interested in pursuing this, that's fine, but please do let us know so
we can plan accordingly.

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/20120316233425.GA32485@burratino

Bug#583310: marked as done (linux-image-2.6.32-5-686: kernel panic! booting 2.6.32-5-686)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2012 18:28:58 -0500
with message-id <20120316232858.GA32463@burratino>
and subject line Re: [2.6.32-3 -> 2.6.32-13 regression] kernel panic! booting
has caused the Debian Bug report #583310,
regarding linux-image-2.6.32-5-686: kernel panic! booting 2.6.32-5-686
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.)


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

I get a kernel panic when booting kernel 2.6.32-686 and -486, which does not
happen with 2.6.32-3 or 2.6.32-2. Machine: Pentium 3 600 MHz.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 620 Host
[1039:0620] (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: agpgart-sis

00:00.1 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513
[IDE] [1039:5513] (rev d0) (prog-if 80 [Master])
Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller
(A,B step) [1039:5513]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:0b.0 Ethernet controller [0200]: Davicom Semiconductor, Inc. 21x4x
DEC-Tulip compatible 10/100 Ethernet [1282:9102] (rev 10)
Subsystem: Davicom Semiconductor, Inc. DM9102A (DM9102AE, SM9102AF)
Ethernet 100/10 MBit [0291:8212]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: dmfe

00:0f.0 Multimedia audio controller [0401]: C-Media Electronics Inc
CM8738 [13f6:0111] (rev 10)
Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device 
[13f6:0111]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- 
Kernel driver in use: C-Media PCI

00:0f.1 Communication controller [0780]: C-Media Electronics Inc
CM8738 [13f6:0211] (rev 10)
Subsystem: C-Media Electronics Inc CM8738 [13f6:0211]
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- 

01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems
[SiS] 530/620 PCI/AGP VGA Display Adapter [1039:6306] (rev 2a)
(prog-if 00 [VGA controller])
Subsystem: Silicon Integrated Systems [SiS] 530/620 PCI/AGP VGA
Display Adapter [1039:6306]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR-  [disabled]
Capabilities: 


** USB devices:
Bus 001 Device 002: ID 07b2:5101 Motorola BCS, Inc. SurfBoard SB5101 Cable Modem
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


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

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

Versions of packages linux-image-2.6.32-5-686 depends on:
ii  debconf [debconf-2.0]1.5.32  Debian configuration management sy
ii  initramfs-tools [linux-initr 0.94.4  tools for generating an initramfs
ii  linux-base   2.6.32-13   Linux image base package
ii  module-init-tools3.12~pre2-3 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.32-5-686 recommends:
ii  firmware-linux-free   2.6.32-13  Binary firmware for various driver
ii  libc6-i6862.10.2-9   GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.32-5-686 suggests:
ii  grub-legacy [grub]0.97-61GRand Unified Bootloader 

Bug#578912: [squeeze] [R520] soft lockups with radeon KMS

[Jonathan Nieder]

Hi Zsolt,

Zsolt Rizsanyi wrote:
> On Tue, Feb 14, 2012 at 11:22 AM, Jonathan Nieder  wrote:
>> Zsolt Rizsanyi wrote:

>>> I could try 2.6.32-41 but I would be testing for a completely
>>> different (possibly irrelevant) issue.
>>
>> I understand.  I would be interested in the result from 2.6.32-41
>> anyway.
>
> OK, I will get around to try both of them again soon :)

So now I'm in suspense.  How does 2.6.32-41 do?

Curious,
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/20120316232504.GA32403@burratino

Bug#562981: marked as done (rt2860-source: connection drops - debian kernel 2.6.32)

[Debian Bug Tracking System]

Your message dated Fri, 16 Mar 2012 18:20:13 -0500
with message-id <20120316232013.GA32365@burratino>
and subject line Re: rt2860-source: connection drops - debian kernel 2.6.32
has caused the Debian Bug report #562981,
regarding rt2860-source: connection drops - debian kernel 2.6.32
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.)


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

On latest sid kernel:
Linux plageis 2.6.32-trunk-amd64 #1 SMP Thu Dec 17 06:29:18 UTC 2009
x86_64 GNU/Linux

My wireless connection suddenly drops after 20 to 30 minutes of usage,
especially when I run the program synergy between my machines (if I am
not running synergy it can take many hours between every drops).

In the syslog I see:
ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
right as the connection drops

at that point only solution is:
ifdown wlan0 ; rmmod rt2860sta ; sleep 2 ; modprobe rt2860sta ; ifup wlan0

I am not sure where else to report this, I found this package from
http://wiki.debian.org/rt2860sta and the vendor's support page returns a
404 (http://www.ralinktech.com/ralink/Home/Support/Linux.html)



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

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


--- End Message ---
--- Begin Message ---
Jonathan Nieder wrote:
> Jonathan Nieder wrote:
>> Timothee Besset wrote:

>>> My wireless connection suddenly drops after 20 to 30 minutes of usage,
>>> especially when I run the program synergy between my machines (if I am
>>> not running synergy it can take many hours between every drops).
> [...]
>>  Could you provide the current (fixed) version number
[...]
> Ping.  Do you still have access to this hardware, and if so, would you
> be interested in pursuing a fix in squeeze?

Closing due to lack of response.

--- End Message ---

Bug#556433: [squeeze] 3c59x: NETDEV WATCHDOG: transmit timed out

[Jonathan Nieder]

Hi again,

Steve Karg wrote:

> Hi Jonathan,

>> Do you get the timeouts with a 3.x kernel from sid or experimental?
>> If so, please report this to the net...@vger.kernel.org list,
>> attaching dmesg output from bootup and cc-ing Steffen Klassert
>>  in case he has driver-specific
>> insights plus this bug log so we can track it.
>
> I will try that when I get some free time. I starred this in my gmail inbox. 
> :-)

I'm just curious: did you get a chance to try 3.x.y from sid?

[...]
> I think the Linux 2.4 kernels worked, but it would have been many
> years ago that I used it, and I don't really recall. I originally used
> a PCMCIA wireless adapter on this laptop when it was running Debian
> and KDE long ago.  I pulled it out of my stash when my NSLU2 crashed
> and I really missed having a keyboard and screen. I wiped the old
> KDE+2.4 kernel, and did a fresh Debian install. I tried to use the
> wireless, but it was too slow for home file serving.  I had the 3com
> PCMCIA 10/100 Ethernet adapter lying around and decided to use it.
> That is when I started having problems with the 2.6 kernel and the
> adapter.

Ah, ok.  (I remember trying to use a 3com Etherlink III (?) PCMCIA
card years ago and not being able to get it to work at all.  I think
the card didn't support autonegotiation and at the time I didn't know
how to configure it.  Luckily your card is a little better than that
one.)

Thanks for working to improve hardware support in Debian.

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/20120316231803.GA32292@burratino

Bug#516382: [2.6.22 -> 2.6.23 regression] [alpha] tg3: incoming ssh fails with "Corrupted MAC on input"

[Jonathan Nieder]

Hi Thibaut,

Thibaut VARÈNE wrote:

> After upgrading from etch to lenny, and booting the new kernel, I
> realized I couldn't login into the box anymore: ssh would
> consistently fail to connect with:
>
> Corrupted MAC on input
>
> It's reproducible across reboots. When I rebooted into 2.6.18, the
> problem vanished. I'm using a BCM 5701 (tg3 driver) GigE NIC.
[...]
> This bug has sufficient evidence proving
> that it's real and affecting 2.6.26 in lenny.

I'm just curious about the current status: do you still have access
to a machine reproducing this?  If so, do you know if squeeze or
wheezy is affected?

Thanks for your awesome porting efforts, btw.

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/20120316230902.GA32184@burratino

Bug#663332: [3.1 -> 3.2.6] xorg fails to start after kernel upgrade

[Jonathan Nieder]

Hi Johannes,

Johannes Kolb wrote:

> --- erg.good.mod  2012-03-10 12:13:49.0 +0100
> +++ erg.bad.mod   2012-03-10 12:13:39.0 +0100
> @@ -1,87 +1,38 @@
> -ac 12552  0 
>  acpi_cpufreq   12807  1 
> -aes_generic32970  1 aes_i586
> -aes_i586   16608  1 
> -arc4   12418  2 
>  ata_generic12439  0 
> -ath17114  1 ath5k
> -ath5k 115246  0 
> -battery12957  0 
>  binfmt_misc12813  1 
[...]

Weird.  If you reinstall or upgrade a previous kernel or run
"update-initramfs -u -k all", do old kernels still load the expected
list of modules?



-- 
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/20120316225700.GA32122@burratino

Processed: Re: ERROR with intel i915 driver after install backports linux-image-3.2.0-0.bpo.1-amd64

[Debian Bug Tracking System]

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

> # unconfuse debbugs
> reassign 664079 src:linux-2.6 3.2.4-1
Bug #664079 [linux-2.6] ERROR with intel i915 driver after install backports 
linux-image-3.2.0-0.bpo.1-amd64
Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'.
No longer marked as found in versions 3.2.4-1~bpo60+1.
Bug #664079 [src:linux-2.6] ERROR with intel i915 driver after install 
backports linux-image-3.2.0-0.bpo.1-amd64
Marked as found in versions linux-2.6/3.2.4-1.
> # fixed in 3.2.9-1?
> tags 664079 + moreinfo
Bug #664079 [src:linux-2.6] ERROR with intel i915 driver after install 
backports linux-image-3.2.0-0.bpo.1-amd64
Added tag(s) moreinfo.
>
End of message, stopping processing here.

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

Processed: Re: Keyboard input problem after somehow connected with win_key

[Debian Bug Tracking System]

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

> reassign 612744 src:linux-2.6 2.6.32-30
Bug #612744 [linux-2.6] general: Keyboard input problem after somehow connected 
with win_key
Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'.
Bug #612744 [src:linux-2.6] general: Keyboard input problem after somehow 
connected with win_key
Marked as found in versions linux-2.6/2.6.32-30.
> quit
Stopping processing here.

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

Bug#612744: Keyboard input problem after somehow connected with win_key

[Jonathan Nieder]

reassign 612744 src:linux-2.6 2.6.32-30
quit

Hi Michal,

michalxo wrote:

> I've described this bug here.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397496
>
> I am getting this error in debian too.
>
> Linux calypso 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 
> GNU/Linux

Sorry for the very slow response.  Please attach output from

reportbug --template linux-image-$(uname -r)

(I want to see the DMI information and what kernel modules are
loaded.)

Ciao,
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/20120316224614.GA31957@burratino

Bug#662895: i8042: keys get stuck and keyboard stops responding

[Jonathan Nieder]

Jonathan Nieder wrote:

> Thanks for a clear report, and sorry for the slow response.
> Quick ideas:

Another:

 4) Does running

echo blacklist asus_atk0110 >/etc/modprobe.d/gsr-fix-keyboard.conf

and then rebooting help?

Context: http://bugs.debian.org/568557



-- 
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/20120316224030.GB31834@burratino

Bug#662895: i8042: keys get stuck and keyboard stops responding

[Jonathan Nieder]

Hi,

GSR wrote:

> Newly installed machine and every few hours the PS/2 keyboard dies
> leaving a key stuck, but the USB mouse still works. Focusing different
> windows shows something being typed or a modifier key taking effect
> (depends, each time is a different key, sometimes they do not conflict
> with the wm and you can also move windows with mouse, etc). Alt-Sysrq
> or C-A-Fx stop working too when it happens.
>
> Accesing the machine via ssh shows the system still works, allows
> changing VT with chvt (just to see what they have, no input allowed),
> killing programs or rebooting, but no obvious way to recover the kbd
> other than restart. Echoing things to /proc/sysrq-trigger is allowed
> but the naK or Raw ones do not manage to get the kbd back in line,
[...]
> After searching some more and finding I am not alone with respect to
> stuck keyboard, I also found that someone suggests (in
> https://bugzilla.redhat.com/show_bug.cgi?id=676446 ) to invoke
>
> echo -n reconnect > /sys/devices/platform/i8042/serio0/drvctl
>
> and so far it seems to recover the keyboard

Thanks for a clear report, and sorry for the slow response.
Quick ideas:

 1) Please try a squeeze kernel (it should work fine on a
wheezy/sid system) to see if this is a regression.

 2) Please attach /proc/interrupts

 3) Output from acpidump would also be interesting.

Hope that helps,
Jonathan

[...]
> In the recent days I have seen lines in the logs like:
>
> ---8<---
> atkbd serio0: Unknown key pressed (translated set 2, code 0x5b on 
> isa0060/serio0).
> atkbd serio0: Use 'setkeycodes 5b ' to make it known.
> atkbd serio0: Unknown key pressed (translated set 2, code 0x0 on 
> isa0060/serio0).
> atkbd serio0: Use 'setkeycodes 00 ' to make it known.
> atkbd serio0: Unknown key pressed (translated set 2, code 0xc0 on 
> isa0060/serio0).
> atkbd serio0: Use 'setkeycodes e040 ' to make it known.
> hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger 
> bdl_pos_adj.
> ACPI: EC: GPE storm detected, transactions will use polling mode
> atkbd serio0: Unknown key pressed (translated set 2, code 0x8b on 
> isa0060/serio0).
> atkbd serio0: Use 'setkeycodes e00b ' to make it known.
> --->8--
>
> but they are not immediate to the kbd hang. Just adding in case they
> are related or can provide extra hints about what is going on (IRQ
> mess? ACPI gone mad?). The serio0 ones show different codes each time.
[...]
> [0.00] DMI: System manufacturer System Product Name/P7P55D, BIOS 1807 
>07/22/2010
[...]
> bios_vendor: American Megatrends Inc.
> bios_version: 1807   
> board_vendor: ASUSTeK Computer INC.
> board_name: P7P55D
> board_version: Rev 1.xx



-- 
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/20120316223433.GA31834@burratino

Processed: Re: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable

[Debian Bug Tracking System]

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

> found 656476 linux-2.6/3.2.1-1
Bug #656476 [linux-2.6] linux-image-2.6.32-5-686: Sundance network driver 
(D-Link DFE-580TX) timeouts rendering interface unusable
Bug #514833 [linux-2.6] linux-image-2.6.18-6-686: sundance network driver get 
timeout on a DFE-580TX when this kernel is installed
Marked as found in versions linux-2.6/3.2.1-1.
Marked as found in versions linux-2.6/3.2.1-1.
> forwarded 656476 http://thread.gmane.org/gmane.linux.network/219101
Bug #656476 [linux-2.6] linux-image-2.6.32-5-686: Sundance network driver 
(D-Link DFE-580TX) timeouts rendering interface unusable
Bug #514833 [linux-2.6] linux-image-2.6.18-6-686: sundance network driver get 
timeout on a DFE-580TX when this kernel is installed
Set Bug forwarded-to-address to 
'http://thread.gmane.org/gmane.linux.network/219101'.
Set Bug forwarded-to-address to 
'http://thread.gmane.org/gmane.linux.network/219101'.
>
End of message, stopping processing here.

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

Processed: Re: hpsa driver does not support multipath on Smart Array 712m with latest firmware

[Debian Bug Tracking System]

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

> # patch not applied, relevant fix (9bc3711c, [SCSI] hpsa: Fix problem
> # with MSA2xxx devices, 2012-01-19) not in linus's tree
> tags 661057 + upstream
Bug #661057 [linux-2.6] linux-2.6: hpsa driver does not support multipath on 
Smart Array 712m with latest firmware
Added tag(s) upstream.
> found 661057 linux-2.6/3.3~rc6-1~experimental.1
Bug #661057 [linux-2.6] linux-2.6: hpsa driver does not support multipath on 
Smart Array 712m with latest firmware
Marked as found in versions linux-2.6/3.3~rc6-1~experimental.1.
>
End of message, stopping processing here.

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

Processed: Re: Noflushd causes flush- processes to eat all CPU

[Debian Bug Tracking System]

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

> # Jonathan Nieder wrote:
> # > Xavier Roche wrote:
> # >> Le 03/03/2012 14:55, Jonathan Nieder a écrit :
> #
> # >>> Thanks.  Does the attached patch help?
> # >>
> # >> Yes, mostly.
> # >
> # > I've passed this information upstream.  Hopefully it can be fixed in a
> # > 2.6.32.y release soon so everyone benefits.
> #
> # Applied in 2.6.32.59-rc1.
> tags 594923 + fixed-upstream
Bug #594923 [linux-2.6] Zero writeback interval sends flush processes into busy 
loop
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Processed: Re: regression: CPU fan fast after resume: won't climb back down

[Debian Bug Tracking System]

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

> severity 596741 important
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Severity set to 'important' from 'normal'
> found 596741 linux-2.6/2.6.32-21
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Marked as found in versions linux-2.6/2.6.32-21.
> found 596741 linux-2.6/2.6.35-1~experimental.3
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Marked as found in versions linux-2.6/2.6.35-1~experimental.3.
> tags 596741 + upstream
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Added tag(s) upstream.
> # bisects to upstream 2.6.32-rc1
> found 596741 2.6.32~rc8-1~experimental.1
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Marked as found in versions linux-2.6/2.6.32~rc8-1~experimental.1.
> # "3.2-something"
> found 596741 linux-2.6/3.2.1-1
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Marked as found in versions linux-2.6/3.2.1-1.
> quit
Stopping processing here.

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

Bug#596741: regression: CPU fan fast after resume: won't climb back down

[Jonathan Nieder]

severity 596741 important
found 596741 linux-2.6/2.6.32-21
found 596741 linux-2.6/2.6.35-1~experimental.3
tags 596741 + upstream
# bisects to upstream 2.6.32-rc1
found 596741 2.6.32~rc8-1~experimental.1
# "3.2-something"
found 596741 linux-2.6/3.2.1-1
quit

Hi,

Jon Dowland wrote:

> Sorry for the delay. Yes, it does, I'm running a 3.2-something kernel now,
> issue remains.

Thanks.  If I understand the upstream report correctly, this doesn't
happen unless the radeon driver is in use.  Will follow up 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/20120316185849.GA29429@burratino

Bug#659363: Hibernate freezes on HP dc7900 with Linux 3.2 (regression)

[Jonathan Nieder]

Hi Pelle,

Per Olofsson wrote:

> I have now tried some debugging steps, but I can't get the system to
> freeze with the debugging modes.

Thanks for checking.  Could you spell this out a little more for me?

Do you mean, for example, that

echo platform >/sys/power/disk
echo disk >/sys/power/state

doesn't hang?



-- 
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/20120316180051.GF28004@burratino

Processed: Re: Xorg goes to 70% MEM and freezes my system when opening big clock in Ardour3

[Debian Bug Tracking System]

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

> reassign 664060 src:linux-2.6 3.2.10-1
Bug #664060 [linux-image-3.2.0-2-amd64] Xorg goes to 70% MEM and freezes my 
system when opening big clock in Ardour3
Bug reassigned from package 'linux-image-3.2.0-2-amd64' to 'src:linux-2.6'.
No longer marked as found in versions linux-2.6/3.2.10-1.
Bug #664060 [src:linux-2.6] Xorg goes to 70% MEM and freezes my system when 
opening big clock in Ardour3
Marked as found in versions linux-2.6/3.2.10-1.
> affects 664060 + xserver-xorg-video-intel
Bug #664060 [src:linux-2.6] Xorg goes to 70% MEM and freezes my system when 
opening big clock in Ardour3
Added indication that 664060 affects xserver-xorg-video-intel
> quit
Stopping processing here.

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

Bug#664060: Xorg goes to 70% MEM and freezes my system when opening big clock in Ardour3

[Jonathan Nieder]

reassign 664060 src:linux-2.6 3.2.10-1
affects 664060 + xserver-xorg-video-intel
quit

Hi Rosea,

rosea grammostola wrote:

> When I open the big clock window (alt-b) in Ardour3 (downloaded from
> ardour.org), Xorg bumps up to 70% MEM and freezes my system (Thinkpad
> T61)
>
> root  20   0 3082m 1.3g 2632 R   4.0 68.7   0:11.23 Xorg

Thanks for a pleasant report.  Has this always behaved that way, or
did the problems appear after some upgrade?  What suggests to you
that it might be a kernel bug?

Please also attach output from "reportbug --template
xserver-xorg-video-intel".

Curious,
Jonathan

[...]
> X.Org X Server 1.11.3.901 (1.11.4 RC 1)
[...]
> [35.176] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
> [35.217] (II) Module intel: vendor="X.Org Foundation"
> [35.217]  compiled for 1.11.3.901, module version = 2.18.0
[...]
> [35.287] (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
> [35.287] (--) intel(0): Chipset: "965GM"
[...]
> [35.360] (II) intel(0): Output LVDS1 using initial mode 1280x800
[...]
> [   138.376] [mi] EQ overflowing. The server is probably stuck in an infinite 
> loop.
> [   138.760] Backtrace:
> [   141.205] 0: /usr/bin/Xorg (xorg_backtrace+0x26) [0x7f2f33965476]
> [   145.579] 1: /usr/bin/Xorg (mieqEnqueue+0x191) [0x7f2f33945d81]
> [   145.579] 2: /usr/bin/Xorg (0x7f2f337e1000+0x65214) [0x7f2f33846214]
> [   145.580] 3: /usr/bin/Xorg (xf86PostMotionEventP+0x4a) [0x7f2f338807aa]
> [   145.591] 4: /usr/lib/xorg/modules/input/evdev_drv.so 
> (0x7f2f2dc52000+0x49ee) [0x7f2f2dc569ee]
> [   145.591] 5: /usr/bin/Xorg (0x7f2f337e1000+0x8a907) [0x7f2f3386b907]
> [   145.591] 6: /usr/bin/Xorg (0x7f2f337e1000+0xb04ee) [0x7f2f338914ee]
> [   145.591] 7: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f2f32b09000+0xf030) 
> [0x7f2f32b18030]
> [   145.591] 8: /usr/bin/Xorg (0x7f2f337e1000+0x1885b0) [0x7f2f339695b0]
> [   145.591] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f2f32b09000+0xf030) 
> [0x7f2f32b18030]
> [   145.606] 10: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
> (0x7f2f32882000+0x561d9) [0x7f2f328d81d9]
> [   145.606] 11: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
> (0x7f2f32882000+0x73cd2) [0x7f2f328f5cd2]
> [   145.606] 12: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
> (pixman_fill+0x31) [0x7f2f3288c371]
> [   145.666] 13: /usr/lib/xorg/modules/libfb.so (fbFill+0x30d) 
> [0x7f2f2edcdbad]
> [   145.666] 14: /usr/lib/xorg/modules/libfb.so (fbPolyFillRect+0x1c4) 
> [0x7f2f2edce354]
> [   145.680] 15: /usr/lib/xorg/modules/drivers/intel_drv.so 
> (0x7f2f2f808000+0x3bc21) [0x7f2f2f843c21]
> [   145.680] 16: /usr/lib/xorg/modules/drivers/intel_drv.so 
> (0x7f2f2f808000+0x345b1) [0x7f2f2f83c5b1]
> [   145.680] 17: /usr/bin/Xorg (0x7f2f337e1000+0x1164d9) [0x7f2f338f74d9]
> [   145.680] 18: /usr/bin/Xorg (0x7f2f337e1000+0x10503e) [0x7f2f338e603e]
> [   145.680] 19: /usr/bin/Xorg (miCompositeRects+0x7a) [0x7f2f338e612a]
> [   145.680] 20: /usr/lib/xorg/modules/drivers/intel_drv.so 
> (0x7f2f2f808000+0x38a26) [0x7f2f2f840a26]
> [   145.680] 21: /usr/bin/Xorg (0x7f2f337e1000+0x10d546) [0x7f2f338ee546]
> [   145.680] 22: /usr/bin/Xorg (0x7f2f337e1000+0x51f81) [0x7f2f33832f81]
> [   145.680] 23: /usr/bin/Xorg (0x7f2f337e1000+0x411aa) [0x7f2f338221aa]
> [   145.681] 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) 
> [0x7f2f31831ead]
> [   145.681] 25: /usr/bin/Xorg (0x7f2f337e1000+0x4149d) [0x7f2f3382249d]



-- 
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/20120316172540.GC28004@burratino

Processed: Re: USB MIDI keyboard fails to initialize

[Debian Bug Tracking System]

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

> # reproducible with sid on one machine, and not with squeeze on another.
> # is it machine-specific, or is it a regression?
> tags 664068 + moreinfo
Bug #664068 [linux-2.6] linux-image-3.2.0-2-amd64: USB MIDI keyboard fails to 
initialize
Added tag(s) moreinfo.
>
End of message, stopping processing here.

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

Processed: Re: multiple, non-physically accesible, HDMI devices

[Debian Bug Tracking System]

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

> tags 660111 + upstream
Bug #660111 [linux-2.6] multiple, non-physically accesible, HDMI devices
Added tag(s) upstream.
> # letting version tracking do its work
> tags 660111 - wheezy
Bug #660111 [linux-2.6] multiple, non-physically accesible, HDMI devices
Removed tag(s) wheezy.
> quit
Stopping processing here.

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

Bug#660111: multiple, non-physically accesible, HDMI devices

[Jonathan Nieder]

tags 660111 + upstream
# letting version tracking do its work
tags 660111 - wheezy
quit

Hi Andres,

Andres Cimmarusti wrote:

> I've marked this bug as affecting pulseaudio. In fact, it seems (to
> me) sufficient to get version 2.0 of pulseaudio into Debian to solve
> this bug.
>
> With convenience and user-friendliness in mind, I feel that the jack
> detection backport from kernel 3.3 to the Debian 3.2 kernel should be
> done. Since Ubuntu already did it, perhaps this will be easy enough ?

Could you file a new report against pulseaudio summarizing the problem
and your suggested fix and mentioning 
for background?

Then we (or the kernel team) can separately pursue a jack detection
backport and figure out what to do on the kernel side, if anything, to
support upgrades cleanly.

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/20120316164639.GA28004@burratino

Processed: multiple, non-physically accesible, HDMI devices

[Debian Bug Tracking System]

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

> retitle 660111 multiple, non-physically accesible, HDMI devices
Bug #660111 [linux-2.6] [3.0 to 3.1 regression] HDMI 3 devices instead of 1
Changed Bug title to 'multiple, non-physically accesible, HDMI devices' from 
'[3.0 to 3.1 regression] HDMI 3 devices instead of 1'
> affects 660111 + pulseaudio
Bug #660111 [linux-2.6] multiple, non-physically accesible, HDMI devices
Added indication that 660111 affects pulseaudio
> tags 660111 + fixed-upstream wheezy
Bug #660111 [linux-2.6] multiple, non-physically accesible, HDMI devices
Added tag(s) wheezy and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#660111: multiple, non-physically accesible, HDMI devices

[Andres Cimmarusti]

retitle 660111 multiple, non-physically accesible, HDMI devices
affects 660111 + pulseaudio
tags 660111 + fixed-upstream wheezy
thanks

>> (but correct me if I'm wrong). However, I think Debian has decided to
>> go with 3.2 kernel for the next stable release. This means no
>> kcontrols. How is this being handled in Ubuntu 12.04 LTS, since it
>> will also be based on kernel 3.2
>
>
> For Ubuntu 12.04, I've backported the jack detection patches from 3.3 and
> applied them to the Ubuntu 12.04 LTS kernel.
>>
>> Can this still be done in the scenario were Debian has pulseaudio 2.0
>> with your patches, but kernel 3.2?
>>
>> Sorry for the basic questions. I just found out that the release of
>> pulseaudio 2.0 is imminentand I want to push for its adoption in
>>
>> Debian, but with a fix for this HDMI issue.
>
>
> So, with PA 2.0 but without jack detection support in the kernel, you would
> essentially get three or four HDMI devices showing up in your GUI, and the
> user would have to try them all manually to check which one is the right
> one. So, better than changing PA configuration files, but not as elegant as
> with the jack detection (where the right one is selected automatically), of
> course.

I've marked this bug as affecting pulseaudio. In fact, it seems (to
me) sufficient to get version 2.0 of pulseaudio into Debian to solve
this bug.

With convenience and user-friendliness in mind, I feel that the jack
detection backport from kernel 3.3 to the Debian 3.2 kernel should be
done. Since Ubuntu already did it, perhaps this will be easy enough ?

Cheers

Andres



-- 
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/CAH=dYrHDsh=hhvh_arrmvxq5gpe59otp+k9+hprveimjcuf...@mail.gmail.com

Bug#660111: [alsa-devel] multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB

[David Henningsson]

On 03/16/2012 04:03 PM, Andres Cimmarusti wrote:

Hello again,

On Sat, Mar 3, 2012 at 9:43 PM, David Henningsson
  wrote:

On 03/04/2012 12:36 AM, Andres Cimmarusti wrote:


There is active work going on in this area. In fact, I just posted a
patch
to the PA mailinglist [1]. And yes, we already have it in Ubuntu 11.10
(to
probe multiple hdmi devices for Intel and NVidia), and the main reason it
took until now to upstream that patch, was the decision to switch jack
detection method from input devices to kcontrols.



Thank you for all the references you provided and your work in fixing
this issue for all users. I just looked at the git repository for the
source code of pulseaudio, but I see your patches have not been
included yet. Do you have any estimate of when they will be merged? if
so, do you think they'll be included in the next release (do you know
when this will be?) ?



I hope they'll be in PulseAudio 2.0, as they are currently waiting for
review. For next release, see [2], but judging from the PulseAudio 1.0
release process - no, I don't know when this will be ;-)



I'm considering reassigning this bug to pulseaudio in debian and
asking them to include the appropriate patches. Which ones would
actually be needed (say, to apply them to pulseaudio 1.1)? would your
6 patches announced on the mailing list in February be enough?



If you want them to apply to PulseAudio 1.1, you can have a look at [1]. The
patches currently posted apply to git head. You'll need all of the 06*
patches (as well as Linux 3.3 for the kcontrols).


It looks like your patches have been merged:
http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/


That is correct.


(but correct me if I'm wrong). However, I think Debian has decided to
go with 3.2 kernel for the next stable release. This means no
kcontrols. How is this being handled in Ubuntu 12.04 LTS, since it
will also be based on kernel 3.2


For Ubuntu 12.04, I've backported the jack detection patches from 3.3 
and applied them to the Ubuntu 12.04 LTS kernel.



A more light-weight version could be what I did in Ubuntu 11.04, where there
was no jack detection, but I just exposed all four devices in PulseAudio and
let the user choose manually, like this [4]. (I later renamed that file from
"nvidia.conf" to "extra-hdmi.conf", and added the same file to be used for
Intel chips.)


Can this still be done in the scenario were Debian has pulseaudio 2.0
with your patches, but kernel 3.2?

Sorry for the basic questions. I just found out that the release of
pulseaudio 2.0 is imminentand I want to push for its adoption in
Debian, but with a fix for this HDMI issue.


So, with PA 2.0 but without jack detection support in the kernel, you 
would essentially get three or four HDMI devices showing up in your GUI, 
and the user would have to try them all manually to check which one is 
the right one. So, better than changing PA configuration files, but not 
as elegant as with the jack detection (where the right one is selected 
automatically), of course.


--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic



--
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/4f6358a4.6020...@canonical.com

Bug#660111: [alsa-devel] multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB

[Andres Cimmarusti]

Hello again,

On Sat, Mar 3, 2012 at 9:43 PM, David Henningsson
 wrote:
> On 03/04/2012 12:36 AM, Andres Cimmarusti wrote:
>>>
>>> There is active work going on in this area. In fact, I just posted a
>>> patch
>>> to the PA mailinglist [1]. And yes, we already have it in Ubuntu 11.10
>>> (to
>>> probe multiple hdmi devices for Intel and NVidia), and the main reason it
>>> took until now to upstream that patch, was the decision to switch jack
>>> detection method from input devices to kcontrols.
>>
>>
>> Thank you for all the references you provided and your work in fixing
>> this issue for all users. I just looked at the git repository for the
>> source code of pulseaudio, but I see your patches have not been
>> included yet. Do you have any estimate of when they will be merged? if
>> so, do you think they'll be included in the next release (do you know
>> when this will be?) ?
>
>
> I hope they'll be in PulseAudio 2.0, as they are currently waiting for
> review. For next release, see [2], but judging from the PulseAudio 1.0
> release process - no, I don't know when this will be ;-)
>
>
>> I'm considering reassigning this bug to pulseaudio in debian and
>> asking them to include the appropriate patches. Which ones would
>> actually be needed (say, to apply them to pulseaudio 1.1)? would your
>> 6 patches announced on the mailing list in February be enough?
>
>
> If you want them to apply to PulseAudio 1.1, you can have a look at [1]. The
> patches currently posted apply to git head. You'll need all of the 06*
> patches (as well as Linux 3.3 for the kcontrols).

It looks like your patches have been merged:
http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/
(but correct me if I'm wrong). However, I think Debian has decided to
go with 3.2 kernel for the next stable release. This means no
kcontrols. How is this being handled in Ubuntu 12.04 LTS, since it
will also be based on kernel 3.2

> A more light-weight version could be what I did in Ubuntu 11.04, where there
> was no jack detection, but I just exposed all four devices in PulseAudio and
> let the user choose manually, like this [4]. (I later renamed that file from
> "nvidia.conf" to "extra-hdmi.conf", and added the same file to be used for
> Intel chips.)

Can this still be done in the scenario were Debian has pulseaudio 2.0
with your patches, but kernel 3.2?

Sorry for the basic questions. I just found out that the release of
pulseaudio 2.0 is imminent and I want to push for its adoption in
Debian, but with a fix for this HDMI issue.

Thanks a million

Andres



-- 
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/CAH=dyrgf2w0dxpgjdobpivqnnkuj+_drvllrj8vm4ymm--f...@mail.gmail.com

Bug#628444: iwlagn - "MAC is in deep sleep", cannot restore wifi operation

[Dafydd Harries]

On Fri, Mar 16, 2012 at 01:30:46PM +0100, Dafydd Harries wrote:
> Today I got a failure, and on my machine it was using L0S, not L1S:
> 
> Mar 16 11:38:45 localhost kernel: [ 9045.913617] iwlwifi :02:00.0: L1 
> Disabled; Enabling L0S
> 
> So I don't think this is the difference necessarily.
> 
> Syslog from today attached.

And I got a failure very quickly (50m) after I tried booting with
power_save=1.
Mar 16 13:05:15 localhost kernel: [   31.986202] iwlwifi :02:00.0: PCI INT 
A -> GSI 16 (level, low) -> IRQ 16
Mar 16 13:05:15 localhost kernel: [   31.986239] iwlwifi :02:00.0: setting 
latency timer to 64
Mar 16 13:05:15 localhost kernel: [   31.986285] iwlwifi :02:00.0: 
pci_resource_len = 0x2000
Mar 16 13:05:15 localhost kernel: [   31.986287] iwlwifi :02:00.0: 
pci_resource_base = c90011794000
Mar 16 13:05:15 localhost kernel: [   31.986288] iwlwifi :02:00.0: HW 
Revision ID = 0x35
Mar 16 13:05:15 localhost kernel: [   31.986414] iwlwifi :02:00.0: irq 42 
for MSI/MSI-X
Mar 16 13:05:15 localhost kernel: [   31.986494] iwlwifi :02:00.0: Detected 
Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
Mar 16 13:05:15 localhost kernel: [   31.986602] iwlwifi :02:00.0: L1 
Enabled; Disabling L0S
Mar 16 13:05:15 localhost kernel: [   32.003127] iwlwifi :02:00.0: device 
EEPROM VER=0x436, CALIB=0x6
Mar 16 13:05:15 localhost kernel: [   32.003132] iwlwifi :02:00.0: Device 
SKU: 0X1f0
Mar 16 13:05:15 localhost kernel: [   32.003136] iwlwifi :02:00.0: Valid Tx 
ant: 0X7, Valid Rx ant: 0X7
Mar 16 13:05:15 localhost kernel: [   32.003190] iwlwifi :02:00.0: Tunable 
channels: 13 802.11bg, 24 802.11a channels
Mar 16 13:05:15 localhost kernel: [   32.716291] iwlwifi :02:00.0: loaded 
firmware version 9.221.4.1 build 25532
Mar 16 13:05:25 localhost kernel: [ 1033.032388] iwlwifi :02:00.0: L1 
Enabled; Disabling L0S
Mar 16 13:05:25 localhost kernel: [ 1033.039190] iwlwifi :02:00.0: Radio 
type=0x0-0x3-0x1
Mar 16 13:05:26 localhost kernel: [ 1033.281070] iwlwifi :02:00.0: L1 
Enabled; Disabling L0S
Mar 16 13:05:26 localhost kernel: [ 1033.287845] iwlwifi :02:00.0: Radio 
type=0x0-0x3-0x1
Mar 16 13:36:18 localhost kernel: [ 2880.810592] iwlwifi :02:00.0: Error 
sending POWER_TABLE_CMD: time out after 2000ms.
Mar 16 13:36:18 localhost kernel: [ 2880.810599] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 6
Mar 16 13:36:21 localhost kernel: [ 2880.810603] iwlwifi :02:00.0: set 
power fail, ret = -110
Mar 16 13:36:21 localhost kernel: [ 2883.304348] iwlwifi :02:00.0: Error 
sending REPLY_QOS_PARAM: time out after 2000ms.
Mar 16 13:36:21 localhost kernel: [ 2883.304355] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 9
Mar 16 13:36:21 localhost kernel: [ 2883.304360] iwlwifi :02:00.0: Failed 
to update QoS
Mar 16 13:36:23 localhost kernel: [ 2885.299347] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 13:36:23 localhost kernel: [ 2885.299355] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 12
Mar 16 13:36:23 localhost kernel: [ 2885.299360] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 13:36:25 localhost kernel: [ 2887.294339] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 13:36:25 localhost kernel: [ 2887.294346] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 15
Mar 16 13:36:25 localhost kernel: [ 2887.294350] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 13:36:27 localhost kernel: [ 2889.289307] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 13:36:27 localhost kernel: [ 2889.289315] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 18
Mar 16 13:36:27 localhost kernel: [ 2889.289320] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 13:36:29 localhost kernel: [ 2891.284303] iwlwifi :02:00.0: Error 
sending REPLY_ADD_STA: time out after 2000ms.
Mar 16 13:36:29 localhost kernel: [ 2891.284309] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 21
Mar 16 13:36:31 localhost kernel: [ 2893.279199] iwlwifi :02:00.0: Error 
sending REPLY_REMOVE_STA: time out after 2000ms.
Mar 16 13:36:31 localhost kernel: [ 2893.279208] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 24
Mar 16 13:36:31 localhost kernel: [ 2893.279215] iwlwifi :02:00.0: Error 
removing station 00:50:7f:cb:4b:58
Mar 16 13:36:33 localhost kernel: [ 2895.278267] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 13:36:33 localhost kernel: [ 2895.278275] iwlwifi :02:00.0: Current 
CMD queue read_ptr 4 write_ptr 27
Mar 16 13:36:33 localhost kernel: [ 2895.278280] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 13:36:35 localhost kernel: [ 2897.281201] iwlwifi :02:00.0: fail to 
flush all tx fifo queues
Mar 16 13:36:37 localhost kernel: [ 2899.276196] iwlwifi 

Bug#628444: iwlagn - "MAC is in deep sleep", cannot restore wifi operation

[Dafydd Harries]

On Fri, Mar 16, 2012 at 10:03:54AM +0100, Bjørn Mork wrote:
> But I wonder about Juha's observation about this difference between my
> setup: 
> 
>   [   12.611061] iwlwifi :03:00.0: L1 Disabled; Enabling L0S
> 
> and his:
> 
>   [245082.407512] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
> 
> This looks extremely suspicious to me in light of Meenakshi's comment on
> known issues with L1 on these devices and that Intel therefore use L0S
> by default.
> 
> How come Juha end up with L1 enabled, then?  And is that the case for
> everyone seeing this bug?

Today I got a failure, and on my machine it was using L0S, not L1S:

Mar 16 11:38:45 localhost kernel: [ 9045.913617] iwlwifi :02:00.0: L1 
Disabled; Enabling L0S

So I don't think this is the difference necessarily.

Syslog from today attached.
Mar 16 11:37:49 localhost kernel: [ 8989.631323] iwlwifi :02:00.0: Error 
sending REPLY_QOS_PARAM: time out after 2000ms.
Mar 16 11:37:49 localhost kernel: [ 8989.631332] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 63
Mar 16 11:37:49 localhost kernel: [ 8989.631336] iwlwifi :02:00.0: Failed 
to update QoS
Mar 16 11:37:51 localhost kernel: [ 8991.626456] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:37:51 localhost kernel: [ 8991.626463] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 66
Mar 16 11:37:51 localhost kernel: [ 8991.626468] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 11:37:53 localhost kernel: [ 8993.621540] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:37:53 localhost kernel: [ 8993.621547] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 69
Mar 16 11:37:53 localhost kernel: [ 8993.621552] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 11:37:55 localhost kernel: [ 8995.616627] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:37:55 localhost kernel: [ 8995.616634] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 70
Mar 16 11:37:55 localhost kernel: [ 8995.616638] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 11:37:57 localhost kernel: [ 8997.611717] iwlwifi :02:00.0: Error 
sending REPLY_SCAN_CMD: time out after 2000ms.
Mar 16 11:37:57 localhost kernel: [ 8997.611724] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 71
Mar 16 11:37:59 localhost kernel: [ 8999.606756] iwlwifi :02:00.0: Error 
sending REPLY_ADD_STA: time out after 2000ms.
Mar 16 11:37:59 localhost kernel: [ 8999.606764] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 72
Mar 16 11:38:01 localhost kernel: [ 9001.601883] iwlwifi :02:00.0: Error 
sending REPLY_REMOVE_STA: time out after 2000ms.
Mar 16 11:38:01 localhost kernel: [ 9001.601891] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 73
Mar 16 11:38:01 localhost kernel: [ 9001.601898] iwlwifi :02:00.0: Error 
removing station 00:50:7f:cb:4b:58
Mar 16 11:38:03 localhost kernel: [ 9003.596977] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:38:03 localhost kernel: [ 9003.596984] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 74
Mar 16 11:38:03 localhost kernel: [ 9003.596989] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 11:38:05 localhost kernel: [ 9005.600071] iwlwifi :02:00.0: fail to 
flush all tx fifo queues
Mar 16 11:38:07 localhost kernel: [ 9007.595140] iwlwifi :02:00.0: Error 
sending POWER_TABLE_CMD: time out after 2000ms.
Mar 16 11:38:07 localhost kernel: [ 9007.595148] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 75
Mar 16 11:38:09 localhost kernel: [ 9007.595154] iwlwifi :02:00.0: set 
power fail, ret = -110
Mar 16 11:38:09 localhost kernel: [ 9009.590164] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:38:09 localhost kernel: [ 9009.590171] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 76
Mar 16 11:38:09 localhost kernel: [ 9009.590175] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 11:38:11 localhost kernel: [ 9011.621214] iwlwifi :02:00.0: Error 
sending REPLY_ADD_STA: time out after 2000ms.
Mar 16 11:38:11 localhost kernel: [ 9011.621221] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 77
Mar 16 11:38:13 localhost kernel: [ 9013.616306] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:38:13 localhost kernel: [ 9013.616312] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 78
Mar 16 11:38:13 localhost kernel: [ 9013.616317] iwlwifi :02:00.0: Error 
clearing ASSOC_MSK on BSS (-110)
Mar 16 11:38:15 localhost kernel: [ 9015.611391] iwlwifi :02:00.0: Error 
sending REPLY_RXON: time out after 2000ms.
Mar 16 11:38:15 localhost kernel: [ 9015.611397] iwlwifi :02:00.0: Current 
CMD queue read_ptr 59 write_ptr 79
Mar 16 11:38

Bug#628444: iwlagn - "MAC is in deep sleep", cannot restore wifi operation

[Bjørn Mork]

Shannon Dealy  writes:

> I created a file "/etc/modprobe.d/iwlagn.conf" and placed the
> following line in it:
>
>   options iwlagn 11n_disable=1 11n_disable50=1

Note that the 11n_disable50 options was removed in 3.0 and the iwlagn
module was renamed to iwlwifi in 3.2.

Which makes this workaround pretty much irrelevant to any current Debian
kernel as noone(?) has seen the bug in 2.6.32.  Are you still using the
2.6.39-1 kernel you originally opened this bug against?

FWIW, I enabled power_save a few days ago (was previously at default)
after the nice summary from Meenakshi, just to see if I could replicate
this issue.  My module parameters are now:

bjorn@nemi:~$ grep . /sys/module/iwlwifi/parameters/*
/sys/module/iwlwifi/parameters/11n_disable:0
/sys/module/iwlwifi/parameters/ack_check:N
/sys/module/iwlwifi/parameters/amsdu_size_8K:1
/sys/module/iwlwifi/parameters/antenna_coupling:0
/sys/module/iwlwifi/parameters/auto_agg:Y
/sys/module/iwlwifi/parameters/bt_ch_inhibition:Y
/sys/module/iwlwifi/parameters/bt_coex_active:Y
/sys/module/iwlwifi/parameters/fw_restart:1
/sys/module/iwlwifi/parameters/led_mode:0
/sys/module/iwlwifi/parameters/no_sleep_autoadjust:Y
/sys/module/iwlwifi/parameters/plcp_check:Y
/sys/module/iwlwifi/parameters/power_level:0
/sys/module/iwlwifi/parameters/power_save:Y
/sys/module/iwlwifi/parameters/queues_num:0
/sys/module/iwlwifi/parameters/swcrypto:0
/sys/module/iwlwifi/parameters/ucode_alternative:1
/sys/module/iwlwifi/parameters/wd_disable:0


And I am often using 802.11n at 5GHz.  Still haven't seen the issue.

But I wonder about Juha's observation about this difference between my
setup: 

  [   12.611061] iwlwifi :03:00.0: L1 Disabled; Enabling L0S

and his:

  [245082.407512] iwlwifi :03:00.0: L1 Enabled; Disabling L0S

This looks extremely suspicious to me in light of Meenakshi's comment on
known issues with L1 on these devices and that Intel therefore use L0S
by default.

How come Juha end up with L1 enabled, then?  And is that the case for
everyone seeing this bug?



Bjørn



--
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/87y5r0ex39@nemi.mork.no

Bug#664064: netlink messages

[Reinhard Karcher]

It's not an effect of Debian specific changes, a kernel generated from 
latest kernel git shows the same messages.


Reinhard



--
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/4f630161.6090...@gmx.net

Bug#664064: linux-image-3.3.0-rc6-amd64: 4 messages every minute in syslog from netlink

[Reinhard Karcher]

Am 15.03.2012 18:14, schrieb Ben Hutchings:

It would be useful if we could tell which program is sending the
message, but I think that may be difficult to do.



Some further investigation showed that the 1st occurrence of the message 
is related to the start of KDE. After stopping X (and KDE) there are no 
new messages logged.


Reinhard



--
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/4f62ff97.9080...@gmx.net