Bug#404416: Fixed since 2.6.21?
On Sat, 06 Oct 2007 23:34:18 +0200, Philippe Cloutier <[EMAIL PROTECTED]> wrote: I can't reproduce this with Linux >= 2.6.21. Is anyone able to reproduce with a current version? For me updating to kernel 2.6.21 completely solved the problem. Thanks, Marco
Bug#424861: marked as done (linux-image-2.6-686: can't install kernel in sid)
Your message dated Sat, 6 Oct 2007 17:43:45 -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) --- Begin Message --- Package: linux-image-2.6-686 Version: 2.6.17-4 Severity: grave Justification: renders package unusable The dependency for linux-image-2.6-686 in sid is wrong. It's depending on a kernel that's no longer available. I can't upgrade my system because of this. There's another bug report from two weeks ago on this, but it's never even been acknowledged, so I'm trying to nudge *someone* into taking a look at this. I don't know the packaging system particulars, but this can't be a difficult problem to fix. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.17-1-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.17-1-686 2.6.17-4 Linux kernel 2.6.17 image on PPro/ linux-image-2.6-686 recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- 2.6.17-4 was not in sid when the report was opened, so I suppose you missed something. If you're still experiencing this problem, feel free to reopen. --- End Message ---
Re: Preparing another 2.6.22 upload
Martin Michlmayr <[EMAIL PROTECTED]> writes: > * maximilian attems <[EMAIL PROTECTED]> [2007-10-06 21:29]: >> > 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: >> >> i don't get your premise. >> and 2.6.23 doesn't fix those? > > It does, but the d-i beta1 will be based on 2.6.22 so we need a > working 2.6.22. Also, it's not clear how long 2.6.23 will take to > reach testing (just look at 2.6.22) and IP32 (SGI O2) is completely > broken with 2.6.22 - that's definitely worth an upgrade. Of course, > the 2.6.22.x stable updates are important for users too. I agree with this. 2.6.23 is not out of question for beta1 but we can't trust it and we need 2.6.22 to be ready as a safe bed. -- 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]
Re: Preparing another 2.6.22 upload
* Otavio Salvador <[EMAIL PROTECTED]> [2007-10-06 17:03]: > > We need to add the last few stable update for 2.6.22. Any volunteers? > > After it, we'd need another udeb uploading cicle. IIRC last stable > updates also changes ABI, don't they? So far, those changes that change ABI have not been commited. I have no idea if those changes are important or if newer stable updates have any ABI changing patches that are important. Maybe maks knows. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Preparing another 2.6.22 upload
* maximilian attems <[EMAIL PROTECTED]> [2007-10-06 21:29]: > > 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: > > i don't get your premise. > and 2.6.23 doesn't fix those? It does, but the d-i beta1 will be based on 2.6.22 so we need a working 2.6.22. Also, it's not clear how long 2.6.23 will take to reach testing (just look at 2.6.22) and IP32 (SGI O2) is completely broken with 2.6.22 - that's definitely worth an upgrade. Of course, the 2.6.22.x stable updates are important for users too. -- Martin Michlmayr http://www.cyrius.com/ -- 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: i don't get your premise. and 2.6.23 doesn't fix those? happy greeting from a tyrolean place -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Preparing another 2.6.22 upload
Martin Michlmayr <[EMAIL PROTECTED]> writes: > 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 > > We need to add the last few stable update for 2.6.22. Any volunteers? After it, we'd need another udeb uploading cicle. IIRC last stable updates also changes ABI, don't they? -- 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]
Preparing another 2.6.22 upload
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 We need to add the last few stable update for 2.6.22. Any volunteers? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445510: initramfs-tools: please fail gracefully for ENOSPC
Package: initramfs-tools Version: 0.85h Severity: wishlist I recently set up a system with /boot being too small. While this is my fault update-initramfs could handle this in a better way than backup the old (working) initramfs and leave a truncated one for the next reboot will fail. (Yes, it told me that my initramfs was broken afterwards!) (According to my understanding of the scripts the bug also applies to 0.91b.) I therefore suggest not creating the new initramfs directly, but create a new file with a different name and then in the last step rename the stuff if and only if no error occurred. By doing so the system will more often be in a bootable state. Furthermore this will prevent making a system unbootable by suspending the machine while updating the initramfs (a DD reported this on planet.d.o). Helmut [extra info wiped as this bug occurred on a different system] -- 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
On 10/04/2007 07:19:14 PM, maximilian attems wrote: please report, back on it, thanks A problem came up with the SATA drives I can't reproduce. I am using an IDE disk for my regular partitions. I've 2 SATA disks attached to the mobo's chipset SATA. The IDE and the unused (single) internal SATA and unused external sata are on another J Micron controller also built into the mobo, see lspci output above. Anyhow when I went to use the 2 SATA drives attached to the non-J Micron controller fdisk said they could not be read and file -s reported them to be zero length files. I saw no messages on the console or in /var/log/messages or in dmesg. After rebooting I no longer have this problem. One thing I did that might have something to do with something is that I installed mdadm. Trying to raid1 the 2 SATA disks is how I discovered I had a problem, but now the raid array seems to create just fine. On another note one thing that's a bit odd is that the non-J Micron SATA is listed as UMDA/133 in the dmesg output. This is probably because the 0701 BIOS (the latest) only has IDE as an option when configuring these SATA ports. (This is even though the mobo manual says these are SATA 3.0Gb ports. Regards, Karl <[EMAIL PROTECTED]> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein
Processed: Re: Bug#445463: linux-image-2.6.18-5-686: system hangs after a few days: pdflush in D state, JFS?
Processing commands for [EMAIL PROTECTED]: > tags 445463 moreinfo Bug#445463: linux-image-2.6.18-5-686: system hangs after a few days: pdflush in D state, JFS? There were no tags set. Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445463: linux-image-2.6.18-5-686: system hangs after a few days: pdflush in D state, JFS?
tags 445463 moreinfo thanks On Sat, Oct 06, 2007 at 02:59:54AM +0200, Tzafrir Cohen wrote: > My system keeps hanging every week or so. If I manage to catch it before > hanging, I notice that the kernel thread pdflush is in D state and > likewise some other processes. There is a deadlock fixed since .18[1]. Can you please test if .22 or newer fix this problem? Or we may just backport it and test it there. Bastian [1]: 4aa0d230c2cfc1ac4bcf7c5466f9943cf14233a9 (v2.6.20-rc4-23-g4aa0d23) -- One does not thank logic. -- Sarek, "Journey to Babel", stardate 3842.4 signature.asc Description: Digital signature
