Bug#968509: Further crashes under linux-image-4.19.0-10-amd64
On 30/08/2020 13:37, Richard Kettlewell wrote: > On 30/08/2020 13:22, Salvatore Bonaccorso wrote: >> Hi Richard, >>>> Would you be able to test 4.19.142? >>> >>> If you can give me a route to getting .deb files for that version then >>> sure - a download or a pointer to instructions. >> >> *unofficial* and *temporary* builds for that version can be found >> here: https://people.debian.org/~carnil/tmp/linux/4.19.142-1/ >> >> If you prefer to build the package yourself, the source package of >> this temporary work is as well uploaded there. >> >> Please let me know if that works for your. > > Thankyou, I'm running that kernel now on the first host. I'll report > back when I know more. The first host has been running that kernel without incident for 48 hours and the second for nearly 24 hours. So it looks like 4.19.142 does fix this issue. ttfn/rjk
Bug#968509: Further crashes under linux-image-4.19.0-10-amd64
On 30/08/2020 13:22, Salvatore Bonaccorso wrote: > Hi Richard, >>> Would you be able to test 4.19.142? >> >> If you can give me a route to getting .deb files for that version then >> sure - a download or a pointer to instructions. > > *unofficial* and *temporary* builds for that version can be found > here: https://people.debian.org/~carnil/tmp/linux/4.19.142-1/ > > If you prefer to build the package yourself, the source package of > this temporary work is as well uploaded there. > > Please let me know if that works for your. Thankyou, I'm running that kernel now on the first host. I'll report back when I know more. ttfn/rjk
Bug#968509: Further crashes under linux-image-4.19.0-10-amd64
On 29/08/2020 15:36, Salvatore Bonaccorso wrote: > Hi Richard, > > On Sat, Aug 22, 2020 at 12:58:47PM +0100, Richard Kettlewell wrote: >> I've had further crashes under 4.19.0-10-amd64 on a second machine. >> Again, after reverting to 4.19.0-9-amd64 this second machine seems to be >> stable. >> >> The full logs are at http://www.greenend.org.uk/rjk/junk/crashboth.log, >> a version without all the iptables clutter is attached. > > I suspect this is possibly same as #966846. If so this was fixed in > 4.19.134 upstream but followup commits were needed as up to commits in > 4.19.140 upstream. > > Would you be able to test 4.19.142? If you can give me a route to getting .deb files for that version then sure - a download or a pointer to instructions. ttfn/rjk
Bug#968509: linux-image-4.19.0-10-amd64: System hangs within a few minutes of booting
Package: src:linux Version: 4.19.132-1 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgraded from 4.19.0-9 to 4.19.0-10. * What exactly did you do (or not do) that was effective (or ineffective)? "apt-get dist-upgrade" and subsequent reboot. * What was the outcome of this action? With kernel 4.19.0-10 the system hangs within minutes. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 1101 board_vendor: ASUSTeK COMPUTER INC. board_name: PRIME H370M-PLUS board_version: Rev 1.xx ** Network interface configuration: auto lo iface lo inet loopback auto br0 iface br0 inet static network 172.17.207.0 address 172.17.207.18 netmask 255.255.255.0 broadcast 172.17.207.255 gateway 172.17.207.1 bridge_ports eno1 bridge_maxwait 2 bridge_stp off up echo 0 > /proc/sys/net/ipv6/conf/br0/accept_ra up ip address add 2001:470:1f09:11ed::12/64 dev br0 up ip route add default via 2001:470:1f09:11ed::1 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec2] (rev 07) Subsystem: ASUSTeK Computer Inc. 8th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] 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:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH USB 3.1 xHCI Host Controller [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10) Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH Shared SRAM [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:16.0 Communication controller [0780]: Intel Corporation Cannon Lake PCH HECI Controller [8086:a360] (rev 10) Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH HECI Controller [1043:8694] 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: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake PCH SATA AHCI Controller [8086:a352] (rev 10) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Cannon Lake PCH SATA AHCI Controller [1043:8694] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port [8086:a33a] (rev f0) (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 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port [8086:a330] (rev f0) (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-
Bug#801463: BUG: unable to handle kernel NULL pointer dereference at 00000001 in smp_apic_timer_interrupt
Package: src:linux Version: 3.16.7-ckt11-1+deb8u4 Severity: important Dear Maintainer, * What led up to the situation? My kernel has started crashing every few days, since 2015-09-09. The system was upgraded to this kernel (linux-image-3.16.0-4-586 3.16.7-ckt11-1+deb8u4) on 2015-09-20, so it's not a regression in that particular version. I retrieved kernel output from the most recent crash, which replaces the kernel log section below. -- Package-specific info: ** Version: Linux version 3.16.0-4-586 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-586 root=/dev/sda3 ro console=ttyS0,115200n8 ** Not tainted ** Kernel log: [587090.909477] inbound: IN=eth2 OUT= MAC=00:04:a7:08:af:b0:00:1f:27:c0:08:01:08:00 SRC=221.3.105.106 DST=86.9.121.8 LEN=60 TOS=0x00 PREC=0x00 TTL=51 ID=62653 DF PROTO=TCP SPT=39416 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0 [587134.548195] BUG: unable to handle kernel NULL pointer dereference at 0001 [587134.548195] IP: [] smp_apic_timer_interrupt+0x24/0x50 [587134.548195] *pde = [587134.548195] Oops: 0002 [#1] [587134.548195] Modules linked in: tcp_diag inet_diag xt_nat xt_addrtype ipt_MASQUERADE ip6t_REJECT xt_multiport ipt_REJECT xt_LOG xt_limit xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack ip6table_mangle iptable_mangle ip6table_raw iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip6table_filter ip6_tables iptable_filter cpufreq_stats cpufreq_conservative ip_tables x_tables cpufreq_userspace cpufreq_powersave nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc sit tunnel4 ip_tunnel evdev iTCO_wdt iTCO_vendor_support video drm_kms_helper processor pcspkr serio_raw drm thermal_sys i2c_i801 i2c_algo_bit lpc_ich rng_core i2c_core shpchp w83627hf hwmon_vid bridge stp llc loop slip slhc tun fuse autofs4 ext4 crc16 mbcache jbd2 sg sd_mod crc_t10dif crct10dif_generic crct10dif_common ata_generic 8139too ata_piix ehci_pci uhci_hcd ahci libahci ehci_hcd libata scsi_mod 8139cp r8169 mii usbcore usb_common [587134.548195] CPU: 0 PID: 0 Comm: swapper Not tainted 3.16.0-4-586 #1 Debian 3.16.7-ckt11-1+deb8u4 [587134.548195] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080012 12/22/2008 [587134.548195] task: c1592500 ti: c1584000 task.ti: c1584000 [587134.548195] EIP: 0060:[] EFLAGS: 00210896 CPU: 0 [587134.548195] EIP is at smp_apic_timer_interrupt+0x24/0x50 [587134.548195] EAX: 0001 EBX: c158beec ECX: c1585f4c EDX: c1585f4c [587134.548195] ESI: c1584001 EDI: c1585fed EBP: c1585f94 ESP: c1585f48 [587134.548195] DS: 007b ES: 007b FS: GS: 00e0 SS: 0068 [587134.548195] CR0: 8005003b CR2: 0001 CR3: 34b8a000 CR4: 0790 [587134.548195] Stack: [587134.548195] c1425474 c1585fec c1584000 c1584000 c1585fec c1585f94 [587134.548195] 0002007b 08be007b 08be 00e0 ff10 c102f1a2 0060 00200246 [587134.548195] c1009d74 c1585fec c1584000 c1585f9c c100a54e c1585fd8 c1066b40 c1585fec [587134.548195] Call Trace: [587134.548195] [] ? apic_timer_interrupt+0x34/0x40 [587134.548195] [] ? native_safe_halt+0x2/0x10 [587134.548195] [] ? default_idle+0x14/0x90 [587134.548195] [] ? arch_cpu_idle+0xe/0x10 [587134.548195] [] ? cpu_startup_entry+0x230/0x370 [587134.548195] [] ? start_kernel+0x3f2/0x3f7 [587134.548195] [] ? set_init_arg+0x3f/0x45 [587134.548195] Code: ff ff eb 80 66 90 90 55 89 e5 53 3e 8d 74 26 00 8b 0d 00 ee 59 c1 31 d2 8b 1d 48 39 59 c1 a3 48 39 59 c1 b8 b0 00 00 00 ff 91 a4 <00> 00 00 e8 d4 a4 c1 ff e8 df f6 bf ff e8 2a a5 c1 ff 89 1d 48 [587134.548195] EIP: [] smp_apic_timer_interrupt+0x24/0x50 SS:ESP 0068:c1585f48 [587134.548195] CR2: 0001 [587134.548195] ---[ end trace c2ab876b17f6fd20 ]--- [587134.548195] Kernel panic - not syncing: Attempted to kill the idle task! [587134.548195] Kernel Offset: 0x0 from 0xc100 (relocation range: 0xc000-0xf7ffdfff) [587134.548195] Rebooting in 300 seconds.. ** Model information not available ** Loaded modules: tcp_diag inet_diag xt_nat xt_addrtype ipt_MASQUERADE ip6t_REJECT xt_multiport ipt_REJECT xt_LOG xt_limit xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack ip6table_mangle iptable_mangle ip6table_raw iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip6table_filter ip6_tables cpufreq_stats iptable_filter cpufreq_conservative ip_tables x_tables cpufreq_userspace cpufreq_powersave nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc sit tunnel4 ip_tunnel evdev iTCO_wdt iTCO_vendor_support video drm_kms_helper drm processor thermal_sys i2c_algo_bit pcspkr serio_raw i2c_i801 lpc_ich shpchp i2c_core rng_core w83627hf hwmon_vid bridge stp llc loop slip slhc tun fuse autofs4 ext4 crc16 mbcache jbd2 sg sd_mod crc_t10dif crct10dif_generic crct10dif_common ata_generic 8139too
Bug#801463: BUG: unable to handle kernel NULL pointer dereference at 00000001 in smp_apic_timer_interrupt
On 2015-10-10 18:49, Ben Hutchings wrote: > This looks rather like a hardware failure, as the instruction pointer > is pointing to the middle of an instruction. Here's the disassembly of > smp_apic_timer_interrupt: Thanks for the diagnosis. Time to spend some money l-/ For future reference, is there a convenient way to get a disassembly corresponding to the kernel I have installed? ttfn/rjk
Bug#767471: [initramfs-tools] / formatted as ext3 but mounted as ext4 not fsck-able
I ran into the inverse situation: my /etc/fstab said ext3, but at runtime the initramfs looked for /sbin/fsck.ext4, and couldn't find it. Perhaps instead of special-casing ext3/ext4, it might be better to make it use 'fsck -N' (or equivalent) to discover which fsck backend will be used at runtime? In the event my system booted successfully anyway, apparently due to other things being broken: [1.849317] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray [1.851592] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.860545] sr 1:0:0:0: Attached scsi generic sg0 type 5 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [2.406902] device-mapper: uevent: version 1.0.3 [2.408440] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com done. Begin: Running /scripts/local-premount ... done. Begin: Checking root file system ... fsck from util-linux 2.25.2 fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mapper/deodand2-droot2 fsck exited with status code 8 done. Failure: An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. Warning: The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. sulogin: cannot open password database! [4.700827] sulogin[132]: segfault at 4 ip 080491f6 sp bfcec4b0 error 4 in sulogin[8048000+3000] Segmentation fault Failure: Attempt to start maintenance shell failed. Will restart in 5 seconds. [9.730265] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. [9.970645] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) [9.975644] systemd[1]: Detected virtualization 'kvm'. [9.977548] systemd[1]: Detected architecture 'x86'. Welcome to Debian GNU/Linux 8 (jessie)! [ 10.054678] systemd[1]: Inserted module 'autofs4' [ 10.059954] systemd[1]: Set hostname to deodand. [ 10.142457] systemd-default-display-manager-generator[158]: No default display manager unit service enabled, setup is manual or a sysvinit file [ 10.384669] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. [ 10.391105] systemd[1]: Expecting device dev-ttyS0.device... Expecting device dev-ttyS0.device... ttfn/rjk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54980a57.9070...@terraraq.org.uk
Bug#708058: cannot set freq 48000 to ep 0x86; beeps cause temporary gnome session hang
On 2013-05-14 03:02, Ben Hutchings wrote:
What are the contents of
/sys/devices/pci:00/:00:1d.7/usb2/2-4/quirks under 3.2?
(I'm assuming the webcam shows up at address 2-4 again - check what the
kernel log shows as the address, alongside the manufacturer and product
names.)
$ cat
/sys/devices/pci:00/:00:1a.7/usb1/1-2/{idVendor,idProduct,serial}
046d
0825
2F31AED0
$ cat /sys/devices/pci:00/:00:1a.7/usb1/1-2/quirks
0x2
$ uname -a
Linux araminta 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux
(I've moved it to a more readily accessible USB port since the original
report.)
ttfn/rjk
--
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/51927e7c.1040...@terraraq.org.uk
Bug#708058: cannot set freq 48000 to ep 0x86; beeps cause temporary gnome session hang
On 2013-05-12 21:35, Ben Hutchings wrote: Did the webcam work as an audio device under squeeze? I've just tested on a machine still running squeeze and audio capture works fine. Can you test whether this is still broken in Linux 3.8 (from unstable)? I've installed linux-image-3.8-1-amd64 3.8.12-1. It didn't produce the same behaviour immediately. I'll continue using this kernel for the time being. Audacity had trouble seeing the device (initially it was visible, after fiddling with input volume it wasn't). However, other applications could set the input volume and record from it. I don't know what criteria Audacity uses so this may be an irrelevant bug in Audacity! ttfn/rjk -- 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/51913112.70...@terraraq.org.uk
Bug#708058: cannot set freq 48000 to ep 0x86; beeps cause temporary gnome session hang
Package: src:linux Version: 3.2.41-2 Severity: normal I booted with Logitech webcam plugged in. The following message appears continuously in my kernel log: May 12 20:49:35 araminta kernel: [174158.144151] 3:3:4: cannot set freq 48000 to ep 0x86 Also, this caused my Gnome session to temporarily hang when tab completing over /var/log (probably when attempting to beep). Initial Gnome login was also very slow; I think the cause is the same. I unplugged my USB webcam. The kernel log showed then showed: May 12 20:49:40 araminta kernel: [174163.144045] 3:3:4: cannot set freq 48000 to ep 0x86 May 12 20:49:40 araminta kernel: [174163.883550] usb 2-4: USB disconnect, device number 3 May 12 20:49:40 araminta kernel: [174163.887534] 3:3:4: cannot set freq 48000 to ep 0x86 May 12 20:49:40 araminta kernel: [174163.888054] 3:3:4: cannot set freq 48000 to ep 0x86 May 12 20:49:40 araminta kernel: [174163.888438] 3:3:4: cannot set freq 48000 to ep 0x86 May 12 20:49:40 araminta kernel: [174163.889238] 3:3:4: usb_set_interface failed May 12 20:49:40 araminta kernel: [174163.889289] 3:3:4: usb_set_interface failed May 12 20:49:40 araminta kernel: [174163.889424] 3:3:4: usb_set_interface failed May 12 20:49:40 araminta kernel: [174163.889745] 3:3:4: usb_set_interface failed May 12 20:49:40 araminta kernel: [174163.890100] 3:3:4: usb_set_interface failed [etc] Beeps stopped causing hangs after this. Linux's initial view of webcam: [2.252040] usb 2-4: new high-speed USB device number 3 using ehci_hcd [2.612801] usb 2-4: New USB device found, idVendor=046d, idProduct=0825 [2.612811] usb 2-4: New USB device strings: Mfr=0, Product=0, SerialNumber=2 [2.612814] usb 2-4: SerialNumber: 2F31AED0 [3.184687] input: UVC Camera (046d:0825) as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input4 [3.184762] usbcore: registered new interface driver uvcvideo [3.184764] USB Video Class driver (1.1.1) Logitech model number is C270 HD. It's been a while since I actually attempted to use this webcam but it seemed to be OK under squeeze's kernel. ttfn/rjk -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/amfast-root ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [174087.036164] 3:3:4: cannot set freq 48000 to ep 0x86 [174088.036144] 3:3:4: cannot set freq 48000 to ep 0x86 [174089.036118] 3:3:4: cannot set freq 48000 to ep 0x86 [174090.036097] 3:3:4: cannot set freq 48000 to ep 0x86 [174091.036078] 3:3:4: cannot set freq 48000 to ep 0x86 [174092.060181] 3:3:4: cannot set freq 48000 to ep 0x86 [174093.060161] 3:3:4: cannot set freq 48000 to ep 0x86 [174094.060137] 3:3:4: cannot set freq 48000 to ep 0x86 [174095.060121] 3:3:4: cannot set freq 48000 to ep 0x86 [174096.060097] 3:3:4: cannot set freq 48000 to ep 0x86 [174097.060077] 3:3:4: cannot set freq 48000 to ep 0x86 [174098.060055] 3:3:4: cannot set freq 48000 to ep 0x86 [174099.060161] 3:3:4: cannot set freq 48000 to ep 0x86 [174100.060138] 3:3:4: cannot set freq 48000 to ep 0x86 [174101.060115] 3:3:4: cannot set freq 48000 to ep 0x86 [174102.065213] 3:3:4: cannot set freq 48000 to ep 0x86 [174103.064075] 3:3:4: cannot set freq 48000 to ep 0x86 [174104.064052] 3:3:4: cannot set freq 48000 to ep 0x86 [174105.064157] 3:3:4: cannot set freq 48000 to ep 0x86 [174106.064133] 3:3:4: cannot set freq 48000 to ep 0x86 [174107.064108] 3:3:4: cannot set freq 48000 to ep 0x86 [174108.064091] 3:3:4: cannot set freq 48000 to ep 0x86 [174109.064070] 3:3:4: cannot set freq 48000 to ep 0x86 [174110.064172] 3:3:4: cannot set freq 48000 to ep 0x86 [174111.064153] 3:3:4: cannot set freq 48000 to ep 0x86 [174112.088132] 3:3:4: cannot set freq 48000 to ep 0x86 [174113.088108] 3:3:4: cannot set freq 48000 to ep 0x86 [174114.088088] 3:3:4: cannot set freq 48000 to ep 0x86 [174115.088068] 3:3:4: cannot set freq 48000 to ep 0x86 [174116.088171] 3:3:4: cannot set freq 48000 to ep 0x86 [174117.088150] 3:3:4: cannot set freq 48000 to ep 0x86 [174118.088128] 3:3:4: cannot set freq 48000 to ep 0x86 [174119.088106] 3:3:4: cannot set freq 48000 to ep 0x86 [174120.088086] 3:3:4: cannot set freq 48000 to ep 0x86 [174121.088065] 3:3:4: cannot set freq 48000 to ep 0x86 [174122.088168] 3:3:4: cannot set freq 48000 to ep 0x86 [174123.088147] 3:3:4: cannot set freq 48000 to ep 0x86 [174124.088125] 3:3:4: cannot set freq 48000 to ep 0x86 [174125.088106] 3:3:4: cannot set freq 48000 to ep 0x86 [174126.088084] 3:3:4: cannot set freq 48000 to ep 0x86 [174127.088064] 3:3:4: cannot set freq 48000 to ep 0x86 [174128.088167] 3:3:4: cannot set freq 48000 to ep 0x86 [174129.088146] 3:3:4: cannot set freq 48000 to ep 0x86 [174130.088123] 3:3:4: cannot set freq 48000 to ep 0x86 [174131.088103] 3:3:4: cannot set freq 48000 to ep 0x86
Bug#651634: rpc.statd runs with gid=root
Package: nfs-common Version: 1:1.2.2-4 richard@araminta:~/src/3rd$ ps -ef|grep statd statd 2084 1 0 Oct11 ?00:00:00 /sbin/rpc.statd richard 6691 17917 0 18:34 pts/100:00:00 grep statd richard@araminta:~/src/3rd$ head /proc/2084/status Name: rpc.statd State: S (sleeping) Tgid: 2084 Pid:2084 PPid: 1 TracerPid: 0 Uid:103 103 103 103 Gid:0 0 0 0 FDSize: 64 Groups: gid 0 is the root login's default group, making it potentially very powerful. ttfn/rjk -- 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/4ee3a964.7010...@greenend.org.uk
Bug#638631: Crash following repeated 'page allocation failure' 'BUG: soft lockup'
On 20/08/2011 15:13, Ben Hutchings wrote: On Sat, 2011-08-20 at 12:44 +0100, Richard Kettlewell wrote: The emulated screen was blank and did not respond to any input. The kernel log is full of messages as shown below. They almost all name the same executable, apache_accesses (from package munin-node) and have the same backtraces, but are different PIDs (it is not a long-running process). The exception is a BUG: soft lockup - CPU#0 stuck for 35s! message, also below. The guest is a news server, with around a kilobyte/second of network traffic going into it at all times. The guest has 512MB RAM assigned. It has a gigabyte of swap available and doesn't seem to have been using much of it. [...] That does sound wrong. Could it be that the host is slow to service the guest's disk I/O? In summary, it does seem to be. Average latency on /dev/vda over the last week is reported as around 200ms. There are occasional spikes to multiple whole seconds. A couple of those spikes are approximately the right time for 'BUG: soft lockup' messages (but the resolution is not very high) there are other spikes with no corresponding messages in the kernel logs. That said there are similar huge latency spikes visible for the host too. I think I need some faster storage l-( As for throughput, a quick test with dd reveals the guest has about 10% of the write performance of the host, which seems pretty poor to me. ttfn/rjk -- 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/4e50de9e.9060...@greenend.org.uk
Bug#638631: Crash following repeated 'page allocation failure' 'BUG: soft lockup'
Package: linux-image-3.0.0-1-686-pae Version: 3.0.0-1 My sid KVM guest crashed yesterday. The emulated screen was blank and did not respond to any input. The kernel log is full of messages as shown below. They almost all name the same executable, apache_accesses (from package munin-node) and have the same backtraces, but are different PIDs (it is not a long-running process). The exception is a BUG: soft lockup - CPU#0 stuck for 35s! message, also below. The guest is a news server, with around a kilobyte/second of network traffic going into it at all times. The guest has 512MB RAM assigned. It has a gigabyte of swap available and doesn't seem to have been using much of it. The host is running 64-bit squeeze. ttfn/rjk Aug 18 14:30:00 deodand kernel: [1547640.899450] apache_accesses: page allocation failure: order:1, mode:0x20 Aug 18 14:30:00 deodand kernel: [1547640.899456] Pid: 456, comm: apache_accesses Not tainted 3.0.0-1-686-pae #1 Aug 18 14:30:00 deodand kernel: [1547640.899458] Call Trace: Aug 18 14:30:00 deodand kernel: [1547640.899469] [c109713f] ? warn_alloc_failed+0xb4/0xc2 Aug 18 14:30:00 deodand kernel: [1547640.899472] [c1099353] ? __alloc_pages_nodemask+0x57e/0x5e0 Aug 18 14:30:00 deodand kernel: [1547640.899478] [c10be9b5] ? cache_alloc+0x281/0x44f Aug 18 14:30:00 deodand kernel: [1547640.899481] [c10bf18b] ? kmem_cache_alloc+0x2b/0x93 Aug 18 14:30:00 deodand kernel: [1547640.899486] [c1206445] ? sk_prot_alloc+0x23/0xf7 Aug 18 14:30:00 deodand kernel: [1547640.899488] [c12065c0] ? sk_clone+0x15/0x273 Aug 18 14:30:00 deodand kernel: [1547640.899492] [c1238a83] ? inet_csk_clone+0xc/0x81 Aug 18 14:30:00 deodand kernel: [1547640.899496] [c124a454] ? tcp_create_openreq_child+0x19/0x3da Aug 18 14:30:00 deodand kernel: [1547640.899499] [c1247fc8] ? tcp_v4_syn_recv_sock+0x31/0x1bb Aug 18 14:30:00 deodand kernel: [1547640.899503] [c128c3bc] ? tcp_v6_syn_recv_sock+0x33/0x3fb Aug 18 14:30:00 deodand kernel: [1547640.899506] [c123e99d] ? tcp_parse_options+0x187/0x21c Aug 18 14:30:00 deodand kernel: [1547640.899509] [c124acfe] ? tcp_check_req+0x1e1/0x297 Aug 18 14:30:00 deodand kernel: [1547640.899512] [c123886d] ? inet_csk_search_req+0x21/0x77 Aug 18 14:30:00 deodand kernel: [1547640.899514] [c1249057] ? tcp_v4_do_rcv+0x19e/0x289 Aug 18 14:30:00 deodand kernel: [1547640.899517] [c124a062] ? tcp_v4_rcv+0x389/0x571 Aug 18 14:30:00 deodand kernel: [1547640.899521] [c1021b55] ? pvclock_clocksource_read+0xc4/0xf6 Aug 18 14:30:00 deodand kernel: [1547640.899525] [c12316d9] ? ip_local_deliver_finish+0x104/0x1a0 Aug 18 14:30:00 deodand kernel: [1547640.899529] [c12315d5] ? xfrm4_policy_check.clone.10+0x45/0x45 Aug 18 14:30:00 deodand kernel: [1547640.899531] [c12317ab] ? NF_HOOK.clone.11+0x36/0x39 Aug 18 14:30:00 deodand kernel: [1547640.899534] [c12318a4] ? ip_local_deliver+0x39/0x3c Aug 18 14:30:00 deodand kernel: [1547640.899537] [c12315d5] ? xfrm4_policy_check.clone.10+0x45/0x45 Aug 18 14:30:00 deodand kernel: [1547640.899540] [c1231571] ? ip_rcv_finish+0x2cb/0x2ea Aug 18 14:30:00 deodand kernel: [1547640.899543] [c12312a6] ? pskb_may_pull+0x2c/0x2c Aug 18 14:30:00 deodand kernel: [1547640.899545] [c12317ab] ? NF_HOOK.clone.11+0x36/0x39 Aug 18 14:30:00 deodand kernel: [1547640.899548] [c1210880] ? __netif_receive_skb+0x338/0x362 Aug 18 14:30:00 deodand kernel: [1547640.899551] [c12312a6] ? pskb_may_pull+0x2c/0x2c Aug 18 14:30:00 deodand kernel: [1547640.899554] [c1210905] ? process_backlog+0x5b/0x109 Aug 18 14:30:00 deodand kernel: [1547640.899557] [c103ae67] ? local_bh_enable+0x2/0x2 Aug 18 14:30:00 deodand kernel: [1547640.899560] [c1211630] ? net_rx_action+0x94/0x17e Aug 18 14:30:00 deodand kernel: [1547640.899563] [c103ae67] ? local_bh_enable+0x2/0x2 Aug 18 14:30:00 deodand kernel: [1547640.899565] [c103aefb] ? __do_softirq+0x94/0x130 Aug 18 14:30:00 deodand kernel: [1547640.899568] [c103ae67] ? local_bh_enable+0x2/0x2 Aug 18 14:30:00 deodand kernel: [1547640.899570] IRQ [c103ae58] ? _local_bh_enable_ip.clone.6+0x62/0x6d Aug 18 14:30:00 deodand kernel: [1547640.899575] [c12125ee] ? dev_queue_xmit+0x37b/0x388 Aug 18 14:30:00 deodand kernel: [1547640.899577] [c1234dff] ? ip_queue_xmit+0x1e6/0x302 Aug 18 14:30:00 deodand kernel: [1547640.899580] [c123430a] ? ip_finish_output2+0x1ab/0x1e6 Aug 18 14:30:00 deodand kernel: [1547640.899583] [c1233774] ? dst_output+0x9/0xa Aug 18 14:30:00 deodand kernel: [1547640.899585] [c1244d60] ? tcp_transmit_skb+0x694/0x6bb Aug 18 14:30:00 deodand kernel: [1547640.899588] [c12457dd] ? tcp_write_xmit+0x6c8/0x7b2 Aug 18 14:30:00 deodand kernel: [1547640.899591] [c1245902] ? __tcp_push_pending_frames+0x15/0x42 Aug 18 14:30:00 deodand kernel: [1547640.899595] [c123baa9] ? tcp_sendmsg+0x576/0x643 Aug 18 14:30:00 deodand kernel: [1547640.899598] [c12545d5] ? inet_sendmsg+0x47/0x4d Aug 18 14:30:00 deodand kernel: [1547640.899602] [c1202dbf] ?
Bug#628200: bug is not visible with -486 kernel.
It did not happen with the same machine's previous kernel, which my backups indicate was 2.6.32-30 (and to which I'm planning to revert if it continues crashing). Instead I tried the corresponding 486 kernel (i.e. linux-image-2.6.32-5-486 2.6.32-34squeeze1). The system has now stayed up for over a week. ttfn/rjk -- 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/4deb7bd4.8080...@greenend.org.uk
Bug#628200: 2.6.32-5-686 null pointer dereference and panic; maybe rtl8139?
Package: linux-image-2.6.32-5-686 Version: 2.6.32-34squeeze1 My Fabiatech FX5624 has started hanging within hours of boot, since upgrading to this kernel; so far this has happened three times in the last 24 hours. Console output from the most recent hang, and other info, attached. It did not happen with the same machine's previous kernel, which my backups indicate was 2.6.32-30 (and to which I'm planning to revert if it continues crashing). ttfn/rjk Loading Linux 2.6.32-5-686 ... Loading initial ramdisk ... [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 07:08:50 UTC 2011 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3f80 (usable) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fed13000 - fed1a000 (reserved) [0.00] BIOS-e820: fed1c000 - fed2 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] last_pfn = 0x3f800 max_arch_pfn = 0x10 [0.00] PAT not supported by CPU. [0.00] init_memory_mapping: -373fe000 [0.00] RAMDISK: 2f20d000 - 2fa3f22b [0.00] ACPI Error: A valid RSDP was not found (20090903/tbxfroot-219) [0.00] 132MB HIGHMEM available. [0.00] 883MB LOWMEM available. [0.00] mapped low ram: 0 - 373fe000 [0.00] low ram: 0 - 373fe000 [0.00] node 0 low ram: - 373fe000 [0.00] node 0 bootmap 00012000 - 00018e80 [0.00] (9 early reservations) == bootmem [00 - 00373fe000] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] [0.00] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] [0.00] #3 [000100 - 00014c8bb4]TEXT DATA BSS == [000100 - 00014c8bb4] [0.00] #4 [002f20d000 - 002fa3f22b] RAMDISK == [002f20d000 - 002fa3f22b] [0.00] #5 [09cc00 - 10]BIOS reserved == [09cc00 - 10] [0.00] #6 [00014c9000 - 00014cf1c1] BRK == [00014c9000 - 00014cf1c1] [0.00] #7 [01 - 012000] PGTABLE == [01 - 012000] [0.00] #8 [012000 - 019000] BOOTMAP == [012000 - 019000] [0.00] found SMP MP-table at [c00ff780] ff780 [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x000373fe [0.00] HighMem 0x000373fe - 0x0003f800 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0003f800 [0.00] Using APIC driver default [0.00] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org [0.00] Intel MultiProcessor Specification v1.4 [0.00] Virtual Wire compatibility mode. [0.00] MPTABLE: OEM ID: Intel [0.00] MPTABLE: Product ID: Alviso [0.00] MPTABLE: APIC at: 0xFEE0 [0.00] Processor #0 (Bootup-CPU) [0.00] I/O APIC #1 Version 32 at 0xFEC0. [0.00] Processors: 1 [0.00] SMP: Allowing 1 CPUs, 0 hotplug CPUs [0.00] PM: Registered nosave memory: 0009f000 - 000a [0.00] PM: Registered nosave memory: 000a - 000e [0.00] PM: Registered nosave memory: 000e - 0010 [0.00] Allocating PCI resources starting at 3f80 (gap: 3f80:a080) [0.00] Booting paravirtualized kernel on bare hardware [0.00] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1 [0.00] PERCPU: Embedded 14 pages/cpu @c200 s34328 r0 d23016 u4194304 [0.00] pcpu-alloc: s34328 r0 d23016 u4194304 alloc=1*4194304 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility
Bug#618930: High network latency with ralink usb wireless device
On 19/03/2011 22:31, Johannes Stezenbach wrote: I sent a patch to disable power save by default, but then work started to fix it instead, but then stalled. Seems like 2.6.38 shipped with broken power save enabled by default. Plese read the discussion following my RFC patch: http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-January/thread.html#3017 You can test if power saving causes your issue by disabling it with iwconfig wlan0 power off. That does the trick - thanks! richard@sfere:~$ ssh violeer uname -a Linux violeer 2.6.38-1-686 #1 SMP Wed Mar 16 17:37:47 UTC 2011 i686 GNU/Linux richard@sfere:~$ ping -qc10 violeer PING violeer.wlan.anjou.terraraq.org.uk (172.31.59.138) 56(84) bytes of data. --- violeer.wlan.anjou.terraraq.org.uk ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9016ms rtt min/avg/max/mdev = 0.919/0.981/1.089/0.057 ms richard@sfere:~$ ttfn/rjk -- 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/4d85c506.1060...@greenend.org.uk
Bug#618930: High network latency with ralink usb wireless device
Package: linux-image-2.6.38-1-686 Version: 2.6.38-1 I have a TP-Link TL-WN321G UBS wireless adapter, which is a badged Ralink RT2070. Under 2.6.32 this worked smoothly with rt2870sta. On upgrading to 2.6.38, I ran into two problems: 1) it is not automatically detected; I had to explicitly load rt2800usb. 2) ping latency is around 600ms. I see that the ralink staging drivers were disabled a few revisions back - perhaps they could be re-enabled since they work better? == Under 2.6.32 == richard@violeer:~$ uname -a Linux violeer 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 2011 i686 GNU/Linux richard@violeer:~$ iwconfig lono wireless extensions. eth0 no wireless extensions. wlan0 Ralink STA ESSID:wlan.anjou.terraraq.org.uk Nickname:RT2870STA Mode:Managed Frequency=2.442 GHz Access Point: 00:0F:CB:A0:0C:70 Bit Rate=54 Mb/s RTS thr:off Fragment thr:off Link Quality=100/100 Signal level:-45 dBm Noise level:-83 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 richard@sfere:~$ ping -qc10 violeer PING violeer.wlan.anjou.terraraq.org.uk (172.31.59.138) 56(84) bytes of data. --- violeer.wlan.anjou.terraraq.org.uk ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9013ms rtt min/avg/max/mdev = 0.973/1.094/1.490/0.141 ms == Under 2.6.38 == richard@violeer:~$ uname -a Linux violeer 2.6.38-1-686 #1 SMP Wed Mar 16 17:37:47 UTC 2011 i686 GNU/Linux richard@violeer:~$ iwconfig lono wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11bg ESSID:wlan.anjou.terraraq.org.uk Mode:Managed Frequency:2.442 GHz Access Point: 00:0F:CB:A0:0C:70 Bit Rate=18 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=67/70 Signal level=-43 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:2 Invalid misc:6 Missed beacon:0 richard@sfere:~$ ping -qc10 violeer PING violeer.wlan.anjou.terraraq.org.uk (172.31.59.138) 56(84) bytes of data. --- violeer.wlan.anjou.terraraq.org.uk ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9006ms rtt min/avg/max/mdev = 509.111/603.472/630.232/47.090 ms == lsusb output == Bus 001 Device 002: ID 148f:2070 Ralink Technology, Corp. RT2070 Wireless Adapter Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x148f Ralink Technology, Corp. idProduct 0x2070 RT2070 Wireless Adapter bcdDevice1.01 iManufacturer 1 Ralink iProduct2 802.11 g WLAN iSerial 3 1.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 67 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 450mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 7 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 1.0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT
Bug#618930: High network latency with ralink usb wireless device
On 19/03/2011 17:13, Richard Kettlewell wrote: 1) it is not automatically detected; I had to explicitly load rt2800usb. Oh, duh, that half of the problem would obviously be because I had it blacklisted. ttfn/rjk -- 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/4d84e653.6090...@greenend.org.uk
Bug#618930: High network latency with ralink usb wireless device
(see also bugs.debian.org/618930 though AFAIK everything important is reproduced in this message.) On 19/03/2011 17:30, Ben Hutchings wrote: Sorry, no. Please report this upstream to linux-wirel...@vger.kernel.org and cc the bug address. I have a TP-Link TL-WN321G USB wireless adapter, which is a badged Ralink RT2070. Under Debian's 2.6.32 this worked smoothly with rt2870sta. On upgrading to Debian's 2.6.38, however, only rt2800usb was available and with that I found that ping latency is around 600ms. == Under 2.6.32, with rt2870sta == richard@violeer:~$ uname -a Linux violeer 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 2011 i686 GNU/Linux richard@violeer:~$ iwconfig lono wireless extensions. eth0 no wireless extensions. wlan0 Ralink STA ESSID:wlan.anjou.terraraq.org.uk Nickname:RT2870STA Mode:Managed Frequency=2.442 GHz Access Point: 00:0F:CB:A0:0C:70 Bit Rate=54 Mb/s RTS thr:off Fragment thr:off Link Quality=100/100 Signal level:-45 dBm Noise level:-83 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 richard@sfere:~$ ping -qc10 violeer PING violeer.wlan.anjou.terraraq.org.uk (172.31.59.138) 56(84) bytes of data. --- violeer.wlan.anjou.terraraq.org.uk ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9013ms rtt min/avg/max/mdev = 0.973/1.094/1.490/0.141 ms == Under 2.6.38, with rt2800usb == richard@violeer:~$ uname -a Linux violeer 2.6.38-1-686 #1 SMP Wed Mar 16 17:37:47 UTC 2011 i686 GNU/Linux richard@violeer:~$ iwconfig lono wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11bg ESSID:wlan.anjou.terraraq.org.uk Mode:Managed Frequency:2.442 GHz Access Point: 00:0F:CB:A0:0C:70 Bit Rate=18 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=67/70 Signal level=-43 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:2 Invalid misc:6 Missed beacon:0 richard@sfere:~$ ping -qc10 violeer PING violeer.wlan.anjou.terraraq.org.uk (172.31.59.138) 56(84) bytes of data. --- violeer.wlan.anjou.terraraq.org.uk ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9006ms rtt min/avg/max/mdev = 509.111/603.472/630.232/47.090 ms == lsusb output == Bus 001 Device 002: ID 148f:2070 Ralink Technology, Corp. RT2070 Wireless Adapter Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x148f Ralink Technology, Corp. idProduct 0x2070 RT2070 Wireless Adapter bcdDevice1.01 iManufacturer 1 Ralink iProduct2 802.11 g WLAN iSerial 3 1.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 67 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 450mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 7 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 1.0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType
Bug#515982: Bug#511703: text_poke_early crash and noreplace-paravirt
Ben Hutchings wrote: I don't have any 486-class systems to test this on, so perhaps you could try this patch: That works for me. Booting 'Debian GNU/Linux, kernel 2.6.26-2-486-511703' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.26-2-486-511703 root=/dev/hda1 ro console=ttyS0,57600 n8 [Linux-bzImage, setup=0x3000, size=0x164590] initrd /boot/initrd.img-2.6.26-2-486 [Linux-initrd @ 0x3d8, 0x26fd3f bytes] Probing EDD (edd=off to disable)... ok [...] [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26 (2.6.26) (rich...@leucomorph) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 Tue Sep 8 11:31:50 BST 2009 [...] [0.104006] CPU: AMD Am5x86-WB stepping 04 [0.112007] Checking 'hlt' instruction... OK. [0.156009] Freeing SMP alternatives: 0k freed [0.160010] ACPI: Core revision 20080321 [...] ttfn/rjk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511703: text_poke_early crash and noreplace-paravirt
I saw the text_poke_early crash too, on a Soekris net4501, which uses an AMD ElanSC520. The problem may or may not apply to other 486-class hardware (some reports of the bug say it does). The workaround is to specify noreplace-paravirt on the kernel command line. If the bug does indeed affect all 486-class CPUs then it would be a good idea to compile CONFIG_PARAVIRT out of the -486 kernels entirely, at least until such time as the bug is fixed. ttfn/rjk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506420: incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
Aurelien Jarno wrote: On Fri, Nov 21, 2008 at 10:14:29AM +, Richard Kettlewell wrote: Package: libc6-xen Version: 2.7-16 As shipped, /etc/ld.so.conf.d/libc6-xen.conf read as follows: # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 1 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 1 nosegneg However I still got thousands of 4gb seg fixup messages and ldd revealed that the runtime linker was not using the Xen-friendly Libc. Changing the 1 to 0, based on a mailing list posting I found, fixed the problem. Unfortunately I've not found where any of this is documented (the ldconfig man page does not contain any useful pointers) so this is slightly guesswork on my part. Perhaps the man page could be improved. The value in this file is the correct one. Where is this documented? ttfn/rjk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387919: stuck file under 'System Volume Information' in Windows XP NTFS
Package: kernel-image-2.6.8-3-k7
Version: 2.6.8-16sarge4
My Windows XP partition contains, among other things, the following
file, as seen under Linux:
-r-xr-x--- 2 root dos 512K Jun 16 2005 /tsais/System Volume
Information/_restore{8B199B4A-7BC9-4D0D-A34A-84F47D527625}/RP2/snapshot/_REGISTRY_USER_NTUSER_S-1-5-21-1482476501-2139871995-682003330-1005
If I try to read it under Linux then, part way through the file,
cat hangs in read() and cannot be interrupted by ^C or SIGKILL.
Other processes are not affected, and I can still read other files off
that filesystem.
dmesg reveals no relevant messages.
I tried cat'ing the underlying block device to /dev/null. This worked
fine, implying that the problem is in the Linux ntfs driver, rather
than a hard disk fault.
I tried running XP's disk checking tool. This was happy with
filesystem and the problem persisted when back in Linux.
The 'System Volume Information' appears to be invisible in XP -
perhaps it is something internal to NTFS? - so I cannot trivially
check whether the file can be read OK under XP.
$ mount|grep tsais
/dev/hda2 on /tsais type ntfs (ro,gid=500,umask=007)
$ uname -a
Linux lyonesse 2.6.8-3-k7 #1 Sat Jul 15 09:58:38 UTC 2006 i686 GNU/Linux
ttfn/rjk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
#296464: initrd and encrypted swapfiles
Hello, I sent this to debian-devel but judging by the archive pages it did not get through. debian-kernel may be a better choice of destination anyway. ttfn/rjk From: Richard Kettlewell [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: #296464: initrd and encrypted swapfiles Date: Fri, 8 Sep 2006 20:29:06 +0100 Summary of bug: kernels that use initrd cannot boot systems with encrypted swap files that get their key from /dev/random. Daniel's patch works for me. Since some systems cannot be booted using a distribution kernel without this fix, please could it, or something equivalent, be included in future versions, and distribution kernels that include initrds built against it? Thanks in advance. ttfn/rjk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296464: #296464: initrd and encrypted swapfiles
Summary of bug: kernels that use initrd cannot boot systems with encrypted swap files that get their from /dev/random. Daniel's patch works for me. Since some systems cannot be booted using a distribution kernel without this fix, please could it, or something equivalent, be included in future versions, and distribution kernels that include initrds built against it? Thanks in advance. ttfn/rjk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
