Bug#542116: linux-image-2.6.30-1-amd64: media players sometimes fail to open audio device
2009/9/8 Ben Hutchings b...@decadent.org.uk: Please cc 542...@bugs.debian.org on all mail concerning this bug report. On Mon, 2009-08-24 at 10:23 +0200, Michal Suchanek wrote: 2009/8/23 Ben Hutchings b...@decadent.org.uk: On Tue, 2009-08-18 at 08:33 +0200, Michal Suchanek wrote: 2009/8/18 Ben Hutchings b...@decadent.org.uk: On Mon, 2009-08-17 at 23:46 +0200, Michal Suchanek wrote: Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-3.local Severity: normal Media players sometimes fail to open the audio device saying that the device is busy. Which specific media players are you using? mplayer and vlc Since re-running the player (or skipping to the next item in playlist) resolves the problem I don't think this is really the case. I am running a rebuild of 2.6.30-3 because I needed the vmlinux image. Are you running esd or any other software mixer? No. Next to nothing works with these. Which sound driver were you using, or which sound chip do you have? I guess it's snd-hda-intel - here is it's message when it loads: HDA Intel :00:1b.0: PCI INT A - GSI 19 (level, low) - IRQ 19 This is what oss says about the chip: 1: oss_hdaudio0 Intel HD Audio interrupts=55013 (55013) HD Audio controller Intel HD Audio Vendor ID 0x808627d8 Subvendor ID 0x10438249 Codec 0: ALC883 (0x10ec0883/0x1043c603) Please try snd-hda-intel again, and send a copy of the kernel log from after you see the 'device is busy' error. I don't think there's any message. It does not happen always, only once in ~10 attempts to reopen the device I will try to reproduce this and see if there is anything in the recent log. Thanks Michal -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535331:
I am sorry, but I'm afraid my previous analysis in this bug report is
completely wrong.
The kernel image maintainer scripts are not supposed to run lilo
directly. They trigger an initramfs update, and that should in turn
cause lilo to run after it's finished. The initramfs update must do
this regardless of why it was run, and having the kernel scripts run
lilo would therefore be useless.
And now for the weird stuff: This did suddenly work for me with the
2.6.26-19 upgrade. I got:
Setting up linux-image-2.6.26-2-686 (2.6.26-19) ...
Running depmod.
Running mkinitramfs-kpkg.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.26-17lenny2 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.26-17lenny2 was configured last, according to dpkg)
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.26-2-686
Added Linux *
Added LinuxOLD
But I cannot understand what may have changed. My /etc/kernel-img.conf
is still and has always been:
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
do_initrd = Yes
do_bootloader = yes
And initramfs-tools have not been upgraded since the last time this
failed according to the dpkg log. But the dpkg log above shows
something very interesting: This time I got a status triggers-pending
initramfs-tools 0.92o which I did not see on the previous kernel image
upgrade:
adler:/tmp# egrep 'linux-image|initramfs-tools' /var/log/dpkg.log{.1,}
/var/log/dpkg.log.1:2009-08-15 01:00:40 upgrade linux-image-2.6.26-2-686
2.6.26-17lenny1 2.6.26-17lenny2
/var/log/dpkg.log.1:2009-08-15 01:00:40 status half-configured
linux-image-2.6.26-2-686 2.6.26-17lenny1
/var/log/dpkg.log.1:2009-08-15 01:00:41 status unpacked
linux-image-2.6.26-2-686 2.6.26-17lenny1
/var/log/dpkg.log.1:2009-08-15 01:00:41 status half-installed
linux-image-2.6.26-2-686 2.6.26-17lenny1
/var/log/dpkg.log.1:2009-08-15 01:00:47 status half-installed
linux-image-2.6.26-2-686 2.6.26-17lenny1
/var/log/dpkg.log.1:2009-08-15 01:00:49 status unpacked
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log.1:2009-08-15 01:00:49 status unpacked
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log.1:2009-08-15 01:00:53 configure linux-image-2.6.26-2-686
2.6.26-17lenny2 2.6.26-17lenny2
/var/log/dpkg.log.1:2009-08-15 01:00:53 status unpacked
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log.1:2009-08-15 01:00:53 status half-configured
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log.1:2009-08-15 01:01:27 status installed
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log:2009-09-06 01:00:53 upgrade linux-image-2.6.26-2-686
2.6.26-17lenny2 2.6.26-19
/var/log/dpkg.log:2009-09-06 01:00:53 status half-configured
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log:2009-09-06 01:00:55 status unpacked linux-image-2.6.26-2-686
2.6.26-17lenny2
/var/log/dpkg.log:2009-09-06 01:00:55 status half-installed
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log:2009-09-06 01:01:07 status half-installed
linux-image-2.6.26-2-686 2.6.26-17lenny2
/var/log/dpkg.log:2009-09-06 01:01:09 status unpacked linux-image-2.6.26-2-686
2.6.26-19
/var/log/dpkg.log:2009-09-06 01:01:09 status unpacked linux-image-2.6.26-2-686
2.6.26-19
/var/log/dpkg.log:2009-09-06 01:01:26 configure linux-image-2.6.26-2-686
2.6.26-19 2.6.26-19
/var/log/dpkg.log:2009-09-06 01:01:26 status unpacked linux-image-2.6.26-2-686
2.6.26-19
/var/log/dpkg.log:2009-09-06 01:01:27 status half-configured
linux-image-2.6.26-2-686 2.6.26-19
/var/log/dpkg.log:2009-09-06 01:02:02 status installed linux-image-2.6.26-2-686
2.6.26-19
/var/log/dpkg.log:2009-09-06 01:02:03 status triggers-pending initramfs-tools
0.92o
/var/log/dpkg.log:2009-09-06 01:02:08 trigproc initramfs-tools 0.92o 0.92o
/var/log/dpkg.log:2009-09-06 01:02:08 status half-configured initramfs-tools
0.92o
/var/log/dpkg.log:2009-09-06 01:02:55 status installed initramfs-tools 0.92o
Why? Or rather: Why doesn't it always do that?
Bjørn
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541169: linux-image-2.6.30-1-amd64 : sis190 driver doesn't work with Ethernet Adpator
Hello, I had some difficulties to find a 2.6.31. The wiki gives the address : http://kernel-archive.buildserver.net/debian-kernel but the server seems to be down. After a lot of googling, I found linux-image-2.6.31-4-rt_2.6.31-4.4_amd64.deb at http://au.archive.ubuntu.com/ubuntu/pool/universe/l/linux-rt/?C=S;O=A Is there another server for experimental kernel ? I installed the upper one with dpkg -i, and I could ping my dhcp server :-) p...@cosidlvm~% uname -a Linux cosidlvm 2.6.31-4-rt #4-Ubuntu SMP PREEMPT RT Sat Aug 29 05:02:32 UTC 2009 x86_64 GNU/Linux p...@cosidlvm~% sudo dhclient eth2 Internet Systems Consortium DHCP Client V3.1.2p1 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth2/00:23:54:32:10:07 Sending on LPF/eth2/00:23:54:32:10:07 Sending on Socket/fallback DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 15 DHCPOFFER from 192.168.9.1 DHCPREQUEST on eth2 to 255.255.255.255 port 67 DHCPACK from 192.168.9.1 bound to 192.168.9.50 -- renewal in 228 seconds. p...@cosidlvm~% ping 192.168.9.1 PING 192.168.9.1 (192.168.9.1) 56(84) bytes of data. 64 bytes from 192.168.9.1: icmp_seq=1 ttl=64 time=0.309 ms 64 bytes from 192.168.9.1: icmp_seq=2 ttl=64 time=0.230 ms 64 bytes from 192.168.9.1: icmp_seq=3 ttl=64 time=0.219 ms 64 bytes from 192.168.9.1: icmp_seq=4 ttl=64 time=0.215 ms 64 bytes from 192.168.9.1: icmp_seq=5 ttl=64 time=0.220 ms 64 bytes from 192.168.9.1: icmp_seq=6 ttl=64 time=0.217 ms ^C --- 192.168.9.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5000ms rtt min/avg/max/mdev = 0.215/0.235/0.309/0.033 ms I connected to the server through ssh too. It worked all right, but I had a system freeze after a few minutes (5-10). I'll experiment further and let you know. Thank you for your messages. -- Pierre Meurisse -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516374: INFO: task * blocked for more than 120 seconds. in numerous non-SCHED_IDLE workloads
Hi, Quoting Ben Hutchings b...@decadent.org.uk: This is not exactly a crash, though I realise the effects are often just as bad as a crash. Yep, that's not really a crash. It can take some hours for the host to be unresponsive due to the high load average (ssh, local login down). It's like the system is waiting for the file system. Please send the kernel logs showing the blocked for more than 120 seconds messages and the following function call traces. I will post it as soon as one of my hosts hangs. I do not know yet how to reproduce this bug on command. Regards. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
looking for kernel-maintainer
Dear maintainers, sorry to write here, but at the moment it is not possible, to register or send bugreports to bugzilla.kernel.org. Seems the mailsystem is completely down. So I even cannot send the message, that the mailservice is down, too. I hope, that one of the kernel-maintainers might read this message here and will have a look on this. The bugreport I want to send, is about the kernel-module ath5k, which is now maintained by the kernel-maintainers themselves. Where can I send it, if not to bugzilla.kernel.org? Please inform the kernel-maintainers of their problem, when you know one! Thank you very much! Hans-J. Ullrich -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: looking for kernel-maintainer
Please don't cross-post to many lists. debian-kernel would have been sufficient. On Tue, 2009-09-08 at 10:39 +0200, Hans-J. Ullrich wrote: Dear maintainers, sorry to write here, but at the moment it is not possible, to register or send bugreports to bugzilla.kernel.org. Seems the mailsystem is completely down. So I even cannot send the message, that the mailservice is down, too. I hope, that one of the kernel-maintainers might read this message here and will have a look on this. The bugreport I want to send, is about the kernel-module ath5k, which is now maintained by the kernel-maintainers themselves. Where can I send it, if not to bugzilla.kernel.org? Please inform the kernel-maintainers of their problem, when you know one! You can find this out from the MAINTAINERS file in the kernel source tree. It is also packaged in the linux-doc-$version packages. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp signature.asc Description: This is a digitally signed message part
Re: looking for kernel-maintainer
Hello, On Tue, Sep 08, 2009 at 10:39:58AM +0200, Hans-J. Ullrich wrote: Dear maintainers, sorry to write here, but at the moment it is not possible, to register or send bugreports to bugzilla.kernel.org. Seems the mailsystem is completely down. So I even cannot send the message, that the mailservice is down, too. I hope, that one of the kernel-maintainers might read this message here and will have a look on this. The bugreport I want to send, is about the kernel-module ath5k, which is now maintained by the kernel-maintainers themselves. Where can I send it, if not to bugzilla.kernel.org? Please inform the kernel-maintainers of their problem, when you know one! Report it to linux-ker...@vger.kernel.org. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions| http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: looking for kernel-maintainer
hello, please do not cross-post to unrelated lists. the upstream development list is linux-ker...@vger.kernel.org On Tue, Sep 08, 2009 at 10:39:58AM +0200, Hans-J. Ullrich wrote: sorry to write here, but at the moment it is not possible, to register or send bugreports to bugzilla.kernel.org. i could just easily login to aboves bugzilla with my account, retry. Seems the mailsystem is completely down. So I even cannot send the message, that the mailservice is down, too. I hope, that one of the kernel-maintainers might read this message here and will have a look on this. The bugreport I want to send, is about the kernel-module ath5k, which is now maintained by the kernel-maintainers themselves. Where can I send it, if not to bugzilla.kernel.org? Please inform the kernel-maintainers of their problem, when you know one! Thank you very much! ath5k had an active dev phase be sure to test a recent kernel at least 2.6.30 kind regards maximilian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545377: marked as done (linux-2.6: Screen flickers on 915GM)
Your message dated Tue, 08 Sep 2009 14:14:13 +0200 with message-id 1252412053.5440.5.ca...@zoe.varbacka and subject line Re: linux-2.6: Screen flickers on 915GM has caused the Debian Bug report #545377, regarding linux-2.6: Screen flickers on 915GM 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.) -- 545377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: important Tags: patch Hi, With Linux 2.6.31, some 915GM-based systems like the Eee PC 4G suffers from screen flickering in X. There's a simple patch available to fix this, but it wasn't merged in time. Could you please apply it for the debian package? Patch: http://lists.freedesktop.org/archives/intel-gfx/2009-August/003995.html Upstream bug: http://bugs.freedesktop.org/show_bug.cgi?id=23368 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.31-rc9-custom (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- The changes made it for 2.6.31 as commit bcc24fb42585dc9f490cf7789a917358414bdab5. Closing the bug. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part ---End Message---
Re: looking for kernel-maintainer
On Tuesday 08 September 2009, Hans-J. Ullrich wrote: Dear maintainers, sorry to write here, but at the moment it is not possible, to register or send bugreports to bugzilla.kernel.org. Seems the mailsystem is completely down. So I even cannot send the message, that the mailservice is down, too. I hope, that one of the kernel-maintainers might read this message here and will have a look on this. The bugreport I want to send, is about the kernel-module ath5k, which is now maintained by the kernel-maintainers themselves. Where can I send it, if not to bugzilla.kernel.org? Please inform the kernel-maintainers of their problem, when you know one! Thank you very much! Hans-J. Ullrich You could try the ath5k development list:- ath5k-de...@lists.ath5k.org That is where all the development of the ath5k driver is done, and where all the experts live. But there is a lot of development going on so it would be as well to be on a current kernel (2.6.30) in order to have a sensible discussion with them. David -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544710: More info on the './etc/modprobe.d/arch-aliases.conf: Cannot stat: No such file or directory' problem
Hi, FYI, I had the same problem when upgrading my box today. Looking inside /etc/modprobe.d/, I saw that arch-aliases.conf was a symlink to arch/i386, which didn't exist. Since I never created that file, I guess that there's a problem with some other package that left that dangling symlink there, and which causes update-initramfs to fail. After removing arch-aliases.conf I could finish the upgrade successfully. -- Antonio Terceiro terce...@softwarelivre.org http://softwarelivre.org/terceiro signature.asc Description: Digital signature
Bug#545728: initramfs-tools(8) missing import instruction in boot script example
Package: initramfs-tools Version: 0.93.4 Severity: normal Tags: patch We need to import /scripts/functions in a boot script for use critic, log_begin_msg and log_end_msg functions but it's not show in the manpage. -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.30-1-amd64 root=UUID=6782d1b5-0fe1-4bf3-b5ea-bad4d75667e7 ro quiet -- /proc/filesystems ext4 ext4dev fuseblk -- lsmod Module Size Used by vboxnetflt 89340 1 vboxdrv 1693436 2 vboxnetflt radeon141984 4 drm 172688 5 radeon ppdev 7784 0 lp 10612 0 parport38224 2 ppdev,lp powernow_k814084 1 cpufreq_userspace 3652 0 cpufreq_stats 4660 0 cpufreq_conservative 7928 0 cpufreq_powersave 1792 0 binfmt_misc 9292 1 fuse 54784 3 loop 15980 0 firewire_sbp2 15424 0 dm_crypt 12984 0 dm_mod 59384 1 dm_crypt snd_hda_codec_realtek 250260 1 sn9c102 140980 0 videodev 36768 1 sn9c102 v4l1_compat12932 1 videodev v4l2_compat_ioctl32 9312 1 videodev snd_hda_intel 26680 6 snd_hda_codec 75248 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 8152 1 snd_hda_codec snd_pcm_oss37200 0 snd_mixer_oss 15072 1 snd_pcm_oss snd_pcm78504 5 snd_hda_intel,snd_hda_codec,snd_pcm_oss pcspkr 2800 0 evdev 10448 14 snd_timer 21824 1 snd_pcm psmouse42172 0 serio_raw 5844 0 snd63912 18 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 7984 1 snd snd_page_alloc 1 2 snd_hda_intel,snd_pcm k8temp 5152 0 i2c_piix4 11040 0 i2c_core 25456 2 drm,i2c_piix4 asus_atk01107744 0 button 6512 0 shpchp 32588 0 processor 40160 1 powernow_k8 pci_hotplug29040 1 shpchp ext4 216256 2 mbcache 8804 1 ext4 jbd2 58816 1 ext4 crc16 2272 1 ext4 usbhid 37328 0 hid41376 1 usbhid ide_cd_mod 29048 0 sd_mod 33720 4 crc_t10dif 2096 1 sd_mod cdrom 34344 1 ide_cd_mod ide_pci_generic 4964 0 ata_generic 5924 0 ahci 36480 3 firewire_ohci 22356 0 firewire_core 44996 2 firewire_sbp2,firewire_ohci crc_itu_t 2720 1 firewire_core ohci_hcd 22812 0 r8169 32548 0 mii 5600 1 r8169 atiixp 4292 0 libata175500 2 ata_generic,ahci scsi_mod 158784 3 firewire_sbp2,sd_mod,libata ehci_hcd 33820 0 ide_core 105120 3 ide_cd_mod,ide_pci_generic,atiixp thermal15936 0 fan 5240 0 thermal_sys16448 3 processor,thermal,fan uvesafb26680 0 cn 9020 1 uvesafb -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- /etc/crypttab # target name source device key file options -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-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/dash Versions of packages initramfs-tools depends on: ii cpio 2.10-1 GNU cpio -- a program to manage ar ii findutils 4.4.2-1utilities for finding files--find, ii klibc-utils 1.5.15-1 small utilities built with klibc f ii module-init-tools 3.10-3 tools for managing Linux kernel mo ii udev 146-1 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.14.2-2 Tiny utilities for small and embed initramfs-tools 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#415068: I can reproduce #415068 on a UltraSparc 5 over USB serial adapter
On Sat, Jul 18, 2009 at 12:32:00AM +0200, Moritz Muehlenhoff wrote: On Wed, Dec 12, 2007 at 09:58:43PM +0100, Axel Beckert wrote: found 415068 2.6.18.dfsg.1-13etch5 found 415068 2.6.18.dfsg.1-13etch4 thanks Hi, I'm currently investigating an UltraSparc 5 which didn't come up after the recent kernel update from 2.6.18.dfsg.1-13etch4 to 2.6.18.dfsg.1-13etch5, but it booted without problems after being moved to the office for investigation. It initially had not serial console configured, but now has /dev/ttyS1 with 9600 8N1. (So this bug is probably not responsible for the initial hang on reboot because of which I started investigating the machine.) I tried to connect over one of these ugly USB to serial adapters. (Also to test the adapter since I will need it if I don't want to carry the Sparc to the office again next time.) And while experimenting a little bit with the baud rates (9600 8N1 as configured and expected on the Sparc lost about every third character), I suddenly got a kernel panic on the VGA monitor (which I connected because the machine stopped pinging). I can reproduce this kernel panic with the following command on the laptop with the USB to serial adapter connected to ttyS1 on the Sparc: screen /dev/ttyUSB0 2400,cs8EnterEnter If I keep the screen running while rebooting, just typing a single Enter into the screen, the box panics. Here's a (manual!) transcript of the Sparc's output: Does this error still occur with the Lenny kernel? Do you still own such a 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#356090: kernel: Can't access PCMCIA card adapter
On Sun, Sep 21, 2008 at 07:43:47PM +0200, Vincent Lefevre wrote: There's something wrong with one of the drivers: On 2008-09-21 19:31:45 +0200, Vincent Lefevre wrote: I've tried with another 1-GB card, a microSD this time (with a microSD to SD adapter between the PCMCIA adapter and the memory card), and I get the following errors: [...] Sep 21 19:18:11 ay kernel: [43576.901343] hdg: 1984000 sectors (1015 MB) w/1KiB Cache, CHS=1968/16/63 [...] However, if I try the same microSD card with a USB adapter, on the same machine, I have no problems: [...] Sep 21 19:19:42 ay kernel: [43589.167567] sd 0:0:0:0: [sda] 1984000 512-byte hardware sectors (1016 MB) [...] Same number of sectors, but not the same number of MB's! Or perhaps they're rounding the value 1015.808 inconsistently. Does this still occur with later 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#387668: rlimit
On Fri, Sep 15, 2006 at 11:11:10PM +0200, Benoît Dejean wrote: getrlimit nice gives me rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY on ppc. I have never touched these settings. I assume these are system default settings which have changed to unexpected and dangerous values (should be 0 i guess). Does this 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#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error xlog_valid_rec_header(2)
On Tue, 2009-09-01 at 19:17 +, Moritz Muehlenhoff wrote: Does this still occur with later kernels, such as 2.6.30 from unstable or backports.org? Yes, it still shows up in 2.6.30-bpo.1-parisc64 from backports.org: [ 282.992000] XFS mounting filesystem dm-2 [ 283.148000] Starting XFS recovery on filesystem: dm-2 (logdev: internal) [ 283.176000] Filesystem dm-2: XFS internal error xlog_valid_rec_header(2) at line 3466 of file /build/buildd/linux-2.6-2.6.30/debian/ build/source_hppa_none/fs/xfs/xfs_log_recover.c. Caller 0x00f132a4 [ 283.176000] [ 283.192000] Backtrace: [ 283.196000] [40116cb4] show_stack+0x14/0x20 [ 283.204000] [40111200] dump_stack+0x18/0x28 [ 283.208000] [00ef5534] xfs_error_report+0x54/0x90 [xfs] [ 283.216000] [00f0fb48] xlog_valid_rec_header+0xe8/0x150 [xfs] [ 283.22] [00f132a4] xlog_do_recovery_pass+0xd4/0x798 [xfs] [ 283.224000] [00f139c4] xlog_do_log_recovery+0x5c/0x190 [xfs] [ 283.232000] [00f13b1c] xlog_do_recover+0x24/0x1d0 [xfs] [ 283.236000] [00f15498] xlog_recover+0xb0/0xe8 [xfs] [ 283.244000] [00f0cf2c] xfs_log_mount+0x11c/0x1f8 [xfs] [ 283.248000] [00f17ef0] xfs_mountfs+0x418/0x830 [xfs] [ 283.256000] [00f39d94] xfs_fs_fill_super+0x224/0x558 [xfs] [ 283.26] [401be328] get_sb_bdev+0x1a0/0x238 [ 283.264000] [00f36868] xfs_fs_get_sb+0x20/0x70 [xfs] [ 283.272000] [401bdd0c] vfs_kern_mount+0xe4/0x1d8 [ 283.276000] [401bde90] do_kern_mount+0x68/0x148 [ 283.284000] [401d9624] do_mount+0x884/0x910 [ 283.288000] [ 283.292000] XFS: log mount/recovery failed: error 177 [ 283.30] XFS: log mount failed -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#406902: kernel NFS data loss
On Wed, Sep 19, 2007 at 08:17:12AM +1000, Paul Szabo wrote: On 24 Jul 07 I wrote: The patch below (against 2.6.8-16sarge7) seems to solve the problem. ... [patch for fs/exportfs/expfs.c] ... Seems to me that this has been incorporated (or done) in linux-source-2.6.18.dfsg.1-13etch2 . Earlier, on 20 Jul 07 I wrote: ... I noticed what I thought were oddities. ... Do you think the following patch against 2.6.8-16sarge7 code would be useful? ... [patch for fs/nfs/dir.c] ... That does not seem to have been added to linux-source-2.6.18.dfsg.1-13etch2 . I am still not quite sure what needs lock_kernel(), and anyway my patch did not actually solve anything, so that might be OK. Can you give us a status update please? Is this fixed upstream in the mean time? If not, did you submit your patches and was there any feedback? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error xlog_valid_rec_header(2)
On Tue, Sep 08, 2009 at 02:21:38PM -0600, Stillwell, Bryan wrote: On Tue, 2009-09-01 at 19:17 +, Moritz Muehlenhoff wrote: Does this still occur with later kernels, such as 2.6.30 from unstable or backports.org? Yes, it still shows up in 2.6.30-bpo.1-parisc64 from backports.org: [ 282.992000] XFS mounting filesystem dm-2 [ 283.148000] Starting XFS recovery on filesystem: dm-2 (logdev: internal) [ 283.176000] Filesystem dm-2: XFS internal error xlog_valid_rec_header(2) at line 3466 of file /build/buildd/linux-2.6-2.6.30/debian/ build/source_hppa_none/fs/xfs/xfs_log_recover.c. Caller 0x00f132a4 [ 283.176000] [ 283.192000] Backtrace: [ 283.196000] [40116cb4] show_stack+0x14/0x20 [ 283.204000] [40111200] dump_stack+0x18/0x28 [ 283.208000] [00ef5534] xfs_error_report+0x54/0x90 [xfs] [ 283.216000] [00f0fb48] xlog_valid_rec_header+0xe8/0x150 [xfs] [ 283.22] [00f132a4] xlog_do_recovery_pass+0xd4/0x798 [xfs] [ 283.224000] [00f139c4] xlog_do_log_recovery+0x5c/0x190 [xfs] [ 283.232000] [00f13b1c] xlog_do_recover+0x24/0x1d0 [xfs] [ 283.236000] [00f15498] xlog_recover+0xb0/0xe8 [xfs] [ 283.244000] [00f0cf2c] xfs_log_mount+0x11c/0x1f8 [xfs] [ 283.248000] [00f17ef0] xfs_mountfs+0x418/0x830 [xfs] [ 283.256000] [00f39d94] xfs_fs_fill_super+0x224/0x558 [xfs] [ 283.26] [401be328] get_sb_bdev+0x1a0/0x238 [ 283.264000] [00f36868] xfs_fs_get_sb+0x20/0x70 [xfs] [ 283.272000] [401bdd0c] vfs_kern_mount+0xe4/0x1d8 [ 283.276000] [401bde90] do_kern_mount+0x68/0x148 [ 283.284000] [401d9624] do_mount+0x884/0x910 [ 283.288000] [ 283.292000] XFS: log mount/recovery failed: error 177 [ 283.30] XFS: log mount failed Adding debian-hppa in the loop: Is this a known issue and specific to hppa? (Since otherwise I would suppose there were earlier reports from the more widely used archs). Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#467291: marked as done (ide-scsi module not compiled into production kernel 2.6.18-6-686)
Your message dated Tue, 8 Sep 2009 22:50:47 +0200 with message-id 20090908205047.ga19...@galadriel.inutil.org and subject line Re: ide-scsi module not compiled into production kernel 2.6.18-6-686 has caused the Debian Bug report #467291, regarding ide-scsi module not compiled into production kernel 2.6.18-6-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.) -- 467291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel Severity: important The ide-scsi module is not compiled into the production kernel. Whilst Linus may deprecate it for CD-burning, it is absolutely essential for IDE tape drives, because ide-tape is flaky, and has been unmaintained for years (Primarily bug 327355 appears to have remained unresolved, but there are other problems). Please make this module avalable in future kernels. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England ---End Message--- ---BeginMessage--- On Mon, Jul 27, 2009 at 11:42:45PM +0200, Moritz Muehlenhoff wrote: On Sun, Feb 24, 2008 at 01:44:25PM +, Tony van der Hoff wrote: Package: kernel Severity: important The ide-scsi module is not compiled into the production kernel. Whilst Linus may deprecate it for CD-burning, it is absolutely essential for IDE tape drives, because ide-tape is flaky, and has been unmaintained for years (Primarily bug 327355 appears to have remained unresolved, but there are other problems). Please make this module avalable in future kernels. ide-tape has seen lots of commits over the recent year. Are their specific problems not yet addressed? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz ---End Message---
Bug#451805: linux-image-2.6.22-3-r4k-ip22 dies early on boot / Starting ELF64 kernel
On Fri, Jul 31, 2009 at 07:05:16AM +0200, Martin Michlmayr wrote: * Moritz Muehlenhoff j...@inutil.org [2009-07-30 22:16]: That's strange because I booted a kernel just fine when I added the patches to 2.6.22-6. I'll test the .deb tomorrow. What is the status of this bug, does it still apply to Lenny? I think the bottom line is that we don't support SGI machines with very old revision CPUs in Debian; the remaining issues discussed in the bug report should be fixed now. I suggest we close the bug report bug I'd like to hear comments from Flo first. Florian? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[Fwd: Packaging Linux BoF has been accepted for LPC 2009]
Forwarded Message From: Darrick J. Wong djw...@us.ibm.com Reply-to: djw...@us.ibm.com To: b...@decadent.org.uk Subject: Packaging Linux BoF has been accepted for LPC 2009 Date: Tue, 8 Sep 2009 12:55:54 -0700 Hi, I'm Darrick Wong, the BoF session organizer for LPC 2009. Your BoF proposal, Packaging Linux, has been accepted at the conference. I've tentatively scheduled you for Wednesday, September 23rd between 1:30-2:30pm in Salon D, which holds about 90 people. Let me know if the time and room are acceptable; if not, there are smaller rooms that hold about 40 people and are available all day and night, and it may be possible to reshuffle the larger rooms. Thank you and I hope that you enjoy LPC 2009! --Darrick signature.asc Description: This is a digitally signed message part
Bug#462229: linux-image-2.6.26-1-686: Additional info and still occuring
On Sat, Feb 07, 2009 at 09:25:12PM +, Ben Whyte wrote:
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13
Followup-For: Bug #462229
While doing disk rights I can achieve the following
Feb 7 20:51:46 thor kernel: [ 1303.442451] sd 1:0:0:0: [sda] 1953523055
512-byte hardware sectors (1000204 MB)
Feb 7 20:51:46 thor kernel: [ 1303.442451] sd 1:0:0:0: [sda] Write Protect
is off
Feb 7 20:51:46 thor kernel: [ 1303.442451] sd 1:0:0:0: [sda] Mode Sense: 00
3a 00 00
Feb 7 20:51:46 thor kernel: [ 1303.442451] sd 1:0:0:0: [sda] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 21:01:54 thor smartd[2596]: Device: /dev/sda, SMART Usage Attribute:
194 Temperature_Celsius changed from 127 to 119
Feb 7 21:07:58 thor kernel: [ 2327.706181] ata2.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x6 frozen
Feb 7 21:07:58 thor kernel: [ 2327.706198] ata2.00: cmd
35/00:e0:5f:68:6b/00:03:03:00:00/e0 tag 0 dma 507904 out
Feb 7 21:07:58 thor kernel: [ 2327.706203] res
40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 7 21:07:58 thor kernel: [ 2327.706208] ata2.00: status: { DRDY }
Feb 7 21:07:58 thor kernel: [ 2327.706227] ata2: soft resetting link
Feb 7 21:07:58 thor kernel: [ 2328.346026] ata2.00: configured for UDMA/133
Feb 7 21:07:58 thor kernel: [ 2328.346026] ata2: EH complete
Feb 7 21:07:58 thor kernel: [ 2328.352930] sd 1:0:0:0: [sda] 1953523055
512-byte hardware sectors (1000204 MB)
Feb 7 21:07:58 thor kernel: [ 2328.361407] sd 1:0:0:0: [sda] Write Protect
is off
Feb 7 21:07:58 thor kernel: [ 2328.361414] Feb 7 21:16:32 thor kernel: [
2894.903319] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x6 frozen
Feb 7 21:16:32 thor kernel: [ 2894.903336] ata2.00: cmd
c8/00:08:0f:44:f4/00:00:00:00:00/e0 tag 0 dma 4096 in
Feb 7 21:16:32 thor kernel: [ 2894.903340] res
40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 7 21:16:32 thor kernel: [ 2894.903346] ata2.00: status: { DRDY }
Feb 7 21:16:32 thor kernel: [ 2894.903364] ata2: soft resetting link
Feb 7 21:16:32 thor kernel: [ 2895.679600] ata2.00: configured for UDMA/133
Feb 7 21:16:32 thor kernel: [ 2895.679600] ata2: EH complete
Feb 7 21:16:32 thor kernel: [ 2895.691278] sd 1:0:0:0: [sda] 1953523055
512-byte hardware sectors (1000204 MB)
Feb 7 21:16:32 thor kernel: [ 2895.691278] sd 1:0:0:0: [sda] Write Protect
is off
Feb 7 21:16:32 thor kernel: [ 2895.691278] sd 1:0:0:0: [sda] Mode Sense: 00
3a 00 00
Feb 7 21:16:32 thor kernel: [ 2895.691278] sd 1:0:0:0: [sda] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 21:17:03 thor kernel: [ 2927.477266] ata2.00: limiting speed to
UDMA/100:PIO4
Feb 7 21:17:03 thor kernel: [ 2927.477277] ata2.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x6 frozen
Feb 7 21:17:03 thor kernel: [ 2927.477289] ata2.00: cmd
ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 7 21:17:03 thor kernel: [ 2927.477293] res
40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 7 21:17:03 thor kernel: [ 2927.477298] ata2.00: status: { DRDY }
Feb 7 21:17:03 thor kernel: [ 2927.477316] ata2: soft resetting link
Feb 7 21:17:03 thor kernel: [ 2928.141432] ata2.00: configured for UDMA/100
Feb 7 21:17:03 thor kernel: [ 2928.141432] ata2: EH complete
Feb 7 21:17:03 thor kernel: [ 2928.141432] sd 1:0:0:0: [sda] 1953523055
512-byte hardware sectors (1000204 MB)
Feb 7 21:17:04 thor kernel: [ 2928.184455] end_request: I/O error, dev sda,
sector 1953519935
Feb 7 21:17:04 thor kernel: [ 2928.184455] md: super_written gets error=-5,
uptodate=0
Feb 7 21:17:04 thor kernel: [ 2928.184455] sd 1:0:0:0: [sda] Write Protect
is off
Feb 7 21:17:04 thor kernel: [ 2928.184455] sd 1:0:0:0: [sda] Mode Sense: 00
3a 00 00
Feb 7 21:17:04 thor kernel: [ 2928.208441] sd 1:0:0:0: [sda] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 21:17:04 thor /USR/SBIN/CRON[3557]: (root) CMD ( cd / run-parts
--report /etc/cron.hourly)
It is consistent across all disks, all ports, all cables. I have been seeing
this issue since june/july and it has cost me significant data
loss and forced 3 reinstalls as the OS has been terminally damaged.
I have tried turning write cache off as it has been mentioned as a pottential
fix this has not worked.
Currently effecting 2 brand new wd 1 tb green drives.
Did you try a more recent kernel than the standard Lenny kernel, e.g. a
2.6.30 kernel from backports.org?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#435054: linux-image-2.6.18-4-686: modprobe diskonchip unconditionally formatted my mtd device! :(
On Sun, Jul 29, 2007 at 12:46:51AM -0600, supaplex wrote: Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12etch2 Severity: critical Justification: causes serious data loss # modprobe diskonchip syslog: Jul 28 23:52:02 pxe1 kernel: NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ Jul 28 23:52:41 pxe1 kernel: DiskOnChip found at 0xd8000 Jul 28 23:52:41 pxe1 kernel: DiskOnChip 2000 responds to DWORD access Jul 28 23:52:41 pxe1 kernel: Detected 1 chips per floor. Jul 28 23:52:41 pxe1 kernel: NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit) Jul 28 23:52:41 pxe1 kernel: ECC error scanning DOC at 0x1 Jul 28 23:52:41 pxe1 kernel: Found DiskOnChip ANAND Media Header at 0x1 Jul 28 23:52:41 pxe1 kernel: ECC error scanning DOC at 0x14000 Jul 28 23:52:41 pxe1 kernel: Found DiskOnChip ANAND Media Header at 0x14000 Jul 28 23:52:41 pxe1 kernel: DataOrgID= ANAND Jul 28 23:52:41 pxe1 kernel: NumEraseUnits= 2044 Jul 28 23:52:41 pxe1 kernel: FirstPhysicalEUN = 4 Jul 28 23:52:41 pxe1 kernel: FormattedSize= 32768000 Jul 28 23:52:41 pxe1 kernel: UnitSizeFactor = 255 Jul 28 23:52:41 pxe1 kernel: Bad block table at page 129, version 0x55 Jul 28 23:52:41 pxe1 kernel: Bad block table at page 161, version 0x55 Jul 28 23:52:41 pxe1 kernel: Formatting block 6 Jul 28 23:52:41 pxe1 kernel: Formatting block 7 Jul 28 23:52:41 pxe1 kernel: Formatting block 8 Jul 28 23:52:41 pxe1 kernel: Formatting block 9 Jul 28 23:52:41 pxe1 kernel: Formatting block 10 Jul 28 23:52:41 pxe1 kernel: Formatting block 11 and so on... Jul 28 23:53:53 pxe1 kernel: Formatting block 2045 Jul 28 23:53:54 pxe1 kernel: Formatting block 2046 Jul 28 23:53:54 pxe1 kernel: Formatting block 2047 Jul 28 23:53:54 pxe1 kernel: nftla: unknown partition table Jul 28 23:53:54 pxe1 kernel: Creating 1 MTD partitions on DiskOnChip 2000 (NFTL Model): Jul 28 23:53:54 pxe1 kernel: 0x00018000-0x0200 : DiskOnChip BDTL partition Jul 28 23:53:54 pxe1 kernel: Found alias of DOC at 0xd8000 to 0xda000 I'd rather expect a kernel message like Failed to load ... use modprobe diskonchip format=1 to format mtd instead of it deciding on its own. My whole intention was to backup the mtd before working with it - but now it's trashed. The kernel I'm using is based on the same code+patches, but with static NFS+NIC and nfsroot support (so it'll pxeboot), otherwise it's identical to the package. (my money is on upstream anyway). Does this still occur with later kernels, such as the one from Lenny? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#488945: marked as done (km...@htwg-konstanz.de: SCSI Recovered Error - stop ext3 journal - remount read-only)
Your message dated Tue, 8 Sep 2009 22:03:39 +0200 with message-id 20090908200339.gm19...@inutil.org and subject line Re: km...@htwg-konstanz.de: SCSI Recovered Error - stop ext3 journal - remount read-only has caused the Debian Bug report #488945, regarding km...@htwg-konstanz.de: SCSI Recovered Error - stop ext3 journal - remount read-only 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.) -- 488945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12etch2 Dear debian-kernel-team, During storage maintainance a scsi error occured and stopped the ext3 journal. The setup: Debian etch/i386: Kernel: Linux homesrv 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux lsmod: nfs 202828 0 nfsd 197936 25 exportfs5600 1 nfsd lockd 54344 3 nfs,nfsd nfs_acl 3584 2 nfs,nfsd sunrpc138812 13 nfs,nfsd,lockd,nfs_acl vmmemctl 10332 0 ipv6 226016 36 quota_v28864 6 dm_snapshot15552 0 dm_mirror 19152 0 dm_mod 50232 2 dm_snapshot,dm_mirror loop 15048 0 tsdev 7520 0 i2c_piix4 8140 0 parport_pc 32132 0 parport33256 1 parport_pc intel_agp 21148 1 floppy 53156 0 shpchp 33024 0 pci_hotplug28704 1 shpchp i2c_core 19680 1 i2c_piix4 vmxnet 11712 0 agpgart29896 1 intel_agp rtc12372 0 psmouse35016 0 pcspkr 3072 0 serio_raw 6660 0 evdev 9088 0 ext3 119240 8 jbd52456 1 ext3 mbcache 8356 1 ext3 sd_mod 19040 17 ide_cd 36064 0 cdrom 32544 1 ide_cd mptspi 16136 9 mptscsih 21696 1 mptspi mptbase46176 2 mptspi,mptscsih scsi_transport_spi 22336 1 mptspi scsi_mod 124168 4 sd_mod,mptspi,mptscsih,scsi_transport_spi piix9444 0 [permanent] generic 5476 0 [permanent] ide_core 110504 3 ide_cd,piix,generic thermal13608 0 processor 28840 1 thermal fan 4804 0 cat /proc/scsi/scsi Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: SUN Model: CSM200_R Rev: 0619 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: SUN Model: CSM200_R Rev: 0619 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: SUN Model: CSM200_R Rev: 0619 Type: Direct-AccessANSI SCSI revision: 05 Host: scsi0 Channel: 00 Id: 05 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-AccessANSI SCSI revision: 02 it is running in a vmware esx 3.0.1 environment with a Sun STK 6140 storage array. During a disk change the following error is logged by the kernel: sdc: Current: sense key: Recovered Error vendor ASC=0xe0 ASCQ=0x6ASC=0xe0 ASCQ=0x6 EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 75569857 Remounting filesystem read-only I have to reboot and fsck the partition. Recovered Errors sounds like - there was an error, but the storage recovered it, by itself - so wy the ext3 failure occured? The same issue happend on a ubuntu 6.06 lts ( Kernel 2.6.16 ). All debian sarge with kernel 2.4.27 survived the scsi error. Is there a setting, to tell the kernel to retry the read or write operation? Regards, Konrad --
Bug#413990: marked as done (linux-image-2.6.18-4-686: inotify CREATE events not sent for )
Your message dated Tue, 8 Sep 2009 22:02:39 +0200 with message-id 20090908200239.gb19...@inutil.org and subject line Re: linux-image-2.6.18-4-686: inotify CREATE events not sent for ??nfs4 filesystems has caused the Debian Bug report #413990, regarding linux-image-2.6.18-4-686: inotify CREATE events not sent for 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.) -- 413990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: normal On nfs4 filesystems, inotify CREATE events are not being sent. When I touch a file, an open event is sent, and a proper event is sent when the file is removed. When I touch a file on a non-nfs4 filesystem, CREATE events occur like normal. This is confusing Nautilus, which does not display new files that are saved to Desktop (/home is nfs-4 mounted) These creations are all occuring on the local machine. I am not expecting creations from other machines to be noticed. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (99, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-4-686 recommends: pn libc6-i686none (no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- On Tue, Jul 28, 2009 at 01:31:36PM +0200, Moritz Muehlenhoff wrote: On Wed, Dec 17, 2008 at 10:23:16PM +0100, Moritz Muehlenhoff wrote: On Wed, Dec 17, 2008 at 03:17:14PM -0600, John Goerzen wrote: Moritz Muehlenhoff wrote: On Thu, Mar 08, 2007 at 07:30:11AM -0600, John Goerzen wrote: Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: normal On nfs4 filesystems, inotify CREATE events are not being sent. When I touch a file, an open event is sent, and a proper event is sent when the file is removed. When I touch a file on a non-nfs4 filesystem, CREATE events occur like normal. This is confusing Nautilus, which does not display new files that are saved to Desktop (/home is nfs-4 mounted) These creations are all occuring on the local machine. I am not expecting creations from other machines to be noticed. Does this error still occur with more recent kernel versions? What kernel version in particular would you like me to test with? 2.6.26 new enough? Ideally the current version targeted for Kenny, i.e. 2.6.26-12. Did you have a chance to test this? No further feedback, closing the bug. Please reopen if the error persists with current kernels. Cheers, Moritz ---End Message---
Driver for HP arry P410I ZM SAS array controller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I recently received 2 HP DL360 G6 with additional SAS controller HP P410i ZM (Zero memory) to interface with a HPLTO3 Library . I started Debian lenny 5.02 (2.6.26-2) but SAS controller is not detected . I know that it is detected on RHEL5 with module cciss 3.6.20-20 version of the driver while Debian module version is 3.6.20. Does a new version of this driver is available in an unstable debian kernel or can it be possible to provide kernel ports ? More information on : http://cciss.sourceforge.net/ Sources are available for Redhat and Suse, none for Debian Regards OJ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqmy6MACgkQkUrg9pTek31x2gCgr0xcNvoiOrVxIaRJAbMGYNnI EBUAnAp/zV2E33qzxwLXQmvkOdMmglv3 =NqUo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522773: Fwd: [issues] glibc uses '__unused' as identifier, which is traditionally used by BSD as macro
tags 522773 wontfix severity 522773 wishlist thanks On Wed, Jul 29, 2009 at 02:10:11PM +, Thorsten Glaser wrote: Hi package maintainers, maybe you can do such a thing during package installation? This would tremendously help porting software (liberal in what one accepts), such as NetBSD® makefs (ITP: #538171 ??? for now I worked around the issue in it). You need to get this changed upstream, we won't deviate from upstream for this. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error xlog_valid_rec_header(2)
Moritz Muehlenhoff wrote: Adding debian-hppa in the loop: Is this a known issue and specific to hppa? (Since otherwise I would suppose there were earlier reports from the more widely used archs). A quick google for xlog_valid_rec_header suggests [1] that this is neither a recent issue, nor specific to hppa. I'd suggest contacting the upstream XFS devs on this. The trace in the link looks very much alike, even though that's 2.6.27 and on arm. It's also a Debian kernel though. I did not really check any of the other hits and I also did not read the thread on this one. Cheers, FJP [1] http://lkml.org/lkml/2008/10/1/314 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#426714: marked as done (intelfb refuses mode switching)
Your message dated Tue, 8 Sep 2009 22:03:29 +0200 with message-id 20090908200329.gk19...@inutil.org and subject line Re: intelfb refuses mode switching has caused the Debian Bug report #426714, regarding intelfb refuses mode switching 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.) -- 426714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-4-686 Architecture: i386 Version: 2.6.18.dfsg.1-12etch2 intelfb fails to load on a laptop although there is no reason for this - my desktop system loads the module just fine with a LCD display. Notebook: # lspci 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Desktop: # lspci 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) Notebook's dmesg output: Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected an Intel 855 Chipset. agpgart: Detected 892K stolen memory. agpgart: AGP aperture is 128M @ 0xf000 intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets intelfb: Version 0.9.4 ACPI: PCI Interrupt :00:02.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 intelfb: 00:02.0: Intel(R) 855GME, aperture size 128MB, stolen memory 892kB intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching. intelfb: Video mode must be programmed at boot time. The module is loaded in /etc/initramfs-tools/modules on both machines with these lines: intel_agp intelfb mode=1024x768...@60 ---End Message--- ---BeginMessage--- On Fri, Aug 14, 2009 at 12:17:23AM +0200, Moritz Muehlenhoff wrote: On Mon, Dec 29, 2008 at 08:22:51PM +0100, Moritz Muehlenhoff wrote: On Mon, Dec 29, 2008 at 09:57:22AM +0100, Olaf Zaplinski wrote: Hello Moritz, I tried 2.6.24 and 2.6.26-bpo on both machines. On both machines intelfb now refuses to load with the message cannot acquire agp. /etc/initramfs-tools/modules contains: agp intel_agp intelfb mode=1024x768...@60 I added the agp module, but I do not know exactly if I need that. Could you send the output of lsmod? It might be that another framebuffer driver blocks (such as vesafb) is blocking the agp_backend_acquire() call. Has this been fixed in more recent kernels? No further feedback, closing. Please reopen if necessary. Cheers, Moritz ---End Message---
Bug#478317: marked as done (kernel: dma cannot be disabled by boot option)
Your message dated Tue, 8 Sep 2009 22:03:22 +0200 with message-id 20090908200322.gj19...@inutil.org and subject line Re: kernel: dma cannot be disabled by boot option has caused the Debian Bug report #478317, regarding kernel: dma cannot be disabled by boot option 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.) -- 478317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel Severity: normal My problem is, that dma cannot be diabled by boot prompt options. I understand, that a simple ide=nodma does not work, as these options only work on drivers included in the kernel, while ide_core is a module loaded from the initrd. Regarding the documentation, the boot option ide_core.ide=nodma should do the trick. However, it didnt work on my system. Some background information: My system had a normal harddisk and I had no problem installing etch (netinstall) on it. Then, I replaced the hard disk with an ide-to-sd converter and an sd-card (a flash disk) which cant handle dma. As a result, I was unable to boot the system, regardless of the boot option I tried (nodma ide=nodma ide0=nodma hda=nodma ide_core.ide=nodma, ...). The only way to disable dma on boot was to add an option to /etc/modprobe.d/ide and rebuild the initrd: echo 'options ide_core options=ide=nodma' /etc/modprobe.d/ide update-initramfs -u Obviously, this isnt possible on a non-bootable system. So, I had to put the working harddisk in the box again, boot, build the initrd and copy it to the sd card. After that, the system runs fine. I think this bug has been addressed many times for woody and sarge. I also found similar bug reports for etch, however, without solution. #475223: How to disable dma on the netinst CD Package: debian-installer #442333: initramfs ignores ide lernel cmd line parameters Package: live-initramfs #284425: debian-installer: A small improvement suggestion Package: rootskel Regards, Juergen Bausa -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- On Wed, Jul 29, 2009 at 07:11:36PM +0200, Moritz Muehlenhoff wrote: On Mon, Apr 28, 2008 at 09:04:54PM +0200, Juergen Bausa wrote: Package: kernel Severity: normal My problem is, that dma cannot be diabled by boot prompt options. I understand, that a simple ide=nodma does not work, as these options only work on drivers included in the kernel, while ide_core is a module loaded from the initrd. Regarding the documentation, the boot option ide_core.ide=nodma should do the trick. However, it didnt work on my system. Did you upgrade to Lenny? If so, did it work? No further feedback, closing the bug. Please reopen if the problem persists. Cheers, Moritz ---End Message---
Bug#420300: marked as done (kernel-2.6.18: MGA video driver crashes system during X - fb or fb - X switching)
Your message dated Tue, 8 Sep 2009 22:02:54 +0200 with message-id 20090908200254.ge19...@inutil.org and subject line Re: Workaround found, but no solution for the bug has caused the Debian Bug report #420300, regarding kernel-2.6.18: MGA video driver crashes system during X - fb or fb - X switching 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.) -- 420300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel-2.6.18 Version: linux-source-2.6.18 Severity: normal As soon as I started to do some work on my new Debian Etch system, I got several severe lockups per day. Severe means: Ctrl-Alt-Del has no effect, and Alt-Print s does not sync the filesystem. The lockups happen, if I switch from X to a tty, or from a tty to X. They don't happen every time, but with a chance of 1:20 - 1:50, about 5 or 10 times a day. (Thank God or somebody else for ext3...) The problem does not exist under Debian Sarge on the same computer. Or sort of: If switching from a certain X program (gthumb) to tty, there is sometimes a slight corruption under Sarge, which can be cleared easily by switching back, changing to a different Gnome workplace, and switching to tty again. Additional system information: 1) Framebuffer The Framebuffer is installed with the following Grub line: kernel /boot/vmlinuz-2.6.18 root=/dev/sda1 ro video=matroxfb:vesa:0x1B5,fh:85000,fv:110 (I calculated the line, when I installed the Matrox card under Debian Woody, many years ago.) It reports itself as Boot video device is :01:00.0 ... matroxfb: MTRR's turned on matroxfb: 800x600x24bpp (virtual: 832x6721) matroxfb: framebuffer at 0xCE00, mapped to 0xdc88, size 33554432 Console: switching to colour frame buffer device 100x37 fb0: MATROX frame buffer device matroxfb_crtc2: secondary head of fb0 was registered as fb1 ... Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected an Intel 440BX Chipset. agpgart: AGP aperture is 256M @ 0xd000 ... Matrox MGA G200/G400/G450/G550 YUV Video interface v2.01 (c) Aaron Holtzman A'rpi mga_vid: Found MGA G400/G450 at :01:00.0 mga_vid: MMIO at 0xde9a framebuffer: 0xCE00 mga_vid: OPTION word: 0x50044120 mem: 0x10 SGRAM mga_vid: detected RAMSIZE is 32 MB mga_vid: 1 supported cards found mga_vid: using major: 83 (assigned or default!) ... [drm] Initialized drm 1.0.1 20051102 [drm] Initialized mga 3.2.1 20051102 on minor 0 agpgart: Found an AGP 1.0 compliant device at :00:00.0. agpgart: Putting AGP V2 device at :00:00.0 into 1x mode agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [drm] Initialized card for AGP DMA. 2) X My EIZO/Nanao CRT is a little older, and does not report its capabilities back to the video adapter. I install it in /etc/X11/xorg.conf with Mode 1152x864 DotClock 127.83 HTimings 1152 1176 1304 1504 VTimings 864 868 872 902 EndMode (I calculated the line, when I installed the Matrox card under Debian Woody.) Additional information: Kernel with video drivers and mga_vid module are compiled from stock Debian Etch Stable. Since my settings have worked well under Debian Woody and Debian Sarge, since quite some years, I assume a video driver problem. Ciao Hans-Joachim -- 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 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- On Mon, Aug 03, 2009 at 07:43:34PM +0200, Moritz Muehlenhoff wrote: On Wed, May 09, 2007 at 01:59:37AM +0200, Hans-Joachim Zierke wrote: Several attempts were undertaken, to solve the problem with different video modes, especially modes very close to each other. No success. Several kernel attributes for the framebuffer were tried, like init - noinit etc. No success. Different settings for the X-Server were tried. Of these, setting Option UseFBDev true has shown an effect: Instead of a system crash after every ~20th switch or so, the system crashed for every ~2nd switching. Workaround for the problem is the following: Don't use the MGA driver for the X-Server. Instead, use the framebuffer driver for the X-Server. After doing so, the system didn't crash for several days, which is only a preliminary result, but already a phantastic one. (I haven't seen
Bug#530823: marked as done (Can't get an IP address using the ath5k driver; madwifi worked.)
Your message dated Tue, 8 Sep 2009 22:03:52 +0200 with message-id 20090908200352.go19...@inutil.org and subject line Re: Can't get an IP address using the ath5k driver; madwifi worked. has caused the Debian Bug report #530823, regarding Can't get an IP address using the ath5k driver; madwifi worked. 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.) -- 530823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.29-2-686 Version: 2.6.29-5 Severity: normal Through kernel 2.6.26, I was able to use my wireless card via the madwifi driver ath-pci. Unfortunately, madwifi was recently removed from Debian, so I'm stuck with only the ath5k driver in the kernel. Problem is, it just doesn't work for me. Well, every once in a while and under conditions I can't figure out, it works 100% perfectly. But most of the time it behaves as if it's not actually connected to my wireless network (it tries to send DHCP packets and doesn't see a response -- I don't have an easy way of checking whether it's failing to send packets or whether it's not seeing the replies). Here's a typical syslog snippet in which I load the driver and attempt to acquire an IP from my home router: May 27 18:00:39 emurlahn kernel: [ 11.200078] cfg80211: Using static regulatory domain info May 27 18:00:39 emurlahn kernel: [ 11.200153] cfg80211: Regulatory domain: US May 27 18:00:39 emurlahn kernel: [ 11.200222] ^I(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) May 27 18:00:39 emurlahn kernel: [ 11.200322] ^I(2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) May 27 18:00:39 emurlahn kernel: [ 11.200394] ^I(517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) May 27 18:00:39 emurlahn kernel: [ 11.200467] ^I(519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) May 27 18:00:39 emurlahn kernel: [ 11.200540] ^I(521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) May 27 18:00:39 emurlahn kernel: [ 11.200613] ^I(523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) May 27 18:00:39 emurlahn kernel: [ 11.200685] ^I(5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) May 27 18:00:39 emurlahn kernel: [ 11.200758] cfg80211: Calling CRDA for country: US May 27 18:00:39 emurlahn kernel: [ 11.236724] ath5k :04:04.0: PCI INT A - GSI 18 (level, low) - IRQ 18 May 27 18:00:39 emurlahn kernel: [ 11.236903] ath5k :04:04.0: registered as 'phy0' May 27 18:00:39 emurlahn kernel: [ 11.395667] wmaster0 (ath5k): not using net_device_ops yet May 27 18:00:39 emurlahn kernel: [ 11.396054] phy0: Selected rate control algorithm 'minstrel' May 27 18:00:39 emurlahn kernel: [ 11.425271] wlan0 (ath5k): not using net_device_ops yet May 27 18:00:39 emurlahn kernel: [ 11.425687] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) [snip lots of non-wifi stuff...] May 27 18:00:39 emurlahn kernel: [ 15.157421] wlan0: authenticate with AP NN:NN:NN:NN:NN:NN May 27 18:00:39 emurlahn kernel: [ 15.165801] wlan0: authenticated May 27 18:00:39 emurlahn kernel: [ 15.165804] wlan0: associate with AP NN:NN:NN:NN:NN:NN May 27 18:00:39 emurlahn kernel: [ 15.215837] wlan0: RX AssocResp from NN:NN:NN:NN:NN:NN (capab=0x431 status=0 aid=1) May 27 18:00:39 emurlahn kernel: [ 15.215842] wlan0: associated [more snip...] May 27 18:00:39 emurlahn dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 May 27 18:00:45 emurlahn dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 May 27 18:00:46 emurlahn dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 [...repeat DHCPDISCOVER until dhclient gives up...] The card in question is a PCI device in a desktop machine: 04:04.0 Ethernet controller [0200]: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter [168c:0013] (rev 01) Daniel -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-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.29-2-686 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo Versions
Bug#375742: marked as done (linux-image-2.6.16-1-686-smp: sync speed of RAID devices is 2000K/sec by default, because don't honor speed_limit_max)
Your message dated Tue, 8 Sep 2009 22:03:05 +0200 with message-id 20090908200305.gg19...@inutil.org and subject line Re: linux-image-2.6.16-1-686-smp: sync speed of RAID devices is 2000K/sec by default, because don't honor speed_limit_max has caused the Debian Bug report #375742, regarding linux-image-2.6.16-1-686-smp: sync speed of RAID devices is 2000K/sec by default, because don't honor speed_limit_max 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.) -- 375742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.16-1-686-smp Version: 2.6.16-11bpo1 Severity: normal The sync speed of RAID devices is only 2000K/sec by default. It's because the raid driver don't honor /proc/sys/dec/raid/speed_limit_max and is using speed_limit_min as the max. speed_limit_min is 1000 by default, if I increase the number for 5000, the sync speed of the RAID increases to 5000K/sec. If I increase to a bigger number the sync speed of the raid maxes on hardware capability. I believe in the kernel 2.6.16 the RAID driver use speed_limit_min as the max, and ignores speed_limit_max. On kernel 2.6.8 the behaviour seems to be correct, the RAID driver honors speed_limit_max. Jose Calhariz -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16-1-686-smp Locale: LANG=C, lc_ctype=pt...@euro (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-1-686-smp depends on: ii initramfs-tools [linux-initr 0.59bpo1tools for generating an initramfs ii module-init-tools3.2.2-1bpo1 tools for managing Linux kernel mo -- debconf information: linux-image-2.6.16-1-686-smp/postinst/kimage-is-a-directory: linux-image-2.6.16-1-686-smp/prerm/would-invalidate-boot-loader-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/old-system-map-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/already-running-this-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/preinst/bootloader-initrd-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/failed-to-move-modules-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/postinst/depmod-error-initrd-2.6.16-1-686-smp: false linux-image-2.6.16-1-686-smp/preinst/overwriting-modules-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/old-dir-initrd-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/depmod-error-2.6.16-1-686-smp: false linux-image-2.6.16-1-686-smp/preinst/abort-install-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/postinst/create-kimage-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/old-initrd-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/lilo-initrd-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/elilo-initrd-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/initrd-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-686-smp/postinst/bootloader-test-error-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/postinst/bootloader-error-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/preinst/abort-overwrite-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/prerm/removing-running-kernel-2.6.16-1-686-smp: true ---End Message--- ---BeginMessage--- Version: 2.6.30-1 On Tue, Aug 11, 2009 at 12:59:35PM +0100, Jose Calhariz wrote: Have you been able to test it? I have not seen the problem with kernels from etch or 2.6.30 from backports.org. Thank you. Thanks, marking as fixed. Cheers, Moritz ---End Message---
Bug#252553: marked as done (Install Report IBM NETVISTA)
Your message dated Tue, 8 Sep 2009 22:03:45 +0200 with message-id 20090908200345.gn19...@inutil.org and subject line Re: Install Report IBM NETVISTA has caused the Debian Bug report #252553, regarding Install Report IBM NETVISTA 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.) -- 252553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package:Install Initial install from cdrom dated 3-15-2004 Updated 06-03-2004 using dselect. Issue: CDROM unavailable since initial install. Eject button will not open cdrom after POC hardware test. All else seems to be working great. lspci and lsmod at bottom of dmesg report: Linux version 2.4.25-1-386 (herb...@gondolin) (gcc version 3.3.3 (Debian 20040401)) #2 Wed Apr 14 19:38:08 EST 2004 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 2fcf (usable) BIOS-e820: 2fcf - 2fcfb000 (ACPI data) BIOS-e820: 2fcfb000 - 2fd0 (ACPI NVS) BIOS-e820: 2fd0 - 2fe8 (usable) BIOS-e820: 2fe8 - 3000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff80 - ffc0 (reserved) BIOS-e820: fc00 - 0001 (reserved) 766MB LOWMEM available. ACPI: have wakeup address 0xc0001000 found SMP MP-table at 000f62e0 hm, page 000f6000 reserved twice. hm, page 000f7000 reserved twice. hm, page 0009f000 reserved twice. hm, page 000a reserved twice. On node 0 totalpages: 196224 zone(0): 4096 pages. zone(1): 192128 pages. zone(2): 0 pages. IBM machine detected. Enabling interrupts during APM calls. ACPI: RSDP (v000 PTLTD ) @ 0x000f62b0 ACPI: RSDT (v001 PTLTD RSDT 0x060400d0 LTP 0x) @ 0x2fcf7424 ACPI: FADT (v001 IBM NETVISTA 0x060400d0 PTL 0x0001) @ 0x2fcfaee2 ACPI: TCPA (v001 IBM NETVISTA 0x060400d0 PTL 0x0001) @ 0x2fcfaf56 ACPI: MADT (v001 PTLTD APIC 0x060400d0 LTP 0x) @ 0x2fcfaf88 ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x060400d0 LTP 0x0001) @ 0x2fcfafd8 ACPI: DSDT (v001 IBM Yelotail 0x060400d0 MSFT 0x010e) @ 0x ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Using ACPI for processor (LAPIC) configuration information Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: IBM Product ID: NETVISTA APIC at: 0xFEE0 I/O APIC #1 Version 32 at 0xFEC0. Enabling APIC mode: Flat. Using 1 I/O APICs Processors: 1 Kernel command line: root=/dev/hda1 ro Initializing CPU#0 Detected 1993.539 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 3971.48 BogoMIPS Memory: 770264k/784896k available (1076k kernel code, 14180k reserved, 465k data, 92k init, 0k highmem) Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode cache hash table entries: 65536 (order: 7, 524288 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 65536 (order: 6, 262144 bytes) Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: After generic, caps: 3febfbff CPU: Common caps: 3febfbff CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. Checking for popad bug... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: ESR value after enabling vector: ENABLING IO-APIC IRQs Setting 1 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 1 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 1-0, 1-21, 1-22 not connected. ..TIMER: vector=0x31 pin1=-1 pin2=0 ...trying to set up timer (IRQ0) through the 8259A ... . (found pin 0) ...works. number of MP IRQ sources: 25. number of IO-APIC #1 registers: 24. testing the IO APIC... IO APIC #1.. register #00: 0100 ... : physical APIC id: 01 ... : Delivery Type: 0 ... : LTS : 0 register #01: 00178020 ... : max redirection entries: 0017 ... : PRQ implemented: 1 ...
Processed: Re: Fwd: [issues] glibc uses '__unused' as identifier, which is traditionally used by BSD as macro
Processing commands for cont...@bugs.debian.org: tags 522773 wontfix Bug #522773 [linux-libc-dev] linux-libc-dev: uses __unused as identifier, which is traditionally used by BSD as macro Added tag(s) wontfix. severity 522773 wishlist Bug #522773 [linux-libc-dev] linux-libc-dev: uses __unused as identifier, which is traditionally used by BSD as macro Ignoring request to change severity of Bug 522773 to the same value. 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#415864: marked as done (aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0)
Your message dated Tue, 8 Sep 2009 22:02:49 +0200 with message-id 20090908200249.gd19...@inutil.org and subject line Re: aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0 has caused the Debian Bug report #415864, regarding aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0 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.) -- 415864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-4-amd64 Version: 2.6.18.dfsg.1-11 Severity: critical Justification: breaks the whole system + netinstall iso lo, well, ive several live cd systems 2.6.19.5i386 that oops and hang boot in aic7xxx init, only one booting here is knoppix 5.2, the latest unofficial debian stable 2.6.8-12-amd64-generic, which says ACPI: PCI interrupt :00:06.0[A] - GSI 17 (level, low) - IRQ 17 aic7xxx: PCI0:6:0 MEM region 0x0 unavailable. Cannot memory map device. but works ok, a debian etch 2.6.18-4-amd64 which says: SCSI subsystem initialized GSI 16 sharing vector 0xA9 and IRQ 16 ACPI: PCI Interrupt :00:06.0[A] - GSI 17 (level, low) - IRQ 169 BUG: soft lockup detected on CPU#0! Call Trace: IRQ [802a3fec] softlockup_tick+0xdb/0xed [802881df] update_process_times+0x42/0x68 [8026cbd8] smp_local_timer_interrupt+0x23/0x47 [8026d2cc] smp_apic_timer_interrupt+0x41/0x47 [8025904a] apic_timer_interrupt+0x66/0x6c EOI [8038a412] pci_conf1_write+0x0/0xc9 [88053718] :aic7xxx:ahc_pci_test_register_access+0xc2/0x391 [880536a5] :aic7xxx:ahc_pci_test_register_access+0x4f/0x391 [88059416] :aic7xxx:ahc_pci_map_registers+0x1bb/0x239 [880523d2] :aic7xxx:ahc_pci_config+0x4c/0x12d0 [80389fb7] pcibios_set_master+0x1e/0x84 [88059186] :aic7xxx:ahc_linux_pci_dev_probe+0x13e/0x213 [80317eea] pci_device_probe+0xdf/0x147 [8036b9db] driver_probe_device+0x52/0xa8 [8036ba96] __driver_attach+0x0/0x9a [8036bae6] __driver_attach+0x50/0x9a [8036ba96] __driver_attach+0x0/0x9a [8036b458] bus_for_each_dev+0x43/0x6e [8036b09a] bus_add_driver+0x7e/0x130 [803180c4] __pci_register_driver+0x57/0x7d [8805903e] :aic7xxx:ahc_linux_pci_init+0x17/0x21 [8806e325] :aic7xxx:ahc_linux_init+0x325/0x336 [8027d27d] default_wake_function+0x0/0xe [8025e2e5] __down_read+0x12/0x9a [80294fa1] __link_module+0x0/0x25 [802200e5] __up_read+0x13/0x8a [80297695] sys_init_module+0x16cc/0x1882 [802584d6] system_call+0x7e/0x83 BUG: soft lockup detected on CPU#0! a kernel.org 2.6.20 with K8 config set but built in a 32Bit debian sid environment, but works ok, and finally the latest kernel.org 2.6.20.3 AMD K8 built on debian amd64 etch userland that hangs boot on aic7xxx init without magic sysreq keys functionality: Loading iSCSI transport class v2.0-724. ACPI: PCI Interrupt :00:06.0[A] - GSI 17 (level, low) - IRQ 17 ... Kernel alive - Kernel direct mapping tables up to 1 @ 8000-d000 according to the stack above this should be a pci adaptor mem resources prob. tweaking boot parameters did not fix. now trying latest scsi git and be on ##kernel at freenode if Q. update: no fix so far in kernel.org scsi-rc-fixes.git, just on building a scsi dev git kernel with change from K8-x86_64 generic Kconfig and full debug, examining driver code and will report if i find the cause. y tom SysRq : Resetting Linux version 2.6.20.3amd64 (r...@tom1) (gcc version 4.1.2 20061115 (prerelease7 Command line: root=/dev/sda1 ro single console=ttyS0,115200n8 aic7xxx=debug=255 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e4000 - 0010 (reserved) BIOS-e820: 0010 - 1ffd (usable) BIOS-e820: 1ffd - 1ffde000 (ACPI data) BIOS-e820: 1ffde000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: ff78 - 0001 (reserved) end_pfn_map = 1048576 DMI 2.3 present. Zone PFN ranges: DMA 0 - 4096 DMA324096 - 1048576 Normal1048576 - 1048576 early_node_map[2] active PFN ranges 0:0 - 159 0: 256 - 131024 ACPI: PM-Timer IO Port: 0x808 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) ACPI: IOAPIC (id[0x01]
Bug#482382: marked as done (linux-image-2.6.24-etchnhalf.1-686: System locks up if I copy data to my USB2-HDD)
Your message dated Tue, 8 Sep 2009 22:52:00 +0200 with message-id 20090908205200.ga22...@galadriel.inutil.org and subject line Re: linux-image-2.6.24-etchnhalf.1-686: System locks up if I copy data to my USB2-HDD has caused the Debian Bug report #482382, regarding linux-image-2.6.24-etchnhalf.1-686: System locks up if I copy data to my USB2-HDD 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.) -- 482382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.24-6~etchnhalf.2 Severity: important *** Please type your report below this line *** If I copy massive data to my USB2-HDD the System completely hangs after a while. This does not occur with 2.6.18 Kernel. m...@matthias:~$ lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) 00:04.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:04.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 00:04.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:09.0 USB Controller: NEC Corporation USB (rev 43) 00:09.1 USB Controller: NEC Corporation USB (rev 43) 00:09.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07) 00:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 07) 00:0b.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02) 00:0c.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 00:0d.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) m...@matthias:~$ cat /proc/interrupts CPU0 0: 24561773XT-PIC-XTtimer 1: 1XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 3: 1XT-PIC-XT 4:139XT-PIC-XTserial 5: 80957XT-PIC-XTEMU10K1 6: 5XT-PIC-XTfloppy 7: 1XT-PIC-XTparport0 8: 1XT-PIC-XTrtc 9: 350314XT-PIC-XTacpi, uhci_hcd:usb2, ohci_hcd:usb3, saa7146 (0) 10: 55520XT-PIC-XTehci_hcd:usb1, ide2 11: 297476XT-PIC-XTohci_hcd:usb4, eth0, m...@pci::01:00.0 14: 31023XT-PIC-XTide0 15: 31041XT-PIC-XTide1 NMI: 0 Non-maskable interrupts LOC: 0 Local timer interrupts RES: 0 Rescheduling interrupts CAL: 0 function call interrupts TLB: 0 TLB shootdowns TRM: 0 Thermal event interrupts SPU: 0 Spurious interrupts ERR: 0 MIS: 0 m...@matthias:~$ lsmod Module Size Used by mga57728 2 drm72280 3 mga tun10976 0 ppdev 8676 0 lp 11012 0 ac 4448 0 battery 8448 0 ipv6 241956 14 nls_utf82080 1 nls_cp437 5792 1 vfat 12160 1 fat46880 1 vfat nls_base7268 4 nls_utf8,nls_cp437,vfat,fat dm_snapshot17444 0 dm_mirror 25316 0 dm_mod 55656 2 dm_snapshot,dm_mirror loop 16708 0 snd_emu10k1_synth 6816 0 snd_emux_synth 30560 1 snd_emu10k1_synth snd_seq_virmidi 6720 1 snd_emux_synth snd_seq_midi_emul 5856 1 snd_emux_synth snd_emu10k1 122688 5 snd_emu10k1_synth snd_seq_dummy 3780 0 tda100235860 1 snd_seq_oss28544 0 snd_seq_midi8064 0 snd_seq_midi_event 6976 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi snd_seq45872 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_rawmidi22528 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi parport_pc 25860 1 snd_ac97_codec 91300 1 snd_emu10k1 parport33868 3 ppdev,lp,parport_pc ac97_bus1952 1 snd_ac97_codec snd_pcm_oss37824 0 snd_mixer_oss 14880 1 snd_pcm_oss budget_av 18880 4 snd_pcm68228 4 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
Driver for HP arry P410I ZM SAS array controller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I recently received 2 HP DL360 G6 with additional SAS controller HP P410i ZM (Zero memory) to interface with a HPLTO3 Library . I started Debian lenny 5.02 (2.6.26-2) but SAS controller is not detected . I know that it is detected on RHEL5 with module cciss 3.6.20-20 version of the driver while Debian module version is 3.6.20. Does a new version of this driver is available in an unstable debian kernel or can it be possible to provide kernel ports ? More information on : http://cciss.sourceforge.net/ Sources are available for Redhat and Suse, none for Debian Regards OJ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqmyeoACgkQkUrg9pTek33FmgCgna2rIABU8jglKCF36y7pgDVt UEQAni1K+t37cGHCIc033TX5VpPkxJM7 =xVa8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#465278: Appletouch failure upon resume after suspend2ram
On Sun, Jul 19, 2009 at 12:24:30AM +0200, Moritz Muehlenhoff wrote: On Sun, Feb 01, 2009 at 07:30:55PM -0500, Simon Valiquette wrote: Severity 465278 grave By searching a little on mailing lists, I saw that someone reported that the problems might be related with this patch, or at least related with this part of the code, but nobody seems to have seriously looked at it: http://www.linuxhq.com/kernel/v2.6/24/drivers/input/mouse/appletouch.c http://www.mail-archive.com/debian-powe...@lists.debian.org/msg59480.html From the Debian PowerPC mailing list, I deduce that the problem appeared in Debian Sid with the kernel 2.6.24. Does this error still occur with more recent kernel versions, such as the 2.6.30 kernel from unstable? Adding a few more people from the bug log to CC. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508492: linux-image-2.6.26-1-parisc64: [hppa64] XFS internal error xlog_valid_rec_header(2)
On Tue, Sep 8, 2009 at 4:31 PM, Moritz Muehlenhoffj...@inutil.org wrote: On Tue, Sep 08, 2009 at 02:21:38PM -0600, Stillwell, Bryan wrote: On Tue, 2009-09-01 at 19:17 +, Moritz Muehlenhoff wrote: Does this still occur with later kernels, such as 2.6.30 from unstable or backports.org? Yes, it still shows up in 2.6.30-bpo.1-parisc64 from backports.org: [ 282.992000] XFS mounting filesystem dm-2 [ 283.148000] Starting XFS recovery on filesystem: dm-2 (logdev: ... [ 283.292000] XFS: log mount/recovery failed: error 177 [ 283.30] XFS: log mount failed Adding debian-hppa in the loop: Is this a known issue and specific to hppa? (Since otherwise I would suppose there were earlier reports from the more widely used archs). XFS is possibly broken on Linux for any arch that has virtually indexed cache, including ARM and HPPA. This is being discussed on linux-parisc, linux-fsdevel, and linux-arch[1] Cheers, Carlos. [1] http://marc.info/?l=linux-fsdevelm=125243448021545w=2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#334843: marked as done (linux-image-2.6.12-1-686: Oops suddenly appearing after a video card change)
Your message dated Tue, 8 Sep 2009 22:03:17 +0200 with message-id 20090908200317.gi19...@inutil.org and subject line Re: more details has caused the Debian Bug report #334843, regarding linux-image-2.6.12-1-686: Oops suddenly appearing after a video card change 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.) -- 334843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.12-1-686 Version: 2.6.12-10 Severity: normal Hello, I suspect this may have something to do with http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330455, as it sounds to be some kind of interrupt conflicts. I had a computer running linux-image-2.6.12-1-686 since a while, with no problem, with a Radeon 9000 onboard. Lately, I changed the card with a Radeon 9600 pro, and since then I get oops while booting, but very late during the boot process (after NFS mounts are mounted, to give you an idea). The same Radeon 9600 pro card was running well in another computer with the exact same kernel since a while. The other computer got an Intel motherboard, while this one got a VIA one. Here's come the lspci results (as you see, there are several possible cause for such conflicts). :00:00.0 Host bridge: VIA Technologies, Inc. VT8753 [P4X266 AGP] (rev 01) :00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] :00:09.0 SCSI storage controller: Tekram Technology Co.,Ltd. TRM-S1040 (rev 01) :00:0a.0 Multimedia audio controller: Creative Labs SB Audigy LS :00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 23) :00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 23) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 40) :01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] :01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) In /var/log/kern.log there's nothing related to the crash. There's nothing relevant in /var/log/debug either. So I dont know exactly what should I provide to make this report more useful. Tell me. Regards, -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15) Versions of packages linux-image-2.6.12-1-686 depends on: ii coreutils [fileutils] 5.2.1-2.1 The GNU core utilities ii fileutils 5.2.1-2.1 The GNU file management utilities ii initrd-tools 0.1.82 tools to create initrd image for p ii module-init-tools 3.2-pre9-2 tools for managing Linux kernel mo linux-image-2.6.12-1-686 recommends no packages. -- no debconf information -- Mathieu Roy + | Thalie : http://yeupou.coleumes.org/ | Clio: http://clio.coleumes.org/ | Euterpe : http://crap.is.free.fr/ | http://kromaniaks.coleumes.org/ +---+ ---End Message--- ---BeginMessage--- On Tue, Jul 28, 2009 at 12:41:56AM +0200, Moritz Muehlenhoff wrote: On Thu, Dec 15, 2005 at 02:19:10PM +0100, Mathieu Roy wrote: Hello, I installed udev, as it is supposed to be the thing to use with such kernel, and this cause the system to segfault too. So the hdparm fix helped to avoid the problem, but there is definitely something very wrong there. I was confused by your initial bug report, thought that it was related to the loading of ide modules, and was offering a work around. If you feel that was off-topic, please ignore it. I wonder what would cause that bug. As said before, I found this problem after an hardware change, the video card, with a video card that worked perfectly on another computer with the same arch (not the same motherboard, but the same system with the same software). I traced the failure at the hdparm init script and Aurelien was able to provide a workaround. But still there's something wrong, as shows udev failure. I find odd that
Bug#409806: marked as done (kernel: general protection fault: 0000 [1] SMP)
Your message dated Tue, 8 Sep 2009 22:02:43 +0200 with message-id 20090908200243.gc19...@inutil.org and subject line Re: kernel: general protection fault: [1] SMP has caused the Debian Bug report #409806, regarding kernel: general protection fault: [1] SMP 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.) -- 409806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel Version: 2.6.18-3-amd64 #1 SMP Mon Dec 4 17:04:37 CET 2006 x86_64 GNU/Linux Severity: normal While using a debian ethc system in an usual way: the following two lines happend: Message from sysl...@computername at Mon Feb 5 18:08:22 2007 ... simi kernel: general protection fault: [1] SMP This deals with 2.6.18-3-amd64 #1 SMP Mon Dec 4 17:04:37 CET 2006 x86_64 GNU/Linux :~$ lsmod Module Size Used by smbfs 69648 2 ext2 70288 0 udf81416 1 radeon116384 2 drm87080 3 radeon nfsd 256200 17 exportfs 10368 1 nfsd button 12192 0 ac 10376 0 battery15496 0 ipv6 285664 49 nfs 236216 3 lockd 67600 3 nfsd,nfs nfs_acl 8320 2 nfsd,nfs sunrpc166984 13 nfsd,nfs,lockd,nfs_acl sk98lin 146656 0 dm_snapshot20536 0 dm_mirror 25216 0 dm_mod 62800 2 dm_snapshot,dm_mirror sbp2 28680 0 loop 20112 0 tsdev 13056 0 snd_hda_intel 23708 1 snd_hda_codec 184192 1 snd_hda_intel snd_pcm_oss48672 0 snd_mixer_oss 21888 1 snd_pcm_oss i2c_i801 13076 0 snd_pcm88968 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss parport_pc 41640 0 parport44684 1 parport_pc psmouse44432 0 snd_timer 29192 1 snd_pcm i2c_core 27776 1 i2c_i801 serio_raw 12036 0 pcspkr 7808 0 shpchp 42156 0 pci_hotplug20872 1 shpchp snd65256 8 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 15392 1 snd snd_page_alloc 14864 2 snd_hda_intel,snd_pcm evdev 15360 1 sky2 46212 0 eth139424840 0 ext3 138256 6 jbd65392 1 ext3 mbcache14216 2 ext2,ext3 ide_cd 45088 1 cdrom 40488 1 ide_cd sd_mod 25856 7 generic10756 0 [permanent] usbhid 45088 0 ata_piix 19976 0 libata106784 1 ata_piix ohci1394 38216 0 ieee1394 361976 3 sbp2,eth1394,ohci1394 aacraid63616 6 scsi_mod 152880 4 sbp2,sd_mod,libata,aacraid skge 43536 0 piix 15492 0 [permanent] ide_core 147584 3 ide_cd,generic,piix uhci_hcd 28432 0 ehci_hcd 36104 0 thermal20240 0 processor 38248 1 thermal fan 9864 0 this happend trying some zip commands, from local drive to udf filesystem removable Iomega drive, working with /dev/hda. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Version: 2.6.24-1 On Fri, Aug 14, 2009 at 02:28:09AM +0200, Jean-Michel wrote: I observed this error with etch, in 2007. Due to issues with 2.6.18, I switched to 2.6.24, some time ago (might be one or two years). Since then I did not observe any error related to UDF filesystem (except one windows incompatibility documented in another bug report). Thanks, marking as closed. Cheers, Moritz ---End Message---
Bug#423248: marked as done (linux-image-2.6.18-4-486: [r8169] drops received TCP packets when using jumbo frames)
Your message dated Tue, 8 Sep 2009 22:03:10 +0200 with message-id 20090908200310.gh19...@inutil.org and subject line Re: linux-image-2.6.18-4-486: [r8169] drops received TCP packets when using jumbo frames has caused the Debian Bug report #423248, regarding linux-image-2.6.18-4-486: [r8169] drops received TCP packets when using jumbo frames 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.) -- 423248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-12, 2.6.18.dfsg.1-12etch1 When upgrading to the etch version of the kernel, I noticed a complete NFS lockup as soon as a client tries to write something. I tracked this down to the TCP layer; I'm using jumbo frames (tried with MTU ranging from 2000 to 7200) and all *received* TCP packets exceeding 1500 bytes are simply dropped. They don't even appear in tcpdump. This does not affect UDP nor ICMP packets, and this does not affect sent TCP packets. 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. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. ---End Message--- ---BeginMessage--- On Sun, Jul 26, 2009 at 11:57:54AM +0200, Moritz Muehlenhoff wrote: 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? Closing the bug for now. If anyone manages to reproduce with a more recent kernel, please reopen. Cheers, Moritz ---End Message---
Re: Driver for HP arry P410I ZM SAS array controller
On Tue, 2009-09-08 at 23:24 +0200, Olivier JUDITH wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I recently received 2 HP DL360 G6 with additional SAS controller HP P410i ZM (Zero memory) to interface with a HPLTO3 Library . I started Debian lenny 5.02 (2.6.26-2) but SAS controller is not detected . Linux 2.6.26 includes support for P410i and the ZM configuration. I think the problem may lie elsewhere. When you say you 'started Debian', do you mean you started to install it, or that you installed it but it did not boot afterwards? Can you send a kernel log from the Debian kernel? If you cannot save it to a file, please take a photograph. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp signature.asc Description: This is a digitally signed message part
Bug#515982: Bug#511703: text_poke_early crash and noreplace-paravirt
Ben Hutchings wrote: I don't have any 486-class systems to test this on, so perhaps you could try this patch: That works for me. Booting 'Debian GNU/Linux, kernel 2.6.26-2-486-511703' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.26-2-486-511703 root=/dev/hda1 ro console=ttyS0,57600 n8 [Linux-bzImage, setup=0x3000, size=0x164590] initrd /boot/initrd.img-2.6.26-2-486 [Linux-initrd @ 0x3d8, 0x26fd3f bytes] Probing EDD (edd=off to disable)... ok [...] [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26 (2.6.26) (rich...@leucomorph) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 Tue Sep 8 11:31:50 BST 2009 [...] [0.104006] CPU: AMD Am5x86-WB stepping 04 [0.112007] Checking 'hlt' instruction... OK. [0.156009] Freeing SMP alternatives: 0k freed [0.160010] ACPI: Core revision 20080321 [...] ttfn/rjk -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444043: [Pkg-utopia-maintainers] Bug#444043: Bug#444043: network-manager: Unconnected USB ethernet device is made to take priority over connected wireless!
2009/9/8 Ben Hutchings b...@decadent.org.uk: Please could you test the attached patch against Linux 2.6.30? The Debian kernel handbook explains how to do this: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. I can also prepare a patch against Linux 2.6.26 if you want. This is great, but I don't have a machine running Debian that I can test with this patch at the moment. Any suggestions? I could boot one temporarily if there were some easy way to run the test... -- http://rrt.sc3d.org Radiance is the appeasement of myth (Adorno) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444043: [Pkg-utopia-maintainers] Bug#444043: Bug#444043: network-manager: Unconnected USB ethernet device is made to take priority over connected wireless!
On Fri, 2009-01-02 at 01:04 +, Reuben Thomas wrote:
On Fri, 26 Dec 2008, Moritz Muehlenhoff wrote:
On Sun, Sep 30, 2007 at 12:41:35AM +0100, Reuben Thomas wrote:
On Sun, 30 Sep 2007, Michael Biebl wrote:
Please reassign to the package providing the flusb driver. In your case
that should probably be on of the linux-image-* packages.
Sounds like the right package, the kernel modules involved seem to be
rather usbnet, plusb and asix...).
Does this error still occur with more recent kernel versions?
If I try the command indicated further up the thread, that is,
$ cat `find . -name carrier | grep usb0`
I get the following output:
cat:
./devices/pci:00/:00:1d.7/usb5/5-6/5-6.2/5-6.2.1/5-6.2.1:1.0/net/usb0/carrier:
Invalid argument
I don't know what this indicates; I hope you do!
# ls -l carrier
-r--r--r-- 1 root root 4096 2009-01-02 01:00 carrier
It means you need to bring the interface up before you can find out the
link state. In any case, I think this is still broken - Network Manager
will use the ethtool get_link() operation, which the generic usbnet
driver implements even where the hardware-specific driver cannot detect
the link state.
Please could you test the attached patch against Linux 2.6.30? The
Debian kernel handbook explains how to do this:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
I can also prepare a patch against Linux 2.6.26 if you want.
Ben.
--
Ben Hutchings
Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp
From 3b051716486432b2967db5b96439234dd3dd7849 Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Tue, 8 Sep 2009 23:01:02 +0100
Subject: [PATCH] usbnet: Do not implement ethtool get_link() if link state is unknown
Many USB network drivers cannot detect the link state. Only define
the ethtool get_link() operation for those that implement
check_connect() or set a flag to indicate that link state is
available through MII or netif_carrier_ok().
---
drivers/net/usb/asix.c | 12 ++--
drivers/net/usb/cdc_ether.c |2 +-
drivers/net/usb/mcs7830.c |4 ++--
drivers/net/usb/smsc95xx.c |2 +-
drivers/net/usb/usbnet.c| 17 +++--
include/linux/usb/usbnet.h |2 ++
6 files changed, 27 insertions(+), 12 deletions(-)
diff --git a/drivers/net/usb/asix.c b/drivers/net/usb/asix.c
index 87b4a02..b062376 100644
--- a/drivers/net/usb/asix.c
+++ b/drivers/net/usb/asix.c
@@ -1327,7 +1327,7 @@ static const struct driver_info ax8817x_info = {
.status = asix_status,
.link_reset = ax88172_link_reset,
.reset = ax88172_link_reset,
- .flags = FLAG_ETHER,
+ .flags = FLAG_ETHER | FLAG_GET_LINK,
.data = 0x00130103,
};
@@ -1337,7 +1337,7 @@ static const struct driver_info dlink_dub_e100_info = {
.status = asix_status,
.link_reset = ax88172_link_reset,
.reset = ax88172_link_reset,
- .flags = FLAG_ETHER,
+ .flags = FLAG_ETHER | FLAG_GET_LINK,
.data = 0x009f9d9f,
};
@@ -1347,7 +1347,7 @@ static const struct driver_info netgear_fa120_info = {
.status = asix_status,
.link_reset = ax88172_link_reset,
.reset = ax88172_link_reset,
- .flags = FLAG_ETHER,
+ .flags = FLAG_ETHER | FLAG_GET_LINK,
.data = 0x00130103,
};
@@ -1357,7 +1357,7 @@ static const struct driver_info hawking_uf200_info = {
.status = asix_status,
.link_reset = ax88172_link_reset,
.reset = ax88172_link_reset,
- .flags = FLAG_ETHER,
+ .flags = FLAG_ETHER | FLAG_GET_LINK,
.data = 0x001f1d1f,
};
@@ -1367,7 +1367,7 @@ static const struct driver_info ax88772_info = {
.status = asix_status,
.link_reset = ax88772_link_reset,
.reset = ax88772_link_reset,
- .flags = FLAG_ETHER | FLAG_FRAMING_AX,
+ .flags = FLAG_ETHER | FLAG_FRAMING_AX | FLAG_GET_LINK,
.rx_fixup = asix_rx_fixup,
.tx_fixup = asix_tx_fixup,
};
@@ -1378,7 +1378,7 @@ static const struct driver_info ax88178_info = {
.status = asix_status,
.link_reset = ax88178_link_reset,
.reset = ax88178_link_reset,
- .flags = FLAG_ETHER | FLAG_FRAMING_AX,
+ .flags = FLAG_ETHER | FLAG_FRAMING_AX | FLAG_GET_LINK,
.rx_fixup = asix_rx_fixup,
.tx_fixup = asix_tx_fixup,
};
diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
index 55e8ecc..dfaea39 100644
--- a/drivers/net/usb/cdc_ether.c
+++ b/drivers/net/usb/cdc_ether.c
@@ -444,7 +444,7 @@ static int cdc_bind(struct usbnet *dev, struct usb_interface *intf)
static const struct driver_info cdc_info = {
.description = CDC Ethernet Device,
- .flags = FLAG_ETHER,
+ .flags = FLAG_ETHER | FLAG_GET_LINK,
// .check_connect = cdc_check_connect,
.bind = cdc_bind,
.unbind = usbnet_cdc_unbind,
diff --git a/drivers/net/usb/mcs7830.c b/drivers/net/usb/mcs7830.c
index 7ae9afe..ccef9ca 100644
--- a/drivers/net/usb/mcs7830.c
+++ b/drivers/net/usb/mcs7830.c
@@ -549,7 +549,7 @@ static const struct driver_info moschip_info = {
.description = MOSCHIP 7830/7730 usb-NET adapter,
.bind = mcs7830_bind,
Re: Driver for HP arry P410I ZM SAS array controller
Ben Hutchings wrote: On Tue, 2009-09-08 at 23:24 +0200, Olivier JUDITH wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I recently received 2 HP DL360 G6 with additional SAS controller HP P410i ZM (Zero memory) to interface with a HPLTO3 Library . I started Debian lenny 5.02 (2.6.26-2) but SAS controller is not detected . Linux 2.6.26 includes support for P410i and the ZM configuration. I think the problem may lie elsewhere. When you say you 'started Debian', do you mean you started to install it, or that you installed it but it did not boot afterwards? Can you send a kernel log from the Debian kernel? If you cannot save it to a file, please take a photograph. Ben. Yeah i success to install lenny but can't see P410i and library attached I will sent you dmesg + lspci in few hours because i'm not in office now. I confirm than the device is not deteted because and have tested the second machine on RHEL5 with the modules provided on HP site. And i can see the controller and my library attached. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540831: missing appointments
I'm missing too many appointments and email notifications. I'm putting a modprobe into /etc/rc.local as a workaround. Hope I remember to take it back out when this bug is fixed. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516374: INFO: task * blocked for more than 120 seconds. (ubuntu bug #276476)
I am having a similar problem with 2.26.30-6. Here are the log entries. I hope this helps. Yours John [43680.636045] INFO: task bacula-sd:12964 blocked for more than 120 seconds. [43680.636079] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [43680.636125] bacula-sd D e9eea480 0 12964 1 [43680.636158] c181a1c0 00200082 f8103b9d e9eea480 c04951c0 c0492134 00200046 c3c8d690 [43680.636221] c3c8d844 0001 f82bd045 0020 c3d0f0ac c3d2d000 e9eea480 [43680.636283] 0500 c3c8d844 00a505ec 00200082 f8103cb5 e9ed5760 c3d0f000 [43680.636345] Call Trace: [43680.636402] [f8103b9d] ? scsi_pool_alloc_command+0x29/0x41 [scsi_mod] [43680.636442] [f82bd045] ? mptscsih_qcmd+0x438/0x45d [mptscsih] [43680.636489] [f8103cb5] ? scsi_get_command+0x5a/0x72 [scsi_mod] [43680.636538] [c031d600] ? schedule+0x5/0x13 [43680.636575] [c031d72b] ? schedule_timeout+0x14/0xbd [43680.636616] [c01f1f8e] ? elv_next_request+0x13e/0x14c [43680.636668] [f81038ce] ? scsi_dispatch_cmd+0x185/0x1e5 [scsi_mod] [43680.636720] [f81081b9] ? scsi_request_fn+0x3c4/0x47d [scsi_mod] [43680.636752] [c031cdfe] ? wait_for_common+0xb8/0x112 [43680.636781] [c0121f09] ? default_wake_function+0x0/0x8 [43680.636816] [f845a73e] ? st_scsi_execute_end+0x0/0x48 [st] [43680.636851] [f845ae07] ? st_do_scsi+0x27e/0x2a6 [st] [43680.636883] [f845bade] ? st_int_ioctl+0x61c/0xa66 [st] [43680.636916] [c0286c9f] ? release_sock+0xf/0x7f [43680.636945] [c02b7584] ? tcp_sendmsg+0x67a/0x757 [43680.636977] [f845b88b] ? st_int_ioctl+0x3c9/0xa66 [st] [43680.637008] [c028462b] ? __sock_sendmsg+0x43/0x4a [43680.637039] [f845d854] ? st_ioctl+0xb1b/0xe62 [st] [43680.637069] [c018d2ca] ? do_sync_write+0xc0/0x107 [43680.637100] [f845cd39] ? st_ioctl+0x0/0xe62 [st] [43680.637129] [c01971e7] ? vfs_ioctl+0x1c/0x5f [43680.637156] [c019766e] ? do_vfs_ioctl+0x444/0x47f [43680.637184] [c018d016] ? fsnotify_modify+0x4c/0x53 [43680.637214] [c018dc42] ? vfs_write+0x9e/0xd6 [43680.637244] [c01976ea] ? sys_ioctl+0x41/0x58 [43680.637274] [c0103014] ? sysenter_do_call+0x12/0x28 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540831: missing appointments
On Wed, Sep 09, 2009 at 08:40:19AM +0800, jida...@jidanni.org wrote: I'm missing too many appointments and email notifications. I'm putting a modprobe into /etc/rc.local as a workaround. Hope I remember to take it back out when this bug is fixed. I don't see how this comment helps the bug report at all - perhaps you could post such stream of consciousness comments to a personal blog? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543308: Kernel bug
The kernel bug system's confirmation message hasn't arrived in over 24 hours. I can't file a bug there without that. Is there any way you can file one? - This E-Mail message has been scanned for viruses and cleared by SmartMail from Smarter Technology, Inc. - -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
