pect the problem not to happen.
My environment is:
[code]
System:Host: flo-P55M-UD2 Kernel: 5.4.0-62-generic x86_64 bits: 64
compiler: gcc v: 7.5.0
Desktop: MATE 1.22.2 wm: marco dm: LightDM Distro: Linux Mint 19.3
Tricia
base: Ubuntu 18.04 bionic
Machin
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System:Host:
e."
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
Syste
e."
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System:
ll mode."
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
e."
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
Syste
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System:Host:
kernel as well and experienced the same I thought it
might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System: Host: flo-P55M-
:
[code]
System:Host: flo-P55M-UD2 Kernel: 5.4.0-62-generic x86_64 bits: 64
compiler: gcc v: 7.5.0
Desktop: MATE 1.22.2 wm: marco dm: LightDM Distro: Linux Mint 19.3
Tricia
base: Ubuntu 18.04 bionic
Machine: Type: Desktop Mobo: Gigabyte model: P55M-UD2 v: x.x s
e."
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
Syste
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System:Host:
mode."
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
As I was using this kernel as well and experienced the same I thought
it might be a good idea to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System:Host:
to upgrade the kernel to 5.4.0-62.
I can state the problem is still there even in 5.4.0-62.
What do I expect: I expect the problem not to happen.
My environment is:
[code]
System: Host: flo-P55M-UD2 Kernel: 5.4.0-62-generic x86_64 bits: 64
compiler: gcc v: 7.5.0
Desktop: MATE
any news on this?
--
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/1504909
Title:
blk_update_request: I/O error when accessing a disk that is spun down
Status in linux package in Ubuntu:
Similar issue here - i own a RFXTRX device which internally uses a FTDI
USB/serial converter. After update to kernel 3.13.0-65, the software
which uses the RFXTRX device ( FHEM ) stops working and hangs while
reading from it.
--
You received this bug notification because you are a member of Kerne
Similar issue here - i own a RFXTRX device which internally uses a FTDI
USB/serial converter. After update to kernel 3.13.0-65, the software
which uses the RFXTRX device ( FHEM ) stops working and hangs while
reading from it.
--
You received this bug notification because you are a member of Kerne
17 matches
Mail list logo
