linux-2.6_2.6.18.dfsg.1-21_i386.changes ACCEPTED
Accepted: linux-2.6_2.6.18.dfsg.1-21.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-21.diff.gz linux-2.6_2.6.18.dfsg.1-21.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-21.dsc linux-doc-2.6.18_2.6.18.dfsg.1-21_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-21_all.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-486_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-21_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-486_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-k7_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb linux-manual-2.6.18_2.6.18.dfsg.1-21_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-21_all.deb linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-21_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18.dfsg.1-21_all.deb linux-source-2.6.18_2.6.18.dfsg.1-21_all.deb to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18.dfsg.1-21_all.deb linux-support-2.6.18-6_2.6.18.dfsg.1-21_all.deb to pool/main/l/linux-2.6/linux-support-2.6.18-6_2.6.18.dfsg.1-21_all.deb linux-tree-2.6.18_2.6.18.dfsg.1-21_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18.dfsg.1-21_all.deb xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-21_i386.deb xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-21_i386.deb Override entries for your package: linux-2.6_2.6.18.dfsg.1-21.dsc - optional devel linux-doc-2.6.18_2.6.18.dfsg.1-21_all.deb
Relocatable kernel
Hey all :) i was playing with Debian and Kexec and i have noticed that Debian kernel is NOT Relocatable , is this not enabled for any particular reason ? -- Armin ranjbar , System Administrator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475852: synaptics touchpad not working
On Fri, 30 May 2008 19:03:17 +0800, Ying-Chun Liu (PaulLiu) wrote: Dear David, Could you please try using i8042.noloop=1 to see if it works? Nothing, still not working. $ cat /proc/cmdline BOOT_IMAGE=(hd0,1)/boot/vmlinuz-2.6.25-2-686 root=/dev/sda1 ro bootkbd=it vga=771 irqpoll i8042.noloop=1 $ grep -i synaptics /var/log/Xorg.0.log (**) |--Input Device Synaptics Touchpad (II) LoadModule: synaptics (II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so (II) Module synaptics: vendor=X.Org Foundation (II) Synaptics touchpad driver version 0.14.6 (1406) Synaptics Touchpad no synaptics event device found Query no Synaptics: 6003C8 (EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device (EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device Synaptics Touchpad (II) UnloadModule: synaptics $ Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#482964: boot freezes with kernel 2.6.24-1-686
On Mon, 26 May 2008, Louis-Maurice De Sousa wrote: [...] no fun that via box, please report upstream in bugzilla.kernel.org and let us know the bug number. Here it is : Bug 10839 has been added to the database Email sent to: [EMAIL PROTECTED], acpi_power- [EMAIL PROTECTED], [EMAIL PROTECTED], bugme- [EMAIL PROTECTED], [EMAIL PROTECTED] Excluding: [EMAIL PROTECTED] If you wish to tweak the kinds of mail Kernel Bug Tracker sends you, you can change your preferences. -- Cordialement. Louis-Maurice De Sousa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445083: marked as done (usb interrupt problem)
Your message dated Sat, 31 May 2008 15:02:34 +0200 with message-id [EMAIL PROTECTED] and subject line Re: usb interrupt problem has caused the Debian Bug report #445083, regarding usb interrupt problem 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.) -- 445083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445083 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: udev Version: 0.114-2 Installing libgphoto2-2version 2.4.0-4 caused all usb devices on a Toshiba A100 to disappear. This seemed to be caused by some device driver being loaded which disabled interrupts from the usb bridge. modifying /etc/udev/rules.d/025_libgphoto2.rules to exclude rules for all devices other than the ones I needed solved this problem. This behaviour was puzzling as there were no devices matching any of the deleted rules, and it was not possible to find any device driver being loaded by udev during the boot process. Setting the irqpoll boot option also renabled the interrupts for the missing devices. I am not quite sure whether this problem relates to the kernel , udev or libgphoto. The kernel version was 2.6.21.5 regards Gregory Eckersley -- -- E-Mail: [EMAIL PROTECTED] phone (61) (3) 98532492,94160130 fax (61) (3) 98532492 mobile (61) 402074026 1/96 Langridge st Collingwood Victoria Australia 3066 5 Reeves Court, Kew , Victoria, Australia 3101 -- ---End Message--- ---BeginMessage--- Version: 2.6.24-1 no follow up since initial report, no answer on ping. closing as most presumably fixed due to newer acpi in newer kernels. -- maks ---End Message---
Bug#444981: marked as done (linux-image-2.6.18-4-686: Oops in free_uid())
Your message dated Sat, 31 May 2008 15:05:47 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-4-686: Oops in free_uid() has caused the Debian Bug report #444981, regarding linux-image-2.6.18-4-686: Oops in free_uid() 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.) -- 444981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444981 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12etch2 Severity: normal Oct 2 12:24:27 olympia kernel: BUG: unable to handle kernel paging request at virtual address 00100104 Oct 2 12:24:27 olympia kernel: printing eip: Oct 2 12:24:27 olympia kernel: c01259aa Oct 2 12:24:27 olympia kernel: *pde = Oct 2 12:24:27 olympia kernel: Oops: 0002 [#1] Oct 2 12:24:27 olympia kernel: SMP Oct 2 12:24:27 olympia kernel: Modules linked in: appletalk button ac battery ipv6 nfs lockd nfs_acl sunrpc ext2 dm_snapshot dm_mirror dm_mod loop psmouse parport_pc serio_raw floppy pcspkr i2c_i801 rtc parport i2c_core shpchp pci_hotplug sg sr_mod cdrom evdev ext3 jbd mbcache raid456 xor raid1 md_mod ide_generic generic ide_core sd_mod tg3 ehci_hcd ata_piix uhci_hcd libata usbcore aic7xxx scsi_transport_spi mptsas mptscsih mptbase scsi_transport_sas scsi_mod thermal processor fan Oct 2 12:24:27 olympia kernel: CPU:2 Oct 2 12:24:27 olympia kernel: EIP:0060:[c01259aa]Not tainted VLI Oct 2 12:24:27 olympia kernel: EFLAGS: 00010002 (2.6.18-4-686 #1) Oct 2 12:24:27 olympia kernel: EIP is at free_uid+0x22/0x64 Oct 2 12:24:27 olympia kernel: eax: 00200200 ebx: f4a1a540 ecx: f4a1a568 edx: 00100100 Oct 2 12:24:27 olympia kernel: esi: 0082 edi: e4edff34 ebp: e5a6e478 esp: e4edfe84 Oct 2 12:24:27 olympia kernel: ds: 007b es: 007b ss: 0068 Oct 2 12:24:27 olympia kernel: Process smbd (pid: 8092, ti=e4ede000 task=f718aaa0 task.ti=e4ede000) Oct 2 12:24:27 olympia kernel: Stack: e5a6e478 e5a6e4a4 c0125e2d f6e25858 c012620f 0023 0023 0022 Oct 2 12:24:27 olympia kernel: e4edff14 f718aaa0 f718af04 c0127441 0021 Oct 2 12:24:27 olympia kernel:b7d70ff4 e4edffbc c01277bb e4edffbc e4edff94 e4edff14 f718af04 0002 Oct 2 12:24:27 olympia kernel: Call Trace: Oct 2 12:24:27 olympia kernel: [c0125e2d] __sigqueue_free+0x1e/0x2d Oct 2 12:24:27 olympia kernel: [c012620f] __dequeue_signal+0x108/0x15c Oct 2 12:24:27 olympia kernel: [c0127441] dequeue_signal+0x2d/0x9c Oct 2 12:24:27 olympia kernel: [c01277bb] get_signal_to_deliver+0xe3/0x3bc Oct 2 12:24:27 olympia kernel: [c01023a6] do_notify_resume+0x71/0x5d7 Oct 2 12:24:27 olympia kernel: [c011624d] __wake_up_common+0x2f/0x53 Oct 2 12:24:27 olympia kernel: [c01672c4] __link_path_walk+0xbe4/0xd1d Oct 2 12:24:27 olympia kernel: [c027fc5a] schedule+0x84e/0x8fe Oct 2 12:24:27 olympia kernel: [c0281470] _spin_unlock_irqrestore+0x8/0x9 Oct 2 12:24:27 olympia kernel: [c012a415] sys_setresuid+0x1ae/0x1c0 Oct 2 12:24:27 olympia kernel: [c0102d0a] work_notifysig+0x13/0x19 Oct 2 12:24:27 olympia kernel: Code: 30 c0 56 9d 5b 31 c0 5e c3 56 85 c0 53 89 c3 74 59 9c 5e fa ba 94 bc 2c c0 e8 ff 1a 09 00 85 c0 74 46 8d 4b 28 8b 53 28 8b 41 04 89 42 04 89 10 89 f2 b8 94 bc 2c c0 c7 41 04 00 02 20 00 c7 43 This happened during normal use, and seems to be the same as reported in http://lkml.org/lkml/2006/10/31/257 and http://lkml.org/lkml/2006/11/4/45 Frank ---End Message--- ---BeginMessage--- Version: 2.6.20-1 fixed in commit 45c18b0bb579b5c1b89f8c99f1b6ffa4c586ba08 that landed in 2.6.19 as this linux image was never uploaded to unstable just mark .20 as the one that fixed the issue. for etch find - http://wiki.debian.org/EtchAndAHalf thanks for report -- maks ---End Message---
Bug#462529: linux-2.6: Add config file support for efika and PS3 (preliminary)
On Fri, 30 May 2008, Geoff Levand wrote:
You don't have CONFIG_LOGO_LINUX_CLUT224 set, so the SPE logos are not
rendered correctly. It looks like the lines of pixel are not aligned.
Geert, can you say why? Is it a bug in the logo code?
If there's no main logo, it also skips (using `return') drawing the extra
SPE logos.
I looked into it a few days ago, and came up with the patch below. But this
is not sufficient to fix the issue, as fb_show_logo_line() needs fb_logo.logo.
As this looks very low-priority to me, I didn't go further.
---
drivers/video/fbmem.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
--- a/drivers/video/fbmem.c
+++ b/drivers/video/fbmem.c
@@ -553,6 +553,7 @@ static inline int fb_show_extra_logos(st
int fb_prepare_logo(struct fb_info *info, int rotate)
{
int depth = fb_get_color_depth(info-var, info-fix);
+ int height = 0;
unsigned int yres;
memset(fb_logo, 0, sizeof(struct logo_data));
@@ -574,12 +575,10 @@ int fb_prepare_logo(struct fb_info *info
depth = 4;
}
- /* Return if no suitable logo was found */
+ /* Skip if no suitable logo was found */
fb_logo.logo = fb_find_logo(depth);
-
- if (!fb_logo.logo) {
- return 0;
- }
+ if (!fb_logo.logo)
+ goto out;
if (rotate == FB_ROTATE_UR || rotate == FB_ROTATE_UD)
yres = info-var.yres;
@@ -588,8 +587,9 @@ int fb_prepare_logo(struct fb_info *info
if (fb_logo.logo-height yres) {
fb_logo.logo = NULL;
- return 0;
+ goto out;
}
+ height = fb_logo.logo-height;
/* What depth we asked for might be different from what we get */
if (fb_logo.logo-type == LINUX_LOGO_CLUT224)
@@ -615,7 +615,8 @@ int fb_prepare_logo(struct fb_info *info
}
}
- return fb_prepare_extra_logos(info, fb_logo.logo-height, yres);
+out:
+ return fb_prepare_extra_logos(info, height, yres);
}
int fb_show_logo(struct fb_info *info, int rotate)
With kind regards,
Geert Uytterhoeven
Software Architect
Sony Network and Software Technology Center Europe
The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium
Phone:+32 (0)2 700 8453
Fax: +32 (0)2 700 8622
E-mail: [EMAIL PROTECTED]
Internet: http://www.sony-europe.com/
Sony Network and Software Technology Center Europe
A division of Sony Service Centre (Europe) N.V.
Registered office: Technologielaan 7 · B-1840 Londerzeel · Belgium
VAT BE 0413.825.160 · RPR Brussels
Fortis Bank Zaventem · BIC GEBABEBB08A · IBAN BE39001382358619
Bug#483837: linux-image-2.6.18-6-686: Clock drift about 20 seconds per hour
Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-18etch5 Severity: normal Too much clock drift with this particular kernel version. Did not have such bad drift with previous kernels. Now clock is OK with 2.6.22 kernel or if running Ubuntu on this same host. NTP can not keep clock in sync, drift is too much. Make complains all the time about timestamps, since home directories in NFS server have correct time stamps, which from this host seem to be in the future. Asus P5B Motherboard $ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation P965/G965 Memory Controller Hub [8086:29a0] (rev 02) 00:01.0 PCI bridge [0604]: Intel Corporation P965/G965 PCI Express Root Port [8086:29a1] (rev 02) 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 [8086:2834] (rev 02) 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 [8086:2835] (rev 02) 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 [8086:283a] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 02) 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 02) 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 [8086:2847] (rev 02) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 [8086:2830] (rev 02) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 [8086:2831] (rev 02) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 [8086:2832] (rev 02) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 [8086:2836] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev f2) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller [8086:2810] (rev 02) 00:1f.2 IDE interface [0101]: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller [8086:2820] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 02) 00:1f.5 IDE interface [0101]: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller [8086:2825] (rev 02) 01:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown device [10de:0402] (rev a1) 02:00.0 SATA controller [0106]: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller [197b:2363] (rev 03) 02:00.1 IDE interface [0101]: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller [197b:2363] (rev 03) 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01) -- 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.22-3-686 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-686 depends on: ii coreutils5.97-5.3The GNU core utilities ii debconf [debconf-2.0]1.5.11etch1 Debian configuration management sy ii initramfs-tools [linux-initr 0.85h tools for generating an initramfs ii module-init-tools3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-6-686 recommends: ii libc6-i686 2.3.6.ds1-13etch5 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-6-686/preinst/elilo-initrd-2.6.18-6-686: true * linux-image-2.6.18-6-686/preinst/already-running-this-2.6.18-6-686: linux-image-2.6.18-6-686/postinst/depmod-error-2.6.18-6-686: false linux-image-2.6.18-6-686/preinst/initrd-2.6.18-6-686: linux-image-2.6.18-6-686/postinst/old-initrd-link-2.6.18-6-686: true linux-image-2.6.18-6-686/preinst/bootloader-initrd-2.6.18-6-686: true linux-image-2.6.18-6-686/preinst/abort-install-2.6.18-6-686: linux-image-2.6.18-6-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-6-686/preinst/overwriting-modules-2.6.18-6-686: true linux-image-2.6.18-6-686/postinst/bootloader-error-2.6.18-6-686: linux-image-2.6.18-6-686/prerm/would-invalidate-boot-loader-2.6.18-6-686: true linux-image-2.6.18-6-686/postinst/bootloader-test-error-2.6.18-6-686: linux-image-2.6.18-6-686/postinst/create-kimage-link-2.6.18-6-686: true linux-image-2.6.18-6-686/postinst/depmod-error-initrd-2.6.18-6-686: false linux-image-2.6.18-6-686/preinst/lilo-initrd-2.6.18-6-686: true linux-image-2.6.18-6-686/postinst/old-dir-initrd-link-2.6.18-6-686: true linux-image-2.6.18-6-686/preinst/failed-to-move-modules-2.6.18-6-686: linux-image-2.6.18-6-686/preinst/abort-overwrite-2.6.18-6-686: linux-image-2.6.18-6-686/prerm/removing-running-kernel-2.6.18-6-686: true
Bug#473800: linux-image-2.6.24: Multiple Reset high speed USB, device using ehci_hcd that sometimes crash the system
I have done some tests with the 2.6.25 from unstable and it seems that it's ok now. However, I have currently very few time to test it and as this bug was not systematic I request some more time before to close it. Thanks, Maxime -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#483830: Writing to a filesystem mounted with 'loop' don't work
Processing commands for [EMAIL PROTECTED]: reassign 483830 linux-2.6 Bug#483830: Writing to a filesystem mounted with 'loop' don't work Warning: Unknown package 'linux-image-2.6.18-5-486' Bug reassigned from package `linux-image-2.6.18-5-486' 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#483830: Writing to a filesystem mounted with 'loop' don't work
Package: linux-image-2.6.18-5-486 Version: 2.6.18.dfsg.1-13etch5 Severity: important When writing into a filesystem mounted using the 'loop' module, the system have unexpected behaviours. Tested with: 2 different Debian Etch running servers, up to date (one Core2Duo and one AMD 4200+). Linux Mint 4.0 personnal computer, up to date (AMD 4000+). Debian Etch i386 fresh install, no updates. Then up to date (AMD 4200+). Debian Etch AMD64 fresh install, no updates. Then up to date (AMD 4200+). Debian Lenny i386 frsh install, no updates. Then up to date (AMD 4200+). Fedora 9 Live: don't have the bug. Thus the bug seems to be related to Debian only. How to reproduce the problem: WARNING: don't do it on a remote computer because the system could completly stop responding. as root: # modprobe loop # cd ~ # mkdir test # cd test # dd if=/dev/zero of=virtualdisk bs=1M count=2000 -- 53 Mb/s # losetup /dev/loop0 virtualdisk # mkfs.ext2 /dev/loop0 -- one system was frozen here once # mount /dev/loop0 /mnt # dd if=/dev/zero of=/mnt/bigfile bs=1M -- the file start growing then nothing happens -- this process never ends -- ctrl+C works after 5 to 15 seconds -- on some systems the computer stop responding -- on some systems some bytes are written to the file every 20 to 40 seconds From another console we can see a strange iowait: # iostat -m 1 avg-cpu: %user %nice %system %iowait %steal %idle 0,500,000,00 50,000,00 49,50 Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn sda 0,00 0,00 0,00 0 0 The size of /mnt/bigfile is between 50 Mb and 400 Mb. The size seems to always be the same on one computer, but vary from computer to computer. i.e. on computer 'A' the file is between 50 Mb and 55 Mb, on computer 'B' the file is between 300 Mb and 310 Mb. Even a simple write without mounting anyfilesystem is affected on some systems: # dd if=/dev/zero of=/dev/loop0 bs=1M -- 14 Mb/s (4 times slower than bare metal speed) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480310: [ixp4xx] armel NSLU2 fails to boot with 2.6.25
* Martin Michlmayr [EMAIL PROTECTED] [2008-05-28 08:54]: * Kevin Price [EMAIL PROTECTED] [2008-05-27 07:45]: If lenny's freeze keeps apex from moving on: Will we need to ask the release manager? Yes, in theory we would; but it seems this package isn't frozen yet. ... okay, the new APEX has moved to testing. Thanks everyone. Seems like we're set for lenny. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483888: linux-image-2.6.18-6-xen-686: Kernel panic after upgrade on loading libcrypt.so
Package: linux-image-2.6.18-6-xen-686 Severity: important On dom0 and/or domU with linux-image-2.6.18-6-xen-686 kernel panics with this message: # grep boot/ /etc/xen/webtest.cfg kernel = '/boot/vmlinuz-2.6.18-6-xen-686' ramdisk = '/boot/initrd.img-2.6.18-6-xen-686' # xm create -c webtest.cfg Freeing unused kernel memory: 148k freed /bin/sh: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory Kernel panic - not syncing: Attempted to kill init! # domU have /lib/tls/libcrypt.so.1 file, and with 2.6.18-5-xen-686 it works. The same message is when starting dom0, machine is rebooting after kernel panic, and loops forever (/boot/grub/menu.list is updated automaticly after update). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476672: Same here
snd-cs46xx can easily be gotten by running: module-assistant -t a-i alsa-source but it would be nice to have it back by default in the Debian kernel images. Cheers, --Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483781: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[EMAIL PROTECTED] wrote: One sees in dmesg FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Try creating files with non-ASCII characters in the name to see the effect. How can one turn off the warning? Ignore the warning, it is completely bogus, because every other IO charset leads to incorrect display (as in: ls output) of filenames created under Windows. See the bottom of http://www.linuxfromscratch.org/lfs/view/6.3/chapter08/fstab.html, and note that Debian has configured the kernel to use the utf8 iocharset by default. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
