dann frazier wrote:
> Yes. I really said woody.
>
> I've imported the woody 2.4 kernel trees into an svn repository:
> svn.debian.org/var/lib/gforge/chroot/home/users/dannf/woody
>
> We're currently tracking 160 issues, across the 6 woody source trees:
> svn://svn.debian.org/svn/kernel/patch
On Thu, 2005-12-08 at 01:24 +, Horms wrote:
> kernel-image-2.4.27-armwrong distribution, needs fix, random changes
arm should be fine now; all known issues have been fixed and I've been
running the netwinder build for a few days now. The other flavors could
use testing though.
> You ca
Yes. I really said woody.
I've imported the woody 2.4 kernel trees into an svn repository:
svn.debian.org/var/lib/gforge/chroot/home/users/dannf/woody
We're currently tracking 160 issues, across the 6 woody source trees:
svn://svn.debian.org/svn/kernel/patch-tracking
I've been slowly going
Package: initrd-tools
Version: 0.1.84
Followup-For: Bug #272079
Hi
This bug is bugging me too. I fixed similar to what Eto Yasuo did.
I've got LVM1 compiled into the kernel. The only reason that I need an
initrd is because of a lame Promise SATA controler that I need to boot
off of. My root
Package: kernel-image-2.4.27-2-686
Version: 2.4.27-12
Severity: important
Today's upgrade installed a new version of the kernel, but depmod fails
with:
[EMAIL PROTECTED]:~# depmod
depmod: *** Unresolved symbols in
/lib/modules/2.4.27-2-686/kernel/drivers/net/wireless/orinoco.o
depmod: *** Unres
Hi,
This has been a long time in the coming, but I'm happy
to report that we are slowly, but very surely making progress
towards being able to release a round of security updates for
Sarge.
These updates were actually prepared a little while ago,
but it has taken us a little while to work with th
> Rest assured, as soon as we start shipping a kernel that Jeff feels
> can run SATA ATAPI, we will turn it on - well, someone might have
> to remind us, things do slip through the craks. But right now
> its an upstream issue. I'm tagging it as such in the BTS.
> And other than working with upstram
This one time, at band camp, Maximilian Attems said:
> tags 342387 important stop
>
> On Wed, Dec 07, 2005 at 05:54:40PM +0100, yoann wrote:
> > Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16 Severity:
> > critical
>
> baah works for others downgrading.
>
> > I had an oops on my box :
>
>
On Wed, Dec 07, 2005 at 09:16:34PM +0100, Frederik Schueler wrote:
> due to upstream changes in 2.6.15-rc series, the current i386 386 flavour
> does not build anymore with plain old M386 support activated.
>
> Deactivating those drivers - which need those instructions not available on
> M386 -
(CC'ing port mailing lists where the port does not have 2.6 support in d-i)
An update of the table of kernel versions.
General comments:
- CD images still use 2.6.12 as Etch is installed
- only x86 and sparc64 fully switched to 2.6.14 for sid_d-i
- powerpc and amd64 have uploaded new udebs, but n
Hi all,
due to upstream changes in 2.6.15-rc series, the current i386 386 flavour
does not build anymore with plain old M386 support activated.
Deactivating those drivers - which need those instructions not available on
M386 - is not an option, because for example ACPI and DRI do need CMPXCHG:
Processing commands for [EMAIL PROTECTED]:
> tags 342387 important
Unknown tag/s: important.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid
help security upstream pending sarge sarge-ignore experimental d-i confirmed
ipv6 lfs fixed-in-experimental fixed-upstream l10
tags 342387 important
stop
On Wed, Dec 07, 2005 at 05:54:40PM +0100, yoann wrote:
> Package: kernel-image-2.6.8-2-686
> Version: 2.6.8-16
> Severity: critical
baah works for others downgrading.
> I had an oops on my box :
looks like one of those reiserfs races,
with some chances they are fixed
Package: kernel-image-2.6.8-2-686
Version: 2.6.8-16
Severity: critical
I had an oops on my box :
the system was responding to ssh, but it was impossible to get any information
about process list
ps, top, kill, pkill, killall, etc was unusable and it was impossible to
get out from the command, CT
On Wed, Dec 07, 2005 at 05:48:21PM +0200, Eero Häkkinen wrote:
> Package: mkvmlinuz
> Version: 17
> Severity: serious
>
> mkvmlinuz requires debconf but does not has a corresponding dependency field
> (and debconf is not Essential).
Oh well, will need to upload a fixed version on friday.
That s
Package: mkvmlinuz
Version: 17
Severity: serious
mkvmlinuz requires debconf but does not has a corresponding dependency field
(and debconf is not Essential).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Dec 06, 2005 at 02:28:01PM +0200, Jari Aalto wrote:
>
> Following my other posts: Here is install report from another machine,
> with exactly the same results. I've tried to reproduce as much debug
> as I know. Let me know how can I help more.
Thanks, very clear report.
> /dev/hda7
I found out that all vanilla kernels don't do it (2.6.12,13,14,15-rcX).
But all ubuntu kernels do.
MfG,
Stefan Sonnenberg-Carstens
NRW.BANK
IT-Handel
Department: 101-79310
Herzogstraße 15
D - 40217 Düsseldorf
Tel.: +49211 826 3211
EMail: [EMAIL PROTECTED]
Diese Nachricht ist vertraulich. Sol
Package: kernel-image-2.6.8-2-686
Severity: normal
Hi,
halting my cluster (~160 machines) usually results in about 5-6 hung
ones. The hang happens at the bottom of rc0.d/S31umountnfs, issuing the
umount command. I modified the script to produce some more output:
/etc/rc0.d/S31umountnfs:
[...]
On Tue, Dec 06, 2005 at 09:31:43PM +0100, Max Vozeler wrote:
> On Tue, Dec 06, 2005 at 06:55:49PM +0100, Sven Luther wrote:
> >
> > You need to set ARCH=ppc64 to build the powerpc64 flavour.
> >
>
> Thanks, now I think I see what's happening :-)
>
> It's a little cumbersome having to special-case
20 matches
Mail list logo
