Bug#674907: severity
On Mon, 2012-10-01 at 23:14 +0200, Mauro wrote: On 1 October 2012 21:01, Thomas Goirand tho...@goirand.fr wrote: On 10/01/2012 09:21 PM, Bastian Blank wrote: Please don't top-post. On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote: - Unreliable Time affects all the system and can make the whole host useless. At least for production use. Still the system. - Is just broken for all my 53 physical servers with different hardware. (with 2 or 3 server shift per week on the whole cluster.) So? Since when is it broken? Squeeze was released 1.5 years ago and noone mentioned a problem before this bug report was filed. This are identical or mostly identical servers? so, I think I'am not playing with words on the severity definition. Right now it seems to only affect two users. Bastian Pierre, Have you tried using independent wallclock and the ntp daemon on your domUs? http://my.opera.com/marcomarongiu/blog/2011/01/05/independent-wallclock-in-xen-4 It seems that independent wallclock is not supported anymore. With modern kernels (since this is kernel not hypervisor dependent) independent wallclock is the default and only option -- so the option has disappeared. Ian. -- Ian Campbell The most difficult years of marriage are those following the wedding. -- 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/1349174652.650.31.ca...@zakaz.uk.xensource.com
Bug#557802: No sound with snd-ens1371.ko
Tino Schmidt wrote: I'm sorry, I sold the hardware a few months ago. No problem. The bug was fixed in 2.6.39: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6ebb8a4a43e34f999ab36f27f972f3cd751cda4f The patch is also included in recent versions of the kernel in Squeeze. Thanks! Do you mind if I forward this information to the bug log? Jonathan Yes, feel free to add it! Tino -- 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/506abad8.40...@gmx.net
Processed: Re: [etch-lenny regression] No sound with snd-ens1371.ko
Processing commands for cont...@bugs.debian.org:
tags 557802 - moreinfo
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Removed tag(s) moreinfo.
End of message, stopping processing here.
Please contact me if you need assistance.
--
557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802
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.134918496210600.transcr...@bugs.debian.org
Processed: Re: Linux does not boot on Intel Core i7-3720QM Processor (2.60GHz Turbo)
Processing commands for cont...@bugs.debian.org:
severity 557802 important
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Severity set to 'important' from 'normal'
reassign 557802 src:linux 3.2.23-1
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Bug reassigned from package 'linux-2.6' to 'src:linux'.
No longer marked as found in versions 2.6.26-19lenny2.
No longer marked as fixed in versions 2.6.32-34.
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Marked as found in versions linux/3.2.23-1.
End of message, stopping processing here.
Please contact me if you need assistance.
--
557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802
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.134918522512429.transcr...@bugs.debian.org
Bug#688222: needs update for 3.2.29-4
reopen 688222 retitle 688222 needs update for 3.2.30-1 thanks obviously, you should upload linux-latest for kernel-abi 3.2.0-4. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/506aef05.1060...@progress-technologies.net
Processed: Re: needs update for 3.2.29-4
Processing commands for cont...@bugs.debian.org:
reopen 688222
Bug #688222 {Done: Bastian Blank wa...@debian.org} [linux-latest] needs
update for 3.2.29-4
Bug reopened
Ignoring request to alter fixed versions of bug #688222 to the same values
previously set
retitle 688222 needs update for 3.2.30-1
Bug #688222 [linux-latest] needs update for 3.2.29-4
Changed Bug title to 'needs update for 3.2.30-1' from 'needs update for
3.2.29-4'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688222
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.134918533013598.transcr...@bugs.debian.org
Processed: Re: Linux does not boot on Intel Core i7-3720QM Processor (2.60GHz Turbo)
Processing commands for cont...@bugs.debian.org:
# drat, copy/paste failure
fixed 557802 linux-2.6/2.6.32-34
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Marked as fixed in versions linux-2.6/2.6.32-34.
found 557802 linux-2.6/2.6.26-19lenny2 , linux-2.6/2.6.32-1
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
The source linux-2.6 and version 2.6.26-19lenny2 do not appear to match any
binary packages
Marked as found in versions linux-2.6/2.6.26-19lenny2 and linux-2.6/2.6.32-1.
notfound 557802 linux/3.2.23-1
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
No longer marked as found in versions linux/3.2.23-1.
severity 689420 important
Bug #689420 [linux-image-3.2.0-3-amd64] Linux does not boot on Intel Core
i7-3720QM Processor (2.60GHz Turbo)
Severity set to 'important' from 'critical'
reassign 689420 src:linux 3.2.23-1
Bug #689420 [linux-image-3.2.0-3-amd64] Linux does not boot on Intel Core
i7-3720QM Processor (2.60GHz Turbo)
Bug reassigned from package 'linux-image-3.2.0-3-amd64' to 'src:linux'.
No longer marked as found in versions linux/3.2.23-1.
Ignoring request to alter fixed versions of bug #689420 to the same values
previously set
Bug #689420 [src:linux] Linux does not boot on Intel Core i7-3720QM Processor
(2.60GHz Turbo)
Marked as found in versions linux/3.2.23-1.
End of message, stopping processing here.
Please contact me if you need assistance.
--
557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802
689420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689420
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.134918587718433.transcr...@bugs.debian.org
Processed: Re: Linux does not boot on Intel Core i7-3720QM Processor (2.60GHz Turbo)
Processing commands for cont...@bugs.debian.org:
# v2.6.39-rc3~7^2~5 (ALSA: ens1371: fix Creative Ectiva support,
# 2011-03-30)
fixed 557802 linux-2.6/2.6.39~rc4-1~experimental.1
Bug #557802 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux]
linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Marked as fixed in versions linux-2.6/2.6.39~rc4-1~experimental.1.
End of message, stopping processing here.
Please contact me if you need assistance.
--
557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802
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.134918648223262.transcr...@bugs.debian.org
Bug#688882: linux-image-2.6.32-5-xen-amd64: Dom0 crashes when starting third DomU
On Wed, 2012-09-26 at 11:08 -0400, Alan P. Laudicina wrote: Package: linux-2.6 Version: 2.6.32-45 Severity: important Whenever I start a third domU, my dom0 immediately crashes and reboots. Because it is in colo, I cannot pull a capture of why it's happening. If there is a way to do this without going onsite, I am willing to do that. It's likely a kernel ooops of some sort, if you aren't able to get a serial console or IP KVM via your colo provider then another option (other than changing providers ;-)) might be to try netconsole to another suitable machine in the colo or to setup a local repro scenario somewhere more conveniently located. I'm afraid that without some data about the actual crash which is happening there is not likely to be much which can be done about this, sorry. Ian. All of the DomU's are using a simple Xen config that looks like this: bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '4' memory = '512' root= '/dev/xvda2 ro' disk= [ 'phy:/dev/mirrorset/test-disk,xvda2,w', 'phy:/dev/mirrorset/test-swap,xvda1,w', ] name= 'test' vif = [ 'ip=x.x.x.x,mac=00:16:3E:79:A1:CA' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash= 'restart' -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 08:57:29 UTC 2012 ** Command line: placeholder root=UUID=30110ed5-e675-4d0f-bf21-70dc8dbf56f2 ro quiet ** Not tainted ** Kernel log: [ 11.105098] ADDRCONF(NETDEV_UP): peth0: link is not ready [ 11.331582] block drbd0: recounting of set bits took additional 1 jiffies [ 11.331588] block drbd0: 1608 MB (411738 bits) marked out-of-sync by on disk bit-map. [ 11.331619] block drbd0: Marked additional 388 MB as out-of-sync based on AL. [ 11.723118] block drbd0: disk( Attaching - UpToDate ) [ 11.758719] block drbd0: conn( StandAlone - Unconnected ) [ 11.758760] block drbd0: Starting receiver thread (from drbd0_worker [1074]) [ 11.758841] block drbd0: receiver (re)started [ 11.758848] block drbd0: conn( Unconnected - WFConnection ) [ 11.758905] block drbd0: bind before connect failed, err = -99 [ 11.758979] block drbd0: conn( WFConnection - Disconnecting ) [ 11.956022] block drbd0: Discarding network configuration. [ 11.956081] block drbd0: Connection closed [ 11.956089] block drbd0: conn( Disconnecting - StandAlone ) [ 11.956134] block drbd0: receiver terminated [ 11.956138] block drbd0: Terminating drbd0_receiver [ 12.791332] e1000e: peth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 12.791337] e1000e :04:00.0: peth0: 10/100 speed: disabling TSO [ 12.792606] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready [ 13.238785] device peth0 entered promiscuous mode [ 13.251960] eth0: port 1(peth0) entering forwarding state [ 13.428648] ip_tables: (C) 2000-2006 Netfilter Core Team [ 23.320012] eth0: no IPv6 routers present [ 23.420007] peth0: no IPv6 routers present [ 68.750960] block drbd0: role( Secondary - Primary ) [ 78.075419] alloc irq_desc for 2251 on node -1 [ 78.075424] alloc kstat_irqs on node -1 [ 78.221963] alloc irq_desc for 2250 on node -1 [ 78.221967] alloc kstat_irqs on node -1 [ 78.255923] device vif4.0 entered promiscuous mode [ 78.259688] eth0: port 2(vif4.0) entering forwarding state [ 78.330986] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 78.331523] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 78.331526] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 78.331529] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 78.368947] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [ 80.539376] blkback: ring-ref 8, event-channel 23, protocol 1 (x86_64-abi) [ 80.539461] alloc irq_desc for 2249 on node -1 [ 80.539465] alloc kstat_irqs on node -1 [ 80.548719] blkback: ring-ref 768, event-channel 24, protocol 1 (x86_64-abi) [ 80.548738] alloc irq_desc for 2248 on node -1 [ 80.548741] alloc kstat_irqs on node -1 [ 80.562789] alloc irq_desc for 2247 on node -1 [ 80.562798] alloc kstat_irqs on node -1 [ 89.060028] vif4.0: no IPv6 routers present [ 90.548501] alloc irq_desc for 2246 on node -1 [ 90.548507] alloc kstat_irqs on node -1 [ 90.672853] alloc irq_desc for 2245 on node -1 [ 90.672859] alloc kstat_irqs on node -1 [ 90.711170] device vif5.0 entered promiscuous mode [ 90.714890] eth0: port 3(vif5.0) entering forwarding state [ 90.732431] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [
Bug#689429: vmxnet3 driver with package drops on ESXi 5.0
Package: linux-2.6 Version: 2.6.32-46 Severity: important Hello, first, I can not check, if Wheezy is also affected. Using ESXi 5.0 with Linux guests (in this case many amd64 Squeeze machines with three vmxnet3 adapter for each VM) could cause package drops, here especially on using UDP (name resolving). So I saw that some machines produced ~ 20 drops / day. This has been fixed by VMware last week: http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=2032587 Could you please adopt this fix for Squeeze (maybe also Wheezy)? Cheers -- 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/506af9a9.9040...@debian.org
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
Hi Michael, 2012/10/1 Michael Prokop m...@debian.org * Samuel Hym [Mon Oct 01, 2012 at 06:41:10PM +0200]: My disk is dm_crypted. After upgrading from 0.107 to 0.108, my system could not boot anymore with the newly generated ramfs: entering the passphrase did not unlock the disk, yielding the same error message as a wrong passphrase. Downgrading to 0.107 solved the problem. [...] What version of cryptsetup are you using? I'm using package version 2:1.4.3-2 but this might just be irrelevant since: Is there any visible difference between running update-initramfs -u -v for 0.107 and 0.108? Yes! With 0.107, I have a line: Adding binary /bin/loadkeys not with 0.108. What about differences between the generated initramfs (check e.g. with lsinitramfs /boot/initrd.img-$(uname -r))? Similarly, the diff is: --- /dev/fd/632012-10-02 17:26:29.136907406 +0200 +++ /dev/fd/622012-10-02 17:26:29.116907309 +0200 @@ -1,4 +1,4 @@ -/root/initrd.img-3.2.0-3-amd64-0.107 +initrd.img-3.2.0-3-amd64 . scripts scripts/functions @@ -955,7 +955,6 @@ bin/reboot bin/mkdir bin/nuke -bin/loadkeys bin/gunzip bin/umount bin/false @@ -990,7 +989,6 @@ etc/ld.so.conf etc/lvm etc/lvm/lvm.conf -etc/boottime.kmap.gz etc/modprobe.d etc/modprobe.d/blacklist-cups-usblp.conf etc/modprobe.d/alsa-base.conf Does setting KEYMAP=y in /etc/initramfs-tools/initramfs.conf help? No change. It was set to n, but there does not seem to make any difference, strangely enough. Regards Sam
Processed: Re: Bug#689433: base: Problem with edid checksum at boot sequence
Processing commands for cont...@bugs.debian.org: reassign 689433 linux Bug #689433 [base] base: Problem with edid checksum at boot sequence Bug reassigned from package 'base' to 'linux'. Ignoring request to alter found versions of bug #689433 to the same values previously set Ignoring request to alter fixed versions of bug #689433 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 689433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689433 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.13491929518756.transcr...@bugs.debian.org
Re: Bug#689433: base: Problem with edid checksum at boot sequence
reassign 689433 linux thanks On Dienstag, 2. Oktober 2012, geoffbou wrote: Package: base Severity: normal Dear Maintainer, I've got this at boot : drm error edid checksum is invalid 255 this repeats 4 or 5 times The system is starting correctly but there is this problem before I didn't found the good answer on google. I've got an intel graphic card -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201210021749.06079.hol...@layer-acht.org
Reassigning [was Cannot install on Intel Centrino Ultimate-N 6300 (802.11 a/b/g/n 3X3) Half Mini Card]
reassign 699416 firmware-iwlwifi thanks Reassigning to firmware-iwlwifi, not a CD-specific issue... -- Steve McIntyre, Cambridge, UK.st...@einval.com liw everything I know about UK hotels I learned from Fawlty Towers -- 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/20121002155316.ga25...@einval.com
Bug#575660: With last kernels, terminal/console processing getting worth.
On Sun, Sep 30, 2012 at 12:16:07PM -0700, Jonathan Nieder wrote: Hi Regid, In 2010, Regid Ichira wrote: 1) With 32-9, when tty1 shows the login prompt after boot, I can't see the characters that I type. I believe they are not processed as expected. This doesn't happen with 32-5. [...] An old AT (DIN5 connector) white colored keyboard. 01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) [...] By connecting over the network one can see that the i8042 interrupt counter does not go up. Do you still have access to this machine? If so, what kernel version are you using these days, and how does it behave? For some time now, the machine has problems with the display. Could be a bios setting issue, or some sort of a software problem. More likely there is one, or more, hardware failures. I am reluctened to make any tests or changes. -- 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/20121002174953.ga22...@mail.nt1.in
Bug#689433: drm error edid checksum is invalid 255
tags 689433 + moreinfo reassign 689433 src:linux 3.2.23-1 # cosmetic severity 689433 minor quit Hi Geoff, geoffbou wrote: I've got this at boot : drm error edid checksum is invalid 255 this repeats 4 or 5 times The system is starting correctly but there is this problem before I didn't found the good answer on google. I've got an intel graphic card Please attach output from reportbug --template linux-image-$(uname -r). Do you get the same message if you plug in a different monitor? Thanks for writing, 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/20121002183742.GA2902@elie.Belkin
Bug#684352: phy0/hp-wifi problems after kernel update from 2.6 to 3.2
Hi, 02.10.2012 17:28, David Smith kirjoitti: Hello, I'm having a problem with my Intel 2200 wireless on my Compaq Presario V4000T (made by HP) that has started happening after I upgraded my kernel from 2.6 to 3.2. Problem: phy0 wireless state is incorrect. Steps to reproduce problem: 1. Upgrade kernel from 2.6 to 3.2 2. rfkill now reports that I have two wireless devices but I only have the Intel 2200 wireless: Miho:/home/david# rfkill list all 0: hp-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes 3. The wireless simply doesn't work anymore because all software believes the wireless is blocked with a hardware switch, which is not the case. After many many hours of searching, I discovered that running rfkill unblock all is able to remove the Hard Block from phy0 and put the wireless into this state: Sounds like the hp-wifi soft block status affects phy0 hard block status. So if some management program softblocks hp-wifi, the phy0 will become hardblocked and the program doesn't understand that it needs to unblock hp-wifi again to undo what it just did. I have no idea what is the proper course of action here, though, but hopefully someone else on the lists has an idea. Miho:/home/david# rfkill unblock all Miho:/home/david# rfkill list all 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Miho:/home/david# However, I find that I have to keep dropping to a console and running sudo rfkill unblock all because the hardware keeps going back into the first state where phy0 is reporting that it is hard blocked, when it really isn't. Workaround #1: Set ACPI=off on 3.2 kernel. After which, the wireless appears to be correctly reported: Miho:/home/david# rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no This causes phy0 to accurately reflect the state of the hardware. Workaround #2: Add hp-wmi to modprobe blacklist. Again, this causes only phy0 wireless to be reported and phy0 always accurately reflects the state of the hardware (both soft and hard blocked). Expected Results; Both phy0 and hp-wifi refer to the same hardware device so they should accurately report the correct state of that hardware device. Actual Results: Phy0 reports it is hard blocked when there is no hard block on the wireless. Further, phy0 keeps going into this hard blocked state from regular usage of the wireless with networkmanager, while the hp-wmi does not. If I remove the hp-wmi then the phy0 works properly. When I have hp-wmi, then phy0's state is often incorrect. It seems there may be some conflict here between phy0 and hp-wmi. Kernel versions tested: linux-image-3.2.0-3-686-pae: Wireless regularly gets into this bad state of reporting it's hard blocked when it isn't. Unable to recover from it without using sudo rfkill unblock all. linux-image-2.6.32-5-686: No problem at all PCI registers from the only wireless device I have in this PC: Miho:/home/david# lspci -vv -s06:05.0 06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) Subsystem: Hewlett-Packard Company Device 12f5 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 128 (750ns min, 6000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 20 Region 0: Memory at c8206000 (32-bit, non-prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Kernel driver in use: ipw2200 Miho:/home/david# Somehow network manager is putting phy0 into a hard blocked state, but the hardware is not really hardblocked. After going into this hard blocked state, the wireless cannot be used anymore unless dropping to a console and running sudo rfkill unblock all which removes the hard block from phy0. Networkmanager alone is not able to bring the wireless back up. Also, sometimes when I turn on the PC, or resume from hibernate the rfkill reports phy0 as hard blocked, when it isn't. Which again, forces me to drop to console and run a sudo rfkill unblock all I am currently using Workaround #2 and am very happy with it. The wireless no longer goes into hard blocked through normal usage of the hardware with network manager. Thank you for your time. -- Anssi Hannula -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe.
Processed: Re: drm error edid checksum is invalid 255
Processing commands for cont...@bugs.debian.org: tags 689433 + moreinfo Bug #689433 [linux] base: Problem with edid checksum at boot sequence Added tag(s) moreinfo. reassign 689433 src:linux 3.2.23-1 Bug #689433 [linux] base: Problem with edid checksum at boot sequence Bug reassigned from package 'linux' to 'src:linux'. Ignoring request to alter found versions of bug #689433 to the same values previously set Ignoring request to alter fixed versions of bug #689433 to the same values previously set Bug #689433 [src:linux] base: Problem with edid checksum at boot sequence Marked as found in versions linux/3.2.23-1. # cosmetic severity 689433 minor Bug #689433 [src:linux] base: Problem with edid checksum at boot sequence Severity set to 'minor' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 689433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689433 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.134920307323388.transcr...@bugs.debian.org
Bug#677457: no audio via HDA-Intel VIA VT1705 on speakers
in-line :- On Sun, Sep 30, 2012 at 6:56 AM, Jonathan Nieder jrnie...@gmail.com wrote: shirish शिरीष wrote: Ok, thanks. Can you reproduce this with aplay from alsa-utils (pausing by suspending with ^Z, resuming with fg)? Does mplayer have the same problem (press space to pause)? with aplay I was not able to suspend it with CTL+Z, it seems that kills but then I'm using guake. So either it is an issue with guake or an issue with aplay or both, dunno but that's something for another day. In vlc I have seen the bug manifest all the times whenever I have paused the movie/moving picture and then played again, just no audio. I've experienced pause/resume flakiness in vlc before, so hopefully we can find a way to reproduce this with another media player. Aha, it's a pause/resume flakiness in vlc. I tried it with a bunch of media players and they played, paused and replayed videos without an issue so definitely can be nailed down to vlc. So all in all, I guess we can treat this bug as closed. Jonathan -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- 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/CADdDZRmFqa8qO�qH=v3kyhmb2ftmklf6h7fz4miatmbfs...@mail.gmail.com
Bug#679545: ia64, SR870, EFI bug breaks ata_piix, uninitialized ICH4 IDE EXBAR mem resource
Thanks a lot for testing this! I'll fix up this typo and work on getting something like this merged. Thank you very much! If you want me to test anything, don't hesitate to contact me. What's the output of dmesg | grep :00:1f.1; lspci -vs00:1f.1? [0.065506] pci :00:1f.1: [8086:24cb] type 0 class 0x000101 [0.065520] pci :00:1f.1: reg 10: [io 0x-0x0007] [0.065531] pci :00:1f.1: reg 14: [io 0x-0x0003] [0.065542] pci :00:1f.1: reg 18: [io 0x-0x0007] [0.065553] pci :00:1f.1: reg 1c: [io 0x-0x0003] [0.065564] pci :00:1f.1: reg 20: [io 0x1000-0x100f] [0.065575] pci :00:1f.1: reg 24: [mem 0x-0x03ff unset] [1.415250] ata_piix :00:1f.1: version 2.13 [1.415276] ata_piix :00:1f.1: can't derive routing for PCI INT A 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corporation Device 3404 Flags: bus master, medium devsel, latency 0 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at 1000 [size=16] Kernel driver in use: ata_piix Stephan -- 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/20121002214859.horde.wgw4bbuwis5qa0ur8afh...@webmail.df.eu
Processed: Re: [3.2.18-1 - 3.2.19-1 regression] no audio via HDA-Intel VIA VT1705 on speakers
Processing commands for cont...@bugs.debian.org: tags 677457 - moreinfo Bug #677457 [src:linux] linux-image-3.2.0-2-amd64: no audio via HDA-Intel VIA VT1705 on speakers Bug #676652 [src:linux] pulseaudio: no audio on the system after some upgrades Removed tag(s) moreinfo. Removed tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 676652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676652 677457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677457 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.134921068715834.transcr...@bugs.debian.org
Bug#676652: marked as done (pulseaudio: no audio on the system after some upgrades)
Your message dated Tue, 2 Oct 2012 13:44:31 -0700 with message-id 20121002204431.GB2902@elie.Belkin and subject line Re: [3.2.18-1 - 3.2.19-1 regression] no audio via HDA-Intel VIA VT1705 on speakers has caused the Debian Bug report #677457, regarding pulseaudio: no audio on the system after some upgrades 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.) -- 677457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pulseaudio Version: 2.0-3 Severity: important Dear Maintainer, After some updates in Debian sid from yesterday I am having no audio. Pulseaudio -v -v -v gives this :- $ pulseaudio -v -v -v I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us. D: [pulseaudio] core-util.c: RealtimeKit worked. I: [pulseaudio] core-util.c: Successfully gained nice level -11. I: [pulseaudio] main.c: This is PulseAudio 2.0 D: [pulseaudio] main.c: Compilation host: x86_64-pc-linux-gnu D: [pulseaudio] main.c: Compilation CFLAGS: -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wextra -pipe -Wno-long-long -Wvla -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -Wp,-D_FORTIFY_SOURCE=2 -fno-common -fdiagnostics-show-option D: [pulseaudio] main.c: Running on host: Linux x86_64 3.2.0-2-amd64 #1 SMP Fri Jun 1 17:49:08 UTC 2012 D: [pulseaudio] main.c: Found 2 CPUs. I: [pulseaudio] main.c: Page size is 4096 bytes D: [pulseaudio] main.c: Compiled with Valgrind support: no D: [pulseaudio] main.c: Running in valgrind mode: no D: [pulseaudio] main.c: Running in VM: no D: [pulseaudio] main.c: Optimized build: yes D: [pulseaudio] main.c: FASTPATH defined, only fast path asserts disabled. I: [pulseaudio] main.c: Machine ID is 8a2df75f821ad3f8f720c07c0007. I: [pulseaudio] main.c: Session ID is 8a2df75f821ad3f8f720c07c0007-1339125835.366722-88359475. I: [pulseaudio] main.c: Using runtime directory /home/shirish/.pulse/8a2df75f821ad3f8f720c07c0007-runtime. I: [pulseaudio] main.c: Using state directory /home/shirish/.pulse. I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-2.0/modules. I: [pulseaudio] main.c: Running in system mode: no E: [pulseaudio] pid.c: Daemon already running. E: [pulseaudio] main.c: pa_pid_file_create() failed. Please lemme know if any info. is needed. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu3 ii consolekit0.4.5-3 ii libasound21.0.25-3 ii libasound2-plugins1.0.25-2 ii libc6 2.13-33 ii libcap2 1:2.22-1.1 ii libdbus-1-3 1.6.0-1 ii libfftw3-33.3.2-1 ii libgcc1 1:4.7.0-12 ii libice6 2:1.0.8-2 ii libltdl7 2.4.2-1 ii liborc-0.4-0 1:0.4.16-2 ii libpulse0 2.0-3 ii libsamplerate00.1.8-4 ii libsm62:1.2.1-2 ii libsndfile1 1.0.25-4 ii libspeexdsp1 1.2~rc1-6 ii libstdc++64.7.0-12 ii libsystemd-daemon044-2 ii libsystemd-login0 44-2 ii libtdb1 1.2.10-2 ii libudev0 175-3.1 ii libwebrtc-audio-processing-0 0.1-2 ii libx11-6 2:1.4.99.901-2 ii libx11-xcb1 2:1.4.99.901-2 ii libxcb1 1.8.1-1 ii libxtst6 2:1.2.1-1 ii lsb-base 4.1+Debian6 ii udev 175-3.1 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.31-3
Bug#677457: marked as done (linux-image-3.2.0-2-amd64: no audio via HDA-Intel VIA VT1705 on speakers)
Your message dated Tue, 2 Oct 2012 13:44:31 -0700
with message-id 20121002204431.GB2902@elie.Belkin
and subject line Re: [3.2.18-1 - 3.2.19-1 regression] no audio via HDA-Intel
VIA VT1705 on speakers
has caused the Debian Bug report #677457,
regarding linux-image-3.2.0-2-amd64: no audio via HDA-Intel VIA VT1705 on
speakers
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.)
--
677457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src
Version: 3.2.20-1
Severity: important
Dear Maintainer,
First of all thank you everybody for all your hard work. Please CC me
if somebody answers me. After update to linux-image-3.2.0-2-amd64 I am
not able to hear audio. First I thought it was a pulseaudio bug hence
filed #676652 for pulseaudio. Then talking with people on IRC I
removed all instances of pulseaudio as well as jack and arts to the
extent that only one library remains, libjack-jackd2-0 . I don't wanna
remove that as around 400 MB of packages woudld also get removed
or/and purged. I have to say though that I'm not sure if it's JUST the
kernel image at fault or alsa too at fault as both of them were
upgraded recently. I had audio for almost 2 years without issue (on
Sid) and went off around a week back.
Warning :- This is gonna be a long and maybe a little winded
bug-report so sorry in advance.
This is the device list :-
$ aplay -l
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: VT1705 Analog [VT1705 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 2: VT1705 HP [VT1705 HP]
Subdevices: 1/1
Subdevice #0: subdevice #0
Then tried playing it on the system :-
$ aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav
aplay: main:682: audio open error: Device or resource busy
I have no ~/.asoundrc file as well /etc/asound.conf which could
interfere with anything.
This is the output of cat /etc/modprobe.d/alsa-base.conf :-
$cat /etc/modprobe.d/alsa-base.conf
cat: cat: No such file or directory
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd { /sbin/modprobe
--quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi {
/sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 {
/sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
alsa-blacklist has this in it :-
/etc/modprobe.d$ cat alsa-base-blacklist.conf
# Uncomment these entries in order to blacklist unwanted modem drivers
# blacklist snd-atiixp-modem
# blacklist snd-intel8x0m
# blacklist snd-via82xx-modem
# Comment this entry in order to load snd-pcsp driver
blacklist snd-pcsp
Now the most interesting thing is in my /var/log/boot
Thu Jun 14 10:00:49 2012: [] Setting up ALSA...warning: 'alsactl
restore' failed with error message 'Found hardware: HDA-Intel VIA
VT1705 HDA:11064397,104383a1,0010 0x1043 0x83a1
Thu Jun 14 10:00:49 2012: Hardware is initialized using a generic method
Thu Jun 14 10:00:49 2012: alsactl: set_control:1328: failed to obtain
info for control #32 (No such file or directory)
Thu Jun 14 10:00:49 2012: alsactl: set_control:1328: failed to obtain
info for control #33 (No such file or directory)
Thu Jun 14 10:00:49 2012: alsactl: set_control:1328: failed to obtain
info for control #34 (No such file or directory)
Thu Jun 14 10:00:49 2012: alsactl: set_control:1328: failed to obtain
info for control #35 (No such file or directory)
Thu Jun 14 10:00:49 2012: alsactl: set_control:1328: failed to obtain
info for control #36 (No such file or
directory)'...^[[?25l^[[?1c^[7^[[1G[^[[32m ok
^[[39;49m^[8^[[?25h^[[?0cdone.
Thu Jun 14 10:00:49 2012: [^[[36minfo^[[39;49m]
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Jonathan Nieder a écrit : Presumably removing and replugging the mouse doesn't help. No. Does unloading and reloading the USB driver (modprobe -r ehci_hcd modprobe ehci_hcd) have any effect? I never tried it. I will test it the next time. Did these machines always behave this way, or is this a regression? Is the 2.6.32.y kernel from squeeze also affected? It is not a regression, I encountered this bug from the first day. If I am not mistaken, I can not try 2.6 Linux kernel because the Ivy Bridge chipset is supported starting from 3.2 Linux kernel. Sébastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- 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/20121002213239.ga9...@dinot.net
Bug#669314: NFS: kernel forces trailing slash for export in /proc/self/mounts
I haven't had a chance to test it yet thanks. I'll be too busy until at least mid-next week, but I will test it then if nobody beats me to it. -Chris On Sep 30, 2012, at 2:23 PM, Jonathan Nieder jrnie...@gmail.com wrote: Thanks for looking it over. Did you get a chance to test Ben's patch? Curious, Jonathan smime.p7s Description: S/MIME cryptographic signature
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Jonathan Nieder a écrit : Does unloading and reloading the USB driver (modprobe -r ehci_hcd modprobe ehci_hcd) have any effect? Good point! Keyboard and mouse work again after these commands. Once again, I found the following event in the kern.log file: Oct 3 01:11:33 hector kernel: [ 4016.352234] usb 2-1.5: USB disconnect, device number 10 Oct 3 01:11:33 hector kernel: [ 4016.558658] usb 2-1.5: new low-speed USB device number 11 using ehci_hcd Oct 3 01:11:33 hector kernel: [ 4016.657061] usb 2-1.5: New USB device found, idVendor=045e, idProduct=00a4 Oct 3 01:11:33 hector kernel: [ 4016.657066] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 3 01:11:33 hector kernel: [ 4016.657069] usb 2-1.5: Product: Microsoft(R) Compact Optical Mouse Oct 3 01:11:33 hector kernel: [ 4016.657071] usb 2-1.5: Manufacturer: Microsoft Oct 3 01:11:33 hector kernel: [ 4016.662142] input: Microsoft Microsoft(R) Compact Optical Mouse as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input19 Oct 3 01:11:33 hector kernel: [ 4016.662536] hid-generic 0003:045E:00A4.0009: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft(R) Compact Optical Mouse] on usb-:00:1d.0-1.5/input0 And the freeze occured at 01:11:33 (more or less few seconds by my watch). Sébastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- 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/20121002233236.ga5...@dinot.net
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Sébastien Dinot wrote: Good point! Keyboard and mouse work again after these commands. Yay. Ok, one more test and then we should take this upstream: if you set the usbcore.autosuspend parameter to -1, does that change anything? # modprobe -r ehci_hcd; # or unplug mouse # echo -1 /sys/module/usbcore/parameters/autosuspend # modprobe ehci_hcd; # or replace mouse Either way, please send a summary to linux-...@vger.kernel.org, cc-ing Alan Stern st...@rowland.harvard.edu, linux-in...@vger.kernel.org, and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough) - which kernels you have tested and what happened with each - how reproducible it is and how long it takes (e.g., within a couple of hours 80% of the time?) - full dmesg output from booting and reproducing it, as an attachment or link - a link to http://bugs.debian.org/689368 for the backstory - any other weird symptoms or observations If we're lucky, someone upstream will have ideas for commands or patches to try to further track down the cause. Thanks again for your help and patience. Good luck, 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/20121003002407.GD5946@elie.Belkin
Bug#575660: marked as done (With last kernels, terminal/console processing getting worse)
Your message dated Tue, 2 Oct 2012 18:26:19 -0700 with message-id 20121003012619.GH5946@elie.Belkin and subject line Re: With last kernels, terminal/console processing getting worth. has caused the Debian Bug report #575660, regarding With last kernels, terminal/console processing getting worse 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.) -- 575660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-source-2.6.32 Version: 2.6.32-9 Severity: normal I am making my own kernels out of Debian's linux-source. I upgraded the source from 32-5 to 32-9. I have added a few more kernel modules with 32-9. I believe the config diff is not relevant for this report. 1) With 32-9, when tty1 shows the login prompt after boot, I can't see the characters that I type. I believe they are not processed as expected. This doesn't happen with 32-5. 2) I am using /etc/console-tools/config to get the terminal into BLANK_DPMS=powerdown. With both 32-5 and 32-9, pressing anything on the keyboard doesn't seem to get the terminal out of BLANK_DPMS=powerdown mode. In the past it did work as expected. I can not tell from which kernel version the problem is apparent. 3) Also with both 32-5 and 32-9, the shutdown command doesn't take the screen out of BLANK_DPMS=powerdown mode. So nothing is displayed on the screen when the system goes down. It was not like that in the past. I can't tell from which kernel version the problem emerged. _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969 ---End Message--- ---BeginMessage--- Regid Ichira wrote: In 2010, Regid Ichira wrote: By connecting over the network one can see that the i8042 interrupt counter does not go up. [...] For some time now, the machine has problems with the display. Could be a bios setting issue, or some sort of a software problem. More likely there is one, or more, hardware failures. I am reluctened to make any tests or changes. No problem. Closing for now, but if you get more information I'd be happy to look into this one again. Regards, Jonathan---End Message---
Processed: reassign 688920 to src:linux, tagging 688920, tagging 688920
Processing commands for cont...@bugs.debian.org: reassign 688920 src:linux Bug #688920 [linux-source] [linux-source] CONFIG_RT2500USB description confusing about target Bug reassigned from package 'linux-source' to 'src:linux'. No longer marked as found in versions 3.5.2-1~experimental.1. Ignoring request to alter fixed versions of bug #688920 to the same values previously set tags 688920 - fixed-upstream Bug #688920 [src:linux] [linux-source] CONFIG_RT2500USB description confusing about target Removed tag(s) fixed-upstream. tags 688920 + wontfix Bug #688920 [src:linux] [linux-source] CONFIG_RT2500USB description confusing about target Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 688920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688920 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.13492287864.transcr...@bugs.debian.org
Bug#607242: psmouse: mitigate failing-mouse symptoms
On 09/30/2012 11:02 AM, Alessandro Rubini wrote:
I think this would be less controversial if the run-time default were
to disable the feature.
Yes, that's the common sensible path
Fixed, there's no way I can test it well enough for anything more widespread.
Then, I think it would be good to have a specific sub-structure for
this stuff.
I don't care much either way, though I think I'm missing the point of subbing
in a memset -- only reason I can think of is efficiency which doesn't make
sense to me here. Ask and I'll add one or both.
I also think it would make it clearer what these are:
I did de-jargonize the names some, interval_start for base makes it
clearer which as you say it could use.
I encountered one other person with this problem and he ran it for a long while
and was happy to have it. I'm appending the latest version, which is a good
bit improved and what I've been running for the last year amended with the name
and default-filter changes above.
But of course I upgraded a month ago to a box with no PS/2 mouse port, so at
this point all I can do is hope someone finds it helpful. The reorg'd code
kinda highlights how incomplete it is, there's lots of mouse models out there.
So if it looks good or almost-good to you and there's anything else I can do,
tell me and I'll be glad to do it.
Thanks,
Jim
From 2681957a610191cb5d7b7f65be11ea2be06df00f Mon Sep 17 00:00:00 2001
From: Jim Hill gjth...@gmail.com
Date: Mon, 28 Mar 2011 13:10:36 -0700
Subject: [PATCH] Input: psmouse - further improve error handling for
basic protocols
Keep a failing PS/2 mouse usable until it's convenient to replace it.
Filter incoming packets: drop invalid ones and attempt to correct for
dropped bytes.
New parameter 'filter' makes filtering and logging selectable, leave at 0
to shut off all effects, 3 to work silently.
--
drivers/input/mouse/psmouse-base.c | 197 +
drivers/input/mouse/psmouse.h | 7 ++
2 files changed, 204 insertions(+)
diff --git a/drivers/input/mouse/psmouse-base.c
b/drivers/input/mous/psmouse-base.c
index 22fe254..4a3a95f 100644
--- a/drivers/input/mouse/psmouse-base.c
+++ b/drivers/input/mouse/psmouse-base.c
@@ -72,6 +72,25 @@ static unsigned int psmouse_resync_time;
module_param_named(resync_time, psmouse_resync_time, uint, 0644);
MODULE_PARM_DESC(resync_time, How long can mouse stay idle before forcing
resync (in seconds, 0 = never).);
+enum {
+ DROP_BAD_PACKET = 1,
+ ATTEMPT_SYNC = 2,
+ LOG_SUMMARIES = 4,
+ LOG_MALFORMED = 8,
+ LOG_ALL = 16,
+ REPORT_SYNC_FAILURE = 32,
+
+ DEFAULT_FILTER = 0
+};
+static int psmouse_filter = DEFAULT_FILTER;
+module_param_named(filter, psmouse_filter, int, 0644);
+MODULE_PARM_DESC(filter, 1 = drop invalid or hotio packets
+ , +2 = attempt-sync
+ , +4 = summary logs
+ , +8 = log-malformed
+ ,+16 = log-all
+ ,+32 = use hard resets);
+
PSMOUSE_DEFINE_ATTR(protocol, S_IWUSR | S_IRUGO,
NULL,
psmouse_attr_show_protocol, psmouse_attr_set_protocol);
@@ -123,6 +142,169 @@ struct psmouse_protocol {
};
/*
+ * psmouse_filter_*: diagnose bad data, recover what we can, drop the rest, log
+ * selected events. See input_report_*()s in psmouse_process_byte below, and
+ * http://www.computer-engineering.org/ps2mouse/
+ */
+
+static int psmouse_filter_header_byte(enum psmouse_type type, int byte)
+{
+ int todo = 0;
+ if ((byte 0xc0)
+ type != PSMOUSE_THINKPS
+ type != PSMOUSE_GENPS)
+ todo |= DROP_BAD_PACKET+ATTEMPT_SYNC;
+ if ((byte 0x08) == 0
+ type != PSMOUSE_THINKPS
+ type != PSMOUSE_CORTRON)
+ todo |= DROP_BAD_PACKET+ATTEMPT_SYNC;
+ return todo;
+}
+
+static int psmouse_filter_wheel_byte(enum psmouse_type type, int byte)
+{
+ int todo = 0;
+ if (type == PSMOUSE_IMPS || type == PSMOUSE_GENPS)
+ if (abs(byte) 3)
+ todo = DROP_BAD_PACKET+ATTEMPT_SYNC;
+ if (type == PSMOUSE_IMEX)
+ if (((byte0xC0) == 0) || ((byte0XC0) == 0xC0))
+ if (abs((byte0x08)-(byte0x07)) 3)
+ todo = DROP_BAD_PACKET+ATTEMPT_SYNC;
+ return todo;
+}
+
+static int psmouse_filter_motion(struct psmouse *m)
+{ /*
+* Hunt for implausible accelerations here if it ever seems necessary.
+* Header/wheel sniffing seems to detect everything recoverable so far.
+*/
+ return 0;
+}
+
+static int psmouse_filter_hotio(struct psmouse *m)
+{
+ int ret = 0;
+ if (time_after(m-last, m-hotio_interval_start + HZ/m-rate)) {
+ m-hotio_interval_pkts = 0;
+ m-hotio_interval_start = m-last;
+ }
+ if (m-hotio_interval_pkts++ m-rate/HZ + 1) {
+
