Re: bullseye-installer fails on Cubox-i due to networking issue
Hi Arnd,
many thanks for the quick response.
There is good news: Networking works both on the LibreELEC (which uses 5.10.1)
and the daily builds of the Debian bullseye installer (which uses 5.9.15). The
problem is in the latest release of the Debian bullseye installer Alpha3
which I think uses 5.9.11
I extracted imx6q-cubox-i.dtb from the bullseye alpha3 installer which has the
modification:
rd@h370:~/tmp.nobackup$ fdtdump imx6q-cubox-i.dtb | grep phy-mode
fdtdump is a low-level debugging tool, not meant for general use.
If you want to decompile a dtb, you probably want
dtc -I dtb -O dts
phy-mode = "rgmii-id";
rd@h370:~/tmp.nobackup$
The xbian image I tested uses 5.9.12 which has the networking issue as well.
Given that it seems to work with the latest versions of the 5.9 and 5.10
series and the daily build of the bullseye installer, I think the topic can be
considered as resolved.
Thanks again
Rainer
Am Donnerstag, 24. Dezember 2020, 17:42:31 CET schrieb Arnd Bergmann:
> On Thu, Dec 24, 2020 at 3:38 PM Rainer Dorsch wrote:
> > Hi,
> >
> > I tried to run the bullseye installer from
> >
> > http://ftp2.de.debian.org/debian/dists/bullseye/main/installer-armhf/curre
> > nt/ images/netboot/SD-card-images/
> >
> > on a cubox-i using a serial console today.
> >
> > It seems the network interface does not come up properly:
> >
> > ~ # dmesg |grep eth
> > [5.009246] fec 2188000.ethernet: Invalid MAC address:
> > 00:00:00:00:00:00
> > [5.015982] fec 2188000.ethernet: Using random MAC address: 4a:
> > 0d:a7:66:c1:e6
> > [5.028381] mdio_bus 2188000.ethernet-1: MDIO device at address 0 is
> > missing.
> > [ 138.479638] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 139.674014] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 141.218830] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 147.400881] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 199.375688] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 736.031852] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 906.069383] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 1156.891662] fec 2188000.ethernet eth0: Unable to connect to phy
> > [ 1266.982998] fec 2188000.ethernet eth0: Unable to connect to phy
>
> Which was the last kernel version on which it worked correctly?
> There were a couple of regressions based on incorrect phy-mode
> settings after a phy driver changed its behavior in an incompatible
> way.
>
> This should be the relevant hunk in your board, it was merged into
> linux-5.2:
>
> 0672d22a1924 ("ARM: dts: imx: Fix the AR803X phy-mode")
>
> diff --git a/arch/arm/boot/dts/imx6qdl-sr-som.dtsi
> b/arch/arm/boot/dts/imx6qdl-sr-som.dtsi
> index 4ccb7afc4b35..6d7f6b9035bc 100644
> --- a/arch/arm/boot/dts/imx6qdl-sr-som.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sr-som.dtsi
> @@ -53,7 +53,7 @@ vcc_3v3: regulator-vcc-3v3 {
> &fec {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_microsom_enet_ar8035>;
> - phy-mode = "rgmii";
> + phy-mode = "rgmii-id";
> phy-reset-duration = <2>;
> phy-reset-gpios = <&gpio4 15 GPIO_ACTIVE_LOW>;
> status = "okay";
>
> If you have a dtb file from before that change and want to run it
> on a newer kernel, at least this change is needed.
> > ~ #
> >
> > Not sure if this backtrace is related or even expected:
> >
> > [5.626874] Freeing unused kernel memory: 2048K
> > [5.632309] [ cut here ]
> > [5.636982] WARNING: CPU: 0 PID: 1 at arch/arm/mm/dump.c:248
> > note_page+0x3d0/0x3dc
> > [5.644576] arm/mm: Found insecure W+X mapping at address 0xf0879000
> > [5.650947] Modules linked in:
> > [5.654033] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.9.0-4-armmp #1
> > Debian 5.9.11-1
> > [5.661953] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
>
> I see the current kernel version here, which is helpful in figuring out the
> problem, but I don't think the warning is relevant here.
>
> I do see two code changes that may be relevant
>
> 0da1ccbbefb6 ("net: fec: Fix PHY init after phy_reset_after_clk_enable()")
> 1e6114f51f9d ("net: fec: fix MDIO probing for some FEC hardware blocks")
>
> both of them are backported into linux-5.9.y and are part of 5.9.7 or newer,
> so you probably have them already, but there is a chance that one of these
> patches caused a regression, so maybe try a v5.9.0 for comparison.
--
Rainer Dorsch
http://bokomoko.de/
bullseye-installer fails on Cubox-i due to networking issue
Hi, I tried to run the bullseye installer from http://ftp2.de.debian.org/debian/dists/bullseye/main/installer-armhf/current/ images/netboot/SD-card-images/ on a cubox-i using a serial console today. It seems the network interface does not come up properly: ~ # dmesg |grep eth [5.009246] fec 2188000.ethernet: Invalid MAC address: 00:00:00:00:00:00 [5.015982] fec 2188000.ethernet: Using random MAC address: 4a: 0d:a7:66:c1:e6 [5.028381] mdio_bus 2188000.ethernet-1: MDIO device at address 0 is missing. [ 138.479638] fec 2188000.ethernet eth0: Unable to connect to phy [ 139.674014] fec 2188000.ethernet eth0: Unable to connect to phy [ 141.218830] fec 2188000.ethernet eth0: Unable to connect to phy [ 147.400881] fec 2188000.ethernet eth0: Unable to connect to phy [ 199.375688] fec 2188000.ethernet eth0: Unable to connect to phy [ 736.031852] fec 2188000.ethernet eth0: Unable to connect to phy [ 906.069383] fec 2188000.ethernet eth0: Unable to connect to phy [ 1156.891662] fec 2188000.ethernet eth0: Unable to connect to phy [ 1266.982998] fec 2188000.ethernet eth0: Unable to connect to phy ~ # Not sure if this backtrace is related or even expected: [5.626874] Freeing unused kernel memory: 2048K [5.632309] [ cut here ] [5.636982] WARNING: CPU: 0 PID: 1 at arch/arm/mm/dump.c:248 note_page+0x3d0/0x3dc [5.644576] arm/mm: Found insecure W+X mapping at address 0xf0879000 [5.650947] Modules linked in: [5.654033] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.9.0-4-armmp #1 Debian 5.9.11-1 [5.661953] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [5.668483] Backtrace: [5.670946] [] (dump_backtrace) from [] (show_stack+0x20/0x24) [5.678522] r7:00f8 r6:6013 r5: r4:c136910c [5.684192] [] (show_stack) from [] (dump_stack+0xc8/0xdc) [5.691430] [] (dump_stack) from [] (__warn+0xe0/0x148) [5.698396] r7:00f8 r6:0009 r5:c031eb6c r4:c0eb24e0 [5.704062] [] (__warn) from [] (warn_slowpath_fmt+0xa4/0xe4) [5.711548] r7:c031eb6c r6:00f8 r5:c0eb24e0 r4:c0eb24ac [5.717214] [] (warn_slowpath_fmt) from [] (note_page+0x3d0/0x3dc) [5.725135] r8: r7: r6:0005 r5:c130c440 r4:ee951f28 [5.731841] [] (note_page) from [] (walk_pmd+0xe8/0x1a4) [5.738895] r10:ee951f28 r9:c0207c20 r8:ee8c6800 r7: r6:c0eb2528 r5:f087b000 [5.746724] r4:ee8c61ec [5.749263] [] (walk_pmd) from [] (ptdump_check_wx+0x88/0x104) [5.756838] r10: r9: r8: r7: r6:c0208000 r5:f080 [5.764667] r4:c0207c28 [5.767215] [] (ptdump_check_wx) from [] (mark_rodata_ro+0x3c/0x40) [5.775223] r6: r5:c0c9ab94 r4: [5.779853] [] (mark_rodata_ro) from [] (kernel_init+0x44/0x130) [5.787605] [] (kernel_init) from [] (ret_from_fork+0x14/0x2c) [5.795176] Exception stack(0xee951fb0 to 0xee951ff8) [5.800232] 1fa0: [5.808414] 1fc0: [5.816595] 1fe0: 0013 [5.823210] r5:c0c9ab94 r4: [5.826848] ---[ end trace eee50453771fe1ab ]--- [5.831714] Checked W+X mappings: FAILED, 1 W+X pages found [5.837378] Run /init as init process I run in a current xbian image a few days back on the same machine in the same issue. This was buster based, but had a recent kernel. This indicates that the issue is related with the kernel. The same network cable works on a buster x86 system and even with the cubox-i with a SD card with and older xbian version without any issues. Any hint or idea what could be wrong is apprectiated. If anybody has a way to get debug data (e.g. dmseg output) easier from the cubox than copy and paste from minicom, that would also help. Many thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#960181: pigz: abort: write error on (No space left on device)
Thanks Raymond for your quick and accurate answer. Fortunately, I am in a much better position than what you describe in your blog entry, I had kernel n-1 and n installed, when trying to install n+1. I removed my oldest kernel version (n-1) which resolved the issue. I shold have created a larger /boot partition in the first place. Interesting enough there was a initrd.img-4.19.0-9-amd64 created already before and also booting the -9 kernel worked well. After removing the n-1 kernel, the initrd for n+1 grew by around 300 bytes. Since df reported that more than 22 MB are free, I do not undertand why update-initramfs complained that it has not enough space. rd@h370:~/tmp.nobackup/covidify-test/reports/images$ ls -l /boot/ insgesamt 192878 -rw-r--r-- 1 root root 206361 Nov 11 01:30 config-4.19.0-6-amd64 -rw-r--r-- 1 root root 206194 Apr 27 07:05 config-4.19.0-8-amd64 -rw-r--r-- 1 root root 206157 Apr 29 11:38 config-4.19.0-9-amd64 drwx-- 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 1024 Mai 10 12:40 grub -rw-r--r-- 1 root root 56649181 Feb 8 23:32 initrd.img-4.19.0-6-amd64 -rw-r--r-- 1 root root 56680246 Apr 28 23:10 initrd.img-4.19.0-8-amd64 -rw-r--r-- 1 root root 56696108 Mai 10 12:40 initrd.img-4.19.0-9-amd64 drwx-- 2 root root12288 Mai 13 2018 lost+found -rw-r--r-- 1 root root 3410671 Nov 11 01:30 System.map-4.19.0-6-amd64 -rw-r--r-- 1 root root 3408461 Apr 27 07:05 System.map-4.19.0-8-amd64 -rw-r--r-- 1 root root 3411358 Apr 29 11:38 System.map-4.19.0-9-amd64 -rw-r--r-- 1 root root 5270768 Nov 11 01:30 vmlinuz-4.19.0-6-amd64 -rw-r--r-- 1 root root 5274864 Apr 27 07:05 vmlinuz-4.19.0-8-amd64 -rw-r--r-- 1 root root 5278960 Apr 29 11:38 vmlinuz-4.19.0-9-amd64 rd@h370:~/tmp.nobackup/covidify-test/reports/images$ su - Passwort: root@h370:~# apt-get purge linux-image-4.19.0-6-amd64 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete werden ENTFERNT: linux-image-4.19.0-6-amd64* 0 aktualisiert, 0 neu installiert, 1 zu entfernen und 4 nicht aktualisiert. 1 nicht vollständig installiert oder entfernt. Nach dieser Operation werden 269 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] (Lese Datenbank ... 613766 Dateien und Verzeichnisse sind derzeit installiert.) Entfernen von linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u2) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-4.19.0-6-amd64 /etc/kernel/postrm.d/zz-update-grub: GRUB-Konfigurationsdatei wird erstellt … Found background image: .background_cache.png Linux-Abbild gefunden: /boot/vmlinuz-4.19.0-9-amd64 initrd-Abbild gefunden: /boot/initrd.img-4.19.0-9-amd64 Linux-Abbild gefunden: /boot/vmlinuz-4.19.0-8-amd64 initrd-Abbild gefunden: /boot/initrd.img-4.19.0-8-amd64 Adding boot menu entry for EFI firmware configuration erledigt initramfs-tools (0.133+deb10u1) wird eingerichtet ... update-initramfs: deferring update (trigger activated) (Lese Datenbank ... 609364 Dateien und Verzeichnisse sind derzeit installiert.) Löschen der Konfigurationsdateien von linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u2) ... rmdir: konnte '/lib/modules/4.19.0-6-amd64' nicht entfernen: Das Verzeichnis ist nicht leer Trigger für initramfs-tools (0.133+deb10u1) werden verarbeitet ... update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64 root@h370:~# apt-get upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig Die folgenden Pakete sind zurückgehalten worden: gnucash-docs libvpx6 virtualbox virtualbox-qt 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 4 nicht aktualisiert. root@h370:~# ls -l /boot/ insgesamt 128620 -rw-r--r-- 1 root root 206194 Apr 27 07:05 config-4.19.0-8-amd64 -rw-r--r-- 1 root root 206157 Apr 29 11:38 config-4.19.0-9-amd64 drwx-- 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 1024 Mai 10 15:32 grub -rw-r--r-- 1 root root 56680246 Apr 28 23:10 initrd.img-4.19.0-8-amd64 -rw-r--r-- 1 root root 56696461 Mai 10 15:33 initrd.img-4.19.0-9-amd64 drwx-- 2 root root12288 Mai 13 2018 lost+found -rw-r--r-- 1 root root 3408461 Apr 27 07:05 System.map-4.19.0-8-amd64 -rw-r--r-- 1 root root 3411358 Apr 29 11:38 System.map-4.19.0-9-amd64 -rw-r--r-- 1 root root 5274864 Apr 27 07:05 vmlinuz-4.19.0-8-amd64 -rw-r--r-- 1 root root 5278960 Apr 29 11:38 vmlinuz-4.19.0-9-amd64 root@h370:~# Thanks again Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#960181: pigz: abort: write error on (No space left on device)
Package: src:linux Version: 4.19.118-2 Severity: normal Dear Maintainer, it is likely that this is not a direct kernel issue, but it worked with the -8 version without any problems. If you can advice where to look for the issue, that would be already helpful. It is weird that mkinitramfs reports no space left on device, but df does not confirm this. So it might be "another" device (like initramfs?). I am aware that I include a virtualbox module with dkms root@h370:~# apt-cache policy virtualbox virtualbox: Installed: 6.0.12-dfsg-1 Candidate: 6.1.6-dfsg-2 Version table: 6.1.6-dfsg-2 100 100 http://ftp.de.debian.org/debian sid/contrib amd64 Packages *** 6.0.12-dfsg-1 100 100 https://snapshot.debian.org/archive/debian/20190928T162431Z sid/contrib amd64 Packages 100 /var/lib/dpkg/status root@h370:~# (I use a snapshot since it got removed from stretch at some point in time). Here is the error report: root@h370:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: linux-image-4.19.0-6-amd64 Use 'apt autoremove' to remove it. The following packages have been kept back: gnucash-docs libvpx6 virtualbox virtualbox-qt 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up initramfs-tools (0.133+deb10u1) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.133+deb10u1) ... update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64 pigz: abort: write error on (No space left on device) E: mkinitramfs failure cpio 141 pigz 28 update-initramfs: failed for /boot/initrd.img-4.19.0-9-amd64 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) root@h370:~# df Filesystem1K-blocks Used Available Use% Mounted on udev 16364780 0 16364780 0% /dev tmpfs 3278936 9768 3269168 1% /run /dev/mapper/b370--vg-root 486574264 416572764 45215172 91% / tmpfs 16394664 78848 16315816 1% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 16394664 0 16394664 0% /sys/fs/cgroup /dev/sda2241965206789 22684 91% /boot /dev/sda1523248 140523108 1% /boot/efi tmpfs 327893228 3278904 1% /run/user/2809 root@h370:~# Any advice is welcome. Thanks Rainer -- Package-specific info: ** Version: Linux version 4.19.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.118-2 (2020-04-29) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-9-amd64 root=/dev/mapper/b370--vg-root ro quiet ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 15.336697] asus_wmi: Initialization: 0x0 [ 15.336712] asus_wmi: BIOS WMI version: 0.9 [ 15.336764] asus_wmi: SFUN value: 0x0 [ 15.336970] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input10 [ 15.337093] asus_wmi: Number of fans: 1 [ 15.351999] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 15.352617] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 15.383010] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [ 15.383012] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x1a/0x0/0x0/0x0/0x0) [ 15.383012] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [ 15.383013] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 15.383013] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x11/0x0 [ 15.383014] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 15.383014] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [ 15.383015] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [ 15.383015] snd_hda_codec_realtek hdaudioC0D0: Line=0x15 [ 15.421179] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 15.421208] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 15.421236] input: HDA Intel PCH Line as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 15.421265] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 15.421289] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1f
No (USB) mouse and keyboard after resume
200704 1 aes_x86_64 20480 1 aesni_intel libahci40960 1 ahci crypto_simd16384 1 aesni_intel cryptd 28672 3 crypto_simd,ghash_clmulni_intel,aesni_intel xhci_pci 16384 0 glue_helper16384 1 aesni_intel xhci_hcd 270336 1 xhci_pci ohci_hcd 61440 1 ohci_pci ehci_pci 16384 0 i2c_piix4 24576 0 ehci_hcd 94208 1 ehci_pci libata278528 2 libahci,ahci usbcore 290816 7 xhci_hcd,ohci_hcd,ehci_pci,usbhid,ehci_hcd,xhci_pci,ohci_pci scsi_mod 253952 3 sd_mod,libata,sg r8169 90112 0 usb_common 16384 1 usbcore mii16384 1 r8169 rd@blackbox:~$ The problem occurs with both the 4.18.0-0.bpo.1-amd64 and 4.9.0-8-amd64 kernels The mainboard is a Gigabyte GA-AM1M-S2H. Any hint or advise is welcome. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Regression in 4.17 Kernels (?)
Am Freitag, 24. August 2018, 11:12:31 schrieb Yves-Alexis Perez: > On Thu, 2018-08-23 at 14:20 +0200, Rainer Dorsch wrote: > > Feel free to ask, I am sorry that I did not provide more information, but > > since there is nothing in the log files, nothing on the screen, it is hard > > for me to provide anything useful. I could switch to a VT which the > > scanner is running shortly before the crash, but not sure if that helps. > > If you manage to reproduce the crash that way, I guess it would help yes. It > might help to increase the dmesg log verbosity too. > > If vt switch is not enough, you might want to try using ssh or netconsole. > Thanks for the pointer to netconsole and sshI will give it a try, as soon as I have physical access to the system again. Will take a few days... Rainer
Re: Regression in 4.17 Kernels (?)
Hi Yves-Alexis, Am Donnerstag, 23. August 2018, 13:53:32 CEST schrieb Yves-Alexis Perez: > On Thu, 2018-08-23 at 13:17 +0200, Rainer Dorsch wrote: > > Yes, I have never seen that with 4.16 and any kernel I used before. I run > > not 4.16. > > Sorry I'm a bit unsure how to read the last sentence. Can you retry right > now with 4.16 kernel (and changing only that) and report back? It's > possible that there is a regression in the USB handling in the 4.17 kernel > but we'd need a bit more information to confirm that. Sorry, this was a typo, I meant I run *now* 4.16 [again]. ...and I did not observe the issue. Feel free to ask, I am sorry that I did not provide more information, but since there is nothing in the log files, nothing on the screen, it is hard for me to provide anything useful. I could switch to a VT which the scanner is running shortly before the crash, but not sure if that helps. Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Regression in 4.17 Kernels (?)
Am Donnerstag, 23. August 2018, 11:57:17 CEST schrieb Yves-Alexis Perez: > On Wed, 2018-08-22 at 18:57 +0200, Rainer Dorsch wrote: > > The issue seems to be 100% reproducible with the 4.17 kernels I tried on > > my > > > system: > Hi, > > is it OK with other kernels? Yes, I have never seen that with 4.16 and any kernel I used before. I run not 4.16. Rainer -- Rainer Dorsch http://bokomoko.de/
Regression in 4.17 Kernels (?)
Hi, I have a strange issue with 4.17 kernels: When I run my scanner (Fujitsu fi-4220C2) using gscan2pdf/sane, the system reboots spontaneously after the first page, there is no log entry, no Oops, nothing, here are lines from kern.log (timestamps are too far apart for a spontaneous reboot): Aug 22 18:26:33 b370 kernel: [ 3118.972889] perf: interrupt took too long (3993 > 3976), lowering kernel.perf_event_max_sample_rate to 5 Aug 22 18:42:27 b370 kernel: [0.00] Linux version 4.17.0-3-amd64 (debian- ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-28)) #1 SMP Debian 4.17.17-1 (2018-08-18) The issue seems to be 100% reproducible with the 4.17 kernels I tried on my system: root@b370:~# dpkg --get-selections |grep linux-image-4.17 Any idea what happens here is welcome. Should I open a bug report? If yes, which data should I include? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#853122: linux-image-4.13.0-0.bpo.1-amd64: Also present at Gigabyte GA-AM1M-S2H
Package: src:linux Version: 4.13.13-1~bpo9+1 Followup-For: Bug #853122 Dear Maintainer, for reference: this issue is still present in 4.13.13 (which is expected, since upstream did not yet handle Zoltan's patches) and applies to my Gigabyte GA-AM1M-S2H mainboard. Regards Rainer -- Package-specific info: ** Version: Linux version 4.13.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #1 SMP Debian 4.13.13-1~bpo9+1 (2017-11-22) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-0.bpo.1-amd64 root=UUID=bd19343e-2b8e-4052-989c-2627246c915f ro quiet ** Not tainted ** Kernel log: [4.022597] [drm] RAM width 128bits DDR [4.032093] [TTM] Zone kernel: Available graphics memory: 1736752 kiB [4.032096] [TTM] Initializing pool allocator [4.032103] [TTM] Initializing DMA pool allocator [4.032147] [drm] radeon: 512M of VRAM memory ready [4.032149] [drm] radeon: 2048M of GTT memory ready. [4.032170] [drm] Loading kabini Microcode [4.032988] radeon :00:01.0: firmware: direct-loading firmware radeon/kabini_pfp.bin [4.033347] radeon :00:01.0: firmware: direct-loading firmware radeon/kabini_me.bin [4.033550] radeon :00:01.0: firmware: direct-loading firmware radeon/kabini_ce.bin [4.033828] radeon :00:01.0: firmware: direct-loading firmware radeon/kabini_mec.bin [4.034051] radeon :00:01.0: firmware: direct-loading firmware radeon/kabini_rlc.bin [4.034370] radeon :00:01.0: firmware: direct-loading firmware radeon/kabini_sdma.bin [4.034379] [drm] Internal thermal controller without fan control [4.035646] [drm] radeon: dpm initialized [4.036687] radeon :00:01.0: firmware: direct-loading firmware radeon/bonaire_uvd.bin [4.036699] [drm] Found UVD firmware Version: 1.64 Family ID: 9 [4.037329] radeon :00:01.0: firmware: direct-loading firmware radeon/BONAIRE_vce.bin [4.039173] [drm] Found VCE firmware/feedback version 40.2.2 / 15! [4.039214] [drm] GART: num cpu pages 524288, num gpu pages 524288 [4.069861] [drm] PCIE GART of 2048M enabled (table at 0x0030E000). [4.070084] radeon :00:01.0: WB enabled [4.070104] radeon :00:01.0: fence driver on ring 0 use gpu addr 0x2c00 and cpu addr 0xa084b742bc00 [4.070107] radeon :00:01.0: fence driver on ring 1 use gpu addr 0x2c04 and cpu addr 0xa084b742bc04 [4.070109] radeon :00:01.0: fence driver on ring 2 use gpu addr 0x2c08 and cpu addr 0xa084b742bc08 [4.070112] radeon :00:01.0: fence driver on ring 3 use gpu addr 0x2c0c and cpu addr 0xa084b742bc0c [4.070114] radeon :00:01.0: fence driver on ring 4 use gpu addr 0x2c10 and cpu addr 0xa084b742bc10 [4.071045] radeon :00:01.0: fence driver on ring 5 use gpu addr 0x00078d30 and cpu addr 0xaf3641c38d30 [4.071390] radeon :00:01.0: fence driver on ring 6 use gpu addr 0x2c18 and cpu addr 0xa084b742bc18 [4.071393] radeon :00:01.0: fence driver on ring 7 use gpu addr 0x2c1c and cpu addr 0xa084b742bc1c [4.071396] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.071397] [drm] Driver supports precise vblank timestamp query. [4.071457] radeon :00:01.0: radeon: using MSI. [4.071495] [drm] radeon: irq initialized. [4.078830] Adding 8378364k swap on /dev/sda5. Priority:-1 extents:1 across:8378364k SSFS [4.090169] [drm] ring test on 0 succeeded in 2 usecs [4.090284] [drm] ring test on 1 succeeded in 3 usecs [4.090306] [drm] ring test on 2 succeeded in 3 usecs [4.090523] [drm] ring test on 3 succeeded in 4 usecs [4.090531] [drm] ring test on 4 succeeded in 4 usecs [4.136627] [drm] ring test on 5 succeeded in 1 usecs [4.157135] [drm] UVD initialized successfully. [4.266822] [drm] ring test on 6 succeeded in 15 usecs [4.266842] [drm] ring test on 7 succeeded in 3 usecs [4.266843] [drm] VCE initialized successfully. [4.269850] [drm] ib test on ring 0 succeeded in 0 usecs [4.429744] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [4.573427] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null) [4.650006] random: crng init done [4.678518] audit: type=1400 audit(1513451935.668:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=458 comm="apparmor_parser" [4.683342] audit: type=1400 audit(1513451935.673:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=459 comm="apparmor_parser" [4.683350] audit: type=1400 audit(1513451935.673:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=459 comm="apparmor_parser" [4.683355] audit: type=1400 audit(1513451935.673:5): apparmor="STATUS"
Kernel 4.13.4 does not show a virtual console on framebuffer on cubox-i
Hi, I recompiled the linux kernel to enable CONFIG_VIDEO_CODA following the exactly description at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building I did the compile on a cubox-i, I added rd@xbian:~/Links/rd.disk/debian/kernel/linux-source-4.13$ cat localversion -armmp rd@xbian:~/Links/rd.disk/debian/kernel/linux-source-4.13$ to get the armmp version. That all went well, the new kernel booted, but I did not see any output on the console anymore. My kern.log is here http://paste.debian.net/993099/ The diff in the .config is here http://paste.debian.net/993101/ Any ideas are welcome. Thanks Rainer PS: I copied debian-kernel, please follow-up on the debian-arm list. -- Rainer Dorsch http://bokomoko.de/
Bug#861419: 4.12.0-0.bpo.1-amd64 does not seem to have this issue
Hi, just a short update: with 4.9.0 from Stretch I hit this issue within a week and had to reboot the system. With 4.12.0-0.bpo.1-amd64 I run now for almost three weeks and the issue did not pop up. Either it is fixed or it seems to be at least triggered less frequently. Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#861419: linux-image-4.9.0-2-amd64: Kernel Oops during resume after upgrade to Stretch
Package: src:linux Version: 4.9.18-1 Severity: normal Dear Maintainer, Hello, after the upgrade from Jessie to Stretch, I see a suspend regression, causing a kernel Oops: Apr 28 19:09:57 blackbox kernel: [79390.432173] PM: resume of devices complete after 3139.829 msecs Apr 28 19:09:57 blackbox kernel: [79390.432423] PM: Finishing wakeup. Apr 28 19:09:57 blackbox kernel: [79390.432424] Restarting tasks ... Apr 28 19:09:57 blackbox kernel: [79390.435906] BUG: unable to handle kernel Apr 28 19:09:57 blackbox kernel: [79390.435937] NULL pointer dereference at (null) Apr 28 19:09:57 blackbox kernel: [79390.435956] IP: [] i915_gem_request_alloc+0x107/0x250 [i915] Apr 28 19:09:57 blackbox kernel: [79390.436041] PGD 0 Apr 28 19:09:57 blackbox kernel: [79390.436052] Apr 28 19:09:57 blackbox kernel: [79390.436061] Oops: 0002 [#1] SMP Apr 28 19:09:57 blackbox kernel: [79390.436061] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache fuse uinput iTCO_wdt iTCO_vendor_support coretemp kvm_intel kvm irqbypass i915 pcspkr serio_raw snd_hda_codec_hdmi sg uvcvideo snd_hda_codec_realtek snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 lpc_ich mfd_core joydev videobuf2_core evdev snd_hda_intel video videodev snd_hda_codec snd_usb_audio drm_kms_helper parport_serial snd_usbmidi_lib media snd_rawmidi snd_seq_device snd_hda_core snd_hwdep snd_pcm snd_timer snd drm shpchp soundcore i2c_algo_bit asus_atk0110 acpi_cpufreq tpm_tis tpm_tis_core tpm button parport_pc ppdev lp parport loop dm_crypt dm_mod sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb glue_helper lrw gf128mul ablk_helper cryptd Apr 28 19:09:57 blackbox kernel: [79390.436061] aes_x86_64 mbcache sr_mod cdrom sd_mod ata_generic hid_cherry hid_generic usbhid hid psmouse ahci i2c_i801 i2c_smbus libahci firewire_ohci pata_jmicron libata firewire_core crc_itu_t scsi_mod atl1 mii floppy ehci_pci uhci_hcd ehci_hcd usbcore usb_common Apr 28 19:09:57 blackbox kernel: [79390.436061] CPU: 0 PID: 626 Comm: Xorg Not tainted 4.9.0-2-amd64 #1 Debian 4.9.18-1 Apr 28 19:09:57 blackbox kernel: [79390.436061] Hardware name: System manufacturer P5E-VM HDMI/P5E-VM HDMI, BIOS 040512/17/2007 Apr 28 19:09:57 blackbox kernel: [79390.436061] task: 9396e1d97000 task.stack: a37941428000 Apr 28 19:09:57 blackbox kernel: [79390.436061] RIP: 0010:[] [] i915_gem_request_alloc+0x107/0x250 [i915] Apr 28 19:09:57 blackbox kernel: [79390.436061] RSP: 0018:a3794142bca8 EFLAGS: 00010246 Apr 28 19:09:57 blackbox kernel: [79390.436061] RAX: 0001 RBX: 93961a3eb000 RCX: Apr 28 19:09:57 blackbox kernel: [79390.436061] RDX: c095fc68 RSI: c094a0c3 RDI: 93961a3eb0c8 Apr 28 19:09:57 blackbox kernel: [79390.436061] RBP: 9396e0202860 R08: 00360572 R09: 000d Apr 28 19:09:57 blackbox kernel: [79390.436061] R10: 0050 R11: 9396e54de000 R12: Apr 28 19:09:57 blackbox kernel: [79390.436061] R13: 9396e020 R14: 93957d9e5840 R15: Apr 28 19:09:57 blackbox kernel: [79390.436061] FS: 7f2ce2314a40() GS:9396efc0() knlGS: Apr 28 19:09:57 blackbox kernel: [79390.436061] CS: 0010 DS: ES: CR0: 80050033 Apr 28 19:09:57 blackbox kernel: [79390.436061] CR2: CR3: 0002242c1000 CR4: 06f0 Apr 28 19:09:57 blackbox kernel: [79390.436061] Stack: Apr 28 19:09:57 blackbox kernel: [79390.436061] 9396e4096000 9396e020 9395fdea4300 9396e572c000 Apr 28 19:09:57 blackbox kernel: [79390.436061] 93957d9e5840 c08dcbc4 93969c027c00 9396e00b9580 Apr 28 19:09:57 blackbox kernel: [79390.436061] 9396e3e71c00 9396e02001d8 93960001 Apr 28 19:09:57 blackbox kernel: [79390.436061] Call Trace: Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? intel_crtc_page_flip+0x414/0x960 [i915] Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? drm_mode_page_flip_ioctl+0x367/0x410 [drm] Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? drm_ioctl+0x1ea/0x470 [drm] Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? do_vfs_ioctl+0x9f/0x600 Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? SyS_ioctl+0x74/0x80 Apr 28 19:09:57 blackbox kernel: [79390.436061] [] ? system_call_fast_compare_end+0xc/0x9b Apr 28 19:09:57 blackbox kernel: [79390.436061] Code: 90 bb 89 c0 e8 cb 8d fc ff 48 8d 83 40 01 00 00 4c 89 6b 68 48 89 6b 78 48 89 83 40 01 00 00 48 89 83 48 01 00 00 b8 01 00 00 00 41 0f c1 04 24 83 c0 01 83 f8 01 0f 8e f5 00 00 00 8b 05 89 Apr 28 19:09:57 blackbox kernel: [79390.436061] RIP [] i915_gem_request_alloc+0x107/0x250 [i915] Apr 28 19:09:57 blackbox kernel: [79390.436061] RSP Apr 28 19:09:57
Bug#826518: Info received (Filesystem Issue (?))
I confirm that with a new SD card the issue disappeared, i.e. the issue is not related to the linux-image package. -- Rainer Dorsch http://bokomoko.de/
Bug#826518: Filesystem Issue (?)
Hi, I realized that the filesystem may have issues, when I check the filesystem on a jessie system (assuming the new kernels do not modify an ext4 fs that it is not backward compatible anymore), I get: blackbox:/home/rd/Links/rd.disk/tmp.nobackup# fsck /dev/sdb2 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) /dev/sdb2: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on /dev/sdb2 /dev/sdb2: ** WARNING: Filesystem still has errors ** blackbox:/home/rd/Links/rd.disk/tmp.nobackup# fsck /dev/sdb2 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) /dev/sdb2: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? no Clear journal? yes fsck.ext4: unable to set superblock flags on /dev/sdb2 /dev/sdb2: ** WARNING: Filesystem still has errors ** blackbox:/home/rd/Links/rd.disk/tmp.nobackup# fsck /dev/sdb2 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) /dev/sdb2: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on /dev/sdb2 /dev/sdb2: ** WARNING: Filesystem still has errors ** blackbox:/home/rd/Links/rd.disk/tmp.nobackup# I try to repro the issue in a new installation. Rainer -- Rainer Dorsch Lärchenstr. 6 72135 Dettenhausen 07157/734133
Bug#826518: Acknowledgement (linux-image-4.5.0-0.bpo.1-armmp: linux-image-4.5.0-0.bpo.2-armmp and linux-image-4.6.0-trunk-armmp fail to boot on cubox-i)
There is some additional information available on the debian-arm mailing list: https://lists.debian.org/debian-arm/2016/06/msg0.html Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#826518: linux-image-4.5.0-0.bpo.1-armmp: linux-image-4.5.0-0.bpo.2-armmp and linux-image-4.6.0-trunk-armmp fail to boot on cubox-i
Package: src:linux Version: 4.5.1-1~bpo8+1 Severity: important Hi, after upgrading to linux-image-4.5.0-0.bpo.2-armmp my cubox-i did not boot anymore. I tested linux-image-4.6.0-trunk-armmp and this resulted in the same effect. I could not boot with the kernel which had the problem, although reportbug requested that ;-) Booting failure with 4.6.0 from experimental: U-Boot 2014.10+dfsg1-2 (Nov 02 2014 - 00:31:26) CPU: Freescale i.MX6D rev1.2 at 792 MHz Reset cause: POR Board: MX6-CuBox-i DRAM: 1 GiB MMC: FSL_SDHC: 0 In:serial Out: vga Err: vga Net: FEC [PRIME] (Re)start USB... USB0: Port not available. USB1: USB EHCI 1.00 scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** File not found /boot.scr ** ** File not found uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 938 bytes read in 89 ms (9.8 KiB/s) Running bootscript from mmc ... ## Executing script at 1080 3620480 bytes read in 308 ms (11.2 MiB/s) 34350 bytes read in 231 ms (144.5 KiB/s) 15046745 bytes read in 13548 ms (1.1 MiB/s) Booting Debian 4.6.0-trunk-armmp from mmc 0:2... Kernel image @ 0x1080 [ 0x00 - 0x373e80 ] ## Flattened Device Tree blob at 1800 Booting using the fdt blob at 0x1800 EHCI failed to shut down host controller. Using Device Tree in place at 1800, end 1800b62d Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.6.0-trunk-armmp (debian- ker...@lists.debian.org) (gcc version 5.3.1 20160509 (Debian 5.3.1-19) ) #1 SMP Debian 4.6-1~exp1 (20) [0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: SolidRun Cubox-i Dual/Quad [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: UEFI not found. [0.00] cma: Reserved 16 MiB at 0x4f00 [0.00] Memory policy: Data cache writealloc [0.00] percpu: Embedded 13 pages/cpu @ef6c s20876 r8192 d24180 u53248 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260416 [0.00] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 ro rootwait console=ttymxc0,115200 console=tty1 elevator=noop [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Memory: 993568K/1048576K available (7773K kernel code, 932K rwdata, 2560K rodata, 1024K init, 390K bss, 38624K reserved, 16384K cma- reserved,) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xffc0 - 0xfff0 (3072 kB) [0.00] vmalloc : 0xf080 - 0xff80 ( 240 MB) [0.00] lowmem : 0xc000 - 0xf000 ( 768 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc0b175d8 (11326 kB) [0.00] .init : 0xc0c0 - 0xc0d0 (1024 kB) [0.00] .data : 0xc0d0 - 0xc0de9274 ( 933 kB) [0.00].bss : 0xc0deb000 - 0xc0e4c9c4 ( 391 kB) [0.00] Hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 32. [0.00] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2 [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] L2C-310 erratum 769419 enabled [0.00] L2C-310 enabling early BRESP for Cortex-A9 [0.00] L2C-310 full line of zeros enabled for Cortex-A9 [0.00] L2C-310 ID prefetch enabled, offset 1 lines [0.00] L2C-310 dynamic clock gating enabled, standby mode enabled [0.00] L2C-310 cache controller enabled, 16 ways, 1024 kB [0.00] L2C-310: CACHE_ID 0x41c7, AUX_CTRL 0x76070001 [0.00] Switching to timer-based delay loop, resolution 333ns [0.07] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns [0.27] clocksource: mxc_timer1: mask: 0x max_cycles: 0x, max_idle_ns: 637086815595 ns [0.002819] Console: colour dummy device 80x30 [0.003690] console [tty1] enabled [0.003734] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=12000) [0.003787] pid_max: default: 32768 minimum: 301 [0.004004] Security Framework initialized [0.004034] Yama: disabled by default; enable with sysctl kernel
Bug#797779: brcmfmac4330-sdio.txt from OpenElec fixes the issue
Hi Stefan, I copied the debian-arm list, because this should be an issue which is present on almost any ARM based SoC and there might exist solutions for other SoCs already. On Wednesday 02 September 2015 19:37:13 Stefan Lippers-Hollmann wrote: > Hi > > On 2015-09-02, Rainer Dorsch wrote: > > Hi, > > > > I copied brcmfmac4330-sdio.txt from OpenElec > > > > https://github.com/OpenELEC/wlan-firmware/blob/master/firmware/brcm/brcmfm > > ac4330-sdio.txt > > > > to /lib/firmware/brcm > > > > which fixes the issue > > [...] > > brcmfmac4330-sdio.txt is OEM, respectively even device specific[1], > nothing that would be generic enough (for all bcm4330 devices) to be > shipped by Debian's firmware packages. > > On x86 systems this blob is typically provided in a UEFI variable (but not > found automatically by the kernel, so you need to copy it from the UEFI > variable to /lib/firmware). On embedded devices it needs to be provided by > the manufacturer (not Broadcom, but the OEM vendor) of your wlan card > (respectively the devboard). > > Regards > Stefan Lippers-Hollmann > > [1] These blobs contain calibration data, regulatory domain settings > and similar information, which is highly specific to your exact > device. Using data from a different device would make it run out > of its specifications (getting you in trouble with FCC, ETSI, > etc.) and could even physically damage your device. Are you saying that I opened the bugreport against the wrong package or that this is not a bug at all? Doesn't on an ARM system the device tree file contain embedded device specific information, which is shipped with the kernel itself? And would this txt file not fit perfectly in this category of information? How is this issue addressed for other ARM SoCs? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#797779: brcmfmac4330-sdio.txt from OpenElec fixes the issue
Hi, I copied brcmfmac4330-sdio.txt from OpenElec https://github.com/OpenELEC/wlan-firmware/blob/master/firmware/brcm/brcmfmac4330-sdio.txt to /lib/firmware/brcm which fixes the issue rd@home:~$ dmesg |grep brcm [2.092917] brcm_reg: disabling [6.786725] usbcore: registered new interface driver brcmfmac [6.846286] brcmfmac_sdio mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac4330-sdio.bin [6.879810] brcmfmac_sdio mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac4330-sdio.txt [7.225901] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 25 2011 19:34:12 version 5.90.125.104 [7.258702] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 11.484505] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists [ 11.491109] brcmfmac: brcmf_add_if: ignore IF event rd@home:~$ /sbin/ifconfig -a eth1 Link encap:Ethernet Hardware Adresse d0:63:b4:00:2b:ac inet Adresse:192.168.178.29 Bcast:192.168.178.255 Maske:255.255.255.0 inet6-Adresse: fd00::d263:b4ff:fe00:2bac/64 Gültigkeitsbereich:Global inet6-Adresse: fe80::d263:b4ff:fe00:2bac/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:6800 errors:0 dropped:0 overruns:0 frame:0 TX packets:5344 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:1065692 (1.0 MiB) TX bytes:5224223 (4.9 MiB) loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:5946 (5.8 KiB) TX bytes:5946 (5.8 KiB) wlan0 Link encap:Ethernet Hardware Adresse b8:5a:f7:82:aa:c2 UP BROADCAST MULTICAST MTU:1500 Metrik:1 RX packets:490 errors:0 dropped:490 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:233292 (227.8 KiB) TX bytes:0 (0.0 B) rd@home:~$ Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#797779: firmware-brcm80211: failed to load brcm/brcmfmac4330-sdio.txt
Package: firmware-brcm80211 Version: 0.43 Severity: normal Dear Maintainer, I installed linux-image-4.2.0-trunk-armmp on a cubox-i with an imx.6 CPU. For the first time the wireless interface should be supported by a stock kernel. Installing the Debian package results in the error in the modprobe of the brcmfmac_sdio during boot and there is no wireless module visible: rd@home:~$ dmesg |grep brcm [2.092789] brcm_reg: disabling [6.744194] usbcore: registered new interface driver brcmfmac [6.798042] brcmfmac_sdio mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac4330-sdio.bin [6.816911] brcmfmac_sdio mmc0:0001:1: firmware: failed to load brcm/brcmfmac4330-sdio.txt (-2) [6.847619] brcmfmac_sdio mmc0:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.txt failed with error -2 [6.847627] brcmfmac_sdio mmc0:0001:1: Falling back to user helper [7.876909] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 [8.65] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 rd@home:~$ /sbin/ifconfig -a eth1 Link encap:Ethernet Hardware Adresse d0:63:b4:00:2b:ac inet Adresse:192.168.178.29 Bcast:192.168.178.255 Maske:255.255.255.0 inet6-Adresse: fd00::d263:b4ff:fe00:2bac/64 Gültigkeitsbereich:Global inet6-Adresse: fe80::d263:b4ff:fe00:2bac/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:1561 errors:0 dropped:0 overruns:0 frame:0 TX packets:1222 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:246316 (240.5 KiB) TX bytes:1150073 (1.0 MiB) loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX packets:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:2718 (2.6 KiB) TX bytes:2718 (2.6 KiB) rd@home:~$ -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (250, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 4.2.0-trunk-armmp (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.120 -- no debconf information
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, Am Samstag 07 März 2015, 14:26:17 schrieb Emil Goode: > Just to clarify, suspend/resume is working but it takes more than 60 sec for > suspend to complete? yes, suspend/resume is working. I did three cycles and measured the time for suspend: The first suspend took approx. 60 seconds, the second and third approx. 30 seconds. Kind regards, Rainer -- 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/1545337.eEYHhnhZWe@silberkiste
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, sorry for the long silence, but I did not have physical access to the machine for which I reported the bug and I did not want to install new kernel from remote... I recompiled a recent kernel with PM_TRACE_RTC enabled, but still get no log data in pm-suspend.log: root@Silberkiste:~# uname -a Linux Silberkiste 4.0.0-rc2+ #1 SMP Thu Mar 5 01:01:25 CET 2015 x86_64 GNU/Linux root@Silberkiste:~# grep PM_TRACE_RTC /boot/config-4.0.0-rc2+ CONFIG_PM_TRACE_RTC=y root@Silberkiste:~# head -4 /usr/lib/pm-utils/pm-functions #!/bin/sh # vim:noexpandtab export PM_DEBUG=true root@Silberkiste:~# cat /var/log/pm-suspend.log root@Silberkiste:~# ls -l /var/log/pm-suspend.log -rw-r--r-- 1 root root 0 Jan 3 15:52 /var/log/pm-suspend.log root@Silberkiste:~# I did 501 echo 1 > /sys/power/pm_trace 502 echo mem > /sys/power/state but this did not create any logs. Do you have any suggestions, what I might do wrong? Thanks, Rainer On Sunday 04 January 2015 18:12:44 Emil Goode wrote: > Hello Rainer, > > On Sat, Jan 03, 2015 at 04:23:44PM +0100, Rainer Dorsch wrote: > > Hi Emil, > > > > I have only remote access to the system for the next few weeks and I feel > > somewhat uncomfortable to experiment with my self-compiled kernels on the > > system or changing networking configurations. > > > > So please apologize that I may need 3-4 weeks to test that. > > > > I assume you suggest to follow > > > > http://kernel-handbook.alioth.debian.org/ch-common-tasks.html > > > > to enable PM_TRACE_RTC and rebuild the kernel, correct? > > Yes and you can clone this tree for testing upstream kernels. > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > Best regards, > > Emil Goode > > > On Tuesday 30 December 2014 12:40:53 Emil Goode wrote: > > > Hello Rainer, > > > > > > On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: > > > > Hi Emil, > > > > > > > > Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: > > > > > Hello Rainer, > > > > > > > > > > The below procedure would give more information: > > > > > > > > > > Add the following line to the top of the file > > > > > /usr/lib/pm-utils/pm-functions. > > > > > > > > > > export PM_DEBUG=true > > > > > > > > > > Then suspend with: > > > > > > > > > > echo 1 > /sys/power/pm_trace > > > > > echo mem > /sys/power/state > > > > > > > > HmmI do not have a pm_trace > > > > > > Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel > > > config. > > > > > > Please be aware that when using pm_trace it will mess with your > > > machine's > > > real-time clock. > > > > > > > There is a similar bug report already for an older kernel, but that > > > > seems > > > > to be fixed (?) > > > > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 > > > > > > The iwlagn module is for intel wireless and I believe you are using > > > broadcom. > > > > > > > > Post dmesg and the contents of /var/log/pm-suspend.log. > > > > > > > > > > Have you tried disabling the mac80211 module? > > > > > > > > Can you tell how I unload a module for suspend or if > > > > > > > > http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-> > > > > > > > to-u > > > > nload-modules-at-suspend-to-disk also applies to systemd? > > > > > > I think you can temporarily blacklist modules as described here: > > > > > > https://wiki.debian.org/KernelModuleBlacklisting > > > > > > I would also try the latest upstream kernel, this might have been fixed. > > > > > > Best regards, > > > > > > Emil Goode -- Rainer Dorsch http://bokomoko.de/
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, I have only remote access to the system for the next few weeks and I feel somewhat uncomfortable to experiment with my self-compiled kernels on the system or changing networking configurations. So please apologize that I may need 3-4 weeks to test that. I assume you suggest to follow http://kernel-handbook.alioth.debian.org/ch-common-tasks.html to enable PM_TRACE_RTC and rebuild the kernel, correct? Kind regards, Rainer On Tuesday 30 December 2014 12:40:53 Emil Goode wrote: > Hello Rainer, > > On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote: > > Hi Emil, > > > > Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: > > > Hello Rainer, > > > > > > The below procedure would give more information: > > > > > > Add the following line to the top of the file > > > /usr/lib/pm-utils/pm-functions. > > > > > > export PM_DEBUG=true > > > > > > Then suspend with: > > > > > > echo 1 > /sys/power/pm_trace > > > echo mem > /sys/power/state > > > > HmmI do not have a pm_trace > > Ok, that is because PM_TRACE_RTC needs to be enabled in the kernel config. > > Please be aware that when using pm_trace it will mess with your machine's > real-time clock. > > > There is a similar bug report already for an older kernel, but that seems > > to be fixed (?) > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 > > The iwlagn module is for intel wireless and I believe you are using > broadcom. > > > Post dmesg and the contents of /var/log/pm-suspend.log. > > > > > > Have you tried disabling the mac80211 module? > > > > Can you tell how I unload a module for suspend or if > > > > http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-u > > nload-modules-at-suspend-to-disk also applies to systemd? > > I think you can temporarily blacklist modules as described here: > > https://wiki.debian.org/KernelModuleBlacklisting > > I would also try the latest upstream kernel, this might have been fixed. > > Best regards, > > Emil Goode -- Rainer Dorsch http://bokomoko.de/ -- 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/1576198.QiKW1aPnlR@blackbox
Bug#774036: Re: Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode: > Hello Rainer, > > The below procedure would give more information: > > Add the following line to the top of the file > /usr/lib/pm-utils/pm-functions. > > export PM_DEBUG=true > > Then suspend with: > > echo 1 > /sys/power/pm_trace > echo mem > /sys/power/state HmmI do not have a pm_trace root@Silberkiste:~# ls -l /sys/power/ insgesamt 0 -rw-r--r-- 1 root root 4096 Dez 29 23:19 disk -rw-r--r-- 1 root root 4096 Dez 30 00:04 image_size -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_async -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_freeze_timeout -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_print_times -rw-r--r-- 1 root root 4096 Dez 30 00:04 pm_test -rw-r--r-- 1 root root 4096 Dez 30 00:04 reserved_size -rw-r--r-- 1 root root 4096 Dez 29 23:19 resume -rw-r--r-- 1 root root 4096 Dez 29 23:19 state -rw-r--r-- 1 root root 4096 Dez 30 00:04 wakeup_count root@Silberkiste:~# There is a similar bug report already for an older kernel, but that seems to be fixed (?) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638264 > Post dmesg and the contents of /var/log/pm-suspend.log. > > Have you tried disabling the mac80211 module? Can you tell how I unload a module for suspend or if http://superuser.com/questions/620201/how-to-force-ubuntu-debian-mint-to-unload-modules-at-suspend-to-disk also applies to systemd? Thanks, Rainer -- 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/1904133.PosVhOpTgo@silberkiste
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, thanks again for our response. I have additional information, the behavior is not a hang, but the system simply needs around additional 30s to really "power off". I copied the dmesg output form dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after into http://bokomoko.de/~rd/Debian/774036/ I do not recall this behavior with the 3.2.x kernel in wheezy, but that makes it really into a very minor issue. Rainer Am Sonntag, 28. Dezember 2014, 15:56:28 schrieb Emil Goode: > Hello, > > On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote: > > Package: src:linux > > Version: 3.16.7-ckt2-1 > > Followup-For: Bug #774036 > > > > Dear Ben, > > > > many thanks for the superfast response and thanks for pointing out > > that I was running the nvidia driver. I run now with nouveau and also > > purge the virtualbox stuff. > > > > Unfortunately, the behavior is exactly the same though (except that > > there is no blinking cursor with nouveau, when the system hangs), > > i.e. the resume works when I use freezer in debug mode, the system > > hangs when I go to the next level (devices). > > When you get a black screen does the system hang completely or is it > possible to login to the system over ssh? If it's possible to login it > could be useful to post the dmesg output here. > > Best regards, > > Emil Goode -- 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/201412281906.57731...@bokomoko.de
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Hi Emil, Am Sonntag, 28. Dezember 2014, 15:56:28 schrieb Emil Goode: > Hello, > > On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote: > > Package: src:linux > > Version: 3.16.7-ckt2-1 > > Followup-For: Bug #774036 > > > > Dear Ben, > > > > many thanks for the superfast response and thanks for pointing out > > that I was running the nvidia driver. I run now with nouveau and also > > purge the virtualbox stuff. > > > > Unfortunately, the behavior is exactly the same though (except that > > there is no blinking cursor with nouveau, when the system hangs), > > i.e. the resume works when I use freezer in debug mode, the system > > hangs when I go to the next level (devices). > > When you get a black screen does the system hang completely or is it > possible to login to the system over ssh? If it's possible to login it > could be useful to post the dmesg output here. Thank you for the idea, I tried it, but the system does not respond anymore to an ssh request. It certainly works when the system is up. Kind regards, Rainer -- 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/201412281810.24747...@bokomoko.de
Bug#774036: linux-image-3.16.0-4-amd64: Untainted Kernel shows similar issue
Package: src:linux Version: 3.16.7-ckt2-1 Followup-For: Bug #774036 Dear Ben, many thanks for the superfast response and thanks for pointing out that I was running the nvidia driver. I run now with nouveau and also purge the virtualbox stuff. Unfortunately, the behavior is exactly the same though (except that there is no blinking cursor with nouveau, when the system hangs), i.e. the resume works when I use freezer in debug mode, the system hangs when I go to the next level (devices). rd@Silberkiste:/etc/default$ cat /sys/power/pm_test [none] core processors platform devices freezer rd@Silberkiste:/etc/default$ Please let me know, if there is anything more I could provide. Thanks Rainer -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=d47ae970-51f3-48d3-b19d-edd7413e080f ro quiet elevator=noop rootflags=noatime,discard,data=ordered,errors=remount-ro acpi_sleep=old_ordering ** Not tainted ** Kernel log: [ 33.205263] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205265] sd 4:0:0:0: [sda] [ 33.205267] Sense Key : Aborted Command [current] [descriptor] [ 33.205270] Descriptor sense data with sense descriptors (in hex): [ 33.205272] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205282] 07 80 0b 58 [ 33.205287] sd 4:0:0:0: [sda] [ 33.205290] Add. Sense: Scsi parity error [ 33.205293] sd 4:0:0:0: [sda] CDB: [ 33.205294] Read(10): 28 00 07 80 0b e8 00 00 08 00 [ 33.205306] sd 4:0:0:0: [sda] [ 33.205308] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205310] sd 4:0:0:0: [sda] [ 33.205312] Sense Key : Aborted Command [current] [descriptor] [ 33.205315] Descriptor sense data with sense descriptors (in hex): [ 33.205317] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205327] 07 80 0b 58 [ 33.205332] sd 4:0:0:0: [sda] [ 33.205335] Add. Sense: Scsi parity error [ 33.205338] sd 4:0:0:0: [sda] CDB: [ 33.205339] Read(10): 28 00 07 80 0b f0 00 00 08 00 [ 33.205351] sd 4:0:0:0: [sda] [ 33.205353] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205355] sd 4:0:0:0: [sda] [ 33.205357] Sense Key : Aborted Command [current] [descriptor] [ 33.205360] Descriptor sense data with sense descriptors (in hex): [ 33.205362] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205372] 07 80 0b 58 [ 33.205377] sd 4:0:0:0: [sda] [ 33.205380] Add. Sense: Scsi parity error [ 33.205383] sd 4:0:0:0: [sda] CDB: [ 33.205385] Read(10): 28 00 07 80 0b f8 00 00 08 00 [ 33.205408] sd 4:0:0:0: [sda] [ 33.205411] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205414] sd 4:0:0:0: [sda] [ 33.205415] Sense Key : Aborted Command [current] [descriptor] [ 33.205419] Descriptor sense data with sense descriptors (in hex): [ 33.205421] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205431] 07 80 0b 58 [ 33.205436] sd 4:0:0:0: [sda] [ 33.205438] Add. Sense: Scsi parity error [ 33.205441] sd 4:0:0:0: [sda] CDB: [ 33.205443] Read(10): 28 00 07 80 0b 38 00 00 08 00 [ 33.205456] sd 4:0:0:0: [sda] [ 33.205459] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205461] sd 4:0:0:0: [sda] [ 33.205463] Sense Key : Aborted Command [current] [descriptor] [ 33.205466] Descriptor sense data with sense descriptors (in hex): [ 33.205468] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205478] 07 80 0b 58 [ 33.205483] sd 4:0:0:0: [sda] [ 33.205486] Add. Sense: Scsi parity error [ 33.205489] sd 4:0:0:0: [sda] CDB: [ 33.205490] Read(10): 28 00 07 80 0b 40 00 00 08 00 [ 33.205502] sd 4:0:0:0: [sda] [ 33.205504] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205507] sd 4:0:0:0: [sda] [ 33.205509] Sense Key : Aborted Command [current] [descriptor] [ 33.205512] Descriptor sense data with sense descriptors (in hex): [ 33.205514] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205524] 07 80 0b 58 [ 33.205529] sd 4:0:0:0: [sda] [ 33.205532] Add. Sense: Scsi parity error [ 33.205535] sd 4:0:0:0: [sda] CDB: [ 33.205536] Read(10): 28 00 07 80 0b 48 00 00 08 00 [ 33.205549] sd 4:0:0:0: [sda] [ 33.205551] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 33.205554] sd 4:0:0:0: [sda] [ 33.20] Sense Key : Aborted Command [current] [descriptor] [ 33.205558] Descriptor sense data with sense descriptors (in hex): [ 33.205560] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 33.205571] 07 80 0b 58 [ 33.205575] sd 4:0:0:0: [sda] [ 33.205578] Add. Sense: Scsi parity error [ 33.205581] sd 4:0:0:0: [sda] CDB: [ 33.205583] Read(10): 28 00 07 80 0b 50 00 00 08 00 [ 33.205596] sd 4:0:0:0: [sda] [ 33.205598
Bug#774036: Upstream bugreport
Hello, this bug seems to be reported upstream as well: https://bugzilla.kernel.org/show_bug.cgi?id=43368 Kind regards, Rainer -- 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/1772054.zErkJ5IP4b@omjuta
Bug#774036: Kernel testing facility
Hi, I have one additional information, when following the "Kernel testing facility" description in https://wiki.debian.org/Suspend freezer test the freezing of processes devices test the freezing of processes and suspending of devices platform test the freezing of processes, suspending of devices and platform global control methods(*) processors test the freezing of processes, suspending of devices, platform global control methods and the disabling of nonboot CPUs core test the freezing of processes, suspending of devices, platform global control methods, the disabling of nonboot CPUs and suspending of platform/system devices On my system # echo freezer > /sys/power/pm_test # dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after resumes successfully. # echo devices > /sys/power/pm_test # dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after does not resume anymore and shows the issue described before. Or to be precise: the screen shows a blinking cursor, when it reaches the hang situation during suspend. This is different than what I would have expected, it seems that not only powering off does not work (then I would have expected an issue in the last step of the sequence described above. Here I am stuck now, please let me know if there is more information I can provide. Thanks, Rainer -- 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/1780974.1UEkOtx4ax@silberkiste
Bug#774036: linux-image-3.16.0-4-amd64: poweroff after suspend or hibernate does not work anymore after upgrade wheezy -> jessie
Package: src:linux Version: 3.16.7-ckt2-1 Severity: normal Dear Maintainer, I upgraded from wheezy to jessie and after the upgrade, suspend and hibernate are not fully functional anymore. Hibernate works, but the final power off does not work. If I do a hard reboot, the resume works flawless. For suspend, there is also no power off and consequently I cannot restart and I have to reboot. For wheezy, I had similar symptoms, there adding acpi_sleep=old_ordering to the kernel cmdline solved the issue for the wheezy kernel 3.2.x, but it does not solve the issue for the 3.16.x kernel from jessie. I see the same behavior when starting the suspend process with KDE, with "systemctl suspend" or even when I just echo mem > /sys/power/state I follow https://01.org/linuxgraphics/documentation/how-debug-suspend-resume-issues-0 and provide more debug information. Since I do not have permanent access to the system, it would be useful, if you can tell me soon, if there is particularly important information to collect. Many thanks, Rainer -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=d47ae970-51f3-48d3-b19d-edd7413e080f ro quiet elevator=noop rootflags=noatime,discard,data=ordered,errors=remount-ro acpi_sleep=old_ordering ** Tainted: PWO (4609) * Proprietary module has been loaded. * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [ 486.009299] pci :00:01.5: no hotplug settings from platform [ 486.009301] pci :00:01.5: using default PCI settings [ 486.009310] pci :00:01.6: no hotplug settings from platform [ 486.009313] pci :00:01.6: using default PCI settings [ 486.009321] pci :00:02.0: no hotplug settings from platform [ 486.009324] pci :00:02.0: using default PCI settings [ 486.009333] pci :00:02.1: no hotplug settings from platform [ 486.009336] pci :00:02.1: using default PCI settings [ 486.009346] pci :00:02.2: no hotplug settings from platform [ 486.009348] pci :00:02.2: using default PCI settings [ 486.009358] pcieport :00:03.0: no hotplug settings from platform [ 486.009370] nvidia :01:00.0: no hotplug settings from platform [ 486.009375] pci :00:09.0: no hotplug settings from platform [ 486.009378] pci :00:09.0: using default PCI settings [ 486.009391] pci :00:0a.0: no hotplug settings from platform [ 486.009394] pci :00:0a.0: using default PCI settings [ 486.009403] nForce2_smbus :00:0a.1: no hotplug settings from platform [ 486.009406] nForce2_smbus :00:0a.1: using default PCI settings [ 486.009416] pci :00:0a.2: no hotplug settings from platform [ 486.009418] pci :00:0a.2: using default PCI settings [ 486.009428] ohci-pci :00:0b.0: no hotplug settings from platform [ 486.009431] ohci-pci :00:0b.0: using default PCI settings [ 486.009440] ehci-pci :00:0b.1: no hotplug settings from platform [ 486.009443] ehci-pci :00:0b.1: using default PCI settings [ 486.009452] pata_amd :00:0d.0: no hotplug settings from platform [ 486.009455] pata_amd :00:0d.0: using default PCI settings [ 486.009464] sata_nv :00:0e.0: no hotplug settings from platform [ 486.009467] sata_nv :00:0e.0: using default PCI settings [ 486.009475] sata_nv :00:0f.0: no hotplug settings from platform [ 486.009478] sata_nv :00:0f.0: using default PCI settings [ 486.009487] pci :00:10.0: no hotplug settings from platform [ 486.009489] pci :00:10.0: using default PCI settings [ 486.009504] b43-pci-bridge :02:06.0: no hotplug settings from platform [ 486.009507] b43-pci-bridge :02:06.0: using default PCI settings [ 486.009519] firewire_ohci :02:08.0: no hotplug settings from platform [ 486.009522] firewire_ohci :02:08.0: using default PCI settings [ 486.009533] snd_hda_intel :00:10.1: no hotplug settings from platform [ 486.009535] snd_hda_intel :00:10.1: using default PCI settings [ 486.009545] forcedeth :00:14.0: no hotplug settings from platform [ 486.009547] forcedeth :00:14.0: using default PCI settings [ 486.044596] done. [ 486.108414] cfg80211: World regulatory domain updated: [ 486.108421] cfg80211: DFS Master region: unset [ 486.108423] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 486.108427] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 486.108431] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 486.108434] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 486.108437] cfg80211: (517 KHz - 525 KHz @ 16 KHz), (N/A, 2000 mBm), (N/A) [ 486.108440] cfg80211: (525 KHz - 533 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 4
Bug#747247: Problem Solved
Hello, the kernel 3.14.12-1 contains the patch discussed in the the freedesktop.org page. I assume that one of these - [x86] drm/i915: Avoid div-by-zero when pixel_multiplier is zero (regression in 3.13) - [x86] drm/i915: set backlight duty cycle after backlight enable for gen4 (regression in 3.14) fixed the regression. Bug can be closed from my perspective. Many thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- 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/5780889.RlzYOKnFgV@blackbox
Bug#747247: Similar issue on freedesktop.org
This issue looks very similar to mine: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747247 Rainer -- Rainer Dorsch http://bokomoko.de/ -- 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/4983901.XmEAhQ9AuN@blackbox
Bug#747247: Kernel Module loaded
151633 6 sg,usb_storage,libata,sd_mod,sr_mod,firewire_sbp2 usbcore 133957 8 uhci_hcd,snd_usb_audio,uvcvideo,usb_storage,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid usb_common 12408 1 usbcore rd@blackbox:~$ -- Rainer Dorsch http://bokomoko.de/ -- 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/3166163.ihHQsxIQWa@blackbox
Bug#747247: linux-image-3.14-1-686-pae: Same issue with linux-image-3.14-1-686-pae
Package: src:linux Version: 3.14.7-1 Followup-For: Bug #747247 Dear Maintainer, I see exactly the same problem as the orignal reporter. I use pm-suspend to suspend. Resume from suspend worked for several years on that system, e.g. 3.13.7-1 works flawless. Thaw from hibernate still works flawless with 3.14 on that system. I followed the procedure described in the Debian wiki, https://wiki.debian.org/Suspend in particular I set the tests in /sys/power/pm_test and all (!) of them successfully resume. While writting the bug report, I am running linux-image 3.13.7-1. I am happy to provide more information if anybody requests something. Thanks, Rainer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: auto lo iface lo inet loopback allow-hotplug wlan1 eth0 iface eth0 inet dhcp mtu 1492 iface wlan1 inet dhcp wpa-ssid LS6 wpa-key-mgmt *** wpa-psk wpa-driver wext iface ppp0 inet ppp provider klarmobil iface ppp1 inet ppp provider fonic allow-hotplug n900 iface n900 inet static address 192.168.2.14 netmask 255.255.255.0 broadcast 192.168.2.255 up iptables -I INPUT 1 -s 192.168.2.15 -j ACCEPT iface n900wiki inet static address 192.168.2.14 netmask 255.255.255.0 up iptables -A POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE up echo 1 > /proc/sys/net/ipv4/ip_forward down iptables -D POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE down echo 0 > /proc/sys/net/ipv4/ip_forward ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82G35 Express DRAM Controller [8086:2980] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8295] 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: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G35 Express Integrated Graphics Controller [8086:2982] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8276] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation 82G35 Express Integrated Graphics Controller [8086:2983] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8276] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] 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: uhci_hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] 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: uhci_hcd 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] 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: uhci_hcd 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8277] 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: ehci-pci 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) Subsystem: ASUSTeK Computer Inc. Device [1043:829f] 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
734430 enables Wifi in Cubox-i and other imx6 devices
Hello, I was just about to submit a bug report to enable support for wifi with the Debian armmp kernels for imx6 devices, in particular the Cubox-i. But then I found that there is already a bug report from January to request this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734430 Is there any plan to include that or a reason not to make these modules available? Many thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- 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/5389a79a.7010...@bokomoko.de
rcu_sched self-detected stall on CPU { 0}
e/0x240 Mar 21 14:29:10 www syslogd: /dev/:0: No such file or directory Mar 21 14:29:10 www syslogd: /dev/:1: No such file or directory Mar 21 14:29:10 www vmunix: [118396.260268] Code: 00 00 8d bc 27 00 00 00 00 fa c3 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 fb c3 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 fb f4 8d b6 00 00 00 00 8d bc 27 00 00 00 00 f4 c3 8d b4 26 00 00 Mar 21 14:29:10 www ddclient[3535]: WARNING: file /etc/ddclient.conf, line 8: Invalid Value for keyword 'login' = '' Mar 21 14:30:25 www vmunix: [118490.575735] [drm:intel_crtc_cursor_set], cursor off Any hint is welcome. Many thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- 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/5760842.nsjZBo4pF4@blackbox
Re: zram advice needed
Hi, Am Monday 09 April 2012 schrieb Ben Hutchings: > On Mon, 2012-04-09 at 17:24 +0200, Rainer Dorsch wrote: > [...] > > > > Most likely you can fix this by running depmod again, but that is run > > > automatically at installation time. > > > > No, doesn't help unforteunately: > > > > blackbox:~# depmod > > blackbox:~# modprobe zram zram_num_devices=2 > > ERROR: could not insert 'zram': No such file or directory > > blackbox:~# > > Well I have no idea what's going wrong. Please report a bug against > kmod (assuming that package is installed) or else module-init-tools. > I have kmod installed rd@blackbox:~/sb$ apt-cache policy kmod kmod: Installiert: 6-2 Kandidat:6-2 Versionstabelle: *** 6-2 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~/sb$ and opened a bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668216 Thanks again, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: zram advice needed
Hello Ben,
thanks for you quick reply.
Am Monday 09 April 2012 schrieb Ben Hutchings:
> On Mon, 2012-04-09 at 11:49 +0200, Rainer Dorsch wrote:
> > Hello,
> >
> > I have a small issue with zram, I cannot load it with modprobe, just with
> > insmod, which broke my /etc/init.d/zram script. The problem was
> > introduced with same recent upgrade in wheezy.
> >
> > blackbox:~# uname -a
> > Linux blackbox 3.2.0-2-686-pae #1 SMP Tue Mar 20 19:48:26 UTC 2012 i686
> > GNU/Linux
> > blackbox:~# modprobe zram
> > ERROR: could not insert 'zram': No such file or directory
> > blackbox:~# modprobe -d /lib/modules/3.2.0-2-686-pae zram
> > blackbox:~# lsmod|grep zram
> > blackbox:~# insmod /lib/modules/3.2.0-2-686-
> > pae/kernel/drivers/staging/zram/zram.ko
> > blackbox:~# lsmod|grep zram
> > zram 13155 0
> > blackbox:~#
> >
> > Any hint what to check is very welcome.
>
> ls -l /lib/modules/3.2.0-2-686-pae/modules.dep{,.bin}
> grep zram /lib/modules/3.2.0-2-686-pae/modules.dep{,.bin}
That looks ok for me (?):
rd@blackbox:~$ ls -l /lib/modules/3.2.0-2-686-pae/modules.dep{,.bin}
-rw-r--r-- 1 root root 351421 Apr 9 17:20 /lib/modules/3.2.0-2-686-
pae/modules.dep
-rw-r--r-- 1 root root 487906 Apr 9 17:20 /lib/modules/3.2.0-2-686-
pae/modules.dep.bin
rd@blackbox:~$ grep zram /lib/modules/3.2.0-2-686-pae/modules.dep{,.bin}
/lib/modules/3.2.0-2-686-pae/modules.dep:kernel/drivers/staging/zram/zram.ko:
Übereinstimmungen in Binärdatei /lib/modules/3.2.0-2-686-pae/modules.dep.bin.
rd@blackbox:~$ su -
Passwort:
blackbox:~# modprobe zram zram_num_devices=2
ERROR: could not insert 'zram': No such file or directory
blackbox:~# ls -l /lib/modules/3.2.0-2-686-
pae/kernel/drivers/staging/zram/zram.ko
-rw-r--r-- 1 root root 17412 Mär 20 23:01 /lib/modules/3.2.0-2-686-
pae/kernel/drivers/staging/zram/zram.ko
blackbox:~#
> Most likely you can fix this by running depmod again, but that is run
> automatically at installation time.
No, doesn't help unforteunately:
blackbox:~# depmod
blackbox:~# modprobe zram zram_num_devices=2
ERROR: could not insert 'zram': No such file or directory
blackbox:~#
Thanks,
Rainer
--
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdor...@web.de
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/
signature.asc
Description: This is a digitally signed message part.
zram advice needed
Hello, I have a small issue with zram, I cannot load it with modprobe, just with insmod, which broke my /etc/init.d/zram script. The problem was introduced with same recent upgrade in wheezy. blackbox:~# uname -a Linux blackbox 3.2.0-2-686-pae #1 SMP Tue Mar 20 19:48:26 UTC 2012 i686 GNU/Linux blackbox:~# modprobe zram ERROR: could not insert 'zram': No such file or directory blackbox:~# modprobe -d /lib/modules/3.2.0-2-686-pae zram blackbox:~# lsmod|grep zram blackbox:~# insmod /lib/modules/3.2.0-2-686- pae/kernel/drivers/staging/zram/zram.ko blackbox:~# lsmod|grep zram zram 13155 0 blackbox:~# Any hint what to check is very welcome. Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- 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/201204091149.27883...@bokomoko.de
Bug#510607: Another patch is required
The applied patch http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d06193f311102b2c990ec5f66b470ea49ecc73a4 does not fix the problem completely, 2.6.26-13 is still not yet working for me. Closer investigation of the commit history between 2.6.26 (July 13th) and the patch applied shows that there are a few other patches. When I apply http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d8acd46fb7e962ac04baef5a118d431fae6b0f6 the USB WLAN stick works for me. I suggest to apply this patch as well. The maintainer of the driver confirms that this patch is save for 2.6.26: http://lists.debian.org/debian-kernel/2009/01/msg00394.html (the patch he is proposing additionally in his mail is already in 2.6.26). Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: rt2500usb
Am Freitag, 23. Januar 2009 schrieb Ivo van Doorn: > On Thursday 22 January 2009, Rainer Dorsch wrote: > > Ivo, > > > > Am Sonntag, 18. Januar 2009 schrieb Ivo van Doorn: > > > [...] > > > > > > No, but I there are dozens of patches between 2.6.26 and 2.6.27 so it > > > is hard to say which patches would exactly have fixed rt2500usb. > > > > I checked the patches which were applied to rt2500usb since the release > > of 2.6.26 (July 13th) > > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=histor > >y;f=drivers/net/wireless/rt2x00/rt2500usb.c;h=cd5af656932dda7c0a49f88d7d3b > >244180e56af0;hb=d06193f311102b2c990ec5f66b470ea49ecc73a4 > > > > This is the one which I need (in addition to commit > > d06193f311102b2c990ec5f66b470ea49ecc73a4) to make my rt2570usb working > > with a 2.6.26 kernel. > > > > rt2x00: Fix VGC lower bound initialization > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit > >diff;h=8d8acd46fb7e962ac04baef5a118d431fae6b0f6;hp=e6d3e902088ac5da77b074f > >513e3cb80422ff471 > > > > To me picking that fix seems to be very save. > > > > Can you confirm this? > > Sounds like a good patch, but how about this one as well: > > rt2x00: Corectly initialize rt2500usb MAC > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdi >ff;h=dd87145d2c3a7b1c8b338e1f6e174b3d2a17cd35 > Hmm, this one is from January 08, i.e. it is already in the 2.6.26 kernel and there is no need for this additional patch.or do I miss something? Rianer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: rt2500usb
Ivo, Am Sonntag, 18. Januar 2009 schrieb Ivo van Doorn: > [...] > > No, but I there are dozens of patches between 2.6.26 and 2.6.27 so it is > hard to say which patches would exactly have fixed rt2500usb. I checked the patches which were applied to rt2500usb since the release of 2.6.26 (July 13th) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/net/wireless/rt2x00/rt2500usb.c;h=cd5af656932dda7c0a49f88d7d3b244180e56af0;hb=d06193f311102b2c990ec5f66b470ea49ecc73a4 This is the one which I need (in addition to commit d06193f311102b2c990ec5f66b470ea49ecc73a4) to make my rt2570usb working with a 2.6.26 kernel. rt2x00: Fix VGC lower bound initialization http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8d8acd46fb7e962ac04baef5a118d431fae6b0f6;hp=e6d3e902088ac5da77b074f513e3cb80422ff471 To me picking that fix seems to be very save. Can you confirm this? Many thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
linux-headers-2.6.28-1-686 ininstallable
Hello,
Hello,
I tried to install linux-headers-2.6.28-1-686 from
http://kernel-archive.buildserver.net but failed with
blackbox:~# aptitude install linux-headers-2.6.28-1-686
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages are BROKEN:
linux-headers-2.6.28-1-686
The following NEW packages will be installed:
linux-headers-2.6.28-1-common{a}
0 packages upgraded, 2 newly installed, 0 to remove and 6 not upgraded.
Need to get 4448kB of archives. After unpacking 35.3MB will be used.
The following packages have unmet dependencies:
linux-headers-2.6.28-1-686: Depends: linux-kbuild-2.6.28 which is a virtual
package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
linux-headers-2.6.28-1-686 [Not Installed]
Score is -9881
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
blackbox:~# tail -1 /etc/apt/sources.list
deb http://kernel-archive.buildserver.net/debian-kernel/ trunk main
blackbox:~#
Is that package missing intentionally?
Thanks,
Rainer
--
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdor...@web.de
jabber: rdor...@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: rt2500usb
Am Samstag, 3. Januar 2009 schrieb Ivo van Doorn: > On Friday 02 January 2009, Rainer Dorsch wrote: > > Am Freitag, 2. Januar 2009 schrieb Ivo van Doorn: > > > On Wednesday 31 December 2008, Rainer Dorsch wrote: > > > > Ivo, > > > > > > > > I am testing an > > > > > > > > blackbox:~# lsusb |grep Link > > > > Bus 008 Device 002: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g > > > > rev. B1 [ralink] > > > > blackbox:~# > > > > > > > > on a Debian Lenny system (to be released as Debian 5.0 very soon). > > > > > > > > Lenny comes with an 2.6.26.8 kernel. > > > > > > > > I get lots of timeouts in when I try to connect to the AP. I found > > > > your commit > > > > > > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=co > > > >mmit ;h=d06193f311102b2c990ec5f66b470ea49ecc73a4 > > > > > > > > though I can not (I have not yet enough git expertise) tell, if that > > > > commit went into 2.6.26.8. If not that would probably explain the > > > > problem I see. > > > > > > According tohttp://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27 > > > the patch went into 2.6.27 so that means it probably won't be present > > > in the 2.6.26 kernel series. > > > > Many thanks for the quick reply. With a 2.6.27 kernel (which is > > unfortunately not in the upcoming Debian lenny release) the timeouts went > > away and the stick worked flawless. > > > > From you commit comments, I get the impression that applying the patch to > > a 2.6.26 kernel should be pretty save. Do you think the patch can break > > anything when applied to a 2.6.26 kernel, is the risk of unexpected side > > effects very low? > > No, the patch shoul be very save to be applied to 2.6.26. > Ivo, even with the patch http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit ;h=d06193f311102b2c990ec5f66b470ea49ecc73a4 my rt2570 is still dead on a Debian 2.6.26 kernel, whereas it works flawless on a Debian 2.6.27 kernel on the same machine. Is there anything else you could imagine which should be patched? lsusb output: Bus 008 Device 004: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g rev. B1 [ralink] Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x2001 D-Link Corp. [hex] idProduct 0x3c00 DWL-G122 802.11g rev. B1 [ralink] bcdDevice0.01 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 300mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 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 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted cannot read device status, Operation not permitted (1) syslog for 2.6.26 with patch: Jan 18 18:07:53 blackbox kernel: [ 686.402861] usb 8-2: new high speed USB device using ehci_hcd and address 4 Jan 18 18:07:53 blackbox kernel: [ 686.811833] usb 8-2: configuration #1 chosen from 1 choice Jan 18 18:07:53 blackbox kernel: [ 686.922369] phy2: Selected rate control algorithm 'pid' Jan 18 18:07:53 blackbox kernel: [ 686.922369
Bug#510607: linux-image-2.6.26-1-686: Bug in rt2500usb makes affected WLAN hardware useless
Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Severity: important Tags: patch Hello, the current lenny kernels have a bug in the rt2500usb driver which renders all Ralink 2570 chipsets useless (it does not transmit any data after AP association) and there is a simple very low risk fix in the mainline kernels starting from 2.6.27. Etch supports this chipset, because in the rt2x00-source package in etch did not contain that bug in etch. It is unfortunate that an upgrade from etch to lenny will break the wireless connection of the affected laptops. The maintainer of the driver confirms that applying the patch to the 2.6.26 kernel is very save: http://lists.debian.org/debian-kernel/2009/01/msg00036.html The patch can be downloaded from http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d06193f311102b2c990ec5f66b470ea49ecc73a4 In the case you decide for some reason not to apply the patch, could you document the problem in the release-notes and give a recommendation for the etch users (backports.org, patch kernel themselves, wait for 5.0r1, etc.)? I tested a 2.6.27 kernel from http://kernel-archive.buildserver.net/debian-kernel/ and it works flawless with my hardware (D-Link DWL-G122 HW rev. B1). If you want me to test a deb before you upload to the debian repository, please let me know. Thanks, Rainer -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-12) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Mon Dec 15 18:15:07 UTC 2008 ** Command line: root=UUID=471d84b1-eb6c-47d7-9ad3-1b137828ece9 ro quiet ** Not tainted ** Kernel log: [7.568749] JMB: 100% native mode on irq 16 [7.568749] ide0: BM-DMA at 0xd400-0xd407 [7.568749] ide1: BM-DMA at 0xd408-0xd40f [7.568749] Probing IDE interface ide0... [7.576578] Driver 'sd' needs updating - please use bus_type methods [7.694603] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [7.694606] Uniform CD-ROM driver Revision: 3.20 [7.694667] sr 0:0:0:0: Attached scsi CD-ROM sr0 [7.694737] sd 1:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [7.694750] sd 1:0:0:0: [sda] Write Protect is off [7.694752] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [7.694779] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [7.694810] sd 1:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [7.694819] sd 1:0:0:0: [sda] Write Protect is off [7.694821] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [7.694838] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [7.694841] sda:<5>sr 0:0:0:0: Attached scsi generic sg0 type 5 [7.704676] sd 1:0:0:0: Attached scsi generic sg1 type 0 [7.727262] sda1 sda2 sda3 < sda5 sda6 sda7 > [7.784925] sd 1:0:0:0: [sda] Attached SCSI disk [7.864852] hda: ST3120023A, ATA DISK drive [8.551798] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [8.552161] hda: UDMA/100 mode selected [8.556258] Probing IDE interface ide1... [9.123807] ide0 at 0xdc00-0xdc07,0xd882 on irq 16 [9.295713] ide1 at 0xd800-0xd807,0xd482 on irq 16 [9.307702] hda: max request size: 128KiB [9.307702] hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=65535/16/63 [9.307702] hda: cache flushes supported [9.307702] hda: hda1 [9.520787] PM: Starting manual resume from disk [9.544896] EXT3-fs: INFO: recovery required on readonly filesystem. [9.544896] EXT3-fs: write access will be enabled during recovery. [9.584312] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d800018ea914] [ 13.672820] kjournald starting. Commit interval 5 seconds [ 13.672820] EXT3-fs: recovery complete. [ 13.672820] EXT3-fs: mounted filesystem with ordered data mode. [ 15.580657] udevd version 125 started [ 15.973057] Linux agpgart interface v0.103 [ 15.993830] agpgart: Detected an Intel G35 Chipset. [ 15.997038] agpgart: Detected 7676K stolen memory. [ 16.007299] agpgart: AGP aperture is 256M @ 0xd000 [ 16.052383] input: Power Button (FF) as /class/input/input2 [ 16.069385] ACPI: Power Button (FF) [PWRF] [ 16.069457] input: Power Button (CM) as /class/input/input3 [ 16.100727] ACPI: Power Button (CM) [PWRB] [ 16.166747] hda: UDMA/100 mode selected [ 16.559042] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008) [ 16.559042] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0860) [ 16.559042] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 16.566561] input: PC Speaker as /class/input/input4 [ 16.630443] ACPI: PCI Interrupt :00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 [ 16.655251] ACPI: PCI Interrupt :04:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 16.655270] parport0: PC-style at 0xe800 [PCSPP,TRISTATE,EPP] [ 16.663157] parport0: Printer, Hewlett-Packard HP Laser
Re: rt2500usb
Am Freitag, 2. Januar 2009 schrieb Ivo van Doorn: > On Wednesday 31 December 2008, Rainer Dorsch wrote: > > Ivo, > > > > I am testing an > > > > blackbox:~# lsusb |grep Link > > Bus 008 Device 002: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g rev. > > B1 [ralink] > > blackbox:~# > > > > on a Debian Lenny system (to be released as Debian 5.0 very soon). > > > > Lenny comes with an 2.6.26.8 kernel. > > > > I get lots of timeouts in when I try to connect to the AP. I found your > > commit > > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit > >;h=d06193f311102b2c990ec5f66b470ea49ecc73a4 > > > > though I can not (I have not yet enough git expertise) tell, if that > > commit went into 2.6.26.8. If not that would probably explain the problem > > I see. > > According tohttp://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27 the > patch went into 2.6.27 so that means it probably won't be present in the > 2.6.26 kernel series. > Many thanks for the quick reply. With a 2.6.27 kernel (which is unfortunately not in the upcoming Debian lenny release) the timeouts went away and the stick worked flawless. From you commit comments, I get the impression that applying the patch to a 2.6.26 kernel should be pretty save. Do you think the patch can break anything when applied to a 2.6.26 kernel, is the risk of unexpected side effects very low? Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
rt2500usb
ticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:36 blackbox kernel: [27170.841370] wlan0: authenticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:37 blackbox kernel: [27171.040596] wlan0: authenticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:37 blackbox kernel: [27171.240575] wlan0: authentication with AP 00:18:4d:89:3f:38 timed out Dec 31 19:26:47 blackbox kernel: [27181.899273] wlan0: authentication frame received from 00:18:4d:89:3f:38, but not in authenticate state - ignored Dec 31 19:26:47 blackbox kernel: [27181.901021] wlan0: Initial auth_alg=0 Dec 31 19:26:47 blackbox kernel: [27181.901025] wlan0: authenticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:47 blackbox kernel: [27181.911246] wlan0: Initial auth_alg=0 Dec 31 19:26:47 blackbox kernel: [27181.911250] wlan0: authenticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:47 blackbox kernel: [27182.111323] wlan0: authenticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:48 blackbox kernel: [27182.315865] wlan0: authenticate with AP 00:18:4d:89:3f:38 Dec 31 19:26:48 blackbox kernel: [27182.520735] wlan0: authentication with AP 00:18:4d:89:3f:38 timed out Dec 31 19:26:54 blackbox kernel: [27189.243775] ADDRCONF(NETDEV_UP): wlan0: link is not ready Any hint here is very welcome. Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2.6.26-1-686 break wlan connectivity on Thinkpad T61p
Hello,
I just noticed that the current lenny kernel 2.6.26-1-686 breaks WLAN on my
T61p. It has an
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN
Network Connection (rev 61)
wlan adapter and with 2.6.26-1-686 I get
paddy:~# ifup wlan0
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.
Failed to bring up wlan0.
paddy:~#
whereas when I boot the T61p with 2.6.25-2-686, the wlan works flawless.
I am happy to provide further debug information.
My configuration:
from /etc/network/interfaces
iface wlan0 inet dhcp
pre-up ip link set wlan0 up
pre-up iwconfig wlan0 essid ABC
pre-up iwconfig wlan0 enc 12345678901234567890 open
wpa-conf /etc/wpa_supplicant/leap.conf
wpa-driver wext
and
paddy:~# cat /etc/wpa_supplicant/leap.conf
#eapol_version=1
# next two, YMMV
#ap_scan=0
#fast_reauth=0
#ctrl_interface=/var/run/wpa_supplicant
network={
scan_ssid=1
ssid="IBM"
key_mgmt=WPA-EAP
eap=LEAP
identity="[EMAIL PROTECTED]"
password="[EMAIL PROTECTED]"
}
paddy:~#
Any hints are welcome.
Thanks,
Rainer
--
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
jabber: [EMAIL PROTECTED]
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: openafs in etchnhalf
Russ, Am Dienstag, 17. Juni 2008 schrieb Russ Allbery: > The only relevant part of the openafs package affected is the > openafs-modules-source arch: all package. I'm fairly sure (although would > need to test) that installing a new kernel module built from the lenny > openafs-modules-source package will work fine with an openafs-client > package from the current etch. (Sometimes there are mismatches between > afsd and the kernel, but I don't think any have happened since etch.) So > we could add to etchnhalf a new openafs-modules-source source package that > supersedes the binary package built from the openafs source package, > although I don't know how confused that would make dak (particularly if we > have to do a security update of openafs). This is worthwile double checking. I recently run with a backports kernel, openafs-client from etch and openafs-modules-source from backports and I got many kernel Oops. Switching to the etchnhalf kernel and the openafs modules and openafs-client from backports solved the problem for me. Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
openafs in etchnhalf
Hello, is anybody taking care of the openafs modules which do not compile any more with the etchnhalf kernel? The openafs modules in backports.org do compile though with the etchnhalf kernel. Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fwd: USB Stick install broken for etch?
Hello, I think the kernels in the current etch installer for USB sticks as described in the release notes for etch might be out of sync. I did not get a response on the debian-release list, therefore I forward it to debian-kernel. Rainer -- Weitergeleitete Nachricht -- Subject: USB Stick install broken for etch? Date: Freitag, 16. November 2007 03:18 From: Rainer Dorsch <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hello, I prepared an 1 GB USB stick as installation medium for etch (wanted to use it as rescue "disk"). I followed the instructions on http://www.debian.org/releases/stable/i386/ch04s04.html.en I followed "4.4.2. Copying the files — the flexible way" since I had a 1GB stick and I could use a full CD image this way. I have taken vmlinuz and initrd.img from ftp://ftp.debian.org/debian/dists/etch/main/installer-i386/current/images/hd- media (that was not entirely clear for me from the description on the page though). syslinux.cfg I created myself with the two lines default vmlinuz append initrd=initrd.gz The system booted nicely from the USB stick. First strange issue is that the installer needed two iteration to find the ISO image on the stick. The first iteration failed, then I selected the entry manually from the installation menu. The I got a message *** Load installer components from an ISO Installer No kernel modules were found. This probalby is due to a mismatch between the kernel used by this version of the installer and the kernel available in the archive * Are the kernels in the iso image and the hd-media in fact out of sync? Did I miss something else? The installation log is available at: http://bokomoko.de/~rd/install.tar.bz2 Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 jabber: [EMAIL PROTECTED] GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ ----------- -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/
