Bug#762838: Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace”

2014-09-26 Thread Ingo Jürgensmann
Hi! I can confirm this bug as well, but I can't confirm Kamils guess that it's related to resolving your own zone. Instead I search my logs and found this: Sep 26 08:59:37 muaddib named[31237]: success resolving 'www.kanirope.de/A' (in 'kanirope.de'?) after reducing the advertised ED NS UDP pa

Bug#701744: Xen netback regression

2013-07-03 Thread Ingo Jürgensmann
Am 04.07.2013 um 05:42 schrieb Ben Hutchings : > My understanding is that disabling scatter/gather on netfront in domU > (ethtool -K eth0 sg off) will prevent it from triggering these bugs, but > at a substantial performance impact. In practice, disabling TSO in domU > (ethtool -K eth0 tso off) s

Bug#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures

2013-02-28 Thread Ingo Jürgensmann
Am 28.02.2013 um 11:28 schrieb Ian Campbell : >> All domUs are still running the updated kernel packages (pre >> DSA-2632-1), the dom0 the downgraded kernel package. linux-image-2.6.32-5-xen-amd64 2.6.32-48squeeze1 triggered the problem within 30 mins. ;-) > When you reach a conclusion (assum

Bug#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures

2013-02-28 Thread Ingo Jürgensmann
Am 28.02.2013 um 11:28 schrieb Ian Campbell : > I am 99% positive it will turn out to be the kernel, but please do let > us know. Shortly before 18:00 today I reinstalled linux-image-2.6.32-5-xen-amd64_2.6.32-48_amd64.deb as kernel and it took only 2.5 hours to trigger the issue. The hyperviso

Bug#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures

2013-02-27 Thread Ingo Jürgensmann
Am 26.02.2013 um 19:19 schrieb Ian Campbell : > So, was the hypervisor upgrade also accompanied by a kernel update, in > either the dom0 or guest domains? If so what versions were involved and > where? Additionally to the last mail: After running two days stable with the downgraded packages, I'

Bug#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures

2013-02-26 Thread Ingo Jürgensmann
Am 26.02.2013 um 19:19 schrieb Ian Campbell : >> Since the update last weekind in stable/squeeze I'm experiencing >> problems with running Xen on amd64 and multiple domUs losing their >> network connection/VIFs. > The hypervisors involvement in the specifics of the networking is pretty > minima

Bug#700545: [drupal7] Latest security patches don't fix security warning within Drupal7 (update.module)

2013-02-23 Thread Ingo Jürgensmann
Am 23.02.2013 um 16:37 schrieb Luigi Gangitano : > 7.14-2 has just been uploaded, acknowledging your NMUs and adding the latest > security fix. Thanks to both of you for dealing with and finally fixing this issue! :-) -- Ciao...// Fon: 0381-2744150 Ingo \X/

Bug#690817: Is that bug still open?

2012-11-04 Thread Ingo Jürgensmann
Hi Gunnar, hi Luigi, hi securiy@d.o! I reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690817 on Oct. 18th and Gunnar replied quickly with a patch. Since then the last message for this bug is pending/uploaded/delayed. In the meanwhile drupal7 7.14-1.1 is in unstable. So, is that bug

Bug#646675: "out of nowhere"?

2011-10-26 Thread Ingo Jürgensmann
Am 26.10.2011 um 22:40 schrieb Vincent Bernat: > Now that the message is in another folder, you don't have the problem > any more, even if you visit this folder? Does the problem comes back if > you move the message to inbox? When I access my Debian-Devel folder the problem occurs in that fol

Bug#646675: "out of nowhere"?

2011-10-26 Thread Ingo Jürgensmann
On 26.10.2011 19:48, Vincent Bernat wrote: Ingo, you reported the bug against 0.6. Is it really the version that is affected by the problem? It seems already patched. Well, yes, I wrote the bug report on the same machine where RC is running. The message in question is most likely this one:

Bug#646675: "out of nowhere"?

2011-10-26 Thread Ingo Jürgensmann
On Wed, Oct 26, 2011 at 09:01:07AM +0200, Holger Levsen wrote: > I use roundcube with suhosin, but not 0.6 yet. What do you mean by "out of > nowhere"? Well, I was at work, enjoying a working roundcube and reading my mails and then, as far as I remember, I reloaded the Inbox and it said "Loading

Bug#646675: "out of nowhere"?

2011-10-26 Thread Ingo Jürgensmann
On 26.10.2011 09:01, Holger Levsen wrote: I use roundcube with suhosin, but not 0.6 yet. What do you mean by "out of nowhere"? Ha! Just discovered: it's working again. BUT: when I used reportbug-ng this morning to report the bug, it started iceweasel - and I use iceweasel to sort my mails i