Bug#925919: (no subject)

2019-03-30 Thread Jan Wagner
Hi, we've seen this with the following errors on several VMWare systems: Mar 28 13:58:13 mail kernel: [26002.992114] general protection fault: [#1] SMP Mar 28 07:03:46 sigten kernel: [ 1251.757467] BUG: Bad page map in process apache2 pte:2c303a2236706f70 pmd:7afb5067 Mar 28 07:03:46 sigte

Re: Re: Uploading linux (3.2.60-1)

2014-07-09 Thread Jan Wagner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, Am 09.07.14 20:29, schrieb Ben Hutchings: > On Wed, 2014-07-09 at 18:59 +0100, Adam D. Barratt wrote: >> The upload has since had some wider exposure as a result of being >> used as the basis for a security release. In the process, a few >>

Bug#754173: Re: The same problem on i386

2014-07-09 Thread Jan Wagner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.07.14 19:27, schrieb Jan Wagner: > Am 09.07.14 06:13, schrieb Kiss Gabor (Bitman): >> The situation is the same on a totally different hardware. > >> Traffic of Windows clients drastically degraded through the >> firew

Bug#754173: The same problem on i386

2014-07-09 Thread Jan Wagner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.07.14 06:13, schrieb Kiss Gabor (Bitman): > The situation is the same on a totally different hardware. > > Traffic of Windows clients drastically degraded through the > firewall. We had to downgrade package > linux-image-3.2.0-4-686-pae:i386 fro

Bug#701744: fixed in linux 3.2.46-1+deb7u1

2013-09-03 Thread Jan Wagner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 03.09.2013 16:57, schrieb dann frazier: > On Tue, Sep 03, 2013 at 11:04:25AM +0200, Jan Wagner wrote: >> as we are facing this also massively on squeeze, is there a >> chance to get that also fixed there, even when this

Bug#701744: fixed in linux 3.2.46-1+deb7u1

2013-09-03 Thread Jan Wagner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, Am 01.09.13 23:47, schrieb dann frazier: > Source: linux Source-Version: 3.2.46-1+deb7u1 > > We believe that the bug you reported is fixed in the latest version > of linux, which is due to be installed in the Debian FTP archive. as we are

Bug#619317: linux-image-2.6.32-5-xen-686: booting via hypervisor slows bootup significant (hang) and also slow on runtime

2011-04-06 Thread Jan Wagner
On Monday, 28. March 2011, Jan Wagner wrote: > On Saturday 26 March 2011 12:11:04 you wrote: > > On Tuesday, 22. March 2011, you wrote: > > > Booting linux-image-2.6.32-5-xen-686 via hypervisor gets hanging > > > (several) init scripts. This seems to "workaround

Bug#619317: linux-image-2.6.32-5-xen-686: booting via hypervisor slows bootup significant (hang) and also slow on runtime

2011-03-28 Thread Jan Wagner
On Saturday 26 March 2011 12:11:04 you wrote: > On Tuesday, 22. March 2011, you wrote: > > Booting linux-image-2.6.32-5-xen-686 via hypervisor gets hanging > > (several) init scripts. This seems to "workaround" with generating input > > on stdin when the init script hangs. Video of bootup is also >

Bug#619317: linux-image-2.6.32-5-xen-686: booting via hypervisor slows bootup significant (hang) and also slow on runtime

2011-03-26 Thread Jan Wagner
On Tuesday, 22. March 2011, you wrote: > Booting linux-image-2.6.32-5-xen-686 via hypervisor gets hanging (several) > init scripts. This seems to "workaround" with generating input on stdin > when the init script hangs. Video of bootup is also available[1]. It looks like “max_cstate=1″ did fix the

Bug#602109: Acknowledgement ([linux-2.6] 1 multicall(s) failed: cpu 0)

2010-12-06 Thread Jan Wagner
Hi Ian, On Monday 06 December 2010 11:10:40 Ian Campbell wrote: > On Fri, 2010-12-03 at 18:57 +0100, Jan Wagner wrote: > > On Friday, 3. December 2010, Ben Hutchings wrote: > > > It is probably filtered out of syslog because it has a low priority > > > level. 

Bug#602109: Acknowledgement ([linux-2.6] 1 multicall(s) failed: cpu 0)

2010-12-04 Thread Jan Wagner
Hi Ben, On Samstag, 4. Dezember 2010, you wrote: > Module loading is serialised by a lock. Because the 'oops' occurs > during module loading, the locks is never released and no more modules > can be loaded. So we don't need to worry about that - it's just a > symptom of the initial 'oops'. > >

Bug#602109: Acknowledgement ([linux-2.6] 1 multicall(s) failed: cpu 0)

2010-12-03 Thread Jan Wagner
Hi Ben, thanks for your reply. On Friday 03 December 2010 06:29:56 Ben Hutchings wrote: > On Thu, 2010-12-02 at 22:00 +0100, Jan Wagner wrote: > Please can you log information about the state of tasks by running: > > echo t > /proc/sysrq-trigger > > then send the mess

Bug#602109: Acknowledgement ([linux-2.6] 1 multicall(s) failed: cpu 0)

2010-12-02 Thread Jan Wagner
Hi there, today I updated to linux-image-2.6.32-bpo.5-xen-686 2.6.32-28~bpo50+1 and recognized that I have a couple of modprobe processes still running after booting: root 966 0.2 0.0 2308 800 ?Shttp://lists.debian.org/201012022200.43301.w...@cyconet.org

Bug#522922: test build available

2009-11-23 Thread Jan Wagner
On Wednesday, 18. November 2009, you wrote: > I made test on HP DL160 G6 and works without problem. Please add support > for this NIC in next official release of kernel package. maybe you could also consider the solution from http://blog.waja.info/2009/11/18/dkms-rocks/ With kind regards, Jan. -

Re: Accepted linux-2.6.24 2.6.24-5~etchnhalf.1 (source all i386)

2008-04-09 Thread Jan Wagner
Hi there, since this kernel will hit etch, maybe all of our users with this kernel will also be effected by #426224? With kind regards, Jan. P.S. Sorry for crossposting, but there are a couple of packages involved. -- Never write mail to <[EMAIL PROTECTED]>, you have been warned! -BEGIN GEE

Bug#417278: Failed to symbolic-link boot/initrd.img-2.6.18-4-686 to initrd.img.

2007-04-02 Thread Jan Wagner
On Monday 02 April 2007 13:41, maximilian attems wrote: > On Mon, Apr 02, 2007 at 01:25:19PM +0200, Jan Wagner wrote: > > On Monday 02 April 2007 12:54, you wrote: > > > On Mon, Apr 02, 2007 at 10:58:56AM +0200, Jan Wagner wrote: > > > > "rm /initrd.img /vmlinu

Bug#417278: Failed to symbolic-link boot/initrd.img-2.6.18-4-686 to initrd.img.

2007-04-02 Thread Jan Wagner
On Monday 02 April 2007 12:54, you wrote: > On Mon, Apr 02, 2007 at 10:58:56AM +0200, Jan Wagner wrote: > > "rm /initrd.img /vmlinuz" fixed it for me, but it seems no general > > solution. > > never saw that error, please try to reprduce: > apt-get --reinstall in

Bug#417278: Failed to symbolic-link boot/initrd.img-2.6.18-4-686 to initrd.img.

2007-04-02 Thread Jan Wagner
The previous package version was: 2.6.18.dfsg.1-11 With kind regards, Jan. -- Never write mail to <[EMAIL PROTECTED]>, you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT d-- s+: a- C+++ UL P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G

Bug#417278: Failed to symbolic-link boot/initrd.img-2.6.18-4-686 to initrd.img.

2007-04-02 Thread Jan Wagner
Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12 Severity: serious --- Please enter the report below this line. --- Latest kernel package does not install correctly: # LANG=C aptitude upgrade Reading package lists... Done Building dependency tree... Done Reading extended state inform

Bug#368308: linux-image-2.6.16-1-686: kernel Oops when trying to use ov511

2007-01-11 Thread Jan Wagner
On Thursday 11 January 2007 10:59, you wrote: > does linux image 2.6.18 work? hi max, it works well here with linux-image-2.6.18-3-686 (2.6.18-7). you could close the bug. thanks, jan. -- Never write mail to <[EMAIL PROTECTED]>, you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.

Bug#386497: Workaround

2006-09-21 Thread Jan Wagner
"# echo '8250_pnp' > /etc/hotplug/blacklist.d/8250_pnp" did work around the problem. With kind regards, Jan. -- -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a- C+++ UL P+ L+++ E- W+++ N+++ o++ K++ w--- O M-- V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++ -

Bug#368308: linux-image-2.6.16-1-686: kernel Oops when trying to use ov511

2006-05-21 Thread Jan Wagner
Package: linux-image-2.6.16-1-686 Version: 2.6.16-12 Severity: important -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Lo