Bug#926717: linux-image-4.19.0-4-amd64: Size of DVD in external drive not recognised properly
On Tue, Apr 09, 2019 at 05:00:49PM +0200, Jan wrote: > JFTR: I do not have 'udftools' installed. Hi Jan, Is there any mention of pktsetup or pktcdvd in dmesg? Although you don't have udftools installed, it seems most of the implementation is in the kernel; udftools's pktsetup is just a userland tool for running modprobe, sending a couple of ioctls, and printing status. BTW, thanks for the hint about udftools, it solved my problem if not yours. BR, Steve
Bug#930860: linux-image-4.19.0-5-amd64: USB Camera seen as multiple devices
On Fri, Jun 21, 2019 at 04:07:25PM +0200, Seba Kerckhof wrote: > Under Debian 10 rc1, when I plug in my USB camera (the very common logitech > c930e), 2 devices are added (e.g. /dev/video0 and /dev/video1). > > v4l-info works on /dev/video0, but fails on /dev/video1 > (VIDIOC_G_FMT(VIDEO_CAPTURE): Invalid argument). When I try to access the > device using gstreamer it tells me that /dev/video1 is not a capture device. This is the feature added in commit 088ead25524583e2200aa99111bea2f66a86545a. media: uvcvideo: Add a metadata device node Some UVC video cameras contain metadata in their payload headers. This patch extracts that data, adding more clock synchronisation information, on both bulk and isochronous endpoints and makes it available to the user space on a separate video node, using the V4L2_CAP_META_CAPTURE capability and the V4L2_BUF_TYPE_META_CAPTURE buffer queue type. By default, only the V4L2_META_FMT_UVC pixel format is available from those nodes. However, cameras can be added to the device ID table to additionally specify their own metadata format, in which case that format will also become available from the metadata node. Guennadi, sorry but this feels more like a bug than a feature to me, and at least three other people have reported it as a bug without working out the cause. * https://bugs.debian.org/930860 * https://bugzilla.kernel.org/show_bug.cgi?id=199193 * https://bugzilla.kernel.org/show_bug.cgi?id=199575 Seba, thanks for reporting this. I met this feature while working on a closed-source application, added a workaround to ignore cameras that don't support normal video capture, and haven't yet got round to replying to the Bugzilla reports above. I'd be happy if someone else took on that task. BR, Steve
Bug#858078: Kernel hangs most of the times when modeset=1 on the i915
On Sat, Mar 18, 2017 at 01:53:09AM +0100, Santiago Garcia Mantinan wrote: > I just upgraded this machine from Jessie to Stretch and found the kernel > crashing (computer completelly frozen) most of the times, even if X is not > started. I then tried to use the kernel from Jessie with current packages > from Stretch and found that it works perfectly, like it used to on Jessie. > ? dump_stack+0x5c/0x78 > ? __warn+0xbe/0xe0 > ? warn_slowpath_fmt+0x5f/0x80 > ? finish_wait+0x3c/0x70 > ? drm_wait_one_vblank+0x197/0x1a0 [drm] > ? prepare_to_wait_event+0xf0/0xf0 > ? intel_get_load_detect_pipe+0x624/0x640 [i915] > ? intel_tv_detect+0x155/0x550 [i915] > ? drm_property_replace_global_blob+0xd8/0x120 [drm] > ? drm_helper_probe_single_connector_modes+0x3f6/0x4e0 [drm_kms_helper] Hi Manty, Does adding video=SVIDEO-1:d to the kernel command line also fix it? There's an upstream bug that "some that of the TV encoding registers not being set properly before trying to call intel_wait_for_vblank()" https://bugs.freedesktop.org/show_bug.cgi?id=93782 BR, Steve
Re: Bug#765380: don't ship gcc-4.8 with jessie
On Tue, Oct 14, 2014 at 05:25:13PM +0200, Matthias Klose wrote: Package: src:gcc-4.8 Version: 4.8.3-11 Severity: serious Tags: sid jessie The current default for GCC (4.9) is good enough for jessie. Don't ship legacy compilers with jessie. Hi Matthias, Removing GCC 4.8 will need Linux kernel ABI transitions. I haven't seen any discussion on the debian-kernel list, and the latest of the Linux package (uploaded to sid this week) still has it generating linux-compiler-* packages depending on gcc-4.8, so I think the Linux maintainers are expecting GCC 4.8 to be in Jessie. (CC'ing the debian-kernel list for comments) Regards, Steve -- 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/2014101717.ga2...@s.cotton.clara.co.uk
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
On Tue, Oct 15, 2013 at 14:08 +0200, Petter Reinholdtsen wrote: Dear Maintainer, I just bought a USB wifi dongle and it fail to work with the Linux kernel in Debian Stable/Wheezy. lsusb show this information about the device: Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp. But I was hoping this dongle would work out of the box with Debian stable, or at least with the next stable (Jessie). Can you add the driver to the kernel package to make this happen? Hi Petter, That device should work with kernel 3.10, module rtl8188ee.ko. Upstream commits: f0eb856...8b138d4 So there is source out there to get this working with Linux. I hope to test it later today. I think the Jessie kernel will already support it. Regards, Steve -- 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/20131015141252.ga5...@s.cotton.clara.co.uk
Bug#726398: linux: Fail to work with USB wifi dongle TP-Link TL-WN725N V2 (USB id 0bda:8179)
On Tue, Oct 15, 2013 at 16:33 +0200, Bjørn Mork wrote: Steve Cotton st...@s.cotton.clara.co.uk writes: That device should work with kernel 3.10, module rtl8188ee.ko. I doubt that. r(tl)8188ee is a PCI-E chip and driver. The USB version is r(tl)8188eu. See http://wireless.kernel.org/en/users/Drivers/rtl819x for the full overview. Bjørn Sorry for incorrect information. Bjørn is correct. (I guess it's better to confirm this in the BTS log than not to). Steve -- 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/20131015151622.ga7...@s.cotton.clara.co.uk
Re: Enabling power management on Debian
On Wed, Sep 18, 2013 at 08:45:56PM -0700, Josef Bailey wrote: I'm trying to enable power management on my debian box .. currently im on wheezy Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux ... modprobe p4-clockmod Hi Josef, p4-clockmod seems to be a hack that shouldn't be needed on Core i5 devices. Please try https://wiki.debian.org/HowTo/CpuFrequencyScaling The debian-kernel is a development lists, debian-user is more appropriate for support requests. Steve -- 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/20130919104958.ga28...@s.cotton.clara.co.uk
Bug#718825: linux-image-3.10-1-amd64: Sound freezes when using usb audio card
On Mon, Aug 05, 2013 at 11:30:26PM +0200, Sergheu Mihai wrote: Running actually the version 3.10, which according to the above sources fixes the regression, I still have the bug. Hi Sergheu, There's further fixes going in to 3.11, and the upstream testing on a Scarlett 2i4 is in Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1185563 57e6dae1087b ALSA: usb-audio: do not trust too-big wMaxPacketSize values 24f531371de1 USB: EHCI: accept very late isochronous URBs Regards, Steve -- 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/20130819112331.ga21...@s.cotton.clara.co.uk
Bug#681418: #681418 debugfs is a big security hole
On Tue, Jul 30, 2013 at 03:37:52PM +0300, Timo Juhani Lindfors wrote: Steve Cotton st...@s.cotton.clara.co.uk writes: For me the mount point changes permission when mounted, and from the hard link count I guess you have it unmounted. That might indeed be true. I can't reproduce the bug with linux-image-3.10-1-amd64 3.10.3-1 today. I'd like to revert the found 681418 3.8.5-1~experimental.1, and close the bug again. Thanks, Steve -- 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/20130807093350.ga6...@s.cotton.clara.co.uk
Bug#718825: linux-image-3.10-1-amd64: Sound freezes when using usb audio card
On Mon, Aug 05, 2013 at 11:30:26PM +0200, Sergheu Mihai wrote: Since a couple on months, I'm using an external usb sound card(Scarlett Focusrite 2i2) for some audio production. I use it mainly with jackd, zynaddsubfx, fluidsynth. Constantly I face some sound freezes when using the card and the kernel reports me the following: [89828.051969] cannot submit urb (err = -18) [89828.051974] cannot submit urb (err = -18) [89828.051982] cannot submit urb (err = -18) [89828.051988] cannot submit urb (err = -18) Hi Sergheu, In this context errno 18 (EXADEV) could mean that audio data is arriving at the USB stack too late. I'm wondering if it's simply that the userland programs can't keep up. Was it working correctly when you first bought it, and if so, which is the last kernel version that it worked on? Does it freeze when playing simple audio (.wav files for example)? Using the synth programs, are you just playing back prerecorded sounds? Are you using it as a live musical instrument (pressing buttons and needing the sound to change immediately)? What's the load / cpu usage on your laptop just before the sound freezes? Could you try turning off swap (to eliminate a cause of latency)? From the hardware, I'm guessing it's an old laptop. Please could you retest on a more powerful PC? Regards, Steve -- 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/20130806084650.ga1...@s.cotton.clara.co.uk
Bug#681418: #681418 debugfs is a big security hole
On Sun, May 05, 2013 at 12:24:44PM +0300, Timo Juhani Lindfors wrote: the issue still exists in experimental lindi3:~$ ls -ld /sys/kernel/debug drwxr-xr-x 2 root root 0 May 5 12:02 /sys/kernel/debug lindi3:~$ cat /proc/version Linux version 3.8-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.8.5-1~experimental.1 Hi Timo, For me the mount point changes permission when mounted, and from the hard link count I guess you have it unmounted. tsunami:~# umount /sys/kernel/debug/ tsunami:~# ls -ld /sys/kernel/debug/ drwxr-xr-x 2 root root 0 Jul 30 13:08 /sys/kernel/debug/ tsunami:~# mount -t debugfs none /sys/kernel/debug tsunami:~# ls -ld /sys/kernel/debug/ drwx-- 16 root root 0 Jul 29 08:52 /sys/kernel/debug/ I'm using a local build of 3.10.2. Regards, Steve -- 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/20130730122411.ga20...@s.cotton.clara.co.uk
Bug#717174: corrupted kernel log file output
On Wed, Jul 17, 2013 at 03:47:24PM +0200, Harald Dunkel wrote: After some uptime kernel logging via rsyslog appears to be broken. Sample from /var/log/kern.log: Jun 1 12:23:16 mydb01b kernel: [ 45.332611] vethwUmR1j: no IPv6 routers present Jun 1 12:23:17 mydb01b kernel: [ 46.020652] br0: port 10(vethAEZSD9) entering forwarding state Jun 1 12:23:18 mydb01b kernel: [ 47.132635] eth0: no IPv6 routers present Jun 1 12:23:18 mydb01b kernel: [ 47.612642] vethAEZSD9: no IPv6 routers present Jun 1 12:23:30 mydb01b kernel: [ 59.102427] sshd (7527): /proc/7527/oom_adj is deprecated, please use /proc/7527/oom_score_adj instead. Jun 2 05:15:20 mydb01b kernel: tr58t614]as:00tam.1ai:x9y:s.4] E(0ie,=14s Oxer=i2-sN(0rliui 0) uAF4Bipu t:A 0rt2AI02ilib Jun 3 00:51:59 mydb01b kernel: F:0)rceu.ygstO:0:tyance Jun 4 08:09:26 mydb01b kernel: tru Jun 4 08:09:26 mydb01b kernel: 41RT)Dit Jun 4 08:10:10 mydb01b kernel: 241227DCNEHG hdle 020 J na 09 (Anfdavdeone5otn6[4.3 1Denas6r Jege Jun 4 08:10:10 mydb01b kernel: s Every helpful hint would be highly appreciated. Harri Hi Harri, This looks similar to #702494, does that machine have any guest VMs? Regards, Steve -- 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/20130730130604.ga20...@s.cotton.clara.co.uk
Bug#698474: usbip: May drop received isochronous packets that require padding
Control: fixed 698474 linux/3.2.41-2+deb7u1 Control: fixed 698474 linux-2.6/3.4.1-1~experimental.1 Control: fixed 698474 linux/3.4.4-1~experimental.1 On Sat, Jan 19, 2013 at 03:03:05AM +, Ben Hutchings wrote: Tags: upstream patch fixed-upstream If usbip_pad_iso() has to pad a packet, it returns the variable ret which is not initialised. If the random value that ends up in the return register has its high bit set, the caller vhci_recv_ret_submit() will treat this as failure and drop the packet. Fixed by commit ac2b41acfa3efe4650102067a99251587a806d70 upstream. Just telling the BTS where the fixes went. ac2b41a was in v3.4-rc1. 7d02c8e was in v3.2.38. It's also fixed in unstable linux/3.2.39-1. But the BTS history thinks that's a predecessor to linux-2.6/3.3~rc6-1~experimental.1, so I'm marking it fixed in the first Wheezy-only version. Steve -- 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/20130722180149.ga14...@s.cotton.clara.co.uk
Bug#521691: Info received (linux-image-2.6.29-1-amd64: appears to be a bug in netfilter)
This bug is on the LKML, thread titled: Revert gro: Fix legacy path napi_complete crash IIUC, patch 8f1ead2d1a626ed0c85b3d2c2046a49081d5933f is a workaround with further fixes coming for 2.6.29.1 / 2.6.30. That patch has been merged in to Linus' tree after 2.6.29, and adding it directly on top of Linus' v2.6.29 works-for-me. Steve -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521691: linux-image-2.6.29-1-amd64: #521691 loopback interface breaks too
Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-1 For me, the loopback interface breaks as well as ethernet CC'ing the other submitters, as that's something to test on their machines. I think this is #521691, but my computer stays online far longer than the original report - so far I've had uptimes of between 45 minutes and 13h50m before the network dies. The upgrade to 2.6.29 is also the time that eth0 became eth1, unsure if that change is from the kernel or udev. It's an upgrade from a custom-built 2.6.26; and the bug occurs both with the official Debian 2.6.29 and a make oldconfig custom one. ping -f localhost ifconfig shows both RX and TX incrementing iptables shows OUTPUT's counter incrementing, but not INPUT's Wireshark shows no packets being sent or received (tried both the lo and eth1 interfaces) ping 1.1.1.1 gets stuck doing an ARP lookup for the default gateway's address ifconfig shows both RX and TX incrementing in roughly equal amounts iptables shows OUTPUT's counter incrementing, but not INPUT's Wireshark in promisc mode shows only the outgoing ARP requests, no responses ifconfig for the *loopback* interface shows both RX and TX incrementing too, but only while the ping is running ping this machine from another machine: ifconfig shows RX incrementing, TX constant iptables shows INPUT's counter being unchanged Wireshark (on this machine) in promisc mode shows no packets being received ping6 ip6-localhost same as IPv4 measuring background network noise Without running any pings, eth1's RX is around 1 packet per 20 seconds Using forcedeth with nForce4's on-board ethernet. 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) iptables -t raw -L -v shows the same as the normal table - OUTPUT is seeing packets, PREROUTING isn't ip6tables shows the same result for the ip6-localhost ping Wireshark's main interface shows that the computer is making ARP requests for the default gateway's address, but getting no reply. Said gateway is itself crappy hardware, but this bug is new with the upgrade to 2.6.29. Wireshark's Capture interfaces dialog does show the packet counts incrementing. It also shows 5 USB buses, but their counters stay at zero. -- Package-specific info: root=/dev/sda5 ro noapic nolapic ** Not tainted (Big run-reportbug-as-root info attached bzip'd. I don't see anything interesting in there.) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.1 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-amd64 recommends no packages. Versions of packages linux-image-2.6.29-1-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v ii linux-doc-2.6.29 2.6.29-10.00.Custom Linux kernel specific documentatio -- debconf information: linux-image-2.6.29-1-amd64/preinst/overwriting-modules-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/failed-to-move-modules-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/old-dir-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/prerm/removing-running-kernel-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/create-kimage-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/initrd-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/kimage-is-a-directory: linux-image-2.6.29-1-amd64/preinst/abort-install-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/old-system-map-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/lilo-initrd-2.6.29-1-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-amd64/postinst/bootloader-test-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-amd64/preinst/elilo-initrd-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/old-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/depmod-error-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/postinst/depmod-error-initrd-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/preinst/abort-overwrite-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/bootloader-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/prerm/would-invalidate-boot-loader-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/bootloader-initrd-2.6.29-1-amd64: true 521691_full_info.txt.bz2 Description: Binary data
Bug#521691: linux-image-2.6.29-1-amd64: #521691 isn't limited to nforce hardware
package linux-image-2.6.29-1-amd64 retitle 521691 fails to reach network a short time after boot severity 521691 important thanks This doesn't seem limited to particular hardware (both nForce and 3c59x affected). Torrenting triggers the bug quite quickly. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
