Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-11
Severity: important
Hi,
I'm running kernel 2.6.18-4-amd64 on a FujitsuSiemens RX 400 computer,
equipped with 8 GB RAM. The computer is used as our file server and
unfortunately, it crashed two times this week with the following kernel
On Thu, Mar 15, 2007 at 02:32:29PM -0600, dann frazier wrote:
According to policy 5.6.3:
List of the names and email addresses of co-maintainers of the
package, if any. If the package has other maintainers beside the one
named in the Maintainer field, their names and email addresses
On Fri, Mar 16, 2007 at 09:09:48AM +0100, Sven Luther wrote:
So, Frans has the right to speak here, while i have not ?
Frans' message was on topic and useful, while you were basically
telling him to shut up, which is neither on topic nor useful. Do you
see the difference?
Greetings
Marc
--
On Fri, Mar 16, 2007 at 09:15:55AM +0100, Sven Luther wrote:
So, will you try to expulse him too, like Frederik and Andres did to me ?
Can you please take your personal vendettas from this technical
mailing list? Both Bastian and you are difficult to work with, but in
different dimensions.
On Fri, Mar 16, 2007 at 09:43:03AM +0100, Marc Haber wrote:
On Fri, Mar 16, 2007 at 09:09:48AM +0100, Sven Luther wrote:
So, Frans has the right to speak here, while i have not ?
Frans' message was on topic and useful, while you were basically
telling him to shut up, which is neither on
On Fri, Mar 16, 2007 at 10:00:48AM +0100, Sven Luther wrote:
So, i played nice, to no avail, so i will try to be an asshole for a week or
two now, and see how people like it.
Welcome to my killfile. Congratulations, this is a real achivement.
Greetings
Marc
--
forcemerge 398470 415112
tags 398470 +patch
tags 398470 +security
tags 398470 serious
retitle 398470 key serial number collision (CVE-2007-0006)
thanks
Severity serious since bugs causing kernel Oopses with CVE number and
patches available are IMHO nothing a stable release should ship with.
cu
Processing commands for [EMAIL PROTECTED]:
forcemerge 398470 415112
Bug#398470: 2.6.18: mysterious, possibly race-y oops in key/keyring code
Bug#415112: linux-image-2.6.18-4-amd64: kernel oops in keyring_destroy
Mismatch - only Bugs in the same package can be forcibly merged:
Bug 415112 is not
On Fri, Mar 16, 2007 at 09:15:55AM +0100, Sven Luther wrote:
I do agree with this interpretation. I also think it's really sad that
we have to invoke policy to regulate the use of the Uploaders field.
There is no reason whatsoever (other than Bastian's anti-social
tendencies) to keep
Processing commands for [EMAIL PROTECTED]:
reassign 415112 linux-2.6
Bug#415112: linux-image-2.6.18-4-amd64: kernel oops in keyring_destroy
Bug reassigned from package `linux-image-2.6.18-4-amd64' to `linux-2.6'.
severity 398470 serious
Bug#398470: key serial number collision (CVE-2007-0006)
Processing commands for [EMAIL PROTECTED]:
# the following bugs are closed by packages in NEW
#
tags 382675 pending
Bug#382675: rm scripts not removing /var/lib/usplash
There were no tags set.
Tags added: pending
tags 397970 pending
Bug#397970: usplash: New upstream package available
There
On Fri, Mar 16, 2007 at 12:18:13PM +0200, Jurij Smakov wrote:
On Fri, Mar 16, 2007 at 09:15:55AM +0100, Sven Luther wrote:
I do agree with this interpretation. I also think it's really sad that
we have to invoke policy to regulate the use of the Uploaders field.
There is no reason
A big international company with great experience and potential is looking for
assistants of manager because of growing of its business.
We provide different services for our clients, which are absolutely unique and
valuable too.
We will be happy to see you in our team if you fit our
On Fri, Mar 16, 2007 at 02:19:11AM +0100, Frans Pop wrote:
On Thursday 15 March 2007 21:32, dann frazier wrote:
Given this, I believe anyone on the kernel team should be permitted an
entry in the Uploaders field. I also do not believe that the presence
of a maintainer's name in the
I just found http://oss.sgi.com/archives/xfs/2007-03/msg00078.html
which is another XFS problem on NSLU2. Apparently it's because of a
miscompilation in XFS on ARM. I'll confirm with the XFS developers
whether your problem may be caused by this too after reproducing it on
another ARM machine,
* Martin Michlmayr [EMAIL PROTECTED] [20070316 21:24]:
I just found http://oss.sgi.com/archives/xfs/2007-03/msg00078.html
which is another XFS problem on NSLU2. Apparently it's because of a
miscompilation in XFS on ARM. I'll confirm with the XFS developers
whether your problem may be caused
Processing commands for [EMAIL PROTECTED]:
tags 398470 + pending
Bug#398470: key serial number collision (CVE-2007-0006)
Tags were: security patch
Bug#415112: linux-image-2.6.18-4-amd64: kernel oops in keyring_destroy
Tags added: pending
End of message, stopping processing here.
Please
17 matches
Mail list logo
