On Mon, May 14, 2018 at 01:38:15PM +0100, Simon McVittie wrote:
> On Sat, 12 May 2018 at 18:26:11 -0700, Ross Vandegrift wrote:
> > It looks like the scope id was added in #644912. This may be a kernel bug
> > if
> > the scope id should be accepted.
>
> I think this might be a bug in whatever us
I notice that amd64-microcode and intel-microcode haven't been updated
in stable this year. (Indeed, amd64-microcode hasn't been updated at
all this year, but I know AMD has issued an update!)
You have updated intel-microcode in backports suites instead. What's
the reasoning behind this? I woul
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 30 Apr 2018 00:13:06 +0100
Source: linux-signed-amd64
Binary: kernel-image-4.17.0-rc3-amd64-di nic-modules-4.17.0-rc3-amd64-di
nic-wireless-modules-4.17.0-rc3-amd64-di nic-shared-modules-4.17.0-rc3-amd64-di
seria
On Mon, May 14, 2018 at 01:38:15PM +0100, Simon McVittie wrote:
> Not including the scope ID in the result of address resolution breaks IPv6
> link-local addressing (fe80:*), and link-local addressing and mDNS are both
> parts of the Zeroconf stack, so they (should) go well together.
Yep, this mak
Hi Pradeep,
thanks for your response.
On 14.05.2018 17:48, Pradeep wrote:
> The patch is for NFS client side bug where it was initializing the
> attributes to zero if NFS4ERR_MOVED is returned in LOOKUP; but referral
> was not followed later. This only happens with NFSv4 server and the
> specific
Package: linux-support-4.9.0-6
Version: 26
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the o
Package: linux-image-4.15.0-3-amd64
Version: 4.15.17-1
after running
reboot
machine start shutdown and hangs several minutes with this message on
console
hpwdt: Unxpected close, not stopping watchdog!
Fans go to maximum speed and machine freeze for several minutes before
rebooting.
Freezi
В письме от воскресенье, 13 мая 2018 г. 19:20:38 +03 Вы написали:
> Hello,
>
> could you provide us the kernel logs ? By running dmesg
> or journalctl -b.
>
> Thanks
>
> On Wed, May 09, 2018 at 03:55:18PM +0300, Alexander Kernozhitsky wrote:
> > Package: firmware-misc-nonfree
> > Version: 201708
On Mon, 2018-05-14 at 15:47 +0200, Sedat Dilek wrote:
> Hi Ben,
>
> some Debian/jessie systems were caught by the bug-report in [1].
> This issue was recently fixed in an updated Debian kernel for v3.16.y.
>
> Will you include the patch "tun: allow positive return values on
> dev_get_valid_name()
Hi Ben,
some Debian/jessie systems were caught by the bug-report in [1].
This issue was recently fixed in an updated Debian kernel for v3.16.y.
Will you include the patch "tun: allow positive return values on
dev_get_valid_name() call" [2] in linux-stable-3.16.y upstream?
This was a fix for "tun
> "Thorsten" == Thorsten Glaser writes:
Thorsten> Adrian Bunk dixit:
>> As an example, what happens if I debootstrap and deploy the
>> resulting filesytem to a large number of identical embedded
>> systems without entropy sources?
Thorsten> Just get into a habit of not do
Package: linux
Version: 4.17~rc3-1~exp1
Severity: wishlist
Tags: patch
Hi,
I've found Fedora28 tries to improve battery life on laptop.
https://docs.fedoraproject.org/f28/release-notes/sysadmin/Kernel.html#sect-kernel-battery
There are three points.
1. A new SATA link-powermanagement-pol
On Sat, 12 May 2018 at 18:26:11 -0700, Ross Vandegrift wrote:
> After upgrading my laptop from stretch to buster, I'm not able to mount NFS
> via
> mdns. I have the following entry in /etc/fstab:
>
> vanvanmojo.local:/mnt/storage /mnt/storage nfs4
> noauto,nofail,x-systemd.aut
Hello Frank and Pradeep,
I was hoping that you would have some insight on a possible
bug/regression/incompability between nfs-ganesha and the Linux kernel
with a specific patch to which you reacted (see below) in
https://marc.info/?l=linux-nfs&m=150998968529002&w=2.
There is no mail about the res
Control: tags -1 + patch upstream
Control: notfound -1 linux/3.16.51-3+deb8u1
Hi everyone,
I have identified the upstream commit that introduced this
bug/regression for us.
It is c05cefcc72416a37eba5a2b35f0704ed758a9145 "nfs: Fix ugly referral
attributes"
(https://git.kernel.org/pub/scm/linux/ke
Processing control commands:
> tags -1 + patch upstream
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via
nfs referrals
Added tag(s) patch and upstream.
> notfound -1 linux/3.16.51-3+deb8u1
Bug #898165 [src:linux] linux-image-3.16.0-6-amd64: can't mount NFS shares via
binary:linux-image-4.17.0-rc3-amd64 is NEW.
binary:linux-image-4.17.0-rc3-cloud-amd64 is NEW.
source:linux-signed-amd64 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature an
17 matches
Mail list logo
