I have tested the proposed kernel as requested and updated tag to
verification-done-bionic. System booted as expected. Thank you for
fixing this.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks You-Sheng, I'll set aside some time shortly to upgrade.
Regards.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1856387
Title:
Freezing on boot since kernel 4.15.0-72-generic
Well done You-Sheng!
Tried both packages and they worked fine. Don't worry about the delay, I have
more than enough to keep me occupied at the moment.
Thanks much for your efforts here. What happens next, just wait for 20.04.1 to
release? Do I need to clean anything up or can I just leave as is
Hello yet again You-Sheng,
OK, I'm missing something here unfortunately. I've dome the first clone:-
git clone -b bug-1856387/fix-PIT-skip/bionic
https://git.launchpad.net/~vicamo/+git/ubuntu-kernel
but obviously the second will be a problem trying to clone into 'ubuntu-kernel'.
What is:-
git
Hello again You-Sheng,
I think I get something. I think I understand what you mean by it would take
several hours to publish built binaries. You want me to follow those links on
the ppa page and do those git clones?
I'm doing that anyway just see what happens.
Regards.
Tony
--
You received
Hello You-Sheng,
(hope you are well by the way)
I've applied your ppa as described
sudo add-apt-repository ppa:vicamo/ppa-1856387
sudo apt-get update
However I'm not sure what to do next. I assume it installed some packages, but
how do I test. I tried a reboot, but I couldn't see how it would
OK. I must confess I'm a bit vague on ppa's. Does it clone the kernel
source and then I do a build and test?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1856387
Title:
Freezing
Hello You-Sheng,
I've only just noticed this. Thanks for responding. I've been a bit busy
lately, but I'll either try one of the bionic 5.3 kernels or try your ppa test
hopefully soon.
Thanks. Regards.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hello all,
Does anyone know if this bug will cause a problem upgrading to Ubuntu 20.04
LTS? I assume it will as we're stuck using an older kernel and 20.04 is based
on kernel 5.4. Or, will it simply upgrade and keep us on the older kernel?
Regards.
--
You received this bug notification because
I have tested a proposed patch by Thomas Gleixner (t...@linutronix.de) at
both the identified commit and also at the latest version and in both cases my
computer booted successfully.
Comment also posted in bugzilla.
https://bugzilla.kernel.org/show_bug.cgi?id=206125
Regards
--
You received
Thanks for your feedback, You-Sheng. I've added a comment to that effect now.
Regards.
--
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/1856387
Title:
Freezing on boot since kernel
I have filed a bug in bugzilla. Hopefully it's been done OK as I've not
done this before.
It is as follows:-
Bug 206125 - Freezing on boot since kernel 4.15.0-72-generic release
Regards.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi You-Sheng,
Thanks for responding. Sadly, the problem is not fixed in v5.5-rc5 mainline
kernel.
I'll look at lodging a bug in bugzilla.
Also I'll try putting some debug code around in that commit to see if I can
identify anything.
Regards.
--
You received this bug notification because you
Hello again, sorry I meant to add the git bisect log (FYI). See below:-
# bad: [48d6312566e04b7a713cc7c15ae7dcd37efcfa95] UBUNTU: Ubuntu-4.15.0-72.81
# good: [ad85666cf30fb921558424a18cabbf396361a90c] UBUNTU: Ubuntu-4.15.0-70.79
git bisect start 'Ubuntu-4.15.0-72.81' 'Ubuntu-4.15.0-70.79'
# good:
Hello,
I have completed the bisect as requested and identified the problem commit. The
bisect message is as follows:-
git bisect good
f723dd269d0740e09af47bb5590ffc4f61766153 is the first bad commit
commit f723dd269d0740e09af47bb5590ffc4f61766153
Author: Thomas Gleixner
Date: Thu Nov 7
Hello You-Sheng,
Thanks for responding again.
Yes, I was just looking at doing a bisect. I've done it before for another
problem. I just have to familiarise myself again with the procedures for it.
Will attend to it soon.
Regards
--
You received this bug notification because you are a member
Hello,
Just updating to say that I tried the upstream kernel below but the problem is
still present.
Upstream kernel:
5.5.0-050500rc1-generic
Regards.
Tony
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello You-Sheng,
Thanks for responding.
I tried "hpet=disable" on a boot for both -70 and -72. No change. Kernel -72
still just stops, but -70 boots OK. As for the dmesg, I don't seem to be able
to get any logging / messaging for -72. The only reference I can find for it is
in the dpkg log
Public bug reported:
After the update to install kernel 4.15.0-72-generic (a bit over a week ago) my
computer will not boot. On boot, all I see is the purple screen with:
Loading Linux 4.15.0-72-generic ...
Loading initial ramdisk ...
and nothing happens. Just sits there. I've waited about 5-10
Hello Christopher,
Sorry for the delay in responding. I've been away.
1. I tested 1.0.4 shortly after release and I can confirm that the problem
still persists. The network plug-in in the package (iscan-network-nt) that I am
fairly sure is the problem has not been changed since 2013. This
There have been some developments with this problem so I thought I should
post the latest news.
Firstly, I have reported the problem as directed above to the people concerned
and the netdev team twice, but there has been no response.
Secondly, I managed to narrow down the cause of the problem in
Sorry just to elaborate on what I did for the above in case its unclear.
git checkout master
git bisect start
git bisect bad v4.4-rc1
git bisect good v4.3
NB. - I built kernels for each of these to confirm the bad / good status
of each beforehand.
Then ran built kernels, then ran git bisect
OK, after all my problems trying bisect (see previous comments) I've
finally managed to successfully complete one. See the attached bisect
log for details of the last good commit
(10cbc8f179177c1a6d5f56a46ebddc8f602ce5ac) and the first bad one
(ef547f2ac16bd9d77a780a0e7c70857e69e8f23f).
Quite a
** Tags removed: needs-bisect
** Tags added: bisect-done
** 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/1613027
Just set status back - thought of something else to try.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1613027
Apologies in advance for marking this as confirmed, but I'm pretty much
out of options. I tried to bisect using mainline kernels (above), but
got nowhere. I followed the instructions as given:-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git checkout
Well after many days and heaven alone knows how many hours, I'm
beginning to go completely loopy. After getting a number of odd messages
(as in above) I finally got the following:
debian/rules.d/4-checks.mk:12: recipe for target 'module-check-generic' failed
make: *** [module-check-generic] Error
I need a little assistance - anyone. I've managed to get started (I
think) and test the first bisect and tried to mark as 'GOOD', but got
the following:
git bisect good
Bisecting: 147 revisions left to test after this (roughly 7 steps)
error: Your local changes to the following files would be
Hello Christopher,
Just to clear what you require here. I'm a little confused. I've been thru the
Mainline builds and established where I'm having a problem (v4.4...) and not
having it (4.3.6-040306-generic).
So the next step next is to run 'git clone...', 'git bisect...' and
start compiling
4.8-rc5 was the latest when I checked, so I tested this instead. Problem
still exists.
** Tags removed: kernel-bug-exists-upstream-4.8-rc2
** Tags added: kernel-bug-exists-upstream-4.8-rc5
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
Hopefully this will be of assistance, in case anyone looks at this bug.
I've run the following commands under the current kernel
(4.4.0-34-generic) and also a previous kernel (4.2.0-41-generic)
strace scanimage -L log_curr_kernel_not_work 2>&1 Scanner not detected
strace scanimage -L
Second log for above post
** Attachment added: "log_curr_kernel_not_work"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+attachment/4729878/+files/log_curr_kernel_not_work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** 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/1613027
Title:
Network scanner not detected by xsane after upgrade to
May be related to bug #1577137
--
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/1613027
Title:
Network scanner not detected by xsane after upgrade to 16.04
Status in linux package in
OK, I've tested a few of the mainlines (binary chop) and as far as I can
tell the last kernel that worked OK was 4.3.6-040306-generic
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3.6-wily/). So it
looks to me as if its since the start of the 4.4... series.
--
You received this bug
I've tried the above mainline (http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.8-rc2/) on both 64 bit and 32 bit PC's, but the problem
has not been fixed. If I get some time and the kernels are available for
download I'll try to identify at exactly what kernel it started.
Thanks.
** Tags
Public bug reported:
Hopefully I'm reporting this in the correct area/group. Sorry if not.
After upgrading to 16.04, my scanner is no longer detected by xsane (and other
scan apps.) The model is 'Epson WF-3520' multi-function and is connected
wirelessly to the network.
The problem occurs on all
OK, a little tedious, but I got there (as advised).
Using the Release list at 'https://launchpad.net/ubuntu/vivid/+source/linux'
I can state that the problem started between 3.16.0-28.38 (3.16.0-28-generic)
and 3.18.0-8.9 (3.18.0-8-generic).
In order to test the latest 3.16 ... I used the
Hello,
BTW Thanks for looking at this. I appreciate it. Alas kernel 4.3-rc5 doesn't
fix it. Things were a little different though. When I booted rc5, the 'Starting
version 219' showed straight away and in a few seconds the screen went blank,
the TV tuner powered off and everything hung. I
Hello, I tried rc6 but it did not work. However, instead of the screen going
blank after seeing 'Starting version 219', pages of text kept rolling thru.
Looked like it was doing some kind of trace and was looping to me. Tried to
find it in /var/log when I rebooted but could find anything that
Hello, sorry it has taken so long to get around to the bios update suggested.
I've had a lot on. Anyway, sadly nothing has changed.
Certainly worth a try, although I was a little doubtful since I can replicate
this on 2 other PC's. Here is the output requested:-
sudo dmidecode -s bios-version
Hello,
Sorry I had to leave this for a few days ...
Anyway I believe I have discovered where the problem lies. First things
first, booting with kernel '3.16.0-43-generic' works OK.
The other thing I discovered (latest kernel) is that if my TV tuner is
active the system won't boot. The light
** 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/1480642
Title:
systemd-boot
Status in linux package in Ubuntu:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439444/+files/WifiSyslog.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/1480642/+attachment/4439436/+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/1480642
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439440/+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
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439439/+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: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439433/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439443/+files/UdevLog.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
** Description changed:
Following advice as per Release Notes
(https://wiki.ubuntu.com/VividVervet/ReleaseNotes)
Just upgraded from 14.10 to 15.04 and now Ubuntu fails to start from
powering up. I select 'ubuntu' on the grub loader
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439434/+files/JournalErrors.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: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439437/+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: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439438/+files/ProcEnviron.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.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439435/+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/1480642
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439432/+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/1480642
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439441/+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/1480642/+attachment/4439442/+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/1480642
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439450/+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/1480642
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439458/+files/WifiSyslog.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/1480642/+attachment/4439454/+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
** Description changed:
Following advice as per Release Notes
(https://wiki.ubuntu.com/VividVervet/ReleaseNotes)
Just upgraded from 14.10 to 15.04 and now Ubuntu fails to start from
powering up. I select 'ubuntu' on the grub loader screen and then get a blank
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439455/+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: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439447/+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: CRDA.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439446/+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/1480642
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439449/+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/1480642
Greetings,
Ran the command as requested (had to install it first). I'm not sure if
its worked OK though. Seemed to collect details and clicked 'Send', but
lots of error messages / warnings rolled thru on the terminal window.
Hopefully OK.
Regards.
On 03/08/15 20:00, Brad Figg wrote:
This
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439457/+files/UdevLog.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: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439453/+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: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439451/+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: UdevDb.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439456/+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/1480642
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439448/+files/JournalErrors.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: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1480642/+attachment/4439452/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello Joseph,
Thanks for responding.
Sadly it didn't work either first up. Its very strange because once I go
through initial hiccups it boots normally on the latest (and previous -
3.19.0-23-generic) kernels. What is even more crazy (and I'm loath to
even say this because it sounds so
I was initially tempted to put 'systemd' as the package, however, today I tried
booting using 'upstart' and the PC still hung. So I've nominated the image as a
best guess and because I received an email urging me to nominate a package, but
in truth, I'm not sure.
Something I have noticed today
74 matches
Mail list logo
