Bug#1001805: linux-image-5.10.0-9-amd64: Permanent blinking of wireless led

[Hans-J. Ullrich]

Package: linux-image-5.10.0-9-amd64
Version: 5.10.70-1
Severity: normal

Dear Maintainer,


with the latest kernel version (change from *-8-amd64 to *-9-amd64 and higher), 
I discovered an annoying issue.
This issue shows, that the wireless led is permanently blinking, but it should 
only blink, when real traffic is 
received. 

Examination showed, that the permanent blinking is caused by the router (it is 
a Fritz!Box), which is permanently
sending brodcast traffic. However, the indication of broadcast traffic with the 
led was suppressed in kernels with version -8-amd64 and lower, and only "real" 
traffic was indicated by the led.

Behaving this way, the led indication is very useful, as normal traffic will 
let the led blink during traffic I know I had initiated (like calling a 
website). Permanently blinking showed, something fishy is going on and I should 
examine it: Is a download/update running? Is there a large mail coming? Does 
someone have access to my system? Is there a bruteforce attack ongoing? 

So, this function is really important for me, and I would like to have it back. 
At the moment I am staying with kernel *-8-amd64. Please note, I saw this on 
kali linux, too.

I believe, this issue is in the atheros module (I am using an AR542x Wireless 
card), and the module is ath5.ko.

If this is really an issue in this module, please take a look at the ath9.ko 
module, maybe the same issue appears there, too.

It would be very nice, if you could take a look at this. Please feel free, to 
ask for more information. 

Network dumps or whatever can be delivered, if needed.

Thank you very much for reading this and any help.

Best regards

Hans
 
 
-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.10.0-9-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod28-1
ii  linux-base  4.6

Versions of packages linux-image-5.10.0-9-amd64 recommends:
ii  apparmor 2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-9-amd64 suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii  grub-pc 2.04-20
pn  linux-doc-5.10  

Bug#998173: linux-image-5.10.0-9-amd64: with kernel version 5.10.0-9-amd64 LED is permanently blinking

[Hans-J. Ullrich]

Package: linux-image-5.10.0-9-amd64
Severity: normal

Dear Maintainer,

with the upgrade from kernel version 5.10.0-8-amd64 to version 0-9-amd64 I 
notice a very annoying issue with my wireless card.

Problem is, the LED is permanently blinking, not (as it was with the former 
kernel) when there is real trffic.

The kernel module which is responsible for that, is ath5k.ko (This is an 
Atheros card)
Normally the wireless LED only blinks, when there is real traffic aimed to my 
IP. 
However, with 0-9- the LED is permanently blinking. 

I could verify, that it is no traffic created by the notebook itself (used 
tcpdump) and killed all network processes (daemons/apps whatever) running on 
the system.

But even when there were no processes running except the one needed for the 
connection with the router, the LED kept on blinking.

Further investigation showed, that the blinking appeared due to the broadcast 
packages sent by the router. The wireless card thinks, this is normal traffic 
and the LED blinks.

This is bad for me, as the LED was in the past often a good sign, when 
soemthing fishy is going on. If the LED is only blinking from time to time, 
everything is ok, but when it was blinking som,ething special is going on 
(i.e. an update is running or freshclam is updating, but also some brute force 
attacks could also be discovered.) 

It would be nice, if you could examine, what has changed at the new kernel, and 
I would be happy, when I 
could get the old behaviour back.

At the moment I reverted back to kernel 5.10.0-8-0*, which is running perfectly.

Thank you very much for all the help!

Best regards

Hans


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#988300: linux-kbuild-5.10: can not build nvidia-kernel-340xx-dkms

[Hans-J. Ullrich]

Package: linux-kbuild-5.10
Version: 5.10.28-1
Severity: important

Dear Maintainer,

I am not quite sure, but I believe, there is a problem with either 
linux-kbuild-5.10 or the nvidia-kernel-340xx-dkms.

The problem is, that the build of the kernel module stops and the make.log says 
the following:

--- snip ---

make[3]: Verzeichnis „/usr/src/linux-headers-5.10.0-6-amd64“ wird betreten
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
make -f /usr/src/linux-headers-5.10.0-6-common/scripts/Makefile.build obj=.. \
single-build= \
need-builtin=1 need-modorder=1
/usr/src/linux-headers-5.10.0-6-common/scripts/Makefile.build:44: 
/usr/src/linux-headers-5.10.0-6-common/../Makefile: Datei oder Verzeichnis 
nicht gefunden
make[4]: *** Keine Regel, um 
„/usr/src/linux-headers-5.10.0-6-common/../Makefile“ zu erstellen.  Schluss.
make[3]: *** [/usr/src/linux-headers-5.10.0-6-common/Makefile:1822: ..] Fehler 2
make[3]: Verzeichnis „/usr/src/linux-headers-5.10.0-6-amd64“ wird verlassen
make[2]: *** [Makefile:185: __sub-make] Fehler 2
make[2]: Verzeichnis „/usr/src/linux-headers-5.10.0-6-common“ wird verlassen
make[1]: *** [Makefile:205: nvidia.ko] Fehler 2
make[1]: Verzeichnis „/var/lib/dkms/nvidia-legacy-340xx/340.108/build“ wird 
verlassen
make: *** [Makefile:221: ../Module.symvers] Fehler 2
make: Verzeichnis „/var/lib/dkms/nvidia-legacy-340xx/340.108/build/uvm“ wird 
verlassen
  
1124,1  
--- snap 

This issue happened, when I deinstalled and reinstalled all the nvidia-packages.

Please note: It was possible before to build the nvidia-module for a 
5.10-version, but this was a prior version before 5.10.0-6-amd64 (maybe 
5.10.0-4-amd64 or similar).

On kernel version 4.19.0-16-amd64 the module can be build, but this is another 
linux-kbuild-version!

Thus and because of the make.log I believe, linux-kbuild-5.10 might be buggy.

Thank you for reading this and any help.

Best regards

Hans
 

 





-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-kbuild-5.10 depends on:
ii  libc6  2.31-11
ii  libelf10.183-1
ii  libssl1.1  1.1.1k-1

linux-kbuild-5.10 recommends no packages.

linux-kbuild-5.10 suggests no packages.

-- debconf-show failed

Bug#977262: linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more

[Hans-J. Ullrich]

Package: src:linux
Version: 5.9.9-1
Severity: important

Dear Maintainer,

when upgrading from linux-image-5.9.0-3-amd64 to *-5.9.0-4-amd64 and its 
headers, it is not 
possible to build the required kernel module for the nividia-packages. This 
includes latest legacy versions "340xx" as well as "390xx". 

So it is not possible, to use hardware acceleration with graphic cards which 
need these packages.

I believe, the problem is kernel related, as the nvidia-packages were not 
updated and they still build fine on linux-image-5.9.0-3-amd64 (the version, I 
am running at the moment).

It would be nice, if you could take a lokk at that, as I believe, there are 
lots of hardware like notebooks, where you can not exchange the graphics card 
easily, if not at all.

Thank you very much for any help!

Best regards

Hans



-- Package-specific info:
** Version:
Linux version 5.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.9.0-3-amd64 
root=UUID=ad01422d-da21-4b7f-ad9e-ce6c459ca494 ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Acer
product_name: Aspire 7520G
product_version: V1.32
chassis_vendor: Acer
chassis_version: N/A
bios_vendor: Acer
bios_version: V1.33
board_vendor: Acer
board_name: Fuquene
board_version: N/A

** Loaded modules:
xfrm_user
xfrm_algo
l2tp_ppp
l2tp_netlink
l2tp_core
ip6_udp_tunnel
udp_tunnel
pppox
ppp_generic
slhc
cmac
ctr
ccm
nf_tables
nfnetlink
cpufreq_conservative
uinput
binfmt_misc
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
mc
ath5k
snd_hda_codec_hdmi
ath
mac80211
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
edac_mce_amd
kvm_amd
snd_hda_intel
ccp
snd_intel_dspcfg
snd_hda_codec
rng_core
snd_hda_core
kvm
joydev
cfg80211
irqbypass
snd_hwdep
snd_pcm_oss
snd_mixer_oss
serio_raw
r852
pcspkr
sm_common
snd_pcm
libarc4
wmi_bmof
nand
k8temp
ir_rc6_decoder
snd_timer
nand_ecc
bch
nandcore
snd
sg
rc_rc6_mce
mtd
r592
memstick
soundcore
ene_ir
evdev
rc_core
ac
button
analog
gameport
isofs
acer_wmi
sparse_keymap
rfkill
vboxvideo
drm_vram_helper
drm_ttm_helper
ttm
drm_kms_helper
cec
nvidia(POE)
usbnet
mii
cpufreq_userspace
cpufreq_ondemand
cpufreq_powersave
powernow_k8
parport_pc
ppdev
lp
parport
loop
drm
fuse
sunrpc
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
ecb
aes_generic
libaes
crypto_simd
cryptd
glue_helper
lrw
gf128mul
algif_skcipher
af_alg
dm_crypt
dm_mod
hid_generic
usbhid
hid
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
crct10dif_common
sr_mod
cdrom
ata_generic
ahci
pata_amd
libahci
ohci_pci
libata
ohci_hcd
psmouse
ehci_pci
ehci_hcd
firewire_ohci
sdhci_pci
usbcore
cqhci
scsi_mod
sdhci
firewire_core
mmc_core
crc_itu_t
forcedeth
usb_common
i2c_nforce2
battery
wmi
video

** PCI devices:
00:00.0 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller 
[10de:0547] (rev a2)
Subsystem: Acer Incorporated [ALI] MCP67 Memory Controller [1025:0126]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP67 ISA Bridge [10de:0548] (rev 
a2)
Subsystem: Acer Incorporated [ALI] MCP67 ISA Bridge [1025:0126]
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- 
Kernel driver in use: nForce2_smbus
Kernel modules: i2c_nforce2

00:01.2 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller 
[10de:0541] (rev a2)
Subsystem: NVIDIA Corporation MCP67 Memory Controller [10de:cb84]
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- 
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci

00:02.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller 
[10de:055f] (rev a2) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] MCP67 EHCI USB 2.0 Controller 
[1025:0126]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:04.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller 
[10de:055e] (rev a2) (prog-if 10 [OHCI])
Subsystem: Acer 

Bug#971951: linux-image-5.8.0-2-amd64: Touchpad module is deinitialized when running plasma5

[Hans-J. Ullrich]

Package: src:linux
Version: 5.8.10-1
Severity: important

Dear Maintainer,

I discovered an issue since the last update with the touchpad of my notebook. 
It is a Synaptic touchpad and as I believe, the 
touchpad driver is a kernel module, send this issue to the kernel. If I am 
wrong, please correct me.

The issue appeares, when the notebook get into high processing, for example, 
when I am running firefox with lots of modules.

Then suddenly the (external) mouse behaves wrong. "Wrong" means, by hovering 
over the scroll bar, it scrolls automatically down, or by clicking in a window 
with several tab buttons, it jumps to the most right tab.

My checks discovered, that it is NOT the mouse itself, when this happens, but 
it is the touchpad. To prove this I did the following when the bug appeared:

1. Disconnected the external mouse = bug still existent
2. Opened systemsettings in plasma, then in the hardwaremenu chose "touchpad 
settings"
3. By hovering the mousepointer over the testfield, I could see the touchpad 
moving without any action by me = bug still existent
4. To delete the touchpad driver, I set "delete touchpad driver when external 
mouse exists" and put in the external mouse again = touchpad no more working, 
mouse working correctly
5. Disconnected external mouse, touchpad again active = bug NO MORE existent, 
everything ok


The issue is also gone, when restarting plasma5.

So, I think, there might be a problem with dbus or the touchpad driver itself.

However, I yet found no way, to reproduce this bug, it appears often, but 
randomly. And it appears not only in plasma5, also when running a game like 
doom3 or some other shooter. These are not started from plasma5, these are 
started from LXDE.

I got you all information, I think them important, but feel free to ask for 
more.

Thank you very much for reading this and your help.

Best regards

Hans



 



-- Package-specific info:
** Version:
Linux version 5.8.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-9) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.10-1 
(2020-09-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.8.0-2-amd64 
root=UUID=ad01422d-da21-4b7f-ad9e-ce6c459ca494 ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Acer
product_name: Aspire 7520G
product_version: V1.32
chassis_vendor: Acer
chassis_version: N/A
bios_vendor: Acer
bios_version: V1.33
board_vendor: Acer
board_name: Fuquene
board_version: N/A

** Loaded modules:
vboxnetadp(OE)
l2tp_ppp
l2tp_netlink
l2tp_core
ip6_udp_tunnel
udp_tunnel
vboxnetflt(OE)
pppox
ppp_generic
slhc
xfrm_user
xfrm_algo
ctr
ccm
nf_tables
nfnetlink
cpufreq_conservative
uinput
binfmt_misc
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
mc
ath5k
ath
mac80211
snd_hda_codec_hdmi
snd_hda_codec_realtek
cfg80211
snd_hda_codec_generic
ledtrig_audio
edac_mce_amd
kvm_amd
snd_hda_intel
snd_intel_dspcfg
ccp
rng_core
snd_hda_codec
snd_hda_core
kvm
snd_hwdep
snd_pcm_oss
snd_mixer_oss
r852
snd_pcm
sm_common
joydev
irqbypass
nand
snd_timer
pcspkr
wmi_bmof
snd
nand_ecc
serio_raw
libarc4
bch
k8temp
ir_rc6_decoder
sg
nandcore
r592
mtd
soundcore
memstick
rc_rc6_mce
ene_ir
rc_core
ac
evdev
button
analog
gameport
isofs
cdrom
acer_wmi
sparse_keymap
rfkill
vboxvideo(OE)
ttm
drm_kms_helper
cec
vboxdrv(OE)
nvidia(POE)
usbnet
mii
cpufreq_userspace
cpufreq_powersave
powernow_k8
parport_pc
ppdev
lp
parport
drm
loop
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
ecb
aes_generic
libaes
crypto_simd
cryptd
glue_helper
lrw
gf128mul
algif_skcipher
af_alg
dm_crypt
dm_mod
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
crct10dif_common
hid_generic
usbhid
hid
ahci
libahci
ata_generic
pata_amd
libata
ohci_pci
psmouse
ohci_hcd
scsi_mod
sdhci_pci
cqhci
sdhci
ehci_pci
ehci_hcd
firewire_ohci
mmc_core
forcedeth
firewire_core
crc_itu_t
usbcore
usb_common
i2c_nforce2
battery
wmi
video

** PCI devices:
00:00.0 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller 
[10de:0547] (rev a2)
Subsystem: Acer Incorporated [ALI] MCP67 Memory Controller [1025:0126]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP67 ISA Bridge [10de:0548] (rev 
a2)
Subsystem: Acer Incorporated [ALI] MCP67 ISA Bridge [1025:0126]
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- 
Kernel driver in use: nForce2_smbus
Kernel modules: i2c_nforce2

00:01.2 RAM memory [0500]: NVIDIA 

Bug#960117: linux-image-5.6.0-1-686: linux-image-5.6.0-1-686-pae starts weird sound at boot on battery

[Hans-J. Ullrich]

Package: src:linux
Version: 5.6.7-1
Severity: important
File: linux-image-5.6.0-1-686

Dear Maintainer,

I am running in an issue when booting the latest kernel 5.6.0-1-pae. This 
appears only on 32-bit-version, every computer with 
64-bit is running fine.

Environment:
I am running am EEEPC with a SSD harddrive, which is seperated in several 
partitions (/boot, /home (luks enc.), /var (luks enc.)
, /usr (luks enc.). The batteries are fully charged and in best shape.

Issue:
When booting on battery, first /usr wants to be decrypted, what is running 
well. Then, as soon it wants to be /var decrypted, ththere is a loud noise from 
the speakers (hardly to describe, such a "taktaktaktaktaktak..." with about 
5Hz.

Ignoring this, the syetem is booting, but the sound stays. I tested with the 
prior kernel-version 5.5.0-2-686-pae, which works without any isues.

I also had to say, that I had an issue with this kernel to the partition of 
/var, which killed my filesystem (glad, could restore it by using the 
superblock) and I believe this crash was due to the same bug in kernel-version 
5.6.0-1-686 so I set this report to "important" as it might kill something.

As a workaround, I am running now kernel 5.5.0-2-686-pae, but it would be nice, 
if you could fix this issue in kernel 5.6.0-1-686-pae (or higher).

Thank you very much for the grrat work!

Best regards and stay healthy!

Hans

 
*** End of the template - remove these template lines ***


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

** Model information

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory 
Controller Hub [8086:27ac] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Memory 
Controller Hub [1043:8340]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE 
Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Integrated 
Graphics Controller [1043:8340]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [1043:8340]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family High Definition Audio 
Controller [1043:8398]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
4 [8086:27d6] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR+ TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #1 [8086:27c8] (rev 

Bug#878403: linux-image-4.13.0-1-686-pae (and prior version!) crashes at boot

[Hans-J. Ullrich]

Package: src:linux
Version: 4.13.4-1
Severity: important

Dear Maintainer,

the latest kernel version crashes at boot, when the intel drm module is loaded 
(this is, what I think is doing). 

Whilst on kernel 4.12.0-2-686-pae there was only a non destructive crash 
information, the latest version makes the computer unuable, as the text console 
is either not readable, and when it is starting X, only one half of the screen 
is seen.

This bugreport is written when running kernel 4.12.0-2-686-pae, and below I 
attach you the warning text, I got at boot (the one, which is not 
destructable). I hope, it will clear, what is happening. This is the warning at 
boot:

---  start 

Oct  2 08:42:04 localhost kernel: [   22.275700] [ cut here 
]
Oct  2 08:42:04 localhost kernel: [   22.275725] WARNING: CPU: 0 PID: 119 at 
/build/linux-JOV0NV/linux-4.12.13/drivers/gpu/drm/drm_atomic_helper.c:842 
drm_atomic_helper_update_legacy_modeset_state+0x1f0/0x210 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.275728] Modules linked in: ath9k_hw 
ath mac80211 sg lpc_ich mfd_core cfg80211 snd_hda_codec_realtek rng_core 
snd_hda_codec_generic snd_hda_intel i915 shpchp snd_hda_codec snd_hda_core 
snd_hwdep drm_kms_helper snd_pcm_oss eeepc_laptop(+) snd_mixer_oss 
sparse_keymap rfkill snd_pcm snd_timer battery drm ac i2c_algo_bit snd video 
soundcore button wmi acpi_cpufreq gspca_sn9c20x gspca_main v4l2_common videodev 
media atl1 mii parport_pc ppdev lp parport loop ip_tables x_tables autofs4 ext4 
crc16 jbd2 fscrypto mbcache ecb lrw gf128mul algif_skcipher af_alg raid10 uas 
usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod 
dm_crypt dm_mod crypto_simd cryptd aes_i586 sd_mod psmouse ahci libahci libata 
scsi_mod
Oct  2 08:42:04 localhost kernel: [   22.275849]  ehci_pci uhci_hcd ehci_hcd 
usbcore usb_common atl1c thermal
Oct  2 08:42:04 localhost kernel: [   22.275869] CPU: 0 PID: 119 Comm: 
kworker/u4:2 Not tainted 4.12.0-2-686-pae #1 Debian 4.12.13-1
Oct  2 08:42:04 localhost kernel: [   22.275872] Hardware name: ASUSTeK 
Computer INC. \x931005HAG\x94/1005HAG, BIOS 040103/02/2010
Oct  2 08:42:04 localhost kernel: [   22.275883] Workqueue: events_unbound 
async_run_entry_fn
Oct  2 08:42:04 localhost kernel: [   22.275888] task: f65c9480 task.stack: 
f65ee000
Oct  2 08:42:04 localhost kernel: [   22.275904] EIP: 
drm_atomic_helper_update_legacy_modeset_state+0x1f0/0x210 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.275906] EFLAGS: 00010246 CPU: 0
Oct  2 08:42:04 localhost kernel: [   22.275911] EAX: f5db9000 EBX: f5df9300 
ECX: f5df1a80 EDX: f5678e00
Oct  2 08:42:04 localhost kernel: [   22.275915] ESI:  EDI:  
EBP: f5e31c00 ESP: f65efc54
Oct  2 08:42:04 localhost kernel: [   22.275918]  DS: 007b ES: 007b FS: 00d8 
GS: 00e0 SS: 0068
Oct  2 08:42:04 localhost kernel: [   22.275923] CR0: 80050033 CR2: b76208d0 
CR3: 3566a820 CR4: 06f0
Oct  2 08:42:04 localhost kernel: [   22.275926] Call Trace:
Oct  2 08:42:04 localhost kernel: [   22.276071]  ? 
intel_atomic_commit_tail+0xa65/0xe70 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276084]  ? 
pick_next_task_fair+0x4f4/0x5c0
Oct  2 08:42:04 localhost kernel: [   22.276132]  ? 
intel_atomic_commit+0x393/0x490 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276277]  ? _cond_resched+0x2a/0x40
Oct  2 08:42:04 localhost kernel: [   22.276414]  ? 
intel_atomic_commit+0x393/0x490 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276447]  ? drm_atomic_commit+0x37/0x40 
[drm]
Oct  2 08:42:04 localhost kernel: [   22.276463]  ? 
restore_fbdev_mode+0x14b/0x270 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276477]  ? 
drm_fb_helper_restore_fbdev_mode_unlocked+0x24/0x70 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276490]  ? 
drm_fb_helper_set_par+0x27/0x5b [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276620]  ? 
intel_fbdev_set_par+0x12/0x50 [i915]
Oct  2 08:42:04 localhost kernel: [   22.276629]  ? fbcon_init+0x53d/0x580
Oct  2 08:42:04 localhost kernel: [   22.276637]  ? visual_init+0xb8/0x110
Oct  2 08:42:04 localhost kernel: [   22.276643]  ? 
do_bind_con_driver+0x15c/0x330
Oct  2 08:42:04 localhost kernel: [   22.276650]  ? 
do_take_over_console+0x108/0x170
Oct  2 08:42:04 localhost kernel: [   22.276657]  ? do_fbcon_takeover+0x55/0xb0
Oct  2 08:42:04 localhost kernel: [   22.276665]  ? 
notifier_call_chain+0x4b/0x70
Oct  2 08:42:04 localhost kernel: [   22.276672]  ? 
__blocking_notifier_call_chain+0x2e/0x50
Oct  2 08:42:04 localhost kernel: [   22.276679]  ? 
blocking_notifier_call_chain+0xe/0x20
Oct  2 08:42:04 localhost kernel: [   22.276685]  ? 
register_framebuffer+0x1df/0x330
Oct  2 08:42:04 localhost kernel: [   22.276702]  ? 
drm_fb_helper_initial_config+0x26c/0x420 [drm_kms_helper]
Oct  2 08:42:04 localhost kernel: [   22.276830]  

Bug#872644: linux-image-4.12.0-1-686-pae: Olinux-imag-4.12.0-1-686-pae sends crash messags at boot

[Hans-J. Ullrich]

Package: src:linux
Version: 4.12.6-1
Severity: normal

Dear Maintainer,

my debian/testing system got /usr, /var and /home luks encrypted. At boot, as 
soon as I entered the passwort for the first partition to decrypt (which is 
always /usr), I get a bunch of messages, that something is crashed. However, 
this is not destructive and I can get booting on by decrypting /var and /home.

I would like to send the messages to you, but I see no way, to file these 
messages, as they are in a too early state, when a kernekl log or a boot log is 
yet not written.

If you can tell me a way, to file down the messages as soon as the kernel 
starts (maybe there is a kernel command or a grub command, which let me do 
this), then I would be happy to send you the messages. I suppose, the message 
is related to my bios. I am running an EEEPC 1005HGO with an intel N270 cpu. 
Most messqages, which are generated are intel oriented and named, and added 
with hex addresses.

Please drop me a line, if you are interested in more. If not, I will just wait 
for the next kernel version. 

As I said, it is weired, but not destroyable.

Best regards

Hans  


 Package-specific info:
** Version:
Linux version 4.12.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 
6.4.0 20170805 (Debian 6.4.0-3) ) #1 SMP Debian 4.12.6-1 (2017-08-12)

** Command line:
BOOT_IMAGE=/vmlinuz-4.12.0-1-686-pae 
root=UUID=da2bbacb-1b05-461e-8b72-9eef666b9bf6 ro net.ifnames=0 quiet 
acpi_osi=Linux

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information

** Loaded modules:
rfcomm
fuse
xt_multiport
iptable_filter
irda
crc_ccitt
decnet
appletalk
ax25
ipx
p8023
p8022
psnap
llc
ctr
ccm
snd_hrtimer
snd_seq_midi
snd_seq_midi_event
snd_rawmidi
snd_seq
snd_seq_device
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
bnep
binfmt_misc
iTCO_wdt
iTCO_vendor_support
option
usb_wwan
usbserial
arc4
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_core
btusb
btrtl
btbcm
btintel
bluetooth
ecdh_generic
coretemp
joydev
evdev
serio_raw
snd_hda_codec_realtek
snd_hda_codec_generic
ath9k
ath9k_common
sg
snd_hda_intel
ath9k_hw
ath
i915
snd_hda_codec
snd_hda_core
snd_hwdep
snd_pcm_oss
snd_mixer_oss
lpc_ich
mfd_core
mac80211
snd_pcm
drm_kms_helper
snd_timer
snd
rng_core
soundcore
cfg80211
drm
wmi
eeepc_laptop
i2c_algo_bit
sparse_keymap
rfkill
shpchp
ac
acpi_cpufreq
button
video
battery
gspca_sn9c20x
gspca_main
v4l2_common
videodev
media
loop
atl1
mii
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
mbcache
ecb
lrw
gf128mul
algif_skcipher
af_alg
uas
usb_storage
hid_generic
usbhid
hid
dm_crypt
dm_mod
crypto_simd
cryptd
aes_i586
sd_mod
psmouse
ahci
libahci
libata
scsi_mod
uhci_hcd
ehci_pci
ehci_hcd
usbcore
usb_common
atl1c
thermal

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory 
Controller Hub [8086:27ac] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Memory 
Controller Hub [1043:8340]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE 
Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Integrated 
Graphics Controller [1043:8340]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [1043:8340]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family High Definition Audio 
Controller [1043:8398]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi Jonathan and Ben.

Some special news. I tested again.

I installed linux-image-3.3.0-rc6-amd64_3.3~rc6-1~experimental.1_amd64.deb 
from snapshots.debian.org, and its headers, but the bug never appeared.

I did almos 10 - 15 rebootsx with no appearence of the bug.

Then I started 3.2 kernel and the bug appeared again. Maybe this information 
might be important for you. However, I guess I already tested this in the 
past, but this time all packagesd are up-to-date (state from today, of 
course).

Hope this helps!

Greets

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201301101902.43088.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi jonatahan,

happy new year! 
 
  Hadn't you tested 3.3-rc6 and found it to work ok?
  
  No, I never did. Maybe I should.
 

Hmm, I could not find it in the repositories and neither in 
backports.debian.org. I remember, there is another source, where packages go, 
but I forgot, where it was.

Can you point me to, where I find a 3.3-rc6-kernel-package? I guess, I will 
find 
the headers there, too.

Cheers

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201301011454.58798.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi Jonathan,

I already tested 3.3-rc6. Just look into the history of this bugreport.

Shall I test it new? Due to my tests in the past, it might be rather possible, 
to find out, in which kernel version and where a change was made, to inhibit 
the described behaviour.

IMO it never appeared in 3.4 and higher.

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201301011633.16038.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi Ben, hi Jonathan!

After several tries and 5 hours of compiling, I am sad, to tell you, the 
patch, Ben sent me, is not working.

Just before you take work into a new patch, let me first try kernel-3.4, which 
might be also possible to be released into next debian stable. Ben told so.

I tested 3.1, 3.2, 3,5 and 3.6, but NOT 3.4! So maybe 3.4 might work as 
wished, then no other action has to be done - just release debian with 3.4!

However, if kernel-3.2 shall be in next release, I am willing to test it for 
you. Maybe it will be easier, if you send me a precompiled module, which I 
then will test here.

Please let me explain: I am not too lazy to compile, but my system is not good 
prepared for it. The main problem is, my /usr partition is too small. It has 
only 20G, so kernel building breaks, with no space left on device.

I built the kernel now on my older 64-bit-machine, which has only 512 MB RAM 
and is rather slow. 

It is not possible for me, to increase /usr (i.e. with gparted) without data 
loss, for it is ecrypted with luks.

This just a little bit of information, why I am not so fast with the kernel 
building. All machines I am using (my 64-bit notebook, the 64-bit desktop-pc, 
my netbook and so on) are mostly permanently needed for my work, so they 
should not be killed somehow. I am happy, when they are working as wished!

However, as I said, I am happy, when I can help, but results may be last a 
little longer as expected due to my weired environment.

Thanks for your patience and best regards

Hans



 


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201212311917.37299.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi Jonathan!
 Gah, that's way more work than should be required. Did the module
 eventually load and just not work well, or were the instructions in my
 message or in the kernel handbook broken? (The latter would be a very
 serious bug, more serious than any particular instance of missing hardware
 support.)
 

It patched fine, it loaded fine, but the bug did not disappear.
 Hadn't you tested 3.3-rc6 and found it to work ok?
 
No, I never did. Maybe I should. 

 [...]
 
 
 It sounds like debuginfo is not disabled like it should be. Did you forget
 to run scripts/config --disable DEBUG_INFO?

Ahm I forgot. I just build the whole kernel with make-kpkg -j4 --initrd 
kernel-image 
 
 Sorry for the trouble and hope that helps.

Next time, I will try better.
 
 Sincerely,
 Jonathan

Greets

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201212311953.59137.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

 Heh, no, sorry.
 
 Could you test whether the attached patches fix the problem in 3.2?
 Please follow the instructions at
 http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-off
 icial to rebuild the kernel package with these patches.
 
 Ben.

Hi Ben, 

so, now after hours and hours of compiling, I could not manage to get the 
patched module loaded. The system is telling something of version mismatch.

Whatever, I think, just close the bug and do no more efforts in fixing the bug, 
it is itz not worth for the following reasons:

1. This bug is now since kernel 3.1 and no one cared of it - except of me.

2. As I am the only one with this bug, it needs not to be fixed - I got a 
solution for me (just using a newer kernel)

3. The kernel 3.2.X is such old, that it will be very soon replaced by the 
newer ones - who cares, what Ubuntu does.

4. I suggest, just to add the patch into the next kernel 3.2-0-XXX version. I 
will report it. It will make things not worse than they are. I will report of 
my tests then.

So, it will be ok for me, if the bug will be closed.


Thank you very much for your help, and do not waste any time for fixing this 
bug. There are much more important bugs to fix, I think!

Best regards and a happy new year!

Hans
 


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201212302001.45418.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi Jonathan,
 
 Could you send the command you used?  Generally you need to install
 the new Debian package you built and reboot to test, but there are
 other possibilities, too.  The above doesn't tell me enough to know
 what went wrong.

Sure! I did the following: Installed all needed packages, unpacked the source 
package and made a symlink /usr/src/linux to /usr/src/linux-source-3.2

Patched: patch -p1  /mypath/blah/0001ath5kxx.patch
So I did with all patches.

Then copied /boot/config-3.2.0-4-amd64 to /usr/src/linux/.config (so I got also 
the version, worked before in the past this way).

After that make menuconfig to check.

Building then:  make modules, because I just wanted to build only the ath5k 
module. 

At last I copied the newly build module ath5k.ko and replaced it with the new 
built one.

depmod -a finished all.

 
 You've made this same argument before.  The sad situation we're in is
 that only a small fraction of Debian users report bugs.  You're a
 representative of quiet masses of Debian users, potential Debian
 users, and other Linux users with similar hardware.  Meanwhile
 stubborn people like me want to see all easily-fixable hardware
 support bugs fixed, even if they only affect one person.
 

Well, if there are other people with the same problem, leave it open. Very ok 
for me! I just did not want to waste your time for a single person (=me), who 
cannot give much help back.

 Sorry for the burden, but it really does help.
 
 Of course if you're sick of it, that's also fine --- we can mark the
 bug as unreproducible, stop bothering you, and probably close it in a
 couple of weeks.

No, I am not sick and I will try it in the next time. But my time is limited, 
as I cannot run compilatiuon at work and in the evening the time is often too 
short, to run a compilation.

 
 Hoping that clarifies,
 Jonathan

Best regards

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201212302147.39949.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Dear maintainers,

I just want to let you know, that this bug is still in linux-image-3.2.0-4-
amd64, but NOT in version linux-image-3.5.XXX and also NOT in version linux-
image-3.6. from experimental.

Both kernels I have run now for the last months (3.5 for over 4 months and now 
3.6 for more than 4 weeks).

Both kernel are running super fine! No problems in any case.

Just in case for the new stable version, I suggest 3.5 or higher should be 
released.

Thanks for reading this mail.

Have a very nice christmess!


Hans 


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201212231118.22386.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Hi guys,

sorry, but somehow I got not the last messages related to this bug. As I read, 
elrond did fix something? Or was his mentioned patch related to some other bug.

However, I am running now kernel 3.5 for over 2 weeks, and got not a single 
problem.

I also did not see a newer version than 3.2.0-45 in wheezy, and I think, the 
next verion in wheezy will be 3.5 either.

So, maybe you might want to upload 3.5 to wheezy and close this bug? Just a 
suggestion. 3.5 is running great!

On the other hand, if there is a patched kernel 3.2 and there is a package 
available, I will be happy to test it and give reports.

Have a nice weekend

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209221453.54475.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Hi Jonathan,

sorry for my late answer. I was tired and early in bed yesterday.

Well,  this is what the system is telling me (please do not matter, that this 
example was made with 3.5. But there is no difference to 3.2):


rmmod powernow-k8
Error: Module powernow_k8 is in use

modinfo powernow-k8 | grep depends
depends:processor,mperf

rmmod mperf
Error: Module mperf is in use by: powernow_k8


rmmod processor
Error: Module processor is in use by: powernow_k8

lsmod | grep freq
cpufreq_conservative13147  0 
cpufreq_stats  12866  0 
cpufreq_userspace  12576  0 
cpufreq_powersave  12454  0

The last four I could unload, but powernow-k8 still not.

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209130935.19198.hans.ullr...@loop.de

Bug#687046: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Donnerstag, 13. September 2012 schrieben Sie:
 Hans-J. Ullrich wrote:
  Am Donnerstag, 13. September 2012 schrieben Sie:
  Does modprobe -r powernow_k8 work?  If not, how about
  for module in powernow_k8 processor mperf; do rmmod -w $module; done?
  
  No, it doesn't.
  
  modprobe -r powernow_k8
  FATAL: Module powernow_k8 is in use.
  
  Second one does not execute, but hangs ( = does nothing).
 
 Thanks for the quick feedback.  Do you mind if I forward this to the
 bug log?
 
 Jonathan

Yeah, no problem. Sorry, my fault, I accedently just responded only to you.

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209131809.53343.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder:
Hi Jonathan, 
 Hi again,
 
 Hans-J. Ullrich wrote:
  I would like to help. Can you tell me, where I find the packages of
  3.3 and 3.4 images? I did not find them in the debian repositories.
 
 http://snapshot.debian.org/package/linux-2.6/

Thank you for pointing me to this. I lookes at backports.debian.org, so I 
didn't find.

However, I tested now 3.3 and 3.4. None of them showed any problems (rebooted 
both each 10 times, Windows - Linux - Windows - Linux and so on.)

I do not know, if this is good or evil. However, i am still running 3.5 from 
experimental, as I guess, 3.3 and 3.4 will not make it into testing.

Still no problems, yet. I will test it now for a while, if no problems will 
occur in the next time, I will send you feedback.

Thumbs up! 

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209121741.25901.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder:
Well, tested again. 10 times each.
 It means my guess was wrong.  Could you try the following two?
 
  - 3.3-rc6
  - 3.2.23-1 again
 

With 3.3-rc6 not a single problem during my tests. However, it might be a 
coincidence, but with 3.223, it happend almost every time, and with 3.3 not a 
single one.

So maybe there is a fix since 3.3. :)) 

 Sorry for the fuss,
 Jonathan

Cheers,

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209121831.20574.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder:
 Hans-J. Ullrich wrote:
  With 3.3-rc6 not a single problem during my tests.
 
 Thanks.
 
 However, it might be a
  
  coincidence, but with 3.223, it happend almost every time, and with 3.3
  not a single one.
 
 Have you tested 3.2.23-1 again?  If not, please do.
 
 Jonathan

I did, and the bug reappeared.

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209121848.15584.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder:
 notfound 665881 linux-2.6/3.3-1~experimental.1

 Does the problem go away if you unload the cpufreq driver
 (powernow_k8)?

Jonathan, I apologize, but powernow-k8 can not be unloaded. The kernel 
inhibits it. Of course I unloaded all dependent modules of powernow-k8 and all 
cpufreq-*.

But no success.

Sorry I can not tell better things.

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209121957.28730.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Montag, 10. September 2012 schrieb Jonathan Nieder:
 Hans-J. Ullrich wrote:
Hi Jonathan,

  1. The described behaviour appears EVERY TIME, when I started Windows 7
  on this system, and rebooted to linux again.
 
 That's very good to hear.  Can you reproduce this with 3.5.y from
 experimental?
 

Well, I installed now 3.5-trunk-amd64 from experimental. First tests are 
showing good results. I still could not reproduce the behaviour with this 
kernel. But it is too early, to make a final conclusion. So I will test it now 
for a few days and will then send a report.

 If so, please send a description of the symptoms to
 linux-wirel...@vger.kernel.org, cc-ing ath5k-de...@lists.ath5k.org,
 Nick Kossifidis mickfl...@gmail.com, 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 kernel versions you have tested and what happened with
each
 
  - full dmesg output from booting and trying to use wireless in the
affected state, as an attachment
 
  - any other weird symptoms or observations
 

Yes, if any strange behaviours occure, I will send them to the list. My 
current system is debian-testing, which I am running on several computers 
(mostly daily updated). These are 2 x amd64-cpus (a notebook Acer Aspire 7520G 
and a Desktop PC) and my Asus EEEPC 1005 HGO (i386).

 Hopefully the symptoms will ring a bell for someone, who can provide
 instructions or a patch to track down the cause further.

Yeah, that might be great!
 
 Hope that helps,
 Jonathan

Thanky for the help.

Best regards

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209111252.15179.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Dienstag, 11. September 2012 schrieb Jonathan Nieder:
 Hans-J. Ullrich wrote:
  Well, I installed now 3.5-trunk-amd64 from experimental. First tests are
  showing good results.
 
 Drat.  Am I correct in guessing that the prebuilt 3.3.6 package from
 http://snapshot.debian.org/package/linux-2.6/ reproduces it, while
 3.4.1 does not?


Huh, I did not test those versions. I just tested 3.2-xx (stock debian 
testing) and now at your advice version 3.5. (experimental)

If 3.5 will work, I can test 3.3 and 3.4, too, if needed.
  
 Jonathan


Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209111309.22992.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Am Dienstag, 11. September 2012 schrieb Jonathan Nieder:

 Ah, I think I see where I misunderstood.  When you said The described
 behavior appears EVERY TIME, did you mean that it appears after a
 while (how long?), and not necessarily the first time you try to use
 wireless after rebooting out of Windows 7 into Linux?

No, I meant it this way: I started Windows 7,  then rebooted and started again 
choosing Linux, then the bahviour appeared every time (hmm, maybe each 
time might be the better English expression).

So I guessed, that Windows switched something in the wirelesscard or the bus.
 
 
 Jonathan

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209111550.38404.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

 Ok, that is how I understood it the first time.
 
 My question still stands: when it happened every time, did it happen
 right away?
 

Yes, it happened at once. Right after I booted Win7 and then booted into Linux 
again. 

It happened also, when I booted Win 7, shut down the computer, powered off 
(power supply and power cell), and then started Linux.

Did I describe it now better?
 If it did, and assuming you rebooted out of Windows 7 to try it,
 there is no need to test 3.5.y any more.  We already know it doesn't
 reproduce the bug under the same circumstances as 3.2.y did.
 

So you know the reasons. That is really good news! I read about, that 3.5 
changed several things in bus strategies. 

 Hoping that clarifies,
 Jonathan

Thank you very much!

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209111640.58551.hans.ullr...@loop.de

Bug#665881: [wheezy] module ath5k is blocking wlan-card

[Hans-J. Ullrich]

 I have my guesses about causes, but I am keeping them to myself until
 we have the additional information I asked about, namely how 3.3.6 and
 3.4.1 do.
 

I would like to help. Can you tell me, where I find the packages of 3.3 and 3.4 
images? I did not find them in the debian repositories.

 Thanks for your patience, and sorry for the lack of clarity.

No problem.

 Jonathan


Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209111827.07024.hans.ullr...@loop.de

Bug#687046: linux-image-3.2.0-3-amd64: module ath5k is blocking wlan-card

[Hans-J. Ullrich]

Dear maintainers,
I tested a little bit, and here are some more informations. Maybe it helps:

1. The described behaviour appears EVERY TIME, when I started Windows 7 on 
this system, and rebooted to linux again. 

Conclusion:  it seems, windows is setting some bit, that linux does not.

2. This behaviour MAY appear, when power was complete taken off (power supply 
and accumulator). It MAY also appear, when power was taken off for a long time 
(several hours)

Conclusion: At boot there is a missing intialisation thing for this card or 
for the pci-bus. 

3. This behaviour NEVER appears at normal running time. Once the wireless-card  
is running, this bug never appears until next boot. Even by unloading and 
reloading the module ath5k it NEVER appears.

Conclusion: It is a problem at boot time.

4. rfkill is showing me, the device is unblocked (soft-block and hard-block), 
even if the bug appears. 

Conclusion: Seems to be a hard-block, which cannot be reset by rfkill.


I hope, this may help a little bit. 

Best regards

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209101315.39289.hans.ullr...@loop.de

Bug#649253: eeepc-wmi does not seem to adjust fan speed, but prevents use of fancontrol

[Hans-J. Ullrich]

Hi Jonathan, 


 To spell this out for me: if you blacklist eeepc-wmi in
 /etc/modprobe.d, does the fan start to behave correctly, or do you
 also need to tell the kernel to respond TRUE to OSI(Linux) queries
 to mimic the pre-2.6.23 situation?  Please do attach acpidump
 output.

Well, with acpi-osi=Linux eeepci-wmi is NOT loaded (no need to blacklist it), 
anbd eeepc-laptop is loaded instead. In this case, pwmcapable kernel-modules 
are loaded, so that pwmconfig will start and is working.

If eeepc-wmi is loaded, and IO start the command pwmconfig, then I get the 
message no pwmcapable hardware found.

I suppose, I already send the exact output before, if needed, I will sed it 
again.

 I'll be happy to write a patch to test that adds a quirk, but first,
 please provide the information listed before (acpidump output, and
 behavior without acpi_osi=Linux when eeepc-wmi is not loaded).
 
Great, I will likely test it. Can you build a kernel-package for it? So it is 
easy for me to install this kernel and deinstall after testing, without 
getting in danger to destroy my system. I need it for work!

 Thanks again for your help,
 Jonathan

I am happy if I can help with my little knowledge.

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209061836.40611.hans.ullr...@loop.de

Bug#649253: eeepc-wmi does not seem to adjust fan speed, but prevents use of fancontrol

[Hans-J. Ullrich]

Hi Jonathan, 

I tried the latest kernel from experimental, but as expected, there is no 
difference. Same as with the other kernels.

For those, who are interested, I advise not to use eeepc-wmi, as doing so, the 
fan will NOT speed up, even when the cpu is getting hot. To say correct: It is 
speeding up, but only a very little bit! You may overheat your cpu.

I reverted back to the acpi-osi=Linux-workaround, which is working very 
well on this computer.

Ben, I think, you understand the situation, as we talked about it some time 
ago. I might remember, that you also told me, that the hardware of this 
computer is not documented and so developing might be impossible.

I doubt, that many people are using an EEEPC 1005HGO with linux, most people 
are having a better machine (with N280 cpu or better) and the newer API.

In my case I can use the workaround, and doing development for a single person 
is really(!) too much of a good thing!

So it is ok for me, when this bug may be closed.

Otherwise I will be pleased, when I can help with some testing.

Thank you very much for your time and help!


Best regards

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209052002.03421.hans.ullr...@loop.de

Bug#649253: Bug can be closed

[Hans-J. Ullrich]

Dear maintainers, 

as there is no hardwaresupport on this old device, I suggest, to close this 
bug. I am running the old kernel module with the workaround acpi=Linux, 
which is working like a charm. 

So, tis bug can safely be closed. 

Thank you very much for your help and work!

Best regards

Hans-J. Ullrich


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

Bug#649253: eeepc-wmi does not seem to adjust fan speed, but prevents use of fancontrol

[Hans-J. Ullrich]

Am Sonntag, 2. September 2012 schrieb Jonathan Nieder:
 tags 649253 + moreinfo
 quit
 
 Hi Hans,
 
Hi Jonathan, 

I will be pleased to answer.

 Hans-J. Ullrich wrote:
  [Subject: Bug can be closed]
 
 Please keep in mind that these appear as emails in a crowded inbox, so
 the subject line can be a good place to put valuable context.
 
 [...]
 
  as there is no hardwaresupport on this old device, I suggest, to close
  this bug. I am running the old kernel module with the workaround
  acpi=Linux, which is working like a charm.
 
 I'd rather see such bugs fixed so others do not have to suffer from
 them.
 


Just to explain: eeepc-wmi will not be fixed, as the developers told me (almost 
2 years ago). The problem of this, is that the old hardware specs of my EEEPC 
1005 HGO are not made available by the vendor. So it is of course impossible, 
to write a kernel module. 

All newer hardware, which is in most newer processors will be supported, of 
course! But as I said, my EEEPC 1005 HGO with the old single core cpu (Intel 
N280), still got the old and undocumentd API.  
 What is the newest kernel you've experienced this bug with?  What
 other kernels have you tested and what happened with each --- is it a
 regression?
 
I am running now linux-image-3.2.0-3-i386 (stock debian kernel of testing). 

 What steps exactly do you use to work around the bug?  What do you
 mean by running the old kernel module?  Are you using an older
 kernel?
 

No, I can choose either to load eeepc-wmi or use the option acpi_osi=Linux 
which let me load eeepc-laptop at startup. The second one I call the old 
module, as this is the old fancontroller module developed for my old cpu.

If eeepc-laptop is used, then eeepc-wmi will not be loaded.

 I imagine upstream would want to know about this, so please do test a
 3.5.y kernel from experimental and let us know the result if you have
 time.  Output from reportbug --template linux-image-$(uname -r) and
 acpidump and full dmesg output from an affected boot (as
 attachments) would be useful as well.
 

Of course, I will be pleased to test, but I doubt, that it will work. The 
developers of the modiule eeepc-wmi wrote me a mail, where they explained, 
that they will not continue further developing of eeepc-wmi. Not because they 
do not want to, but because they can't - because missing informations of the 
hardware API!

So I changed to eeepc-laptop, which is working fine for me. And for these 
reasons I claimed this bugreport closable.

However, I will test a newer kernel (3.5-X) in the next days, maybe not 
tomorrow, but during the coming week. Response and report will then be sent.


 Hope that helps,
 Jonathan

Thank you for your help!

Best regards

Hans


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209022247.02111.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Hi Jonathan, 

today I tested with the old bpo-kernel, but sadly I could not manage to get 
this bug shown again, neither with pcie= nor without pcie= addition.

But what i can say: This bug is gone! I have now rebooted almost 20 times and 
it never appeared a single time. IMO that bugreport can safely be closed (I 
think, it is already). It is a pity, I can give no other answer, but all my 
tests to reproduce the bug with the older kernel failed. 

However, I have already updated some software around it, for example some 
libs. My system (debian-amd/testing) is beeig updated nearly daily, so I can 
see bugs very fast.

This is in one way good, on the other way it might be bad (like this time).

Thank you for your help anyway. I hope, I can help next time better. 

Best regards

Hans 




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204192122.21656.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Am Dienstag, 17. April 2012 schrieb Jonathan Nieder:
 Jonathan Nieder wrote:
  Hans-J. Ullrich wrote:
  I did as you adviced. First I installed the kernel version before. which
  is 3.2.12-1-amd64, and the package is something with bpov bin its
  name. I suppose bpo stand for backport. See:
  
  uname -r
  3.2.0-0.bpo.2-amd64
  
  Then I added pcie_aspm=force to the commandline. With this added, I
  rebooted several times, but I could not manage to reproduce this bug
  again.
  
  Perfect, thanks.
 
 On second thought, if you get a chance to reproduce the bug using 3.2.12-1
 without the pcie_aspm=force parameter, that would be a comfort.  If I
 understood correctly before, when it was happening this was pretty
 repeatable, right?
 
 If you don't have time for it, that's fine with me still.

Yes, the error was very good reproducable, If it is not in a hurry, I will be 
able, to test it on next weekend. At the moment, my notebook is not available 
for me. It is at my work, doing some longer job.

I have not always time for doing such tests. Mostly in the evening or at 
weekends is a good time for me, as I am at the other time at work. I am 
working in a little shop as a Computer guy, and so I have not much time do 
private things. That was better, when I was in my sysadmin job before. :))

So, I will test and report, as soon as I know more.

Best regards

Hans





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204182003.52379.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Jonathan Nieder wrote:

 If you boot the old kernel with pcie_aspm added to the kernel command
 line, does it work?

Sloppy of me.  Make that:

 If you boot the old kernel with pcie_aspm=force added to the kernel command
 line, does it work?  (I left out =force before.)

Hi Jonathan, 

I did as you adviced. First I installed the kernel version before. which is 
3.2.12-1-amd64, and the package is something with bpov bin its name. I 
suppose bpo stand for backport. See:

uname -r
3.2.0-0.bpo.2-amd64

Then I added pcie_aspm=force to the commandline. With this added, I rebooted 
several times, but I could not manage to reproduce this bug again. Did you 
expect the bug with or without the added pcie_asm= switch?

It makes me not happy, when the reason cannot be found, although IMO your idea 
might be correct. In the changelog it was the only bugfix, which might be 
related to this bug.

On the other hand some other packages have been changed, too (i.e. libs), so 
they might also be responsible for this or partly responsible.

Best regards

Hans
 

 




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204162117.56357.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Am Montag, 16. April 2012 schrieb Jonathan Nieder:
 tags 665881 = upstream patch fixed-upstream
 tags 665420 - pending
 forcemerge 665420 665881
 quit
 
 Hans-J. Ullrich wrote:
  I did as you adviced. First I installed the kernel version before. which
  is 3.2.12-1-amd64, and the package is something with bpov bin its
  name. I suppose bpo stand for backport. See:
  
  uname -r
  3.2.0-0.bpo.2-amd64
  
  Then I added pcie_aspm=force to the commandline. With this added, I
  rebooted several times, but I could not manage to reproduce this bug
  again.
 
 Perfect, thanks.
 
 This is the same bug as #665420 and the bugs merged with it.  Closing.
 
 Ciao,
 Jonathan

Hi Jonathan! 
Yeah, great! I am very happy I could help you. 

So I will uninstall the old kernel and run the latest kernel again. You made 
my day! 

Thank you very much for all the help and all the care you did!

Best regards

Hans




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204162135.42587.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Hey dear maintainers!

Did you change something related to this bug? Yesterday I updated linux-image 
from version 3.2.12-1 - 3.2.14-1, and since then the bug didn't appear right 
now.

However, I suggest, to let the report a few days open, so I can see, if the 
bug appears during the following week. I will inform you, as soon as I know 
more.

Best regards

Hans




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204151857.56170.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Made some new tests!

When the wlan-hardware is set by the kernel, also Windows-XP will not see the 
card. 

So it is proven: The kernel is setting my wlancard into some mode, which can 
only be reset, when I take completely the power off the notebook.

Reinitialisation through a reboot or by reloading the kernel-module does not 
work.

Greets

Hans




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201204011437.27078.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Hello all,

it seems now, everything is working again. I cannot really explain, why. 
However, it looks like the last update did fix the problem. I checked my logs, 
and there were two packages updated, which are kernel related. Package kmod 
was added, and package module-init-tools got from version 3.16 to 6.2, which 
is a major jump. I suppose, the problem was fixed by one of these two packages, 
but I cannot prove it. 

Also the problem I mentionened with wicd is gone, too, although wicd was not 
changed.

IMO the bug should be closed for now. If the same problem appears again, I 
might send a new bugreport. 

A great thank you to Jonathan Nieder, who helped me a lot and cared on this 
bug. Again I learned new things, hope I can give some time a little back to 
other users!

Best regards and thanks for all the help!

Hans







-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203281910.24754.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

Hi Jonathan, 

strange things happen. At the moment it is running, no problems at all. But I 
did not change anything. I swear, the last days it did not work. Also the 
weired messages in syslog are gone, those

  223.597826] ath5k phy0: gain calibration timeout (2412MHz)
[  224.086320] ath5k phy0: gain calibration timeout (2417MHz)
[  224.580417] ath5k phy0: gain calibration timeout (2422MHz)

But I think, the bugreport should be left open for some time, as the problem 
might come back. Is this ok for you? 

As soon this will happen, I will send boot.logs and dmesg from boot. But at 
the moment, as long as everything is working, this makes no sense.

Sorry for my late response, but yesterday was late night in Germany and today 
I had to work, so I was able to send my answer just now.

Best regrads

Hans




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203272002.50192.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

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

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

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


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

Sorry!

Hans




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203262244.59242.hans.ullr...@loop.de

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

[Hans-J. Ullrich]

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

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

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

I did, but I got no success.

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

No, it does not help.

  - is rfkill list output as expected?
 

This is the output: 

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


Seems ok for me.

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

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

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

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

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

The problem is always happening.

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


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

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

 Hope that helps,
 Jonathan

I hope it, too. :))

Hans





--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203262242.58579.hans.ullr...@loop.de

Bug#659461: Solved, bug can be closed

[Hans-J. Ullrich]

Dear maintainer-team,

the new kernel module added two new regulators speakers and headphones, 
and they are both set to 0 by default!

Additionally kmix and some other GUI might not show them as well as alsamixer, 
but just start alsamixer -c0 and all sliders appear. Now you can set them as 
you want, and now you can hear sound playing again.

A great thank you! in this matter to Jonathan Nieder and Takashi Iwai, ho 
helped me, to find the solution!

So ist was just PEBCAK! The bug can safely be closed!

Thanks for all the help!

Best regards

Hans





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201202141841.34579.hans.ullr...@loop.de

Bug#659461: [3.1.8 - 3.2.4 regression] Acer Aspire 7520G: no sound

[Hans-J. Ullrich]

Am Samstag, 11. Februar 2012 schrieb Jonathan Nieder:
Hello Jonathan,

sorry it lasted a little bit longer, as I got problems with the download of 
the kernel from snapshots.debian.org.

However, Here I send again both files, one is with kernel 3.2, the other made 
with kernel 3.1 (*-with-sound and *-no-sound). Reverting to the older kernel 
additionallly proved, the bug is a kernel matter.

I hope, this will help. See the attached files please.

Hans

 
upload=truescript=truecardinfo=
!!
!!ALSA Information Script v 0.4.60
!!

!!Script ran on: Sat Feb 11 12:22:34 UTC 2012


!!Linux Distribution
!!--

Debian GNU/Linux lenny/sid \n \l


!!DMI Information
!!---

Manufacturer:  Acer
Product Name:  Aspire 7520G
Product Version:   V1.32


!!Kernel Information
!!--

Kernel release:3.1.0-1-amd64
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: unknown
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: 1.0.24
Library version:1.0.24.1
Utilities version:  1.0.24.2


!!Loaded ALSA modules
!!---

snd_hda_intel


!!Sound Servers on this system
!!

aRts:
  Installed - Yes (/usr/bin/artsd)
  Running - No


!!Soundcards recognised by ALSA
!!-

 0 [NVidia ]: HDA-Intel - HDA NVidia
  HDA NVidia at 0xd088 irq 21


!!PCI Soundcards installed in the system
!!--

00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!

00:07.0 0403: 10de:055c (rev a1)
Subsystem: 1025:0126


!!Modprobe options (Sound related)
!!

snd-atiixp-modem: index=-2
snd-intel8x0m: index=-2
snd-via82xx-modem: index=-2
snd-pcsp: index=-2
snd-usb-audio: index=-2
snd-hda-intel: index=0 model=test


!!Loaded sound module options
!!--

!!Module: snd_hda_intel
bdl_pos_adj : 
32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
0,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
model : 
test,(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
patch : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
position_fix : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
power_save : 0
power_save_controller : N
probe_mask : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
probe_only : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
single_cmd : N


!!HDA-Intel Codec information
!!---
--startcollapse--

Codec: Realtek ALC268
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0268
Subsystem Id: 0x10250126
Revision Id: 0x13
No Modem Function Group found
Default PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=4, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x1d: Stereo Amp-Out
  Device: name=ALC268 Analog, type=Audio, device=0
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x36 0x40]
  Converter: stream=5, channel=0
  PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x03 [Audio Output] wcaps 0x1d: Stereo Amp-Out
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x36 0x40]
  Converter: stream=5, channel=0
  PCM:
rates [0x560]: 44100 48000 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Node 0x04 [Vendor Defined 

Bug#659484: ath9k: kernel module ath9k problem with WEP

[Hans-J. Ullrich]

Package: linux-2.6
Version: 3.2.4-1
Severity: normal
File: ath9k

Hello dear maintainers,

after upgrading to löinux-image 3.2.0 I detected a problem with my wireless
router. I suppose, it is related to kernel module ath9k, which is
responsible for my Atheros wireless card in my EEEPC 1005 HGO.

I tried two ways of connecting. The first one is using the file 
/etc/network/interfaces. As in the past, I am using a static IP. 
Connection is working, I get the IP, but I can never ping to the gateway.

The other way is using wicd. With wicd, it is showing me the connection, 
but never gets an IP. Ping does not work, too, and the line test of wicd
fails.

WPA/WPA2 is working with this module like a charme. Also another computer
with an Atheros card, but ath5k module, can connect on the same router 
with WEP like a charme.

Thus I guess, the module ath9k of the kernel might be buggy.

Besides: I know, WEP is outdated, but I use an older router with only WEP
availablke. But as its PA is defective and sending only just with 1mW (range 
approx.
5m) this is the best protection against sniffers. So I would like to use it 
further more.

Thank you for reading my message!

Best regards

Hans
 


-- Package-specific info:
** Version:
Linux version 3.2.0-1-686-pae (Debian 3.2.4-1) (wa...@debian.org) (gcc version 
4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 23:52:49 UTC 2012

** Command line:
root=UUID=ea6e761d-8e68-49a0-8674-0cc112025d91 ro quiet acpi_osi=Linux

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[58384.155272] wlan0: deauthenticating from 00:06:25:ed:1f:e7 by local choice 
(reason=3)
[58384.194872] cfg80211: Calling CRDA to update world regulatory domain
[58385.399068] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58385.506667] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58386.076090] atl1c :01:00.0: MAC state machine can't be idle since 
disabled for 10ms second
[58386.099541] atl1c :01:00.0: irq 45 for MSI/MSI-X
[58386.316316] atl1c :01:00.0: Error get phy ID
[58386.317416] ADDRCONF(NETDEV_UP): eth0: link is not ready
[58546.794024] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58547.400108] atl1c :01:00.0: MAC state machine can't be idle since 
disabled for 10ms second
[58547.424283] atl1c :01:00.0: irq 45 for MSI/MSI-X
[58547.648328] atl1c :01:00.0: Error get phy ID
[58547.649394] ADDRCONF(NETDEV_UP): eth0: link is not ready
[58547.927157] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58550.270757] wlan0: authenticate with 00:06:25:ed:1f:e7 (try 1)
[58550.272671] wlan0: authenticated
[58550.272765] wlan0: associate with 00:06:25:ed:1f:e7 (try 1)
[58550.274975] wlan0: RX AssocResp from 00:06:25:ed:1f:e7 (capab=0x1 status=0 
aid=3)
[58550.274985] wlan0: associated
[58550.275468] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[58561.128129] wlan0: no IPv6 routers present
[58590.174273] wlan0: deauthenticating from 00:06:25:ed:1f:e7 by local choice 
(reason=3)
[58590.214820] cfg80211: Calling CRDA to update world regulatory domain
[58594.398407] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58594.511036] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58595.092116] atl1c :01:00.0: MAC state machine can't be idle since 
disabled for 10ms second
[58595.115045] atl1c :01:00.0: irq 45 for MSI/MSI-X
[58595.332340] atl1c :01:00.0: Error get phy ID
[58595.333415] ADDRCONF(NETDEV_UP): eth0: link is not ready
[58750.734408] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58751.304110] atl1c :01:00.0: MAC state machine can't be idle since 
disabled for 10ms second
[58751.328515] atl1c :01:00.0: irq 45 for MSI/MSI-X
[58751.548340] atl1c :01:00.0: Error get phy ID
[58751.549416] ADDRCONF(NETDEV_UP): eth0: link is not ready
[58751.860093] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58754.194671] wlan0: authenticate with 00:06:25:ed:1f:e7 (try 1)
[58754.198465] wlan0: authenticated
[58754.198598] wlan0: associate with 00:06:25:ed:1f:e7 (try 1)
[58754.201028] wlan0: RX AssocResp from 00:06:25:ed:1f:e7 (capab=0x1 status=0 
aid=3)
[58754.201043] wlan0: associated
[58754.201782] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[58764.752091] wlan0: no IPv6 routers present
[58794.113219] wlan0: deauthenticating from 00:06:25:ed:1f:e7 by local choice 
(reason=3)
[58794.154772] cfg80211: Calling CRDA to update world regulatory domain
[58798.388367] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58798.501233] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58799.112130] atl1c :01:00.0: MAC state machine can't be idle since 
disabled for 10ms second
[58799.203751] atl1c :01:00.0: irq 45 for MSI/MSI-X
[58799.420311] atl1c :01:00.0: Error get phy ID
[58799.421380] ADDRCONF(NETDEV_UP): eth0: link is not ready
[58954.727020] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[58955.340103] atl1c :01:00.0: MAC state machine can't be idle since 
disabled for 10ms second
[58955.364512] atl1c :01:00.0: irq 45 for MSI/MSI-X
[58955.584322] atl1c 

Bug#645489: linux-image-3.0.0-1-amd64: just an info: weired message at start

[Hans-J. Ullrich]

Package: linux-image-3.0.0-1-amd64
Severity: minor



-- System Information:
Debian Release: wheezy/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash

Dear maintainers,

since kernel version 3.X on my 64-bit system the very first kernel message I 
get, is the 
following:


[ 0.248203] pci_root PNP0A08:00 address space collision: host bridge 
window
[mem 0x000cc000-0x000cfff] conflicts with Video ROM [mem 0x000c-0x000cd9ff]
Loading, please wait.


It might be interesting for you, so I thought it worth, to send you this 
information.
Please remark, that there are no problems on my system, everything is working 
perfectly 
so far as I can see. This message intend just to give you this information!
Maybe it is usefull for you.

Please feel free to contact me for further informations.
 
Best regards

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201110161101.55018.hans.ullr...@loop.de

Bug#620848: Bug can be closed

[Hans-J. Ullrich]

Dear maintainers,

I found out, that this behavior appears only on Nvidia hardware. As it seems, 
I am the only one in the world, who is using the combination of 

[MCP67 OHCI USB 1.1 Controller (rev a2)] + =Kernel 2.6.32-5-amd64 + 64-bit-
System

you can safely close this bug. The bug is opened at bugzilla.,kernel.org with 
bugnumber #22052 if there is surprising someone withe the same hardware and 
software and problems as me.

Thank you for all people, who cared about this.

Best regards

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107061739.37830.hans.ullr...@loop.de

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

Dear maintainers,

this bug is also and still in 2.6.39-rc7-amd64 from debian/experimental.
Jonathan's patch did not work. Maybe we should revert to the ohci-hcd module 
from the last working kernel? I checked some livefile systems, with newer 
kernels - they got the same result (for example BackTrack5).

I suggest, to merge this bugreport and #620848.

With this bug, these kernels are still not usable for me (and I suppose, there 
might be other people with the same problem, too)


Please don't feel annoied by me, I just wanted to mention, there is IMO a big 
problem. Thank you for your considerateness.

Best regards

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201105222307.21472.hans.ullr...@loop.de

Bug#620848: linux-image-2.6.32-5-amd64 (and all higher versions): unable to enumerate usb device 6

[Hans-J. Ullrich]

Dear maintainers,

this bug is also in 2.6.39-rc7-amd64 from experimental.

Best regards

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201105162126.44342.hans.ullr...@loop.de

Bug#620848: linux-image-2.6.38-5-amd64: unable to enumerate usb device 6

[Hans-J. Ullrich]

Dear kernel-maintainers,

it would be nice at bug number #620848, as this bug is still persistent in all 
actual kernels, and not only in the 2.6.32-series.

To make this bug more important, shall I file a new bugreport to the latest 
kernel version? 

It seems, no one cares, as people believe, this bug belongs just to an older 
kernel, but it is existent in the latest kernel, too.

Thank you for reading this.

Best regards

Hans




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201105152229.32945.hans.ullr...@loop.de

Bug#620848: linux-image-2.6.32-5-amd64 (and ALL kernels above) : unable to enumerate usb device 6

[Hans-J. Ullrich]

Hi all,

I have to tell, that ALL kernels higher than version *-2.6.32-5-amd64
show this bug.

This means, also ALL livefilesystems are not usable.

I dicovered this bug i.e. in Backtrack5.

Regards

Hans
 



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201105132109.51152.hans.ullr...@loop.de

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

Hi Jonathan,

thank you for building the kernel with the patch. I just tested it, but sadly 
I got the same problem again. So I think, Alan's patch does not generate the 
wished result.

To make sure, to get rid of old modules, i completely deinstalled all 2.6.38-
packages (image and header-files), but had no success.

Sorry for that! The bug is still existent.

However, your work helped me a lot, to test it fast.

Thanks!

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104171209.09979.hans.ullr...@loop.de

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

Am Freitag, 15. April 2011 schrieb Hans-J. Ullrich:
  I'll handle this, Alan.
  
  Ben.
 
 Thank you very much, Ben!
 
 Hans
Hi Ben, Alan and Jonathan,

I was not lazy and again tried to rebuild the module(s) with the patched 
source-code, but did not succeed. I downloaded the kernel-sources, unpacked 
them to /usr/src and then linked the sources to /usr/src/linux.

Copying /boot/config-2.6.38-2-amd64 to /usr/src/inux/.config.
Then started make menuconfig and added in version option -2-amd64, to make 
sure I have the same version than the running kernel.

After this I started make modules below /usr/src/linux, to build just the 
modules. After building them, I copied ohci-hcd.ko and ehci-hcd.ko to 
/lib/modules/2.6.38-2-amd64/drivers/usb/host and overwrote the existing *-
hcd.ko modules.

With depmod -a I finished.

But I can still not load those kernel modules. I also remarked, the new ones 
are much bigger (old ones are about 60kB, the new ones about 700kB).

I also tried make-kpkg --append-to-version=-2-amd64 modules_image but the 
process stops at the point, where it wants to clean up ( /usr/bin/make clean 
is the last line I see).

What did I do wrong? In the past, I already build some kernels, but the last 
one was a long time ago (I think, it was 2.6.20 something) and did it by using 
make-kpkg.

However, when the patched kernel-package is uploaded, Or if you will send me a 
download-link to a package, I will be very pleased to test it!

Thank you very much for your help.

Cheers


Hans 



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104161419.51362.hans.ullr...@loop.de

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

Hi Jonathan,


 Debian kernels have CONFIG_MODVERSIONS=y set:
yes, this is set!

 entire kernels still.  Did you try make deb-pkg?
No, I dis not.


I tried modprobe ohci-hcd, but got no output. 
Well, for now, I gave up. As Ben wanted to handle the patch, I suppose, there 
will be a new kernel-version during the next days. Then I will test it and 
this way, other people can test it, too.

In the German-user-list people wrote of the same problem and so there are more 
testers than only me.

I will report as soon as possible.

Best regards

Hans

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

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

Am Freitag, 15. April 2011 schrieb Alan Stern:
 On Fri, 15 Apr 2011, Ben Hutchings wrote:
  On Wed, 2011-04-13 at 18:32 +0200, Hans-J. Ullrich wrote:
  [...]
  
   I get massive messages from the kernel unable to enumerate USB device
   on port 6 which is making the pc slower and
   which is filling up my syslog. The problem is caused by the ohci-hcd
   kernel module. Unloading it, is stopping
   the messages, but then the mouse will not work (of course).
   
   This bug appeared the first time at the change from
   linux-image-2.6.32-5-amd64-30 -- linux-image-2.6.32-5-amd64-31 (and
   higher!)
   and it appeared only on 64-bit-systems.
  
  [...]
  
  The only change to ohci-hcd between these versions was:
  
  commit 5f528de0ef9b3e092e276d95930830b847b33dc4
  Author: Alan Stern st...@rowland.harvard.edu
  Date:   Fri Sep 10 16:37:05 2010 -0400
  
  OHCI: work around for nVidia shutdown problem
  
  commit 3df7169e73fc1d71a39cffeacc969f6840cdf52b upstream.
  
  The reporter's system does indeed have an nVidia MCP67 chipset.  Full
  details (kernel log, lspci, etc.) are at http://bugs.debian.org/620848
  and http://bugs.debian.org/622649.
 
 Hans, can you test whether the patch below fixes your problem?
 
 Alan Stern
 
 
 
 Index: usb-2.6/drivers/usb/host/ohci-pci.c
 ===
 --- usb-2.6.orig/drivers/usb/host/ohci-pci.c
 +++ usb-2.6/drivers/usb/host/ohci-pci.c
 @@ -207,10 +207,18 @@ static int ohci_quirk_amd700(struct usb_
   */
  static int ohci_quirk_nvidia_shutdown(struct usb_hcd *hcd)
  {
 + struct pci_dev *pdev = to_pci_dev(hcd-self.controller);
   struct ohci_hcd *ohci = hcd_to_ohci(hcd);
 
 - ohci-flags |= OHCI_QUIRK_SHUTDOWN;
 - ohci_dbg(ohci, enabled nVidia shutdown quirk\n);
 + /* Evidently nVidia fixed their later hardware; this is a guess at
 +  * the changeover point.
 +  */
 +#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_USB0x026d
 +
 + if (pdev-device  PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_USB) {
 + ohci-flags |= OHCI_QUIRK_SHUTDOWN;
 + ohci_dbg(ohci, enabled nVidia shutdown quirk\n);
 + }
 
   return 0;
  }
Hello Alan, 

it lasted a little bit, as I am not very experienced with patching of source-
code. However, I did as you suggested, and hope I did everything correct. 

I compiled the source again and it worked. Please take e look at the source 
code. I send it below.

If I did it correct, I suggest, to patch all versions of the linux kernel 
since version 2.6.32-5-amd64-30 and higher.

Maybe a new and patched kernel version should be uploaded to the repository as 
soon as possible, what do you think?

Thank you very much for your help!!!

Cheers 

Hans





/*
 * OHCI HCD (Host Controller Driver) for USB.
 *
 * (C) Copyright 1999 Roman Weissgaerber wei...@vienna.at
 * (C) Copyright 2000-2002 David Brownell dbrown...@users.sourceforge.net
 *
 * [ Initialisation is based on Linus'  ]
 * [ uhci code and gregs ohci fragments ]
 * [ (C) Copyright 1999 Linus Torvalds  ]
 * [ (C) Copyright 1999 Gregory P. Smith]
 *
 * PCI Bus Glue
 *
 * This file is licenced under the GPL.
 */

#ifndef CONFIG_PCI
#error This file is PCI bus glue.  CONFIG_PCI must be defined.
#endif

#include linux/pci.h
#include linux/io.h


/* constants used to work around PM-related transfer
 * glitches in some AMD 700 series southbridges
 */
#define AB_REG_BAR	0xf0
#define AB_INDX(addr)	((addr) + 0x00)
#define AB_DATA(addr)	((addr) + 0x04)
#define AX_INDXC	0X30
#define AX_DATAC	0x34

#define NB_PCIE_INDX_ADDR	0xe0
#define NB_PCIE_INDX_DATA	0xe4
#define PCIE_P_CNTL		0x10040
#define BIF_NB			0x10002

static struct pci_dev *amd_smbus_dev;
static struct pci_dev *amd_hb_dev;
static int amd_ohci_iso_count;

/*-*/

static int broken_suspend(struct usb_hcd *hcd)
{
	device_init_wakeup(hcd-self.root_hub-dev, 0);
	return 0;
}

/* AMD 756, for most chips (early revs), corrupts register
 * values on read ... so enable the vendor workaround.
 */
static int ohci_quirk_amd756(struct usb_hcd *hcd)
{
	struct ohci_hcd	*ohci = hcd_to_ohci (hcd);

	ohci-flags = OHCI_QUIRK_AMD756;
	ohci_dbg (ohci, AMD756 erratum 4 workaround\n);

	/* also erratum 10 (suspend/resume issues) */
	return broken_suspend(hcd);
}

/* Apple's OHCI driver has a lot of bizarre workarounds
 * for this chip.  Evidently control and bulk lists
 * can get confused.  (BW G3 models, and ...)
 */
static int ohci_quirk_opti(struct usb_hcd *hcd)
{
	struct ohci_hcd	*ohci = hcd_to_ohci (hcd);

	ohci_dbg (ohci, WARNING: OPTi workarounds unavailable\n);

	return 0;
}

/* Check for NSC87560. We have to look at the bridge (fn1) to
 * identify the USB (fn2). This quirk might apply to more or
 * even all NSC stuff.
 */
static int ohci_quirk_ns(struct usb_hcd *hcd)
{
	struct pci_dev *pdev = to_pci_dev(hcd-self.controller);
	struct pci_dev	*b;

	b  = pci_get_slot (pdev-bus

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

Hi Alan, 

I was happy too early, sorry for that. It seems, the compiled module can not 
be loaded somehow.  Maybe it is my fault and I made a mistake at editing or 
compiling.

As I told, I am not experienced with patches of source code.

However, I will be pleased, if I can help with testing. If there is a kernel-
package available, I will be pleased, to install it and send the results.

Sorry for my prior message, which I sent too early!

Best regards

Hans





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104152232.17476.hans.ullr...@loop.de

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

 
 I'll handle this, Alan.
 
 Ben.

Thank you very much, Ben!

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104152353.54909.hans.ullr...@loop.de

Bug#622649: linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6

[Hans-J. Ullrich]

 available)
pn  firmware-bnx2xnone (no description available)
pn  firmware-ipw2x00  none (no description available)
pn  firmware-ivtv none (no description available)
pn  firmware-iwlwifi  none (no description available)
pn  firmware-linuxnone (no description available)
ii  firmware-linux-nonfree0.29   Binary firmware for various driver
pn  firmware-qlogic   none (no description available)
pn  firmware-ralink   none (no description available)
pn  xen-hypervisornone (no description available)


Dear kernel-team, 

I get massive messages from the kernel unable to enumerate USB device on port 
6 which is making the pc slower and 
which is filling up my syslog. The problem is caused by the ohci-hcd kernel 
module. Unloading it, is stopping 
the messages, but then the mouse will not work (of course).

This bug appeared the first time at the change from 
linux-image-2.6.32-5-amd64-30 -- linux-image-2.6.32-5-amd64-31 (and higher!)
and it appeared only on 64-bit-systems.

This message belongs to bug #620848 and can be merged with it.

It would be nice, if you could take a look at it.

Thank you very much!

Best regards

Hans-J. Ullrich



-- 
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/20110413163200.6641.8466.reportbug@localhost

Bug#620848: linux-image-2.6.32-5-amd64: unable to enumerate usb device 6 (UPDATE)

[Hans-J. Ullrich]

Hi all,
got the same bug also with kernel 2.6.38-2-amd64.

Just for info.

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104111821.18762.hans.ullr...@loop.de

Bug#620848: linux-image-2.6.32-5-amd64: unable to enumerate usb device 6

[Hans-J. Ullrich]

 it is loaded. There was a previous 
workaround by unloding ehci-usb 
module, but this does not fix it.

So, could you take a look on it? Would be very nice! The error appeared only on 
my 64-bit system,
on all 32-bit systems it is working well.

Thank you very much!

Kind regards

Hans-J. Ullrich
 



-- 
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/20110404163636.12502.79711.reportbug@localhost

Bug#580894: linux-image-2.6.32-5-amd64 crashes at boot (due to nouveau)

[Hans-J. Ullrich]

Yeah! Found out, why this kernel version crashes. The reason is the new video 
driver nouveau, which is interfering with some nvidia-garphic-cards. 

Workaround: If you are using the binary and accelerated driver nvidia-glx,  
then you will not need the nouveau driver from the kernel. Either delete it , 
or , just blacklist it. (Enter the driver in /etc/modules/blacklist.conf).

This is working for me.

Cheers

Hans



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005161208.13730.hans.ullr...@loop.de

Bug#580894: linux-image-amd64

[Hans-J. Ullrich]

:36:41 localhost kernel: [7.664990] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665063] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665110] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665156] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665202] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665247] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665291] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665336] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665382] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665427] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665473] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665518] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665562] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665607] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665651] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665696] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665741] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665785] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:41 localhost kernel: [7.665830] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:42 localhost kernel: [7.665874] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:42 localhost kernel: [7.665919] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:42 localhost kernel: [7.665936] [drm] nouveau :02:00.0: 
PFIFO still angry after 101 spins, halt
May  9 17:36:42 localhost kernel: [8.652375] [drm] nouveau :02:00.0: 
nouveau_channel_alloc: initialised FIFO 1
May  9 17:36:42 localhost kernel: [8.657735] [drm] nouveau :02:00.0: 
Detected a LVDS output
May  9 17:36:42 localhost kernel: [8.661904] [drm] nouveau :02:00.0: 
Detected a DAC output
May  9 17:36:42 localhost kernel: [8.666259] [drm] nouveau :02:00.0: 
Detected a TMDS output
May  9 17:36:42 localhost kernel: [8.670823] [drm] nouveau :02:00.0: 
DCB encoder 1 unknown
May  9 17:36:42 localhost kernel: [8.675701] [drm] nouveau :02:00.0: 
Detected a LVDS connector
May  9 17:36:42 localhost kernel: [8.777526] [drm] nouveau :02:00.0: 
Detected a VGA connector
May  9 17:36:42 localhost kernel: [8.782930] [drm] nouveau :02:00.0: 
Detected a DVI-D connector
May  9 17:36:42 localhost kernel: [8.807587] ACPI: EC: GPE storm detected, 
transactions will use polling mode
May  9 17:36:42 localhost kernel: [9.812088] ACPI: PCI Interrupt Link 
[LAZA] enabled at IRQ 21
May  9 17:36:42 localhost kernel: [9.818785] HDA Intel :00:07.0: PCI 
INT A - Link[LAZA] - GSI 21 (level, low) - IRQ 21
May  9 17:36:42 localhost kernel: [9.826695] hda_intel: Disable MSI for 
Nvidia chipset
Ma

 
- snap 

It seems, this is the problem. With any other kernels it works. On my EEEPC 
1005HA, which is i386 ans on my desktop PC (AMD Athlon), 
which is i386, too, both kernels *-5-amd64 are working fine.

If required, I can send you the whole kernel.log, too.


Best regards


Hans-J. Ullrich



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

looking for kernel-maintainer

[Hans-J. Ullrich]

Dear maintainers,

sorry to write here, but at the moment it is not possible, to register or send 
bugreports to bugzilla.kernel.org. 

Seems the mailsystem is completely down. So I even cannot send the message, 
that the mailservice is down, too.

I hope, that one of the kernel-maintainers might read this message here and 
will have a look on this.

The bugreport I want to send, is about the kernel-module ath5k, which is now 
maintained by the kernel-maintainers themselves. Where can I send it, if not 
to bugzilla.kernel.org?

Please inform the kernel-maintainers of their problem, when you know one! 

Thank you very much!

Hans-J. Ullrich


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org