I believe this is resolved with version 2.6.18.dfsg.1-24 of
linux-image-2.6.18-6.486:
# cat /proc/cpuinfo
processor : 0
vendor_id : unknown
cpu family : 4
model : 0
model name : 486
stepping: unknown
fdiv_bug: no
hlt_bug : no
f00f_bug
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.26etch1
> tags 514624 + pending
Bug#514624: linux-image for sparc64 sungem problems
There were no tags set.
Bug#508151: linux-image-2.6.26-1-sparc64: soft lockup when trying to bring
On Mon, Feb 09, 2009 at 07:54:24PM +, Alexander Clouter wrote:
> > Would you and/or Evgeni be able to test a 2.6.26 build to verify
> this
> > fix if I provide one?
> >
> Guess I would be then committing myself to move to lenny sooner
> rather
> than later for my co-locatin box :)
>
> Sure, why
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.26etch1
> tags 502553 + pending
Bug#502553: support new smart array controllers
Tags were: pending
Tags added: pending
>
End of message, stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.26etch1
> tags 506418 + pending
Bug#506418: linux-image-2.6.18-6-xen-amd64: domU soft lockup detected
There were no tags set.
Tags added: pending
>
End of message, stopping processi
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.26etch1
> tags 506420 + pending
Bug#506420: incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
There were no tags set.
Tags added: pending
>
End of message, stopping processi
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.26etch1
> tags 502553 + pending
Bug#502553: support new smart array controllers
There were no tags set.
Tags added: pending
>
End of message, stopping processing here.
Please conta
Your message dated Mon, 09 Feb 2009 21:35:53 +
with message-id
and subject line Bug#502553: fixed in user-mode-linux 2.6.18-1um-2etch.24
has caused the Debian Bug report #502553,
regarding support new smart array controllers
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 09 Feb 2009 21:35:40 +
with message-id
and subject line Bug#502553: fixed in linux-2.6.24 2.6.24-6~etchnhalf.8
has caused the Debian Bug report #502553,
regarding support new smart array controllers
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 09 Feb 2009 21:35:53 +
with message-id
and subject line Bug#506418: fixed in user-mode-linux 2.6.18-1um-2etch.24
has caused the Debian Bug report #506418,
regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected
to be marked as done.
This means that you cla
Your message dated Mon, 09 Feb 2009 21:35:30 +
with message-id
and subject line Bug#506418: fixed in fai-kernels 1.17+etch.24
has caused the Debian Bug report #506418,
regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected
to be marked as done.
This means that you claim that the
Your message dated Mon, 09 Feb 2009 21:35:53 +
with message-id
and subject line Bug#506420: fixed in user-mode-linux 2.6.18-1um-2etch.24
has caused the Debian Bug report #506420,
regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
to be marked as done.
This means that you cla
Your message dated Mon, 09 Feb 2009 21:35:30 +
with message-id
and subject line Bug#506420: fixed in fai-kernels 1.17+etch.24
has caused the Debian Bug report #506420,
regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
to be marked as done.
This means that you claim that the
Your message dated Mon, 09 Feb 2009 21:35:39 +
with message-id
and subject line Bug#506418: fixed in linux-2.6 2.6.18.dfsg.1-24
has caused the Debian Bug report #506418,
regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected
to be marked as done.
This means that you claim that t
Your message dated Mon, 09 Feb 2009 21:35:30 +
with message-id
and subject line Bug#502553: fixed in fai-kernels 1.17+etch.24
has caused the Debian Bug report #502553,
regarding support new smart array controllers
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Mon, 09 Feb 2009 21:35:39 +
with message-id
and subject line Bug#506420: fixed in linux-2.6 2.6.18.dfsg.1-24
has caused the Debian Bug report #506420,
regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
to be marked as done.
This means that you claim that t
Your message dated Mon, 09 Feb 2009 21:35:39 +
with message-id
and subject line Bug#502553: fixed in linux-2.6 2.6.18.dfsg.1-24
has caused the Debian Bug report #502553,
regarding support new smart array controllers
to be marked as done.
This means that you claim that the problem has been de
Installing:
linux-2.6.24_2.6.24-6~etchnhalf.8.diff.gz
to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8.diff.gz
linux-2.6.24_2.6.24-6~etchnhalf.8.dsc
to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.8.dsc
linux-doc-2.6.24_2.6.24-6~etchnhalf.8_all.deb
to pool/main/l/lin
Installing:
linux-2.6_2.6.18.dfsg.1-24.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.diff.gz
linux-2.6_2.6.18.dfsg.1-24.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-24.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-24_all.deb
to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-
On Mon, Feb 09, 2009 at 06:30:00PM -0200, Otavio Salvador wrote:
>Steve McIntyre writes:
>
><...>
>> The main focus of the meeting was how d-i builds and releases work,
>> and I think we made quite some progress on that. There are a few
>> changes that we think should be made that will help a grea
On Mon, 9 Feb 2009 11:43:45 -0700 dann frazier wrote:
> Would you and/or Evgeni be able to test a 2.6.26 build to verify this
> fix if I provide one?
I've just rebuilt 2.6.29-rc3 with the patch from
http://marc.info/?l=linux-netdev&m=123393014301523&w=2
And it brought up the interface fine.
Ther
Moritz Muehlenhoff wrote:
Does this error still occur with more recent kernel versions?
If you're running Etch, could you try to reproduce this bug
with the 2.6.24 based kernel added in 4.0r4?
http://packages.qa.debian.org/l/linux-2.6.24.html
Miritz Muehlenhoff,
Here are the results for th
Steve McIntyre writes:
<...>
> The main focus of the meeting was how d-i builds and releases work,
> and I think we made quite some progress on that. There are a few
> changes that we think should be made that will help a great deal in
> building, publishing and releasing d-i. I'm not posting any
It fails the same way with Lenny rc2 as previous versions did.
Adam
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13
Severity: normal
Documentation for temp_prefered_lft states that:
#v+
temp_prefered_lft - INTEGER
Preferred lifetime (in seconds) for temporary addresses.
Default: 86400 (1 day)
#v-
But this setting seems to be ignored:
#v+
# d
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13
Severity: normal
#v+
# dev="wire"
# ip link set $dev down
# sysctl -w net.ipv6.conf.$dev.use_tempaddr=2
net.ipv6.conf.wire.use_tempaddr = 2
# sysctl -w net.ipv6.conf.$dev.max_desync_factor=0
net.ipv6.conf.wire.max_desync_factor = 0
# sysctl -w
Hi,
this is an unknown problem. In fact it's the first time i ever got an error
report for the device. And therefore there isn't any patch.
There seems to be a usb write error. This is a diy hardware. There may
be several reasons causing such problems:
Hardware problems on the i2c-tiny-usb:
- H
Your message dated Mon, 9 Feb 2009 20:22:19 +0100
with message-id <20090209192219.gb5...@piper.oerlikon.madduck.net>
and subject line Re: Bug#446323: mdadm: recovery in infinite loop
has caused the Debian Bug report #446323,
regarding mdadm: recovery in infinite loop
to be marked as done.
This me
reassign 514624 linux-image-2.6.26-1-sparc64
forcemerge 508151 514624
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
sorry for topposting, the symbian mail client sucks ;)
but yes, i would be able to test the fix on my netra.
regards
evgeni
-- Ursprüngl. Mitteil. --
Betreff:Bug#508151: Bug#514624: linux-image for sparc64 sungem problems
Von:dann frazier
Datum: 09/02/2009 18:50
forcem
Processing commands for cont...@bugs.debian.org:
> reassign 514624 linux-image-2.6.26-1-sparc64
Bug#514624: linux-image for sparc64 sungem problems
Bug reassigned from package `linux-image-2.6.24-etchnhalf.1-sparc64' to
`linux-image-2.6.26-1-sparc64'.
> forcemerge 508151 514624
Bug#508151: linux
Hi Till and other I2C developers,
Thomas Koch, a Debian user, reported the following backtrace with
2.6.26 related to i2c and possibly related to the i2c-tiny-usb driver.
This is on an ARM device.
Do you know if this is a known issue for which a patch is available in
newer kernels, or is this a n
On Mon, Feb 09, 2009 at 10:35:40AM +0100, Holger Levsen wrote:
>Hi Otavio ;-)
>
>On Donnerstag, 5. Februar 2009, Otavio Salvador wrote:
>> I won't be at FOSDEM :(
>
>You certainly missed a lot, but you didnt miss that meeting as it didnt take
>place. (TTBOMK)
Sorry, it did. Unfortunately at a rea
On Mon, Feb 09 2009, Michael Tautschnig wrote:
> [...]
>>c. his means there will be no need for /etc/kernel-img.conf file any
>> more.
>
> [...]
>
> Isn't this file also read in the postinst of the "official" kernels?
> In FAI we had several issues when kernel-img.conf was missing or
> h
Am Dienstag 03 Februar 2009 13:47:04 schrieben Sie:
> * root [2009-02-02 08:33]:
> > [42994982.81] Unable to handle kernel paging request at virtual
> > address 692f7473
>
> Can you please tell us more: when does this happen, how often, how
> reliably can you reproduce this problem, etc?
Hel
Hi Till and other I2C developers,
Thomas Koch, a Debian user, reported the following backtrace with
2.6.26 related to i2c and possibly related to the i2c-tiny-usb driver.
This is on an ARM device.
Do you know if this is a known issue for which a patch is available in
newer kernels, or is this a n
Package: linux-image-2.6.24-etchnhalf.1-sparc64
Version: 2.6.24+13~etchnhalf.1
For some time, even since 2.6.18 we have had problems with the sungem
NIC driver on our Sun Netra T1 AC200[1] where the machine is prone to
locking up.
Then recently this month on the LKML someone posted[2] that they
Package: linux-modules-extra-2.6
Severity: wishlist
Tags: patch
Please add batman-adv modules to autobuilt modules. The current version of the
package is currently in the new queue due to a source package split.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.28.1
Debian
Sven Eckelmann wrote:
> Please add batman-adv modules to autobuilt modules. The current version of the
> package is currently in the new queue due to a source package split.
please ping again when lenny is released *and* your source package has
made it into unstable, thanks.
--
Address:D
On Mon, 2009-02-09 at 01:21 -0800, David Miller wrote:
> No, I would have said that if time is tight at least we can use
> "fbdev" as the Xorg driver for PCI devices on sparc until we have a
> better fix for Xorg.
We can probably do that for r1.
Cheers,
Julien
--
To UNSUBSCRIBE, email to debi
Hi
On Montag, 9. Februar 2009, Michael Tautschnig wrote:
> [...]
> >c. his means there will be no need for /etc/kernel-img.conf file any
> > more.
>
> [...]
>
> Isn't this file also read in the postinst of the "official" kernels? In FAI we
> had several issues when kernel-img.conf was
On Mon, Feb 09, 2009 at 12:59:41AM +, Ben Hutchings wrote:
> On Fri, 2009-02-06 at 14:42 +0100, maximilian attems wrote:
> [...]
> > * FIRMWARE_IN_KERNEL
> > default enabled
> > we probably don't ship right yet relevant firmware separetly?
>
> FIRMWARE_IN_KERNEL enables inclusion of firmwa
tags 512617 + patch
thanks
I'm unfortunately able to reproduce this bug on an HP dc7900 with the
latest available BIOS (V1.11).
The patch in 2.6.28 looks trivial to backport to 2.6.26: it consists simply of
replacing WARN_ON with WARN_ON_ONCE. See
http://git.kernel.org/?p=linux/kernel/git/stable/
Package: linux-image-2.6.26-1-486
Version: 2.6.26+17
Severity: normal
The iethernet adaptor 0x8086:0x10de does not work for me with this kernel.
It is supposed to work with 2.6.28.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'un
Processing commands for cont...@bugs.debian.org:
> tags 512617 + patch
Bug#512617: kernel repeated warnings
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
[...]
>c. his means there will be no need for /etc/kernel-img.conf file any
> more.
[...]
Isn't this file also read in the postinst of the "official" kernels? In FAI we
had several issues when kernel-img.conf was missing or hadn't had the proper
values in there.
Best,
Michael
pgp2Ve
From: Josip Rodin
Date: Mon, 9 Feb 2009 09:45:27 +0100
> But then, it would have been completely your prerogative to respond to that
> simply by saying - DTRT and go upgrade X, patching old X is a waste of my
> time, and I guess nobody wanted to risk hearing that answer? :)
No, I would have said
Hi Otavio ;-)
On Donnerstag, 5. Februar 2009, Otavio Salvador wrote:
> I won't be at FOSDEM :(
You certainly missed a lot, but you didnt miss that meeting as it didnt take
place. (TTBOMK)
I planned to attend as I really really would like to see Debian Edu CDs build
as part of the normal Debian
Hi Moritz,
I must have forgotten during that CERN visit, I'm sorry. I tend to
forget a lot of things not related to work lately. I remember I was
upgrading the machine to lenny, so I'll look tonight in what state the
upgrade is and finish it. Then I'll install the latest stable kernel
from upstrea
From: Josip Rodin
Date: Mon, 9 Feb 2009 09:20:39 +0100
> On Sun, Feb 08, 2009 at 04:58:08PM -0800, David Miller wrote:
> > So you're saying that X working is more important than machines
> > actually booting at all? These priorities are wrong.
>
> When N (where N > 0) users complain about dead
On Mon, Feb 09, 2009 at 12:28:18AM -0800, David Miller wrote:
> > > So you're saying that X working is more important than machines
> > > actually booting at all? These priorities are wrong.
> >
> > When N (where N > 0) users complain about dead X, and 0 users complain
> > about not being able to
On Sun, Feb 08, 2009 at 04:58:08PM -0800, David Miller wrote:
> So you're saying that X working is more important than machines
> actually booting at all? These priorities are wrong.
When N (where N > 0) users complain about dead X, and 0 users complain
about not being able to boot, the prioritie
52 matches
Mail list logo
