Bug#620331: linux-2.6: igb driver fix for management card detection
b...@decadent.org.uk wrote on 04/03/2011 06:06:24 AM: Hi Ben, This can lead to a loss of network connectivity for the host and/or the management card eventually. How does the host lose connectivity? I'm somewhat wary of cherry-picking such a patch without a very good reason. Interactions with Lights Out Management seem to be particularly prone to regression. In this specific case, the host isn't actually affected; only the MC can lose connectivity if the driver doesn't detect the MC due to this bug and powers down/resets the interface when it shouldn't. Bugs that led to the host losing connectivity were fixed in or before 2.6.32. This patch is entirely safe to apply, per 82575 documentation and the fact that it comes straight from Intel ;) Thanks, JB. -- Consultant INTM - Debian Developer - TMI Calibre EDF - DSP - CSP IT - ITS Rhône Alpes - C4S - CCNPS 04 69 65 68 56 Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message. Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus. This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message. E-mail communication cannot be guaranteed to be timely secure, error or virus-free. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/of3d6a7d69.8bee67a7-onc1257868.0024a180-c1257868.00252...@notes.edfgdf.fr
Bug#518643: Same problem found in 2.6.26-2-amd64
Hi Moritz, We changed the machine to Proxmox a month ago, which is Debian-based but sports a custom updated kernel. Our original installation had three similar lockups with lennys kernel but we haven't experiencied such problems with proxmox kernels, so I think the problem has been fixed in Kvm. Thanks! Eneko El vie, 01-04-2011 a las 21:44 +0200, Moritz Mühlenhoff escribió: tags 518643 moreinfo thanks On Fri, Aug 14, 2009 at 09:13:53AM +0200, Eneko Lacunza wrote: Hi, We experienced a similar lockup tonight. Sorry for the late reply. The KVM version from Lenny is very old. Did you upgrade to something more recent since then, e.g. to Debian 6.0 (Squeeze)? Cheers, Moritz -- Zuzendari Teknikoa / Director Técnico Binovo IT Human Project, S.L. Telf. 943493611 Astigarraga bidea 2, planta 2 dcha., ofi. 10; 20180 Oiartzun (Gipuzkoa) www.binovo.es -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301902995.3073.2.camel@elacunza-laptop
Bug#619034: [alsa-devel] Problems with snd_hda_intel in Linux kernel 2.6.38
On Thu, 2011-03-31 at 00:42 +0200, Svante Signell wrote: On Wed, 2011-03-30 at 15:13 +0200, Clemens Ladisch wrote: Svante Signell wrote: Code: f4 01 00 00 ef 31 f6 48 89 df e8 15 dd ff ff 85 c0 0f 88 2b 03 00 00 48 89 ef e8 ee 11 b9 e0 8b 7b 40 e8 9f 25 a7 e0 48 8b 43 38 66 8b 10 66 89 14 24 8b 43 14 83 e8 03 83 f8 01 77 32 31 d2 be 5: 31 f6 xor%esi,%esi 7: 48 89 dfmov%rbx,%rdi a: e8 15 dd ff ff callq 0xdd24 f: 85 c0 test %eax,%eax 11: 0f 88 2b 03 00 00 js 0x342 17: 48 89 efmov%rbp,%rdi 1a: e8 ee 11 b9 e0 callq 0xe0b9120d 1f: 8b 7b 40mov0x40(%rbx),%edi 22: e8 9f 25 a7 e0 callq 0xe0a725c6 27: 48 8b 43 38 mov0x38(%rbx),%rax 2b: 66 8b 10mov(%rax),%dx -- crash here 2e: 66 89 14 24 mov%dx,(%rsp) 32: 8b 43 14mov0x14(%rbx),%eax 35: 83 e8 03sub$0x3,%eax 38: 83 f8 01cmp$0x1,%eax 3b: 77 32 ja 0x6f 3d: 31 d2 xor%edx,%edx This is the azx_readw(chip, GCAP) in azx_create(); chip-remap_addr is 0xc90011c08000 which does look like a valid pointer, but isn't. Thank you Clemens! Maybe your input is sufficient to solve this problem. I have now installed the debug version of the kernel, the objdump output is attached (please let me know if you are missing something).sorry, I don't know where to find the relevant information in this file, but that is all I have (still very large). (Does not include the error messages on stderr, maybe something is still missing.) Anything happening here with respect to this bug? How can I help further? Booting with 2.6.32 all the time does not feel lika a good solution in long term. A small except from the objdump output below. The complete file is too big (400k) for the mailing list. Let me know if more is needed. 56c: be 01 00 00 00 mov$0x1,%esi 571: 48 89 efmov%rbp,%rdi 574: e8 00 00 00 00 callq 579 azx_probe+0x37c 579: 85 c0 test %eax,%eax 57b: 79 07 jns584 azx_probe+0x387 57d: 80 a3 f4 01 00 00 efandb $0xef,0x1f4(%rbx) 584: 31 f6 xor%esi,%esi 586: 48 89 dfmov%rbx,%rdi 589: e8 00 00 00 00 callq 58e azx_probe+0x391 58e: 85 c0 test %eax,%eax 590: 0f 88 2b 03 00 00 js 8c1 azx_probe+0x6c4 596: 48 89 efmov%rbp,%rdi 599: e8 00 00 00 00 callq 59e azx_probe+0x3a1 59e: 8b 7b 40mov0x40(%rbx),%edi 5a1: e8 00 00 00 00 callq 5a6 azx_probe+0x3a9 5a6: 48 8b 43 38 mov0x38(%rbx),%rax 5aa: 66 8b 10mov(%rax),%dx - crash here 5ad: 66 89 14 24 mov%dx,(%rsp) 5b1: 8b 43 14mov0x14(%rbx),%eax 5b4: 83 e8 03sub$0x3,%eax 5b7: 83 f8 01cmp$0x1,%eax 5ba: 77 32 ja 5ee azx_probe+0x3f1 5bc: 31 d2 xor%edx,%edx -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301906577.32453.92.ca...@s1499.it.kth.se
Bug#618473: New informations regarding this problem
During the weekend I've created a machine for testing which acts as nis server (and client of course) and I could see the same problem (without nfs, autofs and others). So I assume, that the nis package is responsible for this problem. The nis package is (output from dpkg -l nis): ii nis 3.17-31 clients and daemons for the Network Information Service (NIS) I could also see another problem with the nis package: If I try to do 'dpkg-reconfigure nis' I receive the following message: dpkg: version 'nis_3.17-18' has bad syntax: invalid character in version number Hope this helps Christian -- Name: Christian Andretzky | Address: TU Chemnitz, Fakultaet fuer | Phone: ++49 +371 531 32130 | Elektrotechnik/Informationstechnik | FAX: ++49 +371 531 832130 | Reichenhainer Str. 70| mail: christian.andret...@mb.tu-chemnitz.de | D-09107 Chemnitz| PGP: public key avaliable via public key server | In a world without walls and fences, there is no need for windows and gates | The Box said 'Windows XP or better'. - So I installed Linux. | -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d998259.5030...@mb.tu-chemnitz.de
Bug#613979: [alsa-devel] Problems with snd_hda_intel in Linux kernel 2.6.38
At Mon, 04 Apr 2011 10:42:57 +0200, Svante Signell wrote: On Thu, 2011-03-31 at 00:42 +0200, Svante Signell wrote: On Wed, 2011-03-30 at 15:13 +0200, Clemens Ladisch wrote: Svante Signell wrote: Code: f4 01 00 00 ef 31 f6 48 89 df e8 15 dd ff ff 85 c0 0f 88 2b 03 00 00 48 89 ef e8 ee 11 b9 e0 8b 7b 40 e8 9f 25 a7 e0 48 8b 43 38 66 8b 10 66 89 14 24 8b 43 14 83 e8 03 83 f8 01 77 32 31 d2 be 5: 31 f6 xor%esi,%esi 7: 48 89 dfmov%rbx,%rdi a: e8 15 dd ff ff callq 0xdd24 f: 85 c0 test %eax,%eax 11: 0f 88 2b 03 00 00 js 0x342 17: 48 89 efmov%rbp,%rdi 1a: e8 ee 11 b9 e0 callq 0xe0b9120d 1f: 8b 7b 40mov0x40(%rbx),%edi 22: e8 9f 25 a7 e0 callq 0xe0a725c6 27: 48 8b 43 38 mov0x38(%rbx),%rax 2b: 66 8b 10mov(%rax),%dx -- crash here 2e: 66 89 14 24 mov%dx,(%rsp) 32: 8b 43 14mov0x14(%rbx),%eax 35: 83 e8 03sub$0x3,%eax 38: 83 f8 01cmp$0x1,%eax 3b: 77 32 ja 0x6f 3d: 31 d2 xor%edx,%edx This is the azx_readw(chip, GCAP) in azx_create(); chip-remap_addr is 0xc90011c08000 which does look like a valid pointer, but isn't. Thank you Clemens! Maybe your input is sufficient to solve this problem. I have now installed the debug version of the kernel, the objdump output is attached (please let me know if you are missing something).sorry, I don't know where to find the relevant information in this file, but that is all I have (still very large). (Does not include the error messages on stderr, maybe something is still missing.) Anything happening here with respect to this bug? How can I help further? Booting with 2.6.32 all the time does not feel lika a good solution in long term. The point where it Oops implies that the problem isn't in the sound driver but rather in a breakage in a deeper level, either PCI core, x86 mm or ACPI/BIOS. Any chance to bisect the kernel? thanks, Takashi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/s5h8vvqv0r2.wl%ti...@suse.de
Bug#613979: [alsa-devel] Problems with snd_hda_intel in Linux kernel 2.6.38
On Mon, 2011-04-04 at 11:12 +0200, Takashi Iwai wrote: At Mon, 04 Apr 2011 10:42:57 +0200, Svante Signell wrote: On Thu, 2011-03-31 at 00:42 +0200, Svante Signell wrote: On Wed, 2011-03-30 at 15:13 +0200, Clemens Ladisch wrote: ... Anything happening here with respect to this bug? How can I help further? Booting with 2.6.32 all the time does not feel like a good solution in long term. The point where it Oops implies that the problem isn't in the sound driver but rather in a breakage in a deeper level, either PCI core, x86 mm or ACPI/BIOS. Any chance to bisect the kernel? Never done that before. Is there a bisect HOWTO somewhere? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301908906.32453.94.ca...@s1499.it.kth.se
Bug#620331: linux-2.6: igb driver fix for management card detection
On Mon, Apr 04, 2011 at 08:45:40AM +0200, Julien-externe BLACHE wrote: b...@decadent.org.uk wrote on 04/03/2011 06:06:24 AM: Hi Ben, This can lead to a loss of network connectivity for the host and/or the management card eventually. How does the host lose connectivity? I'm somewhat wary of cherry-picking such a patch without a very good reason. Interactions with Lights Out Management seem to be particularly prone to regression. In this specific case, the host isn't actually affected; only the MC can lose connectivity if the driver doesn't detect the MC due to this bug and powers down/resets the interface when it shouldn't. Bugs that led to the host losing connectivity were fixed in or before 2.6.32. This patch is entirely safe to apply, per 82575 documentation and the fact that it comes straight from Intel ;) So do many interesting regressions. I expect that at some point we'll want to update the driver to add new hardware support, and then we'll pick this up along the way. Until then, however, I'm not going to apply it. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404105824.gi2...@decadent.org.uk
Bug#620814: initramfs-tools: fails to include essential module for other leg of md0
Package: initramfs-tools
Version: 0.98.8
Severity: normal
(resending manually because exim hadn't been configured yet)
This is a new Wheezy install on an old server machine. The machine has four
PATA disks, tied to two controllers. The four disks are combined into a SW-raid
volume using mdadm:
ladmin@fury:/tmp$ sudo mdadm --detail /dev/md0|grep /dev/
/dev/md0:
0 8 360 active sync /dev/sdc4
1 8 521 active sync /dev/sdd4
2 842 active sync /dev/sda4
4 8 203 active sync /dev/sdb4
[ 1.145853] scsi0 : pata_sil680
[ 1.146143] scsi1 : pata_sil680
[ 1.147018] ata1: PATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb000 irq 23
[ 1.147085] ata2: PATA max UDMA/133 cmd 0xb800 ctl 0xb400 bmdma 0xb008 irq 23
[ 1.148407] scsi2 : pata_serverworks
[ 1.148835] scsi3 : pata_serverworks
[ 1.156965] ata3: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 1.157034] ata4: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
During installation, I configured initramfs-tools to determine the required
modules automatically, which resulted in a non-booting system (notice that
the sil680 module is missing):
ladmin@fury:/tmp$ lsinitramfs /boot/initrd.img-2.6.32-5-686 |grep ata
lib/udev/ata_id
lib/modules/2.6.38-2-686/kernel/drivers/ata
lib/modules/2.6.38-2-686/kernel/drivers/ata/ata_generic.ko
lib/modules/2.6.38-2-686/kernel/drivers/ata/pata_serverworks.ko
lib/modules/2.6.38-2-686/kernel/drivers/ata/libata.ko
As a workaround, I've now added both pata_ modules to /e/i-t/modules,
but that is about as far as my knowledge of initramfs-tools will go.
I'll be glad to try other suggestions, or provide more info.
--
(regarding the below: I apologize, I can get carried away sometimes...
I'll leave solving this up to you :)
From my reading of sh -x output, it appears that there is just one level too
much indirection going on. We have a
+ readlink -f /dev/mapper/fury-root
/dev/dm-0
Which finds the correct dm device. Following the trace,
+ ls -1 /sys/block/dm-0/slaves
+ block=md0
md0 is identified as the correct md device underlying the lvm VG. But this is
also where it breaks down; the sed expression following it reduces /proc/mdstat
to just a single block device:
+ block=sdc
[...]
+ readlink -f /sys/block/sdc/device
This code maps to dep_add_modules() in hook-functions, particularly the sed
expression on line 288 (preceded by comment lvm on md). The code surely
doesn't look like it's designed to handle more than one block device per
invocation, but that is probably what's needed here. It's trivial to modify
the sed expression to that end (replacing the last -e argument):
sed [...] -e 's/\[[0-9]\+\]//g' -e '/^'${block}' :/s/^[^[]*\[ //p'
But that still leaves the issue that the rest of the code expects $block to
only represent a single block device. At the very least, the #Error out and
# sys walk ATA code blocks (line 350+) would need a loop.
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 4.2M Apr 3 21:37 /boot/initrd.img-2.6.32-5-686
-rw-r--r-- 1 root root 4.3M Apr 3 21:37 /boot/initrd.img-2.6.38-2-686
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=/dev/mapper/fury-root ro
-- resume
RESUME=/dev/mapper/sda3_crypt
-- /proc/filesystems
btrfs
ext4
ext3
-- lsmod
Module Size Used by
ext3 98001 1
jbd40818 1 ext3
dm_mirror 17249 1
dm_region_hash 13072 1 dm_mirror
dm_log 13269 3 dm_mirror,dm_region_hash
loop 17805 0
sha256_generic 16709 8
aes_i586 16608 16
aes_generic37066 1 aes_i586
cbc12659 8
dm_crypt 17809 4
snd_pcm52774 0
snd_timer 22171 1 snd_pcm
ohci_hcd 21928 0
ehci_hcd 34889 0
snd38153 2 snd_pcm,snd_timer
usbcore99058 3 ohci_hcd,ehci_hcd
soundcore 12878 1 snd
snd_page_alloc 12841 1 snd_pcm
tpm_tis12949 0
tpm17454 1 tpm_tis
tg3 103807 0
pcspkr 12515 0
tpm_bios 12799 1 tpm
aic7xxx97720 0
i2c_piix4 12480 0
libphy 18279 1 tg3
evdev 13084 2
processor 26983 0
nls_base 12649 1 usbcore
i2c_core 18989 1 i2c_piix4
thermal_sys17667 1 processor
scsi_transport_spi 19032 1 aic7xxx
button 12866 0
ext4 251726 3
mbcache12810 2 ext3,ext4
jbd2 55701 1 ext4
crc16 12327 1 ext4
dm_mod 56394 37 dm_mirror,dm_log,dm_crypt
raid45651595 1
async_raid6_recov 12459 1
Bug#620814: initramfs-tools: fails to include essential module for other leg of md0
On Mon, Apr 04, 2011 at 01:28:15PM +0200, Arno Schuring wrote: Package: initramfs-tools Version: 0.98.8 Severity: normal (resending manually because exim hadn't been configured yet) This is a new Wheezy install on an old server machine. The machine has four PATA disks, tied to two controllers. The four disks are combined into a SW-raid volume using mdadm: ladmin@fury:/tmp$ sudo mdadm --detail /dev/md0|grep /dev/ /dev/md0: 0 8 360 active sync /dev/sdc4 1 8 521 active sync /dev/sdd4 2 842 active sync /dev/sda4 4 8 203 active sync /dev/sdb4 [ 1.145853] scsi0 : pata_sil680 [ 1.146143] scsi1 : pata_sil680 [ 1.147018] ata1: PATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb000 irq 23 [ 1.147085] ata2: PATA max UDMA/133 cmd 0xb800 ctl 0xb400 bmdma 0xb008 irq 23 [ 1.148407] scsi2 : pata_serverworks [ 1.148835] scsi3 : pata_serverworks [ 1.156965] ata3: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14 [ 1.157034] ata4: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15 During installation, I configured initramfs-tools to determine the required modules automatically, which resulted in a non-booting system (notice that the sil680 module is missing): [...] The initramfs-tools 'MODULES=dep' mode is primarily meant for small systems with limited RAM and disk space for the initramfs. The dependency detection code does not currently handle all module dependencies, as you see. I recommend using 'MODULES=most'. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404120804.gj2...@decadent.org.uk
Bug#620331: linux-2.6: igb driver fix for management card detection
b...@decadent.org.uk wrote on 04/04/2011 12:58:24 PM: Hi, I expect that at some point we'll want to update the driver to add new hardware support, and then we'll pick this up along the way. Until then, however, I'm not going to apply it. I don't understand your decision; upgrading the whole driver is actually a lot more likely to introduce regressions, seeing how this driver should be at the very least 2 different drivers. I've been working on the igb driver for 5 days, I've read every single upstream commit affecting igb since before 2.6.32 and I've read the 82575 manuals from cover to cover. If you want to see for yourself, Intel document ref. 324632-003, rev. 2.1 01/2011, pages 392-393 document the MANC register. And that'll be it as far as I'm concerned. JB. -- Consultant INTM - Debian Developer - TMI Calibre EDF - DSP - CSP IT - ITS Rhône Alpes - C4S - CCNPS 04 69 65 68 56 Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message. Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus. This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message. E-mail communication cannot be guaranteed to be timely secure, error or virus-free. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/of8a21b97a.d233715a-onc1257868.0041e9e0-c1257868.0042b...@notes.edfgdf.fr
Bug#620331: linux-2.6: igb driver fix for management card detection
On Mon, Apr 04, 2011 at 02:08:41PM +0200, Julien-externe BLACHE wrote: b...@decadent.org.uk wrote on 04/04/2011 12:58:24 PM: Hi, I expect that at some point we'll want to update the driver to add new hardware support, and then we'll pick this up along the way. Until then, however, I'm not going to apply it. I don't understand your decision; upgrading the whole driver is actually a lot more likely to introduce regressions, seeing how this driver should be at the very least 2 different drivers. It also results in a version that is closer to that tested by the upstream developers (and users of more recent distributions). I've been working on the igb driver for 5 days, I've read every single upstream commit affecting igb since before 2.6.32 and I've read the 82575 manuals from cover to cover. So have you verified that there are no earlier or later changes related to this? If you want to see for yourself, Intel document ref. 324632-003, rev. 2.1 01/2011, pages 392-393 document the MANC register. It is naive to believe anything in a hardware manual without testing it! I assume you have done that, though. Ben. And that'll be it as far as I'm concerned. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404121959.gl2...@decadent.org.uk
Bug#614326: bug still appears in 2.6.38-2
FYI, bug still happens with the latest 2.6.38.-2 kernel, so it definitely doesn't seem kernel related: [ 150.720026] [ cut here ] [ 150.720040] WARNING: at /tmp/buildd/linux-aptosid-2.6-2.6.38/debian/build/source_amd64_none/net/sched/sch_generic.c:256 dev_watchdog+0x25b/0x270() [ 150.720043] Hardware name: System Product Name [ 150.720046] NETDEV WATCHDOG: eth1 (asix): transmit queue 0 timed out [ 150.720048] Modules linked in: vboxnetadp vboxnetflt nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ppdev lp ipt_REJECT ipt_ULOG xt_limit xt_state ipt_REDIRECT xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack sco nf_defrag_ipv4 bnep rfcomm l2cap crc16 bluetooth rfkill ipx p8023 iptable_filter ip_tables x_tables capifs ntfs nls_utf8 nls_cp437 vfat fat ext3 jbd mbcache xfs exportfs vboxdrv psmouse powernow_k8 freq_table mperf hwmon_vid eeprom fuse dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek lgdt330x snd_hda_intel cx88_dvb cx88_vp3054_i2c videobuf_dvb dvb_core radeon ir_kbd_i2c rtc_isl1208 snd_hda_codec tuner_simple tuner_types snd_seq_dummy snd_hwdep sp5100_tco snd_pcm_oss snd_mixer_oss snd_seq_oss tda9887 tda8290 tuner snd_seq_midi ttm asix ir_lirc_codec lirc_dev ir_sony_decoder ir_jvc_decoder ir_rc6_decoder cx88_alsa cx8802 ir_rc5_decoder cx8800 ir_nec_decoder cx88xx rc_core snd_rawmidi tveeprom snd_seq_midi_event snd_pcm drm_kms_helper i2c_piix4 usbnet v4l2_common snd_seq videodev v4l2_compat_ioctl32 videobuf_dma_sg tpm_tis drm tpm i2c_algo_bit btcx_risc videobuf_core i2c_core shpchp pci_hotplug tpm_bios amd64_edac_mod edac_core pcspkr k8temp edac_mce_amd evdev snd_timer snd_seq_device rtc_cmos snd rtc_core rtc_lib asus_atk0110 soundcore snd_page_alloc parport_pc wmi button parport processor reiserfs raid1 md_mod dm_mirror dm_region_hash dm_log dm_mod sg sr_mod cdrom sd_mod usbhid crc_t10dif hid ata_generic ahci r8169 pata_acpi ohci_hcd ssb ehci_hcd libahci firewire_ohci usbcore mii mmc_core pata_atiixp pcmcia libata firewire_core crc_itu_t floppy scsi_mod pcmcia_core nls_base [last unloaded: scsi_wait_scan] [ 150.720170] Pid: 0, comm: kworker/0:0 Not tainted 2.6.38-2.slh.2-aptosid-amd64 #1 [ 150.720173] Call Trace: [ 150.720175] IRQ [81051b4b] ? warn_slowpath_common+0x7b/0xc0 [ 150.720185] [81051c45] ? warn_slowpath_fmt+0x45/0x50 [ 150.720190] [811dc22f] ? strlcpy+0x3f/0x50 [ 150.720194] [812ee79b] ? dev_watchdog+0x25b/0x270 [ 150.720197] [81047c53] ? get_nohz_timer_target+0x53/0xa0 [ 150.720202] [8105e7e0] ? mod_timer+0x130/0x220 [ 150.720206] [8105dfc0] ? run_timer_softirq+0x130/0x250 [ 150.720209] [812ee540] ? dev_watchdog+0x0/0x270 [ 150.720212] [81057c18] ? __do_softirq+0x98/0x120 [ 150.720217] [8100ccdc] ? call_softirq+0x1c/0x30 [ 150.720220] [8100eef5] ? do_softirq+0x65/0xa0 [ 150.720223] [81057d95] ? irq_exit+0x95/0xa0 [ 150.720228] [81027c2a] ? smp_apic_timer_interrupt+0x6a/0xa0 [ 150.720231] [8100c793] ? apic_timer_interrupt+0x13/0x20 [ 150.720233] EOI [8102fd82] ? native_safe_halt+0x2/0x10 [ 150.720242] [8107314c] ? __atomic_notifier_call_chain+0x4c/0x70 [ 150.720246] [81015013] ? default_idle+0x23/0x40 [ 150.720248] [81015084] ? c1e_idle+0x54/0x110 [ 150.720253] [8100a1e6] ? cpu_idle+0x56/0xa0 [ 150.720256] ---[ end trace a5ad661b39f55810 ]--- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404081608.16...@web013.roc2.bluetie.com
Bug#620814: initramfs-tools: fails to include essential module for other leg of md0
Hi Ben, During installation, I configured initramfs-tools to determine the required modules automatically, which resulted in a non-booting system (notice that the sil680 module is missing): [...] The initramfs-tools 'MODULES=dep' mode is primarily meant for small systems with limited RAM and disk space for the initramfs. The dependency detection code does not currently handle all module dependencies, as you see. I recommend using 'MODULES=most'. But MODULES=most is exactly what is set: -- /etc/initramfs-tools/initramfs.conf MODULES=most Regards, Arno -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/snt108-w200a41ec816f1e33f7649eb8...@phx.gbl
Re: [gNewSense-users] Suitability of the Debian Squeeze (and later) Linux kernel for gNewSense. Was (no subject)
On Thu, 31 Mar 2011 20:52:39 +0100 Michael Dorrington michael.dorring...@gmail.com wrote: Karl Goetz wrote: On Tue, 29 Mar 2011 11:42:41 -0300 Emiliano M. Rudenick emilianoruden...@gmail.com wrote: We don't have a free kernel in the archive yet, but you could easily install linux-libre of your own accord. thanks, kk The kernel that comes default in Debian Squeeze is completely free. The kernel produced by linux-libre, and the kernel produced by debian differ. This doesn't inherantly mean debians kernel is meant to be non-free, but it does mean there is some confusion between the projects which will have to be worked out. If we can use debians kernel unaltered thats fantastic, but i'm still trying to find someone who knows kernels (not me) to compare them and tell us if thats ok. thanks, kk Hi mike, thanks for the reply. AFAICT, the Debian kernel complies with the DFSG (or is extremely close). However, it retains drivers that require a firmware in order to be functional and where no free firmware currently exists for them. So if you don't considered Debian to be a Free GNU/Linux distribution then, I think, you won't considered the Debian kernel to be suitable for gNewSense. Does this mean 'retained in tree', or is it the stuff with no free firmware in the non-free packages? thanks, kk -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian contributor / gNewSense Maintainer http://www.kgoetz.id.au No, I won't join your social networking group signature.asc Description: PGP signature
Bug#620835: linux-image-2.6.37-2-686: kernel BUG in intel_tv_detect_type
Package: linux-2.6
Version: 2.6.37-2
Severity: normal
Here's a backtrace of a NULL pointer dereference in 2.6.37-2-686 on a
machine with an intel chipset. This machine (an Asus EeePC 900) has
no physical TV connector. The machine is regularly suspended to RAM,
and gets different external VGA monitors plugged in (and sometimes
operates only with the LVDS). At the time of the Oops, the machine
was operated with no external monitor.
Apr 1 11:25:39 localhost kernel: imklog 5.7.8, log source = /proc/kmsg started.
Apr 1 11:25:39 localhost kernel: [0.00] Initializing cgroup subsys
cpuset
Apr 1 11:25:39 localhost kernel: [0.00] Initializing cgroup subsys cpu
Apr 1 11:25:39 localhost kernel: [0.00] Linux version 2.6.37-2-686
(Debian 2.6.37-2) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-11) )
#1 SMP Sun Feb 27 10:51:32 UTC 2011
[...]
Apr 1 20:21:53 localhost kernel: [30919.095086] BUG: unable to handle kernel
NULL pointer dereference at 0100
Apr 1 20:21:53 localhost kernel: [30919.095094] IP: [f930d019]
intel_tv_detect_type+0xa2/0x203 [i915]
Apr 1 20:21:53 localhost kernel: [30919.095125] *pde =
Apr 1 20:21:53 localhost kernel: [30919.095130] Oops: [#1] SMP
Apr 1 20:21:53 localhost kernel: [30919.095135] last sysfs file:
/sys/devices/pci:00/:00:02.0/drm/card0/card0-SVIDEO-1/status
Apr 1 20:21:53 localhost kernel: [30919.095142] Modules linked in: arc4 ecb
pl2303 usbserial sco bnep l2cap crc16 bluetooth binfmt_misc uinput fuse ath5k
ath mac80211 cfg80211 loop snd_hda_codec_realtek joydev snd_hda_intel
snd_hda_codec i915 snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm drm_kms_helper
snd_seq_midi drm snd_rawmidi snd_seq_midi_event snd_seq i2c_algo_bit uvcvideo
snd_timer snd_seq_device snd videodev eeepc_laptop psmouse v4l1_compat
sparse_keymap i2c_core rfkill tpm_tis video tpm evdev processor shpchp rng_core
tpm_bios ac serio_raw output battery soundcore pci_hotplug power_supply
snd_page_alloc button ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc
dm_crypt dm_mod raid1 md_mod usb_storage uas sd_mod crc_t10dif ata_generic ahci
libahci ata_piix libata uhci_hcd ehci_hcd scsi_mod usbcore thermal atl2
thermal_sys nls_base [last unloaded: scsi_wait_scan]
Apr 1 20:21:53 localhost kernel: [30919.095238]
Apr 1 20:21:53 localhost kernel: [30919.095243] Pid: 2866, comm: upowerd Not
tainted 2.6.37-2-686 #1 ASUSTeK Computer INC. 900/900
Apr 1 20:21:53 localhost kernel: [30919.095253] EIP: 0060:[f930d019] EFLAGS:
00010246 CPU: 0
Apr 1 20:21:53 localhost kernel: [30919.095273] EIP is at
intel_tv_detect_type+0xa2/0x203 [i915]
Apr 1 20:21:53 localhost kernel: [30919.095278] EAX: EBX: f7112000
ECX: f9668004 EDX: 00068004
Apr 1 20:21:53 localhost kernel: [30919.095284] ESI: f72fb800 EDI: 000c0c37
EBP: f711229c ESP: f1231e2c
Apr 1 20:21:53 localhost kernel: [30919.095289] DS: 007b ES: 007b FS: 00d8
GS: 00e0 SS: 0068
Apr 1 20:21:53 localhost kernel: [30919.095295] Process upowerd (pid: 2866,
ti=f123 task=f72d74d0 task.ti=f123)
Apr 1 20:21:53 localhost kernel: [30919.095299] Stack:
Apr 1 20:21:53 localhost kernel: [30919.095302] f9317da4 7000 000c0c30
f72fbc00 f1231e54 f1231f24 f72fb800
Apr 1 20:21:53 localhost kernel: [30919.095312] f930d203 0100 0003
4353544e
Apr 1 20:21:53 localhost kernel: [30919.095321] 30383420 0069
Apr 1 20:21:53 localhost kernel: [30919.095331] Call Trace:
Apr 1 20:21:53 localhost kernel: [30919.095354] [f930d203] ?
intel_tv_detect+0x89/0x12d [i915]
Apr 1 20:21:53 localhost kernel: [30919.095376] [f9203cef] ?
status_show+0x0/0x2f [drm]
Apr 1 20:21:53 localhost kernel: [30919.095392] [f9203d03] ?
status_show+0x14/0x2f [drm]
Apr 1 20:21:53 localhost kernel: [30919.095403] [c11c390a] ?
dev_attr_show+0x16/0x32
Apr 1 20:21:53 localhost kernel: [30919.095413] [c10fc020] ?
sysfs_read_file+0x8c/0xf5
Apr 1 20:21:53 localhost kernel: [30919.095420] [c10fbf94] ?
sysfs_read_file+0x0/0xf5
Apr 1 20:21:53 localhost kernel: [30919.095429] [c10ba3aa] ?
vfs_read+0x7c/0xd6
Apr 1 20:21:53 localhost kernel: [30919.095436] [c10b8a34] ?
do_sys_open+0xb5/0xbe
Apr 1 20:21:53 localhost kernel: [30919.095443] [c10ba497] ?
sys_read+0x3c/0x60
Apr 1 20:21:53 localhost kernel: [30919.095451] [c1002f9f] ?
sysenter_do_call+0x12/0x28
Apr 1 20:21:53 localhost kernel: [30919.095455] Code: d8 e8 30 f8 ff ff ba 04
80 06 00 89 d8 8b 4c 24 0c 81 c9 aa 00 00 0f e8 1a f8 ff ff ba 04 80 06 00 89
d8 e8 ea f7 ff ff 8b 46 20 8b 90 00 01 00 00 8b 06 e8 40 11 ff ff b8 14 00 00
00 8b 35 40
Apr 1 20:21:53 localhost kernel: [30919.095500] EIP: [f930d019]
intel_tv_detect_type+0xa2/0x203 [i915] SS:ESP 0068:f1231e2c
Apr 1 20:21:53 localhost kernel: [30919.095523] CR2: 0100
Apr 1 20:21:53 localhost kernel: [30919.095528] ---[ end trace
63beda03e83c9f6c ]---
Processed: bug 620374 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=35936
Processing commands for cont...@bugs.debian.org: forwarded 620374 https://bugs.freedesktop.org/show_bug.cgi?id=35936 Bug #620374 [linux-2.6] linux-image-2.6.38-2-686: booting 2.6.38-2-686 fails during gdm login with: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=35936'. thanks Stopping processing here. Please contact me if you need assistance. -- 620374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130192806716542.transcr...@bugs.debian.org
Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable kernel BUG at fs/jbd2/commit.c:534 from Postfix on ext4
On Apr 02, 2011, at 22:02, Ted Ts'o wrote: Sorry for not following up sooner. Are you still able to reproduce this failure? If I set up an identical Debian stable instance on EC-2, am I likely to reproduce it myself? Do you have a package list or EC2 base image I can use as a starting point? I'll need to check on this. Unfortunately it was not a trivial process to install Debian squeeze onto an EC2 instance; it took a couple ugly Perl scripts, a patched Debian-Installer, and several manual post-install-but-before-reboot steps (like fixing up GRUB 0.99). One of these days I may get time to update all that to the official wheezy release and submit bug reports. I have an exact image of the failing instance, but it has proprietary data on it and if I stand up an old copy I need to be careful not to actually let it send all the queued emails :-D. It's probably easier for me to halt email delivery and clone the working instance and try to reproduce from there. If I recall, the (easily undone) workaround was to remount from data=journal to data=ordered on a couple filesystems. It may take a day or two to get this done, though. If it comes down to it I also have a base image (from squeeze as of 9 months ago) that could be made public after updating with new SSH keys. Thanks again! Cheers, Kyle Moffett -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/15e8241a-37a0-4438-849e-a157a376c...@boeing.com
Re: [gNewSense-users] Suitability of the Debian Squeeze (and later) Linux kernel for gNewSense. Was (no subject)
On Mon, Apr 04, 2011 at 09:51:16PM +0930, Karl Goetz wrote: On Thu, 31 Mar 2011 20:52:39 +0100 Michael Dorrington michael.dorring...@gmail.com wrote: [...] AFAICT, the Debian kernel complies with the DFSG (or is extremely close). However, it retains drivers that require a firmware in order to be functional and where no free firmware currently exists for them. So if you don't considered Debian to be a Free GNU/Linux distribution then, I think, you won't considered the Debian kernel to be suitable for gNewSense. Does this mean 'retained in tree', or is it the stuff with no free firmware in the non-free packages? Practically all modern peripherals run firmware, usually loaded from EEPROM or flash, and almost always non-free. So the question is not whether a driver relies on non-free firmware but whether that firmware is required to be installed in the host filesystem and loaded via the driver. The drivers included in upstream kernel releases that load non-free firmware are retained as part of the linux-2.6 source package and most of them are included in the binary packages. (Some are excluded due to quality considerations or because they rely on firmware embedded within the driver, which we remove.) If we were to package these drivers separately, they would belong in the 'contrib' archive section (free software with non-free or unpackaged dependencies). Since we do not, and since the kernel in general does not have non-free dependencies, these drivers remain in the 'main' archive section. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404151937.go2...@decadent.org.uk
Bug#620835: linux-image-2.6.37-2-686: kernel BUG in intel_tv_detect_type
On Tue, Apr 05, 2011 at 05:46:01AM -0400, Daniel Kahn Gillmor wrote: Package: linux-2.6 Version: 2.6.37-2 [...] Please test 2.6.38-2. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404152036.gp2...@decadent.org.uk
Bug#620835: linux-image-2.6.37-2-686: kernel BUG in intel_tv_detect_type
On 04/04/2011 11:20 AM, Ben Hutchings wrote: On Tue, Apr 05, 2011 at 05:46:01AM -0400, Daniel Kahn Gillmor wrote: Package: linux-2.6 Version: 2.6.37-2 [...] Please test 2.6.38-2. i'm currently running 2.6.38-2, and i have not yet seen this particular bug (NULL dereference in intel_tv_detect_type). otoh, I only saw this bug after running with 2.6.37-2 since March 5th (nearly a month). So it's hard for me to say that switching to 2.6.38-2 fixed things. --dkg signature.asc Description: OpenPGP digital signature
Bug#516785: linux-image-2.6.26-1-sparc64-smp: [sparc] SunFire480R cassini network driver kernel panic
On Fri, Apr 01, 2011 at 09:42:06PM +0200, Moritz M?hlenhoff wrote: On Mon, Mar 01, 2010 at 12:30:05PM +0100, Hermann Lauer wrote: On Wed, Jan 13, 2010 at 09:29:25AM +0100, Hermann Lauer wrote: I tried again with vanilla 2.6.32 (2.6.27-2.6.31 are unusable due to a kernel memory corruption bug), the driver is still crashing my Sunfire V480R. Tried today vanilla 2.6.33, then did a: # modprobe -v cassini cassini_debug=-1 insmod /lib/modules/2.6.33/kernel/drivers/net/cassini.ko cassini_debug=-1 In kern.log the messages appeared: Mar 1 12:17:14 tantalus kernel: cassini.c:v1.6 (21 May 2008) Mar 1 12:17:14 tantalus kernel: PCI: Enabling device: (0002:00:02.0), cmd 146 Mar 1 12:17:15 tantalus kernel: cassini: MAC address not found in ROM VPD Mar 1 12:17:15 tantalus kernel: eth0: Sun Cassini+ (64bit/33MHz PCI/Cu) Ethernet[24] 08:00:20:cb:31:01 Mar 1 12:17:15 tantalus kernel: PCI: Enabling device: (0003:00:01.0), cmd 146 Mar 1 12:17:15 tantalus kernel: cassini: MAC address not found in ROM VPD Mar 1 12:17:15 tantalus kernel: udev: renamed network interface eth0 to eth15 Mar 1 12:17:15 tantalus kernel: eth0: Sun Cassini+ (64bit/66MHz PCI/Cu) Ethernet[30] 08:00:20:bc:c7:b7 Mar 1 12:17:15 tantalus kernel: udev: renamed network interface eth0 to eth16 Mar 1 12:20:48 tantalus kernel: eth15: Link up at 1000 Mbps, full-duplex. Mar 1 12:20:48 tantalus kernel: eth15: TX pause enabled Mar 1 12:20:59 tantalus kernel: eth15: no IPv6 routers present As before, setting up the interface with ifconfig works. After sending out 68 pings the machine crashed with the usual Hardware FATAL RESET. What can be done to debug this further ? Is this fixed in later kernels, e.g. the 2.6.38 from Debian unstable? If so and the fix can be isolated we can fix it in 2.6.32 for Squeeze. Unfortunately squeeze provided kernels are not booting on V880/V480 systems (hangs at boot, log files are available on request). Will try install boots from testing when time permits. Or are there other tftpbootable images I could/should try ? Thats the major issue here at the moment, cassini has to wait... Thanks for caring, Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: hermann.la...@iwr.uni-heidelberg.de -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404151709.gc10...@lemon.iwr.uni-heidelberg.de
Bug#620848: linux-image-2.6.32-5-amd64: unable to enumerate usb device 6
Package: linux-2.6 Severity: important Tags: squeeze -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011 ** Command line: root=UUID=f2f57267-0289-412c-9f9b-e8702e8b7010 ro vga=791 ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [ 473.256064] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 473.496096] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 473.708089] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 473.948068] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 474.160068] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 474.400079] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 474.612083] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 474.852070] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 475.064053] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 475.304067] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 475.516077] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 475.756082] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 475.968485] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 476.209078] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 476.420068] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 476.660073] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 476.872057] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 477.112096] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 477.325029] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 477.565034] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 477.776039] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 478.016091] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 478.229145] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 478.472082] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 478.684094] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 478.925083] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 479.137094] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 479.376106] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 479.591279] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 479.829102] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 480.040060] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 480.280099] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 480.492076] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 480.732088] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 480.944078] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 481.184098] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 481.396058] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 481.637082] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 481.848079] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 482.088093] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 482.300061] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 482.540110] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 482.752081] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 482.992095] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 483.204271] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 483.444061] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 483.656101] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 483.896086] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 484.108091] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 484.348090] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 484.560075] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 484.800125] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 485.016058] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 485.260091] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 485.472096] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 485.712086] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 485.924086] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 486.164072] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 486.376067] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 486.616087] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 486.828099] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 487.068072] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 487.280099] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 487.520110] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 487.732072] hub 3-0:1.0: unable to enumerate USB device on port 6 [ 487.972078] hub 1-0:1.0: unable to enumerate USB device on port 6 [ 488.184081] hub 3-0:1.0: unable to enumerate USB
Processed: tagging 620848, found 620848 in 2.6.32-31
Processing commands for cont...@bugs.debian.org: tags 620848 - squeeze Bug #620848 [linux-2.6] linux-image-2.6.32-5-amd64: unable to enumerate usb device 6 Removed tag(s) squeeze. found 620848 2.6.32-31 Bug #620848 [linux-2.6] linux-image-2.6.32-5-amd64: unable to enumerate usb device 6 There is no source info for the package 'linux-2.6' at version '2.6.32-31' with architecture '' Unable to make a source version for version '2.6.32-31' Bug Marked as found in versions 2.6.32-31. thanks Stopping processing here. Please contact me if you need assistance. -- 620848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130193764120948.transcr...@bugs.debian.org
Bug#620857: linux-image-2.6.32-5-686: xorg x11 server does not display cursor
Package: linux-2.6 Version: 2.6.32-31 Severity: critical Tags: squeeze Justification: breaks unrelated software recent upgrade of linux-image-2.6.32-5-686 (some two weeks ago) made X11 start without mouse cursor visible (mouse operates correctly - when mouse moves over active region, I can see the region gives highlight feedback). No such problem show up, when I boot last linux-image-2.6.32-3-686. Previous version of *-5-686 didn't have that problem either, but I didn't have that package to test it. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3580] (rev 02) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Region 0: Memory at unassigned (32-bit, prefetchable) Capabilities: access denied Kernel driver in use: agpgart-intel 00:00.1 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3584] (rev 02) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:00.3 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3585] (rev 02) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Region 1: Memory at e000 (32-bit, non-prefetchable) [size=512K] Region 2: I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Region 0: Memory at f000 (32-bit, prefetchable) [size=128M] Region 1: Memory at e008 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03) (prog-if 00 [UHCI]) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 4: I/O ports at 1820 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03) (prog-if 00 [UHCI]) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 10 Region 4: I/O ports at 1840 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03) (prog-if 00 [UHCI]) Subsystem: LG Electronics, Inc. Device [1854:000a] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx-
Bug#620374: followup for #620374
Over at https://bugs.freedesktop.org/show_bug.cgi?id=35936 , Chris Wilson asked about the inclusion of commit 29c5a587284195278e233eec5c2234c24fb2c204 in 2.6.38-2. From looking at the changelogs, i don't think it was included, but i'd appreciate if someone from the kernel team could provide a more authoritative follow up. Regards, --dkg signature.asc Description: OpenPGP digital signature
Bug#620857: linux-image-2.6.32-5-686: xorg x11 server does not display cursor
On Mon, Apr 04, 2011 at 07:10:50PM +0200, Rafal Pietrak wrote: Package: linux-2.6 Version: 2.6.32-31 Severity: critical Tags: squeeze Justification: breaks unrelated software [...] All userland software depends on the kernel, so is not unrelated. This bug is important, though. The bug is fixed in version 2.6.32-32, currently in stable-proposed-updates. Due to some regressions on other architectures, this can't be moved to stable-updates, but the next version (2.6.32-33) probably will. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404181449.gq2...@decadent.org.uk
Processed: reassign 620857 to src:linux-2.6, forcibly merging 618665 620857
Processing commands for cont...@bugs.debian.org: reassign 620857 src:linux-2.6 2.6.32-31 Bug #620857 [linux-2.6] linux-image-2.6.32-5-686: xorg x11 server does not display cursor Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.32-31. Bug #620857 [src:linux-2.6] linux-image-2.6.32-5-686: xorg x11 server does not display cursor Bug Marked as found in versions linux-2.6/2.6.32-31. forcemerge 618665 620857 Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files Bug#620857: linux-image-2.6.32-5-686: xorg x11 server does not display cursor Bug#618997: Debian 6.01 - Synaptics Touchpad - no cursor after update Bug#619019: xserver-xorg-video-intel: latest update to debian squeeze made the mouse pointer invisible in my openbox/gdm session Bug#619192: linux-image-2.6.32-5-686: After upgrade to 2.6.32-31 mouse cursor is invisible (but active) Bug#619199: linux-base: mouse pointer invisible after upgrade to 6.0.1 Bug#619315: linux-image-2.6.32-5-686: Mouse pointer invisible with new kernel (intel graphics) Bug#619377: linux-image-2.6.32-5-686: No cursor in X since 2.6.32-31 Bug#619430: linux-image-2.6.32-5-686: X mouse pointer totally invisible Bug#619982: no cursor in GNOME, problems with playing video on Intel 855GM video card Forcibly Merged 618665 618997 619019 619192 619199 619315 619377 619430 619982 620857. thanks Stopping processing here. Please contact me if you need assistance. -- 619019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619019 618997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618997 619982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619982 619192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619192 619315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619315 619199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619199 620857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620857 619377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619377 619430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619430 618665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13019416561381.transcr...@bugs.debian.org
Bug#607301: Cannot boot from debian-6.0.1a-i386-DVD Binary-1 20110322-15:11 and sid 29.03.2011 and debian-rescue-cdrom Grub 1.99~rc1-6 Symptom: error: hd0 cannot get C/H/S values
To address your kind response to me Miguel; I read all the links you gave me for my 'Silicon Image 3114' SATA/Raid controller chip. I also followed and read the sub links. I shall certainly be on the look out for disk corruptions. I could not see any mention of my 'NO BOOT' symptom in the links. including your pointer which eventually lead to Bug 10480 Summary: sil3114 yields ext3_new_block: Allocating block in system zone I came across: https://ata.wiki.kernel.org/index.php/Sata_sil Known problems Some reports of data corruption when paired with NVIDIA chipsets. McTech; I have an ALADDIN5 chipset. For my clarity, that's a number five. The great item I learned from your tip, was that I should not depend searching so much on http:groups.google.com I do not remember coming across your links in my own searching, so thank you. I suppose I was using different search arguments. I thought I had done such a thorough job. I am indebted to you for expanding my search horizons Miguel. If I get data corruption errors, such as kernel: EXT3-fs error kernel: EXT2-fs error or some such, I will know where to look and what to try. So far, I have had no data corruption errors that I am aware of, but then I have not been explicitly looking for them. I have seen no error messages re data corruption, I do get my:- Searching for Boot Record from SCSI..Not Found Boot Failure and that is after a complete installation, of about, I don't know, 15 or 20 various successfull install data transfers. See my /sbin/e2fsck -nv /dev/sda1 clean output below. Of course, I will be looking out in my install logs in future. cat lspci -nn.txt anddmesg -s 100 Output from lspci -nn lspci -nnvvvxxx I will keep a look out for the symptoms described in the following link :- https://bugzilla.kernel.org/show_bug.cgi?id=10480 Comment #8 From Jan Kara 2008-04-24 They (the error messages) generally mean the filesystem is corrupted. In this particular case, bitmap of used blocks is corrupted as system blocks (most likely inode table) are marked as freed in the bitmap of used blocks and then we tried to allocate from there... Miguel, Using grml-daily-sid 110316 codename grml-live-autobuild [2011-03-16] the following is a disk analysis report from my single disk system :- root@grml / # mount /dev/sda1 ... /dev/sda1 on /mnt/sda1 type ext3 (rw) root@grml / # umount /dev/sda1 root@grml / # /sbin/e2fsck -nv /dev/sda1 e2fsck 1.41.12 (17-May-2010) /dev/sda1 was not cleanly unmounted. check forcedMcTech?? Pass1. Checking inodes, blocks, and sizes Pass2. Checking directory structure Pass3. Checking directory connectivity Pass4. Checking reference counts Pass5. Checking group summary information 113443 inodes used (1.16%) 954non-contiguous files (0.8%) 166non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 7293/60/0 1390543 blocks used (3.57%) 0 bad blocks McTech 1 large file 89420 regular files 9396 directories 12character device files 25block device files 2 fifos 419 links 14578 symbolic links (13474 fast symbolic links) 1 socket 113853 files Currently, this disk and controller seems all right to me. So thank you Miguel. I am not sure if the following is the correct protocol. I shall continue my efforts by sending an email Installation-report with package: grub-rescue-pc-1.99~rc1-6 to help-g...@gnu.org. http://lists.gnu.org/archive/html/help-grub/ http://lists.gnu.org/mailman/listinfo/help-grub , and hopefully temporarily put to sleep this thread, Bug#607301 Debian Package: installation-reports here at; http://lists.debian.org/debian-boot/2011/02/msg00320.html I hope this is the correct procedure. If I am standing on anybody's toes, my appologies in advance. Correct procedural guidance is always welcome here. Mucho gracias Miguel F, Melhores cumprimentos. Thank you for your help and time. Best regards,McTech -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTin==Bm50Q9CitBnieT1Lmm2+=i...@mail.gmail.com
Processing of linux-2.6_2.6.32-33_powerpc.changes
linux-2.6_2.6.32-33_powerpc.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-33.dsc linux-2.6_2.6.32-33.diff.gz linux-doc-2.6.32_2.6.32-33_all.deb linux-manual-2.6.32_2.6.32-33_all.deb linux-patch-debian-2.6.32_2.6.32-33_all.deb linux-source-2.6.32_2.6.32-33_all.deb linux-support-2.6.32-5_2.6.32-33_all.deb firmware-linux-free_2.6.32-33_all.deb linux-base_2.6.32-33_all.deb linux-image-2.6.32-5-powerpc_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-powerpc_2.6.32-33_powerpc.deb linux-image-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb linux-image-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-common_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-all_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-all-powerpc_2.6.32-33_powerpc.deb linux-libc-dev_2.6.32-33_powerpc.deb linux-tools-2.6.32_2.6.32-33_powerpc.deb linux-image-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb linux-image-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-common-vserver_2.6.32-33_powerpc.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q6ofv-0004vr...@franck.debian.org
Bug#620814: initramfs-tools: fails to include essential module for other leg of md0
On Mon, Apr 04, 2011 at 12:21:16PM +, Arno Schuring wrote: Hi Ben, During installation, I configured initramfs-tools to determine the required modules automatically, which resulted in a non-booting system (notice that the sil680 module is missing): [...] The initramfs-tools 'MODULES=dep' mode is primarily meant for small systems with limited RAM and disk space for the initramfs. The dependency detection code does not currently handle all module dependencies, as you see. I recommend using 'MODULES=most'. But MODULES=most is exactly what is set: -- /etc/initramfs-tools/initramfs.conf MODULES=most no, check your box with: egrep MODULES -r /etc/initramfs-tools/ -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404185732.ga13...@vostochny.stro.at
Bug#600957: marked as done (linux-image-2.6.32-5-amd64: Please include vmw_pvscsi (VMware PVSCSI))
Your message dated Mon, 04 Apr 2011 19:59:08 + with message-id e1q6pvy-0006kb...@franck.debian.org and subject line Bug#600957: fixed in linux-2.6 2.6.32-33 has caused the Debian Bug report #600957, regarding linux-image-2.6.32-5-amd64: Please include vmw_pvscsi (VMware PVSCSI) 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.) -- 600957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-20 Severity: wishlist Hi, the summary pretty much says it all, please consider backporting the vmw_pvscsi module from 2.6.33 mainline to get full access to the (faster) paravirtualized VMware SCSI controller. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-18) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 01:47:24 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=UUID=45c09f93-97c5-4410-a2cc-a780dc653ae4 ro notsc quiet ** Not tainted ** Model information sys_vendor: VMware, Inc. product_name: VMware Virtual Platform product_version: None chassis_vendor: No Enclosure chassis_version: N/A bios_vendor: Phoenix Technologies LTD bios_version: 6.00 board_vendor: Intel Corporation board_name: 440BX Desktop Reference Platform board_version: None ** Loaded modules: Module Size Used by tcp_diag 880 0 inet_diag 6882 1 tcp_diag vsock 38118 0 vmci 22444 1 vsock vmmemctl6755 0 nfs 240826 1 lockd 57603 1 nfs fscache29834 1 nfs nfs_acl 2031 1 nfs auth_rpcgss33460 1 nfs sunrpc161317 11 nfs,lockd,nfs_acl,auth_rpcgss pvscsi 9724 0 acpiphp15141 0 ext3 106518 1 jbd37085 1 ext3 mbcache 5050 1 ext3 loop 11783 0 snd_pcm60471 0 snd_timer 15582 1 snd_pcm parport_pc 18855 0 parport27954 1 parport_pc snd46446 2 snd_pcm,snd_timer psmouse49777 0 serio_raw 3752 0 soundcore 4598 1 snd snd_page_alloc 6249 1 snd_pcm pcspkr 1699 0 i2c_piix4 8328 0 evdev 7352 0 button 4650 0 container 2389 0 i2c_core 15712 1 i2c_piix4 shpchp 26264 0 pci_hotplug21203 2 acpiphp,shpchp ac 2192 0 processor 30231 0 xfs 436813 1 exportfs3170 1 xfs vmxnet 13161 0 sg 18744 0 sr_mod 12602 0 cdrom 29415 1 sr_mod sd_mod 29777 4 ata_generic 2983 0 crc_t10dif 1276 1 sd_mod ata_piix 21012 0 libata133584 2 ata_generic,ata_piix mptspi 11185 3 floppy 49087 0 mptscsih 16312 1 mptspi mptbase48350 2 mptspi,mptscsih scsi_transport_spi 18774 1 mptspi e1000 85485 0 scsi_mod 122117 8 pvscsi,sg,sr_mod,sd_mod,libata,mptspi,mptscsih,scsi_transport_spi thermal11674 0 thermal_sys11942 2 processor,thermal ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy ii initramfs-tools [linux-initra 0.98 tools for generating an initramfs ii linux-base2.6.32-20 Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-amd64 recommends: pn firmware-linux-free none (no description available) Versions of packages linux-image-2.6.32-5-amd64 suggests: ii grub 0.97-61GRand Unified Bootloader (dummy pa pn linux-doc-2.6.32 none (no description available) Versions of
Bug#619450: marked as done (Oops after loading via-ircc)
Your message dated Mon, 04 Apr 2011 19:59:08 + with message-id e1q6pvy-0006kh...@franck.debian.org and subject line Bug#619450: fixed in linux-2.6 2.6.32-33 has caused the Debian Bug report #619450, regarding Oops after loading via-ircc 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.) -- 619450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-powerpc Version: 2.6.32-31 After upgrading to squeeze userland I now have this Oops. [ 12.894056] via-ircc: dongle probing not supported, please specify dongle_id module parameter. [ 12.915795] [ cut here ] [ 12.936549] kernel BUG at /build/buildd-linux-2.6_2.6.32-31-powerpc-Yemy0c/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/include/asm/dma-mapping.h:153! [ 12.957929] Oops: Exception in kernel mode, sig: 5 [#1] [ 12.978908] CHRP [ 12.999403] Modules linked in: via_ircc(+) vt8231 evdev usblp snd soundcore snd_page_alloc i2c_viapro irda crc_ccitt reiserfs ext4 mbcache jbd2 crc16 ide_cd_mod cdrom ata_generic libata scsi_mod uhci_hcd ohci_hcd ide_pci_generic marvell mv643xx_eth firewire_ohci libphy ehci_hcd via_rhine inet_lro usbcore firewire_core crc_itu_t nls_base via82cxxx [last unloaded: scsi_wait_scan] [ 13.063769] NIP: e272d10c LR: e272d100 CTR: 0008 [ 13.084864] REGS: ddf13c70 TRAP: 0700 Not tainted (2.6.32-5-powerpc) [ 13.105675] MSR: 00029032 EE,ME,CE,IR,DR CR: 42042488 XER: [ 13.126313] TASK = ddebcde0[202] 'modprobe' THREAD: ddf12000 [ 13.126513] GPR00: 4030 ddf13d20 ddebcde0 001c 4a6e [ 13.147352] GPR08: e11e5288 e264573c 0080 22042442 100256a0 1000ca00 [ 13.167894] GPR16: bff76770 10706d38 1000c46c 10708ed4 10708f88 [ 13.188121] GPR24: 3096 e2730150 dd92e800 ddf13d5c dd92ec18 dd92eb60 [ 13.228066] NIP [e272d10c] via_ircc_open+0x138/0x16c [via_ircc] [ 13.247568] LR [e272d100] via_ircc_open+0x12c/0x16c [via_ircc] [ 13.267177] Call Trace: [ 13.286322] [ddf13d20] [e272d100] via_ircc_open+0x12c/0x16c [via_ircc] (unreliable) [ 13.305367] [ddf13d50] [e272d8b0] via_init_one+0x770/0x880 [via_ircc] [ 13.324487] [ddf13dd0] [c01bd6bc] local_pci_probe+0x24/0x34 [ 13.343184] [ddf13de0] [c01be740] pci_device_probe+0x68/0xa0 [ 13.361494] [ddf13e10] [c0278638] driver_probe_device+0xd4/0x1a8 [ 13.379876] [ddf13e30] [c027877c] __driver_attach+0x70/0xa4 [ 13.397843] [ddf13e50] [c0277ca8] bus_for_each_dev+0x5c/0xac [ 13.415410] [ddf13e80] [c0278448] driver_attach+0x24/0x34 [ 13.433026] [ddf13e90] [c02774ec] bus_add_driver+0x118/0x2ac [ 13.450248] [ddf13eb0] [c0278b64] driver_register+0xd0/0x174 [ 13.467058] [ddf13ed0] [c01be99c] __pci_register_driver+0x4c/0xd4 [ 13.483960] [ddf13ef0] [e2734028] via_ircc_init+0x28/0x58 [via_ircc] [ 13.500506] [ddf13f00] [c0003f1c] do_one_initcall+0x74/0x218 [ 13.516671] [ddf13f20] [c007b464] sys_init_module+0xe0/0x224 [ 13.532876] [ddf13f40] [c0014dac] ret_from_syscall+0x0/0x40 [ 13.548678] --- Exception: c01 at 0xff5de04 [ 13.548681] LR = 0x100041c0 [ 13.579405] Instruction dump: [ 13.594338] 40be000c 380001fe 4808 383e b01f00c0 3807 7fc3f378 b01f00e8 [ 13.609265] 4bf0eec9 38004030 901f0158 901f0178 0fe0 4800 7f83e378 48000969 [ 13.624365] ---[ end trace ef5880768dfef5b8 ]--- [ 192.041196] Adding 2096472k swap on /dev/hda5. Priority:-1 extents:1 across:2096472k ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-33 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: firmware-linux-free_2.6.32-33_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-33_all.deb linux-2.6_2.6.32-33.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-33.diff.gz linux-2.6_2.6.32-33.dsc to main/l/linux-2.6/linux-2.6_2.6.32-33.dsc linux-base_2.6.32-33_all.deb to main/l/linux-2.6/linux-base_2.6.32-33_all.deb linux-doc-2.6.32_2.6.32-33_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-33_all.deb linux-headers-2.6.32-5-all-powerpc_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-powerpc_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-all_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-common-vserver_2.6.32-33_powerpc.deb
linux-2.6_2.6.32-33_powerpc.changes ACCEPTED into proposed-updates
Notes: Mapping stable to proposed-updates. Accepted: firmware-linux-free_2.6.32-33_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-33_all.deb linux-2.6_2.6.32-33.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-33.diff.gz linux-2.6_2.6.32-33.dsc to main/l/linux-2.6/linux-2.6_2.6.32-33.dsc linux-base_2.6.32-33_all.deb to main/l/linux-2.6/linux-base_2.6.32-33_all.deb linux-doc-2.6.32_2.6.32-33_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-33_all.deb linux-headers-2.6.32-5-all-powerpc_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all-powerpc_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-all_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-all_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-common-vserver_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common-vserver_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-common_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-common_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-powerpc_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-powerpc_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb linux-headers-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-headers-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb linux-image-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-image-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb linux-image-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-image-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb linux-image-2.6.32-5-powerpc_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-image-2.6.32-5-powerpc_2.6.32-33_powerpc.deb linux-image-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-image-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb linux-image-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-image-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb linux-libc-dev_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-33_powerpc.deb linux-manual-2.6.32_2.6.32-33_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-33_all.deb linux-patch-debian-2.6.32_2.6.32-33_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-33_all.deb linux-source-2.6.32_2.6.32-33_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-33_all.deb linux-support-2.6.32-5_2.6.32-33_all.deb to main/l/linux-2.6/linux-support-2.6.32-5_2.6.32-33_all.deb linux-tools-2.6.32_2.6.32-33_powerpc.deb to main/l/linux-2.6/linux-tools-2.6.32_2.6.32-33_powerpc.deb Override entries for your package: firmware-linux-free_2.6.32-33_all.deb - optional kernel linux-2.6_2.6.32-33.dsc - source devel linux-base_2.6.32-33_all.deb - optional kernel linux-doc-2.6.32_2.6.32-33_all.deb - optional doc linux-headers-2.6.32-5-all-powerpc_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-all_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-common-vserver_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-common_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-powerpc_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb - optional kernel linux-headers-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb - optional kernel linux-image-2.6.32-5-powerpc-smp_2.6.32-33_powerpc.deb - optional kernel linux-image-2.6.32-5-powerpc64_2.6.32-33_powerpc.deb - optional kernel linux-image-2.6.32-5-powerpc_2.6.32-33_powerpc.deb - optional kernel linux-image-2.6.32-5-vserver-powerpc64_2.6.32-33_powerpc.deb - optional kernel linux-image-2.6.32-5-vserver-powerpc_2.6.32-33_powerpc.deb - optional kernel linux-libc-dev_2.6.32-33_powerpc.deb - optional devel linux-manual-2.6.32_2.6.32-33_all.deb - optional doc linux-patch-debian-2.6.32_2.6.32-33_all.deb - optional kernel linux-source-2.6.32_2.6.32-33_all.deb - optional kernel linux-support-2.6.32-5_2.6.32-33_all.deb - optional devel linux-tools-2.6.32_2.6.32-33_powerpc.deb - optional kernel Announcing to debian-chan...@lists.debian.org Closing bugs: 600957 619450 620284 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 Archive: http://lists.debian.org/e1q6pvy-0006kv...@franck.debian.org
Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable kernel BUG at fs/jbd2/commit.c:534 from Postfix on ext4
On Apr 04, 2011, at 10:24, Moffett, Kyle D wrote: On Apr 02, 2011, at 22:02, Ted Ts'o wrote: Sorry for not following up sooner. Are you still able to reproduce this failure? If I set up an identical Debian stable instance on EC-2, am I likely to reproduce it myself? Do you have a package list or EC2 base image I can use as a starting point? I'll need to check on this. Unfortunately it was not a trivial process to install Debian squeeze onto an EC2 instance; it took a couple ugly Perl scripts, a patched Debian-Installer, and several manual post-install-but-before-reboot steps (like fixing up GRUB 0.99). One of these days I may get time to update all that to the official wheezy release and submit bug reports. I have an exact image of the failing instance, but it has proprietary data on it and if I stand up an old copy I need to be careful not to actually let it send all the queued emails :-D. It's probably easier for me to halt email delivery and clone the working instance and try to reproduce from there. If I recall, the (easily undone) workaround was to remount from data=journal to data=ordered on a couple filesystems. It may take a day or two to get this done, though. If it comes down to it I also have a base image (from squeeze as of 9 months ago) that could be made public after updating with new SSH keys. Bah... I went back to the old image that was crashing every boot before and I can't find any way to make it crash at all now... If I manage to reproduce it again later I'll send you another email. Cheers, Kyle Moffett -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/10d1c3aa-79a9-4766-ba4d-6de82...@boeing.com
Re: Stable update of linux-2.6
On Sun, Apr 03, 2011 at 01:21:03PM +0530, Kamalesh Babulal wrote: * dann frazier da...@dannf.org [2011-04-02 11:23:03]: 2.6.32.36 also fails to build on powerpc/SMP: CC arch/powerpc/kernel/crash.o arch/powerpc/kernel/crash.c: In function 'crash_kexec_wait_realmode': arch/powerpc/kernel/crash.c:176: error: 'paca' undeclared (first use in this function) arch/powerpc/kernel/crash.c:176: error: (Each undeclared identifier is reported only once arch/powerpc/kernel/crash.c:176: error: for each function it appears in.) make[1]: *** [arch/powerpc/kernel/crash.o] Error 1 make: *** [arch/powerpc/kernel] Error 2 Hi Dann, Can you please try the following patch, which adds the changes introduced by Kumar Gala to the commit b3df895aeb to my previous patch. Yep, that fixes the build. -dann powerpc: Fix default_machine_crash_shutdown #ifdef build failure Introducing #ifdef to fix the build failure caused by crash_kexec_wait_realmode(), with powerpc build with !SMP. Reported-by: Ben Hutchings b...@decadent.org.uk Reported-by: dann frazier da...@dannf.org Signed-off-by: Kamalesh Babulal kamal...@linux.vnet.ibm.com cc: Paul E. McKenney paul...@linux.vnet.ibm.com cc: Michael Neuling mi...@neuling.org cc: Benjamin Herrenschmidt b...@kernel.crashing.org cc: Anton Blanchard an...@samba.org cc: Kumar Gala ga...@kernel.crashing.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404215755.ge3...@dannf.org
Bug#620814: initramfs-tools: fails to include essential module for other leg of md0
no, check your box with: egrep MODULES -r /etc/initramfs-tools/ Great. /etc/initramfs-tools/initramfs.conf:# MODULES: [ most | netboot | dep | list ] /etc/initramfs-tools/initramfs.conf:MODULES=most /etc/initramfs-tools/conf.d/driver-policy:MODULES=dep So, which one is the preferred location? Will anything break if I just clear out the conf.d directory? ladmin@fury:~$ dpkg -S /etc/initramfs-tools/conf.d/* dpkg: /etc/initramfs-tools/conf.d/driver-policy not found. dpkg: /etc/initramfs-tools/conf.d/resume not found.
Re: Stable update of linux-2.6
On Sun, Apr 03, 2011 at 07:33:39AM +1000, Benjamin Herrenschmidt wrote: On Sun, 2011-04-03 at 00:10 +0530, Kamalesh Babulal wrote: * dann frazier da...@dannf.org [2011-04-02 11:23:03]: 2.6.32.36 also fails to build on powerpc/SMP: CC arch/powerpc/kernel/crash.o arch/powerpc/kernel/crash.c: In function 'crash_kexec_wait_realmode': arch/powerpc/kernel/crash.c:176: error: 'paca' undeclared (first use in this function) arch/powerpc/kernel/crash.c:176: error: (Each undeclared identifier is reported only once arch/powerpc/kernel/crash.c:176: error: for each function it appears in.) make[1]: *** [arch/powerpc/kernel/crash.o] Error 1 make: *** [arch/powerpc/kernel] Error 2 This build is not reproducible locally, can you please send the .config file. Smells to me like a 32-bit build... Yep, it is. Current upstream has the function crash_kexec_wait_realmode() protected by: #ifdef CONFIG_PPC_STD_MMU_64 Maybe that is missing in .32.36 ? You can disable CONFIG_CRASH_DUMP as a workaround. Is it that useful anyways on 32-bit ? (Does it even work ?) I'm just reporting this as a build-time regression in stable as it caused an issue when we merged recent stable updates into the Debian tree. I've never personally tried to configure kdump on powerpc. fwiw, a quick test shows that kexec doesn't work on my test box: dannf@macmini:~$ sudo kexec -l /boot/vmlinux-2.6.32-5-powerpc --append=root=/dev/hda3 ro --initrd=/boot/initrd.img-2.6.32-5-powerpc get_memory_ranges(): Unsupported platform Could not get memory layout -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404221055.gf3...@dannf.org
Re: Stable update of linux-2.6
On Mon, 2011-04-04 at 16:10 -0600, dann frazier wrote: I'm just reporting this as a build-time regression in stable as it caused an issue when we merged recent stable updates into the Debian tree. I've never personally tried to configure kdump on powerpc. fwiw, a quick test shows that kexec doesn't work on my test box: dannf@macmini:~$ sudo kexec -l /boot/vmlinux-2.6.32-5-powerpc --append=root=/dev/hda3 ro --initrd=/boot/initrd.img-2.6.32-5-powerpc get_memory_ranges(): Unsupported platform Could not get memory layout Yes, we've never added support for kexec on macs, I suppose that shouldn't be too hard to do tho... Cheers, Ben. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301956312.2549.94.camel@pasglop
Processed: unmerging 611750
Processing commands for cont...@bugs.debian.org: unmerge 611750 Bug#611750: Asus EeePC resume from hibernation fails Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate Disconnected #611750 from all other report(s). thanks Stopping processing here. Please contact me if you need assistance. -- 613790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613790 611750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130196005729669.transcr...@bugs.debian.org
Bug#620374: followup for #620374
On Mon, 2011-04-04 at 13:31 -0400, Daniel Kahn Gillmor wrote: Over at https://bugs.freedesktop.org/show_bug.cgi?id=35936 , Chris Wilson asked about the inclusion of commit 29c5a587284195278e233eec5c2234c24fb2c204 in 2.6.38-2. From looking at the changelogs, i don't think it was included, but i'd appreciate if someone from the kernel team could provide a more authoritative follow up. No, we don't have that patch yet. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#613790: marked as done (pm-utils: eeepc 1005 PE recently stopped resuming from hibernate)
Your message dated Tue, 05 Apr 2011 00:36:01 +0100 with message-id 1301960161.2935.72.camel@localhost and subject line Re: Bug#611750: Bug#613790: 2nd update (Re: Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate) has caused the Debian Bug report #613790, regarding pm-utils: eeepc 1005 PE recently stopped resuming from hibernate 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.) -- 613790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pm-utils Version: 1.3.0-3 Severity: important I installed testing about one year ago on this machine. The default installation and eeepc-acpi-utils allowed me to use both suspension and hibernation with no problems. A couple of weeks ago, I noticed that resuming from hibernation stopped from working : the machine starts with Asus splash screen, then grub splash screen, detects a resume image, blanks screen for a while (as usual). However, after 5-10 seconds (time expexcted to get the screen-save prompt for a password when resuming from hibernation), the system reboots back to the Asus splash screen, the the grub splash screen ; this second time, the resume image is not detected and the system performs a normal boot (perfectly. I tried to (manually) pass some --quirks options to pm-hibernate, to no avail (ISTR I tried vberestore, pcirestore, but I'm no longer sure). Therefore, I can no longer use hibernation, which is somewhat annoyng and renders me more dependent on power supplies. The same bug has been reported (in analogous circumstances) on the eeepc devel mailong list a few days ago (I don't have the reference currently). Any workaround would be welcome. Sincerely, Emmanuel Charpentier -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pm-utils depends on: ii kbd 1.15.2-2 Linux console font and keytable ut ii powermgmt-base1.31 Common utils and configs for power Versions of packages pm-utils recommends: ii procps1:3.2.8-10 /proc file system utilities ii radeontool1.6.1-1utility to control ATI Radeon back ii vbetool 1.1-2 run real-mode video BIOS code to a Versions of packages pm-utils suggests: ii cpufrequtils 007-1 utilities to deal with the cpufreq -- no debconf information ---End Message--- ---BeginMessage--- On Fri, 2011-04-01 at 21:03 +0200, Emmanuel Charpentier wrote: One more datapoint : I also upgraded to 2.6.32.31 as packaged in testing, without further problems on my 1005PE. I have used it since its apparition in testing (that's 8 days and 8 hours according to uptime), using my machine as usual (meaning 2-5 hibernations per day) without shutdown or reboot. Other models may be pickier ? OK, I'm closing this bug but leaving #611750 open. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Processed: severity of 620896 is normal
Processing commands for cont...@bugs.debian.org: severity 620896 normal Bug #620896 [linux-2.6] Bug when listing files/dirs on ncpfs Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 620896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13019622084854.transcr...@bugs.debian.org
Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable kernel BUG at fs/jbd2/commit.c:534 from Postfix on ext4
On Mon, Apr 04, 2011 at 09:24:28AM -0500, Moffett, Kyle D wrote: Unfortunately it was not a trivial process to install Debian squeeze onto an EC2 instance; it took a couple ugly Perl scripts, a patched Debian-Installer, and several manual post-install-but-before-reboot steps (like fixing up GRUB 0.99). One of these days I may get time to update all that to the official wheezy release and submit bug reports. Sigh, I was whoping someone was maintaining semi-official EC2 images for Debian, much like alestic has been maintaining for Ubuntu. (Hmm, actually, he has EC2 images for Lenny and Etch, but unfortunately not for squeeze. Sigh) It's probably easier for me to halt email delivery and clone the working instance and try to reproduce from there. If I recall, the (easily undone) workaround was to remount from data=journal to data=ordered on a couple filesystems. It may take a day or two to get this done, though. Couple of questions which might give me some clues: (a) was this a natively formatted ext4 file system, or a ext3 file system which was later converted to ext4? (b) How big are the files/directories involved? In particular, how big is the Postfix mail queue directory, and it is an extent-based directory? (what does lsattr on the mail queue directory report) As far as file sizes, does it matter how big the e-mail messages are, and are there any other database files that postgress might be touching at the time that you get the OOPS? I have found a bug in ext4 where we were underestimating how many journal credits were needed when modifying direct/indirect-mapped files (which would be seen on ext4 if you had a ext3 file system that was converted to start using extents; but old, pre-existing directories wouldn't be converted), which is why I'm asking the question about whether this was an ext2/ext3 file system which was converted to use ext4. I have a patch to fix it, but backporting it into a kernel which will work with EC2 is not something I've done before. Can anyone point me at a web page that gives me the quick cheat sheet? If it comes down to it I also have a base image (from squeeze as of 9 months ago) that could be made public after updating with new SSH keys. If we can reproduce the problem on that base image it would be really great! I have an Amazon AWS account; contact me when you have an image you want to share, if you want to share it just with my AWS account id, instead of sharing it publically... - Ted -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110405001542.ge2...@thunk.org
Bug#620896: Bug when listing files/dirs on ncpfs
Another report of ncpfs regression in 2.6.38: On Mon, 2011-04-04 at 19:29 -0400, Diego Rubert wrote: Package: linux-2.6 Version: 2.6.38-2 Severity: grave Got a bug message when listing items on ncpfs filesystem with 'ls' command. Makes mounted filesystem useless. Trace: [ 48.940407] [ cut here ] [ 48.941485] kernel BUG at /build/buildd- linux-2.6_2.6.38-2-amd64-6G9fmV/linux-2.6-2.6.38/debian/build/source_amd64_none/fs/dcache.c:2134! [ 48.942559] invalid opcode: [#1] SMP [ 48.943651] last sysfs file: /sys/devices/virtual/sound/timer/uevent [ 48.944386] CPU 1 [ 48.944386] Modules linked in: nls_cp437 nls_utf8 parport_pc ncpfs ppdev lp parport snd_hrtimer fuse coretemp loop snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi i915 snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc drm_kms_helper drm i2c_algo_bit wmi pcspkr tpm_tis psmouse i2c_i801 tpm i2c_core tpm_bios serio_raw container video processor thermal_sys evdev button ext4 mbcache jbd2 crc16 sg sd_mod sr_mod cdrom crc_t10dif usb_storage usbhid hid uas uhci_hcd ata_generic ata_piix libata ehci_hcd e1000e floppy usbcore scsi_mod nls_base [last unloaded: scsi_wait_scan] [ 48.944386] [ 48.944386] Pid: 2176, comm: bash Not tainted 2.6.38-2-amd64 #1 LENOVO 6234CY8/LENOVO [ 48.944386] RIP: 0010:[8110716a] [8110716a] dentry_update_name_case+0x17/0x4f [ 48.944386] RSP: 0018:88006fd8f9c8 EFLAGS: 00010246 [ 48.944386] RAX: RBX: 88005dc853c0 RCX: 0bcc [ 48.944386] RDX: 0053 RSI: 88006fd8fa98 RDI: 88005dc853c0 [ 48.944386] RBP: 88006fd8fa98 R08: R09: 88005dc853fc [ 48.944386] R10: 0053 R11: 880075b0fdb0 R12: 88005dc65b40 [ 48.944386] R13: 88006fd8fc58 R14: 0001 R15: 88005dc853c0 [ 48.944386] FS: 7f8a2d762700() GS:880075b0() knlGS: [ 48.944386] CS: 0010 DS: ES: CR0: 80050033 [ 48.944386] CR2: 7f23b106bac0 CR3: 6fc5b000 CR4: 000406e0 [ 48.944386] DR0: DR1: DR2: [ 48.944386] DR3: DR6: 0ff0 DR7: 0400 [ 48.944386] Process bash (pid: 2176, threadinfo 88006fd8e000, task 88006fdaca40) [ 48.944386] Stack: [ 48.944386] 88005dca6048 88005dca6048 880071919300 a038d1b5 [ 48.944386] 88006fd8fac4 00013700 0004810086fe [ 48.944386] 88006fd8fe68 0002 88005e3aa000 [ 48.944386] Call Trace: [ 48.944386] [a038d1b5] ? ncp_fill_cache+0x1b5/0x42a [ncpfs] [ 48.944386] [81104c5c] ? filldir+0x0/0xc3 [ 48.944386] [810ec2a8] ? virt_to_head_page+0x9/0x2d [ 48.944386] [a0393407] ? ncp_do_request+0x30f/0x321 [ncpfs] [ 48.944386] [81060331] ? autoremove_wake_function+0x0/0x2a [ 48.944386] [a03934f7] ? ncp_request2+0x49/0x76 [ncpfs] [ 48.944386] [a0391989] ? ncp_search_for_fileset+0x1a4/0x1e6 [ncpfs] [ 48.944386] [a038d65e] ? ncp_do_readdir+0x139/0x18d [ncpfs] [ 48.944386] [81104c5c] ? filldir+0x0/0xc3 [ 48.944386] [810e536f] ? alloc_pages_vma+0x108/0x124 [ 48.944386] [810b5409] ? find_get_page+0x3b/0x5e [ 48.944386] [810b67d4] ? lock_page+0xe/0x2c [ 48.944386] [a038dc34] ? ncp_readdir+0x582/0x587 [ncpfs] [ 48.944386] [81104c5c] ? filldir+0x0/0xc3 [ 48.944386] [810d5b2c] ? vma_merge+0x1ef/0x34a [ 48.944386] [81104c5c] ? filldir+0x0/0xc3 [ 48.944386] [81104d86] ? vfs_readdir+0x67/0xa4 [ 48.944386] [81104eff] ? sys_getdents+0x7d/0xcd [ 48.944386] [81327255] ? page_fault+0x25/0x30 [ 48.944386] [81009952] ? system_call_fastpath+0x16/0x1b [ 48.944386] Code: 8b 52 24 89 50 24 c3 8b 48 24 8b 72 24 89 70 24 89 4a 24 c3 55 48 89 f5 53 48 89 fb 48 83 ec 08 48 8b 47 30 8b 40 28 ff c8 75 04 0f 0b eb fe 8b 47 24 3b 46 04 74 04 0f 0b eb fe 48 8d 7f 5c e8 [ 48.944386] RIP [8110716a] dentry_update_name_case+0x17/0x4f [ 48.944386] RSP 88006fd8f9c8 [ 49.009088] ---[ end trace 274c8a8a3c2d4f6d ]--- [...] -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 620896, bug 620896 is forwarded to linux-fsde...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: tags 620896 + upstream Bug #620896 [linux-2.6] Bug when listing files/dirs on ncpfs Added tag(s) upstream. forwarded 620896 linux-fsde...@vger.kernel.org Bug #620896 [linux-2.6] Bug when listing files/dirs on ncpfs Set Bug forwarded-to-address to 'linux-fsde...@vger.kernel.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 620896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13019626555971.transcr...@bugs.debian.org
Bug#620924: Please drop dead usplash code
Package: initramfs-tools Version: 0.98.8 Severity: normal Hi maks, as you are certainly aware, usplash is dead and has been removed from the archive since quite some time (squeeze does no longer contain it). initramfs-tools still contains usplash specific code, which can be safely dropped (and possibly replaced by plymouth integration code) Cheers, Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-7 GNU cpio -- a program to manage ar ii findutils 4.4.2-1+b1 utilities for finding files--find, ii klibc-utils 1.5.21-1 small utilities built with klibc f ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii udev 167-1 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.18.4-1 Tiny utilities for small and embed Versions of packages initramfs-tools suggests: ii bash-completion 1:1.3-1programmable completion for the ba -- Configuration Files: /etc/initramfs-tools/initramfs.conf changed: MODULES=dep BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE= NFSROOT=auto -- no debconf information -- debsums errors found: debsums: changed file /usr/share/initramfs-tools/init (from initramfs-tools package) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110405032516.1665.95929.report...@pluto.milchstrasse.xx
