Bug#619034: [regression] BUG: Unable to handle kernel paging request at ffffc90013cd8000 and no sound card recognized
forwarded 619034 https://bugzilla.kernel.org/show_bug.cgi?id=42619 quit Dear Svante, dear Jonathan, Am Mittwoch, den 18.01.2012, 19:23 -0600 schrieb Jonathan Nieder: Svante Signell wrote: I have uploaded a dmesg ouput to the kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=30552 The box boots perfectly with the additional option pci=use_crs. Hopefully the kernel developers and Debian Kernel Maintainers can find a permanent solution soon. Thanks again for your help in this. I assume current kernels still don't work out of the box on your machine? If so, please add a comment to [1] with the newest version you've checked and your DMI information. (You can get it with dmidecode or grep . /sys/class/dmi/id/*, or something like dmesg | grep DMI on more recent kernels.) I created a new ticket dedicated to the Svante’s board MS-7253, so that the Debian BTS can track that bug now for #619034. Please comment there anything else. Unfortunately some machines need to use the _CRS table and some need it ignored, so for now upstream is building a table of known cases in which the kernel looks up the machine at boot time. Hopefully over time patterns will emerge and there can be a more principled rule. Let’s hope so. Thanks, Paul [1] https://bugzilla.kernel.org/show_bug.cgi?id=30552 [2] https://bugzilla.kernel.org/show_bug.cgi?id=42619 signature.asc Description: This is a digitally signed message part
Processed: Re: [regression] BUG: Unable to handle kernel paging request at ffffc90013cd8000 and no sound card recognized
Processing commands for cont...@bugs.debian.org: forwarded 619034 https://bugzilla.kernel.org/show_bug.cgi?id=42619 Bug #619034 [linux-2.6] Boot problem due to PCI core, x86 mm or ACPI/BIOS Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=42619' from 'https://bugzilla.kernel.org/show_bug.cgi?id=30552' quit Stopping processing here. Please contact me if you need assistance. -- 619034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619034 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.13271327447259.transcr...@bugs.debian.org
Bug#655152: [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times messages associated with KDE plasma desktop desktop effects
Wojciech Zabolotny wrote: I have stated, that if I disable the desktop effects the problematic [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times do not overload my logs. That explains why I haven't seen this problem before (previously I used the GNOME environment, [...] So currently I don't know if this bug is associated with kernel, with KDE or with Intel drivers? The message comes from the Intel (kernel) driver, so please report this upstream following the instructions from http://intellinuxgraphics.org/how_to_report_bug.html and let us know the bug number so we can track it. Thanks, Jonathan -- 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/20120121084624.GB1691@burratino
Bug#655152: [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times messages associated with KDE plasma desktop desktop effects
Jonathan Nieder wrote: please report this upstream following the instructions from http://intellinuxgraphics.org/how_to_report_bug.html and let us know the bug number so we can track it. Erm, never mind --- this is [1]. So it would be better to attach the relevant info to that report and add yourself to its cc list if ready to answer questions or test patches. Sorry I missed that (by which I mean I lazily didn't bother to check) before. [1] https://bugs.freedesktop.org/show_bug.cgi?id=41793 -- 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/20120121085102.GC1691@burratino
Processed: Re: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Processing commands for cont...@bugs.debian.org: reassign 656375 src:linux-2.6 3.1.8-2 Bug #656375 [libdrm-intel1] libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times Bug reassigned from package 'libdrm-intel1' to 'src:linux-2.6'. Bug No longer marked as found in versions libdrm/2.4.30-1. Bug #656375 [src:linux-2.6] libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times Bug Marked as found in versions linux-2.6/3.1.8-2. reassign 655152 src:linux-2.6 3.1.6-1 Bug #655152 [linux-2.6] linux-image-3.1.0-1-686-pae: /var/log/messages get filled with strange messages: kernel: Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 3.1.6-1. Bug #655152 [src:linux-2.6] linux-image-3.1.0-1-686-pae: /var/log/messages get filled with strange messages: kernel: Bug Marked as found in versions linux-2.6/3.1.6-1. severity 655152 important Bug #655152 [src:linux-2.6] linux-image-3.1.0-1-686-pae: /var/log/messages get filled with strange messages: kernel: Severity set to 'important' from 'normal' merge 656375 655152 Bug#655152: linux-image-3.1.0-1-686-pae: /var/log/messages get filled with strange messages: kernel: Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times Merged 655152 656375. affects 655152 + xserver-xorg-video-intel Bug #655152 [src:linux-2.6] linux-image-3.1.0-1-686-pae: /var/log/messages get filled with strange messages: kernel: Bug #656375 [src:linux-2.6] libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times Added indication that 655152 affects xserver-xorg-video-intel Added indication that 656375 affects xserver-xorg-video-intel quit Stopping processing here. Please contact me if you need assistance. -- 655152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655152 656375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656375 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.132713618027974.transcr...@bugs.debian.org
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Jonathan Nieder jrnie...@gmail.com (21/01/2012): After logging into GNOME, I started getting LOTS of [ 239.494761] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times in kernel log repeated ever few microseconds. Kernel log = kernel bug. :) Reassigning. No. Please don't waste our time. Mraw, KiBi. signature.asc Description: Digital signature
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Cyril Brulebois wrote: Jonathan Nieder jrnie...@gmail.com (21/01/2012): After logging into GNOME, I started getting LOTS of [ 239.494761] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times in kernel log repeated ever few microseconds. Kernel log = kernel bug. :) Reassigning. No. Please don't waste our time. Sorry to waste your time. My tongue was in cheek when I said kernel log = kernel bug, and I apologize for that. However, I fear I must have committed some other offense on top of that. Could you elaborate so I know what not to do again? Confused, Jonathan -- 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/20120121091718.GE1691@burratino
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Jonathan Nieder jrnie...@gmail.com (21/01/2012): Sorry to waste your time. My tongue was in cheek when I said kernel log = kernel bug, and I apologize for that. The problem is not the tongue in cheek. The problem is your fiddling with that bug report while there are (AFAICT) no reasons to reassign it to the kernel. Kernel maintainers have better things to do. Me too. Mraw, KiBi. signature.asc Description: Digital signature
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
(-cc: Witold) Cyril Brulebois wrote: The problem is not the tongue in cheek. The problem is your fiddling with that bug report while there are (AFAICT) no reasons to reassign it to the kernel. Kernel maintainers have better things to do. Me too. Ok, sorry about that. My choice was reassign a kernel bug concerning the same problem to libdrm or the libdrm bug to the kernel, or to leave them unmerged. I should have said so, I guess. Honestly, a little kindness could have helped a lot. I guess you mean that you do not suspect this is a kernel bug? You could easily be right, which is why upstream does not bother to separate DRI bugs from libdrm ones. Though in that case the error message could be a lot better. If the kernel maintainers have better things to do than tolerate my help with bugs, I'll be happy to do something else. Just say the word. -- 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/20120121095610.GA2579@burratino
Bug#615110: tpm_tis prevents suspend working more than once
On 20/01/12 08:46, Jonathan Nieder wrote:
Thanks. Do you know the commit id of this 3.2-rc2+ kernel?
It's one I've been working on to fix Sony Vaio keyboard problems. I'll
try an official kernel today.
There have been some tpm fixes upstream recently, so results from
testing v3.3-rc1 or later would be interesting.
Ok, will try.
I've tried the workaround and it works perfectly.
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
Manufacturer: 0x49465800
TCG version: 1.2
Firmware version: 1.0
*did a suspend there - worked*
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
*tried a suspend - didnt work*
root@carbon:~# dmesg | grep -i failed
[0.076215] pci:00: ACPI _OSC request failed (AE_NOT_FOUND), returned
control mask: 0x1d
[ 1176.136093] PM: Device 00:07 failed to suspend: error 38
[ 1176.136109] PM: Some devices failed to suspend
root@carbon:~# ~john/tpm_startup
Success!
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
Manufacturer: 0x49465800
TCG version: 1.2
Firmware version: 1.0
*did a suspend there - worked*
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
root@carbon:~# ~john/tpm_startup
Success!
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
Manufacturer: 0x49465800
TCG version: 1.2
Firmware version: 1.0
*Did a suspend there - worked*
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
root@carbon:~# ~john/tpm_startup
Success!
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
Manufacturer: 0x49465800
TCG version: 1.2
Firmware version: 1.0
*Try running tpm_startup twice:
*root@carbon:~# ~john/tpm_startup
Got an error code in response: 38
root@carbon:~# cat /sys/devices/pnp0/00:07/caps
Manufacturer: 0x49465800
TCG version: 1.2
Firmware version: 1.0
*Suspend still works*
#include stdio.h
#include stdint.h
#include fcntl.h
#include unistd.h
int main(void) {
const uint8_t startup_st_state[] = {
0x00, 0xc1,
0x00, 0x00, 0x00, 0x0c,
0x00, 0x00, 0x00, 0x99,
0x00, 0x02
};
uint8_t buf[10];
int fd = open(/dev/tpm0, O_RDWR);
int len;
uint32_t err;
if (fd 0) {
printf(Could not open /dev/tpm0\n);
return 1;
}
len = write(fd, startup_st_state, sizeof(startup_st_state));
if (len != sizeof(startup_st_state)) {
printf(Write failed.\n);
goto err_exit;
}
len = read(fd, buf, sizeof(buf));
if (len != sizeof(buf)) {
printf(Expected %d bytes bot got %d\n, (int)sizeof(buf), len);
goto err_exit;
}
if (buf[1] != 0xc4) {
printf(Response tag is bad.\n);
goto err_exit;
}
if (buf[5] != sizeof(buf)) {
printf(Response length is bad: %d\n, buf[5]);
goto err_exit;
}
err = buf[6] 24 | buf[7] 16 | buf[8] 8 | buf[9];
if (err) {
printf(Got an error code in response: %u\n, err);
} else {
printf(Success!\n);
}
err_exit:
close(fd);
return 0;
}
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Saturday, January 21, 2012 4:17 AMJonathan Nieder wrote: Cyril Brulebois wrote: Jonathan Nieder jrnie...@gmail.com (21/01/2012): After logging into GNOME, I started getting LOTS of [ 239.494761] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times in kernel log repeated ever few microseconds. Already fixed 2 weeks ago... Kernel log = kernel bug. :) Reassigning. No. Please don't waste our time. Sorry to waste your time. My tongue was in cheek when I said kernel log = kernel bug, and I apologize for that. However, I fear I must have committed some other offense on top of that. Could you elaborate so I know what not to do again? Confused, Jonathan Will
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Jonathan Nieder jrnie...@gmail.com (21/01/2012): (-cc: Witold) (that's not what I see, fixing) Ok, sorry about that. My choice was reassign a kernel bug concerning the same problem to libdrm or the libdrm bug to the kernel, or to leave them unmerged. I should have said so, I guess. Leaving bugs as-is was very fine, at least with my libdrm hat. Honestly, a little kindness could have helped a lot. I guess you mean that you do not suspect this is a kernel bug? You could easily be right, which is why upstream does not bother to separate DRI bugs from libdrm ones. Though in that case the error message could be a lot better. Since you seem to be missing the big picture, several components are at play here: kernel (+ possibly firmware in the radeon case), libdrm, x server, x driver, mesa. And if one of them is sending shitty commands to the GPU, anything can break havoc. Usually, with the GPU hanging. That does *not* mean the kernel is at fault, just because there's some line in the kernel log! Back to the original topic: it is very difficult for Intel techs to support old (and I'm just echo-ing their views on hardware) hardware, even if older versions of the x driver might have worked at some point. That is sad, but that's the state of affairs today. Mraw, KiBi. signature.asc Description: Digital signature
Bug#656724: linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ...
Package: linux-2.6 Version: 3.2.1-1 Severity: normal Dear Maintainer, After installing this kernel I repeatedly get this kind of messages on any terminal I use: Message from syslogd@pbell-acb at Jan 21 11:31:32 ... kernel:[ 1039.072638] Code: c0 89 c5 74 04 80 63 1c fb 48 83 c4 38 89 e8 5b 5d 41 5c 41 5d c3 90 0f 09 66 66 90 66 90 c3 fa 66 66 90 66 66 90 c3 fb 66 66 90 66 66 90 c3 48 8b 15 2d f1 56 e1 48 8d 42 fd 48 83 f8 01 0f 96 A more detailed explanation of the failure is in the log attached. A. Corbi -- Package-specific info: ** Version: Linux version 3.2.0-1-amd64 (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Thu Jan 19 09:46:46 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/acb--laptop-root ro quiet splash pcie_aspm=force ** Not tainted ** Kernel log: [ 779.104584] [a01c2020] ? acpi_idle_enter_simple+0xc6/0x102 [processor] [ 779.104602] [812633c3] ? cpuidle_idle_call+0xec/0x179 [ 779.104613] [8100d255] ? cpu_idle+0xa1/0xe8 [ 779.104623] [810706b6] ? arch_local_irq_restore+0x2/0x8 [ 779.104633] [81332861] ? start_secondary+0x1d5/0x1db [ 779.104638] Code: c0 89 c5 74 04 80 63 1c fb 48 83 c4 38 89 e8 5b 5d 41 5c 41 5d c3 90 0f 09 66 66 90 66 90 c3 fa 66 66 90 66 66 90 c3 fb 66 66 90 66 66 90 c3 48 8b 15 2d f1 56 e1 48 8d 42 fd 48 83 f8 01 0f 96 [ 779.104732] Call Trace: [ 779.104746] [a01c2020] ? acpi_idle_enter_simple+0xc6/0x102 [processor] [ 779.104759] [812633c3] ? cpuidle_idle_call+0xec/0x179 [ 779.104769] [8100d255] ? cpu_idle+0xa1/0xe8 [ 779.104776] [810706b6] ? arch_local_irq_restore+0x2/0x8 [ 779.104785] [81332861] ? start_secondary+0x1d5/0x1db [ 781.007261] sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 781.008783] sd 5:0:0:0: [sdb] Asking for cache data failed [ 781.008793] sd 5:0:0:0: [sdb] Assuming drive cache: write through [ 831.200064] BUG: scheduling while atomic: swapper/1/0/0x1100 [ 831.200073] Modules linked in: hidp hid cryptd aes_x86_64 aes_generic acpi_cpufreq mperf rfcomm cpufreq_powersave cpufreq_userspace bnep cpufreq_stats cpufreq_conservative binfmt_misc uinput microcode fuse joydev btusb bluetooth sbs sbshc coretemp loop kvm_intel kvm snd_hda_codec_realtek snd_hda_intel arc4 snd_hda_codec snd_usb_audio snd_pcm_oss snd_mixer_oss uvcvideo videodev snd_pcm media snd_hwdep snd_usbmidi_lib v4l2_compat_ioctl32 snd_seq_midi iwl4965 snd_rawmidi iwl_legacy mac80211 pcspkr psmouse serio_raw iTCO_wdt iTCO_vendor_support snd_seq_midi_event cfg80211 snd_seq snd_timer snd_seq_device battery snd ac power_supply asus_laptop sparse_keymap rfkill input_polldev soundcore snd_page_alloc evdev processor ext4 mbcache jbd2 crc16 dm_mod ums_realtek usb_storage uas i915 sd_mod crc_t10dif ata_generic drm_kms_helper drm i2c_algo_bit ata_piix uhci_hcd ahci libahci libata thermal ehci_hcd scsi_mod r8169 mii button i2c_core video thermal_sys usbcore usb_common [last unl! oaded: scsi_wait_scan] [ 831.200265] CPU 1 [ 831.200269] Modules linked in: hidp hid cryptd aes_x86_64 aes_generic acpi_cpufreq mperf rfcomm cpufreq_powersave cpufreq_userspace bnep cpufreq_stats cpufreq_conservative binfmt_misc uinput microcode fuse joydev btusb bluetooth sbs sbshc coretemp loop kvm_intel kvm snd_hda_codec_realtek snd_hda_intel arc4 snd_hda_codec snd_usb_audio snd_pcm_oss snd_mixer_oss uvcvideo videodev snd_pcm media snd_hwdep snd_usbmidi_lib v4l2_compat_ioctl32 snd_seq_midi iwl4965 snd_rawmidi iwl_legacy mac80211 pcspkr psmouse serio_raw iTCO_wdt iTCO_vendor_support snd_seq_midi_event cfg80211 snd_seq snd_timer snd_seq_device battery snd ac power_supply asus_laptop sparse_keymap rfkill input_polldev soundcore snd_page_alloc evdev processor ext4 mbcache jbd2 crc16 dm_mod ums_realtek usb_storage uas i915 sd_mod crc_t10dif ata_generic drm_kms_helper drm i2c_algo_bit ata_piix uhci_hcd ahci libahci libata thermal ehci_hcd scsi_mod r8169 mii button i2c_core video thermal_sys usbcore usb_common [last unl! oaded: scsi_wait_scan] [ 831.200429] [ 831.200436] Pid: 0, comm: swapper/1 Not tainted 3.2.0-1-amd64 #1 Packard Bell BV EasyNote_BG46-P-001/EasyNote_BG46 [ 831.200449] RIP: 0010:[a01c1398] [a01c1398] arch_local_irq_enable+0x4/0x8 [processor] [ 831.200472] RSP: 0018:88013af17e90 EFLAGS: 0246 [ 831.200479] RAX: 000e RBX: a01c5240 RCX: 00c18761bc93 [ 831.200486] RDX: 88013fd0 RSI: 0078 RDI: 00c18761f8bf [ 831.200492] RBP: 0002 R08: 88013af17fd8 R09: 7c4c [ 831.200499] R10: 0046 R11: 88013af17fd8 R12: [ 831.200505] R13: 0004 R14: 8801371e600c R15: [ 831.200513] FS: () GS:88013fd0() knlGS: [ 831.200520] CS: 0010 DS: ES: CR0:
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Saturday, January 21, 2012 5:20 AMCyril Brulebois wrote: [...] a couple of my installs ( syslogs ) grew to several GiB`s for the two weeks of so I noticed this page_flip spamming on my old i865g stuff. Back to the original topic: it is very difficult for Intel techs to support old (and I'm just echo-ing their views on hardware) hardware, even if older versions of the x driver might have worked at some point. That is sad, but that's the state of affairs today. I follow right behind you on this note. I'm still amazed at how much hardware (old and new) this OS supports. Sorry for the extra noise. Will Mraw, KiBi.
Bug#615110: tpm_tis prevents suspend working more than once
Exactly same behaviour with stock debian 3.2: Linux carbon 3.2.0-1-686-pae #1 SMP Thu Jan 19 10:56:51 UTC 2012 i686 GNU/Linux ii linux-image-3.2.0-1-686-pae 3.2.1-1 Linux 3.2 for modern PCs Will try with 3.3 rc1 later. -- 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/4f1a9a62.8020...@calvaedi.com
Processed: Re: tpm_tis prevents suspend working more than once
Processing commands for cont...@bugs.debian.org: found 615110 linux-2.6/3.2.1-1 Bug #615110 [linux-2.6] linux-image-2.6.37-1-686: tpm_tis prevents suspend working more than once Bug #591031 [linux-2.6] linux-image-2.6.35-rc6-686: suspend works for a while (once?) then stops working Bug Marked as found in versions linux-2.6/3.2.1-1. Bug Marked as found in versions linux-2.6/3.2.1-1. End of message, stopping processing here. Please contact me if you need assistance. -- 615110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615110 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.132714364112680.transcr...@bugs.debian.org
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
Will Set debiandu...@yahoo.com (21/01/2012): Saturday, January 21, 2012 5:20 AMCyril Brulebois wrote: Back to the original topic: it is very difficult for Intel techs to support old (and I'm just echo-ing their views on hardware) hardware, even if older versions of the x driver might have worked at some point. That is sad, but that's the state of affairs today. I follow right behind you on this note. I'm still amazed at how much hardware (old and new) this OS supports. For the record, this has little to do with the OS. It has to do with upstream support. Mraw, KiBi. signature.asc Description: Digital signature
Bug#655152: The problem with multiple [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times is associated with KDE plasma desktop desktop effects
On 21/01/2012 00:50, Wojciech Zabolotny wrote: I have stated, that if I disable the desktop effects the problematic [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times do not overload my logs. [...] Anyway the problem does not appear on my other machines with Intel graphic chipsets (but newer than 865G). I have an i855 and i've seen the drm:intel_prepare_page_flip error too when several months ago i've tried Mutter (thus graphic effects) under Gnome2: i had to return to Metacity. Some months ago Gnome2 was upgraded to Gnome3 and several graphic defects have arisen so, like you, i had to switch to another desktop environment (now Xfce, but not very happy). But problems remains with Firefox crashes on some flash-based sites, with random and sporadic screen corruption when watching videos, graphic corruptions with LibreOffice. All bugs that, looking around, are common and limited to owner of gen2 Intel chipsets. The problem with gen2 hardware (830, 845, 855, 865) is that the situation is getting worse as the time goes by. Looks like these chipsets are, for various reasons, a pain in the ass for upstream and from what i understand they have choosen to relegate that old code apart from the modern one, removing from time to time problematic features that cause instabilities and to concentrate on the more modern and documented graphics hardware. For our gen2 hardware the soon to be released mesa 8 seems to have removed other features with the effect that, as someone said on mesa ml, for these chipset the driver will be nearly equal to the unaccelerated vesa one. For the record yesterday i've given a try to PCBSD 9.0 and with the default installer when X started i got a blank screen: i had to reboot to select vesa mode, to get X working. So these chipsets seems to cause pain also to other OSes. It is with great sadness that i suggest you to start saving some money, then change your hardware to something more recent, for example a sandy bridge processor that seems to be very well supported. It will save you time and headache. It's a pity, because our hardware is not so old and its computational power is yet suitable for many tasks, but this is what i've realized by experience. Cesare. -- 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/4f1aa511.4010...@gmail.com
Bug#656754: linux-image-2.6.39-bpo.2-amd64: vlan malfunction
Package: linux-2.6 Version: 2.6.39-3~bpo60+1 Severity: important Tags: d-i ipv6 upstream The network functionality is only guaranteed on the underlying network interface with vlanid 0. dmesg does not report any problems concerning vlan. The 8021q module is loaded. It can be loaded and unloaded without problems. Network interfaces and bridge interfaces which have been set up to use vlan can not be used. /proc/net/vlan/config reports interface-vlan-relations as usual. Manually setting up an interface using vconfig does not change the situation. Monitoring an interface with iptraf shows traffic in eth0 (unidirectional), while traffic on vlan interface will always show non-ip traffic only. Changing the raw interface does not show up a difference in this behaviour. Installing ifupdown-scripts-zg2 and ifupdown-scripts-extras does not change anything. Tested with amd64 on Asus M2A-VM board with RTL8111/8168B network chip a 3c905C-TX/TX-M [Tornado] network card. The error is reproducible. The same configuration works well on the 2.6.32 stock kernel. -- Package-specific info: ** Kernel log: boot messages should be attached currently unable to attach. -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-vserver-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.39-bpo.2-amd64 depends on: ii cdebconf [debconf-2.0]0.153+squeeze2 Debian Configuration Management Sy ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii initramfs-tools [linux-in 0.99~bpo60+1 tools for generating an initramfs ii linux-base3.3~bpo60+1Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.39-bpo.2-amd64 recommends: ii firmware-linux-free2.6.32-39squeeze1 Binary firmware for various driver Versions of packages linux-image-2.6.39-bpo.2-amd64 suggests: ii grub-pc1.98+20100804-14+squeeze1 GRand Unified Bootloader, version pn linux-doc-2.6. none(no description available) Versions of packages linux-image-2.6.39-bpo.2-amd64 is related to: ii firmware-bnx2 0.32~bpo60+1 Binary firmware for Broadcom NetXt ii firmware-bnx2x 0.32~bpo60+1 Binary firmware for Broadcom NetXt ii firmware-ipw2x000.32~bpo60+1 Binary firmware for Intel Pro Wire ii firmware-ivtv 0.32~bpo60+1 Binary firmware for iTVC15-family ii firmware-iwlwifi0.32~bpo60+1 Binary firmware for Intel Wireless ii firmware-linux 0.32~bpo60+1 Binary firmware for various driver ii firmware-linux-nonfree 0.32~bpo60+1 Binary firmware for various driver ii firmware-qlogic 0.32~bpo60+1 Binary firmware for QLogic IBA7220 ii firmware-ralink 0.32~bpo60+1 Binary firmware for Ralink wireles pn xen-hypervisor none (no description available) -- debconf information: linux-image-2.6.39-bpo.2-amd64/prerm/removing-running-kernel-2.6.39-bpo.2-amd64: true * linux-image-2.6.39-bpo.2-amd64/postinst/missing-firmware-2.6.39-bpo.2-amd64: linux-image-2.6.39-bpo.2-amd64/postinst/ignoring-ramdisk: linux-image-2.6.39-bpo.2-amd64/postinst/depmod-error-initrd-2.6.39-bpo.2-amd64: false -- 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/20120121144341.9515.59540.report...@truelove.intern.pekarek.at
Bug#615110: tpm_tis prevents suspend working more than once
On 20/01/12 08:46, Jonathan Nieder wrote: There have been some tpm fixes upstream recently, so results from testing v3.3-rc1 or later would be interesting. Jonathan Exactly the same results with v3.3-rc1 Linux carbon 3.3.0-rc1+ #4 SMP Sat Jan 21 15:46:40 CET 2012 i686 GNU/Linux (This is stock v3.3-rc1 with my Sony Vaio keyboard fixes). -- 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/4f1ad6b3.9070...@calvaedi.com
Processed: tagging 656754
Processing commands for cont...@bugs.debian.org: tags 656754 - d-i ipv6 Bug #656754 [linux-2.6] linux-image-2.6.39-bpo.2-amd64: vlan malfunction Removed tag(s) ipv6 and d-i. thanks Stopping processing here. Please contact me if you need assistance. -- 656754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656754 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.132716329918262.transcr...@bugs.debian.org
Bug#656754: linux-image-2.6.39-bpo.2-amd64: vlan malfunction
On Sat, 2012-01-21 at 15:43 +0100, Erich N. Pekarek wrote: Package: linux-2.6 Version: 2.6.39-3~bpo60+1 This is long outdated; please test 3.2.1-1 from unstable. Severity: important Tags: d-i ipv6 upstream What on earth has this to do with d-i or ipv6?! The network functionality is only guaranteed on the underlying network interface with vlanid 0. dmesg does not report any problems concerning vlan. The 8021q module is loaded. It can be loaded and unloaded without problems. Network interfaces and bridge interfaces which have been set up to use vlan can not be used. [...] It would have been nice if you'd actually provided some specific details of your network configuration, but I'm going to use my psychic powers to guess that you have something like: eth0 - physical interface br0 - bridge including eth0 eth0.N - VLAN interface attached to eth0 br1 - bridge including eth0.N and you expect VLAN-tagged packets that arrive on eth0 to be forwarded through br1, not br0? Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Processed: tagging 656754
Processing commands for cont...@bugs.debian.org: tags 656754 + moreinfo Bug #656754 [linux-2.6] linux-image-2.6.39-bpo.2-amd64: vlan malfunction Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 656754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656754 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.132716371420445.transcr...@bugs.debian.org
Bug#607551: Upstream status
Hi Ben, Has anything changed in the upstream status for this bug to justify a back port? As more people go on IPv6, what are options to work around otherwise? Thanks, -- - Pieter -- 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/camqg8jovqzkq5pasj8dl9yef675xbdsqnq5psa9qcam4-am...@mail.gmail.com
Bug#615110: tpm_tis prevents suspend working more than once
John Hughes wrote: Exactly the same results with v3.3-rc1 Thanks. Let's take this upstream. -- 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/20120121171619.GA17965@burratino
Bug#656786: non-existing lvds output is offered
Package: linux-image-3.1.0-1-amd64 Version: 3.1.8-2 lspci: … Display controller: Intel Corporation N10 Family Integrated Graphics Controller … The kernel offers a lvds output that does not exist. The mainboard (elitegroup ecs TIGT-I) does only have a VGA-out.The boot using video=LVDS-1:d seems to work. Don't know whether this influences xserver-xorg-video-intel extreme bad performence on fullscreen (intel nm10 chipset). I am using debian testing, standard 3.1.0-1-amd64 kernel delivered via the debian testing repository.
Bug#656695: linux-image-2.6.32-5-686-bigmem
Forwarded Message
From: JOHN HUNTER jmd...@btinternet.com
To: Ben Hutchings b...@decadent.org.uk
Subject: Re: Bug#656695: linux-image-2.6.32-5-686-bigmem
Date: Sat, 21 Jan 2012 18:46:58 + (GMT)
More information; you asked what were 'lilo's bleats.
I do not think that `lilo' is directly to blame; the warnings issued by the
lilo installer were:
Skipping /vmlinux.old
Warning: CHANGE AUTOMATIC assumed after other=/dev/sda1
Added Windows
Warning: CHANGE AUTOMATIC assumed after other=/dev/sda2
Added Windows1
Warning: CHANGE AUTOMATIC assumed after other=/dev/sda3
Added Windows2
3 warnings were issued
{end of lilo output}
The usual gang were all caused by a malfunctioning Windows 7 installation.
I have had something similar to this happen before. On the previous occasion,
the cause was the linux image was just too big; I cannot remember the
workaround which I applied then.
--- On Sat, 21/1/12, Ben Hutchings b...@decadent.org.uk wrote:
From: Ben Hutchings b...@decadent.org.uk
Subject: Re: Bug#656695: linux-image-2.6.32-5-686-bigmem
To: JOHN HUNTER jmd...@btinternet.com, 656...@bugs.debian.org
Date: Saturday, 21 January, 2012, 3:15
On Sat, 2012-01-21 at 01:42 +, JOHN HUNTER wrote:
Package: linux-image-2.6.32-5-686-bigmem
Severity: serious [ the system will not boot ]
Symptoms: boot fails almost immediately.
Using synaptic, the kernel was upgraded. I ran `lilo' with the usual
gang of warnings.
There shouldn't be any 'usual gang of warnings'. What did you see?
[...]
Loading, please wait ...
/init: /scripts/functions: line 394: syntax error: unexpected )
(expected ;;
This means something is wrong with the initramfs. It could be a bug in
initramfs-tools but I suspect that lilo is trying to load the wrong disk
blocks.
[...]
How can I get back to the previous kernel suite?
Use the 'rescue mode' of the installer. Start a shell in the installed
system. Then install an older kernel package from the 'stable' suite,
the CD or the APT cache.
You may also be able to do that starting from the live CD.
Ben.
--
Ben Hutchings
When in doubt, use brute force. - Ken Thompson
--
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/1327172229.8004.49.camel@deadeye
Processed: reassign 656695 to lilo
Processing commands for cont...@bugs.debian.org: reassign 656695 lilo Bug #656695 [linux-image-2.6.32-5-686-bigmem] lilo/initramfs breakage after upgrade Bug reassigned from package 'linux-image-2.6.32-5-686-bigmem' to 'lilo'. thanks Stopping processing here. Please contact me if you need assistance. -- 656695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656695 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.132717225414913.transcr...@bugs.debian.org
Bug#605090: definitely, a worth while patchset
Hey, This patch-set should replace linux-patch-grsecurity2.This patch-set provides excellent default settings and capability. For example, the user and group setup helps with creating consistent access user and group ids across servers. Most of the default kernel settings match with gentoo's hardened project kernel settings. Since this patch-set integrates with debian patch-sets, servers get benefits from both patch-sets. And, admins don't have to choose between patching the vanilla sources or resolving conflicts between the debian and grsec patch-sets. I believe a statistic needs to be done on how much of the grsec feature set is used by grsec users. For example, I use RBAC instead of SELINUX and Tomoyo almost always. There's also things like extra chroot security features that should be taken into consideration. My hypothesis for this statistic is that most grsec users use RBAC as well. For those that don't, I understand that a split between larger and smaller feature sets, PAX vs RBAC, would be helpful. For this split to happen, with grsec's history, I think a large interest needs to be shown for them to split the patch-set. So, if this is accepted, maybe the level of interest needed to get a split patch will be generated. Currently, I like this as a patch-set more than a binary because of security conflicts with things like xen. However, if I wasn't using xen, I would use the binary. (Note: I accidently sent this message to 605090-subscr...@bugs.debian.org first.) -
Bug#656802: linux-image-2.6.32-5-amd64: dmesg BUG: scheduling while atomic: ksoftirqd/0/4/0x10000100
Package: linux-2.6 Version: 2.6.32-39squeeze1 Severity: normal -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-39squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 9 20:49:59 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=ed36e35d-7bab-4e9f-8b03-8473ce122967 ro quiet ** Not tainted ** Kernel log: [148654.740747] xt_TCPMSS: bad length (41 bytes) [148656.341170] BUG: scheduling while atomic: ksoftirqd/0/4/0x1100 [148656.341402] Modules linked in: act_police sch_ingress cls_u32 sch_sfq sch_cbq dummy 8021q garp stp xt_TCPMSS ipt_REJECT xt_tcpudp xt_state xt_multiport iptable_filt er iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables xfs exportfs pppoe pppol2tp pptp pppox ppp_generic slhc loop firewire_sbp2 snd_hd a_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer nouveau ttm drm_kms_helper snd drm i2c_piix4 i2c_algo_bit i2c_core k10temp soundcore edac_core s nd_page_alloc edac_mce_amd pcspkr button wmi evdev processor ext3 jbd mbcache ata_generic sd_mod crc_t10dif ohci_hcd pata_via pata_atiixp tg3 libphy ahci ehci_hcd libat a ixgbe xhci firewire_ohci dca floppy usbcore thermal scsi_mod firewire_core nls_base crc_itu_t thermal_sys [last unloaded: scsi_wait_scan] [148656.341440] Pid: 4, comm: ksoftirqd/0 Not tainted 2.6.32-5-amd64 #1 [148656.341442] Call Trace: [148656.341443] IRQ [812facb8] ? schedule+0xc5/0x7b4 [148656.341453] [810963c9] ? handle_edge_irq+0xdd/0x101 [148656.341457] [8104aa4c] ? __cond_resched+0x1d/0x26 [148656.341459] [812fb5ab] ? _cond_resched+0x24/0x2f [148656.341463] [81243945] ? lock_sock_nested+0x16/0xab [148656.341465] [810114d3] ? ret_from_intr+0x0/0x11 [148656.341469] [a01a6b2a] ? pppol2tp_tunnel_destruct+0xe7/0x1f7 [pppol2tp] [148656.341472] [8124433f] ? __sk_free+0x15/0xe8 [148656.341474] [81247c06] ? skb_release_head_state+0x6d/0xc8 [148656.341476] [8124797a] ? __kfree_skb+0x9/0x7d [148656.341485] [a00cf989] ? ixgbe_poll+0x119/0x1840 [ixgbe] [148656.341489] [81272e08] ? ip_rcv_finish+0x0/0x38d [148656.341493] [8124fd8e] ? net_rx_action+0xae/0x1c9 [148656.341496] [81053d2b] ? __do_softirq+0xdd/0x1a6 [148656.341498] [81011cac] ? call_softirq+0x1c/0x30 [148656.341500] EOI [8101322b] ? do_softirq+0x3f/0x7c [148656.341503] [81053952] ? ksoftirqd+0x5f/0xd3 [148656.341505] [810538f3] ? ksoftirqd+0x0/0xd3 [148656.341508] [81064cc5] ? kthread+0x79/0x81 [148656.341510] [81011baa] ? child_rip+0xa/0x20 [148656.341512] [81064c4c] ? kthread+0x0/0x81 [148656.341514] [81011ba0] ? child_rip+0x0/0x20 [148656.373399] BUG: scheduling while atomic: ksoftirqd/0/4/0x1100 [148656.373628] Modules linked in: act_police sch_ingress cls_u32 sch_sfq sch_cbq dummy 8021q garp stp xt_TCPMSS ipt_REJECT xt_tcpudp xt_state xt_multiport iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables xfs exportfs pppoe pppol2tp pptp pppox ppp_generic slhc loop firewire_sbp2 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer nouveau ttm drm_kms_helper snd drm i2c_piix4 i2c_algo_bit i2c_core k10temp soundcore edac_core snd_page_alloc edac_mce_amd pcspkr button wmi evdev processor ext3 jbd mbcache ata_generic sd_mod crc_t10dif ohci_hcd pata_via pata_atiixp tg3 libphy ahci ehci_hcd libata ixgbe xhci firewire_ohci dca floppy usbcore thermal scsi_mod firewire_core nls_base crc_itu_t thermal_sys [last unloaded: scsi_wait_scan] [148656.373663] Pid: 4, comm: ksoftirqd/0 Not tainted 2.6.32-5-amd64 #1 [148656.373665] Call Trace: [148656.373667] IRQ [812facb8] ? schedule+0xc5/0x7b4 [148656.373675] [8101657d] ? read_tsc+0xa/0x20 [148656.373679] [810677c9] ? hrtimer_interrupt+0xe4/0x18d [148656.373683] [8104aa4c] ? __cond_resched+0x1d/0x26 [148656.373685] [812fb5ab] ? _cond_resched+0x24/0x2f [148656.373687] [81053bad] ? irq_exit+0x48/0x76 [148656.373691] [81243945] ? lock_sock_nested+0x16/0xab [148656.373694] [81024d58] ? smp_apic_timer_interrupt+0x87/0x95 [148656.373696] [81011673] ? apic_timer_interrupt+0x13/0x20 [148656.373700] [a01a6b2a] ? pppol2tp_tunnel_destruct+0xe7/0x1f7 [pppol2tp] [148656.373703] [8124433f] ? __sk_free+0x15/0xe8 [148656.373705] [81247c06] ? skb_release_head_state+0x6d/0xc8 [148656.373707] [8124797a] ? __kfree_skb+0x9/0x7d [148656.373715] [a00cf989] ? ixgbe_poll+0x119/0x1840 [ixgbe] [148656.373719] [81250891] ? dev_queue_xmit+0x35b/0x38d [148656.373721] [8124fd8e] ? net_rx_action+0xae/0x1c9 [148656.373723] [81053d2b] ? __do_softirq+0xdd/0x1a6 [148656.373726] [81011cac] ? call_softirq+0x1c/0x30
Bug#656812: linux-image-3.2.0-1-486: module dm-raid45/unix not found in modules.dep
Package: linux-2.6 Version: 3.2.1-1 Severity: normal I'm not sure if the kernel is the correct package for this bug: my apologize if i'm wrong. Since some version i see these messages on the early boot: --- Loading, please wait... modprobe: module dm-raid45 not found in modules.dep modprobe: module unix not found in modules.dep --- All is apparently functioning well, without problem that i might relate to the above messages. And my disk configuration is based on two simple ext3 partitions, so no raid. I've tried these with no effect: depmod update-initramfs -u Cesare. -- Package-specific info: ** Version: Linux version 3.2.0-1-486 (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 Thu Jan 19 09:52:54 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-486 root=UUID=07b633c9-1242-48ee-a6f4-f37c43f639fd ro quiet lapic hpet=force ** Not tainted ** Kernel log: [5.003498] ACPI: AC Adapter [ACAD] (on-line) [5.089981] yenta_cardbus :02:04.0: CardBus bridge found [104d:818f] [5.089998] yenta_cardbus :02:04.0: Using CSCINT to route CSC interrupts to PCI [5.090001] yenta_cardbus :02:04.0: Routing CardBus interrupts to PCI [5.090007] yenta_cardbus :02:04.0: TI: mfunc 0x01001b22, devctl 0x64 [5.209917] i801_smbus :00:1f.3: PCI INT B - Link[LNKB] - GSI 9 (level, low) - IRQ 9 [5.228994] lib80211: common routines for IEEE802.11 drivers [5.228997] lib80211_crypt: registered algorithm 'NULL' [5.295918] [drm] Initialized drm 1.1.0 20060810 [5.306805] intel_rng: FWH not detected [5.320758] yenta_cardbus :02:04.0: ISA IRQ mask 0x0cf8, PCI irq 9 [5.320763] yenta_cardbus :02:04.0: Socket status: 3006 [5.320768] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #02 to #06 [5.320780] yenta_cardbus :02:04.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff] [5.320785] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff: excluding 0x3000-0x303f 0x3400-0x34ff 0x3800-0x38ff [5.328197] yenta_cardbus :02:04.0: pcmcia: parent PCI bridge window: [mem 0xe020-0xe02f] [5.328202] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe020-0xe02f: excluding 0xe020-0xe020 [5.328220] yenta_cardbus :02:04.0: pcmcia: parent PCI bridge window: [mem 0x4400-0x47ff pref] [5.328224] pcmcia_socket pcmcia_socket0: cs: memory probe 0x4400-0x47ff: excluding 0x4400-0x47ff [5.341461] iTCO_vendor_support: vendor-support=0 [5.370645] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [5.370747] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [5.393935] i915 :00:02.0: PCI INT A - Link[LNKA] - GSI 9 (level, low) - IRQ 9 [5.393944] i915 :00:02.0: setting latency timer to 64 [5.396581] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.396585] [drm] Driver supports precise vblank timestamp query. [5.396671] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [5.426388] sony_laptop: Sony Programmable IO Control Driver v0.6 [5.426398] sony_laptop: detected Type2 model [5.427425] input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:0d/SNY6001:00/input/input5 [5.427596] input: Sony Vaio Jogdial as /devices/virtual/input/input6 [5.428429] sony_laptop: device allocated minor is 58 [5.432326] sony_laptop: Sony Notebook Control Driver v0.6 [5.582021] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x1f0-0x1f7 0x370-0x377 0x3c0-0x3df 0x3f0-0x3f7 0x4d0-0x4d7 [5.588804] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x800-0x8ff: clean. [5.590538] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff [5.596902] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc7fff 0xd8000-0xf [5.596938] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [5.596973] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: clean. [5.597008] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [5.604629] ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5 [5.604634] PCI: setting IRQ 5 as level-triggered [5.604642] tifm_7xx1 :02:04.3: PCI INT B - Link[LNKF] - GSI 5 (level, low) - IRQ 5 [5.624891] cfg80211: Calling CRDA to update world regulatory domain [5.628030] tifm_core: MMC/SD card detected in socket 0:0 [5.703150] libipw: 802.11 data/management/control stack, git-1.1.13 [5.703154] libipw: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [5.706517] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.706521] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.706644] ipw2200
Bug#656786: non-existing lvds output is offered
On Sat, Jan 21, 2012 at 19:08:13 +0100, eeemsi wrote: Package: linux-image-3.1.0-1-amd64 Version: 3.1.8-2 lspci: … Display controller: Intel Corporation N10 Family Integrated Graphics Controller … The kernel offers a lvds output that does not exist. The mainboard (elitegroup ecs TIGT-I) does only have a VGA-out.The boot using video=LVDS-1:d seems to work. Don't know whether this influences xserver-xorg-video-intel extreme bad performence on fullscreen (intel nm10 chipset). Please provide the full lspci -vnn, and dmesg with drm.debug=4. And use the reportbug utility next time. Cheers, Julien -- 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/20120121215721.gv9...@radis.cristau.org
Processed: reassign 656812 to module-init-tools
Processing commands for cont...@bugs.debian.org: reassign 656812 module-init-tools Bug #656812 [linux-2.6] linux-image-3.2.0-1-486: module dm-raid45/unix not found in modules.dep Bug reassigned from package 'linux-2.6' to 'module-init-tools'. Bug No longer marked as found in versions 3.2.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 656812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656812 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.1327183048336.transcr...@bugs.debian.org
Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!
Package: linux-2.6 Version: 3.2.1-1 Severity: normal Some kernel version ago (some version before #656812), i started to see this message on boot: --- waiting for /dev to be fully populated...[5.775083] cfg80211: failed to add phy80211 symlink to netdev! done. --- No apparent affect apart the message: the network seems functioning well. Cesare. -- Package-specific info: ** Version: Linux version 3.2.0-1-486 (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 Thu Jan 19 09:52:54 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-486 root=UUID=07b633c9-1242-48ee-a6f4-f37c43f639fd ro quiet lapic hpet=force ** Not tainted ** Kernel log: [5.003498] ACPI: AC Adapter [ACAD] (on-line) [5.089981] yenta_cardbus :02:04.0: CardBus bridge found [104d:818f] [5.089998] yenta_cardbus :02:04.0: Using CSCINT to route CSC interrupts to PCI [5.090001] yenta_cardbus :02:04.0: Routing CardBus interrupts to PCI [5.090007] yenta_cardbus :02:04.0: TI: mfunc 0x01001b22, devctl 0x64 [5.209917] i801_smbus :00:1f.3: PCI INT B - Link[LNKB] - GSI 9 (level, low) - IRQ 9 [5.228994] lib80211: common routines for IEEE802.11 drivers [5.228997] lib80211_crypt: registered algorithm 'NULL' [5.295918] [drm] Initialized drm 1.1.0 20060810 [5.306805] intel_rng: FWH not detected [5.320758] yenta_cardbus :02:04.0: ISA IRQ mask 0x0cf8, PCI irq 9 [5.320763] yenta_cardbus :02:04.0: Socket status: 3006 [5.320768] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #02 to #06 [5.320780] yenta_cardbus :02:04.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff] [5.320785] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff: excluding 0x3000-0x303f 0x3400-0x34ff 0x3800-0x38ff [5.328197] yenta_cardbus :02:04.0: pcmcia: parent PCI bridge window: [mem 0xe020-0xe02f] [5.328202] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe020-0xe02f: excluding 0xe020-0xe020 [5.328220] yenta_cardbus :02:04.0: pcmcia: parent PCI bridge window: [mem 0x4400-0x47ff pref] [5.328224] pcmcia_socket pcmcia_socket0: cs: memory probe 0x4400-0x47ff: excluding 0x4400-0x47ff [5.341461] iTCO_vendor_support: vendor-support=0 [5.370645] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [5.370747] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [5.393935] i915 :00:02.0: PCI INT A - Link[LNKA] - GSI 9 (level, low) - IRQ 9 [5.393944] i915 :00:02.0: setting latency timer to 64 [5.396581] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.396585] [drm] Driver supports precise vblank timestamp query. [5.396671] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [5.426388] sony_laptop: Sony Programmable IO Control Driver v0.6 [5.426398] sony_laptop: detected Type2 model [5.427425] input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:0d/SNY6001:00/input/input5 [5.427596] input: Sony Vaio Jogdial as /devices/virtual/input/input6 [5.428429] sony_laptop: device allocated minor is 58 [5.432326] sony_laptop: Sony Notebook Control Driver v0.6 [5.582021] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x4ff: excluding 0x170-0x177 0x1f0-0x1f7 0x370-0x377 0x3c0-0x3df 0x3f0-0x3f7 0x4d0-0x4d7 [5.588804] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x800-0x8ff: clean. [5.590538] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff [5.596902] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc7fff 0xd8000-0xf [5.596938] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [5.596973] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: clean. [5.597008] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [5.604629] ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5 [5.604634] PCI: setting IRQ 5 as level-triggered [5.604642] tifm_7xx1 :02:04.3: PCI INT B - Link[LNKF] - GSI 5 (level, low) - IRQ 5 [5.624891] cfg80211: Calling CRDA to update world regulatory domain [5.628030] tifm_core: MMC/SD card detected in socket 0:0 [5.703150] libipw: 802.11 data/management/control stack, git-1.1.13 [5.703154] libipw: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [5.706517] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.706521] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.706644] ipw2200 :02:0b.0: power state changed by ACPI to D0 [5.706650] ipw2200 :02:0b.0: power state changed by ACPI to D0 [5.706662] ipw2200 :02:0b.0: PCI INT A - Link[LNKD] - GSI 9 (level, low) - IRQ 9 [5.706685]
Bug#656824: marked as done (linux-image-3.2.0-1-amd64 Boot Failure)
Your message dated Sun, 22 Jan 2012 00:18:44 + with message-id 1327191524.8004.51.camel@deadeye and subject line Re: Bug#656824: linux-image-3.2.0-1-amd64 Boot Failure has caused the Debian Bug report #656824, regarding linux-image-3.2.0-1-amd64 Boot Failure 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.) -- 656824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.1-1 Severity: normal Dear Maintainer, After installing this kernel I was not able to boot to it and received the following error on the console. Loading Linux 3.2.0-1-amd64 ... error: cannot read the Linux header. Loading intitial ramdisk ... error: you need to load the kernel first. press any key to continue... I use LVM with XFS on top of that, not sure if that has any relevance. I also received a time out when Querying Debian BTS for reports on linux-2.6 (source)... So apologies if this bug has already been reported. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 27327YM product_version: ThinkPad R500 chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: 7YET83WW (3.13 ) board_vendor: LENOVO board_name: 27327YM board_version: Not Available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Lenovo Device [17aa:20e0] 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 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) (prog-if 00 [Normal decode]) 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, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: f800-f80f Prefetchable memory behind bridge: f000-f7ff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) Subsystem: Lenovo Device [17aa:20e6] 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 f8504800 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo Device [17aa:20f0] 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 20 Region 4: I/O ports at 1800 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo Device [17aa:20f0] 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 21 Region 4: I/O ports at 1820 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03)
Re: Linux kernel version for wheezy
If I don't hear any objections from the kernel team in the next week, I'm going to assume that everyone is happy to go with Linux 3.2. The decision needs to be communicated to Debian developers in general (d-d-a) and to Greg Kroah-Hartman in his capacity as organiser of stable/longterm series. If we go with 3.2 then we will also want to work closely with the Ubuntu kernel maintainers. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!
On Sat, 2012-01-21 at 22:58 +0100, Cesare Leonardi wrote:
Package: linux-2.6
Version: 3.2.1-1
Severity: normal
Some kernel version ago (some version before #656812), i started to see
this message on boot:
---
waiting for /dev to be fully populated...[5.775083] cfg80211: failed
to add phy80211 symlink to netdev!
done.
---
No apparent affect apart the message: the network seems functioning
well.
[...]
Can you test whether the attache patch fixes this (and doesn't cause any
new problems)? Instructions for rebuilding the kernel package are at:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
Ben.
--
Ben Hutchings
Knowledge is power. France is bacon.
From 8f5f91cb3ba851ddef1829c89326438ab210a6e2 Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Sun, 22 Jan 2012 00:55:29 +
Subject: [PATCH] ipw2200: Fix order of device registration
Currently cfg80211 fails to create a phy80211 symlink in sysfs from
the net device to the wiphy device. The latter needs to be registered
first.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/net/wireless/ipw2x00/ipw2200.c | 23 ---
1 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/drivers/net/wireless/ipw2x00/ipw2200.c b/drivers/net/wireless/ipw2x00/ipw2200.c
index 99a710d..6e4aec3 100644
--- a/drivers/net/wireless/ipw2x00/ipw2200.c
+++ b/drivers/net/wireless/ipw2x00/ipw2200.c
@@ -11830,16 +11830,17 @@ static int __devinit ipw_pci_probe(struct pci_dev *pdev,
}
mutex_unlock(priv-mutex);
- err = register_netdev(net_dev);
+
+ err = ipw_wdev_init(net_dev);
if (err) {
- IPW_ERROR(failed to register network device\n);
+ IPW_ERROR(failed to register wireless device\n);
goto out_remove_sysfs;
}
- err = ipw_wdev_init(net_dev);
+ err = register_netdev(net_dev);
if (err) {
- IPW_ERROR(failed to register wireless device\n);
- goto out_unregister_netdev;
+ IPW_ERROR(failed to register network device\n);
+ goto out_unregister_wiphy;
}
#ifdef CONFIG_IPW2200_PROMISCUOUS
@@ -11848,10 +11849,8 @@ static int __devinit ipw_pci_probe(struct pci_dev *pdev,
if (err) {
IPW_ERROR(Failed to register promiscuous network
device (error %d).\n, err);
- wiphy_unregister(priv-ieee-wdev.wiphy);
- kfree(priv-ieee-a_band.channels);
- kfree(priv-ieee-bg_band.channels);
- goto out_unregister_netdev;
+ unregister_netdev(priv-net_dev);
+ goto out_unregister_wiphy;
}
}
#endif
@@ -11863,8 +11862,10 @@ static int __devinit ipw_pci_probe(struct pci_dev *pdev,
return 0;
- out_unregister_netdev:
- unregister_netdev(priv-net_dev);
+ out_unregister_wiphy:
+ wiphy_unregister(priv-ieee-wdev.wiphy);
+ kfree(priv-ieee-a_band.channels);
+ kfree(priv-ieee-bg_band.channels);
out_remove_sysfs:
sysfs_remove_group(pdev-dev.kobj, ipw_attribute_group);
out_release_irq:
--
1.7.8.2
signature.asc
Description: This is a digitally signed message part
Processed: tagging 656813
Processing commands for cont...@bugs.debian.org: tags 656813 + patch moreinfo Bug #656813 [linux-2.6] cfg80211: failed to add phy80211 symlink to netdev! Added tag(s) moreinfo and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 656813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656813 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.13271947549910.transcr...@bugs.debian.org
Bug#656802: linux-image-2.6.32-5-amd64: dmesg BUG: scheduling while atomic: ksoftirqd/0/4/0x10000100
On Sat, 2012-01-21 at 22:19 +0200, alex wrote: [...] [148654.740747] xt_TCPMSS: bad length (41 bytes) [148656.341170] BUG: scheduling while atomic: ksoftirqd/0/4/0x1100 [148656.341402] Modules linked in: act_police sch_ingress cls_u32 sch_sfq sch_cbq dummy 8021q garp stp xt_TCPMSS ipt_REJECT xt_tcpudp xt_state xt_multiport iptable_filt er iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables xfs exportfs pppoe pppol2tp pptp pppox ppp_generic slhc loop firewire_sbp2 snd_hd a_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer nouveau ttm drm_kms_helper snd drm i2c_piix4 i2c_algo_bit i2c_core k10temp soundcore edac_core s nd_page_alloc edac_mce_amd pcspkr button wmi evdev processor ext3 jbd mbcache ata_generic sd_mod crc_t10dif ohci_hcd pata_via pata_atiixp tg3 libphy ahci ehci_hcd libat a ixgbe xhci firewire_ohci dca floppy usbcore thermal scsi_mod firewire_core nls_base crc_itu_t thermal_sys [last unloaded: scsi_wait_scan] [148656.341440] Pid: 4, comm: ksoftirqd/0 Not tainted 2.6.32-5-amd64 #1 [148656.341442] Call Trace: [148656.341443] IRQ [812facb8] ? schedule+0xc5/0x7b4 [148656.341453] [810963c9] ? handle_edge_irq+0xdd/0x101 [148656.341457] [8104aa4c] ? __cond_resched+0x1d/0x26 [148656.341459] [812fb5ab] ? _cond_resched+0x24/0x2f [148656.341463] [81243945] ? lock_sock_nested+0x16/0xab [148656.341465] [810114d3] ? ret_from_intr+0x0/0x11 [148656.341469] [a01a6b2a] ? pppol2tp_tunnel_destruct+0xe7/0x1f7 [pppol2tp] [148656.341472] [8124433f] ? __sk_free+0x15/0xe8 [148656.341474] [81247c06] ? skb_release_head_state+0x6d/0xc8 [148656.341476] [8124797a] ? __kfree_skb+0x9/0x7d [148656.341485] [a00cf989] ? ixgbe_poll+0x119/0x1840 [ixgbe] [148656.341489] [81272e08] ? ip_rcv_finish+0x0/0x38d [148656.341493] [8124fd8e] ? net_rx_action+0xae/0x1c9 [148656.341496] [81053d2b] ? __do_softirq+0xdd/0x1a6 [148656.341498] [81011cac] ? call_softirq+0x1c/0x30 [...] It appears that a transmit completion results in dropping the last reference to a PPPoL2TP tunnel, causing it to be destroyed. pppo2ltp_tunnel_destruct() calls pppo2ltp_tunnel_closeall() (inlined here) which calls lock_sock(), and that may sleep. Although this was observed in 2.6.32, the bug appears to be present today: l2tp_tunnel_destruct() calls l2tp_tunnel_closeall() calls pppol2tp_session_close() calls lock_sock(). But maybe this is actually a ref-counting bug and the tunnel should never actually be destroyed in atomic context. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Processed: bug 656802 is forwarded to net...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: forwarded 656802 net...@vger.kernel.org Bug #656802 [linux-2.6] linux-image-2.6.32-5-amd64: dmesg BUG: scheduling while atomic: ksoftirqd/0/4/0x1100 Set Bug forwarded-to-address to 'net...@vger.kernel.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 656802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656802 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.132719594018263.transcr...@bugs.debian.org
Processed: tagging 607551
Processing commands for cont...@bugs.debian.org: tags 607551 + ipv6 Bug #607551 [linux-2.6] [linux-image-2.6.32-5-amd64] IPV6 and ethernet bonding Added tag(s) ipv6. thanks Stopping processing here. Please contact me if you need assistance. -- 607551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607551 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.132719596518323.transcr...@bugs.debian.org
Bug#607551: Upstream status
On Sat, 2012-01-21 at 17:01 +, Pieter Ennes wrote: Hi Ben, Has anything changed in the upstream status for this bug to justify a back port? Sorry, I don't believe this can be fixed in Debian 6.0 'squeeze'. There have been many other changes to the IPv6 address configuration code and I don't think we can safely cherry-pick these. As more people go on IPv6, what are options to work around otherwise? Install a kernel from testing/unstable. You will currently find Linux 3.2 in unstable, and this is likely to be the version we use in Debian 7.0 'wheezy'. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Processed: tagging 607551, fixed 607551 in 2.6.37~rc4-1~experimental.1
Processing commands for cont...@bugs.debian.org: # Patches are not applicable to 2.6.32 tags 607551 - patch Bug #607551 [linux-2.6] [linux-image-2.6.32-5-amd64] IPV6 and ethernet bonding Removed tag(s) patch. # Fixed upstream in 2.6.37-rc1 fixed 607551 2.6.37~rc4-1~experimental.1 Bug #607551 [linux-2.6] [linux-image-2.6.32-5-amd64] IPV6 and ethernet bonding There is no source info for the package 'linux-2.6' at version '2.6.37~rc4-1~experimental.1' with architecture '' Unable to make a source version for version '2.6.37~rc4-1~experimental.1' Bug Marked as fixed in versions 2.6.37~rc4-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 607551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607551 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.13271988483581.transcr...@bugs.debian.org
Processed: tagging 607551
Processing commands for cont...@bugs.debian.org: tags 607551 + wontfix Bug #607551 [linux-2.6] [linux-image-2.6.32-5-amd64] IPV6 and ethernet bonding Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 607551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607551 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.13271988583638.transcr...@bugs.debian.org
Bug#656724: linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ...
On Sat, 2012-01-21 at 11:37 +0100, Antonio-M. Corbi Bellot wrote: Package: linux-2.6 Version: 3.2.1-1 Severity: normal Dear Maintainer, After installing this kernel I repeatedly get this kind of messages on any terminal I use: Message from syslogd@pbell-acb at Jan 21 11:31:32 ... kernel:[ 1039.072638] Code: c0 89 c5 74 04 80 63 1c fb 48 83 c4 38 89 e8 5b 5d 41 5c 41 5d c3 90 0f 09 66 66 90 66 90 c3 fa 66 66 90 66 66 90 c3 fb 66 66 90 66 66 90 c3 48 8b 15 2d f1 56 e1 48 8d 42 fd 48 83 f8 01 0f 96 A more detailed explanation of the failure is in the log attached. [...] Can you send the kernel log from boot up to and including the first such error? You can probably find this in /var/log/dmesg. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Processed: tagging 656642
Processing commands for cont...@bugs.debian.org: tags 656642 + pending Bug #656642 [src:linux-latest] [INTL:da] Danish translation of the debconf templates linux-latest-2.6 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 656642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656642 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.13271993815810.transcr...@bugs.debian.org
Processed: tagging 654681
Processing commands for cont...@bugs.debian.org: tags 654681 + pending Bug #654681 [src:linux-latest] [INTL:es] Spanish debconf template translation for linux-latest-2.6 Bug #654354 [src:linux-latest] [INTL:es] Spanish debconf template translation for linux-latest-2.6 Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 654681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654681 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.13271995166796.transcr...@bugs.debian.org
Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!
On 22/01/2012 02:12, Ben Hutchings wrote: Can you test whether the attache patch fixes this (and doesn't cause any new problems)? Instructions for rebuilding the kernel package are at: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official Looking inside your patch i've learned it's related to wifi. That could explain why i haven't seen any problem so far, because i use this laptop always with a cabled ethernet. This is a problem to test your patch, because i have no wireless network at hand. The other problem is the current lack of time: i hope i can find some time to learn how to build kernels nowadays, then doing it on my old hardware, but i cannot guarantee. It would be really really helpful and time saving if you could provide me a patched .deb kernel. In that case i'll do my best to find a temporary access point to test. Thank you as usual, Ben. Cesare. -- 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/4f1b757c.8000...@gmail.com
Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!
On Sun, 2012-01-22 at 03:33 +0100, Cesare Leonardi wrote: On 22/01/2012 02:12, Ben Hutchings wrote: Can you test whether the attache patch fixes this (and doesn't cause any new problems)? Instructions for rebuilding the kernel package are at: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official Looking inside your patch i've learned it's related to wifi. That could explain why i haven't seen any problem so far, because i use this laptop always with a cabled ethernet. This is a problem to test your patch, because i have no wireless network at hand. The other problem is the current lack of time: i hope i can find some time to learn how to build kernels nowadays, then doing it on my old hardware, but i cannot guarantee. It would be really really helpful and time saving if you could provide me a patched .deb kernel. In that case i'll do my best to find a temporary access point to test. Then don't worry about it. I'll send the patch upstream for review. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#656813: [PATCH 1/2] ipw2200: Fix order of device registration
Currently cfg80211 fails to create a phy80211 symlink in sysfs from
the net device to the wiphy device. The latter needs to be registered
first.
Compile-tested only.
Reported-by: Cesare Leonardi celeo...@gmail.com
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/net/wireless/ipw2x00/ipw2200.c | 23 ---
1 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/drivers/net/wireless/ipw2x00/ipw2200.c
b/drivers/net/wireless/ipw2x00/ipw2200.c
index 018a8de..737dfaf 100644
--- a/drivers/net/wireless/ipw2x00/ipw2200.c
+++ b/drivers/net/wireless/ipw2x00/ipw2200.c
@@ -11839,16 +11839,17 @@ static int __devinit ipw_pci_probe(struct pci_dev
*pdev,
}
mutex_unlock(priv-mutex);
- err = register_netdev(net_dev);
+
+ err = ipw_wdev_init(net_dev);
if (err) {
- IPW_ERROR(failed to register network device\n);
+ IPW_ERROR(failed to register wireless device\n);
goto out_remove_sysfs;
}
- err = ipw_wdev_init(net_dev);
+ err = register_netdev(net_dev);
if (err) {
- IPW_ERROR(failed to register wireless device\n);
- goto out_unregister_netdev;
+ IPW_ERROR(failed to register network device\n);
+ goto out_unregister_wiphy;
}
#ifdef CONFIG_IPW2200_PROMISCUOUS
@@ -11857,10 +11858,8 @@ static int __devinit ipw_pci_probe(struct pci_dev
*pdev,
if (err) {
IPW_ERROR(Failed to register promiscuous network
device (error %d).\n, err);
- wiphy_unregister(priv-ieee-wdev.wiphy);
- kfree(priv-ieee-a_band.channels);
- kfree(priv-ieee-bg_band.channels);
- goto out_unregister_netdev;
+ unregister_netdev(priv-net_dev);
+ goto out_unregister_wiphy;
}
}
#endif
@@ -11872,8 +11871,10 @@ static int __devinit ipw_pci_probe(struct pci_dev
*pdev,
return 0;
- out_unregister_netdev:
- unregister_netdev(priv-net_dev);
+ out_unregister_wiphy:
+ wiphy_unregister(priv-ieee-wdev.wiphy);
+ kfree(priv-ieee-a_band.channels);
+ kfree(priv-ieee-bg_band.channels);
out_remove_sysfs:
sysfs_remove_group(pdev-dev.kobj, ipw_attribute_group);
out_release_irq:
--
1.7.8.2
--
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/1327201775.8004.83.camel@deadeye
Bug#656813: [PATCH 2/2] ipw2100: Fix order of device registration
Currently cfg80211 fails to create a phy80211 symlink in sysfs from
the net device to the wiphy device. The latter needs to be registered
first.
Compile-tested only.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
This appears to have the same bug as ipw2200.
Ben.
drivers/net/wireless/ipw2x00/ipw2100.c | 24 +---
1 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/drivers/net/wireless/ipw2x00/ipw2100.c
b/drivers/net/wireless/ipw2x00/ipw2100.c
index a0e5c21..a5437e7 100644
--- a/drivers/net/wireless/ipw2x00/ipw2100.c
+++ b/drivers/net/wireless/ipw2x00/ipw2100.c
@@ -1956,10 +1956,8 @@ static int ipw2100_wdev_init(struct net_device *dev)
}
set_wiphy_dev(wdev-wiphy, priv-pci_dev-dev);
- if (wiphy_register(wdev-wiphy)) {
- ipw2100_down(priv);
+ if (wiphy_register(wdev-wiphy))
return -EIO;
- }
return 0;
}
@@ -6337,6 +6335,11 @@ static int ipw2100_pci_init_one(struct pci_dev *pci_dev,
printk(KERN_INFO DRV_NAME
: Detected Intel PRO/Wireless 2100 Network Connection\n);
+ err = ipw2100_wdev_init(dev);
+ if (err)
+ goto fail;
+ registered = 1;
+
/* Bring up the interface. Pre 0.46, after we registered the
* network device we would call ipw2100_up. This introduced a race
* condition with newer hotplug configurations (network was coming
@@ -6353,11 +6356,7 @@ static int ipw2100_pci_init_one(struct pci_dev *pci_dev,
Error calling register_netdev.\n);
goto fail;
}
- registered = 1;
-
- err = ipw2100_wdev_init(dev);
- if (err)
- goto fail;
+ registered = 2;
mutex_lock(priv-action_mutex);
@@ -6396,13 +6395,16 @@ static int ipw2100_pci_init_one(struct pci_dev *pci_dev,
fail_unlock:
mutex_unlock(priv-action_mutex);
- wiphy_unregister(priv-ieee-wdev.wiphy);
- kfree(priv-ieee-bg_band.channels);
fail:
if (dev) {
- if (registered)
+ if (registered = 2)
unregister_netdev(dev);
+ if (registered) {
+ wiphy_unregister(priv-ieee-wdev.wiphy);
+ kfree(priv-ieee-bg_band.channels);
+ }
+
ipw2100_hw_stop_adapter(priv);
ipw2100_disable_interrupts(priv);
--
1.7.8.2
--
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/1327201872.8004.85.camel@deadeye
Bug#656813: [PATCH 1/2] ipw2200: Fix order of device registration
Hi On Sunday 22 January 2012, Ben Hutchings wrote: Currently cfg80211 fails to create a phy80211 symlink in sysfs from the net device to the wiphy device. The latter needs to be registered first. Compile-tested only. Reported-by: Cesare Leonardi celeo...@gmail.com Signed-off-by: Ben Hutchings b...@decadent.org.uk --- drivers/net/wireless/ipw2x00/ipw2200.c | 23 --- 1 files changed, 12 insertions(+), 11 deletions(-) I've tested this patch on my ipw2200 (inside an Acer TravelMate 292LMi). While the original [5.525347] libipw: 802.11 data/management/control stack, git-1.1.13 [5.525352] libipw: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com […] [5.787605] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.787610] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.787742] ipw2200 :02:02.0: power state changed by ACPI to D0 [5.787749] ipw2200 :02:02.0: power state changed by ACPI to D0 [5.787762] ipw2200 :02:02.0: PCI INT A - Link[LNKC] - GSI 10 (level, low) - IRQ 10 [5.787789] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [6.120089] cfg80211: failed to add phy80211 symlink to netdev! [6.120373] ipw2200: Detected geography ZZG (13 802.11bg channels, 0 802.11a channels) [6.138818] udevd[252]: renamed network interface eth1 to wlan0 […] [8.744754] acerhk: registered input device [8.744878] input: Acer hotkey driver as /devices/virtual/input/input7 [8.747175] acerhk: forced laptop series to 290 [8.747184] acerhk: enabling dritek keyboard extension [8.747704] acerhk: bios routine found at 0xc00fdf22 [8.747706] Acer Travelmate hotkey driver v0.5.35 […] [ 15.107990] lib80211_crypt: registered algorithm 'CCMP' [ 15.276082] Intel AES-NI instructions are not detected. [ 24.386037] wlan0: no IPv6 routers present [wlan available] is almost cosmetic, without any apparent ill-effects, applying that patch to kernel 3.2.1 (not exactly Debian's - e.g. I need acerhk/ dritek to disable rfkill for that card, but it should be close enough) results in this trace: [5.708938] libipw: 802.11 data/management/control stack, git-1.1.13 [5.708942] libipw: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com […] [5.785178] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.785184] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.785323] ipw2200 :02:02.0: power state changed by ACPI to D0 [5.785330] ipw2200 :02:02.0: power state changed by ACPI to D0 [5.785344] ipw2200 :02:02.0: PCI INT A - Link[LNKC] - GSI 10 (level, low) - IRQ 10 [5.785370] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [5.785416] [ cut here ] [5.785435] WARNING: at /tmp/buildd/linux-aptosid-3.2/debian/build/source_i386_none/net/wireless/core.c:562 wiphy_register+0x45/0x38d [cfg80211]() [5.785440] Hardware name: TravelMate 290 \x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x [5.785443] Modules linked in: ipw2200(+) iTCO_wdt libipw joydev drm snd_seq snd_timer snd_seq_device iTCO_vendor_support yenta_socket snd intel_agp i2c_i801 pcmcia_rsrc cfg80211 soundcore parport_pc psmouse parport rng_core snd_page_alloc serio_raw pcspkr i2c_algo_bit intel_gtt pcmcia_core evdev irda crc_ccitt rfkill lib80211 processor container ac battery shpchp pci_hotplug button ext4 mbcache jbd2 crc16 dm_mod sd_mod sr_mod crc_t10dif cdrom ata_generic pata_acpi ata_piix libata scsi_mod firewire_ohci firewire_core crc_itu_t 8139too 8139cp mii uhci_hcd ehci_hcd usbcore usb_common [last unloaded: scsi_wait_scan] [5.785512] Pid: 328, comm: modprobe Not tainted 3.2-1.slh.4-aptosid-686 #1 [5.785515] Call Trace: [5.785527] [c012eaf4] ? warn_slowpath_common+0x7c/0x8f [5.785538] [e0ff0b3e] ? wiphy_register+0x45/0x38d [cfg80211] [5.785549] [e0ff0b3e] ? wiphy_register+0x45/0x38d [cfg80211] [5.785554] [c012eb22] ? warn_slowpath_null+0x1b/0x1f [5.785565] [e0ff0b3e] ? wiphy_register+0x45/0x38d [cfg80211] [5.785574] [c01f89d7] ? internal_create_group+0xf5/0xff [5.785589] [e0a2de1c] ? ipw_pci_probe+0xa9a/0xbd0 [ipw2200] [5.785597] [c01519f4] ? arch_local_irq_save+0xf/0x14 [5.785605] [c0252986] ? pci_device_probe+0x53/0x9a [5.785612] [c02c2820] ? driver_probe_device+0x94/0x124 [5.785617] [c0252871] ? pci_match_id+0x15/0x34 [5.785622] [c02c28f0] ? __driver_attach+0x40/0x5b [5.785626] [c02c1d81] ? bus_for_each_dev+0x37/0x60 [5.785631] [c02c25aa] ? driver_attach+0x17/0x1a [5.785636] [c02c28b0] ? driver_probe_device+0x124/0x124 [5.785641] [c02c22c4] ? bus_add_driver+0x92/0x1d1 [5.785648] [e099d000] ? 0xe099cfff [5.785652] [c02c2cb8] ? driver_register+0x7d/0xd4 [
Bug#656476: linux-image-2.6.32-5-686: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable
On Thu, 2012-01-19 at 17:55 +0100, Mike . wrote: Package: linux-2.6 Version: 2.6.32-39squeeze1 Severity: important *** Please type your report below this line *** Network traffic on my D-Link DFE-580TX card results in a transmit queue timeout and gives endless resets after that untill the interface is brought down. The amount of traffic required to generate the error seems to vary but sooner rather then later it will occur. The 1218.002863 - 1226.000260 part of the log repeats itself (with different TxFrameId's) until the interface is brought down. [...] Please test whether this also occurs under Linux 3.2, currently available in unstable (the package name is linux-3.2.0-1-686-pae). Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Processed: tagging 656476
Processing commands for cont...@bugs.debian.org: tags 656476 + moreinfo Bug #656476 [linux-2.6] linux-image-2.6.32-5-686: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 656476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656476 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.13272051938705.transcr...@bugs.debian.org
Bug#656813: [PATCH 1/2] ipw2200: Fix order of device registration
On Sun, 2012-01-22 at 04:32 +0100, Stefan Lippers-Hollmann wrote:
Hi
On Sunday 22 January 2012, Ben Hutchings wrote:
Currently cfg80211 fails to create a phy80211 symlink in sysfs from
the net device to the wiphy device. The latter needs to be registered
first.
Compile-tested only.
Reported-by: Cesare Leonardi celeo...@gmail.com
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/net/wireless/ipw2x00/ipw2200.c | 23 ---
1 files changed, 12 insertions(+), 11 deletions(-)
I've tested this patch on my ipw2200 (inside an Acer TravelMate 292LMi).
While the original
[...]
is almost cosmetic, without any apparent ill-effects, applying that
patch to kernel 3.2.1 (not exactly Debian's - e.g. I need acerhk/
dritek to disable rfkill for that card, but it should be close enough)
results in this trace:
[5.708938] libipw: 802.11 data/management/control stack, git-1.1.13
[5.708942] libipw: Copyright (C) 2004-2005 Intel Corporation
jketr...@linux.intel.com
[…]
[5.785178] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.2.2kmprq
[5.785184] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[5.785323] ipw2200 :02:02.0: power state changed by ACPI to D0
[5.785330] ipw2200 :02:02.0: power state changed by ACPI to D0
[5.785344] ipw2200 :02:02.0: PCI INT A - Link[LNKC] - GSI 10
(level, low) - IRQ 10
[5.785370] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[5.785416] [ cut here ]
[5.785435] WARNING: at
/tmp/buildd/linux-aptosid-3.2/debian/build/source_i386_none/net/wireless/core.c:562
wiphy_register+0x45/0x38d [cfg80211]()
[...]
Which is:
if (!have_band) {
WARN_ON(1);
return -EINVAL;
}
and have_band is set if any element of wiphy-bands[] is non-NULL.
ipw_wdev_init() clearly does initialise wiphy-bands... except that it
seems to depend on the regulatory area having been determined already,
which I suppose must be done during the callback from netdev
registration (ipw_net_init()). Judging by the comment about this in
ipw2100.c, it's probably important that initialisation is done in this
order.
So maybe cfg80211 should instead tolerate registration in this order?
Ben.
--
Ben Hutchings
Knowledge is power. France is bacon.
signature.asc
Description: This is a digitally signed message part
Bug#656824: linux-image-3.2.0-1-amd64 Boot Failure
On 22.01.12 10:41, James Robertson wrote: Package: linux-2.6 Version: 3.2.1-1 Severity: normal Dear Maintainer, After installing this kernel I was not able to boot to it and received the following error on the console. Loading Linux 3.2.0-1-amd64 ... error: cannot read the Linux header. Loading intitial ramdisk ... error: you need to load the kernel first. press any key to continue... I use LVM with XFS on top of that, not sure if that has any relevance. I also received a time out when Querying Debian BTS for reports on linux-2.6 (source)... So apologies if this bug has already been reported. Same here. Thinkpad T500+LVM+XFS: $ mount | grep root /dev/mapper/vg0-root on / type xfs (rw,nodev,relatime,attr2,delaylog,noquota) $ ls -l /boot/ total 47772 -rw-r--r-- 1 root root 125263 Aug 27 19:54 config-3.0.0-1-amd64 -rw-r--r-- 1 root root 128350 Dec 23 18:12 config-3.1.0-1-amd64 -rw-r--r-- 1 root root 130657 Jan 19 11:48 config-3.2.0-1-amd64 drwxr-xr-x 3 root root 8192 Jan 21 08:53 grub -rw-r--r-- 1 root root 11230400 Nov 21 17:18 initrd.img-3.0.0-1-amd64 -rw-r--r-- 1 root root 11342985 Jan 21 08:07 initrd.img-3.1.0-1-amd64 -rw-r--r-- 1 root root 11585465 Jan 21 08:53 initrd.img-3.2.0-1-amd64 -rw-r--r-- 1 root root 2007368 Aug 27 19:54 System.map-3.0.0-1-amd64 -rw-r--r-- 1 root root 2034035 Dec 23 18:12 System.map-3.1.0-1-amd64 -rw-r--r-- 1 root root 2072539 Jan 19 11:48 System.map-3.2.0-1-amd64 -rw-r--r-- 1 root root 2705680 Aug 27 19:49 vmlinuz-3.0.0-1-amd64 -rw-r--r-- 1 root root 2727792 Dec 23 18:10 vmlinuz-3.1.0-1-amd64 -rw-r--r-- 1 root root 2779248 Jan 21 08:54 vmlinuz-3.2.0-1-amd64 The grubshell can display the kernel image but isn't be able to load it: grub ls (vg0-root)/boot/ kern/disk.c:245: Opening `vg0-root'... grub/ config-3.0.0-1-amd64 vmlinuz-3.0.0-1-amd64 System.map-3.0.0-1-amd64 initrd.img-3.0.0-1-amd64 vmlinuz-3.1.0-1-amd64 config-3.1.0-1-amd64 System.map-3.1.0-1-amd64 initrd.img-3.1.0-1-amd64 config-3.2.0-1-amd64 System.map-3.2.0-1-amd64 initrd.img-3.2.0-1-amd64 vmlinuz-3.2.0-1-amd64 kern/disk.c:330: Closing `vg0-root'. grub linux (vg0-root)/boot/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/vg0-root ro kern/disk.c:245: Opening `vg0-root'... kern/disk.c:330: Closing `vg0-root'. error: cannot read the Linux header. Loading with 3.1.0-1 works: grub linux (vg0-root)/boot/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/vg0-root ro kern/disk.c:245: Opening `vg0-root'... kern/disk.c:330: Closing `vg0-root'. I think it's a grub bug. Weird. Regards Friedemann -- 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/20120122045940.ga5...@excelsior.lab.swapon.de
