Package: linux
Version: 4.13.13-1~bpo9+1
Looking at the output of dmesg, I see warnings like this:
md0: Warning: Device sde3 is misaligned
Checking the same disk with parted tells me it is aligned correctly:
# parted /dev/sde
GNU Parted 3.2
Using /dev/sde
Welcome to GNU Parted! Type 'help' t
Hi,
I've seen this problem on a fresh install of stretch on a Thinkpad T470s
when docked.
I found another upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=709062
and a Fedora bug that was incorrectly closed:
https://bugzilla.redhat.com/show_bug.cgi?id=876134
If I dock the laptop, pre
On 05/03/17 19:42, Niels Thykier wrote:
> On Sat, 04 Feb 2017 09:58:00 + Niels Thykier wrote:
>> Daniel Pocock:
>>> [...]
>>>
>>> Upstream is not really supporting rpc.svcgssd any more, they actually
>>> disabled it in the build so people can s
On 04/02/17 10:50, Niels Thykier wrote:
> Control: tags -1 moreinfo
>
> CC'ing the maintainer of nfs-common and the reporter of #848306.
>
> Robbie Harwood:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: unblock
>>
>> Please unblock p
After about a month without any reboot there was a crash with the 4.7
backports kernel too
Unfortunately, when I upgraded the kernel, the linux-image-amd64-dbg
package wasn't automatically installed with it so kdump hasn't given me
a stack trace for the crash. Therefore, I don't know if it was
package: nfs-kernel-server
version: 1:1.3.4-2
severity: serious
The blkmapd process looks for /run/rpc_pipefs/nfs/blocklayout
It fails to find it and the system boot doesn't complete, it asks for an
emergency login on the text console.
I don't see anything under /run/rpc_pipefs/nfs
Other NFS s
Package: nfs-common
Version: 1:1.3.4-1
Severity: important
Upstream no longer encourages the use of rpc.svcgssd and encourages use
of gssproxy instead
Need to remove it from the configure flags in debian/rules
Users should migrate to gssproxy
The nfs-utils packages should add appropriate sugges
On 15/12/16 11:44, Daniel Pocock wrote:
>
>
> On 14/12/16 23:41, Ben Hutchings wrote:
>> On Tue, 2016-12-13 at 20:55 +0100, Daniel Pocock wrote: [...]
>>> Thanks for providing this feedback
>>>
>>> I've done the following: - forked the upstream re
On 14/12/16 23:41, Ben Hutchings wrote:
> On Tue, 2016-12-13 at 20:55 +0100, Daniel Pocock wrote: [...]
>> Thanks for providing this feedback
>>
>> I've done the following: - forked the upstream repository
>
> The existing packaging repos are also based on th
On 15/12/16 09:50, Sven Geggus wrote:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 13:35 Uhr:
>
>> If the latest NFS / kernel combination in sid definitely won't work
>> without gss-proxy then you could open an RC bug against the nfs-utils
>> package
On 15/12/16 00:49, Ben Hutchings wrote:
> Control: tag -1 moreinfo
>
> On Fri, 9 Dec 2016 09:35:40 +0100 Daniel Pocock
> wrote:
>> Package: linux Version: 3.16.36-1+deb8u1 Severity: important
>>
>> The system is an NFS server running linux-image-3.16.0-4-amd64
&g
Package: nfs-kernel-server
Version: 1:1.2.8-9.2
Severity: serious
Fixed: 1:1.3.4-1
The kernel looks[1] for nfsdcltrack in /sbin
The package released in jessie installs it to /usr/sbin
Fixed in the 1.3.4-1 upload.
This affects jessie users, a stable update may be necessary
1. https://bugs.debi
Brief update on this issue: nfs-utils 1.3.4 is now in Debian sid
There is discussion about changes (e.g. going from svcgssd to gss-proxy)
in this bug, if anybody could add any comments it would be very welcome
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847681
On 11/12/16 20:01, Daniel
On 14/12/16 12:12, Sven Geggus wrote:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 11:01 Uhr:
>
>> Would you consider uploading it or proposing it in mentors.debian.net?
>> Please also send details on the gss-proxy ITP bug.
>
> Robbie is the one with the I
On 14/12/16 10:31, Sven Geggus wrote:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 09:38 Uhr:
>
>> They stopped including rpc-svcgssd in the default build as of 1.3.2 and
>> recommended gssproxy[1] instead.
>
> Yes, gssproxy is a working drop-in replacement
On 14/12/16 08:24, Andreas Henriksson wrote:
> On Wed, Dec 14, 2016 at 08:11:52AM +0100, Daniel Pocock wrote:
>> I agree the loss of Debian packaging history is a concern, that is one
>> reason I didn't clobber the existing repository and I wrote that we can
>> blo
On 13/12/16 22:46, Andreas Henriksson wrote:
> On Tue, Dec 13, 2016 at 08:55:34PM +0100, Daniel Pocock wrote:
>> Hi Ben,
>>
>> Thanks for providing this feedback
>>
>> I've done the following:
>> - forked the upstream repository
>> - created a
On 13/12/16 21:40, Raphaël Halimi wrote:
> Le 13/12/2016 à 21:36, Daniel Pocock a écrit :
>> Do you think you could investigate a little bit more and add
>> details to the bug, maybe have a look in Fedora's repositories to
>> see if they have a way to do that or ask on
On 13/12/16 21:21, Raphaël Halimi wrote:
> Hi guys,
>
> Sorry to intrude but, since you all seem eager to revive nfs
> packages (which I'm very happy about), could you please take a look
> at #539201 and include my patch ? It would allow to close both this
> bug and #738063, which are both quite
On 12/12/16 21:05, Ben Hutchings wrote:
> On Mon, 2016-12-12 at 11:13 +0100, Salvatore Bonaccorso wrote:
>> Hi,
>>
>> On Mon, Dec 12, 2016 at 10:23:49AM +0100, Ferenc Wágner wrote:
>>>>> Daniel Pocock writes:
>>>
>>>> Could either of y
On 12/12/16 10:23, Ferenc Wágner wrote:
> Daniel Pocock writes:
>
>> Could either of you comment on this bug? I saw your names in the
>> nfs-utils changelog. I've seen various problems with NFS under jessie
>> and I was hoping to help test if for stretch.
Hi Salvatore, Ferenc,
Could either of you comment on this bug? I saw your names in the
nfs-utils changelog. I've seen various problems with NFS under jessie
and I was hoping to help test if for stretch.
https://bugs.debian.org/847681
Regards,
Daniel
Package: nfs-utils
Version: 1:1.2.8-9.2
Severity: important
X-Debbugs-CC: andr...@fatal.se
I notice that Andreas made uploads to unstable in June and August 2016:
http://metadata.ftp-master.debian.org/changelogs/main/n/nfs-utils/unstable_changelog
while other developers have made unrelated chang
Package: linux
Version: 3.16.36-1+deb8u1
Severity: important
The system is an NFS server running linux-image-3.16.0-4-amd64
At times of heavy load on NFS, such as "git checkout some-branch" in a
large repository, the system crashes (dmesg output attached). It has
been happening regularly since t
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: serious
Ever since upgrading the server from wheezy to jessie, I've been having
crashes every couple of weeks. Running wheezy, it had been stable and
running continuously for over a year. NFS configuration was not changed
when upgrading.
T
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt9-3~deb8u1
NFS server stopped responding
I looked in the log and found 4 kernel stack traces, the last one
occurred at about the time that the NFS problem was noticed.
The final stack is similar to this OpenSUSE stack:
https://forums.opensu
I tried the workaround from the Ubuntu bug:
i915.i915_enable_rc6=0
After rebooting, I notice that the screen flashes at me from time to
time, and the errors are regularly appearing in dmesg, gdm login screen
broken, etc
[ 164.522266] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed
Since upgrading my laptop to wheezy, I experience several freezes per day
This time, I've been able to connect to it remotely and find the dmesg
output matches this bug report:
[ 5449.676827] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed... GPU hung
[ 5449.676833] [drm] capturing
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683039
I have various wifi routers running OpenWRT
I can connect to a TP-Link TL-WR1043ND over and over again without any
problem
But when I try to connect to a Buffalo WZR-HP-AG300H I always have this
problem, from every client device, includi
Package: linux-image-3.2.0-3-amd64
Version: 3.2.21-3
Severity: serious
Leaves root filesystem in read-only state, some users have reported root
filesystem corruption (see below), so I have marked this as serious
I have a dom0 running Xen (standard squeeze installation) and several
domU VM instanc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/09/12 16:01, Ben Hutchings wrote:
> On Sun, 2012-09-16 at 13:37 +0200, Julien Cristau wrote:
>> On Sun, Sep 16, 2012 at 13:24:56 +0200, Daniel Pocock wrote:
>>
>>> The second point, (b), apt-get seems to be unabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/09/12 13:05, Julien Cristau wrote:
> On Sun, Sep 16, 2012 at 12:33:33 +0200, Daniel Pocock wrote:
>
>> Now, running `apt-get dist-upgrade' chokes on updating the
>> linux-image package. Two issues come to mind:
&
Package: linux
Version: 3.2.0-3-amd64
Severity: important
I have flagged this as `important' because (a) it impacts people using
default settings from guided partitioning, and (b) it seems essential to
be able to have at least two kernels installed concurrently, otherwise
upgrades are impossible.
Maybe this workaround needs to be added to the list of tips in:
/usr/share/doc/nfs-common/README.Debian.nfsv4
I've found the same problem
I've been trying to set up NFS4 between a lenny client and squeeze
server with Kerberos
Client and server logs from kerberos have the following:
Dec 3
My box had lenny (installed in December, before the official release), I
just did:
apt-get dist-upgrade
It upgraded the box from 2.6.26-1 to 2.6.26-2
I did a reboot to get the new kernel
On booting, eth0 became eth0_rename_ren
I looked at:
/etc/udev/rules.d/70-persistent-net.rules
a
Package: firmware-bnx2
Platform: Dell M600 blade
OS: lenny amd64 (freshly installed in December 2008) as a Xen dom0
Problem description:
Thursday, the blade hardware was swapped (an M600 replaced with another
M600), same disks however.
Now, the ethernet devices don't appear after booting
M
36 matches
Mail list logo
