4.15.0-45 does not fix my problem. The boot continues to hang when
gnome tries to start. I cannot "Ctrl-Alt-F1 (or any F?)", but I can ssh
from another computer to this affected computer. Log files don't show
anything remarkable to me, but I wouldn't know what was remarkable in
all of the verbia
Stephane Guilard:
I think that comment was for me -- if so, thanks:
I was able to get 4.15.0-43 installed (another way). That didn't help.
It seems something else has happened that they haven't found. I have
another computer "Samsung NP300E5C Notebook" that has the "43" and "45"
kernels install
Public bug reported:
This problem was introduced in the "4.15.0-44" or "4.15.0-45" kernel in
late January 2019. The same problem happens in 32 bit and 64 bit
systems -- both installed before January 2019 and AFTER the problem was
introduced (that is, complete new installations AFTER). I have an
I tried to do the "apport-collect 1814604" above, but I never got an
indication the browser was trying to connect to the https server. So, I
am changing status to confirmed, as shown above.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificatio
fixed already in the latest 16.04, im using lenovo e550.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1433906
Title:
Acer, Inc ID 5986:055a is useless after 14.04.2 installed
I just tested and have the same issue. I tried the modprobe options
idea with no change.
Ubuntu 16.10 64-bit.
4.8.0-41-generic #44-Ubuntu SMP
My next approach will be to try the firmware blob from Intel's website
to see if pushing a newer one in helps.
--
You received this bug notification be
dmesg | grep firmware
337586.320046] iwlwifi :03:00.0: loaded firmware version 9.221.4.1
build 25532 op_mode iwldvm
--
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/1471794
Title:
Wif
Went to
http://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-
networking/05511.html
and tried version 9.176 with no luck, same slow speeds.
loaded firmware version 9.176.4.1 build 15835 op_mode iwldvm
sudo mv -i ~rbeede/Downloads/iwlwifi-6000-4.ucode /lib/firmware
sudo mo
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/log/iwlwifi-6000-4.ucode
Last activity in master branch was 2011-06-03 so not much hope.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Firmware changes did not help, but the following doubled my speed from
20mbps to 40mbps (still 50% lower than what I got in Windows 7):
vi /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
Change line to
wifi.powersave = 2
echo "options iwlwifi 11n_disable=8" | sudo tee /etc/modprobe.d/
** 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/1424181
Title:
Huawei E3372 USB modem not always detected
Status in l
I can also confirm that this issue affects a Dell XPS 13 (9343) running
16.04 with the kernel the 4.4.0-21. This install was done through an
upgrade from an existing Ubuntu installation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmw
Yes, the bug is still present in 14.04 on kernel 3.13.0-29-generic.
** 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/1021
This is still an issue as of 2014-06-20 on 3.13.0-29-generic in Ubuntu
14.04, however I have now upgraded to a single 4K monitor and a Haswell
CPU, so I won't be able to test any further possible fixes for this
issue.
One thing of note though, is that when X came up on 3.13.0-29, the
second monito
I have retested using the latest stable kernel and can confirm that this
error still occurs.
Linux okdev1383 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
root@okdev1383:~# sudo md5deep -r -c -z /dev/
root@okdev1383:~# cat /etc/os-release
NAME="U
Playing with xrandr some more, I have gotten "xrandr --output HDMI1
--crtc 0 --output HDMI3 --crtc 2 --right-of HDMI1" to work. I can use
both screens at full resolution, with this command. I don't know if it
will stick after a reboot, but I will comment here as soon as I do
reboot.
--
You receiv
Now running 3.13.0-1 on Ubuntu, and second display still not working,
and no link train errors in dmesg.
Second screen remains black. I can use both screens only when I set them
to an extremely low resolution of 1280x800 each. Any higher resolution,
and the second screen remains black.
If I run "
After getting the second monitor working properly with xrandr faffing,
the settings do not stick after a reboot, unfortunately.
How can I get it to work correctly by default, every time?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Created attachment 93418
dmesg|grep drm output for drm.debug=0xe on 2014-02-04
Here is a drm.debug log with the 3.13.0-6-generic kernel in Ubuntu
Trusty. It includes all the drm output from the boot command up to the
second display failure when lightdm comes up, another failure for the
display to
This issue still exists on 14.04.
** Changed in: gnome-bluetooth (Ubuntu)
Importance: Undecided => High
** Tags removed: lucid
** Tags added: trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchp
Uname: Linux 3.16.0-6-generic x86_64
NonfreeKernelModules: fglrx
Annotation: This occured during a previous hibernate and prevented it from
resuming properly.
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rodney22706 F
If I switch to Gallium driver, the problem is gone.
On 08/08/2014 05:36 AM, Christopher M. Penalver wrote:
> Rodney Navratil, thank you for reporting this and helping make Ubuntu
> better. If you switch to the open source graphics driver, is this still
> reproducible?
>
> ** Ch
, "Christopher M. Penalver"
wrote:
>Rodney Navratil, just to clarify, how did you install the Gallium
>driver
>precisely?
>
>As well, did you try the drivers that come with Ubuntu by default?
>
>--
>You received this bug notification because you are subs
(In reply to Rodrigo Vivi from comment #34)
> Since the error reported cannot be reproduced anymore by reporter of reopen
> let's close this as invalid.
> Anyone able to reproduce again it feel free to re-reopen. But remind to test
> on latest drm-intel-nightly.
Well, it's still an issue. I just n
The BIOS update rev 0061 lists no changes in its release notes file,
that would be potentially related to this 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/1021924
Title:
8086:0
sudo dpkg -i linux-
image-3.11.0-031100rc3-generic_3.11.0-031100rc3.201307290035_amd64.deb
uname -a
Linux okdev1383 3.11.0-031100rc3-generic #201307290035 SMP Mon Jul 29 04:36:40
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Aug 2 14:57:26 okdev1383 kernel: [ 68.538338] [ cut here
]-
Tested with issue on
Vmware workstation 9 on windows 7 64-bit host. No vmware tools.
Vmware esxi 5.1 with no vmware tools.
Physical hardware Biostar a68i-350 deluxe r2.0 motherboard, 8gb ram.
All ubuntu 13.04 lts 64-bit server edition.
Works fine on all 3 when using ubuntu 12.04 64-bit serv
Last worked in Ubuntu 12.04.02 LTS 64-bit Server Edition
Kernel 3.5.0-34-generic
Broken in Ubuntu 12.04.02 LTS 64-bit Server Edition
Kernel 3.5.0-37-generic
Broken in Ubuntu 12.10 64-bit Server Edition.
Kernel 3.5.0-37-generic
Broken in Ubuntu 13.04 64-bit Server Edition.
Kernel 3.8.0-19-gener
Ubuntu 12.04:
No kernel bug crash on:
3.5.0-36-generic
Kernel crash occurs with:
linux-image-3.5.0-37-generic
--
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/1206980
Title
The BIOS update did not help. Here is the new information:
MKQ7710H.86A.0060.2013.0618.1012
06/18/2013
I am now also running on Ubuntu Saucy 13.10, with kernel
3.10.0-6-generic.
The second display is entirely red, and the fdi link train failures are
still occurring:
[ 57.936050] [drm:ivb_manu
Is there a specific version I should test? I see 3.11-rc5 mentioned, but
3.11.0-1-generic was installed as an update when I did a dist-upgrade
earlier today, and the bug is still present there. Given that, I would
also expect the bug to be present in upstream 3.11-rc5.
Also, this is not trivial to
I've also removed the Quantal and Raring tasks, as they are non-LTS
releases, and I don't see the chance of this being fixed in them because
of that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
I have upgraded to a new version of Ubuntu now, which is using 3.10.0-6,
as well as the latest version of the BIOS for this board, from Intel.
The second screen is completely red, and link train errors are
occurring:
: dmesg|grep drm
[7.281683] [drm] Initialized drm 1.1.0 20060810
[7.33615
I am encountering this issue as well. Attached is a screenshot.
My setup:
Ubuntu 13.04 LTS 64-bit Server Edition
VMWare Workstation 9 on a Windows 7 64-bit Enterprise Edition host
No floppy drive in the VM settings, but I didn't modify the default BIOS either.
One good tool to quickly reproduce
kern.log from crash with 3.8.0-27-generic
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+attachment/3754957/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Pulling the latest updates to 3.8.0-27 results in the same crash.
--
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/1203933
Title:
Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13
My system seems to crash whether doing the md5deep / probe or when doing
a large amount of I/O on other mount points.
--
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/1203933
Title:
Kernel
I am able to reproduce this issue 100% of the time. A quick way to
trigger the kernel panic is
sudo md5deep -r -c -z /dev
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Reproducable 100% of the time.
sudo md5deep -r -c -z /dev/
Other intensive I/O commands such as fsck /dev/Some3TBDrive also cause the
panic.
/var/log/kern.log shows stack trace.
Ubuntu 13.04 64-bit (amd64) Server Edition
Tested running under VMWare ESXi 5, VMWare Workstat
sudo dpkg -i linux-
image-3.9.0-030900-generic_3.9.0-030900.201304291257_amd64.deb
[rbeede@ubuntu13:/home/rbeede] $ uname -a
Linux ubuntu13 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
sudo md5deep -r -c -z /dev/
Same kernel panic:
Aug 1
Christopher, no, making the assumption that something may be "fixed" by
a BIOS update, which contains no documentation relevant to the issue, is
exactly that; an assumption. There is no evidence that suggests a BIOS
update would fix something that is not documented in the release notes
for the upda
(In reply to comment #26)
> Rodney, please post the full dmesg from the failure case. Since plenty of
> time has passed, please use a later kernel. Thanks.
I've just upgraded the machine to Ubuntu Trusty development series,
which has kernel 3.12.0-7.15. The second display is still
This is still an issue, even on the 13.10 RC kernel:
$: dmesg|grep link_train && uname -r
[9.766419] [drm:ivb_manual_fdi_link_train] *ERROR* FDI train 1 fail!
[9.768562] [drm:ivb_manual_fdi_link_train] *ERROR* FDI train 2 fail!
[ 118.902507] [drm:ivb_manual_fdi_link_train] *ERROR* FDI tra
I've removed the i386 tag as well as the tag for requesting test on an
older kernel than is currently available. I was running 12.04 32-bit
when originally filing this bug, but have long since upgraded to a
64-bit only system, after installing a new hard drive.
** Tags removed: i386 kernel-reques
Christopher, must I really waste our time by updating the BIOS every
time a fix for the Q77 chip set comes out? It's a pain to do the BIOS
update, and it's a pain to test this bug specifically, because it
requires several reboots and shifting cables behind a rack.
If you read the Release Notes for
Christopher, while I appreciate your passion for triaging bugs, and
wishing to strictly adhere to process or protocol, a BIOS update that
will not fix anything is unnecessary, and a waste of time. One can
easily see by looking at the release notes of the BIOS update that it
will not affect this iss
46 matches
Mail list logo
