Kernel 5.4.0-1012.12 fixes the issue.
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1880607
Title:
Ra
Public bug reported:
After upgrading my Raspberry Pi 4 from Eoan to Focal (arm64), it now
runs awfully slow with dmesg showing loots of these warnings:
[ 3821.602211] [ cut here ]
[ 3821.603018] WARNING: CPU: 2 PID: 25391 at drivers/mmc/host/sdhci.c:1101
sdhci_prepare
This was fixed in #1847163.
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boo
The DTB is also missing from the package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boot on Raspberry Pi 4
Status in linux-raspi2 package in Ubuntu:
Public bug reported:
linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to
missing kernel modules for the new hardware components. It would be nice
if these got included. Also it only boots the kernel when the Pi is
configured for 1GB RAM or less. (Then gets stuck on missing root FS
My problem seems to also be reported in bug #1535008 .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697230
Title:
atkbd serio0: Unknown key pressed (translated set 2, code 0x87 on
i
I see this during bootup with a fresh install of artful on a HP Spectre
x360 13-4104ng notebook. For me it's setkeycodes e057 and code 0xd7,
though.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
For the record: I upgraded to zesty and with kernel 4.10.0-1004
everything works fine, too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi
4.8.0-1035 seems to fix the problem. (Didn't check -1034.) Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since 4.8.0-1025 on Ra
Did anybody check the current kernel from zesty? I'm thinking about
upgrading, but don't want to render the thing unbootable because there's
no working kernel left.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Problem still exists with 4.8.0-1033.37.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
Status in linux packag
Possible duplicate: bug #1667160
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1666421
Title:
kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Status in linux package in Ubuntu:
A workaround seems to be using https://github.com/dz0ny/rt8192cu instead
of the rtlwifi driver.
Bug also reported for the Orange Pi here: https://github.com/orangepi-
xunlong/orangepi_h3_linux/pull/1
Also related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421
** Summary changed:
Same problem with 4.8.0-1032.
** Summary changed:
- Kernel panic with 4.8.0-1025 through -1031 on RasPi 2
+ Kernel panic since 4.8.0-1025 on RasPi 2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Still no worky with kernel 4.8.0-1031.
** Attachment added: "Kernel panic with kernel 4.8.0-1031"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4849159/+files/vlcsnap-2017-03-28-21h33m24s240.png
** Summary changed:
- Kernel panic with 4.8.0-1025, -1026 and -1028 on
I just got the update to kernel 4.8.0-1031.35 ... will test later today.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic with 4.8.0-1025, -1026 and -1028 on Ra
** Also affects: linux-meta-raspi2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-meta-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Summary changed:
- Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
+ Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667160
T
Tested today with the -1028 kernel. The problem IS STILL THERE.
This time, I made a video of the problem:
https://www.youtube.com/watch?v=H_PxSXsgVQU
The error part starts with:
Unable to handle kernel NULL pointer dereference at virtual address 0034
pgd = afcfc000
[0034] *pgd=
** Attachment added: "vlcsnap-2017-03-09-23h36m39s986.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4834940/+files/vlcsnap-2017-03-09-23h36m39s986.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825139/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825140/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825134/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/16
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825135/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825141/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825136/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
NOTE: The apport I sent was created with the WORKING 1024 kernel. IT IS
NOT from the here mentioned -1025 or -1026 kernel as there I can barely
login until the kernel panics.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you ar
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825137/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825138/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Tags added: apport-collected yakkety
** Description changed:
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
there's a RTL2838 DVB-T USB stick attached to monitor airplane positio
Public bug reported:
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
there's a RTL2838 DVB-T USB stick attached to monitor airplane positions
for Flightradar24.
After updateing the kernel from 4.8.0-1024, whi
** Attachment added: "Screenshot of kernel panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4824869/+files/IMG_20170223_0030047.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
I just got access to that Raspberry Pi 3 again. I saw that the expected
fdt address now changed to 0x02008000 in the boot script.
In the config.txt, it was set as:
# set extended DT area
device_tree_address=0x100
device_tree_end=0x8000
So I changed it to:
# set extended DT area
device_tree_add
I don't have access to the RasPi3 at the moment (due to the changing MAC
screwing with DHCP and port forwardings). I'll see what I can do.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/165
Could the missing fdt at 0x0200 be the reason, the RasPi now has a
different MAC address on each and every boot? Because I noticed this
after I got the boot process working again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Also the official flash-kernel_3.0~rc.4ubuntu64_armhf.deb sets the fdt
address to 0x100 whereas 3.0~rc.4ubuntu64.1.1 from yakkety-updates sets
it to 0x0200. So it seems to be a regression in that package.
Downgrading to 3.0~rc.4ubuntu64 and running "sudo flash-kernel" works.
(Don't know why it
Upon further inspection: The flash-kernel from the rpi3 PPA
https://launchpad.net/~ubuntu-raspi2/+archive/ubuntu/ppa-rpi3 is only
published for Xenial and there, the boot script sets the fdt address to
0x100 instead of 0x200. And that works without explicitly loading
the fdt.
So it seems I had
Downgrading the kernel or recently upgraded packages flash-kernel or
linux-firmware-raspi2 didn't work for me. But you can fix this
temporarily by editing /usr/share/flash-kernel/bootscript/bootscr.rpi3
and adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
after the line
It seems the FDT isn't loaded properly. I can boot the system if I load
the FDT manually and do the remaining steps from the boot.scr manually:
fatload mmc 0:1 0x0200 bcm2710-rpi-3-b.dtb
fdt addr 0x0200
fatload mmc 0:1 0x0100 vmlinuz
fatload mmc 0:1 0x0210 initrd.im
The actual problem happens earlier in the process than depicted in the
screenshot above:
Found U-Boot script /boot.scr
reading /boot.scr
412 bytes read in 13 ms (30.3 KiB/s)
## Executing script at 0200
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address co
Same here. The update to 1021 breaks the boot and the only way to
recover is to rename all *.bak files back so it boots the older kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
41 matches
Mail list logo
