Package: src:linux
Version: 3.2.51-1
Severity: normal
Hello,
I am seeing the backtrace below in my kernel log after the system has been
running for several weeks.
Looks like it has something to do with Xen - memory leak maybe?
Thanks,
George
-- Package-specific info:
** Version:
Linux versi
> On Mon, Dec 16, 2013 at 09:41:56AM +, George B. wrote:
> > Package: src:linux
> > Version: 3.2.51-1
> > Severity: normal
> >
> > Hello,
> >
> > I am seeing the backtrace below in my kernel log after the system has
> been running for several week
> From: Jonathan Nieder
>
> Closing due to lack of response. :/ But please don't hesitate to write
> if you have more information, and we can pick this up again.
Sorry, I somehow missed the information request e-mail... :-(
Anyway the problem has gone away a long time ago after some kernel
upda
> 1. Install 2.6.32-27 from http://snapshot.debian.org/, keeping all
> other packages the same, and check if it still reproduces the
> problem. (It might not, if X was involved.)
I ran 2.6.32-27 for a few days and couldn't reproduce the problem any more.
FWIW the environment has changed s
it to
compile. I know that there is some sort of variable I could pass when
building, but I could not get that to work bor some reason.
2) Get it to build with 4.0 :-p
HTH,
George B.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'uns
On 8/17/05, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>
> The 2.4.27-11 uploaded today depends on gcc-3.3 and should solve that
> problem. (It is not yet installed in the archive but available from
> http://packages.vergenet.net/pending/ )
:-)
Will it automatically use gcc-3.3 when compiling? With
On 8/18/05, Horms <[EMAIL PROTECTED]> wrote:
>
>
> Yes, it should do just that.
Sorry, which one? Automatically use gcc-3.3, or default to gcc-4.0?
On 8/19/05, Horms <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 18, 2005 at 01:05:10PM +0100, George B. wrote:
> > On 8/18/05, Horms <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Yes, it should do just that.
> >
> > Sorry, which one? Automatica
mem
---
The initial DMA error messages appear now and again, and seem to be
harmless (but also PM related) then it all goes wrong after a few weeks
running. :-(
I will be happy to privide more specific information, if you tell me
how to get it. I don't really know much about hardware/kernel debu
ive in it before,
that displayed similar symptoms. Thinking the disk was dying I swapped
it, only to have the problem come back. (The 3.5" drive is being
happily used by my brother now, with no problems whatsoever.)
Also, 3 out of 3 is a bit high failure rate...
George B.
On 27/10/05, Horms <[EMAIL PROTECTED]> wrote:
>
> Ok, that does sound like fair resoning, though I should
> say that almost always these kind of errors show up faulty hardware.
> In this case, its probably a bug.
Don't get me wrong, I think may well be faulty hardware, but a general
fault rather t
On 01/11/05, Horms <[EMAIL PROTECTED]> wrote:
> Is there any chance that #336103 is related to this?
>
> http://bugs.debian.org/336103
Hmm, don't think so. In my case I had no trouble turning DMA on (in
fact, I disabled it yesterday with hdparm just to see if it would make
any difference - it will
P.S. I could try unloading the ide-generic module etc. if you think
that's a good idea.
I think I finally fixed the problem by installing the apmd package. :-\
The problem was, I am guessing, that the hard drive went to sleep at
some random time (despite it being explicitly told not to in the BIOS)
and regardless of the disk activity (so even my 15 min dd cronjob did
not fix it) and
Source: firmware-nonfree
Severity: grave
Justification: renders package unusable
Hello,
The binary packages generated from this source have not been avaiable in
Sid for at least one day now.
E.g. https://packages.debian.org/unstable/firmware-iwlwifi
Thanks,
George
-- System Information:
Debi
Just to let you know that the 'fix' did not work. :-(
The hard drives will still randomly go to sleep and not wake up.
What's more, even a sysrq forced reboot does not wake the drive up -
only a cold boot works!
The end result is that we are gradually replacing these crappy disks
in our firewalls
** [init/main.o] Error 1
make[1]: Leaving directory `/usr/src/kernel-source-2.4.27'
make: *** [stamp-build] Error 2
---
A attach my kernel .config file.
HTH,
George B.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable&#
, I think you misunderstood. It's just that I am running an older
version of 2.4.27 kernel that has security issues (which is why I was
upgrading.) ;-)
HTH,
George B.
On 04/09/06, Eito Tamura <[EMAIL PROTECTED]> wrote:
Hi George,
I am having the same problem as you did. So installing ampd package didn't
fix the problem?
Just those crappy HDD problem? Upgrading kernel might fix this problem?
Hello,
The problem is still there, although it does not occur ver
c1 10 0f 85 d9 14 00 00 eb 2a f6 c4 08 74 25 8b 41
70 83 fa 06 <8b> 98 48 01 00 00 74 07 83 fa 0b 75 12 eb 09 89 ca e8 b9 fc ff
Sep 14 14:37:20 dxsfw-dc01 kernel: EIP: []
bond_netdev_event+0x67/0x8b [bonding] SS:ESP 0068:ee997ec0
---
HTH,
George B.
-- System Information:
Debian Relea
On 14/09/06, maximilian attems <[EMAIL PROTECTED]> wrote:
blaeh, please try to reproduce with current trunk:
http://wiki.debian.org/DebianKernel
Any one in particular (2.6.17 or the 2.6.18 RC builds)?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Con
On 15/09/06, maximilian attems <[EMAIL PROTECTED]> wrote:
On Thu, 14 Sep 2006, George B. wrote:
> On 14/09/06, maximilian attems <[EMAIL PROTECTED]> wrote:
> >
> >blaeh, please try to reproduce with current trunk:
> >http://wiki.debian.org/DebianKernel
Package: linux-image-2.6.26-1-686
Version: 2.6.26-2
Severity: important
Hello,
I got an Oops message (see below) when I plugged in a Belkin 54g USB wireless
network adapter. Looks like upstream is aware of the problem, but I'm reporting
this here so you can track this.
http://lkml.org/lkml/200
Package: linux-image-2.6-686
Version: 2.6.30+21
Severity: grave
Justification: renders package unusable
Hello,
Package currently depends on linux-image-2.6.31-1-686 that is not available.
Dependency information needs to be updated?
This has been broken for at least a week now.
Thanks,
Georg
Uwe Kleine-König wrote:
I'm sure you intended to write
Version: 2.6.31+22
here?
Probably. I was lazy and copied and pasted from
http://packages.debian.org/sid/linux-image-2.6-686
The problem is that the package hangs in the new queue that isn't
handled at the moment.
Thanks for
2008/11/29 Moritz Muehlenhoff <[EMAIL PROTECTED]>:
> George, did you report that bug upstream?
Hi Mortiz,
I don't think I submitted a bug upstream (I think I may have had some
problems, but I can't remember now). Since then, I've changed jobs
twice, so I no longer have access to that hardware.
I
Package: linux-image-2.6-686
Version: 2.6.32+28
Severity: important
Hello,
I am getting regular oopses again from the kernel after returning from
hibernation - this used to work without issue for some time before.
>From syslog:
---
Nov 22 10:03:19 deli kernel: [12670.808315] firewire_core: red
27 matches
Mail list logo
