That line was already commented out (#dtoverlay=vc4-fkms-v3d) in config.txt
so I blacklisted module v3d, works now better with 1013 kernel. Thanks.
On Sat, Nov 23, 2019 at 2:05 PM Hui Wang wrote:
> @Jussi,
>
> I found that issue too. the driver v3d.ko crashed. In the 1013, we
> enabled v3d.ko,
I tried kernel linux-image-5.3.0-1013-raspi2 on Pi4. I'm running mate-
desktop-environment using autologin and with this kernel X-server
started but only showing black screen with mouse cursor, I could log in
with ssh. I rolled back to linux-image-5.3.0-1012-raspi2 for now.
** Attachment added:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686362/+attachment/4868217/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This issue seems to affect only another nvme device:
lspci:
02:00.0 Non-Volatile memory controller: Intel Corporation Device f1a5 (rev 03)
mounted at:
/dev/nvme0n1p1 973844116 277803160 646502624 31% /opt/store
--
You received this bug notification because you are a member of Kernel
Packages,
Full dmesg with error is attached
** Attachment added: "dmesg-full.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686362/+attachment/4868216/+files/dmesg-full.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Hardware is HP Zbook Studio G3 with two nvme devices in m.2 slots.
I was running three Virtualbox clients while two of them hung. Those two
which hung were on same nvme disk while the one which remained in
operation was another nvme disk.
Dmesg error is attached as
I managed to find one more bug report similar to this one. So now there
are at least four bug reports (including this one) here in Launchpad on
this problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
I managed to find one more bug report similar to this one. So now there
are at least four bug reports (including this one) here in Launchpad on
this problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
I managed to find one more bug report similar to this one. So now there
are at least four bug reports (including this one) here in Launchpad on
this problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
Since ArchLinux has currently kernel 3.15.3, I'm marking this fixed in
ArchLinux
** Package changed: linux (Arch Linux) = archlinux
** Changed in: archlinux
Status: New = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Gianluca Anzolin writes on bluetooth-linux mailing list that though his
tty refcount patch series is needed, more work is required to fix the
problem. If I understood his mailing list message correctly, the system
locks up when the device is released even after his patches have been
applied.
Sorry, forgot the links to the commits:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-
next.git/commit/?id=e7abfe40928f4f8c1aa908477c36c13843bd1a57
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cc998ff8811530be521f6b316f37ab7676a07938
--
You received this
Gianluca Azolin's patches were merged to net-next day before yesterday.
And yesterday they were merged to Linus' master branch. So patches will
be in 3.12 rc1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, forgot the links to the commits:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-
next.git/commit/?id=e7abfe40928f4f8c1aa908477c36c13843bd1a57
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cc998ff8811530be521f6b316f37ab7676a07938
--
You received this
Gianluca Azolin's patches were merged to net-next day before yesterday.
And yesterday they were merged to Linus' master branch. So patches will
be in 3.12 rc1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Gianluca Azolin's patches were merged to net-next day before yesterday.
And yesterday they were merged to Linus' master branch. So patches will
be in 3.12 rc1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, forgot the links to the commits:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-
next.git/commit/?id=e7abfe40928f4f8c1aa908477c36c13843bd1a57
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cc998ff8811530be521f6b316f37ab7676a07938
--
You received this
Gianluca Anzolin writes on bluetooth-linux mailing list that though his
tty refcount patch series is needed, more work is required to fix the
problem. If I understood his mailing list message correctly, the system
locks up when the device is released even after his patches have been
applied.
Gianluca Anzolin writes on bluetooth-linux mailing list that though his
tty refcount patch series is needed, more work is required to fix the
problem. If I understood his mailing list message correctly, the system
locks up when the device is released even after his patches have been
applied.
There are at least three similar bug reports on this problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189998
--
You received this bug notification because
ekin wrote:
This bug seems similar to bug 1165433. By the way, the patch referred
to in comment #4 is still being reviewed and revised it seems. See
for instance http://marc.info/?a=12747661669r=1w=2
The fix being discussed on Bluetooth mailing list has already been
merged to
The patch series is apparently too extensive to consider for -stable
[1]. So another solution is required for stable kernels. Gianluca's fix
should eventually end up in mainline though (3.12 hopefully).
[1] http://marc.info/?l=linux-bluetoothm=137762583515880w=2
--
You received this bug
Actually, there are at least three bug reports on this same problem on
launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189998
--
You received this bug
Gianluca Anzolin's patches have now been merged to bluetooth-next.
Eventually they should find their way to mainline and stable kernels.
http://marc.info/?l=linux-bluetoothm=137699050920055w=2
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-
Gianluca Anzolin's patches that should fix this problem have now been
merged to bluetooth-next. Eventually they should find their way to
mainline and stable kernels.
http://marc.info/?l=linux-bluetoothm=137699050920055w=2
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-
Gianluca Anzolin's patches that should fix this problem have now been
merged to bluetooth-next. Eventually they should find their way to
mainline and stable kernels.
http://marc.info/?l=linux-bluetoothm=137699050920055w=2
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-
*** This bug is a duplicate of bug 1144322 ***
https://bugs.launchpad.net/bugs/1144322
** This bug has been marked a duplicate of bug 1144322
[Toshiba Satellite A80] Kernel 3.8.x Panic when disconnecting from network
manager via ppp0
--
You received this bug notification because you are
** Bug watch added: Gentoo Bugzilla #474432
https://bugs.gentoo.org/show_bug.cgi?id=474432
** Changed in: gentoo
Importance: Undecided = Unknown
** Changed in: gentoo
Status: New = Unknown
** Changed in: gentoo
Remote watch: None = Gentoo Bugzilla #474432
--
You received this
28 matches
Mail list logo
