Bug#491309: linux-2.6: Kernel supports "only" 32 cpu's
On Tue, Jul 22, 2008 at 07:30:03AM +0200, Rik Theys wrote: > I would think that for most of the x86_64 machines, a 2MB increase in > memory usage is acceptable? Most of them are probably equiped with at > least 1Gb. | # free -m | total used free sharedbuffers cached | Mem: 128107 20 0 27 23 | -/+ buffers/cache: 56 71 | Swap: 255 0255 | # uname -m | x86_64 (Okay, it is a virtualised machine ...) Bastian -- "Get back to your stations!" "We're beaming down to the planet, sir." -- Kirk and Mr. Leslie, "This Side of Paradise", stardate 3417.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491309: linux-2.6: Kernel supports "only" 32 cpu's
Bastian Blank wrote: Setting it to 255 needs 2MiB of image size and unswappable memory. |textdata bss dec hex filename |1345623 3148364 417112 4911099 4aeffb x86_64-255/vmlinux |1339887 380556 273880 1994323 1e6e53 x86_64-32/vmlinux It adds 32 interrupt vectors (a 32 bytes or so) for each new cpu into the data section, maybe this can be changed to dynamic allocation some time as this does not look like a critical path. I would think that for most of the x86_64 machines, a 2MB increase in memory usage is acceptable? Most of them are probably equiped with at least 1Gb. I don't think this is exchange of different resources. I know there are already machines with nearly 200 cores out there and even Xen choked on them. Maybe setting it to 64 will be okay for now. OK, setting it to 64 will certainly help during the Lenny lifecycle. Thanks, Rik Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: #490751: linux-image-2.6.25-2-686: proprietary NVIDIA module will not install; #481485: nVidia driver fails to compile due to active Xen support
It would be great if the XEN options:
CONFIG_XEN=y
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_HVC_XEN=y
were turned off in the Debian stock kernel until there is adequate
support for installing the Debian NVIDIA packages (nvidia-kernel-source,
nvidia-kernel-common and nvidia-glx) under testing, given that this is
now the default testing kernel.
Note that instructions similar to the following (available at
http://blog.creonfx.com/linux/how-to-install-nvidia-driver-on-2625-2-debian-kernel-with-xen
and elsewhere):
1. cd /lib/modules/2.6.25-2-686 (or wherever are your modules)
2. grep CONFIG_XEN . -Rl | xargs -i sed -i -e 's/CONFIG_XEN/CONFIG_LUPO/g' {}
3. export IGNORE_XEN_PRESENCE=1
4. sh NVIDIA-Linux-x86-173.08-pkg1.run (or you can use patched 169.12 -
http://www.nvnews.net/vbulletin/showthread.php?t=110088 )
do not always work (they didn't for me, nor for several other people
who have reported this problem in various places).
Also note:
The following advice (from bug report 481485):
|- If you use the nvidia installer you are on your own. You also cause
|- package files to be overwritten and will likely have breakage on
|- upgrades in the future. Have fun.
|-
|- If you use the debian packages then we can help. We already fixed the
|- xen problem in the debian packages by patching the driver build system.
is completely unhelpful (and unappreciated) since, as noted above (and in the
Debian wiki:
http://wiki.debian.org/NvidiaGraphicsDrivers#head-816174f32ba98061bdd68615838ee453646721f1),
the Debian packages won't install in testing.
Thanks for your efforts on our behalf,
--
Steve Lane
System, Network and Security Administrator
Doudna Lab
Biomolecular Structure and Mechanism Group
UC Berkeley
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
About bug# 484779
Hi all, Bug# 484779 is affecting me, since I don NOT use desktop environment (neither KDE nor GNome). There are several tools I use for power management (laptop Compaq 8510w), between them a couple of tools I use: acpitool cpufreqd Both look for /proc/acpi/battery contents, on to report battery information (-B) and the other to decide how to regulate the processors frequency. The case of cpufreq is really fatal to me under kernel image 2.6.25-2-amd64 (# CONFIG_ACPI_PROCFS_POWER is not set), since as there's no battery info under /proc/acpi/battery, cpufreq no longer has criteria to decide, and thus stops deciding forcing slowest frequency (for me the rank of frequencies goes from 800MHz to 2.2GHz, so cpufreq forces this 2.2GHz on AC power @ 800MHz, how sad can that be?), see: Jul 21 11:07:34 jevv-ofic cpufreqd: acpi_battery_init: error, acpi_battery module not compiled or inserted (/proc/acpi/battery/: No such file or directory)? Jul 21 11:07:34 jevv-ofic cpufreqd: acpi_battery_init: exiting. The result of the mentioned bug is to merge it to a KDE one, which doesn't have anything to do with acpitool neither cpufreqd. I order to get my laptop working I had to recompile the kernel: % diff /boot/config-2.6.25 /boot/config-2.6.25-2-amd64 4c4 < # Mon Jul 21 12:49:21 2008 --- > # Mon Jul 14 10:38:33 2008 308c308 < CONFIG_ACPI_PROCFS_POWER=y --- > # CONFIG_ACPI_PROCFS_POWER is not set And now I can work @ 2.2GHz as I expected... Can the bug be reopened considering this is NOT kde related? BTW I do not use gnome either, so my set of tools include acpi, acpid, acpitool, cpufreqd, cpufrequtils, acpi-support-base, acpi-support, laptop-mode-tools. All this tools are still support under unstable, so I see no reason why the latest unstable linux-image wouldn't support them... If not, then the users get forced to recompile the kernel to get things working, :(. Can you please confirm? Thanks, -- Javier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407217: r8169: Thecus N2100, multicast packets problem
Martin Michlmayr <[EMAIL PROTECTED]> : [...] > Did you see the bug report below ? Yes. I have not had time to investigate it yet. -- Ueimor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490704:
2.6.26 hangs too, in the same way, and again after up to two days of uptime. The new iwlwifi driver can drive the wireless LED, and that still works while the system is hung. Going to try to enable HPET_RTC_IRQ and HPET_RTC_IRQ as suggested in 479709, and if that fails, hpet=disable on the kernel cmdline. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491522: linux-image-2.6.25-2-686: The machine gets complete halted and Freezed after some minutes.
Could this be related? Or might this be hardware related? [ 4637.885035] Bad page state in process 'apt-listchanges' [ 4637.885041] page:c10bd900 flags:0x40001308 mapping: mapcount:0 count:0 [ 4637.885066] Trying to fix it up, but a reboot is needed [ 4637.885069] Backtrace: [ 4637.885077] Pid: 14856, comm: apt-listchanges Not tainted 2.6.25-2-686 #1 [ 4637.885170] [] bad_page+0x52/0x7a [ 4637.885198] [] get_page_from_freelist+0x2a4/0x37b [ 4637.885257] [] __alloc_pages+0x5f/0x2cb [ 4637.885288] [] __pagevec_lru_add_active+0xa2/0xad [ 4637.885312] [] handle_mm_fault+0x16b/0x6bb [ 4637.885433] [] kunmap_atomic+0x67/0x87 [ 4637.885472] [] get_page_from_freelist+0x2fe/0x37b [ 4637.885527] [] __alloc_pages+0x5f/0x2cb [ 4637.885554] [] do_page_fault+0x268/0x584 [ 4637.885600] [] do_page_fault+0x0/0x584 [ 4637.885611] [] error_code+0x72/0x78 [ 4637.885663] [] file_read_actor+0x47/0xcc [ 4637.885709] [] generic_file_aio_read+0x2e7/0x50d [ 4637.885812] [] xfs_read+0x1bd/0x230 [xfs] [ 4637.885995] [] get_page_from_freelist+0x2fe/0x37b [ 4637.886042] [] xfs_file_aio_read+0x50/0x58 [xfs] [ 4637.886110] [] do_sync_read+0xbf/0xfe [ 4637.886181] [] autoremove_wake_function+0x0/0x2d [ 4637.886252] [] security_file_permission+0xc/0xd [ 4637.886276] [] do_sync_read+0x0/0xfe [ 4637.886286] [] vfs_read+0x81/0x11e [ 4637.886311] [] sys_read+0x3c/0x63 [ 4637.886339] [] sysenter_past_esp+0x6d/0xa5 [ 4637.886409] === -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#489190: ps/2 mouse not working in 2.6.24
The patch that fixes the problem for me was merged. It applies cleanly on the debian tree. Would it be possible for you to pick it up in the deb? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=87d9173ea0c820021cf49e4c675b3821cfb4f0eb -- Guillaume Morin <[EMAIL PROTECTED]> This message was sent using IMP, the Internet Messaging Program. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490704: hangs shortly after boot
I installed the latest update (2.6.25-7) and I got the same hang. Probably unrelated, this time it took about 20 minutes of uptime. It was about the time of my hourly cron-apt run, so it could have been the first time it used swap, I'll try to duplicate it later. I see another similar bug appeared, #491522. -- Petre. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490984: / is busy causes EXT3-fs: INFO: recovery required on readonly filesystem)
Maks, Thank you for telling me about the discussion of 2.6.26 at the kernelnewbies page. I read it. Since we don't KNOW what's causing the bug, it involves data corruption, it's still happening, and I'd like to try a few more diagnostic techniques, I'd like to keep this bug open. Feel free to share your thoughts on ways to diagnose why a mount command would sometimes fail in /etc/init.d/umountroot. So far, I've found... it started failing after installing 2.6.25, and it happens less often if either a "cat /proc/mounts" is done, or ALSA is reconfigured. Best regards, Kingsley On 07/17/08 07:39, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the linux-image-2.6-686 package: > > #490984: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery > required on readonly filesystem > > It has been closed by maximilian attems <[EMAIL PROTECTED]>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact maximilian attems > <[EMAIL PROTECTED]> by > replying to this email. > > > -- > 490984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490984 > Debian Bug Tracking System > Contact [EMAIL PROTECTED] with problems > Date: Thu, 17 Jul 2008 09:33:04 +0200 > From: maximilian attems <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Bug#490984: linux-image-2.6-686: / is busy causes EXT3-fs: > INFO: recovery required on readonly filesystem > > On Wed, 16 Jul 2008, Kingsley G. Morse Jr. wrote: > > > Hi Maks, > > > > Thank you for replying quickly. > > > > On 07/16/08 10:47, maximilian attems wrote: > > [...] > > > hmm how is the bug you reported related to the kernel? > > [...] > > > > To be fair, I'm not sure that the kernel is to > > blame. > > closing as bug is unreproducible and certainly not a kernel bug. > > > It could be data corruption (I'm recovering from a > > bad CPU chip), incompatible package versions, or > > even something else I suppose. > > > > However, I suspect the kernel because the > > changelog at kernel.org for the next version, > > 2.6.26, mentions the words "mount" and "remount" > > hundreds of times, which leads me to suspect bugs > > and active development. > > please read the kernelnewbies page about 2.6.26 > it will tell you a lot about ro bind mounts. > nothing to be worried about. > > best regards > > -- > maks > > From: "Kingsley G. Morse Jr." <[EMAIL PROTECTED]> > To: Debian Bug Tracking System <[EMAIL PROTECTED]> > Subject: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery > required on > readonly filesystem > X-Mailer: reportbug 3.31 > Date: Tue, 15 Jul 2008 12:14:05 -0700 > > Package: linux-image-2.6-686 > Version: 2.6.25+14 > Severity: normal > > > Thanks for maintaining debian's kernel packages. > > They're a remarkable technology in more ways than > one. > > Here's how I duplicate the bug. > > 1.) $ shutdown -r now > > 2.) ctl-alt-F7 > > 3.) look quickly for something like > > "mount: / is busy" > > 4.) After the system has rebooted, if the root > filesystem is EXT3, look for > > EXT3-fs: INFO: recovery required on readonly filesystem. > > in /var/log/messages. > > If the root filesystem is EXT2, I get a long, > slow fsck recovery. > > > It seems to me that this can be partially > explained by the shutdown command running a > script named > > /etc/init.d/umountroot > > which calls the "mount" command to remount the > root file system as read only. > > It fails, and complains that > > "/ is busy" > > Since the root file system wasn't cleanly > unmounted, it'll be recovered during the next > boot. > > I investigated other processes interfering with > the root file system, without result. > > However, it seems that inserting > > "cat /proc/mounts" > > just before the (re)mount command in > > /etc/init.d/umountroot > > usually allows mount to complete. > > As an aside, the words "mount" and "remount" occur > hundreds of times in the changelog for 2.6.26. > > Frankly, I'm a little worried about data > corrutpion. > > Thanks, > Kingsley > > -- System Information: > Debian Release: lenny/sid > APT prefers unstable > APT policy: (990, 'unstable'), (1, 'experimental') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.25-2-686 > Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) > > Versions of packages linux-image-2.6-686 depends on: > ii linux-image-2.6.25-2-686 2.6.25-6 Linux 2.6.25 image on > PPro/Celeron > > linux-image-2.6-686 recommends no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491522: linux-image-2.6.25-2-686: The machine gets complete halted and Freezed after some minutes.
Hi, is this bug related to #479709 ? Disabling HPET support (BIOS) or stopping chrony (or maybe other programs using rtc) solves the problem for me. Best regards Jörgen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Reopen 490984
Processing commands for [EMAIL PROTECTED]: > reopen 490984 Bug#490984: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery required on readonly filesystem Bug reopened, originator not changed. > 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#491692: initramfs-tools: udev not copied to ramdisk as hookscript is skipped
Oh sorry forgot to attach the update-initramfs.log in the previous message... here it is Phil Keeping /boot/initrd.img-2.6.25.10-customy.dpkg-bak update-initramfs: Generating /boot/initrd.img-2.6.25.10-customy /usr/share/initramfs-tools/hooks/kernelextras ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/keymap ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/legacylvm ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/libsplashy ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/splashy ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/thermal ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/udev ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/udevhelper ignored: not alphanumeric or '_' file /usr/share/initramfs-tools/hooks/uswsusp ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/kernelextras ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/keymap ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/legacylvm ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/libsplashy ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/splashy ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/thermal ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/udev ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/udevhelper ignored: not alphanumeric or '_' file /etc/initramfs-tools/hooks/uswsusp ignored: not alphanumeric or '_' file Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/usb/core/usbcore.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/usb/host/ehci-hcd.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/usb/host/ohci-hcd.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/usb/host/uhci-hcd.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/hid/usbhid/usbhid.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/usb/storage/libusual.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/scsi_mod.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/usb/storage/usb-storage.ko Adding module /lib/modules/2.6.25.10-customy/kernel/fs/ext2/ext2.ko Adding module /lib/modules/2.6.25.10-customy/kernel/fs/jfs/jfs.ko Adding module /lib/modules/2.6.25.10-customy/kernel/net/sunrpc/sunrpc.ko Adding module /lib/modules/2.6.25.10-customy/kernel/fs/lockd/lockd.ko Adding module /lib/modules/2.6.25.10-customy/kernel/fs/nfs/nfs.ko Adding module /lib/modules/2.6.25.10-customy/kernel/fs/reiserfs/reiserfs.ko Adding module /lib/modules/2.6.25.10-customy/kernel/net/packet/af_packet.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/net/mii.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/net/8139cp.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/net/8139too.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/net/eql.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/net/slhc.ko Copying module directory kernel/drivers/ide Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/pcmcia/pcmcia_core.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/pcmcia/pcmcia.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/ide/legacy/ide-cs.ko Copying module directory kernel/drivers/scsi Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/scsi_transport_iscsi.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/libiscsi.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/iscsi_tcp.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/BusLogic.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/advansys.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/ch.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/scsi_transport_fc.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/megaraid/megaraid_sas.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/sg.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/scsi_transport_spi.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/scsi_wait_scan.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/scsi/sd_mod.ko Copying module directory kernel/drivers/block Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/block/pktcdvd.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/block/brd.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/ieee1394/ieee1394.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/ieee1394/ohci1394.ko Adding module /lib/modules/2.6.25.10-customy/kernel/drivers/ieee1394/sbp2.ko Adding binary /usr/share/initramfs-tools/init Adding binary /etc/initramfs-tools/initramfs.conf Adding binary /usr/share/initramfs-tools/conf.d/uswsusp Adding binary
Bug#491692: initramfs-tools: udev not copied to ramdisk as hookscript is skipped
Hi,
> could you please tell the udev version running:
> dpkg -l udev
ii udev 0.114-2
> also stick an set -x on top of /usr/share/initramfs-tools/hooks/udev
> and set in the output you get then of mkinitramfs -o /tmp/foo
I'm not sure what you mean by "stick an set -x"... however if this is about
the file system rights of the hook scripts an
"ls -l /usr/share/initramfs-tools/hooks/" gives back:
-rwxr-xr-x 1 root root 498 2007-12-25 17:03 kernelextras
-rwxr-xr-x 1 root root 981 2008-06-04 17:21 keymap
-rwxr-xr-x 1 root root 444 2008-06-04 17:21 legacylvm
-rwxr-xr-x 1 root root 1316 2008-06-16 08:02 libsplashy
-rwxr-xr-x 1 root root 537 2008-06-16 08:02 splashy
-rwxr-xr-x 1 root root 844 2007-12-25 17:03 thermal
-rwxr-xr-x 1 root root 653 2007-08-06 06:12 udev
-rwxr-xr-x 1 root root 563 2008-07-07 13:50 udevhelper
-rwxr-xr-x 1 root root 600 2008-06-08 12:08 uswsusp
so they're all executable and always have been so the output of
mkinitramfs -o /tmp/foo shouldn't change.
Most interestingly in my opinion is the output of
update-initramfs -utv
which gives back a lot including lines like this:
/usr/share/initramfs-tools/hooks/keymap ignored: not alphanumeric or '_' file
/usr/share/initramfs-tools/hooks/udev ignored: not alphanumeric or '_' file
(The complete output of that is included in update-initramfs.log) which makes
clear that this is not an execution-rights issue.
Anyway these messages are issued by this code snippet
in /usr/share/initramfs-tools/script/functions:
set_initlist()
{
unset initlist
for si_x in ${initdir}/*; do
# skip empty dirs without warning
[ "${si_x}" = "${initdir}/*" ] && return
# only allow variable name chars
case ${si_x#${initdir}/} in
*[![:alnum:]_]*)
[ "${verbose}" = "y" ] \
&& echo "$si_x ignored: not alphanumeric or '_' file"
continue
;;
esac
This causes the udev hook script to be skipped...
Cheers
Phil
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491692: initramfs-tools: udev not copied to ramdisk as hookscript is skipped
On Mon, Jul 21, 2008 at 04:29:48PM +0200, Philipp Sternberg wrote: > Hi, > > > > please sendin the output of > > sh -x mkinitramfs -o /tmp/o > > > > "sh -x mkinitramfs -o /tmp/o" gave me a "sh: Can't open mkinitramfs" > so I executed > sh -x /usr/sbin/mkinitramfs -o /tmp/o 2> mkinitramfs.log and attached the > outputfile. > Or did you mean the content of the image (i.e. /tmp/o?) to be attached? > > Thanks a lot for your quick answer... okay thanks for the quick report. anyway this looks pretty normal. could you please tell the udev version running: dpkg -l udev also stick an set -x on top of /usr/share/initramfs-tools/hooks/udev and set in the output you get then of mkinitramfs -o /tmp/foo as the hook scripts are sourced an eventual failure there goes unnoticed. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 392015
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 392015 + pending Bug#392015: Request for openvz patched binary kernels. There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491692: initramfs-tools: udev not copied to ramdisk as hookscript is skipped
On Mon, Jul 21, 2008 at 02:03:23PM +0200, Philipp Sternberg wrote: > > Hi folks, > > i ran into this after trying to install a 2.6.25.10-vanilla using make-kpkg. > When I tried to boot the new kernel, > the system hung. It said /scripts/init-premount/udev : 17 : udevd : not > found. Well the reason for that was very > simple: udevd was not copied into the kernel image: > > Allright here is how one might reprduce it (at least that was how I ran into > it): > 1. unpack the kernel sources and configure the kernel. > --> After unpacking I did > cd /usr/src/linux-2.6.25.10 > zcat /proc/config.gz > .config > make oldeconfig > make menuconfig > 2. Create the kernelimage > make-kpkg clean && make-kpkg --initrd --append-to-version=-custom > --rootcmd fakeroot \ > kernel_image kernel_headers > 3. Install the Kernel > dpkg -i > /usr/src/linux-image-2.6.25.10-customy_2.6.25.10-customy-10.00.Custom_i386.deb > --> dpkg told me that the ramdisk was created > 4.If I reboot now the above described problem happens. > 5. To check if udevd was included in the image i unpacked the kernelimage > into a directory and tried to find the > udevd binary: > mkdir /home/philipp/Desktop/initrd > cd /home/philipp/Desktop/initrd > zcat /boot/initrd.img-2.6.25.10-customy | cpio -i > find -name '*udev*' > --> which gave me just > ./scripts/init-premount/udev > ./scripts/init-bottom/udev > > Unfortunately i was not able to see what really happend during the creation > of the image so i ran: > update-initramfs -utv > which revealed that all the hook scripts were skipped with the message > /usr/share/initramfs-tools/hooks/whatever ignored: not alphanumeric or > '_' file > > Thus the udev hook script was skipped as well and no udevd-binary was copied. > > I worked around this by temporarily changing line 77 of > /usr/share/initramfs-tools/scripts/functions > from > *[![:alnum:]_]* > to ___ > very very ugly, but however the line, which is in a section which figures out > which scripts to exclude from > participation in the ramdisk-image creation process, more or less tells to > exclude everything as far as i > interpreted the > glob expression (this *[![:alnum:]_]* string) correctly. Why is that so? > I'd guess it is a bug. Anyhow even if it isn't I would expect the freshly > installed initramfs-tools scripts to > create a consistent ramdisk image. > > Well that's it basically > > Regards > > Phil > root=/dev/hda1 ro please sendin the output of sh -x mkinitramfs -o /tmp/o thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491692: initramfs-tools: udev not copied to ramdisk as hookscript is skipped
Package: initramfs-tools Version: 0.92e Severity: important Hi folks, i ran into this after trying to install a 2.6.25.10-vanilla using make-kpkg. When I tried to boot the new kernel, the system hung. It said /scripts/init-premount/udev : 17 : udevd : not found. Well the reason for that was very simple: udevd was not copied into the kernel image: Allright here is how one might reprduce it (at least that was how I ran into it): 1. unpack the kernel sources and configure the kernel. --> After unpacking I did cd /usr/src/linux-2.6.25.10 zcat /proc/config.gz > .config make oldeconfig make menuconfig 2. Create the kernelimage make-kpkg clean && make-kpkg --initrd --append-to-version=-custom --rootcmd fakeroot \ kernel_image kernel_headers 3. Install the Kernel dpkg -i /usr/src/linux-image-2.6.25.10-customy_2.6.25.10-customy-10.00.Custom_i386.deb --> dpkg told me that the ramdisk was created 4.If I reboot now the above described problem happens. 5. To check if udevd was included in the image i unpacked the kernelimage into a directory and tried to find the udevd binary: mkdir /home/philipp/Desktop/initrd cd /home/philipp/Desktop/initrd zcat /boot/initrd.img-2.6.25.10-customy | cpio -i find -name '*udev*' --> which gave me just ./scripts/init-premount/udev ./scripts/init-bottom/udev Unfortunately i was not able to see what really happend during the creation of the image so i ran: update-initramfs -utv which revealed that all the hook scripts were skipped with the message /usr/share/initramfs-tools/hooks/whatever ignored: not alphanumeric or '_' file Thus the udev hook script was skipped as well and no udevd-binary was copied. I worked around this by temporarily changing line 77 of /usr/share/initramfs-tools/scripts/functions from *[![:alnum:]_]* to ___ very very ugly, but however the line, which is in a section which figures out which scripts to exclude from participation in the ramdisk-image creation process, more or less tells to exclude everything as far as i interpreted the glob expression (this *[![:alnum:]_]* string) correctly. Why is that so? I'd guess it is a bug. Anyhow even if it isn't I would expect the freshly installed initramfs-tools scripts to create a consistent ramdisk image. Well that's it basically Regards Phil -- Package-specific info: -- /proc/cmdline root=/dev/hda1 ro -- /proc/filesystems ext3 iso9660 udf -- lsmod Module Size Used by ipv6 188264 8 cpufreq_powersave 1344 0 cpufreq_performance 1536 0 lp 7724 0 af_packet 13568 4 sbp2 16780 0 scsi_mod 77220 1 sbp2 arc41600 2 ecb 2432 2 crypto_blkcipher 13124 1 ecb ath5k 81156 0 mac80211 104524 1 ath5k cfg80211 13832 1 mac80211 joydev 7808 0 pcmcia 21160 0 snd_intel8x0 25180 4 snd_ac97_codec 84512 1 snd_intel8x0 nsc_ircc 16464 0 ac97_bus1408 1 snd_ac97_codec snd_pcm54024 3 snd_intel8x0,snd_ac97_codec snd_timer 15556 2 snd_pcm snd37620 10 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 4804 1 snd asus_laptop13624 0 irda 144972 1 nsc_ircc snd_page_alloc 6856 2 snd_intel8x0,snd_pcm intelfb29348 0 video 16016 0 backlight 3524 2 asus_laptop,video yenta_socket 20108 3 rsrc_nonstatic 9024 1 yenta_socket pcmcia_core27600 3 pcmcia,yenta_socket,rsrc_nonstatic i2c_algo_bit4804 1 intelfb psmouse31504 0 battery 9860 0 led_class 2820 1 asus_laptop ac 3908 0 evdev 7360 6 button 5776 0 parport_pc 30456 1 parport26696 2 lp,parport_pc intel_agp 20988 1 i2c_core 16272 2 intelfb,i2c_algo_bit 8139too17856 0 ohci1394 23856 0 8139cp 15296 0 mii 4032 2 8139too,8139cp ieee1394 65728 2 sbp2,ohci1394 ehci_hcd 25548 0 uhci_hcd 17484 0 usbcore 100860 3 ehci_hcd,uhci_hcd thermal14684 0 processor 26740 2 thermal fan 2944 0 -- /etc/kernel-img.conf do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = /sbin/update-grub postrm_hook = /sbin/update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSY
Re: Userland compatibility fixes for 2.6.26
On Sat, 19 Jul 2008, Bastian Blank wrote: > On Fri, Jul 18, 2008 at 02:20:12PM +0200, Bastian Blank wrote: > > Following the discussion some weeks ago I have a patch to fix most of > > the problematic userspace header changes in 2.6.26. > > I withdraw the patch. The release team knows why. i don't see any technical reasons to withdraw. can you please explain your reasons to d-kernel. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#407217: comment
< Womble2> tbm: re 8169, perhaps you need to add yet another multicast-filter-challenged MAC variant in rtl_set_rx_mode() -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491522: Additional information
Some more information about my machine in the attachments... Thanks in advance. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut <[EMAIL PROTECTED]> Jabber: [EMAIL PROTECTED] / GPG: 0x9EA93CB2 # dmidecode 2.9 SMBIOS 2.4 present. 22 structures occupying 1128 bytes. Table at 0x000FBC40. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: P1.30 Release Date: 09/04/2006 Address: 0xF Runtime Size: 64 kB ROM Size: 512 kB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 KB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 8.12 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: To Be Filled By O.E.M. Product Name: 775i945GZ Version: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. UUID: 00020003-0004-0005-0006-000700080009 Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Product Name: 775i945GZ Version: Serial Number: Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 21 bytes Chassis Information Manufacturer: To Be Filled By O.E.M. Type: Desktop Lock: Not Present Version: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: CPUSocket Type: Central Processor Family: Pentium 4 Manufacturer: Intel ID: 65 0F 00 00 FF FB EB BF Signature: Type 0, Family 15, Model 6, Stepping 5 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Hyper-threading technology) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Pentium(R) D CPU 3.20GHz Voltage: 1.3 V External Clock: 200 MHz Max Speed: 3200 MHz Current Speed: 3200 MHz Status: Populated, Enabled Upgrade: Othe
Bug#491522: The same here
Hi, I've got the same problem since the update to 2.6.25-2-686 kernel. My lenny system worked fine with the older 2.6.24 kernel. Since the new kernel upstream version my machine freezed sporadically after some uptime 3 times now. There are no kernel messages before this happens. Unfortunately I purged the older kernel after the update. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut <[EMAIL PROTECTED]> Jabber: [EMAIL PROTECTED] / GPG: 0x9EA93CB2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491677: linux-image-2.6.25-2-powerpc: suspend broken with 2.6.25 on an iBook G4
Package: linux-image-2.6.25-2-powerpc Version: 2.6.25-6 Severity: normal Since the upgrade to 2.6.25 suspend is broken on my iBook G4. Suspend on 2.6.24 works well. When coming back from sleep it shows something along the lines of "Freezing user space processes" and the last line shown is "Suspending console(s)" with a timestamp. As this should be the last output before sleep I think that the kernel somehow misses the wake-up and locks itself to the state before it supposedly called the PMU to initiate the sleep. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.24-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-powerpc depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.25-2-powerpc recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-powerpc/preinst/lilo-initrd-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/postinst/bootloader-test-error-2.6.25-2-powerpc: linux-image-2.6.25-2-powerpc/preinst/abort-install-2.6.25-2-powerpc: linux-image-2.6.25-2-powerpc/preinst/elilo-initrd-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-powerpc/preinst/initrd-2.6.25-2-powerpc: linux-image-2.6.25-2-powerpc/postinst/old-system-map-link-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/preinst/overwriting-modules-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/postinst/depmod-error-initrd-2.6.25-2-powerpc: false linux-image-2.6.25-2-powerpc/preinst/bootloader-initrd-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/postinst/kimage-is-a-directory: linux-image-2.6.25-2-powerpc/postinst/depmod-error-2.6.25-2-powerpc: false linux-image-2.6.25-2-powerpc/postinst/bootloader-error-2.6.25-2-powerpc: linux-image-2.6.25-2-powerpc/preinst/abort-overwrite-2.6.25-2-powerpc: linux-image-2.6.25-2-powerpc/postinst/old-dir-initrd-link-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/prerm/would-invalidate-boot-loader-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/postinst/create-kimage-link-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/preinst/failed-to-move-modules-2.6.25-2-powerpc: linux-image-2.6.25-2-powerpc/prerm/removing-running-kernel-2.6.25-2-powerpc: true linux-image-2.6.25-2-powerpc/postinst/old-initrd-link-2.6.25-2-powerpc: true signature.asc Description: Digital signature
Processed: tagging 487721
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 487721 + pending Bug#487721: linux-2.6: ipw2200 wrongly claims it can scan for hidden ESSIDs Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491443: marked as done (/var/lib/initramfs-tools/ not updated)
Your message dated Mon, 21 Jul 2008 10:06:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#491443: /var/lib/initramfs-tools/ not updated has caused the Debian Bug report #491443, regarding /var/lib/initramfs-tools/ not updated 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.) -- 491443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491443 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: initramfs-tools Version: 0.92e Severity: minor Today i've changed "update_initramfs" variable from "yes" to "all". The update-initramfs scripts seems to look at the contents of the directory "/var/lib/initramfs-tools/" to know for what image to update (it contain MD5 files, one for every initramfs created in this system). The problem is that nobody seems to care of cleaning that directory after a kernel removal, so it is full of obsolete files, that makes update-initramfs a bit noisy. On my system: # update-initramfs -u update-initramfs: Generating /boot/initrd.img-2.6.25-2-686 update-initramfs: Generating /boot/initrd.img-2.6.24-1-686 /boot/initrd.img-2.6.23-1-686 does not exist. Cannot update. /boot/initrd.img-2.6.22-3-686 does not exist. Cannot update. /boot/initrd.img-2.6.22-2-686 does not exist. Cannot update. /boot/initrd.img-2.6.22-1-686 does not exist. Cannot update. /boot/initrd.img-2.6.21-2-686 does not exist. Cannot update. /boot/initrd.img-2.6.21-1-686 does not exist. Cannot update. /boot/initrd.img-2.6.20-1-686 does not exist. Cannot update. /boot/initrd.img-2.6.18-4-686 does not exist. Cannot update. /boot/initrd.img-2.6.18-3-686 does not exist. Cannot update. /boot/initrd.img-2.6.18-2-686 does not exist. Cannot update. /boot/initrd.img-2.6.18-1-686 does not exist. Cannot update. /boot/initrd.img-2.6.18-1-486 does not exist. Cannot update. /boot/initrd.img-2.6.17-2-686 does not exist. Cannot update. /boot/initrd.img-2.6.16-2-686 does not exist. Cannot update. # In fact i've only the first two kernel installed. Maybe when a kernel get purged, the removal scripts should clean its files under /var. Regards. Cesare. --- End Message --- --- Begin Message --- On Sat, 19 Jul 2008, Cesare Leonardi wrote: > Today i've changed "update_initramfs" variable from "yes" to "all". > The update-initramfs scripts seems to look at the contents of the > directory "/var/lib/initramfs-tools/" to know for what image to update > (it contain MD5 files, one for every initramfs created in this system). > The problem is that nobody seems to care of cleaning that directory > after a kernel removal, so it is full of obsolete files, that makes > update-initramfs a bit noisy. On my system: > > # update-initramfs -u > update-initramfs: Generating /boot/initrd.img-2.6.25-2-686 > update-initramfs: Generating /boot/initrd.img-2.6.24-1-686 > /boot/initrd.img-2.6.23-1-686 does not exist. Cannot update. > /boot/initrd.img-2.6.22-3-686 does not exist. Cannot update. > /boot/initrd.img-2.6.22-2-686 does not exist. Cannot update. > /boot/initrd.img-2.6.22-1-686 does not exist. Cannot update. > /boot/initrd.img-2.6.21-2-686 does not exist. Cannot update. > /boot/initrd.img-2.6.21-1-686 does not exist. Cannot update. > /boot/initrd.img-2.6.20-1-686 does not exist. Cannot update. > /boot/initrd.img-2.6.18-4-686 does not exist. Cannot update. > /boot/initrd.img-2.6.18-3-686 does not exist. Cannot update. > /boot/initrd.img-2.6.18-2-686 does not exist. Cannot update. > /boot/initrd.img-2.6.18-1-686 does not exist. Cannot update. > /boot/initrd.img-2.6.18-1-486 does not exist. Cannot update. > /boot/initrd.img-2.6.17-2-686 does not exist. Cannot update. > /boot/initrd.img-2.6.16-2-686 does not exist. Cannot update. > # > > In fact i've only the first two kernel installed. > Maybe when a kernel get purged, the removal scripts should clean its > files under /var. right this is fixed in newer linux images on removal the sha1sum disappears. for cleanup on those old non existant linux images look into /var/lib/initramfs-tools as those kernels are not longer around it is harmless to remove. closing as only fixed in newer linux-images. -- maks --- End Message ---
Bug#487721: linux-2.6: ipw2200 wrongly claims it can scan for hidden ESSIDs
On Mon, 21 Jul 2008, Ben Hutchings wrote: > I rather suspect that that would not be acceptable upstream! > > However, when I reviewed the thread referred to above I realised I had > not tried the patch that Dan Williams suggested. Something similar was > committed as ea177305b321a4127e448b88de20d5792682ace1, between > 2.6.26-rc4 and -rc5. I applied this to the kernel source package in > unstable, rebuilt and reloaded ipw2200 and it fixed the bug for me. So > I think you can close this in 2.6.26-1. > > Ben. ok cool, added to changelog. thanks for the info. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490293: marked as done (linux-image-2.6.24-etchnhalf.1-686: CONFIG_SMB_FS is not set)
Your message dated Mon, 21 Jul 2008 07:53:19 + with message-id <[EMAIL PROTECTED]> and subject line Bug#490293: fixed in linux-2.6.24 2.6.24-6~etchnhalf.4 has caused the Debian Bug report #490293, regarding linux-image-2.6.24-etchnhalf.1-686: CONFIG_SMB_FS is not set 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.) -- 490293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490293 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.3 Severity: wishlist CONFIG_SMB_FS is not set in the kernel config. it would be nice to have smbfs -- Package-specific info: -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable'), (103, 'proposed-updates') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.21-1-k7 Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Versions of packages linux-image-2.6.24-etchnhalf.1-686 depends on: ii debconf [debconf-2.0]1.5.11etch1 Debian configuration management sy ii initramfs-tools [linux-initr 0.85h tools for generating an initramfs ii module-init-tools3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.24-etchnhalf.1-686 recommends: ii libc6-i686 2.3.6.ds1-13etch5 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.24-etchnhalf.1-686/postinst/depmod-error-2.6.24-etchnhalf.1-686: false linux-image-2.6.24-etchnhalf.1-686/postinst/old-dir-initrd-link-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/initrd-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/kimage-is-a-directory: linux-image-2.6.24-etchnhalf.1-686/preinst/abort-install-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/prerm/removing-running-kernel-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/lilo-has-ramdisk: linux-image-2.6.24-etchnhalf.1-686/postinst/bootloader-error-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/old-initrd-link-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/bootloader-initrd-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/elilo-initrd-2.6.24-etchnhalf.1-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-etchnhalf.1-686/preinst/abort-overwrite-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/prerm/would-invalidate-boot-loader-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/overwriting-modules-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/postinst/old-system-map-link-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/postinst/depmod-error-initrd-2.6.24-etchnhalf.1-686: false linux-image-2.6.24-etchnhalf.1-686/preinst/lilo-initrd-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/failed-to-move-modules-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/bootloader-test-error-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/create-kimage-link-2.6.24-etchnhalf.1-686: true --- End Message --- --- Begin Message --- Source: linux-2.6.24 Source-Version: 2.6.24-6~etchnhalf.4 We believe that the bug you reported is fixed in the latest version of linux-2.6.24, which is due to be installed in the Debian FTP archive: linux-2.6.24_2.6.24-6~etchnhalf.4.diff.gz to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.4.diff.gz linux-2.6.24_2.6.24-6~etchnhalf.4.dsc to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.4.dsc linux-doc-2.6.24_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-doc-2.6.24_2.6.24-6~etchnhalf.4_all.deb linux-headers-2.6.24-etchnhalf.1-all-alpha_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all-alpha_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb linux-
linux-2.6.24_2.6.24-6~etchnhalf.4_alpha.changes ACCEPTED
Accepted: linux-2.6.24_2.6.24-6~etchnhalf.4.diff.gz to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.4.diff.gz linux-2.6.24_2.6.24-6~etchnhalf.4.dsc to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.4.dsc linux-doc-2.6.24_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-doc-2.6.24_2.6.24-6~etchnhalf.4_all.deb linux-headers-2.6.24-etchnhalf.1-all-alpha_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all-alpha_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-alpha-smp_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-alpha-smp_2.6.24-6~etchnhalf.4_alpha.deb linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.4_alpha.deb linux-image-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb linux-image-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb linux-image-2.6.24-etchnhalf.1-alpha-smp_2.6.24-6~etchnhalf.4_alpha.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-alpha-smp_2.6.24-6~etchnhalf.4_alpha.deb linux-manual-2.6.24_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-manual-2.6.24_2.6.24-6~etchnhalf.4_all.deb linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.4_all.deb linux-source-2.6.24_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-source-2.6.24_2.6.24-6~etchnhalf.4_all.deb linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.4_all.deb linux-tree-2.6.24_2.6.24-6~etchnhalf.4_all.deb to pool/main/l/linux-2.6.24/linux-tree-2.6.24_2.6.24-6~etchnhalf.4_all.deb Override entries for your package: linux-2.6.24_2.6.24-6~etchnhalf.4.dsc - optional devel linux-doc-2.6.24_2.6.24-6~etchnhalf.4_all.deb - optional doc linux-headers-2.6.24-etchnhalf.1-all-alpha_2.6.24-6~etchnhalf.4_alpha.deb - optional devel linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.4_alpha.deb - optional devel linux-headers-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb - optional devel linux-headers-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb - optional devel linux-headers-2.6.24-etchnhalf.1-alpha-smp_2.6.24-6~etchnhalf.4_alpha.deb - optional devel linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.4_alpha.deb - optional devel linux-image-2.6.24-etchnhalf.1-alpha-generic_2.6.24-6~etchnhalf.4_alpha.deb - optional admin linux-image-2.6.24-etchnhalf.1-alpha-legacy_2.6.24-6~etchnhalf.4_alpha.deb - optional admin linux-image-2.6.24-etchnhalf.1-alpha-smp_2.6.24-6~etchnhalf.4_alpha.deb - optional admin linux-manual-2.6.24_2.6.24-6~etchnhalf.4_all.deb - optional doc linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.4_all.deb - optional devel linux-source-2.6.24_2.6.24-6~etchnhalf.4_all.deb - optional devel linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.4_all.deb - optional devel linux-tree-2.6.24_2.6.24-6~etchnhalf.4_all.deb - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 490293 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #425250 # * http://bugzilla.kernel.org/show_bug.cgi?id=11084 # * remote status changed: (?) -> NEW usertags 425250 + status-NEW # remote status report for #426414 # * http://bugzilla.kernel.org/show_bug.cgi?id=11027 # * remote status changed: (?) -> NEW usertags 426414 + status-NEW # remote status report for #475319 # * http://bugzilla.kernel.org/show_bug.cgi?id=10448 # * remote status changed: (?) -> NEEDINFO usertags 475319 + status-NEEDINFO # remote status report for #487490 # * http://bugzilla.kernel.org/show_bug.cgi?id=10977 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE # * closed upstream tags 487490 + fixed-upstream usertags 487490 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE # remote status report for #487725 # * http://bugzilla.kernel.org/show_bug.cgi?id=10997 # * remote status changed: (?) -> NEW usertags 487725 + status-NEW # remote status report for #488566 # * http://bugzilla.kernel.org/show_bug.cgi?id=10743 # * remote status changed: (?) -> ASSIGNED usertags 488566 + status-ASSIGNED # remote status report for #488794 # * http://bugzilla.kernel.org/show_bug.cgi?id=11050 # * remote status changed: (?) -> NEW usertags 488794 + status-NEW # remote status report for #488799 # * http://bugzilla.kernel.org/show_bug.cgi?id=11022 # * remote status changed: (?) -> REJECTED # * remote resolution changed: (?) -> DOCUMENTED # * closed upstream tags 488799 + fixed-upstream usertags 488799 + status-REJECTED resolution-DOCUMENTED # remote status report for #489139 # * http://bugzilla.kernel.org/show_bug.cgi?id=11031 # * remote status changed: (?) -> ASSIGNED usertags 489139 + status-ASSIGNED thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package linux-2.6
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package linux-2.6 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #425250 > # * http://bugzilla.kernel.org/show_bug.cgi?id=11084 > # * remote status changed: (?) -> NEW > usertags 425250 + status-NEW Bug#425250: linux-source-2.6.18 : "make pdfdocs" in the linux-source-2.6.18 fails. There were no usertags set. Usertags are now: status-NEW. > # remote status report for #426414 > # * http://bugzilla.kernel.org/show_bug.cgi?id=11027 > # * remote status changed: (?) -> NEW > usertags 426414 + status-NEW Bug#426414: kernel: time jumps and usb resets There were no usertags set. Usertags are now: status-NEW. > # remote status report for #475319 > # * http://bugzilla.kernel.org/show_bug.cgi?id=10448 > # * remote status changed: (?) -> NEEDINFO > usertags 475319 + status-NEEDINFO Bug#475319: linux-2.6: loading video kernel module causes Samsung Q45 to freeze There were no usertags set. Usertags are now: status-NEEDINFO. > # remote status report for #487490 > # * http://bugzilla.kernel.org/show_bug.cgi?id=10977 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE > # * closed upstream > tags 487490 + fixed-upstream Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work There were no tags set. Tags added: fixed-upstream > usertags 487490 + status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE Bug#487490: linux-image-2.6.25-2-686: USB_PERSIST is enabled, but does not work There were no usertags set. Usertags are now: status-RESOLVED resolution-PATCH-ALREADY-AVAILABLE. > # remote status report for #487725 > # * http://bugzilla.kernel.org/show_bug.cgi?id=10997 > # * remote status changed: (?) -> NEW > usertags 487725 + status-NEW Bug#487725: linux-image-2.6.25-2-amd64: Got much trouble and message 'ehci_hcd: HC died' when scanning image from 'Canon PIXMA MP150'. There were no usertags set. Usertags are now: status-NEW. > # remote status report for #488566 > # * http://bugzilla.kernel.org/show_bug.cgi?id=10743 > # * remote status changed: (?) -> ASSIGNED > usertags 488566 + status-ASSIGNED Bug#488566: linux-image-2.6.25-2-686: Corrupt writes with SATA DVD writer on VIA hardware There were no usertags set. Usertags are now: status-ASSIGNED. > # remote status report for #488794 > # * http://bugzilla.kernel.org/show_bug.cgi?id=11050 > # * remote status changed: (?) -> NEW > usertags 488794 + status-NEW Bug#488794: linux-image-2.6.25-2-686: cannot suspend to disk while a mounted cifs share is inaccessible There were no usertags set. Usertags are now: status-NEW. > # remote status report for #488799 > # * http://bugzilla.kernel.org/show_bug.cgi?id=11022 > # * remote status changed: (?) -> REJECTED > # * remote resolution changed: (?) -> DOCUMENTED > # * closed upstream > tags 488799 + fixed-upstream Bug#488799: linux-image-2.6.25-2-686: power button produces multiple events There were no tags set. Tags added: fixed-upstream > usertags 488799 + status-REJECTED resolution-DOCUMENTED Bug#488799: linux-image-2.6.25-2-686: power button produces multiple events There were no usertags set. Usertags are now: resolution-DOCUMENTED status-REJECTED. > # remote status report for #489139 > # * http://bugzilla.kernel.org/show_bug.cgi?id=11031 > # * remote status changed: (?) -> ASSIGNED > usertags 489139 + status-ASSIGNED Bug#489139: Removing AVM ISDN PCMCIA card from the slot freezes the system There were no usertags set. Usertags are now: status-ASSIGNED. > 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]
[bts-link] source package linux-latest-2.6
# # bts-link upstream status pull for source package linux-latest-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #490816 # * http://bugzilla.kernel.org/show_bug.cgi?id=11092 # * remote status changed: (?) -> NEW usertags 490816 + status-NEW thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
