Bug#362056: More board combinations tested
If the target machine is configured with two identical 3C905B boards: eth0 gets assigned to IRQ 11 and shared with uhci_hcd:usb1. eth1 gets assigned to IRQ 10 and shared with cs46xx. With two 3C509B boards installed and configured, the kernel can also assign an IRQ to one ISA-PNP board. An SMC-ultra gets assigned to IRQ 5. All three of these boards come up properly, and communicate. But, if there is a PCI Tulip board installed, its driver module is loaded automatically at boot time after 3c59x. Then, the command ifconfig eth2 192.168.136.55 causes the machine to freeze instantly. No error messages are available. This happens whether the ISA board is plugged in or not. There's nothing wrong with the Tulip board. It works on other machines. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#100421: Quo te for pat hysler
Hi, My colleague has recei ved your form applied. http://www.geocities.com/EllenBowman4646 Please hit the site above, Our office shall then re-confirm your info. With Ref to: pat hysler and your past track record is not an issue. All debt consol types have been Ap prove d for you pat hysler say never: http://www.geocities.com/JosefinaGlover1887/a.htm Respects, Josie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361741: Fail to mount root filesystem
On Mon, 10 Apr 2006, Cesare Leonardi wrote: > Begin: running /scripts/local-premount... > Attempting manual resume > Done. > mount: mounting /dev/hda2 on /root failed: no such device > Begin: running /scripts/log-bottom... > Done. > Done. > Begin: running /scripts/init-bottom... > mount: Mounting /root/dev on /dev/.static/dev failed: no such device or > directory > Done. > mount: Mounting /sys on /root/sys failed: no such file or directory > mount: Mounting /proc on /root/proc failed: no such file or directory > Target filesystem doesn't have /sbin/init > > If helps, i have seen the following modules inside /proc/modules: looks good from the udev side sofar, but missing fs module. > As you can see the modules to mount my ATA (not sata) drive are in > place. I have tryed to mount root manually: > mount /dev/hda2 / > but it fails. can you please post: /usr/lib/klibc/bin/fstype < /dev/hda2 > klibc-utils 1.3.3-1 that one seems to be confused lately since it got new lvm2 support. ragards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#362631: linux-image-2.6.16-1: fails to mount root device
Processing commands for [EMAIL PROTECTED]: > reassign 362631 klibc-utils Bug#362631: linux-image-2.6.16-1: fails to mount root device Bug reassigned from package `initramfs-tools' to `klibc-utils'. > retitle 362631 fstype recognises ext3 as lvm2 Bug#362631: linux-image-2.6.16-1: fails to mount root device Changed Bug title. > 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#362631: linux-image-2.6.16-1: fails to mount root device
reassign 362631 klibc-utils retitle 362631 fstype recognises ext3 as lvm2 stop On Fri, 14 Apr 2006, C. Dominik Bódi wrote: > > I tried something in the rescue shell: I mounted /dev/hda8 to /root manually > using the following command: > mount -t ext3 /dev/hda8 /root gone to an online debugging irc debugging session # /usr/lib/klibc/bin/fstype < /dev/hda8 FSTYPE=lvm2 FSSIZE=0 the partition was used as lvm2 previously but is now an ext3 root. fdisk -l /dev/hda Disk /dev/hda: 80.0 GB, 80060424192 bytes 255 heads, 63 sectors/track, 9733 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1243219535008+ 7 HPFS/NTFS /dev/hda22433973358645282+ 5 Extended /dev/hda52433486419535008+ b W95 FAT32 /dev/hda648654927 506016 82 Linux swap / Solaris /dev/hda749284957 240943+ 83 Linux /dev/hda84958973338363188+ 83 Linux -- maks
Processed: severity of 358397 is serious
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.16 > severity 358397 serious Bug#358397: initramfs-tools: Fails to install Severity set to `serious'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362631: linux-image-2.6.16-1: fails to mount root device
On Fri, 14 Apr 2006, C. Dominik Bódi wrote: > Yes, booting that kernel gets me into the rescue shell. All /dev/hda? > partitions that should exist do so, as well. > > Here's a list of modules that are loaded: > ide_disk > atiixp so udev is doing the job, but i don't see any fs in your aboves list. > I am using grub, with an extra partition /dev/hda7 set up as /boot. > > /proc/cmdline is > root=/dev/hda8 ro lapic looks sane > I did install debian again, once I had upgraded it to unstable, the same bug > happened. I did keep the kernel from testing this time (see original report > for version), which boots without having this problem. > > I tried something in the rescue shell: I mounted /dev/hda8 to /root manually > using the following command: > mount -t ext3 /dev/hda8 /root > > Then I exited the rescue shell and the system did boot normally. what does simply exiting the shell do? can you please post all the initramfs-tools lines you see when you get dropped into the shell. regards -- maks
Processed: severity of 361741 is important
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.16 > severity 361741 important Bug#361741: Fail to mount root filesystem Severity set to `important'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 361741
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.16 > tags 361741 moreinfo Bug#361741: Fail to mount root filesystem There were no tags set. Tags added: moreinfo > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362064: udev: udev tries to write to an installed, working initrd without asking
Le vendredi 14 avril 2006 à 21:24 +0200, maximilian attems a écrit : > Having evms call update-initramfs at install time is completely gratuitous, > because the system *won't* be set up for evms at the time of the evms > postinst: either the update-initramfs will be a complete no-op and have to > be repeated later once evms is set up, or it won't be a no-op -- meaning it > will likely have done something undesirable, unrelated to evms. update-initramfs isn't a noop, it happily include all the needed evms root support, as evms added its hooks and calls update-initramfs. Specifically, if you forget to do some piece of configuration, you now have enough piece in the initramfs to recover your system. This is by design. > So I don't see any real benefit to having all of these tools rebuilding the > initramfs repeatedly during an upgrade cycle. Theoretically it would be > nice to know as soon as a package is installed that it will break the > initramfs, but using update-initramfs doesn't do this: the only way to be > sure whether a new initramfs is broken is to try to boot from it. Since we > can't force reboots during an upgrade (especially not once for each hook!), > there is no significant increase in predictability by using this method, and > users are better off if the upgrade doesn't touch the existing, working > initramfs images at all. I'm only reading this thread intermittantly, sorry for the lag. The bug here is generally that dpkg doesn't have a "do this last and once" hook. I agree that it would be nice if it didn't burn time on each step of the way. Having a backup file might make sense. Then again, if you've just installed something to get support, why should this support *not* be available everywhere? Requiring the user to do a step that a computer ought to have done doesn't make sense. tks, Jeff Bailey -- Although when you're in the situation that RMS is telling you that you're being too ideological about freedom, maybe, just maybe, it's true. - Matthew Wilcox signature.asc Description: Ceci est une partie de message numériquement signée
Bug#362631: linux-image-2.6.16-1: fails to mount root device
Yes, booting that kernel gets me into the rescue shell. All /dev/hda? partitions that should exist do so, as well. Here's a list of modules that are loaded: usbhid 8139too ide_cd cdrom ide_disk generic ohci1394 ieee1394 8139cp mii ehci_hcd ohci_hcd atiixp ide_core usbcore thermal processor fan I am using grub, with an extra partition /dev/hda7 set up as /boot. /proc/cmdline is root=/dev/hda8 ro lapic I did install debian again, once I had upgraded it to unstable, the same bug happened. I did keep the kernel from testing this time (see original report for version), which boots without having this problem. I tried something in the rescue shell: I mounted /dev/hda8 to /root manually using the following command: mount -t ext3 /dev/hda8 /root Then I exited the rescue shell and the system did boot normally. Regards, Dominik pgphBndVPsT81.pgp Description: PGP signature
Bug#362064: udev: udev tries to write to an installed, working initrd without asking
initramfs differs from initrd as it's no fs, but just an archive. you can easily append stuff to it that wasn't inside yet. On Thu, 13 Apr 2006, Steve Langasek wrote: > On Thu, Apr 13, 2006 at 08:18:59PM +0200, maximilian attems wrote: > > by design initramfs-tools needs that: > > a) allows each hook to add it's boot device detection scripts > > if you want evms root you simply install evms. > > thanks to it's initramfs hook you get evms root support. > > You can never "simply install evms" and get evms root support. There are > other configuration changes that must be made to the installation to set up > a system for evms root that isn't currently using it, including: > > - setting up an evms volume (probably) > - changing the references in /etc/fstab to point to the new device > (definitely) sure and point the $bootloader to your new location. but i bet many user will forget to regnerate your initramfs in those cases. > Having evms call update-initramfs at install time is completely gratuitous, > because the system *won't* be set up for evms at the time of the evms > postinst: either the update-initramfs will be a complete no-op and have to > be repeated later once evms is set up, or it won't be a no-op -- meaning it > will likely have done something undesirable, unrelated to evms. update-initramfs isn't a noop, it happily include all the needed evms root support, as evms added its hooks and calls update-initramfs. > > b) prevents races in install order: > > mkinitramfs-kpkg run by newer linux-image when not _all_ hooks are > > yet unpacked, so latest updated initramfs has all content. > > thus _only_ latest initramfs gets updated. > > And this is bad, because all you're doing is covering up bugs. The bug is > either: > > - some package in the chain has broken dependencies, so packages it should > depend on are not guaranteed to be in 'installed' state at the time its > postinst runs, or linux-image doesn't directly depend on an initramfs-tools hook like udev so i don't understand that point. > - a package provides functionality which is called opportunistically by > packages that do not (and should not) depend on it, but the package is not > guaranteed to do the right thing when the interface is called while in > state: unpacked. > Based on the bug you pointed me to in the previous IRC discussion, it > appears that there is (or was) an instance of the second of these in > initramfs-tools -- where update-initramfs was called, overwrote the initrd > with something broken, and exited 0. Repeatedly calling update-initramfs > until it does the right thing isn't a good answer. My system shouldn't be > left unbootable by an interrupted apt upgrade, nor should it be left > unbootable if I try to build an initramfs by hand while the package is > unconfigured (perhaps without being aware of this). > > Now, let's look closer at the race condition issue, which I admit is a real > concern. Suppose that you have a system with root on lvm2 already, and > initramfs-tools (or linux-image) is configured while lvm2 is unpacked but > not yet configured -- and because it's not configured, it can't do the right > thing. What should happen is: > > - update-initramfs calls the lvm2 hook script > - the lvm2 hook script, because lvm2 is not currently usable, throws an > error > - update-initramfs catches the error, and the postinst of whichever package > is involved aborts -- allowing the admin to retry after the lvm2 package > has been configured. > > With the current behavior, where you rebuild the initramfs repeatedly and > hope it comes out right at the end, you are throwing away very valuable > information when it is possible to *know* that an initramfs is not bootable. > And once you stop doing that (which isn't acceptable in the first place), > you stop needing to update the initramfs separately for every hook because > you'll get it right the first time the initramfs is written out! ok this indicates 2 bugs: - initramfs-tools no longer allowed to call update-initramfs - exit 1 if hook script doesn't get it right as linux-image will never depend on the hook itself, there is an high probability that the hook is in state unpacked. > So I don't see any real benefit to having all of these tools rebuilding the > initramfs repeatedly during an upgrade cycle. Theoretically it would be > nice to know as soon as a package is installed that it will break the > initramfs, but using update-initramfs doesn't do this: the only way to be > sure whether a new initramfs is broken is to try to boot from it. Since we > can't force reboots during an upgrade (especially not once for each hook!), > there is no significant increase in predictability by using this method, and > users are better off if the upgrade doesn't touch the existing, working > initramfs images at all. third bug: disallowing any hook to rebuild it's initramfs > Now, Marco has a persuasive argument that udev versi
Processed: tagging 362631
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.16 > tags 362631 moreinfo Bug#362631: linux-image-2.6.16-1: fails to mount root device There were no tags set. Tags added: moreinfo > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#362631: linux-image-2.6.16-1: fails to mount root device
Processing commands for [EMAIL PROTECTED]: > tags 362631 morinfo Unknown tag/s: morinfo. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore. Bug#362631: linux-image-2.6.16-1: fails to mount root device There were no tags set. Tags added: > severity 362631 important Bug#362631: linux-image-2.6.16-1: fails to mount root device Severity set to `important'. > reassign 362631 initramfs-tools Bug#362631: linux-image-2.6.16-1: fails to mount root device Bug reassigned from package `linux-2.6' to `initramfs-tools'. > 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#362642: ipv4 dhcp is not working in kernel 2.6.14-2
package: kernel version: 2.6.14-2 severity: important Hi, I have the same problem as bug 270451 here, although my networking card is different. I have dist-upgraded my box yestoday, and the dhcp-client just never got an address anymore. When I type "ifconfig", strangely, eth0 got a IPv6 address. I think that is the problem, but it seems I can't get back to IPv4 address. I have modified /etc/modules.conf to avoid load ipv6 module, and blacklist-ed it in /etc/hotplug/blacklist. Nevertheless, it was just never back to IPv4 anymore. My /etc/network/interfaces is as the following, auto eth0 iface eth0 inet dhcp Qian
Bug#362631: linux-image-2.6.16-1: fails to mount root device
tags 362631 morinfo severity 362631 important reassign 362631 initramfs-tools stop On Fri, Apr 14, 2006 at 06:19:04PM +0100, C. Dominik =?UTF-8?Q?B=C3=B3di ?= wrote: > *** Please type your report below this line *** > The kernel seems to boot up normally, but then fails to mount the root device > with a message > "failed to mount root on /dev/hda8 - no such device" that is the error message of initramfs-tools when no root device came up. i guess you got into the rescue shell: did you check if /dev/hda8 existed? did you check which modules got loaded? > according to dmesg logs I can see that hda gets initialised normally. I > could not find any errors related to the initalisation of the ide controller > or hard disk, either. > > Booting the kernel without the initial ramdisk fails with a kernel panic. sure modular ide needs the drivers to recognise your root. > The system used to work with version 2.6.16-5 or earlier. However, since the > last upgrade was done on April 3rd 2006, I cannot remember the exact version > of the linux-image package I upgraded from. Due to not having a backup > kernel installed, I had to re-install the box from scratch and lost all > apt/dpkg logfiles. hmm will make hard to check what error you had. > I tried booting the linux-image-2.6.16-1-686 instead but bot the same error. where you using grub? please post: cat /proc/cmdline what about your reinstall does it boot normaly? regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362631: linux-image-2.6.16-1: fails to mount root device
Package: linux-2.6 Version: 2.6.16-6 Severity: critical Justification: breaks the whole system *** Please type your report below this line *** The kernel seems to boot up normally, but then fails to mount the root device with a message "failed to mount root on /dev/hda8 - no such device" according to dmesg logs I can see that hda gets initialised normally. I could not find any errors related to the initalisation of the ide controller or hard disk, either. Booting the kernel without the initial ramdisk fails with a kernel panic. The system used to work with version 2.6.16-5 or earlier. However, since the last upgrade was done on April 3rd 2006, I cannot remember the exact version of the linux-image package I upgraded from. Due to not having a backup kernel installed, I had to re-install the box from scratch and lost all apt/dpkg logfiles. I tried booting the linux-image-2.6.16-1-686 instead but bot the same error. -- System Information: Debian Release: testing/unstable APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-1-k7 depends on: ii initramfs-tools [linux-initra 0.59b tools for generating an initramfs ii module-init-tools 3.2.2-2tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-1-k7 recommends: ii libc6-i6862.3.6-6GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-1-k7/preinst/initrd-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/bootloader-test-error-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/bootloader-error-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/lilo-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/abort-overwrite-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/bootloader-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/kimage-is-a-directory: linux-image-2.6.16-1-k7/postinst/old-initrd-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/depmod-error-2.6.16-1-k7: false linux-image-2.6.16-1-k7/prerm/would-invalidate-boot-loader-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/elilo-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-k7/preinst/already-running-this-2.6.16-1-k7: linux-image-2.6.16-1-k7/prerm/removing-running-kernel-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/depmod-error-initrd-2.6.16-1-k7: false linux-image-2.6.16-1-k7/postinst/old-dir-initrd-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/overwriting-modules-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/create-kimage-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/old-system-map-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/failed-to-move-modules-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/abort-install-2.6.16-1-k7: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > submitter 360588 ! Bug#360588: hibernate: prerm renders package uninstallable with a read-only /usr/local Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 315182 ! Bug#315182: does not provide x-terminal-emulator/install alternatives and menu entry Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 310415 ! Bug#310415: kernel-image-2.6.11-1-686: debsums warnings about mismatching checksum on 2.6.11-5 after upgrading from 2.6.11-3 Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 360761 ! Bug#360761: pdnsd: New upstream software version 1.2.4 available Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 278391 ! Bug#278391: installing doesn't setup toms/toix links (see: 'flip -h' and 'man flip') Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 315725 ! Bug#315725: aterm-ml doesn't have appropriate documentation or manual page Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 357297 ! Bug#357297: Include a hook script in /etc/X11/Xsession.d to start xscreensaver via Xsession Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 356088 ! Bug#356088: samba: package talloc as a separate library Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 292477 ! Bug#292477: mozilla-thunderbird: "view" pull down filter 'To Do' doesn't work with search setting "Entire Message" Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 331682 ! Bug#331682: meld: Support for 'Save As' in the File menu and Toolbar Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. > submitter 309353 ! Bug#309353: mutt: segmentation fault (core dumped) while Fetching message headers... Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 316164 ! Bug#316164: xfce4-terminal: doesn't update x-terminal-emulator and x-terminal-emulator.1.gz alternatives correctly Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 292475 ! Bug#292475: mozilla-thunderbird: Incorrect conffiles settings result in debsums checksum mismatch Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 276527 ! Bug#276527: The language 'Telugu' is mis-spelled in /usr/share/i18n/locales/te_IN Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 277937 ! Bug#277937: grub in Suggests:, has non-existant grubconf package. Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 316168 ! Bug#316168: xfce4-terminal(1) refers to the upstream Terminal program rather than xfce4-terminal Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 357678 ! Bug#357678: ifstatus: Fails with error "/usr/sbin/ifstatus: line 3: exec: ifplugstatus: not found" Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 298784 ! Bug#298784: /etc/locale.alias should be removed Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 311078 ! Bug#311078: wdg-html-validator: should not 'Depends:' on wdg-html-reference Changed Bug submitter from Y Giridhar Appaji Nag <[EMAIL PROTECTED]> to Y Giridhar Appaji Nag <[EMAIL PROTECTED]>. (By the way, that Bug is currently marked as done.) > submitter 288563 ! Bug number 288563 not found. > submitter 305179 ! Bug number 305179 not found. > submitter 310420 ! Bug number 310420 not found. > submitter 275993 ! Bug number 275993 not found. > submitter 275323 ! Bug numb
Re: note on "2.4 is deprecated"
dann frazier wrote: > If for no other reason, upstream release process changes will likely > make this much more difficult. As I'm sure you know, 2.6 is being > actively developed indefinitely, as opposed to the previous method of > branching off and stabalising a development tree. Since there is no > existing plan for a 2.8, 2.4 would need to be maintained indefinitely > to continue a major + major-1 support model. Sure, I think there's something to the point someone else made in this thread that each 2.6.x is essentially a new major version now. Although clearly not quite the same as before. -- see shy jo signature.asc Description: Digital signature
Bug#361368: fixed upstream
Hi, I'd been trying kernels out of git, a few days before 2.6.16 was released, and had seen these Oopses (and subsequent modprobe segfaults) there, too. However, the final 2.6.16 kernel did not show this behaviour; I can load the snd-powermac module on kernel.org 2.6.16 (and .1) with no issues. Don't know whether this is helpful, just tought I'd mention it... -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Preparing 2.6.16-7, Call for discussion on SECCOMP and HZ_250
On Fri, Apr 14, 2006 at 02:25:44PM +0200, Bastian Blank wrote: > On Wed, Apr 12, 2006 at 04:44:33PM +0200, Frederik Schueler wrote: > > I would like to schedule the upload of 2.6.16-7, containing 2.6.16.3 and > > 2.6.16.4, for tomorrow Apr. 13th. > > powerpc stopped building. Do you have a build log somewhere ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Preparing 2.6.16-7, Call for discussion on SECCOMP and HZ_250
On Wed, Apr 12, 2006 at 04:44:33PM +0200, Frederik Schueler wrote: > I would like to schedule the upload of 2.6.16-7, containing 2.6.16.3 and > 2.6.16.4, for tomorrow Apr. 13th. powerpc stopped building. Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, "Elaan of Troyius", stardate 4372.5 signature.asc Description: Digital signature
Re: Preparing 2.6.16-7, Call for discussion on SECCOMP and HZ_250
maximilian attems wrote: [snip] > > - HZ_250 instead of HZ_1000: If I remember correctly, we kept HZ_1000 > > because it was the prior default. IMHO, we should follow upstream and > > change the default to HZ_250 too. > > > > A short pro/cons is here: http://kerneltrap.org/node/5411 > > > > Considering we plan to use the smp-alternatives patches for both amd64 > > and i386, at least here HZ_250 makes sense. For the other arches and > > flavours, either HZ_100 for smp and HZ_1000 for up/desktop flavours > > could make sense, or just HZ_250 too for the sake of simplicity. > > > > There will for sure be users requesting to revert this change, similar > > to PREEMPT, so I would like to have a concensus in the team regarding > > this option. > > i would stick with HZ_250 everywhere. > the upstream change seems not contested since. Agreed. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: note on "2.4 is deprecated"
Manoj Srivastava wrote: > On 13 Apr 2006, Bastian Blank wrote: > > > On Thu, Apr 13, 2006 at 10:28:56AM -0500, Manoj Srivastava wrote: > >> That is stretching it. The third component of a version is > >> hardly a "major" revision. > > > > Why? > > Component in a version are major.minor.sub. Now, given that > Linux 1.0 was ages ago, one could conced that the versioning is > Epoch.Major.Minor Upstream declared 2.6 a constant for the time being, so the third component remains the only one to make a version distinction. > But claiming that 2.5.16 is majorly different from > 2.5.15 when it comews to support is a facile argument that most > people are not gonna buy. We already saw that for 2.6.12 -> .13. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362568: ALL/all
Package: initramfs-tools Version: 0.59b Severity: normal -k [version] Specify kernel version or ALL The actual string that is used to specific all kernels is "all", not "ALL" -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages initramfs-tools depends on: ii busybox 1:1.01-4 Tiny utilities for small and embed ii cpio 2.6-11 GNU cpio -- a program to manage ar ii klibc-utils 1.3.3-1small statically-linked utilities ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii udev 0.089-1/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature
Bug#348147: Bug#358452: [Pkg-cryptsetup-devel]...
Please note that this bug (348147) is not about the cryptsetup hook/script per se anymore, but rather about the possibility to alter global variables from subscripts. Therefore, I've cloned Arjan's mail into a separate bug report against cryptsetup (362564, which in turn in an enhancement of the hook and script in report 358452). The gist of this bug report is still: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348147;msg=48 Regards, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Preparing 2.6.16-7, Call for discussion on SECCOMP and HZ_250
On Wed, 12 Apr 2006, Frederik Schueler wrote: > Hello, > > I would like to schedule the upload of 2.6.16-7, containing 2.6.16.3 and > 2.6.16.4, for tomorrow Apr. 13th. > > Additionally, I would like to call for comments on the following options: > > - SECCOMP: already deactivated in trunk, should be deactivated in sid > too, for more info on the issue please see > http://marc.theaimsgroup.com/?l=linux-kernel&m=113679955125413&w=2 > It seems to not change the ABI, so it could still be changed for -7. done > - HZ_250 instead of HZ_1000: If I remember correctly, we kept HZ_1000 > because it was the prior default. IMHO, we should follow upstream and > change the default to HZ_250 too. > > A short pro/cons is here: http://kerneltrap.org/node/5411 > > Considering we plan to use the smp-alternatives patches for both amd64 > and i386, at least here HZ_250 makes sense. For the other arches and > flavours, either HZ_100 for smp and HZ_1000 for up/desktop flavours > could make sense, or just HZ_250 too for the sake of simplicity. > > There will for sure be users requesting to revert this change, similar > to PREEMPT, so I would like to have a concensus in the team regarding > this option. i would stick with HZ_250 everywhere. the upstream change seems not contested since. also you may get subtile driver breaks on those that don't get HZ right. much safer calculation is upstream value. i'm no fanboy of dyn_hz. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354598: Bug seems to be fixed in 2.6.16
After upgrading to kernel 2.6.16 I could boot my laptop without the power cable plugged in. It seems that this bug has been fixed. Anders E. Andersen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
