Package: nfs-kernel-server
Version: 1:1.3.4-6
Followup-For: Bug #971238
I have also hit the problem about how to specify nfs-server options,
which still exists in this version.
Fortunately the equivalent Ubuntu bug report
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1898778 comes up i
Package: src:linux
Version: 4.3.5-1
Severity: normal
kernel BUG in btrfs. After BUG system hung and had to be rebooted.
Feb 24 01:53:43 black vmunix: [524578.024484] [ cut here
]
Feb 24 01:53:43 black vmunix: [524578.026952] kernel BUG at
/build/linux-19r8NQ/linux-4.3.5
Package: src:linux
Version: 3.9.6-1
Severity: important
Dear Maintainer,
After "apt-get dist-upgrade" from Wheezy to Jessie, could not reboot with the
new linux 3.9 kernel. The boot appeared to stop, with the console hung,
shortly after loading the nouveau graphics driver.
The lspci info for
From reading the kernel vdso code I discovered that there is a kernel command
line option to disable vdso for 32-bit applications in the 64-bit kernel:
vdso32=0.
This fixes my problem, although I couldn't find any documentation mentioning
this option. I will suggest to the scratchbox team that
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-7
Severity: normal
I use an AMD64 Debian lenny system to develop software for the Nokia Maemo
environment. The Maemo SDK uses scratchbox to provide cross-compilation.
Until the latest lenny update, I used scratchbox, and the Maemo SDK, in a
32
Package: linux-image-2.6.22-3-amd64
Version: 2.6.22-6
Severity: important
I recently upgraded to the latest lenny kernel: 2.6.22-3-amd64. This evening,
during a period of about 40 minutes, I have had the same kernel BUG occur
5 times. The most recent two are shown in the kernel log extract belo
I have been running 2.6.22 (from unstable) for one week now and this problem
has not recurred. When will 2.6.22 make it into lenny?
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tuesday 28 August 2007 11:18, maximilian attems wrote:
> why are your reporting against that old image,
> fetch 2.6.22 from unstble.
Maks,
I run testing, not unstable. If the problem is fixed in 2.6.22 that is good
to know. If you are asking me to test out the unstable kernel to report
whe
Package: linux-image-2.6.21-2-amd64
Version: 2.6.21-6
Severity: important
My AMD64 dual core system hosts a backup disk (SATA) and every night it takes
a local backup and is also accessed over NFS by another system which writes a
backup. Every few days, the system has hung or crashed when I go
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6
Severity: normal
When running user mode linux (particularly more than one instance) uml reports
tasks failing with random segfaults. Apparently this is a symptom of a known
kernel bug: fault information pollution.
There is a patch for the kern
On Thursday 11 January 2007 10:00, maximilian attems wrote:
> On Sun, 21 May 2006, Graham Cobb wrote:
> > Package: linux-image-2.6.15-1-amd64-k8-smp
> > Version: 2.6.15-8
> > Severity: important
> >
> > I am seeing occasional overnight system hangs. At lea
Package: linux-image-2.6.16-2-amd64-k8-smp
Version: 2.6.16-17
Severity: important
During an "rm -rf" of a large directory tree, kernel logged an oops. Any
subsequent access to that disk hangs.
It is likely that a similar "rm -rf" of the same directory tree was already
in progress at the time. N
Package: linux-image-2.6.15-1-amd64-k8-smp
Version: 2.6.15-8
Severity: important
I am seeing occasional overnight system hangs. At least one has been caused
by the following kernel problem (syslog entry follows)...
May 21 01:30:39 black kernel: <3>BUG: soft lockup detected on CPU#1!
May 21 01:3
13 matches
Mail list logo
