ck is kind of completely
broken, and I have to reboot.
Let me know what I can do to improve this bug report. Maybe
install the debug kernel?
Cheers,
Thomas Goirand (zigo)
[114704.251050] iwlwifi :6f:00.0: RF_KILL bit toggled to disable radio.
[114704.251053] iwlwifi :6f:00.0: reporting RF_K
On 4/4/20 5:42 PM, Noah Meyerhans wrote:
>> So, when I'm being asked about it, my answer from an OpenStack operator
>> point of view, is always a big "NO !". I want to be able to service my
>> compute nodes. This means being able to live-migrate the workload away,
>> otherwise, customers may
l modules we generate for 9P and VHOST_SCSI.
>
> So, I think the answer for these specific requests can be affirmative.
> The cost is small enough that if these features are useful to somebody,
> then we might as well enable them.
>
> noah
Thanks for taking the time to investigate.
+1 to what you wrote.
Cheers,
Thomas Goirand (zigo)
O !". I want to be able to service my
compute nodes. This means being able to live-migrate the workload away,
otherwise, customers may notice.
Cheers,
Thomas Goirand (zigo)
t;
> Which we will, some time soon.
>
> Ben.
>
Ben,
In such case, would you consider maintaining this tiny patch?
https://github.com/NixOS/nixpkgs/pull/61076/commits/7b77c27caa8617c82df5c5af6b9ce6ae010d7f9a
Thanks for maintaining the kernel over the years.
Cheers,
Thomas Goirand (zigo)
4.9 backport to the
> regular jessie and jessie-security suites? Are there users currently
> running jessie with Linux 4.9 and expecting to continue doing so
> through the LTS period?
By all means, YES !
Cheers,
Thomas Goirand (zigo)
ghting the fact that
Ubuntu has such a kernel for virtual machine / cloud. The thread
unfortunately went to nowhere, though if such a kernel flavor was made,
I'd happily use it. The only thing is: I do *not* have time to work on
this, and I do not intend to volunteer / commit into it myself.
Cheers,
Thomas Goirand (zigo)
ere also may be some optimization that
we could do.
Also, I don't see this happening without a prior agreement from the
kernel team (which means probably that Ben has to agree). On our side,
we could prepare a list of kernel modules that we do *not* want.
Cheers,
Thomas Goirand (zigo)
kernel flavor would be a lot of maintenance. Though
of course, as I wouldn't be the one doing it, it is not up to me to
judge the amount of work.
Could we see this happening in Debian? Please let us know your thoughts.
Cheers,
Thomas Goirand (zigo)
.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
+- Adds dh_installinit call in debian/rules
+- adds debian/init
+
+ -- Thomas Goirand z...@debian.org Thu, 11 Apr 2013 23:25:08 +0800
+
tgt (1:1.0.17-1) unstable; urgency=low
* New upstream release.
diff -Nru tgt-1.0.17/debian/control tgt-1.0.17/debian/control
--- tgt-1.0.17/debian/control
On 04/10/2013 10:49 PM, Anthony Sheetz wrote:
___
Pkg-xen-devel mailing list
pkg-xen-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel
Hi,
Could you please avoid writing a 1km long subject
Hi Ingo,
Could you please try with kernel 3.2, just to see if we have the problem
in Wheezy as well?
Cheers,
Thomas
P.S: Because your follow-up on 28 Feb, I've reassigned this bug to the
kenrel package.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of
Hi,
Not having this bug fixed, *3 years* after this bug has been filled, is
unacceptable.
If you don't have time to maintain this package, please fill an RFA. No
init script is not only annoying, it renders the package unusable in its
current state.
Thomas Goirand (zigo)
--
To UNSUBSCRIBE
@@
+tgt (1:1.0.17-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Adds an init script.
+
+ -- Thomas Goirand z...@debian.org Thu, 11 Apr 2013 23:25:08 +0800
+
tgt (1:1.0.17-1) unstable; urgency=low
* New upstream release.
diff -Nru tgt-1.0.17/debian/init.d tgt-1.0.17/debian/init.d
On Fri Apr 12 2013 01:00:12 AM CST, Ben Hutchings b...@decadent.org.uk wrote:
I don't deny that the lack of an init script is at best a nuisance,
but it certainly doesn't render the package unusable.
Right, I over-stated it.
Thomas
--
To UNSUBSCRIBE, email to
Hi,
On one of my server, I had the issue as well. I'm not sure if it's the
exact same one, but at least I fixed it.
What happened for me was that my KVM over IP was printing No signal
just right after the login prompt (eg: the rest of the boot process
seemed to not be bothered). Then I did:
On 10/01/2012 09:21 PM, Bastian Blank wrote:
Please don't top-post.
On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote:
- Unreliable Time affects all the system and can make the whole host
useless. At least for production use.
Still the system.
- Is just broken for all my 53
On 05/20/2012 10:16 AM, Ben Hutchings wrote:
Does anyone see a problem with the above, in particular points 1 and 2?
I agree with all you said (you know better than I), but what
I would really love to see would be the installer warning
people when they try to install the i386 version on a 64
. This
patch will be (or has already been?) applied upstream.
Cheers,
Thomas Goirand (zigo)
diff -u -N -r a/debian/patches/bugfix/all/ioat_unsigned_long_to_dma_addr_t.patch b/debian/patches/bugfix/all/ioat_unsigned_long_to_dma_addr_t.patch
--- a/debian/patches/bugfix/all
On 03/02/2012 04:55 PM, Bastian Blank wrote:
On Fri, Mar 02, 2012 at 01:20:17PM +0800, Thomas Goirand wrote:
Replacing BUG_ON by a WARN_ON, and adding #define DEBUG 1 on top of
dma_v2.c, my kernel booted, and I had the attached dmesg output.
Please provide /proc/interrupts from all four
On 03/01/2012 11:53 PM, Bastian Blank wrote:
On Thu, Mar 01, 2012 at 06:02:15PM +0800, Thomas Goirand wrote:
On 03/01/2012 04:55 PM, Bastian Blank wrote:
Broken ACPI table, aka firmware bug.
Do you then suggest I try upgrading my BIOS? It's the one providing the
ACPI tables, right?
Yes
On 02/20/2012 05:11 AM, Jonathan Nieder wrote:
Hi Thomas,
kernel BUG at [...]/drivers/dma/ioat/dma_v2.c:163!M
[...]
Pid: 0, comm: swapper/0 Not tainted 3.2.0-1-686-pae #1 Supermicro X8STi/X8STi
EIP: 0061:[f74df33d] EFLAGS: 00010246 CPU: 0
EIP is at __cleanup+0xd6/0x113 [ioatdma]
This is
is a Supermicro with a
X8-STi-F motherboard, which is running all on Intel chipset, so this
should be some quite common hardware, especially for servers.
Cheers,
Thomas Goirand (zigo)
[8.771014] kernel BUG at
/build/buildd-linux-2.6_3.2.6-1-i386-Ea61XL/linux-2.6-3.2.6/debian/build
On 02/01/2012 12:01 AM, micah anderson wrote:
What is stopping you from creating another package, that provides the
kernel with grsecurity patches applied? Don't bother the kernel team
with it, and just maintain it yourself in the archive? Its free software
afterall.
micah
Having such
in current SID 3.0.0?
Cheers,
Thomas Goirand (zigo)
--
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/4e426534.4080...@debian.org
Hi,
I need to clear something I'm not sure about. Will aufs continue to be
available in upstream kernel from kernel.org, or is there something new
that I should use instead?
Thomas
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
On 07/11/2011 03:06 AM, maximilian attems wrote:
On Mon, Jul 11, 2011 at 02:30:27AM +0800, Thomas Goirand wrote:
Hi,
I need to clear something I'm not sure about. Will aufs continue to be
available in upstream kernel from kernel.org, or is there something new
that I should use instead
- Original message -
CONFIG_RT2800PCI_RT33XX
CONFIG_RT2800PCI_RT35XX
CONFIG_RT2800USB_RT33XX
CONFIG_RT2800USB_RT35XX
These options currently carry the disclaimer:
| Support for these devices is non-functional at the moment and is
| intended for testers and developers.
backport
instead of the quick and dirty one that I did myself.
Thanks, and keep-up the good work,
Thomas Goirand (zigo)
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5
7.5 euros).
Cheers, and keep on the good work,
Thomas Goirand (zigo)
On 04/17/2011 12:01 PM, Thomas Goirand wrote:
On 04/16/2011 05:40 PM, Norbert Tretkowski wrote:
Hi,
yesterday I prepared a backport for linux-2.6 2.6.38-3, which works for
me, but I would like to get some feedback from
On 01/30/2011 07:13 AM, Julien Cristau wrote:
On Sat, Jan 29, 2011 at 17:32:51 +, Ian Campbell wrote:
BTW, why do we refer users to the wiki instead of including the advice
inline in the release notes? Is that just the way the release notes are
normally written?
No, if the information
- Original message -
Apparently now that there are xen-linux-system-2.6-xen-* metapackages
in Squeeze this should read something like:
We have this package in Lenny as well, but it wasn't
enough. The claim you just had it from Ian...
Thomas
--
To UNSUBSCRIBE, email to
- Original message -
On Tue, Jan 25, 2011 at 15:34:23 +, Justin B Rye wrote:
# para
# Upgrades from Lenny will not automatically install Xen version 4.0.
Instead # you need to install Xen 4.0 and a corresponding dom0 kernel
explicitly. See # the wiki page for instructions
the same order in Squeeze in order
to not break things (but that can have a lower priority than fixing the
above which is really more annoying...).
Cheers,
Thomas Goirand (zigo)
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
Ben Hutchings wrote:
On Mon, 2010-08-23 at 15:22 +0100, Ian Campbell wrote:
On Mon, 2010-08-23 at 17:11 +0300, Pasi Kärkkäinen wrote:
On Sun, Aug 22, 2010 at 01:16:20AM +0300, Pasi Kärkkäinen wrote:
On Sat, Aug 21, 2010 at 10:27:16PM +0100, Ian Campbell wrote:
On Sat, 2010-08-21 at 23:52
Bastian Blank wrote:
It would be a terrible shame if Squeeze did not have support for the
modern graphics subsystem when running Xen.
Well. All the intel cards seems to work.
Bastian
I can confirm that issues that has been reported to the xen-devel list
were only with specific cards like
Ian Campbell wrote:
On Tue, 2009-11-03 at 10:04 +0800, Thomas Goirand wrote:
as if my kernel was NOT Xen dom0 capable. But I've checked my .config,
and I did switch the correct flag(s). Also, there's a /proc/xen (but
empty). What did I miss here?
http://lists.debian.org/debian-kernel/2009
Bastian Blank wrote:
Yes. http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test.
I used to run the 2.6.26-2-xen-amd64 dom0, and it was quite fast. Since
I am using that new version, I really have the bad feeling that my
computer is A LOT slower than before. It used to be nearly as fast as
Ian Campbell wrote:
On Tue, 2009-11-03 at 19:41 +0800, Thomas Goirand wrote:
Bastian Blank wrote:
Yes. http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test.
I used to run the 2.6.26-2-xen-amd64 dom0, and it was quite fast. Since
I am using that new version, I really have the bad feeling
Bastian Blank wrote:
On Wed, Oct 28, 2009 at 02:22:49PM +0800, Thomas Goirand wrote:
Would this kernel work as a dom0 in Lenny?
No. It needs a newer hypervisor.
Can you also provide the source package so I can
recompile it with the Lenny gcc/libs?
The patch
Bastian Blank wrote:
On Tue, Oct 27, 2009 at 10:32:52PM +0100, Bastian Blank wrote:
On Tue, Oct 27, 2009 at 10:05:45PM +0100, Thomas Schwinge wrote:
Bastian, is any of your Xen dom0 work available somewhere?
Yes. http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test.
The xen utils are
dann frazier wrote:
oops - sorry, that was the wrong version. updated patches attached.
EXCELLENT! That actually seem to work!!!
Will that be included in the next Debian kernel release?
Thomas
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe.
Ben Hutchings wrote:
On Tue, Jun 16, 2009 at 12:50:34AM +0800, Thomas Goirand wrote:
[...]
So I'm wondering, did somebody applied some patches for e1000e between
the release of Lenny 5.01? Or maybe, the e1000e on the X8STi-3F is
different from the one of my Thinkpad t500? Is there even
dann frazier wrote:
95b866d e1000e: Fix incorrect debug warning
[...]
a5136e2 e1000e: allow VLAN devices to use TSO and TCP CSUM offload
I've put these individual changes in
http://womble.decadent.org.uk/tmp/e1000e-patches/ so you don't need to
use git to generate them.
Hi,
I started to
Ben Hutchings wrote:
We normally backport specific bug fixes and small changes to support new
hardware, rather than updating drivers completely. Some driver changes
will depend on core changes in the kernel.
(Lenny and a half)?
I don't know when that will be released, but it will use an
Hi there,
There's more and more e1000e hardware around these days, and I was
wondering if it was possible to have the attached patch applied to the
current kernel of Lenny. This patch, I made it by taking the sources
from 2.6.27 and back porting it. I tested it, and my ethernet e1000e was
seen
Hi,
You guys are talking about crashes at 6:26. Amazingly, the cron.daily is
by default at exactly this time. Can you guys past here an ls of what is
in your /etc/cron.daily?
I have to say that we have quite a large number of Xen servers (as we do
VPS hosting in 10 locations), all upgraded to
Hi,
I have a thinkpad t500. On it, the stock Lenny 2.6.26 kernel doesn't
recognize my e1000e eth0, when it works perfectly with 2.6.27. So I
began to work on a backport of the driver. The PCI id is in the list, so
it's not only about this.
The resulting patch is attached to this email. It's
Goswin von Brederlow wrote:
Thomas Goirand [EMAIL PROTECTED] writes:
Goswin von Brederlow wrote:
The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
can be installed and they are incompatible with each other. If each
one contained /usr/lib/python/xen then the packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Goswin von Brederlow wrote:
The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
can be installed and they are incompatible with each other. If each
one contained /usr/lib/python/xen then the packages would have to
conflict.
I
and other images.
Best regards and thanks for this work,
Thomas Goirand
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.17.7
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
52 matches
Mail list logo
