Dependency missing in linux-image-2.6-686 package
Hello, i have Debian lenny installed on my notebook. I've got error while updating kernel(log is in end of message). As i can see, reason is becouse of missing grub, or grub-pc package in my system, i resolved this simply by installing grub-pc, but i think that it is nessecary to add grub | grub-pc to dependence list at this moment i have: rilium-lenovo:~# LANG=C aptitude show linux-image-2.6-686 .. Depends: linux-image-2.6.26-1-686 . rilium-lenovo:~# LANG=C aptitude show linux-image-2.6.26-1-686 . Depends: module-init-tools, initramfs-tools (= 0.55) | yaird (= 0.0.13) | linux-initramfs-tool .. Failure of updating log: Setting up linux-image-2.6.26-1-686 (2.6.26-8) ... Running depmod. Running mkinitramfs-kpkg Not updating initrd symbolic links since we are being updated/reinstalled (2.6.26-5 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.26-5 was configured last, according to dpkg) Running postinst hook script update-grub. User postinst hook script [update-grub] failed to execute: No such file or directory dpkg: error processing linux-image-2.6.26-1-686 (--configure): subprocess post-installation script returned error exit status 255 Errors were encountered while processing: linux-image-2.6.26-1-686 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.26-1-686 (2.6.26-8) ... Running depmod. Running mkinitramfs-kpkg. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.26-5 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.26-5 was configured last, according to dpkg) Running postinst hook script update-grub. User postinst hook script [update-grub] failed to execute: No such file or directory dpkg: error processing linux-image-2.6.26-1-686 (--configure): subprocess post-installation script returned error exit status 255 Errors were encountered while processing: linux-image-2.6.26-1-686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503172: linux-image-2.6.26-1-orion5x: Improve support for the DNS-323
Package: linux-image-2.6.26-1-orion5x
Severity: normal
Tags: patch
The attached patch improves the kernel's support for the DNS-323 in a few
areas:
* It reads the MAC address for the on-board NIC out of flash, and uses it in
the NIC initialisation (all DNS-323 models); and
* The SATA controller for the rev B1 hardware (also used in the CH3SNAS)
requires PCI to be disabled, and the SATA controller to be initialised
separately.
* The rev B1 hardware also has different MPP mappings.
A functionally-equivalent patch has been prepared for the mainline kernel,
and I'm working on getting that accepted upstream at the moment.
- Matt
--- dns323-setup.c.orig 2008-10-17 21:56:01.0 +1100
+++ dns323-setup.c 2008-10-21 09:25:42.0 +1100
@@ -21,6 +21,7 @@
#include linux/gpio_keys.h
#include linux/input.h
#include linux/i2c.h
+#include linux/ata_platform.h
#include asm/mach-types.h
#include asm/gpio.h
#include asm/mach/arch.h
@@ -67,8 +68,18 @@
static int __init dns323_pci_init(void)
{
- if (machine_is_dns323())
- pci_common_init(dns323_pci);
+ u32 dev, rev;
+
+ orion5x_pcie_id(dev, rev);
+
+ if (machine_is_dns323()) {
+ if (dev != MV88F5182_DEV_ID) {
+ /* The 5182 doesn't really use it's PCI bus, so
+ * we don't initialise it.
+ */
+ pci_common_init(dns323_pci);
+ }
+ }
return 0;
}
@@ -76,15 +87,6 @@
subsys_initcall(dns323_pci_init);
/
- * Ethernet
- */
-
-static struct mv643xx_eth_platform_data dns323_eth_data = {
- .phy_addr = 8,
- .force_phy_addr = 1,
-};
-
-/
* 8MiB NOR flash (Spansion S29GL064M90TFIR4)
*
* Layout as used by D-Link:
@@ -143,6 +145,79 @@
};
/
+ * Ethernet
+ */
+
+static struct mv643xx_eth_platform_data dns323_eth_data = {
+ .phy_addr = 8,
+ .force_phy_addr = 1,
+};
+
+/* parse_hex_*() taken from ts209-setup.c; should a common copy of these
+ * functions be kept somewhere?
+ */
+static int __init parse_hex_nibble(char n)
+{
+ if (n = '0' n = '9')
+ return n - '0';
+
+ if (n = 'A' n = 'F')
+ return n - 'A' + 10;
+
+ if (n = 'a' n = 'f')
+ return n - 'a' + 10;
+
+ return -1;
+}
+
+static int __init parse_hex_byte(const char *b)
+{
+ int hi;
+ int lo;
+
+ hi = parse_hex_nibble(b[0]);
+ lo = parse_hex_nibble(b[1]);
+
+ if (hi 0 || lo 0)
+ return -1;
+
+ return (hi 4) | lo;
+}
+
+static int __init dns323_read_mac_addr(void)
+{
+ u_int8_t addr[6] = { 0x00, 0x00, 0xDE, 0xAD, 0xBE, 0xEF };
+ int i;
+ char *mac_page;
+
+ /* MAC address is stored as a regular ol' string in /dev/mtdblock4
+ * (0x007d-0x0080) starting at offset 196480 (0x2ff80).
+ */
+ mac_page = ioremap(DNS323_NOR_BOOT_BASE + 0x7d + 196480, 1024);
+
+ for (i = 0; i 6; i++) {
+ int byte;
+
+ byte = parse_hex_byte(mac_page + (i * 3));
+ if (byte 0) {
+ iounmap(mac_page);
+ return -1;
+ }
+
+ addr[i] = byte;
+ }
+
+ iounmap(mac_page);
+ printk(DNS323: Found ethernet MAC address: );
+ for (i = 0; i 6; i++)
+ printk(%.2x%s, addr[i], (i 5) ? : : .\n);
+
+ memcpy(dns323_eth_data.mac_addr, addr, 6);
+
+ return 0;
+}
+
+/
* GPIO LEDs (simple - doesn't use hardware blinking support)
*/
@@ -204,6 +279,13 @@
.dev = { .platform_data = dns323_button_data, },
};
+/*
+ * SATA
+ /
+static struct mv_sata_platform_data dns323_sata_data = {
+ .n_ports= 2,
+};
+
/
* General Setup
*/
@@ -247,6 +329,11 @@
static void __init dns323_init(void)
{
+ u32 rev, dev;
+
+ /* Whooo are we? Who who, who who? */
+ orion5x_pcie_id(dev, rev);
+
/* Setup basic Orion functions. Need to be called early. */
orion5x_init();
@@ -262,11 +349,21 @@
orion5x_setup_pcie_wa_win(ORION5X_PCIE_WA_PHYS_BASE,
ORION5X_PCIE_WA_SIZE);
- /* set MPP to 0 as D-Link's 2.6.12.6 kernel did */
- orion5x_write(MPP_0_7_CTRL, 0);
- orion5x_write(MPP_8_15_CTRL, 0);
- orion5x_write(MPP_16_19_CTRL, 0);
- orion5x_write(MPP_DEV_CTRL, 0);
+ if (dev == MV88F5182_DEV_ID) {
+ /* The 5182 has a different MPP map, so we wire it up this way
+ * to let the HDD LEDs do their thing. Values taken directly
+ * from the D-Link kernel.
+ */
+ orion5x_write(MPP_0_7_CTRL, 0x3);
+ orion5x_write(MPP_8_15_CTRL, 0x);
+ orion5x_write(MPP_16_19_CTRL, 0x);
+ } else {
+ /* set MPP to 0 as D-Link's 2.6.12.6 kernel did */
+ orion5x_write(MPP_0_7_CTRL, 0);
+ orion5x_write(MPP_8_15_CTRL, 0);
+ orion5x_write(MPP_16_19_CTRL, 0);
+ orion5x_write(MPP_DEV_CTRL, 0);
+ }
/* Define used GPIO pins
@@ -305,7 +402,15 @@
Bug#503172: linux-image-2.6.26-1-orion5x: Improve support for the DNS-323
* Matthew Palmer [EMAIL PROTECTED] [2008-10-23 18:23]: The attached patch improves the kernel's support for the DNS-323 in a few areas: * It reads the MAC address for the on-board NIC out of flash, and uses it in the NIC initialisation (all DNS-323 models); and I put the MAC patch into 2.6.26-9 already. Can you please make a patch with only the rev B1 changes (again 2.6.26-9)? (Sorry, short on time right now.) -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496858: linux-image-2.6.26-1-686 won't boot on Toshiba
linux-image-2.6.26-1-686 (2.6.26-9) fixed the problem, this bug can be closed. Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503172: linux-image-2.6.26-1-orion5x: Improve support for the DNS-323
On Thu, Oct 23, 2008 at 10:00:23AM +0200, Martin Michlmayr wrote:
* Matthew Palmer [EMAIL PROTECTED] [2008-10-23 18:23]:
The attached patch improves the kernel's support for the DNS-323 in a few
areas:
* It reads the MAC address for the on-board NIC out of flash, and uses it in
the NIC initialisation (all DNS-323 models); and
I put the MAC patch into 2.6.26-9 already. Can you please make a
patch with only the rev B1 changes (again 2.6.26-9)? (Sorry, short on
time right now.)
Sure, I've attached a SATA-only patch. I didn't realise you were so
efficient. grin
- Matt
--- dns323-setup.c.orig 2008-10-23 21:16:57.0 +1100
+++ dns323-setup.c 2008-10-23 21:17:12.0 +1100
@@ -21,6 +21,7 @@
#include linux/gpio_keys.h
#include linux/input.h
#include linux/i2c.h
+#include linux/ata_platform.h
#include asm/mach-types.h
#include asm/gpio.h
#include asm/mach/arch.h
@@ -67,8 +68,18 @@
static int __init dns323_pci_init(void)
{
- if (machine_is_dns323())
- pci_common_init(dns323_pci);
+ u32 dev, rev;
+
+ orion5x_pcie_id(dev, rev);
+
+ if (machine_is_dns323()) {
+ if (dev != MV88F5182_DEV_ID) {
+ /* The 5182 doesn't really use it's PCI bus, so
+ * we don't initialise it.
+ */
+ pci_common_init(dns323_pci);
+ }
+ }
return 0;
}
@@ -204,6 +215,13 @@
.dev = { .platform_data = dns323_button_data, },
};
+/*
+ * SATA
+ /
+static struct mv_sata_platform_data dns323_sata_data = {
+ .n_ports= 2,
+};
+
/
* General Setup
*/
@@ -247,6 +265,11 @@
static void __init dns323_init(void)
{
+ u32 rev, dev;
+
+ /* Whooo are we? Who who, who who? */
+ orion5x_pcie_id(dev, rev);
+
/* Setup basic Orion functions. Need to be called early. */
orion5x_init();
@@ -262,11 +285,21 @@
orion5x_setup_pcie_wa_win(ORION5X_PCIE_WA_PHYS_BASE,
ORION5X_PCIE_WA_SIZE);
- /* set MPP to 0 as D-Link's 2.6.12.6 kernel did */
- orion5x_write(MPP_0_7_CTRL, 0);
- orion5x_write(MPP_8_15_CTRL, 0);
- orion5x_write(MPP_16_19_CTRL, 0);
- orion5x_write(MPP_DEV_CTRL, 0);
+ if (dev == MV88F5182_DEV_ID) {
+ /* The 5182 has a different MPP map, so we wire it up this way
+ * to let the HDD LEDs do their thing. Values taken directly
+ * from the D-Link kernel.
+ */
+ orion5x_write(MPP_0_7_CTRL, 0x3);
+ orion5x_write(MPP_8_15_CTRL, 0x);
+ orion5x_write(MPP_16_19_CTRL, 0x);
+ } else {
+ /* set MPP to 0 as D-Link's 2.6.12.6 kernel did */
+ orion5x_write(MPP_0_7_CTRL, 0);
+ orion5x_write(MPP_8_15_CTRL, 0);
+ orion5x_write(MPP_16_19_CTRL, 0);
+ orion5x_write(MPP_DEV_CTRL, 0);
+ }
/* Define used GPIO pins
@@ -306,6 +339,11 @@
ARRAY_SIZE(dns323_i2c_devices));
orion5x_eth_init(dns323_eth_data);
+ /* The 5182 has it's SATA controller internally, and it needs it's own
+ * little init routine.
+ */
+ if (dev == MV88F5182_DEV_ID)
+ orion5x_sata_init(dns323_sata_data);
}
/* Warning: D-Link uses a wrong mach-type (=526) in their bootloader */
Bug#498691: claims of £1,350.000
E-mail([EMAIL PROTECTED]) for the claims of £1,350.000 pounds in the Irish-Promo claims Requirement: Name, Occupation, Address, Tel: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503172: linux-image-2.6.26-1-orion5x: Improve support for the DNS-323
* Matthew Palmer [EMAIL PROTECTED] [2008-10-23 21:18]: Sure, I've attached a SATA-only patch. I didn't realise you were so efficient. grin One more question before I apply this: do you have to update orion5x_gpio_set_valid_pins as well? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479217: Apparently resolved in 2.6.26
Package: linux-2.6 Followup-For: Bug #479217 I am not certain in which version of 2.6.26 this was first fixed, but can confirm on my Eee PC model 701 that the limited to UDMA/33 due to 40-wire cable message no longer appears and the drive is now configured for UDMA/66 (hdparm -i reports *udma4 and syslog messages indicate UDMA/66) on both 2.6.26-8 and 2.6.26-9, so this bug can be closed. Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502326: Bug confirmed
I can confirm this bug for linux-image-2.6.26-1-686-bigmem (lenny) as well as for 2.6.25.10 (vanilla, iwl4965 module) and 2.6.27.2 (vanilla, iwlagn module) on my Thinkpad T61 (as well as on a T61p). * My current workaround is to switch off wifi using the RF kill switch * Please note that the problem occurred yesterday for the first time. It then kept crashing my machine repeatedly in approx. 30 minutes - until I got to know the workaround. It seems that the issue is related to one of my last system updates because neither my kernel nor the iwl-firmware have been updated recently. The following packages might be involved somehow: Aptitude 0.4.11.10: Protokoll Mo, Okt 20 2008 16:08:09 +0200 === [ENTFERNEN, NICHT VERWENDET] libsmbios1 [ENTFERNEN, NICHT VERWENDET] libsmbiosxml1 [INSTALLIEREN, ABHÄNGIGKEITEN] libsmbios2 [AKTUALISIERUNG] hal 0.5.11-3 - 0.5.11-5 [AKTUALISIERUNG] libapr1 1.2.12-4 - 1.2.12-5 [AKTUALISIERUNG] libaudio-dev 1.9.1-4 - 1.9.1-5 [AKTUALISIERUNG] libaudio2 1.9.1-4 - 1.9.1-5 [AKTUALISIERUNG] libenchant1c2a 1.4.2-3.1 - 1.4.2-3.3 [AKTUALISIERUNG] libhal-storage1 0.5.11-3 - 0.5.11-5 [AKTUALISIERUNG] libhal1 0.5.11-3 - 0.5.11-5 [AKTUALISIERUNG] libpci3 1:3.0.0-4 - 1:3.0.0-6 [AKTUALISIERUNG] libpth20 2.0.7-10 - 2.0.7-12 [AKTUALISIERUNG] libsmbios-bin 0.13.13-1 - 2.0.3.dfsg-1 [AKTUALISIERUNG] net-tools 1.60-20 - 1.60-21 [AKTUALISIERUNG] pciutils 1:3.0.0-4 - 1:3.0.0-6 === Aptitude 0.4.11.10: Protokoll Mi, Okt 22 2008 17:28:54 +0200 === [AKTUALISIERUNG] djvulibre-desktop 3.5.20-8 - 3.5.20-8+lenny0 [AKTUALISIERUNG] emacs22-bin-common 22.2+2-3 - 22.2+2-4 [AKTUALISIERUNG] emacs22-common 22.2+2-3 - 22.2+2-4 [AKTUALISIERUNG] emacs22-gtk 22.2+2-3 - 22.2+2-4 [AKTUALISIERUNG] libdjvulibre21 3.5.20-8 - 3.5.20-8+lenny0 [AKTUALISIERUNG] libdrm2 2.3.1-1 - 2.3.1-2 [AKTUALISIERUNG] libhyphen0 2.4-2 - 2.4-4 [AKTUALISIERUNG] libperl5.10 5.10.0-15 - 5.10.0-16 [AKTUALISIERUNG] libpq5 8.3.4-1 - 8.3.4-2 [AKTUALISIERUNG] perl 5.10.0-15 - 5.10.0-16 [AKTUALISIERUNG] perl-base 5.10.0-15 - 5.10.0-16 [AKTUALISIERUNG] perl-doc 5.10.0-15 - 5.10.0-16 [AKTUALISIERUNG] perl-modules 5.10.0-15 - 5.10.0-16 [AKTUALISIERUNG] perl-suid 5.10.0-15 - 5.10.0-16 [AKTUALISIERUNG] tzdata 2008g-1 - 2008h-2 Cheers, Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502346: please rebuild against virtualbox-ose-source in lenny/sid
On Wed, Oct 22, 2008 at 11:49:25PM +0200, Adam Borowski wrote: Except, the prebuilt module doesn't work for the version of virtualbox in Lenny. Since that is this package's sole purpose, that makes it useless. Please explain. Bastian -- You're dead, Jim. -- McCoy, Amok Time, stardate 3372.7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502346: please rebuild against virtualbox-ose-source in lenny/sid
On Thu, Oct 23, 2008 at 03:17:34PM +0200, Bastian Blank wrote: On Wed, Oct 22, 2008 at 11:49:25PM +0200, Adam Borowski wrote: Except, the prebuilt module doesn't work for the version of virtualbox in Lenny. Since that is this package's sole purpose, that makes it useless. Please explain. It's not a problem between kernel = the module. It's one between the module = virtualbox. The interface between these two has changed. You can use the module just fine if you have an old version of vbox -- just not the one in Lenny (nor the one in Etch). Akin to library transitions, all that is needed is a rebuild. It may be a good idea to add a Conflicts: virtualbox-ose (1.6.6) -- I'm not sure if a normal dependency would be the right thing for a kernel module. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.18.dfsg.1-23_i386.changes INSTALLED into stable
Installing: linux-2.6_2.6.18.dfsg.1-23.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.diff.gz linux-2.6_2.6.18.dfsg.1-23.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.dsc linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-manual-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-23_all.deb linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18.dfsg.1-23_all.deb linux-source-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18.dfsg.1-23_all.deb linux-support-2.6.18-6_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-support-2.6.18-6_2.6.18.dfsg.1-23_all.deb linux-tree-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18.dfsg.1-23_all.deb xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb Override entries for your package: linux-2.6_2.6.18.dfsg.1-23.dsc - source devel linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb
Bug#498309: marked as done (xfs filesystem corruption due to attr2 bug)
Your message dated Thu, 23 Oct 2008 15:28:01 + with message-id [EMAIL PROTECTED] and subject line Bug#498309: fixed in linux-2.6 2.6.18.dfsg.1-23 has caused the Debian Bug report #498309, regarding xfs filesystem corruption due to attr2 bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498309 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Ralf ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-23 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-23.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.diff.gz linux-2.6_2.6.18.dfsg.1-23.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.dsc linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb
Bug#445987: marked as done (linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU)
Your message dated Thu, 23 Oct 2008 15:28:01 + with message-id [EMAIL PROTECTED] and subject line Bug#445987: fixed in linux-2.6 2.6.18.dfsg.1-23 has caused the Debian Bug report #445987, regarding linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 445987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445987 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-xen-amd64 Version: 2.6.18.dfsg.1-13etch4 Severity: normal I have exported (or whatever you call it) all USB ports on my XEN server to one of the domU instances. I've been using an USB connected printer for some time without problems. However, today I plugged in an USB CD writer. And the oops below came out with the writer unusable. And the XEN is 3.0.3 from etch. From dpkg: ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2 The Xen Hypervisor on AMD64 Oct 9 14:23:39 suzy2 kernel: SCSI subsystem initialized Oct 9 14:23:39 suzy2 kernel: Initializing USB Mass Storage driver... Oct 9 14:23:39 suzy2 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Oct 9 14:23:39 suzy2 kernel: usbcore: registered new driver usb-storage Oct 9 14:23:39 suzy2 kernel: USB Mass Storage support registered. Oct 9 14:23:39 suzy2 kernel: usb-storage: device found at 3 Oct 9 14:23:39 suzy2 kernel: usb-storage: waiting for device to settle before scanning Oct 9 14:23:44 suzy2 kernel: Unable to handle kernel NULL pointer dereference at 0078 RIP: Oct 9 14:23:44 suzy2 kernel: [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: PGD 2d33d067 PUD 2ca54067 PMD 0 Oct 9 14:23:44 suzy2 kernel: Oops: [1] SMP Oct 9 14:23:44 suzy2 kernel: CPU 0 Oct 9 14:23:44 suzy2 kernel: Modules linked in: usb_storage scsi_mod ide_core nfsd exportfs ipv6 ppdev parport_pc lp parport nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod evdev pcspkr usblp 8250 serial_core ext3 jbd mbcache ehci_hcd uhci_hcd Oct 9 14:23:44 suzy2 kernel: Pid: 3423, comm: usb-stor-scan Not tainted 2.6.18-4-xen-amd64 #1 Oct 9 14:23:44 suzy2 kernel: RIP: e030:[881e23a2] [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: RSP: e02b:8800214c7ca8 EFLAGS: 00010246 Oct 9 14:23:44 suzy2 kernel: RAX: RBX: 880033cce088 RCX: 0071 Oct 9 14:23:44 suzy2 kernel: RDX: 0067 RSI: 00f0 RDI: 880022ea5800 Oct 9 14:23:44 suzy2 kernel: RBP: 880022ea5800 R08: 880034023000 R09: 0014 Oct 9 14:23:44 suzy2 kernel: R10: 881e38d0 R11: 0048 R12: 880028c2e028 Oct 9 14:23:44 suzy2 kernel: R13: 880022ea5800 R14: R15: 880028c2e000 Oct 9 14:23:44 suzy2 kernel: FS: 2b97072425c0() GS:804c4000() knlGS: Oct 9 14:23:44 suzy2 kernel: CS: e033 DS: ES: Oct 9 14:23:44 suzy2 kernel: Process usb-stor-scan (pid: 3423, threadinfo 8800214c6000, task 88003406a080) Oct 9 14:23:44 suzy2 kernel: Stack: 881e29f2 880022afb800 880022afb800 880028c2e000 Oct 9 14:23:44 suzy2 kernel: 881e4641 880022ea5968 0001881de1fe 880022ea5800 Oct 9 14:23:44 suzy2 kernel: Oct 9 14:23:44 suzy2 kernel: Call Trace: Oct 9 14:23:44 suzy2 kernel: [881e29f2] :scsi_mod:scsi_alloc_queue+0x65/0xb6 Oct 9 14:23:44 suzy2 kernel: [881e4641] :scsi_mod:scsi_alloc_sdev+0x12e/0x1d2 Oct 9 14:23:44 suzy2 kernel: [881e4870] :scsi_mod:scsi_probe_and_add_lun+0x10d/0x9c6 Oct 9 14:23:44 suzy2 kernel: [881e546c] :scsi_mod:scsi_alloc_target+0x21e/0x327 Oct 9 14:23:44 suzy2 kernel: [881e56b8] :scsi_mod:__scsi_scan_target+0xc3/0x5e7 Oct 9 14:23:44 suzy2 kernel: [8026084e] _spin_lock_irq+0x9/0x14 Oct 9 14:23:44 suzy2 kernel: [8025f1a8] wait_for_completion_interruptible_timeout+0x140/0x14e Oct 9 14:23:44 suzy2 kernel: [8027d487] default_wake_function+0x0/0xe Oct 9 14:23:44 suzy2 kernel: [881e5c21] :scsi_mod:scsi_scan_channel+0x45/0x70 Oct 9 14:23:44 suzy2 kernel: [881e5d0c] :scsi_mod:scsi_scan_host_selected+0xc0/0xfb Oct 9 14:23:44 suzy2 kernel: [802901a5] keventd_create_kthread+0x0/0x61 Oct 9 14:23:44 suzy2 kernel: [882074c9] :usb_storage:usb_stor_scan_thread+0x12e/0x156 Oct 9 14:23:44 suzy2 kernel: [80290368] autoremove_wake_function+0x0/0x2e Oct 9 14:23:44 suzy2
Bug#498309: marked as done (xfs filesystem corruption due to attr2 bug)
Your message dated Thu, 23 Oct 2008 15:27:53 + with message-id [EMAIL PROTECTED] and subject line Bug#498309: fixed in fai-kernels 1.17+etch.23 has caused the Debian Bug report #498309, regarding xfs filesystem corruption due to attr2 bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498309 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Ralf ---End Message--- ---BeginMessage--- Source: fai-kernels Source-Version: 1.17+etch.23 We believe that the bug you reported is fixed in the latest version of fai-kernels, which is due to be installed in the Debian FTP archive: fai-kernels_1.17+etch.23.dsc to pool/main/f/fai-kernels/fai-kernels_1.17+etch.23.dsc fai-kernels_1.17+etch.23.tar.gz to pool/main/f/fai-kernels/fai-kernels_1.17+etch.23.tar.gz fai-kernels_1.17+etch.23_i386.deb to pool/main/f/fai-kernels/fai-kernels_1.17+etch.23_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated fai-kernels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 13 Oct 2008 17:52:29 -0600 Source: fai-kernels Binary: fai-kernels Architecture: source i386 Version: 1.17+etch.23 Distribution: stable Urgency: high Maintainer: Holger Levsen [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: fai-kernels - special kernels for FAI (Fully Automatic Installation) Closes: 445987 498309 Changes: fai-kernels (1.17+etch.23) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-23: [ Ian Campbell ] * Fix DMA crash under Xen when no IOMMU is present (closes: #445987) . [ dann frazier ] * [xfs] Fix attr2 corruption with btree data extents (closes: #498309) Files: c0560675eb1281154c3e4663bbb78aa8 725 admin extra fai-kernels_1.17+etch.23.dsc a3a13ca0e0a745d9732637937465 57048 admin extra fai-kernels_1.17+etch.23.tar.gz 93cb3f9580aa9cfc80143d2adcb1fb04 5506466 admin extra fai-kernels_1.17+etch.23_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFI9QMIhuANDBmkLRkRAs8yAJ4t2lt20KcxNyJhFW5C4DnKcjnNfwCghcHr Ul1nCHpY3EZZPCH3JnAK1iA= =V6yq -END PGP SIGNATURE- ---End Message---
Bug#445987: marked as done (linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU)
Your message dated Thu, 23 Oct 2008 15:27:53 + with message-id [EMAIL PROTECTED] and subject line Bug#445987: fixed in fai-kernels 1.17+etch.23 has caused the Debian Bug report #445987, regarding linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 445987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445987 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-xen-amd64 Version: 2.6.18.dfsg.1-13etch4 Severity: normal I have exported (or whatever you call it) all USB ports on my XEN server to one of the domU instances. I've been using an USB connected printer for some time without problems. However, today I plugged in an USB CD writer. And the oops below came out with the writer unusable. And the XEN is 3.0.3 from etch. From dpkg: ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2 The Xen Hypervisor on AMD64 Oct 9 14:23:39 suzy2 kernel: SCSI subsystem initialized Oct 9 14:23:39 suzy2 kernel: Initializing USB Mass Storage driver... Oct 9 14:23:39 suzy2 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Oct 9 14:23:39 suzy2 kernel: usbcore: registered new driver usb-storage Oct 9 14:23:39 suzy2 kernel: USB Mass Storage support registered. Oct 9 14:23:39 suzy2 kernel: usb-storage: device found at 3 Oct 9 14:23:39 suzy2 kernel: usb-storage: waiting for device to settle before scanning Oct 9 14:23:44 suzy2 kernel: Unable to handle kernel NULL pointer dereference at 0078 RIP: Oct 9 14:23:44 suzy2 kernel: [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: PGD 2d33d067 PUD 2ca54067 PMD 0 Oct 9 14:23:44 suzy2 kernel: Oops: [1] SMP Oct 9 14:23:44 suzy2 kernel: CPU 0 Oct 9 14:23:44 suzy2 kernel: Modules linked in: usb_storage scsi_mod ide_core nfsd exportfs ipv6 ppdev parport_pc lp parport nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod evdev pcspkr usblp 8250 serial_core ext3 jbd mbcache ehci_hcd uhci_hcd Oct 9 14:23:44 suzy2 kernel: Pid: 3423, comm: usb-stor-scan Not tainted 2.6.18-4-xen-amd64 #1 Oct 9 14:23:44 suzy2 kernel: RIP: e030:[881e23a2] [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: RSP: e02b:8800214c7ca8 EFLAGS: 00010246 Oct 9 14:23:44 suzy2 kernel: RAX: RBX: 880033cce088 RCX: 0071 Oct 9 14:23:44 suzy2 kernel: RDX: 0067 RSI: 00f0 RDI: 880022ea5800 Oct 9 14:23:44 suzy2 kernel: RBP: 880022ea5800 R08: 880034023000 R09: 0014 Oct 9 14:23:44 suzy2 kernel: R10: 881e38d0 R11: 0048 R12: 880028c2e028 Oct 9 14:23:44 suzy2 kernel: R13: 880022ea5800 R14: R15: 880028c2e000 Oct 9 14:23:44 suzy2 kernel: FS: 2b97072425c0() GS:804c4000() knlGS: Oct 9 14:23:44 suzy2 kernel: CS: e033 DS: ES: Oct 9 14:23:44 suzy2 kernel: Process usb-stor-scan (pid: 3423, threadinfo 8800214c6000, task 88003406a080) Oct 9 14:23:44 suzy2 kernel: Stack: 881e29f2 880022afb800 880022afb800 880028c2e000 Oct 9 14:23:44 suzy2 kernel: 881e4641 880022ea5968 0001881de1fe 880022ea5800 Oct 9 14:23:44 suzy2 kernel: Oct 9 14:23:44 suzy2 kernel: Call Trace: Oct 9 14:23:44 suzy2 kernel: [881e29f2] :scsi_mod:scsi_alloc_queue+0x65/0xb6 Oct 9 14:23:44 suzy2 kernel: [881e4641] :scsi_mod:scsi_alloc_sdev+0x12e/0x1d2 Oct 9 14:23:44 suzy2 kernel: [881e4870] :scsi_mod:scsi_probe_and_add_lun+0x10d/0x9c6 Oct 9 14:23:44 suzy2 kernel: [881e546c] :scsi_mod:scsi_alloc_target+0x21e/0x327 Oct 9 14:23:44 suzy2 kernel: [881e56b8] :scsi_mod:__scsi_scan_target+0xc3/0x5e7 Oct 9 14:23:44 suzy2 kernel: [8026084e] _spin_lock_irq+0x9/0x14 Oct 9 14:23:44 suzy2 kernel: [8025f1a8] wait_for_completion_interruptible_timeout+0x140/0x14e Oct 9 14:23:44 suzy2 kernel: [8027d487] default_wake_function+0x0/0xe Oct 9 14:23:44 suzy2 kernel: [881e5c21] :scsi_mod:scsi_scan_channel+0x45/0x70 Oct 9 14:23:44 suzy2 kernel: [881e5d0c] :scsi_mod:scsi_scan_host_selected+0xc0/0xfb Oct 9 14:23:44 suzy2 kernel: [802901a5] keventd_create_kthread+0x0/0x61 Oct 9 14:23:44 suzy2 kernel: [882074c9] :usb_storage:usb_stor_scan_thread+0x12e/0x156 Oct 9 14:23:44 suzy2 kernel: [80290368] autoremove_wake_function+0x0/0x2e Oct 9 14:23:44 suzy2
linux-2.6.24_2.6.24-6~etchnhalf.6_i386.changes INSTALLED into stable
Installing: linux-2.6.24_2.6.24-6~etchnhalf.6.diff.gz to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.6.diff.gz linux-2.6.24_2.6.24-6~etchnhalf.6.dsc to pool/main/l/linux-2.6.24/linux-2.6.24_2.6.24-6~etchnhalf.6.dsc linux-doc-2.6.24_2.6.24-6~etchnhalf.6_all.deb to pool/main/l/linux-2.6.24/linux-doc-2.6.24_2.6.24-6~etchnhalf.6_all.deb linux-headers-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.6_i386.deb linux-headers-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.6_i386.deb linux-headers-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.6_i386.deb linux-headers-2.6.24-etchnhalf.1-all-i386_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all-i386_2.6.24-6~etchnhalf.6_i386.deb linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.6_i386.deb linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.6_i386.deb linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.6_i386.deb linux-image-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.6_i386.deb linux-image-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.6_i386.deb linux-image-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.6_i386.deb linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.6_i386.deb to pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.6_i386.deb linux-manual-2.6.24_2.6.24-6~etchnhalf.6_all.deb to pool/main/l/linux-2.6.24/linux-manual-2.6.24_2.6.24-6~etchnhalf.6_all.deb linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.6_all.deb to pool/main/l/linux-2.6.24/linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.6_all.deb linux-source-2.6.24_2.6.24-6~etchnhalf.6_all.deb to pool/main/l/linux-2.6.24/linux-source-2.6.24_2.6.24-6~etchnhalf.6_all.deb linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.6_all.deb to pool/main/l/linux-2.6.24/linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.6_all.deb linux-tree-2.6.24_2.6.24-6~etchnhalf.6_all.deb to pool/main/l/linux-2.6.24/linux-tree-2.6.24_2.6.24-6~etchnhalf.6_all.deb Override entries for your package: linux-2.6.24_2.6.24-6~etchnhalf.6.dsc - source devel linux-doc-2.6.24_2.6.24-6~etchnhalf.6_all.deb - optional doc linux-headers-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-headers-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-headers-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-headers-2.6.24-etchnhalf.1-all-i386_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.6_i386.deb - optional devel linux-image-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.6_i386.deb - optional admin linux-image-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.6_i386.deb - optional admin linux-image-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.6_i386.deb - optional admin linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.6_i386.deb - optional admin linux-manual-2.6.24_2.6.24-6~etchnhalf.6_all.deb - optional doc linux-patch-debian-2.6.24_2.6.24-6~etchnhalf.6_all.deb - optional devel linux-source-2.6.24_2.6.24-6~etchnhalf.6_all.deb - optional devel linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.6_all.deb - optional devel linux-tree-2.6.24_2.6.24-6~etchnhalf.6_all.deb - optional devel Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498309: marked as done (xfs filesystem corruption due to attr2 bug)
Your message dated Thu, 23 Oct 2008 15:28:18 + with message-id [EMAIL PROTECTED] and subject line Bug#498309: fixed in user-mode-linux 2.6.18-1um-2etch.23 has caused the Debian Bug report #498309, regarding xfs filesystem corruption due to attr2 bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498309 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Ralf ---End Message--- ---BeginMessage--- Source: user-mode-linux Source-Version: 2.6.18-1um-2etch.23 We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive: user-mode-linux_2.6.18-1um-2etch.23.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.23.diff.gz user-mode-linux_2.6.18-1um-2etch.23.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.23.dsc user-mode-linux_2.6.18-1um-2etch.23_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.23_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 13 Oct 2008 17:47:53 -0600 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.18-1um-2etch.23 Distribution: stable Urgency: high Maintainer: User Mode Linux Maintainers [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: user-mode-linux - User-mode Linux (kernel) Closes: 445987 498309 Changes: user-mode-linux (2.6.18-1um-2etch.23) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-23: [ Ian Campbell ] * Fix DMA crash under Xen when no IOMMU is present (closes: #445987) . [ dann frazier ] * [xfs] Fix attr2 corruption with btree data extents (closes: #498309) Files: 4fa86f3f3b7ef615787582605c693537 877 misc extra user-mode-linux_2.6.18-1um-2etch.23.dsc 5d833925bf8183f9ed081b6acba4a033 18628 misc extra user-mode-linux_2.6.18-1um-2etch.23.diff.gz fe002e862a48d4b1a66130b104cacf1c 25589992 misc extra user-mode-linux_2.6.18-1um-2etch.23_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFI9QMlhuANDBmkLRkRAv0HAKCR6/fMO384djKX/9AMVLrasWeR7QCfeinI 5rh/Y+4uMsRUxgwmfksvdos= =WqaV -END PGP SIGNATURE- ---End Message---
Bug#445987: marked as done (linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU)
Your message dated Thu, 23 Oct 2008 15:28:18 + with message-id [EMAIL PROTECTED] and subject line Bug#445987: fixed in user-mode-linux 2.6.18-1um-2etch.23 has caused the Debian Bug report #445987, regarding linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 445987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445987 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-xen-amd64 Version: 2.6.18.dfsg.1-13etch4 Severity: normal I have exported (or whatever you call it) all USB ports on my XEN server to one of the domU instances. I've been using an USB connected printer for some time without problems. However, today I plugged in an USB CD writer. And the oops below came out with the writer unusable. And the XEN is 3.0.3 from etch. From dpkg: ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2 The Xen Hypervisor on AMD64 Oct 9 14:23:39 suzy2 kernel: SCSI subsystem initialized Oct 9 14:23:39 suzy2 kernel: Initializing USB Mass Storage driver... Oct 9 14:23:39 suzy2 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Oct 9 14:23:39 suzy2 kernel: usbcore: registered new driver usb-storage Oct 9 14:23:39 suzy2 kernel: USB Mass Storage support registered. Oct 9 14:23:39 suzy2 kernel: usb-storage: device found at 3 Oct 9 14:23:39 suzy2 kernel: usb-storage: waiting for device to settle before scanning Oct 9 14:23:44 suzy2 kernel: Unable to handle kernel NULL pointer dereference at 0078 RIP: Oct 9 14:23:44 suzy2 kernel: [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: PGD 2d33d067 PUD 2ca54067 PMD 0 Oct 9 14:23:44 suzy2 kernel: Oops: [1] SMP Oct 9 14:23:44 suzy2 kernel: CPU 0 Oct 9 14:23:44 suzy2 kernel: Modules linked in: usb_storage scsi_mod ide_core nfsd exportfs ipv6 ppdev parport_pc lp parport nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod evdev pcspkr usblp 8250 serial_core ext3 jbd mbcache ehci_hcd uhci_hcd Oct 9 14:23:44 suzy2 kernel: Pid: 3423, comm: usb-stor-scan Not tainted 2.6.18-4-xen-amd64 #1 Oct 9 14:23:44 suzy2 kernel: RIP: e030:[881e23a2] [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: RSP: e02b:8800214c7ca8 EFLAGS: 00010246 Oct 9 14:23:44 suzy2 kernel: RAX: RBX: 880033cce088 RCX: 0071 Oct 9 14:23:44 suzy2 kernel: RDX: 0067 RSI: 00f0 RDI: 880022ea5800 Oct 9 14:23:44 suzy2 kernel: RBP: 880022ea5800 R08: 880034023000 R09: 0014 Oct 9 14:23:44 suzy2 kernel: R10: 881e38d0 R11: 0048 R12: 880028c2e028 Oct 9 14:23:44 suzy2 kernel: R13: 880022ea5800 R14: R15: 880028c2e000 Oct 9 14:23:44 suzy2 kernel: FS: 2b97072425c0() GS:804c4000() knlGS: Oct 9 14:23:44 suzy2 kernel: CS: e033 DS: ES: Oct 9 14:23:44 suzy2 kernel: Process usb-stor-scan (pid: 3423, threadinfo 8800214c6000, task 88003406a080) Oct 9 14:23:44 suzy2 kernel: Stack: 881e29f2 880022afb800 880022afb800 880028c2e000 Oct 9 14:23:44 suzy2 kernel: 881e4641 880022ea5968 0001881de1fe 880022ea5800 Oct 9 14:23:44 suzy2 kernel: Oct 9 14:23:44 suzy2 kernel: Call Trace: Oct 9 14:23:44 suzy2 kernel: [881e29f2] :scsi_mod:scsi_alloc_queue+0x65/0xb6 Oct 9 14:23:44 suzy2 kernel: [881e4641] :scsi_mod:scsi_alloc_sdev+0x12e/0x1d2 Oct 9 14:23:44 suzy2 kernel: [881e4870] :scsi_mod:scsi_probe_and_add_lun+0x10d/0x9c6 Oct 9 14:23:44 suzy2 kernel: [881e546c] :scsi_mod:scsi_alloc_target+0x21e/0x327 Oct 9 14:23:44 suzy2 kernel: [881e56b8] :scsi_mod:__scsi_scan_target+0xc3/0x5e7 Oct 9 14:23:44 suzy2 kernel: [8026084e] _spin_lock_irq+0x9/0x14 Oct 9 14:23:44 suzy2 kernel: [8025f1a8] wait_for_completion_interruptible_timeout+0x140/0x14e Oct 9 14:23:44 suzy2 kernel: [8027d487] default_wake_function+0x0/0xe Oct 9 14:23:44 suzy2 kernel: [881e5c21] :scsi_mod:scsi_scan_channel+0x45/0x70 Oct 9 14:23:44 suzy2 kernel: [881e5d0c] :scsi_mod:scsi_scan_host_selected+0xc0/0xfb Oct 9 14:23:44 suzy2 kernel: [802901a5] keventd_create_kthread+0x0/0x61 Oct 9 14:23:44 suzy2 kernel: [882074c9] :usb_storage:usb_stor_scan_thread+0x12e/0x156 Oct 9 14:23:44 suzy2 kernel: [80290368] autoremove_wake_function+0x0/0x2e Oct 9 14:23:44
Bug#494308: e100 firmware testing
On Thu, Oct 23, 2008 at 12:47:09AM +0100, Ben Hutchings wrote: On Wed, 2008-10-22 at 17:05 -0600, dann frazier wrote: hey Ben, I got around to testing a build from the source you reference in your blog[1] today - but it appears that the e100 patch in place simply removes the firmware and marks the driver broken. I see in #494308 that there were a couple of different approaches being considered for e100, so perhaps e100 is still a work in progress. My changes to e100 in linux-2.6 are actually divided across 3 files under debian/patches, following what has been done for several other instances of sourceless firmware: 1. debian/dfsg/e100-disable.patch inserts #ifdef REMOVE_DFSG...#endif around the microcode and marks the driver as BROKEN in Kconfig. 2. debian/dfsg/files-1 uses unifdef to remove the microcode. 3. features/all/e100-request_firmware.patch removes the BROKEN mark and adds firmware loading using request_firmware. Each of the 11 other drivers is dealt with similarly, except that for most of them we can use rm instead of unifdef. The orig tarball has steps 1 and 2 already applied and step 3 is part of the normal build process. Ah - I somehow missed the step3 patch. Also, it turns out my controller (8086:1229) isn't one of the devices that gets fw loaded. The driver still works fine though, fwiw. If you decide to move forward w/ a request_firmware() approach, you might want to take note that the e100 driver will be included in the initramfs by default. This means that the firmware should be included in the initramfs as well. You should be able to enable an initramfs hook in the firmware-nonfree source package - see bnx2/defines for an example. I know this works for fw blobs that live in /lib/firmware, but I don't know how well it would deal with files in other subdirectories (e.g. /lib/firmware/e100/). Right, I hadn't got that far yet. Ben. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503216: initramfs-tools: Network drivers missing from netboot and most sets
Package: initramfs-tools Version: 0.92l Severity: important I noticed that the sfc driver is not included in an initramfs by default. On further investigation I found that neither are cxgb, ixgb, ixgbe, s2io, netxen_nic, mlx4_core or tehuti. Also the typhoon driver is not included due to a typo (typhon). Maybe auto_add_modules() should handle the net class by including everything under kernel/drivers/net with specific exclusions (wan, wireless, irda, hamradio, ...)? Ben. -- Package-specific info: -- /proc/cmdline root=LABEL=sid-root ro -- /proc/filesystems ext3 -- lsmod Module Size Used by binfmt_misc 7528 1 ppdev 6468 0 parport_pc 22500 0 lp 8164 0 parport30988 3 ppdev,parport_pc,lp ipv6 235300 12 video 16400 0 output 2912 1 video ac 4196 0 battery10180 0 dm_snapshot14340 0 dm_mirror 15104 0 dm_log 8452 1 dm_mirror dm_mod 46184 3 dm_snapshot,dm_mirror,dm_log loop 12748 0 sd_mod 22200 0 arc41824 2 ecb 2624 2 crypto_blkcipher 15236 1 ecb pcspkr 2432 0 rt2500pci 17152 0 rt2x00pci 7648 1 rt2500pci rt2x00lib 22592 2 rt2500pci,rt2x00pci firmware_class 6816 1 rt2x00lib rfkill 5652 1 rt2x00lib led_class 3908 1 rt2x00lib button 6064 0 snd_intel8x0 26268 3 input_polldev 3752 1 rt2x00lib mac80211 139680 2 rt2x00pci,rt2x00lib snd_ac97_codec 88484 1 snd_intel8x0 cfg80211 21576 2 rt2x00lib,mac80211 ac97_bus1728 1 snd_ac97_codec snd_pcm62628 3 snd_intel8x0,snd_ac97_codec snd_seq41456 0 snd_timer 17800 3 snd_pcm,snd_seq snd_seq_device 6380 1 snd_seq eeprom_93cx62144 1 rt2500pci snd45604 10 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_seq,snd_timer,snd_seq_device soundcore 6368 1 snd snd_page_alloc 7816 2 snd_intel8x0,snd_pcm sis_agp 6752 1 i2c_sis96x 4132 0 i2c_sis630 5644 0 agpgart28776 1 sis_agp shpchp 25528 0 pci_hotplug23460 1 shpchp i2c_core 19828 2 i2c_sis96x,i2c_sis630 evdev 8000 3 ext3 105256 2 jbd39444 1 ext3 mbcache 7108 1 ext3 ide_cd_mod 27652 0 cdrom 30176 1 ide_cd_mod ide_disk 10496 4 ide_pci_generic 3908 0 [permanent] usbhid 35904 0 hid33184 1 usbhid ff_memless 4392 1 usbhid usb_storage75936 0 floppy 47716 0 sis5513 6788 0 [permanent] ide_core 96168 4 ide_cd_mod,ide_disk,ide_pci_generic,sis5513 ata_generic 4676 0 via_rhine 18664 0 mii 4896 1 via_rhine libata140416 1 ata_generic scsi_mod 129356 3 sd_mod,usb_storage,libata dock8272 1 libata ohci_hcd 18500 0 usbcore 118160 4 usbhid,usb_storage,ohci_hcd thermal15228 0 processor 32576 1 thermal fan 4164 0 thermal_sys10856 4 video,thermal,processor,fan -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9-14 GNU cpio -- a program to manage ar ii findutils 4.4.0-2utilities for finding files--find, ii klibc-utils 1.5.12-2 small utilities built with klibc f ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii udev 0.125-7/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- no debconf information -- To
Bug#502668: WhiteHEAT driver and firmware distribution for Linux
David Worthen wrote: Thanks for the info Ben. Can you re-send the original message? I didn't save the recommended texts of the licenses. The message is available here: http://lists.debian.org/debian-kernel/2008/10/msg00447.html Best regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 [EMAIL PROTECTED] GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503172: linux-image-2.6.26-1-orion5x: Improve support for the DNS-323
On Thu, Oct 23, 2008 at 01:03:08PM +0200, Martin Michlmayr wrote: * Matthew Palmer [EMAIL PROTECTED] [2008-10-23 21:18]: Sure, I've attached a SATA-only patch. I didn't realise you were so efficient. grin One more question before I apply this: do you have to update orion5x_gpio_set_valid_pins as well? I didn't change the GPIO pin map, so I don't think that I need to change the valid_pins. However, I'm not sure that the GPIO map is *necessarily* the same for the A1 and B1, so it's possible that it'll need to be updated. I know that there are more changes that need to be made to *fully* support the DNS-323 (i2c, fan, possibly LEDs); this patch is really targetted at just getting the kernel to the point where it'll run d-i and the system. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Firmware removal
On Fri, Oct 17, 2008 at 12:34:38AM +0100, Ben Hutchings wrote: I'm going to post a series of patches that aim to fix the RC bugs relating to sourceless firmware. Thanks for the work on that, but can you please send all of them to David Woodhouse and let him push them through the firmware tree? This is a patch against SVN which adds source for dsp56k's firmware and modifies the other drivers to use request_firmware, and removes the other firmware from the original tarball. As already declared to the release team, I don't consider any of them for Lenny unless forced/asked by the responsible entities (TC, ftp, release or GR with 2:1 majority). This is a decision under §3.1.1 of the constitution. Bastian -- Is truth not truth for all? -- Natira, For the World is Hollow and I have Touched the Sky, stardate 5476.4. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
