For the record, I was running into the same issue as Max with my network
adapter.
harry@harry-Laptop:~$ lspci | grep Network
01:00.0 Network controller: MEDIATEK Corp. Device 0616
I don't have a snapshot from then, but updating my firmware from the
proposed repository didn't change the build
** Tags added: kernel-net
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2025311
Title:
packet storm as nics in STP enabled netns bridges lack BPDU maddr
01:80:c2:00:00:00
Public bug reported:
Bridges with STP enabled, only if in the non-default namespace,
connecting the nic as a port to the bridge will not add the STP
multicast address to the port nics, causing them to fail in all
important BPDU topology updates. This leads to packet storms,
effectively locking
Public bug reported:
[ 46.222634] [ cut here ]
[ 46.222636] WARNING: CPU: 4 PID: 1883 at drivers/gpu/drm/ttm/ttm_bo.c:409
ttm_bo_release+0x323/0x350 [ttm]
[ 46.222647] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE
nf_nat nf_conntrack_netlink
Public bug reported:
Kernel bugs on boot, latest jammy, edac/i5000 related?
[ +0.214131] systemd-journald[502]: Received client request to flush runtime
journal.
[ +2.520374]
[ +0.008680] UBSAN:
Public bug reported:
Using the latest generic 'jammy' kernel, in a mate-desktop VM with no
GUI/user activity, mostly used as a router/gateway, after at least 12
hours of typical operations, we see:
Dec 20 01:11:53 gate2.1.quietfountain.com systemd-networkd[331]: enp0s3: Lost
carrier
Dec 20
https://github.com/juju/juju/pull/14028
** Changed in: juju
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1944080
Title:
[fan-network]
I also ran into this on upgrade to 22.04 - and the workaround worked for
me too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1967842
Title:
Ubuntu 22.04 Beta: linux-firmware
It looks to be 'an interesting mystery' we're chasing. This system is
in production, so the results below are with the whole 'snooping engine'
off as without it the whole thing dies. As such, I don't think the
contents of the fdb and mdb tables mean much. The setups below are
unchanged, they
P.S. The reason this is a security issue is-- there is now an address on
the host that the guest also 'knows' and it sits on the bridge giving
access to all the other guests on the bridge. Most admins will not
'just know' they need rules to block fe80 traffic generated by host
interfaces--
I need to repeat: in sysctl.d put this line in a file, then reboot,
then your test setup will show the failure:
net.ipv6.conf.all.autoconf = 0
Otherwise, in your test setup the tables are populated, then you delete
the addresses, but the L3/4 code engaged by even a little time with the
fe80:...
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1959702
Title:
Regression: ip6 ndp broken, host bridge doesn't add
Public bug reported:
After a normal day's operations, the monitors switch off after an hour
or so. Every morning since Impish, upon waking up and unlocking the
system: 2 of the monitors wake, the rest remain in sleep mode. The
only recourse is to do a graceful poweroff and cold boot. There is
Yup, those failures were to do with an old radeon chipset on an ancient
server.
On 2/1/22 17:33, Seth Arnold wrote:
> Sounds good, thanks:
>
> [0.00] Linux version 5.11.0-49-generic (buildd@lcy02-amd64-054)
> (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu)
>
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p
04F3:3186 Touchpad as
/devices/platform/AMDI0010:03/i2c-0/i2c-
MSFT0001:00/0018:04F3:3186.0001/input/input7
This as you may gather stops my trackpad from working and they have suggested I
visit here and ask for
any help!
All the best - Harry
--
You received this bug notification because you
it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/sn
device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/sn
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2'
usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2'
device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/sn
it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/de
it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/sn
ause it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/control
it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/sn
it's an usb-device ?
If you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/sn
f you need more information, please tell me which,
i will provide them.
best regards Harry
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/
php?f=64=21380
My opinion is that somewhere in development of kernel alsa has lost it's
capability to configure more than 2 capture-channels.
I wonder why nobody else is complaining, maybe because it's an usb-device ?
If you need more information, please tell me which,
i will provide
Sir no resolution legion y545 not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1861532
Title:
brightness control not working [Lenovo Legion Y540/Y545]
ything
+ except a hard press of the power button. The attached log output was
+ recorded at the time of the attempted sleep, indicating a kernel oops.
+ There are a lot of Nvidia references, so not sure if it's the Nvidia
+ driver, kernel or both. This is Ubunty 20.04.1 with the latest kernel
+ 5(Ub
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405013/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405008/+files/Lsusb.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/1893152
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405011/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405007/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405010/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405015/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405017/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405005/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405016/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405003/+files/CRDA.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/1893152
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405012/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405004/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405018/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405006/+files/Lspci.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/1893152
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405009/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1893152/+attachment/5405014/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected focal
** Description changed:
- Random freeze on laptop machine, when trying to sleep (normal power-
- save/timed sleep mechanism). The machine would not respond to anything
- except a hard press of the power button. The attached log output
Public bug reported:
Random freeze on laptop machine, when trying to sleep (normal power-
save/timed sleep mechanism). The machine would not respond to anything
except a hard press of the power button. The attached log output was
recorded at the time of the attempted sleep, indicating a kernel
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+attachment/5405000/+files/lspci-vnvn.log
** Description changed:
Random freeze on laptop machine, when trying to sleep (normal power-
save/timed sleep mechanism). The machine would not
** Description changed:
Random freeze on laptop machine, when trying to sleep (normal power-
save/timed sleep mechanism). The machine would not respond to anything
- except a hard press of the power button. The attached output was
- recorded in the logs at the time of the attempted sleep,
** Attachment added: "kernel oops log output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893152/+attachment/5404999/+files/kerneloops.log
** Description changed:
Random freeze on laptop machine, when trying to sleep (normal power-
save/timed sleep mechanism). The machine
Public bug reported:
I bought some "posh" eggs, but when I ate them they were unhygienic.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic
This is plaguing my system as well. Doing updates gives the errors. Not
sure I want to perform a get:clone due to the software I have loaded and
that it seems to be an issue with the new kernel.
update-initramfs: Generating /boot/initrd.img-5.4.0-37-generic
W: Possible missing firmware
It crashed again without insert or pull out any device.
** Attachment added: "dmesg02.log"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1874241/+attachment/5357938/+files/dmesg02.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1874241/+attachment/5357920/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
apport information
** Tags added: apport-collected focal
** Description changed:
The intel iwlwifi firmware will crash when you insert a device into the
thunderbolt3 port, and this will be trigger probabilistically.
wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354
Firmware
Public bug reported:
The intel iwlwifi firmware will crash when you insert a device into the
thunderbolt3 port, and this will be trigger probabilistically.
wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354
Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
Linux-firmware
Urgent cut in!!
Testing today on a daily build of Kubuntu 20.04 I observed the same issue.
Linux version 5.4.0-14-generic, linux-firmware/focal,now 1.186.
I did a CRC check on the oland_rlc.bin file in linux-firmware 1.186 and
it was the same as from the one in linux-firmware/bionic-updates
There are two separate issues presented here now and it has become
confusing to the person it was assigned to. The original issue was the
latest firmware update: linux-firmware 1.173.15 with the current HWE
5.3.0-40-generic kernel causing issues with the AMD Oland graphics.
It was apparent on
I see the same thing related to slowness in a old-style parallel port device
passed to a VM. Shortly after there's traffic related to the parallel port the
task will hang forever, eventually locking up the VM entirely.
This has happened on two SuperMicro servers, the problem did not exist in
This is against disco, crashed not an hour ago. Detail:
Jun 26 12:17:03 ceo1homenx btrbk: finished success - - - -
Jun 26 12:18:21 ceo1homenx systemd[1]: Starting Cleanup of Temporary
Directories...
Jun 26 12:18:21 ceo1homenx systemd-tmpfiles[11589]:
[/usr/lib/tmpfiles.d/spice-vdagentd.conf:2]
The above:
uname -a
Linux ceo1homenx 5.0.0-19-generic #20-Ubuntu SMP Wed Jun 19 17:04:04 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
--
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/1797296
Apparently this is happening across the distro world. Thought the link
below is fedora, notice it includes debug detail from ubuntu, debian,
etc.
Seems nouveau is just simply random broken when used with more than a
few windows for more than a few hours without much of a clue or interest
as to
Jan 7 02:41:41 ceo1homenx kernel: [40698.439354] WARNING: CPU: 6 PID: 24218 at
drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau]
Jan 7 02:41:41 ceo1homenx kernel: [40698.439355] Modules linked in: vfio_pci
vfio_virqfd vfio_iommu_type1 vfio rfcomm ebtable_filter ebtables
an 7 06:39:01 ceo1homenx CRON[29352]: (root) CMD ( [ -x
/usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then
/usr/lib/php/sessionclean; fi)
Jan 7 06:47:12 ceo1homenx kernel: [55429.029596] nouveau :01:00.0: fifo:
SCHED_ERROR 0a [CTXSW_TIMEOUT]
Jan 7 06:47:12 ceo1homenx
Thanks, mind posting the same for the non-working kernel? I'm curious if the
problem is
1) we don't detect the display
2) we don't enable the display
3) we enable the display but wrong
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Is it HDMI from the board to HDMI on the monitor? I'd like to rule out
any use of an adapter or HDMI-to-DVI cable.
What monitor is this?
Is the monitor detected?
What do you see in the 'status', 'enabled', 'dpms', and 'modes' files in
/sys/class/drm/card0-HDMI-A-1/ ?
--
You received this bug
What display connectors are being used?
If this is about displays with VGA or LVDS connections this is the same
bug as upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=105880
mentioned above.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Replied on the ticket.
If this is about non-functioning LVDS or VGA I'm aware of it and trying
to find time to find a good solution.
Harry
On 2018-04-30 11:14 AM, Joseph Salisbury wrote:
> Hi Harry,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect,
My hardware by the way is an Asus Zenbook pro laptop with the Intel dual
band wireless-AC 7260 adapter and nvidia GTX 960M
--
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/1724317
Title:
Been lurking on this bug and hoped it would be fixed with the new
4.13.0-17 kernel update, which I just installed after wrestling with the
unreliable apt-get mechanisms for over an hour by the way (but that's a
topic for another bug) but no such luck. This buggy beast is still
hanging on shutdown
Public bug reported:
After start up the system error report pops up.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
ApportVersion:
I found the patch that causes the keyboard to malfunction !:
https://www.spinics.net/lists/linux-gpio/msg18340.html
reverse patching this patch 'solves' the issue (specifically reverse
patching pinctrl-baytrail, reverse patching pinctrl-intel is not really
necessary)
--
You received this bug
This bug is solved with the version 1.1.3-2.
** Changed in: alsa-lib (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1658606
Title:
** Summary changed:
- Alsa-lib 1.1.3-1 puls in python2.7 (Zepus dev)
+ Alsa-lib 1.1.3-1 puls in python2.7 (Zesty dev)
** Description changed:
- The newest alsa-lib (package libasound2) in Zesty Zepus (v. 1.1.3-1) puls in
python2.7.
+ The newest alsa-lib (package libasound2) in Zesty Zapus (v.
Public bug reported:
The newest alsa-lib (package libasound2) in Zesty Zepus (v. 1.1.3-1) puls in
python2.7.
Package libasound2 depends on libpython2.7 (>= 2.7).
Earlier version did not depend on python2.7, so this is a new feature.
However, the aim was to get rid of puthon2.7 (transition to
adding i2c_hid.debug=1 as a boot parameter gives the following output:
[4.572059] i2c_hid i2c-PDEC3393:00: Fetching the HID descriptor
[4.572065] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f1 00
[4.575576] i2c_hid i2c-PDEC3393:00: HID Descriptor: 1e 00 00 01 b4 00 f2 00
f3 00 0e
and with dyndbg==pmf enabled while loading the module:
<7>[ 857.237099] i2c_hid:i2c_hid_init_irq: i2c_hid i2c-PDEC3393:00: Requesting
IRQ: 195
<3>[ 868.461393] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[ 880.840464] i2c_hid i2c-PDEC3393:00: failed to reset device.
<4>[ 881.884430]
the OOB write fix was submitted in march 2016, so I doubt that has
anything to do with it.
I tried debugging the module i2c_hid (which I'm not accustomed to) and
dug op the following while loading the module and reading /proc/kmsg
simultaneously (on kernel 4.10-rc1):
<3>[ 299.249790] i2c_hid
Same issue as before. As with all of the 4.1 kernels, the screen freezes
before going into Plymouth. Only the cursor is visible and I have to
manually restart the computer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just for kicks, I went ahead and tried booting into the latest 16.10
beta. As expected, I get the black screen on boot.
--
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/1609242
Title:
@jsalisbury If I'm not mistaken, I think we have one more kernel to
test. Would it be possible to test the last one 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/1609242
Title:
Same as before with this one:
>This one was broken but not in the same way. With this >one, right
after the PC booted it gets stuck in a >console (only a blinking cursor
in the upper left corner) >right before plymouth is supposed to load.
>The keyboard and everything else is unresponsive. I had
Same as before with this one:
>This one was broken but not in the same way. With this >one, right
after the PC booted it gets stuck in a console >(only a blinking cursor
in the upper left corner) right >before plymouth is supposed to load.
>The keyboard and everything else is unresponsive. I had
@jsalisbury the "all" headers are missing. Should I install without?
** Attachment added: "Selection_019.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+attachment/4741153/+files/Selection_019.png
--
You received this bug notification because you are a member of Kernel
@jsalisbury How's it looking with this bug? Are we any closer to find
the root cause? Please let me know how I can help further. I'm ready to
test whatever you throw at me :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Same as before with this one:
>This one was broken but not in the same way. With this one, right
>after the PC booted it gets stuck in a console (only a blinking >cursor
in the upper left corner) right before plymouth is supposed to >load.
>The keyboard and everything else is unresponsive. I had
Hi All,
Until this issue is resolved, is there anything I could do to protect
myself (esp., since I'm not getting any security updates using the
mainline 4.2.8 kernel)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Same as before with this one:
>This one was broken but not in the same way. With this one, right
>after the PC booted it gets stuck in a console (only a blinking >cursor
in the upper left corner) right before plymouth is supposed to >load.
>The keyboard and everything else is unresponsive. I had
Same as before with this one:
>This one was broken but not in the same way. With this one, right
>after the PC booted it gets stuck in a console (only a blinking >cursor
in the upper left corner) right before plymouth is supposed to >load.
>The keyboard and everything else is unresponsive. I had
Same as before with this one:
>This one was broken but not in the same way. With this one, right >after the
>PC booted it gets stuck in a console (only a blinking >cursor in the upper
>left corner) right before plymouth is supposed to >load.
>The keyboard and everything else is unresponsive.
I went ahead and installed linux-
image-4.1.0-040100rc6-generic_4.1.0-040100rc6.201608291255_amd64
As with the last kernel:
>This one was broken but not in the same way. With this one, right >after the
>PC booted it gets stuck in a console (only a blinking >cursor in the upper
>left corner)
Joseph,
It appears that there are two kernels in the list. Which one should I
use? Both?
For example:
linux-headers-4.1.0-040100rc6_4.1.0-040100rc6.201608291255_all.deb
linux-headers-4.1.0-040100rc6_4.1.0-040100rc6.201608231554_all.deb
--
You received this bug notification because you are a
This one was broken but not in the same way. With this one, right after
the PC booted it gets stuck in a console (only a blinking cursor in the
upper left corner) right before plymouth is supposed to load.
The keyboard and everything else is unresponsive. I had to physically
restart the
this one is broken. Same blackscreen.
--
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/1609242
Title:
Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Status in linux package in
this one works. It boots without blackscreen.
--
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/1609242
Title:
Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Status in linux
OK. That one is broken. Does that mean it's the culprit?
--
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/1609242
Title:
Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Status in
@Joseph - I only tested the generic kernel. Did you want me to test the
low latency kernel as well?
--
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/1609242
Title:
Kernels 4.3-4.8 result
No problem with the test kernel. It boots without issue.
--
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/1609242
Title:
Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Status in
1 - 100 of 133 matches
Mail list logo
