Bug#586381: initramfs-tools: lsinitramfs fails with non-gzipped initramfs images
* Christoph Anton Mitterer [Sat Jun 19, 2010 at 02:26:05AM +0200]: > lsinitramgs fails with non-gzipped (well at least with lzma-ed) > initramfs images: > gzip: /boot/initrd.img-2.6.33: not in gzip format > cpio: premature end of archive Thanks for reporting. We're not yet sure what might be the best approach to distinguish between different compression versions but could you please provide output of: dd if=/boot/initrd.img-2.6.33 bs=1 count=8 | od to us so we can evaluate a possible solution? regards, -mika- signature.asc Description: Digital signature
Processed: tagging 586554
Processing commands for cont...@bugs.debian.org: > tags 586554 = pending Bug #586554 [initramfs-tools] initramfs-tools fails to upgrade from 0.96.1 to 0.97 Added tag(s) pending; removed tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 586554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127716327122210.transcr...@bugs.debian.org
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
tags 586554 - moreinfo tags 586554 + pending thanks * thebickhams [Tue Jun 22, 2010 at 12:03:29AM +0100]: [...] > find /usr/share/initramfs-tools -print0 | xargs -0 dpkg -S > iscan, initramfs-tools, udev, dmsetup: /usr/share/initramfs-tools > iscan: /usr/share/initramfs-tools/hooks/iscan [...] That's the problematic package (thanks to devil + Carpenter from #debian.de for helping in debugging this issue). "sudo apt-get --purge remove iscan" will get rid of it and the problem will disappear. The iscan package isn't shipped nor distributed via Debian, so this isn't a valid bug report for us anymore. But I'll keep this bugreport open until we have verified that the failing hooks like the one from iscan are listed during (failed) upgrades. In the meanwhile Sidux users can be pointed to this bugreport. regards, -mika- signature.asc Description: Digital signature
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
find /usr/share/initramfs-tools /usr/share/initramfs-tools /usr/share/initramfs-tools/modules /usr/share/initramfs-tools/conf-hooks.d /usr/share/initramfs-tools/hooks /usr/share/initramfs-tools/hooks/klibc /usr/share/initramfs-tools/hooks/iscan /usr/share/initramfs-tools/hooks/busybox /usr/share/initramfs-tools/hooks/keymap /usr/share/initramfs-tools/hooks/udev /usr/share/initramfs-tools/hooks/dmsetup /usr/share/initramfs-tools/hooks/thermal /usr/share/initramfs-tools/hook-functions /usr/share/initramfs-tools/modules.d /usr/share/initramfs-tools/conf.d /usr/share/initramfs-tools/init /usr/share/initramfs-tools/scripts /usr/share/initramfs-tools/scripts/functions /usr/share/initramfs-tools/scripts/init-top /usr/share/initramfs-tools/scripts/init-top/all_generic_ide /usr/share/initramfs-tools/scripts/init-top/keymap /usr/share/initramfs-tools/scripts/init-top/udev /usr/share/initramfs-tools/scripts/init-top/blacklist /usr/share/initramfs-tools/scripts/local-premount /usr/share/initramfs-tools/scripts/local-premount/resume /usr/share/initramfs-tools/scripts/local /usr/share/initramfs-tools/scripts/init-bottom /usr/share/initramfs-tools/scripts/init-bottom/udev /usr/share/initramfs-tools/scripts/nfs AND find /usr/share/initramfs-tools -print0 | xargs -0 dpkg -S iscan, initramfs-tools, udev, dmsetup: /usr/share/initramfs-tools initramfs-tools: /usr/share/initramfs-tools/modules initramfs-tools: /usr/share/initramfs-tools/conf-hooks.d iscan, initramfs-tools, udev, dmsetup: /usr/share/initramfs-tools/hooks initramfs-tools: /usr/share/initramfs-tools/hooks/klibc iscan: /usr/share/initramfs-tools/hooks/iscan initramfs-tools: /usr/share/initramfs-tools/hooks/busybox initramfs-tools: /usr/share/initramfs-tools/hooks/keymap udev: /usr/share/initramfs-tools/hooks/udev dmsetup: /usr/share/initramfs-tools/hooks/dmsetup initramfs-tools: /usr/share/initramfs-tools/hooks/thermal initramfs-tools: /usr/share/initramfs-tools/hook-functions initramfs-tools: /usr/share/initramfs-tools/modules.d initramfs-tools: /usr/share/initramfs-tools/conf.d initramfs-tools: /usr/share/initramfs-tools/init initramfs-tools, udev: /usr/share/initramfs-tools/scripts initramfs-tools: /usr/share/initramfs-tools/scripts/functions initramfs-tools, udev: /usr/share/initramfs-tools/scripts/init-top initramfs-tools: /usr/share/initramfs-tools/scripts/init-top/all_generic_ide initramfs-tools: /usr/share/initramfs-tools/scripts/init-top/keymap udev: /usr/share/initramfs-tools/scripts/init-top/udev initramfs-tools: /usr/share/initramfs-tools/scripts/init-top/blacklist initramfs-tools: /usr/share/initramfs-tools/scripts/local-premount initramfs-tools: /usr/share/initramfs-tools/scripts/local-premount/resume initramfs-tools: /usr/share/initramfs-tools/scripts/local udev: /usr/share/initramfs-tools/scripts/init-bottom udev: /usr/share/initramfs-tools/scripts/init-bottom/udev initramfs-tools: /usr/share/initramfs-tools/scripts/nfs On 06/21/2010 11:50 PM, Michael Prokop wrote: * maximilian attems [Tue Jun 22, 2010 at 12:06:00AM +0200]: your first report shows clearly an mkinitramfs failure, currently we don't know where to trace it. While discussing this with maks we also noticed that this could be caused by a problem in a hook script shipped with sidux. thebickhams - as a first shot towards this idea please provide output of: find /usr/share/initramfs-tools and: find /usr/share/initramfs-tools -print0 | xargs -0 dpkg -S regards, -mika- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c1fefc1.5010...@ntlworld.com
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
hello, On Mon, 21 Jun 2010, thebickhams wrote: > log file as attachment from a quick look at this looks like an older mkinitramfs, we'd need belows output from the one that fails to install: > sh -x /usr/sbin/mkinitramfs -o > /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64.new 2.6.34-0.slh.9-sidux-amd64 > 1>/tmp/mkinitramfs.log 2>&1 please resend from 0.97, thanks. your first report shows clearly an mkinitramfs failure, currently we don't know where to trace it. thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621220600.ga7...@stro.at
How to apt-get install new kernel 2.6.34 on debian ?
How to apt-get install new kernel 2.6.34 on debian ? _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
* maximilian attems [Tue Jun 22, 2010 at 12:06:00AM +0200]: > your first report shows clearly an mkinitramfs failure, > currently we don't know where to trace it. While discussing this with maks we also noticed that this could be caused by a problem in a hook script shipped with sidux. thebickhams - as a first shot towards this idea please provide output of: find /usr/share/initramfs-tools and: find /usr/share/initramfs-tools -print0 | xargs -0 dpkg -S regards, -mika- signature.asc Description: Digital signature
Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
On Mon, 21 Jun 2010, Michael Prokop wrote: > What about a configuration variable to completely disable it (as > mentioned above) and another one to white- or blacklist specific > kernels? well we could have one that can be tristate all, none, version_list? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621221055.gb7...@stro.at
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Sat, 19 Jun 2010, Michal Suchanek wrote: > On 19 June 2010 15:23, maximilian attems wrote: > > On Sat, Jun 19, 2010 at 03:17:20PM +0200, Michal Suchanek wrote: > >> Why is sorting code required? > > > > dpkg --compare-versions does sort rc images before non rc ones. > > as mentioned in the manpages initramfs-tools updates the "newest" one. > > > > here the assumption is that rc is newer then not rc, which is wrong. > > but rc admin should be smart enough to kick rc once the real is out. > > > > So the issue is that it updates the newest kernel, not the running > kernel if that is different. please explain why it should update the running one? this makes zero sense for the most usual case of newer linux-2.6 installed but not yet rebooted. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621221338.gc7...@stro.at
Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
* maximilian attems [Tue Jun 22, 2010 at 12:10:55AM +0200]: > On Mon, 21 Jun 2010, Michael Prokop wrote: > > What about a configuration variable to completely disable it (as > > mentioned above) and another one to white- or blacklist specific > > kernels? > well we could have one that can be tristate all, none, version_list? Yeah, I didn't want to go to far into design detail, but if you agree that the issue should be considered implementing overall I think we should add it to our todolist. regards, -mika- signature.asc Description: Digital signature
Bug#520468: Incorporate fixes for WUSB54GS support from 2.6.33
Possibily you are right. :) It seems to be working for 2.6.32. I'll compile 2.6.34 today or tomorrow without the patch and see if it also works. Thanks, Pitxyoki On Sun, Jun 20, 2010 at 11:29 PM, Ben Hutchings wrote: (...) > > Or possibly this bug fix is bad for that device: > > debian/patches/bugfix/all/rndis_host-Poll-status-channel-before-control-channel.patch > > Could you try reverting that in either of the Debian kernel packages? > > Ben. > > -- > Ben Hutchings > Once a job is fouled up, anything done to improve it makes it worse. > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin7ecsp2bcrjx112ugtxtvtstmiydwsaziqd...@mail.gmail.com
Bug#585790: linux-image-2.6.32-5-kirkwood: Oops in mv_cesa
* Martin Michlmayr | 2010-06-20 14:26:22 [+0100]: >> The patches until 0328ac267 to 15d4dd3 are probably required. > >All of these changes seem pretty self-contained, so I'd like to go >ahead and apply all of them to Debian's 2.6.32 package. Do you see >any problems with this? No I don't, you should be able to take them. I could test the debian kernel with those patches on-top if you want me to. Sebastian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621180755.ga7...@chamillionaire.breakpoint.cc
Re: A way to get 2.6.33 or 34 (or head)?
Jeff Carr writes: > Is there a way to pull down newer versions of the kernels? I put sid > on a new laptop, but the wireless is flaky. It's of course worth > trying newer kernels with something like this. I'd try the stock deb > packages if there was a apt repository for them. It's in experimental: bj...@nemi:~$ apt-cache policy linux-image-2.6.34-1-amd64 linux-image-2.6.34-1-amd64: Installed: (none) Candidate: 2.6.34-1~experimental.2 Version table: 2.6.34-1~experimental.2 0 1 http://ftp.no.debian.org experimental/main Packages See http://wiki.debian.org/DebianExperimental for instructions. Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mxuo71fy@nemi.mork.no
Re: A way to get 2.6.33 or 34 (or head)?
On 06/21/2010 07:47 PM, Jeff Carr wrote: Is there a way to pull down newer versions of the kernels? I put sid on a new laptop, but the wireless is flaky. It's of course worth trying newer kernels with something like this. I'd try the stock deb packages if there was a apt repository for them. =)) ... sorry, but if you read carefully, the subject line is quite funny...:P Second of all, enable experimental, aptitude update, aptitude -t experimental install linux-image-2.6.34-1-amd64 (or whatever your arch is - replace amd64 accordingly) . -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c1fa07a.8010...@gmail.com
Processed: merging mantis driver requests
Processing commands for cont...@bugs.debian.org: > reassign 559915 linux-2.6 Bug #559915 [wnpp] RFP: mantis-driver -- Kernel module for several DVB cards Bug reassigned from package 'wnpp' to 'linux-2.6'. > forcemerge 577264 559915 Bug#577264: V4L/DVB: Add driver for Mantis/Hopper based cards Bug#559915: RFP: mantis-driver -- Kernel module for several DVB cards Forcibly Merged 559915 577264. > thanks Stopping processing here. Please contact me if you need assistance. -- 577264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577264 559915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127714050816074.transcr...@bugs.debian.org
A way to get 2.6.33 or 34 (or head)?
Is there a way to pull down newer versions of the kernels? I put sid on a new laptop, but the wireless is flaky. It's of course worth trying newer kernels with something like this. I'd try the stock deb packages if there was a apt repository for them. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilodvdvqthbmssaptfc4763mslfwbmi5b6l8...@mail.gmail.com
Bug#582177: grub-pc: system with RAID & CRYPTO; tested initramfs-tools under bug #582177
More information: Smoke-tested system with most recent version of grub-pc and grub-common from sid (versions 1.98+20100617-1 and 1.98+20100617-1) and all recent updates for Squeeze. Sorry for the delay, I had to backup everything to the moon before I could do this... ;-) During the execution of update-grub an error message was posted with the NEW kernel (2.6.32-5-amd64) with the OLD grub: paraphrased... cannot identify / (is /dev mounted?) After updating OLD grub to version 1.98+20100617-1 and executing update-grub, the above error message disappeared. However, when I booted the machine, I cannot load the NEW kernel (2.6.32-5- amd64) at all... error message: "error: you need to load the kernel first" "Press any key to continue..." and the grub menu reappears... ...but now I CAN load the initramfs image for the old kernel (2.6.32-3-amd64) that was the original problem. Repeat: I do NOT need to load the initramfs backup image now. The above acts identically with and without the firewire device attached. I am still using the 0.96.1 version of initramfs-tools. C. Cropper -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201006211123.10863.crop...@acm.org
Processed: #575924 forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=16264
Processing commands for cont...@bugs.debian.org: > forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=16264 Bug #575924 [linux-2.6] linux-image-2.6.32-4-amd64: fuse module oops on boot Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=16264' from 'https://bugzilla.kernel.org/show_bug.cgi?id=14347' > End of message, stopping processing here. Please contact me if you need assistance. -- 575924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127713329917724.transcr...@bugs.debian.org
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
* Michael Prokop [Mon Jun 21, 2010 at 01:22:01PM +0200]: > * thebickhams [Mon Jun 21, 2010 at 12:11:12PM > +0100]: > > Still won't update. I note three other people have reported the issue in > > the sidux forums; both 32bit and 64bit. > Please provide output of: > apt-get --download-only --reinstall --print-uris install > 2.6.34-0.slh.9-sidux-amd64 > so I can grab the kernel version on try to reproduce it on my own. Of course I meant linux-image-2.6.34-0.slh.9-sidux-amd64 - I've written with thebickhams via PM. I can't reproduce the problem with the -686 flavour from ftp://ftp.spline.de/pub/sidux/debian/pool/main/l/linux-sidux-2.6/ yet. regards, -mika- signature.asc Description: Digital signature
Bug#498724: ALSA: snd-hda-intel: no working master and unmutable pcm channel
On 02/17/2010 07:38 PM, Moritz Muehlenhoff wrote: > On Fri, Sep 12, 2008 at 05:37:40PM +0200, Alexander Prinsier wrote: >> Package: linux-image-2.6.26-1-686 >> Version: 2.6.26-4 >> Severity: normal >> >> When I run alsamixer, I can see a master channel, but it has no volume >> slider. >> It's possible to mute the master but it has no effect (sound keeps playing). >> >> The PCM channel does control the volume, but it is not mutable (the m key >> doesn't do anything). >> >> Any gui mixer application fails to correctly work in this situation. Muting >> using shortcuts doesn't work, as the only way it could work is by setting >> the volume to 0%, not by actually "muting". >> >> Somehow this problem does not exist in Ubuntu, I don't know how they fixed >> it. > > Sorry for the late response :-/ Also sorry about my late response ;) > The next release of Debian (6.0, code name Squeeze) will be based > on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell > us whether the problem persists. If so, we should report it upstream > to the kernel.org developers. I installed linux-image-2.6.32-bpo.5-686 (version 2.6.32-15~bpo50+1) on my Debian Lenny laptop. After rebooting sound was no longer working. Beeping however still continued to work. With "sound no longer working" I mean I couldn't get any sound player to produce sound. They appeared to be working fine, the progress bar etc advances, but no sound was coming from my speakers. Using alsamixer I double checked that everything was un-muted and volume was set high enough. But relating to the original question, is the bug about unmutable PCM channel gone in the new kernel: NO. Using alsamixer, again I saw a mutable master and an un-mutable PCM channel. I couldn't test whether or not muting the master channel actually mutes the sound now, as no sound was coming from my speakers in any case :) Regards, Alexander -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c1f562f.4010...@mailhaven.com
Bug#584549: linux-2.6: please enable CONFIG_IP_VS_IPV6
Hi, netdev wasn't particularly interested, but Julius Volz, the author of this code directed me to the lvs-users mailing list. Nobody reported any problem since then, but I got a success report, see http://thread.gmane.org/gmane.linux.network/163055/focus=11035 I also got a personal reply from Rob Gallagher. Quoting him: > From: Rob Gallagher > Subject: Re: Is CONFIG_IP_VS_IPV6 still/really dangerous? > To: Ferenc Wagner > Cc: Julius Volz > Date: Thu, 17 Jun 2010 15:56:53 +0100 > > We've been using IPVS with IPv6 on our mirror site, ftp.heanet.ie, for > nearly a year now. > > The only major issue we encountered was with mtu discovery for some > users on IPv6 tunnels, however this was quickly resolved with a patch > from Julius that has since gone into the mainline kernel. The referenced patch is commit 94b26551: IPVS: Add handling of incoming ICMPV6 messages, which is seems to be already present in the Sid kernel. Based on the above, I don't think there are known problems with this option. While it's untested on the wider scale, it seems to work for those using it. Please consider enabling it, or tell me how I could help researching this further. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iq5cpqx3.fsf...@tac.ki.iif.hu
Bug#586494: linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26
> BTW, I also attached the dmesg for 2.6.26 working just > for reference to anyone else who might stumble upon this bug, and for > your curiosity as well. ooops, forgot the attachement. Attached as promised! troubled [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-2-686 (Debian 2.6.26-22lenny1) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed May 12 21:56:10 UTC 2010 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 2000 (usable) [0.00] BIOS-e820: fec0 - fec01000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: fff8 - 0001 (reserved) [0.00] 0MB HIGHMEM available. [0.00] 512MB LOWMEM available. [0.00] found SMP MP-table at [c00fdbd0] 000fdbd0 [0.00] Entering add_active_range(0, 0, 131072) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] Normal 4096 -> 131072 [0.00] HighMem131072 -> 131072 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 -> 131072 [0.00] On node 0 totalpages: 131072 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 992 pages used for memmap [0.00] Normal zone: 125984 pages, LIFO batch:31 [0.00] HighMem zone: 0 pages used for memmap [0.00] Movable zone: 0 pages used for memmap [0.00] DMI not present or invalid. [0.00] ACPI Error (tbxfroot-0218): A valid RSDP was not found [20080321] [0.00] Intel MultiProcessor Specification v1.4 [0.00] Virtual Wire compatibility mode. [0.00] MPTABLE: OEM ID: DELL Product ID: POWEREDGE<6>MPTABLE: Product ID: POWEREDGE<6>MPTABLE: APIC at: 0xFEE0 [0.00] Processor #1 (Bootup-CPU) [0.00] Processor #0 [0.00] Unknown bustype EISA - ignoring [0.00] I/O APIC #2 Version 17 at 0xFEC0. [0.00] Enabling APIC mode: Flat. Using 1 I/O APICs [0.00] Processors: 2 [0.00] Allocating PCI resources starting at 3000 (gap: 2000:dec0) [0.00] PM: Registered nosave memory: 0009f000 - 000a [0.00] PM: Registered nosave memory: 000a - 000f [0.00] PM: Registered nosave memory: 000f - 0010 [0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs [0.00] PERCPU: Allocating 37992 bytes of per cpu data [0.00] NR_CPUS: 8, nr_cpu_ids: 2 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [0.00] Kernel command line: root=/dev/md1 ro vga=787 console=tty0 console=ttyS0 noapic [0.00] mapped APIC to b000 (fee0) [0.00] mapped IOAPIC to a000 (fec0) [0.00] Initializing CPU#0 [0.00] PID hash table entries: 2048 (order: 11, 8192 bytes) [0.00] Detected 299.160 MHz processor. [0.004000] Console: colour dummy device 80x25 [0.004000] console [tty0] enabled [0.004000] console [ttyS0] enabled [0.004000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.004000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.004000] Memory: 508484k/524288k available (1771k kernel code, 15264k reserved, 750k data, 244k init, 0k highmem) [0.004000] virtual kernel memory layout: [0.004000] fixmap : 0xfff4c000 - 0xf000 ( 716 kB) [0.004000] pkmap : 0xff80 - 0xffc0 (4096 kB) [0.004000] vmalloc : 0xe080 - 0xff7fe000 ( 495 MB) [0.004000] lowmem : 0xc000 - 0xe000 ( 512 MB) [0.004000] .init : 0xc037f000 - 0xc03bc000 ( 244 kB) [0.004000] .data : 0xc02bad7d - 0xc0376620 ( 750 kB) [0.004000] .text : 0xc010 - 0xc02bad7d (1771 kB) [0.004000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [0.004000] CPA: page pool initialized 1 of 1 pages preallocated [0.085074] Calibrating delay using timer specific routine.. 600.09 BogoMIPS (lpj=1200192) [0.096006] Security Framework initialized [0.16] SELinux: Disabled at boot. [0.104006] Capability LSM initialized [0.108006] Mount-cache hash table entries: 512 [0.112007] Initializing cgroup subsys ns [0.116007] Initializing cgroup subsys cpuacct [
Processed: reopen 498724
Processing commands for cont...@bugs.debian.org: > reopen 498724 Bug #498724 {Done: Moritz Muehlenhoff } [linux-2.6] ALSA: snd-hda-intel: no working master and unmutable pcm channel > End of message, stopping processing here. Please contact me if you need assistance. -- 498724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127712253418892.transcr...@bugs.debian.org
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
Hi Michael, Still won't update. I note three other people have reported the issue in the sidux forums; both 32bit and 64bit. Best regards, Dai The following packages will be upgraded: initramfs-tools 1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 0B/84.9kB of archives. After this operation, 32.8kB of additional disk space will be used. (Reading database ... 204070 files and directories currently installed.) Preparing to replace initramfs-tools 0.94.4 (using .../initramfs-tools_0.97_all.deb) ... Unpacking replacement initramfs-tools ... Processing triggers for man-db ... Setting up initramfs-tools (0.97) ... Installing new version of config file /etc/initramfs-tools/update-initramfs.conf ... Installing new version of config file /etc/initramfs-tools/initramfs.conf ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 update-initramfs: failed for /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) On 06/21/2010 11:58 AM, Michael Prokop wrote: apt-get install initramfs-tools -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c1f48d0.3050...@ntlworld.com
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
* thebickhams [Mon Jun 21, 2010 at 12:11:12PM +0100]: > Still won't update. I note three other people have reported the issue in > the sidux forums; both 32bit and 64bit. Please provide output of: apt-get --download-only --reinstall --print-uris install 2.6.34-0.slh.9-sidux-amd64 so I can grab the kernel version on try to reproduce it on my own. regards, -mika- signature.asc Description: Digital signature
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
* thebickhams [Mon Jun 21, 2010 at 11:35:52AM +0100]: > On 06/21/2010 11:17 AM, Michael Prokop wrote: >> sh -x /usr/sbin/update-initramfs -u 1>/tmp/update-initramfs.log 2>&1 > Running as root (not sudo), log file attached. > + STATEDIR=/var/lib/initramfs-tools [...] > + return 0 Seems to work as well, huh. And executing "apt-get install initramfs-tools" (to [re]run installation/update) still fails? regards, -mika- signature.asc Description: Digital signature
Bug#551101: still exists
also sprach Ben Hutchings [2010.06.21.1211 +0200]: > We switched from IDE drivers to libata-based drivers in 2.6.32-10. My > suspicion is that this is a bug in ide-cd which will no longer apply. This could very well be. I was running linux-image-2.6.32-bpo.2-amd64 2.6.32-8~bpo50+1 at the time. With linux-image-2.6.32-bpo.5-amd64 2.6.32-15~bpo50+1, the problem seems to have disappeared. Thanks, -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#586494: linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26
Ben, > Another option that may be worth trying is 'noapic'. Wow, that worked just fine actually on 2.6.26 stock kernel. Thanks a lot! I am curious though, what in the world changed since 2.6.18 and lower versions that might have required noapic? I've seen the option needed by so many people on many occasions, but I've never needed it until now. Any ideas? BTW, I also attached the dmesg for 2.6.26 working just for reference to anyone else who might stumble upon this bug, and for your curiosity as well. > You need to get the corresponding linux-base package from testing or > experimental, but the other dependencies should be satisfiable in lenny. FWIW, I did try grab linux-base too, but it then wanted to pull in a bunch of other packages to do with perl and stuff, so I just opted to recompile using the config and the source package and backport it manually with less hassle (assuming 5 hour compiles are less hassle lol). Also, I did try 2.6.32 from squeeze (after removing the lguest makefile line stopping the compile) and the vanilla 2.6.34 (after a UTS issue that involved tweaking /linux/ path to /generated/) kernel with noapic, and everything worked flawlessly. A shame it took an hour to hand configure 2.6.34 though, but at least I know to disable apic now. Anyways, thank you Obi-Wan Kenobi, errr, old Ben Kenobi ;) troubled -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikyzmug-ge0xhhd_kmfjhxsvyun8ecvbmibj...@mail.gmail.com
Bug#551101: still exists
On Mon, 2010-06-21 at 11:33 +0200, martin f krafft wrote: > also sprach Ben Hutchings [2010.06.21.0120 +0200]: > > > I am running 2.6.32 and am faced by exactly this problem on > > > a machine I cannot just reboot: > > > > > > % ps aux | egrep -c '\.+vgdisplay' > > > 37821 > > > > > > lsof or strace on existing processes don't show anything, but strace > > > on a new vgdisplay process shows that it blocks on opening > > > /dev/cdrom, which seems to be defective. > > > > Was this a version before or after the libata transition? > > I have not really followed the transition, but this is on a lenny > system with a 2.6.32 backports.org kernel. How can I check? We switched from IDE drivers to libata-based drivers in 2.6.32-10. My suspicion is that this is a bug in ide-cd which will no longer apply. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
Ben Hutchings writes ("Re: Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated"): > We really need to see the kernel messages reporting soft-lockup. There aren't any. Or, if there are, it isn't printing them to the serial console. Perhaps it is trying to send them only to syslogd which obviously can't write to the disk either. I know that the serial console is working after the crash as it echoes my first carriage return (although then login or the shell wedges before being able to print a prompt). I could have asked for a magic sysrq process dump but given that the process table is probably full I expect this would take many hours at 9600bps. > Note that your disk configuration is unusual and probably not > well-tested by others. It is unlikely that anyone in the kernel team > will be able to debug this as I don't think any of us have particular > expertise in this area. Search the web suggests that symptoms very similar to mine are not uncommon, including instances without soft lockup messages, and none of the other users seem to have a similar disk layout. I can't easily test this theory but I think the unusual disk layout is probably simply making a race easier to trigger. > If you have the opportunity, it would be > helpful if you could test a newer kernel version. This would give us a > clue as to whether the bug has subsequently been fixed upstream, and if > not then it would be the basis for an upstream bug report. Unfortunately testing this bug on the live system involves (a) risking a crash and then if the test fails (b) an extremely vulnerable system without backups for the following four days. I'll see if I can borrow a spare R210 from Jump, in which case I may be able to reproduce the problem in controlled conditions on my coffee table at home (and with access to the VGA console). Which kernel should I test in that case ? Ian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/19487.15030.702626.287...@chiark.greenend.org.uk
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
* thebickhams [Mon Jun 21, 2010 at 11:07:01AM +0100]: > On 06/21/2010 09:43 AM, Michael Prokop wrote: >> sh -x /usr/sbin/mkinitramfs -o >> /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64.new 2.6.34-0.slh.9-sidux-amd64 >> 1>/tmp/mkinitramfs.log 2>&1 > + umask 0022 [...] > + exit 0 Ok, this works as expected. I'd need the same for: sudo sh -x /usr/sbin/update-initramfs -u 1>/tmp/update-initramfs.log 2>&1 please. regards, -mika- signature.asc Description: Digital signature
Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
* maximilian attems [Sat Jun 19, 2010 at 05:06:27PM +0200]: > On Wed, 09 Jun 2010, Michael Prokop wrote: > > How about giving people the chance to disable generation of initrds > > through e.g. /etc/default/initramfs-tools? > well that would assume that you want *none* anywhere, which is often > not the case as you may very well have a "mixed" setup. Good point, thanks. What about a configuration variable to completely disable it (as mentioned above) and another one to white- or blacklist specific kernels? regards, -mika- signature.asc Description: Digital signature
Bug#551101: still exists
also sprach Ben Hutchings [2010.06.21.0120 +0200]: > > I am running 2.6.32 and am faced by exactly this problem on > > a machine I cannot just reboot: > > > > % ps aux | egrep -c '\.+vgdisplay' > > 37821 > > > > lsof or strace on existing processes don't show anything, but strace > > on a new vgdisplay process shows that it blocks on opening > > /dev/cdrom, which seems to be defective. > > Was this a version before or after the libata transition? I have not really followed the transition, but this is on a lenny system with a 2.6.32 backports.org kernel. How can I check? -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
* thebickhams [Mon Jun 21, 2010 at 08:51:00AM +0100]: > The output is as follows : > # sh -x /var/lib/dpkg/info/initramfs-tools.postinst > + set -e > + [ ! -e /etc/initramfs-tools/modules ] > + [ x != xtriggered ] > + dpkg --compare-versions ge 1.14.5ubuntu10~~ > + DPKG_MAINTSCRIPT_PACKAGE= update-initramfs -u > update-initramfs: Generating /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 > My original report was the output of the update from 0.94.4 as I had gone > back to testing after 0.97 failed to update correctly; I got the same > output on trying to update from 0.96.1 to 0.97 Ok, then we need the logfile /tmp/mkinitramfs.log generated by executing: sh -x /usr/sbin/mkinitramfs -o /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64.new 2.6.34-0.slh.9-sidux-amd64 1>/tmp/mkinitramfs.log 2>&1 PS: Please don't drop 586...@bugs.debian.org from the receivers so your mails reach the bug tracking system as well. regards, -mika- signature.asc Description: Digital signature
Processed: Re: Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
Processing commands for cont...@bugs.debian.org: > tags 586554 + moreinfo Bug #586554 [initramfs-tools] initramfs-tools fails to upgrade from 0.96.1 to 0.97 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 586554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127710599714715.transcr...@bugs.debian.org
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
tags 586554 + moreinfo thanks * drb [Sun Jun 20, 2010 at 03:42:34PM +0100]: > Unpacking replacement initramfs-tools ... > Processing triggers for man-db ... > Setting up initramfs-tools (0.97) ... > Installing new version of config file /etc/initramfs-tools/update- > initramfs.conf ... > Installing new version of config file /etc/initramfs-tools/initramfs.conf ... > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools ... > update-initramfs: Generating /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 > update-initramfs: failed for /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 > dpkg: error processing initramfs-tools (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > initramfs-tools > E: Sub-process /usr/bin/dpkg returned an error code (1) > This problem has been noteed with at least two other people using my (sidux) > distro Please execute: sh -x /var/lib/dpkg/info/initramfs-tools.postinst (with root permissions) and provides its output. regards, -mika- signature.asc Description: Digital signature