Bug#292061: marked as done (kernel-image-2.6.10-i386: please disable PREEMPT)
Your message dated Sat, 25 Jul 2009 16:17:07 +0200 with message-id <20090725141707.ga18...@galadriel.inutil.org> and subject line Re: Bug#292061 closed by Nathanael Nerode (PREEMPT will remain enabled) has caused the Debian Bug report #292061, regarding kernel-image-2.6.10-i386: please disable PREEMPT to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 292061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel-image-2.6.10-i386 Severity: wishlist Hi, PREEMPT might be a nice feature for desktop users who reboot their box 3 times a day, but it should be disabled for stability reasons, especially on the SMP flavours. This concerns both 2.6.8-i386 and 2.6.10-i386 kernel images. We should seek a consensus among the kernel team members whether or not PREEMPT should be enabled, if supported by the corresponding architecture. For some concerns, see http://kerneltrap.org/node/2702 Kind regards Frederik Schueler -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7-smp Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) pgpRH8KW2Db5U.pgp Description: PGP signature --- End Message --- --- Begin Message --- On Tue, Aug 22, 2006 at 08:34:23AM +0200, Frederik Schueler wrote: > reopen 292061 > thanks > > Who gives you the authority to close this bug? Preemption has been disabled for a long time now, closing. Cheers, Moritz --- End Message ---
Bug#298334: marked as done (kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX))
Your message dated Sat, 25 Jul 2009 11:13:38 +0200 with message-id <20090725091338.ga26...@galadriel.inutil.org> and subject line Re: kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX) has caused the Debian Bug report #298334, regarding kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 298334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel-image-2.6.10-1-686 Version: 2.6.10-4 Severity: normal like the usb-audio device i have (a PDT cyberphone with mono capabilities), my Intel I440MX Cirrus Logic CS4299 (rev 6) has started being reported with volume as an INPUT device not an OUTPUT. the I440MX was not until about 2.6.9 detected as a CS4299. in 2.6.9 it was intermittently detected and reported by userspace programs as either an I440MX or a CS4299. when reported as an I440X, the volume was successfully shown on the output. after running shockwave flash and some jumbled garbage coming from the audio (my browser is running the flash plugin at 100% CPU on this 800Mhz machine and so hasn't got time to feed things like audio) resulting in ear-howling noise followed by silence, re-running kmix would definitely show up the device (now silent) as a CS4299. prior to shockwave messing things up, the device would show up as an I440MX. when running 2.6.10, it's always absolutely 100% guaranteed to show up as a CS4299 - again, 100% guaranteed to have the volume as an input. l. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux highfield 2.6.10-1-686 #1 Tue Jan 18 04:34:19 EST 2005 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages kernel-image-2.6.10-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.0-pre9-1 tools for managing Linux kernel mo -- no debconf information --- End Message --- --- Begin Message --- On Wed, Dec 24, 2008 at 04:22:02PM +0100, Moritz Muehlenhoff wrote: > reassign 298334 linux-2.6 > thanks > > On Sun, Mar 06, 2005 at 08:20:41PM +, Luke Kenneth Casson Leighton wrote: > > Package: kernel-image-2.6.10-1-686 > > Version: 2.6.10-4 > > Severity: normal > > > > > > like the usb-audio device i have (a PDT cyberphone with mono > > capabilities), my Intel I440MX Cirrus Logic CS4299 (rev 6) has started > > being reported with volume as an INPUT device not an OUTPUT. > > > > the I440MX was not until about 2.6.9 detected as a CS4299. > > > > in 2.6.9 it was intermittently detected and reported by userspace > > programs as either an I440MX or a CS4299. > > > > when reported as an I440X, the volume was successfully shown on > > the output. > > > > after running shockwave flash and some jumbled garbage coming > > from the audio (my browser is running the flash plugin at 100% > > CPU on this 800Mhz machine and so hasn't got time to feed things > > like audio) resulting in ear-howling noise followed by silence, > > re-running kmix would definitely show up the device (now silent) > > as a CS4299. > > > > prior to shockwave messing things up, the device would show up as > > an I440MX. > > > > when running 2.6.10, it's always absolutely 100% guaranteed to > > show up as a CS4299 - again, 100% guaranteed to have the volume > > as an input. > > Does this error still occur with more recent kernel versions? No further feedback, closing the bug. If anyone reencounters the problem, please reopen this bug. Cheers, Moritz --- End Message ---
Bug#298334: kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX)
reassign 298334 linux-2.6 thanks On Sun, Mar 06, 2005 at 08:20:41PM +, Luke Kenneth Casson Leighton wrote: > Package: kernel-image-2.6.10-1-686 > Version: 2.6.10-4 > Severity: normal > > > like the usb-audio device i have (a PDT cyberphone with mono > capabilities), my Intel I440MX Cirrus Logic CS4299 (rev 6) has started > being reported with volume as an INPUT device not an OUTPUT. > > the I440MX was not until about 2.6.9 detected as a CS4299. > > in 2.6.9 it was intermittently detected and reported by userspace > programs as either an I440MX or a CS4299. > > when reported as an I440X, the volume was successfully shown on > the output. > > after running shockwave flash and some jumbled garbage coming > from the audio (my browser is running the flash plugin at 100% > CPU on this 800Mhz machine and so hasn't got time to feed things > like audio) resulting in ear-howling noise followed by silence, > re-running kmix would definitely show up the device (now silent) > as a CS4299. > > prior to shockwave messing things up, the device would show up as > an I440MX. > > when running 2.6.10, it's always absolutely 100% guaranteed to > show up as a CS4299 - again, 100% guaranteed to have the volume > as an input. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX)
Processing commands for cont...@bugs.debian.org: > reassign 298334 linux-2.6 Bug#298334: kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX) Bug reassigned from package `kernel' to `linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#290474: marked as done (kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA disk)
Your message dated Mon, 05 May 2008 10:23:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line initrd-tools has been removed from Debian, closing #290474 has caused the Debian Bug report #290474, regarding kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA disk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 290474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=290474 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: kernel-image-2.6.10-1-686 Version: 2.6.10-3 Severity: critical Justification: breaks the whole system -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1) 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-rel-2 tools for managing Linux kernel mo -- no debconf information I have a Dell Optiplex computer with a SATA hard drive. Kernel 2.4 works OK with the disk in non-SATA mode. Kernel 2.6 panics on booting with the message /dev/console not found, preceded by a message from pivot_root which does not found the root partition. I tried both SATA modes in the BIOS: combination, or normal. I tried root=/dev/hda5 or root=/dev/sda5 in the Grub menu.lst file. I tried to omit initrd in this file. I tried root=probe, point to /dev/hda5 in initrd, or root=/dev/sda5. Note that /dev/[hs]da5 is in XFS mode. --- End Message --- --- Begin Message --- Version: 0.1.84.2+rm The initrd-tools package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/393092 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Lucas --- End Message ---
Bug#296579: marked as done (initrd-tools: Disabling unloading of ide modules with kernel 2.6.10)
Your message dated Mon, 05 May 2008 10:23:25 +0200 with message-id <[EMAIL PROTECTED]> and subject line initrd-tools has been removed from Debian, closing #296579 has caused the Debian Bug report #296579, regarding initrd-tools: Disabling unloading of ide modules with kernel 2.6.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 296579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296579 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: initrd-tools Version: 0.1.77 Severity: minor When booting a 2.6.10 kernel with initrd, many error messages like this are produced: ERROR: Removing 'amd74xx': Device or resource busy The problem is that kernel 2.6.10 (and probably also others) is unable to unload ide modules. This error message is very worrying for new users and I have thus made a patch (attached) for our local installation, which disables the unloading of ide modules on kernel 2.6.10. Maybe other kernels can be included in the list too. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-isgee-neptun-1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii cpio 2.5-1.2GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.2-1The Debian Almquist Shell ii util-linux2.12-10Miscellaneous system utilities -- no debconf information --- init.old2005-01-23 19:38:08.0 +0100 +++ init2005-02-23 12:46:34.0 +0100 @@ -281,6 +281,11 @@ oldstyle=$1 shift + # unloading doesn't work with kernel 2.6.10 + case $(cat /proc/version) in + "Linux version 2.6.10"*) return;; + esac + if ! [ $oldstyle ]; then mount -nt sysfs sysfs sys fi --- End Message --- --- Begin Message --- Version: 0.1.84.2+rm The initrd-tools package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/393092 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Lucas --- End Message ---
Bug#298736: marked as done (initrd-tools - mkinitrd does not find scsi driver on 2.6.10)
Your message dated Mon, 05 May 2008 10:23:25 +0200 with message-id <[EMAIL PROTECTED]> and subject line initrd-tools has been removed from Debian, closing #298736 has caused the Debian Bug report #298736, regarding initrd-tools - mkinitrd does not find scsi driver on 2.6.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 298736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298736 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: initrd-tools Version: 0.1.77 Severity: critical mkinitrd does not warn for lack of scsi lagacy proc support and produces an initrd which lacks any scsi support. Bastian -- Death, when unnecessary, is a tragic thing. -- Flint, "Requiem for Methuselah", stardate 5843.7 signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Version: 0.1.84.2+rm The initrd-tools package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/393092 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Lucas --- 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 ---
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#298287: marked as done (kernel-image-2.6.10: usb-storage troubles with iPod shuffle)
Your message dated Wed, 28 Nov 2007 00:46:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line kernel-image-2.6.10: usb-storage troubles with iPod shuffle 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-k7 Version: 2.6.10-4 Severity: normal File: kernel-image-2.6.10 Here is the dmesg output of plugging in my iPod shuffle the first time after a reboot. Mar 6 12:57:42 academia kernel: usb 4-4: new high speed USB device using ehci_hcd and address 3 Mar 6 12:57:42 academia kernel: usb 4-4: configuration #1 chosen from 2 choices Mar 6 12:57:42 academia usb.agent[8406]: Keeping default configuration with /sys//devices/pci:00/:00:10.3/usb4/4-4 Mar 6 12:57:47 academia kernel: usb 4-4: hald timed out on ep0in Mar 6 12:57:57 academia last message repeated 2 times Mar 6 12:57:57 academia hal.hotplug[8417]: timout(1 ms) waiting for /devices/pci:00/:00:10.3/usb4/4-4/4-4:1.0 Mar 6 12:57:57 academia usb.agent[8418]: usb-storage: already loaded Mar 6 12:57:58 academia kernel: scsi0 : SCSI emulation for USB Mass Storage devices Mar 6 12:58:02 academia kernel: usb 4-4: hald timed out on ep0in Mar 6 12:58:03 academia kernel: Vendor: Apple Model: iPod Rev: 2.70 Mar 6 12:58:03 academia kernel: Type: Direct-Access ANSI SCSI revision: 04 Mar 6 12:58:03 academia scsi.agent[8470]: disk at /devices/pci:00/:00:10.3/usb4/4-4/4-4:1.0/host0/target0:0:0/0:0:0:0 Mar 6 12:58:11 academia kernel: usb 4-4: hald timed out on ep0in Mar 6 12:58:26 academia last message repeated 3 times Mar 6 12:58:36 academia kernel: usb 4-4: reset high speed USB device using ehci_hcd and address 3 Mar 6 12:58:37 academia kernel: usb 4-4: scsi_eh_0 timed out on ep0in Mar 6 12:58:42 academia kernel: usb 4-4: scsi_eh_0 timed out on ep0in Mar 6 12:58:42 academia kernel: usb 4-4: reset high speed USB device using ehci_hcd and address 3 Mar 6 12:58:43 academia kernel: usb 4-4: scsi_eh_0 timed out on ep0in Mar 6 12:58:48 academia kernel: usb 4-4: scsi_eh_0 timed out on ep0in Mar 6 12:58:48 academia kernel: scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0 Mar 6 12:58:48 academia kernel: usb 4-4: USB disconnect, address 3 Mar 6 12:58:48 academia kernel: sda : READ CAPACITY failed. Mar 6 12:58:48 academia kernel: sda : status=0, message=00, host=0, driver=04 Mar 6 12:58:48 academia kernel: sda : sense not available. Mar 6 12:58:48 academia kernel: sda: assuming Write Enabled Mar 6 12:58:48 academia kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Mar 6 12:58:49 academia kernel: usb 4-4: new high speed USB device using ehci_hcd and address 4 Mar 6 12:58:50 academia kernel: usb 4-4: khubd timed out on ep0in Mar 6 12:58:55 academia kernel: usb 4-4: khubd timed out on ep0in Mar 6 12:58:55 academia kernel: usb 4-4: new high speed USB device using ehci_hcd and address 6 Mar 6 12:58:56 academia kernel: usb 4-4: khubd timed out on ep0in Mar 6 12:59:01 academia kernel: usb 4-4: khubd timed out on ep0in Mar 6 12:59:02 academia kernel: usb 4-4: new high speed USB device using ehci_hcd and address 7 Mar 6 12:59:03 academia kernel: usb 4-4: khubd timed out on ep0in M This is a dmesg output when plugging in the second time... Mar 6 13:14:18 academia kernel: usb 4-4: new high speed USB device using ehci_hcd and address 67 Mar 6 13:14:18 academia kernel: usb 4-4: configuration #1 chosen from 2 choices Mar 6 13:14:19 academia usb.agent[8729]: Keeping default configuration with /sys//devices/pci:00/:00:10.3/usb4/4-4 Mar 6 13:14:24 academia kernel: usb 4-4: hald timed out on ep0in Mar 6 13:14:34 academia last message repeated 2 times Mar 6 13:14:34 academia hal.hotplug[8740]: timout(1 ms) waiting for /devices/pci:00/:00:10.3/usb4/4-4/4-4:1.0 Mar 6 13:14:34 academia usb.agent[8741]: usb-storage: already loaded Mar 6 13:14:35 academia kernel: scsi1 : SCSI emulation for USB Mass Storage devices Mar 6 13:14:39 academia kernel: usb 4-4: hald timed out on ep0in Mar 6 13:14:40 academia kernel: Vendor: Apple Model: iPod Rev: 2.70 Mar 6 13:14:40 academia kernel: Type: Direct-Access ANSI SCSI revision: 04 Mar 6 13:14:40 academia kernel: SCSI device sda: 1000448 512-byte hdwr sectors (512 MB) Mar 6 13:14:40 academia kernel: sda: assuming Write Enabled Mar 6 13:14:40 academia kernel: SCSI device sda: 1
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) --- Begin Message --- 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 --- --- Begin Message --- 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#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) --- Begin Message --- 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 --- --- Begin Message --- 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#421078: linux-image-2.6.10: Does not find initramfs-tools
On Thu, Apr 26, 2007 at 11:28:40AM +0200, Tobias Frost wrote: > Setting up linux-image-2.6.20-1-k7 (2.6.20-3) ... > Running depmod. > Finding valid ramdisk creators. > Failed to find suitable ramdisk generation tool for kernel version > 2.6.20-1-k7 on running kernel 2.6.18 in /usr/sbin/mkinitrd.yaird > dpkg: error processing linux-image-2.6.20-1-k7 (--configure): > subprocess post-installation script returned error exit status 9 And /etc/kernel-img.conf contains what? Bastian -- The sight of death frightens them [Earthers]. -- Kras the Klingon, "Friday's Child", stardate 3497.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#421078: linux-image-2.6.10: Does not find initramfs-tools
Processing commands for [EMAIL PROTECTED]: > reassign 421078 linux-2.6 Bug#421078: linux-image-2.6.10: Does not find initramfs-tools Bug reassigned from package `linux-2.6' to `linux-2.6'. > retitle 421078 linux-image-2.6.20: Does not find initramfs-tools Bug#421078: linux-image-2.6.10: Does not find initramfs-tools Changed Bug title to linux-image-2.6.20: Does not find initramfs-tools from linux-image-2.6.10: Does not find initramfs-tools. > -- 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: Re: Bug#421078: Acknowledgement (linux-image-2.6.10: Does not find initramfs-tools)
Processing commands for [EMAIL PROTECTED]: > retitle 421078 "linux-image-2.6.20: Does not find initramfs-tools" Bug#421078: linux-image-2.6.20: Does not find initramfs-tools Changed Bug title to "linux-image-2.6.20: Does not find initramfs-tools" from linux-image-2.6.20: Does not find initramfs-tools. > 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#421078: Acknowledgement (linux-image-2.6.10: Does not find initramfs-tools)
retitle 421078 "linux-image-2.6.20: Does not find initramfs-tools" thanks Correcting typo in title -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#421078: linux-image-2.6.10: Does not find initramfs-tools
Package: linux-image-2.6.20.3 Version: 3 Severity: normal If initramfs-tools are installed, the kernel fails to install with this message: Setting up linux-image-2.6.20-1-k7 (2.6.20-3) ... Running depmod. Finding valid ramdisk creators. Failed to find suitable ramdisk generation tool for kernel version 2.6.20-1-k7 on running kernel 2.6.18 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.20-1-k7 (--configure): subprocess post-installation script returned error exit status 9 Interesting is, that it looked for yaird, but I purged yaird recently in favor for initramfs-tools. According the dependencies, initramfs-tools should be an alternaive to yaird and sufficient. dpkg -l intiramfs-tools yaird +++-===-==- ii initramfs-tools 0.87b tools for generating an initramfs pn yaird(no description available) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.20.3 depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy linux-image-2.6.20.3 recommends no packages. -- debconf information: linux-image-2.6.20.3/preinst/overwriting-modules-2.6.20.3: true linux-image-2.6.20.3/postinst/old-dir-initrd-link-2.6.20.3: true linux-image-2.6.20.3/postinst/depmod-error-initrd-2.6.20.3: false linux-image-2.6.20.3/postinst/create-kimage-link-2.6.20.3: true linux-image-2.6.20.3/preinst/abort-install-2.6.20.3: linux-image-2.6.20.3/preinst/elilo-initrd-2.6.20.3: true linux-image-2.6.20.3/preinst/lilo-initrd-2.6.20.3: true linux-image-2.6.20.3/preinst/failed-to-move-modules-2.6.20.3: linux-image-2.6.20.3/postinst/old-initrd-link-2.6.20.3: true linux-image-2.6.20.3/postinst/old-system-map-link-2.6.20.3: true linux-image-2.6.20.3/preinst/already-running-this-2.6.20.3: shared/kernel-image/really-run-bootloader: true linux-image-2.6.20.3/postinst/depmod-error-2.6.20.3: false linux-image-2.6.20.3/preinst/initrd-2.6.20.3: linux-image-2.6.20.3/postinst/kimage-is-a-directory: linux-image-2.6.20.3/prerm/removing-running-kernel-2.6.20.3: true linux-image-2.6.20.3/preinst/bootloader-initrd-2.6.20.3: true linux-image-2.6.20.3/prerm/would-invalidate-boot-loader-2.6.20.3: true linux-image-2.6.20.3/postinst/bootloader-test-error-2.6.20.3: linux-image-2.6.20.3/preinst/lilo-has-ramdisk: linux-image-2.6.20.3/postinst/bootloader-error-2.6.20.3: linux-image-2.6.20.3/preinst/abort-overwrite-2.6.20.3: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296808: marked as done (kernel-source-2.6.10: Please consider enabling reiserfs extended attributes(posix acls))
Your message dated Sat, 24 Feb 2007 01:27:18 +0100 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) --- Begin Message --- Package: kernel-source-2.6.10 Version: 2.6.10-5 Severity: wishlist Enabling the reiserfs extended attributes would be greatly appreciated, i see that this has been enabled on ext2/3. I do not know if this can break anything, but please consider it. Thank You, Jonathan -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) 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 --- --- Begin Message --- reiserfs extended attribute and posix acl support is enabled since some time. -- We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu! --- End Message ---
Bug#292318: marked as done (kernel-image-2.6.10-1-686: Disappearing header line in /proc/swaps)
Your message dated Wed, 24 Jan 2007 21:40:23 + with message-id <[EMAIL PROTECTED]> and subject line Bug#292318: fixed in linux-2.6 2.6.18.dfsg.1-9 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 Version: 2.6.10-3 Severity: minor The file /proc/swaps normally contains a header line reading something like "Filename\t\t\t\tType\t\tSize\tUsed\tPriority\n" at least that's how it appears to be generated in mm/swapfile.c. I just had a situation where this header line went missing, breaking dynswap (a dynamic swap manager designed to replace swapd). The scenario went as follows. In the /proc/swaps dumps I trimmed some whitespace for legibility and line length. - started out with a swapless system (with /proc/swaps completely empty) - added n swap files (with swapon(file, 0)) - removed the most recent n-2 swapfiles in LIFO order (using swapoff()) - removed the original swapfile - left with only the second swapfile, /proc/swaps now read: /var/tmp/dynswap/2 file320544 10112 -2 - note missing header line! - after "swapoff /var/tmp/dynswap/2", /proc/swaps was (properly) empty - then, after "swapon /var/tmp/dynswap/2", it was back to normal: Filename TypeSizeUsed Priority/var/tmp/dynswap/2 file320544 0 -18 I can reproduce the scenario with a minimum of 3 swapfiles, i.e. n=3: - swapon 1 - swapon 2 - swapon 3 - swapoff 3 - swapoff 1 - cat /proc/swaps -> missing header! -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) 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-rel-2 tools for managing Linux kernel mo -- no debconf information --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-9 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-9.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-9.diff.gz linux-2.6_2.6.18.dfsg.1-9.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-9.dsc linux-2.6_2.6.18.dfsg.1.orig.tar.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1.orig.tar.gz linux-doc-2.6.18_2.6.18.dfsg.1-9_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-9_all.deb linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-powerpc_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-all_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-powerpc-smp_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc-smp_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-powerpc64_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc64_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-powerpc_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-powerpc_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-prep_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-prep_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-vserver-powerpc64_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-vserver-powerpc64_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-vserver-powerpc_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-vserver-powerpc_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4-vserver_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4-vserver_2.6.18.dfsg.1-9_powerpc.deb linux-headers-2.6.18-4_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-4_2.6.18.dfsg.1-9_powerpc.deb linux-image-2.6.18-4-powerpc-miboot_2.6.18.dfsg.1-9_powerpc.deb to pool/main/l/linux-2.6/linux-image
Bug#292061: marked as done (kernel-image-2.6.10-i386: please disable PREEMPT)
Your message dated Mon, 21 Aug 2006 18:03:22 -0400 with message-id <[EMAIL PROTECTED]> and subject line PREEMPT will remain enabled 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-i386 Severity: wishlist Hi, PREEMPT might be a nice feature for desktop users who reboot their box 3 times a day, but it should be disabled for stability reasons, especially on the SMP flavours. This concerns both 2.6.8-i386 and 2.6.10-i386 kernel images. We should seek a consensus among the kernel team members whether or not PREEMPT should be enabled, if supported by the corresponding architecture. For some concerns, see http://kerneltrap.org/node/2702 Kind regards Frederik Schueler -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7-smp Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) pgpOv4EZdmiHo.pgp Description: PGP signature --- End Message --- --- Begin Message --- Sorry. Preempt is a lot more stable than when this bug was filed, thankfully. It will certainly be staying on, because it seems to be needed currently for some realtime applications, and we don't want to ship separate kernels just for them. Closing this bug now. Please do feel free to report any specific PREEMPT-related bugs or slowdowns, of course! If there is a documented problem in the current kernel, we want to know. -- Nathanael Nerode <[EMAIL PROTECTED]> Read it and weep. http://rawstory.com/news/2005/Text_of_Gore_speech_0116.html --- End Message ---
Bug#295245: marked as done (kernel-source-2.6.10: VIA Rhine driver leaves i/f in state which prevents re-boot)
Your message dated Thu, 27 Apr 2006 00:06:38 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line No response to ping, closing 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-source-2.6.10 Severity: normal I use a number of Mini-ITX systems as diskless workstations. These boot over Ethernet using PXELINUX. They work fine with kernel 2.6.8 but as soon as I upgraded one to 2.6.10 I found I couldn't reboot it without turning the power right off. You actually have to disconnect the power lead - it's not enough for the board just to go to its power-off state. What happens when you switch on is the BIOS doesn't seem to be able to make head or tail of the state of the ethernet interface and exits without attempting to boot. This happens 100% of the time if the previous boot used a 2.6.10 kernel. It doesn't happen if the previous kernel used was 2.6.8 or earlier. I note that the VIA-Rhine driver has had a "Massive clean-up" between kernels 2.6.8 and 2.6.10. Possibly too massive? -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-stb4 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- End Message --- --- Begin Message --- Hi, Since the original bug is reported against the 2.6.10 kernel which is not in Debian anymore, and no new information is available, I'll go ahead and close this bug. Please feel free to reopen it at any time with updated info if the problem still persists. Thanks, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC --- End Message ---
Bug#289948: marked as done (kernel-source-2.6.10: Text display is set to 80x50, but switches back to 80x25)
Your message dated Wed, 26 Apr 2006 23:57:53 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line No response to ping, closing 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-source-2.6.10 Version: 2.6.10-3 Severity: normal ..config is attached. I noticed this problem already in 2.6.9: I set the text display to 80x25 (vga=ext or according number in /etc/lilo.conf), but when I switch back from X to the console, the text is 80x25. This is annoying, because the console still "thinks" it has 50 rows, but shows only the upper 25, rendering the console completely useless as you don't see what you type. .config # # Automatically generated make config: don't edit # Linux kernel version: 2.6.10 # Wed Jan 12 00:25:27 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set 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 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set # CONFIG_X86_EMU486 is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set CONFIG_TOSHIBA=y # CONFIG_I8K is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y # CONFIG_ACPI_SLEEP is not set CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y # CONFIG_ACPI_BUTTON is not set CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set CONFIG_ACPI_TOSHIBA=y CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_X86_PM_TIMER is not set # # APM (Advanced Power Management) BIOS Support # # CONFIG_APM is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y # CONFIG_CPU_FREQ_DEBUG is not set #
Bug#301063: marked as done (kernel-source-2.6.10: emu10k driver broken in version 6 of this package)
Your message dated Sun, 23 Apr 2006 16:42:53 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line Bug#301063: kernel-source-2.6.10: emu10k driver broken in version 6 of this package 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-source-2.6.10 Version: 2.6.10-6 Severity: normal After untarring 2.6.10-6 and recompiling (w/o changing my configuration), snd no longer works. Downgrading to my previous kernel (compiled from 2.6.10-5) fixes the problem. I see the following error message on startup: Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_info_free_entry Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_unregister_oss_device Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_register_oss_device Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_ctl_register_ioctl Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_card_file_add Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_iprintf Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_unregister_device Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_device_new Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_ctl_unregister_ioctl Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_card_file_remove Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_info_unregister Mar 23 10:16:59 cavy kernel: snd_hwdep: Unknown symbol snd_register_device Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_register Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_create_module_entry Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_free_entry Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_iprintf Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_ecards_limit Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_oss_info_register Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_unregister_device Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_device_new Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_kmalloc_strdup Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_unregister Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_register_device Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_register Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_create_module_entry Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_free_entry Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_iprintf Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_ecards_limit Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_oss_info_register Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_unregister_device Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_device_new Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_kmalloc_strdup Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_info_unregister Mar 23 10:16:59 cavy kernel: snd_timer: Unknown symbol snd_register_device Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_info_register Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_info_create_module_entry Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_timer_notify Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_timer_interrupt Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_info_free_entry Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_info_get_str Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_ctl_register_ioctl Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_card_file_add Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_iprintf Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_major Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_unregister_device Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_timer_new Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_device_new Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_ctl_unregister_ioctl Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_info_create_card_entry Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_power_wait Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_device_free Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_card_file_remove Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_info_unregister Mar 23 10:16:59 cavy kernel: snd_pcm: Unknown symbol snd_device_re
Bug#301063: kernel-source-2.6.10: emu10k driver broken in version 6 of this package
Hi Itai, Are you still able to reproduce the old bug #301063 against any current Debian kernels? I've just tried inserting snd_emu10k1 module on 2.6.15-1-686, and it loaded without problems. Please send an update to the bug within two weeks, otherwise I'll assume that this bug is no longer relevant and close it. Thanks, 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#301514: marked as done (kernel-image-2.6.10-powerpc: firewall not working any longer)
Your message dated Wed, 19 Apr 2006 23:38:01 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line kernel-image-2.6.10-powerpc: firewall not working any longer 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-powerpc Version: 2.6.10-3 Severity: normal Hi, With 2.6.10-3, I cannot make my firewall working, either by hand with iptables, or with firestarter. After some experiments, it seems to be due to rules with -m state (thus passing through ipt_state I guess). When such a rule is present, I got no answer to any tcp request. DNS is passing through though. No other problem to signal, but this one is pretty annoying... -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages kernel-image-2.6.10-powerpc depends on: ii initrd-tools 0.1.77 tools to create initrd image for p ii mkvmlinuz 13 create a kernel to boot a PowerPC ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- Cedric --- End Message --- --- Begin Message --- Hi, These bugs was pinged over three months ago, no response from the submitter. I am therefore taking the liberty to close them. Cedric, if you are still experiencing them, you are more than welcome to reopen them at any time. Thanks, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC --- End Message ---
Bug#297086: kernel-source-2.6.10: drivers/block/pktcdvd.c : no device number specified
Hi Vincent,
Looking at the 2.6.10 and 2.6.16 kernel source, I see that pkt_major gets
initialized in the pkt_init() function by the following sequence:
ret = register_blkdev(pkt_major, "pktcdvd");
if (ret < 0) {
printk("pktcdvd: Unable to register block device\n");
goto out2;
}
if (!pkt_major)
pkt_major = ret;
So, pkt_major should have the correct value on exit. If it does not, you
should see some error in dmesg or kernel logs from register_blkdev. Do you
see anything like that?
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#295245: kernel-source-2.6.10: VIA Rhine driver leaves i/f in state which prevents reboot
Hi John, I wonder if you are still experiencing this bug (#295245) with any current Debian kernels. Please send an update to the bug (preferrably within two weeks) if you do, otherwise there is not much point for this bug to remain open. Thanks, 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#289948: kernel-source-2.6.10: Text display is set to 80x50, but switches back to 80x25
Hi Andreas, I've been going through the old kernel bug reports and noticed your report (289948), filed over a year ago. I'm sorry to see that nobody have tried to solve the problems you were experiencing. At this point kernel 2.6.10 is long gone from the archive, so I'd appreciate if you could tell whether you're still experiencing it with any kernel currently available in etch or unstable. Kind 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#290226: marked as done (acpi is dumb on 2.6.9-1-386 and 2.6.10-1-386 on hp/compaq nx9010)
Your message dated Sun, 16 Apr 2006 14:35:23 -0300 with message-id <[EMAIL PROTECTED]> and subject line Bug#290226: acpi is dumb on 2.6.9-1-386 and 2.6.10-1-386 on hp/compaq nx9010 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-386 Version: 101 Severity: normal I'm reporting this here as I'm not sure if I should report separate bugs for 2.6.9 and 2.6.10. My ACPI seems to be quite dumb when using these kernels. The battery status, to be specific. I booted my 2.6.10-1-386 kernel and had this: /proc/acpi/battery/BAT1 [EMAIL PROTECTED] $ cat state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 3584 mAh present voltage: 16640 mV Then I unplugged my AC cable and everything continued the same. The LCD didn't have the light lowered and proc didn't notice a change. I plugged it again, unplugged and the GNOME battery applet did notice that change, the screen got darker, but state continued the same. I left it that way for some time, the battery monitor was still showing 100%, the state proc file contained the same info as above. Then I plugged the cable again and the GNOME monitor showed 94%, the screen got brighter and state was like this: /proc/acpi/battery/BAT1 [EMAIL PROTECTED] $ cat state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 3392 mAh present voltage: 16032 mV I left it plugged and then unplugged it again after some time. Screen got darker, battery monitor showed 99% and state was like this: ~ [EMAIL PROTECTED] $ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 3552 mAh present voltage: 16224 mV This happens with 2.6.9 and 2.6.10 kernels. Does not happen with 2.6.8 ones. What kind of information can I provide to help debug this problem? I've got a compaq/hp nx9010, as I said. Some aditional info: ~ [EMAIL PROTECTED] $ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 4400 mAh last full capacity: 3584 mAh battery technology: rechargeable design voltage: 14800 mV design capacity warning: 300 mAh design capacity low: 200 mAh capacity granularity 1: 32 mAh capacity granularity 2: 32 mAh model number:30 32 4B 54 00 serial number: 38 33 31 30 00 00 00 00 00 battery type:4C 49 4F 4E 00 OEM info:4D 6F 74 20 53 61 6D 20 4F 00 ~ [EMAIL PROTECTED] $ dmesg | grep -i acpi BIOS-e820: 1df7 - 1df7c000 (ACPI data) BIOS-e820: 1df7c000 - 1df8 (ACPI NVS) ACPI: RSDP (v000 PTLTD ) @ 0x000f6ab0 ACPI: RSDT (v001 PTLTDRSDT 0x0604 LTP 0x) @ 0x1df7529b ACPI: FADT (v001 ATISalmon 0x0604 ATI 0x000f4240) @ 0x1df7bf64 ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x0604 LTP 0x0001) @ 0x1df7bfd8 ACPI: DSDT (v001ATI MS2_1535 0x0604 MSFT 0x010e) @ 0x ACPI: PM-Timer IO Port: 0x8008 ACPI: setting ELCR to 0200 (from 0420) ACPI: Subsystem revision 20041105 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT] ACPI: PCI Interrupt Link [LNK0] (IRQs 7 10) *0, disabled. ACPI: PCI Interrupt Link [LNK1] (IRQs 7 *10) ACPI: PCI Interrupt Link [LNK2] (IRQs 7 *10) ACPI: PCI Interrupt Link [LNK3] (IRQs 7 *10) ACPI: PCI Interrupt Link [LNK4] (IRQs 7 10) *0, disabled. ACPI: PCI Interrupt Link [LNK5] (IRQs 7 11) *0, disabled. ACPI: PCI Interrupt Link [LNK6] (IRQs 7 10) *0, disabled. ACPI: PCI Interrupt Link [LNK7] (IRQs *5) ACPI: PCI Interrupt Link [LNK8] (IRQs 7 10) *0, disabled. ACPI: Embedded Controller [EC0] (gpe 24) pnp: PnP ACPI init pnp: PnP ACPI: found 13 devices PnPBIOS: Disabled by ACPI PCI: Using ACPI for IRQ routing ACPI: PCI Interrupt Link [LNK6] enabled at IRQ 10 ACPI: PCI interrupt :00:08.0[A] -> GSI 10 (level, low) -> IRQ 10 ACPI wakeup devices: ACPI: (supports S0 S3 S4 S5) ACPI: PCI interrupt :00:10.0[A]: no GSI - using IRQ 0 ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 10 ACPI: PCI interrupt :00:12.0[A] -> GSI 10 (level, low) -> IRQ 10 ACPI:
Bug#290925: marked as done (kernel-source-2.6.10: Blank Screen When Using intelfb Module)
Your message dated Wed, 12 Apr 2006 23:16:41 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb 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) --- Begin Message --- Package: kernel-source-2.6.10 Version: 2.6.10-3 Severity: normal When the intelfb module is compiled into the kernel all consoles remain blank until the X server starts up. Using it as a module is not an option for non-CRT screens (see http://www.xfree86.org/~dawes/intelfb.html, which I'm assuming not to be outdated on this issue). This makes the driver unusable for laptops. The initialization seems to be OK (from dmesg): Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected an Intel 830M Chipset. agpgart: Maximum main memory to use for agp memory: 202M agpgart: Detected 892K stolen memory. agpgart: AGP aperture is 128M @ 0xe800 intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G chipsets intelfb: Version 0.9.2 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9 PCI: setting IRQ 9 as level-triggered ACPI: PCI interrupt :00:02.0[A] -> GSI 9 (level, low) -> IRQ 9 intelfb: 00:02.0: Intel(R) 830M, aperture size 128MB, stolen memory 892kB intelfb: Non-CRT device is enabled ( DVO port B ). Disabling mode switching. intelfb: Initial video mode is [EMAIL PROTECTED] I was unable to try vesa modes with a higher resolution than vga=0x311 as my BIOS doesn't support these values. This problem is similar to bug #289810, but I doubt that is directly related as vesafb doesn't figure into this particular configuration. Thanks for looking into this. Georg -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-gw1 Locale: LANG=C, LC_CTYPE=C (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 ii bzip2 1.0.2-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information --- End Message --- --- Begin Message --- On Thu, 13 Apr 2006, Georg Wittenburg wrote: Hi Juri, As mentioned in the bug report, the problems you were experiencing most likely resulted from Debian-specific modular framebuffer patches. These patches have been dropped from Debian kernels long ago, and the kernel you've originally reported the problem against is long gone too. Thus there are reasons to believe that this bug is fixed in current kernels, so I plan to close this bug report in two weeks from today (April 26th, 2006), unless you're still experiencing problems. If that's still the case, please post updated information to the bug. Please, feel free to close the bug. I'm running 2.6.15 now, which works like a charm, and don't even own the hardware in question anymore. Excellent, closing the bug. Thanks, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC --- End Message ---
Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb Module
Hi Georg, As mentioned in the bug report, the problems you were experiencing most likely resulted from Debian-specific modular framebuffer patches. These patches have been dropped from Debian kernels long ago, and the kernel you've originally reported the problem against is long gone too. Thus there are reasons to believe that this bug is fixed in current kernels, so I plan to close this bug report in two weeks from today (April 26th, 2006), unless you're still experiencing problems. If that's still the case, please post updated information to the bug. Thanks, 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#290226: acpi is dumb on 2.6.9-1-386 and 2.6.10-1-386 on hp/compaq nx9010
Hi, Can you please confirm that the problems you describe in bug 290226 are still present in the Debian kernels currently in the archive? As ACPI is under constant development, there is a chance that newer kernel will behave better with your hardware. As this bug is quite old, I currently plan to close it in two weeks from now (April 26, 2006), unless you are still experiencing problems with current kernels. 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#297627: marked as done (kernel-source-2.6.10: Please consider include rivafb as builtin)
Your message dated Thu, 23 Mar 2006 17:32:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line closed 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-source-2.6.10 Version: 2.6.10-5 Severity: wishlist Good day, Radeonfb and offb are builtin but rivafb is not. I don't know why but it seems that rivafb can't take over from offb even with video=rivafb kernel parameter. So this mean that on my 12" powerbook I can only used offb which is not so good because then I don't have any backlight control and It reduce a lot my battery's autonomy. I have recompile kernel-image-2.6.10 with CONFIG_FB_RIVA=y and it works nice. Regards. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) 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 --- --- Begin Message --- Backlight control works fine with Debian 2.6.15 on my 12" powerbook. -- Djoume SALVETTI --- End Message ---
Bug#291464: marked as done (kernel-source-2.6.10: Kernel Panic with SMP PIII as NFS Client under heavy NFS Load)
Your message dated Wed, 11 Jan 2006 19:41:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Kernel Panic with SMP PIII as NFS Client under heavy NFS Load 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) -- Received: (at submit) by bugs.debian.org; 20 Jan 2005 22:16:39 + >From [EMAIL PROTECTED] Thu Jan 20 14:16:39 2005 Return-path: <[EMAIL PROTECTED]> Received: from build.actusa.net [205.147.47.53] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CrkbW-0005K6-00; Thu, 20 Jan 2005 14:16:38 -0800 Received: from build.actusa.net ([EMAIL PROTECTED] [127.0.0.1]) by build.actusa.net (8.13.2/8.13.2/Debian-1) with ESMTP id j0KMGbVp031239 for <[EMAIL PROTECTED]>; Thu, 20 Jan 2005 14:16:37 -0800 Received: (from [EMAIL PROTECTED]) by build.actusa.net (8.13.2/8.13.2/Submit) id j0KMGbdK031238 for [EMAIL PROTECTED]; Thu, 20 Jan 2005 14:16:37 -0800 Message-Id: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Stuart Sheldon <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: Kernel Panic with SMP PIII as NFS Client under heavy NFS Load X-Mailer: reportbug 3.2 Date: Thu, 20 Jan 2005 14:00:09 -0800 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.10 Version: 2.6.10-4 Severity: important -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-actusa Locale: LANG=C, LC_CTYPE=C (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 ii bzip2 1.0.2-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities -- no debconf information System kernel is installed on displays following message on screen: Kernel panic - not syncing: Attempting to free lock with active block list References found in this thread from linux-kernel list: http://seclists.org/lists/linux-kernel/2005/Jan/1198.html This bug report is being generated from our main build machine, not system that was kernel panic'ing. Thread was not clear if this was resolved with the patch listed, but problem still exists in unpatched kernel-source-2.6.10-4. Please advise if I can be of any assistance. Stu Sheldon --- Received: (at 291464-done) by bugs.debian.org; 11 Jan 2006 18:50:50 + >From [EMAIL PROTECTED] Wed Jan 11 10:50:50 2006 Return-path: <[EMAIL PROTECTED]> Received: from baikonur.stro.at ([213.239.196.228]) by spohr.debian.org with esmtp (Exim 4.50) id 1EwkuW-DF-It for [EMAIL PROTECTED]; Wed, 11 Jan 2006 10:41:28 -0800 Received: from nancy (stallburg.stro.at [128.131.216.190]) by baikonur.stro.at (Postfix) with ESMTP id 431095C00B for <[EMAIL PROTECTED]>; Wed, 11 Jan 2006 19:42:09 +0100 (CET) Received: from max by nancy with local (Exim 4.60) (envelope-from <[EMAIL PROTECTED]>) id 1EwkuK-0005kA-3V for [EMAIL PROTECTED]; Wed, 11 Jan 2006 19:41:16 +0100 Date: Wed, 11 Jan 2006 19:41:16 +0100 From: maximilian attems <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Kernel Panic with SMP PIII as NFS Client under heavy NFS Load Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.11 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 spohr.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 On Wed, 11 Jan 2006, Stuart Sheldon wrote: > This is a very old bug report... It has been resolved to my knowledge. > > Stu > i
Bug#317787: marked as done (kernel-source-2.6.10: md memory leak)
Your message dated Wed, 11 Jan 2006 13:16:35 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing all those bug reports, as they where erroneously labeled closed-in-NMU. 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) -- Received: (at submit) by bugs.debian.org; 11 Jul 2005 13:41:36 + >From [EMAIL PROTECTED] Mon Jul 11 06:41:36 2005 Return-path: <[EMAIL PROTECTED]> Received: from ahmler5.mail.eds.com [192.85.154.70] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DryXQ-00064X-00; Mon, 11 Jul 2005 06:41:36 -0700 Received: from ahmlir4.mail.eds.com (ahmlir4-2.mail.eds.com [192.85.154.134]) by ahmler5.mail.eds.com (8.13.2/8.12.10) with ESMTP id j6BDf2x7027955 for <[EMAIL PROTECTED]>; Mon, 11 Jul 2005 09:41:05 -0400 Received: from ahmlir4.mail.eds.com (localhost [127.0.0.1]) by ahmlir4.mail.eds.com (8.13.4/8.12.10) with ESMTP id j6BDeROI011737; Mon, 11 Jul 2005 09:40:27 -0400 Received: from hamster.dsddi.eds.com (hamster.dsddi.eds.com [130.175.220.28]) by ahmlir4.mail.eds.com (8.13.4/8.12.10) with ESMTP id j6BDeRcm011732; Mon, 11 Jul 2005 09:40:27 -0400 Received: from hamster.dsddi.eds.com ([EMAIL PROTECTED] [127.0.0.1]) by hamster.dsddi.eds.com (8.13.4/8.13.4/Debian-3) with ESMTP id j6BDeLpk030430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Jul 2005 09:40:21 -0400 Received: (from [EMAIL PROTECTED]) by hamster.dsddi.eds.com (8.13.4/8.13.4/Submit) id j6BDeLms030427; Mon, 11 Jul 2005 09:40:21 -0400 Message-Id: <[EMAIL PROTECTED]> X-Authentication-Warning: hamster.dsddi.eds.com: czhc72 set sender to [EMAIL PROTECTED] using -f Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "R. Scott Bailey" <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: md memory leak X-Mailer: reportbug 3.15 Date: Mon, 11 Jul 2005 09:40:21 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.10 Version: 2.6.10-5 Severity: important Tags: patch The attached patch against 2.6.10-5, due to Neil Brown, corrects a problem in 2.6.10 which causes the md driver to leak bios -- eventually resulting in a OOM condition. The problem appears to have been corrected upstream for 2.6.11, but my system hates that version :-) so I would like to see this backported if you release additional 2.6.10 updates. I have been running this patch on my system for over 4 days with no sign of the slab growth that was forcing me to reboot a couple times a week previously. Thanks, Scott Bailey [EMAIL PROTECTED] --- drivers/md/md.c.orig2005-02-07 15:44:50.0 -0500 +++ drivers/md/md.c 2005-07-06 10:55:56.0 -0400 @@ -336,8 +336,6 @@ struct completion event; int ret; - bio_get(bio); - rw |= (1 << BIO_RW_SYNC); bio->bi_bdev = bdev; -- System Information: Debian Release: testing/unstable Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-hamster.5c Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.15-7 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.10 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6.1-dev [libc6-dev] 2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the "make" util -- no debconf information --- Received: (at 317787-done) by bugs.debian.org; 11 Jan 2006 12:18:06 + >From [EMAIL PROTECTED] Wed Jan 11 04:18:06 2006 Return-path: <[EMAIL PROTECTED]> Received: from smtp8.wanadoo.fr ([193.252.22.23]) by spohr.debian.org with esmtp (Exim 4.50)
Bug#289810: marked as done (kernel-source-2.6.10: blank screen with static vesafb driver)
Your message dated Wed, 11 Jan 2006 13:16:35 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing all those bug reports, as they where erroneously labeled closed-in-NMU. 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) -- Received: (at submit) by bugs.debian.org; 11 Jan 2005 07:50:09 + >From [EMAIL PROTECTED] Mon Jan 10 23:50:09 2005 Return-path: <[EMAIL PROTECTED]> Received: from k1.dinoex.de [80.237.200.138] (root) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CoGn2-0003JV-00; Mon, 10 Jan 2005 23:50:08 -0800 Received: from eris.sebi.org ([EMAIL PROTECTED] [80.237.237.122]) by k1.dinoex.de (8.13.2/8.13.1) with ESMTP id j0B7nc6L098370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <[EMAIL PROTECTED]>; Tue, 11 Jan 2005 08:49:44 +0100 (CET) (envelope-from [EMAIL PROTECTED]) X-MDaemon-Deliver-To: <[EMAIL PROTECTED]> Received: from eris.sebi.org ([EMAIL PROTECTED] [127.0.0.1]) by eris.sebi.org (8.13.1/8.13.1/Debian-15) with ESMTP id j0B7nbld004342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Jan 2005 08:49:38 +0100 Received: (from [EMAIL PROTECTED]) by eris.sebi.org (8.13.1/8.13.1/Submit) id j0B7nbco004339; Tue, 11 Jan 2005 08:49:37 +0100 Date: Tue, 11 Jan 2005 08:49:37 +0100 From: Sebastian Bork <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: blank screen with static vesafb driver Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 3.1 X-PGP: 1024D/42DFB65F D4B1 7EC8 8674 EEAD D97F 36E3 6BF4 5152 42DF B65F User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.10 Version: 2.6.10-3 Severity: important Again the vesafb driver does only lead to a blank screen when compiled in statically, just like the bug pending for kernel-source-2.6.9. The problem exists within the Debian patches only. When I use the vesafb.c out of the kernel.org sources, everything works as expected. Please fix that patch to make the next kernel source package usable with vesafb again! It's a pity the Debian kernels are unusable for weeks now. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) 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-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information --- Received: (at 289810-done) by bugs.debian.org; 11 Jan 2006 12:18:08 + >From [EMAIL PROTECTED] Wed Jan 11 04:18:06 2006 Return-path: <[EMAIL PROTECTED]> Received: from smtp8.wanadoo.fr ([193.252.22.23]) by spohr.debian.org with esmtp (Exim 4.50) id 1EwevW-0003iZ-4B for [EMAIL PROTECTED]; Wed, 11 Jan 2006 04:18:06 -0800 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0802.wanadoo.fr (SMTP Server) with ESMTP id 5A6D91C00221 for <[EMAIL PROTECTED]>; Wed, 11 Jan 2006 13:17:35 +0100 (CET) Received: from pegasos (AStrasbourg-251-1-48-86.w82-126.abo.wanadoo.fr [82.126.221.86]) by mwinf0802.wanadoo.fr (SMTP Server) with ESMTP id 3AC9C1C00204; Wed, 11 Jan 2006 13:17:35 +0100 (CET) X-ME-UUID: [EMAIL PROTECTED] Received: from sven by pegasos with local (Exim 4.50) id 1Eweu9-0001um-0K; Wed, 11 Jan 2006 13:16:41 +0100 Date: Wed, 11 Jan 2006 13:16:35 +0100 To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Closing all those bug reports, as they where erroneously labeled closed-in-NMU. Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=
Bug#296955: marked as done (kernel-image-2.6.10-powerpc: ADT7467 bad fan speed)
Your message dated Wed, 11 Jan 2006 12:42:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line We believe this bug is closed in 2.6.15-2, please confirm
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)
--
Received: (at submit) by bugs.debian.org; 25 Feb 2005 23:24:17 +
>From [EMAIL PROTECTED] Fri Feb 25 15:24:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from lns-th2-4f-81-56-240-53.adsl.proxad.net (localhost.localdomain)
[81.56.240.53]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D4ooj-0002qw-00; Fri, 25 Feb 2005 15:24:17 -0800
Received: from localhost ([127.0.0.1] helo=localhost.localdomain)
by localhost.localdomain with esmtp (Exim 4.44)
id 1D4oof-0002e5-U4; Sat, 26 Feb 2005 00:24:13 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: =?utf-8?q?Beno=C3=AEt_Dejean?= <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-image-2.6.10-powerpc: ADT7467 bad fan speed
Reply-To: [EMAIL PROTECTED]
X-Mailer: reportbug 3.8
Date: Sat, 26 Feb 2005 00:24:13 +0100
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kernel-image-2.6.10-powerpc
Version: 2.6.10-3
Severity: normal
I've installed 2.6.10 tonight and the fan behaviour changed. With
2.6.9, fan speed is {0, 128, 255}. Fan speed is usually 0 when idle or
with low charge @ half cpu speed (533MHz on my ibook). With 2.6.10,
i've noticed that my fan now run at speed 64. At speed 64, it makes a
strange noise like it's running to slow. And even when idle, fan never
stops.
booting 2.6.10 :
adt746x: Thermostat bus: 1, address: 0x2e, limit_adjust: 0, fan_speed:-1
adt746x: ADT7467 initializing
adt746x: Lowering max temperatures from 69, 92, 101 to 70, 50, 70
'70, 50, 70' looks buggy.
Thanks.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.10-powerpc
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to fr_FR.UTF-8)
Versions of packages kernel-image-2.6.10-powerpc depends on:
ii initrd-tools 0.1.76 tools to create initrd image for p
ii mkvmlinuz 12 create a kernel to boot a PowerPC
ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo
-- no debconf information
---
Received: (at 296955-done) by bugs.debian.org; 11 Jan 2006 11:43:46 +
>From [EMAIL PROTECTED] Wed Jan 11 03:43:46 2006
Return-path: <[EMAIL PROTECTED]>
Received: from smtp12.wanadoo.fr ([193.252.22.20])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EweOH-0004eM-UH
for [EMAIL PROTECTED]; Wed, 11 Jan 2006 03:43:46 -0800
Received: from me-wanadoo.net (localhost [127.0.0.1])
by mwinf1209.wanadoo.fr (SMTP Server) with ESMTP id 055371C0007E
for <[EMAIL PROTECTED]>; Wed, 11 Jan 2006 12:43:15 +0100 (CET)
Received: from pegasos (AStrasbourg-251-1-48-86.w82-126.abo.wanadoo.fr
[82.126.221.86])
by mwinf1209.wanadoo.fr (SMTP Server) with ESMTP id D49D51C00079;
Wed, 11 Jan 2006 12:43:14 +0100 (CET)
X-ME-UUID: [EMAIL PROTECTED]
Received: from sven by pegasos with local (Exim 4.50)
id 1EweMk-0001dw-A2; Wed, 11 Jan 2006 12:42:10 +0100
Date: Wed, 11 Jan 2006 12:42:05 +0100
To: [EMAIL PROTECTED],
=?iso-8859-1?Q?Beno=EEt?= Dejean <[EMAIL PROTECTED]>
Subject: We believe this bug is closed in 2.6.15-2, please confirm
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
From: Sven Luther <[EMAIL PROTECTED]>
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00,RCVD_IN_SORBS
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Hi Benoit, ...
I believe this bug has been fixed in the latest 2.6.15-2 kernel curren
Bug#281912: udev: Fails to re-created FireWire CDROM device node after reconnecting: Still Present in 2.6.10
Hi David! On Monday 02 January 2006 21:24, David Schmitt wrote: > Dear Georg! > > Could you please retest with a current kernel (testing:2.6.12, > unstable:2.6.14) and a current udev (>= 0.076). > > Using initramfs-tools for creating the initrd is probably a good idea too. Unfortunately, I don't have the hardware available for testing anymore and thus can't tell whether the bug still exists in current kernels. I'm sorry. Nevertheless, thank you very much for spending time on this issue. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgpT1OhhP5tPI.pgp Description: PGP signature
Bug#281912: udev: Fails to re-created FireWire CDROM device node after reconnecting: Still Present in 2.6.10
Dear Georg! Could you please retest with a current kernel (testing:2.6.12, unstable:2.6.14) and a current udev (>= 0.076). Using initramfs-tools for creating the initrd is probably a good idea too. Thanks for your time and work, David -- You can have your application built cheaply, quickly, or well. Pick two. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324368: marked as done (kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h))
Your message dated Sat, 12 Nov 2005 01:18:48 +0100 with message-id <[EMAIL PROTECTED]> and subject line kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h) 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) -- Received: (at submit) by bugs.debian.org; 21 Aug 2005 20:17:52 + >From [EMAIL PROTECTED] Sun Aug 21 13:17:52 2005 Return-path: <[EMAIL PROTECTED]> Received: from postfix3-1.free.fr [213.228.0.44] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E6wGN-0005hN-00; Sun, 21 Aug 2005 13:17:51 -0700 Received: from localhost.localdomain (unknown [62.147.111.218]) by postfix3-1.free.fr (Postfix) with ESMTP id 97D561734E0 for <[EMAIL PROTECTED]>; Sun, 21 Aug 2005 22:17:49 +0200 (CEST) Received: by localhost.localdomain (Postfix, from userid 1000) id B0ED85AA87; Sun, 21 Aug 2005 21:26:13 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alexandre Pineau <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h) X-Mailer: reportbug 3.8 Date: Sun, 21 Aug 2005 21:26:13 +0200 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: kernel-source-2.6.10 Version: 2.6.10-6 Severity: important I cannot build the kernel 2.6.10 with gcc 4.0.1-3 and linux-kernel-headers_2.6.13+0rc3-1.1_i386.deb. I have the following error: In file included from drivers/video/fbmem.c:48: include/linux/fb.h:860: error: array type has incomplete element type drivers/video/fbmem.c: In function 'fb_get_buffer_offset': drivers/video/fbmem.c:178: warning: pointer targets in initialization differ in signedness make[2]: *** [drivers/video/fbmem.o] Error 1 I dont know if it's an issue in gcc, in the kernel or in kernel headers. Regards, Alexandre Pineau -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.16.1-2 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 --- Received: (at 324368-done) by bugs.debian.org; 12 Nov 2005 00:18:55 + >From [EMAIL PROTECTED] Fri Nov 11 16:18:55 2005 Return-path: <[EMAIL PROTECTED]> Received: from defiant.lowpingbastards.de ([213.178.77.226] helo=mail.lowpingbastards.de ident=UNKNOWN) by spohr.debian.org with esmtp (Exim 4.50) id 1Eaj6c-0007Ra-No for [EMAIL PROTECTED]; Fri, 11 Nov 2005 16:18:55 -0800 Received: from defiant.lowpingbastards.de ([EMAIL PROTECTED] [127.0.0.1]) by mail.lowpingbastards.de (8.13.4/8.13.4/Debian-3) with ESMTP id jAC0ImVZ005413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 12 Nov 2005 01:18:48 +0100 Received: (from [EMAIL PROTECTED]) by defiant.lowpingbastards.de (8.13.4/8.13.4/Submit) id jAC0ImF3005410; Sat, 12 Nov 2005 01:18:48 +0100 Date: Sat, 12 Nov 2005 01:18:48 +0100 From: Frederik Schueler <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: re: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h) Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wLAMOaPNJ0fu1fTG" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.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 --wLAMOaPNJ0fu1fTG Content-Typ
Bug#292328: marked as done (kernel-image-2.6.10-1-686: kernel freezes for about 30 sec. during the boot process)
Your message dated Tue, 8 Nov 2005 11:46:20 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#292328: It works fine with linux-image-2.6.14-1-686 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) -- Received: (at submit) by bugs.debian.org; 26 Jan 2005 12:12:43 + >From [EMAIL PROTECTED] Wed Jan 26 04:12:42 2005 Return-path: <[EMAIL PROTECTED]> Received: from hki1-4-1-c4.hoasnet.inet.fi (sombra) [80.221.28.196] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ctm2L-0003Z7-00; Wed, 26 Jan 2005 04:12:41 -0800 Received: from localhost ([127.0.0.1] helo=[192.168.0.2]) by sombra with esmtp (Exim 4.43) id 1Ctm2N-0001sS-U1; Wed, 26 Jan 2005 14:12:43 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Cesar Martinez Izquierdo <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-image-2.6.10-1-686: kernel freezes for about 30 sec. during the boot process Bcc: Cesar Martinez Izquierdo <[EMAIL PROTECTED]> X-Mailer: reportbug 3.6 Date: Wed, 26 Jan 2005 14:12:43 +0200 Message-ID: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.10-1-686 Version: 2.6.10-4 Severity: normal Hi, kernel-image-2.6.10-1-686 freezes for about 30 sec. during the boot procces, just after the message: ide1 at 0x170-0x177,0x376 on irq 15 After that, the boot proccess continues but a bunch of error messages with modules are shown; something like this: ERROR: Removing 'rz1000': Device or resource busy These error messages are shown just before the message: EXT3-fs: mounted filesystem with ordered data mode. (But they are not shown in dmesg!) Finally, the boot proccess ends normally, and everything works fine. lspci -vv output: :00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02) Subsystem: Toshiba America Info Systems: Unknown device 0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- (32-bit, prefetchable) Capabilities: [40] #09 [0105] :00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control Registers (rev 02) Subsystem: Toshiba America Info Systems: Unknown device 0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- FastB2B- :00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Region 1: I/O ports at Region 2: I/O ports at Region 3: I/O ports at Region 4: I/O ports at bfa0 [size=16] Region 5: Memory at 1f080400 (32-bit, non-prefetchable) [size=1K] :00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) Subsystem: Toshiba America Info Systems: Unknown device 0241 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 dmesg output: 0 (reserved) BIOS-e820: 0010 - 1ef4 (usable) BIOS-e820: 1ef4 - 1ef5 (ACPI data) BIOS-e820: 1ef5 - 1f00 (reserved) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fec1 - fec2 (reserved) BIOS-e820: feda - fedc (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ffb0 - ffc0 (reserved) BIOS-e820: 00
Bug#293109: marked as done (kernel-image-2.6.10-1-k7: /lib/modules/2.6.10-1-k7/source points to wrong place)
Your message dated Fri, 14 Oct 2005 17:44:46 +0900 with message-id <[EMAIL PROTECTED]> and subject line kernel-image-2.6.10-1-k7: /lib/modules/2.6.10-1-k7/source points to wrong place 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) -- Received: (at submit) by bugs.debian.org; 1 Feb 2005 07:07:13 + >From [EMAIL PROTECTED] Mon Jan 31 23:07:13 2005 Return-path: <[EMAIL PROTECTED]> Received: from metromaster.physics.ucsb.edu [128.111.16.30] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cvs81-0002re-00; Mon, 31 Jan 2005 23:07:13 -0800 Received: from ppro ([128.111.16.241]) by metromaster.physics.ucsb.edu (8.12.10/8.12.10) with ESMTP id j1177BPX025195 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 31 Jan 2005 23:07:13 -0800 Received: from lenya by ppro with local (Exim 4.34) id 1Cvs7u-0004I0-Tv; Mon, 31 Jan 2005 23:07:07 -0800 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: jane <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-image-2.6.10-1-k7: /lib/modules/2.6.10-1-k7/source points to wrong place X-Mailer: reportbug 3.2 Date: Mon, 31 Jan 2005 23:07:06 -0800 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD, HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.10-1-k7 Version: 2.6.10-4 Severity: normal lib/modules/2.6.10-1-k7/source points to maintainer's build directory. This is a problem when compiling non-debian kernel modules with debian stock image and debian kernel sources. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.10-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information --- Received: (at 293109-done) by bugs.debian.org; 14 Oct 2005 08:55:52 + >From [EMAIL PROTECTED] Fri Oct 14 01:55:52 2005 Return-path: <[EMAIL PROTECTED]> Received: from koto.vergenet.net [210.128.90.7] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1EQLM0-7m-00; Fri, 14 Oct 2005 01:55:52 -0700 Received: by koto.vergenet.net (Postfix, from userid 7100) id 0312C34034; Fri, 14 Oct 2005 17:54:49 +0900 (JST) Date: Fri, 14 Oct 2005 17:44:46 +0900 From: Horms <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: kernel-image-2.6.10-1-k7: /lib/modules/2.6.10-1-k7/source points to wrong place Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Cluestick: seven User-Agent: Mutt/1.5.11 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.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 This problem is no longer present in linux-2.6 derived kernels, which are the only 2.6 kernels supported for Etch. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
Horms: > With regards to pcmcia-modules-2.4.26-i386. > I notice that pcmcia-modules-2.4.27-i386 exists and presumably works. > I've CCed the maintainer, Per Olofsson for comment. Sorry for replying so late. Yes, pcmcia-modules-2.4.26-i386 should indeed be removed. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Fri, Sep 16, 2005 at 10:38:21AM +0900, Horms wrote: > Out of interest, what is a good way to check dependancies across all > architectures and distributions? I know that apt-cache can do this based on > the sources it knows about, but thats usually only for the current > arch and distro. I use the build-in reverse-dependency checking by the script doing the removals: merkel (mirror): /org/ftp.debian.org/katie/melanie. Invoke it as such: /org/ftp.debian.org/katie/melanie -n -R kernel-source-2.6.8 Note that also this tool isn't without bugs, it gives spurious warnings with arch-specific removals, it will warn when you remove a package but another Provides: it so it goes well after all, and erm, it crashes when it encounters a contrib/non-free reverse dependency. After manually patching the last issue (trivial), it provides a good starting point. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Thu, Sep 15, 2005 at 07:35:48PM -0700, Steve Langasek wrote: > On Fri, Sep 16, 2005 at 10:38:21AM +0900, Horms wrote: > > On Fri, Sep 16, 2005 at 02:35:24AM +0200, Jeroen van Wolffelaar wrote: > > > On Thu, Sep 15, 2005 at 03:05:18PM +0900, Horms wrote: > > > > As requested, here is an updated list of kernel and related packages > > > > to be removed at this time. > > > > So, I just removed the follow packages, but forgot to close this bug. Oh > > > well. As usual, changes take effect upon next mirror pulse, and packages > > > are later removed from testing automatically but not before reverse > > > dependencies are all gone too. > > > Thanks, very much appreciated. > > > Out of interest, what is a good way to check dependancies across all > > architectures and distributions? I know that apt-cache can do this based on > > the sources it knows about, but thats usually only for the current > > arch and distro. > > For existing packages, /org/ftp.debian.org/katie/melanie -n -R -s > warns you of any packages left uninstallable (or > unbuildable due to build-dependencies) by a removal. That seems quite useful indeed. For those, like I, who aren't in the know, it should be run on merkel (as Steve told me on IRC). -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Thu, Sep 15, 2005 at 07:35:48PM -0700, Steve Langasek wrote: > On Fri, Sep 16, 2005 at 10:38:21AM +0900, Horms wrote: > > On Fri, Sep 16, 2005 at 02:35:24AM +0200, Jeroen van Wolffelaar wrote: > > > On Thu, Sep 15, 2005 at 03:05:18PM +0900, Horms wrote: > > > > As requested, here is an updated list of kernel and related packages > > > > to be removed at this time. > > > > So, I just removed the follow packages, but forgot to close this bug. Oh > > > well. As usual, changes take effect upon next mirror pulse, and packages > > > are later removed from testing automatically but not before reverse > > > dependencies are all gone too. > > > Thanks, very much appreciated. > > > Out of interest, what is a good way to check dependancies across all > > architectures and distributions? I know that apt-cache can do this based on > > the sources it knows about, but thats usually only for the current > > arch and distro. > > For existing packages, /org/ftp.debian.org/katie/melanie -n -R -s > warns you of any packages left uninstallable (or > unbuildable due to build-dependencies) by a removal. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Fri, Sep 16, 2005 at 10:38:21AM +0900, Horms wrote: > On Fri, Sep 16, 2005 at 02:35:24AM +0200, Jeroen van Wolffelaar wrote: > > On Thu, Sep 15, 2005 at 03:05:18PM +0900, Horms wrote: > > > As requested, here is an updated list of kernel and related packages > > > to be removed at this time. > > So, I just removed the follow packages, but forgot to close this bug. Oh > > well. As usual, changes take effect upon next mirror pulse, and packages > > are later removed from testing automatically but not before reverse > > dependencies are all gone too. > Thanks, very much appreciated. > Out of interest, what is a good way to check dependancies across all > architectures and distributions? I know that apt-cache can do this based on > the sources it knows about, but thats usually only for the current > arch and distro. For existing packages, /org/ftp.debian.org/katie/melanie -n -R -s warns you of any packages left uninstallable (or unbuildable due to build-dependencies) by a removal. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Fri, Sep 16, 2005 at 02:35:24AM +0200, Jeroen van Wolffelaar wrote: > On Thu, Sep 15, 2005 at 03:05:18PM +0900, Horms wrote: > > As requested, here is an updated list of kernel and related packages > > to be removed at this time. > > So, I just removed the follow packages, but forgot to close this bug. Oh > well. As usual, changes take effect upon next mirror pulse, and packages > are later removed from testing automatically but not before reverse > dependencies are all gone too. Thanks, very much appreciated. Out of interest, what is a good way to check dependancies across all architectures and distributions? I know that apt-cache can do this based on the sources it knows about, but thats usually only for the current arch and distro. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Thu, Sep 15, 2005 at 03:05:18PM +0900, Horms wrote: > As requested, here is an updated list of kernel and related packages > to be removed at this time. So, I just removed the follow packages, but forgot to close this bug. Oh well. As usual, changes take effect upon next mirror pulse, and packages are later removed from testing automatically but not before reverse dependencies are all gone too. [Date: Thu, 15 Sep 2005 17:29:45 -0700] [ftpmaster: Jeroen van Wolffelaar] Removed the following packages from unstable: fai-kernels | 1.9.1 | source, i386 kernel-doc-2.4.24 | 2.4.24-3 | all kernel-doc-2.4.25 | 2.4.25-3 | all kernel-doc-2.4.26 | 2.4.26-6 | all kernel-patch-2.6.10-hppa | 2.6.10-1 | source, all kernel-patch-debian-2.4.24 | 2.4.24-3 | all kernel-patch-debian-2.4.25 | 2.4.25-3 | all kernel-patch-debian-2.4.26 | 2.4.26-6 | all kernel-source-2.4.24 | 2.4.24-3 | source, all kernel-source-2.4.25 | 2.4.25-3 | source, all kernel-source-2.4.26 | 2.4.26-6 | source, all kernel-tree-2.4.24 | 2.4.24-3 | all kernel-tree-2.4.25 | 2.4.25-3 | all kernel-tree-2.4.26 | 2.4.26-6 | all mol-modules-2.6.11 | 1:0.9.70+2.6.11+2-1 | source mol-modules-2.6.11-powerpc | 1:0.9.70+2.6.11+2-1 | powerpc mol-modules-2.6.11-powerpc-smp | 1:0.9.70+2.6.11+2-1 | powerpc --- Reason --- RoM; Superseded by 2.6.12 -- --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
Processing commands for [EMAIL PROTECTED]: > reassign 323183 ftp.debian.org Bug#323183: Please remove some linux packages from sid Bug reassigned from package `kernel' to `ftp.debian.org'. > 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]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
reassign 323183 ftp.debian.org thanks As requested, here is an updated list of kernel and related packages to be removed at this time. This does not include 2.6.8 and related packages. Its probably best to handle them in a separate bug once d-i no longer needs them. kernel-source-2.4.24 kernel-source-2.4.25 kernel-source-2.4.26 kernel-patch-2.6.10-hppa fai-kernels (request from Holger Levsen) mol-modules-2.6.11 (mol-modules-2.6.12 is in new) This is also separate from #328325, requesting the removal of the following packages: kernel-image-2.4.27-ia64 kernel-patch-2.4.27-ia64 linux-kernel-di-ia64 -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Thu, Sep 15, 2005 at 04:50:26AM +0200, Jeroen van Wolffelaar wrote: > On Thu, Sep 15, 2005 at 11:19:37AM +0900, Horms wrote: > > On Thu, Sep 15, 2005 at 01:35:47AM +0200, Jeroen van Wolffelaar wrote: > > > (...) > > Thanks, hopefully we can get to the bottom of this sooner rather > > than later > > I hope so too :) > > > With regards to pcmcia-modules-2.4.26-i386. > > I notice that pcmcia-modules-2.4.27-i386 exists and presumably works. > > I've CCed the maintainer, Per Olofsson for comment. > > Ok, either way, since 2.4.27 exists, I won't let pcmcia-modules-2.4.26 block > removal. > > > > > kernel-latest-2.6-amd64 > > > > > > Ditto -- shouldn't this one be simply superseded by packages generated by > > > a > > > next upload of linux-2.6? > > > > amd64 still doesn't seem to exist for linux-2.6, I'm not sure why, > > perhaps I am just blind or looking in the wrong place > > > > http://ftp2.jp.debian.org/debian/pool/main/l/linux-2.6/ > > > > However, once it is uploaded, it will have binary packages with > > the same names as those previously produced by the > > kernel-latest-2.6-amd64 source package. Does this mean that > > kernel-latest-2.6-amd64 will automatically be removed, or automatically > > flagged for removal? > > Yes, if all binary packages of a give source package are 'hijacked' by another > package, the source package will be automatically flagged for removal, and > packages automatically flagged for removal will be removed by an ftp-team > member every few days. > > So, no action needed, and not removing will ensure a smooth transition. Thanks, I'll prepare a fresh list for you ASAP. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Thu, Sep 15, 2005 at 11:19:37AM +0900, Horms wrote: > On Thu, Sep 15, 2005 at 01:35:47AM +0200, Jeroen van Wolffelaar wrote: > > (...) > Thanks, hopefully we can get to the bottom of this sooner rather > than later I hope so too :) > With regards to pcmcia-modules-2.4.26-i386. > I notice that pcmcia-modules-2.4.27-i386 exists and presumably works. > I've CCed the maintainer, Per Olofsson for comment. Ok, either way, since 2.4.27 exists, I won't let pcmcia-modules-2.4.26 block removal. > > > kernel-latest-2.6-amd64 > > > > Ditto -- shouldn't this one be simply superseded by packages generated by a > > next upload of linux-2.6? > > amd64 still doesn't seem to exist for linux-2.6, I'm not sure why, > perhaps I am just blind or looking in the wrong place > > http://ftp2.jp.debian.org/debian/pool/main/l/linux-2.6/ > > However, once it is uploaded, it will have binary packages with > the same names as those previously produced by the > kernel-latest-2.6-amd64 source package. Does this mean that > kernel-latest-2.6-amd64 will automatically be removed, or automatically > flagged for removal? Yes, if all binary packages of a give source package are 'hijacked' by another package, the source package will be automatically flagged for removal, and packages automatically flagged for removal will be removed by an ftp-team member every few days. So, no action needed, and not removing will ensure a smooth transition. > Thanks Thanks you, --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Thu, Sep 15, 2005 at 01:35:47AM +0200, Jeroen van Wolffelaar wrote: [snip] > > I suggest that we just track this as 323183, rather than mucking around > > with opening and merging existing bugs. Please let me know if you would > > prefer a different approach. > > No, that is fine. Having just one report makes things easiest -- though the > most important thing is a clear overview of which sourcepackages are really > ready to be removed and which are not yet -- an overview which you've > succeeded quite well to produce. Thanks, hopefully we can get to the bottom of this sooner rather than later [snip] Matt Zimmerman, the maintainer, has indicated that he is not interested in updating uml to 2.6, which in his oppinion is the only way forward. I guess the package should be orphaned or removed from the archive. But in any case it seems that it shouldn't block the removal of kernel-source-2.4.26. I have CCed Matt so he can clarify this. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323183;msg=25 With regards to pcmcia-modules-2.4.26-i386. I notice that pcmcia-modules-2.4.27-i386 exists and presumably works. I've CCed the maintainer, Per Olofsson for comment. > > kernel-image-2.6.11-alpha > > kernel-image-2.6.11-amd64 > > kernel-image-2.6.11-i386 > > kernel-image-2.6.11-ia64 > > All gone already ttbomk. > > > kernel-patch-2.6.10-hppa > > Still around, ok. > > > kernel-latest-2.6-amd64 > > Ditto -- shouldn't this one be simply superseded by packages generated by a > next upload of linux-2.6? amd64 still doesn't seem to exist for linux-2.6, I'm not sure why, perhaps I am just blind or looking in the wrong place http://ftp2.jp.debian.org/debian/pool/main/l/linux-2.6/ However, once it is uploaded, it will have binary packages with the same names as those previously produced by the kernel-latest-2.6-amd64 source package. Does this mean that kernel-latest-2.6-amd64 will automatically be removed, or automatically flagged for removal? > > fai-kernels (request from Holger Levsen) > > > > mol-modules-2.6.11 > > Ok. > > After you clarified my two minor questions, could you please reassign this bug > back to ftp.debian.org? I'll then remove all packages mentioned from "Ready > for removal by ftpmasters" up until here. You can then open a new bug for the > packages mentioned below when the time is there. [snip] I'll wait for some feedback from Matt and Per and do just that. Could you clarify the sistuation with regards to kernel-latest-2.6-amd64 being removed once linux-2.6 for amd64 is uploaded. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Wed, Sep 14, 2005 at 04:27:32PM +0900, Horms wrote: > On Wed, Sep 14, 2005 at 04:54:04AM +0200, Jeroen van Wolffelaar wrote: > > On Tue, Sep 13, 2005 at 08:01:11PM +0200, Sven Luther wrote: > > > Hi, > > > > > > I write this email to ask, now that linux-2.6 2.6.12-6 is in testing, > > > there > > > isn't any reason to keep those 2.6.10 and 2.6.11 kernels around, A quick > > > glance listed those : > > > > (...) > > > > > Also, if there are 2.6.8 kernels in sid/etch still, these can be removed > > > as > > > well. > > > > Please see #317079, #322697 and and #323183. This report is a duplicate from > > what's already in those three reports, so please followup to them where > > appropriate. I already see a duplicate discussion on whether 2.6.8 can be > > removed, so please coordinate in the -kernel team about this, I mailed > > -kernel > > about it before, and there's a bug on the kernel package (#323183) about it. > > First up I'd like to applogise for the confusion and multiple bug > reports surrounding this. The simple truth is that the legacy > of the Sarge-era kernel packaging has left us with a mess, that > we are trying to sift through and slowly clean up. Its turning > out to be quite complicated, and thats not something that > you should have been asked to worry about. I understand, > I suggest that we just track this as 323183, rather than mucking around > with opening and merging existing bugs. Please let me know if you would > prefer a different approach. No, that is fine. Having just one report makes things easiest -- though the most important thing is a clear overview of which sourcepackages are really ready to be removed and which are not yet -- an overview which you've succeeded quite well to produce. > I've just spent a bit of time looking through this and here > is a summary of where I beleive we are, others, please comment > if this is inaccurate or incomplete. If there are ammendments > I'll try and correlate them into an updated list. > > Already removed: > kernel-image-2.6.11-s390 (done in Bug #317079) > kernel-image-2.6.11-sparc (done in Bug #317079) > kernel-patch-powerpc-2.6.11 (done in Bug #317079) > kernel-source-2.6.11 (done in Bug #317079) > > kernel-image-2.6.10-alpha (done in Bug #322697) > kernel-image-2.6.10-hppa(done in Bug #322697) > kernel-image-2.6.10-sparc (done in Bug #322697) > kernel-source-2.6.10(done in Bug #322697) Indeed, I removed both source packages and all of the kernel-* stuff that was broken by that removal. I did leave some 3rd-party packages around that seemed like they 'just' needed to be upgraded to 2.6.12. > Ready for removal by ftpmasters > kernel-source-2.4.24 > kernel-source-2.4.25 > kernel-source-2.4.26 Reverse-dependencies: ** pcmcia-modules-2.4.26-i386 has an unsatisfied build-dependency: kernel-tree-2.4.26-2 ** user-mode-linux has an unsatisfied build-dependency: kernel-source-2.4.26 I guess pcmcia-modules-2.4.26-i386 should be dropped too, and user-mode-linux left broken for the moment? > kernel-image-2.6.11-alpha > kernel-image-2.6.11-amd64 > kernel-image-2.6.11-i386 > kernel-image-2.6.11-ia64 All gone already ttbomk. > kernel-patch-2.6.10-hppa Still around, ok. > kernel-latest-2.6-amd64 Ditto -- shouldn't this one be simply superseded by packages generated by a next upload of linux-2.6? > fai-kernels (request from Holger Levsen) > > mol-modules-2.6.11 Ok. After you clarified my two minor questions, could you please reassign this bug back to ftp.debian.org? I'll then remove all packages mentioned from "Ready for removal by ftpmasters" up until here. You can then open a new bug for the packages mentioned below when the time is there. > Will be ready for removal once d-i moves from 2.6.8 to 2.6.12 > (...) > Not ready for removal > (...) Thanks a lot, --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Wed, Sep 14, 2005 at 04:27:32PM +0900, Horms wrote: > On Wed, Sep 14, 2005 at 04:54:04AM +0200, Jeroen van Wolffelaar wrote: > > On Tue, Sep 13, 2005 at 08:01:11PM +0200, Sven Luther wrote: > > > Hi, > > > > > > I write this email to ask, now that linux-2.6 2.6.12-6 is in testing, > > > there > > > isn't any reason to keep those 2.6.10 and 2.6.11 kernels around, A quick > > > glance listed those : > > > > (...) > > > > > Also, if there are 2.6.8 kernels in sid/etch still, these can be removed > > > as > > > well. > > > > Please see #317079, #322697 and and #323183. This report is a duplicate from > > what's already in those three reports, so please followup to them where > > appropriate. I already see a duplicate discussion on whether 2.6.8 can be > > removed, so please coordinate in the -kernel team about this, I mailed > > -kernel > > about it before, and there's a bug on the kernel package (#323183) about it. > > First up I'd like to applogise for the confusion and multiple bug > reports surrounding this. The simple truth is that the legacy > of the Sarge-era kernel packaging has left us with a mess, that > we are trying to sift through and slowly clean up. Its turning > out to be quite complicated, and thats not something that > you should have been asked to worry about. > > I suggest that we just track this as 323183, rather than mucking around > with opening and merging existing bugs. Please let me know if you would > prefer a different approach. > > I've just spent a bit of time looking through this and here > is a summary of where I beleive we are, others, please comment > if this is inaccurate or incomplete. If there are ammendments > I'll try and correlate them into an updated list. > > Already removed: > kernel-image-2.6.11-s390 (done in Bug #317079) > kernel-image-2.6.11-sparc (done in Bug #317079) > kernel-patch-powerpc-2.6.11 (done in Bug #317079) > kernel-source-2.6.11 (done in Bug #317079) > > kernel-image-2.6.10-alpha (done in Bug #322697) > kernel-image-2.6.10-hppa(done in Bug #322697) > kernel-image-2.6.10-sparc (done in Bug #322697) > kernel-source-2.6.10(done in Bug #322697) > > Ready for removal by ftpmasters > kernel-source-2.4.24 > kernel-source-2.4.25 > kernel-source-2.4.26 > > kernel-image-2.6.11-alpha > kernel-image-2.6.11-amd64 > kernel-image-2.6.11-i386 > kernel-image-2.6.11-ia64 > > kernel-patch-2.6.10-hppa > > kernel-latest-2.6-amd64 > > fai-kernels (request from Holger Levsen) > > mol-modules-2.6.11 I just uploaded mol-modules-2.6.12, so once they pass NEW, mol-modules-2.6.12 can go indeed. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Wed, Sep 14, 2005 at 04:54:04AM +0200, Jeroen van Wolffelaar wrote: > On Tue, Sep 13, 2005 at 08:01:11PM +0200, Sven Luther wrote: > > Hi, > > > > I write this email to ask, now that linux-2.6 2.6.12-6 is in testing, there > > isn't any reason to keep those 2.6.10 and 2.6.11 kernels around, A quick > > glance listed those : > > (...) > > > Also, if there are 2.6.8 kernels in sid/etch still, these can be removed as > > well. > > Please see #317079, #322697 and and #323183. This report is a duplicate from > what's already in those three reports, so please followup to them where > appropriate. I already see a duplicate discussion on whether 2.6.8 can be > removed, so please coordinate in the -kernel team about this, I mailed -kernel > about it before, and there's a bug on the kernel package (#323183) about it. First up I'd like to applogise for the confusion and multiple bug reports surrounding this. The simple truth is that the legacy of the Sarge-era kernel packaging has left us with a mess, that we are trying to sift through and slowly clean up. Its turning out to be quite complicated, and thats not something that you should have been asked to worry about. I suggest that we just track this as 323183, rather than mucking around with opening and merging existing bugs. Please let me know if you would prefer a different approach. I've just spent a bit of time looking through this and here is a summary of where I beleive we are, others, please comment if this is inaccurate or incomplete. If there are ammendments I'll try and correlate them into an updated list. Already removed: kernel-image-2.6.11-s390(done in Bug #317079) kernel-image-2.6.11-sparc (done in Bug #317079) kernel-patch-powerpc-2.6.11 (done in Bug #317079) kernel-source-2.6.11(done in Bug #317079) kernel-image-2.6.10-alpha (done in Bug #322697) kernel-image-2.6.10-hppa(done in Bug #322697) kernel-image-2.6.10-sparc (done in Bug #322697) kernel-source-2.6.10(done in Bug #322697) Ready for removal by ftpmasters kernel-source-2.4.24 kernel-source-2.4.25 kernel-source-2.4.26 kernel-image-2.6.11-alpha kernel-image-2.6.11-amd64 kernel-image-2.6.11-i386 kernel-image-2.6.11-ia64 kernel-patch-2.6.10-hppa kernel-latest-2.6-amd64 fai-kernels (request from Holger Levsen) mol-modules-2.6.11 Will be ready for removal once d-i moves from 2.6.8 to 2.6.12 kernel-image-2.6.8-alpha kernel-image-2.6.8-amd64 kernel-image-2.6.8-hppa kernel-image-2.6.8-i386 kernel-image-2.6.8-ia64 kernel-image-2.6.8-m68k kernel-image-2.6.8-s390 kernel-image-2.6.8-sparc kernel-patch-2.6.8-hppa kernel-patch-2.6.8-m68k kernel-patch-powerpc-2.6.8 kernel-source-2.6.8 kernel-latest-2.6-i386 kernel-latest-2.6-s390 kernel-latest-2.6-sparc kernel-latest-2.6-hppa Not ready for removal kernel-latest-powerpc (needed for 2.4 and in turn d-i) -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Tue, Sep 13, 2005 at 08:01:11PM +0200, Sven Luther wrote: > Hi, > > I write this email to ask, now that linux-2.6 2.6.12-6 is in testing, there > isn't any reason to keep those 2.6.10 and 2.6.11 kernels around, A quick > glance listed those : (...) > Also, if there are 2.6.8 kernels in sid/etch still, these can be removed as > well. Please see #317079, #322697 and and #323183. This report is a duplicate from what's already in those three reports, so please followup to them where appropriate. I already see a duplicate discussion on whether 2.6.8 can be removed, so please coordinate in the -kernel team about this, I mailed -kernel about it before, and there's a bug on the kernel package (#323183) about it. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Tue, Sep 13, 2005 at 08:34:28PM +0200, Frans Pop wrote: > On Tuesday 13 September 2005 20:01, Sven Luther wrote: > > Also, if there are 2.6.8 kernels in sid/etch still, these can be > > removed as well. > > Note: 2.6.8 should _not_ yet be removed and I understand from Sven on IRC > that he did not intend to request that with this mail. Indeed, i probably should have sais : "these should probably be removed from ecth/sid in the near futur: :) > 2.6.8 is currently still in use by d-i, although we are working on a > switch to 2.6.12 now that that's in testing. > A separate removal request for 2.6.8 will be filed after that is complete. Ok. Would be easier though if the kernel .udebs where moved to the responsability of the kernel team, or another solution be found for them. > The requested removals for remaining 2.6.10 and 2.6.11 packages is OK from > a d-i standpoint. Cool, they should definitively go as soon as possible, since people are still using them and reporting strange bug reports about them, which are often already fixed in 2.6.12. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
On Tuesday 13 September 2005 20:01, Sven Luther wrote: > Also, if there are 2.6.8 kernels in sid/etch still, these can be > removed as well. Note: 2.6.8 should _not_ yet be removed and I understand from Sven on IRC that he did not intend to request that with this mail. 2.6.8 is currently still in use by d-i, although we are working on a switch to 2.6.12 now that that's in testing. A separate removal request for 2.6.8 will be filed after that is complete. The requested removals for remaining 2.6.10 and 2.6.11 packages is OK from a d-i standpoint. Cheers, FJP pgphY0HwvPayk.pgp Description: PGP signature
RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
Package: ftp.debian.org Severity: important Hi, I write this email to ask, now that linux-2.6 2.6.12-6 is in testing, there isn't any reason to keep those 2.6.10 and 2.6.11 kernels around, A quick glance listed those : kernel-image-2.6.10-alpha kernel-image-2.6.10-hppa kernel-image-2.6.10-sparc kernel-image-2.6.11-alpha kernel-image-2.6.11-amd64 kernel-image-2.6.11-i386 kernel-image-2.6.11-ia64 kernel-image-2.6.11-s390 kernel-image-2.6.11-sparc kernel-patch-2.6.10-hppa kernel-patch-powerpc-2.6.11 kernel-source-2.6.10 kernel-source-2.6.11 kernel-kbuild-2.6-3 As well as all the kernel-latest too, since those provided by linux-2.6. Maybe there are others too, but those one will do for a first round. Also, if there are 2.6.8 kernels in sid/etch still, these can be removed as well. Friendly, Sven Luther -n System Information: Debian Release: 3.1 Architecture: powerpc (ppc) Kernel: Linux 2.6.12-1-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324368: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h)
On Mon, Aug 22, 2005 at 08:47:42PM +0200, Alexandre Pineau wrote: > On Mon, 22 Aug 2005 11:50:20 +0900 > Horms <[EMAIL PROTECTED]> wrote: > > > > Its an issue with the kernel. 2.6.10 does not compile cleanly > > with gcc-4.0. 2.6.10 is being debricated and is no longer supported, > > please consider using 2.6.12 or later. If you really need to > > compile 2.6.10 for some reason, please use gcc-3.3. > > Thanks for your reponse. Maybe you can remove this package from > unstable then. We are in the process of doing just that. There is a bug open with the ftpmasters to remove the package, which is the mechanism used to remove packages from the archive. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324368: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h)
On Mon, 22 Aug 2005 11:50:20 +0900 Horms <[EMAIL PROTECTED]> wrote: > Its an issue with the kernel. 2.6.10 does not compile cleanly > with gcc-4.0. 2.6.10 is being debricated and is no longer supported, > please consider using 2.6.12 or later. If you really need to > compile 2.6.10 for some reason, please use gcc-3.3. Thanks for your reponse. Maybe you can remove this package from unstable then. Alexandre Pineau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324368: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h)
On Sun, Aug 21, 2005 at 09:26:13PM +0200, Alexandre Pineau wrote: > Package: kernel-source-2.6.10 > Version: 2.6.10-6 > Severity: important > > I cannot build the kernel 2.6.10 with gcc 4.0.1-3 and > linux-kernel-headers_2.6.13+0rc3-1.1_i386.deb. > > I have the following error: > > In file included from drivers/video/fbmem.c:48: > include/linux/fb.h:860: error: array type has incomplete element type > drivers/video/fbmem.c: In function 'fb_get_buffer_offset': > drivers/video/fbmem.c:178: warning: pointer targets in initialization > differ in signedness > make[2]: *** [drivers/video/fbmem.o] Error 1 > > I dont know if it's an issue in gcc, in the kernel or in kernel headers. Its an issue with the kernel. 2.6.10 does not compile cleanly with gcc-4.0. 2.6.10 is being debricated and is no longer supported, please consider using 2.6.12 or later. If you really need to compile 2.6.10 for some reason, please use gcc-3.3. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324368: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h)
Package: kernel-source-2.6.10 Version: 2.6.10-6 Severity: important I cannot build the kernel 2.6.10 with gcc 4.0.1-3 and linux-kernel-headers_2.6.13+0rc3-1.1_i386.deb. I have the following error: In file included from drivers/video/fbmem.c:48: include/linux/fb.h:860: error: array type has incomplete element type drivers/video/fbmem.c: In function 'fb_get_buffer_offset': drivers/video/fbmem.c:178: warning: pointer targets in initialization differ in signedness make[2]: *** [drivers/video/fbmem.o] Error 1 I dont know if it's an issue in gcc, in the kernel or in kernel headers. Regards, Alexandre Pineau -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.16.1-2 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291940: marked as done (kernel-source-2.6.10: IPv6-in-IPv4 tunnel hangs at shutdown, "Waiting for to become free")
Your message dated Fri, 12 Aug 2005 12:30:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line unregister_netdevice: waiting for ... to become free 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) -- Received: (at submit) by bugs.debian.org; 24 Jan 2005 03:33:10 + >From [EMAIL PROTECTED] Sun Jan 23 19:33:10 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl081-048-014.sfo1.dsl.speakeasy.net (ns1.hamachi.us) [64.81.48.14] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CsuyU-00026J-00; Sun, 23 Jan 2005 19:33:10 -0800 Received: by ns1.hamachi.us (Postfix, from userid 2513) id 374D23812B; Sun, 23 Jan 2005 19:33:09 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Steven Ihde <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: IPv6-in-IPv4 tunnel hangs at shutdown, "Waiting for to become free" X-Mailer: reportbug 3.5 Date: Sun, 23 Jan 2005 19:33:09 -0800 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.10 Version: 2.6.10-4 Severity: important My IPv6-in-IPv4 tunnel causes 2.6.10 to hang on shutdown (every time). The tunnel is named henet0; the message printed over and over is: unregister_netdevice: waiting for henet0 to become free. Usage count = 1 I verified that the hang also happens with 2.6.10 vanilla (i.e., Debian patches removed). It worked fine with 2.6.8 (Debian). Apparently there were issues with unregister_netdevice that were solved previously, but this appears to be a new bug with 2.6.10. This has been discussed recently on the linux-netdev mailing list; here are some links: http://marc.theaimsgroup.com/?l=linux-netdev&m=110585721626841&w=2 http://marc.theaimsgroup.com/?l=linux-netdev&m=110476395824647&w=2 http://marc.theaimsgroup.com/?l=linux-netdev&m=110405248721053&w=2 This appears similar to Debian bug 291029 but I'm filing it as a separate bug, because 291029 involves a bridge device whereas this involves a 6-in-4 tunnel device. From perusing the discussion on linux-netdev it sounds like they may be separate issues. This message on linux-netdev had a patch; it wasn't clear whether it was supposed to fix this problem, but I tried it anyway and it did not: http://marc.theaimsgroup.com/?l=linux-netdev&m=110451354301328&w=2 For now, I'm hanging back at 2.6.8 because I don't like the idea that I can't reboot the box remotely. Thanks, Steve -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (900, 'unstable'), (890, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-hamachi Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) 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-2high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information --- Received: (at 290964-done) by bugs.debian.org; 12 Aug 2005 10:30:25 + >From [EMAIL PROTECTED] Fri Aug 12 03:30:25 2005 Return-path: <[EMAIL PROTECTED]> Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E3Wnx-0003Il-00; Fri, 12 Aug 2005 03:30:25 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id C3ADF5C001; Fri, 12 Aug 2005 12:30:15 +0200 (CEST) Date: Fri, 12 Aug 2005 12:30:15 +0200 From: Maximilian Attems <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: unregister_netdevice: waiting for ... to become free Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> Us
Bug#290964: marked as done (kernel-image-2.6.10-1-686: ifdown freezes: unregister_netdevice: waiting for ... to become free)
Your message dated Fri, 12 Aug 2005 12:30:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line unregister_netdevice: waiting for ... to become free 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) -- Received: (at submit) by bugs.debian.org; 17 Jan 2005 23:06:59 + >From [EMAIL PROTECTED] Mon Jan 17 15:06:59 2005 Return-path: <[EMAIL PROTECTED]> Received: from mandy.eunet.fi [193.66.1.129] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cqfxb-0007Co-00; Mon, 17 Jan 2005 15:06:59 -0800 Received: from js-1.kpnqwest.fi (js-1.kpnqwest.fi [193.64.243.217]) by mandy.eunet.fi (Postfix) with ESMTP id 36CC713DDA0; Tue, 18 Jan 2005 01:06:37 +0200 (EET) Received: from js by js-1.kpnqwest.fi with local (Exim 4.43) id 1CqfxF-yb-3D; Tue, 18 Jan 2005 01:06:37 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jukka Suomela <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-image-2.6.10-1-686: ifdown freezes: unregister_netdevice: waiting for ... to become free X-Mailer: reportbug 3.5 Date: Tue, 18 Jan 2005 01:06:37 +0200 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.10-1-686 Version: 2.6.10-3 Severity: normal With the 2.6.10-1-686 kernel, "ifdown -a" freezes. After a while kernel starts logging messages such as: unregister_netdevice: waiting for tunnel0 to become free. Usage count = 1 (Above "tunnel0" is an IPv6-in-IPv4 tunneling device.) The same setup works fine with the current 2.6.8-2-686 kernel package, and it has worked with earlier kernels, too. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=fi_FI, LC_CTYPE=fi_FI (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.10-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.76 tools to create initrd image for p ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo --- Received: (at 290964-done) by bugs.debian.org; 12 Aug 2005 10:30:25 + >From [EMAIL PROTECTED] Fri Aug 12 03:30:25 2005 Return-path: <[EMAIL PROTECTED]> Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E3Wnx-0003Il-00; Fri, 12 Aug 2005 03:30:25 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id C3ADF5C001; Fri, 12 Aug 2005 12:30:15 +0200 (CEST) Date: Fri, 12 Aug 2005 12:30:15 +0200 From: Maximilian Attems <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: unregister_netdevice: waiting for ... to become free Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by Amavis (ClamAV) at stro.at Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.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 On Fri, Aug 12, 2005 at 12:54:41PM +0300, Jukka Suomela wrote: > On Friday 12 August 2005 12:19, Maximilian Attems wrote: > > can you still reproduce this bug with newer linux kernel images, > > like the linux image 2.6.12? > > If I remember right, I never saw this problem with 2.6.11 kernel images > from Debian unstable. It just happened on 2.6.10. > > I am sorry I do not have the same network setup any more, so I cannot > tell what would have happened with 2.6.12. Anyway, 2.6.12 works fine on > my current system. > > Best regards, &
Bug#296721: marked as done (kernel-source-2.6.10: a third instance of unregister_netdevice: waiting for eth0 to become free. Usage count = )
Your message dated Fri, 12 Aug 2005 12:30:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line unregister_netdevice: waiting for ... to become free 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) -- Received: (at submit) by bugs.debian.org; 24 Feb 2005 10:08:17 + >From [EMAIL PROTECTED] Thu Feb 24 02:08:17 2005 Return-path: <[EMAIL PROTECTED]> Received: from smtp-out-02.utu.fi [130.232.202.172] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D4Fuq-0003WJ-00; Thu, 24 Feb 2005 02:08:17 -0800 Received: from alnitak.stiff.utu.fi (mintaka-dsl.utu.fi [130.232.36.179]) by smtp02.mess.utu.fi (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <[EMAIL PROTECTED]> for [EMAIL PROTECTED]; Thu, 24 Feb 2005 12:06:12 +0200 (EET) Date: Thu, 24 Feb 2005 12:06:12 +0200 From: Juha =?ISO-8859-15?Q?J=E4ykk=E4?= <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: a third instance of unregister_netdevice: waiting for eth0 to become free. Usage count = To: Debian Bug Tracking System <[EMAIL PROTECTED]> Message-id: <[EMAIL PROTECTED]> Organization: University of Turku MIME-version: 1.0 X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-pc-linux-gnu) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.10 Version: 2.6.10-5 Severity: important I am experiencing the same symptoms as bugs #291029, #290964 and #291940. This time the device is just an ordinary eth0 (happens to be a prism54) - no tunnels, bridges or anything. I even removed all IPv6- and tunneling support from the kernel (that's why my kernel is not Debian's own kernel-image - the .config is identical except swsusp is turned on and the forementioned parts off). This happens almost every time there is a network connection established when I try to ifdown the interface or remove the pccard or unload the module. I say almost: it looks like only ssh connections and actively refreshed http-connections actually make this happen. Perhaps those queues' Recv-Q or Send'Q are non-empty? (A connection established means here that netstat says it's established.) The problem sometimes goes away by terminating the offending process - if I can find which one it is. This does not happen every time, though. Shutting down works fine, since the processes are terminated before ifdown is run. The problem is that using ACPI sleep states (swsusp, S3, hibernate etc) take ethernet devices down first and hang there - with the line in subject. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (999, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10+juhaj+v1.7 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) 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 ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information --- Received: (at 296721-done) by bugs.debian.org; 12 Aug 2005 10:30:25 + >From [EMAIL PROTECTED] Fri Aug 12 03:30:25 2005 Return-path: <[EMAIL PROTECTED]> Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E3Wnx-0003Il-00; Fri, 12 Aug 2005 03:30:25 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id C3ADF5C001; Fri, 12 Aug 2005 12:30:15 +0200 (CEST) Date: Fri, 12 Aug 2005 12:30:15 +0200 From: Maximilian Attems <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: unregister_netdevice: waiting for ... to become free Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.5.9i X-Virus
Bug#289974: marked as done (kernel-source-2.6.10: kernel compilation fails with selinux without ipv6 : patch)
Your message dated Sun, 7 Aug 2005 13:46:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kernel-source-2.6.10: kernel compilation fails with selinux
without ipv6 : patch
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)
--
Received: (at submit) by bugs.debian.org; 12 Jan 2005 06:50:22 +
>From [EMAIL PROTECTED] Tue Jan 11 22:50:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from rwcrmhc12.comcast.net [216.148.227.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CocKk-0003a1-00; Tue, 11 Jan 2005 22:50:22 -0800
Received: from zona.someotherplace.org
(pcp0010755515pcs.howard01.md.comcast.net[69.243.110.85])
by comcast.net (rwcrmhc12) with ESMTP
id <2005011206495101400ggafpe>; Wed, 12 Jan 2005 06:49:51 +
Received: by zona.someotherplace.org (Postfix, from userid 1001)
id 68DA47D044; Wed, 12 Jan 2005 01:49:50 -0500 (EST)
Content-Type: multipart/mixed; boundary="===1183575809=="
MIME-Version: 1.0
From: David Coe <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.6.10: kernel compilation fails with selinux without
ipv6 :
patch
X-Mailer: reportbug 3.5
Date: Wed, 12 Jan 2005 01:49:49 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===1183575809==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: kernel-source-2.6.10
Version: 2.6.10-3
Severity: normal
Tags: patch
http://www.kernel.org/pub/linux/kernel/v2.6/testing/cset/[EMAIL PROTECTED]
(also attached) briefly describes and fixes the problem.
"It works for me." (Well, it compiles now, at least.)
Thanks.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (600, 'unstable'), (300, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.9zona-06022se
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
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-3high-quality block-sorting file co
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
ii fileutils 5.2.1-2The GNU file management utilities
-- no debconf information
--===1183575809==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="[EMAIL PROTECTED]|ChangeSet|20050102174642|47485.txt"
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2005/01/02 09:46:42-08:00 [EMAIL PROTECTED]
# [PATCH] fix inet6_sk for non IPV6 builds again
#
# The recent ipv6 "fix" broke the build:
#
# security/selinux/avc.c: In function `avc_audit':
# security/selinux/avc.c:581: warning: implicit declaration of function
`inet6_sk'
# security/selinux/avc.c:581: warning: initialization makes pointer from
integer without a cast
#
# Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
# Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
#
# include/linux/ipv6.h
# 2005/01/02 01:37:34-08:00 [EMAIL PROTECTED] +11 -0
# fix inet6_sk for non IPV6 builds again
#
diff -Nru a/include/linux/ipv6.h b/include/linux/ipv6.h
--- a/include/linux/ipv6.h 2005-01-02 10:13:56 -08:00
+++ b/include/linux/ipv6.h 2005-01-02 10:13:56 -08:00
@@ -289,6 +289,17 @@
#else
#define __ipv6_only_sock(sk) 0
#define ipv6_only_sock(sk) 0
+
+static inline struct ipv6_pinfo * inet6_sk(const struct sock *__sk)
+{
+ return NULL;
+}
+
+static inline struct raw6_opt * raw6_sk(const struct sock *__sk)
+{
+ return NULL;
+}
+
#endif
#endif
--===1183575809==--
---
Received: (at 289974-done) by bugs.debian.org; 7 Aug 2005 12:11:01 +
>From [EMAIL PROTECTED] Sun Aug 07 05:11:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from baikonur
Bug#291232: marked as done (kernel-source-2.6.10: Cannot burn DVD as normal user)
Your message dated Sun, 7 Aug 2005 13:22:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kernel-source-2.6.10: Cannot burn DVD as normal user
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)
--
Received: (at submit) by bugs.debian.org; 19 Jan 2005 14:44:25 +
>From [EMAIL PROTECTED] Wed Jan 19 06:44:25 2005
Return-path: <[EMAIL PROTECTED]>
Received: from out007pub.verizon.net (out007.verizon.net) [206.46.170.107]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrH4L-0006l5-00; Wed, 19 Jan 2005 06:44:25 -0800
Received: from localhost.localdomain ([151.205.40.151])
by out007.verizon.net
(InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP
id <[EMAIL PROTECTED]>;
Wed, 19 Jan 2005 08:44:24 -0600
Content-Type: multipart/mixed; boundary="===0911412019=="
MIME-Version: 1.0
From: Brian Pack <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.6.10: Cannot burn DVD as normal user
Bcc: Brian Pack <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.5
Date: Wed, 19 Jan 2005 09:44:23 -0500
X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from
[151.205.40.151] at Wed, 19 Jan 2005 08:44:23 -0600
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===0911412019==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: kernel-source-2.6.10
Version: 2.6.10-4
Severity: important
Tags: patch
When running as normal user with kernel 2.6.10, growisofs gives the
following error when attempting to burn a DVD:
Executing 'builtin_dd if=/dev/fd/0 of=/dev/hdc obs=32k seek=0'
:-( unable to PREVENT MEDIA REMOVAL: Operation not permitted
Running as root works fine.
I found this patch on LKML, and can now burn as normal user:
--- linux-2.6.11-mm1/drivers/block/scsi_ioctl.c.orig2005-01-17
20:42:40.0 +0100
+++ linux-2.6.11-mm1/drivers/block/scsi_ioctl.c 2005-01-17
20:43:14.0 +0100
@@ -197,9 +197,7 @@ static int verify_command(struct file *f
if (type & CMD_WRITE_SAFE) {
if (file->f_mode & FMODE_WRITE)
return 0;
- }
-
- if (!(type &
CMD_WARNED)) {
+ } else
if (!(type &
CMD_WARNED)) {
cmd_type[cmd[0]]
=
CMD_WARNED;
printk(KERN_WARNING
"scsi:
unknown
opcode
0x%02x\n",
cmd[0]);
}
Link to patch web page:
http://marc.theaimsgroup.com/?l=linux-kernel&m=110599420505734&w=2
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-20050119
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages kernel-source-2.6.10 depends on:
ii bin
Bug#296677: marked as done (kernel-source-2.6.10: Please consider include Guido Guenther powerpc patches)
Your message dated Sun, 7 Aug 2005 13:12:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line kernel-source-2.6.10: Please consider include Guido Guenther powerpc patches 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) -- Received: (at submit) by bugs.debian.org; 23 Feb 2005 22:17:18 + >From [EMAIL PROTECTED] Wed Feb 23 14:17:18 2005 Return-path: <[EMAIL PROTECTED]> Received: from krepost.taket.org (localhost) [82.233.235.217] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D44on-0003uH-00; Wed, 23 Feb 2005 14:17:17 -0800 Received: from djoume by localhost with local (Exim 4.44) id 1D44ok-0006YR-81 for [EMAIL PROTECTED]; Wed, 23 Feb 2005 23:17:14 +0100 Content-Type: multipart/mixed; boundary="===2132322025==" MIME-Version: 1.0 From: Djoume SALVETTI <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.10: Please consider include Guido Guenther powerpc patches X-Mailer: reportbug 3.8 Date: Wed, 23 Feb 2005 23:17:13 +0100 X-Debbugs-Cc: [EMAIL PROTECTED] Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.9 required=4.0 tests=BAYES_44,DOMAIN_BODY, HAS_PACKAGE,X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: This is a multi-part MIME message sent by reportbug. --===2132322025== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: kernel-source-2.6.10 Severity: wishlist Tags: patch Good day, Guido Guenther maintains some patches against 2.6 that I found very usefull : software suspend : >From debian-ppc : | On Wed, Feb 23, 2005 at 11:54:20AM +1100, Benjamin Herrenschmidt wrote: | > > I also gather that suspend-to-disk is available - | > > http://article.gmane.org/gmane.linux.debian.ports.powerpc/25379 | > | > I don't think suspend to disk is very reliable tho ... | Works here without problems for several days now, patch is at | http://honk.physik.uni-konstanz.de/~agx/linux-ppc/kernel/2.6.11-rc4-agx0.diff | Cheers, | -- Guido Again From debian-ppc on 04 december 2004 : | The patch contains some other small goodies such as a selectable HZ | value (default is 1000, 100 saves some battery) and some alsa and | cpufreq fixes. | Please note that this patch still conflicts with suspend to ram, so you | won't be able to use both. | Cheers, | -- Guido patch is at : http://honk.physik.uni-konstanz.de/~agx/linux-ppc/kernel/ and attached to this bug report. Regards. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.9-rfb-swsusp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) --===2132322025== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="2.6.10-agx0.diff" diff -u -Naur linux-2.6.10.orig/arch/ppc/Kconfig linux-2.6.10/arch/ppc/Kconfig --- linux-2.6.10.orig/arch/ppc/Kconfig 2004-12-24 22:35:40.0 +0100 +++ linux-2.6.10/arch/ppc/Kconfig 2005-01-04 14:21:32.583281000 +0100 @@ -966,6 +966,15 @@ source "drivers/zorro/Kconfig" +source kernel/power/Kconfig + +config PPC_HZ + int "Clock Tick Rate" + default 1000 + help + Select the kernel clock tick rate in interrupts per second. + Slower processors should choose 100; everything else 1000. + endmenu menu "Bus options" diff -u -Naur linux-2.6.10.orig/arch/ppc/kernel/Makefile linux-2.6.10/arch/ppc/kernel/Makefile --- linux-2.6.10.orig/arch/ppc/kernel/Makefile 2004-12-24 22:35:28.0 +0100 +++ linux-2.6.10/arch/ppc/kernel/Makefile 2005-01-04 14:21:32.583281000 +0100 @@ -16,6 +16,7 @@ semaphore.o syscalls.o setup.o \ cputable.o ppc_htab.o obj-$(CONFIG_6xx) += l2cr.o cpu_setup_6xx.o +obj-$(CONFIG_SOFTWARE_SUSPEND) += swsusp.o obj-$(CONFIG_POWER4) += cpu_setup_power4.o obj-$(CONFIG_MODULES) += module.o ppc_ksyms.o obj-$(C
Bug#299879: marked as done (Nat is not working from 2.6.10-5 to 2.6.10-6)
Your message dated Sun, 7 Aug 2005 13:14:58 +0200 with message-id <[EMAIL PROTECTED]> and subject line Nat is not working from 2.6.10-5 to 2.6.10-6 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) -- Received: (at submit) by bugs.debian.org; 17 Mar 2005 02:39:19 + >From [EMAIL PROTECTED] Wed Mar 16 18:39:19 2005 Return-path: <[EMAIL PROTECTED]> Received: from tu201010.ip.tsinghua.edu.cn (tu201235.ip.tsinghua.edu.cn) [166.111.201.10] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DBkut-TX-00; Wed, 16 Mar 2005 18:39:19 -0800 Received: from bear by tu201235.ip.tsinghua.edu.cn with local (Exim 4.50) id 1DBkw5-Cc-Al for [EMAIL PROTECTED]; Thu, 17 Mar 2005 10:40:33 +0800 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: bear <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: Nat is not working from 2.6.10-5 to 2.6.10-6 X-Mailer: reportbug 3.8 Date: Thu, 17 Mar 2005 10:40:33 +0800 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS, HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.10 Version: 2.6.10-6 Severity: important "modprobe iptable_nat" with following kernel error ip_conntrack: Unknown symbol ip_defrag iptable_nat: Unknown symbol ip_ct_protos iptable_nat: Unknown symbol ip_ct_selective_cleanup iptable_nat: Unknown symbol invert_tuplepr iptable_nat: Unknown symbol ip_ct_gather_frags iptable_nat: Unknown symbol ip_conntrack_untracked iptable_nat: Unknown symbol ip_conntrack_htable_size iptable_nat: Unknown symbol ip_conntrack_tcp_update iptable_nat: Unknown symbol ip_conntrack_destroyed iptable_nat: Unknown symbol need_ip_conntrack iptable_nat: Unknown symbol ip_conntrack_tuple_taken iptable_nat: Unknown symbol ip_conntrack_alter_reply and "modprobe ip_conntrack" with following kernel error ip_conntrack: disagrees about version of symbol ip_defrag ip_conntrack: Unknown symbol ip_defrag Thanks for your help! -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-k7 Locale: LANG=zh_CN.GBK, LC_CTYPE=zh_CN.GBK (charmap=GBK) 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 --- Received: (at 299879-done) by bugs.debian.org; 7 Aug 2005 11:15:08 + >From [EMAIL PROTECTED] Sun Aug 07 04:15:08 2005 Return-path: <[EMAIL PROTECTED]> Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E1j7U-0004OF-00; Sun, 07 Aug 2005 04:15:08 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id CC09D5C00F; Sun, 7 Aug 2005 13:14:58 +0200 (CEST) Date: Sun, 7 Aug 2005 13:14:58 +0200 From: Maximilian Attems <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Nat is not working from 2.6.10-5 to 2.6.10-6 Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by Amavis (ClamAV) at stro.at Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.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 working for me on linux image 2.6.12 earlier images are no longer supported. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299545: marked as done (kernel-source-2.6.10: Please enable sk98lin hotplug support)
Your message dated Sat, 6 Aug 2005 18:45:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kernel-source-2.6.10: Please enable sk98lin hotplug support
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)
--
Received: (at submit) by bugs.debian.org; 14 Mar 2005 21:32:21 +
>From [EMAIL PROTECTED] Mon Mar 14 13:32:21 2005
Return-path: <[EMAIL PROTECTED]>
Received: from postfix3-2.free.fr [213.228.0.169]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DAxAi-0005gy-00; Mon, 14 Mar 2005 13:32:20 -0800
Received: from heffalump.sk2.org (villeurbanne-7-82-228-207-51.fbx.proxad.net
[82.228.207.51])
by postfix3-2.free.fr (Postfix) with ESMTP id 92202C1CB
for <[EMAIL PROTECTED]>; Mon, 14 Mar 2005 22:32:19 +0100 (CET)
Received: from steve by heffalump.sk2.org with local (Exim 4.44)
id 1DAxAX-0005yQ-2d
for [EMAIL PROTECTED]; Mon, 14 Mar 2005 22:32:09 +0100
Content-Type: multipart/mixed; boundary="===1738611426=="
MIME-Version: 1.0
From: Stephen Kitt <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.6.10: Please enable sk98lin hotplug support
X-Mailer: reportbug 3.8
Date: Mon, 14 Mar 2005 22:32:08 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.8 required=4.0 tests=BAYES_00,DOMAIN_BODY,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===1738611426==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: kernel-source-2.6.10
Version: 2.6.10-6
Severity: wishlist
Tags: patch
Hi,
The attached patch allows the sk98lin network driver to be loaded by
hotplug.
Regards,
Stephen Kitt
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-sk2-3
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
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
ii fileutils 5.2.1-2The GNU file management utilities
-- no debconf information
--===1738611426==
Content-Type: text/x-c; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="sk98lin.patch"
--- linux-old/drivers/net/sk98lin/skge.c2004-12-24 22:34:01.0
+0100
+++ linux/drivers/net/sk98lin/skge.c2005-02-25 12:19:48.0 +0100
@@ -5168,6 +5168,7 @@
{ PCI_VENDOR_ID_LINKSYS, 0x1064, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
{ 0, }
};
+MODULE_DEVICE_TABLE(pci, skge_pci_tbl);
static struct pci_driver skge_driver = {
.name = "skge",
--===1738611426==--
---
Received: (at 299545-done) by bugs.debian.org; 6 Aug 2005 16:46:07 +
>From [EMAIL PROTECTED] Sat Aug 06 09:46:07 2005
Return-path: <[EMAIL PROTECTED]>
Received: from baikonur.stro.at [213.239.196.228]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E1RoF-0007oS-00; Sat, 06 Aug 2005 09:46:07 -0700
Received: by baikonur.stro.at (Postfix, from userid 1001)
id A4AF75C00F; Sat, 6 Aug 2005 18:45:30 +0200 (CEST)
Date: Sat, 6 Aug 2005 18:45:30 +0200
From: Maximilian Attems <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: kernel-source-2.6.10: Please enable sk98lin hotplug support
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by Amavis (ClamAV) at stro.at
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.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.
Bug#317787: kernel-source-2.6.10: md memory leak
On Mon, 11 Jul 2005, Bailey, Scott wrote: > > anyway please report back if 2.6.12 works for you? > > Stay tuned. The system that was having the problem with 2.6.10 is an SMP > alpha box, but I usually build my own kernels anyway so I downloaded the > src.deb from your site and I'll try it out. Probably a few days until I > can see what it does. I bet the problem I'm whining about here is fixed, > since it was in 2.6.11. :-) hmm, i'm not sure the alpha configs from the snapshot i took 4 days ago, where already for 2.6.12. nobse is working on it, we should have soon 2.6.12 in the archive also for alpha, please try them out, when they get available. > BTW, I have been avoiding 2.6.11 because sooner or later (5 minutes to > 24 hours or so after booting) I start seeing SCSI underflow errors which > repeat infinitely and things on the system begin to progressively lock > up. > > Let me know how you want to handle it -- my thought is to consider this > problem closed and I will open a new report on 2.6.12 if I see SCSI > errors again. (I don't feel it is a hardware issue as I have no problems > at all with this on 2.6.10 and earlier.) I just don't know if you want > an official bug report or just an email from me. 2.6.12 and 2.6.13 (yes still rc) saw some scsi work if it is reproducible, with newer images seperate bug would be cool (could also be a clone of this one). best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317787: kernel-source-2.6.10: md memory leak
> no 2.6.10 is unsupported, we are switching to 2.6.12 atm > there is some delay due to the new unified packaging, > but if you just need x86 version you can test those out: > http://charm.itp.tuwien.ac.at/~mattems/ > > anyway please report back if 2.6.12 works for you? Stay tuned. The system that was having the problem with 2.6.10 is an SMP alpha box, but I usually build my own kernels anyway so I downloaded the src.deb from your site and I'll try it out. Probably a few days until I can see what it does. I bet the problem I'm whining about here is fixed, since it was in 2.6.11. :-) BTW, I have been avoiding 2.6.11 because sooner or later (5 minutes to 24 hours or so after booting) I start seeing SCSI underflow errors which repeat infinitely and things on the system begin to progressively lock up. Let me know how you want to handle it -- my thought is to consider this problem closed and I will open a new report on 2.6.12 if I see SCSI errors again. (I don't feel it is a hardware issue as I have no problems at all with this on 2.6.10 and earlier.) I just don't know if you want an official bug report or just an email from me. Thanks, Scott
Bug#317787: kernel-source-2.6.10: md memory leak
On Mon, 11 Jul 2005, R. Scott Bailey wrote: > The attached patch against 2.6.10-5, due to Neil Brown, corrects a > problem in 2.6.10 which causes the md driver to leak bios -- eventually > resulting in a OOM condition. The problem appears to have been corrected > upstream for 2.6.11, but my system hates that version :-) so I would > like to see this backported if you release additional 2.6.10 updates. I > have been running this patch on my system for over 4 days with no sign > of the slab growth that was forcing me to reboot a couple times a week > previously. > > Thanks, > > Scott Bailey > [EMAIL PROTECTED] no 2.6.10 is unsupported, we are switching to 2.6.12 atm there is some delay due to the new unified packaging, but if you just need x86 version you can test those out: http://charm.itp.tuwien.ac.at/~mattems/ > --- drivers/md/md.c.orig 2005-02-07 15:44:50.0 -0500 > +++ drivers/md/md.c 2005-07-06 10:55:56.0 -0400 missing one level deeper, as for usual kernel patches. ;-) anyway please report back if 2.6.12 works for you? -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317787: kernel-source-2.6.10: md memory leak
Package: kernel-source-2.6.10 Version: 2.6.10-5 Severity: important Tags: patch The attached patch against 2.6.10-5, due to Neil Brown, corrects a problem in 2.6.10 which causes the md driver to leak bios -- eventually resulting in a OOM condition. The problem appears to have been corrected upstream for 2.6.11, but my system hates that version :-) so I would like to see this backported if you release additional 2.6.10 updates. I have been running this patch on my system for over 4 days with no sign of the slab growth that was forcing me to reboot a couple times a week previously. Thanks, Scott Bailey [EMAIL PROTECTED] --- drivers/md/md.c.orig2005-02-07 15:44:50.0 -0500 +++ drivers/md/md.c 2005-07-06 10:55:56.0 -0400 @@ -336,8 +336,6 @@ struct completion event; int ret; - bio_get(bio); - rw |= (1 << BIO_RW_SYNC); bio->bi_bdev = bdev; -- System Information: Debian Release: testing/unstable Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-hamster.5c Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.15-7 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.10 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6.1-dev [libc6-dev] 2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the "make" util -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Looking for stable > 2.6.10 kernel-source package
On Sat, Jun 18, 2005 at 07:42:54PM -0700, Mark Fletcher wrote: > Hello all > > I'm looking for a stable 2.6.10 or later kernel source > package. The latest kernel-source package in stable > seems to be 2.6.8. I find this a bit odd since 2.6.10 > came out at Christmas last year... > > Can anyone advise where I can get a debian package of > 2.6.10 or later kernel source or should I just get it > from kernel.org? 2.6.8 was chosen for sarge, because at the time we had to make a choice, which was many, many months ago, it was the best choice. There was some discussion of switching to 2.6.10, but it was decided that it was too late in the release cycle. If you want a newer kernel, 2.6.11 is in unstable and this should drop straigt into sarge. 2.6.12 should be available shortly. 2.6.10 is no longer supported. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Looking for stable > 2.6.10 kernel-source package
Hello all I'm looking for a stable 2.6.10 or later kernel source package. The latest kernel-source package in stable seems to be 2.6.8. I find this a bit odd since 2.6.10 came out at Christmas last year... Can anyone advise where I can get a debian package of 2.6.10 or later kernel source or should I just get it from kernel.org? Cheers Mark __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303200: kernel-image-2.6.10-1-686: kernel BUG at fs/reiserfs/file.c:534!
severity 303200 important
tags 303200 moreinfo
thanks
> On Tue, 05 Apr 2005, Pau Capdevila wrote:
>
> > *** Please type your report below this line ***
> >
> > When the following occurs:
> >
> > Apr 3 21:59:31 localhost kernel: hda: dma_intr: status=0x51 {
> > DriveReady SeekComplete Error }
> > Apr 3 21:59:31 localhost kernel: hda: dma_intr: error=0x40 {
> > UncorrectableError }, LBAsect=57642412, sector=57642408
> > Apr 3 21:59:31 localhost kernel: ide: failed opcode was: unknown
> > Apr 3 21:59:31 localhost kernel: end_request: I/O error, dev hda,
> > sector 57642408
> > Apr 3 21:59:31 localhost kernel: [ cut here ]
> > Apr 3 21:59:31 localhost kernel: kernel BUG at fs/reiserfs/file.c:534!
> > Apr 3 21:59:31 localhost kernel: invalid operand: [#1]
> > Apr 3 21:59:31 localhost kernel: PREEMPT
> > Apr 3 21:59:31 localhost kernel: Modules linked in: tdfx lp ipv6 floppy
> > parport_pc parport pcspkr rtc snd_ens1371 snd_rawmidi snd_seq_device
> > snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore
> > snd_page_alloc gameport 8139cp 8139too mii i2c_piix4 i2c_core joydev
> > tsdev usbhid uhci_hcd usbcore pci_hotplug intel_agp agpgart
> > nls_iso8859_1 vfat fat nls_cp437 ntfs capability commoncap evdev apm
> > ide_cd cdrom mousedev psmouse reiserfs ext2 ext3 jbd mbcache ide_generic
> > siimage aec62xx trm290 alim15x3 hpt34x hpt366 ide_disk cmd64x piix
> > rz1000 slc90e66 generic cs5530 cs5520 sc1200 triflex atiixp pdc202xx_old
> > pdc202xx_new opti621 ns87415 cy82c693 amd74xx sis5513 via82cxxx
> > serverworks ide_core unix fbcon font bitblit vesafb cfbcopyarea
> > cfbimgblt cfbfillrect
> > Apr 3 21:59:31 localhost kernel: CPU:0
> > Apr 3 21:59:31 localhost kernel: EIP:
> > 0060:[pg0+341663470/1069863936]Not tainted VLI
> > Apr 3 21:59:31 localhost kernel: EFLAGS: 00210256 (2.6.10-1-686)
> > Apr 3 21:59:31 localhost kernel: EIP is at
> > reiserfs_allocate_blocks_for_region+0xb6e/0x1620 [reiserfs]
> > Apr 3 21:59:31 localhost kernel: eax: 2000 ebx: c2709ad8 ecx:
> > edx: c1028d20
> > Apr 3 21:59:31 localhost kernel: esi: 0001 edi: cbb4fedc ebp:
> > cf5a6018 esp: cbb4fcb0
> > Apr 3 21:59:31 localhost kernel: ds: 007b es: 007b ss: 0068
> > Apr 3 21:59:31 localhost kernel: Process amule (pid: 4705,
> > threadinfo=cbb4e000 task=cb8c0570)
> > Apr 3 21:59:31 localhost kernel: Stack: cbb4feac c8850bfc cbb4fdb4
> > fffb 000f 0003 c02a343e c1280ca8
> > Apr 3 21:59:31 localhost kernel:cbb4fd24 cbb4fd2c
> > c02a3651 c24b3fb8 c0157100 cbb4fd38 cb8c0570
> > Apr 3 21:59:31 localhost kernel:cbb4fd20 c0157100 00200296
> > 0002 c1280ca8 c8850bb0
> > Apr 3 21:59:31 localhost kernel: Call Trace:
> > Apr 3 21:59:31 localhost kernel: [io_schedule+14/32]
> > io_schedule+0xe/0x20
> > Apr 3 21:59:31 localhost kernel: [__wait_on_bit+81/112]
> > __wait_on_bit+0x51/0x70
> > Apr 3 21:59:31 localhost kernel: [sync_buffer+0/80]
> > sync_buffer+0x0/0x50
> > Apr 3 21:59:31 localhost kernel: [sync_buffer+0/80]
> > sync_buffer+0x0/0x50
> > Apr 3 21:59:31 localhost kernel: [free_buffer_head+57/112]
> > free_buffer_head+0x39/0x70
> > Apr 3 21:59:31 localhost kernel: [pg0+341666258/1069863936]
> > reiserfs_unprepare_pages+0x32/0x70 [reiserfs]
> > Apr 3 21:59:31 localhost kernel: [pg0+341669618/1069863936]
> > reiserfs_prepare_file_region_for_write+0x562/0x990 [reiserfs]
> > Apr 3 21:59:31 localhost kernel: [pg0+341672407/1069863936]
> > reiserfs_file_write+0x6b7/0x6d0 [reiserfs]
> > Apr 3 21:59:31 localhost kernel: [vfs_statfs+100/128]
> > vfs_statfs+0x64/0x80
> > Apr 3 21:59:31 localhost kernel: [vfs_statfs64+64/80]
> > vfs_statfs64+0x40/0x50
> > Apr 3 21:59:31 localhost kernel: [path_release+21/80]
> > path_release+0x15/0x50
> > Apr 3 21:59:31 localhost kernel: [sys_statfs64+143/208]
> > sys_statfs64+0x8f/0xd0
> > Apr 3 21:59:31 localhost kernel: [vfs_write+237/352]
> > vfs_write+0xed/0x160
> > Apr 3 21:59:31 localhost kernel: [sys_write+81/128]
> > sys_write+0x51/0x80
> > Apr 3 21:59:31 localhost kernel: [syscall_call+7/11]
> > syscall_call+0x7/0xb
> > Apr 3 21:59:31 localhost kernel: Code: 24 e8 c7 9e 00 00 8b 94 24 8c 01
> > 00 00 b8 60 5d 9a d4 89 44 24 04 8b 82 8c 00 00 00 eb e0 0f 0b 19 02 20
> > a6 9a d4 e9 00 ff ff ff <0f> 0b 16 02 20 a6 9a d4 e9 e5 fe ff ff 89 7c
> > 24 04 8b 84 24 88
> >
> > The system doesn't panic but X fall down and you must reset the machine.
> >
> well reiserfs doesn't work well with preempt,
> could you please try the 2.6.11 kernel-iamge.
> there preempt is disabled afair.
>
> also aboves looks like an hardware error of your harddisc,
> is it still alive?
> can you reproduce the dma error with ext3?
>
still awaiting answers to above question,
btw really downgrading.
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#303200: kernel-image-2.6.10-1-686: kernel BUG at fs/reiserfs/file.c:534!
Processing commands for [EMAIL PROTECTED]: > severity 303200 important Bug#303200: kernel-image-2.6.10-1-686: kernel BUG at fs/reiserfs/file.c:534! Severity set to `important'. > tags 303200 moreinfo Bug#303200: kernel-image-2.6.10-1-686: kernel BUG at fs/reiserfs/file.c:534! There were no tags set. Tags added: moreinfo > 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]
Processed: reassign 293195 to kernel-source-2.6.10
Processing commands for [EMAIL PROTECTED]: > reassign 293195 kernel-source-2.6.10 Bug#293195: concurrent usage of snd_cmipci and sk98lin freezes system Bug reassigned from package `kernel-source-2.6.8' to `kernel-source-2.6.10'. > 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#303200: kernel-image-2.6.10-1-686: kernel BUG at fs/reiserfs/file.c:534!
severity 303200 important
thanks
On Tue, 05 Apr 2005, Pau Capdevila wrote:
> *** Please type your report below this line ***
>
> When the following occurs:
>
> Apr 3 21:59:31 localhost kernel: hda: dma_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Apr 3 21:59:31 localhost kernel: hda: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=57642412, sector=57642408
> Apr 3 21:59:31 localhost kernel: ide: failed opcode was: unknown
> Apr 3 21:59:31 localhost kernel: end_request: I/O error, dev hda,
> sector 57642408
> Apr 3 21:59:31 localhost kernel: [ cut here ]
> Apr 3 21:59:31 localhost kernel: kernel BUG at fs/reiserfs/file.c:534!
> Apr 3 21:59:31 localhost kernel: invalid operand: [#1]
> Apr 3 21:59:31 localhost kernel: PREEMPT
> Apr 3 21:59:31 localhost kernel: Modules linked in: tdfx lp ipv6 floppy
> parport_pc parport pcspkr rtc snd_ens1371 snd_rawmidi snd_seq_device
> snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore
> snd_page_alloc gameport 8139cp 8139too mii i2c_piix4 i2c_core joydev
> tsdev usbhid uhci_hcd usbcore pci_hotplug intel_agp agpgart
> nls_iso8859_1 vfat fat nls_cp437 ntfs capability commoncap evdev apm
> ide_cd cdrom mousedev psmouse reiserfs ext2 ext3 jbd mbcache ide_generic
> siimage aec62xx trm290 alim15x3 hpt34x hpt366 ide_disk cmd64x piix
> rz1000 slc90e66 generic cs5530 cs5520 sc1200 triflex atiixp pdc202xx_old
> pdc202xx_new opti621 ns87415 cy82c693 amd74xx sis5513 via82cxxx
> serverworks ide_core unix fbcon font bitblit vesafb cfbcopyarea
> cfbimgblt cfbfillrect
> Apr 3 21:59:31 localhost kernel: CPU:0
> Apr 3 21:59:31 localhost kernel: EIP:
> 0060:[pg0+341663470/1069863936]Not tainted VLI
> Apr 3 21:59:31 localhost kernel: EFLAGS: 00210256 (2.6.10-1-686)
> Apr 3 21:59:31 localhost kernel: EIP is at
> reiserfs_allocate_blocks_for_region+0xb6e/0x1620 [reiserfs]
> Apr 3 21:59:31 localhost kernel: eax: 2000 ebx: c2709ad8 ecx:
> edx: c1028d20
> Apr 3 21:59:31 localhost kernel: esi: 0001 edi: cbb4fedc ebp:
> cf5a6018 esp: cbb4fcb0
> Apr 3 21:59:31 localhost kernel: ds: 007b es: 007b ss: 0068
> Apr 3 21:59:31 localhost kernel: Process amule (pid: 4705,
> threadinfo=cbb4e000 task=cb8c0570)
> Apr 3 21:59:31 localhost kernel: Stack: cbb4feac c8850bfc cbb4fdb4
> fffb 000f 0003 c02a343e c1280ca8
> Apr 3 21:59:31 localhost kernel:cbb4fd24 cbb4fd2c
> c02a3651 c24b3fb8 c0157100 cbb4fd38 cb8c0570
> Apr 3 21:59:31 localhost kernel:cbb4fd20 c0157100 00200296
> 0002 c1280ca8 c8850bb0
> Apr 3 21:59:31 localhost kernel: Call Trace:
> Apr 3 21:59:31 localhost kernel: [io_schedule+14/32]
> io_schedule+0xe/0x20
> Apr 3 21:59:31 localhost kernel: [__wait_on_bit+81/112]
> __wait_on_bit+0x51/0x70
> Apr 3 21:59:31 localhost kernel: [sync_buffer+0/80]
> sync_buffer+0x0/0x50
> Apr 3 21:59:31 localhost kernel: [sync_buffer+0/80]
> sync_buffer+0x0/0x50
> Apr 3 21:59:31 localhost kernel: [free_buffer_head+57/112]
> free_buffer_head+0x39/0x70
> Apr 3 21:59:31 localhost kernel: [pg0+341666258/1069863936]
> reiserfs_unprepare_pages+0x32/0x70 [reiserfs]
> Apr 3 21:59:31 localhost kernel: [pg0+341669618/1069863936]
> reiserfs_prepare_file_region_for_write+0x562/0x990 [reiserfs]
> Apr 3 21:59:31 localhost kernel: [pg0+341672407/1069863936]
> reiserfs_file_write+0x6b7/0x6d0 [reiserfs]
> Apr 3 21:59:31 localhost kernel: [vfs_statfs+100/128]
> vfs_statfs+0x64/0x80
> Apr 3 21:59:31 localhost kernel: [vfs_statfs64+64/80]
> vfs_statfs64+0x40/0x50
> Apr 3 21:59:31 localhost kernel: [path_release+21/80]
> path_release+0x15/0x50
> Apr 3 21:59:31 localhost kernel: [sys_statfs64+143/208]
> sys_statfs64+0x8f/0xd0
> Apr 3 21:59:31 localhost kernel: [vfs_write+237/352]
> vfs_write+0xed/0x160
> Apr 3 21:59:31 localhost kernel: [sys_write+81/128]
> sys_write+0x51/0x80
> Apr 3 21:59:31 localhost kernel: [syscall_call+7/11]
> syscall_call+0x7/0xb
> Apr 3 21:59:31 localhost kernel: Code: 24 e8 c7 9e 00 00 8b 94 24 8c 01
> 00 00 b8 60 5d 9a d4 89 44 24 04 8b 82 8c 00 00 00 eb e0 0f 0b 19 02 20
> a6 9a d4 e9 00 ff ff ff <0f> 0b 16 02 20 a6 9a d4 e9 e5 fe ff ff 89 7c
> 24 04 8b 84 24 88
>
> The system doesn't panic but X fall down and you must reset the machine.
>
well reiserfs doesn't work well with preempt,
could you please try the 2.6.11 kernel-iamge.
there preempt is disabled afair.
also aboves looks like an hardware error of your harddisc,
is it still alive?
can you reproduce the dma error with ext3?
thanks for your reply.
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
On Sun, 2005-05-15 at 12:10 +0200, Svante Signell wrote: > On Sat, 2005-05-14 at 20:19 +0200, maximilian attems wrote: > > tags 308878 moreinfo > > thanks Installing the updated initrd-tools (0.1.79) gives no error in cpio with /lib/ld-linux.so.2 not found: #> apt-get install --reinstall kernel-image-2.6.10-1-686-smp ... Unpacking replacement kernel-image-2.6.10-1-686-smp ... Setting up kernel-image-2.6.10-1-686-smp (2.6.10-6) ... Not touching initrd symlinks since we are being reinstalled (2.6.10-6) Not updating image symbolic links since we are being updated (2.6.10-6 compared to before the upgrade: #> apt-get install --reinstall kernel-image-2.6.10-1-686-smp ... Unpacking replacement kernel-image-2.6.10-1-686-smp ... Setting up kernel-image-2.6.10-1-686-smp (2.6.10-6) ... cpio: /lib/ld-linux.so.2 (0xb7fea000): No such file or directory cpio: (0xe000): No such file or directory Not touching initrd symlinks since we are being reinstalled (2.6.10-6) Not updating image symbolic links since we are being updated (2.6.10-6) Now the kernel boots!!! Problem solved. >From the Debian changelog of initrd-tools-0.1.79: * GOTO Masanori - Make mkinitrd work with new ldd format which change is introduced in glibc 2.3.4. (Closes: #301455, #303281) This change also fixes amd64 mkinitrd breakage. (Closes: #279382, #292080, #295412, #295422, #297724) Installed libc is from experimental: ii libc62.3.5-1 GNU C Library: Shared libraries and Timezone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
On Sat, 2005-05-14 at 20:19 +0200, maximilian attems wrote: > tags 308878 moreinfo > thanks > > On Fri, 13 May 2005, Svante Signell wrote: > > > Package: kernel-image > > Version: 2.6.10-1-686-smp and 2.6.11-1-686-smp ... > please send in working dmesg of 2.6.8 or 2.6.9. Attached. > are you using scsi root? > if yes it's a initrd bug, you might want to look at #298736 No, the board has built-in SCSI but all disks are IDE. Root is at /dev/hda1, see the fstab entry: /dev/hda1 / ext3,ext2 defaults0 1 > > -- > maks Linux version 2.6.9-1-686-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-2)) #1 SMP Thu Nov 25 02:24:54 EST 2004 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 27ff (usable) BIOS-e820: 27ff - 27ff8000 (ACPI data) BIOS-e820: 27ff8000 - 2800 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: - 0001 (reserved) 0MB HIGHMEM available. 639MB LOWMEM available. found SMP MP-table at 000fb4b0 On node 0 totalpages: 163824 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 159728 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 DMI 2.0 present. ACPI: RSDP (v000 AMI ) @ 0x000faf40 ACPI: RSDT (v001 AMIINT 0x0010 MSFT 0x0097) @ 0x27ff ACPI: FADT (v001 AMIINT 0x0010 MSFT 0x0097) @ 0x27ff0030 ACPI: MADT (v001 AMIINT DRAC-100 0x0009 MSFT 0x0097) @ 0x27ff00b0 ACPI: DSDT (v001MSI AMIACPI 0x1000 MSFT 0x010a) @ 0x ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 6:6 APIC version 17 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 6:6 APIC version 17 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Built 1 zonelists Kernel command line: auto BOOT_IMAGE=269-686-smp ro root=301 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 463.948 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 641136k/655296k available (1668k kernel code, 13660k reserved, 731k data, 184k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 917.50 BogoMIPS (lpj=458752) Security Scaffold v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: 0183fbff CPU: After vendor identify, caps: 0183fbff CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K CPU: After all inits, caps:0183fbff 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Enabling fast FPU save and restore... done. Checking 'hlt' instruction... OK. CPU0: Intel Celeron (Mendocino) stepping 05 per-CPU timeslice cutoff: 366.40 usecs. task migration cache decay timeout: 1 msecs. Booting processor 1/1 eip 3000 Initializing CPU#1 Calibrating delay loop... 927.74 BogoMIPS (lpj=463872) CPU: After generic identify, caps: 0183fbff CPU: After vendor identify, caps: 0183fbff CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K CPU: After all inits, caps:0183fbff 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#1. CPU1: Intel Celeron (Mendocino) stepping 05 Total of 2 processors activated (1845.24 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 checking TSC synchronization across 2 CPUs: passed. Brought up 2 CPUs checking if image is initramfs...it isn't (ungzip failed); looks like an initrd Freeing initrd memory: 4572k freed NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xfdb91, last bus=1 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040816 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [NRTH] (00:00) PCI: Probing PCI hardware (bus 00) ACPI: PCI Int
Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
tags 308878 moreinfo thanks On Fri, 13 May 2005, Svante Signell wrote: > Package: kernel-image > Version: 2.6.10-1-686-smp and 2.6.11-1-686-smp > Severity: Grave > > The latest smp kernels fails to boot due to the root partiton is not > found, resulting in a kernel panic. Kernels 2.6.8 and 2.6.9 boot OK. > Hardware is dual Celerons. > > When installing these kernels I get an error not seen before: > #> apt-get install --reinstall kernel-image-2.6.10-1-686-smp > Unpacking replacement kernel-image-2.6.10-1-686-smp ... > Setting up kernel-image-2.6.10-1-686-smp (2.6.10-6) ... > cpio: /lib/ld-linux.so.2 (0xb7fea000): No such file or directory > cpio: (0xe000): No such file or directory > Not touching initrd symlinks since we are being reinstalled (2.6.10-6) > Not updating image symbolic links since we are being updated (2.6.10-6) > ... > > Attached is a diff between the configurations files of 2.6.9 and 2.6.10. > > Thanks, > -- > Svante Signell <[EMAIL PROTECTED]> please send in working dmesg of 2.6.8 or 2.6.9. are you using scsi root? if yes it's a initrd bug, you might want to look at #298736 -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
Processing commands for [EMAIL PROTECTED]: > tags 308878 moreinfo Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot There were no tags set. Tags added: moreinfo > 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#296579: initrd-tools: Disabling unloading of ide modules with kernel 2.6.10
This problem is still there for 2.6.11 (and up, probably) As it's not problematic to try to rmmod, maybe we can just consider it a cosmetic bug and do something like: --- init2005-04-10 16:14:12.0 +0200 +++ init.new2005-05-14 09:01:24.0 +0200 @@ -300,7 +300,7 @@ set -- /sys/bus/pci/drivers/$ret/*:* unset IFS if [ ! -h "$1" ]; then - rmmod $i + rmmod $i > /dev/null 2>&1 fi done This makes the bootup just a bit less noisy, and less "scary". I agree that these modules should probably not be loaded in the first place. Maybe hotplug-ng -in-initrd is the (long-term) answer? -- M -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
Processing commands for [EMAIL PROTECTED]: > reassign 308878 kernel-image-2.6.10-1-686-smp Bug#308878: kernel-image-2.6.10+11-1-686-smp fails to boot Bug reassigned from package `kernel' to `kernel-image-2.6.10-1-686-smp'. > -- 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#308878: kernel-image-2.6.10+11-1-686-smp fails to boot
Package: kernel-image Version: 2.6.10-1-686-smp and 2.6.11-1-686-smp Severity: Grave The latest smp kernels fails to boot due to the root partiton is not found, resulting in a kernel panic. Kernels 2.6.8 and 2.6.9 boot OK. Hardware is dual Celerons. When installing these kernels I get an error not seen before: #> apt-get install --reinstall kernel-image-2.6.10-1-686-smp Unpacking replacement kernel-image-2.6.10-1-686-smp ... Setting up kernel-image-2.6.10-1-686-smp (2.6.10-6) ... cpio: /lib/ld-linux.so.2 (0xb7fea000): No such file or directory cpio: (0xe000): No such file or directory Not touching initrd symlinks since we are being reinstalled (2.6.10-6) Not updating image symbolic links since we are being updated (2.6.10-6) ... Attached is a diff between the configurations files of 2.6.9 and 2.6.10. Thanks, -- Svante Signell <[EMAIL PROTECTED]> --- /boot/config-2.6.9-1-686-smp2004-11-25 08:21:15.0 +0100 +++ /boot/config-2.6.10-1-686-smp 2005-03-11 07:43:55.0 +0100 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit -# Linux kernel version: 2.6.9-1-686-smp -# Thu Nov 25 02:21:15 2004 +# Linux kernel version: 2.6.10-1-686-smp +# Fri Mar 11 01:43:55 2005 # CONFIG_X86=y CONFIG_MMU=y @@ -16,6 +16,7 @@ # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y +CONFIG_LOCK_KERNEL=y # # General setup @@ -30,6 +31,7 @@ # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=15 CONFIG_HOTPLUG=y +CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y @@ -37,12 +39,12 @@ # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y -CONFIG_IOSCHED_NOOP=y -CONFIG_IOSCHED_AS=y -CONFIG_IOSCHED_DEADLINE=y -CONFIG_IOSCHED_CFQ=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set 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 # @@ -53,6 +55,7 @@ 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 @@ -82,6 +85,7 @@ # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set +# CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set @@ -151,10 +155,12 @@ CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m +CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m +CONFIG_ACPI_IBM=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=2001 # CONFIG_ACPI_DEBUG is not set @@ -181,21 +187,21 @@ # CPU Frequency scaling # CONFIG_CPU_FREQ=y +# CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_PROC_INTF=m CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m -CONFIG_CPU_FREQ_GOV_ONDEMAND=m # CONFIG_CPU_FREQ_24_API is not set +CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_TABLE=m # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=m -# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set CONFIG_X86_POWERNOW_K6=m CONFIG_X86_POWERNOW_K7=m CONFIG_X86_POWERNOW_K7_ACPI=y @@ -203,17 +209,23 @@ CONFIG_X86_POWERNOW_K8_ACPI=y CONFIG_X86_GX_SUSPMOD=m CONFIG_X86_SPEEDSTEP_CENTRINO=m -CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y +CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_ICH=m CONFIG_X86_SPEEDSTEP_SMI=m CONFIG_X86_P4_CLOCKMOD=m -CONFIG_X86_SPEEDSTEP_LIB=m -CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y +CONFIG_X86_CPUFREQ_NFORCE2=m CONFIG_X86_LONGRUN=m CONFIG_X86_LONGHAUL=m # +# shared options +# +# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set +CONFIG_X86_SPEEDSTEP_LIB=m +CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y + +# # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y @@ -233,12 +245,18 @@ CONFIG_SCx200=m # -# PCMCIA/CardBus support +# PCCARD (PCMCIA/CardBus) support # -CONFIG_PCMCIA=m +CONFIG_PCCARD=m # CONFIG_PCMCIA_DEBUG is not set -CONFIG_YENTA=m +# CONFIG_PCMCIA_OBSOLETE is not set +CONFIG_PCMCIA=m CONFIG_CARDBUS=y + +# +# PC-card bridges +# +CONFIG_YENTA=m CONFIG_PD6729=m CONFIG_I82092=m CONFIG_I82365=m @@ -343,6 +361,7 @@ CONFIG_MTD_PNC2000=m CONFIG_MTD_SC520CDP=m CONFIG_MTD_NETSC520=m +CONFIG_MTD_TS5500=m CONFIG_MTD_SBC_GXX=m CONFIG_MTD_ELAN_104NC=m CONFIG_MTD_SCx200_DOCFLASH=m @@ -354,7 +373,7 @@ CONFIG_MTD_DILNETPC_BOOTSIZE=0x8 # CONFIG_MTD_L440GX is not set CONFIG_MTD_PCI=m -# CONFIG_MTD_PCMCIA is not set +CONFIG_MTD_PCMCIA=m # # Self-contained MTD device drivers @@ -416,6 +435,7 @@ CONFIG_ISAPNP=y CONFIG_PNPBIOS=y CONFIG_PNPBIOS_PROC_FS=y +CONFIG_PNPACPI=y # # Block devices @@ -464,9 +484,22 @@ CONFIG_BLK_DEV_SX8=m # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y +CONFIG_BLK_DE
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
hello, On Tue, 03 May 2005, Toni Mueller wrote: > On Tue, 03.05.2005 at 17:02:22 +0200, maximilian attems <[EMAIL PROTECTED]> > wrote: > > > > in oom cases 2.6.11 is very recommended as it has nice fixes from -aa > > in that release. > > thanks for this statement. I almost assumed as much after some research > on Google... some remarks, though: > > I have an identical machine running 2.6.10 with no problems. Why does > one machine exhibit this problem, and the other doesn't? have you checked the ratio in /proc/sys/vm/swappiness on both? see on the topic http://kerneltrap.org/node/3000 60 is default iirc beside this no idea. > > do you have enough swap, is it activated? > > $ free > total used free sharedbuffers > cached > Mem: 1033256 505200 528056 0 118348 > 168228 > -/+ buffers/cache: 218624 814632 > Swap: 2104220 02104220 > > > Should be sufficient... ;-) yes, is aboves 0 after boot, what happens if you eat up memory resulting in a swap storm, does the swap get used? regards. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
Hi, On Tue, 03.05.2005 at 17:02:22 +0200, maximilian attems <[EMAIL PROTECTED]> wrote: > On Tue, 03 May 2005, Toni Mueller wrote: > > On Tue, 03.05.2005 at 12:16:51 +0200, maximilian attems <[EMAIL PROTECTED]> > > wrote: > > oom-killer: gfp_mask=0xd0 > > oom-killer: gfp_mask=0x1d2 > > oom-killer: gfp_mask=0x4d0 > > > > > anyway please try kernel-image-2.6.11 from unstable! > > > > This is currently impossible, due to #306930. Currently, I try to fix > > this (ie, create a local kernel-nonfree-... package). > > in oom cases 2.6.11 is very recommended as it has nice fixes from -aa > in that release. thanks for this statement. I almost assumed as much after some research on Google... some remarks, though: I have an identical machine running 2.6.10 with no problems. Why does one machine exhibit this problem, and the other doesn't? > here you'lll find the intersting non-free bits: > http://www.acm.cs.rpi.edu/~dilinger/kernel-source-nonfree-2.6.11/ Thanks, this may speed things up considerably. > do you have enough swap, is it activated? $ free total used free sharedbuffers cached Mem: 1033256 505200 528056 0 118348 168228 -/+ buffers/cache: 218624 814632 Swap: 2104220 02104220 Should be sufficient... ;-) Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
On Tue, 03 May 2005, Toni Mueller wrote: > On Tue, 03.05.2005 at 12:16:51 +0200, maximilian attems <[EMAIL PROTECTED]> > wrote: > > On Tue, 03 May 2005, Toni Mueller wrote: > > > Package: kernel-image-2.6.10-1-686-smp > > > Severity: important > > > > > > I find error messages like the one above (not sure about the actual > > > value of gfp_mask) on a regular basis in the logs. Sometimes I just find > > > out hard because the machine simply crashes shortly after. This makes > > > the machine in question unreliable, crashing at least every few weeks. > > > Therefore I'm flagging this bug as "important". > > > > > > Hardware is a rather new IBM x205, with ServeRAID4, GigE, and 1GB RAM. > > > > you didn't report the error message?! > > dmesg after boot would also be usefull. > > Ok. I thought I was clear enough. The error messages I see are at > least: > > oom-killer: gfp_mask=0xd0 > oom-killer: gfp_mask=0x1d2 > oom-killer: gfp_mask=0x4d0 > > > > anyway please try kernel-image-2.6.11 from unstable! > > This is currently impossible, due to #306930. Currently, I try to fix > this (ie, create a local kernel-nonfree-... package). in oom cases 2.6.11 is very recommended as it has nice fixes from -aa in that release. here you'lll find the intersting non-free bits: http://www.acm.cs.rpi.edu/~dilinger/kernel-source-nonfree-2.6.11/ do you have enough swap, is it activated? thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
Hi, On Tue, 03.05.2005 at 12:16:51 +0200, maximilian attems <[EMAIL PROTECTED]> wrote: > On Tue, 03 May 2005, Toni Mueller wrote: > > Package: kernel-image-2.6.10-1-686-smp > > Severity: important > > > > I find error messages like the one above (not sure about the actual > > value of gfp_mask) on a regular basis in the logs. Sometimes I just find > > out hard because the machine simply crashes shortly after. This makes > > the machine in question unreliable, crashing at least every few weeks. > > Therefore I'm flagging this bug as "important". > > > > Hardware is a rather new IBM x205, with ServeRAID4, GigE, and 1GB RAM. > > you didn't report the error message?! > dmesg after boot would also be usefull. Ok. I thought I was clear enough. The error messages I see are at least: oom-killer: gfp_mask=0xd0 oom-killer: gfp_mask=0x1d2 oom-killer: gfp_mask=0x4d0 > anyway please try kernel-image-2.6.11 from unstable! This is currently impossible, due to #306930. Currently, I try to fix this (ie, create a local kernel-nonfree-... package). Dmesg: Linux version 2.6.10-1-686-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-6)) #1 SMP Tue Jan 18 03:03:11 EST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 3ffd (usable) BIOS-e820: 3ffd - 3ffd8000 (ACPI data) BIOS-e820: 3ffd8000 - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000fa460 On node 0 totalpages: 262096 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:16 HighMem zone: 32720 pages, LIFO batch:7 DMI 2.3 present. ACPI: RSDP (v000 IBM ) @ 0x000fe030 ACPI: RSDT (v001 IBMM51G 0x0001 IBM 0x0001) @ 0x3ffd ACPI: FADT (v001 IBMM51G 0x0001 IBM 0x0001) @ 0x3ffd0125 ACPI: ASF! (v016IBM 0x0100 0x) @ 0x3ffd0030 ACPI: MADT (v001 IBMM51G 0x0001 IBM 0x0001) @ 0x3ffd00cb ACPI: DSDT (v001IBM M51G0x1000 MSFT 0x010a) @ 0x ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:2 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Built 1 zonelists Kernel command line: auto BOOT_IMAGE=2610 ro root=801 mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 2666.565 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1030856k/1048384k available (1700k kernel code, 16960k reserved, 711k data, 200k init, 130880k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 5275.64 BogoMIPS (lpj=2637824) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: bfebfbff 4400 CPU: After vendor identify, caps: bfebfbff 4400 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Hyper-Threading is disabled CPU: After all inits, caps: bfebfbff 0080 4400 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. CPU0: Intel(R) Pentium(R) 4 CPU 2.66GHz stepping 09 per-CPU timeslice cutoff: 1463.12 usecs. task migration cache decay timeout: 2 msecs. Total of 1 processors activated (5275.64 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 Brought up 1 CPUs CPU0: domain 0: span 01 groups: 01 domain 1: span 01 groups: 01 checking if image is initramfs...it isn't (bad gzip magic
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
tags 307457 moreinfo stop On Tue, 03 May 2005, Toni Mueller wrote: > Package: kernel-image-2.6.10-1-686-smp > Severity: important > > > > Hello, > > I find error messages like the one above (not sure about the actual > value of gfp_mask) on a regular basis in the logs. Sometimes I just find > out hard because the machine simply crashes shortly after. This makes > the machine in question unreliable, crashing at least every few weeks. > Therefore I'm flagging this bug as "important". > > Hardware is a rather new IBM x205, with ServeRAID4, GigE, and 1GB RAM. you didn't report the error message?! dmesg after boot would also be usefull. anyway please try kernel-image-2.6.11 from unstable! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
Processing commands for [EMAIL PROTECTED]: > tags 307457 moreinfo Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often 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#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
Package: kernel-image-2.6.10-1-686-smp Severity: important Hello, I find error messages like the one above (not sure about the actual value of gfp_mask) on a regular basis in the logs. Sometimes I just find out hard because the machine simply crashes shortly after. This makes the machine in question unreliable, crashing at least every few weeks. Therefore I'm flagging this bug as "important". Hardware is a rather new IBM x205, with ServeRAID4, GigE, and 1GB RAM. Best, --Toni++ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306355: linux-image-2.6.10-5-k7-smp: fails to boot on udev system
On Mon, May 02, 2005 at 10:47:21PM +0300, Pasi Savolainen wrote: > On 5/2/05, Colin Watson <[EMAIL PROTECTED]> wrote: > > On Tue, Apr 26, 2005 at 03:22:49AM +0300, Pasi Savolainen wrote: > > > Package: linux-image-2.6.10-5-k7-smp > > > Version: 2.6.10-34 > > > Severity: important > > > > This appears to be a bug report against an Ubuntu kernel. Please report > > those to Ubuntu, not Debian. > > > > Is there anything in particular that misled you into reporting this bug > > to Debian? If so, perhaps we could fix it. > > Looks like reportbug misbehaviour, can't tell what caused it. Modern versions of reportbug check lsb_release and use that to decide where to report bugs by default. What does "lsb_release -a" show on your system? -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306355: linux-image-2.6.10-5-k7-smp: fails to boot on udev system
On Tue, Apr 26, 2005 at 03:22:49AM +0300, Pasi Savolainen wrote: > Package: linux-image-2.6.10-5-k7-smp > Version: 2.6.10-34 > Severity: important This appears to be a bug report against an Ubuntu kernel. Please report those to Ubuntu, not Debian. Is there anything in particular that misled you into reporting this bug to Debian? If so, perhaps we could fix it. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306355: linux-image-2.6.10-5-k7-smp: fails to boot on udev system
On 5/2/05, Colin Watson <[EMAIL PROTECTED]> wrote: > On Tue, Apr 26, 2005 at 03:22:49AM +0300, Pasi Savolainen wrote: > > Package: linux-image-2.6.10-5-k7-smp > > Version: 2.6.10-34 > > Severity: important > > This appears to be a bug report against an Ubuntu kernel. Please report > those to Ubuntu, not Debian. > > Is there anything in particular that misled you into reporting this bug > to Debian? If so, perhaps we could fix it. Looks like reportbug misbehaviour, can't tell what caused it. -- psi -- http://iki.fi/psavo
