Bug#435062: linux-image-2.6.22-1-k7: nforce2 firewire unsupported in new stack, please enable old fw stack
On Sun, Jul 29, 2007 at 05:19:53AM +0200, Mourad De Clerck wrote: After upgrading to 2.6.22, my firewire controller just stopped working altogether. It had been working perfectly in all previous versions. I was looking to manually load the old stack/sbp2 modules, but I see you chose not to include them anymore. yes they can't work both equaly on the same pci ids. I found this message from Stefan Richter that explains things a bit: The NVidia nForce2 chipset has an own FireWire controller, and that one is only supported by a gross hack in ohci1394 and at the moment unsupported in firewire-ohci. There is even a bug report in Red Hat's bugzilla where fw-ohci hung up when trying to initialize an nForce2 chip. See: http://www.ussg.iu.edu/hypermail/linux/kernel/0707.2/3700.html This is a regression for me, and all nforce2 firewire users. I believe it's also one of the reasons Linux 2.6.22 shipped with 2 firewire stacks instead of just the new one: the new one just doesn't cover all cases yet. so your bugreport needs to reach upstream, so that your chipset regains support on the new stack. this is kind of an expected fallout and no the old stack had to many shortcomings that he won't be enabled. the new stack is gaining enough momentum to have it's bug shaken out for the next release of Lenny. please file aboves report in bugzilla.kernel.org and inform us of your bug nr. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 360876
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 360876 + pending Bug#360876: linux-doc-2.6.16: Credits There were no tags set. 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 420099
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 tags 420099 moreinfo Bug#420099: Extremely slow ACPI on Thinkpad R51e Tags were: upstream Tags added: moreinfo 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#425851: marked as done (linux-image-2.6.21-1-686: 2.6.21 doesn't find HDD in VMware Workstation (2.6.20 did))
Your message dated Sun, 29 Jul 2007 11:37:04 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.21-1-686: 2.6.21 doesn't find HDD in VMware Workstation (2.6.20 did) 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) ---BeginMessage--- Package: linux-image-2.6.21-1-686 Version: 2.6.21-2 Severity: important Hi, I've installed 2.6.21 on two different VMware Workstation guests running on two different hosts and both fail to boot. They wait for a long time at Begin: Waiting for root file system... ... Then it says: ALERT! /dev/sha1 does not exist. Dropping to a shell! I have no idea how to debug this. Olaf -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.21-1-686 depends on: ii initramfs-tools [linux-initr 0.87b tools for generating an initramfs ii module-init-tools3.3-pre11-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.21-1-686 recommends: ii libc6-i6862.5-8 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.21-1-686/postinst/kimage-is-a-directory: linux-image-2.6.21-1-686/prerm/removing-running-kernel-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/lilo-initrd-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/elilo-initrd-2.6.21-1-686: true linux-image-2.6.21-1-686/postinst/depmod-error-2.6.21-1-686: false linux-image-2.6.21-1-686/postinst/old-initrd-link-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.21-1-686/preinst/abort-overwrite-2.6.21-1-686: linux-image-2.6.21-1-686/postinst/bootloader-error-2.6.21-1-686: linux-image-2.6.21-1-686/preinst/bootloader-initrd-2.6.21-1-686: true linux-image-2.6.21-1-686/postinst/old-dir-initrd-link-2.6.21-1-686: true linux-image-2.6.21-1-686/postinst/bootloader-test-error-2.6.21-1-686: linux-image-2.6.21-1-686/preinst/already-running-this-2.6.21-1-686: linux-image-2.6.21-1-686/prerm/would-invalidate-boot-loader-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/abort-install-2.6.21-1-686: linux-image-2.6.21-1-686/postinst/depmod-error-initrd-2.6.21-1-686: false linux-image-2.6.21-1-686/postinst/old-system-map-link-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/failed-to-move-modules-2.6.21-1-686: linux-image-2.6.21-1-686/preinst/initrd-2.6.21-1-686: linux-image-2.6.21-1-686/postinst/create-kimage-link-2.6.21-1-686: true linux-image-2.6.21-1-686/preinst/overwriting-modules-2.6.21-1-686: true ---End Message--- ---BeginMessage--- closing as known vmware bug, and has been fixed in version 6 of VMWare Workstation. -- maks ---End Message---
Processed: tagging 420099
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 tags 420099 - fixed-upstream Bug#420099: Extremely slow ACPI on Thinkpad R51e Tags were: fixed-upstream upstream Tags removed: fixed-upstream 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#394200: marked as done (kernel freezes (no panic), seems related to acpid)
Your message dated Sun, 29 Jul 2007 11:44:06 +0200 with message-id [EMAIL PROTECTED] and subject line kernel freezes (no panic), seems related to acpid 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) ---BeginMessage--- Package: linux-2.6 Version: 2.6.17-3 Severity: important See also: #391955 (same machine) My X40 laptop hangs itself up with both 2.6.17-2-686 and 2.6.18-1-686 kernels *without sending a kernel panic via netconsole* during the rc2.d startup sequence. lapse:~# ls /etc/rc2.d K00nstxcd@ S20cpufrequtils@ S20openbsd-inetd@ S89anacron@ K00openvpn@S20cupsys@S20postfix@S89atd@ K08vmware@ S20dbus@ S20rsync@ S89cron@ README S20dictd@ S20smartmontools@ S90vmware@ S10syslog-ng@ S20gpm@ S20ssh@S99fail2ban@ S15ibm-acpi@ S20hotkey-setup@ S20sysfsutils@ S99rc.local@ S19xdm@S20ifplugd@ S23ntp@S99rmnologin@ S20acpid@ S20laptop-mode@ S25bluetooth@ S99stop-bootlogd@ S20apt-index-watcher@ S20makedev@ S30mpd@ S20cpufreqd@ S20mixmaster@ S30squid@ With 2.6.17, the machine prints Starting printing deamon: cupsd and hangs itself up hard. No sysrq-b or ctrl-alt-del make it restart, I have to cold-cycle it (no reset button on the X40). With 2.6.18, X blanks the screen just after starting cupsd, then hangs. In both cases, the machine becomes equally unresponsive to everything. No lights flash; hard lock. If I boot into single-mode and start acpid manually, then reboot, it freezes during the reboot as well. It shuts down processes and then says Will now reboot followed by Rebooting system and hangs right there and requires a cold-cycle. If I move xdm to S99, where it is normally, or even just S21, the boot process gets past cupsd and X starts fine, and it does not hang itself up on reboot. The problem does *not* occur with 2.6.16-1-686, and I have always started xdm at S19. The problem with the machine freezing while starting X first appeared after the support technician replaced a defective keyboard in the middle of July, so probably after the 2.6.17-3 upgrade; I do remember not using 2.6.17 right from the start due to madwifi-related problems a friend of mine was experiencing. In July, it was possible then to work around it by going to single-user mode and pressing ctrl-d, so I thought it was a simple timing issue. The machine would then run pretty stable. I did not have dm-crypt partitions back then. Since then, I have reinstalled the machine. The problem resurfaced two weeks ago, and I called the technician, suspecting a hardware defect. Together, we replaced the motherboard/CPU/RAM/e1000/graphics card combo, tried with and without the WLAN and Bluetooth cards, tried two mirrored harddisks, and replaced the keyboard again; the problem persists -- it is thus somewhat unlikely to be a hardware problem. Please refer to #391955 for information about the machine hardware. And please let me know whether you need more information. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP) ---End Message--- ---BeginMessage--- this seems related to a funky specific hardware model - http://blog.madduck.net/debian/2007.06.26_60-efficient-minutes-of-intel.xhtml x40 are known to work in general. closing for now in this bug cleanup round as it seems xorg related. -- maks ---End Message---
Bug#307459: marked as done (kernel-image-2.6.11-1-686: tridentfb fails to set correct resolution at boot)
Your message dated Sun, 29 Jul 2007 11:29:37 +0200 with message-id [EMAIL PROTECTED] and subject line kernel-image-2.6.11-1-686: tridentfb fails to set correct resolution at boot 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) ---BeginMessage--- Package: kernel-image-2.6.11-1-686 Version: 2.6.11-3 Severity: normal Hi, according to documentation shipped with kernel sources (kernel-sources-.../Documentation/fb/tridentfb.txt), it should be possible to set virtual consoles resolution using tridentfb driver. I used this (and many other) parameters: video=tridentfb:1024x768,bpp=16 The tridentfb is loaded, during the boot, but the resolution is always set to 640x480 and the screen is broken. Launching fbset 1024x768-60 after login, solves the problem. However, the switch -a of fbset seems not to work. I tried this on a laptop with a Trident CyberBlade XPA1i. dmesg related output is: tridentfb: framebuffer size = 16384 Kb tridentfb: :01:00.0 board found tridentfb: 1024x768 flat panel found tridentfb: fb0: Trident frame buffer device 640x480-8bpp Console: switching to colour frame buffer device 80x30 Ciao Ciao Marco -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kernel-image-2.6.11-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.78 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information ---End Message--- ---BeginMessage--- thanks for your bug report. if you still can reproduce your bug with the etch kernel 2.6.18 than please try 2.6.21 from backports.org and report back. the bug report is against an old linux kernel version and the bug report didn't get any answer on subsequent pings. thus closing for now. on a subsequent verification the bug can be reopened. regards -- maks ---End Message---
Bug#325229: marked as done (ifconfig.8.gz: down but still could ping)
Your message dated Sun, 29 Jul 2007 11:33:53 +0200 with message-id [EMAIL PROTECTED] and subject line ifconfig doesn't shut down interface 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) ---BeginMessage--- Package: net-tools Version: 1.60-15 Severity: wishlist File: /usr/share/man/man8/ifconfig.8.gz We see down This flag causes the driver for this interface to be shut down. However, we notice we were still able to successfully ping the interface afterwards. Perhaps add mention of why that may be. ---End Message--- ---BeginMessage--- closing as this is based on the linux networking model see for instance http://www.mail-archive.com/[EMAIL PROTECTED]/msg01235.html Q: Why can I ping an IP address when the interface is down? A: Linux uses a host based addressing model, IP addresses are owned by the host, not individual interfaces. So as long as the IP address is configured to some interface, we will accept packets destinated to that IP address as our's. thus closing -- maks ---End Message---
Bug#40346: marked as done (ifconfig doesn't shut down interface)
Your message dated Sun, 29 Jul 2007 11:33:53 +0200 with message-id [EMAIL PROTECTED] and subject line ifconfig doesn't shut down interface 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) ---BeginMessage--- Package: netbase Version: 3.14-3 After I shutted down an interface: ifconfig eth1:6 down I still was able to make ping to IP that card represented. Only after I killed redirector of an port from that IP to IP on local network (NAT firewall), I wasn't able nor to ping, nor to use that port. Fix it to kill interface anyway, even if somebody has listenning sockets on it. -- Bye,| Unix is simple. It just takes a Penn. | genius to understand its simplicity |Dennis Ritchie ---End Message--- ---BeginMessage--- closing as this is based on the linux networking model see for instance http://www.mail-archive.com/[EMAIL PROTECTED]/msg01235.html Q: Why can I ping an IP address when the interface is down? A: Linux uses a host based addressing model, IP addresses are owned by the host, not individual interfaces. So as long as the IP address is configured to some interface, we will accept packets destinated to that IP address as our's. thus closing -- maks ---End Message---
Bug#320056: marked as done (linux-2.6: FTBFS (ppc64): Please support the ppc64 architecture)
Your message dated Sun, 29 Jul 2007 12:05:50 +0200 with message-id [EMAIL PROTECTED] and subject line linux-2.6: FTBFS (ppc64): Please support the ppc64 architecture 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) ---BeginMessage--- Package: linux-2.6 Version: 2.6.12-1 Severity: wishlist Tags: patch When trying to build 'linux-2.6' on ppc64/unstable, I get the following error: dpkg-gencontrol -DArchitecture=ppc64 -isp \ -plinux-headers-2.6.12-1 -Pdebian/tmp-headers/ dpkg-gencontrol: error: current build architecture ppc64 does not appear in package's list (alpha amd64 arm hppa i386 ia64 m68k powerpc s390 sparc) make[3]: *** [real_stamp_headers] Error 255 make[3]: Leaving directory `/linux-2.6-2.6.12/debian/linux-source-2.6.12-none' With the attached patch 'linux-2.6' can be compiled on ppc64. The patch does the following: * Add 'ppc64' to the Architecture list in debian/templates/control.headers.in * Create Makefile.inc, config and config.ppc64 in new debian/arch/ppc64 directory Regards Andreas Jochens diff -urN ../tmp-orig/linux-2.6-2.6.12/debian/templates/control.headers.in ./debian/templates/control.headers.in --- ../tmp-orig/linux-2.6-2.6.12/debian/templates/control.headers.in 2005-07-26 11:21:10.0 + +++ ./debian/templates/control.headers.in 2005-07-26 07:38:25.0 + @@ -1,5 +1,5 @@ Package: [EMAIL PROTECTED]@@[EMAIL PROTECTED]@abiname@ -Architecture: alpha amd64 arm hppa i386 ia64 m68k powerpc s390 sparc +Architecture: alpha amd64 arm hppa i386 ia64 m68k powerpc ppc64 s390 sparc Section: devel Priority: optional Depends: coreutils | fileutils (= 4.0) diff -urN ../tmp-orig/linux-2.6-2.6.12/debian/arch/ppc64/Makefile.inc ./debian/arch/ppc64/Makefile.inc --- ../tmp-orig/linux-2.6-2.6.12/debian/arch/ppc64/Makefile.inc 1970-01-01 00:00:00.0 + +++ ./debian/arch/ppc64/Makefile.inc2005-07-26 11:20:16.0 + @@ -0,0 +1,6 @@ +# +# Variables +# +header_dirs = 'ppc | ppc64' +headers_subarch = ppc64 +build_subarch = ppc64 diff -urN ../tmp-orig/linux-2.6-2.6.12/debian/arch/ppc64/config.ppc64 ./debian/arch/ppc64/config.ppc64 --- ../tmp-orig/linux-2.6-2.6.12/debian/arch/ppc64/config.ppc64 1970-01-01 00:00:00.0 + +++ ./debian/arch/ppc64/config.ppc642005-07-26 11:15:42.0 + @@ -0,0 +1,3 @@ +CONFIG_6PACK=m +CONFIG_SCSI_IBMVSCSI=m +# CONFIG_MD_RAID6 is not set diff -urN ../tmp-orig/linux-2.6-2.6.12/debian/arch/ppc64/config ./debian/arch/ppc64/config --- ../tmp-orig/linux-2.6-2.6.12/debian/arch/ppc64/config 1970-01-01 00:00:00.0 + +++ ./debian/arch/ppc64/config 2005-07-26 07:32:13.0 + @@ -0,0 +1,2229 @@ +# +# Automatically generated make config: don't edit +# Linux kernel version: 2.6.12 +# Fri Jul 15 18:10:25 2005 +# +CONFIG_64BIT=y +CONFIG_MMU=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_GENERIC_CALIBRATE_DELAY=y +CONFIG_GENERIC_ISA_DMA=y +CONFIG_HAVE_DEC_LOCK=y +CONFIG_EARLY_PRINTK=y +CONFIG_COMPAT=y +CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y +CONFIG_FORCE_MAX_ZONEORDER=13 + +# +# Code maturity level options +# +CONFIG_EXPERIMENTAL=y +CONFIG_CLEAN_COMPILE=y +CONFIG_LOCK_KERNEL=y +CONFIG_INIT_ENV_ARG_LIMIT=32 + +# +# General setup +# +CONFIG_LOCALVERSION= +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_POSIX_MQUEUE=y +CONFIG_BSD_PROCESS_ACCT=y +# CONFIG_BSD_PROCESS_ACCT_V3 is not set +CONFIG_SYSCTL=y +CONFIG_AUDIT=y +CONFIG_AUDITSYSCALL=y +CONFIG_HOTPLUG=y +CONFIG_KOBJECT_UEVENT=y +# CONFIG_IKCONFIG is not set +CONFIG_CPUSETS=y +# CONFIG_EMBEDDED is not set +CONFIG_KALLSYMS=y +# CONFIG_KALLSYMS_ALL is not set +# CONFIG_KALLSYMS_EXTRA_PASS is not set +CONFIG_PRINTK=y +CONFIG_BUG=y +CONFIG_BASE_FULL=y +CONFIG_FUTEX=y +CONFIG_EPOLL=y +CONFIG_SHMEM=y +CONFIG_CC_ALIGN_FUNCTIONS=0 +CONFIG_CC_ALIGN_LABELS=0 +CONFIG_CC_ALIGN_LOOPS=0 +CONFIG_CC_ALIGN_JUMPS=0 +# CONFIG_TINY_SHMEM is not set +CONFIG_BASE_SMALL=0 + +# +# Loadable module support +# +CONFIG_MODULES=y +CONFIG_MODULE_UNLOAD=y +CONFIG_MODULE_FORCE_UNLOAD=y +CONFIG_OBSOLETE_MODPARM=y +CONFIG_MODVERSIONS=y +# CONFIG_MODULE_SRCVERSION_ALL is not set +CONFIG_KMOD=y +CONFIG_STOP_MACHINE=y +CONFIG_SYSVIPC_COMPAT=y + +# +# Platform support +# +# CONFIG_PPC_ISERIES is not set +CONFIG_PPC_MULTIPLATFORM=y +CONFIG_PPC_PSERIES=y +CONFIG_PPC_PMAC=y +CONFIG_PPC_MAPLE=y +CONFIG_PPC=y +CONFIG_PPC64=y +CONFIG_PPC_OF=y +CONFIG_ALTIVEC=y +CONFIG_PPC_SPLPAR=y +CONFIG_IBMVIO=y +CONFIG_U3_DART=y +CONFIG_MPIC_BROKEN_U3=y +CONFIG_PPC_PMAC64=y +CONFIG_BOOTX_TEXT=y +# CONFIG_POWER4_ONLY is
Bug#297086: marked as done (kernel-source-2.6.10: drivers/block/pktcdvd.c : no device number specified)
Your message dated Sun, 29 Jul 2007 11:24:34 +0200 with message-id [EMAIL PROTECTED] and subject line kernel-source-2.6.10: drivers/block/pktcdvd.c : no device number specified 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) ---BeginMessage--- Package: kernel-source-2.6.10 Version: 2.6.10-5 Severity: normal Hello ! I just did notice that the new/old packet writing support doesn't provide it's own device major number, namely 97, so the whole stuff is unusable. Just adding pkt_major = 97; after the beginning of int pkt_init(void) does the trick. Could it be fixed, or would there be a better way to fix it ? Thanks Vincent Fourmond -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.15-5 The GNU assembler, linker and bina ii bzip2 1.0.2-5high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.16-1 -- upstream author says: Changing the driver to use dynamic device numbers was one of the many changes that were made in order to have the driver accepted into the mainline kernel. -- thus closing. -- maks ---End Message---
Bug#410939: marked as done (linux-image-2.6.18-3-686: capabilities as kernel module)
Your message dated Sun, 29 Jul 2007 12:43:59 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.18-3-686: capabilities as kernel module 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) ---BeginMessage--- Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 Severity: wishlist I've installed clamav and I've wanted to enable dazuko module (this module is needed to scan your every file you open or use). I've downloaded the debian package from dazuko site and i've given the following input m-a a-i dazuko But i've got this message. error: capabilities are built-in to the kernel; you will need to recompile a kernel with capabilities as a kernel module Unless it create stability or security problems, for the next release can you compile capabilities as module? Thanks -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-10 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: -- Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada14feb07 ---End Message--- ---BeginMessage--- this has been discsussed repeatably in the past and always rejected as an modular CONFIG_SECURITY_CAPABILITIES has bad security implications. tell the dazuko guys to get their stuff upstream. thus closing -- maks ---End Message---
Bug#392015: marked as done (Request for openvz patched binary kernels.)
Your message dated Sun, 29 Jul 2007 13:13:05 +0200 with message-id [EMAIL PROTECTED] and subject line Request for openvz patched binary kernels. 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) ---BeginMessage--- Package: linux-latest-2.6 Severity: wishlist Hi I would like to have kernel binary images with the openvz patch applied. I have just a few days ago added support for 2.6.18 to the kernel-patch-openvz and I have verified that it build on at least i386 (actually 686). I did a make menuconfig before building in order to verify that openvz is actually enabled and it was. Do you need to handle that in a special way? I have seen that such binary packages exist for example vserver (that I'm also the maintainer of) and support for openvz would be really nice. Upstream would be very happy to have that support in Debian as well. The kernel-patch-openvz works on i386 (including all subarches), amd64 and ia64. So my question is: 1) Can this be added? 2) Do you want a patch (I'm not fully sure how to create that as it seem to follow some special rules...)? 3) Do you think it is possible to get this kind of binary packages in before etch is out? Please tell me what you think about this, if you have some special rules, and what I can help with to get this done. Regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- ---End Message--- ---BeginMessage--- the kernel team is already serving prebuild vserver patches. the feature list of openvz and vserver seems quite similar i thus fail to see a compelling arg to have more flavours to take care of. push it upstream with the container patches. see also - http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines closing in this round of kernel bug cleanup. -- maks ---End Message---
Bug#389693: marked as done (linux-image-2.6.18-1-powerpc: enable CONFIG_PMAC_BACKLIGHT_LEGACY on powerpc builds)
Your message dated Sun, 29 Jul 2007 13:16:06 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.18-1-powerpc: enable CONFIG_PMAC_BACKLIGHT_LEGACY on powerpc builds 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) ---BeginMessage--- Package: linux-image-2.6.18-1-powerpc Version: 2.6.18-1 Severity: wishlist On debian kernel CONFIG_PMAC_BACKLIGHT_LEGACY isn't set, which prevents pbbuttonsd (a daemon used to control display and keyboard backlight, sound, to manage power management etc.) to control the display backlight. I guess it should switch to new pmu syscall, but in the meanwhile could this config option be enabled ? Regards, -- Yves-Alexis Perez -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.18-1-powerpc depends on: ii mkvmlinuz 24 create a kernel to boot a PowerPC ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD linux-image-2.6.18-1-powerpc recommends no packages. -- debconf information: linux-image-2.6.18-1-powerpc/postinst/old-dir-initrd-link-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.18-1-powerpc/postinst/bootloader-error-2.6.18-1-powerpc: linux-image-2.6.18-1-powerpc/postinst/old-initrd-link-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/preinst/already-running-this-2.6.18-1-powerpc: linux-image-2.6.18-1-powerpc/postinst/depmod-error-initrd-2.6.18-1-powerpc: false linux-image-2.6.18-1-powerpc/postinst/bootloader-test-error-2.6.18-1-powerpc: linux-image-2.6.18-1-powerpc/preinst/bootloader-initrd-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.18-1-powerpc/preinst/lilo-initrd-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/prerm/would-invalidate-boot-loader-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/preinst/abort-install-2.6.18-1-powerpc: linux-image-2.6.18-1-powerpc/preinst/abort-overwrite-2.6.18-1-powerpc: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-1-powerpc/preinst/initrd-2.6.18-1-powerpc: linux-image-2.6.18-1-powerpc/preinst/elilo-initrd-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/postinst/old-system-map-link-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/preinst/overwriting-modules-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/postinst/create-kimage-link-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/prerm/removing-running-kernel-2.6.18-1-powerpc: true linux-image-2.6.18-1-powerpc/preinst/failed-to-move-modules-2.6.18-1-powerpc: linux-image-2.6.18-1-powerpc/postinst/depmod-error-2.6.18-1-powerpc: false ---End Message--- ---BeginMessage--- A new pbbuttonsd (0.7.9) with sysfs backend has been uploaded to unstable, so I guess there's no need for this option anymore. You can close the bug if you want. doing, thanks for report. -- maks ---End Message---
Bug#412098: marked as done (no files bigger than 1GB possible on udf-Filesystems)
Your message dated Sun, 29 Jul 2007 12:46:28 +0200 with message-id [EMAIL PROTECTED] and subject line no files bigger than 1GB possible on udf-Filesystems 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) ---BeginMessage--- Package: kernel-image-2.6-k7 Version: 101sarge1 2.6.18+5 Severity: wishlist Since http://www.debian.org/security/2006/dsa-1184 it is not possible to write files larger than 1GB on udf-Filesystems, both on sarge and etch. ( udf-deadlock.dpatch [SECURITY] Fix possible UDF deadlock and memory corruption See CVE-2006-4145 ) This decreases the funktionality of udf-media especially for backup issues. ---End Message--- ---BeginMessage--- Version: 2.6.22 fixed upstream, see commit 31170b6ad4ebe6c43c1cc3b8112274cf59474de0 thus closing -- maks ---End Message---
Bug#435088: linux-image-2.6.17-2-amd64: module bcm43xx cannot load firmware any more
Package: linux-image-2.6.17-2-amd64 Version: linux-image-2.6.17-2-amd64 Severity: normal -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Dear maintainers, after upgrading to the last kernel-version (from 2.6.17-1-amd64-k8 to 2.6.17-2-amd64) it is no more possible , to activate the broadcom wirelesscard AeroOne54g which is normally the kernel-driver bcm43xx. The module itself can be loaded, but refuses to load the firmware bcm43xx_microcode5.fw. I installed firmware new, with no success. The firmware is installed below /usr/lib/hotplug/firmware, and additionally /lib/firmware (as it does by bcm43xx-fwcutter) Please let me know, if you need more information. Hint: In the former kernel it worked fine and there was nothing else changed ! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399722: marked as done (linux-image-2.6.18-2-686: please enable NF_CONNTRACK_IPV6)
Your message dated Sun, 29 Jul 2007 13:08:56 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.18-2-686: please enable NF_CONNTRACK_IPV6 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) ---BeginMessage--- Package: linux-image-2.6.18-2-686 Version: 2.6.18-5 Severity: wishlist Hello, Please enable NF_CONNTRACK_IPV6 feature to support tracking of ipv6 packets. -- With best wishes Dmitry Baryshkov -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-2-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-2-686 depends on: ii initramfs-tools [linux-initra 0.85b tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-2-686 recommends: ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i -- debconf information excluded ---End Message--- ---BeginMessage--- Version: 2.6.20 enabled since aboves version, thus available in backports.org too. closing -- maks ---End Message---
Processed: fixed 412098 in 2.6.22-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 412098 2.6.22-1 Bug#412098: no files bigger than 1GB possible on udf-Filesystems Bug marked as fixed in version 2.6.22-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 349021 in 2.6.18-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 349021 2.6.18-1 Bug#349021: [amd64] Oopses (USB mass-storage?) Bug marked as fixed in version 2.6.18-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 349067 in 2.6.21-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 349067 2.6.21-1 Bug#349067: flavours file missing Bug marked as fixed in version 2.6.21-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 347147 in 2.6.21-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 347147 2.6.21-1 Bug#347147: kernel-headers-2.6: asm/param.h includes linux/autoconf.h Bug marked as fixed in version 2.6.21-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 399722 in 2.6.20-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 399722 2.6.20-1 Bug#399722: linux-image-2.6.18-2-686: please enable NF_CONNTRACK_IPV6 Bug marked as fixed in version 2.6.20-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-2.6_2.6.22-3_powerpc.changes
linux-2.6_2.6.22-3_powerpc.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.22-3.dsc linux-2.6_2.6.22-3.diff.gz linux-doc-2.6.22_2.6.22-3_all.deb linux-manual-2.6.22_2.6.22-3_all.deb linux-patch-debian-2.6.22_2.6.22-3_all.deb linux-source-2.6.22_2.6.22-3_all.deb linux-support-2.6.22-1_2.6.22-3_all.deb linux-tree-2.6.22_2.6.22-3_all.deb linux-headers-2.6.22-1-all_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-all-powerpc_2.6.22-3_powerpc.deb linux-libc-dev_2.6.22-3_powerpc.deb linux-headers-2.6.22-1_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-vserver_2.6.22-3_powerpc.deb linux-image-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb linux-image-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.22-3_powerpc.changes ACCEPTED
Accepted: linux-2.6_2.6.22-3.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.22-3.diff.gz linux-2.6_2.6.22-3.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.22-3.dsc linux-doc-2.6.22_2.6.22-3_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.22_2.6.22-3_all.deb linux-headers-2.6.22-1-all-powerpc_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-all-powerpc_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-all_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-all_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-powerpc_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-powerpc_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb linux-headers-2.6.22-1-vserver_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1-vserver_2.6.22-3_powerpc.deb linux-headers-2.6.22-1_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-1_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb linux-image-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb linux-image-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb linux-libc-dev_2.6.22-3_powerpc.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.22-3_powerpc.deb linux-manual-2.6.22_2.6.22-3_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.22_2.6.22-3_all.deb linux-patch-debian-2.6.22_2.6.22-3_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.22_2.6.22-3_all.deb linux-source-2.6.22_2.6.22-3_all.deb to pool/main/l/linux-2.6/linux-source-2.6.22_2.6.22-3_all.deb linux-support-2.6.22-1_2.6.22-3_all.deb to pool/main/l/linux-2.6/linux-support-2.6.22-1_2.6.22-3_all.deb linux-tree-2.6.22_2.6.22-3_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.22_2.6.22-3_all.deb Override entries for your package: linux-2.6_2.6.22-3.dsc - source devel linux-doc-2.6.22_2.6.22-3_all.deb - optional doc linux-headers-2.6.22-1-all-powerpc_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-all_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-powerpc_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1-vserver_2.6.22-3_powerpc.deb - optional devel linux-headers-2.6.22-1_2.6.22-3_powerpc.deb - optional devel linux-image-2.6.22-1-powerpc-miboot_2.6.22-3_powerpc.deb - optional admin linux-image-2.6.22-1-powerpc-smp_2.6.22-3_powerpc.deb - optional admin linux-image-2.6.22-1-powerpc64_2.6.22-3_powerpc.deb - optional admin linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb - optional admin linux-image-2.6.22-1-vserver-powerpc64_2.6.22-3_powerpc.deb - optional admin linux-image-2.6.22-1-vserver-powerpc_2.6.22-3_powerpc.deb - optional admin linux-libc-dev_2.6.22-3_powerpc.deb - optional devel linux-manual-2.6.22_2.6.22-3_all.deb - optional doc linux-patch-debian-2.6.22_2.6.22-3_all.deb - optional devel linux-source-2.6.22_2.6.22-3_all.deb - optional devel linux-support-2.6.22-1_2.6.22-3_all.deb - optional devel linux-tree-2.6.22_2.6.22-3_all.deb - optional devel Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435134: linux-image-2.6.22-1-alpha-smp: various modules cannot be loaded
Package: linux-image-2.6.22-1-alpha-smp Version: 2.6.22-2 Severity: normal The kernel boots, but various kernel modules cannot be loaded. Notables: module xfs: Relocation (type 17) overflow vs per_cpu__xfsstats module ipv6: Relocation (type 17) overflow vs section 32 Peter -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-rc7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.22-1-alpha-smp depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85g tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.22-1-alpha-smp recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.22-1-alpha-smp/postinst/old-system-map-link-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/postinst/bootloader-error-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/postinst/kimage-is-a-directory: linux-image-2.6.22-1-alpha-smp/preinst/elilo-initrd-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/postinst/create-kimage-link-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/prerm/removing-running-kernel-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/preinst/overwriting-modules-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/preinst/bootloader-initrd-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/postinst/depmod-error-initrd-2.6.22-1-alpha-smp: false linux-image-2.6.22-1-alpha-smp/postinst/old-initrd-link-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/preinst/initrd-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/preinst/abort-overwrite-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/postinst/depmod-error-2.6.22-1-alpha-smp: false linux-image-2.6.22-1-alpha-smp/preinst/lilo-has-ramdisk: linux-image-2.6.22-1-alpha-smp/preinst/failed-to-move-modules-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/preinst/abort-install-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/preinst/already-running-this-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/postinst/bootloader-test-error-2.6.22-1-alpha-smp: linux-image-2.6.22-1-alpha-smp/prerm/would-invalidate-boot-loader-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/postinst/old-dir-initrd-link-2.6.22-1-alpha-smp: true linux-image-2.6.22-1-alpha-smp/preinst/lilo-initrd-2.6.22-1-alpha-smp: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431657: automatic wlan connection at bootprocess on Etch only on second try
On Mon, Jul 16, 2007 at 08:44:21AM +0200, Michael Lansche wrote: before sending my bug report I read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405270 and also tried to set sleep to a higher number. But this doesn't solve the problem. May I ask for any further suggestions concerning this problem? Hi, After reading the thread on debianhelp [0], I wonder whether your problems might be related to wpa_supplicant configuration. Maybe it fails to authenticate to access point the first time during some race condition? Could you post the output of your wpa_supplicant configuration file (after stripping out sensitive information), and check whether you get any error messages from wpa in the logs (dmesg, /var/log/messages, /var/log/syslog, /var/log/kern.log). [0] http://www.debianhelp.org/node/8512 Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413279: ipw3945d: leaves a user behind after purge
tags 413279 wontfix thanks Hi Eddy, This was discussed numerous times before, and the consensus (the way I see it, at least) is that it is better to leave the user behind. There is always a possibility that there will be files owned by the user left on the system (or entries in /proc, in case of ipw3945d). If the user is removed and another user with the same uid is created later, it may lead to undesired consequences. I understand that it's a bit far fetched, but there is really no good reason, other than aesthetic, for removing it. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: ipw3945d: leaves a user behind after purge
Processing commands for [EMAIL PROTECTED]: tags 413279 wontfix Bug#413279: ipw3945d: leaves a user behind after purge There were no tags set. Tags added: wontfix thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419460: /etc/modprobe.d/ipw3945d causes drop of module parameters supplied via modprobe
Hi Sebastian, Sorry for the delayed reply. You are absolutely right, there is no good reason not to pass the options to the daemon. I'll prepare a fixed package within the next few days and ask you to test it. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #397975 # * http://bugzilla.kernel.org/show_bug.cgi?id=7201 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 397975 + fixed-upstream usertags 397975 - status-NEW usertags 397975 + status-CLOSED resolution-CODE-FIX thanks
Bug#392015: closed by maximilian attems [EMAIL PROTECTED] (Re: Request for openvz patched binary kernels.)
Hi I understand. However openvz have several advantages over vserver as it support live migration. I can see that the Xen version of the kernel has been removed with recent images. Is that one already included upstream? Regards, // Ola On Sun, Jul 29, 2007 at 11:18:03AM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report #392015: Request for openvz patched binary kernels., which was filed against the linux-2.6 package. It has been closed by maximilian attems [EMAIL PROTECTED]. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact maximilian attems [EMAIL PROTECTED] by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) From: maximilian attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Request for openvz patched binary kernels. X-Virus-Scanned: by Amavis (ClamAV) at stro.at X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on rietz.debian.org X-Spam-Level: X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 the kernel team is already serving prebuild vserver patches. the feature list of openvz and vserver seems quite similar i thus fail to see a compelling arg to have more flavours to take care of. push it upstream with the container patches. see also - http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines closing in this round of kernel bug cleanup. -- maks -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392015: closed by maximilian attems [EMAIL PROTECTED] (Re: Request for openvz patched binary kernels.)
On Sun, Jul 29, 2007 at 05:21:15PM +0200, Ola Lundqvist wrote: Hi I understand. However openvz have several advantages over vserver as it support live migration. vserver existed already in debian for longer with a patch, plus upstream is directly responsive on bugs. i guess it is the matter of beeing the first. I can see that the Xen version of the kernel has been removed with recent images. Is that one already included upstream? xen is on the way to be merged, domU is in 2.6.23 but the reason there is currently no linux xen image is that upstream provided no patch for any kernel later than 2.6.18 best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372523: marked as done (linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0))
Your message dated Sun, 29 Jul 2007 21:08:30 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0) 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) ---BeginMessage--- Package: linux-image-2.6.16-2-xen-686 Version: 2.6.16-14 Severity: critical Justification: breaks the whole system Hello, I have been using this article to set up and install my new Xen server (nice article btw) : http://www.debian-administration.org/articles/396 I did set up grub this way : title Xen 3.0 / XenLinux 2.6 root(hd0,0) kernel /xen-3.0-i386.gz noreboot module /vmlinuz-2.6.16-2-xen-686 root=/dev/md0 ro module /initrd.img-2.6.16-2-xen-686 It unfortunately dies straight when it tries to find the root RAID partition. This is my partitions layout : /dev/md0 4.6G 134M 4.3G 4% / tmpfs 443M 0 443M 0% /dev/shm /dev/hda1 177M 13M 155M 8% /boot /dev/md3 897M 8.1M 841M 1% /home /dev/md5 158G 272K 158G 1% /mnt/xen /dev/md4 449M 8.1M 417M 2% /tmp /dev/md1 9.2G 313M 8.4G 4% /usr /dev/md2 8.3G 233M 7.7G 3% /var Is there a way around this ? Thanks, Steph -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-2-xen-686 depends on: ii initramfs-tools [linux-initra 0.60 tools for generating an initramfs ii linux-modules-2.6.16-2-xen-68 2.6.16-14 Linux kernel modules 2.6.16 image ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-xen-686 recommends: ii libc6-xen 2.3.6-15 GNU C Library: Shared libraries [X -- no debconf information ---End Message--- ---BeginMessage--- different userspace ordering of devices is not a kernel bug, thus closing in this round of linux-2.6 bug cleanup. regards -- maks ---End Message---
Processed: Re: kernel: AT keyboard driver doesn't recognize some fancy Logitech keyboard keys
Processing commands for [EMAIL PROTECTED]: tags 282035 moreinfo Bug#282035: kernel: AT keyboard driver doesn't recognize some fancy Logitech keyboard keys There were no tags set. Tags added: moreinfo stop 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#282035: kernel: AT keyboard driver doesn't recognize some fancy Logitech keyboard keys
tags 282035 moreinfo stop any update on that bug with latest linux-2.6.22 in sid? thanks for your feedback -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378436: marked as done (linux-image-2.6.15-1-686: bootsplash does not work)
Your message dated Sun, 29 Jul 2007 21:03:28 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.15-1-686: bootsplash does not work 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) ---BeginMessage--- Package: linux-image-2.6.15-1-686 Version: 2.6.15-8 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I hope you will include in the next kernel-image the bootsplash support patch, or build two diffrent packages: both one with and one without the bootsplash patch support in the .deb Excuse me for my english, I'm italian. - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-686 depends on: ii initramfs-tools [linux-initra 0.68b tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i - -- debconf information: linux-image-2.6.15-1-686/preinst/abort-install-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/abort-overwrite-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/bootloader-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/would-invalidate-boot-loader-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/kimage-is-a-directory: linux-image-2.6.15-1-686/preinst/lilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-dir-initrd-link-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/overwriting-modules-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/depmod-error-initrd-2.6.15-1-686: false * linux-image-2.6.15-1-686/preinst/already-running-this-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/initrd-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/depmod-error-2.6.15-1-686: false linux-image-2.6.15-1-686/postinst/bootloader-error-2.6.15-1-686: linux-image-2.6.15-1-686/postinst/bootloader-test-error-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-686/postinst/create-kimage-link-2.6.15-1-686: true linux-image-2.6.15-1-686/prerm/removing-running-kernel-2.6.15-1-686: true linux-image-2.6.15-1-686/preinst/failed-to-move-modules-2.6.15-1-686: linux-image-2.6.15-1-686/preinst/elilo-initrd-2.6.15-1-686: true linux-image-2.6.15-1-686/postinst/old-system-map-link-2.6.15-1-686: true -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEuiStZtGWqtLzOOERAtoLAJ4yWy0OFZuJKSya71gUEp7y75TgDACfZPHb vluc6yzf4a/F3lIQC2Fm8rk= =6aM0 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- that is an userspace question and not a kernel bug, thus closing. you may want to test in testing/unstable: apt-get install usplash regards -- maks ---End Message---
Bug#291191: marked as done (kernel-source-2.6.10: avermedia firware filename)
Your message dated Sun, 29 Jul 2007 21:12:42 +0200 with message-id [EMAIL PROTECTED] and subject line kernel-source-2.6.10: avermedia firware filename 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) ---BeginMessage--- Package: kernel-source-2.6.10 Version: 2.6.10-3 Severity: wishlist I recently tried to use kernel 2.6.10 with my avermedia DVB-T card. I had trouble operating the card as the firmware which had previously installed in the correct directory was not found by the sp887x module. Reading the included perl script to fetch and install the firmware, I discovered the filename has been changed. This could have been documented in the avermedia.txt file. I believe this document patch may help others, as the avermedia DVB-T card now works with a default kernel, once the firmware is placed in the correct location. cd /usr/src/linux/Documentation/dvb/ diff -u /usr/src/linux/Documentation/dvb/avermedia.txt /usr/src/linux/Documentation/dvb/avermedia.dmm.txt --- /usr/src/linux/Documentation/dvb/avermedia.txt 2004-12-25 08:35:01.0 +1100 +++ /usr/src/linux/Documentation/dvb/avermedia.dmm.txt 2005-01-19 21:19:33.0 +1100 @@ -152,6 +152,9 @@ Please use the command get_dvb_firmware sp887x to download it. Then copy it to /usr/lib/hotplug/firmware. + Alternatively manually extract the firmware file sc_main.mc. + Then copy it to /usr/lib/hotplug/firmware/dvb-fe-sp887x.fw + Receiving DVB-T in Australia I have no experience of DVB-T in other countries other than Diff finished at Wed Jan 19 21:19:54 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-debian-dmm Locale: LANG=POSIX, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.15-5 The GNU assembler, linker and bina hi bzip2 1.0.2-1A high-quality block-sorting file hi coreutils [fileutils] 5.2.1-2The GNU core utilities hi fileutils 5.0.91-2 The GNU file management utilities -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.20-1 upstream changed the script and the location for the firmware as in /lib/firmware, thus this patch seems obsolete now. thanks anyway, closing bug report. -- maks ---End Message---
Bug#375845: marked as done (linux-source-2.6.17: Pre-emptive features not enabled in Debian kernel builds)
Your message dated Sun, 29 Jul 2007 21:06:38 +0200 with message-id [EMAIL PROTECTED] and subject line linux-source-2.6.17: Pre-emptive features not enabled in Debian kernel builds 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) ---BeginMessage--- Package: linux-source-2.6.17 Severity: wishlist Per a recent thread on the Debian-KDE mailing list questioning why the system seems to stall under heavy processing, it was pointed out that the Debian kernel builds do not enable the CONFIG_PREEMPT options. Per my config file in /boot for 2.6.16-1-686, the following options are configured: CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set On my other machine which has a 2.6.17 K7 kernel there are a couple more options. Would it be possible to create desktop kernel image packages with the CONFIG-PREEMPT options enabled? For reference, here is the thread: http://lists.debian.org/debian-kde/2006/06/msg00229.html - Nate -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) ---End Message--- ---BeginMessage--- in the past preemptive managed to trigger a *lot* of bugs and was thus highly unstable, nowadays as most distros switch to it we might reconsider at a later base. this is a duplicate bug report, there are other on this topic thus closing in this linux-2.6 bug cleanup round. regards -- maks ---End Message---
Bug#392015: closed by maximilian attems [EMAIL PROTECTED] (Re: Request for openvz patched binary kernels.)
Hi Maximilian On Sun, Jul 29, 2007 at 08:47:57PM +0200, maximilian attems wrote: On Sun, Jul 29, 2007 at 05:21:15PM +0200, Ola Lundqvist wrote: Hi I understand. However openvz have several advantages over vserver as it support live migration. vserver existed already in debian for longer with a patch, plus upstream is directly responsive on bugs. i guess it is the matter of beeing the first. Oh, yes I know. I'm the maintainer of vserver as well. And was the maintainer of the kernel patch as well. However it was not I that requested the inclusion to the kernel package, but rather my co-maintainer. I can also assure you that upstream is very responsive on bugs in the case of openvz. I can see that the Xen version of the kernel has been removed with recent images. Is that one already included upstream? xen is on the way to be merged, domU is in 2.6.23 but the reason there is currently no linux xen image is that upstream provided no patch for any kernel later than 2.6.18 I see. If I can convince upstream to give support to the Debian variant of the kernel, there is no way to get in openvz? I mean if we can remove xen, there will be plenty of room for openvz, right? :) If I get some basic instructions (more or less verify what I think I need to do to get the support working) I can help maintain that part of the kernel tree. Best regards, // Ola best regards -- maks -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering / [EMAIL PROTECTED] Annebergsslingan 37\ | [EMAIL PROTECTED] 654 65 KARLSTAD| | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394049: Problem also occurs with kernel 2.4
Hello, these error messages also appear with kernel 2.4 (in my case, kernel-image-2.4.27-1-k7). As far as I understand it, the reason for this is that the kernel tries to set a DMA mode that is too fast for the hardware to handle. On my box, the DMA mode is initially set to UDMA100 which results in these errors, and the kernel consequently lowers the DMA mode to UDMA33. Interestingly, this happens during most, but not all bootups. In some (seemingly random) cases the kernel initially selects UDMA33 and the errors stay away. I am getting these errors since I upgraded to the 2.4.27 kernel; before I was running 2.4.24 which always selected the UDMA33 mode right from the beginning. As far as I can tell the system works well in spite of the error messages; still it might be a more clean solution not to boot with a DMA mode set to a too aggresive value. Unfortunately, it does not seem to be possible to set the DMA mode with a bootprompt parameter (or am I missing something?) Greetings, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392015: closed by maximilian attems [EMAIL PROTECTED] (Re: Request for openvz patched binary kernels.)
hello ola, On Sun, Jul 29, 2007 at 10:34:42PM +0200, Ola Lundqvist wrote: snipp vserver existed already in debian for longer with a patch, plus upstream is directly responsive on bugs. i guess it is the matter of beeing the first. Oh, yes I know. I'm the maintainer of vserver as well. And was the maintainer of the kernel patch as well. However it was not I that requested the inclusion to the kernel package, but rather my co-maintainer. oh cool, didn't knew that. I can also assure you that upstream is very responsive on bugs in the case of openvz. yes they have very good devs. best way is to push it upstream :) I see. If I can convince upstream to give support to the Debian variant of the kernel, there is no way to get in openvz? I mean if we can remove xen, there will be plenty of room for openvz, right? :) If I get some basic instructions (more or less verify what I think I need to do to get the support working) I can help maintain that part of the kernel tree. you misunderstood me, the current disabling of xen is not correlated to dropping that flavour. xen merged in the kernel will allow it to be build for itself, that should happen early enough for lenny. xen has lived up with some hype and even now with kvm and lguest user will expect it for the next release. so it would be more trading against vserver, which has build itself quite a userbase inside of debian. happy hacking -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394049: Problem also occurs with kernel 2.4
hello, On Mon, Jul 30, 2007 at 01:03:45AM +0200, Jan Harnisch wrote: I am getting these errors since I upgraded to the 2.4.27 kernel; before I was running 2.4.24 which always selected the UDMA33 mode right from the beginning. as it seems easy for you to reproduce with linux-2.6 too, can you please try the latest from backports.org should be a 2.6.21 if that happen to be still bad. please reholler and we need to inform upstream. thanks + best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409019: marked as done (linux-image-2.6.18-3-686: Fails to uninstall/purge.)
Your message dated Mon, 30 Jul 2007 00:06:46 +0200 with message-id [EMAIL PROTECTED] and subject line linux-image-2.6.18-3-686: Fails to uninstall/purge. 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) ---BeginMessage--- Subject: linux-image-2.6.18-3-686: Fails to uninstall/purge. Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 Severity: normal *** Please type your report below this line *** I cannot get this package to uninstall/purge from the system. No matter what I do I continue to get the following error: dpkg: error processing linux-image-2.6.18-3-686 (--purge): subprocess post-removal script returned error exit status 128 Errors were encountered while processing: linux-image-2.6.18-3-686 I have tried reinstalling the package to attempt to get a proper install, and then trying to purge it again, with the same result. Nothing I do seems to get rid of it. Note: this error occurs only with dpkg, or with dselect as the front-end to dpkg. If I attemp apt-get --purge remove linux-image-2.6.18-3-686 instead, apt-get tells me the package is not installed. There's seems to be some sort of disconnect betwee the two, obviously. Nevertheless, I cannot get this out of my dselect queue since it always fails, and subsequent dselect runs just try it again and again. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85e tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i ---End Message--- ---BeginMessage--- Version: 2.6.18-4 should have been fixed inbetween or we had several reports from etch users, thus closing. -- maks ---End Message---
Bug#433640: I have the same problem
I found some lines in dmesg that might be related to the problem: CPI: PM-Timer IO Port: 0x4008 time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer. time.c: Detected 1794.962 MHz processor. Calibrating delay using timer specific routine.. 3593.32 BogoMIPS (lpj=7186655) Using local APIC timer interrupts. Detected 12.465 MHz APIC timer. Real Time Clock Driver v1.12ac Your time source seems to be instable or some driver is hogging interupts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410845: marked as done ([powerpc] The PCILynx firewire driver is broken on PPC machines, and should be disabled.)
Your message dated Mon, 30 Jul 2007 00:14:44 +0200 with message-id [EMAIL PROTECTED] and subject line [powerpc] The PCILynx firewire driver is broken on PPC machines, and should be disabled. 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) ---BeginMessage--- Package: linux-2.6 When I boot Debian (Etch or Sarge) on my BlueWhite PowerMac, with the old TI PCILynx firewire chip on the motherboard, the pcilynx driver crashes consistently. If I blacklist pcilynx, the crash goes away, but I have no firewire capability. https://lists.sourceforge.net/lists/listinfo/linux1394-devel Looking at the archives of the Linux1394 developers mailinglist, it appears that pcilynx on PPC hardware has been horribly broken for a long time (at least since 2004). Furthermore, it looks like support for pcilynx may be dropped entirely from the next generation of ieee1394 drivers, regardless of CPU type. I'd like to suggest that pcilynx be disabled in the Debian PPC kernels, and a note to that effect be put in the release documents, encouraging users who need firewire to avail themselves of one of the cheap OHCI1394 cards. Rick ---End Message--- ---BeginMessage--- Version: 2.6.22 due to enabling the new firewire stack and disabling the old there is no longer any pcilynx driver around thus closing. -- maks ---End Message---
Bug#433640: System lock too slow on AMD 64
I think, I found a solution: Please see http://bugzilla.kernel.org/show_bug.cgi?id=8825 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433307: linux-image-2.6-k7: results of git bisect
Package: linux-image-2.6-k7 Version: 2.6.21+8 Followup-For: Bug #433307 I've followed through with a git bisect, and homed in on the following commit (before 2.6.19): a99c19492a801013fd25ce7bab1f0f65a328a4ba is first bad commit commit a99c19492a801013fd25ce7bab1f0f65a328a4ba Author: Jamie Painter [EMAIL PROTECTED] Date: Thu Jul 27 14:17:28 2006 -0400 USB: usbnet - Add unlink_rx_urbs() call to allow for Jumbo Frames Add usbnet_unlink_rx_urbs() which can be called by mini-drivers when they change their MTU such as for Jumbo Frame support. Signed-off-by: David Hollis [EMAIL PROTECTED] Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED] :04 04 4248c6b610ebe61233e08bf6e2051c733c69245d 28b8a35b3b280711e12183a17a312c4db17c7002 M drivers So it looks like a problem with the usb ethernet connection to the cable modem. I've posted a query on the linux-usb-users mailing list, but got no replies so far. I'd appreciate any feedback on this. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) 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-k7 depends on: ii linux-image-2.6.21-2-k7 2.6.21-6 Linux 2.6.21 image on AMD K7 linux-image-2.6-k7 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 433640 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=8825
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 forwarded 433640 http://bugzilla.kernel.org/show_bug.cgi?id=8825 Bug#433640: linux-image-2.6.22-1-amd64: time runs too slow Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=8825. 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#392915: Is this fixed in 2.6.22?
Is fix for this freeze included in recent kernels? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258979: marked as done (kernel-image-2.6.7-1-686: debsums checksum mismatch)
Your message dated Mon, 30 Jul 2007 02:36:06 +0300 with message-id [EMAIL PROTECTED] and subject line Fixed 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) ---BeginMessage--- Package: kernel Severity: normal Hi, a freshly installed package yields: = # debsums -s kernel-image-2.6.7-1-686 debsums: checksum mismatch kernel-image-2.6.7-1-686 file lib/modules/2.6.7-1-686/modules.pcimap debsums: checksum mismatch kernel-image-2.6.7-1-686 file lib/modules/2.6.7-1-686/modules.dep debsums: checksum mismatch kernel-image-2.6.7-1-686 file lib/modules/2.6.7-1-686/modules.alias = Thanks for considering. bye, Roland -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (ignored: LC_ALL set to en_GB.UTF-8) ---End Message--- ---BeginMessage--- This is now fixed in etch. ---End Message---
Processed: fixed 411813 in 2.6.21-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 411813 2.6.21-1 Bug#411813: linux-2.6/alpha: math-emu built as a module, should be built-in Bug marked as fixed in version 2.6.21-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed 418344 in 2.6.21-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 fixed 418344 2.6.21-1 Bug#418344: linux-2.6: Please disable CONFIG_IP_ROUTE_MULTIPATH_CACHED as it breaks the multipath route behavior in iproute Bug#418624: multipath routing broken in etch Bug marked as fixed in version 2.6.21-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 411813 in 2.6.21-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.6 found 411813 2.6.21-1 Bug#411813: linux-2.6/alpha: math-emu built as a module, should be built-in Bug marked as found in version 2.6.21-1 and reopened. 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#392015: closed by maximilian attems [EMAIL PROTECTED] (Re: Request for openvz patched binary kernels.)
Hi Maximilian On Mon, Jul 30, 2007 at 12:03:52AM +0200, maximilian attems wrote: ...CUT... I can also assure you that upstream is very responsive on bugs in the case of openvz. yes they have very good devs. best way is to push it upstream :) I suppose you mean linux kernel upstream in this case, right? Because it is openvz upstream that want me to push this. :) I see. If I can convince upstream to give support to the Debian variant of the kernel, there is no way to get in openvz? I mean if we can remove xen, there will be plenty of room for openvz, right? :) If I get some basic instructions (more or less verify what I think I need to do to get the support working) I can help maintain that part of the kernel tree. you misunderstood me, the current disabling of xen is not correlated to dropping that flavour. xen merged in the kernel will allow it to be build for itself, that should happen early enough for lenny. When you say build for itself, do you mean as a kernel module? xen has lived up with some hype and even now with kvm and lguest user will expect it for the next release. I see. I'll check with the openvz team to see if they can build it for itself now when kvm is there. so it would be more trading against vserver, which has build itself quite a userbase inside of debian. Personally I would like to see all the techniques of virtualization in Debian: Xen, openvz, vserver and user mode linux. The reason of that is that they have their special gains and drawbacks because of how they are designed. Best regards, // Ola happy hacking -- maks -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering / [EMAIL PROTECTED] Annebergsslingan 37\ | [EMAIL PROTECTED] 654 65 KARLSTAD| | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
