Bug#583686: Kernel exceptions in ext3/journal subsystem
Package: linux-2.6 Version: 2.6.32-13 Severity: important Hi! Running sbuild with lvm snapshots seems to hang and the kernel is spitting out error messages. Seems it is having some trouble! Unfortunately I'm no kernel expert so if you need something please ask. Regards Christoph -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-13) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-10) ) #1 Tue May 18 19:39:04 UTC 2010 ** Command line: root=/dev/mapper/michelangelo-root ro ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 601.538740] debconf-set-s D 0fd51810 0 1424 1414 0x [ 601.544871] Call Trace: [ 601.550905] [d66dfcb0] [d7690a3c] 0xd7690a3c (unreliable) [ 601.557095] [d66dfd70] [c00097d4] __switch_to+0x78/0x90 [ 601.563304] [d66dfd80] [c03754ac] schedule+0x468/0x4b4 [ 601.569504] [d66dfdd0] [c0375560] io_schedule+0x68/0xc4 [ 601.575688] [d66dfdf0] [c00bf4d4] sync_page+0x5c/0x70 [ 601.581830] [d66dfe00] [c0375be8] __wait_on_bit+0x68/0xc0 [ 601.587926] [d66dfe20] [c00bf79c] wait_on_page_bit+0xc4/0xd8 [ 601.593984] [d66dfe60] [c00c0208] wait_on_page_writeback_range+0x6c/0x148 [ 601.600070] [d66dfee0] [c00c0444] filemap_write_and_wait_range+0x70/0x94 [ 601.606163] [d66dff00] [c0116954] vfs_fsync_range+0x54/0xb4 [ 601.612175] [d66dff20] [c0116a74] do_fsync+0x30/0x54 [ 601.618068] [d66dff40] [c00153dc] ret_from_syscall+0x0/0x40 [ 601.623887] --- Exception: c01 at 0xfd51810 [ 601.623893] LR = 0xfae42b8 [ 721.633748] INFO: task kjournald:1319 blocked for more than 120 seconds. [ 721.639677] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 721.645683] kjournald D 0 1319 2 0x [ 721.651777] Call Trace: [ 721.657756] [d6ab1d00] [d66d8b10] 0xd66d8b10 (unreliable) [ 721.663895] [d6ab1dc0] [c00097d4] __switch_to+0x78/0x90 [ 721.670008] [d6ab1dd0] [c03754ac] schedule+0x468/0x4b4 [ 721.676097] [d6ab1e20] [c0375560] io_schedule+0x68/0xc4 [ 721.682182] [d6ab1e40] [c0119830] sync_buffer+0x50/0x64 [ 721.688201] [d6ab1e50] [c0375be8] __wait_on_bit+0x68/0xc0 [ 721.694233] [d6ab1e70] [c0375d04] out_of_line_wait_on_bit+0xc4/0xd8 [ 721.700300] [d6ab1ec0] [c011971c] __wait_on_buffer+0x2c/0x3c [ 721.706348] [d6ab1ed0] [da6763ac] journal_commit_transaction+0x484/0xf20 [jbd] [ 721.712499] [d6ab1f70] [da679cc0] kjournald+0xb4/0x1d4 [jbd] [ 721.718585] [d6ab1fc0] [c00625fc] kthread+0x74/0x78 [ 721.724549] [d6ab1ff0] [c001512c] kernel_thread+0x4c/0x68 [ 721.730409] INFO: task debconf-set-sel:1424 blocked for more than 120 seconds. [ 721.736381] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 721.742437] debconf-set-s D 0fd51810 0 1424 1414 0x [ 721.748555] Call Trace: [ 721.754572] [d66dfcb0] [d7690a3c] 0xd7690a3c (unreliable) [ 721.760740] [d66dfd70] [c00097d4] __switch_to+0x78/0x90 [ 721.766936] [d66dfd80] [c03754ac] schedule+0x468/0x4b4 [ 721.773121] [d66dfdd0] [c0375560] io_schedule+0x68/0xc4 [ 721.779298] [d66dfdf0] [c00bf4d4] sync_page+0x5c/0x70 [ 721.785431] [d66dfe00] [c0375be8] __wait_on_bit+0x68/0xc0 [ 721.791515] [d66dfe20] [c00bf79c] wait_on_page_bit+0xc4/0xd8 [ 721.797565] [d66dfe60] [c00c0208] wait_on_page_writeback_range+0x6c/0x148 [ 721.803652] [d66dfee0] [c00c0444] filemap_write_and_wait_range+0x70/0x94 [ 721.809732] [d66dff00] [c0116954] vfs_fsync_range+0x54/0xb4 [ 721.815730] [d66dff20] [c0116a74] do_fsync+0x30/0x54 [ 721.821610] [d66dff40] [c00153dc] ret_from_syscall+0x0/0x40 [ 721.827429] --- Exception: c01 at 0xfd51810 [ 721.827434] LR = 0xfae42b8 [ 841.837754] INFO: task kjournald:1319 blocked for more than 120 seconds. [ 841.843703] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 841.849694] kjournald D 0 1319 2 0x [ 841.855778] Call Trace: [ 841.861751] [d6ab1d00] [d66d8b10] 0xd66d8b10 (unreliable) [ 841.867862] [d6ab1dc0] [c00097d4] __switch_to+0x78/0x90 [ 841.873959] [d6ab1dd0] [c03754ac] schedule+0x468/0x4b4 [ 841.880038] [d6ab1e20] [c0375560] io_schedule+0x68/0xc4 [ 841.886115] [d6ab1e40] [c0119830] sync_buffer+0x50/0x64 [ 841.892125] [d6ab1e50] [c0375be8] __wait_on_bit+0x68/0xc0 [ 841.898143] [d6ab1e70] [c0375d04] out_of_line_wait_on_bit+0xc4/0xd8 [ 841.904196] [d6ab1ec0] [c011971c] __wait_on_buffer+0x2c/0x3c [ 841.910228] [d6ab1ed0] [da6763ac] journal_commit_transaction+0x484/0xf20 [jbd] [ 841.916368] [d6ab1f70] [da679cc0] kjournald+0xb4/0x1d4 [jbd] [ 841.922441] [d6ab1fc0] [c00625fc] kthread+0x74/0x78 [ 841.928394] [d6ab1ff0] [c001512c] kernel_thread+0x4c/0x68 [ 841.934247] INFO: task debconf-set-sel:1424 blocked for more than 120 seconds. [ 841.940208] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 841.946252] debconf-set-s D 0fd51810 0 1424 1414 0x [ 841.952351] Call Trace: [ 841.958349] [d66dfcb0] [d7690a3c] 0xd7690a3c (unreliable) [
Bug#583686: Kernel exceptions in ext3/journal subsystem
Ben Hutchings b...@decadent.org.uk writes: On Sat, 2010-05-29 at 17:20 +0200, Christoph Egger wrote: Running sbuild with lvm snapshots seems to hang and the kernel is spitting out error messages. Seems it is having some trouble! Unfortunately I'm no kernel expert so if you need something please ask. [...] This may be related to the infamous sync/umount bug https://bugzilla.kernel.org/show_bug.cgi?id=15906. This bug report always talks about ext4, which isn't used here. So I'm not quite sure it's related. Also running the touch / umount snipet From the bug report runs in acceptable time and doesn't spit out loads of kernel traces as debootstrap / sbuild / et all does Does this happen when sbuild unmounts a temporary filesystem? Last time it died in the middle of an apt-cache call which doesn't (as far as I understand it) do any (u)mounts. Regards Christoph pgp4lTTIdX7ef.pgp Description: PGP signature
Bug#668036: Please enable touchscreen input drivers on loongson2f
Package: linux-2.6 Version: 3.2.14-1 Severity: wishlist Hi! Debugging why my touchscreen won't work when connected to my loongson-2f box but definitely working on amd64 I noticed the drivers are missing from loongson-2f builds. Please consider enabling these modules in distro-kernel builds Regards Christoph -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (1, 'experimental') Architecture: mipsel (mips64) Kernel: Linux 3.2.0-0.bpo.1-loongson-2f Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120408131306.21314.95682.report...@oteiza.siccegge.de
Bug#668036: Please enable touchscreen input drivers on loongson2f
Ben Hutchings b...@decadent.org.uk writes: On Sun, 2012-04-08 at 15:13 +0200, Christoph Egger wrote: Package: linux-2.6 Version: 3.2.14-1 Severity: wishlist Hi! Debugging why my touchscreen won't work when connected to my loongson-2f box but definitely working on amd64 I noticed the drivers are missing from loongson-2f builds. Please consider enabling these modules in distro-kernel builds Is this a USB touchscreen? There are a lot of touchscreen drivers enabled on amd64 but yet not actually usable as they depend on platform data for configuration... but generally USB drivers should be enabled for all architectures. Jep it's a USB device Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/87sjgew15c@hepworth.siccegge.de
Bug#718199: linux-image-3.9-0.bpo.1-kirkwood: mv643xx driver slow
Ben Hutchings b...@decadent.org.uk writes: On Sun, 2013-07-28 at 15:44 +, Christoph Egger wrote: Package: src:linux Version: 3.9.6-1~bpo70+1 Severity: normal Hi! I've upgraded the kernel on my QNAP to 3.9. Unfortunately, network is now stuck around 1 MBit/s and I'm seeing lots of error messages in syslog like the ones below: [ 203.642744] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet spanning multiple descriptors [ 203.642783] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet spanning multiple descriptors Please try Linux 3.10 from unstable (but not if you use md-RAID, as there are nasty bugs not yet fixed there). Right. 3.10.1 and 3.10.7 do not boot (I don't have JTAG or serial or anything so I just don't see the system coming up unfortunately. Can try 3.10.11 later, currently recovering down to 3.2 to get something that at least once worked ;-) Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/87eh8vsffz@anonymous.siccegge.de
Bug#718199: linux-image-3.9-0.bpo.1-kirkwood: mv643xx driver slow
Ben Hutchings b...@decadent.org.uk writes: On Wed, 2013-09-11 at 14:36 +0200, Christoph Egger wrote: Ben Hutchings b...@decadent.org.uk writes: On Sun, 2013-07-28 at 15:44 +, Christoph Egger wrote: Package: src:linux Version: 3.9.6-1~bpo70+1 Severity: normal Hi! I've upgraded the kernel on my QNAP to 3.9. Unfortunately, network is now stuck around 1 MBit/s and I'm seeing lots of error messages in syslog like the ones below: [ 203.642744] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet spanning multiple descriptors [ 203.642783] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet spanning multiple descriptors Please try Linux 3.10 from unstable (but not if you use md-RAID, as there are nasty bugs not yet fixed there). Right. 3.10.1 and 3.10.7 do not boot (I don't have JTAG or serial or anything so I just don't see the system coming up unfortunately. Can try 3.10.11 later, currently recovering down to 3.2 to get something that at least once worked ;-) This is probably bug #719680 which is fixed in 3.10.11-1. Nope, just installed linux-image-3.10-3-kirkwood=3.10.11-1 and it still does not come up. Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/87fvt6ar1e@anonymous.siccegge.de
Bug#707641: overriding root device on TS-419 non-working
Package: flash-kernel Version: 3.3 Severity: serious Hi! Overriding the RootFS device for the initramfs doesn't seem to work. Might well also be a bug in initramfs-tools. Setting serious because it prevents this system from booting, feel free to change. [ 17.714542] IP-Config: eth0 hardware address 00:08:9b:d1:4b:10 mtu 1500 DHCP RARP [ 17.714549] IP-Config: eth0 complete (dhcp from 10.70.255.1): [ 17.714552] address: 10.42.0.6broadcast: 10.255.255.255 netmask: 255.0.0.0 [ 17.714556] gateway: 10.130.130.130 dns0 : 172.16.0.1 dns1 : 0.0.0.0 [ 17.714559] domain : asgard [ 17.714563] rootserver: 10.42.23.2 rootpath: [ 17.714566] filename : F_TS-419P2+ [ 17.728125] Begin: Assembling all MD arrays ... [ 17.776829] md: md0 stopped. [ 17.786608] md: bindsdb1 [ 17.786976] md: bindsdc1 [ 17.787305] md: bindsdd1 [ 17.787987] md: bindsda1 [ 17.981071] raid6: int32x1122 MB/s [ 18.151049] raid6: int32x2192 MB/s [ 18.321192] raid6: int32x4200 MB/s [ 18.491240] raid6: int32x8254 MB/s [ 18.491265] raid6: using algorithm int32x8 (254 MB/s) [ 18.494632] async_tx: api initialized (async) [ 18.495755] xor: measuring software checksum speed [ 18.541021]arm4regs : 1810.400 MB/sec [ 18.591022]8regs : 1086.000 MB/sec [ 18.641019]32regs: 1503.600 MB/sec [ 18.641042] xor: using function: arm4regs (1810.400 MB/sec) [ 18.667005] md: raid6 personality registered for level 6 [ 18.667054] md: raid5 personality registered for level 5 [ 18.667073] md: raid4 personality registered for level 4 [ 18.667836] bio: create slab bio-1 at 1 [ 18.667889] md/raid:md0: not clean -- starting background reconstruction [ 18.667926] md/raid:md0: device sda1 operational as raid disk 0 [ 18.667950] md/raid:md0: device sdd1 operational as raid disk 3 [ 18.667972] md/raid:md0: device sdc1 operational as raid disk 2 [ 18.667992] md/raid:md0: device sdb1 operational as raid disk 1 [ 18.668728] md/raid:md0: allocated 4218kB [ 18.668834] md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2 [ 18.668983] md0: detected capacity change from 0 to 6000789159936 [ 18.669072] mdadm: /dev/md/0 has been started with 4 drives. [ 18.685574] md0: unknown partition table [ 18.869802] Success: assembled all arrays. [ 18.869948] done. [ 18.871347] + [ -e /conf/param.conf ] [ 18.871682] + . /conf/param.conf [ 18.871914] + ROOT=/dev/mapper/root-root [ 18.872071] + debug=y [ 18.872208] + rootdelay=2 [ 18.872366] + /scripts/local-top/lvm2 [ 18.882717] device-mapper: uevent: version 1.0.3 [ 18.883977] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-de...@redhat.com [ 18.922123] Volume group root not found [ 18.922443] Skipping volume group root [ 18.923555] Unable to find LVM volume root/root [ 18.924038] + [ -e /conf/param.conf ] [ 18.924365] + . /conf/param.conf [ 18.924596] + ROOT=/dev/mapper/root-root [ 18.924752] + debug=y [ 18.924889] + rootdelay=2 [ 18.925046] + /scripts/local-top/cryptroot [ 18.959385] Unlocking the disk /dev/disk/by-uuid/b55ee1d9-d00e-42c4-946c-a4d85e169d3b (md0_crypt) [ 18.959467] Enter passphrase: [ 26.957381] Reading all physical volumes. This may take a while... [ 26.971742] Found volume group root using metadata type lvm2 [ 27.038792] 1 logical volume(s) in volume group root now active [ 28.453053] /scripts/local-top/cryptroot: line 1: can't open /dev/ram: no such file [ 28.453760] cryptsetup: md0_crypt set up successfully [ 28.458560] + [ -e /conf/param.conf ] [ 28.458905] + . /conf/param.conf [ 28.459138] + ROOT=/dev/mapper/root-root [ 28.459293] + debug=y [ 28.459430] + rootdelay=2 [ 28.459566] + ROOT=/dev/ram [ 28.459749] + [ n != y ] [ 28.460065] + log_end_msg [ 28.460194] + _log_msg done.\n [ 28.460374] + [ n = y ] [ 28.460684] + printf done.\n [ 28.460832] done. [ 28.460892] + wait_for_udev 10 [ 28.461121] + command -v udevadm [ 28.461408] + udevadm settle --timeout=10 [ 28.465738] + [ -n ] [ 28.466096] + [ /ram = /dev/ram ] [ 28.466429] + [ ! -e /dev/ram ] [ 28.466765] + log_begin_msg Waiting for root file system [ 28.466958] + _log_msg Begin: Waiting for root file system ... [ 28.467149] + [ n = y ] [ 28.467469] + printf Begin: Waiting for root file system ... [ 28.467623] Begin: Waiting for root file system ... + slumber=2 [ 28.467868] + slumber=20 [ 28.468017] + [ ! -e /dev/ram ] [ 28.468337] + /bin/sleep 0.1 [ 28.570103] + slumber=19 [ 28.570297] + [ 19 -gt 0 ] [ 28.570654] + [ ! -e /dev/ram ] [ 28.570988] + /bin/sleep 0.1 [ 28.672723] + slumber=18 [ 28.672912] + [ 18 -gt 0 ] [ 28.673252] + [ ! -e /dev/ram ] [ 28.673579] + /bin/sleep 0.1 [ 28.775280] + slumber=17 [ 28.775468] + [ 17 -gt 0 ] [ 28.775805] + [ ! -e /dev/ram ] [ 28.776141]
Bug#707641: overriding root device on TS-419 non-working
Martin Michlmayr t...@cyrius.com writes: reassign 707641 initramfs-tools thanks I don't see anything flash-kernel related here. Is this right after an installation with d-i? Actually it's cryptsetup's fault. I'ts not pristine from the installer. Got dropbear / cryptroot to run untill there and enabled netconsole via [0] basically. Never really bootet into the installed system though (doesn't boot) Christoph [0] http://www.hellion.org.uk/blog/posts/debugging-initramfs-over-netconsole/ -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/87obcj98kn@hepworth.siccegge.de
Bug#718196: linux-image-3.9-0.bpo.1-kirkwood: mv_cesa broken
Package: src:linux Version: 3.9.6-1~bpo70+1 Severity: normal Hi! The mv_cesa module seems to be broken (both in 3.2 stable kernel and 3.9). Symptoms: If I have mv_cesa loaded, do a cryptsetup open and then a pvscan it doesn't find any suitable volumes. If I unload mv_cesa before cryptsetup open, everything works fine. This *seems* to be a somewhat known problem but should be, as far as I understand, solved before 3.9 (which is the reason I tried 3.9). It is, however, still showing there as well. I'm trying the 3.10 kernel now Christoph -- Package-specific info: ** Version: Linux version 3.9-0.bpo.1-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 Debian 3.9.6-1~bpo70+1 ** Command line: root=/dev/ram initrd=0xa0,0x90 ramdisk=34816 ** Not tainted ** Kernel log: [ 72.698194] [ 72.698265] [ 72.698336] [ 72.698408] [ 72.698479] [ 72.698553] [ 72.698657] [ 72.700871] [ 72.703237] [ 72.703449] [ 74.094157] udevd[447]: starting version 175 [ 74.651014] input: gpio-keys as /devices/platform/gpio-keys/input/input0 [ 74.835844] usbcore: registered new interface driver usbfs [ 74.835949] usbcore: registered new interface driver hub [ 74.842620] usbcore: registered new device driver usb [ 74.909213] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 74.950312] xhci_hcd :01:01.0: xHCI Host Controller [ 74.950385] xhci_hcd :01:01.0: new USB bus registered, assigned bus number 1 [ 74.950808] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 74.950846] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 74.950874] usb usb1: Product: xHCI Host Controller [ 74.950897] usb usb1: Manufacturer: Linux 3.9-0.bpo.1-kirkwood xhci_hcd [ 74.950920] usb usb1: SerialNumber: :01:01.0 [ 74.951409] xHCI xhci_add_endpoint called for root hub [ 74.951417] xHCI xhci_check_bandwidth called for root hub [ 74.951662] hub 1-0:1.0: USB hub found [ 74.951718] hub 1-0:1.0: 2 ports detected [ 74.952003] xhci_hcd :01:01.0: xHCI Host Controller [ 74.952047] xhci_hcd :01:01.0: new USB bus registered, assigned bus number 2 [ 74.952136] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 74.952167] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 74.952194] usb usb2: Product: xHCI Host Controller [ 74.952217] usb usb2: Manufacturer: Linux 3.9-0.bpo.1-kirkwood xhci_hcd [ 74.952240] usb usb2: SerialNumber: :01:01.0 [ 74.954890] xHCI xhci_add_endpoint called for root hub [ 74.954900] xHCI xhci_check_bandwidth called for root hub [ 74.957249] hub 2-0:1.0: USB hub found [ 74.957323] hub 2-0:1.0: 2 ports detected [ 74.991892] ehci-orion: EHCI orion driver [ 75.073148] orion_wdt: Initial timeout 21 sec [ 75.073743] orion-ehci orion-ehci.0: EHCI Host Controller [ 75.073805] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 3 [ 75.073967] orion-ehci orion-ehci.0: irq 19, io mem 0xf105 [ 75.091216] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 75.091327] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 75.091359] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 75.091387] usb usb3: Product: EHCI Host Controller [ 75.091409] usb usb3: Manufacturer: Linux 3.9-0.bpo.1-kirkwood ehci_hcd [ 75.091433] usb usb3: SerialNumber: orion-ehci.0 [ 75.091858] hub 3-0:1.0: USB hub found [ 75.091906] hub 3-0:1.0: 1 port detected [ 75.411222] usb 3-1: new high-speed USB device number 2 using orion-ehci [ 75.562981] usb 3-1: New USB device found, idVendor=05e3, idProduct=0608 [ 75.563045] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 75.563072] usb 3-1: Product: USB2.0 Hub [ 75.564265] hub 3-1:1.0: USB hub found [ 75.564606] hub 3-1:1.0: 4 ports detected [ 76.539311] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 76.856608] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [ 77.571414] loop: module loaded [ 79.684918] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 79.742391] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 79.801780] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 79.858010] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null) [ 81.417984] RPC: Registered named UNIX socket transport module. [ 81.418044] RPC: Registered udp transport module. [ 81.418067] RPC: Registered tcp transport module. [ 81.418088] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 81.447038] FS-Cache: Loaded [ 81.454311] Key type dns_resolver registered [ 81.507694] FS-Cache: Netfs 'nfs' registered for caching [ 81.585295] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 86.593205] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down [ 88.110251] NFSD: Using
Bug#718196: linux-image-3.9-0.bpo.1-kirkwood: mv_cesa broken
Hi! Christoph Egger christ...@debian.org writes: The mv_cesa module seems to be broken (both in 3.2 stable kernel and 3.9). Symptoms: If I have mv_cesa loaded, do a cryptsetup open and then a pvscan it doesn't find any suitable volumes. If I unload mv_cesa before cryptsetup open, everything works fine. This *seems* to be a somewhat known problem but should be, as far as I understand, solved before 3.9 (which is the reason I tried 3.9). It is, however, still showing there as well. I'm trying the 3.10 kernel now FWIW: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-September/122873.html Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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/87siyyk6ve@anonymous.siccegge.de
Bug#718199: linux-image-3.9-0.bpo.1-kirkwood: mv643xx driver slow
Package: src:linux Version: 3.9.6-1~bpo70+1 Severity: normal Hi! I've upgraded the kernel on my QNAP to 3.9. Unfortunately, network is now stuck around 1 MBit/s and I'm seeing lots of error messages in syslog like the ones below: [ 203.642744] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet spanning multiple descriptors [ 203.642783] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet spanning multiple descriptors Regards Christoph -- Package-specific info: ** Version: Linux version 3.9-0.bpo.1-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 Debian 3.9.6-1~bpo70+1 ** Command line: root=/dev/ram initrd=0xa0,0x90 ramdisk=34816 ** Not tainted ** Kernel log: [ 72.697308] [ 72.697383] [ 72.697456] [ 72.697530] [ 72.697602] [ 72.697674] [ 72.697745] [ 72.697829] [ 72.697904] [ 72.697977] [ 72.698050] [ 72.698121] [ 72.698194] [ 72.698265] [ 72.698336] [ 72.698408] [ 72.698479] [ 72.698553] [ 72.698657] [ 72.700871] [ 72.703237] [ 72.703449] [ 74.094157] udevd[447]: starting version 175 [ 74.651014] input: gpio-keys as /devices/platform/gpio-keys/input/input0 [ 74.835844] usbcore: registered new interface driver usbfs [ 74.835949] usbcore: registered new interface driver hub [ 74.842620] usbcore: registered new device driver usb [ 74.909213] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 74.950312] xhci_hcd :01:01.0: xHCI Host Controller [ 74.950385] xhci_hcd :01:01.0: new USB bus registered, assigned bus number 1 [ 74.950808] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 74.950846] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 74.950874] usb usb1: Product: xHCI Host Controller [ 74.950897] usb usb1: Manufacturer: Linux 3.9-0.bpo.1-kirkwood xhci_hcd [ 74.950920] usb usb1: SerialNumber: :01:01.0 [ 74.951409] xHCI xhci_add_endpoint called for root hub [ 74.951417] xHCI xhci_check_bandwidth called for root hub [ 74.951662] hub 1-0:1.0: USB hub found [ 74.951718] hub 1-0:1.0: 2 ports detected [ 74.952003] xhci_hcd :01:01.0: xHCI Host Controller [ 74.952047] xhci_hcd :01:01.0: new USB bus registered, assigned bus number 2 [ 74.952136] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 74.952167] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 74.952194] usb usb2: Product: xHCI Host Controller [ 74.952217] usb usb2: Manufacturer: Linux 3.9-0.bpo.1-kirkwood xhci_hcd [ 74.952240] usb usb2: SerialNumber: :01:01.0 [ 74.954890] xHCI xhci_add_endpoint called for root hub [ 74.954900] xHCI xhci_check_bandwidth called for root hub [ 74.957249] hub 2-0:1.0: USB hub found [ 74.957323] hub 2-0:1.0: 2 ports detected [ 74.991892] ehci-orion: EHCI orion driver [ 75.073148] orion_wdt: Initial timeout 21 sec [ 75.073743] orion-ehci orion-ehci.0: EHCI Host Controller [ 75.073805] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 3 [ 75.073967] orion-ehci orion-ehci.0: irq 19, io mem 0xf105 [ 75.091216] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 75.091327] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 75.091359] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 75.091387] usb usb3: Product: EHCI Host Controller [ 75.091409] usb usb3: Manufacturer: Linux 3.9-0.bpo.1-kirkwood ehci_hcd [ 75.091433] usb usb3: SerialNumber: orion-ehci.0 [ 75.091858] hub 3-0:1.0: USB hub found [ 75.091906] hub 3-0:1.0: 1 port detected [ 75.411222] usb 3-1: new high-speed USB device number 2 using orion-ehci [ 75.562981] usb 3-1: New USB device found, idVendor=05e3, idProduct=0608 [ 75.563045] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 75.563072] usb 3-1: Product: USB2.0 Hub [ 75.564265] hub 3-1:1.0: USB hub found [ 75.564606] hub 3-1:1.0: 4 ports detected [ 76.539311] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 76.856608] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [ 77.571414] loop: module loaded [ 79.684918] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 79.742391] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 79.801780] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 79.858010] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null) [ 81.417984] RPC: Registered named UNIX socket transport module. [ 81.418044] RPC: Registered udp transport module. [ 81.418067] RPC: Registered tcp transport module. [ 81.418088] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 81.447038] FS-Cache: Loaded [ 81.454311] Key type dns_resolver registered [ 81.507694] FS-Cache: Netfs 'nfs' registered for caching [ 81.585295] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [
Bug#755249: IPv6 link non-functional after suspend
Package: src:linux Version: 3.14.12-1 Severity: important Hi! After suspend/resume the computer is unable to perform any IPv6 connection (no ping to fixed IP, no nc, no anything). tcpdump was unfortunately not helpfull in figuring out where exactly it breaks because, as soon as I start tcpdump, things work again. If I stop tcpdump after resume I can still reach all routed IPv6 addresses but only the local ones I have contacted while tcpdump running. Removing the interface and adding it again helps as well. Christoph -- Package-specific info: ** Version: Linux version 3.14-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=/dev/mapper/ssd-root ro quiet rootdelay=2 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 4017.392368] PM: early resume of devices complete after 0.097 msecs [ 4017.392667] r8169 :06:00.0: System wakeup disabled by ACPI [ 4017.407482] [drm] probing gen 2 caps for device 1022:9603 = 300d02/0 [ 4017.407486] [drm] PCIE gen 2 link speeds already enabled [ 4017.408227] serial 00:06: activated [ 4017.411290] [drm] PCIE GART of 1024M enabled (table at 0x00478000). [ 4017.411375] radeon :01:00.0: WB enabled [ 4017.411377] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x88049af11c00 [ 4017.411378] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x88049af11c04 [ 4017.411379] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x88049af11c08 [ 4017.411380] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x88049af11c0c [ 4017.411381] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x88049af11c10 [ 4017.412156] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90013735a18 [ 4017.556738] ata7.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out [ 4017.572711] ata7.00: configured for UDMA/33 [ 4017.579225] [drm] ring test on 0 succeeded in 1 usecs [ 4017.579228] [drm] ring test on 1 succeeded in 0 usecs [ 4017.579231] [drm] ring test on 2 succeeded in 0 usecs [ 4017.579298] [drm] ring test on 3 succeeded in 2 usecs [ 4017.579306] [drm] ring test on 4 succeeded in 1 usecs [ 4017.581956] r8169 :06:00.0 eth0: link down [ 4017.712104] ata5: SATA link down (SStatus 0 SControl 300) [ 4017.712132] ata2: SATA link down (SStatus 0 SControl 300) [ 4017.712157] ata4: SATA link down (SStatus 0 SControl 300) [ 4017.765000] br0: port 1(eth0) entered disabled state [ 4017.765068] [drm] ring test on 5 succeeded in 2 usecs [ 4017.765072] [drm] UVD initialized successfully. [ 4017.765681] [drm] ib test on ring 0 succeeded in 0 usecs [ 4017.765702] [drm] ib test on ring 1 succeeded in 0 usecs [ 4017.765722] [drm] ib test on ring 2 succeeded in 0 usecs [ 4017.765743] [drm] ib test on ring 3 succeeded in 0 usecs [ 4017.765763] [drm] ib test on ring 4 succeeded in 0 usecs [ 4017.784087] usb 1-4: reset high-speed USB device number 3 using ehci-pci [ 4017.884105] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 4017.886062] ata6.00: failed to get NCQ Send/Recv Log Emask 0x1 [ 4017.886289] ata6.00: failed to get NCQ Send/Recv Log Emask 0x1 [ 4017.886291] ata6.00: configured for UDMA/133 [ 4017.900172] sd 5:0:0:0: [sdc] Starting disk [ 4017.916305] [drm] ib test on ring 5 succeeded [ 4018.069640] firewire_core :02:00.0: rediscovered device fw0 [ 4018.384278] usb 1-4.1: reset low-speed USB device number 4 using ehci-pci [ 4018.924338] usb 1-4.4: reset low-speed USB device number 6 using ehci-pci [ 4019.228049] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 4019.230434] ata3.00: configured for UDMA/133 [ 4019.244158] sd 2:0:0:0: [sdb] Starting disk [ 4019.340070] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 4019.352019] ata1.00: configured for UDMA/133 [ 4019.368157] sd 0:0:0:0: [sda] Starting disk [ 4019.390838] PM: resume of devices complete after 1998.468 msecs [ 4019.391011] PM: Finishing wakeup. [ 4019.391012] Restarting tasks ... done. [ 4019.500092] usb 1-2: new high-speed USB device number 7 using ehci-pci [ 4019.538481] r8169 :06:00.0 eth0: link up [ 4019.539255] br0: port 1(eth0) entered forwarding state [ 4019.539277] br0: port 1(eth0) entered forwarding state [ 4019.707857] xhci_hcd :03:00.0: xHCI Host Controller [ 4019.707868] xhci_hcd :03:00.0: new USB bus registered, assigned bus number 2 [ 4019.812515] xhci_hcd :03:00.0: irq 45 for MSI/MSI-X [ 4019.812540] xhci_hcd :03:00.0: irq 46 for MSI/MSI-X [ 4019.812560] xhci_hcd :03:00.0: irq 47 for MSI/MSI-X [ 4019.812579] xhci_hcd :03:00.0: irq 48 for MSI/MSI-X [ 4019.812596] xhci_hcd :03:00.0: irq 49 for MSI/MSI-X [ 4019.812613] xhci_hcd
Bug#755249: IPv6 link non-functional after suspend
Hi! Ben Hutchings b...@decadent.org.uk writes: On Sat, 2014-07-19 at 08:39 +0200, Christoph Egger wrote: Package: src:linux Version: 3.14.12-1 Severity: important After suspend/resume the computer is unable to perform any IPv6 connection (no ping to fixed IP, no nc, no anything). tcpdump was unfortunately not helpfull in figuring out where exactly it breaks because, as soon as I start tcpdump, things work again. If I stop tcpdump after resume I can still reach all routed IPv6 addresses but only the local ones I have contacted while tcpdump running. Removing the interface and adding it again helps as well. [...] IPv6 addresses are dropped when the interface is taken down. Do you have a script that does that on suspend? I'm using pm-suspend for suspending: | % cat /var/log/pm-suspend.log | | % ls /etc/pm/* | /etc/pm/config.d: | unload_module | | /etc/pm/power.d: | | /etc/pm/sleep.d: | | % cat /etc/pm/config.d/unload_module | SUSPEND_MODULES=xhci_hcd anywhere else to look? I haven't done anything manually. Also what's the current-good way to do suspend without any magic for debugging purposes? The interface seems up after suspend (IPv4 works, even the autoconf address works after I remove the manually set IPv6 address). The problem either appeared with booting into the 3.13 kernel or with adding the br0.65 vlan interface -- I can try and see if removing the vlan interface changes anything as soon as I'm back home. Christoph pgpUUJK12R7Lc.pgp Description: PGP signature
Bug#755249: IPv6 link non-functional after suspend
Control: reopen -1 Christoph Egger christ...@christoph-egger.org writes: Sorry for the delay. I can't reproduce the problem using the current kernel. Taking that back. Seems just suspending for a few seconds does not trigger this behaviour. I had the computer in suspend over the night and now it.s back ethtool after boot == RealTek RTL8168e/8111e registers: 0x00: MAC Address 48:5b:39:c9:ec:73 0x08: Multicast Address Filter 0x 0x 0x10: Dump Tally Counter Command 0xb3a479c0 0xe2ece169 0x20: Tx Normal Priority Ring Addr 0xcb818000 0x 0x28: Tx High Priority Ring Addr 0xf740e900 0xc346a1a9 0x30: Flash memory read/write 0x 0x34: Early Rx Byte Count 0 0x36: Early Rx Status 0x00 0x37: Command 0x0c Rx on, Tx on 0x3C: Interrupt Mask 0x803f SERR LinkChg RxNoBuf TxErr TxOK RxErr RxOK 0x3E: Interrupt Status0x 0x40: Tx Configuration0x2f100700 0x44: Rx Configuration0x0002870f 0x48: Timer count 0xfacc1c23 0x4C: Missed packet counter 0xcc1cd1 0x50: EEPROM Command0x00 0x51: Config 0 0x04 0x52: Config 1 0xcf 0x53: Config 2 0x3d 0x54: Config 3 0x62 0x55: Config 4 0x55 0x56: Config 5 0x02 0x58: Timer interrupt 0x 0x5C: Multiple Interrupt Select 0x 0x60: PHY access 0x80001000 0x64: TBI control and status 0x2701 0x68: TBI Autonegotiation advertisement (ANAR)0xf70c 0x6A: TBI Link partner ability (LPAR) 0x 0x6C: PHY status0x93 0x84: PM wakeup frame 00x 0xfacc26f1 0x8C: PM wakeup frame 10x 0xe5a07be8 0x94: PM wakeup frame 2 (low) 0xf17a89a9 0x33e576f9 0x9C: PM wakeup frame 2 (high) 0xf760d3c8 0x834cf908 0xA4: PM wakeup frame 3 (low) 0xe202c8c9 0xf16fe3f9 0xAC: PM wakeup frame 3 (high) 0xf064f869 0x 0xB4: PM wakeup frame 4 (low) 0x 0x 0xBC: PM wakeup frame 4 (high) 0x 0x 0xC4: Wakeup frame 0 CRC 0x 0xC6: Wakeup frame 1 CRC 0x 0xC8: Wakeup frame 2 CRC 0x 0xCA: Wakeup frame 3 CRC 0x 0xCC: Wakeup frame 4 CRC 0x 0xDA: RX packet maximum size 0x4000 0xE0: C+ Command 0x20a1 RX checksumming 0xE2: Interrupt Mitigation0x5151 TxTimer: 5 TxPackets: 1 RxTimer: 5 RxPackets: 1 0xE4: Rx Ring Addr 0xcb80 0x 0xEC: Early Tx threshold0x3f 0xF0: Func Event 0x00ff 0xF4: Func Event Mask 0x 0xF8: Func Preset State 0x0003 0xFC: Func Force Event0x ethtool after resume RealTek RTL8168e/8111e registers: 0x00: MAC Address 48:5b:39:c9:ec:73 0x08: Multicast Address Filter 0x 0x 0x10: Dump Tally Counter Command 0xb3a479c0 0xe2ece169 0x20: Tx Normal Priority Ring Addr 0xcb818000 0x 0x28: Tx High Priority Ring Addr 0xf740e900 0xc346a1a9 0x30: Flash memory read/write 0x 0x34: Early Rx Byte Count 0 0x36: Early Rx Status 0x00 0x37: Command 0x0c Rx on, Tx on 0x3C: Interrupt Mask 0x803f SERR LinkChg RxNoBuf TxErr TxOK RxErr RxOK 0x3E: Interrupt Status0x 0x40: Tx Configuration0x2f100700 0x44: Rx Configuration0x0002070f 0x48: Timer count 0x5369f3a2 0x4C: Missed packet counter 0x69f44e 0x50: EEPROM Command0x00 0x51: Config 0 0x04 0x52: Config 1 0xcf 0x53: Config 2 0x3d 0x54: Config 3 0x62 0x55: Config 4 0x55 0x56: Config 5
Bug#723042: QNAP still not booting
Control: found -1 3.14.15-2 FWIW it still doesn't boot. I'll buy a jtag adapter post-debconf so I can get anything out of it that might b usefull Christoph -- 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/87mwavvna5@mitoraj.siccegge.de
Bug#809740: initramfs-tools: Completely ignores rootdelay
Package: initramfs-tools Version: 0.120 Severity: important Hi! the initramfs totally ignores the rootdelay / rootwait parameters and just instantly boots up. As a result I always get a degraded array activated as the second disk is not yet available. The second disk just shows up a few blinks later. Christoph -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 5.5M Sep 23 2013 /boot/initrd.img-3.10-2-amd64 -rw-r--r-- 1 root root 5.6M Nov 15 2013 /boot/initrd.img-3.10-3-amd64 -rw-r--r-- 1 root root 6.7M Dec 19 21:02 /boot/initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 6.8M Sep 25 13:58 /boot/initrd.img-4.1.0-2-amd64 -rw-r--r-- 1 root root 6.8M Dec 19 21:06 /boot/initrd.img-4.2.0-1-amd64 -rw-r--r-- 1 root root 6.8M Jan 3 01:50 /boot/initrd.img-4.3.0-1-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/ssd-root ro quiet rootdelay=30 rootwait=30 systemd.log_target=kmsg systemd.debug-shell -- resume RESUME=UUID=160f4b55-b95a-416c-aec0-a20b510e40ee -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by fuse 94208 3 ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 36864 5 ip6table_filter,ip_tables,iptable_filter,ebtables,ip6_tables nfnetlink_queue20480 0 nfnetlink_log 20480 0 nfnetlink 16384 2 nfnetlink_log,nfnetlink_queue bluetooth 512000 0 rfkill 24576 2 bluetooth tun28672 2 sit24576 0 tunnel416384 1 sit ip_tunnel 28672 1 sit nfsd 286720 11 auth_rpcgss61440 1 nfsd oid_registry 16384 1 auth_rpcgss nfs_acl16384 1 nfsd lockd 90112 1 nfsd grace 16384 2 nfsd,lockd sunrpc327680 17 nfsd,auth_rpcgss,lockd,nfs_acl pci_stub 16384 1 vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 450560 3 vboxnetadp,vboxnetflt,vboxpci binfmt_misc20480 1 bridge114688 0 stp16384 1 bridge llc16384 2 stp,bridge joydev 20480 0 snd_usb_audio 176128 0 snd_usbmidi_lib32768 1 snd_usb_audio snd_hwdep 16384 1 snd_usb_audio hid_generic16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid sr_mod 24576 0 cdrom 57344 1 sr_mod evdev 20480 13 amdkfd122880 1 kvm_amd65536 0 ohci_pci 16384 0 kvm 507904 1 kvm_amd radeon 1490944 2 snd_ca0106 45056 0 psmouse 126976 0 snd_rawmidi32768 2 snd_usbmidi_lib,snd_ca0106 snd_seq_device 16384 1 snd_rawmidi ehci_pci 16384 0 snd_ac97_codec126976 1 snd_ca0106 serio_raw 16384 0 xhci_pci 16384 0 ttm94208 1 radeon r8169 81920 0 pcspkr 16384 0 snd_pcm_oss49152 0 xhci_hcd 172032 1 xhci_pci drm_kms_helper131072 1 radeon ohci_hcd 49152 1 ohci_pci mii16384 1 r8169 snd_mixer_oss 24576 1 snd_pcm_oss ehci_hcd 77824 1 ehci_pci drm 348160 5 ttm,drm_kms_helper,radeon snd_pcm 102400 4 snd_pcm_oss,snd_usb_audio,snd_ac97_codec,snd_ca0106 pata_via 16384 0 firewire_ohci 40960 0 i2c_algo_bit 16384 1 radeon snd_timer 32768 1 snd_pcm snd81920 11 snd_pcm_oss,snd_usb_audio,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_usbmidi_lib,snd_seq_device,snd_mixer_oss,snd_ca0106 edac_mce_amd 24576 0 usbcore 233472 9 snd_usb_audio,ohci_hcd,ohci_pci,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd,xhci_pci sp5100_tco 16384 0 soundcore 16384 1 snd ahci 36864 1 ac97_bus 16384 1 snd_ac97_codec k10temp16384 0 edac_core 57344 0 sg 32768 0 i2c_piix4 24576 0 shpchp 36864 0 libahci32768 1 ahci usb_common 16384 1 usbcore wmi20480 0 8250_fintek16384 0 asus_atk0110 20480 0 acpi_cpufreq 20480 1 button 16384 0 processor 36864 1 acpi_cpufreq hwmon_vid 16384 0 loop 28672 0 firewire_sbp2 24576 0
Bug#871049: Acknowledgement (linux: please enable MMC_SDHCI_XENON)
Hi again Also adding CONFIG_MVNETA would be great. It's the right driver for the hardware and missing on arm64. Christoph
Bug#871049: MMC_SDHCI_XENON: arm64!
Hi! Seems it's missing so far: This is about arm64 kernel Thanks! Christoph
Bug#871049: linux: please enable MMC_SDHCI_XENON
Source: linux Version: 4.12.2-1~exp1 Severity: normal Hi there! Please consider enabling MMC_SDHCI_XENON on the 4.12 and later kernels. With this modification I can successfully boot plain debian kernels from Espressobin using the SD card. it needs two patches for devicetree which should be on the way for 4.14 latest: http://git.infradead.org/linux-mvebu.git/commit/9be778f6c6d8f90ff2fad88d1770e2a7843aee43 http://git.infradead.org/linux-mvebu.git/commit/1208d2f0c84120d4e3eb2caf663a9a8b784b38ba Though I'm not sure you're going to include those two already. Christoph -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#723042: QNAP still not booting
On Sunday 4 March 2018 18:28:39 CET Martin Michlmayr wrote: > * Christoph Egger <christ...@debian.org> [2014-08-22 21:32]: > > FWIW it still doesn't boot. I'll buy a jtag adapter post-debconf so I > > can get anything out of it that might b usefull > > This bug report is quite old. > > There are users running Debian jessie (3.16) and stretch (4.9) > successfully on QNAP TS-41x hardware. > > Do you still have problems? I have since then retired the QNAP Christoph
Bug#919807: src:linux: Please consider CONFIG_TLS=m
Package: src:linux Severity: wishlist Dear Maintainer, it would be great to have CONFIG_TLS enabled (as module like in fedora I guess) to help experiment with this functionality. Thanks! Christoph -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (150, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.20.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature
Bug#951610: linux-image-5.4.0-4-amd64: Does not prompt for cryptsetup password
Package: src:linux Version: 5.4.19-1 Severity: important Hi! Starting with -4 the system fails to boot from encrypted harddrive. switchng back to -3 kernel and everything works fine again. Setup is unencrypted /boot (ext) and / (and other things) via lvm2 inside a cryptsetup volume type:LUKS1 cipher: aes-xts-plain64 keysize: 512 bits key location: dm-crypt device: /dev/nvme0n1p2 sector size: 512 offset: 4096 sectors size:992397312 sectors mode:read/write I can try and see if I get linux to output any usefull messages if that helps. Thanks! Christoph -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20HGS0A600 product_version: ThinkPad T470s chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N1WET56W (1.35 ) board_vendor: LENOVO board_name: 20HGS0A600 board_version: Not Defined ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:224b] 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 HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] 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 Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:224b] 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 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) Subsystem: Lenovo Sunrise Point-LP Thermal subsystem [17aa:224b] 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: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21) Subsystem: Lenovo Sunrise Point-LP Serial IO I2C Controller [17aa:224b] 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: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:224b] 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:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d10] (rev f1) (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.2 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d12] (rev f1) (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 Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) (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
