Re: Lastest klibc breaks rootskel?
On Wednesday 08 November 2006 19:10, Joey Hess wrote: > Jérôme Marant wrote: > > I tried to rebuilt rootskel yesterday and I got: > > > > Making install in src-bootfloppy > > make[2]: entrant dans le répertoire « > > /home/jerome/d-i/packages/rootskel/src-bootfloppy » Making build in > > bin > > make[3]: entrant dans le répertoire « > > /home/jerome/d-i/packages/rootskel/src-bootfloppy/bin » klcc-c -o > > cpio.o cpio.c > > open3: exec of /usr/local/bin/gcc -D__KLIBC__=1 -D__KLIBC_MINOR__=4 > > -D_BITSIZE=64 -fno-stack-protector -m64 -D__KLIBC__=1 > > -D__KLIBC_MINOR__=4 -D_BITSIZE=64 > > -I/usr/lib/klibc/include/arch/x86_64 -I/usr/lib/klibc/include/bits64 > > -I/usr/lib/klibc/include -Os -fno-asynchronous-unwind-tables > > -fomit-frame-pointer -falign-functions=1 -falign-jumps=1 > > -falign-loops=1 -c -o cpio.o -x c cpio.c failed at /usr/bin/klcc line > > 138 > > > > Can anyone confirm? > > No, works fine here. Why is your klcc trying to run a gcc in > /usr/local/bin? Exactly the same thing happened with a previous version of klibc. Apparently this happens if klibc is built in a "dirty" build environment. It would be great if the maintainers/uploaders of klibc could take a bit more care not to repeat this mistake... pgp4wCLmUOGna.pgp Description: PGP signature
Bug#391626: Please include mol into linux-modules-extra before etch
tags 391626 +patch Hi As the mol maintainer I would really appreciate it if you could include my patch before the etch release. The patch is already in the bug log since about a month. AFAICS a new upload of linux-modules-extra is needed anyway for linux-image-2.6.18-2-*. Please contact me if you need additional information or assistance. If you are busy with other things I can also prepare an NMU. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ pgptUBnNw2CZP.pgp Description: PGP signature
Processed (with 5 errors): Please include mol into linux-modules-extra before etch
Processing commands for [EMAIL PROTECTED]: > tags 391626 +patch Bug#391626: add mol to linux-modules-extra-2.6 There were no tags set. Tags added: patch > Hi Unknown command or malformed arguments to command. > As the mol maintainer I would really appreciate it if you could include Unknown command or malformed arguments to command. > my patch before the etch release. The patch is already in the bug log Unknown command or malformed arguments to command. > since about a month. Unknown command or malformed arguments to command. > AFAICS a new upload of linux-modules-extra is needed anyway for Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
initramfs-tools 0.85a MIGRATED to testing
FYI: The status of the initramfs-tools source package in Debian's testing distribution has changed. Previous version: 0.84 Current version: 0.85a -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm
* Sjoerd Simons <[EMAIL PROTECTED]> [2006-11-08 21:07]: > Sure, wookey had some extra comments after i asked for permission to post it > so > i've added those too: > http://beast.luon.net/~sjoerd/arm_unaligned.log http://netwinder.osuosl.org/users/b/brianbr/public_html/alignment.html Ok, thanks for the pointer. I don't think it's a good idea to enable this right now, but we should do it after etch is out. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm
On Wed, Nov 08, 2006 at 06:46:38PM +, Martin Michlmayr wrote: > * Sjoerd Simons <[EMAIL PROTECTED]> [2006-11-08 14:02]: > > Some discussion on #debian-arm indicates that it the current default > > Can you make logs of that discussion available? Sure, wookey had some extra comments after i asked for permission to post it so i've added those too: http://beast.luon.net/~sjoerd/arm_unaligned.log Sjoerd -- The amount of time between slipping on the peel and landing on the pavement is precisely 1 bananosecond. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm
* Sjoerd Simons <[EMAIL PROTECTED]> [2006-11-08 14:02]: > Some discussion on #debian-arm indicates that it the current default Can you make logs of that discussion available? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397139: marked as done (ftbfs alpha + ia64)
Your message dated Wed, 08 Nov 2006 10:50:29 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397139: fixed in linux-2.6 2.6.18-5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-2.6
Version: 2.6.18-4
Severity: serious
-- snipp alpha
CC arch/alpha/kernel/core_cia.o
{standard input}: Assembler messages:
{standard input}:250: Error: macro requires $at register while noat in effect
{standard input}:265: Error: macro requires $at register while noat in effect
{standard input}:280: Error: macro requires $at register while noat in effect
{standard input}:293: Error: macro requires $at register while noat in effect
{standard input}:329: Error: macro requires $at register while noat in effect
{standard input}:344: Error: macro requires $at register while noat in effect
{standard input}:359: Error: macro requires $at register while noat in effect
{standard input}:372: Error: macro requires $at register while noat in effect
make[5]: *** [arch/alpha/kernel/core_cia.o] Error 1
make[4]: *** [arch/alpha/kernel] Error 2
-- snipp ia64
CC mm/hugetlb.o
mm/hugetlb.c: In function 'copy_huge_page':
mm/hugetlb.c:54: error: too few arguments to function 'copy_user_highpage'
make[5]: *** [mm/hugetlb.o] Error 1
other archs fallout yet unkown,
amd64 and arm are in installed status.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.18-5
We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:
linux-2.6_2.6.18-5.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18-5.diff.gz
linux-2.6_2.6.18-5.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18-5.dsc
linux-doc-2.6.18_2.6.18-5_all.deb
to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18-5_all.deb
linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb
linux-headers-2.6.18-2_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-headers-2.6.18-2_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb
to pool/main/l/linux-2.6/linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb
linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb
to
pool/main/l/linux-2.6/linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_po
Bug#397281: marked as done (BUG: [EMAIL PROTECTED]/irq/handle.c:177/__do_IRQ())
Your message dated Wed, 08 Nov 2006 10:50:29 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397281: fixed in linux-2.6 2.6.18-5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: linux-image-2.6.18-1-xen-vserver-686
Version: 2.6.18-3
Severity: minor
Tags: patch
Hi *!
When using the -xen-vserver kernel, the domU spits many errors like
this:
Nov 5 21:28:39 frontend kernel: BUG: warning at
kernel/irq/handle.c:177/__do_IRQ()
Nov 5 21:28:39 frontend kernel: [] __do_IRQ+0x45/0x160
Nov 5 21:28:39 frontend kernel: [] do_IRQ+0x43/0x53
Nov 5 21:28:39 frontend kernel: [] evtchn_do_upcall+0x64/0x9b
Nov 5 21:28:39 frontend kernel: [] hypervisor_callback+0x3d/0x48
Nov 5 21:28:39 frontend kernel: [] page_address+0x1/0x81
Nov 5 21:28:39 frontend kernel: [] __handle_mm_fault+0x115/0xc21
Nov 5 21:28:39 frontend kernel: [] error_code+0x2b/0x30
Nov 5 21:28:39 frontend kernel: [] do_page_fault+0x39f/0x7c8
Nov 5 21:28:39 frontend kernel: [] schedule_tail+0x80/0x85
Nov 5 21:28:39 frontend kernel: [] do_page_fault+0x0/0x7c8
Nov 5 21:28:39 frontend kernel: [] error_code+0x2b/0x30
Nov 5 21:28:39 frontend kernel: BUG: warning at
kernel/irq/handle.c:177/__do_IRQ()
Nov 5 21:28:39 frontend kernel: [] __do_IRQ+0x45/0x160
Nov 5 21:28:39 frontend kernel: [] do_IRQ+0x43/0x53
Nov 5 21:28:39 frontend kernel: [] evtchn_do_upcall+0x64/0x9b
Nov 5 21:28:39 frontend kernel: [] hypervisor_callback+0x3d/0x48
With the help of #vserver I have tracked this down to a missing
__enter/leave_vx_admin() call in irq-xen.c:
- --- orig/linux-2.6-2.6.18/debian/patches/features/all/xen/fedora-36252.patch
2006-11-06 09:36:27.0 +0100
+++
linux-2.6-2.6.18.modified/debian/patches/features/all/xen/fedora-36252.patch
2006-11-05 22:44:50.0 +0100
@@ -7210,7 +7210,7 @@
diff -urN -x .hg -x .hgtags linux-2.6.18.1/arch/i386/kernel/irq-xen.c
linux-2.6.18-xen/arch/i386/kernel/irq-xen.c
--- linux-2.6.18.1/arch/i386/kernel/irq-xen.c 1970-01-01 01:00:00.0
+0100
+++ linux-2.6.18-xen/arch/i386/kernel/irq-xen.c2006-09-04
16:31:00.0
+0200
- -@@ -0,0 +1,324 @@
+@@ -0,0 +1,328 @@
+/*
+ *linux/arch/i386/kernel/irq.c
+ *
@@ -7231,6 +7231,7 @@
+#include
+#include
+#include
++#include
+
+DEFINE_PER_CPU(irq_cpustat_t, irq_stat)
cacheline_internodealigned_in_smp;
+EXPORT_PER_CPU_SYMBOL(irq_stat);
@@ -7268,6 +7269,7 @@
+{
+ /* high bit used in ret_from_ code */
+ int irq = ~regs->orig_eax;
++ struct vx_info_save vxis;
+#ifdef CONFIG_4KSTACKS
+ union irq_ctx *curctx, *irqctx;
+ u32 *isp;
@@ -7295,6 +7297,7 @@
+ }
+#endif
+
++ __enter_vx_admin(&vxis);
+#ifdef CONFIG_4KSTACKS
+
+ curctx = (union irq_ctx *) current_thread_info();
@@ -7333,6 +7336,7 @@
+ } else
+#endif
+ __do_IRQ(irq, regs);
++ __leave_vx_admin(&vxis);
+
+ irq_exit();
+
Using this patch i have no further BUG traces.
daniel_hozac of #vserver recommended this shell fragment to repair
missing vserver patch pieces in xen:
(23:47:36) daniel_hozac: DavidS: i usually run find . -name '*-xen.[chS]' | {
while read FILE; do f=${FILE/./}; f=${f/-xen/}; filterdiff -i "*$f" | patch $FILE; done }
Thank you for your time and work!
Regards, David
- -- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-vserver-686
Locale: LANG=C, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-1-xen-vserver-686 depends on:
ii initramfs-tools 0.85 tools for generating an initramfs
ii linux-modules-2.6.18-1-xen-vs 2.6.18-3 Linux 2.6.18 modules on
PPro/Celer
Versions of packages linux-image-2.6.18-1-xen-vserver-686 recommends:
ii libc6-xen2.3.6.ds1-7 GNU C Library: Shared libraries
[X
- -- no debconf information
- --
- - hallo... wie gehts heute?
- - *hust* gut *rotz* *keuch*
- - gott sei dank kommunizieren wir über ein septisches medium ;)
-- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFTvun/Pp1N6Uzh0URAp9cAJ4rfdXnHcZVI4nW3ivPeHxMmTk6dgCfSyz3
rLHPqzfEMJYQWCSjL0IqfNc=
=0Sb0
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.18-5
We believe that
Bug#391275: marked as done (linux-2.6: please add CONFIG_SX=m in the 686 kernel image)
Your message dated Wed, 08 Nov 2006 10:50:26 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#391275: fixed in linux-2.6 2.6.18-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-2.6 Version: 2.6.18-2 Severity: wishlist Hi, I need the sx module on one of my machines, but the 686 kernel image is built without CONFIG_SX. Please consider adding this module to the configuration (it's already enabled for the 486 flavour, and I don't know of any reason to have a different setting here). Thanks, Julien -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.18-5 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18-5.diff.gz linux-2.6_2.6.18-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18-5.dsc linux-doc-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18-5_all.deb linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb linux-headers-2.6.18-2_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb linux-manual-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18-5_all.deb linux-patch-debian-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18-5_all.deb linux-source-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18-5_all.deb linux-support-2.6.18-2_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-support-2.6.18-2_2.6.18-5_all.deb linux-tree-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and
Bug#376230: linux-image-2.6.17-1-686: sound(only) no longer works with BTTV television card
UPDATE: BTTV SOUND is now WORKING AGAIN with this KERNEL 2.6.18-1-686 #1 SMP Sat Oct 21 17:21:28 UTC 2006 i686 GNU/Linux I've periodically tried newer kernels and this one (above) is the FIRST ONE (since 2.6.17) that has sound working OK again on my PCI BTTV Telivision CARD. - thanks for all your efforts- - Original Message From: john robertson <[EMAIL PROTECTED]>To: [EMAIL PROTECTED]Sent: Saturday, July 1, 2006 12:51:28 AMSubject: linux-image-2.6.17-1-686: sound(only) no longer works with BTTV television cardSubject: linux-image-2.6.17-1-686: sound(only) no longer worksPackage: linux-image-2.6.17-1-686Version: 2.6.17-2Severity: normal*** Please type your report below this line *** sound(only) no longer works with BTTV television card with an debian kernels released so far TV Sound still works OK if I go back to the 2.6.16 kernel. -- System Information:Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable')Architecture: i386 (i686)Shell: /bin/sh linked to /bin/bashKernel: Linux 2.6.16-2-686Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)Versions of packages linux-image-2.6.17-1-686 depends on:ii module-init-tools 3.2.2-3 tools for managinii yaird [linux-initramfs-tool] 0.0.12-15 Yet Another mkIniVersions of packages linux-image-2.6.17-1-686 recommends:pn libc6-i686 (no description a-- debconf information: linux-image-2.6.17-1-686/preinst/bootloader-initrd-2.6.17-1- linux-image-2.6.17-1-686/postinst/old-dir-initrd-link-2.6.17* linux-image-2.6.17-1-686/postinst/bootloader-test-error-2.6. linux-image-2.6.17-1-686/postinst/old-initrd-link-2.6.17-1-6 linux-image-2.6.17-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-1-686/postinst/depmod-error-2.6.17-1-686: linux-image-2.6.17-1-686/prerm/removing-running-kernel-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/overwriting-modules-2.6.17-1-686: true* linux-image-2.6.17-1-686/preinst/lilo-initrd-2.6.17-1-686: false linux-image-2.6.17-1-686/preinst/failed-to-move-modules-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/create-kimage-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/kimage-is-a-directory: linux-image-2.6.17-1-686/postinst/old-system-map-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/elilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/already-running-this-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/abort-overwrite-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/bootloader-error-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/initrd-2.6.17-1-686: Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail Beta.
linux-2.6_2.6.18-5_powerpc.changes ACCEPTED
Accepted: linux-2.6_2.6.18-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18-5.diff.gz linux-2.6_2.6.18-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18-5.dsc linux-doc-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18-5_all.deb linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb linux-headers-2.6.18-2_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb linux-manual-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18-5_all.deb linux-patch-debian-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18-5_all.deb linux-source-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18-5_all.deb linux-support-2.6.18-2_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-support-2.6.18-2_2.6.18-5_all.deb linux-tree-2.6.18_2.6.18-5_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18-5_all.deb Override entries for your package: linux-2.6_2.6.18-5.dsc - source devel linux-doc-2.6.18_2.6.18-5_all.deb - optional doc linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb - optional devel linux-headers-2.6.18-2_2.6.18-5_powerpc.deb - optional devel linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb - optional admin linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb - optional admin linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb - optional admin linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb - optional admin linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb - optional admin linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb - optional admin linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb - optional admin linux-manual-2.6.18_2.6.18-5_all.deb - optional doc linux-patch-debian-2.6.18_2.6.18-5_all.deb - optional devel linux-source-2.6.18_2.6.18-5_all.deb - optional devel linux-support-2.6.18-2_2.6.18-5_all.deb - optional devel linux-tree-2.6.18_2.6.18-5_all.deb - optional devel Announcing to debian-devel-changes@lists.debian.org Closing bugs: 391275 397139 397281 Thank you for your c
Processing of linux-2.6_2.6.18-5_powerpc.changes
linux-2.6_2.6.18-5_powerpc.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.18-5.dsc linux-2.6_2.6.18-5.diff.gz linux-doc-2.6.18_2.6.18-5_all.deb linux-manual-2.6.18_2.6.18-5_all.deb linux-patch-debian-2.6.18_2.6.18-5_all.deb linux-source-2.6.18_2.6.18-5_all.deb linux-support-2.6.18-2_2.6.18-5_all.deb linux-tree-2.6.18_2.6.18-5_all.deb linux-headers-2.6.18-2-all_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-all-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc-smp_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc-miboot_2.6.18-5_powerpc.deb linux-image-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-powerpc64_2.6.18-5_powerpc.deb linux-image-2.6.18-2-prep_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-prep_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver_2.6.18-5_powerpc.deb linux-image-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver-powerpc_2.6.18-5_powerpc.deb linux-image-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb linux-headers-2.6.18-2-vserver-powerpc64_2.6.18-5_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397139: ftbfs alpha + ia64
On Tue, 7 Nov 2006, Falk Hueffner wrote: Steve Langasek <[EMAIL PROTECTED]> writes: Given that you mention you're not running a Debian kernel at all right now, and that this code is in place upstream and nobody else seems to have complained loudly enough to get it fixed, I'm not sure how much effort we'll want to put into it if it turns out to not work on ev5, but it will still be good to know -- and if the kernel *does* work for you, that's a good reason to find a solution other than switching the kernel to build ev56 code. :) It should work, the code is guarded to be only executed on ev56+. See also the thread http://gcc.gnu.org/ml/gcc/2005-07/msg00371.html Yes, it does seem to work. I'm running linux-image-2.6.18-1-alpha-generic now, and haven't seen anything blatantly broken. Ivan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.18-5 schedule
* maximilian attems wrote: > nobse please check if the patch from vorlon satitisfies. Looks good, first flavour built fine, second one still building. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.18-4_m68k.changes ACCEPTED
Accepted: linux-headers-2.6.18-2-all-m68k_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all-m68k_2.6.18-4_m68k.deb linux-headers-2.6.18-2-all_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-all_2.6.18-4_m68k.deb linux-headers-2.6.18-2-amiga_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-amiga_2.6.18-4_m68k.deb linux-headers-2.6.18-2-mac_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2-mac_2.6.18-4_m68k.deb linux-headers-2.6.18-2_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-2_2.6.18-4_m68k.deb linux-image-2.6.18-2-amiga_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-amiga_2.6.18-4_m68k.deb linux-image-2.6.18-2-mac_2.6.18-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.18-2-mac_2.6.18-4_m68k.deb Override entries for your package: linux-headers-2.6.18-2-all-m68k_2.6.18-4_m68k.deb - optional devel linux-headers-2.6.18-2-all_2.6.18-4_m68k.deb - optional devel linux-headers-2.6.18-2-amiga_2.6.18-4_m68k.deb - optional devel linux-headers-2.6.18-2-mac_2.6.18-4_m68k.deb - optional devel linux-headers-2.6.18-2_2.6.18-4_m68k.deb - optional devel linux-image-2.6.18-2-amiga_2.6.18-4_m68k.deb - optional admin linux-image-2.6.18-2-mac_2.6.18-4_m68k.deb - optional admin Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375995: marked as done (linux-image-2.6.17-1-686: ethernet stops working (rtl8139) )
Your message dated Wed, 8 Nov 2006 15:09:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line ethernet stops working (rtl8139) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.17-1-686 Version: 2.6.17-1 Severity: important The ethernet interface on my Acer Travelmate 223X stops working directly or shortly after boot. This is very similar to #358744, but now I also get more interesting log messages, see below. After that, network connectivity is lost and I cannot restore it except by rebooting. I have replaced the switch that my laptop was connected to, with the same results. The network interface is a builtin Realtek 8139. My wireless cardbus card still works correctly though. Jun 28 07:49:47 kelev kernel: __report_bad_irq+0x24/0x90 note_interrupt+0x8b/0x1f0 Jun 28 07:49:47 kelev kernel: handle_IRQ_event+0x33/0x70 __do_IRQ+0xae/0xc0 Jun 28 07:49:47 kelev kernel: do_IRQ+0x19/0x30 common_interrupt+0x1a/0x20 Jun 28 07:49:47 kelev kernel: __do_softirq+0x2d/0xa0 do_softirq+0x26/0x30 Jun 28 07:49:47 kelev kernel: do_IRQ+0x1e/0x30 common_interrupt+0x1a/0x20 Jun 28 07:49:47 kelev kernel: syscall_call+0x7/0xb Jun 28 07:50:36 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Jun 28 07:50:39 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Jun 28 07:50:51 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Jun 28 07:50:54 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Jun 28 07:51:06 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Jun 28 07:51:09 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Jun 28 07:51:21 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Jun 28 07:51:24 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-1-686 depends on: ii initramfs-tools [linux-initra 0.60 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-14 Yet Another mkInitRD Versions of packages linux-image-2.6.17-1-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-1-686/preinst/bootloader-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/old-dir-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/bootloader-test-error-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/old-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-1-686/postinst/depmod-error-2.6.17-1-686: false linux-image-2.6.17-1-686/prerm/removing-running-kernel-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/overwriting-modules-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/failed-to-move-modules-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/create-kimage-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/kimage-is-a-directory: linux-image-2.6.17-1-686/postinst/old-system-map-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/elilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/already-running-this-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/abort-overwrite-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/bootloader-error-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/initrd-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/depmod-error-initrd-2.6.17-1-686: false linux-image-2.6.17-1-686/preinst/abort-install-2.6.17-1-686: linux-image-2.6.17-1-686/prerm/would-invalidate-boot-loader-2.6.17-1-686: true --- End Message --- --- Begin Message --- Version: 2.6.18-4 The problem was corrected upstream at some point. --- End Message ---
Bug#358744: marked as done (linux-image-2.6.16-1-686: ethernet does not work)
Your message dated Wed, 8 Nov 2006 15:09:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line ethernet stops working (rtl8139) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.16-1-686 Version: 2.6.16-2 Severity: important The Ethernet does not work after resuming 2.6.16. (It always works with 2.6.15.) Nothing can be sent or received on the ethernet interface. I'm seeing messages such as these: Mar 24 08:06:51 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Mar 24 08:07:03 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 24 08:07:06 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Mar 24 08:07:18 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 24 08:07:21 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Mar 24 08:07:33 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 24 10:20:56 kelev kernel: NETDEV WATCHDOG: eth0: transmit timed out Mar 24 10:20:57 kelev dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 Mar 24 10:20:59 kelev kernel: eth0: Transmit timeout, status 0c 0005 c07f media 10. Mar 24 10:20:59 kelev kernel: eth0: Tx queue start entry 4 dirty entry 0. Mar 24 10:20:59 kelev kernel: eth0: Tx descriptor 0 is 8008a03c. (queue head) Mar 24 10:20:59 kelev kernel: eth0: Tx descriptor 1 is 8008a03c. Mar 24 10:20:59 kelev kernel: eth0: Tx descriptor 2 is 8008a03c. Mar 24 10:20:59 kelev kernel: eth0: Tx descriptor 3 is 8008a03c. Mar 24 10:20:59 kelev kernel: eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 I am using ifplugd. The Ethernet card is a built-in Realtek RTL-8139, the system is an Acer Travelmate 220. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-1-686 depends on: ii initramfs-tools [linux-initra 0.53c tools for generating an initramfs ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-3 Yet Another mkInitRD Versions of packages linux-image-2.6.16-1-686 recommends: ii libc6-i6862.3.6-3GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-1-686/preinst/initrd-2.6.16-1-686: linux-image-2.6.16-1-686/postinst/create-kimage-link-2.6.16-1-686: true linux-image-2.6.16-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-686/prerm/removing-running-kernel-2.6.16-1-686: true linux-image-2.6.16-1-686/postinst/old-dir-initrd-link-2.6.16-1-686: true linux-image-2.6.16-1-686/postinst/depmod-error-initrd-2.6.16-1-686: false linux-image-2.6.16-1-686/preinst/lilo-initrd-2.6.16-1-686: true linux-image-2.6.16-1-686/postinst/old-system-map-link-2.6.16-1-686: true linux-image-2.6.16-1-686/postinst/kimage-is-a-directory: linux-image-2.6.16-1-686/preinst/bootloader-initrd-2.6.16-1-686: true linux-image-2.6.16-1-686/preinst/already-running-this-2.6.16-1-686: linux-image-2.6.16-1-686/preinst/overwriting-modules-2.6.16-1-686: true linux-image-2.6.16-1-686/postinst/old-initrd-link-2.6.16-1-686: true linux-image-2.6.16-1-686/preinst/abort-overwrite-2.6.16-1-686: linux-image-2.6.16-1-686/postinst/depmod-error-2.6.16-1-686: false linux-image-2.6.16-1-686/preinst/failed-to-move-modules-2.6.16-1-686: linux-image-2.6.16-1-686/preinst/elilo-initrd-2.6.16-1-686: true linux-image-2.6.16-1-686/prerm/would-invalidate-boot-loader-2.6.16-1-686: true linux-image-2.6.16-1-686/postinst/bootloader-error-2.6.16-1-686: linux-image-2.6.16-1-686/preinst/abort-install-2.6.16-1-686: linux-image-2.6.16-1-686/postinst/bootloader-test-error-2.6.16-1-686: --- End Message --- --- Begin Message --- Version: 2.6.18-4 The problem was corrected upstream at some point. --- End Message ---
d-i on mac [was Re: yaird on m68k]
On Tue, 2006-11-07 at 22:46 +0100, Christian T. Steigies wrote: > On Tue, Nov 07, 2006 at 10:11:52PM +0100, Eugen Paiuc wrote: > > On Tue, 2006-11-07 at 21:32 +0100, maximilian attems wrote: > > > On Tue, Nov 07, 2006 at 09:18:36PM +0100, Eugen Paiuc wrote: > > > > Hi , > > > > > > > > The situation described in > > > > http://lists.debian.org/debian-68k/2006/11/msg00032.html > > > > http://lists.debian.org/debian-68k/2006/11/msg00034.html > > > > > > > > it's of failed of yaird for installing linux-image-2.6.17-2-mac kernel. > > > > Can you take a look there, please . > > > > > > afaik m68k doesn't need an initramfs at all? > > That was dropped, but maybe only with 2.6.18. But I wonder why I could > install 2.6.17 on my q840av, I did not test the debian-installer on the mac, > though. If I understand do you wand test the debian-installer on the mac ? regards eugen > Can you try with a recent kernel? now it's ok . [snip] regards eugen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: rename Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm
Processing commands for [EMAIL PROTECTED]: > retitle 397616 [arm] /proc/cpu/alignment should default to warn and fixup on > arm Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397616: /proc/cpu/alignment should default to warn and fixup on arm
Package: linux-2.6 Severity: normal Hi, By default the ARM kernel just ignores unaligned accesses from userspace and can just accesses another address then actually specified. This can cause strange behaviour by userspace programs. While i agree that these programs are somewhat buggy, but doing something undefined and not telling anyone doesn't seem like a good strategy :) Some discussion on #debian-arm indicates that it the current default made some sense in the old days. Where some programs actually relied on the behaviour and the amount of buggy programs was so big that it actually caused a flood of warnings. Times have changed though, no applications in debian should depend on this behaviour and turning on warn+fixup doesn't seem cause a flood anymore. Most problemeatic should have been fixed by now, as on Sparc you'll get a sigbus on unaligned access and iirc Alpha gives a warning about it. For reference, i discovered this issue because powerdns on my arm was giving out weird SOA records. So enabling fixup does solves real problems or at least shows where they are :) (Yes i've already patched pdns and will be sending the patch out after some more testing) Sjoerd -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (101, 'unstable') Architecture: arm (armv5tel) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-iop32x Locale: LANG=C, LC_CTYPE=nl_NL (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394742: crash logs with a kernel.org 2.6.18.2
Hello, I can reproduce this with the latest from kernel.org too. Here are the logs: http://kapsi.fi/mcfrisk/temp/bt_oops.txt -Mikko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
So long and thanks for all the kernels
BTW, having Xen + vserver in the one kernel is a sweet sweet thing for me. Kudos and thanks to the whizzes in the kernel team. Tony -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: -xen-vserver kernel: does the Xen stuff work?
Tony Lewis wrote: My initial question: is anybody using the Xen stuff in this kernel? Just so as I know I'm not wasting time on something not yet working... ... never mind - should have waited and tried some more things. Got it working now. Tony -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Replies off-list (Was: yaird on m68k)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian T. Steigies wrote: > On Tue, Nov 07, 2006 at 10:11:52PM +0100, Eugen Paiuc wrote: >> ps. i'm on the list > > I guess you should tell your MUA and not us, I didn't see any note of that > in the headers of your mail. Debian Mailinglist Code of conduct[1] says the opposite: > When using the Debian mailing lists, please follow these rules: > [snip] > When replying to messages on the mailing list, do not send a > carbon copy (CC) to the original poster unless they explicitly > request to be copied. If this list follows different rules, could they please be advertised somewhere? Regards, - - Jonas [1] http://www.debian.org/MailingLists/index.en.html#codeofconduct - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFUcxLn7DbMsAkQLgRAgRjAKCDcaq4D/INVKOFWvo17kAvqqOz5QCgoQW/ 7NHDpjzwo2KJ/nyNp7y47nE= =MjTd -END PGP SIGNATURE-
Re: Mounting UFS under Linux with R/W
On 04.11.06 09:51, Alien wrote: > I did not seem to find this topic in this list - I hope it is the right > place to discuss that. > > The problem is - mounting UFS under Linux and to provide > both - R and W options. &npsb? Where did you edit this mail? > So far I have found that R is easily implemented but Write option is > quite dangerous - > it harms the filesystem. > > Is there yet a correctsolution on any new Kernel? man mount, see 'ufs' section. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Quantum mechanics: The dreams stuff is made of. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-xen-vserver kernel: does the Xen stuff work?
I'm trying the linux-image-2.6.18-1-xen-vserver (2.6.18-3) kernel, and
I'm having trouble creating (booting) a domU. The symptom appears to be
that it boots, then hangs for about 100 seconds, then crashes. I assume
the 100s is a Xen timeout thing.
My initial question: is anybody using the Xen stuff in this kernel?
Just so as I know I'm not wasting time on something not yet working...
If anyone wants to take a look further, I see the following in xend.log:
-
[2006-11-08 23:21:00 xend.XendDomainInfo 2452] DEBUG (__init__:1072)
XendDomainInfo.create(['vm', ['name', 'xen0'], ['memory', 32], ['vcpus',
1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.18-1-xen-vserver-686'
], ['ip',
'192.168.18.98:1.2.3.4:192.168.18.254:255.255.255.0:xentest.home:eth0:off'],
['root', '/dev/hda1'], ['args', '3']]], ['device', ['vbd', ['uname',
'phy:vg0/xen0'], ['dev', 'hda1'], ['mode', 'w']]], ['device',
['vif', ['bridge', 'xenbr0')
[2006-11-08 23:21:00 xend.XendDomainInfo 2452] DEBUG (__init__:1072)
parseConfig: config is ['vm', ['name', 'xen0'], ['memory', 32],
['vcpus', 1], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.18-1-xen-vserver-686
'], ['ip',
'192.168.18.98:1.2.3.4:192.168.18.254:255.255.255.0:xentest.home:eth0:off'],
['root', '/dev/hda1'], ['args', '3']]], ['device', ['vbd', ['uname',
'phy:vg0/xen0'], ['dev', 'hda1'], ['mode', 'w']]], ['device'
, ['vif', ['bridge', 'xenbr0'
[2006-11-08 23:21:00 xend.XendDomainInfo 2452] DEBUG (__init__:1072)
parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash':
None, 'on_reboot': None, 'localtime': None, 'image': ['linux', ['kernel', '
/boot/vmlinuz-2.6.18-1-xen-vserver-686'], ['ip',
'192.168.18.98:1.2.3.4:192.168.18.254:255.255.255.0:xentest.home:eth0:off'],
['root', '/dev/hda1'], ['args', '3']], 'on_poweroff': None,
'bootloader_args': None, 'cpus'
: None, 'name': 'xen0', 'backend': [], 'vcpus': 1, 'cpu_weight': None,
'features': None, 'vcpu_avail': None, 'memory': 32, 'device': [('vbd',
['vbd', ['uname', 'phy:vg0/xen0'], ['dev', 'hda1'], ['mode', 'w']]), ('vif'
, ['vif', ['bridge', 'xenbr0']])], 'bootloader': None, 'cpu': None,
'maxmem': None}
[2006-11-08 23:21:00 xend.XendDomainInfo 2452] DEBUG (__init__:1072)
XendDomainInfo.construct: None
[2006-11-08 23:21:00 xend.XendDomainInfo 2452] DEBUG (__init__:1072)
XendDomainInfo.initDomain: 3 1.0
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) Balloon: 33772 KiB
free; need 32768; done.
[2006-11-08 23:21:00 xend 2452] INFO (__init__:1072) buildDomain
os=linux dom=3 vcpus=1
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) dom= 3
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) image =
/boot/vmlinuz-2.6.18-1-xen-vserver-686
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) store_evtchn = 1
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) console_evtchn = 2
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) cmdline=
ip=192.168.18.98:1.2.3.4:192.168.18.254:255.255.255.0:xentest.home:eth0:off
root=/dev/hda1 3
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) ramdisk=
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) vcpus = 1
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) features =
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) DevController:
writing {'backend-id': '0', 'virtual-device': '769', 'device-type':
'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/3/769'} to
/local/
domain/3/device/vbd/769.
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) DevController:
writing {'domain': 'xen0', 'frontend': '/local/domain/3/device/vbd/769',
'dev': 'hda1', 'state': '1', 'params': 'vg0/xen0', 'mode': 'w', 'online': '
1', 'frontend-id': '3', 'type': 'phy'} to /local/domain/0/backend/vbd/3/769.
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) DevController:
writing {'backend-id': '0', 'mac': '00:16:3e:7b:64:71', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/3/0'} to
/local/domain/
3/device/vif/0.
[2006-11-08 23:21:00 xend 2452] DEBUG (__init__:1072) DevController:
writing {'bridge': 'xenbr0', 'domain': 'xen0', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/3/de
vice/vif/0', 'mac': '00:16:3e:7b:64:71', 'online': '1', 'frontend-id':
'3'} to /local/domain/0/backend/vif/3/0.
[2006-11-08 23:21:00 xend.XendDomainInfo 2452] DEBUG (__init__:1072)
Storing VM details: {'shadow_memory': '0', 'uuid':
'21b0998a-8393-a844-98f1-8d32c683ea64', 'on_reboot': 'restart',
'start_time': '1162988460.71', 'o
n_poweroff': 'destroy', 'name': 'xen0', 'xend/restart_count': '0',
'vcpus': '1', 'vcpu_avail': '1', 'memory': '32', 'on_crash': 'restart',
'image': '(linux (kernel /boot/vmlinuz-2.6.18-1-xen-vserver-686) (ip
192.168.1
8.98:1.2.3.4:192.168.18.254:255.255.255.0:xentest.home:eth0:off) (root
/dev/hda1) (args 3))', 'maxmem': '32'}
[2006-11-08 23:21:00
Re: yaird on m68k
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 maximilian attems wrote: > On Tue, Nov 07, 2006 at 09:18:36PM +0100, Eugen Paiuc wrote: >> Hi , >> >> The situation described in >> http://lists.debian.org/debian-68k/2006/11/msg00032.html >> http://lists.debian.org/debian-68k/2006/11/msg00034.html >> >> it's of failed of yaird for installing linux-image-2.6.17-2-mac kernel. >> Can you take a look there, please . > > afaik m68k doesn't need an initramfs at all? > what is the failure for initramfs-tools? > dropping to a shell indicates that a wrong root boot arg was passed. > > and please don't waste time with yaird it is broken behind imagination. Discussing yaird on this list is obviously counterproductive. Please continue such discussion at its own mailinglist: [EMAIL PROTECTED] . Regards, Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFUciyn7DbMsAkQLgRAsmZAJ9bvdJa+kDXrrVGL50hqqWlSxsqHgCcCEzC pTHznSkk+EVCDTGiB2eLqpI= =VeLi -END PGP SIGNATURE-
Processed: Re: Bug#397550: routing between alias subnets on same interface produces RFC-1812 contravening ICMP redirects
Processing commands for [EMAIL PROTECTED]: > reassign 397550 linux-2.6 Bug#397550: routing between alias subnets on same interface produces RFC-1812 contravening ICMP redirects Warning: Unknown package 'linux-image' Bug reassigned from package `linux-image' to `linux-2.6'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397550: routing between alias subnets on same interface produces RFC-1812 contravening ICMP redirects
Package: linux-image Version: 2.6.18 This really isnt debian's fault. I just want to see if I can get a bug that was talked about and a patch offered for linux 2.2 in 2000 (!!) and discussed several times since actually FIXED sometime somehow. At least debian can patch it in its kernels even if the rest of the world carries this around forever. All the details of how this bug works are described here (though Ive included all salient details in this report): http://oss.sgi.com/archives/netdev/2004-07/msg00512.html The offending line in linux-tree-2.6.18 is now at line 1750 of net/ipv4/route.c and can use the same patch as per the above url. As the url above indicates, reproduce this bug with: To trigger this, you need two linux boxes. On the box acting as router (it only needs one ethernet interface), do: ifconfig eth0 down ifconfig eth0 192.168.10.1 netmask 255.255.255.0 ifconfig eth0:1 192.168.99.1 netmask 255.255.255.0 echo 1 > /proc/sys/net/ipv4/ip_forward for f in /proc/sys/net/ipv4/conf/*/shared_media do echo 0 > $f done On the other box, start a sniffer such as ethereal, and do: ifconfig eth0 down ifconfig eth0 192.168.10.2 netmask 255.255.255.0 route add -net 192.168.99.0/24 gw 192.168.10.1 ping 192.168.99.2 You will see ICMP redirect packets sent from 10.1 to 10.2 telling it to route to 99.2 directly itself. Obviously impossible for 10.2 since it's not on the 99.0/24 network. This is tested with 2.6.17-2-vserver-k7 and 2.4.22-ac2 (which I spose is not strictly debian), but the bug has been in the source since linux 2.2 as mentioned. /kc -- Ken Chase - [EMAIL PROTECTED] Toronto CANADA. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
