Bug#576918: linux-image-2.6-686: Keyboard disabled: atkbd.c: Spurious ACK on isa0060/serio0 ...
On Sat, Apr 10, 2010 at 11:15:22PM +0100, Ben Hutchings wrote: Please report this upstream at https://bugzilla.kernel.org under product 'Drivers', component 'Input Devices'. Let us know the bug number so we can track it. OK. Will do. I am short of time just now. As I no longer have a clear correlation with the spurious interrupt message, I doubt that I have enough information to make a useful bug report. And I should probably try with the latest git kernel before reporting. So it may take a while ael -- 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/20100411094232.ga2...@elf.conquest
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
Hello On Sat, 13 Mar 2010, M G Berberich wrote: It is meant as: “packages and tools which are still being developed, and are still in the alpha testing stage.“ It surely shouldn't be a trash-heap for packages that cannot even be installed, because someone forget to upload the dependies. linux-2.6 images can be installed on their own, this is the point of the linux-2.6 upload to experimental. why would you need kbuild of that version? aboves message has no usage claim at all. A rather late reply to a mail I found in the archives... but regarding the usage claim, I would like to mention that people who use e.g. the nvidia binary driver do not have much fun with the experimental kernel images without the corresponding linux-kbuild package. Although one can find http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage after some googling, it would be nice if the package would be uploaded as well. bye, -christian- -- 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/20100411123342.5abf0...@james.intern
Re: 5.0.4-i386 freezes at boot
Quoting Ben Hutchings b...@decadent.org.uk: Please try to install the 'testing' suite (work in progress for Debian 6.0 'squeeze') using the installer from http://www.debian.org/devel/debian-installer/. This will install a newer kernel version (2.6.32) which might include a fix for this bug. Even if you are sure you want to use Debian 5.0 'lenny', this will at least tell us whether a bug fix exists. Here are the results from my attempt to install *netinst testing squeeze Alpha 1*. Without 'noapic', the newer install did not stop at the MP-BIOS bug error message, but did advance to the language selection screen. But it was impossible to select the language, as the keyboard did not work. With 'noapic', the install proceeded to completion. However, the language/locale selection was strange in that if I selected English as the language, I was only able to select the locale from a list of English-language countries. This does not make sense. I could very well be a native speaker of English residing in a non-English-language locale. Or, I could simply prefer to use English at the installation stage - if there is a problem in the screen Tee pakettienhallintajärjestelmän asetukset, say, then how do I file a bug report if I don't know how that phrase was written, originally, in English? The installer finds the Fedora 12 that I installed earlier and promises that that OS will be bootable in addition to the Debian one. However, when I next restart the machine, the GRUB menu does *not* have an entry for Fedora. There are only Debian entries - 4 of them, in fact. OK, I select the top entry. But... I cannot log in, as the Welcome screen does not accept me either as a normal user or as root. I have now done the installation - all of it - twice, to make sure I did input the password(s) correctly. But, well, no luck. I will note that I have, successively, installed OpenSUSE 11.2, Ubuntu 9.10 and Fedora 12 on this machine. They did have problems, yes, but I could still log in. Also, the Debian install seems to have made the Fedora 12 installation unbootable. A pity, as it was working pretty well this morning. Sakari Aaltonen -- 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/20100411140445.e06924lk1wgck...@webmail3.tkk.fi
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
David didn't leave the linux-...@packages.qa.d.o CC'ed. Re-adding it so that kernel packages maintainers can comment (Ben at first). Quoting David Prévot (dav...@altern.org): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 31/03/2010 12:37, Christian PERRIER a écrit : Most firmware files are not included in the system because no source code is available for them. You may need to reconfigure the package manager to include the non-free section of the package archive before you can install these firmware files. It may be pedantic, but the reason why most firmware are not available is because they do not conform to the Debian Free Software Guidelines: they might be open source with a non compatible license. Anyway, I don't know for sure for the Linux kernel : all the non free firmware may also be closed source. Unless you are exclusively referencing the firmware-linux-nonfree package, which is in the non-free section, some firmware can also be available through the contrib section (bcm43xx-fwcutter used to download sources, extract and install firmware from these downloaded files. I don't know if some packages are still running this way). I really might be talking nonsense, but if not, what about (no doubt that it needs to be rephrased in proper English) : Most firmware files are not included in the system because they do not conform to the Debian Free Software Guidelines. You may need to reconfigure the package manager to include the contrib and non-free sections of the package archive before you can install these firmware files. Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvBIv0ACgkQ18/WetbTC/oDTQCfStHyPv5ywdIaCjBOMm4X/VCU bOIAnA1krBbuCfWdenYAKLNmq6i79ecP =V2MH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-l10n-english-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hpr7u0$qm...@dough.gmane.org ** CRM114 Whitelisted by: WHITELIST ** -- signature.asc Description: Digital signature
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
On Sun, 2010-04-11 at 16:20 +0200, Christian PERRIER wrote: David didn't leave the linux-...@packages.qa.d.o CC'ed. Re-adding it so that kernel packages maintainers can comment (Ben at first). Quoting David Prévot (dav...@altern.org): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 31/03/2010 12:37, Christian PERRIER a écrit : Most firmware files are not included in the system because no source code is available for them. You may need to reconfigure the package manager to include the non-free section of the package archive before you can install these firmware files. It may be pedantic, but the reason why most firmware are not available is because they do not conform to the Debian Free Software Guidelines: they might be open source with a non compatible license. Anyway, I don't know for sure for the Linux kernel : all the non free firmware may also be closed source. Indeed, we do not have source code for any of the non-free firmware. In many cases it is under a BSDish licence and would thus become DFSG-free if the source code was released. Unless you are exclusively referencing the firmware-linux-nonfree package, which is in the non-free section, some firmware can also be available through the contrib section (bcm43xx-fwcutter used to download sources, extract and install firmware from these downloaded files. I don't know if some packages are still running this way). [...] They might be; I hadn't thought tof that. 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
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, Apr 11, 2010 at 12:33:42PM +0200, Christian Hammers wrote: A rather late reply to a mail I found in the archives... but regarding the usage claim, I would like to mention that people who use e.g. the nvidia binary driver do not have much fun with the experimental kernel images without the corresponding linux-kbuild package. binary out of tree stuff is not our focus, use nouveau. and woow this is a DD email adress, you can't be serious. -- 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/20100411142806.ga13...@baikonur.stro.at
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
Quoting Ben Hutchings (b...@decadent.org.uk): It may be pedantic, but the reason why most firmware are not available is because they do not conform to the Debian Free Software Guidelines: they might be open source with a non compatible license. Anyway, I don't know for sure for the Linux kernel : all the non free firmware may also be closed source. Indeed, we do not have source code for any of the non-free firmware. In many cases it is under a BSDish licence and would thus become DFSG-free if the source code was released. Can you comment (maybe later) on David's proposal so that I can decide whether to include that paragraph in the reviewed templates. signature.asc Description: Digital signature
Re: 5.0.4-i386 freezes at boot
On Sun, 2010-04-11 at 14:04 +0300, Sakari Aaltonen wrote: Quoting Ben Hutchings b...@decadent.org.uk: Please try to install the 'testing' suite (work in progress for Debian 6.0 'squeeze') using the installer from http://www.debian.org/devel/debian-installer/. This will install a newer kernel version (2.6.32) which might include a fix for this bug. Even if you are sure you want to use Debian 5.0 'lenny', this will at least tell us whether a bug fix exists. Here are the results from my attempt to install *netinst testing squeeze Alpha 1*. Without 'noapic', the newer install did not stop at the MP-BIOS bug error message, but did advance to the language selection screen. But it was impossible to select the language, as the keyboard did not work. This is obviously a kernel bug, but may be fixed now (the installer currently runs on Linux 2.6.30 but installs 2.6.32). With 'noapic', the install proceeded to completion. However, the language/locale selection was strange in that if I selected English as the language, I was only able to select the locale from a list of English-language countries. This does not make sense. I could very well be a native speaker of English residing in a non-English-language locale. You may need to use 'expert' mode to make that choice. However I believe there have been some later changes to locale selection to make it more flexible. Or, I could simply prefer to use English at the installation stage - if there is a problem in the screen Tee pakettienhallintajärjestelmän asetukset, say, then how do I file a bug report if I don't know how that phrase was written, originally, in English? The installer finds the Fedora 12 that I installed earlier and promises that that OS will be bootable in addition to the Debian one. However, when I next restart the machine, the GRUB menu does *not* have an entry for Fedora. There are only Debian entries - 4 of them, in fact. OK, I select the top entry. But... I cannot log in, as the Welcome screen does not accept me either as a normal user or as root. I have now done the installation - all of it - twice, to make sure I did input the password(s) correctly. But, well, no luck. I'm wondering whether the keyboard is still broken here. Did you type the username in or did you select it with the mouse? Or were you forced to select the wrong keymap for your keyboard because of the restrictions in the installer? I will note that I have, successively, installed OpenSUSE 11.2, Ubuntu 9.10 and Fedora 12 on this machine. They did have problems, yes, but I could still log in. Also, the Debian install seems to have made the Fedora 12 installation unbootable. A pity, as it was working pretty well this morning. Sorry about that; maybe the installer developers (debian-boot list) can help you to debug and fix this. 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#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot
On Sat, 2010-04-10 at 23:05 -0400, Denis Laxalde wrote: Hi, On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote: The more serious error messages suggest memory corruption. Have you tested the RAM with memtest86+ yet? Yes, I've just run a pretty long test with memtest86+ and there was no error reported. OK, so we can be fairly sure this is a kernel bug. Please report this at https://bugzilla.kernel.org. It is hard to know where the bug may be, but try submitting it under product 'Memory Management', component 'Slab Allocator'. Let us know the bug number so we can track it. 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#509923: dmesg output
Further to the last post. These are the errors I see from pata_marvell
on boot with drives attached to the controller if I leave everything as
default.
pata_marvell :03:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
pata_marvell :03:00.0: setting latency timer to 64
scsi2 : pata_marvell
scsi3 : pata_marvell
ata3: PATA max UDMA/100 cmd 0xef00 ctl 0xee00 bmdma 0xeb00 irq 16
ata4: PATA max UDMA/133 cmd 0xed00 ctl 0xec00 bmdma 0xeb08 irq 16
BAR5:00:04 01:7F 02:22 03:C8 04:02 05:00 06:00 07:80 08:00 09:00 0A:00
0B:00 0C:1F 0D:00 0E:00 0F:00
ata4.01: qc timeout (cmd 0xec)
ata4.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4: link is slow to respond, please be patient (ready=0)
ata4: device not ready (errno=-16), forcing hardreset
ata4: link is slow to respond, please be patient (ready=0)
ata4: SRST failed (errno=-16)
ata4: link is slow to respond, please be patient (ready=0)
ata4: SRST failed (errno=-16)
ata4: link is slow to respond, please be patient (ready=0)
ata4: SRST failed (errno=-16)
ata4: SRST failed (errno=-16)
ata4: reset failed, giving up
ata4: link is slow to respond, please be patient (ready=0)
ata4: device not ready (errno=-16), forcing hardreset
ata4: soft resetting link
ata4: link is slow to respond, please be patient (ready=0)
ata4: SRST failed (errno=-16)
ata4: soft resetting link
ata4: link is slow to respond, please be patient (ready=0)
ata4: SRST failed (errno=-16)
ata4: soft resetting link
ata4: link is slow to respond, please be patient (ready=0)
ata4: SRST failed (errno=-16)
ata4: soft resetting link
ata4: SRST failed (errno=-16)
ata4: reset failed, giving up
ata4: EH complete
If I blacklist pata_marvell and set ahci.enable_marvell=1 I get similar
problems.
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata4.00: failed command: IDENTIFY DEVICE
ata3.00: failed command: IDENTIFY DEVICE
ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
res 40/00:00:1f:00:00/00:00:00:00:00/e0 Emask 0x4 (timeout)
ata3.00: status: { DRDY }
ata4.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3: hard resetting link
ata4.00: status: { DRDY }
ata4: hard resetting link
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
eth0: no IPv6 routers present
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3: hard resetting link
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0xec)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3: limiting SATA link speed to 1.5 Gbps
ata3: hard resetting link
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Cheers,
D.
--
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/1270997684.28817.21.ca...@nano.danalderman.co.uk
Re: 5.0.4-i386 freezes at boot
Quoting Ben Hutchings b...@decadent.org.uk: I'm wondering whether the keyboard is still broken here. Did you type the username in or did you select it with the mouse? Or were you forced to select the wrong keymap for your keyboard because of the restrictions in the installer? I typed in the usernames, both 'root' and my own. They appeared correctly on-screen, so I would assume the passwords that I typed in were correct, too. But the installed system just did not accept them. I will note that I have, successively, installed OpenSUSE 11.2, Ubuntu 9.10 and Fedora 12 on this machine. They did have problems, yes, but I could still log in. Also, the Debian install seems to have made the Fedora 12 installation unbootable. A pity, as it was working pretty well this morning. Sorry about that; maybe the installer developers (debian-boot list) can help you to debug and fix this. It's OK; I found instructions at http://fedoraforum.org/forum/showthread.php?t=975 on what to do to make the Fedora 12 installation bootable again. It's odd how the Debian installer (correctly) claims to have identified the F12 (on a different partition), but then does not list it in the boot menu. Sakari Aaltonen -- 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/20100411194831.6l5azzmyo0gwc...@webmail1.tkk.fi
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, Apr 11 2010, maximilian attems wrote:
On Sun, Apr 11, 2010 at 12:33:42PM +0200, Christian Hammers wrote:
A rather late reply to a mail I found in the archives... but regarding
the usage claim, I would like to mention that people who use e.g. the
nvidia binary driver do not have much fun with the experimental kernel
images without the corresponding linux-kbuild package.
binary out of tree stuff is not our focus, use nouveau.
Or just use make-kpkg. It does not care where you get the kernel
sources from; it just builds the packages. Works from git, or the
official kernel sources, and with nvidia as well.
and woow this is a DD email adress, you can't be serious.
Seriously, I use nvidia non-free drivers as well. I can affirm
that I can pull from stable, or Linus' tree, and build kernel images
and nvidia modules. My usual sequence of action is to
,
| % cd /usr/local/src/kernel/linus-tree.git
| % git fetch stable
| % git co -b my-machine-v2.6.33.2 v2.6.33.2
| % make oldconfig
| % ./.compile_command
| % sudo dpkg -i ../*.deb
`
Where .compile command looks like:
,
| #!/bin/sh
|
| export MODULE_LOC=/usr/local/src/kernel/modules
|
| # Optionally, refresh the nvidia module
| # rm -rf ${MODULE_LOC}/nvidia-kernel
| # (cd /usr/local/src/kernel; tar jfx /usr/src/nvidia-kernel.tar.bz2
|
| # make sure we get a machine specific name for the image, even if
| # I forgot toe specify one on the command line
| ev=$(uname -n)
|
| # Use the version extension given on the command line, if any
| if [ -n $1 ]; then
| ev=$1
| fi
|
| make-kpkg --rootcmd=fakeroot --append-to-version=-$ev kernel_image
| fakeroot make-kpkg --append-to-version=-$ev modules_image
`
Once you have your variant of .compile_command, building kernels
and nvidia packages is painless :-)
manoj
--
Exceptions prove the rule, and wreck the budget. Miller
Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C
--
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/87zl19kj4k@anzu.internal.golden-gryphon.com
Bug#536896: linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace
On Thu, 25 Feb 2010, Moritz Muehlenhoff wrote:
On Tue, Jul 14, 2009 at 09:57:54PM +0800, James Andrewartha wrote:
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-17
Severity: normal
All audio from gstreamer-using apps (eg Totem and Banshee) pops when I use a
2.6.{25,26,28,30} amd64 kernel and i386 userspace. 2.6.24-etchnhalf.1-amd64
does not have this problem, nor does 2.6.26-2-686. It doesn't occur when
using
non-gstreamer apps like mplayer or mpd, nor with various gst-launch
pipelines
suggested by #gstreamer like gst-launch playbin uri=file:///home/trs80/a.mp3
Hi,
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.
The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.
I've bisected it, and the bad patch is 130755108ba03461f69da990e54e02a254accd23:
Author: Takashi Iwai ti...@suse.de 2008-01-09 02:08:14
Committer: Jaroslav Kysela pe...@perex.cz 2008-02-01 01:29:47
Parent: d948035a928400ae127c873fbf771389bee18949 ([ALSA] Remove PCM xfer_align
sw params)
[ALSA] PCM - clean up snd_pcm_lib_read/write
Introduce a common helper function for snd_pcm_lib_read and
snd_pcm_lib_write
for cleaning up the code.
Signed-off-by: Takashi Iwai ti...@suse.de
Signed-off-by: Jaroslav Kysela pe...@perex.cz
I don't know anything about this code, but I'm happy to deal with upstream
if you'd prefer me to.
--
# TRS-80 trs80(a)ucc.gu.uwa.edu.au #/ Otherwise Bub here will do \
# UCC Wheel Member http://trs80.ucc.asn.au/ #| what squirrels do best |
[ There's nobody getting rich writing ]| -- Collect and hide your |
[ software that I know of -- Bill Gates, 1980 ]\ nuts. -- Acid Reflux #231 /
--
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/alpine.deb.1.10.1004120102110.24...@martello.ucc.gu.uwa.edu.au
Bug#557033: linux-image-2.6.32-4-amd64: bug still present
Package: linux-2.6 Version: 2.6.32-10 Severity: normal I have very similar hardware to the original reporter's: Core i7 860, P55-based motherboard (Asus P7P55-M), NVIDIA graphics card. Here's the call trace produced by the hpet.c warning: Apr 11 12:35:48 stratocaster kernel: [5.730742] [ cut here ] Apr 11 12:35:48 stratocaster kernel: [5.730749] WARNING: at /build/mattems-linux-2.6_2.6.32-10-amd64-Ff7Wwa/linux-2.6-2.6.3 2-10/debian/build/source_amd64_none/arch/x86/kernel/hpet.c:392 hpet_next_event+0x52/0x77() Apr 11 12:35:48 stratocaster kernel: [5.730752] Hardware name: System Product Name Apr 11 12:35:48 stratocaster kernel: [5.730753] Modules linked in: psmouse serio_raw processor(+) usbhid hid ext3 jbd mbcac he sg usb_storage sr_mod sd_mod cdrom crc_t10dif ata_generic pata_via r8169 ata_piix ehci_hcd firewire_ohci libata mii usbcore button nls_base firewire_core crc_itu_t scsi_mod thermal fan thermal_sys [last unloaded: scsi_wait_scan] Apr 11 12:35:48 stratocaster kernel: [5.730774] Pid: 0, comm: swapper Not tainted 2.6.32-4-amd64 #1 Apr 11 12:35:48 stratocaster kernel: [5.730775] Call Trace: Apr 11 12:35:48 stratocaster kernel: [5.730779] [8102b587] ? hpet_next_event+0x52/0x77 Apr 11 12:35:48 stratocaster kernel: [5.730782] [8102b587] ? hpet_next_event+0x52/0x77 Apr 11 12:35:48 stratocaster kernel: [5.730785] [8104dbe4] ? warn_slowpath_common+0x77/0xa3 Apr 11 12:35:48 stratocaster kernel: [5.730788] [8102b587] ? hpet_next_event+0x52/0x77 Apr 11 12:35:48 stratocaster kernel: [5.730793] [8106fa7b] ? tick_dev_program_event+0x2d/0x95 Apr 11 12:35:48 stratocaster kernel: [5.730796] [8106f4f9] ? tick_broadcast_oneshot_control+0x9c/0xf4 Apr 11 12:35:48 stratocaster kernel: [5.730799] [8106eec3] ? tick_notify+0x218/0x36e Apr 11 12:35:48 stratocaster kernel: [5.730802] [810681b1] ? notifier_call_chain+0x29/0x4c Apr 11 12:35:48 stratocaster kernel: [5.730805] [8106e8ef] ? clockevents_notify+0x31/0x115 Apr 11 12:35:48 stratocaster kernel: [5.730809] [810170cd] ? read_tsc+0xa/0x20 Apr 11 12:35:48 stratocaster kernel: [5.730817] [a0185407] ? acpi_idle_enter_bm+0x17b/0x2a5 [processor] Apr 11 12:35:48 stratocaster kernel: [5.730821] [81232456] ? menu_select+0x145/0x205 Apr 11 12:35:48 stratocaster kernel: [5.730825] [81231757] ? cpuidle_idle_call+0x95/0xee Apr 11 12:35:48 stratocaster kernel: [5.730829] [8100fe90] ? cpu_idle+0xa2/0xda Apr 11 12:35:48 stratocaster kernel: [5.730831] ---[ end trace 76231a6dbff94f70 ]--- -- Package-specific info: ** Version: Linux version 2.6.32-4-amd64 (Debian 2.6.32-10) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Mar 17 03:23:53 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-4-amd64 root=UUID=8d303374-9e9e-494f-862e-be63e69f0fdb ro quiet ** Tainted: PW (513) * Proprietary module has been loaded. * Taint on warning. ** Kernel log: [ 16.633146] Bluetooth: SCO socket layer initialized [ 16.764817] lp0: using parport0 (interrupt-driven). [ 16.820319] ppdev: user-space parallel port driver [ 20.317873] eth0: no IPv6 routers present [ 31.499509] CPU0 attaching NULL sched-domain. [ 31.499511] CPU1 attaching NULL sched-domain. [ 31.499513] CPU2 attaching NULL sched-domain. [ 31.499514] CPU3 attaching NULL sched-domain. [ 31.499515] CPU4 attaching NULL sched-domain. [ 31.499516] CPU5 attaching NULL sched-domain. [ 31.499517] CPU6 attaching NULL sched-domain. [ 31.499518] CPU7 attaching NULL sched-domain. [ 31.603308] CPU0 attaching sched-domain: [ 31.603314] domain 0: span 0,4 level SIBLING [ 31.603317] groups: 0 (cpu_power = 589) 4 (cpu_power = 589) [ 31.603326] domain 1: span 0-7 level MC [ 31.603329]groups: 0,4 (cpu_power = 1178) 1,5 (cpu_power = 1178) 2,6 (cpu_power = 1178) 3,7 (cpu_power = 1178) [ 31.603344] CPU1 attaching sched-domain: [ 31.603347] domain 0: span 1,5 level SIBLING [ 31.603350] groups: 1 (cpu_power = 589) 5 (cpu_power = 589) [ 31.603357] domain 1: span 0-7 level MC [ 31.603360]groups: 1,5 (cpu_power = 1178) 2,6 (cpu_power = 1178) 3,7 (cpu_power = 1178) 0,4 (cpu_power = 1178) [ 31.603373] CPU2 attaching sched-domain: [ 31.603376] domain 0: span 2,6 level SIBLING [ 31.603379] groups: 2 (cpu_power = 589) 6 (cpu_power = 589) [ 31.603387] domain 1: span 0-7 level MC [ 31.603390]groups: 2,6 (cpu_power = 1178) 3,7 (cpu_power = 1178) 0,4 (cpu_power = 1178) 1,5 (cpu_power = 1178) [ 31.603403] CPU3 attaching sched-domain: [ 31.603406] domain 0: span 3,7 level SIBLING [ 31.603409] groups: 3 (cpu_power = 589) 7 (cpu_power = 589) [ 31.603416] domain 1: span 0-7 level MC [ 31.603419]groups: 3,7 (cpu_power = 1178) 0,4 (cpu_power = 1178) 1,5
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, Apr 11, 2010 at 10:13:15AM -0700, Manoj Srivastava wrote: Seriously, I use nvidia non-free drivers as well. I can affirm that I can pull from stable, or Linus' tree, and build kernel images and nvidia modules. My usual sequence of action is to yes indeed you lost *all* of my respect, when you were crying out about firmware issues in linux-2.6, did zero work on it, and then run an immense blob in ring 0. not happy that you are still doing although nouveau is shaping up. dude you are very inconsistent. BTW i saw no thank you from your side for the work that Ben did in linux-2.6, porting drivers to request_firmware, firmware relicensing. so until that any mail from you may be ignored. -- 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/20100411173851.gd13...@baikonur.stro.at
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, Apr 11 2010, maximilian attems wrote: On Sun, Apr 11, 2010 at 10:13:15AM -0700, Manoj Srivastava wrote: Seriously, I use nvidia non-free drivers as well. I can affirm that I can pull from stable, or Linus' tree, and build kernel images and nvidia modules. My usual sequence of action is to yes indeed you lost *all* of my respect, when you were crying out about firmware issues in linux-2.6, did zero work on it, and then run an immense blob in ring 0. You seem to mistake what Debian does, and what we support our users doing. Debian should not ship binary blobs. But if users want to do so, we support them. not happy that you are still doing although nouveau is shaping up. dude you are very inconsistent. No, I am not inconsistent. I just distinguish between what we do (no non-free) and what we let users do (we ack that users do need non-free sutff, and we help users) BTW i saw no thank you from your side for the work that Ben did in linux-2.6, porting drivers to request_firmware, firmware relicensing. so until that any mail from you may be ignored. While the kernel team has its current composition, you are unlikely to see much help from me, no. The tone of the email I am responding to is exemplar. manoj -- Life is like a 10 speed bicycle. Most of us have gears we never use. Schultz Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C -- 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/87vdbxkgef@anzu.internal.golden-gryphon.com
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, 2010-04-11 at 11:12 -0700, Manoj Srivastava wrote: On Sun, Apr 11 2010, maximilian attems wrote: On Sun, Apr 11, 2010 at 10:13:15AM -0700, Manoj Srivastava wrote: Seriously, I use nvidia non-free drivers as well. I can affirm that I can pull from stable, or Linus' tree, and build kernel images and nvidia modules. My usual sequence of action is to yes indeed you lost *all* of my respect, when you were crying out about firmware issues in linux-2.6, did zero work on it, and then run an immense blob in ring 0. You seem to mistake what Debian does, and what we support our users doing. Debian should not ship binary blobs. But if users want to do so, we support them. [...] We shouldn't stand in their way but we have no obligation and limited ability to support them. 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#534422: Bug#576800: libc6: Cannot create new processes after hibernating
On 07/04/2010 15:48, Aurelien Jarno wrote: Francois Gouget a écrit : Package: libc6 Version: 2.10.2-6 Severity: critical Justification: breaks the whole system After resuming my EeePC from hibernation, I can no longer start new processes. This goes so far as preventing shutdown since init itself cannot be forked so that the only solution is a hard reset. Hence the 'breaks the whole system' justification. Also, although this only happens after hibernating, I feel this is a pretty unavoidable activity on a laptop. Since no new process can be started (including gdb, strace, etc), this is quite hard to debug. I do get some traces in /var/log/syslog though: Apr 7 11:58:47 malte kernel: [ 122.856385] sh[2687]: segfault at b773f11f ip b772f001 sp bffb8300 error 7 in ld-2.10.2.so[b7725000+1c000] Apr 7 11:58:47 malte kernel: [ 122.961515] date[2690]: segfault at b781f11f ip b780f001 sp bfaaed00 error 7 in ld-2.10.2.so[b7805000+1c000] Apr 7 11:58:47 malte kernel: [ 122.963258] sort[2693]: segfault at b78e311f ip b78d3001 sp bfa10ad0 error 7 in ld-2.10.2.so[b78c9000+1c000] Apr 7 11:58:47 malte kernel: [ 122.963836] uniq[2694]: segfault at b787c11f ip b786c001 sp bfa5fdc0 error 7 in ld-2.10.2.so[b7862000+1c000] Apr 7 11:58:47 malte kernel: [ 122.966155] rm[2696]: segfault at b770711f ip b76f7001 sp bff05d20 error 7 in ld-2.10.2.so[b76ed000+1c000] I am reporting this bug against libc6 because if I understand the above traces correctly, they indicate that the crash occurs in ld-2.10.2.so which belongs to libc6. But I acknowledge that the bug may instead be in the Linux kernel. In my case: ii linux-image-2.6-6862.6.32+25 Linux 2.6 for modern PCs ii linux-image-2.6.32-3-686 2.6.32-9 Linux 2.6.32 for modern PCs What is your video card? If it is and Intel one, it's likely a memory corruption caused by the video driver: https://bugzilla.kernel.org/show_bug.cgi?id=13811 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534422 I also have a Intel video card and I experienced this kind of behavior recently. More exactly, its happens about half the times when I suspended my laptop with kernel linux-image-2.6.32-4-amd64 version 2.6.32-11. Two times, this even leads to on-disk corruption. Since, I go back to 2.6.32-10. I still sometimes see this behavior (all applications failing after resume) but it is far less often. Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main -- 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/4bc2248b.7020...@free.fr
Processed: tagging 536896, bug 536896 is forwarded to alsa-de...@alsa-project.org
Processing commands for cont...@bugs.debian.org: tags 536896 - moreinfo Bug #536896 [linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace Removed tag(s) moreinfo. forwarded 536896 alsa-de...@alsa-project.org Bug #536896 [linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace Set Bug forwarded-to-address to 'alsa-de...@alsa-project.org'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.127101756210179.transcr...@bugs.debian.org
Bug#536896: linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace
[Earlier messages can be found at http://bugs.debian.org/536896 ]
On Mon, 2010-04-12 at 01:08 +0800, James Andrewartha wrote:
On Thu, 25 Feb 2010, Moritz Muehlenhoff wrote:
On Tue, Jul 14, 2009 at 09:57:54PM +0800, James Andrewartha wrote:
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-17
Severity: normal
All audio from gstreamer-using apps (eg Totem and Banshee) pops when I
use a
2.6.{25,26,28,30} amd64 kernel and i386 userspace.
2.6.24-etchnhalf.1-amd64
does not have this problem, nor does 2.6.26-2-686. It doesn't occur when
using
non-gstreamer apps like mplayer or mpd, nor with various gst-launch
pipelines
suggested by #gstreamer like gst-launch playbin
uri=file:///home/trs80/a.mp3
Hi,
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.
The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.
I've bisected it, and the bad patch is
130755108ba03461f69da990e54e02a254accd23:
Thanks for taking the time to do this.
Author: Takashi Iwai ti...@suse.de 2008-01-09 02:08:14
Committer: Jaroslav Kysela pe...@perex.cz 2008-02-01 01:29:47
Parent: d948035a928400ae127c873fbf771389bee18949 ([ALSA] Remove PCM
xfer_align sw params)
[ALSA] PCM - clean up snd_pcm_lib_read/write
Introduce a common helper function for snd_pcm_lib_read and
snd_pcm_lib_write
for cleaning up the code.
Signed-off-by: Takashi Iwai ti...@suse.de
Signed-off-by: Jaroslav Kysela pe...@perex.cz
I don't know anything about this code, but I'm happy to deal with upstream
if you'd prefer me to.
The above commit is supposed to be cleanup, but it has at least one
semantic change: snd_pcm_mmap_control::avail_min no longer applies to
non-blocking file handles. I don't know whether this is was an
intentional or unintentional change, but it wasn't commented. I also
don't know whether this can explain the popping, but I expect that it
has changed the timing of audio I/O.
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
Re: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
On Sun, 2010-04-11 at 16:54 +0200, Christian PERRIER wrote: Quoting Ben Hutchings (b...@decadent.org.uk): It may be pedantic, but the reason why most firmware are not available is because they do not conform to the Debian Free Software Guidelines: they might be open source with a non compatible license. Anyway, I don't know for sure for the Linux kernel : all the non free firmware may also be closed source. Indeed, we do not have source code for any of the non-free firmware. In many cases it is under a BSDish licence and would thus become DFSG-free if the source code was released. Can you comment (maybe later) on David's proposal so that I can decide whether to include that paragraph in the reviewed templates. I am happy with David's version, if you do not think it will be too much trouble for translators who have already started. 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
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, Apr 11 2010, Ben Hutchings wrote: On Sun, 2010-04-11 at 11:12 -0700, Manoj Srivastava wrote: On Sun, Apr 11 2010, maximilian attems wrote: On Sun, Apr 11, 2010 at 10:13:15AM -0700, Manoj Srivastava wrote: Seriously, I use nvidia non-free drivers as well. I can affirm that I can pull from stable, or Linus' tree, and build kernel images and nvidia modules. My usual sequence of action is to yes indeed you lost *all* of my respect, when you were crying out about firmware issues in linux-2.6, did zero work on it, and then run an immense blob in ring 0. You seem to mistake what Debian does, and what we support our users doing. Debian should not ship binary blobs. But if users want to do so, we support them. [...] We shouldn't stand in their way but we have no obligation and limited ability to support them. I think we put it as: , | We acknowledge that some of our users require the use of works that do | not conform to the Debian Free Software Guidelines. | | SNIP parts about contrinb and non-free | | Thus, although non-free works are not a part of Debian, we | support their use and provide infrastructure for non-free | packages (such as our bug tracking system and mailing lists). ` However, I think your statement is reasonable. The level of support depends on the teams/maintainers. Supporting free software comes above supporting non-free software. The kernel team has made their level of commitment clear, as is proper. Indeed, I don't expect the kernel team to support either non-debian sources, nor _any_ third party modules, really. Which is why I directed the user to make-kpkg, which does, to an extent, supports both. manoj -- DeVries' Dilemma: If you hit two keys on the typewriter, the one you don't want hits the paper. Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C -- 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/87r5mlk7z8@anzu.internal.golden-gryphon.com
Processed: tagging 571279
Processing commands for cont...@bugs.debian.org: tags 571279 - moreinfo Bug #571279 [linux-2.6] suspend-script: kernel errors when resuming from suspend Ignoring request to alter tags of bug #571279 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.12710205123614.transcr...@bugs.debian.org
Bug#509923: dmesg output
On Sun, 2010-04-11 at 15:54 +0100, Dan Alderman wrote: Further to the last post. These are the errors I see from pata_marvell on boot with drives attached to the controller if I leave everything as default. [...] I see, so you are in an even worse situation with neither driver working for you. Unfortunately the vendor driver is so different from current in-tree drivers that I cannot begin to look for significant differences in hardware setup. Please report this upstream at https://bugzilla.kernel.org, under product 'IO/Storage', component 'Serial ATA' and let us know the bug number so we can track it. 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#566516: linux-image-2.6.32-trunk-686: suspend failure in ehci_hcd
On Sat, 2010-01-23 at 19:00 +0100, Thiemo Nagel wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: normal Sometimes, my Eee PC 1000HG fails to suspend and I get: [130899.106047] sd 0:0:0:0: [sda] Stopping disk [130899.971193] ACPI handle has no context! [130899.971205] ACPI handle has no context! [130899.984470] ata_piix :00:1f.2: PCI INT B disabled [130900.000260] hcd_pci_suspend(): ehci_pci_suspend+0x0/0x6f [ehci_hcd] returns -22 [130900.000305] pci_pm_suspend(): hcd_pci_suspend+0x0/0x6c [usbcore] returns -22 [130900.000324] pm_op(): pci_pm_suspend+0x0/0xc1 returns -22 [130900.000335] PM: Device :00:1d.7 failed to suspend: error -22 [130900.000342] PM: Some devices failed to suspend Running rmmod ehci_hcd modprobe ehci_hcd cures the problem. Sorry for the delay in responding to this. Does this problem still occur when using the current kernel version (2.6.32-9 in testing or 2.6.32-11 in unstable)? If this bug is not fixed, please report it at https://bugzilla.kernel.org under product 'Drivers', component 'USB'. Then let us know the bug number so we can track it. 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
Processed: Re: Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot
Processing commands for cont...@bugs.debian.org: forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347 Bug #575924 [linux-2.6] linux-image-2.6.32-4-amd64: fuse module oops on boot Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=14347'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.127102465227736.transcr...@bugs.debian.org
Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot
forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347 thanks On Sun, 11 Apr 2010 16:05:57 +0100, Ben Hutchings wrote: On Sat, 2010-04-10 at 23:05 -0400, Denis Laxalde wrote: Hi, On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote: The more serious error messages suggest memory corruption. Have you tested the RAM with memtest86+ yet? Yes, I've just run a pretty long test with memtest86+ and there was no error reported. OK, so we can be fairly sure this is a kernel bug. Please report this at https://bugzilla.kernel.org. It is hard to know where the bug may be, but try submitting it under product 'Memory Management', component 'Slab Allocator'. Let us know the bug number so we can track it. The above bug report looks similar, so I just added comments and dmesgs there. Maybe the bug should be retitled ? Cheers, Denis -- 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/20100411182357.6be83...@schloss
Little Bang timing
Hi maks I wanted to time the new pre cached boot scripts when I read about them, but no watch battery... Anyways, today I grabbed my old pocketwatch and timed the boot. 45 seconds from grub-pc selection to cli login. I upgraded both initramfs-tools and linux-image-2.6.32-4-686 than timed the reboot at 30 seconds from Grub to login. Very nice. I have a few more installations to test all of next week and will look for boot messages as I try to follow what the team has done vvill -- 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/733269.42823...@web35605.mail.mud.yahoo.com
Re: linux-headers-2.6.33-2-amd64 (2.6.33-1~experimental.3) uninstallable
On Sun, 11 Apr 2010, Manoj Srivastava wrote: The kernel team has made their level of commitment clear, as is proper. Indeed, I don't expect the kernel team to support either non-debian sources, nor _any_ third party modules, really. Which is why I directed the user to make-kpkg, which does, to an extent, supports both. which is wrong, you can easily build your oot black magic with linux-kbuild, who is in stable/testing/sid just not in exp. and even there it is trivial and just a matter of svn co and debuild: svn co svn://svn.debian.org/kernel/dists/trunk/linux-kbuild-2.6 debuild over and out. -- 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/20100412050308.ga1...@stro.at
[LCFC] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
This is the last call for comments for the review of debconf
templates for linux-2.6.
The reviewed templates will be sent on Wednesday, April 14, 2010 to the package
maintainer as a bug report and a mail will be sent to this list with
[BTS] as a subject tag.
--
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
_Description: Update disk device IDs in system configuration?
The new Linux kernel version provides different drivers for some
PATA (IDE) controllers. The names of some hard disk, CD-ROM, and
tape devices may change.
.
It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
which will work with both old and new kernel versions.
.
The system configuration can be updated automatically in most cases.
Please choose whether you want this action to be performed.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
#flag:translate!:3,5,7
_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
.
These configuration files will be updated:
.
${files}
.
The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
#flag:translate!:3,5
_Description: Apply configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-manual
Type: error
#flag:translate!:3
_Description: Configuration files still contain deprecated device names
The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
Template: linux-base/disk-id-manual-boot-loader
Type: error
_Description: Boot loader configuration check needed
The boot loader configuration for this system was not recognized. These
settings in the configuration may need to be updated:
.
* The root device ID passed as a kernel parameter;
* The boot device ID used to install and update the boot loader.
.
You should generally identify these devices by UUID or
label. However, on MIPS systems the root device must be identified by
name.
Template: =ST-image-=V/postinst/depmod-error-initrd-=V
Type: boolean
Default: false
_Description: Abort installation after depmod error?
The 'depmod' command exited with the exit code ${exit_value}
(${SIGNAL}${CORE}).
.
Since this image uses initrd, the ${modules_base}/=V/modules.dep file
will not be deleted, even though it may be invalid.
.
You should abort the installation and fix the
errors in depmod, or regenerate the initrd image with a known good
modules.dep file. If you don't abort the installation, there is
a danger that the system will fail to boot.
Template: shared/kernel-image/really-run-bootloader
Type: boolean
Default: true
_Description: Run the default boot loader?
The default boot loader for this architecture is $loader, which is
present.
.
However, there is no explicit request to run that boot loader in
/etc/kernel-img.conf while GRUB seems to be installed with
a postinst hook set.
.
It thus seems that this system is using GRUB as
boot loader instead of $loader.
.
Please choose which should run: the default boot loader now, or the
GRUB update later.
Template: =ST-image-=V/postinst/bootloader-test-error-=V
Type: note
_Description: Error running the boot loader in test mode
An error occurred while running the ${loader} boot loader in test mode.
.
A log is available in ${temp_file_name}. Please edit /etc/${loader}.conf
manually and re-run ${loader} to fix that issue and keep this system
bootable.
Template: =ST-image-=V/postinst/bootloader-error-=V
Type: note
_Description: Error running the boot loader
An error occurred while running the ${loader} boot loader.
.
A log is available in ${temp_file_name}. Please edit /etc/${loader}.conf
manually and re-run ${loader} to fix that issue and keep this system
bootable.
Template: =ST-image-=V/prerm/removing-running-kernel-=V
Type: boolean
Default: true
_Description: Abort kernel removal?
You are running a kernel (version ${running}) and attempting to remove
the same version.
.
This can make the system unbootable as it will remove
/boot/vmlinuz-${running} and all modules under the directory
/lib/modules/${running}. This can only be fixed with a copy of the
kernel image and the corresponding modules.
.
It is highly recommended to abort the kernel removal unless you are
prepared to fix the system after removal.
Template: =ST-image-=V/prerm/would-invalidate-boot-loader-=V
Type: boolean
Default: true
_Description: Abort kernel removal?
This system uses a valid /etc/${loader}.conf file that mentions
${kimage}-=V. Removing =ST-image-=V will invalidate
that file.
.
You will need to edit /etc/${loader}.conf or re-target
symbolic links mentioned there (typically, /vmlinuz
