Bug#464197: Any update on this issue?
Ben Hutchings writes: > - Remove "Modified on..." lines; that's what the commit message is for Those were the prominent notices mentioned in GPLv2 2. a). pgpGEfIUch6fL.pgp Description: PGP signature
Bug#525220:
2009/5/3 Dominique Meeùs > Maximi89 a écrit ce qui suit, le 03/05/09 21:47 : > >> maxim...@maximiliano:~$ sudo dpkg -l | grep bluez : ii bluez >> 4.35-0ubuntu1 >> > I wrote this on one line to keep the message shorter. After : ii etc. is > the result. You have to understand it as > sudo dpkg -l | grep bluez > iibluez4.35-0ubuntu1 > >> maxim...@maximiliano:~$ sudo /etc/init.d/bluetooth stop >> Stopping bluetooth: hcid. ... > > >> maxim...@maximiliano:~$ sudo hciconfig -a >> hci0: Type: USBBD Address: 00:11:67:CB:5D:87 ACL MTU: 1021:4 SCO MTU: >> 48:10 >> UP RUNNING PSCAN ISCANRX bytes:1226 acl:0 sco:0 events:26 errors:0 >> TX bytes:347 acl:0 sco:0 commands:27 errors:0Features: 0xff 0xfe 0xff >> 0x7e 0x98 0x19 0x00 0x80Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 >>Link policy: RSWITCH HOLD SNIFF PARKLink mode: SLAVE ACCEPTName: >> 'Maximiliano-0'Class: 0x080104Service Classes: CapturingDevice >> Class: Computer, Desktop workstationHCI Ver: 2.0 (0x3) HCI Rev: 0x302 >> LMP Ver: 2.0 (0x3) LMP Subver: 0x302 >> Manufacturer: Integrated System Solution Corp. (57) >> > In your case too, there is no more "hci0 command tx timeout" with bluetooth > stopped. in my case i have a lot if i try to transfers files with bluetooth-applet [ 2034.124020] eth0: no IPv6 routers present [ 2629.953632] usb 2-2: USB disconnect, address 2 [ 2629.954009] btusb_bulk_complete: hci0 urb f481b5c0 failed to resubmit (19) [ 2629.954020] btusb_intr_complete: hci0 urb ef8567c0 failed to resubmit (19) [ 2629.955005] btusb_bulk_complete: hci0 urb f481b640 failed to resubmit (19) [ 2629.955471] btusb_send_frame: hci0 urb f481b6c0 submission failed [ 2629.987752] __set_isoc_interface: hci0 setting interface failed (19) [ 2633.580049] usb 2-2: new full speed USB device using ohci_hcd and address 4 [ 2633.804786] usb 2-2: New USB device found, idVendor=1131, idProduct=1004 [ 2633.804794] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2633.804799] usb 2-2: Product: ISSCEDRBTA [ 2633.804802] usb 2-2: Manufacturer: ISSC [ 2633.804929] usb 2-2: configuration #1 chosen from 1 choice [ 2634.457317] usb 2-2: USB disconnect, address 4 [ 2634.457727] btusb_bulk_complete: hci0 urb f481b5c0 failed to resubmit (19) [ 2634.457739] btusb_intr_complete: hci0 urb ef91f8c0 failed to resubmit (19) [ 2634.458726] btusb_bulk_complete: hci0 urb f4c6cec0 failed to resubmit (19) [ 2634.461581] btusb_send_frame: hci0 urb f4c6cf40 submission failed [ 2634.461597] __set_isoc_interface: hci0 setting interface failed (19) [ 2640.348039] usb 2-2: new full speed USB device using ohci_hcd and address 5 [ 2640.568353] usb 2-2: New USB device found, idVendor=1131, idProduct=1004 [ 2640.568361] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2640.568366] usb 2-2: Product: ISSCEDRBTA [ 2640.568370] usb 2-2: Manufacturer: ISSC [ 2640.568500] usb 2-2: configuration #1 chosen from 1 choice [ 2918.198211] usb 2-2: USB disconnect, address 5 [ 2920.896041] usb 2-2: new full speed USB device using ohci_hcd and address 6 [ 2921.124852] usb 2-2: New USB device found, idVendor=1131, idProduct=1004 [ 2921.124860] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2921.124865] usb 2-2: Product: ISSCEDRBTA [ 2921.124869] usb 2-2: Manufacturer: ISSC [ 2921.124998] usb 2-2: configuration #1 chosen from 1 choice [ 2994.696241] hci_cmd_task: hci0 command tx timeout [ 3049.227800] hci_cmd_task: hci0 command tx timeout [ 3817.808874] hci_cmd_task: hci0 command tx timeout [ 3855.659734] hci_cmd_task: hci0 command tx timeout Linux Maximiliano 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686 GNU/Linux today i get the phone to say "connect with Maximiliano-0" but only some times... later nothing, but when i press "yes" nothing happens, i try with kernel 2.6.26-1 and works great, with a newer kernel we think this works better than, but this don't happen. with the old kernel i can send and receive files, with newer one i can't. > > > This should be an important information to debug this problem. I am not > able to do it myself, so the next step should be to convince some developer > to take the problem seriously > > -- Maximiliano Augusto Castañón Araneda Santiago, Chile Linux user # 394821
Processed: tagging 524230
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 524230 + pending Bug#524230: include ivtv firmware in firmware-nonfree Tags were: patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: setting package to firmware-ipw2x00 firmware-bnx2 firmware-nonfree firmware-ivtv firmware-iwlwifi firmware-ralink firmware-qlogic firmware-linux ...
Processing commands for cont...@bugs.debian.org: > #firmware-nonfree (0.17) UNRELEASED; urgency=low > # > # * Add firmware for use with ivtv and pvrusb2 drivers (closes: #524230), > #thanks to Ian Campbell . > # > package firmware-ipw2x00 firmware-bnx2 firmware-nonfree firmware-ivtv > firmware-iwlwifi firmware-ralink firmware-qlogic firmware-linux Ignoring bugs not assigned to: firmware-ipw2x00 firmware-nonfree firmware-iwlwifi firmware-ralink firmware-linux firmware-bnx2 firmware-ivtv firmware-qlogic > tags 524230 + pending Bug#524230: include ivtv firmware in firmware-nonfree Tags were: pending patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526805: marked as done (firmware-iwlwifi: wlan0 needs extra poke to come up)
Your message dated Mon, 04 May 2009 01:12:53 +0100 with message-id <1241395973.11921.40.ca...@deadeye> and subject line Re: Bug#526805: firmware-iwlwifi: wlan0 needs extra poke to come up has caused the Debian Bug report #526805, regarding firmware-iwlwifi: wlan0 needs extra poke to come up 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 ow...@bugs.debian.org immediately.) -- 526805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-iwlwifi Version: 0.16 Severity: normal My /etc/network/interfaces has, iface wlan0 inet dhcp wireless_mode Managed wireless_essid "mtbc at home" I'm doing these tests without encryption, to make it simpler. If I do an ifup wlan0 then it says, ADDRCONF(NETDEV_UP): wlan0: link is not ready and the DHCP goes ahead and doesn't get any response. If I wait a moment after the ifup (three seconds is normally enough) and then in another shell set an iwconfig option, e.g., iwconfig wlan0 essid "mtbc at home", then I get a, ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready and then the next DHCP request gets an answer. This has been true for me ever since I first switched to iwl3945 from ipw3945 a few versions and many months ago. (Also, I tried installing Debian 5.0 from a netinst CD on an identical machine and after I fed it the firmware the installer couldn't get a DHCP address over wifi so I had to do the first parts by using wired ethernet to a wireless access point working as a transparent bridge instead - that worked fine.) I have no idea if it's relevant, but I mention just in case: during boot the kernel log mentions, pci :0a:08.0: Firmware left e100 interrupts enabled; disabling and, ACPI: EC: missing confirmations, switch off interrupt mode. (I wondered if some sort of interrupt is generated when the card associates with an AP.) Mark -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (600, 'stable'), (50, 'unstable'), (40, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: pn initramfs-tools(no description available) pn linux-image(no description available) -- no debconf information --- End Message --- --- Begin Message --- On Sun, 2009-05-03 at 19:37 -0400, Mark T.B. Carroll wrote: > Ben Hutchings writes: > > >> wireless_essid "mtbc at home" > > > What does "iwconfig wlan0" say in this case? > > Argh. I'm an idiot. [...] I wouldn't say that - I'd certainly have expected quotes to be needed. This is documented though you have to look around a bit. Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#526805: firmware-iwlwifi: wlan0 needs extra poke to come up
Ben Hutchings writes: >> wireless_essid "mtbc at home" > What does "iwconfig wlan0" say in this case? Argh. I'm an idiot. The above from /etc/network/interfaces /should/ have been: wireless_essid mtbc at home That works fine. I've not looked hard into this issue since a few versions of things back, so if there ever was a real problem, it was probably fixed and I didn't notice because of that other mistake. I don't know why I used to have the " - maybe by analogy with wpa-supplicant.conf - but it sure isn't good now. (It doesn't explain why the Debian installer couldn't pick up DHCP over wifi but now I have Linux installed on that machine it's not an issue for me. Still, if anybody wants my help in looking into it, they should feel free to ask.) Mark -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#464197: Any update on this issue?
On Mon, 2009-05-04 at 01:35 +0200, Antonio Ospite wrote:
> On Mon, 04 May 2009 00:17:03 +0100
> Ben Hutchings wrote:
>
> > On Mon, 2009-04-20 at 21:45 -0600, dann frazier wrote:
> > >
> > > Kalle: would you mind submitting your patch upstream, if you haven't
> > > already? A lot of similar patches for other drives have been accepted
> > > in recent months.
> >
> > Kalle's patch has a serious problem in that it attempts to byte-swap the
> > firmware in place. On a big-endian system where the firmware is built
> > into the kernel, or if a cache is implemented, this will corrupt the
> > image or cause an oops.
> >
>
> I saw also that some drivers provide blobs as ihex files, a textual
> representation of the binary data, and convert it to a binary image at
> build time. Could this be useful in this case?
In the upstream repository, all firmware extracted from drivers is
stored in some variant of Intel hex format. But this is still
byte-oriented and does not help to avoid byte-swapping.
> > Furthermore, I think any patch sent upstream will need to handle the
> > "new" DSP code as well.
> >
>
> Indeed.
>
> > Anyway, here's my proposed patch for unstable (against 2.6.30-rc4) that
> > deals with the first problem. I'll have a go at handling the "new" DSP
> > code as well, but as I don't have the hardware for this driver this will
> > need testing by others.
> >
>
> I will test this patch soon; wrt the NEW DSP feature, I don't know if I
> can test everything, because I have a Thinkpad T20, only stereo output.
>
> BTW, what binary image to use? Is the one extracted with the tool in
> this thread, to be run on a little-endian host, ok?
You would need to apply this patch to cs46xx_image.h before running that
program:
--- a/sound/pci/cs46xx/cs46xx_image.h
+++ b/sound/pci/cs46xx/cs46xx_image.h
@@ -1,14 +1,13 @@
struct BA1struct {
struct {
- unsigned long offset;
- unsigned long size;
+ u32 size;
} memory[BA1_MEMORY_COUNT];
u32 map[BA1_DWORD_SIZE];
};
static struct BA1struct BA1Struct = {
-{{ 0x, 0x3000 },{ 0x0001, 0x3800 },{ 0x0002,
0x7000 }},
+{{ 0x3000 },{ 0x3800 },{ 0x7000 }},
{0x,0x,0x,0x,
0x,0x,0x,0x,
0x,0x,0x0163,0x,
--- END ---
Also note the change of filename (partly because of the format change).
Ben.
--
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot
signature.asc
Description: This is a digitally signed message part
Processed: Bug#525958: Disable CONFIG_PROM_CONSOLE on sparc - also affects Lenny!
Processing commands for cont...@bugs.debian.org: > found 525958 2.6.26-15 Bug#525958: Disable CONFIG_PROM_CONSOLE on sparc Bug marked as found in version 2.6.26-15. > 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
Bug#525958: Disable CONFIG_PROM_CONSOLE on sparc - also affects Lenny!
found 525958 2.6.26-15 thanks If I understand David Miller correctly, this also affects stable kernels. Here's a message I received from him for #504721 against D-I's rootskel (which was rejected because that bug's already been archived). I'm not sure if changing this is appropriate for stable, but I guess if anyone is an authority on correct Sparc kernel configuration, then David is. Cheers, FJP Forwarded message === From: David Miller To: 504...@bugs.debian.org Date: 03/05/09 23:32 The reason this bug happens is because CONFIG_PROM_CONSOLE is enabled in the kernel. It unconditionally gets registered as a real console before the Sun Hypervisor console driver has a chance to register. The kernel takes whatever real console registers first, as the highest priority console (unless specified otherwise on the command line). This is why the test program that runs to determine the inittab getty settings doesn't see the console as a "serial" device. And no, using console=ttyS0 will not fix this problem on Niagara. On Niagara you would need to use console=ttyHV0. The only reasonable fix for this bug is to disable CONFIG_PROM_CONSOLE in the kernel configuration. Nobody should be enabling that kernel config option on sparc. It specifically creates this problem because unlike the framebuffer and serial console drivers, it does not have a way to know whether it should register or not. The serial and framebuffer drivers check the PROM indicated device node of the console device, and it only registers the device as the console if it matches the value of the 'output-device' PROM environment variable setting. Therefore, having CONFIG_PROM_CONSOLE enabled in the tree is going to do nothing other than constantly create problems and conflicts like this. It needs to be turned off, forever. == -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#464197: Any update on this issue?
On Mon, 04 May 2009 00:17:03 +0100 Ben Hutchings wrote: > On Mon, 2009-04-20 at 21:45 -0600, dann frazier wrote: > > > > Kalle: would you mind submitting your patch upstream, if you haven't > > already? A lot of similar patches for other drives have been accepted > > in recent months. > > Kalle's patch has a serious problem in that it attempts to byte-swap the > firmware in place. On a big-endian system where the firmware is built > into the kernel, or if a cache is implemented, this will corrupt the > image or cause an oops. > I saw also that some drivers provide blobs as ihex files, a textual representation of the binary data, and convert it to a binary image at build time. Could this be useful in this case? > Furthermore, I think any patch sent upstream will need to handle the > "new" DSP code as well. > Indeed. > Anyway, here's my proposed patch for unstable (against 2.6.30-rc4) that > deals with the first problem. I'll have a go at handling the "new" DSP > code as well, but as I don't have the hardware for this driver this will > need testing by others. > I will test this patch soon; wrt the NEW DSP feature, I don't know if I can test everything, because I have a Thinkpad T20, only stereo output. BTW, what binary image to use? Is the one extracted with the tool in this thread, to be run on a little-endian host, ok? Thanks, Antonio -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Web site: http://www.studenti.unina.it/~ospite Public key: http://www.studenti.unina.it/~ospite/aopubkey.asc pgpwpoFxu8tZV.pgp Description: PGP signature
Bug#464197: Any update on this issue?
On Mon, 2009-04-20 at 21:45 -0600, dann frazier wrote:
> On Wed, Apr 15, 2009 at 11:01:09AM +0200, Antonio Ospite wrote:
> > Hi,
> >
> > I just wonder if there is any update on this one and if the split-out
> > patch has been proposed to upstream yet.
> >
> > If you manage to get this upstream, with Linus keeping on distributing
> > the binary images, debian can well choose not to distribute them, but
> > debian users can still get the blob somewhere and have an easier life.
> > Not ideal, I know, but that's the world.
>
> Yep - that's true.
>
> Kalle: would you mind submitting your patch upstream, if you haven't
> already? A lot of similar patches for other drives have been accepted
> in recent months.
Kalle's patch has a serious problem in that it attempts to byte-swap the
firmware in place. On a big-endian system where the firmware is built
into the kernel, or if a cache is implemented, this will corrupt the
image or cause an oops.
Furthermore, I think any patch sent upstream will need to handle the
"new" DSP code as well.
Anyway, here's my proposed patch for unstable (against 2.6.30-rc4) that
deals with the first problem. I'll have a go at handling the "new" DSP
code as well, but as I don't have the hardware for this driver this will
need testing by others.
I made the following changes relative to Kalle's patch:
- Remove "Modified on..." lines; that's what the commit message is for
- Do not call release_firmware() if request_firmware() fails
- Make firmware images explicitly const and little-endian and never swap
them.
- Remove offsets from firmware header so that we don't have to validate
them; we know the offset should be the base of the corresponding memory
bank.
- Validate sizes against the memory bank size.
- Change filename to cs46xx-old.fw as this is easier to associate with
its use. We can use cs46xx-new.fw for the "new" DSP code.
Ben.
diff --git a/sound/pci/Kconfig b/sound/pci/Kconfig
index 17e03b9..124b3a0 100644
--- a/sound/pci/Kconfig
+++ b/sound/pci/Kconfig
@@ -229,7 +229,7 @@ config SND_CS4281
config SND_CS46XX
tristate "Cirrus Logic (Sound Fusion) CS4280/CS461x/CS462x/CS463x"
- depends on BROKEN
+ select FW_LOADER
select SND_RAWMIDI
select SND_AC97_CODEC
help
@@ -241,6 +241,7 @@ config SND_CS46XX
config SND_CS46XX_NEW_DSP
bool "Cirrus Logic (Sound Fusion) New DSP support"
+ depends on BROKEN
depends on SND_CS46XX
default y
help
diff --git a/sound/pci/cs46xx/cs46xx_lib.c b/sound/pci/cs46xx/cs46xx_lib.c
index 1be96ea..b12b930 100644
--- a/sound/pci/cs46xx/cs46xx_lib.c
+++ b/sound/pci/cs46xx/cs46xx_lib.c
@@ -53,6 +53,7 @@
#include
#include
#include
+#include
#include
@@ -308,7 +309,7 @@ static void snd_cs46xx_ac97_write(struct snd_ac97 *ac97,
*/
int snd_cs46xx_download(struct snd_cs46xx *chip,
- u32 *src,
+ const __le32 *src,
unsigned long offset,
unsigned long len)
{
@@ -321,9 +322,9 @@ int snd_cs46xx_download(struct snd_cs46xx *chip,
dst = chip->region.idx[bank+1].remap_addr + offset;
len /= sizeof(u32);
- /* writel already converts 32-bit value to right endianess */
while (len-- > 0) {
- writel(*src++, dst);
+ __raw_writel((__force u32)*src++, dst);
+ mmiowb();
dst += sizeof(u32);
}
return 0;
@@ -360,23 +361,77 @@ int snd_cs46xx_clear_BA1(struct snd_cs46xx *chip,
#else /* old DSP image */
-#include "cs46xx_image.h"
+struct cs46xx_old_image {
+ __le32 size[BA1_MEMORY_COUNT];
+ __le32 data[0];
+};
-int snd_cs46xx_download_image(struct snd_cs46xx *chip)
+static int snd_cs46xx_check_image_size(const struct firmware *firmware)
{
- int idx, err;
- unsigned long offset = 0;
+ const struct cs46xx_old_image *image =
+ (const struct cs46xx_old_image *)firmware->data;
+ size_t offset = sizeof(*image);
+ int idx;
+
+ if (firmware->size < offset) {
+ snd_printk(KERN_ERR "cs46xx: firmware too small\n");
+ return -EINVAL;
+ }
for (idx = 0; idx < BA1_MEMORY_COUNT; idx++) {
- if ((err = snd_cs46xx_download(chip,
- &BA1Struct.map[offset],
- BA1Struct.memory[idx].offset,
- BA1Struct.memory[idx].size)) < 0)
- return err;
- offset += BA1Struct.memory[idx].size >> 2;
- }
+ size_t size = le32_to_cpu(image->size[idx]);
+
+ if (size % sizeof(u32)) {
+ snd_printk(KERN_ERR "cs46xx: firmware hunk
misaligned\n");
+ return -EINVAL;
+ }
+ if (size > BA1_DWORD_SIZE * sizeof(u32)) {
+
Bug#526693: [pkg-wpa-devel] Bug#526693: BUG: soft lockup - CPU#0 stuck for 61s (wpa_supplicant + jfs)
reassign 526693 linux-latest-2.6 found 526693 2.6.28-1 stop Reinhard Tartler ha scritto: reassing 526693 linux-latest-2.6 found 526693 2.6.28-1 stop I have rewritten this as looked like there was a typo. legolas558 writes: I am reluctant to agree because it happens also when wpa_supplicant is not running and the wifi device is turned off. A very common effect of this type of crash is that the JFS filesystem creates a 'stale NFS file' at /etc/mtab (I suppose failing to delete it), but the filesystem is marked as clean so I have to force a fsck to fix it (root filesystem won't mount without being able to write to /etc/mtab). I've never used jfs myself, but this story does not make me feel more comfortable to try it out. I have always read/heard that it is *stable*, this is surprising me too. Does the backtrace tell anything relevant? no, as it is not cause by a crash or something. I understand. Perhaps we need serial console output? Perhaps that could be useful. OK, I will make a test next week. Thanks for everything, -- Daniele C. I agree that the wpasupplicant is not responsible anyway. great! Package: linux-image-2.6.28-1-686 Version: 2.6.28-1 I'm reassinging accordingly. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526846: No support for Fintek F71862FG Super IO Sensors in linux 2.6.26
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15 Severity: wishlist Tags: patch lenny I've just installed debian stable (lenny) on a new Jetway JNC91-330-LF Intel ATOM Mainboard. Running 'sensors-detect' from lm-sensors (1:3.0.2-1+b2) reports: Driver `to-be-written' (should be inserted): Detects correctly: * ISA bus, address 0x295 Chip `Fintek F71862FG Super IO Sensors' (confidence: 9) I found support for this chip was added in linux 2.6.29 by these patches: http://lists.lm-sensors.org/pipermail/lm-sensors/2008-October/024510.html Backporting these patches to linux 2.6.26 and the resulting driver seems to dtrt. A quilt stack of these patches is attached. -- -- Ian Bygrave f71862fg-patches.tar.gz Description: GNU Zip compressed data
Bug#525220:
Works great on old kernel, Linux Maximiliano 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux [ 29.676030] eth0: no IPv6 routers present [ 30.792584] Bluetooth: L2CAP ver 2.9 [ 30.792584] Bluetooth: L2CAP socket layer initialized [ 30.844260] Bluetooth: RFCOMM socket layer initialized [ 30.844283] Bluetooth: RFCOMM TTY layer initialized [ 30.844288] Bluetooth: RFCOMM ver 1.8 [ 32.316296] lp: driver loaded but no devices found [ 32.333244] ppdev: user-space parallel port driver [ 40.987900] device-mapper: table: 254:0: striped: Couldn't parse stripe destination [ 40.987914] device-mapper: ioctl: error adding target to table [ 40.994512] device-mapper: table: 254:0: striped: Couldn't parse stripe destination [ 40.994525] device-mapper: ioctl: error adding target to table [ 41.453801] device-mapper: table: 254:0: striped: Couldn't parse stripe destination [ 41.453817] device-mapper: ioctl: error adding target to table [ 44.560879] ip_tables: (C) 2000-2006 Netfilter Core Team [ 291.174324] usb 2-2: USB disconnect, address 2 [ 292.684033] usb 2-2: new full speed USB device using ohci_hcd and address 4 [ 292.888012] usb 2-2: configuration #1 chosen from 1 choice [ 292.915310] usb 2-2: New USB device found, idVendor=1131, idProduct=1004 [ 292.915322] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 292.915327] usb 2-2: Product: ISSCEDRBTA [ 292.915331] usb 2-2: Manufacturer: ISSC [ 444.408934] usb 1-9: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 4 ret -110 [ 449.408135] usb 1-9: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 0 len 2 ret -110 [ 490.771059] hci_cmd_task: hci0 command tx timeout maxim...@maximiliano:~$ sudo hci hciattach hciconfig hcid hcidump hcitool maxim...@maximiliano:~$ sudo hciconfig -a hci0: Type: USB BD Address: 00:11:67:CB:5D:87 ACL MTU: 1021:4 SCO MTU: 48:10 UP RUNNING PSCAN ISCAN RX bytes:6431 acl:66 sco:0 events:253 errors:0 TX bytes:2173 acl:72 sco:0 commands:105 errors:0 Features: 0xff 0xfe 0xff 0x7e 0x98 0x19 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'Maximiliano-0' Class: 0x080104 Service Classes: Capturing Device Class: Computer, Desktop workstation HCI Ver: 2.0 (0x3) HCI Rev: 0x302 LMP Ver: 2.0 (0x3) LMP Subver: 0x302 Manufacturer: Integrated System Solution Corp. (57) maxim...@maximiliano:~$ sudo lsusb -v Bus 002 Device 004: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 16 idVendor 0x1131 Integrated System Solution Corp. idProduct 0x1004 Bluetooth Device bcdDevice 3.73 iManufacturer 1 ISSC iProduct 2 ISSCEDRBTA iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 186 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Sync
Bug#525958: (no subject)
There is no reason whatsoever to enable the CONFIG_PROM_CONSOLE option in the kernel. By definition it can only cause problems and conflicts with other console drivers. For one example, it unconditionally gets registered as a real console before the Sun Hypervisor console driver has a chance to register. The kernel takes whatever real console registers first, as the highest priority console (unless specified otherwise on the command line). It specifically creates this problem because unlike the framebuffer and serial console drivers, it does not have a way to know whether it should register or not. The serial and framebuffer drivers check the PROM indicated device node of the console device, and it only registers the device as the console if it matches the value of the 'output-device' PROM environment variable setting. Therefore, having CONFIG_PROM_CONSOLE enabled in the tree is going to do nothing other than constantly create problems and conflicts like this. It needs to be turned off, forever. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526836: linux-image-2.6-r5k-cobalt: Please include modules for scsi host adapters like aic7xxx or 53c8xx!
Package: linux-image-2.6-r5k-cobalt Version: 2.6.26+17+lenny1 Severity: wishlist Dear Debian kernel team! I use the kernel on a Cobalt Qube2 with 256 MB of RAM and a 200GB harddisk as my home/web-server. I would like to use an PCI scsi host adapter to connect a scsi tape drive. Unfortunately there are no kernel modules compiled for the available symbios-logic or adaptec controllers. Could you please include modules for aic7xxx and 53c8xx if they compile on this platform? Thank you very much in advance and keep up the good work! Christian -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: mipsel (mips) Kernel: Linux 2.6.18-6-r5k-cobalt Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-r5k-cobalt depends on: ii linux-image-2.6.26-2-r5k-coba 2.6.26-15 Linux 2.6.26 image on Cobalt linux-image-2.6-r5k-cobalt recommends no packages. linux-image-2.6-r5k-cobalt suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525220:
Maximi89 a écrit ce qui suit, le 03/05/09 21:47 : maxim...@maximiliano:~$ sudo dpkg -l | grep bluez : ii bluez 4.35-0ubuntu1 I wrote this on one line to keep the message shorter. After : ii etc. is the result. You have to understand it as sudo dpkg -l | grep bluez iibluez4.35-0ubuntu1 maxim...@maximiliano:~$ sudo /etc/init.d/bluetooth stop Stopping bluetooth: hcid. ... maxim...@maximiliano:~$ sudo hciconfig -a hci0: Type: USB BD Address: 00:11:67:CB:5D:87 ACL MTU: 1021:4 SCO MTU: 48:10 UP RUNNING PSCAN ISCAN RX bytes:1226 acl:0 sco:0 events:26 errors:0 TX bytes:347 acl:0 sco:0 commands:27 errors:0 Features: 0xff 0xfe 0xff 0x7e 0x98 0x19 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'Maximiliano-0' Class: 0x080104 Service Classes: Capturing Device Class: Computer, Desktop workstation HCI Ver: 2.0 (0x3) HCI Rev: 0x302 LMP Ver: 2.0 (0x3) LMP Subver: 0x302 Manufacturer: Integrated System Solution Corp. (57) In your case too, there is no more "hci0 command tx timeout" with bluetooth stopped. This should be an important information to debug this problem. I am not able to do it myself, so the next step should be to convince some developer to take the problem seriously -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525220:
Sorry Dominique, but i'm running Debian, and i have an another device:
Bus 002 Device 003: ID 1131:1004 Integrated System Solution Corp. Bluetooth
Device
[ 57.235079] Bluetooth: Core ver 2.14
[ 57.236915] NET: Registered protocol family 31
[ 57.236977] Bluetooth: HCI device and connection manager initialized
[ 57.237025] Bluetooth: HCI socket layer initialized
[ 57.308889] Bluetooth: L2CAP ver 2.11
[ 57.308946] Bluetooth: L2CAP socket layer initialized
[ 57.329295] Bluetooth: RFCOMM socket layer initialized
[ 57.329375] Bluetooth: RFCOMM TTY layer initialized
[ 57.329416] Bluetooth: RFCOMM ver 1.10
[ 59.033637] lp: driver loaded but no devices found
[ 59.064151] ppdev: user-space parallel port driver
[ 67.736226] device-mapper: table: 254:0: striped: Couldn't parse stripe
destination
[ 67.736235] device-mapper: ioctl: error adding target to table
[ 67.744887] device-mapper: table: 254:1: striped: Couldn't parse stripe
destination
[ 67.744895] device-mapper: ioctl: error adding target to table
[ 71.204500] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 92.811657] usb 1-2: USB disconnect, address 2
[ 112.752030] usb 2-2: new full speed USB device using ohci_hcd and address
3
[ 112.976555] usb 2-2: New USB device found, idVendor=1131, idProduct=1004
[ 112.976561] usb 2-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 112.976566] usb 2-2: Product: ISSCEDRBTA
[ 112.976570] usb 2-2: Manufacturer: ISSC
[ 112.976694] usb 2-2: configuration #1 chosen from 1 choice
[ 113.153738] Bluetooth: Generic Bluetooth USB driver ver 0.4
[ 113.153861] usbcore: registered new interface driver btusb
[ 120.328027] usb 1-9: new high speed USB device using ehci_hcd and address
5
[ 120.461335] usb 1-9: New USB device found, idVendor=04e8, idProduct=508a
[ 120.461343] usb 1-9: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 120.461348] usb 1-9: Product: T10
[ 120.461352] usb 1-9: Manufacturer: SAMSUNG
[ 120.461355] usb 1-9: SerialNumber: 824AFBFB0021613686F0573DF3000F16
[ 120.461488] usb 1-9: configuration #1 chosen from 1 choice
[ 123.256237] hci_cmd_task: hci0 command tx timeout
maxim...@maximiliano:~$ sudo modinfo btusb
[sudo] password for maximi89:
filename: /lib/modules/2.6.29-1-486/kernel/drivers/bluetooth/btusb.ko
license: GPL
version: 0.4
description: Generic Bluetooth USB driver ver 0.4
author: Marcel Holtmann
srcversion: F7380744D6CF408FCA36AE2
alias: usb:v0C10pd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDBp1002d*dc*dsc*dp*ic*isc*ip*
alias: usb:v044Ep3002d*dc*dsc*dp*ic*isc*ip*
alias: usb:v044Ep3001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04BFp030Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v057Cp3800d*dc*dsc*dp*ic*isc*ip*
alias: usb:v*p*d*dcE0dsc01dp01ic*isc*ip*
depends: usbcore,bluetooth
vermagic: 2.6.29-1-486 mod_unload modversions 486
parm: ignore_dga:Ignore devices with id 08fd:0001 (bool)
parm: ignore_csr:Ignore devices with id 0a12:0001 (bool)
parm: ignore_sniffer:Ignore devices with id 0a12:0002 (bool)
parm: disable_scofix:Disable fixup of wrong SCO buffer size (bool)
parm: force_scofix:Force fixup of wrong SCO buffers size (bool)
parm: reset:Send HCI reset command on initialization (bool)
maxim...@maximiliano:~$ sudo dpkg -l | grep bluez : ii bluez 4.35-0ubuntu1
grep: :: No existe el fichero o el directorio
grep: ii: No existe el fichero o el directorio
grep: bluez: No existe el fichero o el directorio
grep: 4.35-0ubuntu1: No existe el fichero o el directorio
maxim...@maximiliano:~$ sudo /etc/init.d/bluetooth status
Usage: /etc/init.d/bluetooth {start|stop|restart|force-reload}
maxim...@maximiliano:~$ sudo /etc/init.d/bluetooth stop
Stopping bluetooth: hcid.
maxim...@maximiliano:~$ sudo hciconfig
hci0: Type: USB
BD Address: 00:11:67:CB:5D:87 ACL MTU: 1021:4 SCO MTU: 48:10
UP RUNNING PSCAN ISCAN
RX bytes:1226 acl:0 sco:0 events:26 errors:0
TX bytes:347 acl:0 sco:0 commands:27 errors:0
maxim...@maximiliano:~$ sudo hciconfig -a
hci0: Type: USB
BD Address: 00:11:67:CB:5D:87 ACL MTU: 1021:4 SCO MTU: 48:10
UP RUNNING PSCAN ISCAN
RX bytes:1226 acl:0 sco:0 events:26 errors:0
TX bytes:347 acl:0 sco:0 commands:27 errors:0
Features: 0xff 0xfe 0xff 0x7e 0x98 0x19 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Maximiliano-0'
Class: 0x080104
Service Classes: Capturing
Device Class: Computer, Desktop workstation
HCI Ver: 2.0 (0x3) HCI Rev: 0x302 LMP Ver: 2.0 (0x3) LMP Subver: 0x302
Manufacturer: Integrated System Solution Corp. (57)
maxim...@maximiliano:~$ hcitool scan
Scanning ...
00:1A:1B:96:93:22 Archer's L6
00:1F:C8:FF:2C:A9 n/a
Bus 002 Device 003: ID 1131:1004 Integrated System Solution Corp. Bluetooth
Device
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 16
idVendor 0x1131 Integrated System Solution Corp.
idProduct 0x1004 Bluetooth Device
bcdDevice 3.73
iManu
reassign 526693 to linux-2.6
reassign 526693 linux-2.6 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: > # Sun May 3 20:03:31 UTC 2009 > # Tagging as pending bugs that are closed by packages in NEW > # http://ftp-master.debian.org/new.html > # > # Source package in NEW: fswebcam > tags 513575 + pending Bug#513575: ITP: fswebcam -- Tiny and flexible webcam program There were no tags set. Tags added: pending > # Source package in NEW: bpython > tags 526740 + pending Bug#526740: ITP: bpython -- fancy curses interface to the Python interactive interpreter There were no tags set. Tags added: pending > # Source package in NEW: linux-2.6 > tags 525926 + pending Bug#525926: linux-2.6 2.6.29-3 built with wrong config on sparc There were no tags set. Bug#526001: linux-image-2.6.29-1-sparc64: boot failure: Fast Data Access MMU Miss Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #408635 # * http://bugzilla.kernel.org/show_bug.cgi?id=7952 # * remote status changed: NEW -> ASSIGNED usertags 408635 - status-NEW usertags 408635 + status-ASSIGNED # remote status report for #503544 # * http://bugzilla.kernel.org/show_bug.cgi?id=13199 # * remote status changed: (?) -> NEW usertags 503544 + status-NEW # remote status report for #513095 # * http://bugzilla.openvz.org/show_bug.cgi?id=1252 # * remote status changed: (?) -> NEW usertags 513095 + status-NEW # remote status report for #513537 # * http://bugzilla.openvz.org/show_bug.cgi?id=1161 # * remote status changed: (?) -> PATCHSENT usertags 513537 + status-PATCHSENT # remote status report for #526097 # * http://bugzilla.openvz.org/show_bug.cgi?id=1254 # * remote status changed: (?) -> NEW usertags 526097 + status-NEW thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 526693 to linux-2.6
Processing commands for cont...@bugs.debian.org: > reassign 526693 linux-2.6 Bug#526693: BUG: soft lockup - CPU#0 stuck for 61s (wpa_supplicant + jfs) Bug reassigned from package `wpasupplicant' to `linux-2.6'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526805: firmware-iwlwifi: wlan0 needs extra poke to come up
On Sun, 2009-05-03 at 13:00 -0400, Mark T.B. Carroll wrote: > Package: firmware-iwlwifi > Version: 0.16 > Severity: normal > > My /etc/network/interfaces has, > > iface wlan0 inet dhcp > wireless_mode Managed > wireless_essid "mtbc at home" > > I'm doing these tests without encryption, to make it simpler. > > If I do an ifup wlan0 then it says, > > ADDRCONF(NETDEV_UP): wlan0: link is not ready This is normal. > and the DHCP goes ahead and doesn't get any response. [...] What does "iwconfig wlan0" say in this case? Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot signature.asc Description: This is a digitally signed message part
Bug#526805: firmware-iwlwifi: wlan0 needs extra poke to come up
It occurs to me to add, m...@evangeline:~$ lspci | grep 3945 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) m...@evangeline:~$ dmesg | grep iwl iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26k iwl3945: Copyright(c) 2003-2008 Intel Corporation iwl3945 :03:00.0: enabling device ( -> 0002) iwl3945 :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwl3945 :03:00.0: setting latency timer to 64 iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels iwl3945: Detected Intel Wireless WiFi Link 3945ABG iwl3945 :03:00.0: PCI INT A disabled wmaster0 (iwl3945): not using net_device_ops yet phy0: Selected rate control algorithm 'iwl-3945-rs' wlan0 (iwl3945): not using net_device_ops yet iwl3945 :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwl3945 :03:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x16) iwl3945 :03:00.0: irq 24 for MSI/MSI-X iwl3945 :03:00.0: firmware: requesting iwlwifi-3945-2.ucode iwl3945 loaded firmware version 15.28.2.8 m...@evangeline:~$ Mark -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526805: Acknowledgement (firmware-iwlwifi: wlan0 needs extra poke to come up)
I should add that the problem also existed back when I was using iwlwifi-3945-1.ucode instead of -2 Mark -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526805: firmware-iwlwifi: wlan0 needs extra poke to come up
Package: firmware-iwlwifi Version: 0.16 Severity: normal My /etc/network/interfaces has, iface wlan0 inet dhcp wireless_mode Managed wireless_essid "mtbc at home" I'm doing these tests without encryption, to make it simpler. If I do an ifup wlan0 then it says, ADDRCONF(NETDEV_UP): wlan0: link is not ready and the DHCP goes ahead and doesn't get any response. If I wait a moment after the ifup (three seconds is normally enough) and then in another shell set an iwconfig option, e.g., iwconfig wlan0 essid "mtbc at home", then I get a, ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready and then the next DHCP request gets an answer. This has been true for me ever since I first switched to iwl3945 from ipw3945 a few versions and many months ago. (Also, I tried installing Debian 5.0 from a netinst CD on an identical machine and after I fed it the firmware the installer couldn't get a DHCP address over wifi so I had to do the first parts by using wired ethernet to a wireless access point working as a transparent bridge instead - that worked fine.) I have no idea if it's relevant, but I mention just in case: during boot the kernel log mentions, pci :0a:08.0: Firmware left e100 interrupts enabled; disabling and, ACPI: EC: missing confirmations, switch off interrupt mode. (I wondered if some sort of interrupt is generated when the card associates with an AP.) Mark -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (600, 'stable'), (50, 'unstable'), (40, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: pn initramfs-tools(no description available) pn linux-image(no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#444182: Boot-time driver configuration
It is not uncommon (and not unreasonable) for multiple modules to declare support for the same hardware. However, short of recompiling or blacklisting entire modules, there is no mechanism, e.g. via configuration files, for configuring which module will actually take charge of which hardware. Isn't this lack the real problem? Is there a reason why the kernel does not provide such a mechanism? Justus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#444182: linux-image-2.6.29-1-686: please include a kernel build without the drivers-ata-ata_piix-postpone-pata.patch patch
Package: linux-image-2.6.29-1-686 Version: 2.6.29-3 Severity: normal As the drivers-ata-ata_piix-postpone-pata.patch removes the ability to hot-swap a CD-ROM from a laptop media bay for several chipsets, please consider building a flavour of the linux kernel that does not include that patch, so that those of us with this problem can make the choice to install a functional kernel, while not breaking operation for other users. Or, perhaps create a package with only a functional ata_piix module that then creates a diversion for those of us that wish it. -- Package-specific info: ** Version: Linux version 2.6.29-1-686 (Debian 2.6.29-3) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-3) ) #1 SMP Fri May 1 16:55:14 MDT 2009 ** Command line: root=/dev/sda2 ro ** Not tainted ** Kernel log: [ 131.158904] tg3 :09:00.0: PME# disabled [ 131.159061] tg3 :09:00.0: irq 29 for MSI/MSI-X [ 131.220093] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 131.676985] iwlagn :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 131.677170] iwlagn :0c:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106) [ 131.677349] iwlagn :0c:00.0: irq 30 for MSI/MSI-X [ 131.677466] iwlagn :0c:00.0: firmware: requesting iwlwifi-4965-2.ucode [ 131.722237] iwlagn loaded firmware version 228.57.2.23 [ 131.928281] Registered led device: iwl-phy0:radio [ 131.928322] Registered led device: iwl-phy0:assoc [ 131.928363] Registered led device: iwl-phy0:RX [ 131.928397] Registered led device: iwl-phy0:TX [ 131.975445] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 132.797707] tg3: eth0: Link is up at 100 Mbps, full duplex. [ 132.797716] tg3: eth0: Flow control is on for TX and on for RX. [ 132.798178] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 134.317998] Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008) [ 134.318009] bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. [ 134.405547] tg3 :09:00.0: PME# enabled [ 134.422824] bonding: bond0: doing slave updates when interface is down. [ 134.422835] bonding: bond0: Adding slave eth0. [ 134.422842] bonding bond0: master_dev is not up in bond_enslave [ 134.432279] tg3 :09:00.0: PME# disabled [ 134.452311] tg3 :09:00.0: irq 29 for MSI/MSI-X [ 134.513330] bonding: bond0: enslaving eth0 as an active interface with an up link. [ 134.607904] iwlagn :0c:00.0: PCI INT A disabled [ 134.615728] bonding: bond0: doing slave updates when interface is down. [ 134.615739] bonding: bond0: Adding slave wlan0. [ 134.615746] bonding bond0: master_dev is not up in bond_enslave [ 134.629235] iwlagn :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 134.629381] iwlagn :0c:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106) [ 134.629555] iwlagn :0c:00.0: irq 30 for MSI/MSI-X [ 134.831809] Registered led device: iwl-phy0:radio [ 134.831851] Registered led device: iwl-phy0:assoc [ 134.831885] Registered led device: iwl-phy0:RX [ 134.831922] Registered led device: iwl-phy0:TX [ 134.868001] bonding: bond0: Warning: failed to get speed and duplex from wlan0, assumed to be 100Mb/sec and Full. [ 134.868038] bonding: bond0: enslaving wlan0 as an active interface with an up link. [ 134.868540] bonding: bond0: setting mode to active-backup (1). [ 134.868731] bonding: bond0: Setting MII monitoring interval to 100. [ 134.872326] bonding: bond0: Setting eth0 as primary slave. [ 135.181128] tun: Universal TUN/TAP device driver, 1.6 [ 135.181136] tun: (C) 1999-2004 Max Krasnyansky [ 135.475624] Bridge firewalling registered [ 135.502099] device bond0 entered promiscuous mode [ 135.508513] bonding: bond0: link status definitely down for interface eth0, disabling it [ 135.508522] bonding: bond0: link status definitely down for interface wlan0, disabling it [ 135.518072] device tap0 entered promiscuous mode [ 135.524841] br0: port 2(tap0) entering learning state [ 136.070066] tg3: eth0: Link is up at 100 Mbps, full duplex. [ 136.070074] tg3: eth0: Flow control is on for TX and on for RX. [ 136.108167] bonding: bond0: link status definitely up for interface eth0. [ 136.108178] bonding: bond0: making interface eth0 the new active one. [ 136.108184] device eth0 entered promiscuous mode [ 136.108267] bonding: bond0: first active interface up! [ 136.320612] br0: port 1(bond0) entering learning state [ 138.139846] wlan0: authenticate with AP 00:1c:10:41:cd:9e [ 138.142005] wlan0: authenticated [ 138.142014] wlan0: associate with AP 00:1c:10:41:cd:9e [ 138.145821] wlan0: RX AssocResp from 00:1c:10:41:cd:9e (capab=0x431 status=0 aid=1) [ 138.145828] wlan0: associated [ 138.208173] bonding: bond0: link status definitely up for interface wlan0. [ 145.556152] br0: no IPv6 routers present [ 145.592142] bond0: no IPv6 routers present
Bug#526737: marked as done (md: RAID 1 check makes kernel almost panic)
also sprach Bastian Blank [2009.05.03.1133 +0200]: > It is a valid bug and fixed with the next upload. Can you please provide details on how I can reproduce this bug? -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "and no one sings me lullabies, and no one makes me close my eyes, and so i throw the windows wide, and call to you across the sky" -- pink floyd, 1971 digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#366175: Rootdelay
I've just tried setting up a new machine (a Dell Precision 670) and hit this bug *hard*. The setup I was aiming for was a software RAID 1 for root (pair of SCSI discs, to be replaced by some small flash drives later), and at a later date, a software RAID 5 array for everything else (collection of SATA discs). I initially wanted to install Testing, but at the time I was looking for install images those available were having disk detection issues, so I plumped for a Lenny image instead, which installed just fine, and booted fine every time. Once Lenny was installed I upgraded to Testing, and once that was installed the reboot always failed, with the dreaded "no devices" preventing md0 from coming up. What really annoyed me at this point was the fact that I could never catch the last few log messages before the busybox shell popped up, as straight after it appeared some more boot messages about my disks would always scroll it off the top of the screen. This should have been a clue as to the issue, but I had no reason to even assume that Debian would have such a fundamental bug! Surely waiting until disk detection is complete (or at the very least, any dependencies of the root filesystem!) is pretty fundamental? Anyway. I've spent countless evenings after work trying to get this to work until I stumbled upon a mailing list post suggesting rootdelay as a workaround, and searching on that brought me here. Would it be possible to get a message to appear when the root device isn't available suggesting the use of rootdelay as a stopgap until this gets fixed? - Jamie signature.asc Description: OpenPGP digital signature
Bug#526001: marked as done (linux-image-2.6.29-1-sparc64: boot failure: Fast Data Access MMU Miss)
Your message dated Sun, 03 May 2009 09:58:04 + with message-id and subject line Bug#525926: fixed in linux-2.6 2.6.29-4 has caused the Debian Bug report #525926, regarding linux-image-2.6.29-1-sparc64: boot failure: Fast Data Access MMU Miss 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 ow...@bugs.debian.org immediately.) -- 525926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.29-1-sparc64 Version: 2.6.29-3 Severity: normal This kernel fails to boot on my Ultra60. Immediately after loading the initrd image, the message "Fast Data Access MMU Miss" appears and I get dropped back to the PROM "ok" prompt without any additional output. This appears to be new with 2.6.29 (or at least doesn't appear with 2.6.26-2-sparc64). -- Package-specific info: -- System Information: Debian Release: squeeze/sid Architecture: sparc (sparc64) Kernel: Linux 2.6.26-2-sparc64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-sparc64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-sparc64 recommends no packages. Versions of packages linux-image-2.6.29-1-sparc64 suggests: ii fdutils5.5-20060227-3Linux floppy utilities pn linux-doc-2.6.29 (no description available) ii silo 1.4.13a+git20070930-3 Sparc Improved LOader -- debconf information: linux-image-2.6.29-1-sparc64/postinst/bootloader-error-2.6.29-1-sparc64: linux-image-2.6.29-1-sparc64/prerm/would-invalidate-boot-loader-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/preinst/abort-overwrite-2.6.29-1-sparc64: linux-image-2.6.29-1-sparc64/preinst/abort-install-2.6.29-1-sparc64: linux-image-2.6.29-1-sparc64/preinst/lilo-initrd-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/postinst/depmod-error-initrd-2.6.29-1-sparc64: false linux-image-2.6.29-1-sparc64/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-sparc64/postinst/create-kimage-link-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/postinst/old-system-map-link-2.6.29-1-sparc64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-sparc64/postinst/bootloader-test-error-2.6.29-1-sparc64: linux-image-2.6.29-1-sparc64/preinst/bootloader-initrd-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/preinst/failed-to-move-modules-2.6.29-1-sparc64: linux-image-2.6.29-1-sparc64/postinst/kimage-is-a-directory: linux-image-2.6.29-1-sparc64/preinst/overwriting-modules-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/postinst/old-dir-initrd-link-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/preinst/elilo-initrd-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/prerm/removing-running-kernel-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/postinst/old-initrd-link-2.6.29-1-sparc64: true linux-image-2.6.29-1-sparc64/preinst/initrd-2.6.29-1-sparc64: linux-image-2.6.29-1-sparc64/postinst/depmod-error-2.6.29-1-sparc64: false --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.29-4 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.29-4.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.diff.gz linux-2.6_2.6.29-4.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.dsc linux-doc-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.29_2.6.29-4_all.deb linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc-smp_2.6.29-4_power
Bug#525926: marked as done (linux-2.6 2.6.29-3 built with wrong config on sparc)
Your message dated Sun, 03 May 2009 09:58:04 + with message-id and subject line Bug#525926: fixed in linux-2.6 2.6.29-4 has caused the Debian Bug report #525926, regarding linux-2.6 2.6.29-3 built with wrong config on sparc 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 ow...@bugs.debian.org immediately.) -- 525926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.29-3 Severity: serious The 2.6.29-3 packages are built using wrong config on sparc, resulting kernel won't boot on any sparc64 hardware: ju...@debian:/boot$ head config-2.6.29-1-sparc64 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.29 # Fri Apr 17 14:27:44 2009 # # CONFIG_64BIT is not set CONFIG_SPARC=y CONFIG_SPARC32=y # CONFIG_SPARC64 is not set CONFIG_ARCH_DEFCONFIG="arch/sparc/configs/sparc32_defconfig" Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.29-4 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.29-4.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.diff.gz linux-2.6_2.6.29-4.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.dsc linux-doc-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.29_2.6.29-4_all.deb linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-libc-dev_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.29-4_powerpc.deb linux-manual-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.29_2.6.29-4_all.deb linux-patch-debian-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.29_2.6.29-4_all.deb linux-source-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-source-2.6.29_2.6.29-4_all.deb linux-support-2.6.29-2_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-support-2.6.29-2_2.6.29-4_all.deb linux-tree-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.29_2.6.29-4_all.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 525...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated linux-2.6 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 03 May 2009 09:38:42 +0200 Source: linux-2.6 Binary: linux-source-2.6.29 linux-doc-2.6.29 linux-manual-2.6.29 linux-patch-debian-2.6.29 linux-tree-2.6.29 linux-support-2.6.29-2 linux-libc-dev linux-headers-2.6.29-2-all linux-headers-2.6.29-2-all-alpha linux-headers-2.6.29-2-common linux-image-2.6.29-2-alpha-generic linux-headers-2.6.29-2-alpha-generic linux-image-2.6.29-2-alpha-smp linux-headers-2.6.29-2-alpha-smp linux-image-2.6.29-2-alpha-legacy linux-headers-2.6.29-2-alpha-legacy linux-headers-2.6.29-2-all-amd64 linux-image-2.6.29-2-amd64 linux-headers-2.6.29-2-amd64 linux-headers-2.6.29-2-all-arm
linux-2.6_2.6.29-4_powerpc.changes ACCEPTED
Accepted: linux-2.6_2.6.29-4.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.diff.gz linux-2.6_2.6.29-4.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.dsc linux-doc-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.29_2.6.29-4_all.deb linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-libc-dev_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.29-4_powerpc.deb linux-manual-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.29_2.6.29-4_all.deb linux-patch-debian-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.29_2.6.29-4_all.deb linux-source-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-source-2.6.29_2.6.29-4_all.deb linux-support-2.6.29-2_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-support-2.6.29-2_2.6.29-4_all.deb linux-tree-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.29_2.6.29-4_all.deb Override entries for your package: linux-2.6_2.6.29-4.dsc - optional devel linux-doc-2.6.29_2.6.29-4_all.deb - optional doc linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb - optional devel linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb - optional devel linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb - optional devel linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb - optional devel linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb - optional devel linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb - optional devel linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb - optional admin linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb - optional admin linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb - optional admin linux-libc-dev_2.6.29-4_powerpc.deb - optional devel linux-manual-2.6.29_2.6.29-4_all.deb - optional doc linux-patch-debian-2.6.29_2.6.29-4_all.deb - optional devel linux-source-2.6.29_2.6.29-4_all.deb - optional devel linux-support-2.6.29-2_2.6.29-4_all.deb - optional devel linux-tree-2.6.29_2.6.29-4_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 525926 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526519: cmake immediately hangs if run in i386 chroot on amd64 host
On Fri, May 01, 2009 at 05:28:40PM +, Joachim Reichel wrote: > Package: cmake > Version: 2.6.3-2 > Severity: normal > > If i use cmake in an i386 chroot on an amd64 machine, it just prints "Linux" > and hangs. The same happens inside an i386 pbuilder environment on an amd64 > machine (therefore I think this problem is not caused by a dirty chroot). > > How to reproduce: > - create i386 chroot on amd64 machine > - touch CMakeLists.txt > - cmake . Do you run it under "linux32" so that the uname is changed ? -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org pgpDqgTk52iB2.pgp Description: PGP signature
linux-2.6_2.6.29-4_powerpc.changes is NEW
linux-2.6_2.6.29-4.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.diff.gz linux-2.6_2.6.29-4.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.29-4.dsc linux-doc-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.29_2.6.29-4_all.deb (new) linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb optional devel All header files for Linux 2.6.29 This package depends against all architecture-specific kernel header files for Linux kernel version 2.6.29, generally used for building out-of-tree kernel modules. (new) linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb optional devel All header files for Linux 2.6.29 This package depends against all architecture-specific kernel header files for Linux kernel version 2.6.29, generally used for building out-of-tree kernel modules. (new) linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb optional devel Common header files for Linux 2.6.29-2 This package provides the architecture-specific common kernel header files for Linux kernel version 2.6.29-2, generally used for building out-of-tree kernel modules. To obtain a complete set of headers you also need to install the linux-headers-2.6.29-2-(flavour) package, matching the flavour of the kernel you intend the build for. (new) linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb optional devel Header files for Linux 2.6.29-2-powerpc-smp This package provides the architecture-specific kernel header files for Linux kernel 2.6.29-2-powerpc-smp, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.29-2-powerpc-smp, and can be used for building modules that load into the kernel provided by the linux-image-2.6.29-2-powerpc-smp package. (new) linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb optional devel Header files for Linux 2.6.29-2-powerpc64 This package provides the architecture-specific kernel header files for Linux kernel 2.6.29-2-powerpc64, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.29-2-powerpc64, and can be used for building modules that load into the kernel provided by the linux-image-2.6.29-2-powerpc64 package. (new) linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb optional devel Header files for Linux 2.6.29-2-powerpc This package provides the architecture-specific kernel header files for Linux kernel 2.6.29-2-powerpc, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.29-2-powerpc, and can be used for building modules that load into the kernel provided by the linux-image-2.6.29-2-powerpc package. (new) linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb optional admin Linux 2.6.29 image on multiprocessor 32-bit PowerPC This package provides the binary image and pre-built loadable modules for Linux kernel 2.6.29 on multiprocessor 32-bit PowerPC machines. (new) linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb optional admin Linux 2.6.29 image on 64-bit PowerPC This package provides the binary image and pre-built loadable modules for Linux kernel 2.6.29 on 64-bit PowerPC machines. (new) linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb optional admin Linux 2.6.29 image on uniprocessor 32-bit PowerPC This package provides the binary image and pre-built loadable modules for Linux kernel 2.6.29 on uniprocessor 32-bit PowerPC machines. linux-libc-dev_2.6.29-4_powerpc.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.29-4_powerpc.deb linux-manual-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.29_2.6.29-4_all.deb linux-patch-debian-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.29_2.6.29-4_all.deb linux-source-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-source-2.6.29_2.6.29-4_all.deb (new) linux-support-2.6.29-2_2.6.29-4_all.deb optional devel Support files for Linux 2.6.29 This package provides support files for the Linux kernel build. linux-tree-2.6.29_2.6.29-4_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.29_2.6.29-4_all.deb Changes: linux-2.6 (2.6.29-4) unstable; urgency=low . [ maximilian attems ] * drm/i915: allow tiled front buffers on 965+. . [ Martin Michlmayr ] * Extend erase timeout in M25P80 SPI Flash driver (Peter Horton). * Add driver for GMT G760A fan speed PWM controller chip. * [arm/orion5x] Enable SENSORS_G760A. * Add patches from git.marvell.com: - allow for alternative __copy_to_user/__clear_user implementations - alternative copy_to_user/clear_user implementation copy_user * [arm/orion5x, armel/kirkwood] Enable UACCESS_WITH_MEMCPY. * [MMC] give Sandisk/Kingston SDHC cards some slack before the SWITCH command. . [ dann frazier ] * [parisc] Fix macro expansion in atomic.h fixing PHONET compilation issue * [parisc] reenable PHONET * Btrfs: fix __ucmpdi2 compile bug on 32 bit builds . [ Stephen R. Marenka ]
Bug#526737: marked as done (md: RAID 1 check makes kernel almost panic)
fixed 526737 2.6.29-4 thanks On Sun, May 03, 2009 at 08:24:07AM +, Debian Bug Tracking System wrote: > Date: Sun, 3 May 2009 10:19:29 +0200 > From: martin f krafft > To: Julien Danjou , 526737-d...@bugs.debian.org > Subject: Re: Bug#526737: md: RAID 1 check makes kernel almost panic > > also sprach Julien Danjou [2009.05.03.0931 +0200]: > > The check was stuck at 2% according to /proc/mdstat. I tried to > > run it again, but that caused the second backtrace you can see > > below. > > Sounds like memory corruption or another hardware issue to me. Not > a bug, I've sync'd many dozens of arrays, levels 1,5,6,10, with > 2.6.26 and 2.6.29, with mdadm 2.6.[789] and 3.0, and I've never seen > anything like it. It is a valid bug and fixed with the next upload. Bastian -- The sooner our happiness together begins, the longer it will last. -- Miramanee, "The Paradise Syndrome", stardate 4842.6 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#526737: marked as done (md: RAID 1 check makes kernel almost panic)
Processing commands for cont...@bugs.debian.org: > fixed 526737 2.6.29-4 Bug#526737: md: RAID 1 check makes kernel almost panic Bug marked as fixed in version 2.6.29-4. > 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
Bug#526737: md: RAID 1 check makes kernel almost panic
tags 526737 fixed-upstream
thanks
On Sun, May 03, 2009 at 09:31:35AM +0200, Julien Danjou wrote:
> Version: 2.6.29-3
This does not match the version listed below.
> Today was the normal crondate for mdadm to run a check on my 2 raid 1
> devices.
> Problem, when I woke up this morning I found very bad stuff on my
> terminals.
>
> The check was stuck at 2% according to /proc/mdstat. I tried to run it
> again, but that caused the second backtrace you can see below.
Looks like this is fixed in 303a0e11d0ee136ad8f53f747f3c377daece763b and
also in 2.6.29.2.
> Now, I cannot even check the RAID status since "cat /proc/mdstat" hangs.
>
> % strace cat /proc/mdstat
> [...]
> open("/proc/mdstat", O_RDONLY) = 3
> fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> read(3,
The MD subsystem is dead at this time, so such fallouts are likely.
> -- Package-specific info:
> ** Version:
> Linux version 2.6.29-1-amd64 (Debian 2.6.29-2) (wa...@debian.org) (gcc
> version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Sat Apr 4 16:54:07 UTC 2009
>
> ** Command line:
> root=/dev/mapper/system-root ro vga=791 splash
>
> ** Tainted: P D (129)
You use proprietary drivers. We don't support systems in this state.
> ** Kernel log:
> [1404264.039924] md: data-check of RAID array md0
> [1404264.039927] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
> [1404264.039930] md: using maximum available idle IO bandwidth (but not more
> than 20 KB/sec) for data-check.
> [1404264.039934] md: using 128k window, over a total of 48064 blocks.
The check started here.
> [1404264.042298] general protection fault: [#1] SMP
> [1404264.042302] last sysfs file:
> /sys/devices/virtual/block/md1/md/sync_action
> [1404264.042304] CPU 0
> [1404264.042306] Modules linked in: rfcomm l2cap bluetooth nvidia(P) ipv6
> acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace
> cpufreq_conservative nfs lockd nfs_acl auth_rpcgss sunrpc coretemp w83627ehf
> hwmon_vid firewire_sbp2 loop snd_hda_codec_realtek snd_hda_intel
> snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy
> snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
> snd_seq_device i2c_i801 snd soundcore snd_page_alloc i2c_core pcspkr
> serio_raw evdev button ext3 jbd mbcache dm_mirror dm_region_hash dm_log
> dm_snapshot dm_mod raid1 md_mod hid_logitech ff_memless usbhid hid sd_mod
> crc_t10dif ide_cd_mod cdrom ata_generic uhci_hcd ide_pci_generic ata_piix
> firewire_ohci firewire_core crc_itu_t ahci atl1 mii libata jmicron ide_core
> scsi_mod ehci_hcd intel_agp thermal processor fan thermal_sys
> [1404264.042363] Pid: 32532, comm: md0_resync Tainted: P
> 2.6.29-1-amd64 #1 P5K
> [1404264.042365] RIP: 0010:[] []
> put_page+0xb/0xbb
It died in put_page with a general protection fault.
Bastian
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#526737: md: RAID 1 check makes kernel almost panic
Processing commands for cont...@bugs.debian.org: > tags 526737 fixed-upstream Bug#526737: md: RAID 1 check makes kernel almost panic There were no tags set. Tags added: fixed-upstream > 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
Bug#525871: linux-image-2.6.29-1-amd64: there seems to be a path for this
Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://bugs.gentoo.org/264090 - -- Package-specific info: - -- System Information: Debian Release: squeeze/sid Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=sv_SE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-amd64 recommends no packages. Versions of packages linux-image-2.6.29-1-amd64 suggests: ii grub 0.97-53GRand Unified Bootloader (Legacy v pn linux-doc-2.6.29 (no description available) - -- debconf information: linux-image-2.6.29-1-amd64/preinst/overwriting-modules-2.6.29-1-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-amd64/preinst/failed-to-move-modules-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/bootloader-test-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/old-dir-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/prerm/removing-running-kernel-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-amd64/postinst/create-kimage-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/initrd-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/preinst/elilo-initrd-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/kimage-is-a-directory: linux-image-2.6.29-1-amd64/postinst/old-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/depmod-error-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/postinst/depmod-error-initrd-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/preinst/abort-install-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/preinst/abort-overwrite-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/bootloader-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/prerm/would-invalidate-boot-loader-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/old-system-map-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/lilo-initrd-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/bootloader-initrd-2.6.29-1-amd64: true -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn9X7sACgkQw5UvgfnzqGoflgCfcIQ/v6rmcd6aB4I0yhGbzxhF eVEAn3Y3O6fhBUCQfsLawFjO9PZe7LyZ =6J0U -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6_2.6.29-4_powerpc.changes
linux-2.6_2.6.29-4_powerpc.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.29-4.dsc linux-2.6_2.6.29-4.diff.gz linux-support-2.6.29-2_2.6.29-4_all.deb linux-tree-2.6.29_2.6.29-4_all.deb linux-patch-debian-2.6.29_2.6.29-4_all.deb linux-headers-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc_2.6.29-4_powerpc.deb linux-source-2.6.29_2.6.29-4_all.deb linux-headers-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc-smp_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-image-2.6.29-2-powerpc64_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-common_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-all_2.6.29-4_powerpc.deb linux-headers-2.6.29-2-all-powerpc_2.6.29-4_powerpc.deb linux-libc-dev_2.6.29-4_powerpc.deb linux-doc-2.6.29_2.6.29-4_all.deb linux-manual-2.6.29_2.6.29-4_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 526737 is important
Processing commands for cont...@bugs.debian.org: > severity 526737 important Bug#526737: md: RAID 1 check makes kernel almost panic Severity set to `important' from `critical' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526737: marked as done (md: RAID 1 check makes kernel almost panic)
Your message dated Sun, 3 May 2009 10:19:29 +0200
with message-id <20090503081929.gc11...@piper.oerlikon.madduck.net>
and subject line Re: Bug#526737: md: RAID 1 check makes kernel almost panic
has caused the Debian Bug report #526737,
regarding md: RAID 1 check makes kernel almost panic
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 ow...@bugs.debian.org
immediately.)
--
526737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.29-1-amd64
Version: 2.6.29-3
Severity: critical
Today was the normal crondate for mdadm to run a check on my 2 raid 1
devices.
Problem, when I woke up this morning I found very bad stuff on my
terminals.
The check was stuck at 2% according to /proc/mdstat. I tried to run it
again, but that caused the second backtrace you can see below.
Now, I cannot even check the RAID status since "cat /proc/mdstat" hangs.
% strace cat /proc/mdstat
[...]
open("/proc/mdstat", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3,
-- Package-specific info:
** Version:
Linux version 2.6.29-1-amd64 (Debian 2.6.29-2) (wa...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-5) ) #1 SMP Sat Apr 4 16:54:07 UTC 2009
** Command line:
root=/dev/mapper/system-root ro vga=791 splash
** Tainted: P D (129)
** Kernel log:
[1404264.039924] md: data-check of RAID array md0
[1404264.039927] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[1404264.039930] md: using maximum available idle IO bandwidth (but not more
than 20 KB/sec) for data-check.
[1404264.039934] md: using 128k window, over a total of 48064 blocks.
[1404264.042298] general protection fault: [#1] SMP
[1404264.042302] last sysfs file: /sys/devices/virtual/block/md1/md/sync_action
[1404264.042304] CPU 0
[1404264.042306] Modules linked in: rfcomm l2cap bluetooth nvidia(P) ipv6
acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace
cpufreq_conservative nfs lockd nfs_acl auth_rpcgss sunrpc coretemp w83627ehf
hwmon_vid firewire_sbp2 loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec
snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device
i2c_i801 snd soundcore snd_page_alloc i2c_core pcspkr serio_raw evdev button
ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod raid1
md_mod hid_logitech ff_memless usbhid hid sd_mod crc_t10dif ide_cd_mod cdrom
ata_generic uhci_hcd ide_pci_generic ata_piix firewire_ohci firewire_core
crc_itu_t ahci atl1 mii libata jmicron ide_core scsi_mod ehci_hcd intel_agp
thermal processor fan thermal_sys
[1404264.042363] Pid: 32532, comm: md0_resync Tainted: P
2.6.29-1-amd64 #1 P5K
[1404264.042365] RIP: 0010:[] []
put_page+0xb/0xbb
[1404264.042371] RSP: :88008bf67be0 EFLAGS: 00010202
[1404264.042374] RAX: 88008c488680 RBX: RCX:
0002
[1404264.042376] RDX: 0006 RSI: RDI:
01003531204f544f
[1404264.042378] RBP: 01003531204f544f R08: 0008 R09:
880028101080
[1404264.042380] R10: 0002 R11: 0002 R12:
88009af747c0
[1404264.042383] R13: 88013bda2c20 R14: 00011200 R15:
88013b956c00
[1404264.042385] FS: () GS:806c1000()
knlGS:
[1404264.042388] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
[1404264.042390] CR2: 7f7a97d694f8 CR3: b2bdc000 CR4:
06e0
[1404264.042392] DR0: DR1: DR2:
[1404264.042394] DR3: DR6: 4ff0 DR7:
0400
[1404264.042397] Process md0_resync (pid: 32532, threadinfo 88008bf66000,
task 880096127730)
[1404264.042399] Stack:
[1404264.042400] 0010 88009af747c0
88013bda2c20
[1404264.042404] 00011200 a016bcbd 88008c2de7c8
8800b2103240
[1404264.042408] 88008bf67e7c 00011210 88008bf67c60
88008bf67c78
[1404264.042412] Call Trace:
[1404264.042415] [] ? r1buf_pool_alloc+0x121/0x16f [raid1]
[1404264.042421] [] ? mempool_alloc+0x3f/0xf5
[1404264.042425] [] ? _spin_lock_irq+0xd/0xf
[1404264.042430] [] ? raise_barrier+0x179/0x18f [raid1]
[1404264.042434] [] ? try_to_wake_up+0x1b0/0x1c2
[1404264.042439] [] ? scsi_request_fn+0x41b/0x4e9 [scsi_mod]
[1404264.042457] [] ? sync_request+0x195/0x519 [raid1]
[1404264.042462] [] ? is_mddev_idle+0xa3/0xf5 [md_mod]
[1404264.042472] [] ? md_do_sync+0x5d0/0x
Bug#526737: md: RAID 1 check makes kernel almost panic
Package: linux-image-2.6.29-1-amd64
Version: 2.6.29-3
Severity: critical
Today was the normal crondate for mdadm to run a check on my 2 raid 1
devices.
Problem, when I woke up this morning I found very bad stuff on my
terminals.
The check was stuck at 2% according to /proc/mdstat. I tried to run it
again, but that caused the second backtrace you can see below.
Now, I cannot even check the RAID status since "cat /proc/mdstat" hangs.
% strace cat /proc/mdstat
[...]
open("/proc/mdstat", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3,
-- Package-specific info:
** Version:
Linux version 2.6.29-1-amd64 (Debian 2.6.29-2) (wa...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-5) ) #1 SMP Sat Apr 4 16:54:07 UTC 2009
** Command line:
root=/dev/mapper/system-root ro vga=791 splash
** Tainted: P D (129)
** Kernel log:
[1404264.039924] md: data-check of RAID array md0
[1404264.039927] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[1404264.039930] md: using maximum available idle IO bandwidth (but not more
than 20 KB/sec) for data-check.
[1404264.039934] md: using 128k window, over a total of 48064 blocks.
[1404264.042298] general protection fault: [#1] SMP
[1404264.042302] last sysfs file: /sys/devices/virtual/block/md1/md/sync_action
[1404264.042304] CPU 0
[1404264.042306] Modules linked in: rfcomm l2cap bluetooth nvidia(P) ipv6
acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace
cpufreq_conservative nfs lockd nfs_acl auth_rpcgss sunrpc coretemp w83627ehf
hwmon_vid firewire_sbp2 loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec
snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device
i2c_i801 snd soundcore snd_page_alloc i2c_core pcspkr serio_raw evdev button
ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod raid1
md_mod hid_logitech ff_memless usbhid hid sd_mod crc_t10dif ide_cd_mod cdrom
ata_generic uhci_hcd ide_pci_generic ata_piix firewire_ohci firewire_core
crc_itu_t ahci atl1 mii libata jmicron ide_core scsi_mod ehci_hcd intel_agp
thermal processor fan thermal_sys
[1404264.042363] Pid: 32532, comm: md0_resync Tainted: P
2.6.29-1-amd64 #1 P5K
[1404264.042365] RIP: 0010:[] []
put_page+0xb/0xbb
[1404264.042371] RSP: :88008bf67be0 EFLAGS: 00010202
[1404264.042374] RAX: 88008c488680 RBX: RCX:
0002
[1404264.042376] RDX: 0006 RSI: RDI:
01003531204f544f
[1404264.042378] RBP: 01003531204f544f R08: 0008 R09:
880028101080
[1404264.042380] R10: 0002 R11: 0002 R12:
88009af747c0
[1404264.042383] R13: 88013bda2c20 R14: 00011200 R15:
88013b956c00
[1404264.042385] FS: () GS:806c1000()
knlGS:
[1404264.042388] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
[1404264.042390] CR2: 7f7a97d694f8 CR3: b2bdc000 CR4:
06e0
[1404264.042392] DR0: DR1: DR2:
[1404264.042394] DR3: DR6: 4ff0 DR7:
0400
[1404264.042397] Process md0_resync (pid: 32532, threadinfo 88008bf66000,
task 880096127730)
[1404264.042399] Stack:
[1404264.042400] 0010 88009af747c0
88013bda2c20
[1404264.042404] 00011200 a016bcbd 88008c2de7c8
8800b2103240
[1404264.042408] 88008bf67e7c 00011210 88008bf67c60
88008bf67c78
[1404264.042412] Call Trace:
[1404264.042415] [] ? r1buf_pool_alloc+0x121/0x16f [raid1]
[1404264.042421] [] ? mempool_alloc+0x3f/0xf5
[1404264.042425] [] ? _spin_lock_irq+0xd/0xf
[1404264.042430] [] ? raise_barrier+0x179/0x18f [raid1]
[1404264.042434] [] ? try_to_wake_up+0x1b0/0x1c2
[1404264.042439] [] ? scsi_request_fn+0x41b/0x4e9 [scsi_mod]
[1404264.042457] [] ? sync_request+0x195/0x519 [raid1]
[1404264.042462] [] ? is_mddev_idle+0xa3/0xf5 [md_mod]
[1404264.042472] [] ? md_do_sync+0x5d0/0x9bb [md_mod]
[1404264.042480] [] ? md_thread+0xe5/0x103 [md_mod]
[1404264.042488] [] ? __wake_up_common+0x44/0x73
[1404264.042492] [] ? md_thread+0x0/0x103 [md_mod]
[1404264.042499] [] ? md_thread+0x0/0x103 [md_mod]
[1404264.042507] [] ? kthread+0x47/0x73
[1404264.042510] [] ? child_rip+0xa/0x20
[1404264.042514] [] ? cap_capable+0x0/0x1c
[1404264.042518] [] ? kthread+0x0/0x73
[1404264.042521] [] ? child_rip+0x0/0x20
[1404264.042523] Code: fe ff ff f0 80 23 fb eb 09 80 e1 04 75 04 f0 80 0b 04 5b
c3 48 c7 c7 c4 7e 29 80 e9 5d c2 fb ff 41 56 41 55 41 54 55 48 89 fd 53 <48> 8b
07 f6 c4 60 74 2d f6 c4 40 74 04 48 8b 6f 10 48 8d 45 08
[1404264.042552] RIP [] put_page+0xb/0xbb
[1404264.042556] RSP
[1404264.042558] ---[ end trace 68cadf7f004fcdc7 ]---
[1404264.066775] md: delaying data-check of md1 until md0 has finished (they
share one or more physical units
