Bug#495529: linux-source: SMP process scheduler leaves CPUs idle
On Mon, Aug 18, 2008 at 08:43:30PM +1000, Paul Szabo wrote: > Package: linux-source > Version: 2.6.18.dfsg.1-18etch6 > Severity: normal > > > I have some machines with 8 CPUs (dual Intel Xeon quad-core CPU chips), > used for long-running calculations; normally there are no short-lived > processes. If all processes are "niced" to the same or nearby level, > then things behave as expected. But if there is a large difference in > the "nice" level (e.g. one job at level 15 and 8 jobs at level 18), then > one CPU is left idle: total CPU percentages adding to 700% and "top" > shows idleness at 12.5%. (Under some similar conditions I have also > observed 2 idle CPUs.) > > Please let me know if you need further details. Did you upgrade to Lenny in the mean time? If so, does the behaviour persist? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523964: linux-image-2.6.28-1-486: memory corruption on resuming from STR/ACPI State 3
On Mon, Apr 13, 2009 at 03:30:53PM -0700, Kushal Koolwal wrote: > Package: linux-image-2.6.28-1-486 > Version: 2.6.28-1 > Severity: normal > > I get the following memory corruption error message after my system wakes up > from Suspend-to-ram. This happens from console and from X too. > I have tried to use the following methods to suspend by computer and I get > the error messages with all of them: > echo mem > /sys/power/state > s2ram -f > pm-hibernate > > [ 239.816522] [ cut here ] > [ 239.816538] WARNING: at arch/x86/kernel/setup.c:718 > check_for_bios_corruption+0xa0/0xaa() > [ 239.816554] Memory corruption detected in low memory > [ 239.816566] Modules linked in: pcspkr snd_cs5535audio snd_ac97_codec > ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc evdev > [ 239.816617] Pid: 4351, comm: grep Not tainted 2.6.28-1-acpi #1 > [ 239.816630] Call Trace: > [ 239.816654] [] warn_slowpath+0x5a/0x78 > [ 239.816678] [] vt_console_print+0x0/0x27f > [ 239.816700] [] __call_console_drivers+0x34/0x40 > [ 239.816724] [] read_tsc+0x6/0x22 > [ 239.816747] [] getnstimeofday+0x4a/0xc5 > [ 239.816769] [] printk+0xe/0x11 > [ 239.816789] [] check_for_bios_corruption+0xa0/0xaa > [ 239.816812] [] periodic_check_for_corruption+0x0/0x28 > [ 239.816834] [] periodic_check_for_corruption+0x5/0x28 > [ 239.816858] [] run_timer_softirq+0x12a/0x18e > [ 239.816878] [] __do_softirq+0x4a/0xbc > [ 239.816896] [] do_softirq+0x22/0x26 > [ 239.816913] [] irq_exit+0x25/0x5f > [ 239.816931] [] do_IRQ+0x5a/0x6c > [ 239.816949] [] common_interrupt+0x23/0x28 > [ 239.816972] [] sta_apply_parameters+0x12e/0x14e > [ 239.816987] ---[ end trace 1c9338d4c6e94f6c ]--- > [ 362.200042] Hangcheck: hangcheck value past margin! > > I am using software suspend method in kernel (CONFIG_SUSPEND=y). Please let > me know if you need more information on this. Does this error still occur with the 2.6.30 kernel from unstable? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523503: Unbalanced enable for IRQ 16 seems to be solved by using kernel 2.6.29
On Mon, Apr 13, 2009 at 02:55:35PM +0200, axel.ludszuw...@t-online.de wrote: > I have > installed kernel 2.6.29 after some difficults to compil Nvidias binary > driver . The "Unbalanced IRQ16" error does not appear > until yet. > Ihave booted apporximately 10 to 15 times. > I will let you know, if the kernel oops will be happen in the future. > Did this error even happen again with the 2.6.29 kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#494875: marked as done (linux-image-2.6.25-2-686-bigmem: hangs after a while)
Your message dated Mon, 27 Jul 2009 02:12:45 +0200 with message-id <20090727001245.ga3...@galadriel.inutil.org> and subject line Re: linux-image-2.6.25-2-686-bigmem: hangs after a while has caused the Debian Bug report #494875, regarding linux-image-2.6.25-2-686-bigmem: hangs after a while 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 ow...@bugs.debian.org immediately.) -- 494875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.25-2-686-bigmem Version: 2.6.25-7 Severity: critical Justification: breaks the whole system I've upgraded recently to kernel 2.6.25, used it for a while (couple of hourse, it's not on my primary machine). Today I noticed that it produces random hangs. First it crashed while doing a partimage from sda to sda. After that (and after doing an upgrade to 2.6.25-7 - it was 6 before, so it affects both packages) it hung while copying from sda to sdb (a USB hdd). The hang is the same in both cases: console is still active (receives keystrokes) but no command gets through. I can switch consoles, though (Alt-F1, Alt-F2) but obviously none of them work. I can press SysReq, and reboot from there. 2.6.24-7 is stable so far. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686-bigmem depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686-bigmem recommends: ii libc6-i6862.7-13 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.25-2-686-bigmem suggests: ii grub 0.97-46GRand Unified Bootloader (Legacy v pn linux-doc-2.6.25 (no description available) -- debconf information excluded --- End Message --- --- Begin Message --- On Sat, Dec 27, 2008 at 06:43:31PM +0100, Moritz Muehlenhoff wrote: > On Tue, Aug 12, 2008 at 10:24:14PM +0300, VALKAI Elod wrote: > > Package: linux-image-2.6.25-2-686-bigmem > > Version: 2.6.25-7 > > Severity: critical > > Justification: breaks the whole system > > > > > > I've upgraded recently to kernel 2.6.25, used it for a while (couple of > > hourse, > > it's not on my primary machine). > > > > Today I noticed that it produces random hangs. First it crashed while doing > > a > > partimage from sda to sda. > > > > After that (and after doing an upgrade to 2.6.25-7 - it was 6 before, so it > > affects both packages) it hung while copying from sda to sdb (a USB hdd). > > > > The hang is the same in both cases: console is still active (receives > > keystrokes) > > but no command gets through. I can switch consoles, though (Alt-F1, Alt-F2) > > but > > obviously none of them work. > > > > I can press SysReq, and reboot from there. 2.6.24-7 is stable so far. > > Does this error still occur with more recent kernel versions? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#404568: marked as done (linux-image-2.6.18-3-686: sata ii hard disk on via chipset appeards both as hdg and as sda)
Your message dated Mon, 27 Jul 2009 01:36:07 +0200 with message-id <20090726233607.ga28...@galadriel.inutil.org> and subject line Re: linux-image-2.6.18-3-686: sata ii hard disk on via chipset appeards both as hdg and as sda has caused the Debian Bug report #404568, regarding linux-image-2.6.18-3-686: sata ii hard disk on via chipset appeards both as hdg and as sda 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 ow...@bugs.debian.org immediately.) -- 404568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-3-686 Version: 2.6.18-8 Severity: normal The system has a VIA K8T890 CF chipset with two IDE, two SATA and two SATA II JMicron JMB 363 ports. The system has a DVD burner set as master on the second IDE interface, and a hard disk connected to the first SATA II port. The SATA II port can be set in the BIOS to work in either IDE or AHCI mode, but the problem appears in both cases. The problem is that the hard disk appears both as /dev/hdg (initially) and /dev/sda (when the SATA driver gets loaded), but accessing it via /dev/hdg generates lots of I/O error messages, as shown in the attached dmesg (lspci and dmesg outputs refer to the SATA II ports set to AHCI mode in the BIOS). Passing ide2=noprobe ide3=noprobe hdg=noprobe or similar options to the kernel (the system is set up with GRUB) has no effect, so it seems to be not possible to disable the (non-functional) PATA acccess to the SATA II disk. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5.2 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-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-9 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: -- lspci output: 00:00.0 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.5 PIC: VIA Technologies, Inc. VT3351 I/O APIC Interrupt Controller 00:00.7 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. [K8T890 North / VT8237 South] PCI Bridge 00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.1 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.
Bug#402710: marked as done (Loop mount of XFS on DVD-RW fails on Debian, works on SUSE)
Your message dated Mon, 27 Jul 2009 01:36:46 +0200 with message-id <20090726233646.ga30...@galadriel.inutil.org> and subject line Re: Bug#402710: Loop mount of XFS on DVD-RW fails on Debian, works on SUSE has caused the Debian Bug report #402710, regarding Loop mount of XFS on DVD-RW fails on Debian, works on SUSE 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 ow...@bugs.debian.org immediately.) -- 402710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: loop-aes-utils Version: 2.12r-14 Severity: important A mountable encrypted dvd image cannot be mounted after burned to dvd. i CREATED A DVD IMAGE dd if=/dev/zero of=/mnt/hda7/iso/xfs_dvd_f9.raw bs=1M count=4482 THEN losetup -e AES256 /dev/loop0 /mnt/hda7/iso/xfs_dvd_f9.raw CREATED A FILESYSTEM mkfs.xfs /dev/loop0 MOUNTED AND FILLED WITH DATA Debian Etch uname -a: Linux prometheus 2.6.17-2-k7 #1 SMP Wed Sep 13 17:18:46 UTC 2006 i686 GNU/Linux prometheus:/mnt/hda7/iso# mount -vv -o loop,encryption=AES256 ./xfs_dvd_f9.raw ./mounted/ mount: going to use the loop device /dev/loop/0 Password: set_loop(/dev/loop/0,./xfs_dvd_f9.raw): success mount: setup loop device successfully mount: you didn't specify a filesystem type for /dev/loop/0 I will try type xfs /mnt/hda7/iso/xfs_dvd_f9.raw on /mnt/hda7/iso/mounted type xfs (rw,loop=/dev/loop/0,encryption=AES256) prometheus:/mnt/hda7/iso# /var/log/messages: Dec 10 19:53:57 localhost kernel: Linux version 2.6.17-2-k7 (Debian 2.6.17-9) (wa...@debian.org) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Wed Sep 13 17:18:46 UTC 2006 Dec 10 20:01:01 localhost kernel: SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled Dec 10 20:01:01 localhost kernel: SGI XFS Quota Management subsystem Dec 10 20:01:01 localhost kernel: XFS mounting filesystem hda7 Dec 10 20:01:43 localhost kernel: loop: AES key scrubbing enabled Dec 10 20:01:43 localhost kernel: loop: loaded (max 8 devices) Dec 10 20:01:52 localhost kernel: Filesystem "loop0": Disabling barriers, not supported by the underlying device Dec 10 20:01:53 localhost kernel: XFS mounting filesystem loop0 BURNED TO DVD growisofs -speed=4 -Z /dev/hdc=/mnt/hda7/iso/xfs_dvd_f9.raw BUT FAILS TO MOUNT HTE BURNED DVD prometheus:/home/toni# mount -vv -o loop,encryption=AES256 /dev/hdc /media/cdrom0/ mount: going to use the loop device /dev/loop0 Password: set_loop(/dev/loop0,/dev/hdc): success mount: setup loop device successfully mount: you didn't specify a filesystem type for /dev/loop0 I will try type xfs del_loop(/dev/loop0): success mount: Function not implemented /var/log/messages: Dec 10 19:08:49 localhost kernel: Unable to identify CD-ROM format. Dec 10 19:09:32 localhost kernel: loop: AES key scrubbing enabled Dec 10 19:09:32 localhost kernel: loop: loaded (max 8 devices) Dec 10 19:09:42 localhost kernel: SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled Dec 10 19:09:42 localhost kernel: SGI XFS Quota Management subsystem IT CANNOT BE MOUNTED NEITHER WITH KERNEL 2.6.18-3-K7 -- 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-3-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages loop-aes-utils depends on: ii gnupg1.4.6-1 GNU privacy guard - a free PGP rep ii libblkid 1.39+1.40-WIP-2006.11.14+dfsg-1 block device id library ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-1 universally unique id library ii mount2.12r-15Tools for mounting and manipulatin Versions of packages loop-aes-utils recommends: ii sharutils 1:4.2.1-15 shar, unshar, uuencode, uudecode -- no debconf information --- End Message --- --- Begin Message --- On Wed, Dec 17, 2008 at 08:50:10PM +0100, Moritz Muehlenhoff wrote: > On Sun, Mar 18, 2007 at 12:03:45PM +0100, Max Vozeler wrote: > > reassign 402710 linux-2.6 > > retitle 402710 Loop mount of XFS on DVD-RW fails on Debian, works on SUSE > > thanks > > > > Hi kernel team, hi Kosza, > > > > This bug is about a problem Kosza experienced when trying to loop > > mount an XFS filesystem stored on DVD-RW. This works correctly on > > SUSE 10.0 but fails on Debian 2.6.17-2. Summarizing what I think > > we have found out so far: > > > > - DVD has a fixed block size of 2048 by
Bug#398964: marked as done (linux-image-2.6.17-2-686: i810 fb module conflicts with X)
Your message dated Mon, 27 Jul 2009 01:32:33 +0200 with message-id <20090726233233.ga12...@galadriel.inutil.org> and subject line Re: linux-image-2.6.17-2-686: i810 fb module conflicts with X has caused the Debian Bug report #398964, regarding linux-image-2.6.17-2-686: i810 fb module conflicts with X 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 ow...@bugs.debian.org immediately.) -- 398964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Severity: important When I load i810 fb module (which by itself works fine with my adapter), X (also a i810 server) won't load and I get a message about X being unable to access the hardware. However, when I load vesafb (which I don't want to), both work fine. X also works fine when no fb. I'm not quitw sure if it's a kernel or X bug, but I report it as a kernel bug based on the fact that X works fine, except when i810fb module loaded. Arny -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-686 Locale: LANG=hr_HR, LC_CTYPE=hr_HR (charmap=ISO-8859-2) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.85a tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-686 recommends: pn libc6-i686 (no description available) -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: --- End Message --- --- Begin Message --- On Thu, Dec 04, 2008 at 11:16:30PM +0100, Moritz Muehlenhoff wrote: > On Thu, Nov 16, 2006 at 08:57:05PM +0100, Arni Kromic wrote: > > Package: linux-image-2.6.17-2-686 > > Version: 2.6.17-9 > > Severity: important > > > > > > When I load i810 fb module (which by itself works fine with my adapter), X > > (also a i810 > > server) won't load and I get a message about X being unable to access the > > hardware. However, > > when I load vesafb (which I don't want to), both work fine. X also works > > fine when no fb. > > > > I'm not quitw sure if it's a kernel or X bug, but I report it as a kernel > > bug based on the > > fact that X works fine, except when i810fb module loaded. > > Does this error still occur with more recent kernel and X.org versions? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#409822: marked as done (linux-image-2.6.18-4-vserver-686: pcmcia wireless card doesn't work until inserting usb ethernet)
Your message dated Mon, 27 Jul 2009 01:35:19 +0200 with message-id <20090726233519.ga26...@galadriel.inutil.org> and subject line Re: no longer have hardware to test: 409822, 405135 has caused the Debian Bug report #409822, regarding linux-image-2.6.18-4-vserver-686: pcmcia wireless card doesn't work until inserting usb ethernet 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 ow...@bugs.debian.org immediately.) -- 409822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-4-vserver-686 Version: 2.6.18.dfsg.1-10 Severity: normal so, i've got this old pcmcia wireless card, and the strange thing is that it doesn't work until i insert a usb ethernet device. i don't know what could be causing this behavior ... from my syslog: Feb 2 11:10:00 ghig kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 2 11:10:04 ghig kernel: eth0: New link status: Connected (0001) Feb 2 11:10:04 ghig kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 2 11:10:04 ghig kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2 Feb 2 11:10:05 ghig kernel: usb 1-1: configuration #1 chosen from 1 choice Feb 2 11:10:05 ghig kernel: pegasus: v0.6.13 (2005/11/13), Pegasus/Pegasus II USB Ethernet driver Feb 2 11:10:05 ghig kernel: pegasus 1-1:1.0: setup Pegasus II specific registers Feb 2 11:10:05 ghig kernel: pegasus 1-1:1.0: eth1, D-Link DSB-650TX, 00:40:05:8e:d4:a0 Feb 2 11:10:05 ghig kernel: usbcore: registered new driver pegasus if i don't insert the usb ethernet device, i can wait 5-10 hours and still not get the "ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready" message. i've tried at least a dozen times over the past couple months, and it seems reproduceable on my system. could somehow the link status on the usb ethernet device trigger some sort of link status event for the pcmcia wireless card? certainly got me a little confused. lsusb Bus 001 Device 003: ID 2001:400b D-Link Corp. [hex] Bus 001 Device 001: ID : pccardctl info PRODID_1="Lucent Technologies" PRODID_2="WaveLAN/IEEE" PRODID_3="Version 01.01" PRODID_4="" MANFID=0156,0002 FUNCID=6 live well, vagrant -- 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-vserver-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-vserver-686 depends on: ii coreutils 5.97-5 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-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-4-vserver-686 recommends: ii libc6-i686 2.3.6.ds1-10 GNU C Library: Shared libraries [i ii util-vserver0.30.211-6 user-space tools for Linux-VServer -- debconf information excluded --- End Message --- --- Begin Message --- On Mon, Jun 15, 2009 at 07:24:48PM -0700, Vagrant Cascadian wrote: > i no longer have the hardware necessary to test the following bugs: > > 405135: linux-image-2.6.18-3-xen-vserver-686: kernel freezes on pcmcia card > insertion > > 409822: linux-image-2.6.18-4-vserver-686: pcmcia wireless card doesn't work > until inserting usb ethernet > > please feel free to close them or mark as unreproducible. Let's just close them, then. Greetings from the other side of hacklab #1, Moritz --- End Message ---
Bug#405135: marked as done (linux-image-2.6.18-3-xen-vserver-686: kernel freezes on pcmcia card insertion)
Your message dated Mon, 27 Jul 2009 01:35:19 +0200 with message-id <20090726233519.ga26...@galadriel.inutil.org> and subject line Re: no longer have hardware to test: 409822, 405135 has caused the Debian Bug report #405135, regarding linux-image-2.6.18-3-xen-vserver-686: kernel freezes on pcmcia card insertion 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 ow...@bugs.debian.org immediately.) -- 405135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-3-xen-vserver-686 Version: 2.6.18-8 Severity: important at boot, when the pcmcia cards get initialized, the kernel freezes entirely. if i boot without the card inserted, it freezes upon insertion of the card. i have no problems with linux-image-2.6.18-3-vserver-686 (2.6.18-8). card information: pccardctl ident Socket 0: product info: "Lucent Technologies", "WaveLAN/IEEE", "Version 01.01", "" manfid: 0x0156, 0x0002 function: 6 (network) using: ii pcmciautils014-3 PCMCIA utilities for Linux 2.6 live well, vagrant -- 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-3-vserver-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-xen-vserver-686 depends on: ii initramfs-tools 0.85e tools for generating an initramfs ii linux-modules-2.6.18-3-xen-vs 2.6.18-8 Linux 2.6.18 modules on PPro/Celer Versions of packages linux-image-2.6.18-3-xen-vserver-686 recommends: pn libc6-xen (no description available) at the time, i have libc6-xen installed, if that matters... -- no debconf information --- End Message --- --- Begin Message --- On Mon, Jun 15, 2009 at 07:24:48PM -0700, Vagrant Cascadian wrote: > i no longer have the hardware necessary to test the following bugs: > > 405135: linux-image-2.6.18-3-xen-vserver-686: kernel freezes on pcmcia card > insertion > > 409822: linux-image-2.6.18-4-vserver-686: pcmcia wireless card doesn't work > until inserting usb ethernet > > please feel free to close them or mark as unreproducible. Let's just close them, then. Greetings from the other side of hacklab #1, Moritz --- End Message ---
Bug#404626: marked as done (linux-image-2.6.18-3-486: logitech quickcam not detected by ati rage r128 all-in- wonder-tvout-card)
Your message dated Mon, 27 Jul 2009 01:33:34 +0200 with message-id <2009072624.ga22...@galadriel.inutil.org> and subject line Re: linux-image-2.6.18-3-486: logitech quickcam not detected by ati rage r128 all-in- wonder-tvout-card has caused the Debian Bug report #404626, regarding linux-image-2.6.18-3-486: logitech quickcam not detected by ati rage r128 all-in- wonder-tvout-card 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 ow...@bugs.debian.org immediately.) -- 404626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-3-486 Version: 2.6.18-7 Severity: important Dear Sir, The quickcam messenger logitech cannot be detected by the kernel of linux if it is with a video card of type : ati all-in-wonder rage 128 tvin / tvout bulk. The corresponding webcam is shown there : http://patrick295767.sitesled.com/debian-bug-report/logitech-webcam-quickcam-messenger.jpg The webcam has been tried on several linux image version above 2.6 (ubuntu dapper & edgy) and is fully working on computer having nvidia video card and s3 video cards... For ati all in wonder video card, the problem can be caused by the fact that both ati tvout/tvin and webcam are not detected by the kernel. No additioanl /dev/video are created and seen for the logitech webcam and ati. I recently bought an additional tv-card tuner and the /dev/video0 has been created. I can watch tv via the newly bought tv-card tuner of type pinnacle and pci. Hence, on the computer, /dev/video0 /dev/video1 /dev/video2 at least should be seen and recognized. Only the /dev/video0 corresponding to the tv tuner card pinnacle can be accessible. I tried anything that can be adviced on forums and persons around since more than 6-8 months, even more. I would be very welcoming if you could fix the linux kernel issue. Thank you very much, Yours sincerely, Patrick -- 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-3-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-486 depends on: ii coreutils 5.97-5 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-pre3-1 tools for managing Linux kernel mo linux-image-2.6.18-3-486 recommends no packages. -- debconf-show failed --- End Message --- --- Begin Message --- On Thu, Dec 25, 2008 at 11:18:29PM +0100, Moritz Muehlenhoff wrote: > On Wed, Dec 27, 2006 at 02:39:23AM +0100, patrick295767 wrote: > > Package: linux-image-2.6.18-3-486 > > Version: 2.6.18-7 > > Severity: important > > > > Dear Sir, > > > > The quickcam messenger logitech cannot be detected by the kernel of linux > > if it is with a > > video card of type : ati all-in-wonder rage 128 tvin / tvout bulk. The > > corresponding webcam > > is shown there : > > http://patrick295767.sitesled.com/debian-bug-report/logitech-webcam-quickcam-messenger.jpg > > > > > > The webcam has been tried on several linux image version above 2.6 (ubuntu > > dapper & > > edgy) > > and is fully working on computer having nvidia video card and s3 video > > cards... > > > > For ati all in wonder video card, the problem can be caused by the fact > > that both ati > > tvout/tvin and webcam are not detected by > > the kernel. No additioanl /dev/video are created and seen for the logitech > > webcam and ati. > > > > I recently bought an additional tv-card tuner and the /dev/video0 has been > > created. I can > > watch tv via the newly bought tv-card tuner of type pinnacle and pci. > > > > Hence, on the computer, /dev/video0 /dev/video1 /dev/video2 at least > > should be seen and > > recognized. Only the /dev/video0 corresponding to the tv tuner card > > pinnacle can be > > accessible. > > > > I tried anything that can be adviced on forums and persons around since > > more than 6-8 > > months, even more. > > > > I would be very welcoming if you could fix the linux kernel issue. > > Does this error still occur with more recent kernel versions? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#395008: marked as done (linux-image-2.6.18-1-686: Oops with irda driver)
Your message dated Mon, 27 Jul 2009 01:29:26 +0200 with message-id <20090726232926.ga8...@galadriel.inutil.org> and subject line Re: linux-image-2.6.18-1-686: Oops with irda driver has caused the Debian Bug report #395008, regarding linux-image-2.6.18-1-686: Oops with irda driver 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 ow...@bugs.debian.org immediately.) -- 395008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-1-686 Version: 2.6.18-3 Severity: important Hi ! I am using gnokii, via xgnokii, and I have strange behaviour. When I quit (after being connected, or after the phone crashed) xgnokii, I have this kernel oops : Oct 24 13:17:04 localhost kernel: IrLAP, no activity on link! Oct 24 13:17:13 localhost last message repeated 3 times Oct 24 13:17:14 localhost kernel: irlap_change_speed(), setting speed to 9600 Oct 24 13:17:14 localhost kernel: irda_poll(), POLLHUP Oct 24 13:17:14 localhost kernel: irda_poll(), POLLHUP Oct 24 13:17:42 localhost kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address Oct 24 13:17:42 localhost kernel: printing eip: Oct 24 13:17:42 localhost kernel: c1304908 Oct 24 13:17:42 localhost kernel: *pde = Oct 24 13:17:42 localhost kernel: Oops: 0002 [#1] Oct 24 13:17:42 localhost kernel: SMP Oct 24 13:17:42 localhost kernel: Modules linked in: nls_utf8 nls_cp437 vfat fat radeon drm binfmt_misc cpufreq_ondemand nfs lockd nfs_acl sunrpc irtty_sir sir_dev ipv6 button ac battery xfs sd_mod cpufreq_powersave cpufreq_userspace acpi_cpufreq freq_table ide_generic usbhid usb_storage scsi_mod eth1394 ehci_hcd ohci_hcd ohci1394 ieee1394 pcmcia firmware_class joydev snd_intel8x0m snd_seq_dummy snd_seq_oss snd_intel8x0 tsdev snd_ac97_codec snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_ac97_bus snd_seq_device evdev snd_pcm_oss snd_mixer_oss shpchp pci_hotplug intel_agp agpgart snd_pcm snd_timer snd soundcore snd_page_alloc yenta_socket rsrc_nonstatic pcmcia_core psmouse parport_pc parport pcspkr rtc serio_raw floppy irda crc_ccitt ext3 jbd mbcache dm_mirror dm_snapshot dm_mod ide_disk ide_cd cdrom piix generic ide_core uhci_hcd usbcore 3c59x mii thermal processor fan Oct 24 13:17:42 localhost kernel: CPU:0 Oct 24 13:17:42 localhost kernel: EIP:0060:[]Not tainted VLI Oct 24 13:17:42 localhost kernel: EFLAGS: 00210086 (2.6.18-1-686 #1) Oct 24 13:17:42 localhost kernel: EIP is at 0xc1304908 Oct 24 13:17:42 localhost kernel: eax: d5627db0 ebx: d5627d90 ecx: edx: 0001 Oct 24 13:17:42 localhost kernel: esi: 00100100 edi: ebp: d5627df0 esp: d5627dd0 Oct 24 13:17:42 localhost kernel: ds: 007b es: 007b ss: 0068 Oct 24 13:17:42 localhost kernel: Process xgnokii (pid: 4635, ti=d5626000 task=caf1faa0 task.ti=d5626000) Oct 24 13:17:42 localhost kernel: Stack: c0116251 0001 cb37c0d8 cb37c0d8 Oct 24 13:17:42 localhost kernel:d5627e14 c01166a2 0001 00200286 cb37c0d8 caed9000 Oct 24 13:17:42 localhost kernel:cb37c0c0 d4d89910 c0222358 cb37c0c0 caed9000 d896e785 cb37c0c0 Oct 24 13:17:42 localhost kernel: Call Trace: Oct 24 13:17:42 localhost kernel: [] __wake_up_common +0x2f/0x53 Oct 24 13:17:42 localhost kernel: [] __wake_up+0x2a/0x3d Oct 24 13:17:42 localhost kernel: [] sock_def_wakeup +0x2e/0x39 Oct 24 13:17:42 localhost kernel: [] irda_release+0x49/0x129 [irda] Oct 24 13:17:42 localhost kernel: [] __lock_irda_stream_release+0xf/0x1a [irda] Oct 24 13:17:42 localhost kernel: [] sock_release+0x11/0x86 Oct 24 13:17:42 localhost kernel: [] sock_close+0x26/0x2a Oct 24 13:17:42 localhost kernel: [] __fput+0x8a/0x13f Oct 24 13:17:42 localhost kernel: [] filp_close+0x4e/0x54 Oct 24 13:17:42 localhost kernel: [] put_files_struct +0x65/0xa7 Oct 24 13:17:42 localhost kernel: [] do_exit+0x1d1/0x71b Oct 24 13:17:42 localhost kernel: [] sys_exit_group+0x0/0xd Oct 24 13:17:42 localhost kernel: [] get_signal_to_deliver +0x395/0x3bc Oct 24 13:17:42 localhost kernel: [] do_notify_resume +0x71/0x5d7 Oct 24 13:17:42 localhost kernel: [] remove_wait_queue +0xf/0x34 Oct 24 13:17:42 localhost kernel: [] sys_recv+0x19/0x1d Oct 24 13:17:42 localhost kernel: [] sys_socketcall +0xfc/0x181 Oct 24 13:17:42 localhost kernel: [] work_notifysig+0x13/0x19 Oct 24 13:17:42 localhost kernel: Code: 00 00 00
Bug#391459: marked as done (8250/serial driver conflicts with smsc-ircc2 driver)
Your message dated Mon, 27 Jul 2009 01:21:15 +0200 with message-id <20090726232115.ga22...@galadriel.inutil.org> and subject line Re: Problem with serial/8250 driver still under 2.6.18 has caused the Debian Bug report #391459, regarding 8250/serial driver conflicts with smsc-ircc2 driver 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 ow...@bugs.debian.org immediately.) -- 391459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Severity: important Hi, I've seen different bugs related to serial ports and the 8250 driver but not exactly like mine, so here you get a new report (can it be that the driver is pretty broken in the 2.6.17 kernel? :-> ). Anyway, even though everything seems pretty OK (modules loaded, device files present, kernel recognizes the port), I'm not able anymore to sync with jpilot on /dev/ttyS0 under kernel 2.6.17 (I tested it: it still works perfectly under kernel 2.6.16-18), telling me that: pi_bind error: /dev/ttyS0 No such device Check your serial port and settings Exiting with status SYNC_ERROR_BIND I get similar errors using pilot-link tools, and each time I try to access the serial port, I get a new "ttyS0: LSR safety check engaged!" message in dmesg. I set the bug to important because I will have to rollback to 2.6.16; without ability to sync PC and Palm, I can't really work. I put some more info below, don't hesitate to tell me if you need more. Thanks for your help, have a nice week-end, Eric $ dmesg | grep tty serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A 00:02: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS0: LSR safety check engaged! ttyS0: LSR safety check engaged! ttyS0: LSR safety check engaged! ttyS2: LSR safety check engaged! [...] $ setserial -g /dev/ttyS? /dev/ttyS0: No such device /dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3 /dev/ttyS2, UART: unknown, Port: 0x, IRQ: 0 /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3 $ ll /dev/ttyS? crw-rw 1 root dialout 4, 64 2006-10-06 20:02 /dev/ttyS0 crw-rw 1 root dialout 4, 65 2006-10-06 20:02 /dev/ttyS1 crw-rw 1 root dialout 4, 66 2006-10-06 20:02 /dev/ttyS2 crw-rw 1 root dialout 4, 67 2006-10-06 20:02 /dev/ttyS3 $ find /sys -name \*ttyS? /sys/class/tty/ttyS0 /sys/class/tty/ttyS3 /sys/class/tty/ttyS2 /sys/class/tty/ttyS1 /sys/devices/pnp0/00:02/tty:ttyS0 /sys/devices/platform/serial8250/tty:ttyS3 /sys/devices/platform/serial8250/tty:ttyS2 /sys/devices/platform/serial8250/tty:ttyS1 $ ll /sys/class/tty/ttyS0 total 0 -r--r--r-- 1 root root 4096 2006-10-06 18:17 dev lrwxrwxrwx 1 root root0 2006-10-06 20:02 device -> .../../../devices/pnp0/00:02 --w--- 1 root root 4096 2006-10-06 18:17 uevent - ttyS2 is set quiet for use by irda-utils (which works) - parameters of the port are correct as compared with Windows -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.80 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i686 2.3.6.ds1-4 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-6
Bug#538212: please provide a linux-image-r5k-ip22
* Siggy Brentrup [2009-07-25 13:48]: > openssh is compiled with -fPIC on mipsen, downgrading to the stable > version cures the system. Actually I planned to follow up after > compiling w/o -fPIC and testing installation to be sure to have found > the culprit, but since you are writing this, here's the current status: Do you think you could mention this in a follow-up to your mail on debian-mips. Maybe some of the porters will have an idea. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#377152: marked as done (debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz fails; miBoot works)
Your message dated Mon, 27 Jul 2009 01:06:30 +0200 with message-id <20090726230630.ga14...@galadriel.inutil.org> and subject line Re: Bug#377152: debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz fails; miBoot works has caused the Debian Bug report #377152, regarding debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz fails; miBoot works 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 ow...@bugs.debian.org immediately.) -- 377152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: important Tags: powerpc debian-installer For Old World PowerPC Macintosh BootX hangs at the 'MMU:exit' line of the kernel boot for both hd-media and cdrom kernel and initrd images, but the miBoot floppy works. All methods use a variant of 2.6.16-2-powerpc, but the miBoot uses a different .config. For BootX booting, the 2006-03-30 images are the last ones that work. 2006-04-01 was the first use of 2.6.16-1-powerpc kernels and initrds, however, as with the current situation, the miBoot floppies worked (until the abi change, as change over to wouter doing the builds). I didn't detect this situation because I only used BootX for a Beta2 install, and subsequently used the miBoot floppies. The following system information is irrelevant; it's from a completely different machine & architecture, but I leave it because reportbug puts it there. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (50, 'testing'), (7, 'unstable'), (3, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.16-2-k7 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) --- End Message --- --- Begin Message --- On Sat, Feb 07, 2009 at 03:25:05PM +0100, Moritz Muehlenhoff wrote: > On Sun, Jan 04, 2009 at 10:45:26PM -0500, Daniel Dickinson wrote: > > On Thu, 25 Dec 2008 23:20:05 +0100 > > Moritz Muehlenhoff wrote: > > > > > > Does this error still occur with more recent kernel versions? > > > > I will try later this week. > > Have you been able to reproduce the problem? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#379218: marked as done (linux-image-2.6.16-2-powerpc: Can't boot with bootx on a beige G3 (oldworld))
Your message dated Mon, 27 Jul 2009 01:06:30 +0200 with message-id <20090726230630.ga14...@galadriel.inutil.org> and subject line Re: Bug#377152: debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz fails; miBoot works has caused the Debian Bug report #377152, regarding linux-image-2.6.16-2-powerpc: Can't boot with bootx on a beige G3 (oldworld) 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 ow...@bugs.debian.org immediately.) -- 377152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.16-2-powerpc Version: 2.6.16-17 Severity: important I wanted to upgrade from 2.6.15 to 2.6.16, but this kernel seems to be unbootable for my oldworld G3. The kernel just writes a welcome-message, writes strange green signs on the top of the screen and freezes. Because quik doesn't seem to work on the beige G3, I'm forced to use the bootx-extension for MacOS - Maybe it has sth. to do with this? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-2-powerpc depends on: ii initramfs-tools [linux-initra 0.69b tools for generating an initramfs ii mkvmlinuz 23 create a kernel to boot a PowerPC ii module-init-tools 3.2.2-3tools for managing Linux kernel mo linux-image-2.6.16-2-powerpc recommends no packages. -- debconf information: linux-image-2.6.16-2-powerpc/postinst/old-system-map-link-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/postinst/create-kimage-link-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/preinst/overwriting-modules-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/postinst/depmod-error-2.6.16-2-powerpc: false linux-image-2.6.16-2-powerpc/preinst/abort-overwrite-2.6.16-2-powerpc: linux-image-2.6.16-2-powerpc/prerm/removing-running-kernel-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/postinst/depmod-error-initrd-2.6.16-2-powerpc: false linux-image-2.6.16-2-powerpc/prerm/would-invalidate-boot-loader-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-powerpc/postinst/old-dir-initrd-link-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/preinst/bootloader-initrd-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/preinst/lilo-initrd-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/postinst/old-initrd-link-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/preinst/already-running-this-2.6.16-2-powerpc: linux-image-2.6.16-2-powerpc/preinst/initrd-2.6.16-2-powerpc: linux-image-2.6.16-2-powerpc/preinst/failed-to-move-modules-2.6.16-2-powerpc: linux-image-2.6.16-2-powerpc/preinst/abort-install-2.6.16-2-powerpc: linux-image-2.6.16-2-powerpc/preinst/elilo-initrd-2.6.16-2-powerpc: true linux-image-2.6.16-2-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.16-2-powerpc/postinst/bootloader-error-2.6.16-2-powerpc: linux-image-2.6.16-2-powerpc/postinst/bootloader-test-error-2.6.16-2-powerpc: --- End Message --- --- Begin Message --- On Sat, Feb 07, 2009 at 03:25:05PM +0100, Moritz Muehlenhoff wrote: > On Sun, Jan 04, 2009 at 10:45:26PM -0500, Daniel Dickinson wrote: > > On Thu, 25 Dec 2008 23:20:05 +0100 > > Moritz Muehlenhoff wrote: > > > > > > Does this error still occur with more recent kernel versions? > > > > I will try later this week. > > Have you been able to reproduce the problem? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#532721: marked as done (linux-2.6: CVE-2009-1385 dos in e1000 driver)
Your message dated Mon, 27 Jul 2009 01:00:06 +0200 with message-id <20090726230006.ga26...@galadriel.inutil.org> and subject line fixed has caused the Debian Bug report #532721, regarding linux-2.6: CVE-2009-1385 dos in e1000 driver 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 ow...@bugs.debian.org immediately.) -- 532721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Severity: important Version: 2.6.18.dfsg.1-24 (and newer) Tags: security , patch Hi, the following CVE (Common Vulnerabilities & Exposures) id was published for linux-2.6. CVE-2009-1385[0]: | Integer underflow in the e1000_clean_rx_irq function in | drivers/net/e1000/e1000_main.c in the e1000 driver in the Linux kernel | before 2.6.30-rc8, the e1000e driver in the Linux kernel, and Intel | Wired Ethernet (aka e1000) before 7.5.5 allows remote attackers to | cause a denial of service (panic) via a crafted frame size. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. Patches available [1]. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1385 http://security-tracker.debian.net/tracker/CVE-2009-1385 [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ea30e11970a96cfe5e32c03a29332554573b4a10 --- End Message --- --- Begin Message --- Version: 2.6.30-1 --- End Message ---
Bug#532722: marked as done (linux-2.6: CVE-2009-1914 local dos in /proc/iomem on sparc)
Your message dated Sun, 26 Jul 2009 23:45:59 +0200 with message-id <20090726214559.ga17...@galadriel.inutil.org> and subject line Fixed has caused the Debian Bug report #532722, regarding linux-2.6: CVE-2009-1914 local dos in /proc/iomem on sparc 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 ow...@bugs.debian.org immediately.) -- 532722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: FILLINAFFECTEDVERSION Severity: important Tags: security , patch Hi, the following CVE (Common Vulnerabilities & Exposures) id was published for linux-2.6. CVE-2009-1914[0]: | The pci_register_iommu_region function in | arch/sparc/kernel/pci_common.c in the Linux kernel before 2.6.29 on | the sparc64 platform allows local users to cause a denial of service | (system crash) by reading the /proc/iomem file, related to | uninitialized pointers and the request_resource function. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. Patches available [1]. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1914 http://security-tracker.debian.net/tracker/CVE-2009-1914 [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=192d7a4667c6d11d1a174ec4cad9a3c5d5f9043c --- End Message --- --- Begin Message --- Version: 2.6.29-1 --- End Message ---
Bug#538410: atl1c: ethernet broken on Eee PC model 1005HA-H
On Sat, Jul 25, 2009 at 01:39:55PM -0300, Ben Armstrong wrote: > Package: linux-image-2.6.30-1-686 > Version: 2.6.30-3 > Severity: normal > > When using a debian-installer daily image on an Eee PC model 1005HA-H, to > which > Otavio just added atl1c, our tester, Yoda-BZH on irc, could not get ethernet > to > work at all. Here is his report: > > > debian-installer/i386/linux vga=771 > initrd=debian-installer/i386/initrd.gz -- quiet > > Choosing language French > Country: France > KB Layout: Françs (fr-latin9) > > At this point I have few lines about atl1c in dmesg : > atl1c :01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > atl1c :01:00.0: setting latency timer to 64 > atl1c :01:00.0: PME# disabled > atl1c :01:00.0: PME# disabled > atl1c :01:00.0: version 1.0.0.1-NAPI > > ** detecting hardware step > In dmesg I now have : > atl1c :01:00.0: irq 27 for MSI/MSI-X > atl1c :01:00.0: alt1c: eth0 NIC Link is Up<100 Mbps Full Duplex> > atl1c :01:00.0: Unable to allocate MSI interrupt Error: -22 > ADDRCONF(NETDEV_UP): eth0: link is not ready > > At this point, dhcp fails to acquire an address. Statically configuring the > network doesn't help, either. > > Searching Linus's git tree reveals that there have been some patches to atl1c > since 2.6.30 was released, but we don't know if any of these are relevant to > our problem or not: > > http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git&a=search&h=HEAD&st=commit&s=atl1c > > I find it annoying that at least this bug appears to be a duplicate of an > atl1e > bug fixed a year ago: > > In atl1c this year, after 2.6.30 was released: > > atl1c: WAKE_MCAST tested twice, not WAKE_UCAST > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0ed586d075ef65c0268982e5b7f36d0ffaa95547 > > In atl1e last year, submitted by the same upstream author! > > atl1e: WAKE_MCAST 2x. 1st WAKE_UCAST? > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1a3c4bc61547e5a75fd3b85b425624756da4cffb > > Do you need any more info to patch 2.6.30's atl1c for us? We'd like to get > ethernet working on this model as soon as possible. > > Thanks, > Ben Armstrong, debian-eeepc project leader Hi Ben, could you (or "Yoda BSH") test that applying 0ed586d075ef65c0268982e5b7f36d0ffaa95547 on top of 2.6.30 fixes support for atl1c? If so, the best way to proceed would be to mail sta...@kernel.org so that the fix is picked up for the kernel stable update (2.6.30.4 or .5). In that case it will land in sid rather quickly and users of the stock upstream kernel benefit as well. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#538765: tp-smapi-modules-2.6.30-1-686: Cannot be modprobed with 2.6.30-1-686 kernel
Processing commands for cont...@bugs.debian.org: > reassign 538765 tp-smapi-source Bug #538765 [tp-smapi-modules-2.6.30-1-686] tp-smapi-modules-2.6.30-1-686: Cannot be modprobed with 2.6.30-1-686 kernel Bug reassigned from package 'tp-smapi-modules-2.6.30-1-686' to 'tp-smapi-source'. Bug #538765 [tp-smapi-source] tp-smapi-modules-2.6.30-1-686: Cannot be modprobed with 2.6.30-1-686 kernel Bug No longer marked as found in versions linux-modules-extra-2.6/2.6.30-1. Bug #538765 [tp-smapi-source] tp-smapi-modules-2.6.30-1-686: Cannot be modprobed with 2.6.30-1-686 kernel Ignoring request to alter fixed versions of bug #538765 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516150: more information
Hi there, 2009/7/26 Moritz Muehlenhoff : > On Thu, Feb 19, 2009 at 05:47:55PM +0100, Bastian Blank wrote: >> Please provide more information: >> - uname -a >> - the complete kernel log (dmesg) >> - cat /sys/devices/system/clocksource/clocksource0/* > > Dimitri, can you provide the mentioned information? Sorry, I missed one of the February messages... it must have gone into the spam trap. I sent the output of 'uname -a' here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515978#62 The system from which the information below was taken now appears to be working fine, as per my message http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515978#57 More info, in case it helps: - tornado:~$ >>> date Sun Jul 26 22:01:29 BST 2009 - tornado:~$ >>> uname -a Linux tornado 2.6.26-2-amd64 #1 SMP Fri Mar 27 04:02:59 UTC 2009 x86_64 GNU/Linux - Output of dmesg is attached. - tornado:~$ >>> cat /sys/devices/system/clocksource/clocksource0/* jiffies tsc tsc Please let me know if you need any other information. I'll keep a closer eye on the spam traps for a few days. :) -- 73, Ged.[0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-2-amd64 (Debian 2.6.26-15) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Mar 27 04:02:59 UTC 2009 [0.00] Command line: auto BOOT_IMAGE=Debian-2.6.26-2 ro root=fe01 irqfixup rootdelay=9 clock=tsc [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - c000 (usable) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fec0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 0001c000 (usable) [0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used [0.00] Entering add_active_range(0, 256, 786432) 1 entries of 3200 used [0.00] Entering add_active_range(0, 1048576, 1835008) 2 entries of 3200 used [0.00] max_pfn_mapped = 1835008 [0.00] init_memory_mapping [0.00] DMI 2.3 present. [0.00] ACPI Error (tbxfroot-0218): A valid RSDP was not found [20080321] [0.00] Scanning NUMA topology in Northbridge 24 [0.00] Number of nodes 2 [0.00] Node 0 MemBase Limit 0001c000 [0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used [0.00] Entering add_active_range(0, 256, 786432) 1 entries of 3200 used [0.00] Entering add_active_range(0, 1048576, 1835008) 2 entries of 3200 used [0.00] Skipping disabled node 1 [0.00] NUMA: Using 63 for the hash shift. [0.00] Using node hash shift of 63 [0.00] Intel MultiProcessor Specification v1.4 [0.00] MPTABLE: OEM ID: OEM0 Product ID: PROD <6>MPTABLE: Product ID: PROD <6>MPTABLE: APIC at: 0xFEE0 [0.00] Bootmem setup node 0 -0001c000 [0.00] NODE_DATA [0001 - 00014fff] [0.00] bootmap [00015000 - 0004cfff] pages 38 [0.00] early res: 0 [0-fff] BIOS data page [0.00] early res: 1 [6000-7fff] TRAMPOLINE [0.00] early res: 2 [20-673397] TEXT DATA BSS [0.00] early res: 3 [396-40ef05e] RAMDISK [0.00] early res: 4 [9f000-f] BIOS reserved [0.00] early res: 5 [8000-] PGTABLE [0.00] [e200-e200025f] PMD -> [81000120-8100037f] on node 0 [0.00] [e2000260-e200061f] PMD -> [81000420-810006ff] on node 0 [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1835008 [0.00] Movable zone start PFN for each node [0.00] early_node_map[3] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 786432 [0.00] 0: 1048576 -> 1835008 [0.00] On node 0 totalpages: 1572767 [0.00] DMA zone: 56 pages used for memmap [0.00] DMA zone: 1249 pages reserved [0.00] DMA zone: 2694 pages, LIFO batch:0 [0.00] DMA32 zone: 14280 pages used for memmap [0.00] DMA32 zone: 768056 pages, LIFO batch:31 [0.00] Normal zone: 10752 pages used for memmap [0.00] Normal zone: 775680 pages, LIFO batch:31 [0.00] Movable zone: 0 pages used for memmap [0.00] Nvidia board detected. Ignoring ACPI timer override. [0.00] If you got timer trouble try acpi_use_timer_override [0.00] Intel MultiProcessor Specif
Bug#538765: tp-smapi-modules-2.6.30-1-686: Cannot be modprobed with 2.6.30-1-686 kernel
Package: tp-smapi-modules-2.6.30-1-686 Version: 2.6.30+0.40-1 Severity: grave Justification: renders package unusable Hi I am using kernel 2.6.30-1-686 on my Thinkpad T61 and suddenly I realized that tp_smapi module is not loaded in my kernel. Few outputs r...@gondolin:~# uname -r 2.6.30-1-686 r...@gondolin:~# modprobe tp_smapi WARNING: All config files need .conf: /etc/modprobe.d/thinkpad_acpi, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a future release. FATAL: Error inserting tp_smapi (/lib/modules/2.6.30-1-686/extra/tp-smapi/tp_smapi.ko): No such device or address r...@gondolin:~# lsmod | grep smapi r...@gondolin:~# r...@gondolin:~# lsmod | grep thinkpad thinkpad_acpi 55612 0 rfkill 9668 4 iwlcore,thinkpad_acpi led_class 3852 2 iwlcore,thinkpad_acpi nvram 6376 2 thinkpad_acpi I also tried building it myself with module-assistant, building and installation of package were successful, but inserting module failed with same error like the distribution pre-packaged module... Thanks for your time Jakub Lucký P.S. Hope I didn't select too high priority, but seems completely unusable for me -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tp-smapi-modules-2.6.30-1-686 depends on: ii linux-image-2.6.30-1-686 [lin 2.6.30-3 Linux 2.6.30 image on PPro/Celeron tp-smapi-modules-2.6.30-1-686 recommends no packages. tp-smapi-modules-2.6.30-1-686 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#488022: New findings
Christian, According to this PDF, if you are getting "Waiting for root file system" on bootup, IT821X IDE support needs to be hardcoded into the kernel, as opposed to a kernel module. CONFIG_BLK_DEV_IT821X=y. Changing this parameter works for me on a later kernel. http://www.compactpc.com.tw/drivers/ebox-2300SX/Vortex86SX_Linux_HowTo.pdf Sean Lazar -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#496934: base: Mounting Sony Ericsson C902 as mass storage fails on lenny, but works on etch
On Mon, Jun 01, 2009 at 11:58:01PM +0100, Ben Hutchings wrote: > Some other Sony Ericsson phones are known to implement USB storage > incorrectly, and the usb-storage driver has workarounds for them. > Please try running these commands (as root) to enable the same > workarounds for your phone: > > rmmod usb_storage > modprobe usb_storage quirks=0fce:e0d4:cr > > Then report whether this fixes the problem. Florian, have you been able to test this? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[stable] Adding bnx2x driver in 5.0.3
The bnx2x driver was disabled in lenny due to its use of non-free firmware. I have put together a patch that would reenable this driver in lenny's 2.6.26 kernel, making use of the firmware split-out patch that has gone upstream in Linux 2.6.31-rc releases (and is currently in use in the linux-2.6 2.6.30 packages in sid). I'd like to see if we can enable the use of this driver in 5.0.3. As far as I can tell, the necessary steps would be: - Update the kernel (obviously) - planned for a p-u upload this week - Backport the necessary changes for firmware-nonfree from sid to add the firmware-bnx2x package - Update kernel-wedge/stable to include bnx2x if available (are there space issues here?) - Update d-i in 5.0.3 to incorporate this driver -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519984: Cannot boot 2.6.26 kernel on HPPA N4000
On Sun, Jul 26, 2009 at 04:59:34PM +0200, Thibaut VARENE wrote: > On Sun, Jul 26, 2009 at 4:45 PM, Grant > Grundler wrote: > > On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote: > > >> Debian kernel seems to triggers HPMCs with PCI addon cards. It's been > >> discussed previously here, dunno what the status of that bug is, but > >> iirc it doesn't affect upstream. > > > > > > While many PCI cards won't work in PARISC systems, some do including many > > of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge > > support is broken and I've not tested those in a while. I have two systems > > setup in Cupertino Test Ring which each have one add-on card with PCI-PCI > > bridge (rio and ios). > > I guess this wasn't obvious enough from the thread I was pointing to, > but this bug affects otherwise perfectly working PCI cards (such as > tulip, SYM2, or tg3). As I said, only 2.6.26 from Debian seems to be > affected (among the few kernels I've tested). If we can narrow down the fix/config, we can try and fix it in a point release. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521548: linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels
Fathi Boudra wrote: >> Does this still occur with 2.6.30? > > yes > >> If so, can you pin down which init script triggers the failure? > > sure, as soon as I find the init script, I'll update the bug report. You can boot adding "init=/bin/sh" on the command line (grub or lilo) You will get the hand just after initramfs. Then, you can go to /etc/rc.S and /etc/rc2.d and start each script by hand. Ie, something like: cd /etc/rcS.d ls ./S01glibc.sh start ./S02hostname.sh start ... ./S99stop-bootlogd-single start cd ../rc2.d ls ./S10rsyslog start ... Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#425373: linux-image-2.6.18-3-xen-686: Xen kernel opps
On Mon, May 21, 2007 at 12:52:04PM +1000, Anand Kumria wrote: > Package: linux-image-2.6.18-3-xen-686 > Version: 2.6.18-7 > Severity: normal > > Hi, > > BUG: unable to handle kernel paging request at virtual address c79d00d9 > printing eip: > c79d00d9 > *pde = ma 03f59067 pa 00f59067 > *pte = ma pa f000 > Oops: [#1] > SMP > Modules linked in: xt_tcpudp xt_physdev bridge iptable_filter ip_tables > x_tables button ac battery ipv6 loop rtc parport_pc parport evdev > snd_cmipci gameport snd_pcm snd_page_alloc snd_opl3_lib shpchp snd_timer > snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd pci_hotplug > soundcore i2c_sis630 i2c_core serial_core sis_agp agpgart floppy pcspkr > ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid1 md_mod ide_generic > ide_cd cdrom ide_disk sis5513 generic ide_core ohci_hcd usbcore sis900 > mii thermal processor fan > CPU:0 > EIP:0061:[]Not tainted VLI > EFLAGS: 00010286 (2.6.18-3-xen-686 #1) > EIP is at 0xc79d00d9 > eax: ebx: c4c200c0 ecx: 0002 edx: c13a7a98 > esi: edi: c13a0084 ebp: c33a644c esp: c4c25f98 > ds: 007b es: 007b ss: 0069 > Process loop101 (pid: 9468, ti=c4c24000 task=c0e53000 task.ti=c4c24000) > Stack: 1000 0001 c5f50aa0 c79d25dc > a4001000 > 0001 c13a7984 c1019d80 1000 1000 a4001000 > >c79d227b c0102941 c13a7984 > > Call Trace: > [] do_lo_send_aops+0x0/0x20f [loop] > [] loop_thread+0x0/0x361 [loop] > [] kernel_thread_helper+0x5/0xb > Code: Bad EIP value. > EIP: [] 0xc79d00d9 SS:ESP 0069:c4c25f98 > > The BUG initially occurred in one of the DomUs and when it had locked up, > I destroyed it and attempted to create it again. That failed and I found > this on Dom0s dmesg output. Was this a one-time error and can the issue be reproduced? If you're running Lenny in the mean time, did the error reappear? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#426692: marked as done (One CPU slow down with kernel 2.6.18-4-686 (etch2))
Your message dated Sun, 26 Jul 2009 18:51:55 +0200 with message-id <20090726165155.ga15...@galadriel.inutil.org> and subject line Re: One CPU slow down with kernel 2.6.18-4-686 (etch2) has caused the Debian Bug report #426692, regarding One CPU slow down with kernel 2.6.18-4-686 (etch2) 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 ow...@bugs.debian.org immediately.) -- 426692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image Version: 2.6.18-4-686 (etch2) I have a dual xeon system with 2 xeon 5050 dual core processors with HyperTreading. Sometimes one of the physical cores slow down and never speed up again. There is a lot of "system" and "user" load (~80-90%) and a lot of "soft irq" (~20-30%) on that CPU (on 2 virtual CPU because of HyperTreading). When a process running on the slow CPU it finished approximately 10 times slower than on one of the other CPUs. The slow CPU speed up only when I reboot the system. I am using Debian GNU/Linux 4.0, kernel 2.6.18-4-686 (etch2). Used packages: apache2, bind9, postfix, courier, mysql, proftpd, etc... I am not using x-window. --- End Message --- --- Begin Message --- On Thu, Dec 25, 2008 at 05:12:07PM +0100, Moritz Muehlenhoff wrote: > On Wed, May 30, 2007 at 11:42:21AM +0200, Unas Mérnöki Iroda wrote: > > Package: linux-image > > Version: 2.6.18-4-686 (etch2) > > > > I have a dual xeon system with 2 xeon 5050 dual core processors with > > HyperTreading. > > Sometimes one of the physical cores slow down and never speed up again. > > There is > > a lot of "system" and "user" load (~80-90%) and a lot of "soft irq" > > (~20-30%) on > > that CPU (on 2 virtual CPU because of HyperTreading). When a process > > running on > > the slow CPU it finished approximately 10 times slower than on one of the > > other CPUs. > > > > The slow CPU speed up only when I reboot the system. > > > > I am using Debian GNU/Linux 4.0, kernel 2.6.18-4-686 (etch2). > > Used packages: apache2, bind9, postfix, courier, mysql, proftpd, etc... > > I am not using x-window. > > Does this error still occur with more recent kernel versions? > > If you're running Etch, could you try to reproduce this bug > with the 2.6.24 based kernel added in 4.0r4? > http://packages.qa.debian.org/l/linux-2.6.24.html No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#420602: marked as done (kernel fails to boot on SunBlade 100)
Your message dated Sun, 26 Jul 2009 18:49:11 +0200 with message-id <20090726164911.ga12...@galadriel.inutil.org> and subject line Re: Bug#420602: kernel fails to boot on SunBlade 100 has caused the Debian Bug report #420602, regarding kernel fails to boot on SunBlade 100 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 ow...@bugs.debian.org immediately.) -- 420602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-4-sparc64 Version: 2.6.18.dfsg.1-12 After upgrading a SunBlade 100 from Sarge to Etch, the 2.6.18 kernel fails to boot after SILO loaded it. The screen shows: Remapping the kernel... done. Booting Linux... flashes black and comes back to this. The machine looks hung because nothing else happens and the hard drive is idle. I have also tried booting from the Etch CD-ROM but the same error happens (just like bug #419698). _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ --- End Message --- --- Begin Message --- Version: 2.6.26-1 On Wed, Nov 12, 2008 at 02:02:13PM +0100, Moritz Muehlenhoff wrote: > On Wed, Nov 12, 2008 at 01:43:29PM +0100, Kolargol double zero wrote: > > > > > If you're running Etch, could you try to reproduce this bug > > > with the 2.6.24 based kernel added in 4.0r4? > > > > Thanks for your suggestion Moritz. > > > > I've tried that by installing packages linux-image-2.6-sparc64-etchnhalf > > (version 2.6.24+13~etchnhalf.1) and linux-image-2.6.24-etchnhalf.1-sparc64 > > (version 2.6.24-6~etchnhalf.6). My machine boots correctly with a nice > > console :) but the built-in Ethernet device doesn't work anymore... :( > > Could this be related to http://bugzilla.kernel.org/show_bug.cgi?id=10273 ? > > Quite likely. #10273 was introduced in 2.6.23 and fixed in 2.6.25.4. > > To verify you could apply the patch provided by David Miller > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;a=commit;h=227c3311786dbe64cb221e63d53817f98240e587 > to your 2.6.24 kernel or alternatively you could upgrade to Lenny, > which is based on 2.6.26 and won't change very much any more, since > the release is close. Marking 2.6.26 as fixed. Cheers, Moritz --- End Message ---
Bug#381719: marked as done (Kernel panic enabling IO-APIC IRQs on MacBook Pro)
Your message dated Sun, 26 Jul 2009 18:46:16 +0200 with message-id <20090726164616.ga7...@galadriel.inutil.org> and subject line Re: Still happening with 2.6.26-8 has caused the Debian Bug report #381719, regarding Kernel panic enabling IO-APIC IRQs on MacBook Pro 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 ow...@bugs.debian.org immediately.) -- 381719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.16-17 When I boot the installer on my MacBook Pro, it sometimes kernel panics: Getting VERSION: 50014 Getting VERSION: 50014 Getting ID: 0 Getting LVT0: 700 Getting LVT1: 400 enabled ExtINT on CPU#0 ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... failed. ...trying to set up timer as Virtual Wire IRQ... failed. ...trying to set up timer as ExtINT IRQ... failed :(. Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option -- Matt signature.asc Description: Digital signature --- End Message --- --- Begin Message --- On Sun, Jul 26, 2009 at 08:56:40AM -0700, Matt Kraai wrote: > On Sun, Jul 26, 2009 at 05:51:09PM +0200, Moritz Muehlenhoff wrote: > > On Mon, Dec 15, 2008 at 12:02:28AM +0100, Moritz Muehlenhoff wrote: > > > On Wed, Oct 15, 2008 at 08:54:03AM -0700, Matt Kraai wrote: > > > > Howdy, > > > > > > > > I'm still experiencing this problem with 2.6.26-8. Should I report it > > > > upstream or should I reproduce it with a pristine upstream kernel > > > > first? > > > > > > Please try to reproduce it with a pristine 2.6.28-rcX kernel. If the > > > problem persists, please file a bug at bugzilla.kernel.org and pass > > > it to the bug report. > > > > Did you test this and/or file a bug report upstream? > > I've been running upstream kernels, but I haven't experienced this in > quite a while, so I haven't reported it upstream. Marking as closed, then. Cheers, Moritz --- End Message ---
Bug#381719: Still happening with 2.6.26-8
On Sun, Jul 26, 2009 at 05:51:09PM +0200, Moritz Muehlenhoff wrote: > On Mon, Dec 15, 2008 at 12:02:28AM +0100, Moritz Muehlenhoff wrote: > > On Wed, Oct 15, 2008 at 08:54:03AM -0700, Matt Kraai wrote: > > > Howdy, > > > > > > I'm still experiencing this problem with 2.6.26-8. Should I report it > > > upstream or should I reproduce it with a pristine upstream kernel > > > first? > > > > Please try to reproduce it with a pristine 2.6.28-rcX kernel. If the > > problem persists, please file a bug at bugzilla.kernel.org and pass > > it to the bug report. > > Did you test this and/or file a bug report upstream? I've been running upstream kernels, but I haven't experienced this in quite a while, so I haven't reported it upstream. -- Matt Kraai http://ftbfs.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#381719: Still happening with 2.6.26-8
On Mon, Dec 15, 2008 at 12:02:28AM +0100, Moritz Muehlenhoff wrote: > On Wed, Oct 15, 2008 at 08:54:03AM -0700, Matt Kraai wrote: > > Howdy, > > > > I'm still experiencing this problem with 2.6.26-8. Should I report it > > upstream or should I reproduce it with a pristine upstream kernel > > first? > > Please try to reproduce it with a pristine 2.6.28-rcX kernel. If the > problem persists, please file a bug at bugzilla.kernel.org and pass > it to the bug report. Did you test this and/or file a bug report upstream? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#475556: marked as done (ma311 wireless card not assigned correct driver after installation)
Your message dated Sun, 26 Jul 2009 17:52:09 +0200 with message-id <20090726155209.ga20...@galadriel.inutil.org> and subject line Re: linux-source-2.6.17: crash: hostap_cs & orinoco_cs both loading for same card? has caused the Debian Bug report #383865, regarding ma311 wireless card not assigned correct driver after installation 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 ow...@bugs.debian.org immediately.) -- 383865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation Severity: grave Justification: renders package unusable I have the Netgear MA311 card, which works correctly with the orinoco_pci module. However, both orinoco_pci and hostap_pci are loaded, rendering the card useless. To fix it, I need to rmmod hostap_pci, hostap, ieee80211_crypt, orinoco_pci, orinoco, hermes, and then finally modprobe orinoco_pci to get the card working again. To get the card to work each time the machine boots up, I've had to blacklist the hostap drivers too. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=en, LC_CTYPE=en (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) --- End Message --- --- Begin Message --- On Mon, Dec 15, 2008 at 12:05:46AM +0100, Moritz Muehlenhoff wrote: > On Sun, Aug 20, 2006 at 02:37:03PM +0800, clayton wrote: > > Package: linux-source-2.6.17 > > Version: 2.6.17-6 > > Severity: normal > > > > > > I have a wireless PCMCIA card that works fine on another machine using > > kernel 2. > > 6.16/hotplug, but locks this machine up hard every time using 2.6.16 and > > 2.6.17 > > and udev (requires power down and reboot). Crash occurs both on card > > insertion a > > nd on boot with card already inserted. > > > > On the machine where the card works: > > cardctl ident: > > Socket 0: > > product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", "" > > manfid: 0x0156, 0x0002 > > function: 6 (network) > > Does this error still occur with more recent kernel versions? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#383865: marked as done (linux-source-2.6.17: crash: hostap_cs & orinoco_cs both loading for same card?)
Your message dated Sun, 26 Jul 2009 17:52:09 +0200 with message-id <20090726155209.ga20...@galadriel.inutil.org> and subject line Re: linux-source-2.6.17: crash: hostap_cs & orinoco_cs both loading for same card? has caused the Debian Bug report #383865, regarding linux-source-2.6.17: crash: hostap_cs & orinoco_cs both loading for same card? 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 ow...@bugs.debian.org immediately.) -- 383865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-source-2.6.17 Version: 2.6.17-6 Severity: normal I have a wireless PCMCIA card that works fine on another machine using kernel 2. 6.16/hotplug, but locks this machine up hard every time using 2.6.16 and 2.6.17 and udev (requires power down and reboot). Crash occurs both on card insertion a nd on boot with card already inserted. On the machine where the card works: cardctl ident: Socket 0: product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", "" manfid: 0x0156, 0x0002 function: 6 (network) syslog on working machine: kernel: pccard: PCMCIA card inserted into slot 0 kernel: pcmcia: registering new device pcmcia0.0 cardmgr[2864]: socket 0: Senao SL-2011CD/SL-2011CDPLUS cardmgr[2864]: executing: 'modprobe hostap 2>&1' cardmgr[2864]: + WARNING: Failed to open config file /etc/modprobe.d/alsa: No such file or directory kernel: ieee80211_crypt: registered algorithm 'NULL' cardmgr[2864]: executing: 'modprobe hostap_cs 2>&1' cardmgr[2864]: + WARNING: Failed to open config file /etc/modprobe.d/alsa: No such file or directory kernel: hostap_cs: 0.4.4-kernel (Jouni Malinen ) kernel: hostap_cs: setting Vcc=33 (constant) kernel: hostap_cs: setting Vcc=33 (from config) kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01) kernel: IO window settings: cfg->io.nwin=1 dflt.io.nwin=1 kernel: io->flags = 0x0046, io.base=0x, len=64 kernel: hostap_cs: Registered netdevice wifi0 kernel: hostap_cs: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f kernel: prism2_hw_init: initialized in 200 ms kernel: wifi0: NIC: id=0x800c v1.0.0 kernel: wifi0: PRI: id=0x15 v1.1.0 kernel: wifi0: STA: id=0x1f v1.4.9 kernel: wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS kernel: wifi0: registered netdevice wlan0 On the machine that crashes, normally there is nothing interesting written to th e logs after I reboot. However, syslog tails sometimes show a few lines at crash time: syslog tail showed this one time on crash (2.6.16 or 2.6.17, not sure): kernel: pccard: PCMCIA card inserted into slot 0 kernel: cs: memory probe 0xa000-0xa0ff: excluding 0xa000-0xa0f kernel: cs: memory probe 0x6000-0x60f: clean kernel: pcmcia: register new device pcmcia0.0 cardmgr[2163]: socket 0: Senao SL-2011CD/SL-2011CDPLUS another syslog tail (kernel 2.6.17): kernel: pccard: PCMCIA card inserted into slot 0 kernel: pcmcia: registering new device pcmcia0.0 kernel: orinoco 0.15rc3 (David Gibson. And one time I swear I saw what looked like orinoco_cs and hostap_cs loading at same time, which I am thinking might be the problem? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-tp600e.13 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-source-2.6.17 depends on: ii binutils 2.17-2 The GNU assembler, linker and bina ii bzip2 1.0.3-3high-quality block-sorting file co Versions of packages linux-source-2.6.17 recommends: ii gcc 4:4.1.1-5 The GNU C compiler ii libc6-dev [libc-dev] 2.3.6-15 GNU C Library: Development Librari ii make 3.81-2 The GNU version of the "make" util -- no debconf information --- End Message --- --- Begin Message --- On Mon, Dec 15, 2008 at 12:05:46AM +0100, Moritz Muehlenhoff wrote: > On Sun, Aug 20, 2006 at 02:37:03PM +0800, clayton wrote: > > Package: linux-source-2.6.17 > > Version: 2.6.17-6 > > Severity: normal > > > > > > I have a wireless PCMCIA card that works fine on another machine using > > kernel 2. > > 6.16/hotplug, but locks this machine up hard every time using 2.6.16 and > > 2.6.17 > > and udev (requires power down and reboot). Crash occurs both on card > > insertion a > > nd on boot with card already inserted. > > > > On the machine where the card works: > > cardctl ident: > > Socket 0: > > product info: "INTERSIL", "HF
Bug#384933: marked as done (snd-emu10k1: Can't record audio on line-in)
Your message dated Sun, 26 Jul 2009 17:53:02 +0200 with message-id <20090726155302.ga25...@galadriel.inutil.org> and subject line Re: snd-emu10k1: Can't record audio on line-in has caused the Debian Bug report #384933, regarding snd-emu10k1: Can't record audio on line-in 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 ow...@bugs.debian.org immediately.) -- 384933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.17-2-k7 Version: 2.6.17-6 Severity: normal I've been using my SoundBlaster Live! Platinum 5.1 (with Live!Drive IR -- a front panel access with several inputs and outputs that fits in a 5-1/4" drive bay) for many years. Of course, it's never had all of its options working, since the routing of this input to that output and everything in between is rather complex. Now it seems that even recording sound on the normal line-in jack of the card is not functional when using ALSA's snd-emu10k1 driver. I can change the volume of the input and can hear "live" sound coming through, but I'm not able to record on that input. I've tried gnome-volume-control (aka gmix), alsamixergui, and aumix. None of them have gotten the card set up correctly. My main interest in having a functional recording capability is the fact that I run MythTV and have my TV capture card sending audio through the line-in jack. I also tried using the "sound-recorder" program to save a WAV file. I don't have a microphone handy, and I don't think I have an analog CD-ROM drive hooked up, so I don't know if all recording is broken, or if it's just the line-in jack. I've found that the OSS emu10k1 driver is still functional in this regard, so I'm using that for the time being. Also, I just noticed that the OSS driver is able to change the input gain when recording, something I've never been able to figure out with the ALSA driver. Unfortunately, the OSS driver doesn't route any sound to the headphone jack on the Live!Drive, which was my original reason for moving from the OSS drivers to ALSA a few years ago. There is (or was) a package of "emu-tools" that could allow users to play around with the audio routing, but I haven't seen any suitable ALSA replacement. I'll try to track it down, but I seem to recall that it was not in a usable state the last time I tried it. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (988, 'testing'), (500, 'stable'), (499, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.17-2-k7 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-k7 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-k7/postinst/old-system-map-link-2.6.17-2-k7: true linux-image-2.6.17-2-k7/preinst/overwriting-modules-2.6.17-2-k7: true linux-image-2.6.17-2-k7/postinst/create-kimage-link-2.6.17-2-k7: true linux-image-2.6.17-2-k7/preinst/failed-to-move-modules-2.6.17-2-k7: linux-image-2.6.17-2-k7/preinst/bootloader-initrd-2.6.17-2-k7: true linux-image-2.6.17-2-k7/preinst/abort-overwrite-2.6.17-2-k7: linux-image-2.6.17-2-k7/postinst/old-dir-initrd-link-2.6.17-2-k7: true linux-image-2.6.17-2-k7/preinst/abort-install-2.6.17-2-k7: linux-image-2.6.17-2-k7/preinst/initrd-2.6.17-2-k7: linux-image-2.6.17-2-k7/postinst/depmod-error-initrd-2.6.17-2-k7: false linux-image-2.6.17-2-k7/postinst/really-run-bootloader-2.6.17-2-k7: true linux-image-2.6.17-2-k7/prerm/removing-running-kernel-2.6.17-2-k7: true linux-image-2.6.17-2-k7/postinst/kimage-is-a-directory: linux-image-2.6.17-2-k7/prerm/would-invalidate-boot-loader-2.6.17-2-k7: true linux-image-2.6.17-2-k7/preinst/already-running-this-2.6.17-2-k7: linux-image-2.6.17-2-k7/postinst/old-initrd-link-2.6.17-2-k7: true linux-image-2.6.17-2-k7/postinst/depmod-error-2.6.17-2-k7: false linux-image-2.6.17-2-k7/preinst/lilo-initrd-2.6.17-2-k7: true linux-image-2.6.17-2-k7/postinst/bootloader-error-2.6.17-2-k7: linux-image-2.6.17-2-k7/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-k7/postinst/bootloader-test-error-2.6.17-2-k7: linux-image-2.6.17-2-k7/preinst/elilo-initrd-2.6.17-2-k7: true -- Mike Hicks signature.asc Description: This is a digitally signed message part --
Bug#380029: marked as done (linux-image-2.6.17-1-686: Can not find tty Serial using 2.6.17)
Your message dated Sun, 26 Jul 2009 17:49:57 +0200 with message-id <20090726154957.ga17...@galadriel.inutil.org> and subject line Re: Bug#380029: (linux-image-2.6.17-1-686: Can not find tty Serial using 2.6.17) has caused the Debian Bug report #380029, regarding linux-image-2.6.17-1-686: Can not find tty Serial using 2.6.17 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 ow...@bugs.debian.org immediately.) -- 380029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.17-1-686 Version: 2.6.17-4 Severity: normal When using linux-image-2.6.17 udev does not recognize and build the /dev/ttyS* ports for the serial8250 ports on my machine. Booting the machine with kernel 2.6.16 resolves this issue. This may be related to Bug#377539. My machine has the same IR SIR issue and kernel 2.6.16 resolved it as well. Please let me know if there is a specific area you would like me to troubleshoot to help resolve this problem. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.17-1-686 depends on: ii initramfs-tools [linux-initra 0.72 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-1-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-1-686/preinst/bootloader-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/old-dir-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/bootloader-test-error-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/old-initrd-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-1-686/postinst/depmod-error-2.6.17-1-686: false linux-image-2.6.17-1-686/prerm/removing-running-kernel-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/overwriting-modules-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/lilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/failed-to-move-modules-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/create-kimage-link-2.6.17-1-686: true linux-image-2.6.17-1-686/postinst/kimage-is-a-directory: linux-image-2.6.17-1-686/postinst/old-system-map-link-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/elilo-initrd-2.6.17-1-686: true linux-image-2.6.17-1-686/preinst/already-running-this-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/abort-overwrite-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/bootloader-error-2.6.17-1-686: linux-image-2.6.17-1-686/preinst/initrd-2.6.17-1-686: linux-image-2.6.17-1-686/postinst/depmod-error-initrd-2.6.17-1-686: false linux-image-2.6.17-1-686/preinst/abort-install-2.6.17-1-686: linux-image-2.6.17-1-686/prerm/would-invalidate-boot-loader-2.6.17-1-686: true --- End Message --- --- Begin Message --- On Fri, Dec 26, 2008 at 11:40:05AM +0100, Moritz Muehlenhoff wrote: > On Fri, Aug 11, 2006 at 03:18:24PM -0700, Bill Thompson wrote: > > A quick follow-up on this bug. I have been able to partially resolve > > this issue by forcing the 8250_pnp module to load at boot. > > Initially that module did not load by default. > > > > However, the first time the module loads, the UART settings for the > > ttyS* ports are listed as "unknown". This prevents the ports from being > > used. If I manually remove the 8250_pnp module and load it a second > > time, the UART is correctly set and the ports become available. It does > > not matter if the module is initially loaded at boot time or manually > > loaded after boot, you must load the module, unload it, and load it a > > second time to properly set the ttyS* ports. > > > > I will keep working on this and pass on what I find, but I would > > appreciate any thoughts or ideas people may have. > > Does this error still occur with more recent kernel versions? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#519984: Cannot boot 2.6.26 kernel on HPPA N4000
On Sun, Jul 26, 2009 at 4:45 PM, Grant Grundler wrote: > On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote: >> Debian kernel seems to triggers HPMCs with PCI addon cards. It's been >> discussed previously here, dunno what the status of that bug is, but >> iirc it doesn't affect upstream. > > > While many PCI cards won't work in PARISC systems, some do including many > of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge > support is broken and I've not tested those in a while. I have two systems > setup in Cupertino Test Ring which each have one add-on card with PCI-PCI > bridge (rio and ios). I guess this wasn't obvious enough from the thread I was pointing to, but this bug affects otherwise perfectly working PCI cards (such as tulip, SYM2, or tg3). As I said, only 2.6.26 from Debian seems to be affected (among the few kernels I've tested). HTH -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510853: closed by Bastian Blank (presume fixed)
Debian Bug Tracking System wrote: I presume that this bug is fixed with the virtualbox fixes. Closing, as no new information was provided. Yes, I think this is indeed fixed. My apologies for not responding earlier. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519984: Cannot boot 2.6.26 kernel on HPPA N4000
On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote: > On Sat, Jul 25, 2009 at 4:10 PM, Moritz Muehlenhoff wrote: > > > [Adding debian-hppa to CC and quoting in full] > > > > Is this a known issue, has it been fixed in current kernels from unstable? > > I believe this relates to that previous post: > http://www.mail-archive.com/debian-h...@lists.debian.org/msg06301.html > > Debian kernel seems to triggers HPMCs with PCI addon cards. It's been > discussed previously here, dunno what the status of that bug is, but > iirc it doesn't affect upstream. While many PCI cards won't work in PARISC systems, some do including many of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge support is broken and I've not tested those in a while. I have two systems setup in Cupertino Test Ring which each have one add-on card with PCI-PCI bridge (rio and ios). cheers, grant -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519984: Cannot boot 2.6.26 kernel on HPPA N4000
Moritz, thanks for forwarding... On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote: > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC) > > yields the following results (beginning at system startup): > > <> ... > > Elroy version TR3.0 (0x4) found at 0xfecf4000 > > PCI: Address space collision on region 0 of device :d0:00.0 > > [70e0800:70e08ff] ... > > sym53c8xx :d0:00.0: enabling device ( -> 0003) > > sym53c8xx :d0:00.0: enabling SERR and PARITY (0003 -> 0143) > > > > * SYSTEM ALERT ** ... > > 0x187000FF6292 - type 0 = Data Field Unused > > 0x5800187000FF6292 6D02 100F120F - type 11 = Timestamp 03/16/2009 The address space collision is likely the cause of this HPMC. (0xff6292 == HPMC) With HPMC's, "PIM" info is worth collecting. See http://www.parisc-linux.org/faq/kernelbug-howto.html for details on how to collect PIM info. It would also be helpful to collect "in io" output from the same PDC prompt that allows one to run "ser pim" and "clearpim". Lastly, if an older kernel does boot, "lspci -v" would be helpful. > Is this a known issue, has it been fixed in current kernels from unstable? The "parenting" of resources in the generic PCI support has been changed. I can't say if it fixes this problem. Is it possible to test a 2.6.30 or 2.6.31-rc kernel? thanks, grant -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521548: linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels
> Does this still occur with 2.6.30? yes > If so, can you pin down which init script triggers the failure? sure, as soon as I find the init script, I'll update the bug report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#477233: marked as done (linux-image-2.6.24-1-686: no sound with alsa/ICH6 anymore)
Your message dated Sun, 26 Jul 2009 16:26:13 +0200 with message-id <20090726142613.ga5...@galadriel.inutil.org> and subject line Re: linux-image-2.6.26-1-amd64: Got *my* problem solved meanwhile has caused the Debian Bug report #477233, regarding linux-image-2.6.24-1-686: no sound with alsa/ICH6 anymore 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 ow...@bugs.debian.org immediately.) -- 477233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: important After upgrading to kernel image 2.4.24 there's no pcm output any more to the speaker / line out. Previous used kernel image (2.6.18) still works. -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-5) (wa...@debian.org) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Thu Mar 27 17:45:04 UTC 2008 ** Command line: root=/dev/hda7 ro vga=791 ** Not tainted ** Kernel log: PCI: Setting latency timer of device :00:02.0 to 64 PM: Writing back config space on device :00:02.1 at offset 4 (was 0, writing 6000) PM: Writing back config space on device :00:1c.0 at offset f (was 40100, writing 4010a) PM: Writing back config space on device :00:1c.0 at offset 9 (was 10001, writing d3f1d001) PM: Writing back config space on device :00:1c.0 at offset 8 (was 0, writing b7f0b400) PM: Writing back config space on device :00:1c.0 at offset 7 (was 0, writing 3030) PM: Writing back config space on device :00:1c.0 at offset 3 (was 81, writing 810008) PM: Writing back config space on device :00:1c.0 at offset 1 (was 10, writing 100507) PCI: Setting latency timer of device :00:1c.0 to 64 ACPI: PCI Interrupt :00:1d.0[A] -> GSI 23 (level, low) -> IRQ 21 PCI: Setting latency timer of device :00:1d.0 to 64 usb usb1: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20 PCI: Setting latency timer of device :00:1d.1 to 64 usb usb2: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.2[C] -> GSI 18 (level, low) -> IRQ 19 PCI: Setting latency timer of device :00:1d.2 to 64 usb usb3: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.3[D] -> GSI 16 (level, low) -> IRQ 17 PCI: Setting latency timer of device :00:1d.3 to 64 usb usb4: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.7[A] -> GSI 23 (level, low) -> IRQ 21 PCI: Setting latency timer of device :00:1d.7 to 64 PM: Writing back config space on device :00:1e.0 at offset f (was 4, writing 400ff) PM: Writing back config space on device :00:1e.0 at offset 9 (was 10001, writing 1fff1) PM: Writing back config space on device :00:1e.0 at offset 8 (was 0, writing b800b800) PM: Writing back config space on device :00:1e.0 at offset 7 (was 22800010, writing 328000f0) PM: Writing back config space on device :00:1e.0 at offset 6 (was 20060600, writing 200a0600) PM: Writing back config space on device :00:1e.0 at offset 1 (was 15, writing 8100107) PCI: Setting latency timer of device :00:1e.0 to 64 PM: Writing back config space on device :00:1e.2 at offset f (was 100, writing 10a) PM: Writing back config space on device :00:1e.2 at offset 7 (was 0, writing b0040400) PM: Writing back config space on device :00:1e.2 at offset 6 (was 0, writing b0040800) PM: Writing back config space on device :00:1e.2 at offset 5 (was 1301, writing 18c1) PM: Writing back config space on device :00:1e.2 at offset 4 (was 1201, writing 1c01) PM: Writing back config space on device :00:1e.2 at offset 1 (was 295, writing 293) ACPI: PCI Interrupt :00:1e.2[A] -> GSI 17 (level, low) -> IRQ 16 PCI: Setting latency timer of device :00:1e.2 to 64 ipw2200: Unable to load ucode: -22 ipw2200: Unable to load firmware: -22 ipw2200: Failed to up device PM: Writing back config space on device :00:1e.3 at offset f (was 200, writing 20b) PM: Writing back config space on device :00:1e.3 at offset 5 (was 1501, writing 2001) PM: Writing back config space on device :00:1e.3 at offset 4 (was 1401, writing 2401) PM: Writing back config space on device :00:1e.3 at offset 1 (was 295, writing 291) ACPI: PCI Interrupt :00:1e.3[B] -> GSI 20 (level, low) -> IRQ 18 PCI: Setting latency timer of device :00:1e.3 to 64 PM: Writing back config space on device :00:1f.0 at offset 1 (was 207, writing 2000107) PM: Writing back config space on device :00:1f
Bug#510863: Lenny freezes as VMware guest in VMware Server 2.0
Hi, Does this error still with the final Lenny release? Did you run this with Vmware server kernel modules or pristine? This is fixed on final Lenny release. Kind regards, Marko. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 538391
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 538391 + pending Bug #538391 [linux-2.6] Alsa VIA driver: Surround and side channels are swapped Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#506644: marked as done (gnome-power-manager: Brightness applet does not change brightness)
Your message dated Sun, 26 Jul 2009 16:05:22 +0200 with message-id <20090726140522.ga10...@galadriel.inutil.org> and subject line Re: Bug#506644: [Pkg-utopia-maintainers] Bug#506644: gnome-power-manager: Brightness applet does not change brightness has caused the Debian Bug report #506644, regarding gnome-power-manager: Brightness applet does not change brightness 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 ow...@bugs.debian.org immediately.) -- 506644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-power-manager Version: 2.22.1-4 Severity: normal Dear GNOME team, Since an update of my Lenny system, the brightness applet does not manage to set the brightness anymore. Althouhg not 100 % sure, I have the impression that it happened before the update to the version that migrated to testing recently. I attached to this bug a digest of the updates made yesterday and today. My machine is a Sony VGC-LT71DB, a kind of iMac clone that has the bad idea of overheating when the brighness of the screen is at its default (and highest) level… Ah, I have `deb http://kde4.debian.net/ lenny main' in my sources.list. I hope it is not the cause of the problem! Many thanks for the work you made so far, and have a nice day, -- Charles Plessy, Tsurumi, Kanagawa, Japan -- Package-specific info: Distro version: lenny/sid Kernel version: 2.6.26-1-amd64 g-p-m version:2.22.1 HAL version: 0.5.11 System manufacturer: missing System version: missing System product: missing AC adapter present: no Battery present: no Laptop panel present: yes CPU scaling present: yes Battery Information: GNOME Power Manager Process Information: charles 3835 0.0 0.4 208456 10012 ?Ss 18:10 0:00 gnome-power-manager charles 5180 0.0 0.0 9532 916 pts/1S+ 18:30 0:00 | \_ less /usr/share/doc/gnome-power-manager/changelog.Debian.gz charles 7341 2.0 0.5 93576 11396 pts/3S+ 19:09 0:01 | \_ /usr/bin/python /usr/bin/reportbug gnome-power-manager charles 7389 0.0 0.0 10160 1320 pts/3S+ 19:10 0:00 | \_ /bin/bash /usr/share/reportbug/handle_bugscript /usr/share/bug/gnome-power-manager/script /tmp/reportbug-gnome-power-manage charles 5887 0.0 0.7 200100 16088 ?S18:42 0:00 /usr/lib/gnome-power-manager/gnome-brightness-applet --oaf-activate-iid=OAFIID:GNOME_BrightnessApplet_Factory --oaf-ior-fd=26 HAL Process Information: 106 3340 0.0 0.2 29596 4384 ?Ss 18:09 0:01 /usr/sbin/hald root 3341 0.0 0.0 17768 1192 ?S18:09 0:00 \_ hald-runner root 3361 0.0 0.0 19880 1172 ?S18:09 0:00 \_ hald-addon-input: Listening on /dev/input/event9 /dev/input/event8 /dev/input/event7 /dev/input/event5 /dev/input/event3 /dev/i root 3368 0.0 0.0 19892 1260 ?S18:09 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 106 3369 0.0 0.0 16604 1004 ?S18:09 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket root 3374 0.0 0.0 19880 1148 ?S18:09 0:00 \_ hald-addon-storage: polling /dev/hda (every 2 sec) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-power-manager depends on: ii dbus-x11 1.2.1-4 simple interprocess messaging syst ii gconf2 2.22.0-1 GNOME configuration database syste ii hal0.5.11-6 Hardware Abstraction Layer ii libart-2.0-2 2.3.20-2 Library of functions for 2D graphi ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libbonobo2-0 2.22.0-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.22.0-1 The Bonobo UI library ii libc6 2.7-16GNU C Library: Shared libraries ii libcairo2 1.6.4-6.1 The Cairo 2D vector graphics libra ii libdbus-1-31.2.1-4 simple interprocess messaging syst ii libdbus-glib-1-2 0.76-1simple interprocess messaging syst ii libfontconfig1 2.6.0-1 generic font configuration library ii libfreetype6 2.3.7-2 FreeType 2 font e
Bug#520409: linux-image-2.6.28-1-686: hangs on via padlock RNG module initialization
On Thu, Mar 19, 2009 at 02:45:16PM +0100, Olivier Berger wrote: > On Thu, Mar 19, 2009 at 02:25:37PM +0100, Olivier Berger wrote: > > > > Whenever booting the kernel on my VIA mainboard, it hangs, and I need to > > CTRL-C the VIA RNG module initialization. > > > > The same problem seems to have been reported here : > > http://bugs.archlinux.org/task/12823 but couldn't google anything else on > > the subject. > > > > Best regards, > > FYI, commenting padlock_aes and padlock_sha in /etc/modules (and leaving > via_rng) worked around the issue (also this worked fine with 2.6.26 from > stable). This could've been fixed by http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a760a6656e6f00bb0144a42a048cf0266646e22c Does it still show up with 2.6.30 from unstable? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#518467: linux-image-2.6.28-1-amd64: bluetooth mouse stutters since kernel upgrade
On Mon, Mar 09, 2009 at 06:14:08PM +0100, maximilian attems wrote: > On Mon, Mar 09, 2009 at 06:08:30PM +0100, pHilipp Zabel wrote: > > On Mon, Mar 9, 2009 at 1:04 PM, maximilian attems wrote: > > > On Fri, 06 Mar 2009, pHilipp Zabel wrote: > > > > > >> On Fri, Mar 6, 2009 at 1:12 PM, Bastian Blank wrote: > > >> > On Fri, Mar 06, 2009 at 12:41:25PM +0100, pHilipp Zabel wrote: > > >> >> ** Tainted: P M (17) > > >> > > > >> > You have a proprietary module loaded, we don't support kernels in this > > >> > state. Also the kernel logged machine checks, aka low level hardware > > >> > errors, which often shows serious hardware problems. > > >> > > > >> > Bastian > > >> > > >> I installed mcelog, changed the video driver from fglrx to vesa and > > >> rebooted, same result. (/var/log/mcelog is empty.) > > >> > > > > > > could you test if 2.6.29-rc7 trunk builds fix it for you: > > > see apt line http://wiki.debian.org/DebianKernel > > > > The problem persists. 2.6.26-1 works, 2.6.28-1 and 2.6.29-rc7 don't. > > Here is a log of the evdev output and a hcidump. The delays already > > appear in the hcidump: > > ok i see, please report upstream with this dump on bugzilla.kernel.org > and let us know the bug number. > > thanks a lot for quick reaction Philipp, did you report this upstream or has the problem been resolved by a more recent version? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#506644: [Pkg-utopia-maintainers] Bug#506644: gnome-power-manager: Brightness applet does not change brightness
Le Sun, Jul 26, 2009 at 03:03:38PM +0200, Moritz Muehlenhoff a écrit : > > > > Interestingly, on my machine both methods work. > > Did this change in more recent kernels? I just installed and tried 2.6.30-1-amd64 and it worked fine. Thanks for the ping. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510863: Lenny freezes as VMware guest in VMware Server 2.0
On Mon, Jan 05, 2009 at 02:54:54PM +0100, Marko Kobal wrote: > Package: main > Version: lenny RC1 release > > I've been testing Debian Lenny RC1 release as an VMware Guest in VMware > Server 2.0 (host Debian Etch 4.0 p5). After some time (couple of hours) of > normal work without any load Lenny just freezed. After reboot it is OK, but > then again same problem. > > The guest virtual machine uses one cpu, 256 MB of RAM, LSI logic for virtual > SCSI adapter, the host machine is an Intel Xeon 7120 server with Supermicro > motherboard. > > > I've seen this entries in guest's log > > Dec 19 19:16:09.985: vcpu-1| SCSI0: RESET BUS > Dec 19 19:16:09.986: vcpu-1| SCSI0: RESET BUS > Dec 19 19:16:20.017: vcpu-1| SCSI0: RESET BUS > Dec 19 19:16:21.117: vcpu-1| SCSI0: RESET BUS > > Also I'm sending vmware-core0.gz as attachemnt. Does this error still with the final Lenny release? Did you run this with Vmware server kernel modules or pristine? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508527: via-velocity.[ch] from 2.6.28 fixes the issue for me too
On Mon, Jan 19, 2009 at 09:55:23PM +, Russell Howe wrote: > I also experienced the same issue on a VIA EPIA SN motherboard. > > Copying drivers/net/via-velocity.[ch] from 2.6.28 into the 2.6.26 tree > seems to have fixed the issue and I have noticed no ill effects. > > via-velocity oopses for me straight away with 2.6.26 - I think it is > triggered by Debian's scripts bringing the interface up rather than when > the module loads. > > I will try to isolate the exact commit which fixes this issue. Did you narrow this down or test whether the commit below fixes the problem? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=3c4dc7115dfdb9e0450b7a3b0649948f5356d4af Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509628: marked as done (kernel 2.6.18 usb capabilities hang up after plugging in Nokia 6110 Navigator)
Your message dated Sun, 26 Jul 2009 15:15:22 +0200 with message-id <20090726131521.ga20...@galadriel.inutil.org> and subject line Re: kernel 2.6.18 usb capabilities hang up after plugging in Nokia 6110 Navigator has caused the Debian Bug report #509628, regarding kernel 2.6.18 usb capabilities hang up after plugging in Nokia 6110 Navigator 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 ow...@bugs.debian.org immediately.) -- 509628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image 2.6.18-6-686 Version: 2.6.18.dfsg.1-23etch1 After I plug in my Nokia 6110 Navigator into USB the kernel log gets filled with the following: Dec 24 00:43:59 4150 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2 Dec 24 00:43:59 4150 kernel: usb 1-1: configuration #1 chosen from 1 choice Dec 24 00:44:03 4150 kernel: cdc_acm 1-1:1.8: ttyACM0: USB ACM device Dec 24 00:44:03 4150 kernel: usbcore: registered new driver cdc_acm Dec 24 00:44:03 4150 kernel: drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters Dec 24 00:44:03 4150 kernel: usbcore: registered new driver cdc_ether Dec 24 00:44:03 4150 kernel: rndis_host 1-1:1.10: RNDIS init failed, -32 Dec 24 00:44:03 4150 kernel: usb%%d: unregister 'rndis_host' usb-:00:07.2-1, RNDIS device Dec 24 00:44:03 4150 kernel: unregister_netdevice: device usb%%d/df9fa800 never was registered Dec 24 00:44:03 4150 kernel: [ cut here ] Dec 24 00:44:03 4150 kernel: kernel BUG at mm/slab.c:595! Dec 24 00:44:03 4150 kernel: invalid opcode: [#1] Dec 24 00:44:03 4150 kernel: SMP Dec 24 00:44:03 4150 kernel: Modules linked in: rndis_host cdc_ether usbnet cdc_acm button ac battery ipv6 ext3 jbd mbcache dm_snapshot dm_mirror dm_mod loop snd_es1968 gameport snd_ac97_codec snd_ac97_bus xirc2ps_cs snd_pcm_oss snd_mixer_oss snd_pcm serial_cs snd_page_alloc snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_timer tsdev snd_rawmidi snd_seq_device irda crc_ccitt snd soundcore pcmcia firmware_class floppy rtc shpchp radio_maestro psmouse serio_raw compat_ioctl32 i2c_piix4 pcspkr videodev v4l1_compat v4l2_common intel_agp agpgart i2c_core pci_hotplug yenta_socket rsrc_nonstatic pcmcia_core evdev reiserfs ide_cd cdrom ide_disk uhci_hcd usbcore piix generic ide_core thermal processor fan Dec 24 00:44:03 4150 kernel: CPU:0 Dec 24 00:44:03 4150 kernel: EIP:0060:[]Not tainted VLI Dec 24 00:44:03 4150 kernel: EFLAGS: 00010006 (2.6.18-6-686 #1) Dec 24 00:44:03 4150 kernel: EIP is at kfree+0x2e/0x65 Dec 24 00:44:03 4150 kernel: eax: 8001006c ebx: df9faac0 ecx: c40e47a0 edx: c13f3e80 Dec 24 00:44:03 4150 kernel: esi: 0282 edi: df9f4392 ebp: df9fa800 esp: d8447e18 Dec 24 00:44:03 4150 kernel: ds: 007b es: 007b ss: 0068 Dec 24 00:44:03 4150 kernel: Process modprobe (pid: 6942, ti=d8446000 task=df261aa0 task.ti=d8446000) Dec 24 00:44:03 4150 kernel: Stack: df9faac0 e0cab60e df9fa806 e0cab01a c972ce00 e0caf6a0 d58da228 d0437c00 Dec 24 00:44:03 4150 kernel:ffe0 c40c7e00 0001 0001 0001 0001 Dec 24 00:44:03 4150 kernel:e0caf660 c972ce00 e0cb0520 e0cb0550 c02110c8 e089cba5 c972ce14 c972ce14 Dec 24 00:44:03 4150 kernel: Call Trace: Dec 24 00:44:03 4150 kernel: [] usbnet_probe+0x4ee/0x503 [usbnet] Dec 24 00:44:03 4150 kernel: [] __driver_attach+0x0/0x5d Dec 24 00:44:03 4150 kernel: [] usb_probe_interface+0x58/0x87 [usbcore] Dec 24 00:44:03 4150 kernel: [] driver_probe_device+0x42/0x8b Dec 24 00:44:03 4150 kernel: [] __driver_attach+0x38/0x5d Dec 24 00:44:03 4150 kernel: [] bus_for_each_dev+0x33/0x55 Dec 24 00:44:03 4150 kernel: [] driver_attach+0x11/0x13 Dec 24 00:44:03 4150 kernel: [] __driver_attach+0x0/0x5d Dec 24 00:44:03 4150 kernel: [] bus_add_driver+0x64/0xfd Dec 24 00:44:03 4150 kernel: [] usb_register_driver+0x60/0xbb [usbcore] Dec 24 00:44:03 4150 kernel: [] sys_init_module+0x16c3/0x1846 Dec 24 00:44:03 4150 kernel: [] journal_end+0xad/0xb2 [reiserfs] Dec 24 00:44:03 4150 kernel: [] syscall_call+0x7/0xb Dec 24 00:44:03 4150 kernel: Code: 56 89 c7 53 74 58 9c 5e fa 8d 90 00 00 00 40 c1 ea 0c c1 e2 05 03 15 70 f3 36 c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 <0f> 0b 53 02 81 b0 29 c0 89 e0 8b 4a 18 25 00 e0 ff ff 8b 40 10 Dec 24 00:44:03 4150 kernel: EIP: [] kfree+0x2e/0x65 SS:ESP 0068:d8447e18 Sometimes the modem in the cell phone works after plugging in, sometimes does not but the bug in
Bug#506644: [Pkg-utopia-maintainers] Bug#506644: gnome-power-manager: Brightness applet does not change brightness
On Sat, Dec 06, 2008 at 12:01:15PM +0900, Charles Plessy wrote: > Le Fri, Dec 05, 2008 at 04:20:07PM +0100, Josselin Mouette a écrit : > > Indeed, the kernel support seems broken. I can change the values > > in /sys/class/backlight/acpi_video0/brightness but they have no impact > > on the brightness. > > > > Charles, setting "xrandr --output LVDS --set BACKLIGHT_CONTROL native" > > should make at least xbacklight work, but for HAL which relies on the > > ACPI interface, this is up to the kernel. > > Thanks a lot everybody for your help. > > Interestingly, on my machine both methods work. Did this change in more recent kernels? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#500834: need more information
On Sat, Jan 03, 2009 at 03:44:50PM -0800, Peter Farkas wrote: > Hello Bastian and Moritz, >Sorry for not responding more promptly, I was too busy with > various other things. Today I wanted to test the fix. However, > I am not that familiar with finding and testing kernels, so > after about an hour of trying to find the necessary information, > I gave up. >I would be happy to test the new kernel, but in order to do > it I need to know where to get it from, and how to install it. >Regards, The kernel mentioned by Bastian is the kernel from the current Debian stable (version 5.0 aka Lenny). Your report was filed against the previous release, so this would involve a system update. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499307: dpkg information as requsted
On Thu, Sep 18, 2008 at 05:45:44PM +0100, Aimee Daniells wrote: > $ dpkg -l linux-image-2.6.26-1-686 > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name VersionDescription > +++-==-==- > ii linux-image-2. 2.6.26-4 Linux 2.6.26 image on > PPro/Celeron/PII/PIII/ Does the error still occur with more recent kernels? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516150: more information
On Thu, Feb 19, 2009 at 05:47:55PM +0100, Bastian Blank wrote: > Please provide more information: > - uname -a > - the complete kernel log (dmesg) > - cat /sys/devices/system/clocksource/clocksource0/* Dimitri, can you provide the mentioned information? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521548: linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels
On Thu, Apr 02, 2009 at 09:42:58PM +0200, Fathi Boudra wrote: > > please report upstream on bugzilla.kernel.org and let us know the bug > > number. you d have to add 2.6.29 dmesg and lscpi -vv output there. > > Dunno if it can help to understand the issue but I noticed the machine boots > in single. > > As I understand: > - the kernel boots > - we are in userspace and we go through runlevels. > > I see services starting (I guess we are at runlevel 2) then the fans go crazy. > > So, it seems caused by a userspace daemon or a module loaded later in the > boot > process ? > > reminder: the laptop works fine with kernel 2.6.26 Does this still occur with 2.6.30? If so, can you pin down which init script triggers the failure? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512083: libsensors3: Troubles with CPU FAN speed control
On Sat, Jan 17, 2009 at 02:50:45AM +0300, Ilia Lilov wrote: > > I have the next troubles with CPU FAN speed control on my notebook. I had no > CPU FAN speed control (cooler works on full speed all the time) on GNU/Linux > at all about a > year, but on MS Windows XP FAN speed control was nice. I thinked my Linux > "can't see" how to control FAN speed. Few days ago I tried to use "Sleep > mode". It works fine. > But when I boot my notebook from sleep mode... FAN speed control started to > work fine! I checked this effect some times and result was the same. > I understand, that some more information about my hardware are needed, but I > don't know what exactly I should to send. Say me, what information I should > to send or what > command output line I should to send. Now I can say, that almost all chips > manufactured by VIA company: north and south bridges, network card, sound > card, and even CPU > (VIA C7-M, 1500MHz). And I think some confusion with terms is possible: In my > language modes called "Sleeping mode" and "Waiting mode" (I sayd about > sleeping one), but I > not sure how they are called in English. > Sorry for terreble English. > Best regards, Ilia. Does this error persist with 2.6.30 from unstable? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521778: regression: errors from dvd drive
On Mon, Mar 30, 2009 at 12:06:05AM -0400, Jerry Quinn wrote: > Package: linux-image-2.6.29-1-amd64 > Version: 2.6.29-1 > Severity: normal > > > I just upgraded to 2.6.29-1 and rebooted, then found tons of errors like: > > Mar 29 20:32:20 cerberus kernel: [8.247470] sr 0:0:0:1: [sr0] Unhandled > sense code > Mar 29 20:32:20 cerberus kernel: [8.247472] sr 0:0:0:1: [sr0] Result: > hostbyte=DID_ERROR driverbyte=DRIVER_SENSE,SUGGEST_RETRY > Mar 29 20:32:20 cerberus kernel: [8.247475] sr 0:0:0:1: [sr0] Sense Key : > No Sense [current] > Mar 29 20:32:20 cerberus kernel: [8.247478] sr 0:0:0:1: [sr0] Add. Sense: > No additional sense information > Mar 29 20:32:20 cerberus kernel: [8.247481] end_request: I/O error, dev > sr0, sector 196592 > > in my kernel log. Does this message still appear with 2.6.30 from unstable? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#471910: marked as done (kernel-2.6: kernel BUG at include/linux/mm.h:300!)
Your message dated Sun, 26 Jul 2009 14:37:38 +0200 with message-id <20090726123738.ga28...@galadriel.inutil.org> and subject line Re: kernel-2.6: kernel BUG at include/linux/mm.h:300! has caused the Debian Bug report #471910, regarding kernel-2.6: kernel BUG at include/linux/mm.h:300! 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 ow...@bugs.debian.org immediately.) -- 471910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel-2.6 Version: linux-image-2.6 Severity: normal So when I plug in my Sweex USB, do nothing, and then take it out it prints the following. Other times (when I actually try to use it) it crashes my system. ro...@tribbin:~$ lsusb Bus 004 Device 001: ID : Bus 005 Device 001: ID : Bus 003 Device 002: ID 04f9:0027 Brother Industries, Ltd Bus 003 Device 001: ID : Bus 001 Device 008: ID 0c45:6009 Microdia Bus 001 Device 006: ID 046d:c30e Logitech, Inc. Bus 001 Device 007: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver Bus 001 Device 002: ID 152d:2339 Bus 001 Device 005: ID 05e3:0606 Genesys Logic, Inc. Bus 001 Device 003: ID 04a9:221c Canon, Inc. Bus 001 Device 001: ID : Bus 002 Device 001: ID : ro...@tribbin:~$ Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: [ cut here ] Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: kernel BUG at mm/slab.c:595! Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: invalid opcode: [#1] Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: SMP Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: CPU:0 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: EIP is at kfree+0x2e/0x65 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: eax: 8400 ebx: cdde9fc0 ecx: c02cd56c edx: c102c780 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: esi: 0286 edi: c163c400 ebp: 0001 esp: f7d83c20 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: ds: 007b es: 007b ss: 0068 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: Process hald-addon-stor (pid: 2711, ti=f7d82000 task=dff67000 ta sk.ti=f7d82000) Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: Stack: cdde9fc0 c9d04b40 f4e2d4b8 c015e3eb cdde9fc0 c015e8c5 000 c 0001 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel:fff2 0001 e80ce078 0bb9db6c f7d83d50 c01 add7e c01b1661 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel:e80ce0f4 dfdb2380 dfd8fba0 c9d04b40 000a 00011000 f88 de305 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: Call Trace: Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: Code: 56 89 c7 53 74 58 9c 5e fa 8d 90 00 00 00 40 c1 ea 0c c1 e 2 05 03 15 70 f3 36 c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 <0f> 0b 5 3 02 81 b0 29 c0 89 e0 8b 4a 18 25 00 e0 ff ff 8b 40 10 Message from sysl...@tribbin at Fri Mar 21 00:12:26 2008 ... tribbin kernel: EIP: [] kfree+0x2e/0x65 SS:ESP 0068:f7d83c20 ro...@tribbin:~$ lsusb Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: kernel BUG at include/linux/mm.h:300! Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: invalid opcode: [#2] Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: SMP Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: CPU:1 Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: EIP is at put_page+0x17/0x32 Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: eax: ebx: 0001 ecx: 0292 edx: 081c2870 Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: esi: c44f5d40 edi: f73e05e0 ebp: f73e0580 esp: f6763de4 Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: ds: 007b es: 007b ss: 0068 Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: Process gnome-settings- (pid: 4150, ti=f6762000 task=dfbb5550 task.ti=f6762000) Message from sysl...@tribbin at Fri Mar 21 00:12:48 2008 ... tribbin kernel: Stack: c0225179 c44f5d40 c44f5d40 c0224f97 01a0 c027528a f6763eb4 f78d3ac0
Bug#515125: general: cpu frequency scalling crashes my system
On Thu, Feb 19, 2009 at 10:07:23AM +1100, Hamish Moffatt wrote: > On Fri, Feb 13, 2009 at 08:13:45PM +0100, Mark Poks wrote: > > i am not sure what exacly causes the problem. it maight be cpufreq, or > > kernel > > or maybe something else (or CPU Frequency Scalling Monitor applet in GNOME > > which is rather in doubt). > > > > when enabled "AMD Quiet'n'cool" in BIOS (the CPU frequency scalling) and > > have > > installed CPUFreq package, it very often happens that system crashes > > totally. > > Hi Mark, > > I had similar problems with my AMD64 system. Whenever frequency scaling > was enabled the machine would crash within a few hours of operation, > even when it was idle. The kernel would oops a few times before finally > locking up. > > I also saw video and database corruption, but generally the system was > stable. > > The problem was a BIOS bug. It started when I increased my system RAM to > 4 DIMMs. The CPU (AMD64 939 pin x2 4800) can't handle 4 DIMMs at the > full speed of 400MHz; the BIOS is supposed to automatically slow the RAM > down to 333MHz in this case, but that didn't work on my Gigabyte K8NS > Ultra 939. I slowed the RAM down manually and the system is now > perfectly stable. > > Maybe something like this is happening to you too. Memory tests did not > show any fault by the way. Mark, does the issue still manifest itself with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#511846: netatalk: kernel panic after package update to 2.0.3-11+lenny1 amd64
On Wed, Jan 14, 2009 at 10:19:03PM +, Vladimir Komendantsky wrote: > > > > Netatalk interacts with the kernel through the Linux module "appletalk" > > provided by the Linux kernel, so I believe that kernel panics would be > > a bug in the Linux kernel package, so reassigning. > > > > I'd like to point out that the module restart triggered by the update didn't > bring the system to a crash. This only happened after I restarted the > computer. Did it repeatedly bring down the machine or a single time? Can you still run netatalk on this system? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#443780: marked as done (zd1211rw: can't connect in 2.6.22-2-686 (regression from 2.6.22-1-686))
Your message dated Sun, 26 Jul 2009 14:01:27 +0200 with message-id <20090726120127.ga31...@galadriel.inutil.org> and subject line Re: zd1211rw: can't connect in 2.6.22-2-686 (regression from 2.6.22-1-686) has caused the Debian Bug report #443780, regarding zd1211rw: can't connect in 2.6.22-2-686 (regression from 2.6.22-1-686) 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 ow...@bugs.debian.org immediately.) -- 443780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: normal I tried upgrading from 2.6.22-1-686 to 2.6.22-2-686 (both packages are installed on my system) and suddenly my wireless adapter can not seem to connect to the access point. Some messages I see in my logs: Sep 23 22:07:24 boomtime kernel: zd1211rw 3-2:1.0: firmware version 4605 Sep 23 22:07:24 boomtime kernel: zd1211rw 3-2:1.0: zd1211 chip 0ace:1211 v4330 h igh 00-0e-2e AL2230_RF pa0 - Sep 23 22:07:24 boomtime kernel: zd1211rw 3-2:1.0: eth1 Sep 23 22:07:24 boomtime kernel: udev: renamed network interface eth1 to wlan0 Sep 23 22:07:25 boomtime kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 23 22:07:42 boomtime kernel: zd1211rw 3-2:1.0: error ioread32(CR_REG1): -11 Sep 23 22:07:42 boomtime kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready On some other attepts to connect the device I got: Sep 23 22:07:42 boomtime kernel: zd1211rw 3-2:1.0: error ioread32(CR_REG1): -22 (instead of -11) I have not tried previous kernel versions, as I used the external zd1211 before. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core) Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.22-2-686 depends on: ii initramfs-tools [linux-initr 0.91a tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.22-2-686 recommends: ii libc6-i6862.6.1-5GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.22-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.22-2-686/prerm/would-invalidate-boot-loader-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/elilo-initrd-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/abort-overwrite-2.6.22-2-686: linux-image-2.6.22-2-686/preinst/lilo-initrd-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/depmod-error-initrd-2.6.22-2-686: false linux-image-2.6.22-2-686/preinst/overwriting-modules-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/failed-to-move-modules-2.6.22-2-686: linux-image-2.6.22-2-686/preinst/bootloader-initrd-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/create-kimage-link-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/bootloader-error-2.6.22-2-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.22-2-686/postinst/kimage-is-a-directory: linux-image-2.6.22-2-686/postinst/old-dir-initrd-link-2.6.22-2-686: true linux-image-2.6.22-2-686/prerm/removing-running-kernel-2.6.22-2-686: true linux-image-2.6.22-2-686/preinst/initrd-2.6.22-2-686: linux-image-2.6.22-2-686/postinst/depmod-error-2.6.22-2-686: false linux-image-2.6.22-2-686/preinst/already-running-this-2.6.22-2-686: linux-image-2.6.22-2-686/postinst/old-initrd-link-2.6.22-2-686: true linux-image-2.6.22-2-686/postinst/bootloader-test-error-2.6.22-2-686: linux-image-2.6.22-2-686/preinst/abort-install-2.6.22-2-686: linux-image-2.6.22-2-686/postinst/old-system-map-link-2.6.22-2-686: true -- Tzafrir Cohen tzaf...@technion.ac.il http://www.technion.ac.il/~tzafrir --- End Message --- --- Begin Message --- On Wed, Nov 12, 2008 at 01:48:34AM +0100, Moritz Muehlenhoff wrote: > On Mon, Sep 24, 2007 at 05:44:52AM +0200, Tzafrir Cohen wrote: > > Package: linux-image-2.6.22-2-686 > > Version: 2.6.22-4 > > Severity: normal > > > > I tried upgrading from 2.6.22-1-686 to 2.6.22-2-686 (both packages are > > installed on my system) and suddenly my wireless adapter can not seem to > > connect to the access point. > > Does this error still persist with the current 2.6.26 kernel from Lenny? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#443526: marked as done (linux-image-2.6.22: ACPI Wakeup interface change between 2.6.21 and 2.6.22)
Your message dated Sun, 26 Jul 2009 13:57:35 +0200 with message-id <20090726115735.ga19...@galadriel.inutil.org> and subject line Re: linux-image-2.6.22: ACPI Wakeup interface change between 2.6.21 and 2.6.22 has caused the Debian Bug report #443526, regarding linux-image-2.6.22: ACPI Wakeup interface change between 2.6.21 and 2.6.22 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 ow...@bugs.debian.org immediately.) -- 443526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.22-1-amd64 Version: 2.6.22-3 Severity: normal File: linux-image-2.6.22 The /proc/acpi/alarm interface was obsoleted. The new interface for ACPI wakeup is /sys/class/rtc/rtcX/wakealarm, but it requires enabling a kernel config option. Here is the thread about the interface change: http://lkml.org/lkml/2007/6/19/264 This problem is hitting other distro as well: https://bugzilla.novell.com/show_bug.cgi?id=287539 I will keep my MythTV DVR on 2.6.21 in the meantime. -- Package-specific info: ** Version: Linux version 2.6.22-1-amd64 (Debian 2.6.22-3) (wa...@debian.org) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Sun Jul 29 13:54:41 UTC 2007 ** Not tainted ** Kernel log: ohci_hcd :00:02.0: OHCI Host Controller ohci_hcd :00:02.0: new USB bus registered, assigned bus number 1 ohci_hcd :00:02.0: irq 23, io mem 0xf0102000 SCSI subsystem initialized libata version 2.21 loaded. usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 10 ports detected forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx pnp: the driver 'ide' has been registered NFORCE-CK804: IDE controller at PCI slot :00:06.0 NFORCE-CK804: chipset revision 162 NFORCE-CK804: not 100% native mode: will probe irqs later NFORCE-CK804: BIOS didn't set cable bits correctly. Enabling workaround. NFORCE-CK804: BIOS didn't set cable bits correctly. Enabling workaround. NFORCE-CK804: :00:06.0 (rev a2) UDMA133 controller ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA Probing IDE interface ide0... Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 hda: SAMSUNG SP1614N, ATA DISK drive usb 1-2: new full speed USB device using ohci_hcd and address 2 usb 1-2: configuration #1 chosen from 1 choice usb 1-10: new low speed USB device using ohci_hcd and address 3 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... usb 1-10: configuration #1 chosen from 1 choice usbcore: registered new interface driver hiddev input: Logitech USB Receiver as /class/input/input0 input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-:00:02.0-10 input: Logitech USB Receiver as /class/input/input1 input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-:00:02.0-10 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver hdc: HL-DT-ST DVDRAM GSA-4160B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22 ACPI: PCI Interrupt :00:0a.0[A] -> Link [APCH] -> GSI 22 (level, low) -> IRQ 22 PCI: Setting latency timer of device :00:0a.0 to 64 forcedeth: using HIGHDMA eth0: forcedeth.c: subsystem: 01458:e000 bound to :00:0a.0 ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 ACPI: PCI Interrupt :01:0a.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18 firewire_ohci: Added fw-ohci device :01:0a.0, OHCI version 1.10 hda: max request size: 512KiB hda: Host Protected Area detected. current capacity is 312579695 sectors (160040 MB) native capacity is 312581808 sectors (160041 MB) hda: Host Protected Area disabled. hda: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100) hda: cache flushes supported hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 > hdc: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(66) Uniform CD-ROM driver Revision: 3.20 firewire_core: created new fw device fw0 (0 config rom retries) Attempting manual resume ReiserFS: hda8: found reiserfs format "3.6" with standard journal ReiserFS: hda8: using ordered data mode ReiserFS: hda8: journal params: device hda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda8: checking transaction log (hda8) ReiserFS: hda8:
Bug#423248: linux-image-2.6.18-4-486: [r8169] drops received TCP packets when using jumbo frames
On Sun, Nov 30, 2008 at 09:51:22AM +0100, Josselin Mouette wrote: > Le samedi 29 novembre 2008 à 02:33 +0100, Moritz Muehlenhoff a écrit : > > > It is a regression from 2.6.18.dfsg.1-8, and I think it is related to > > > the r8169 changes introduced in -9, as the network controller is a > > > D-Link DGE-528T using this driver. > > > > Does this error still occur with more recent kernel versions? > > > > If that machine still runs Etch, could you try to reproduce this bug > > with the 2.6.24 based kernel added in 4.0r4? > > I???m not using this controller anymore, but I still have it. I???ll be able > to check with the lenny kernel in a few days, but probably not with the > etch kernel. Joss, have you been able to test this in the mean time? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#421780: linux-image-2.6.18-4-686: Kernel with ACPI + SMP + AC power plugged on sony vaio S4M really slow
On Mon, Jun 08, 2009 at 08:46:44PM -0400, Mark T.B. Carroll wrote: > This looks a bit like a problem I've been having with 2.6.29-4 built > from Debian's Linux source package. My SMP system can slow down a lot > when the AC adaptor is plugged in. kacpid and kacpi_notify get very busy > and when I type letters get missed. I enclose my kernel config and an > extract from a minute's fussing in kern.log in case they help. > > I apologize if I am mistaken about the relevance of the enclosed. Is this still reprocible with 2.6.30? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#423082: marked as done (linux-image-2.6.18-4-686: Problem with Belkin USB 2.0 Notebook Card in Toshiba 4000CDS.)
Your message dated Sun, 26 Jul 2009 11:55:21 +0200 with message-id <20090726095521.ga16...@galadriel.inutil.org> and subject line Re: Belkin USB 2.0 Notebook Card has caused the Debian Bug report #423082, regarding linux-image-2.6.18-4-686: Problem with Belkin USB 2.0 Notebook Card in Toshiba 4000CDS. 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 ow...@bugs.debian.org immediately.) -- 423082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12 Severity: normal Subject: linux-image-2.6.18-4-686: Problem with Belkin USB 2.0 Notebook Card in Toshiba 4000CDS. Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12 Severity: normal *** Please type your report below this line *** I have a Belkin USB 2.0 Notebook Card, part F5U222v1, in a Toshiba 4000CDS laptop. An Altec-Lansing USB headset plugged into the Notebook Card, is not recognized by alsa. When connected to the built-in USB port, the headset is recognized automatically. If the Belkin USB Ethernet adapter is plugged into the Notebook Card, FTP does not work properly. If the USB Ethernet adapter is plugged into the built-in USB port, communication is normal. This appears to be a problem with a PCMCIA, Cardbus or USB driver. If you want more specific information, just let me know. My apologies if this report is not submitted correctly. If there is a better package to target, please let me know. Thanks, ... Peter Easthope peasthope at cablelan.net -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-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.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: pn libc6-i686 (no description available) -- 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 shared/kernel-image/really-run-bootloader: 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/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/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/preinst/initrd-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true 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: --- End Message --- --- Begin Message --- On Wed, Dec 17, 2008 at 11:02:52PM +0100, Moritz Muehlenhoff wrote: > > I have a Belkin USB 2.0 Notebook Card, part F5U222v1, > > in a Toshiba 4000CDS laptop. > > > > An Altec-Lansing USB headset plugged into the > > Notebook Card, is not recognized by alsa. When > > connected to the built-in USB port, the headset > > is recognized automatically. > > > > If the Belkin USB Ethernet adapter is plugged into > > the Notebook Card, FTP does not work properly. > > If the USB Ethernet adapter is plugged into the > > built-in USB port, communication is normal. > > > > This appears to be a problem with a PCMCIA, > > Cardbus or USB driver. If you want more specific > > information, just let me know. > >
Bug#423084: marked as done (maxmem parameter apparently ignored)
Your message dated Sun, 26 Jul 2009 11:56:18 +0200 with message-id <20090726095618.ga22...@galadriel.inutil.org> and subject line Re: maxmem parameter apparently ignored has caused the Debian Bug report #423084, regarding maxmem parameter apparently ignored 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 ow...@bugs.debian.org immediately.) -- 423084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xen-linux-system-2.6.20-1-xen-amd64 Version: 2.6.20-3 The maxmem parameter in Xen config files does not work, that is, regardless of the use of that setting, domU can never be ballooned to a value greater than the value set in the memory field. -- Tom Allen Email: tal...@10east.com Senior Open Systems EngineerPhone: 904-220-3627 10East Corp FAX: 904-384-1038 --- End Message --- --- Begin Message --- On Sat, Nov 29, 2008 at 02:32:19AM +0100, Moritz Muehlenhoff wrote: > On Wed, May 09, 2007 at 12:45:43PM -0400, Tom Allen wrote: > > Package: xen-linux-system-2.6.20-1-xen-amd64 > > Version: 2.6.20-3 > > > > The maxmem parameter in Xen config files does not work, that is, > > regardless of the use of that setting, domU can never be ballooned to a > > value greater than the value set in the memory field. > > Does this error still occur with more recent kernel/Xen versions, such > as the ones from Lenny? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#422675: marked as done (sis900: tons of corrupted packets are reported)
Your message dated Sun, 26 Jul 2009 11:48:50 +0200 with message-id <20090726094850.ga2...@galadriel.inutil.org> and subject line Re: Bug still occurs in 2.6.26 has caused the Debian Bug report #422675, regarding sis900: tons of corrupted packets are reported 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 ow...@bugs.debian.org immediately.) -- 422675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-4-k7 Version: 2.6.18.dfsg.1-12etch1 Severity: normal While tracking down some rsync trouble I found this error/waring message appears 4-5 times every second: May 6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x908401b8/440. May 6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x90880187/391. May 6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x90840143/323. May 6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x90880134/308. May 6 06:28:28 vargas kernel: eth0: Corrupted packet received, buffer status = 0x9084019e/414. As you see the numbers at the end vary, but I see no close relation to the amount of traffic trough the interface. If it is related to my network problem isn't sure yet, but it creates 18MB of logfile a day. I had no such messages with it previous kernel version (before the latest security update). The NIC is reported to be a 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) the mii module is loaded aswell. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Versions of packages linux-image-2.6.18-4-k7 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-k7 recommends: ii libc6-i686 2.3.6.ds1-13 GNU C Library: Shared libraries [i -- debconf information excluded --- End Message --- --- Begin Message --- On Sun, Dec 07, 2008 at 05:28:52PM +0100, Moritz Muehlenhoff wrote: > On Sun, Nov 30, 2008 at 05:51:09PM +, Chris Carr wrote: > > I have recently found this problem on an old socket 7 machine with an > > SiS900 network card. The lspci output for the card is > > > > 00:0b.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI > > Fast Ethernet (rev 02) > > > > The motherboard is a PC Chips (Hsin Tech) M537DMA33: > > > > http://www.users.zetnet.co.uk/thorfin/motherboards/mb01/motherboard_1.htm > > > > Kernel is 2.6.26 from the Lenny RC1 installer. > > > > I'm afraid I don't know how to troubleshoot this bug. For example, > > earlier messages mention setting the card to half-duplex mode - should I > > try that, and if so how is it done? > > You can use "mii-tools -F" from net-tools for that. > > Could you try to reproduce this with a current 2.6.28-rcX kernel (you can use > the Debian > config from /boot/config* ) and file a bug at bugzilla.kernel.org if the > problem > persists? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#425960: marked as done (initramfs-tools: prep ppc root= not present)
Your message dated Sun, 26 Jul 2009 11:59:43 +0200 with message-id <20090726095943.ga4...@galadriel.inutil.org> and subject line Re: Bug#425960: initramfs-tools: prep ppc root= not present has caused the Debian Bug report #425960, regarding initramfs-tools: prep ppc root= not present 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 ow...@bugs.debian.org immediately.) -- 425960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.87b Severity: normal I do use my own daily kernels on PReP PPC machine but occassionally test debian kernels to make sure debian is installabale here. linux-image-2.6.21-1-prep mostly works here but can not boot automatically. It can not find root since ROOT= empty. Debian kernels are compiled with no builtin cmdline for root= and initramfs does not contain the value either so I have to boot the kernel by hand, providing root=/dev/sda3 in boot stub. This seems to be a initramfs-tools defect. -- Package-specific info: -- /proc/cmdline console=ttyS0,9600 console=tty0 root=/dev/sda3 -- /proc/filesystems ext3 -- lsmod Module Size Used by appletalk 36316 20 iptable_nat 7364 1 nf_nat 17652 1 iptable_nat nf_conntrack_ipv4 18092 2 iptable_nat nf_conntrack 64460 3 iptable_nat,nf_nat,nf_conntrack_ipv4 nfnetlink 6552 3 nf_nat,nf_conntrack_ipv4,nf_conntrack ip_tables 12296 1 iptable_nat x_tables 14308 2 iptable_nat,ip_tables dm_snapshot19728 0 dm_mirror 24372 0 dm_mod 63868 2 dm_snapshot,dm_mirror ipv6 319236 20 serio_raw 6884 0 pata_sl82c105 6688 0 sata_sil 10120 1 libata115100 2 pata_sl82c105,sata_sil evdev 11392 0 -- /etc/kernel-img.conf do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = yes -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.21 Locale: LANG=et_EE.ISO-8859-15, LC_CTYPE=et_EE.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii busybox 1:1.1.3-4 Tiny utilities for small and embed ii cpio 2.7-3 GNU cpio -- a program to manage ar ii klibc-utils 1.5-2 small statically-linked utilities ii module-init-tools3.3-pre11-1 tools for managing Linux kernel mo ii udev 0.105-4 /dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- On Sun, May 27, 2007 at 01:57:55AM +0200, maximilian attems wrote: > On Fri, 25 May 2007, Meelis Roos wrote: > > > I do use my own daily kernels on PReP PPC machine but occassionally test > > debian kernels to make sure debian is installabale here. > > linux-image-2.6.21-1-prep mostly works here but can not boot > > automatically. It can not find root since ROOT= empty. Debian kernels > > are compiled with no builtin cmdline for root= and initramfs does not > > contain the value either so I have to boot the kernel by hand, providing > > root=/dev/sda3 in boot stub. This seems to be a initramfs-tools > > defect. > > prep bootloader seems pretty archic if he can pass any values > to the cmdline of the kernel. > > aboves failure is expected, the best would be that the prep > linux-image postinst takes care to set a proper ROOT hardcoding > in /etc/initramfs-tools/conf.d/root. > > but currently i read prep got disabled due to other brokeness, > no idea if there is enough porter interest for that specific flavour. prep was disabled for 2.6.22, closing the bug. Cheers, Moritz --- End Message ---
Bug#421896: marked as done (linux-image-2.6.18-4-686: cpufreq-info reports wrong frequency for 2nd core)
Your message dated Sun, 26 Jul 2009 11:52:08 +0200 with message-id <20090726095208.ga12...@galadriel.inutil.org> and subject line Re: linux-image-2.6.18-4-686: cpufreq-info reports wrong frequency for 2nd core has caused the Debian Bug report #421896, regarding linux-image-2.6.18-4-686: cpufreq-info reports wrong frequency for 2nd core 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 ow...@bugs.debian.org immediately.) -- 421896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12 Severity: normal Modules: speedstep-centrino, cpufreq-ondemand The frequency cpufreq-info reports conflicting info for the frequency of the second core: -f switch (normal user): always shows max frequency -w switch (root only): shows frequency matching the first core For the first core the frequencies match regardless of the query method. Regards, C. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.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.13 Debian configuration management sy ii initramfs-tools [linux-initra 0.87b 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: 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/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/postinst/depmod-error-2.6.18-4-686: false shared/kernel-image/really-run-bootloader: 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/abort-install-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/bootloader-error-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/prerm/removing-running-kernel-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/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/initrd-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/create-kimage-link-2.6.18-4-686: true 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: -- cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz stepping: 6 cpu MHz : 1596.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm bogomips: 4791.28 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz stepping: 6 cpu MHz : 1596.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss h
Bug#528028: marked as done (BUG: Bad page state in process md?_resync pfn:)
Your message dated Sun, 26 Jul 2009 10:37:20 +0200 with message-id <20090726083720.ga13...@galadriel.inutil.org> and subject line Re: BUG: Bad page state in process md?_resync pfn: has caused the Debian Bug report #528028, regarding BUG: Bad page state in process md?_resync pfn: 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 ow...@bugs.debian.org immediately.) -- 528028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.29-1-686 Version: 2.6.29-3 Justification: breaks the whole system Severity: critical I wonder if this is the same thing Neil Brown refers to, here: http://www.spinics.net/lists/raid/msg23053.html The syslog shows first 97 of these: , | May 10 02:10:05 kernel: [107468.160593] BUG: Bad page state in process md9_resync pfn:36243 | May 10 02:10:05 kernel: [107468.160602] page:c16c4860 flags:4000 count:-1 mapcount:0 mapping:(null) index:24 | May 10 02:10:05 kernel: [107468.160610] Pid: 31239, comm: md9_resync Tainted: PB 2.6.29-1-686 #1 | May 10 02:10:05 kernel: [107468.160614] Call Trace: | May 10 02:10:05 kernel: [107468.160626] [] bad_page+0xc6/0xda | May 10 02:10:05 kernel: [107468.160633] [] get_page_from_freelist+0x31b/0x3f3 | May 10 02:10:05 kernel: [107468.160641] [] __alloc_pages_internal+0x98/0x398 | May 10 02:10:05 kernel: [107468.160676] [] r1buf_pool_alloc+0x8f/0x164 [raid1] | May 10 02:10:05 kernel: [107468.160684] [] mempool_alloc+0x27/0xcb | May 10 02:10:05 kernel: [107468.160691] [] bio_add_page+0x28/0x2e | May 10 02:10:05 kernel: [107468.160707] [] sync_request+0x1fd/0x5ee [raid1] | May 10 02:10:05 kernel: [107468.160739] [] md_do_sync+0x6d4/0xb60 [md_mod] | May 10 02:10:05 kernel: [107468.160753] [] autoremove_wake_function+0x0/0x2d | May 10 02:10:05 kernel: [107468.160775] [] md_thread+0xdd/0xf4 [md_mod] | May 10 02:10:05 kernel: [107468.160796] [] md_thread+0x0/0xf4 [md_mod] | May 10 02:10:05 kernel: [107468.160803] [] kthread+0x38/0x5d | May 10 02:10:05 kernel: [107468.160808] [] kthread+0x0/0x5d | May 10 02:10:05 kernel: [107468.160815] [] kernel_thread_helper+0x7/0x10 ` and then continues and alternates with 81 of these: , | May 10 02:10:14 kernel: [107477.308920] BUG: Bad page state in process find pfn:04322 | May 10 02:10:14 kernel: [107477.308928] page:c1086440 flags:4000 count:-1 mapcount:0 mapping:(null) index:1 | May 10 02:10:14 kernel: [107477.308933] Pid: 32146, comm: find Tainted: P B 2.6.29-1-686 #1 | May 10 02:10:14 kernel: [107477.308937] Call Trace: | May 10 02:10:14 kernel: [107477.308946] [] bad_page+0xc6/0xda | May 10 02:10:14 kernel: [107477.308952] [] get_page_from_freelist+0x31b/0x3f3 | May 10 02:10:14 kernel: [107477.308957] [] __alloc_pages_internal+0x98/0x398 | May 10 02:10:14 kernel: [107477.308962] [] find_or_create_page+0x3e/0x76 | May 10 02:10:14 kernel: [107477.308968] [] __getblk+0x137/0x2df | May 10 02:10:14 kernel: [107477.308973] [] ll_rw_block+0xb5/0xc6 | May 10 02:10:14 kernel: [107477.309013] [] search_by_key+0x69/0x560 [reiserfs] | May 10 02:10:14 kernel: [107477.309036] [] search_by_key+0x454/0x560 [reiserfs] | May 10 02:10:14 kernel: [107477.309042] [] __find_get_block+0x168/0x172 | May 10 02:10:14 kernel: [107477.309047] [] __alloc_pages_internal+0x98/0x398 | May 10 02:10:14 kernel: [107477.309052] [] __getblk+0x27/0x2df | May 10 02:10:14 kernel: [107477.309073] [] reiserfs_read_locked_inode+0x64/0x50e [reiserfs] | May 10 02:10:14 kernel: [107477.309093] [] search_by_entry_key+0x14/0x184 [reiserfs] | May 10 02:10:14 kernel: [107477.309114] [] make_cpu_key+0x1c/0x38 [reiserfs] | May 10 02:10:14 kernel: [107477.309134] [] reiserfs_init_locked_inode+0x0/0xe [reiserfs] | May 10 02:10:14 kernel: [107477.309154] [] reiserfs_iget+0x47/0x78 [reiserfs] | May 10 02:10:14 kernel: [107477.309173] [] reiserfs_lookup+0xa7/0xf6 [reiserfs] | May 10 02:10:14 kernel: [107477.309188] [] do_lookup+0xa6/0x116 | May 10 02:10:14 kernel: [107477.309193] [] __link_path_walk+0x523/0x630 | May 10 02:10:14 kernel: [107477.309198] [] mntput_no_expire+0x1a/0xfe | May 10 02:10:14 kernel: [107477.309203] [] dput+0x1a/0x108 | May 10 02:10:14 kernel: [107477.309207] [] path_walk+0x4f/0xa3 | May 10 02:10:14 kernel: [107477.309212] [] do_path_lookup+0x132/0x178 | May 10 02:10:14 kernel: [107477.309216] [] getname+0x5e/0xb0 | May 10 02:10:14 kernel: [107477.309221] [] user_path_at+0x37/0x5f | May 10 02:10:14 kernel: [107477.309227] [] vfs_lstat_fd+0x12/0x38 | May 10 02:10:14 kernel: [107
Bug#528028: BUG: Bad page state in process md?_resync pfn:
On Sun, 19 Jul 2009, Moritz Muehlenhoff wrote: > On Sun, May 10, 2009 at 02:25:14PM +0200, Cristian Ionescu-Idbohrn wrote: > > Package: linux-image-2.6.29-1-686 > > Version: 2.6.29-3 > > Justification: breaks the whole system > > Severity: critical > > > > I wonder if this is the same thing Neil Brown refers to, here: > > > > http://www.spinics.net/lists/raid/msg23053.html > > The referenced patch was merged into 2.6.30. Can you confirm that this > problem has been solved in the current kernel from unstable? Confirmed. Been using 2.6.30 for a week, did a mdadm check too. Problem seems to be solved. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
