Processing commands for cont...@bugs.debian.org:
reassign 566116 linux-image-2.6.32-trunk-686
Bug #566116 [linux] dosemu: Cannot access CIFS shares
Warning: Unknown package 'linux'
Bug reassigned from package 'linux' to 'linux-image-2.6.32-trunk-686'.
Bug No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
reassign 566116 linux-2.6 2.6.32-3
Bug #566116 [linux-image-2.6.32-trunk-686] dosemu: Cannot access CIFS shares
Bug reassigned from package 'linux-image-2.6.32-trunk-686' to 'linux-2.6'.
Bug No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
reopen 561880
Bug #561880 {Done: Ryan Niebur ryanrya...@gmail.com} [linux-2.6]
inotify/hppa: Not assigning sequential ids as expected
severity 561880 normal
Bug #561880 [linux-2.6] inotify/hppa: Not assigning sequential ids as expected
Severity
Hi, ALL
I'm sorry that I've report a untrue bug. I've replug the touchpad jump in the
mainboad, and the touchpad works fine today. Please close this bug. Thanks!
I apologize one again for my mistake.
Thanks~
--
Liang Guo
http://bluestone.cublog.cn
--
To UNSUBSCRIBE, email to
Processing commands for cont...@bugs.debian.org:
# submitter acknowledged as hardware problem, now fixed
close 565977
Bug#565977: [linux-2.6] touchpad not woks severail minutes after X startup
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further
Hi there, I had some problem updating due to udev asking for a new
kernel. Is there one coming down into squeeze, or what have I missed?
Thank you,
-- Forwarded message --
From: Kai Hendry hen...@webconverger.com
Date: 2010/1/20
Subject: udev 2.6.26
To: supp...@bitfolk.com
Hi
hibernation (suspend2disk) does also not work.
Black screen after he loads the image from the disk.
By the way, i use kde4 menu to suspend etc.
I think kde is using pm-utils to do that.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
hen...@webconverger.com wrote:
Hi there, I had some problem updating due to udev asking for a new
kernel. Is there one coming down into squeeze, or what have I missed?
I do not expect dom0 support in testing soon.
Somebody should rebuild the lenny xen kernel without
CONFIG_SYSFS_DEPRECATED.
--
JY == Jie Yang jie.y...@atheros.com writes:
Have you tested NFS over TCP? The block-size the application
uses can have an effect on this. What application did you
use? Block-size?
JY yes, I tested NFS over TCP.
One strange observation is that I can only reproduce this problem when
Processing commands for cont...@bugs.debian.org:
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #479652 (http://bugs.debian.org/479652)
# *
Processing commands for cont...@bugs.debian.org:
reassign 414287 udev 0.125-7+lenny3
Bug #414287 [linux-2.6] udev: renames eth5 to eth5_rename_ren
Bug reassigned from package 'linux-2.6' to 'udev'.
Bug #414287 [udev] udev: renames eth5 to eth5_rename_ren
Bug Marked as found in versions
reassign 414287 udev 0.125-7+lenny3
tags 414287 + patch
thanks
On Thu, May 21, 2009 at 10:50:51PM +0100, Daniel Pocock wrote:
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
In case it's of any use to anyone reading this, I have a system which
was experiencing hangs of this nature:
[862971.676821] INFO: task apache2:29156 blocked for more than 120 seconds
every week or too. The dom0 kernel is current 2.6.26-2-xen-amd64 and the
domU kernel was current
Package: initramfs-tools
Version: 0.93.4
Severity: critical
Justification: breaks the whole system
I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system over
the new kernel. I still can boot it from the old 2.6.26 kernel.
My root disk is on a mirror raid based on 2 SCSI
Package: linux-image-2.6.26-2-486
Version: 2.6.26-19lenny2
Severity: critical
Justification: breaks the whole system
After upgrading linux-image-2.6.26-2-486 from 17lenny1 to 19lenny2, I
started experiencing 100% reproducable system lockups on a VIA C7
system. No errors in the logs, no oops, no
also sprach Louis Richard Pirlet lrpir...@gmail.com [2010.01.22.0952 +1300]:
I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the
system over the new kernel. I still can boot it from the old
2.6.26 kernel.
My root disk is on a mirror raid based on 2 SCSI disk. The boot
process
Processing commands for cont...@bugs.debian.org:
reassign 566192 mdadm
Bug #566192 [initramfs-tools] initramfs-tools: md0 device not recognized at
boot after upgrade to kernel 2.6.30
Bug reassigned from package 'initramfs-tools' to 'mdadm'.
Bug No longer marked as found in versions
reassign 566192 mdadm
severity 566192 grave
thanks
On Thu, Jan 21, 2010 at 09:52:08PM +0100, Louis Richard Pirlet wrote:
I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system
over the new kernel. I still can boot it from the old 2.6.26 kernel.
My root disk is on a mirror
Processing commands for cont...@bugs.debian.org:
severity 566208 important
Bug #566208 [linux-image-2.6.26-2-486] linux-image-2.6.26-2-486: e_powersaver
causes constant lockups
Severity set to 'important' from 'critical'
thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
clone 566208 -1
Bug#566208: linux-image-2.6.26-2-486: e_powersaver causes constant lockups
Bug 566208 cloned as bug 566214.
reassign -1 cpufrequtils
Bug #566214 [linux-image-2.6.26-2-486] linux-image-2.6.26-2-486: e_powersaver
causes constant
On Thu, 2010-01-21 at 19:24 -0500, Ross Vandegrift wrote:
Package: linux-image-2.6.26-2-486
Version: 2.6.26-19lenny2
Severity: critical
Justification: breaks the whole system
After upgrading linux-image-2.6.26-2-486 from 17lenny1 to 19lenny2, I
started experiencing 100% reproducable system
Package: linux-2.6
Version: 2.6.32-5
Severity: important
vserver_686-bigmem is not bigmem because the bigmem config file
reference is missing in debian/rules.gen.
IOW vserver_686-bigmem=vserver_686. You can verify this in the
respective /boot/configs* of the two packages.
Adding the bigmem
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 566213 + pending
Bug #566213 [linux-2.6] linux-image-2.6.32-trunk-vserver-686-bigmem:
vserver_686-bigmem is not bigmem
Added tag(s) pending.
End of message,
On Thu, 2010-01-21 at 17:52 -0800, Bardia Behabadi wrote:
Package: linux-2.6
Version: 2.6.32-5
Severity: important
vserver_686-bigmem is not bigmem because the bigmem config file
reference is missing in debian/rules.gen.
IOW vserver_686-bigmem=vserver_686. You can verify this in the
25 matches
Mail list logo
