This bug affected me, upgrading from 6.8.0-39 to 6.8.0-40 fixed it! Many
thanks.
--
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/2039368
Title:
UBSAN: array-index-out-of-bounds in
/buil
I scrapped the two 6715s I had and can no longer test them.
/ Carl
Den 20 dec 2016 18:25 skrev "Christopher M. Penalver" <
christopher.m.penal...@gmail.com>:
> Carl Englund, please see
> https://community.ubuntu.com/contribute/support/irc/ .
>
> In addition to the b
I could use some help, but nobody answered. Is there some IRC channel I
should turn to instead?
https://ubuntuforums.org/showthread.php?t=2338146
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Tested 4.8-rc8, problem remains
--
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/1611536
Title:
Fan on full speed without noapic or nolapic on HP 6715s
Status in linux package in Ubuntu:
I made a mistake, 4.4.0-34 does not boot with normal fan speed without
noapic. Instead, it seems the change/break appears between 4.2.3 and
4.2.4. I will try to bisect there. Here is the updated list:
4.1.0: fan ok, 32-bit FADT
4.1.1: fan ok, 32-bit FADT
4.1.2: fan ok, 32-bit FADT
4.1.3: fan ok, 3
I have done some testing of different kernels from the mainline
repository, omitting the noapic parameter to see if they start and how
the fan behaves. This is the result. Kernels using 64-bit FADT cause the
machine to malfunction, as per:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159015
Tested 4.8.0 rc2, problem persists.
** Attachment added: "480rc2.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/+attachment/4725156/+files/480rc2.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You rec
Reported separate bug for noapic nolapic here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536
--
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/1590154
Title:
System slow unle
Public bug reported:
Without adding noapic or nolapic to boot parameters the fan will run on
full speed, the system is sluggish (can almost see windows redrawing on
screen). On some kernel versions tested, rebooting also fails.
The parameter(s) were not required in Trusty. I also tested some
Main
I can confirm 4.8.0 rc1 works great with noapic/nolapic and
"acpi_force_32bit_fadt_addr". Without the last parameter it uses 64-bit
FADT adress and the problem occurs.
Interestingly, mainline kernels 4.3.6, 4.2.8 and 4.1.29 seem not to
honor the parameter and use 64-bit adress no matter what.
--
I did some further testing and it seems I have found a culprit and a
solution. In older kernel versions (3.19.8 and 4.0.9 worked flawlessly
without extra boot parameters) I get something like this when booting:
ACPI BIOS Warning (bug): 32/64X address mismatch in
FADT/Pm2ControlBlock: 0x8800/0x
I did get the system to boot in 4.4.0-34 without noapic and nolapic -
but the fan was running on full (separate issue?). However, the system
seemed even slower than when booting WITH said parameters.
4.8 rc1 failed to boot without noapic nolapic, however fan was also on
full.
--
You received thi
Problem remains in 4.8 rc1.
** Tags removed: kernel-bug-exists-upstream-4.7-rc2
** Tags added: kernel-bug-exists-upstream-4.8-rc1
--
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/1590154
Ti
Did a part of the command fall off? I changed the last part to "bios-
release-date". Here is the output:
68YTT Ver. F.20
12/01/2011
The last kernel version that worked fine is in my Trusty install on a
separate partition, kernel 3.19.0-59. There, the boot parameter
"acpi_force_32bit_fadt_addr" is
I found a smart way to upgrade the BIOS, so now it's up to date, F.20. I
tested 4.4.0 and 4.7-rc2 again but I'm afraid the results were the same
:-(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Yes! 4.7-rc2 booted (with noapic and nolapic) but the slowness-problem
still remains there, tested with the disk utility again.
I tried to boot without noapic and nolapic but the computer seemed
really slow and the graphical environment never came up. I was able to
switch to console and reboot fro
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
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/1590154
Title:
System slow
** Attachment added: "Fail to boot, readable output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590154/+attachment/4679853/+files/readable.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Tested kernel mentioned in #3:
With noapic, nolapic:
Fails to boot, with readable output
Without noapic, nolapic:
Fails to boot, with unreadable output (but supposedly the same content?)
** Attachment added: "Unreadable, screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590
Public bug reported:
I tested this installing the Disks tool and running a read-only
benchmark. The transfer rate is very slow (2-3 MB/s) unless I'm moving
the cursor, then it jumps up.
As I understand this could have something to do with triggering/handling
interrupts. In this context it might b
Issue started after fresh install, no knowledge of earlier kernels.
Laptop is currently broken and unavailable for testing, it suddently
died in the middle of normal usage. Ruled out memory and reseted BIOS.
Unsure of reason for malfunction but suspecting solderings. Will perhaps
try baking in ove
I added the "proposed" source and from there installed kernel 3.19.0-46
(using Synaptic). Booted with acpi_force_32bit_fadt_addr and system
froze.
I get the feeling this kernel wasn't the one I was supposed to be
testing with. Could it be because I am on Trusty? Is the proposed kernel
released to
Public bug reported:
After install and updates this laptop still becomes VERY hot. I
installed indicator-sensors to get a handle on the temperature and it's
hovering at about 80C without much load at all.
I managed to work around this by adding "radeon.runpm=0" to boot options
and adding to /etc/
Bug submitted to bugzilla.kernel.org as per developer instructions:
https://bugzilla.kernel.org/show_bug.cgi?id=110451
** Bug watch added: Linux Kernel Bug Tracker #110451
http://bugzilla.kernel.org/show_bug.cgi?id=110451
--
You received this bug notification because you are a member of Kerne
My post to the developers:
http://marc.info/?l=linux-acpi&m=145186512903943&w=2
Reply:
http://marc.info/?l=linux-acpi&m=145191133113281&w=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
Done. 4.4.0-040400rc7 tested:
- Message about loading initrd image or somesuch.
- Screen goes black.
- Fan goes to full speed.
- HD light lit for about 15 seconds or so, then goes dark.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
I got it! If I didn't mess it up but I don't think so.
Side question: do you have to do "fakeroot debian/rules clean" for every
step when bisecting? The guide was a bit unclear on that. I was just
thinking the compile process might be quicker if I didn't do clean in
between..
19114b5458510b757cd2
Hi! Bisecting stuff is new to me - I'm not sure I did it the right way,
but..
..I tested precompiled kernel commits found via a link in the Kernel
bisection guide. My results are:
3.19.0-26.27 doesn't boot
3.19.0-25.26 boots normally
** Changed in: linux (Ubuntu)
Status: Incomplete => Con
Tested 3.19.0-23 just to make sure..and yes, it works. Everything I've
tested after 3.19.0-25 doesn't.
** Tags added: kernel-bug-exists-upstream-3.19.0-26 kernel-bug-exists-
upstream-3.19.0-42 kernel-bug-exists-upstream-4.2.0-22
** Tags added: kernel-bug-exists-upstream-4.3.2
--
You received th
Testing 4.4-rc6 had the difference in result that after the fan went on
max speed (unlike when booting on 3.19.0-25) and hdd was working - after
a while the blue XUbuntu screen with the spinning wheel came up. After
that the screen went black again and hdd stopped.
4.3.3 was same result but withou
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540783/+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
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540778/+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/15
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540781/+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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540786/+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/1529381
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540782/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540785/+files/PulseList.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/
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540780/+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/1529381
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540777/+files/CurrentDmesg.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
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540779/+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/1529381
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540775/+files/BootDmesg.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/
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540787/+files/UdevLog.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/1529
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540776/+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/1529381
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1529381/+attachment/4540784/+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
** Tags added: apport-collected
** Description changed:
To reproduce (on this hardware)
1) Install 14.04.3 LTS (Ubuntu or XUbuntu)
2) Install updates
3) Reboot
The kernel used after update is 3.19.0-42. Booting with the kernel that
came with the install image
What should I do to complete the bug report?
--
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/1529381
Title:
Updating 14.04.3 to latest updates renders system unbootable
Status
I did some testing using different kernels:
3.19.0-26, no boot.
- ACPI PCC error on screen, disappears after a few seconds
- Black screen, normal fan, no HDD activity
- Ctrl+alt+del doesn't work
3.19.0-42
- ACPI PCC error on screen, disappears after a longer time
- HDD works longer before stopp
Public bug reported:
To reproduce (on this hardware)
1) Install 14.04.3 LTS (Ubuntu or XUbuntu)
2) Install updates
3) Reboot
The kernel used after update is 3.19.0-42. Booting with the kernel that
came with the install image (3.19.0-25) works fine.
This computer is a HP Compaq 6715s. I have loo
Haven't had time to experiment for a while. However, I just upgraded to
Wily 15.10 (with updates) and the machine froze just as before. Will
report when I have again tried the latest mainline kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
#5 didn't solve, still has to reload wl now and then returning from
suspend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl stops working after resume from suspend
I had the same problem solved with the same change (128M -> 256M) on
15.04 amd64 running on a laptop. Should I open a separate bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1359
Installing 6.30.223.248+bdcom-0ubuntu3 (from Wily) seems to solve the
problem for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl stops working after resume from
Getting kernel panic every third or fourth resume.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Title:
bcmwl stops working after resume from suspend
Status in bcmwl package in
Bug occurred again, does seem to exist even after reinstalling driver.
** Changed in: bcmwl (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1466994
T
** Description changed:
After 10 min or so, or an hour. The freeze happened also when using the
performance (max freq) governor.
-
- WORKAROUND: Lock the CPU freq to something.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-18-generic 3.19.0-18.18
ProcVers
Other times the screen just freezes without becoming white. There is
however a very quick flicker of white it the lower part of the screen
before this happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
The sysrq+alt+1 and sysrq+alt+t had no effect. No sign of anything in
kern.log or kern.log.1 after reboot. SSH doesn't work either.
** Attachment added: "Photo of screen"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458569/+attachment/4417979/+files/DSC04561.JPG
--
You received this
Problems seems to be solved after removing and reinstalling driver!
** Changed in: bcmwl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1466994
Titl
Public bug reported:
Should this be reported against kernel instead?
The driver worked fine in 14.10. Since 15.04 module needs to be reloaded
after suspend for wlan to work again.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
ProcVersionSig
I just had a freeze using rc8 BUT it happened when I was also using the
performance governor - that is, no CPU cycling going on.
** Tags removed: kernel-bug-exists-upstream-4.1-rc6
** Tags added: kernel-bug-exists-upstream-4.1-rc8
** Description changed:
After 10 min or so, or an hour.
- Wo
** Description changed:
After 10 min or so, or an hour.
Workaround seems to be locking the CPU freq to something. I'm guessing
there might be a bug in the powernow-k8 driver that exhibits itself in
- systems with the XPRESS 200M CPU chipset.
+ systems with the XPRESS 200M GPU chipset.
Tested! System still freezes as before.
--
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/1458569
Title:
System freezes randomly
Status in linux package in Ubuntu:
Confirmed
Bug descri
Have been trying vmlinuz-4.1.0-040100rc5-generic for about a week, using
the laptop for maybe 2h a day, mostly just running Facebook. I was
starting to hope but it froze again today. I was hammering ctrl+alt+f2
in hope of a console just after that, and to my surprise it switched
(but not immediatel
Will continue to test with the powersave governor. For some reason just
setting the frequency and userspace governor doesn't seem to work.
--
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/145
Forgot the command output: root@emmas:~# sudo dmidecode -s bios-version &&
sudo dmidecode -s bios-release-date
68DTT Ver. F.13
09/08/2008
--
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/14
Thanks for the tip! I had forgotten about updating the BIOS because it
was such a hassle, but I finally got it done.
Unfortunately, the problem remains. I got a whitescreen today after
about 20-30 minutes of usage.
--
You received this bug notification because you are a member of Kernel
Packages
Public bug reported:
After 10 min or so, or an hour.
Workaround seems to be locking the CPU freq to something. I'm guessing
there might be a bug in the powernow-k8 driver that exhibits itself in
systems with the XPRESS 200M CPU chipset.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux
I currently don't have access to the same laptop anymore, as I seem to
have found a workaround by locking the CPU frequency and gave the
computer back to its owner.
However, I do have another laptop with the same GPU which has the same
symptoms. Should I open a new bug and post the information the
** No longer affects: linux-2.6 (Ubuntu)
** Also affects: linux-lts-utopic (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/14
** Tags added: kernel-bug-exists-upstream
--
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/1215441
Title:
Screen blank or shaking if boot without nomodeset
Status in “linux” package in Ub
kernel-bug-exists-upstream
--
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/1215441
Title:
Screen blank or shaking if boot without nomodeset
Status in “linux” package in Ubuntu:
Incompl
The folder 3.2.50-precise did not contain a i386 image, only amd64.
Still, it's older that the kernel I'm having trouble with.
Through synaptic, I downloaded some other kernels to test. Here is the
result, NOT using the nomodeset parameter:
3.2.0-51: shaking/distorted
3.2.0-49: shaking/distorted
** Attachment added: "This is the X.org log booting 3.2.0.52 withOUT nomodeset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215441/+attachment/3782497/+files/Xorg.0.log.old-without-nomodeset
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Booting with kernel 3.2.0-29 works normally. After upgrading to 3.2.0-52
the screen started shaking erratically and it was very hard to make out
anything on it. Adding the "nomodeset" parameter to boot work as a
workaround but also seems to make X.org use the vesa driver inste
** Attachment added: "This is dmesg booting 3.2.0-52 withOUT nomodeset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215441/+attachment/3782498/+files/dmesg.without-nomodeset
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Attachment added: "X.org.log booting 3.2.0-29 withOUT nomodeset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215441/+attachment/3782501/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
** Attachment added: "dmesg booting 3.2.0-29 withOUT nomodeset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215441/+attachment/3782500/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
76 matches
Mail list logo