Steve Cotton writes:
> I'd like to revert the "found 681418 3.8.5-1~experimental.1",
> and close the bug again.
sure, please go ahead. Sorry for the confusion.
-Timo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
Steve Cotton writes:
> For me the mount point changes permission when mounted, and from the hard
> link count I guess you have it unmounted.
>
> tsunami:~# umount /sys/kernel/debug/
> tsunami:~# ls -ld /sys/kernel/debug/
> drwxr-xr-x 2 root root 0 Jul 30 13:08 /sys/kernel/debug/
> tsunami:~# moun
package src:linux
reopen 681418
found 681418 3.8.5-1~experimental.1
thanks
Hi,
the issue still exists in experimental
lindi3:~$ ls -ld /sys/kernel/debug
drwxr-xr-x 2 root root 0 May 5 12:02 /sys/kernel/debug
lindi3:~$ cat /proc/version
Linux version 3.8-trunk-amd64 (debian-kernel@lists.debian.
Ben Hutchings writes:
> We have a longstanding support problem where there is confusion between
> the kernel release string (utsname::release, output of uname -r, tail of
> package names) and the kernel package version.
Agreed.
> Would anyone like to argue in favour of any particular alternative
Hi,
it seems 3.7.3-1~experimental.1 still lacks CONFIG_UPROBES. I'd like to
know if there is something I could do to help. Systemtap would greatly
benefit.
-Timo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
Julien Cristau writes:
> What's your hypervisor? You need one with xz support, see 695056.
xen-hypervisor-4.0-amd64 4.0.1-5.5
I guess we could try upgrading the dom0 to testing (wheezy) in a
non-production environment but that'll take several weeks at least.
--
To UNSUBSCRIBE, email to debia
Package: src:linux
Version: 3.7.3-1~experimental.1
Severity: normal
With the following configuration the kernel fails to boot as xen domU:
pyGRUB version 0.6
┌┐
│ Debian GNU/Linux, with Linux 3.7-trunk-amd64
Package: src:linux
Version: 3.5.5-1~experimental.1
Severity: wishlist
CONFIG_UPROBES lets systemtap place probes on user code just like
kprobes lets it to do with kernel code. Support was merged mainline in
3.5. Please consider enabling this option.
commit 654443e20dfc0617231f28a07c96a979ee1a023
Hi,
I seem to have hit the same bug again with 2.6.32-38 domU (amd64). After
I rebooted dom0 to 2.6.32-41 I see that the jiffies value of the domU
does not increase but cpu_time in xm list -l output does. Value of
"last_value" seems to increase (now around 1804512135271).
I looked at linux-source
package linux-2.6
notfound 637234 3.0.0-3
found 637234 3.1.0-1~experimental.1
found 637234 3.1.1-1
found 637234 3.1.8-2
found 637234 3.2.4-1
thanks
dom0
amd64 squeeze with
Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-39) (da...@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu
Roberto Dal Zilio writes:
> On the xenserver I do not have a crashdump because the VM does not
> crash
Can you delibaretly crash it to obtain such a dump? The stuck processes
would still be visible in the dump.
> (I only get the task hang and the error in dmesg on the VM). Is it
> helpfull for y
Hi,
Roberto Dal Zilio writes:
> [904313.840676] updatedb.mloc D 880001855c40 0 14983 14979
> 0x
> [904313.840684] 880001855c40 0282 000800017880
> 8800032f5810
> [904313.840693] f9e0
> 88002cf2dfd8
> [904
Hi Frank and Ritesh,
>> The last module unloaded was generated by SystemTap.
> There is much more information needed from the submitter, regardless.
I didn't get your email. Please remember to Cc:
633535-submit...@bugs.debian.org or the emails won't reach the submitter
of the bug.
> - What was
Package: linux-2.6
Version: 2.6.32-34squeeze1
Severity: normal
I was playing around with ptrace when I got the following kernel oops. I
do not know if this is related to use of ptrace or not.
[1131224.792749] alignment check: [#1] SMP
[1131224.792761] last sysfs file: /sys/devices/vbd-51712
Package: linux-2.6
Version: 2.6.32-34squeeze1
Severity: wishlist
kexec, kdump and crash are pretty powerful debugging tools. It would be
nice if debian kernels supported kdump fully. If I read
/usr/share/doc/kdump-tools/README.Debian correctly this would involve
enabling CONFIG_CRASH_DUMP=y.
I co
maximilian attems writes:
> as I didn't want to continue my 1 hour search for an eventual PS/2 mouse,
> and eventual combinations of the two.
> I just applied your patch without the check to the branch timo/panic
Thanks!
-Timo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.or
USB modules are not normally loaded at break=top time but since USB
keyboards are very common we should take the effort to try to load
extra kernel modules at break (=panic) time. This patch closes #615831
and has been adapted from comments mentioned in
https://bugs.launchpad.net/ubuntu/+source/in
Loading a kernel module can crash the system so it is useful that the
user sees which module might be causing trouble.
---
scripts/functions |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/functions b/scripts/functions
index 9b961d2..0a02f04 100644
--- a/scripts
Hi,
maximilian attems writes:
>> cat: /sys/class/input/input*/device/description: No such file or directory
>
> yep that is the case for usb keyboard, so you can check no existence of that.
aha, good idea. I'll send new patches against git HEAD.
I built these with git-buildpackage and tested th
maximilian attems writes:
> now the only thing that is holding me up to merge your patch is that
> /proc/bus/input/devices usage, there should be some sysfs file, no?
>
>
> cat /sys/class/input/input*/device/description shows a KBD
Unfortunately it does not show a keyboard here:
root@metunconf:~
Package: initramfs-tools
Version: 0.98.8
Severity: normal
Description
===
On a network booting machine with
oper@watt:~$ zcat /boot/initrd.img-2.6.32-5-amd64 | cpio -i --to-stdout
lib/udev/rules.d/70-persistent-net.rules
# lindi: ethernet port #1 (BIOS boots using this)
SUBSYSTEM=="net"
Package: linux-2.6
Version: 2.6.32-30
Severity: minor
While trying to debug chromium-browser build failures on my sheevaplug I
attached gdb to a running "ld.bfd" process. After some time I got a
kernel panic and had to use JTAG to read the dmesg from memory.
The dmesg is attached. I don't expect
Hi,
I can also reproduce the issue with 2.6.32-33:
overlord3:~$ sudo xm dmesg
(XEN) Xen version 4.0.1 (Debian 4.0.1-2) (wa...@debian.org) (gcc version 4.4.5
(Debian 4.4.5-10) ) Wed Jan 12 14:04:06 UTC 2011
(XEN) Bootloader: GRUB 1.98+20100804-14
(XEN) Command line: placeholder
(XEN) Video inform
maximilian attems writes:
>> +try_modprobe()
> I'd prefer the function to be named modprobe_verbose()
Ok.
>> +try_modprobe atkbd
> why not using "-v" from modprobe,
> the only argument against that would count is busybox support.
> please check?
I'm not very familiar with busybox internals
Package: linux-2.6
Version: 2.6.32-30
Severity: normal
I keep hitting this oops maybe once a week when browsing with
chromium-browser.
I have symlinked ~/.config/chromium and ~/.cache/chromium to
/dev/shm/lindi since the internal SSD of my aspire one laptop is so
slow. I do not know if this has a
Michal Suchanek writes:
> Can't use an USB keyboard when I boot with init=/bin/sh.
This is related to bug #615831.
--
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.o
m...@linux.it (Marco d'Itri) writes:
> My only request is that the loading in panic() of *every* module is
> preceded by printing on the console an appropriate debug message
> containing the module name, because loading the module could cause an
> oops.
Ok. I reworked this a bit and resent with
g
/initramfs-tools/+bug/229732
and tested on a HP ProLiant MicroServer that lacks a PS2 port
completely.
Signed-off-by: Timo Juhani Lindfors
diff --git a/scripts/functions b/scripts/functions
index af49e45..3c95b55 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -37,6 +37,20
Loading a kernel can crash the system so it is useful that the user
sees which module might be causing trouble.
Signed-off-by: Timo Juhani Lindfors
diff --git a/scripts/functions b/scripts/functions
index 579696a..af49e45 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -31,6 +31,12
USB modules are not normally loaded at break=top time but since USB
keyboards are very common we should take the effort to try to load
extra kernel modules at break (=panic) time. This patch closes #615831
and has been adapted from comments mentioned in
https://bugs.launchpad.net/ubuntu/+source/in
Package: initramfs-tools
Version: 0.98.8
Severity: normal
Steps to reproduce:
1) connect usb keyboard
2) boot with break=top
Expected results:
2) "(initramfs)" prompt that responds to user input
Actual results:
2) "(initramfs)" prompt that does not respond to user input
More info:
1) This happe
The purpose of panic= is to make the system reboot automatically on
panic but also give the interactive user some time to see what went
wrong.
Signed-off-by: Timo Juhani Lindfors
diff --git a/scripts/functions b/scripts/functions
index 2280ba2..025001f 100644
--- a/scripts/functions
+++ b
ic= he/she can get break= debugging to
work.
Signed-off-by: Timo Juhani Lindfors
diff --git a/scripts/functions b/scripts/functions
index 025001f..579696a 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -40,6 +40,7 @@ panic()
echo "$@"
# Disallow console ac
ow...@bugs.debian.org (Debian Bug Tracking System) writes:
> The source is added by
>
> debian/patches/bugfix/all/firmware-pcmcia-cs-CIS-source-and-copyright.patch
whoa! Thanks. I don't understand why I missed that.
-Timo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with
Package: firmware-linux-free
Version: 2.6.32-30
Severity: wishlist
Just out of curiosity went through all the files
/lib/firmware/cis/NE2K.cis
/lib/firmware/cis/3CCFEM556.cis
/lib/firmware/cis/COMpad2.cis
/lib/firmware/cis/PE-200.cis
/lib/firmware/cis/MT5634ZLX.cis
/lib/firmware/cis/RS-COM-2P.cis
Ben Hutchings writes:
> It's a kernel feature to be more efficient when running in a recognised
> virtual machine implementation (PV = paravirtualisation).
thanks. I think it is the following code from vmi_32.c:
/*
* Apply patch if appropriate, return length of new instruction
* sequence. The
Bastian Blank writes:
> Maybe this could be used to enable the possibility to do limited
> debugging on all images without emiting too much preasure on the
> buildd/archive.
Probably not a bad idea. However, such partially debuggable kernels
should be marked clearly. It is not nice to spend weeks
Ben Hutchings writes:
> The backend drivers have not yet been merged, so it's not yet very
> useful as dom0.
ok. Is there still hope that they will get merged before wheezy is
released or would now be a good time to start looking at KVM migration
plans?
--
To UNSUBSCRIBE, email to debian-kerne
Ben Hutchings writes:
> Note that the OpenVZ, VServer and Xen flavours have been dropped and
> will not come back.
Does this mean that it would be a good day to start testing the dom0
support of plain 2.6.37 to make sure regressions will be minimal? (I
am assuming 2.6.37 does support dom0 now).
Ben Hutchings writes:
> Which version of qemu are you using in the host? If you are using
> kvm-qemu, which kernel version are you using in the host?
The host is a xen domU:
lindi1:~$ qemu-system-x86_64 --version
QEMU PC emulator version 0.12.5 (Debian 0.12.5+dfsg-3), Copyright (c) 2003-2008
F
Package: linux-2.6
Version: 2.6.32-30
Severity: normal
Sometimes when I use
shutdown -r now
under qemu I get a general protection fault:
<6>[ 103.542142] e1000 :00:03.0: PCI INT A disabled
<0>[ 103.543710] Restarting system.
<4>[ 103.543772] machine restart
<0>[ 103.544118] general prot
Ronny Standtke writes:
> Just boot the DVD in your home machine, the installer starts up automatically
> and makes producing a Debian Live USB flash drive a breeze. Then you can test
> on any machine that can boot from USB.
Well I don't have any DVDs and the cdrom drive is not easily
accessible
Philip Ashmore writes:
> What I really meant was your hardware device info.
$ lspci
00:00.0 Host bridge: ATI Technologies Inc RD890 Northbridge only single slot
PCI-e GFX Hydra part (rev 02)
00:04.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express
gpp port D)
00:06.0 PCI br
Peter Viskup writes:
> 'xm block-attach phy:data/disk /dev/xvda6 w'
I can attach a block device
$ sudo xm block-attach 27 file:/local/xen/lindi-exp1/disk.img /dev/xvda w
$ sudo xm block-list 27
Vdev BE handle state evt-ch ring-ref BE-path
51712 00 4 9 770 /local/domain/0/
Ben Hutchings writes:
> I do check for blobs in each new upstream version but apparently I
> missed this one.
Thanks a lot for your work. Are you using the same deblob script or is
there some heuristics used for new versions?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debia
Package: linux-source-2.6.37
Version: 2.6.37-1~experimental.1
Severity: serious
drivers/staging/ft1000/ft1000-pcmcia/boot.h seems to contain firmware
in binary form. Is the source code available somewhere?
(This is the only blob I could find with
http://www.linux-libre.fsfla.org/pub/linux-libre/r
yellow writes:
> Package: nfs-kernel-server
> Version: 1:1.2.2-4
> Severity: normal
>
> For the clients to mount their /home, I need to do :
Jikes, that sounds scary. How often do you need to restart it? Can
you make it happen more often if you mount/remount in a loop?
--
To UNSUBSCRIBE,
package linux-2.6
retitle 608858 copying large file with smbd on raid causes BUG at
fs/jbd/transaction.c:1156
thanks
Gregg writes:
> [1393760.788377] EXT3-fs error (device dm-5): ext3_valid_block_bitmap:
> Invalid block bitmap - block_group = 1229, block = 40271874
> [1393760.788779] --
package linux-2.6
retitle 608858 copying large file with smbd on raid causes BUG at
fs/jbd/transaction.c:1156
thanks
[resending via smtp.academica.fi since smtp.netsonic.fi does not seem
to be delivering my emails any time soon...]
Gregg writes:
> [1393760.788377] EXT3-fs error (device dm-5): e
Ronny Standtke writes:
> I just tested it. Booting the DVD ISO in qemu took more than 20 minutes to
> get
How much RAM did you assign to the virtualized machine? I think the
default is 128MB.
> I did not experience the system hang in this one single qemu test run (I also
> do not run into the
Hi,
thanks for your report. I get the same behavior:
overlord3:~$ sudo modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.32-5-xen-amd64/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko):
No such device
overlord3:~$ dpkg-query -W linux-image-$(uname -r)
linux-image-2.
Ronny Standtke writes:
> I can confirm this bug.
> I created a Debian Live system based on Squeeze and on many machines the
> system just hangs when shutting down.
>
> My latest test was on a Dell Optiplex SX280. I will attach the entries in
> kern.log and the output of lspci on this system.
ok
Grzegorz Wyrobek writes:
> So I'm looking forward to fix this bug.
> We are going to make test ISO tomorrow for you.
If the ISO includes non-free nvidia drivers then I don't think I want
to test it either. Are you creating them with live-helper?
--
To UNSUBSCRIBE, email to debian-kernel-requ
Philip Ashmore writes:
> I'd recommend also attaching your hardware information, or trying it
Not sure how much this matters under xen really but the cpuinfo in dom0 has
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 10
model name : AMD Phenom(tm)
Giuseppe Sacco writes:
> This is dom0 hosting a windows machine.
Ok, then I'm afraid I can't help much. I know only about debugging
domU'ss and not dom0's.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
gring...@poczta.onet.pl writes:
> Dec 7 12:16:26 wokanda1 kernel: [ 24.817488] [] ?
> aufs_fault+0xf1/0xfb [aufs]
Hmm, how are you using aufs? (I have never used it so I don't even
know how to set it up to test anything...)
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.
Peter Viskup writes:
> Execution of xm block-attach to PV domU failed and I have got Ooops
> kernel messages in attachment.
Can you tell me the exact block-attach command so that I can at least
test that it works with squeeze? (I doubt it can be fixed for lenny.)
--
To UNSUBSCRIBE, email to
Giuseppe Sacco writes:
> Package: linux-image-2.6.32-5-xen-686
> Version: 2.6.32-27
> Severity: important
Are you running this as a dom0 or domU? You don't need to use a
"-xen-" kernel as a domU.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscri
Peter Viskup writes:
> I want to run official Debian stable versions.
I understand that perfectly. However, it is not likely that this can
be fixed for 2.6.26 -- the best thing you can do about this problem is
to ensure that it gets fixed before squeeze is released.
> Just find there is backport
Peter Viskup writes:
> Package: linux-image-2.6-xen-amd64
> Version: 2.6.26+17+lenny1
Can you try linux-image-2.6.32-5-xen-amd64 2.6.32-29 from debian
squeeze? You probably should be able to install it to a lenny system
without upgrading the system otherwise.
--
To UNSUBSCRIBE, email to deb
Ian Campbell writes:
> Just to clarify, since the recent messages are not completely clear on
> the details, we think that with the 2.6.32-29 package reboot works fine
> for both 32 and 64 bit domU and dom0?
Yes. It seems the failed reboot of 32-bit domUs was due to
[2010-12-14 13:01:45 2071] ER
Richard Mittendorfer writes:
>> > Did you try with an updated dom0 kernel as well?
64bit dom0 seems to shutdown and reboot properly.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http:/
Richard Mittendorfer writes:
> Did you try with an updated dom0 kernel as well? Don't have 32bit
> guests here, neither gave debian 2.6.32-29 a try yet.
Reboot seems to work with a 64bit guest:
squeeze64:~# dmesg|head -n4
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializ
Hi,
at least on a 32-bit domU, 2.6.32-29 seems to break reboot
completely. The guest just disappears as if it had called halt
instead:
overlord2:~$ cat /local/xen/squeeze32/config
name = 'squeeze32'
bootloader = '/usr/bin/pygrub'
vcpus = '4'
memory = '512'
disk = [ 'file:/local/xen/squeeze32/disk
Ben Hutchings writes:
> Since perf doesn't use any of the functionality in libssl via Python,
> I'm not convinced there's a problem here.
Good. Would it be appropriate to describe this in copyright file
though?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject
Ben Hutchings writes:
> I have no idea what the upstream developers intended, they seem a bit
> clueless about distribution. I only just realised that they try to use
> libbfd (GPLv3, incompatible) even though perf can get the same
> functionality from libiberty (GPLv2)!
Hmm, are you planning to
Package: linux-tools-2.6.36
Version: 2.6.36-1~experimental.1
Severity: serious
/usr/share/doc/linux-tools-2.6.36/copyright gives me the impression
that we have a license to distribute /usr/bin/perf_2.6.36 only under
the terms of the GPLv2. Is this correct?
It seems that perf_2.6.36 uses openssl:
Ian Campbell writes:
> My ping at http://marc.info/?l=linux-kernel&m=128879080525214&w=2 went
> unanswered but Jeremy picked it up again at
> http://marc.info/?l=linux-kernel&m=129045702011984&w=2 and it seems to
> have gone into the tip.git tree (in x86/urgent) but not to Linus yet.
Ok thanks. I
Ian Campbell writes:
> On Wed, 2010-11-03 at 13:23 +0200, Timo Juhani Lindfors wrote:
>> http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html
>
> Thanks, I've pinged upstream to see if this patch will be applied and
> also requested that it gets tagged
I can reproduce the problem. The guest never really quits:
squeeze64:~# dpkg-query -W linux-image-$(uname -r)
linux-image-2.6.32-5-amd64 2.6.32-28
squeeze64:~# halt
Broadcast message from r...@squeeze64 (hvc0) (Tue Nov 30 13:02:53 2010):
The system is going down for system halt NOW!
INIT:
Richard Mittendorfer writes:
> Version: 2.6.32-28
> likely https://lkml.org/lkml/2010/11/26/197
Does this mean that you tested 2.6.32-27 and that works?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
Marcel Langner writes:
> Does a report exists for this transmit timeout problem already?
I don't know. I have hit the issue only twice and it is difficult to
debug so I did not report it yet.
> No I have not. Do you think it makes sense to try it? It's a long time
> since I compiled my own kerne
Marcel Langner writes:
> Bug seems to exist for a long time now. Should be fixed before Squeeze
> gets out officially!
1) Are the "scheduling while atomic" and "transmit timed out"
different bugs?
2) Have you tried if this occurs with mainline kernel from kernel.org?
I have a geode box with
$
Christoph Anton Mitterer writes:
> Unfortunately it turned out, that my ISP had to but that respective
> cluster into production now, and was therefore not longer able to play
> around very much.
That's unfortunate. Do they advertise support for hosting debian in a
xen publicly?
--
To UNSUBS
Ian Campbell writes:
> The version of xen-utils-common may also have some bearing on this since
> it is the package which provides /lib/udev/rules.d/xend.rules
Here in working case I have
$ dpkg-query -W xen*
xen-hypervisor-amd64
xen-linux-system-2.6.32-5+bug580889.1-xen-amd64
xen-tools
xen-util
"George B." writes:
> Nov 22 10:03:19 deli kernel: [12673.102822] [] ?
> mousedev_destroy+0xe/0x2c
Just to narrow things down. Does this occur if you
1) login using ssh from another computer
2) stop Xorg
3) sudo rmmod psmouse usbhid hid
?
If yes, is just loading one of these modules enough
Ben Hutchings writes:
> On Mon, 2010-11-15 at 12:55 +0200, Timo Juhani Lindfors wrote:
>> Ben Hutchings writes:
>> > However, the same applies to several other package names that change
>> > with the upstream version number: linux-source-,
>> > linux-doc-
Jason Kendall writes:
> Which kernel do you have on this client - what are your NFS mount
> options for this directory?
linux-image-2.6.32-5-amd64 2.6.32-27
nfs:/home /home nfs
rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.7
Jason Kendall writes:
> 1. All the scripts/commands should be run on the client.
> 2. As far as I can tell, you can't just move the directory, you have to move
> each file, but again, I was able to trigger it with just the process of
> making the files.
> 3. Most of the time there is no difference
Holger Levsen writes:
>> This is a test on the Kirkwood machine:
>>
>>
>> r...@dockstar:/srv/tftp# md5sum systemrescuecd-x86-1.6.2.iso
>> b7662eb44b530d62c487dd367f2036ed systemrescuecd-x86-1.6.2.iso
>> r...@dockstar:/srv/tftp# uname -a
>> Linux dockstar.lab.elconas.de 2.6.32-5-kirkwood #1 S
You meantion SCHED_IDLE only in the subject but don't elaborate it in
the bug report itself. What do you mean by it exactly?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.d
With
$ dpkg-query -W linux-image-$(uname -r)
linux-image-2.6.32-5-xen-amd64 2.6.32-27
I see
$ find /dev|grep evt
/dev/.udev/db/misc:xen/evtchn
/dev/xen/evtchn
Does everything work if you create evtchn manually with mknod
/dev/xen/evtchn c 10 57?
--
To UNSUBSCRIBE, email to debian-kernel-
Kind of hard to debug without console output indeed. Does the kernel
boot without xen? Have you tried 2.6.32-27?
--
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/84s
Hi,
it would be useful to know
sudo brctl show
sudo xm info
sudo xm list
lsmod
dpkg-query -W linux-image-$(uname -r)
on dom0 when you have no networking and
sudo ip link
lsmod
dpkg-query -W linux-image-$(uname -r)
on domU when you have no networking.
With squeeze dom0 and domU on amd64 at lea
Hmm. So you are running an X server in the dom0 or in a domU?
--
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/8462vvnkp0@sauna.l.org
Works for me.
In the following ceasar and lindi1 are nfs clients, lindi1 is a domU
with 2.6.32-27 and nova is an nfs server with 2.6.26+17+lenny1:
nova:~$ ssh caesar bash -c "'for i in \$(seq 1 1); do touch tmp/\$i; done'"
nova:~$ ssh lindi1 ls tmp | sort | uniq -d
nova:~$ ssh caesar mv tmp/
masterdead writes:
> Package: linux-image-2.6.26-2-amd64
> Version: 2.6.26-25
> Severity: important
What hardware do you have? Especially disks, raid/lvm/crypto
configuration would be important. Is there any kind of virtualization
involved?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@l
Artur Linhart writes:
> If the kernel is used for paravirtual DomU, then the DomU is
> normally started orshutdown. Ifthe xm save and xm restore is invoked
> explicitely,then the DomU also restores normally. Only in the case
> the DomU is restored automatically via xendomains script facility on
>
Ben Hutchings writes:
> However, the same applies to several other package names that change
> with the upstream version number: linux-source-,
> linux-doc-, linux-manual- and
> linux-patch-debian-. I think perhaps we should remove those
> with wildcards as well.
Sure, should I send a new patch
Angelo Pantano writes:
> since I cannot dump a core if the machine has already crashed I dumped
> it right after launching the migration command
I'm afraid that dump is not going to be very useful. There must be a
way to trigger dumping on crash?
--
To UNSUBSCRIBE, email to debian-kernel-requ
Christoph Anton Mitterer writes:
> Package: linux-image-2.6.32-5-amd64
> Version: 2.6.32-27
> Severity: important
Can you also attach the output of "xm info" from the dom0 to the bug
report? 2.6.32-27 boots here as a domU just fine when I also use
2.6.32-27 as a dom0 :-)
--
To UNSUBSCRIBE, em
Christoph Anton Mitterer writes:
> If you need any further help or so, please ask. My great ISP (Star-Hosting)
> is very
> cooperative and they'll probably give me a test system for some time, if we
> need it.
Thanks for reporting this bug. Can you please save the save the state
of the hung dom
Hi,
Google finds the same crash at
http://www.chiark.greenend.org.uk/~xensrcts/logs/2449/test-amd64-amd64-pair/guest-debian.guest.osstest-console
which is apparently some sort of testsuite log. It says that the
version was 28a160746815. Then in the same directory hierarchy I found
that the first
Hi,
it seems that if I debuild the linux-2.6 package multiple times in a
row and increment the version number it does not remove the old
debian/linux-support-* directories.
Is there some reason why it is not removed on clean? If not, would the
attached patch be ok?
Index: linux-2.6/debian/rules
Angelo Pantano writes:
> if there is anything else we can provide let us know
> regards
Just in case the problem becomes hard to reproduce you probably want
to save the state of the crashed child with
xm dump-core
If you have lots of private data you obviously can not share that dump
but we m
Hi,
while struggling with various kernel bugs[1] this year I had to do a
lot of rebuilds to test patches. I wanted proper source packages that
I can share from my private debian repository and also wanted
-headers, -dbg and -source binary packages. Most importantly I wanted
proper changelog entrie
package linux-image-2.6.32-5-686-bigmem
tags 602273 patch
thanks
The patch from
http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html
seems to help! Please consider applying this to debian.
For completeness, here's the patch from the email archive (probably
messes up whitespace
package linux-image-2.6.32-5-686-bigmem
found 602273 2.6.32-27
thanks
This issue looks a lot like
"[Xen-devel] DomU clock jumps forward then freezes after Dom0 reboot"
http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00498.html
and
"[Xen-devel] Migrated domUs hangs"
http://lists.xe
Package: linux-image-2.6.32-5-686-bigmem
Version: 2.6.32-26
Severity: normal
Steps to reproduce:
1) use 64-bit squeeze as dom0
2) use 32-bit squeeze as domU
3) reboot dom0
Expected results:
3) domU's state is saved to disk and then restored
Actual results:
2) domU's state is saved to disk but it
Hi,
now that I know that the issue is related to interrupts I found
http://kerneltrap.org/mailarchive/linux-kernel/2010/8/24/4610615
with google. I'll test if applying this patch fixes the problem for
me.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "
1 - 100 of 122 matches
Mail list logo
