Processed: Re: Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13
Processing control commands: > reassign -1 src:linux 5.9.15-1 Bug #979187 [linux-image-5.9.0-5-arm64] 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13 Bug reassigned from package 'linux-image-5.9.0-5-arm64' to 'src:linux'. No longer marked as found in versions linux-signed-arm64/5.9.15+1. Ignoring request to alter fixed versions of bug #979187 to the same values previously set Bug #979187 [src:linux] 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13 Marked as found in versions linux/5.9.15-1. -- 979187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13
Control: reassign -1 src:linux 5.9.15-1 On Lu, 04 ian 21, 11:03:09, Ryutaroh Matsumoto wrote: > Package: llinux-image-5.9.0-5-arm64 > Version: 5.9.15-1 > Severity: normal Hello, There is a typo in the package name, so the bug was assigned to an inexistent package, fixing it with this message. Please use reportbug linux-image-5.9.0-5-arm64 while booted with this kernel and select the option to Follow-Up to this bug (you might want to have the bug number handy), so that reportbug can collect more information about your system. Kind regards, Andrei > Dear Debian kernel maintainers, > > This is a report different from > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694 > > Debian kernel earlier than 5.9.14 booted with the > following Elecom USB MSD. > But Debian kernel 5.9.15 stopped working, while > it boots with another USB MSD from Elecom... > > Best regards, Ryutaroh Matsumoto > V > # lsusb -v > > Bus 002 Device 005: ID 056e:6a13 Elecom Co., Ltd ESD-EMN > Device Descriptor: > bLength18 > bDescriptorType 1 > bcdUSB 3.20 > bDeviceClass0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 9 > idVendor 0x056e Elecom Co., Ltd > idProduct 0x6a13 > bcdDevice 11.00 > iManufacturer 1 ELECOM > iProduct2 ESD-EMN > iSerial 3 20B10164305600A9 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 0x0079 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 504mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 8 Mass Storage > bInterfaceSubClass 6 SCSI > bInterfaceProtocol 80 Bulk-Only > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 8 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 8 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > bAlternateSetting 1 > bNumEndpoints 4 > bInterfaceClass 8 Mass Storage > bInterfaceSubClass 6 SCSI > bInterfaceProtocol 98 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 8 > MaxStreams 4 > Data-out pipe (0x04) > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 8 > MaxStreams 4 > Data-in pipe (0x03) > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 0 > Command pipe (0x01) > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x84 EP 4 IN > bmAtt
Re: Any ETA for Linux 5.10 to land in buster-backports
Salvatore Bonaccorso writes: > Hi Vasudev, > > On Mon, Dec 14, 2020 at 05:32:30PM +0530, Vasudev Kamath wrote: >> >> Hi Kernel Team, >> >> Is there any ETA on Linux 5.10 version to land in buster-backports?. >> >> Not the right time to ask this question as vactions are coming in. Since >> one of our projects depend on Linux 5.10 and we do not want to build the >> package in house just wanted to get a better picture. > > I think we did not reply to that yet. So the next 5.10.y import will > now land in unstable in the next few days, after which we still need > to get that first to testing before it can proceed to > buster-backports. Thank you Salvatore, I saw that its been uploaded to unstable on Dec 31st. Will wait for it to migrate to testing. Cheers, Vasudev
Bug#970634: marked as done (linux-image-5.8.0-1-arm64: Kernel image misaligned at boot on raspi 4B)
Your message dated Mon, 04 Jan 2021 13:57:00 +0900 (JST) with message-id <20210104.135700.18996732646451456.ryuta...@ict.e.titech.ac.jp> and subject line has caused the Debian Bug report #970634, regarding linux-image-5.8.0-1-arm64: Kernel image misaligned at boot on raspi 4B to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 970634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.8.7-1 Severity: minor Dear Maintainer, With a recent SD card image from raspi.debian.net, running on Raspberry Pi 4B 8GB (board revision 1.4), I see Sep 14 15:04:42 rpi4-20200909 kernel: [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader! I have no functional problem, though. Best regards, Ryutaroh Matsumoto -- Package-specific info: ** Version: Linux version 5.8.0-1-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05) ** Command line: video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=tty0 console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes net.ifnames=0 rootwait ** Tainted: C (1024) * staging driver was loaded ** Kernel log: [ 35.811564] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-cinnamon\x2dsettings\x2ddaemon\x2dxsettings-autostart.service, startup phases are not supported. [ 35.831413] systemd-xdg-autostart-generator[1975]: kde-systemd-start-condition not found: No such file or directory [ 35.844863] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-cinnamon\x2dsettings\x2ddaemon\x2dscreensaver\x2dproxy-autostart.service, startup phases are not supported. [ 35.865776] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-cinnamon\x2dsettings\x2ddaemon\x2dcolor-autostart.service, startup phases are not supported. [ 35.885280] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.PrintNotifications-autostart.service, startup phases are not supported. [ 35.910138] systemd-xdg-autostart-generator[1975]: gnome-systemd-autostart-condition not found: No such file or directory [ 35.923850] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Wwan-autostart.service, startup phases are not supported. [ 35.942947] systemd-xdg-autostart-generator[1975]: gnome-systemd-autostart-condition not found: No such file or directory [ 35.957811] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.ScreensaverProxy-autostart.service, startup phases are not supported. [ 35.977740] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported. [ 35.996632] systemd-xdg-autostart-generator[1975]: kde-systemd-start-condition not found: No such file or directory [ 36.010080] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-xfce4\x2dclipman\x2dplugin\x2dautostart-autostart.service, it is hidden. [ 36.032819] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-cinnamon\x2dsettings\x2ddaemon\x2dxrandr-autostart.service, startup phases are not supported. [ 36.052914] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. [ 36.070574] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-cinnamon\x2dsettings\x2ddaemon\x2dmouse-autostart.service, startup phases are not supported. [ 36.090536] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported. [ 36.109234] systemd-xdg-autostart-generator[1975]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported. [ 36.127828] systemd-xdg-autostart-generator[1975]: Not gene
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 979187 linux-image-5.9.0-5-arm64 5.9.15-1 Bug #979187 [llinux-image-5.9.0-5-arm64] 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13 Warning: Unknown package 'llinux-image-5.9.0-5-arm64' Bug reassigned from package 'llinux-image-5.9.0-5-arm64' to 'linux-image-5.9.0-5-arm64'. No longer marked as found in versions 5.9.15-1. Ignoring request to alter fixed versions of bug #979187 to the same values previously set Bug #979187 [linux-image-5.9.0-5-arm64] 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13 Marked as found in versions linux-signed-arm64/5.9.15+1. > End of message, stopping processing here. Please contact me if you need assistance. -- 979187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd
Processing control commands: > reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1 Bug #977694 [src:linux] 5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and usb-msd Bug reassigned from package 'src:linux' to 'linux-image-5.10.0-1-arm64'. No longer marked as found in versions linux/5.10.1-1~exp1. Ignoring request to alter fixed versions of bug #977694 to the same values previously set Bug #977694 [linux-image-5.10.0-1-arm64] 5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and usb-msd Marked as found in versions linux-signed-arm64/5.10.4+1. > retitle -1 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and > usb-msd Bug #977694 [linux-image-5.10.0-1-arm64] 5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and usb-msd Changed Bug title to '5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd' from '5.10 boot hang on Raspberry Pi 4 with ext4 rootfs and usb-msd'. -- 977694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd
Control: reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1 Control: retitle -1 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd I checked the reported symptom with linux-image-5.10.0-1-arm64 5.10.4-1 The symptom remains the same, unlike https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645 I have checked the symptom with two usb msds, one is hdd and the other is ssd. Ryutaroh
Anna wartet auf Ihre Antwort
Google Formulare Danke, dass Sie das Formular Anna wartet auf Ihre Antwort ausgefüllt haben Wir haben folgende Informationen von Ihnen erhalten: Anna wartet auf Ihre Antwort Hallo meine Süße. Ich kenne dich schon seit ein paar Tagen von Insta und möchte dich kennenlernen. Ich bin Kate Ich mache einige Berichte mit meinen Nacktfotos. Ich warte auf dich. Mein Nickname: Kate127 Schatz, finde meine Fotos: http://zombie-master-reborn.com/dating2s E-Mail-Adresse * debian-kernel@lists.debian.org Bild ohne Titel Untitled Question Option 1 Eigenes Google-Formular erstellen
Processed: Re: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard
Processing control commands: > reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1 Bug #977645 [src:linux] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Bug reassigned from package 'src:linux' to 'linux-image-5.10.0-1-arm64'. No longer marked as found in versions linux/5.10.2-1~exp1 and linux/5.10.1-1~exp1. Ignoring request to alter fixed versions of bug #977645 to the same values previously set Bug #977645 [linux-image-5.10.0-1-arm64] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Marked as found in versions linux-signed-arm64/5.10.4+1. > severity -1 important Bug #977645 [linux-image-5.10.0-1-arm64] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Ignoring request to change severity of Bug 977645 to the same value. -- 977645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977645: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard
Control: reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1 Control: severity -1 important I checked the reported symptom with linux-image-5.10.0-1-arm64 5.10.4-1 It booted with completely garbled screen output. disable_fw_kms_setup=1 in config.txt did not help. Removing vc4.ko let the screen output normal. /proc/cmdline looked like dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=tty0 console=ttyS1,115200 root=LABEL=RASPIROOT rw fsck.repair=yes net.ifnames=0 cma=64M rootwait Ryutaroh
Processed (with 2 errors): unarchiving 934105, reassign 932250 to src:xfdesktop4, forcibly merging 934105 932250 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 934105
Bug #934105 {Done: Yves-Alexis Perez } [xfdesktop4]
xfdesktop4: xfdesktop crashes and coredump when upgrading
Unarchived Bug 934105
> reassign 932250 src:xfdesktop4
Bug #932250 [src:linux] linux-image-amd64: random segfaults without taking
something down
Bug reassigned from package 'src:linux' to 'src:xfdesktop4'.
No longer marked as found in versions linux/4.19.37-5.
Ignoring request to alter fixed versions of bug #932250 to the same values
previously set
> forcemerge 934105 932250
Bug #934105 {Done: Yves-Alexis Perez } [xfdesktop4]
xfdesktop4: xfdesktop crashes and coredump when upgrading
Unable to merge bugs because:
package of #932250 is 'src:xfdesktop4' not 'xfdesktop4'
Failed to forcibly merge 934105: Did not alter merged bugs.
> archive 934105
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
932250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932250
934105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
