Source: linux
Version: 3.16.0-4
Followup-For: Bug #758870
I have investigated further and determined that /sbin/request-key never gets
called
(I intercepted calls to /sbin/request-key which a program which first logs and
it didn't
even get triggered once despite using NFSv4, in this with
Note that the id mapping issue is not actually caused by the wrong arg
count. The wrong arg count appears to be harmless (no effect). The id
mapping was failing because the nfs server being accessed was in fact
using the wrong domain name.
Regards,
Daniel
--
To UNSUBSCRIBE, email to
Package: nfs-common
Version: 1:1.2.8-6
Severity: normal
idmapd does not work (fails to use correct domain depsite configure in
idmap.conf) because
/etc/request-key.d/id_resolver.conf has incorrect number of arguments. Syslog
says:
Aug 2 22:19:04 host nfsidmap[29796]: Bad arg count. Check
Package: src:linux
Version: 3.11.8-1~bpo70+1
Severity: normal
There is a regression in 3.11.8-1~bpo70+1 compared to current wheezy 3.2.
Using macvtap in 3.11 bpo hard hangs the system. The module loads fine, but
when I actually start a qemu-kvm session that uses macvtap in virt-manager the
Hi,
I just thought I'd let you know that the issue appears to occur only
rarely now, even without jumbo frames (which I had to disable because of
communicating to a target host through a router that doesn't support
jumbo frames).
Regards,
Daniel
--
To UNSUBSCRIBE, email to
Source: linux
Version: 3.2.0-4-amd64
Severity: normal
Tags: upstream
I have an ASUS M5A97 R2.0 Motherboard which a build realtek gigabit NIC.
It hangs (at least) when there is significant amounts of traffic (e.g.
accessing large files on a web server on the machine). It doesn't
matter if the
Because of the reassembled fragments I decided to try an experiments. I
enabled Jumbo frames on the other side (the Windows 8) machine's driver
(an r8168 incidentally) and set the MTU to 9000 on the local host. So
far this fixes the issues with the Windows 8 hosts. I am not sure of the
effects
Package: src:linux
Version: 3.2.35-2
Severity: important
I am running Debian Wheezy inside a libvirt-bin qemu-kvm virtual machine
(running on a Debian Wheezy host) and have noticed that the virtio balloon
driver is not working.
I have the initial allocation set to 512MB and allow up to 4096MB
Requested output below:
On Tue, 16 Aug 2011 20:51:32 +0200
Laurent Pinchart laurent.pinch...@ideasonboard.com wrote:
Hi Jonathan and Daniel,
On Sunday 14 August 2011 18:31:31 Jonathan Nieder wrote:
Daniel Dickinson wrote[1]:
New in 3.0.0:
webcam oopses and then spams syslog
Package: linux-2.6
Version: 3.0.0-1
Severity: normal
New in 3.0.0:
webcam oopses and then spams syslog. Didn't happen in .39 so is a regression.
uvcvideo: Found UVC 1.00 device HP Webcam-101 (0bda:58e0)
From syslog:
Aug 13 18:47:23 henryj kernel: [ 428.117889] Linux video capture
On Sat, 1 May 2010 23:08:54 +0200
Moritz Muehlenhoff j...@inutil.org wrote:
On Wed, Feb 25, 2009 at 08:43:10PM -0500, Daniel Dickinson wrote:
In response to your query; I don't have the Logitech mouse anymore
but I just tested and Microsoft mice don't work so it probably is
still
In response to your query; I don't have the Logitech mouse anymore but
I just tested and Microsoft mice don't work so it probably is still not
working for any serial mice.
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of the afternoon to sniff
On Thu, 25 Dec 2008 23:20:05 +0100
Moritz Muehlenhoff j...@inutil.org wrote:
Does this error still occur with more recent kernel versions?
I will try later this week.
Regards,
Daniel
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of the
The motherboard the exhibited the problem is no longer in my
possession, therefore I have no means of testing the situation.
Regards,
Daniel
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of the afternoon to sniff fragrant tea-roses or
strangle
Hi,
This is the second bug of mine you have closed for which the submitter
works (else I wouldn't know about this message) but for which you
closed the bug because of submitter bouncing. Please stop doing that.
The BTS has a command that lets you change your submitter address when
you email
Hi,
You closed the bug report because the submitter address bounced, but
the submitter address had been updated to a working email address not
the one you used. Nonetheless I have update once again, to my newest
address (although the one that was there was still valid namely
csh...@fionavar.ca ;
On Sat, 06 Sep 2008 08:09:03 +
[EMAIL PROTECTED] (Debian Bug Tracking System) wrote:
This is an automatic notification regarding your Bug report
which was filed against the linux-2.6 package:
#498013: [linux-2.6] Syslog reports Error: Driver 'pcspkr' is already
registered, aborting...
Package: linux-2.6
Severity: minor
--- Please enter the report below this line. ---
I don't know that this means much but:
Sep 3 21:13:20 brennin kernel: [ 55.143002] input: PC Speaker
as /class/input/input3
Sep 3 21:13:20 brennin kernel: [ 55.216724]
Error: Driver 'pcspkr' is already
On Wed, 16 Jul 2008 10:57:44 +0200
maximilian attems [EMAIL PROTECTED] wrote:
On Tue, 15 Jul 2008, Daniel Dickinson wrote:
Package: linux-image-2.6.25-2-686
Version: 2.6.25-6
Followup-For: Bug #490903
I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2
boots
On Thu, 31 Jul 2008 09:26:52 +0200
maximilian attems [EMAIL PROTECTED] wrote:
could you please report upstream on bugzilla.kernel.org
the debian kernel has no scsi specific patches.
and let us know the upstream bug number.
Kernel Bugzilla #11194
--
And that's my crabbing done for the day.
Hi,
Sorry for the delay. My internet has been down for a while and won't
be back until at least Wednesday. I am unable to the the .26 kernel
until then, but I do know that it is not the scanner because I have
had to boot using .24 because even with the scanner removed I get the
kernel
Package: linux-image-2.6.25-2-686
Version: 2.6.25-6
Severity: important
I just attempted to upgrade to 2.6.25-2-686 and discovered that if .25 were
released as is, I'd be unable to use debian on this system. The kernel panics
during boot. It happens after entering cryptsetup password and
Package: linux-image-2.6.25-2-686
Version: 2.6.25-6
Followup-For: Bug #490903
I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2 boots
sucessfully in that configuration with the megaraid. I suspect it is the
SCSI-2 scanner as a non-RAID device on channel 2 that is confusing
On Tue, 8 Jul 2008 09:15:14 +0200
maximilian attems [EMAIL PROTECTED] wrote:
When a new stable *is* uploaded, D-I should be able to switch
faster too (at least, if there's someone willing to do the initial
kernel-wedge work) as the main criterium for D-I to switch to a new
kernel
Package: linux-2.6
Version: 2.6.18 through 2.6.24 (latest versions in etch and lenny as of now)
Severity: normal
On a Toshiba Satellite 1800 laptop it is impossible to reboot the
system. When the system says Restarting system now (e.g. when the
software reset is being issued, after all the
Package: linux-2.6
Version: 2.6.18
Followup-For: Bug #479094
For 2.6.24 I tried loading the apm module (with the apci=off)
(including adding it to the initramfs), and loading apmd but had no
better luck than before.
All other acpi functions work correctly.
Shutdown works fine.
I don't
On Sat, 19 Jan 2008 01:36:10 +0100
Jonas Meurer [EMAIL PROTECTED] wrote:
On 20/12/2007 Daniel Dickinson wrote:
The system then reports on megaraid logical disks (appearing as
sda, sdb) and then hangs (but responds to keyboard and reboots
with Ctrl-Alt-Del)
Maks: if the disks do
Hi,
I just wanted to make sure that someone on debian-kernel who can look into
this bug sees it. If already so, please forgive me.
Also, what's the best way to make sure the new list sees a bug when the bug is
reassigned (I reassigned this bug).
Regards,
Daniel
--
And that's my crabbing
On Thursday 20 December 2007 08:35, David Härdeman wrote:
Daniel said in the BR:
Installation succeeded however on reboot the encrypted LVM partition
was not activated. The messages during startup (after install), were:
Setting up cryptographic volume sdb1_crypt (based on /dev/sdb1)
On Tuesday 18 December 2007 04:24, Frans Pop wrote:
On Tuesday 18 December 2007, Daniel Dickinson wrote:
I have just tried to make this (LVM on crypto partition on top of real
hardware RAID) work by doing an Etch install (which works) and then
dist-upgrading to lenny. That doesn't work
According to
http://dri.freedesktop.org/wiki/ATI?highlight=%28CategoryHardware%29
The Radeon seems to have problems with certain early VIA chipsets. Your best
bet is to try and see if it works.
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of
According to
http://dri.freedesktop.org/wiki/ATI?highlight=%28CategoryHardware%29
The Radeon seems to have problems with certain early VIA chipsets. Your best
bet is to try and see if it works.
--
And that's my crabbing done for the day. Got it out of the way early,
now I have the rest of
Package: linux-2.6
Version: 2.6.22-4
Severity: normal
Default operation of xserver fails because DRI locks system (disabling
DRI works). This is probably because the video card in question (a Radeon
8500 LE / Radeon R200 QL) is not detected by the kernel drm module.
This card worked on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
maximilian attems wrote:
On Mon, 28 Aug 2006, Daniel Dickinson wrote:
On a system that works with 2.6.16-2-k7_2.6.16-18 upgrading to
2.6.17-2-k7_2.6.17-7 results in a system for which the mouse (a
Logitech TrackMan) is flaky (jumps around
Package: linux-image-2.6.17-2-k7
Version: 2.6.17-7
Severity: important
On a system that works with 2.6.16-2-k7_2.6.16-18 upgrading to
2.6.17-2-k7_2.6.17-7 results in a system for which the mouse (a
Logitech TrackMan) is flaky (jumps around on the screen) and which
feels sluggish (perhaps just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mdadm version is 1.9.0-4sarge1
Output of mdadm --examine --scan is,
ARRAY /dev/md0 level=raid1 num-devices=3
UUID=183e8bbf:4b7a95cd:f5b4be0c:3fe0c682
devices=/dev/hdc1,/dev/hdb1,/dev/hda1 ARRAY /dev/md1 level=raid5
num-devices=3
Package: initramfs-tools
Version: 0.73c
Severity: important
Upgrading initramfs (when package in testing changed) resulted in
non-booting system. I managed to fix things by adding a script to
init-premount that activates (mdam -assemble's) the raid5 device
(/dev/md1) that contains my root
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have append=console=tty0 console=ttyS0,115200 in my quik.conf and
booting bombs out with:
pmac_zilog: 0.6 (Benjamin Herrenschmidt [EMAIL PROTECTED])
pmac_zilog: Error registering serial device, disabling pmac_zilog.
pmac_zilog: Did another serial
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following are the same for kernel 2.6.16-2-powerpc 2.6.16-16 and
2.6.17-1-powerpc 2.6.17-3 - I tried to get around #364637 (pmac_zilog
serial conflict when using a serial console) but was unsuccessful, so
the following is hand-copied:
TCP: Hash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please ignore the last message; It
a) should have gone to control, and
b) It is unconfirmed (the success may have been with 2.6.15).
Must be less quick with bts...
- --
And that's my crabbing done for the day. Got it out of the way early,
now I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity important
thanks
This, apparently, does not affect all systems, therefore, while it
limits my ability to test etch (after reboot), it is not
severity grave.
- --
And that's my crabbing done for the day. Got it out of the way early,
now I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought it was fixed because after a reinstall using stable, then
adding 2.6.15, 2.6.15 failed to boot, but upgrading initramfs-tools
fixed things. I mistakenly concluded that was the same bug as was
affecting 2.6.16, which is not the case.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have confirmed that this is required to successfully boot oldworld
mac after the install completes and am ready to make use of the
updated kernel, so if you could add the /proc/device-tree (openfirmware
device tree) to the miboot kernel it would be
Package: linux-image-2.6.16-2-powerpc
Version: 2.6.16-14
Severity: important
quik writes to whatever input-device and output-device are
configured in open firmware. Unfortunately for many old world macs
(including mine), this defaults to the ttya (/dev/ttyS0) which means
all the user sees is a
Package: linux-image-2.6-powerpc-miboot
Severity: important
In order to fix the bug which prevents quik-installer in
debian-installer from working, I need /proc/device-tree. The module
for this was removed from the miBoot floppies, but is on the other
types of install (cd, hd-media, etc).
With
Package: initramfs-tools
Version: 0.60
Followup-For: Bug #362816
As the previous reporter reported, linux-image-2.6.15 and
initramfs-tools 0.60 results in a non-booting system on some hardware.
In my case I need the ide-generic module, which wasn't being loaded.
I switched to yaird and my
Package: linux-image-2.6.15-1-486
Version: 2.6.15-8
Severity: normal
Using the mousedev module doesn't work with sermouse, for my mouse (the
mouse is not detected, as evidenced by udev not create a new
/dev/input/mouse0 when modprobe sermouse is performed, and X loading,
but with a frozen
Package: kernel-image-2.6.8-1-386
Version: 2.6.8-10
Severity: critical
File: kernel-image-2.6.8
Justification: breaks unrelated software
The USB controller on my board doesn't work with 2.6.8 but does with
2.6.10. I've called this critical but you may only consider it grave
sicne not too many
48 matches
Mail list logo
