A Request
Dear Debian Linux kernel developers/maintainers, Could you please provide a backport of the latest sky2.c driver on the latest stable Linux kernel source or image of the Debian GNU/Linux Etch? As you may notice this site => http://tinyurl.com/2udyqr and the sky2.c version that we have on our latest stable Linux kernel for the Debian GNU/Linux Etch, there are lots of bug fixes for the said driver. I have several production servers that uses this sky2.c driver running Debian GNU/Linux Etch but I must say that the bugs for this driver are still a threat to the stability of my servers most especially when one of my servers crashed (kernel panic) because of this sky2.c driver. Please, I am requesting from your kind heart to provide a backport of the sky2.c driver for the Debian GNU/Linux Etch. Thank you in advance and hoping for a favorable response. Regards, GNUbie
Bug#459210: marked as done (initramfs-tools: Initramfs problem with module which needs firmware (e.g. aic94xx))
Your message dated Sat, 5 Jan 2008 16:48:24 +0100 with message-id <[EMAIL PROTECTED]> and subject line initramfs-tools: Initramfs problem with module which needs firmware (e.g. aic94xx) has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: initramfs-tools Version: 0.85h Severity: normal Tags: patch Firmware installation for aic94xx I had to create a hooks file and a hotplug file to load the driver correctly during system boot. Download http://kernel.org/pub/linux/kernel/people/jejb/aic94xx-seq.fw cp aic94xx-seq.fw /lib/firmware Create /etc/initramfs-tools/hooks/firmware_aic94xx ---BEGIN OF /etc/initramfs-tools/hooks/firmware_aic94xx--- #!/bin/sh PREREQ="udev" prereqs() { echo "$PREREQ" } case $1 in prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions copy_exec /lib/udev/firmware.agent /lib/udev/ mkdir -p $DESTDIR/lib/firmware cp /lib/firmware/aic94xx-seq.fw $DESTDIR/lib/firmware copy_exec /sbin/hotplug /sbin ---END OF /etc/initramfs-tools/hooks/firmware_aic94xx--- Create /sbin/hotplug ---BEGIN OF /sbin/hotplug--- #!/bin/sh # Simple hotplug script sample: # Both $DEVPATH and $FIRMWARE are already provided in the environment. HOTPLUG_FW_DIR=/lib/firmware/ if [ ! -e /sys/$DEVPATH/loading ]; then echo /sys not found exit 1 fi echo 1 > /sys/$DEVPATH/loading cat $HOTPLUG_FW_DIR/$FIRMWARE > /sys/$DEVPATH/data echo 0 > /sys/$DEVPATH/loading ---END OF /sbin/hotplug--- -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (900, 'stable') Architecture: amd64 (amd64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.23.9 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) --- End Message --- --- Begin Message --- Version: 0.88 newer initramfs-tools in Lenny and unstable support firwmare loading without the need of an special crafted hook script. it was not possible to deliver that for etch due to too old module-init-tools where modinfo would not report the needed firmware by the corresponding driver. thus closing -- maks --- End Message ---
Bug#446724: marked as done (SAME SITUATION - initramfs-tools: creates broken initramfs image as reported on Bug #445688)
Your message dated Sat, 5 Jan 2008 16:50:56 +0100 with message-id <[EMAIL PROTECTED]> and subject line initramfs-tools: creates broken initramfs image has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: initramfs-tools Version: 0.90a Severity: critical Justification: breaks the whole system Hi, I have the same situation described by Beojan in one of my boxes but not the other two - all three are debian testing. His solution - yaird - also worked for me. Reading the bug report I came about an interesting point in that the phrases below do not apply to me as my systems always were/are debian: " i'm sorry but your initramfs-tools is not from debian, we _never_ shipped with an modprobe -Q argument in those boot scripts. " " >You may wish to know that I switched to Debian from Feisty using > dist-upgrade, and udev > didn't get upgraded. " A call to egrep -r modprobe /usr/share/initramfs-tools/scripts/init-premount/ shows some modprobe commands, all are without options such as: tatarana:/etc/default# egrep -r modprobe /usr/share/initramfs-tools/scripts/init-premount/ | head -2 /usr/share/initramfs-tools/scripts/init-premount/ps3:modprobe ps3_storage /usr/share/initramfs-tools/scripts/init-premount/ps3:modprobe gelic_net I run apt-get dist-upgrade regularly on these systems. Yesterday - oct 14 2007 - I brought all three up to date. Only one maintained the problem. The other two booted ok with new 2.6.22-2 kernel. My systems differ only in installed packages and initial install date. I do not get any deb files outside of apt. At the end of this message is my sources.list for reference. My current initramfs is also 0.90a. tatarana:~# ls /var/cache/apt/archives/ | grep initram initramfs-tools_0.89_all.deb initramfs-tools_0.90a_all.deb initramfs-tools_0.90_all.deb Since apt installed kernel 2.6.21-2 on my system I get the "Waiting for root filesystem" at boot time error. What is amazing is that my other two boxes have also up to date kernels and never had this problem. I initially reported this error as a kernel error but was unable to do a good follow-up on it. I imagined that as the kernel evolved the problem would dissapear. Since it did not I resumed trying to figure out the situation. Beojan's report reproduced my error. His modprobe -Q explanation though does not seem to apply to my computer. I hope a comparision of my three systems will help in finding the cause of this problem. Thanks for your help, I am available to supply any necessary information. Miguel sources.list information tatarana:~# grep ^deb /etc/apt/sources.list deb http://http.us.debian.org/debian testing main contrib non-free deb http://security.debian.org testing/updates main contrib non-free deb http://http.us.debian.org/debian unstable main contrib non-free deb http://download.skype.com/linux/repos/debian/ stable non-free deb http://www.debian-multimedia.org testing main deb-src http://http.us.debian.org/debian testing main contrib non-free -- Package-specific info: -- /proc/cmdline root=/dev/hda1 ro -- /proc/filesystems cramfs ext3 fuseblk vfat -- lsmod Module Size Used by tcp_diag1760 0 inet_diag 11432 1 tcp_diag nls_iso8859_1 4128 1 nls_cp437 5792 1 vfat 12032 1 fat48540 1 vfat sd_mod 27136 2 usb_storage76608 1 ppdev 8676 0 lp 10980 0 thermal13416 0 fan 4836 0 button 7920 0 ac 5188 0 battery 9988 0 xt_TCPMSS 4672 1 xt_tcpmss 2176 1 xt_tcpudp 3072 8 xt_state2432 12 processor 31016 1 thermal speedstep_lib 5156 0 cpufreq_ondemand8300 0 cpufreq_powersave 1792 0 cpufreq_userspace 4128 0 cpufreq_stats 5120 0 freq_table 4512 2 cpufreq_ondemand,cpufreq_stats cpufreq_conservative 6888 0 ipt_LOG 5952 0 iptable_mangle 2784 1 iptable_filter 2944 1 iptable_nat 7204 1 ip_tables 12260 3 iptable_mangle,iptable_filter,iptable_nat nf_nat 17964 1 iptable_nat nf_conntrack_ipv4 17772 14 iptable_nat nf_conntrack 60424 4 xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4 nfnetlink
Bug#445510: marked as done (initramfs-tools: please fail gracefully for ENOSPC)
Your message dated Sat, 5 Jan 2008 17:15:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#445510: initramfs-tools: please fail gracefully for ENOSPC has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: initramfs-tools Version: 0.85h Severity: wishlist I recently set up a system with /boot being too small. While this is my fault update-initramfs could handle this in a better way than backup the old (working) initramfs and leave a truncated one for the next reboot will fail. (Yes, it told me that my initramfs was broken afterwards!) (According to my understanding of the scripts the bug also applies to 0.91b.) I therefore suggest not creating the new initramfs directly, but create a new file with a different name and then in the last step rename the stuff if and only if no error occurred. By doing so the system will more often be in a bootable state. Furthermore this will prevent making a system unbootable by suspending the machine while updating the initramfs (a DD reported this on planet.d.o). Helmut [extra info wiped as this bug occurred on a different system] --- End Message --- --- Begin Message --- Version: 0.86 On Sat, 06 Oct 2007, Helmut Grohne wrote: > I recently set up a system with /boot being too small. While this is my > fault update-initramfs could handle this in a better way than backup the > old (working) initramfs and leave a truncated one for the next reboot > will fail. (Yes, it told me that my initramfs was broken afterwards!) > > (According to my understanding of the scripts the bug also applies to > 0.91b.) > > I therefore suggest not creating the new initramfs directly, but create > a new file with a different name and then in the last step rename the > stuff if and only if no error occurred. By doing so the system will more > often be in a bootable state. Furthermore this will prevent making a > system unbootable by suspending the machine while updating the initramfs > (a DD reported this on planet.d.o). newer update-initramfs restores the backup if the initramfs creation failed due to not enough space. christian perrier had a bad experience that was shared on planet.d.o back in the times when we didn't even created a backup initramfs. closing with appropriate versioning info. happy hacking -- maks --- End Message ---
Bug#458772: initramfs-tools: update-initramfs' check for ro-mounted /boot partitions yields false positives
On Wed, 02 Jan 2008, Daniel Reichelt wrote: > > i stumbled over this bug when I wanted to update my initrd while I had > some isos loop-mounted like this: > > - boot_opts=$(awk '/boot/{if (match($4, /^ro/) || match($4, /,ro/) \ > + boot_opts=$(awk '/boot/{if ((match($4, /^ro/) || match($4, /,ro/)) \ thanks applied to initramfs-tools, will be fixed with next upload. -> http://git.debian.org/?p=kernel/initramfs-tools.git -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 458772
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.11 > tags 458772 pending Bug#458772: initramfs-tools: update-initramfs' check for ro-mounted /boot partitions yields false positives Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 433708
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.11 > tags 433708 - patch Bug#433708: initramfs-tools: Wants to have /lib/modules/${version}/ present when creating initramfs even under kernel without modules support Tags were: patch Bug#445735: image creation fails with a non-modular kernel Tags removed: patch > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442103: initramfs-tools: update-initramfs fails with lilo and a degraded raid1 array
On Fri, 28 Sep 2007, Jens Thiele wrote: > On 17 Sep 2007, [EMAIL PROTECTED] wrote: > > hey guys sorry if you still use lilo, you need to do > > manual intervence, i see no other way. > > > > unless a real strong argument comes up, i'll close that bug in a > > month. > > AFAIK grub does not support LVM on top of md raid1 whereas lilo does? > The installer allows to setup LVM on top of raid and as far as I > remember then suggests usage of lilo. good reason enough for separate small / or /boot on raid > Just as explanation / usage scenario: > I use lvm on top of raid1 on a laptop and run the raid in degraded state > most of the time. From time to time I attach an external usb disk and > resync it. (incremental resync that is) > > IMHO lilo should provide an option in lilo.conf corresponding -H. > See also bug: #278373 i fail to find the mentioned lilo -H mention in the lilo manpage. dpkg -l lilo | grep ^ii ii lilo 22.6.1-9.3 LInux LOader - The Classic OS loader can loa a lilo -H invocation leads into usage() message. what are you guys using? happy hacking -- maks > Greetings > Jens > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442103: initramfs-tools: update-initramfs fails with lilo and a degraded raid1 array
maximilian attems <[EMAIL PROTECTED]> writes: > i fail to find the mentioned lilo -H mention in the lilo manpage. > dpkg -l lilo | grep ^ii > ii lilo 22.6.1-9.3 LInux LOader - The Classic OS loader can > loa > > a lilo -H invocation leads into usage() message. what are you guys using? $ LC_ALL=C dpkg -l lilo; man lilo|grep -n -- -H Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++--- ii lilo 1:22.8-3.1 LInux LOader - The Classic OS loader can load Linux and others 108: -H Override fatal halt when a RAID array does not have all disks Greetings Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 442103
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.11 > tags 442103 wontfix Bug#442103: initramfs-tools: update-initramfs fails with lilo and a degraded raid1 array There were no tags set. Tags added: wontfix > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#442103: initramfs-tools: update-initramfs fails with lilo and a degraded raid1 array
On Sat, Jan 05, 2008 at 08:27:53PM +0100, Jens Thiele wrote: > ii lilo 1:22.8-3.1 LInux > LOader - The Classic OS loader can load Linux and others > 108: -H Override fatal halt when a RAID array does not have > all disks > > Greetings > Jens i see, thanks for quick response. as debian supports partial upgrades and initramfs-tools is not gonna start depend on lilo this inocation can only be used after Lenny release. marking as wontfix. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#257629: marked as done (kernel-image-2.6.7-1-686-smp: load pcspkr by default)
Your message dated Sat, 5 Jan 2008 21:56:50 +0100 with message-id <[EMAIL PROTECTED]> and subject line kernel-image-2.6.7-1-686-smp: load pcspkr by default has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kernel-image-2.6.7-1-686-smp Version: 2.6.7-1 Severity: normal I've found lots of mailing list messages about this, but no bug, so let me report it. The 2.6 kernels don't support pcspkr by default. Possible solutions: - Build it statically in the kernel. This seems fine to me, but some people seem to have a thing about everything being modular... - Have a list of modules loaded automatically at boot. Sort of an /etc/modules owned by the kernel package. (/etc/modules.d?) - Have discover or some other hardware auto-detection program take care of it. It seems discover should be smart enough to know that almost any PC has speaker. Andrew -- System Information: Debian Release: 3.0 APT prefers unstable APT policy: (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686-smp Locale: LANG=C, LC_CTYPE=C Versions of packages kernel-image-2.6.7-1-686-smp depends on: ii coreutils [fileutils] 5.0.91-2 The GNU core utilities ii fileutils 5.0.91-2 The GNU file management utilities ii initrd-tools 0.1.71 tools to create initrd image for p ii module-init-tools 3.1-pre4-1 tools for managing Linux kernel mo -- no debconf information --- End Message --- --- Begin Message --- Version: 2.6.23-1 fixed since some time setting to a value, where i'm sure it's fixed: lsmod|grep pcspk pcspkr 7936 0 closing -- maks --- End Message ---
Bug#300264: marked as done (forkbomb takes down system)
Your message dated Sat, 5 Jan 2008 22:14:44 +0100 with message-id <[EMAIL PROTECTED]> and subject line forkbomb takes down system has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kernel-image Version: 2.6.* http://www.securityfocus.com/columnists/308 http://catb.org/~esr/jargon/html/F/fork-bomb.html A simple shell script containing the line "$0 & $0 &" run by an unprivileged user can lock up the system hardcore. Not good. Jiann-Ming Su "Yeah, Lois, that'll be about as much fun as a lecture on ontological empiricism." --Peter Griffin --- End Message --- --- Begin Message --- learn to set limits, see /etc/security/limits.conf closing as not kernel trouble -- maks --- End Message ---
Bug#311358: marked as done (strange system time behaviour)
Your message dated Sat, 5 Jan 2008 22:16:35 +0100 with message-id <[EMAIL PROTECTED]> and subject line strange system time behaviour has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: presumably kernel we experience a strange behaviour of the system time which sometimes seems to be stopped, but a closer inspection by issuing the date command repeatedly reveals that the time actually is jumping back and ahead by just a couple of seconds. this happens currently once every couple of days on three machines (all Fujitsu-Siemens RX-100 Servers) running Debian Sarge with different kernel versions (2.6.7-1-386 and 2.6.8-1-686). all machines are updated regularily once a week. we found some older bug report which is already closed where such a behaviour was connected to systems which once had been upgraded from stable to testing, and which might be true for the two 2.6.8-kernels (i'm sorry that i cannot give more details, but i cannot remember definitely how those systems had been set up), but the machine running the 2.6.7-kernel was set up as sarge (testing) from the very start. with best regards Peter Walter __ Systemadministration ThinPrint GmbH Alt-Moabit 91 10559 Berlin Tel. +49 30 39493205 Fax +49 30 39493199 eMail: [EMAIL PROTECTED] --- End Message --- --- Begin Message --- Version: 2.6.23-1 timer subsystem got significantly rewritten for no-hz kernels, and thus it is most likely that this bug no longer applies. closing -- maks --- End Message ---
Bug#283245: marked as done (Sarge-testing for Sparc, 2.6.8 SMP prebuilt kernel has failing eps driver)
Your message dated Sat, 5 Jan 2008 22:03:40 +0100 with message-id <[EMAIL PROTECTED]> and subject line 2.6.8 SMP prebuilt kernel has failing eps driver has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: Prebuilt 2.6.8 SMP kernel install disks Version: 2.6.8 prebuilt as found on Sarge-testing Sparc install disks After loading the system I opted to install a factory SMP kernel. After installing the kernel I tried to boot it. The kernel was unable to boot the system. It got to the where it was supposed to load the SCSI driver (esp) and starting having malfunctions, it struggled for a time and then eventually quit. I am using Sarge - testing on an Ultra 2 with dual 200mhz CPUs Please feel free to contact me if you have any more questions or if I need to write these bug reports differently. Walt L. Williams [EMAIL PROTECTED] --- End Message --- --- Begin Message --- Version: 2.6.23-1 closing as no further answer since intial report nor any answer on ping after bug report. also esp in newer linux images got significantly rewritten thus closing. -- maks --- End Message ---
Bug#350978: marked as done (2.6.8 module loading sequence prevents mixed IDE and SATA LVM VGs)
Your message dated Sat, 5 Jan 2008 22:17:51 +0100 with message-id <[EMAIL PROTECTED]> and subject line 2.6.8 module loading sequence prevents mixed IDE and SATA LVM VGs has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: kernel Version: 2.6.8-2-686 The module loading sequence in the default initrd image loads the LVM modules before it loads the SATA modules, which make it impossible to have a VG that spans both IDE and SATA drives in a VG. It's kind of difficult to demonstrate it through log files, since LVM initialization does not make any syslog entries. Fix: to re-order the module loading so that all internal drive modules are loaded before the LVM and RAID drivers are loaded. - -- GPG key available gpg --keyserver pgp.mit.edu --recv-keys 359DBF73 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFD4YOuevfmjTWdv3MRAmErAJ0aAk64PJWNW/iXvFk+R/qywuQb8gCfeXND 4LBo6vwDtnDplgJRu9VkSIY= =owCU -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 2.6.15-1 > The module loading sequence in the default initrd image loads the LVM > modules before it loads the SATA modules, which make it impossible to > have a VG that spans both IDE and SATA drives in a VG. newer linux images no longer use initrd-tools but initramfs-tools thus this critic no longer applies. closing -- maks --- End Message ---
Bug#296593: marked as done (Installer will not load mptscsih module after aic7xxx is loaded)
Your message dated Sat, 5 Jan 2008 22:11:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Installer will not load mptscsih module after aic7xxx is loaded has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: debian-installer Version: unstable daily-build 2005-02-21 Baed on symptoms, this seems to be same issue as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107749 - (got same message in dmesg during debian install as below with redhat...) Workaround given in redhat bug report: remove adaptec card during install (lsi mpt is on-mobo). Excerpted from redhat (tm) bugzilla: Opened by (Nate Golnik) on 2003-10-22 13:11 From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716 Description of problem: Attempting to install QU2 on a Dell 1750 with an LSI MPT scsi controller for the onboard disks and a Adaptec 39160 for connecting to a Dell Powervault 220. During the install aic7xxx loads followed by mptscsih. Mptscsih fails out with the following: mptbase: Initiating ioc0 bringup ioc0: ERROR Doorbell Ack timeout (2) ioc0: ERROR Doorbell Ack timeout (2) ioc0: ERROR Diagnostic reset failed (102h) ioc0: Not Ready Warning WARNING: ioc0 did not initalize properly! (-1) Repeats for ioc1 mptbase: 2 mpt adapters found, 0 installed. pgp1IyoTLcwQi.pgp Description: PGP signature --- End Message --- --- Begin Message --- Version: 2.6.18-1 this report of ressource stealing is against an quite old linux image and thus most likely fixed as noted in the red hat bugzilla entry. if you can still reproduce with etch or lenny images please holler. happy new year -- maks --- End Message ---
Bug#286628: marked as done (Filesystem coruption. local attack for setuid root executable?)
Your message dated Sat, 5 Jan 2008 22:05:22 +0100 with message-id <[EMAIL PROTECTED]> and subject line Filesystem coruption. local attack for setuid root executable? has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: unknow Version: unknow On Debian sarge net install whit ext3 filesystem i got somme verry strange file and error. somme file read as follow: ?rwx-wS-wt 6743 1909420011 2288661400 3.7G 1962-09-28 08:23 ?r-s-wSrwt 59484 2155108859 3093106996 3.8G 1951-08-27 16:14 b-wsr-sr-x 58990 2148981355 1947303819 165, 77 1920-03-04 05:03 c-wx-w--wT 58075 3390588804 4291936288 181, 122 1992-01-03 06:27 ?--Sr--r-t 32243 3182936007 1421612276 2.7G 1961-05-16 20:05 ?rwx-wsr-t 40822 3819429815 896982909 4.0G 1930-08-30 05:12 p-wS--x--x 61104 456274484 3143202295 419M 1952-04-16 01:20 ?rwSrwSrwT 27385 3445454714 3915889634 2.8G 2009-06-27 23:08 ?r--rwxrwt 45494 1042776226 3513874223 2.7G 2015-08-01 10:46 ?-wS--x-wt 28663 2080074714 3750305767 3.6G 1989-08-16 08:13 s-ws-wSrwT 18770 1943752241 4021181408 3.7G 1918-11-18 14:58 they where all created by my user(uid 1000) Could somme exectable be crafted to have set uid bit and owner of uid 0? i was also building a cvs checkout of wine. the first build was successfull, then i make clean and make again. it stop on that error: async.c:75:19: warning: netdb.h: Value too large for defined data type async.c:83:21: warning: resolv.h: No such device i've never see somme thing like that before. additionaly logs report: hdb: dma_timer_expiry: dma status == 0x60 hdb: DMA timeout retry hdb: timeout waiting for DMA hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } hdb: drive not ready for command init_special_inode: bogus i_mode (173005) Cyclades driver 2.3.2.20 2004/02/25 18:14:16 built Nov 25 2004 04:25:23 init_special_inode: bogus i_mode (153723) init_special_inode: bogus i_mode (77527) init_special_inode: bogus i_mode (115045) init_special_inode: bogus i_mode (173735) init_special_inode: bogus i_mode (167666) init_special_inode: bogus i_mode (71477) init_special_inode: bogus i_mode (155213) Whit the DMA timer expire, i look like a hardware probleme but i've been runing other distribution before on this system and i never got surch error. --- End Message --- --- Begin Message --- closing as the kernel don't set the setuid bit on files also the dma failure looks much more then dying hardware. no furture report since initial post. -- maks --- End Message ---
Bug#298490: marked as done (kernel-image-2.6.10-1-686-smp: network interfaces down => machine needs hard reboot)
Your message dated Sat, 5 Jan 2008 22:13:37 +0100 with message-id <[EMAIL PROTECTED]> and subject line kernel-image-2.6.10-1-686-smp: network interfaces down => machine needs hard reboot has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kernel-image-2.6.10-1-686-smp Severity: normal When gvpe (a vpn daemon using a tun-device under linux) exits (e.g. by kill -9 or SIGINT, which cases the daemon to simply exit without doing anything to the tun device it has open) I get these messages in a loop: unregister_netdevice: waiting for vpn0 to become free. Usage count = 23 and gvpe doesn't exit (cannot be killed with -9 even). ifconfig -a or ip link ls both hang and cannot be killed either and the machine hangs when trying to reboot. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (700, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-rc2 Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) --- End Message --- --- Begin Message --- Version: 2.6.18-1 usage count of the tun network module has been fixed since, closing. -- maks --- End Message ---
Bug#297231: marked as done (hotplug failure trying to load rtc on sis746 based machines)
Your message dated Sat, 5 Jan 2008 22:12:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line hotplug failure trying to load rtc on sis746 based machines has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: hotplug Version: 0.0.20040329-17 I have an FIC brand AMD K7 sis746 based mainboard and I've discovered that /etc/hotplug/isapnp.rc determines that it needs to load the rtc driver and that doesn't work, === isapnp modprobe: FATAL: Error inserting rtc (/lib/modules/2.6.10-1-k7/kernel/drivers/c har/rtc.ko): No such device rtc: can't be loaded === In my case it's /sys/bus/pnp/devices/00:03/id = PNP0b00 that generates the dependency on rtc. The only useful info from sysfs is the resources file, state = active io 0x70-0x73 irq 8 I don't know what that is, but I guess it's something that rtc is supposed to handle. For now I have blacklisted the rtc driver on this machine. Another developer ([EMAIL PROTECTED]) reports the same problem on his ECS sis746 based mainboard as well. I also have a Gigabyte sis748 (note: 74_8_) based mainboard, but it does NOT have the problem. I'm not sure if hotplug should be responsible for not loading in this case (although I'm not sure how it would determine that) or if the rtc driver needs to be enhanced to support this thing that hotplug is seeing via sysfs. What do you think? Let me know if you'd like me to try anything. Thanks, -- Matt Taggart [EMAIL PROTECTED] --- End Message --- --- Begin Message --- hotplug is long gone and udev has better mechanism to load the corresponding module, thus closing. -- maks --- End Message ---
Bug#279681: marked as done (serious problem with "Host Protected Area")
Your message dated Sat, 5 Jan 2008 22:02:23 +0100 with message-id <[EMAIL PROTECTED]> and subject line serious problem with "Host Protected Area" has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: installation-reports Debian-installer-version: sarge-i386-netinst.iso (daily 3.11.2004) from debian.de uname -a: Linux (none) 2.6.8-1-386 #1 Thu Oct 7 02:21:16 EDT 2004 i686 unknown Date: 4.11.2004 3pm Method: Boot from CD Machine: Gericom EGO MS1003 (Centrino-Notebook) Processor: Pentium M (Banias) 1,5 Ghz Memory: 512MB DDR Root Device: hda (IDE) Root Size/partition table: That's part of the problem Output of lspci and lspci -n: can't get it right now, but it has centrino chipset ide controller is piix, I think. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] (onboard ethernet, no WLAN) Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: The Notebook comes with Phoenix's cME (core Management Environment) which uses a Host Protected Area of 10GB on the Harddisk. (Fujitsu MHS2060AT 60GB). I don't want to use the Phoenix Recovery feature (for which the reserved 10GB are meant to be used) and the HPA but cannot turn it off in the BIOS. Knoppix discovers the full capacity of the drive and allows me to create partitions, filesystems in the HPA. di currently doesn't. dmesg after Knoppix boot (V3.4, Kernel 2.4.23-xfs) tells me: --snip-- hda: Host Protected Area detected. current capacity is 104041314 sectors (53269 MB) native capacity is 117210240 sectors (60011 MB) hda: Host Protected Area disabled hda: 117210240 sectors (60011 MB) [...] --snap-- whereas dmesg on a shell during the di-setup tells me: --snip-- hda: Host Protected Area detected. current capacity is 104041314 sectors (53269 MB) native capacity is 117210240 sectors (60011 MB) hda: 104041314 sectors (53269 MB) [...] --snap-- obviously the default behaviour of how to treat the HPA-"feature" differs between the knoppix and the di kernel. Unfortunately I was not able to get the di kernel to disable the HPA, too. I tried the following boot parameters: hd=7296,255,63 (which is the "native" geometry reported by fdisk on knoppix) hda=stroke (which after looking at the source of the current ide-driver should disable HPA, I think) hda=noprobe hda=stroke hda=7296,255,63 but nothing works. I have the feeling that these options aren't even passed to the ide-driver which is loaded after the 3 language settings during setup are configured. I tried to load the ide-generic module from a shell, before di loads it with modprobe ide-generic hda=stroke and some other options as mentioned above. but all of that has no effect. di still recognizes the drive as 53.something GB and does not allow me to install into the last 10GB of the disk. (btw. removing the ide-driver at this stage with modprobe -r ide-generic causes a segfault in the kernel! That's pretty ugly even if the ide module is not to be expected to be removed, anyway. While experimenting I had to do several reboots because of that.) I tried to shrink my XP-Partition and install debian into the "official" disk-space, but this causes an even more severe problem. In that case the installation goes very well at first. Everything is copied and GRUB is installed into the MBR. But after the reboot GRUB says (approximately from my memory): GRUB stage 1.5 loading GRUB, please wait... And nothing happens. Not even an error message. I can only hard-reset. Probably GRUB gets confused with the 2 drive geometries (thanks to HPA) and can't access the stage2? I have booted knoppix, mounted and chrooted the debian partition and rerun grub-install: No effect. The problem then was that the Windows XP-CD didn't boot after that for some reason(black screen after scanning hardware and the disk LED flashing for a splitsecond) which would have allowed me to reinstall the Windows-MBR. -> I had to completely reinstall XP after zeroing out the MBR!!! So, since it can be expected that more and more notebooks will be built with this nice HPA/cME-"feature" (I didn't know abou
Bug#288273: kernel-image-2.6.8-1-sparc64: ieee1394 disk problem on sparc (SunBlade
sparc fixes went into upstream, you may want to test trunk linux-images 2.6.24-rc6, see apt lines wiki.debian.org/DebianKernel thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#278822: 8139too and 3c509 hang alpha kernel hard
can you still reproduce that with an Etch debian installer image or better with a newer Lenny install image? thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#368788: marked as done (system hangs at boot while "Restoring mixer settings: ")
Your message dated Sat, 5 Jan 2008 22:19:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line system hangs at boot while "Restoring mixer settings: " has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: kernel Version: kernel-image-2.6-686 i have installed debian sarge 3.1r0a with kernel 2.6 i686 default sometimes, when booting, debian hangs while displaying the line "Restoring mixer settings: " which belongs to aumix. i think it's a problem with the modules of the sound cards, not with aumix 2.8-15. i have two soundcards: below is the output of lspci and lspci -n :00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) :00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02) :00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02) :00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02) :00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio (rev 02) :01:01.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) :01:04.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) :02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) :00:00.0 0600: 8086:1130 (rev 02) :00:01.0 0604: 8086:1131 (rev 02) :00:1e.0 0604: 8086:2418 (rev 02) :00:1f.0 0601: 8086:2410 (rev 02) :00:1f.1 0101: 8086:2411 (rev 02) :00:1f.2 0c03: 8086:2412 (rev 02) :00:1f.3 0c05: 8086:2413 (rev 02) :00:1f.5 0401: 8086:2415 (rev 02) :01:01.0 0401: 13f6:0111 (rev 10) :01:04.0 0200: 10b7:9200 (rev 78) :02:00.0 0300: 102b:0525 (rev 82) -- ___ Get your free email from http://www.keromail.com --- End Message --- --- Begin Message --- Version: 2.6.18-1 most likely fixed due to newer alsa in Etch or Lenny. if you can still reproduce in Lenny please holler loudly. thanks -- maks --- End Message ---
Bug#290827: marked as done (kernel-image-2.6.10-1-686: Module saa7134 still broken)
Your message dated Sat, 5 Jan 2008 22:08:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Re Module saa7134 still broken has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Subject: kernel-image-2.6.10-1-686: Module saa7134 still broken Package: kernel-image-2.6.10-1-686 Version: 2.6.10-3 Severity: normal *** Please type your report below this line *** Since Kernel 2.6.9 (not with kernel 2.6.8) a white noise occurs while booting just at the moment the aumix settings are being applied. It sounds like if you switch on the TV and have no TV station tuned in. As I can see after the boot by adjusting the mixer settings, the noise comes from the TV card channel. The noise disappears when starting and closing a TV application. When I start Nextview EPG (nxtvepg), which is an electronic program guide, I can hear the sound of the TV station currently tuned in. The EPG does not provide any TV screen output and should not provide any audio output either. The TV sound does not disappear when closing Nextview EPG. To get rid of it, I have to start a TV application like xawtv, MoTV or tvtime and close it. To me it seems as if the TV card sound is being switched on during the boot process, probably when loading the module. The card is a Medion with a Philips SAA7134 chip. OSS is used here. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.10-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.76 tools to create initrd image for p ii module-init-tools 3.1-pre6-1 tools for managing Linux kernel mo -- no debconf information --- End Message --- --- Begin Message --- Version: 2.6.18-1 no further report since longer time of white noise, so most likely fixed, please holler if still broken on Etch or Lenny. thanks -- maks --- End Message ---