Anthony Buckley, the issue you are reporting is an upstream one. Could
you please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: Eric Dumazet, and David S. Miller, CC netdev)?
Please provide a direct URL
4.9-rc4 is now the latest. Problem not fixed.
Regards.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-bug-exists-upstream-4.8-rc5
** Tags added: kernel-bug-exists-upstream-4.9-rc4
--
You received this bug notification because you are a member of
Anthony Buckley, could you please advise to the results of 4.9-rc2? If
it is still reproducible in this, then this would be an upstream bug
also.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613027
Title:
Network
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613027
Title:
Network
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
Anthony Buckley, the next step is to fully commit bisect from kernel 4.2
to 4.4 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following
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
Anthony Buckley, to keep this relevant to upstream, one would want to
test the latest mainline kernel (now 4.8-rc4) as it is released.
Could you please advise?
** Tags added: bios-outdated-208
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-4.8-rc2
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 Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613027
Title:
Network scanner not detected by xsane after upgrade to 16.04
To
May be related to bug #1577137
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613027
Title:
Network scanner not detected by xsane after upgrade to 16.04
To manage notifications about this bug go
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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
21 matches
Mail list logo
