Bug#679519: Suddenly unable to replicate problem (Re: usbhid causes crashes in applications by memory corruption)

2012-07-25 Thread Steve Graham
The laptop (Samsung NC110) which had this problem no longer has it, for no obvious reason. The kernel is unchanged. The one difference is that I was trying to boot a Knoppix installation from USB stick to see if it also had the usb problem and when the laptop couldn't see the device, I

Bug#679519: Suddenly unable to replicate problem (Re: usbhid causes crashes in applications by memory corruption)

2012-07-25 Thread Steve Graham
If you came here through an Internet search and are having similar problems, upgrading my kernel to a custom-compiled 3.5.0 seems to have fixed iwlwifi, provided the module has the following options: options iwlwifi 11n_disable=1 wd_disable=1 swcrypto=1 power_save=0 5ghz_disable=1 Development

Bug#679519: Problem still occurs in linux-3.4-trunk-amd64 from Debian experimental (Re: usbhid causes crashes in applications by memory corruption)

2012-07-09 Thread Steve Graham
And did you plug in a new HID device? Yes. Just to be clear, nothing untoward happens with usbhid.ko simply loaded, e.g directly via modprobe or automagically when a device is plugged in. But the first event, be it a mouse movement or a keystroke, causes particular applications to crash. I've

Bug#679519: unable to obtain better info (Re: usbhid causes crashes in applications by memory corruption))

2012-07-02 Thread Steve Graham
After building a kernel with X86_CHECK_BIOS_CORRUPTION enabled, I set it to scan (almost) as advised. No corruption of the low memory was reported after running some hours either with or without usbhid loaded. (Booting with memory_corruption_check_size=640K caused an immediate kernel panic --

Bug#679519: linux-image-3.2.0-3-rt-amd64: usbhid causes crashes in applications by memory corruption

2012-06-29 Thread Steve Graham
Package: src:linux Version: 3.2.21-2 X-Mailer: reportbug 4.12.6 Date: Fri, 29 Jun 2012 11:26:06 +0100 Severity: normal Tags: upstream When I plug in a USB mouse (or keyboard, but I don't normally do that) into this laptop, the first event -- mouse movement -- causes some applications to crash

Bug#679519: same on non-RT kernel (Re: usbhid causes crashes in applications by memory corruption)

2012-06-29 Thread Steve Graham
Is that a standard (non-realtime) kernel? If not, can you also test a standard kernel configuration (linux-image-3.2.0-3-amd64)? Identical behaviour on linux-image-3.2.0-3-amd64 Please try booting with the extra kernel parameters: memory_corruption_check=1

Bug#668616: workaround by reverting /usr/share/initramfs-tools/hook-functions to 0.99

2012-06-02 Thread Steve Graham
I copied /usr/share/initramfs-tools/hook-functions from a machine which had not been updated and this allowed update-initramfs to build a new, bootable ramdisk. Note For Googlers: I believe that the closed bug 659948 is a duplicate of this one, and it suggests ln -s / /rootfs as a workaround.

Bug#665881: Fix available in latest kernel. (Re: ath5k reports gain calibration timeout errors and loses connectivity)

2012-04-10 Thread Steve Graham
Replacing the ath5k driver code with the updated code from Linux 3.4-rc1 fixes this problem for me. (Specifically drivers/net/wireless/ath/ath5k/ath5k.h, base.c and phy.c - nothing else changed from 3.3.0) On 02/04/12 14:36, Debian Bug Tracking System wrote: Thank you for the additional

Bug#665881: not Debian-specific

2012-04-01 Thread Steve Graham
I have just compiled a custom 3.3.0 kernel for an Acer netbook, previously running 3.0.0, and see the same problem as reported by Hans. In my case, after 36 hours of uptime with the new kernel, the ath5k began to report constant gain calibration timeout errors and connectivity was lost.

Bug#627933: Regression: hot plugging sdhc card on Acer Aspire One

2011-08-05 Thread Steve Graham
I can confirm the same behaviour on the same hardware with kernel 3.0.0-1-686-pae from unstable. (In the workaround situation of booting with a card in the right-hand slot, everything works as expected: both cards can be inserted and ejected and generate the expected udev events.