Processed: severity of 445688 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.7 severity 445688 important Bug#445688: initramfs-tools: creates broken initramfs image Severity set to `important' from `critical' 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#445314: linux-image-2.6.22-2-amd64: Kernel hang with ASUS P5KC mobo apparently fixed with Linux 2.6.23-rc9
FYI, making a JFS filesystem with the journal on an external device seems to fail. At first I thought it was because I made the journal too big, but I reduced the size to 32MB and still got the error. # mkfs.jfs -L mythtv -j /dev/vg00/mythtvjournal /dev/vg00/mythtv mkfs.jfs version 1.1.11, 05-Jun-2006 Warning! All data on device /dev/vg00/mythtv will be lost! Warning! All data on device /dev/vg00/mythtvjournal will be lost! Continue? (Y/N) Y *** glibc detected *** double free or corruption (!prev): 0x0050f260 *** Aborted Karl [EMAIL PROTECTED] Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein
Bug#445735: image creation fails with a non-modular kernel
On Sun, Oct 07, 2007 at 11:17:32PM -0400, Brad Jorsch wrote: I compiled a kernel using kernel-package, with CONFIG_MODULES not set since this machine is not going to need to load any modules. When trying to install the generated .deb, I get the following error: Executing update-initramfs with the -v option gives more information: # update-initramfs -c -v -k linux-image-2.6.22.9 update-initramfs: Generating /boot/initrd.img-linux-image-2.6.22.9 Cannot find /lib/modules/linux-image-2.6.22.9 update-initramfs: failed for /boot/initrd.img-linux-image-2.6.22.9 Unless I'm mistaken, an initramfs is still required if / is on an LVM2 logical volume. bah this is a duplicate bug report. boring and yes modular kernel are recommended! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445749: Kernel assertion failure when using bonding
Package: linux-image-2.6.18-5-686 Version: 2.6.18.dfsg.1-13etch3 ifenslave version: ifenslave-2.6 1.1.0-6 After setting up bonding for two ethernet devices, the kernel complains about an assertion failure (viewable with dmesg) in net/ipv4/devinet.c. Bonding seems to work, but it's hardly comforting. Configuration: In /etc/network/interfaces: auto bond0 iface bond0 inet static address 10.0.0.2 netmask 255.255.255.0 gateway 10.0.0.1 broadcast 10.0.0.255 up ifenslave bond0 eth0 eth1 down ifenslave -d bond0 eth0 eth1 (IP information has been modified. Actual address is a 10.* address with the same netmask, available in private email to a developer on request). /etc/modprobe.d/bonding: alias bond0 bonding options bond0 mode=balance-alb miimon=100 (this file also symlinked to /etc/modutils/bonding. have run update-modules) Computer is a Hewlett Packard DL380 G5, ethernet devices in lspci: 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) lspci -n: 03:00.0 0200: 14e4:164c (rev 12) 05:00.0 0200: 14e4:164c (rev 12) relevant dmesg output: ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_UP): eth1: link is not ready ADDRCONF(NETDEV_UP): bond0: link is not ready IPv6 over IPv4 tunneling driver bnx2: eth0 NIC Link is Up, 100 Mbps full duplex, receive transmit flow control ON ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready bonding: bond0: link status definitely up for interface eth0. bonding: bond0: making interface eth0 the new active one. RTNL: assertion failed at net/ipv4/devinet.c (985) [c0261c66] inetdev_event+0x3e/0x286 [c02807fa] _spin_lock_bh+0xb/0x18 [c02807f7] _spin_lock_bh+0x8/0x18 [c023eed0] rt_run_flush+0x68/0x8f [c01284c3] notifier_call_chain+0x19/0x32 [c0228361] dev_set_mac_address+0x46/0x4b [f8b8ed7b] alb_set_slave_mac_addr+0x5a/0x7f [bonding] [f8b8f15f] alb_swap_mac_addr+0x8a/0x138 [bonding] [f8b8a9f1] bond_change_active_slave+0x187/0x27f [bonding] [f8b8b411] bond_select_active_slave+0x8d/0xbb [bonding] [f8b8c6a1] bond_mii_monitor+0x363/0x3a8 [bonding] [f8b8c33e] bond_mii_monitor+0x0/0x3a8 [bonding] [c0125607] run_timer_softirq+0xfb/0x151 [c0121838] __do_softirq+0x5a/0xbb [c01218cf] do_softirq+0x36/0x3a [c0103747] apic_timer_interrupt+0x1f/0x24 [c0101b91] mwait_idle+0x25/0x38 [c0101b52] cpu_idle+0x9f/0xb9 [c03176fd] start_kernel+0x379/0x380 RTNL: assertion failed at net/ipv4/devinet.c (985) [c0261c66] inetdev_event+0x3e/0x286 [c02807fa] _spin_lock_bh+0xb/0x18 [c02807f7] _spin_lock_bh+0x8/0x18 [c023eed0] rt_run_flush+0x68/0x8f [c01284c3] notifier_call_chain+0x19/0x32 [c0228361] dev_set_mac_address+0x46/0x4b [f8b8ed7b] alb_set_slave_mac_addr+0x5a/0x7f [bonding] [f8b8f16e] alb_swap_mac_addr+0x99/0x138 [bonding] [f8b8a9f1] bond_change_active_slave+0x187/0x27f [bonding] [f8b8b411] bond_select_active_slave+0x8d/0xbb [bonding] [f8b8c6a1] bond_mii_monitor+0x363/0x3a8 [bonding] [f8b8c33e] bond_mii_monitor+0x0/0x3a8 [bonding] [c0125607] run_timer_softirq+0xfb/0x151 [c0121838] __do_softirq+0x5a/0xbb [c01218cf] do_softirq+0x36/0x3a [c0103747] apic_timer_interrupt+0x1f/0x24 [c0101b91] mwait_idle+0x25/0x38 [c0101b52] cpu_idle+0x9f/0xb9 [c03176fd] start_kernel+0x379/0x380 bonding: bond0: first active interface up! ACPI: Power Button (FF) [PWRF] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready eth0: no IPv6 routers present bond0: no IPv6 routers present Thanks, Øystein -- Outgoing mail is certified Virus Free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#445573: auto-ro raids have 'recover' for sync-action
Processing commands for [EMAIL PROTECTED]: reassign 445573 linux-image-2.6.18-5-686 Bug#445573: auto-ro raids have 'recover' for sync-action Bug reassigned from package `mdadm' to `linux-image-2.6.18-5-686'. tags 445573 patch confirmed Bug#445573: auto-ro raids have 'recover' for sync-action Tags were: upstream Tags added: patch, confirmed severity 445573 minor Bug#445573: auto-ro raids have 'recover' for sync-action Severity set to `minor' from `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391328: bug report: ethtool.h broken
Le jeudi 05 octobre 2006, à 17:41:22 -0700, Xin a écrit : Package: linux-kernel-headers Version: 2.6.18-1 ethtool.h makes use of types like __u32 but does not include linux/types.h. The consequence is that some software that includes linux/ethtool.h but not linux/types.h, such as xorp-1.3, does not compile. Hi, problem also occurs with wireless.h arno signature.asc Description: Digital signature
Bug#445849: linux-2.6: NULL pointer exception after mounting a filesystem with a SELinux context option.
Package: linux-2.6 Severity: normal When a filesystem is mounted with the option fscontext=selinux security context and there is a mistake in the security context, the kernel issues a NULL pointer exception. After this the machine is still usable, but the command sync hangs (though the machine is not hang). This is serious because the scripts that shutdown vserver virtual machines run sync, and thus hang. Note that this is part of the normal shutdown process. Thus, if the machine is remotly managed, as is the current case, one has to contact the personal of the hosting provider and ask them to reset by hand. And it is quite unfriendly having to logout and login again every time one runs sync. Futhermore, this mount option that may look rare is essential for mounting the /tmp directory a vserver virtual machine that uses Apache. If SELinux is enabled, the web server cannot access the /tmp directory unless it has the appropiate security label. Reproducing this problem is simple: mkdir foo mount -t tmpfs -o fscontext=system_u:object_r:tmp_t none ./foo dmesg | tail (the correct fscontext option is fscontext=system_u:object_r:tmp_t:s0). Please fix this problem in the next kernel upgrade. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-vserver-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
From a newbie
Hello, I'm Sisir K from IIT Kharagpur, India. I'm a 17 year old wannabe hacker...and am interested to contribute something to free software and Debian in particular...I'm a very old user of free software but am new to it's development side...can anyone here please guide me? I run Debian sid btw, maybe I could start off by helping test some stuffor maybe docs or whatever you think fit for a newbie Thanks, Sisir -- Sisir Koppaka 1st Year Undergraduate Student Dept. of Mechanical Engineering IIT Kharagpur India
Bug#445688: Bug cause identified
By combining the error messages I get and looking at the initramdisk runs, I have found the problem is that the scripts call modpobe -Qb, with a capital q instead of a small q. Modprobe doesn't recognise this, so doesn't load the modules. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445862: sata_nv driver won't work on linux-image-2.6.18-5-amd64
Package: linux-image-2.6.18-5-amd64 Version: 2.6.18.dfsg.1-13 The amd64 kernel in Etch will not boot on motherboards based on the nvidia chipset, like my asus M2N4SLI as the sata_nv driver doesn't work and therefore hard-drives are not recognised. The 32bit Etch worked fine. The Etch amd64 installer is not able to load the sata_nv driver even by choosing it manually after automatic detection fails. By the way, the installation cd only boots with the noapic option (on the same system the 32bit installer worked fine) I installed the amd64 kernel on my 32bit Etch system to install amd64 by debootstrap, but it hangs as well during boot time on drive recognition. Thank you very much for your atteniton, Roberto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#445688: Bug cause identified
Processing commands for [EMAIL PROTECTED]: severity 445688 normal Bug#445688: initramfs-tools: creates broken initramfs image Severity set to `normal' from `important' tags 445688 moreinfo Bug#445688: initramfs-tools: creates broken initramfs image There were no tags set. Tags added: moreinfo stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445688: Bug cause identified
severity 445688 normal tags 445688 moreinfo stop On Mon, Oct 08, 2007 at 06:19:08PM +0100, Beojan Stanislaus wrote: By combining the error messages I get and looking at the initramdisk runs, I have found the problem is that the scripts call modpobe -Qb, with a capital q instead of a small q. Modprobe doesn't recognise this, so doesn't load the modules. can you please tell which boot script does this? [EMAIL PROTECTED]:~/src/initramfs-tools$ egrep modprobe -r scripts/ | egrep Q | wc -l 0 yes modprobe -Q is an ultra silent ubuntu extension and has never been submitted upstream. anyway newer modprobe sets early in init MODPROBE_OPTIONS, so there shouldn't be the need to specify them anywhere else. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Preparing another 2.6.22 upload
On Sat, Oct 06, 2007 at 08:30:42PM +0200, Martin Michlmayr wrote: Now that 2.6.22 is finally in testing, we should start planning to upload 2.6.22-5. This update is definitely needed on mips since it fixes two important bugs: - #444104: Kernel crashes on boot on IP32 (SGI O2): this kernel flavour currently doesn't work at all. - qemu NE2000 doesn't work on mips fwiw, I'd also like to see another upload, due to various missing modules on ia64 that weren't detected until we prepared the lkdi builds. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445876: initramfs-tools: DEVICE /dev/sd* in mdadm.conf prevents finding of lvm volume groups
Package: initramfs-tools Version: 0.85h Severity: normal hi, having DEVICE /dev/sd* or DEVICE /dev/sd[ab] in mdadm.conf (as specified in the mdadm.conf manpage) prevents finding of root lvm volumegroup by initrd. setting DEVICE partitions and then running update-initramfs -u solves this problem. regards martin sofaru -- Package-specific info: -- /proc/cmdline root=/dev/mapper/vgMandy0-mandy_root ro md=d0,/dev/sda,/dev/sdb pci=nommconf -- /proc/filesystems cramfs ext3 -- lsmod Module Size Used by button 12192 0 ac 10376 0 battery15496 0 ipv6 286048 18 loop 20112 0 snd_hda_intel 23708 0 snd_hda_codec 184192 1 snd_hda_intel snd_pcm89096 2 snd_hda_intel,snd_hda_codec snd_timer 29192 1 snd_pcm snd65256 4 snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer soundcore 15392 1 snd serio_raw 12036 0 snd_page_alloc 14864 2 snd_hda_intel,snd_pcm psmouse44432 0 pcspkr 7808 0 evdev 15360 0 parport_pc 41640 0 parport44684 1 parport_pc intel_agp 30400 1 floppy 67112 0 dm_mirror 25216 0 dm_snapshot20664 0 dm_mod 62800 5 dm_mirror,dm_snapshot usbhid 45088 0 ide_generic 5760 0 [permanent] ehci_hcd 36104 0 e1000 123968 0 uhci_hcd 28696 0 generic10500 0 [permanent] ide_core 147584 2 ide_generic,generic thermal20240 0 processor 38248 1 thermal fan 9864 0 ext3 138512 1 jbd65392 1 ext3 mbcache14216 1 ext3 ata_piix 19976 0 sata_sil24 20740 0 ahci 24708 2 libata106784 3 ata_piix,sata_sil24,ahci sd_mod 25856 2 scsi_mod 153008 3 ahci,libata,sd_mod raid1 27008 1 md_mod 82844 3 raid1 -- kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 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.1.3-4 Tiny utilities for small and embed ii cpio 2.6-17 GNU cpio -- a program to manage ar ii klibc-utils 1.4.34-1 small statically-linked utilities ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo ii udev 0.105-4/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445862: Strange statement....
The amd64 kernel in Etch will not boot on motherboards based on the nvidia chipset Way too general. And way too incorrect. I have about 10 etch/amd64 machines with sata_nv, and they work fine. ~# uname -a Linux mailhost 2.6.18-5-vserver-amd64 #1 SMP Sun Aug 12 21:05:24 UTC 2007 x86_64 GNU/Linux sata_nv :00:07.0: version 2.0 ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20 GSI 19 sharing vector 0x32 and IRQ 19 ACPI: PCI Interrupt :00:07.0[A] - Link [APSI] - GSI 20 (level, low) - IRQ 50 PCI: Setting latency timer of device :00:07.0 to 64 ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xCC00 irq 50 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xCC08 irq 50 scsi0 : sata_nv ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : sata_nv ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32) ata2.00: ata2: dev 0 multi count 16 ata2.00: configured for UDMA/133 Vendor: ATA Model: ST3250623NS Rev: 5.01 Type: Direct-Access ANSI SCSI revision: 05 Vendor: ATA Model: ST3250623NS Rev: 5.01 Type: Direct-Access ANSI SCSI revision: 05 ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23 ACPI: PCI Interrupt :00:08.0[A] - Link [APSJ] - GSI 23 (level, low) - IRQ 217 PCI: Setting latency timer of device :00:08.0 to 64 ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xB800 irq 217 ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xB808 irq 217 scsi2 : sata_nv ata3: SATA link down (SStatus 0 SControl 300) scsi3 : sata_nv ata4: SATA link down (SStatus 0 SControl 300) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445688: Info received (Bug cause identified)
Sorry, that information doesn't help since it doesn't fix anything when I fix this in /usr/share/initramfs-tools/scripts. The initramfs from yaird works, but can't load the usb driver. Pleas Reply. myhosting.com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting.com/myhosting
Re: Preparing another 2.6.22 upload
On Sat, 06 Oct 2007, Martin Michlmayr wrote: Now that 2.6.22 is finally in testing, we should start planning to upload 2.6.22-5. This update is definitely needed on mips since it fixes two important bugs: - #444104: Kernel crashes on boot on IP32 (SGI O2): this kernel flavour currently doesn't work at all. - qemu NE2000 doesn't work on mips due to popular demand voici stable updates synced. i'll announce an 2.6.22 upload for wednesday, has newer abi -3 if 2.6.23 gets released at the same time, i'll consider it pretty soon for exp. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445688: Bug cause identified
[ please keep the bug report on cc, that is not private conversation, cool thanks ] On Mon, 08 Oct 2007, [EMAIL PROTECTED] wrote: It's /scripts/init-premount Both the PS3 script and the thermal script have this error. However, this has not helped, and the initrd still doesn't boot. i'm sorry but your initramfs-tools is not from debian, we _never_ shipped with an modprobe -Q argument in those boot scripts. check the following on any debian initramfs-tools release: egrep -r modprobe /usr/share/initramfs-tools/scripts/init-premount/ also to diagnose your error i would need the actual error output and btw yaird is not supported, for initramfs debugging see - http://wiki.debian.org/InitramfsDebug It tells me that it acpi_pm has been installed, then stalls. The initrd generated by yaird boots the ystem, but my usb devices, so I am counting on an improvement of this. You may wish to know that I switched to Debian from Feisty using dist-upgrade, and udev didn't get upgraded. i see that is the explanation, so you'd need to reinstall a bunch of stuff in that case. apt-get --reinstall install initramfs-tools. but i'm sorry cross distro changing is not supported, you are pretty much on your own in that case. i'd recommed using debian-installer to get a clean root on your swap or such for a start, see daily build images - http://www.at.debian.org/devel/debian-installer/ best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Preparing another 2.6.22 upload
On Sat, Oct 06, 2007 at 08:30:42PM +0200, Martin Michlmayr wrote: We need to add the last few stable update for 2.6.22. Any volunteers? No. We need license and SC fixes. Bastian -- We have found all life forms in the galaxy are capable of superior development. -- Kirk, The Gamesters of Triskelion, stardate 3211.7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445862: marked as done (sata_nv driver won't work on linux-image-2.6.18-5-amd64)
Your message dated Tue, 9 Oct 2007 01:51:32 +0200 with message-id [EMAIL PROTECTED] and subject line update on Bug#445862 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.18-5-amd64 Version: 2.6.18.dfsg.1-13 The amd64 kernel in Etch will not boot on motherboards based on the nvidia chipset, like my asus M2N4SLI as the sata_nv driver doesn't work and therefore hard-drives are not recognised. The 32bit Etch worked fine. The Etch amd64 installer is not able to load the sata_nv driver even by choosing it manually after automatic detection fails. By the way, the installation cd only boots with the noapic option (on the same system the 32bit installer worked fine) I installed the amd64 kernel on my 32bit Etch system to install amd64 by debootstrap, but it hangs as well during boot time on drive recognition. Thank you very much for your atteniton, Roberto ---End Message--- ---BeginMessage--- Hallo. I've installed on my 32bit Etch system the 2.6.22amd64 kernel from lenny and it booted correctly, so I think it proves that the problem I met with installing Etch amd64 lies with the Etch kernel version. Thank you very much for your attention. Roberto ---End Message---
Re: Preparing another 2.6.22 upload
Bastian Blank [EMAIL PROTECTED] writes: On Sat, Oct 06, 2007 at 08:30:42PM +0200, Martin Michlmayr wrote: We need to add the last few stable update for 2.6.22. Any volunteers? No. We need license and SC fixes. SC? It's not worse what we have now so I'd consider it for 2.6.23 instead of blocking it due this now. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#445735: image creation fails with a non-modular kernel
Processing commands for [EMAIL PROTECTED]:
merge 445735 433708
Bug#433708: initramfs-tools: Wants to have /lib/modules/${version}/ present
when creating initramfs even under kernel without modules support
Bug#445735: image creation fails with a non-modular kernel
Merged 433708 445735.
tags 445735 patch
Bug#445735: image creation fails with a non-modular kernel
There were no tags set.
Bug#433708: initramfs-tools: Wants to have /lib/modules/${version}/ present
when creating initramfs even under kernel without modules support
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445735: image creation fails with a non-modular kernel
merge 445735 433708
tags 445735 patch
thanks
On Mon, Oct 08, 2007 at 09:00:09AM +0200, maximilian attems wrote:
bah this is a duplicate bug report.
boring and yes modular kernel are recommended!
bah, that was a useless reply.
Other people recommend a non-modular kernel, especially if no modules
are needed. There is no reason not to support this configuration.
Here's another patch, a little less quick and dirty than the one in
433708. Works for me, but I can't promise it doesn't break someone's
hook script somewhere.
--- /usr/sbin/mkinitramfs 2007-10-09 00:21:04.0 +
+++ /usr/sbin/mkinitramfs 2007-10-09 00:21:12.0 +
@@ -155,7 +155,11 @@
if [ ! -e ${MODULESDIR} ]; then
echo Cannot find ${MODULESDIR}
- exit 1
+# exit 1
+else
+ if [ ! -e ${MODULESDIR}/modules.dep ]; then
+ depmod ${version}
+ fi
fi
DESTDIR=$(mktemp -t -d mkinitramfs_XX) || exit 1
Bug#348739: Leather Goods
Hello, Our company is producing some high class leather products, Jackets Wallets and all kind of stuff, i wanted to know if anyone is interested in really cheap leather prodcuts please. Nudge me back at [EMAIL PROTECTED] Regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404416: marked as done (686 stock image very slow on Intel 915[GP]M)
Your message dated Tue, 9 Oct 2007 00:09:44 -0400 with message-id [EMAIL PROTECTED] and subject line Close has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.18-3-686 Version: 2.6.18-8 Severity: grave Justification: renders package unusable Using debian linux kernel 2.6.16 works perfectly, but booting with version 2.6.18-3 makes everything work much slower. The slowness can be experienced in the boot sequence (it takes about 5 minutes to start the system), in particular i think there must be some problem before (or in?) the IDE interface probing, because this is the first process in the boot sequence to be very slow. Running gnome, something strange happens: something is running slow and something else works normally. For example, opening a terminal window takes some seconds, while continous mathematical processing takes exactly the same time as with kernel 2.6.16. BTW, i'm attaching the first lines of dmesg, in the two version (the working 2.6.16 and the slow 2.6.18) till the IDE interface probing, because i think the problem is before it. Thanks a lot. - 2.6.16 dmesg --- Aug 18 19:01:49 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 1f6e (usable) BIOS-e820: 1f6e - 1f6ea000 (ACPI data) BIOS-e820: 1f6ea000 - 1f70 (ACPI NVS) BIOS-e820: 1f70 - 2000 (reserved) BIOS-e820: e000 - f0006000 (reserved) BIOS-e820: f0008000 - f000c000 (reserved) BIOS-e820: fed2 - fed9 (reserved) BIOS-e820: ff00 - 0001 (reserved) 0MB HIGHMEM available. 502MB LOWMEM available. On node 0 totalpages: 128736 DMA zone: 4096 pages, LIFO batch:0 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 124640 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:0 DMI present. ACPI: RSDP (v000 PTLTD ) @ 0x000f7530 ACPI: RSDT (v001 Sony J0 0x20041219 PTL 0x) @ 0x1f6e5a12 ACPI: MADT (v001 Sony J0 0x20041219 PTL 0x005f) @ 0x1f6e9e78 ACPI: FADT (v002 Sony J0 0x20041219 PTL 0x005f) @ 0x1f6e9ee0 ACPI: BOOT (v001 Sony J0 0x20041219 PTL 0x0001) @ 0x1f6e9fd8 ACPI: MCFG (v001 Sony J0 0x20041219 PTL 0x005f) @ 0x1f6e9f9c ACPI: SSDT (v001 Sony J0 0x20041219 PTL 0x20030224) @ 0x1f6e62cf ACPI: SSDT (v001 Sony J0 0x20041219 PTL 0x20030224) @ 0x1f6e5e8a ACPI: SSDT (v001 Sony J0 0x20041219 PTL 0x20030224) @ 0x1f6e5c6f ACPI: SSDT (v001 Sony J0 0x20041219 PTL 0x20030224) @ 0x1f6e5a56 ACPI: DSDT (v001 Sony J0 0x20041219 PTL 0x20030224) @ 0x ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:13 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:c000) Built 1 zonelists Kernel command line: root=/dev/hda2 ro mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1596.429 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 503240k/514944k available (1408k kernel code, 11108k reserved, 528k data, 144k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 3200.75 BogoMIPS
