On Friday 10 July 2009, dann frazier wrote:
Maybe the -fwrapv change?
Bingo. Makes a lot of sense too for an issue related to gcc version.
Reverting only that patch on top of -17 results in good boot too.
Gah! And it's even a known issue:
- http://bugzilla.kernel.org/show_bug.cgi?id=13012
-
Processing commands for cont...@bugs.debian.org:
tags 536354 patch
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 536354 patch
thanks
On Friday 10 July 2009, Frans Pop wrote:
On Friday 10 July 2009, dann frazier wrote:
Maybe the -fwrapv change?
Bingo. Makes a lot of sense too for an issue related to gcc version.
I've proposed the attached patch on lkml: http://lkml.org/lkml/2009/7/10/49.
From:
Processing commands for cont...@bugs.debian.org:
tags 536455 patch upstream
Bug#536455: linux-source-2.6.30: Unable to set NIC hwaddress
There were no tags set.
Tags added: patch, upstream
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
On Fri, 2009-07-10 at 09:51 +0200, Frans Pop wrote:
tags 536354 patch
thanks
On Friday 10 July 2009, Frans Pop wrote:
On Friday 10 July 2009, dann frazier wrote:
Maybe the -fwrapv change?
Bingo. Makes a lot of sense too for an issue related to gcc version.
I've proposed the
On Friday 10 July 2009, Ben Hutchings wrote:
On Fri, 2009-07-10 at 09:51 +0200, Frans Pop wrote:
On Friday 10 July 2009, Frans Pop wrote:
On Friday 10 July 2009, dann frazier wrote:
Maybe the -fwrapv change?
Bingo. Makes a lot of sense too for an issue related to gcc
version.
Your message dated Fri, 10 Jul 2009 16:46:03 +0200
with message-id 4a57542b.5040...@e-tobi.net
and subject line Fixed in 2.6.30
has caused the Debian Bug report #523424,
regarding [linux-libc-dev] header clash between linux/types.h and stdint.h
to be marked as done.
This means that you claim
We've had multiple crashes while using an external USB drive for backups
on our main file server. The stack trace is the same set of functions
as George's (not identical addresses but the same function calls; I'm
still trying to figure out how to get the picture of the stack trace
off of my cell
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-2
Severity: normal
As to be seen below, this behaviour still continues after upgrading to latest
version 2.6.30-2
- every run of nvclock results in a bunch of logfile entries complaining about
'freeing invalid
memtype'
Regards,
Edgar
--
On Fri, Jul 10, 2009 at 07:14:03PM +0200, Edgar Sippel wrote:
As to be seen below, this behaviour still continues after upgrading to latest
version 2.6.30-2
- every run of nvclock results in a bunch of logfile entries complaining
about 'freeing invalid
memtype'
This means that nvclock
On Friday 10 July 2009, Frans Pop wrote:
I've proposed the attached patch on lkml:
http://lkml.org/lkml/2009/7/10/49.
The version check in the patch was incorrect. Here's an improved version
that also allows -fwrapv for gcc 4.2.
See also the follow ups on lkml.
From: Frans Pop
This is an automated mail. These mails are sent twice a month.
For more information about these mails, refer to
http://wiki.debian.org/qa.debian.org/DdpoByMail
=== linux-2.6:
= No migration to testing for 139 days.
See http://release.debian.org/migration/testing.pl?package=linux-2.6
= Lintian
Package: linux-image-2.6.30-1-686
Version: 2.6.30-2
Severity: minor
*** Please type your report below this line ***
fit-pc2 is a small Intel-Atomm-based computer. See:
http://fit-pc2.com/wiki/index.php?title=Fit-PC2_Specifications
The system hangs on reboot. A workaround is to use 'reboot=b'
unfortunately, in the last couple weeks, i've been experiencing some issues
with some domU machines crashing on lenny xen dom0.
at some point, the domU just hangs, and xm console is unresponsive. still
able to ping the domU server, but not log in via ssh, and existing ssh
connections stop
Processing commands for cont...@bugs.debian.org:
reassign 536497 linux-image-2.6.26-2-686
Bug#536497: Apache2 become unkillable after trying to stop it
Bug reassigned from package `apache2' to `linux-image-2.6.26-2-686'.
End of message, stopping processing here.
Please contact me if you need
This looks more like a kernel bug to me
I am reassigning this to linux-image-2.6.26-2-686
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Fri, Jul 10, 2009 at 09:06:51PM +, Tzafrir Cohen wrote:
http://www.fit-pc2.com/forum/viewtopic.php?f=9t=301
Is such a patch (using CONFIG_X86_REBOOTFIXUPS=yes) acceptable?
How about a fixed bios?
Bastian
--
Violence in reality is quite different from theory.
--
On Fri, Jul 10, 2009 at 09:08:53PM +0200, Bastian Blank wrote:
Thanks for your quick response,
This means that nvclock access some address space, which have no valid
definition. As it runs with root priviledges, it may do so via /dev/mem.
Access to PCI resources is now handled via
18 matches
Mail list logo
