I'm guessing my problem is at least related if not exactly the same.
Here is the /var/log/apt/term.log relevant info:
Preparing to unpack .../08-firmware-sof-signed_1.7-1_all.deb ...
Unpacking firmware-sof-signed (1.7-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-60a2xL/08-firmware-
Title:
> NVidia driver 460 doesn't work after updating to proposed kernel
> 5.11.0-14.15-generic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923390/+subscriptions
>
--
Chris Hermansen · clhermansen "
Sorry I forgot to mention that...
After the boot where the screen resolution was messed up, I tried:
1. The recovery boot (nothing improved)
2. Installing the NVidia driver manually (terminated with error, no
improvement)
3. Apt purge (resolution back to 1920 x 1080, seemingly ok)
So just to be
Daniel, I rebooted into 5.11.0-13.14 as you requested and everything
seems OK, display-wise at least. I also fired up Additional Drivers and
that seems to be in order (ie the official NVidia driver).
Anything else I can try for you?
--
You received this bug notification because you are a member
Daniel, I rebooted into 5.11.0-13.14 as you requested and everything
seems OK, display-wise at least. I also fired up Additional Drivers and
that seems to be in order (ie the official NVidia driver).
Anything else I can try for you?
--
You received this bug notification because you are a member
@Joseph Salisbury, the 4.10.0-21 kernel crapped out on me but with a
different error:
May 1 18:42:25 vancouver kernel: [28120.190864] BUG: unable to handle kernel
NULL pointer dereference at 0021
May 1 18:42:25 vancouver kernel: [28120.190895] IP:
dma_fence_wait_timeout+0x36/0xf0
M
@Joseph Salisbury, I'm running the 4.10.0-21 kernel now. Let's see what
happens.
--
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/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux
@Joseph Salisbury,
I've had the 4.10.0-20.22~lp1674838 kernel running overnight with stress
and dmesg running in a loop and Firefox open to my gmail account, and no
problems (neither evident nor in dmesg output).
--
You received this bug notification because you are a member of Kernel
Packages,
@Joseph Salisbury;
Just getting ready to try out your kernel test. During the dpkg -i
there were some messages I did not care for, for instance:
dpkg: warning: downgrading linux-headers-4.10.0-20 from 4.10.0-20.22 to
4.10.0-20.22~lp1674838
and
Not updating initrd symbolic links since we are be
@Ken Haase congratulations, you are a kernel-testing machine and I
gladly stand in your shadow!
Your experience jibes with mine but I feel less certain since I have a
hard time provoking evidence in syslog.
--
You received this bug notification because you are a member of Kernel
Packages, which
@Ken Haase, here is what I do:
1. make sure you aren't running any proprietary drivers and if you are
and you can back them out (use the Software > Alternative Drivers tool
for this)
2. look back at the kernels @Joseph Salisbury has requested we test
https://launchpad.net/~canonical-kernel-
team
@Joseph Salisbury,
No system hangs yet with kernel 4.9.0-16. I am seeing this:
[ 8034.959275] nouveau :01:00.0: gr: TRAP ch 2 [003fa69000 Xorg[1191]]
[ 8034.959288] nouveau :01:00.0: gr: GPC0/TPC2/TEX: 8009
which I am trying to ignore...
--
You received this bug notification beca
@Joseph Salisbury, installed the 4.9.0-16 recommended and running now
(continuing to use stress). More later...
--
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/1674838
Title:
kernel BUG
Still no problems with 4.10.11-041011.
--
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/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Status
@Joseph Salisbury,
Running the same test on 4.10.11-041011-generic did not wedge the
system.
This was the test:
for t in 1 2 3 4 5 6 7 8 9 10; do echo iter $t; stress -c 2 -m 2 -t 60;
dmesg; done
So I'm leaving this running for awhile and will report back.
--
You received this bug notificatio
@Joseph Salisbury my computer, running 4.10.0-8, hung just now (display
frozen etc). I was running "stress". This is similar to what happened
previously with respect to this bug, but there seems to be nothing but a
bunch of nulls in syslog this time. Not sure how to determine whether
the same bu
Joseph, I'm running 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59
UTC 2017 x86_64 x86_64 x86_64 now. I'll keep you posted.
BTW no problems yesterday with 4.10.11. My wife has been using the
computer for a photo project on a web-based photo book service and that
is what brought about this p
Joseph, for us rookies out here, can you confirm that these are the only
files we need to install with the 4.10.0-8 kernel you would like tested?
linux-headers-4.10.0-8_4.10.0-8.10_all.deb
linux-headers-4.10.0-8-generic_4.10.0-8.10_amd64.deb
linux-image-4.10.0-8-generic_4.10.0-8.10_amd64.deb
linux
Joseph, kiney;
I was having the problem yesterday with 4.10.0-19-generic whose vmlinuz
is dated 8 April.
I installed 4.11.0-rc7 and ran it for awhile today with no problems, but
I don't have a good feeling for how long is necessary to say "I think
the problem is solved".
I have now installed 4.1
Public bug reported:
This is a relatively fresh installation of 17.04 on a relatively old
Dell Optiplex.
This message appears in /var/log/syslog:
Apr 17 14:20:22 vancouver kernel: [ 3688.848621] [ cut here
]
Apr 17 14:20:22 vancouver kernel: [ 3688.848628] kernel BUG at
Christopher, just to report in again. No crashes since the first (the
one reported in this bug).
--
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/1495136
Title:
System hard froze, kernel
Christopher, good afternoon and thank you for your testing instructions.
Since the crash reported in this bug, I have not had another such
problem. I cannot find similar error messages in the syslog file.
So I am wondering what to do. I can certainly test the kernels as you
suggest, but since t
Public bug reported:
When I rebooted and looked in syslog, I saw this:
Sep 12 15:05:41 avignon thermald[681]: Dropped below poll threshold
Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset
Sep 12 15:05:41 avignon thermald[681]: thd_trip_cdev_state_reset
Sep 12 15:05:41 avignon ther
Hi Tony and others,
I had planned to file an upstream bug but my inspiron (because of this
problem and a problem with the Broadcomm wireless) is very awkward to
test... So I have not - yet anyway - done that.
Regards, Chris Hermansen
On May 9, 2014 9:10 PM, "Anthony Matt" wrote:
Christopher, thank you very much for your guidance. I won't be able to
submit the information until the 13th as I am away from that computer until
then.
Chris Hermansen
On 2013-11-02 5:20 AM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
> Chr
Christopher, I am ready to report this bug upstream. I have read the
process described in your link carefully but I still have one
uncertainty arising from my general ignorance of these matters; would
you please be so kind as to provide some advice?
The instructions provided in your link suggest
nning fine on the
4311 device.
Chris Hermansen
On 2013-10-30 9:26 PM, "Christian S." <732...@bugs.launchpad.net> wrote:
> What is the state here?
>
> This issue still exists with a fresh install of 12.04.3 and 13.10. The
> default used driver is bcmwl but bcm4311 does n
Just a brief followup to the odd efect noted above in #14. On this
boot, which resulted in an SHM-free greeting, I left the computer idle,
and after the screen blank engaged, I wiggled the touchpad to awaken the
screen, and it was again SHM-free.
I will avoid concluding anything from that experie
Christopher, based on your question, I added NOMODESET to
/etc/default/grub definition of GRUB_CMDLINE_LINUX_DEFAULT, ran update-
grub, and rebooted.
Short answer - it no longer provides any salubrious effect.
Long answer:
The system booted into stripey / herringbone display, though there were
s
Christopher, please see the comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/572521/comments/73
It appears I reported this against Frank Lovegrove's bug 572521 as
affecting me in 10.04 and 10.10
--
You received this bug notification because you are a member of Kernel
Packages, which
Christopher, I have had this problem to one degree or another with every
Ubuntu release since I converted this laptop from running Windows XP to
running Ubuntu, which if memory serves was in 2010 or 2011.
For clarity: in Saucy, the problem does not occur on every boot (cold
boot or reboot). I wou
AHA!!!
Tonight I booted the machine and all worked fine. Then I rebooted and
got stripey herringbone display.
So in fact it is not fixed in 3.12.RC6 and I have changed the tags.
** Tags removed: kernel-fixed-upstream kernel-fixed-upstream-v3.12-rc6
** Tags added: kernel-bug-exists-upstream kern
Sorry an error in my above post. The two messages that flash on screen
between the all-purple screen and the Ubuntu splash screen are:
MP-BIOS bug: 8254 timer not connected to IO-APIC
ata3: softreset failed (device not ready)
The all-purple screen lasts for about 20 seconds. The two messages
abo
Christopher Penalver, thank you for your continued interest in sorting
out this problem.
Following your instructions, I have installed kernel 3.12.0-031200rc6.
So far I am unable to make the stripey / herringbone pattern show up
(neither on reboot nor on cold boot). In contrast I booted twice wit
Christopher Penalver (message #3) I have experimented with the bios
upgrade as you suggest.
I managed to upgrade the bios as you requested to 2.6.3 but this does
not seem to solve the problem; when I boot from today's Saucy image, I
still get the weird herringbone stripey screen. The workaround i
com> wrote:
> Chris Hermansen, if reproducible, please open a new report so we may track
> this for your hardware via a terminal:
> ubuntu-bug linux
>
> frank lovegrove, this bug report is being closed due to your last
> comment
> https://bugs.launchpad.net/ubuntu/+source/li
Completely in agreement with bkloppenbork above in #30. Bug
https://bugs.launchpad.net/bugs/1174145 is not a duplicate of this bug.
--
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/1097519
*** This bug is a duplicate of bug 1097519 ***
https://bugs.launchpad.net/bugs/1097519
Actually I think bug 1097519 is a duplicate of this bug.
The title of this bug is a better description of the problem: the wrong
driver is loaded for the 4311 (at least on my Dell Inspiron 1501) and
worse i
Public bug reported:
This problem occurs intermittently on my Dell Inspiron 1501 laptop. For
instance, on booting the Saucy beta 2 release from USB stick; or today,
booting the installed 13.10 beta 2 with all updates current. But not
always.
The workaround is to wait for the screen to blank on
Christopher, if Frank cannot test this, I can, but not until Wednesday or
so when I am in the same city as the offending laptop.
On 2013-09-28 7:01 PM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
> frank lovegrove, this bug was reported a while ago and there hasn't been
>
I should have said - the laptop this occurs on is a testing laptop; I
can do anything to it (well perhaps hurling it out the second floor
window won't help but if necessary)
** Summary changed:
- vertical coloured lines on bootup dell inspiron 1501
+ vertical coloured lines on bootup dell ins
I am sorry to say that I removed this card a couple of releases ago - I
was finally able to get an ethernet cable to the computer in question -
and I don't know where I put it (blush).
So I am not able to test at this time. Very sorry.
If I am able to find it at some point in the future, should
42 matches
Mail list logo
