On 2024-11-30 12:39:31, Luca Boccassi wrote:
There are no patches or color choices downstream, it's just what
upstream provides, so if you don't like their choice of a default,
please bring it up upstream, we will not carry out-of-tree patches to
customise something like this for one particular u
Hi Luca,
I think it is inappropriate that you put your personal preferences
over usability in general. It is unreasonable to set a font color
without taking the background color into account.
My request is to go with upstream's default, giving a readable output
in general. If a user prefers to h
Sorry to say, but this annoying bug is still in:
:
:
Nov 30 11:43:00 cecil.afaics.de systemd[1]: nfs-mountd.service: State
'stop-sigterm' timed out. Killing.
Nov 30 11:43:00 cecil.afaics.de systemd[1]: nfs-mountd.service: Killing process
1229 (rpc.mountd) with signal SIGKILL.
Nov 30 11:43:00 ce
Package: iproute2
Version: 6.12.0-1
Blue on a black background is as impossible to read as yellow on
white. Obviously it is not reasonable to modify the foreground
color without taking the background color into accout. Could you
please make sure ip and the other tools in iproute2 produce a
readabl
Hi Uwe,
In the meantime I had found Tuxedo's driver package as well, not to
mention the project on github https://github.com/dante1613/Motorcomm-YT6801.
I just wonder how a renowned maker of Linux laptops comes to the
idea to add such exotic hardware to their main laptop line?
Regards
Harri
Package: linux-headers-6.11.6-amd64
Version: 6.11.6-1
Could you please enable support for
Motorcomm YT6801 GBit NIC
in the kernel configuration for amd64? Hardware is a Tuxedo
InfinityBook Pro Intel Gen9.
By now I could just verify the Bookworm backports kernel,
but reading the changel
Package: linux-image-amd64
Version: 6.10.6-1
Hi folks,
would it be possible to provide meta packages linux-headers-amd64-6.10
and linux-image-amd64-6.10 (and similar), to support installing several
major kernel versions in parallel (stable and backports, for example)?
Currently it is easy to lo
Package: iproute2
Version: 6.10.0-2
Could you please drop the color output of ip by default?
Sometimes color output is very helpful, eg. for syntax
highlighting in your favorite editor, but I cannot imagine
why it would be helpful to show the IPv6 address in blue
on black background, or the MAC a
Package: linux-image-amd64
Version: 6.10.6-1
Upgrading from 6.1.106 to 6.10.6 failed, because some network
interfaces changed their names, eg.
enp49s0f1 --> enp49s0f1np1
Pretty painful for a headless server system. The system booted,
but drbd was dead.
Before (6.1.106):
2024-09-04T10:
Hi Salvatore,
for testing I have derived a private nfs-utils package for shiny new
version 2.7.1 and gave it a try: 3 patches could be dropped, one patch
had to be refreshed, the rest builds out of the box (on Bookworm).
quilt delete fsidd-call-anonymous-sockets-by-their-name-only-don-.p
You might want to consider to use upstream's python script to build
an up-to-date firmware package for Debian. Clone
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
check out the most recent tag, and run the script, eg
% cd linux-firmware
% git
Sorry, I didn't mean to blame you. My real problem is, I have an NFS
server based on Debian 12 in the office that gets stuck every other
week. nfsd just stops and cannot be killed, see #1071562. *This* is
the bug report not making any progress.
All I can do is trying to improve the NFServer, eg b
Somehow this got stuck :-(.
Recently we have seen the "no config found" error for backports kernel
6.9.7 as well, ie the problem is not solved for newer kernels, either.
[Wed Aug 7 09:43:34 2024] Linux version 6.9.7+bpo-amd64
(debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-12 (Debian 12.2.0-14)
12.2.0, GNU ld (GNU
Hi Salvatore,
is running the backports kernel supposed to be the official fix,
or will there be fixed 6.1 kernel for Bookworm as well?
Regards
Harri
Package: nfs-utils
Version: 2.6.4-5
Trying to backport nfs-utils to Bookworm I ran into a build error:
:
gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include/tirpc -I/usr/include/libxml2 -I ../../support/nfsidmap -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -pipe -Wall -Wextra -
Package: linux-image-6.1.0-23-amd64
Version: 6.1.99-1
Sometimes iwlwifi becomes unavailable on our Tuxedo laptops
running Debian's kernel 6.1.90, 6.1.94 or 6.1.99. The error message
in system log is
2024-07-23T09:14:59.386353+02:00 ppcl013 kernel: [ 18.191543] Intel(R)
Wireless WiFi driver fo
On 2024-06-20 15:16:50, Thomas Glanzmann wrote:
Hello,
since I have also three productions systems with proxmox and bookworm nfs
servers which did not show the issue, I wonder which NFS version you're
using? I use nfs version 3.
Cheers,
Thomas
I am using NFS version 4, e.g.
% grep -
Package: nfs-common
Version: 2.6.4-4
Severity: wishlist
Backporting 2.6.4-4 to Bookworm fails with
:
:
Making all in reexport
make[3]: Entering directory '/build/nfs-utils-2.6.4/support/reexport'
gcc -DHAVE_CONFIG_H -I. -I../../support/include -I/usr/include/tirpc
-I/usr/include/libxml2 -Wdat
PS: I am not using Proxmox (here), but the nfsd was running inside
a LXC container. The container couldn't be stopped due to the stuck
service and the whole LXC server had to be restarted.
PS: I am not using Proxmox in this case, but native Debian 12. nfsd
is running inside an LXC container.
Regards
Harri
metoo. I am not sure if a modern kernel on the clients is involved
(most clients are running 6.1.90), but I have seen a blocking nfsd
twice as well, last time this morning.
The kern.log on the server says
2024-06-10T15:54:23.722921+02:00 nasl006b kernel: [1298984.543582]
receive_cb_reply: Got u
Found it on Bookworm as well.
Regards
Harri
Hi Salvatore,
sorry for not sending a reply. I completely forgot this bug report.
Fortunately it appears to be still open.
I ran into this problem again just a few minutes ago on running apt upgrade.
Several services were restarted in parallel, using "needrestart".
journalctl shows:
Apr 21 12:
Package: nfs-common
Version: 1:2.6.4-3
Restarting rpc-statd.service (e.g via needrestart at upgrade time)
runs into a timeout:
Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: State
'stop-sigterm' timed out. Killing.
Mar 16 20:06:58 lola.afaics.de systemd[1]: rpc-statd.service: Kill
It didn't work when I tried, sorry. Seems to be OK now.
Package: firmware-iwlwifi
Version: 20230625-2
The source URL mentioned in the copyright file doesn't work anymore.
It seems to be
https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware
now.
Same goes for other packages.
Regards Harri
On 2023-12-28 14:40:30, Salvatore Bonaccorso wrote:
Because it needs backporting work in 6.1.y upstream, which for John
Johansen aimed to work on. You can read about the history and backlog
in #1050256 . So far I have not got a reply from John on
https://bugs.debian.org/1050256#215 .
Oh, I th
Hi folks,
apparently LXC is affected by a bug around apparmor support for months,
see #1052934 and #1050256. The workaround is to set PrivateNetwork=false
(set by default as a security measure) or to use a backports kernel.
AFAIU reason is a bug in 6.1. The fix (1cf26c3d2c4c) is not a one-liner,
Package: firmware-linux-free
Version: 20200122-1
The source mentioned in the copyright file is broken:
% git clone
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git
Cloning into 'linux-firmware'...
fatal: repository
'https://git.kernel.org/cgit/linux/kernel/git/firmware/
Hi folks,
what is Debian's policy wrt using the current stable version with
current hardware? Am I supposed to create a bug report about
linux-signed-amd64 or firmware-nonfree, if (lets say) WLAN is
broken on a 1 year old notebook? Use backports or unstable instead?
Regards
Harri
metoo. The current nonfree package is more than 12 months old.
Thank you very much in advance
Harri
Sure, but why does systemctl complain about rpc-svcgssd.service, if
there are no NFS credentials inside? Its perfectly fine to run NFS
without cryptographic security, even though /etc/krb5.keytab does
exist.
I have the impression that the conditionals you mentioned are not
complete.
Hi Salvatore,
would it be possible to check if there are some NFS credentials in the
krb5.keytab file before issuing an error?
Regards
Harri
Package: nfs-kernel-server
Version: 1:1.3.4-6
I would like to reduce nfsv4gracetime and nfsv4leasetime from 90 sec
to something reasonable. Looking through several scripts and systemd
config files I figured out that I have to set
RPCNFSDOPTS
in /etc/default/nfs-server.conf to make a hel
Package: nfs-common
Version: 1:1.3.4-6
systemd moans about krb5.keytab at boot time
```
# systemctl --failed
UNITLOAD ACTIVE SUBDESCRIPTION
* rpc-svcgssd.service loaded failed failed RPC security service for NFS server
LOAD = Reflects whether the unit definition was pr
Package: linux-image-5.10.0-9-amd64
Version: 5.10.70-1
I have found a lot of messages in on 4 Dell R740 (with Perc H740P controller
and 7 SSDs in RAID5 plus 1 hot spare) this morning:
[Fri Nov 5 07:40:53 2021] DMAR: DRHD: handling fault status reg 2
[Fri Nov 5 07:40:53 2021] DMAR: [DMA Write]
PS: Using sysvinit both services are fine.
Package: nfs-kernel-server
Version: 1:1.3.4-6
After boot the nfs-server is not ready yet:
# systemctl status nfs-server
* nfs-server.service - NFS server and services
Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-c
Hi folks,
using linux-image-5.10.0-0.bpo.3-amd64 (buster-backports) and dd
to write an iso image (e.g. ubuntu-20.10-desktop-amd64.iso) to an
USB stick:
dd stops writing and closes source and destination file handle, but
it does not exit. It cannot be interrupted, either. At shutdown time
the sys
Actually I cannot say. I haven't seen this problem in a while. And
/etc/init.d/nfs-common start does
PIPEFS_MOUNTPOINT=/run/rpc_pipefs
:
mkdir -p "$PIPEFS_MOUNTPOINT"
:
modprobe sunrpc nfs nfsd
mount -t rpc_pipefs rpc_pipefs $PIPEFS_MOUNTPOINT
prov
Actually I cannot say. I haven't seen this problem in a while. And
/etc/init.d/nfs-common start does
PIPEFS_MOUNTPOINT=/run/rpc_pipefs
:
mkdir -p "$PIPEFS_MOUNTPOINT"
:
modprobe sunrpc nfs nfsd
mount -t rpc_pipefs rpc_pipefs $PIPEFS_MOUNTPOINT
prov
PS: /etc/default/nfs-common says
NEED_STATD=yes
STATDOPTS="-n nasl006.example.com"
NEED_IDMAPD=yes
NEED_GSSD=
PIPEFS_MOUNTPOINT=/var/lib/rpc_pipefs
Package: nfs-common
Version: 1:1.3.4-2.1
Running "/etc/init.d/nfs-common start" rpc.idmapd failed with
rpc.idmapd[9725]: main: open(/run/rpc_pipefs/nfs): No such file or directory
Ain't the startup script supposed to create this directory?
init is sysv
Regards
Harri
Hi folks,
using the 5.5.17 backports kernel: lspci froze the whole pc (at least
on a Lenovo p53). Is it possible that we need a backport of the 3.6
pciutils package?
I had sent this to the debian-backports list before, but there was no
response.
Regards
Harri
Would it be reasonable to configure these kind of items and
limits *independent* of the init system? This would help to
avoid unexpected side effects of changing the init system.
Thanx in advance
Harri
Hi folks,
looking at the number of cores and highly parallel applications
I wonder if it would be reasonable to increase the default
kernel.pid_max (currently 0x8000) to lets say 0x3f?
Do you expect negative side effects?
Regards
Harri
I cannot confirm the fix. Even when rpcsec_gss_krb5 *is* loaded,
rpc-svcgssd.service still fails for Buster:
root@srvl064:/etc# systemctl daemon-reload
root@srvl064:/etc# systemctl restart rpc-svcgssd
Job for rpc-svcgssd.service failed because the control process exited with
error code.
See "sys
Package: linux-image-4.19.0-6-amd64
Version: 4.19.67-2+deb10u1
When I switched off my USB disk dockingstation (2 slots, 2 Sata
disks were inserted) I got a kernel dump:
Oct 31 16:26:44 dpcl082 kernel: [22985.418721] usb 6-2: USB disconnect, device
number 2
Oct 31 16:26:44 dpcl082 kernel: [22985
FYI:
I had problems with linux-image-4.19.0-5-amd64, too, esp. on writing
large amounts of data to an USB block device (USB-C). "sync" got stuck,
umount didn't work, host became unresponsive, etc. Reset necessary.
linux-image-4.19.0-6-amd64 (in proposed-updates) seems to work better.
Regards
Ha
FYI: "fsck -y" on an external USB drive (USB-C, ext4) gave
me a ton of messages
:
[ 191.261939] xhci_hcd :05:00.0: WARN Wrong bounce buffer write length:
1024 != 0
[ 191.263743] xhci_hcd :05:00.0: WARN Wrong bounce buffer write length:
1024 != 0
[ 191.263788] xhci_hcd :05:00.0: W
Hi folks,
since 4.19.37 there have been quite a number of new versions in
upstream's linux-4.19.y branch. I have to support recent hardware
for my Debian 9 systems, so I wonder what are your plans for buster
and stretch-backports?
Regards
Harri
Are other Intel NICs affected by this problem as well?
Regards
Harri
Hi folks,
Using kernel 4.19.0-0.bpo.2-amd64 on Stretch I had 2 incidents
in the past 3 weeks: The PC got stuck, apparently related to md and
RAID1 (see the attached logfiles).
I have installed 4.19.0-0.bpo.4-amd64 this morning. According
to the changelog there were a few changes wrt md and raid s
Hi folks,
On 3/30/19 5:47 AM, Debian FTP Masters wrote:
linux_4.19.28-2~bpo9+1_multi.changes uploaded successfully to localhost
along with the files:
linux_4.19.28-2~bpo9+1.dsc
linux_4.19.28-2~bpo9+1.debian.tar.xz
linux_4.19.28-2~bpo9+1_source.buildinfo
linux-doc-4.19_4.19.28-2~bpo9+
Hi Ben,
On 2/6/19 8:11 PM, Ben Hutchings wrote:
Please open a bug against the version in sid.
Done: https://bugs.debian.org/921616
Many thanx
Harri
Package: linux-image-4.19.0-2-amd64
Version: 4.19.16-1
I am hit by a general protection fault in netfilter, see
https://marc.info/?l=netfilter&m=154807599219095 .
According to upstream the problem has been fixed in 4.19.17.
Regards
Harri
Hi folks,
I am hit by a general protection fault in the 4.19.12 backports
kernel, see https://marc.info/?l=netfilter&m=154807599219095 .
According to upstream it has been fixed for 4.19.17, which is not
in Sid yet.
AFAIR I am not allowed to post bug reports about backports. OTOH
is is pretty unl
Hi folks,
is it safe to assume that Buster goes with kernel 4.19.x?
Regards
Harri
obsolete, please close
obsolete (AFAICT), please close
There were tons of messages, then the network went down.
kernel.log:
Jun 5 17:33:39 nasl006a kernel: [ 4624.059640] RPC request reserved 84 but
used 268
Jun 5 17:33:39 nasl006a kernel: [ 4624.060169] RPC request reserved 84 but
used 268
Jun 5 17:33:39 nasl006a kernel: [ 4624.060702] RPC requ
metoo
I have "rpc request reserved 84 but used 268", but I am not picky.
Regards
Harri
:56 +0200
Ben Hutchings wrote:
> On Thu, 2017-09-28 at 16:50 +0200, Harald Dunkel wrote:
> > Hi folks,
> >
> > what is the story behind linux_4.9.47-1.dsc that popped up
> > in p-u on the ftp server more than 2 weeks ago? Looking at
> > its changelog there are
Hi folks,
the backported kernel for Jessie (4.9.30-2+deb9u2~bpo8+1) gave me an
error message:
Oct 9 19:00:02 dpcl083 kernel: [981816.818862] BUG: unable to handle kernel
paging request at 45810f79
Oct 9 19:00:02 dpcl083 kernel: [981816.818866] IP: []
__d_lookup+0x4f/0x130
Oct 9 19:00
Hi folks,
what is the story behind linux_4.9.47-1.dsc that popped up
in p-u on the ftp server more than 2 weeks ago? Looking at
its changelog there are tons of interesting fixes inside.
Should I upgrade? Or has it been obsoleted by 4.9.{48..52}
in the meantime?
Regards
Harri
On Thu, 3 Aug 2017 11:17:04 +
Daniel Sobe wrote:
> Providing lvm.conf for both Debian 8 and Debian 9 as suggested. I'm not aware
> of any modifications to them.
>
>
I am not sure if this is your problem, but I would suggest to
tell lvm2 to ignore the raw devices and to scan only the drbd
Package: nfs-common
Version: 1:1.3.4-2.1
I am using NFS without Kerberos. Problem:
Aug 4 10:32:53 il06 rpc.svcgssd[18935]: ERROR: GSS-API: error in
gss_acquire_cred(): GSS_S_FAILURE (Unspecified GSS failure. Minor code may
provide more information) - No key table entry found matching nfs/@
Au
I would suggest to post /etc/lvm/lvm.conf as well.
Regards
Harri
Hi folks,
What is the relationship between upstream's 4.9.x LTS series and
the "regular" kernel in Stretch for x>30?
Regards
Harri
I had a similar effect for kernel linux-image-4.8.0-0.bpo.2-amd64-unsigned
(even though a reset on the front panel was sufficient to reboot). Some say
this problem has been introduced by memory cgroups.
Does this ring a bell? Are you using dockers or LXCs with cgroup_enable=memory ?
Regards
Harri
On 06/03/17 15:59, Ben Hutchings wrote:
> On Sat, 2017-06-03 at 08:08 +0200, Harald Dunkel wrote:
>>
>> What would you suggest?
>
> I would suggest not using linux-libc-dev from jessie-backports.
>
This workaround is already known; see my first post in this
thread.
Regards
Harri
On 06/02/17 11:16, Ben Hutchings wrote:
> On Thu, 2017-06-01 at 10:37 +0200, Harald Dunkel wrote:
>>
>> Workaround is to avoid the backports package, but I wonder if it would
>> be possible to fix this? How comes that the fix for #822396 doesn't
>> work for Je
Hi folks,
wrt #822396:
Using the 4.9.25 backports linux-libc-dev for Jessie I still get
the conflict between linux/if.h and net/if.h, e.g. on building
strongswan 5.5.3 (see below).
Workaround is to avoid the backports package, but I wonder if it would
be possible to fix this? How comes that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Laurence,
On 04/15/17 18:02, Laurence Parry wrote:
> memory cgroups decreased the stability of 4.8, regardless of whether they
> were actively being used; we were not actively using them, but still
> experienced lockups. Disabling them on the k
On 03/03/17 16:59, Ben Hutchings wrote:
> On Fri, 2017-03-03 at 15:54 +, Ben Hutchings wrote:
>>
>> linux is still in NEW for all other architectures, and linux-latest and
>> linux-signed are waiting for that.
>
> Actually, it just got accepted, so the other two can be uploaded.
>
I am looki
>
> If you have any questions, you may reply to this email.
>
Is there a new linux-latest for bpo8 as well?
Regards
Harri
Hi Romain,
On 01/31/17 08:35, Romain Francoise wrote:
>
> It is waiting for approval in the backports NEW queue, which you can
> view here:
>
> https://ftp-master.debian.org/backports-new.html
>
The source package and some *.debs for arm showed up.
Thanx very much
Harri
Hi folks,
On 01/27/17 12:48, Debian FTP Masters wrote:
> linux_4.9.2-2~bpo8+1_amd64.changes uploaded successfully to localhost
> along with the files:
> linux_4.9.2-2~bpo8+1.dsc
> linux_4.9.2-2~bpo8+1.debian.tar.xz
:
is it just me, or did this upload got lost somewhere?
I highly appreciate t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Unfortunately some of the hosts affected most by this problem are LXC
servers. They rely upon "cgroup_enable=memory swapaccount=1" on the kernel
command line, making sure that I can start containers with memory
restrictions. I have to make sure that
Hi Ben,
On 01/02/17 14:28, Ben Hutchings wrote:
>
> It's probably dpkg in a wheezy (or earlier) chroot.
>
I checked, but all LXCs and Dockers were off. AFAICT it was
some forgotten tool execed by /etc/cron.daily/dpkg. /usr/bin/dpkg
appears to be innocent, and there are no other executables with
Hi folks,
Running 4.8.11 from the backports repository for Jessie I found
this in kern.log:
Jan 1 03:00:53 dpcl082 kernel: [829504.082278] dpkg[24427] vsyscall attempted
with vsyscall=none ip:ff600400 cs:33 sp:7fff8cb7c818
ax:ff600400 si:428720 di:7fff8cb7c830
Jan 1 03:00:53 d
Hi folks,
On 12/19/2016 01:58 PM, Salvatore Bonaccorso wrote:
> Hi
>
> We intend to upload linux version 4.8.15-1 tonight or on Tuesday.
>
> The upload incorporates the upstream stable updates 4.8.12, 4.8.13,
> 4.8.14 and 4.8.15 with various bugfixes and fixed vulnerabilities
> (CVE-2016-8399, C
Package: nfs-common
Version: 1:1.2.8-9.2
rpc.svcgssd woes at boot time
-- Unit rpc-svcgssd.service has begun starting up.
Dec 13 10:04:07 dpcl064.ac.aixigo.de rpc.svcgssd[2019]: ERROR: GSS-API: error
in gss_acquire_cred(): GSS_S_FAILURE (Unspecified GSS failure. Minor code may
provide more inf
On 04/26/2016 04:05 PM, Ben Hutchings wrote:
>
> I'm guessing that you didn't built the mgag200 driver (CONFIG_DRM_MGA),
> right?
>
Of course its in, as for the official kernel.
% grep -i mga /boot/config-4.5.2
CONFIG_DRM_MGA=m
CONFIG_DRM_MGAG200=m
Would you suggest to
Without GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX I get
Apr 26 13:07:57 usbpc kernel: [ 18.245417] AES CTR mode by8 optimization
enabled
Apr 26 13:07:57 usbpc kernel: [ 18.256518] alg: No test for fips(ansi_cprng)
(fips_ansi_cprng)
Apr 26 13:07:57 usbpc kernel: [ 18.271819] fbcon: mgadrmfb (f
We can focus on 4.5.1-1, even though the regression
came up with 4.4.x.
Without GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX I get
Apr 26 13:07:57 usbpc kernel: [ 18.245417] AES CTR mode by8 optimization
enabled
Apr 26 13:07:57 usbpc kernel: [ 18.256518] alg: No test for fips(ansi_cprng)
(fips_ansi_cprng)
Apr 26 13:07:57 usbpc kernel: [ 18.271819] fbcon: mgadrmfb (f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yup.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJWoGOcAAoJEAqeKp5m04HLqk8H/RLH14ZPiDgZr1yHFCyiGEPY
46snYvavBNa2JBjYZXdwynHTRS9oWApYPTgSAdNYhYJ2Kjbr838hiH9V/5Wv030q
yVofhD1bNm7sA1ynflMXdgvvDI8RemNRpmKflG7rRBeZfOHkDxgOXYiT0wNLaoDg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: initramfs-tools
Version: 0.121
If I boot the initrd generated by the new tools, then it
exits at a busybox prompt, complaining that /bin/init
cannot be found. Of course its there.
Below are the diffs of lsinitramfs for old and new tools.
M
Hi folks,
I am running Whezzy on my NFServer and the NFS clients.
Kernel is
Linux nfs-home.example.com 3.16.0-0.bpo.4-amd64 #1 SMP Debian
3.16.7-ckt11-1~bpo70+1 (2015-06-08) x86_64 GNU/Linux
Problem: Sometimes a client cannot write to /home
via NFS anymore. The error message in kern.log on th
Since upstream provides longterm support for 3.14.x I wonder if
3.14.18 and its successors will make it into wheezy-backports?
Of course I agree that Unstable should keep pace with the new
kernel versions, but for Wheezy I would be highly interested in
a reasonably modern longterm kernel.
Thanx
Package: linux
Version: 3.14.15-2
How comes that linux_3.14.15.orig.tar.xz differs so much from
upstream? I understand that some code has to be removed due
to licensing restrictions, but shouldn't the remaining changes
be included into the quilt set?
Regards
Harri
--
To UNSUBSCRIBE, email to
Package: linux-image-3.10-0.bpo.3-amd64
Version: 3.10.11-1~bpo70+1
NFSv4 on my client froze with
nfs4_reclaim_open_state: unhandled error -10026. Zeroing state
The server (running the same kernel) showed no incident at
this time. By now I could not reproduce the problem, though.
mount o
Any news about this?
Harri
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51e25e9d.3020...@afaics.de
Package: initramfs-tools
Version: 0.110
Severity: wishlist
It would be very nice if mkinitramfs considers the kernel
module dependencies when creating the initrd. /lib/modules/\
3.8.?/modules.dep shows pretty clear that ehci-hcd depends
upon ehci-pci, for example. See #700572.
This would make ini
Hi Jonathan,
I've got a new PC in the meantime (running Squeeze and
the 3.2.x backports kernel). I am sorry, but the old PC
is running Testing now.
AFAICS the problem doesn't come up with the 3.2.x kernel.
>From my side its OK to drop this bug report.
Regards
Harri
--
To UNSUBSCRIBE, email
Package: linux-image-2.6-amd64
Version: 3.2+44
On a Lenovo T420s laptop the screen backlight is dimmed
from the power-on default to "very low" at boot time.
This happens after Grub started the kernel and while the
Loading initial ramdisk...
is shown, but before all the "usual" hardware i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: initramfs-tools
Version: 0.101
Hi folks,
I am trying to setup an encrypted logical volume to
hold the root filesystem and swap. "Hardware" a virtual PC
created using kvm. Problem: There is no password dialog
at boot time. After a minute wait
On 03/09/12 15:57, Ben Hutchings wrote:
> On Fri, 2012-03-09 at 13:30 +0100, Harald Dunkel wrote:
>> PS: I just noticed that severity is set to "normal". Sorry
>> to say, but I disagree on the severity in this case. If our
>> production environment dies after 200 day
1 - 100 of 201 matches
Mail list logo
