Bug#276500: marked as done (system call need nanosecond resolution)
Your message dated Sun, 22 Jun 2008 09:18:13 +0200 with message-id [EMAIL PROTECTED] and subject line #276500: utimensat added as syscall has caused the Debian Bug report #276500, regarding system call need nanosecond resolution 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.) -- 276500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276500 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: kernel-image-2.6.8-1-k7 Version: 2.6.8-3 Severity: normal $ touch -r a b $ stat -c %y a b 2004-10-13 11:36:18.169474381 +0800 2004-10-13 11:36:18.169474000 +0800 the difference messes up test -nt, make, cp -u, etc. etc. From: Paul Eggert [EMAIL PROTECTED] Subject: Re: cp -up forever Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] touch operates by means of system calls. If the system calls mishandle submicrosecond time stamps, touch will as well. So you'll have to direct your bug reports to the kernel people who have misdesigned their system calls. The basic problem is that utimes() has only microsecond resolution; the kernel need to add a system call (utimens(), say?) that supports nanosecond resolution. ---End Message--- ---BeginMessage--- Version: 2.6.22-1 There is a new syscall in 2.6.22, utimensat. It gets a struct timespec which allows nanosecond resultion. It is currently supported on any arch except hppa. Therefor I believe this as resolved from the kernel side. Bastian -- Actual war is a very messy business. Very, very messy business. -- Kirk, A Taste of Armageddon, stardate 3193.0 signature.asc Description: Digital signature ---End Message---
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: normal In 2.6.25 debian kernels, USB_PERSIST has been enabled, to make it possible to suspend with mounted usb storage filesystems which lose power during suspend. Even though the interface in /sys exists, and I write 1 to every device's persist file, I still lose the usb storage devices after resume as if I had suspended without USB_PERSIST. The result is journal commit I/O errors and risk of filesystem corruption. The storage devices in question are a usb SD card reader and a usb stick attached to a usb hub, which contains my / filesystem. I've done a little bit of digging and found someone who reported a suspiciously similar problem. In the thread a patch is mentioned: http://article.gmane.org/gmane.linux.usb.general/2031/match=usb+persist+issue The patch was supposed to be submitted for 2.6.25, but the 2.6.25 debian-patched kernel sources don't seem to have it. I have not been able to test yet wether this patch fixes my problem. Kind regards, Astrid -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Thu Jun 12 16:26:30 UTC 2008 ** Command line: root=/dev/disk/by-uuid/343c422f-ede8-4fc2-a9d7-ee424e9dceb0 ro quiet ** Not tainted ** Kernel log: [5.930035] usb 5-8.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [6.148112] usb 5-8.4: new high speed USB device using ehci_hcd and address 5 [6.258532] usb 5-8.4: configuration #1 chosen from 1 choice [6.259369] usb 5-8.4: New USB device found, idVendor=0324, idProduct=bc06 [6.259382] usb 5-8.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6.259389] usb 5-8.4: Product: RALLY2 [6.259394] usb 5-8.4: Manufacturer: OCZ Technology [6.259400] usb 5-8.4: SerialNumber: AA04012700091894 [6.272678] scsi3 : SCSI emulation for USB Mass Storage devices [6.278790] usbcore: registered new interface driver usb-storage [6.278801] USB Mass Storage support registered. [6.281782] usb-storage: device found at 5 [6.281791] usb-storage: waiting for device to settle before scanning [ 10.582757] usb-storage: device scan complete [ 10.583355] scsi 2:0:0:0: Direct-Access USB2.0 CardReader SD0 0100 PQ: 0 ANSI: 0 [ 10.955159] sd 2:0:0:0: [sdb] 1990656 512-byte hardware sectors (1019 MB) [ 10.955561] sd 2:0:0:0: [sdb] Write Protect is off [ 10.955561] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 10.955561] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 10.956629] sd 2:0:0:0: [sdb] 1990656 512-byte hardware sectors (1019 MB) [ 10.957032] sd 2:0:0:0: [sdb] Write Protect is off [ 10.957032] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 10.957032] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 10.957032] sdb: sdb1 [ 10.958190] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 11.224252] usb-storage: device scan complete [ 11.225350] scsi 3:0:0:0: Direct-Access OCZ RALLY2 1100 PQ: 0 ANSI: 0 CCS [ 11.232097] sd 3:0:0:0: [sdc] 31326208 512-byte hardware sectors (16039 MB) [ 11.232950] sd 3:0:0:0: [sdc] Write Protect is off [ 11.232960] sd 3:0:0:0: [sdc] Mode Sense: 43 00 00 00 [ 11.232966] sd 3:0:0:0: [sdc] Assuming drive cache: write through [ 11.235809] sd 3:0:0:0: [sdc] 31326208 512-byte hardware sectors (16039 MB) [ 11.236688] sd 3:0:0:0: [sdc] Write Protect is off [ 11.236696] sd 3:0:0:0: [sdc] Mode Sense: 43 00 00 00 [ 11.236702] sd 3:0:0:0: [sdc] Assuming drive cache: write through [ 11.236786] sdc: sdc1 [ 11.237634] sd 3:0:0:0: [sdc] Attached SCSI removable disk [ 11.446583] EXT3-fs: INFO: recovery required on readonly filesystem. [ 11.446597] EXT3-fs: write access will be enabled during recovery. [ 18.007564] kjournald starting. Commit interval 5 seconds [ 18.007564] EXT3-fs: recovery complete. [ 18.010505] EXT3-fs: mounted filesystem with ordered data mode. [ 21.318987] Linux agpgart interface v0.103 [ 21.358280] agpgart: Detected an Intel 915GM Chipset. [ 21.358570] agpgart: Detected 7932K stolen memory. [ 21.388869] agpgart: AGP aperture is 256M @ 0xd000 [ 22.044439] Atheros(R) L2 Ethernet Driver - version 2.0.3 [ 22.08] Copyright (c) 2007 Atheros Corporation. [ 22.044525] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 22.044549] PCI: Setting latency timer of device :03:00.0 to 64 [ 22.761196] input: Power Button (FF) as /class/input/input1 [ 22.795657] ACPI: Power Button (FF) [PWRF] [ 22.795847] input: Lid Switch as /class/input/input2 [ 22.821849] ACPI: Lid Switch [LID] [ 22.822048] input: Sleep Button (CM) as /class/input/input3 [ 22.848798] ACPI: Sleep Button (CM) [SLPB] [ 22.848937] input: Power Button (CM) as /class/input/input4 [ 22.873879] ACPI: Power Button (CM) [PWRB] [ 23.832967] ACPI: AC Adapter [AC0] (on-line) [ 25.099544]
Processed: Re: Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
Processing commands for [EMAIL PROTECTED]: tags 487490 fixed-upstream Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work There were no tags set. Tags added: fixed-upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
tags 487490 fixed-upstream thanks On Sun, Jun 22, 2008 at 10:28:55AM +0200, Astrid S. de Wijn wrote: I've done a little bit of digging and found someone who reported a suspiciously similar problem. In the thread a patch is mentioned: http://article.gmane.org/gmane.linux.usb.general/2031/match=usb+persist+issue The patch was supposed to be submitted for 2.6.25, but the 2.6.25 debian-patched kernel sources don't seem to have it. I have not been able to test yet wether this patch fixes my problem. There was a commit upstream which does that in a different way: 5e6effaed6da94e727cd45f945ad2489af8570b3 Bastian -- Spock: The odds of surviving another attack are 13562190123 to 1, Captain. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 487421 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.29 severity 487421 important Bug#487421: Early boot-time kernel panic with linux-image-2.6.25-2-amd64 (2.6.25-5). Severity set to `important' 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#487421: Early boot-time kernel panic with linux-image-2.6.25-2-amd64 (2.6.25-5).
On Sat, Jun 21, 2008 at 07:43:37PM +0200, Valentin QUEQUET wrote:
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-5
Severity: grave
Justification: renders package unusable
learn to set severities, not working on *one* box is not grave
Hello all,
I experience early boot-time kernel panic with linux-image-2.6.25-2-amd64
(2.6.25-5)
on my amd64 box.
After having read tons of posts on forums, and particularly:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482773
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479101
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607#96
I know that the bug I discovered is closely related to already reported bug
#479607
which apparently concerns lilo because:
The bug - kernel panic - happens just before any piece of userspace code
being
loaded from initial RAM disk :
===
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions :
010065536ram0 (driver?)
..
..
..
010f65536ram15 (driver?)
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(22,65)
===
But I have to add food for thought:
Here follow key files on my Debian_amd64 system:
ls -l /boot gave: ( cropped the list to meaningful parts )
-rw-r--r-- 1 root root 6621847 jun 21 11:19 initrd.img-2.6.18-6-amd64
-rw--- 1 root root 7090895 jun 21 09:40 initrd.img-2.6.24-1-amd64
-rw-r--r-- 1 root root 7276007 jun 21 11:41 initrd.img-2.6.25-2-amd64
-rw-r--r-- 1 root root 21132800 jun 21 18:03 initrd.img-2.6.25-2-amd64.cpio
-rw-r--r-- 1 root root 5598429 jun 21 18:06 initrd.img-2.6.25-2-amd64_light
-rw-r--r-- 1 root root 16109056 jun 21 18:12
initrd.img-2.6.25-2-amd64_light.cpio
-rw-r--r-- 1 root root 1512362 jun 6 09:20 vmlinuz-2.6.18-6-amd64
-rw-r--r-- 1 root root 1668248 mai 10 11:32 vmlinuz-2.6.24-1-amd64
-rw-r--r-- 1 root root 1727488 jun 12 18:35 vmlinuz-2.6.25-2-amd64
ls -l /boot/initrd.img-2.6.*amd64{,_light}{,.cpio} gave: ( cropped the list
to meaningful parts )
/boot/initrd.img-2.6.18-6-amd64:gzip compressed data, from Unix,
last modified: Sat Jun 21 11:19:01 2008
/boot/initrd.img-2.6.24-1-amd64:gzip compressed data, from Unix,
last modified: Sat Jun 21 09:40:50 2008
/boot/initrd.img-2.6.25-2-amd64:gzip compressed data, from Unix,
last modified: Sat Jun 21 11:41:17 2008
/boot/initrd.img-2.6.25-2-amd64.cpio: ASCII cpio archive (SVR4 with no
CRC)
/boot/initrd.img-2.6.25-2-amd64_light: gzip compressed data, from Unix,
last modified: Sat Jun 21 18:06:31 2008, max compression
/boot/initrd.img-2.6.25-2-amd64_light.cpio: ASCII cpio archive (SVR4 with no
CRC)
WHERE initrd.img-2.6.25-2-amd64_light is a manually lightened customization
of the
original initrd.
Finally, since I only experience trouble - very early kernel panic - with
2.6.25-2-amd64
regardless wether my initrd is heavy or not, how do you explain this strange
behavior ?
In hope my report will prove useful.
Sincerely,
Valentin QUEQUET
read http://wiki.debian.org/InitramfsDebug
and provide info based on that.
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421270: marked as done (gdb: fails to debug multithread programs)
Your message dated Sun, 22 Jun 2008 13:39:52 +0200 with message-id [EMAIL PROTECTED] and subject line Re: 32-bit ptrace with a 64-bit kernel has caused the Debian Bug report #421270, regarding gdb: fails to debug multithread programs 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.) -- 421270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421270 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: gdb Version: 6.6.dfsg-1 Severity: important When I try to debug a multithread application, I get a general error as it is showed below: === ~$gdb ./hello GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i486-linux-gnu... Using host libthread_db library /lib/tls/libthread_db.so.1. (gdb) start Breakpoint 1 at 0x80483a5: file hello.c, line 5. Starting program: /home/dpotapov/hello warning: Lowest section in system-supplied DSO at 0xe000 is .hash at e0b4 [Thread debugging using libthread_db enabled] Error while reading shared library symbols: Cannot find new threads: generic error Cannot find user-level thread for LWP 2518: generic error === I have tried to use both 'stable' and 'unstable' versions of gdb with the same result. I suspect that the problem has something to do with -amd64 kernel (linux-image-2.6-amd64_2.6.18+6_i386.deb), because at the address 0xe000 (which mentioned in the above warning) is the address of linux-gate.so.1, which is a virtual DSO provided by the kernel. === $ldd ./hello linux-gate.so.1 = (0xe000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xf7ecb000) libc.so.6 = /lib/tls/libc.so.6 (0xf7d99000) /lib/ld-linux.so.2 (0xf7ef4000) === The error happens only when libpthread is linked to the program, but the warning about system-supplied DSO is always showed up. Also if the debug version of libthread_db is used then there is no error, but only the warning. === ~$LD_LIBRARY_PATH=/usr/lib/debug gdb ./hello GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i486-linux-gnu... Using host libthread_db library /usr/lib/debug/libthread_db.so.1. (gdb) start Breakpoint 1 at 0x80483a5: file hello.c, line 5. Starting program: /home/dpotapov/hello warning: Lowest section in system-supplied DSO at 0xe000 is .hash at e0b4 [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 2542)] [Switching to Thread 16384 (LWP 2542)] main () at hello.c:5 5 printf(Hello world\n); === -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages gdb depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libncurses5 5.5-5Shared libraries for terminal hand ii libreadline55.2-2GNU readline and history libraries gdb recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.24-1 has been fixed upstream, thus closing. -- maks ---End Message---
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
On Sun, Jun 22, 2008 at 10:28:55AM +0200, Astrid S. de Wijn wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: normal In 2.6.25 debian kernels, USB_PERSIST has been enabled, to make it possible to suspend with mounted usb storage filesystems which lose power during suspend. Even though the interface in /sys exists, and I write 1 to every device's persist file, I still lose the usb storage devices after resume as if I had suspended without USB_PERSIST. The result is journal commit I/O errors and risk of filesystem corruption. The storage devices in question are a usb SD card reader and a usb stick attached to a usb hub, which contains my / filesystem. I've done a little bit of digging and found someone who reported a suspiciously similar problem. In the thread a patch is mentioned: http://article.gmane.org/gmane.linux.usb.general/2031/match=usb+persist+issue The patch was supposed to be submitted for 2.6.25, but the 2.6.25 debian-patched kernel sources don't seem to have it. I have not been able to test yet wether this patch fixes my problem. Kind regards, Astrid please checkout 2.6.26-rcX kernels. they have got patches for it see apt trunk lines http://wiki.debian.org/DebianKernel (beware to blacklist snd-pcsp ) -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422284: marked as done (linux-image-2.6.18-4-686: bad page state)
Your message dated Sun, 22 Jun 2008 14:01:42 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-4-686: bad page state has caused the Debian Bug report #422284, regarding linux-image-2.6.18-4-686: bad page state 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.) -- 422284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422284 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12etch1 Severity: important This morning the following kernel message appeared in my console log: Bad page state in process 'dpkg-query' page:c1209300 flags:0x8000 mapping: mapcount:0 count:8192 Trying to fix it up, but a reboot is needed Backtrace: [c0144f15] bad_page+0x41/0x67 [c01456b3] get_page_from_freelist+0x22e/0x36e [c027fc22] schedule+0x84e/0x8fe [c0145841] __alloc_pages+0x4e/0x275 [c01ae1f0] __generic_unplug_device+0x14/0x1f [c0146b97] __do_page_cache_readahead+0xc8/0x1e8 [e09cf97d] dm_any_congested+0x2f/0x35 [dm_mod] [e09d12da] dm_table_any_congested+0x32/0x48 [dm_mod] [e09cf97d] dm_any_congested+0x2f/0x35 [dm_mod] [c0143c8c] filemap_nopage+0x15b/0x313 [c014c154] __handle_mm_fault+0x26e/0x740 [c014eb88] do_brk+0x133/0x1c3 [c01154b6] do_page_fault+0x18a/0x481 [c011532c] do_page_fault+0x0/0x481 [c01037f9] error_code+0x39/0x40 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85g tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-4-686 recommends: ii libc6-i686 2.3.6.ds1-13 GNU C Library: Shared libraries [i -- debconf information excluded ---End Message--- ---BeginMessage--- closing as most likely hardware bug. -- maks ---End Message---
Bug#426414: marked as done (kernel: time jumps and usb resets)
Your message dated Sun, 22 Jun 2008 14:05:01 +0200 with message-id [EMAIL PROTECTED] and subject line Re: kernel: time jumps and usb resets has caused the Debian Bug report #426414, regarding kernel: time jumps and usb resets 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.) -- 426414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426414 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-1-powerpc Version: 2.6.21-4 Severity: important File: kernel I don't know if this is a hardware problem or a kernel bug. the same hardware had served correctly for years, so I sincerely hope it's a kernel bug... I'm not sure when the problem started to display... a crontab line for root runs ntpdate -q every single minute... the drift looks more or less constant, until occasional jumps. these jumps are coincident with some kernel logging... here are the syslog lines, bracketed by the output of ntpdate: ... 28 May 16:46:04 ntpdate[27236]: step time server 206.57.44.149 offset -23.773322 sec May 28 16:49:06 localhost kernel: usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 May 28 16:49:07 localhost kernel: usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 28 May 16:49:10 ntpdate[27256]: step time server 206.57.44.149 offset -187.783438 sec ... 28 May 16:55:04 ntpdate[27340]: step time server 206.57.44.149 offset -187.782406 sec May 28 16:57:43 localhost kernel: usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 May 28 16:57:43 localhost kernel: usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 28 May 16:57:46 ntpdate[27362]: step time server 206.57.44.149 offset -297.535529 sec ... 28 May 17:01:04 ntpdate[27427]: step time server 206.57.44.149 offset -297.534059 sec May 28 17:03:27 localhost kernel: usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 May 28 17:03:27 localhost kernel: usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 28 May 17:03:30 ntpdate[27453]: step time server 206.57.44.149 offset -409.487201 sec ... are these kernel logs an other effect of the jumps, or are they closely related to the cause? maybe it's also relevant that I am running wmaker and that more or less with the same frequency of these problems (maybe in coincidence?) I have to restart the window manager because the keyboard stops working (but the keys simulating mouse buttons 2 and 3 keep working). -- Package-specific info: ** Version: Linux version 2.6.21-1-powerpc (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #1 Sat May 26 14:30:26 CEST 2007 ** Not tainted ** Kernel log: sdf: Mode Sense: 27 00 00 00 sdf: assuming drive cache: write through sdf: [mac] sdf1 sdf2 sdf3 sdf4 sdf5 sdf6 sd 7:0:0:0: Attached scsi disk sdf sd 7:0:0:0: Attached scsi generic sg5 type 0 hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: filesystem is marked journaled, leaving read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. usb 2-1.2: USB disconnect, address 10 ieee1394: Node changed: 0-01:1023 - 0-00:1023 ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[001010055b43] Synchronizing SCSI cache for disk sda: FAILED status = 0, message = 00, host = 1, driver = 00 6usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 usb 1-1.2: reset full speed USB device using
Bug#413094: marked as done (linux-image-2.6.18-4-686: ata_piix module doesn't recognize a second harddisk)
Your message dated Sun, 22 Jun 2008 14:01:01 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-4-686: ata_piix module doesn't recognize a second harddisk has caused the Debian Bug report #413094, regarding linux-image-2.6.18-4-686: ata_piix module doesn't recognize a second harddisk 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.) -- 413094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413094 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: important We have some HP dc7700 installed with GNU/Linux 4.0, kernel version is linux-image-2.6.18-4-686. With this version I can't see the second installed SATA disk. If I use a (self compiled) kernel version 2.6.20.1, I see this disk as /dev/sdb. lspci -vv | grep -A15 SATA 00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Hewlett-Packard Company Unknown device 2802 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 233 Region 0: I/O ports at ignored Region 1: I/O ports at ignored Region 2: I/O ports at ignored Region 3: I/O ports at ignored Region 4: I/O ports at 20e0 [size=16] Region 5: I/O ports at 20f0 [size=16] Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- lsmod|grep ata: ata_piix 13576 7 libata 89396 1 ata_piix scsi_mod 124168 4 sg,sr_mod,sd_mod,libata -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs ii module-init-tools 3.3-pre4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-4-686 recommends: ii libc6-i686 2.3.6.ds1-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/kimage-is-a-directory: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true ---End Message--- ---BeginMessage--- Version: 2.6.20-1 If I use a (self compiled) kernel version 2.6.20.1, I see this disk as /dev/sdb. closing as fixed in newer upstream, see http://wiki.debian.org/EtchAndAHalf thanks for report -- maks ---End Message---
Bug#425703: marked as done (linux-image-2.6.18-4-xen-686: xen kernel oopses on removing the netloop module)
Your message dated Sun, 22 Jun 2008 14:03:37 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.18-4-xen-686: xen kernel oopses on removing the netloop module has caused the Debian Bug report #425703, regarding linux-image-2.6.18-4-xen-686: xen kernel oopses on removing the netloop module 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.) -- 425703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425703 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-4-xen-686 Version: 2.6.18.dfsg.1-12 Severity: critical Justification: breaks the whole system On a running xen machine, I tried the command: rmmod netloop. This is an obvious issue that I should not do that, however this module should not be unloaded. Result: kernel panic and restart of machine. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-xen-686 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.18-4-xen-686 depends on: ii initramfs-tools 0.87btools for generating an initramfs ii linux-modules-2.6.18-4- 2.6.18.dfsg.1-12 Linux 2.6.18 modules on i686 Versions of packages linux-image-2.6.18-4-xen-686 recommends: ii libc6-xen 2.5-7 GNU C Library: Shared libraries [X -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.25-1 upstream paravirt ops merged Xen kernels no longer features sch fancy behayviour. thus closing -- maks ---End Message---
Bug#428807: marked as done (linux-image-2.6.21-1-powerpc: keyboard and touchpad doesn't work)
Your message dated Sun, 22 Jun 2008 14:16:36 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-1-powerpc: keyboard and touchpad doesn't work has caused the Debian Bug report #428807, regarding linux-image-2.6.21-1-powerpc: keyboard and touchpad doesn't work 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.) -- 428807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428807 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-1-powerpc Version: 2.6.21-4 Severity: important After booting up on 2.6.21 keyboard and tuchpad doesn't work. I have few kernels, and last fully-working kernel is 2.6.18-4-powerpc. Simpliy rebooting on old kernel makes keyboard avalialble again. Attached kernel.log diff betweeen 2.6.18 (working keyboard), and 2.6.20 (not working). -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.18-4-powerpc Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.21-1-powerpc depends on: ii initramfs-tools [linux-initr 0.87b tools for generating an initramfs ii mkvmlinuz33 create a kernel to boot a PowerPC ii module-init-tools3.3-pre11-1 tools for managing Linux kernel mo linux-image-2.6.21-1-powerpc recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.21-1-powerpc/preinst/bootloader-initrd-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/prerm/removing-running-kernel-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.21-1-powerpc/postinst/old-dir-initrd-link-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/postinst/depmod-error-initrd-2.6.21-1-powerpc: false linux-image-2.6.21-1-powerpc/postinst/old-system-map-link-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/preinst/elilo-initrd-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/postinst/bootloader-error-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/preinst/abort-install-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/postinst/create-kimage-link-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/preinst/overwriting-modules-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/postinst/bootloader-test-error-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/preinst/initrd-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/preinst/lilo-initrd-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/preinst/failed-to-move-modules-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/preinst/abort-overwrite-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/prerm/would-invalidate-boot-loader-2.6.21-1-powerpc: true linux-image-2.6.21-1-powerpc/postinst/depmod-error-2.6.21-1-powerpc: false linux-image-2.6.21-1-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.21-1-powerpc/preinst/already-running-this-2.6.21-1-powerpc: linux-image-2.6.21-1-powerpc/postinst/old-initrd-link-2.6.21-1-powerpc: true --- kern.2.6.18-4.striped.log 2007-06-14 12:02:42.0 +0200 +++ kern.2.6.21.striped.log 2007-06-14 12:02:53.0 +0200 @@ -1,12 +1,12 @@ klogd 1.4.1#17.2, log source = /proc/kmsg started. -Inspecting /boot/System.map-2.6.18-4-powerpc -Loaded 23099 symbols from /boot/System.map-2.6.18-4-powerpc. -Symbols match kernel version 2.6.18. +Inspecting /boot/System.map-2.6.21-1-powerpc +Loaded 24453 symbols from /boot/System.map-2.6.21-1-powerpc. +Symbols match kernel version 2.6.21. No module symbols loaded - kernel modules not enabled. Using PowerMac machine description Total memory = 256MB; using 512kB for hash table (at cff8) -Linux version 2.6.18-4-powerpc (Debian 2.6.18.dfsg.1-11) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Wed Feb 21 13:39:54 CET 2007 -Found initrd at 0xc190:0xc1e1a000 +Linux version 2.6.21-1-powerpc (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #1 Sat May 26 14:30:26 CEST 2007 +Found initrd at 0xc190:0xc1eb1000 Found UniNorth memory controller host bridge @ 0xf800 revision: 0xd2 Mapped at 0xfdfc Found a Intrepid mac-io controller, rev: 0, mapped at 0xfdf4 @@ -14,6 +14,7 @@ PowerMac motherboard: iBook G4 via-pmu: Server Mode is disabled PMU driver v2 initialized for Core99, firmware: 0c +Entering add_active_range(0, 0, 65536) 0 entries of 256
Bug#427841: marked as done (linux-image-2.6.21-1-amd64: Kernel version 2.6.21-4 breaks USB permissions)
Your message dated Sun, 22 Jun 2008 14:15:07 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-1-amd64: Kernel version 2.6.21-4 breaks USB permissions has caused the Debian Bug report #427841, regarding linux-image-2.6.21-1-amd64: Kernel version 2.6.21-4 breaks USB permissions 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.) -- 427841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427841 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-1-amd64 Version: 2.6.21-4 Severity: important The latest version of the kernel package breaks the permissions for access to USB devices, causing the nut-usb package to break. Please see http://www.gossamer-threads.com/lists/linux/kernel/777580 If I run the nut newhidups driver with it remaining as root, then everything works fine. If I tell it to relinquish its privileges (as per default) then it fails with the following debug messages: # /lib/nut/newhidups -u nut -DD -a faithful Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '2' Checking device (051D/0002) (001/002) - VendorID: 051d - ProductID: 0002 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 1 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 0 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... Unable to get HID descriptor (error sending control message: Operation not permitted) HID descriptor retrieved (Reportlen = 1217) Unable to get Report descriptor (-1): Operation not permitted -- Package-specific info: ** Version: Linux version 2.6.21-1-amd64 (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #1 SMP Sat May 26 17:22:54 CEST 2007 ** Tainted: PFSRMB ** Kernel log: ACPI: PCI Interrupt :00:0f.2[C] - GSI 22 (level, low) - IRQ 22 ohci_hcd :00:0f.2: OHCI Host Controller ohci_hcd :00:0f.2: new USB bus registered, assigned bus number 3 ohci_hcd :00:0f.2: irq 22, io mem 0xfdffc000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 3 ports detected ACPI: PCI Interrupt :00:0f.3[D] - GSI 23 (level, low) - IRQ 23 ehci_hcd :00:0f.3: EHCI Host Controller ehci_hcd :00:0f.3: new USB bus registered, assigned bus number 4 ehci_hcd :00:0f.3: debug port 1 ehci_hcd :00:0f.3: irq 23, io mem 0xfdffb000 ehci_hcd :00:0f.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 8 ports detected ACPI: PCI Interrupt :02:07.0[A] - GSI 18 (level, low) - IRQ 18 eth1: Via 86C926 found at 0xef00, IRQ 18, 08:00:30:00:1C:AC. hda: max request size: 128KiB hda: 33683328 sectors (17245 MB) w/512KiB Cache, CHS=33416/16/63, UDMA(33) hda: cache flushes not supported hda: hda1 hda2 hda3 hda4 hdb: max request size: 512KiB hdb: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63, UDMA(133) hdb: cache flushes supported hdb: hdb1 hdb2 hdb3 hdb5 hdb6 hdb7 hdb4 usb 2-1: new low speed USB device using ohci_hcd and address 3 Attempting manual resume usb 2-1: configuration #1 chosen from 1 choice usbcore: registered new interface driver hiddev input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /class/input/input1 input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-:00:0f.1-1 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. input: PC Speaker as /class/input/input2 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 pnp: the driver 'parport_pc' has been registered pnp: match found with the PnP device '00:09' and the driver 'parport_pc' parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] ali15x3_smbus :00:03.1: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr ali15x3_smbus :00:03.1: ALI15X3 not
Bug#430779: marked as done (linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected.)
Your message dated Sun, 22 Jun 2008 14:18:54 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected. has caused the Debian Bug report #430779, regarding linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected. 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.) -- 430779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430779 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-2-686 Severity: important This bug is a regression from linux-image-2.6.18-4-686 2.6.18.dfsg.1-1 When booted with 2.6.21, the mouse pointer moves with an unacceptable delay. Sound played with xmms has interrupts, and even now, while typing this report on the console, some characters appear with a delay on the screen, (or disappear with delay when I remove something) At least the mouse issue can be improved slightly setting cpufreq governor to userspace and setting the highest possible cpu frequency. I guess this report is not very useful, because I don't provide any logfiles. Can you give me any hints, how to produce something useful? -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 2.6.24-1 since the scheduler changed a lot thus closing. -- maks ---End Message---
Bug#429662: marked as done (linux-image-2.6.21-1-powerpc: Suspend fails on PowerBook)
Your message dated Sun, 22 Jun 2008 14:17:47 +0200 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.21-1-powerpc: Suspend fails on PowerBook has caused the Debian Bug report #429662, regarding linux-image-2.6.21-1-powerpc: Suspend fails on PowerBook 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.) -- 429662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429662 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.21-1-powerpc Version: 2.6.21-4 Severity: important Since upgrading to this kernel version any attempt to suspend my laptop has failed. The machine begins to suspend, complains that it cannot suspend and then attempts to abort the suspend but fails to do so, forcing a manual reset. Both aspects of this are a problem - the failure to abort is a more serious issue for me since it can cause data loss. When I have access to something I can use to capture the console output I will provie that, unfortunately I don't have anything right now. The machine is: processor : 0 cpu : 7447A, altivec supported clock : 749.999000MHz revision: 0.1 (pvr 8003 0101) bogomips: 36.73 timebase: 18432000 platform: PowerMac machine : PowerBook5,4 motherboard : PowerBook5,4 MacRISC3 Power Macintosh detected as : 287 (PowerBook G4 15) pmac flags : 001b L2 cache: 512K unified pmac-generation : NewWorld -- Package-specific info: ** Version: Linux version 2.6.21-1-powerpc (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #1 Sat May 26 14:30:26 CEST 2007 ** Not tainted ** Kernel log: Yenta: Routing CardBus interrupts to PCI Yenta TI: socket 0001:10:13.0, mfunc 0x1002, devctl 0x60 Yenta: ISA IRQ mask 0x, PCI irq 53 Socket status: 3087 pcmcia: parent PCI bridge I/O window: 0x0 - 0x7f pcmcia: parent PCI bridge Memory window: 0xf300 - 0xf3ff pcmcia: parent PCI bridge Memory window: 0x8000 - 0xafff bcm43xx driver PCI: Enabling device 0001:10:12.0 (0004 - 0006) bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243 bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243 bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243 bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off ieee1394: Initialized config rom entry `ip1394' PCI: Enabling device 0001:10:1b.2 (0004 - 0006) ehci_hcd 0001:10:1b.2: EHCI Host Controller ehci_hcd 0001:10:1b.2: new USB bus registered, assigned bus number 4 ehci_hcd 0001:10:1b.2: irq 63, io mem 0xa000 ehci_hcd 0001:10:1b.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 5 ports detected Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized PowerMac i2c bus pmu 2 registered PowerMac i2c bus pmu 1 registered PowerMac i2c bus mac-io 0 registered PowerMac i2c bus uni-n 1 registered PowerMac i2c bus uni-n 0 registered sungem.c:v0.98 8/24/03 David S. Miller ([EMAIL PROTECTED]) PHY ID: 1410cc1, addr: 0 eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:c1:97:b6 eth1: Found Marvell 88E PHY PCI: Enabling device 0002:24:0e.0 ( - 0002) ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[40] MMIO=[f500-f50007ff] Max Packet=[4096] IR/IT contexts=[8/8] Bluetooth: HCI USB driver ver 2.9 hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, (U)DMA Uniform CD-ROM driver Revision: 3.20 usbcore: registered new interface driver hci_usb snd-aoa-fabric-layout: found bus with layout 51 snd-aoa-fabric-layout: Using direct GPIOs snd-aoa-codec-tas: found 'deq' node snd-aoa-fabric-layout: can use this codec snd-aoa-codec-tas: tas found, addr 0x35 on /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] ieee1394: Host added: ID:BUS[0-00:1023] GUID[000d93fffec197b6] eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) Adding 500644k swap on /dev/hda6. Priority:-1 extents:1 across:500644k EXT3 FS on hda3, internal journal SCSI subsystem initialized snd-powermac no longer handles any machines with a layout-id property in the device-tree, use snd-aoa. apm_emu: APM Emulation 0.5 initialized.
Bug#478419: marked as done (linux-image-2.6.25: firewire ipod no longer works under kernels = 2.6.22 with new firewire stack)
Your message dated Sun, 22 Jun 2008 14:26:49 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#478419: linux-image-2.6.25: firewire ipod no longer works under kernels = 2.6.22 with new firewire stack has caused the Debian Bug report #478419, regarding linux-image-2.6.25: firewire ipod no longer works under kernels = 2.6.22 with new firewire stack 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.) -- 478419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478419 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.25-rc8-686 Version: 2.6.25~rc8-1~experimental.1~snapshot.11067 Severity: normal File: linux-image-2.6.25 My firewire ipod no longer works with either the new juju firewire stack (firewire_sbp2) nor the old ieee1394 (sbp2) stack. The ipod has worked for many years prior to the switch in 2.6.22 to the new stack. The ipod works on macs and pcs so it's not an ipod error. The ipod connects fine and I can see the music, but when I try to write anything (either with gnupod, gtkpod or amarok) then the ipod just sits there with the hard drive clicking over every 5-10 seconds in what sounds to be a reset noise. The system slows to a crawl and the only way I can resume is to pull out the firewire pcmcia card. Interestingly, the problem/symptoms seem consistent between the two stacks? I raised these issues in bug #475295 but that seems to have devolved into an old vs new flamefest and I'm afraid my useability concerns got lost in there :( I understand the need for secure and clean code for the firewire stack, but arguing that the userspace applications need to catch up to a stack that doesn't even work is not an argument. Meanwhile, my ipod continues not to work. -- Package-specific info: ** Version: Linux version 2.6.25-rc8-686 (Debian 2.6.25~rc8-1~experimental.1~snapshot.11067) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14+2)) #1 SMP Fri Apr 11 00:53:51 UTC 2008 ** Command line: root=/dev/hda2 ro acpi_sleep=s3_bios ** Not tainted ** Kernel log: [53162.617483] PM: Syncing filesystems ... done. [53164.385786] Freezing user space processes ... (elapsed 0.08 seconds) done. [53164.472410] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [53164.472628] Suspending console(s) [53164.490373] drm_sysfs_suspend [53166.086465] serial 00:09: disabled [53166.209878] ACPI: PCI interrupt for device :02:02.0 disabled [53166.225838] ACPI: PCI interrupt for device :02:01.0 disabled [53166.225844] ACPI handle has no context! [53166.241853] radeonfb (:01:00.0): suspending for event: 2... [53166.242194] ACPI: PCI interrupt for device :00:1f.5 disabled [53166.242346] ACPI: PCI interrupt for device :00:1d.7 disabled [53166.259430] ACPI: PCI interrupt for device :00:1d.2 disabled [53166.259458] ACPI: PCI interrupt for device :00:1d.1 disabled [53166.259484] ACPI: PCI interrupt for device :00:1d.0 disabled [53166.261508] ACPI: Preparing to enter system sleep state S3 [53166.270720] Disabling non-boot CPUs ... [53166.270720] Intel machine check architecture supported. [53166.270728] Intel machine check reporting enabled on CPU#0. [53166.270764] Back to C! [53166.319014] PCI: Enabling device :00:1d.0 ( - 0001) [53166.319021] ACPI: PCI Interrupt :00:1d.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 [53166.319029] PCI: Setting latency timer of device :00:1d.0 to 64 [53166.319035] PM: Writing back config space on device :00:1d.0 at offset f (was 100, writing 10b) [53166.319046] PM: Writing back config space on device :00:1d.0 at offset 8 (was 1, writing 1801) [53166.319076] usb usb1: root hub lost power or was reset [53166.319091] PCI: Enabling device :00:1d.1 ( - 0001) [53166.319094] ACPI: PCI Interrupt :00:1d.1[B] - Link [LNKD] - GSI 11 (level, low) - IRQ 11 [53166.319101] PCI: Setting latency timer of device :00:1d.1 to 64 [53166.319107] PM: Writing back config space on device :00:1d.1 at offset f (was 200, writing 20b) [53166.319119] PM: Writing back config space on device :00:1d.1 at offset 8 (was 1, writing 1821) [53166.319146] usb usb2: root hub lost power or was reset [53166.319165] PCI: Enabling device :00:1d.2 ( - 0001) [53166.319168] ACPI: PCI Interrupt :00:1d.2[C] - Link [LNKC] - GSI 11 (level, low) - IRQ 11 [53166.319175] PCI: Setting latency timer of device :00:1d.2 to 64 [53166.319181] PM: Writing back config space on device :00:1d.2 at offset f (was 300, writing 30b) [53166.319192] PM: Writing back config
Bug#487421: Early boot-time kernel panic with linux-image-2.6.25-2-amd64 (2.6.25-5).
Hello, Maks and others. Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-5 Severity: grave Justification: renders package unusable learn to set severities, not working on *one* box is not grave Really, I apologize, if not too late ;-) But I've been influenced in this choice by some other thread. It would have been *nice* if you gave me a pointer to learn more about that. Furthermore, I don't think this problem is sporadic or even endemic to Compaq Presario SR1917FR boxes. Instead, I think either the kernel or LILO (or both) is unpredictable (= buggy) over a wide range of combinations of hardware and filesystems ( /boot ; I use reiserfs3 withOUT 'notail' option, which I may change later, but I'm fine with my boot (and root) partition in all other cases. ). read http://wiki.debian.org/InitramfsDebug and provide info based on that. I must agree that I didn't say that I had already read the page at http://wiki.debian.org/InitramfsDebug but I DID SO indeed. And parameter rootdelay=9 (i.e. an arbitrary delay of 9 seconds) did NOT HELP ; this option really is for LVM and networked filesystems. Furthermore, I can hardly provide useful info based on http://wiki.debian.org/InitramfsDebug because : either - I boot with a complete initial RAM disk image and the kernel hangs, loading no file (init, shell, ...) from within the RAM disk. or - I boot with a manually pruned initial RAM disk image and the kernel does well, though I MUST break startup process at some point (i.e. break=premount) to get a console, because my custom initRD is missing some modules (I'm working on adding just the modules I need). Thus, one cannot think it's just that the kernel might not detect the good filesystem type of the initial RAM disk image. It's clear that the problem is more complex, and I bet it is a Kernel+LILO problem (like in the mythology of the Babel Tower). I'm looking forward to hearing from you. Sincerely, Valentin QUEQUET -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426414: closed by maximilian attems [EMAIL PROTECTED] (Re: kernel: time jumps and usb resets)
From: maximilian attems [EMAIL PROTECTED] Date: Sun, 22 Jun 2008 14:05:01 +0200 Subject: Re: kernel: time jumps and usb resets To: [EMAIL PROTECTED] X-Spam-Status: No, score=-5.0 required=4.0 tests=BAYES_00,VERSION autolearn=no version=3.1.4-bugs.debian.org_2005_01_02 Version: 2.6.25-1 time subsys saw substantial effort with no hz, unlikely that this bug still persists. thus closing Linux croese 2.6.25-2-powerpc #1 Thu Jun 12 17:54:44 UTC 2008 ppc GNU/Linux 22 Jun 14:28:12 ntpdate[10125]: step time server 192.87.106.3 offset 0.004075 sec 22 Jun 14:29:13 ntpdate[10129]: step time server 192.87.106.3 offset 0.004126 sec 22 Jun 14:29:43 ntpdate[10132]: step time server 192.87.106.3 offset -30.970661 sec 22 Jun 14:30:21 ntpdate[10136]: step time server 192.87.106.3 offset -121.627927 sec 22 Jun 14:31:02 ntpdate[10154]: step time server 192.87.106.3 offset -131.852532 sec 22 Jun 14:32:03 ntpdate[10159]: step time server 192.87.106.3 offset 0.003970 sec 22 Jun 14:33:04 ntpdate[10166]: step time server 192.87.106.3 offset 0.004255 sec 22 Jun 14:33:58 ntpdate[10170]: step time server 192.87.106.3 offset -6.787904 sec 22 Jun 14:34:08 ntpdate[10189]: step time server 192.87.106.3 offset -151.243010 sec 22 Jun 14:35:09 ntpdate[10195]: step time server 192.87.106.3 offset 0.004647 sec however unlikely, it still here... do you think you can examine it if I make you an account here? Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418750: linux-image-2.6.20-1-powerpc: kernel fails to boot on mac mini G4
Package: linux-image-2.6.20-1-powerpc sorry for late reply, is that still reproducible with uptodate linux images from testing / unstable? thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 426414 in 2.6.25-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.29 found 426414 2.6.25-1 Bug#426414: kernel: time jumps and usb resets Bug marked as found in version 2.6.25-1. 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: reopening 426414
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.29 reopen 426414 Bug#426414: kernel: time jumps and usb resets 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. 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#426414: closed by maximilian attems [EMAIL PROTECTED] (Re: kernel: time jumps and usb resets)
On Sun, Jun 22, 2008 at 02:38:37PM +0200, Mario Frasca wrote: however unlikely, it still here... reopened of course and marked as found in 2.6.25-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426414: closed by maximilian attems [EMAIL PROTECTED] (Re: kernel: time jumps and usb resets)
On Sun, Jun 22, 2008 at 02:38:37PM +0200, Mario Frasca wrote: Linux croese 2.6.25-2-powerpc #1 Thu Jun 12 17:54:44 UTC 2008 ppc GNU/Linux 22 Jun 14:28:12 ntpdate[10125]: step time server 192.87.106.3 offset 0.004075 sec 22 Jun 14:29:13 ntpdate[10129]: step time server 192.87.106.3 offset 0.004126 sec 22 Jun 14:29:43 ntpdate[10132]: step time server 192.87.106.3 offset -30.970661 sec 22 Jun 14:30:21 ntpdate[10136]: step time server 192.87.106.3 offset -121.627927 sec 22 Jun 14:31:02 ntpdate[10154]: step time server 192.87.106.3 offset -131.852532 sec 22 Jun 14:32:03 ntpdate[10159]: step time server 192.87.106.3 offset 0.003970 sec 22 Jun 14:33:04 ntpdate[10166]: step time server 192.87.106.3 offset 0.004255 sec 22 Jun 14:33:58 ntpdate[10170]: step time server 192.87.106.3 offset -6.787904 sec 22 Jun 14:34:08 ntpdate[10189]: step time server 192.87.106.3 offset -151.243010 sec 22 Jun 14:35:09 ntpdate[10195]: step time server 192.87.106.3 offset 0.004647 sec however unlikely, it still here... thanks for quick feedback, please report upstream in bugzilla.kernel.org and let us know the bug number. you might want to checkout before 2.6.26-rcX trunk snapshots see http://wiki.debian.org/DebianKernel thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486394: closed by Daniel Baumann [EMAIL PROTECTED] (Bug#486394: fixed in linux-modules-extra-2.6 2.6.25-3)
Hello, Debian Bug Tracking System, le Sun 22 Jun 2008 00:05:30 +, a écrit : #486394: linux-modules-extra-2.6: Please add speakup modules It has been closed by Daniel Baumann [EMAIL PROTECTED]. Cool, thanks! It looks like it doesn't compile yet at least on arm* and sparc. We'll try to fix that upstream. In the meanwhile we can disable it on those archs, as the attached patch does. Samuel Index: speakup/defines === --- speakup/defines (révision 11683) +++ speakup/defines (copie de travail) @@ -1,4 +1,5 @@ [base] +arches: alpha amd64 hppa i386 ia64 m68k mips mipsel powerpc s390 desc: screen review module longdesc: Speakup allows you to interact with applications and Linux with audible
Bug#414932: linux-image-2.6.18-4-ixp4xx: xfs partition from x86 system can not be used on arm
* Eric Sandeen [EMAIL PROTECTED] [2008-06-21 10:50]: Do you know what the status is of your XFS patch to make it work on ARM (old ABI)? It was just recently added to the xfs cvs tree. Message to the list was TAKE 982930 - fix dir2 shortform structures on ARM old ABI Excellent news, thanks! -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#299567: closed by Martin Michlmayr [EMAIL PROTECTED] (Kernel from Debian 3.1 no longer supported)
Processing commands for [EMAIL PROTECTED]: reopen 299567 Bug#299567: kernel-image-2.6.8-2-686-smp: x86 has no uncompressed vmlinux (for oprofile) 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Warning: Unknown package 'kernel-image-2.6.8-3-686-smp' Bug reopened, originator not changed. reassign 299567 linux-2.6 Bug#299567: kernel-image-2.6.8-2-686-smp: x86 has no uncompressed vmlinux (for oprofile) Warning: Unknown package 'kernel-image-2.6.8-3-686-smp' Bug reassigned from package `kernel-image-2.6.8-3-686-smp' to `linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299567: closed by Martin Michlmayr [EMAIL PROTECTED] (Kernel from Debian 3.1 no longer supported)
At least 2.6.22 and 2.6.24 have this bug. I suppose the best way to handle this would be to have a 'linux-image-*-dbg' package, like libc6-dbg, which would include a vmlinux file for use with oprofile. If the vmlinux could be built with debugging symbols and still match the 'production' vmlinuz image that would be even better. Version: 2.6.8-99+rm You reported a bug against the Linux kernel (version 2.6.8) that was shipped with Debian 3.1 (sarge). Since Debian 3.1 is no longer supported and the kernel has changed so much that it would be very difficult to verify every outstanding bug from 2.6.8, I'm hereby closing your bug report. If you still see this issue with the kernel from the upcoming release of Debian (lenny, version 5.0), then please me know and I'll be happy to reopen this bug report. - There appears to be no package that provides uncompressed vmlinux files for use with oprofile. Other architectures (ppc) provide kernel packages with vmlinux files that get wrappered or booted directly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487421: Early boot-time kernel panic with linux-image-2.6.25-2-amd64 (2.6.25-5).
... and finally I'm hearing from myself ! Hello, Maks and others. Because of some experiments with kernel 2.6.24-1 (always functional) I got a rough idea of the modules I would really have to put in the initrd (with respect to my hardware BIOS) for kernel 2.6.25-2 (ver 2.6.25-5) which I was not able to boot my system with. (c.f. my previous post.) Hoollaoup*! I'm writing this e-mail under my now-functional kernel 2.6.25-2 (ver 2.6.25-5) -running system. * I don't know the english world - if it exist - to convey such an intense joy ;-) Now, though, I very much fear this kernel (2.6.25-2 ver 2.6.25-5) be broken and would endanger my - not so valuable - data (filesystems). I say that because having read the following thread: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485464 One can read that Arno Griffioen reported such corruptions with kernel in linux-image-2.6.25-2-amd64 (which version?). Then you, Maks, answered him to try out latest 2.6.26-rc5 (there is some 2.6.26-rc6~... snapshot now). You now see why I fear what I fear. So, I decide to always run 2.6.25-2 (ver 2.6.25-5) ; that will serve as a testcase (though not exhaustive wrt hardware usage patterns). If you can't hear from me in the following 1-2 year(s) that would mean that kernel 2.6.25-2 (ver 2.6.25-5) crunched my whole system, all my partitions ( Including M$ Windaube eXPrès ;-) ). Said that, I still find the imputability of guilt, in the Linux_Kernel/LILO/Initial_RAM_Disk case, be a moot point. To your opinion, who's guilty ? I don't necessarily want to make the case against Linux_Kernel overflated ;-) I'm looking forward to hearing from you. Sincerely, Valentin QUEQUET -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Alpha Linux kernel fails with inconsistent kallsyms data
Hi folks
The build of the Alpha Linux kernel currently fails[1] with inconsistent
kallsyms data. As I never saw that before, I thought about hardware
problems. But in fact it is a bug in the Linux kernel.
The end of the rodata section is marked with the __end_rodata symbol.
This symbol have different aligning constraints than the inittext parts
and therefor the start marked _sinittext. Because of that the
__end_rodata symbol shifts between _sinittext and == _sinittext. The
later variant is seen as a code symbol and recorded in the kallsyms
data.
On fix would be to move the exception table a little bit and get some
space between that two areas.
Bastian
[1]:
http://buildd.debian.org/fetch.cgi?pkg=linux-2.6arch=alphaver=2.6.25-5stamp=1213919009file=logas=raw
--
The face of war has never changed. Surely it is more logical to heal
than to kill.
-- Surak of Vulcan, The Savage Curtain, stardate 5906.5
diff --git a/arch/alpha/kernel/vmlinux.lds.S b/arch/alpha/kernel/vmlinux.lds.S
index f13249b..ef37fc1 100644
--- a/arch/alpha/kernel/vmlinux.lds.S
+++ b/arch/alpha/kernel/vmlinux.lds.S
@@ -25,6 +25,13 @@ SECTIONS
} :kernel
_etext = .; /* End of text section */
+ NOTES :kernel :note
+ .dummy : {
+ *(.dummy)
+ } :kernel
+
+ RODATA
+
/* Exception table */
. = ALIGN(16);
__ex_table : {
@@ -33,13 +40,6 @@ SECTIONS
__stop___ex_table = .;
}
- NOTES :kernel :note
- .dummy : {
- *(.dummy)
- } :kernel
-
- RODATA
-
/* Will be freed after init */
. = ALIGN(PAGE_SIZE);
/* Init code and data */
signature.asc
Description: Digital signature
Processed: retitle 483431 to please include drivers for OLPC MMC controller
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 retitle 483431 please include drivers for OLPC MMC controller Bug#483431: please include drivers for mtd and mmc devices Changed Bug title to `please include drivers for OLPC MMC controller' from `please include drivers for mtd and mmc devices'. 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#487586: linux-image-2.6.25-2-686: Realtek / r8169 drivers do not properly detect link status or work at 1000BaseT (gigabit)
Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: normal There is a widely-reported problem with the r8169 driver in certain configurations. Auto-link detection does not work, and while the device comes up it can't connect and the physical link light on the device turns off during the bootup process (maybe when the r8169 module is loaded). I have two boxes: using the same Debian distribution on both, and the same exact card (i.e., the same actual card, not the same type of card), it works fine in one but not in the other. Most of the solutions that have been discussed involve powering off the box to reset wake-on-LAN functionality. That doesn't work for me. The only solution I have found is to override link negotiation with ethtool -s eth1 autoneg off. This at least makes the card usable, but I can't use 1000BaseT/gigabit ethernet. If I try to force it with ethtool -s eth1 speed 1000, the link goes back down and is unusable no matter what else I do. I've tried all the suggestions listed here: http://ubuntuforums.org/showthread.php?t=538448 None of them work for me. I didn't see another placeholder for this bug in BTS, so I filed this. Presumably this is something upstream ultimately needs to solve. -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Thu Jun 12 16:26:30 UTC 2008 ** Command line: root=/dev/hda1 ro ** Not tainted ** Kernel log: [30621.905433] r8169: eth1: link down [30621.906002] ADDRCONF(NETDEV_UP): eth1: link is not ready ** Loaded modules: Module Size Used by snd_mixer_oss 14880 0 usblp 13664 0 nfs 225128 0 nfsd 199568 17 lockd 59752 3 nfs,nfsd nfs_acl 3520 2 nfs,nfsd auth_rpcgss39168 1 nfsd sunrpc171872 14 nfs,nfsd,lockd,nfs_acl,auth_rpcgss exportfs4768 1 nfsd ppdev 8676 0 lp 11012 0 ipt_MASQUERADE 3776 1 iptable_nat 6728 1 nf_nat 18136 2 ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 16616 68 iptable_nat,nf_nat xt_state2496 65 nf_conntrack 59892 5 ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_LOG 5700 7 xt_limit2628 9 xt_tcpudp 3104 110 iptable_filter 3424 1 ip_tables 13168 2 iptable_nat,iptable_filter x_tables 15716 7 ipt_MASQUERADE,iptable_nat,xt_state,ipt_LOG,xt_limit,xt_tcpudp,ip_tables ipv6 241956 24 dm_snapshot17444 0 dm_mirror 25316 0 dm_mod 55656 2 dm_snapshot,dm_mirror snd_intel8x0 31740 2 snd_ac97_codec 91300 1 snd_intel8x0 i2c_i8019520 0 psmouse35920 0 ac97_bus1952 1 snd_ac97_codec snd_pcm68228 3 snd_intel8x0,snd_ac97_codec snd_timer 21320 2 snd_pcm snd48772 7 snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 7488 1 snd i2c_core 22548 1 i2c_i801 button 8240 0 rng_core4900 0 serio_raw 6532 0 iTCO_wdt 11204 0 intel_agp 25084 1 agpgart31720 1 intel_agp evdev 11328 0 shpchp 29716 0 pci_hotplug26980 1 shpchp snd_page_alloc 9992 2 snd_intel8x0,snd_pcm pcspkr 3136 0 rtc14272 0 parport_pc 25860 1 parport33868 3 ppdev,lp,parport_pc ext3 120360 2 jbd43444 1 ext3 mbcache 8260 1 ext3 raid1 22176 1 md_mod 74556 2 raid1 ide_cd_mod 32864 0 cdrom 31872 1 ide_cd_mod ide_disk 13952 3 sd_mod 26072 2 piix7176 0 [permanent] ata_piix 20196 1 ata_generic 8004 0 libata142288 2 ata_piix,ata_generic scsi_mod 138508 2 sd_mod,libata dock 10448 1 libata r8169 28740 0 tg389316 0 ehci_hcd 32620 0 uhci_hcd 22352 0 usbcore 130032 4 usblp,ehci_hcd,uhci_hcd thermal19100 0 processor 39660 1 thermal fan 5636 0 pdc202xx_new5856 0 [permanent] ide_core 100312 4 ide_cd_mod,ide_disk,piix,pdc202xx_new ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02) Subsystem: Hewlett-Packard Company Unknown device
Bug#483431: ping
Hi, Any comments on this one? -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What good is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#385553: linux-modules-extra-2.6: ndiswrapper requires rules target override
On Fri, Jun 20, 2008 at 08:03:16PM +0200, Bastian Blank wrote: Several people, including Linux upstream, declares ndiswrapper as non-free. Please move it to the appropriate section. No they don't. There are even completely GPL drivers that are possible to run under ndiswrapper. The upstream kernel accidentally tainted ndiswrapper for a version or two, but it wasn't done entirely on purpose, more do to lack of understanding by the person doing it. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#385553: linux-modules-extra-2.6: ndiswrapper requires rules target override
On Sun, Jun 22, 2008 at 05:54:57PM -0400, Lennart Sorensen wrote: On Fri, Jun 20, 2008 at 08:03:16PM +0200, Bastian Blank wrote: Several people, including Linux upstream, declares ndiswrapper as non-free. Please move it to the appropriate section. No they don't. There are even completely GPL drivers that are possible to run under ndiswrapper. ndiswrapper is a module loader. But it does not take the appropriate actions while handling non-free modules. The upstream kernel accidentally tainted ndiswrapper for a version or two, but it wasn't done entirely on purpose, more do to lack of understanding by the person doing it. | /* | * ndiswrapper is under GPL by itself, but loads proprietary modules. | * Don't use add_taint_module(), as it would prevent ndiswrapper from | * using GPL-only symbols it needs. | */ | if (strcmp(mod-name, ndiswrapper) == 0) | add_taint(TAINT_PROPRIETARY_MODULE); There is nothing accidentally. Bastian -- Humans do claim a great deal for that particular emotion (love). -- Spock, The Lights of Zetar, stardate 5725.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487594: bttv: deadlock when using v4l interface
Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: normal Hi, when using v4l application hang in D state with the current debian version. A patch exist [1], and it is in a stable release [2]. Please update the package to the last stable release. [1] http://lkml.org/lkml/2008/6/13/293 [2] http://lkml.org/lkml/2008/6/16/349 -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Thu Jun 12 16:26:30 UTC 2008 ** Command line: root=/dev/hdf3 ro vga=791 ** Not tainted ** Kernel log: [23670.400267] Wpa Removing key 0 [23670.758067] status : 600 [23684.463386] WPA enable [23684.801258] status : 400 [23684.916344] set wpa : 2 32 0 a [23684.916344] Setting default tx key to 0 [23684.953409] set wpa : 2 32 1 6 [23686.012910] set wpa : 2 32 1 6 [23938.625129] set wpa : 2 32 2 6 [24193.552751] INFO: task mplayer:16181 blocked for more than 120 seconds. [24193.552763] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [24193.552767] mplayer D 0 16181 16110 [24193.552772]e76a5910 00200082 e76a5b60 e76a5a90 c180b920 001368be [24193.552781]00318ee4 f77179a4 00ff e776b810 e776b818 [24193.552788]e776b814 e76a5910 c02b47e9 e776b818 e776b818 e76a5910 e776b810 00208000 [24193.552795] Call Trace: [24193.552886] [c02b47e9] __mutex_lock_slowpath+0x50/0x7b [24193.552915] [c02b467f] mutex_lock+0xa/0xb [24193.552921] [f8d26e8d] videobuf_mmap_setup+0xe/0x2d [videobuf_core] [24193.552945] [f8de3d6b] vidiocgmbuf+0x24/0x83 [bttv] [24193.552977] [f8de3d47] vidiocgmbuf+0x0/0x83 [bttv] [24193.552998] [f8d797fd] __video_do_ioctl+0x93/0x2cca [videodev] [24193.553014] [c0158558] __lock_page+0x4e/0x54 [24193.553036] [c0133a21] wake_bit_function+0x0/0x3c [24193.553056] [c01586a1] find_lock_page+0x19/0x7f [24193.553068] [c015a57f] filemap_fault+0x1ff/0x36d [24193.553104] [c01635f0] __do_fault+0x34d/0x38e [24193.553115] [f8de217b] set_tvnorm+0x205/0x20f [bttv] [24193.553148] [f8d7c69d] video_ioctl2+0x16d/0x233 [videodev] [24193.553205] [c0137c03] getnstimeofday+0x30/0xb6 [24193.553226] [c013659d] ktime_get_ts+0x16/0x44 [24193.553236] [c01365d8] ktime_get+0xd/0x21 [24193.553248] [c011b720] hrtick_start_fair+0xeb/0x12c [24193.553262] [c0106970] __switch_to+0xa3/0x12f [24193.553283] [c017f70b] vfs_ioctl+0x47/0x5d [24193.553302] [c017f966] do_vfs_ioctl+0x245/0x258 [24193.553324] [c017f9ba] sys_ioctl+0x41/0x5b [24193.553341] [c01077e8] sysenter_past_esp+0x6d/0xa5 [24193.553390] === [24457.693416] INFO: task mplayer:16181 blocked for more than 120 seconds. [24457.693425] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [24457.693428] mplayer D 0 16181 16110 [24457.693434]e76a5910 00200082 e76a5b60 e76a5a90 c180b920 001368be [24457.693442]00318ee4 f77179a4 00ff e776b810 e776b818 [24457.693449]e776b814 e76a5910 c02b47e9 e776b818 e776b818 e76a5910 e776b810 00208000 [24457.693456] Call Trace: [24457.693546] [c02b47e9] __mutex_lock_slowpath+0x50/0x7b [24457.693573] [c02b467f] mutex_lock+0xa/0xb [24457.693580] [f8d26e8d] videobuf_mmap_setup+0xe/0x2d [videobuf_core] [24457.693604] [f8de3d6b] vidiocgmbuf+0x24/0x83 [bttv] [24457.693635] [f8de3d47] vidiocgmbuf+0x0/0x83 [bttv] [24457.693656] [f8d797fd] __video_do_ioctl+0x93/0x2cca [videodev] [24457.693672] [c0158558] __lock_page+0x4e/0x54 [24457.693693] [c0133a21] wake_bit_function+0x0/0x3c [24457.693712] [c01586a1] find_lock_page+0x19/0x7f [24457.693725] [c015a57f] filemap_fault+0x1ff/0x36d [24457.693761] [c01635f0] __do_fault+0x34d/0x38e [24457.693771] [f8de217b] set_tvnorm+0x205/0x20f [bttv] [24457.693804] [f8d7c69d] video_ioctl2+0x16d/0x233 [videodev] [24457.693861] [c0137c03] getnstimeofday+0x30/0xb6 [24457.693882] [c013659d] ktime_get_ts+0x16/0x44 [24457.693892] [c01365d8] ktime_get+0xd/0x21 [24457.693904] [c011b720] hrtick_start_fair+0xeb/0x12c [24457.693918] [c0106970] __switch_to+0xa3/0x12f [24457.693939] [c017f70b] vfs_ioctl+0x47/0x5d [24457.693958] [c017f966] do_vfs_ioctl+0x245/0x258 [24457.693980] [c017f9ba] sys_ioctl+0x41/0x5b [24457.693997] [c01077e8] sysenter_past_esp+0x6d/0xa5 [24457.694046] === [24565.976950] set wpa : 2 32 1 6 [24895.779278] INFO: task mplayer:16181 blocked for more than 120 seconds. [24895.779289] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [24895.779293] mplayer D 0 16181 16110 [24895.779298]e76a5910 00200082 e76a5b60 e76a5a90 c180b920 001368be [24895.779306]00318ee4 f77179a4 00ff e776b810 e776b818 [24895.779313]e776b814 e76a5910 c02b47e9 e776b818 e776b818 e76a5910 e776b810 00208000 [24895.779320]
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
On Sun, Jun 22, 2008 at 01:18:50PM +0200, maximilian attems wrote: On Sun, Jun 22, 2008 at 10:28:55AM +0200, Astrid S. de Wijn wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-5 Severity: normal In 2.6.25 debian kernels, USB_PERSIST has been enabled, to make it possible to suspend with mounted usb storage filesystems which lose power during suspend. Even though the interface in /sys exists, and I write 1 to every device's persist file, I still lose the usb storage devices after resume as if I had suspended without USB_PERSIST. The result is journal commit I/O errors and risk of filesystem corruption. The storage devices in question are a usb SD card reader and a usb stick attached to a usb hub, which contains my / filesystem. I've done a little bit of digging and found someone who reported a suspiciously similar problem. In the thread a patch is mentioned: http://article.gmane.org/gmane.linux.usb.general/2031/match=usb+persist+issue The patch was supposed to be submitted for 2.6.25, but the 2.6.25 debian-patched kernel sources don't seem to have it. I have not been able to test yet wether this patch fixes my problem. Kind regards, Astrid please checkout 2.6.26-rcX kernels. they have got patches for it see apt trunk lines http://wiki.debian.org/DebianKernel (beware to blacklist snd-pcsp ) -- maks I've tried it with 2.6.26-rc6. USB_PERSIST works for the card reader, but unfortunately not for the usb stick. Aparently there is another problem. :( Astrid - [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] - Dr. Astrid S. de Wijn Theory of Condensed Matter (TCM) Institute for Molecules and Materials (IMM) Faculty of Science Radboud University Nijmegen P.O. Box 9010 6500 GL Nijmegen The Netherlands Tel: +31(0)243652849 - signature.asc Description: Digital signature
Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work
On Mon, Jun 23, 2008 at 01:02:44AM +0200, Astrid S. de Wijn wrote: I've tried it with 2.6.26-rc6. USB_PERSIST works for the card reader, but unfortunately not for the usb stick. Aparently there is another problem. :( Astrid thanks for quick response. please report upstream in bugzilla.kernel.org and let us know the bug number. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Processed: Re: Bug#414932: linux-image-2.6.18-4-ixp4xx: xfs partition from x86 system can not be used on arm
Processing commands for [EMAIL PROTECTED]: tag 414932 +patch Bug#414932: linux-image-2.6.18-4-ixp4xx: xfs partition from x86 system can not be used on arm There were no tags set. Tags added: patch -- 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#414932: Processed: Re: Bug#414932: linux-image-2.6.18-4-ixp4xx: xfs partition from x86 system can not be used on arm
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commit;h=7a9ba9bb899933293604a2b3c5ca4f40ad5a92a8 This fixes the issue, and should be pushed in the next kernel.org xfs. Cheers, -- Niv Sardi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-modules-extra-2.6_2.6.25-4_i386.changes
linux-modules-extra-2.6_2.6.25-4_i386.changes uploaded successfully to localhost along with the files: linux-modules-extra-2.6_2.6.25-4.dsc linux-modules-extra-2.6_2.6.25-4.tar.gz atl2-modules-2.6.25-2-486_2.6.25+2.0.3-4_i386.deb atl2-modules-2.6-486_2.6.25-4_i386.deb aufs-modules-2.6.25-2-486_2.6.25+0+20080609-4_i386.deb aufs-modules-2.6-486_2.6.25-4_i386.deb btrfs-modules-2.6.25-2-486_2.6.25+0.15-4_i386.deb btrfs-modules-2.6-486_2.6.25-4_i386.deb drbd8-modules-2.6.25-2-486_2.6.25+8.0.12-4_i386.deb drbd8-modules-2.6-486_2.6.25-4_i386.deb eeepc-acpi-modules-2.6.25-2-486_2.6.25+1.0-4_i386.deb eeepc-acpi-modules-2.6-486_2.6.25-4_i386.deb et131x-modules-2.6.25-2-486_2.6.25+1.2.3-2-4_i386.deb et131x-modules-2.6-486_2.6.25-4_i386.deb gspca-modules-2.6.25-2-486_2.6.25+01.00.20-4_i386.deb gspca-modules-2.6-486_2.6.25-4_i386.deb iscsitarget-modules-2.6.25-2-486_2.6.25+0.4.15+svn148-4_i386.deb iscsitarget-modules-2.6-486_2.6.25-4_i386.deb kqemu-modules-2.6.25-2-486_2.6.25+1.3.0~pre11-4_i386.deb kqemu-modules-2.6-486_2.6.25-4_i386.deb loop-aes-modules-2.6.25-2-486_2.6.25+3.2c-4_i386.deb loop-aes-modules-2.6-486_2.6.25-4_i386.deb lzma-modules-2.6.25-2-486_2.6.25+4.43-4_i386.deb lzma-modules-2.6-486_2.6.25-4_i386.deb nilfs2-modules-2.6.25-2-486_2.6.25+2.0.2-4_i386.deb nilfs2-modules-2.6-486_2.6.25-4_i386.deb r6040-modules-2.6.25-2-486_2.6.25+0.17-4_i386.deb r6040-modules-2.6-486_2.6.25-4_i386.deb redhat-cluster-modules-2.6.25-2-486_2.6.25+2.20080603-4_i386.deb redhat-cluster-modules-2.6-486_2.6.25-4_i386.deb sfc-modules-2.6.25-2-486_2.6.25+2.2.0136-4_i386.deb sfc-modules-2.6-486_2.6.25-4_i386.deb speakup-modules-2.6.25-2-486_2.6.25+3.0.2+git20080517.dfsg.1-4_i386.deb speakup-modules-2.6-486_2.6.25-4_i386.deb squashfs-modules-2.6.25-2-486_2.6.25+3.3-4_i386.deb squashfs-modules-2.6-486_2.6.25-4_i386.deb tp-smapi-modules-2.6.25-2-486_2.6.25+0.37-4_i386.deb tp-smapi-modules-2.6-486_2.6.25-4_i386.deb virtualbox-ose-modules-2.6.25-2-486_2.6.25+1.6.2-dfsg-4_i386.deb virtualbox-ose-modules-2.6-486_2.6.25-4_i386.deb virtualbox-ose-guest-modules-2.6.25-2-486_2.6.25+1.6.2-dfsg-4_i386.deb virtualbox-ose-guest-modules-2.6-486_2.6.25-4_i386.deb atl2-modules-2.6.25-2-686_2.6.25+2.0.3-4_i386.deb atl2-modules-2.6-686_2.6.25-4_i386.deb aufs-modules-2.6.25-2-686_2.6.25+0+20080609-4_i386.deb aufs-modules-2.6-686_2.6.25-4_i386.deb btrfs-modules-2.6.25-2-686_2.6.25+0.15-4_i386.deb btrfs-modules-2.6-686_2.6.25-4_i386.deb drbd8-modules-2.6.25-2-686_2.6.25+8.0.12-4_i386.deb drbd8-modules-2.6-686_2.6.25-4_i386.deb eeepc-acpi-modules-2.6.25-2-686_2.6.25+1.0-4_i386.deb eeepc-acpi-modules-2.6-686_2.6.25-4_i386.deb et131x-modules-2.6.25-2-686_2.6.25+1.2.3-2-4_i386.deb et131x-modules-2.6-686_2.6.25-4_i386.deb gspca-modules-2.6.25-2-686_2.6.25+01.00.20-4_i386.deb gspca-modules-2.6-686_2.6.25-4_i386.deb iscsitarget-modules-2.6.25-2-686_2.6.25+0.4.15+svn148-4_i386.deb iscsitarget-modules-2.6-686_2.6.25-4_i386.deb kqemu-modules-2.6.25-2-686_2.6.25+1.3.0~pre11-4_i386.deb kqemu-modules-2.6-686_2.6.25-4_i386.deb loop-aes-modules-2.6.25-2-686_2.6.25+3.2c-4_i386.deb loop-aes-modules-2.6-686_2.6.25-4_i386.deb lzma-modules-2.6.25-2-686_2.6.25+4.43-4_i386.deb lzma-modules-2.6-686_2.6.25-4_i386.deb nilfs2-modules-2.6.25-2-686_2.6.25+2.0.2-4_i386.deb nilfs2-modules-2.6-686_2.6.25-4_i386.deb r6040-modules-2.6.25-2-686_2.6.25+0.17-4_i386.deb r6040-modules-2.6-686_2.6.25-4_i386.deb redhat-cluster-modules-2.6.25-2-686_2.6.25+2.20080603-4_i386.deb redhat-cluster-modules-2.6-686_2.6.25-4_i386.deb sfc-modules-2.6.25-2-686_2.6.25+2.2.0136-4_i386.deb sfc-modules-2.6-686_2.6.25-4_i386.deb speakup-modules-2.6.25-2-686_2.6.25+3.0.2+git20080517.dfsg.1-4_i386.deb speakup-modules-2.6-686_2.6.25-4_i386.deb squashfs-modules-2.6.25-2-686_2.6.25+3.3-4_i386.deb squashfs-modules-2.6-686_2.6.25-4_i386.deb tp-smapi-modules-2.6.25-2-686_2.6.25+0.37-4_i386.deb tp-smapi-modules-2.6-686_2.6.25-4_i386.deb virtualbox-ose-modules-2.6.25-2-686_2.6.25+1.6.2-dfsg-4_i386.deb virtualbox-ose-modules-2.6-686_2.6.25-4_i386.deb virtualbox-ose-guest-modules-2.6.25-2-686_2.6.25+1.6.2-dfsg-4_i386.deb virtualbox-ose-guest-modules-2.6-686_2.6.25-4_i386.deb atl2-modules-2.6.25-2-686-bigmem_2.6.25+2.0.3-4_i386.deb atl2-modules-2.6-686-bigmem_2.6.25-4_i386.deb aufs-modules-2.6.25-2-686-bigmem_2.6.25+0+20080609-4_i386.deb aufs-modules-2.6-686-bigmem_2.6.25-4_i386.deb btrfs-modules-2.6.25-2-686-bigmem_2.6.25+0.15-4_i386.deb btrfs-modules-2.6-686-bigmem_2.6.25-4_i386.deb drbd8-modules-2.6.25-2-686-bigmem_2.6.25+8.0.12-4_i386.deb drbd8-modules-2.6-686-bigmem_2.6.25-4_i386.deb et131x-modules-2.6.25-2-686-bigmem_2.6.25+1.2.3-2-4_i386.deb et131x-modules-2.6-686-bigmem_2.6.25-4_i386.deb gspca-modules-2.6.25-2-686-bigmem_2.6.25+01.00.20-4_i386.deb gspca-modules-2.6-686-bigmem_2.6.25-4_i386.deb
