"BUG: soft lockup", always with the same call trace (interpretation needed)
I keep getting the same "BUG: soft lockup", always with the same call trace - what exactly could be causing this? [18546.997502] BUG: soft lockup - CPU#3 stuck for 22s! [imap-login:69073] [18546.998273] Modules linked in: st sr_mod cdrom binfmt_misc fuse btrfs raid6_pq zlib_deflate xor ufs qnx4 hfsplus hfs minix vfat msdos fat jfs xfs libcrc32c reiserfs iptable_filter ip_tables x_tables bonding joydev hid_generic iTCO_wdt iTCO_vendor_support gpio_ich x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul pcspkr usbhid ses enclosure acpi_cpufreq mperf wmi isci igb ptp libsas pps_core scsi_transport_sas button mei_me lpc_ich ioatdma mei i2c_i801 mfd_core shpchp dca sg loop ghash_clmulni_intel crc32c_intel aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 autofs4 linear mgag200 ttm drm_kms_helper ehci_pci drm ehci_hcd i2c_algo_bit sysimgblt sysfillrect usbcore syscopyarea usb_common megaraid_sas processor thermal_sys scsi_dh_rdac scsi_dh_hp_sw scsi_dh_emc scsi_dh_alua [18546.998328] scsi_dh dm_snapshot dm_mirror dm_region_hash dm_log dm_crypt dm_mod [last unloaded: cpuid] [18546.998336] CPU: 3 PID: 69073 Comm: imap-login Not tainted 3.11.10-7-default #1 [18546.998337] Hardware name: Supermicro X9DRi-LN4+/X9DR3-LN4+/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.0a 12/04/2013 [18546.998339] task: 8800421383c0 ti: 880cbc1be000 task.ti: 880cbc1be000 [18546.998341] RIP: 0010:[] [] _raw_spin_lock+0x1d/0x30 [18546.998347] RSP: 0018:880cbc1bf8d0 EFLAGS: 0293 [18546.998349] RAX: 5313 RBX: 8806f90ab318 RCX: 531f [18546.998350] RDX: 531f RSI: RDI: 880c41b82480 [18546.998352] RBP: 880c41b82000 R08: a038 R09: 06f90ab1501c [18546.998353] R10: f8e8f70cf2905407 R11: 88187ffe9d80 R12: 880c42da3400 [18546.998355] R13: 8803a0892920 R14: R15: [18546.998357] FS: 2b1ba53f2cc0() GS:880c7fc6() knlGS: [18546.998358] CS: 0010 DS: ES: CR0: 80050033 [18546.998360] CR2: 2af5f7c72cf0 CR3: 000583107000 CR4: 001407e0 [18546.998361] Stack: [18546.998362] 8122c57c 8806f90ab0b0 8806f90ab1b8 8120e1e8 [18546.998367] 8806f90ab0b0 81193af3 880cbc1bf940 88018d5ad530 [18546.998370] 880c42da3508 81193c11 88018d5ad5a0 81194a1c [18546.998374] Call Trace: [18546.998383] [] ext4_es_lru_del+0x1c/0x60 [18546.998390] [] ext4_clear_inode+0x38/0x80 [18546.998395] [] evict+0xa3/0x190 [18546.998400] [] dispose_list+0x31/0x40 [18546.998403] [] prune_icache_sb+0x16c/0x310 [18546.998409] [] prune_super+0x15b/0x190 [18546.998416] [] shrink_slab+0x153/0x2d0 [18546.998421] [] do_try_to_free_pages+0x39f/0x4c0 [18546.998426] [] try_to_free_pages+0xd8/0x160 [18546.998433] [] __alloc_pages_nodemask+0x5c9/0x980 [18546.998439] [] alloc_pages_current+0x9d/0x170 [18546.998445] [] sk_page_frag_refill+0x5b/0x100 [18546.998452] [] tcp_sendmsg+0x2ee/0xd70 [18546.998460] [] sock_aio_write+0x12f/0x150 [18546.998466] [] do_sync_write+0x67/0x90 [18546.998470] [] vfs_write+0x1b5/0x1e0 [18546.998475] [] SyS_write+0x43/0xa0 [18546.998480] [] system_call_fastpath+0x1a/0x1f [18546.998487] [<2b1ba5d9d9e0>] 0x2b1ba5d9d9df [18546.998489] Code: 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 b8 00 00 01 00 f0 0f c1 07 89 c1 c1 e9 10 66 39 c1 89 ca 74 0d 0f 1f 00 f3 90 0f b7 07 <66> 39 d0 75 f6 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 53 48 -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: soft lockup, always with the same call trace (interpretation needed)
I keep getting the same BUG: soft lockup, always with the same call trace - what exactly could be causing this? [18546.997502] BUG: soft lockup - CPU#3 stuck for 22s! [imap-login:69073] [18546.998273] Modules linked in: st sr_mod cdrom binfmt_misc fuse btrfs raid6_pq zlib_deflate xor ufs qnx4 hfsplus hfs minix vfat msdos fat jfs xfs libcrc32c reiserfs iptable_filter ip_tables x_tables bonding joydev hid_generic iTCO_wdt iTCO_vendor_support gpio_ich x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul pcspkr usbhid ses enclosure acpi_cpufreq mperf wmi isci igb ptp libsas pps_core scsi_transport_sas button mei_me lpc_ich ioatdma mei i2c_i801 mfd_core shpchp dca sg loop ghash_clmulni_intel crc32c_intel aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 autofs4 linear mgag200 ttm drm_kms_helper ehci_pci drm ehci_hcd i2c_algo_bit sysimgblt sysfillrect usbcore syscopyarea usb_common megaraid_sas processor thermal_sys scsi_dh_rdac scsi_dh_hp_sw scsi_dh_emc scsi_dh_alua [18546.998328] scsi_dh dm_snapshot dm_mirror dm_region_hash dm_log dm_crypt dm_mod [last unloaded: cpuid] [18546.998336] CPU: 3 PID: 69073 Comm: imap-login Not tainted 3.11.10-7-default #1 [18546.998337] Hardware name: Supermicro X9DRi-LN4+/X9DR3-LN4+/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.0a 12/04/2013 [18546.998339] task: 8800421383c0 ti: 880cbc1be000 task.ti: 880cbc1be000 [18546.998341] RIP: 0010:[8155d6cd] [8155d6cd] _raw_spin_lock+0x1d/0x30 [18546.998347] RSP: 0018:880cbc1bf8d0 EFLAGS: 0293 [18546.998349] RAX: 5313 RBX: 8806f90ab318 RCX: 531f [18546.998350] RDX: 531f RSI: RDI: 880c41b82480 [18546.998352] RBP: 880c41b82000 R08: a038 R09: 06f90ab1501c [18546.998353] R10: f8e8f70cf2905407 R11: 88187ffe9d80 R12: 880c42da3400 [18546.998355] R13: 8803a0892920 R14: R15: [18546.998357] FS: 2b1ba53f2cc0() GS:880c7fc6() knlGS: [18546.998358] CS: 0010 DS: ES: CR0: 80050033 [18546.998360] CR2: 2af5f7c72cf0 CR3: 000583107000 CR4: 001407e0 [18546.998361] Stack: [18546.998362] 8122c57c 8806f90ab0b0 8806f90ab1b8 8120e1e8 [18546.998367] 8806f90ab0b0 81193af3 880cbc1bf940 88018d5ad530 [18546.998370] 880c42da3508 81193c11 88018d5ad5a0 81194a1c [18546.998374] Call Trace: [18546.998383] [8122c57c] ext4_es_lru_del+0x1c/0x60 [18546.998390] [8120e1e8] ext4_clear_inode+0x38/0x80 [18546.998395] [81193af3] evict+0xa3/0x190 [18546.998400] [81193c11] dispose_list+0x31/0x40 [18546.998403] [81194a1c] prune_icache_sb+0x16c/0x310 [18546.998409] [8117ebeb] prune_super+0x15b/0x190 [18546.998416] [81128883] shrink_slab+0x153/0x2d0 [18546.998421] [8112b69f] do_try_to_free_pages+0x39f/0x4c0 [18546.998426] [8112b898] try_to_free_pages+0xd8/0x160 [18546.998433] [81121899] __alloc_pages_nodemask+0x5c9/0x980 [18546.998439] [8115a86d] alloc_pages_current+0x9d/0x170 [18546.998445] [814641cb] sk_page_frag_refill+0x5b/0x100 [18546.998452] [814b63ce] tcp_sendmsg+0x2ee/0xd70 [18546.998460] [8145fcdf] sock_aio_write+0x12f/0x150 [18546.998466] [8117ac27] do_sync_write+0x67/0x90 [18546.998470] [8117b3a5] vfs_write+0x1b5/0x1e0 [18546.998475] [8117bcb3] SyS_write+0x43/0xa0 [18546.998480] [815652ed] system_call_fastpath+0x1a/0x1f [18546.998487] [2b1ba5d9d9e0] 0x2b1ba5d9d9df [18546.998489] Code: 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 b8 00 00 01 00 f0 0f c1 07 89 c1 c1 e9 10 66 39 c1 89 ca 74 0d 0f 1f 00 f3 90 0f b7 07 66 39 d0 75 f6 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 53 48 -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies)
l: [3531872.467874] [] x86_64_start_kernel+0xcd/0xdc Jan 2 13:24:08 mail kernel: [3531872.467874] Code: 55 48 89 e5 0f 1f 44 00 00 fa 5d c3 0f 1f 40 00 55 48 89 e5 0f 1f 44 00 00 fb 5d c3 0f 1f 40 00 55 48 89 e5 0f 1f 44 00 00 fb f4 <5d> c3 0f 1f 00 55 48 89 e5 0f 1f 44 00 00 f4 5d c3 0f 1f 40 00 Jan 2 13:24:08 mail kernel: [3531872.467874] Call Trace: Jan 2 13:24:08 mail kernel: [3531872.467874] [] default_idle+0x53/0x1d0 Jan 2 13:24:08 mail kernel: [3531872.467874] [] cpu_idle+0xd6/0x120 Jan 2 13:24:08 mail kernel: [3531872.467874] [] rest_init+0x72/0x74 Jan 2 13:24:08 mail kernel: [3531872.467874] [] start_kernel+0x3b0/0x3bd Jan 2 13:24:08 mail kernel: [3531872.467874] [] x86_64_start_reservations+0x132/0x136 Jan 2 13:24:08 mail kernel: [3531872.467874] [] ? early_idt_handlers+0x140/0x140 Jan 2 13:24:08 mail kernel: [3531872.467874] [] x86_64_start_kernel+0xcd/0xdc -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
INFO: rcu_bh detected stall on CPU 3 (t=0 jiffies)
81c01fd8 81cdbc60 Jan 2 13:24:08 mail kernel: [3531872.467874] 88011ffb0840 81c01f08 81012236 Jan 2 13:24:08 mail kernel: [3531872.467874] a87feeb7073bf6b3 81d42d20 Jan 2 13:24:08 mail kernel: [3531872.467874] Call Trace: Jan 2 13:24:08 mail kernel: [3531872.467874] [8101b8a3] default_idle+0x53/0x1d0 Jan 2 13:24:08 mail kernel: [3531872.467874] [81012236] cpu_idle+0xd6/0x120 Jan 2 13:24:08 mail kernel: [3531872.467874] [8161ac2e] rest_init+0x72/0x74 Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9c03] start_kernel+0x3b0/0x3bd Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9388] x86_64_start_reservations+0x132/0x136 Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9140] ? early_idt_handlers+0x140/0x140 Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9459] x86_64_start_kernel+0xcd/0xdc Jan 2 13:24:08 mail kernel: [3531872.467874] Code: 55 48 89 e5 0f 1f 44 00 00 fa 5d c3 0f 1f 40 00 55 48 89 e5 0f 1f 44 00 00 fb 5d c3 0f 1f 40 00 55 48 89 e5 0f 1f 44 00 00 fb f4 5d c3 0f 1f 00 55 48 89 e5 0f 1f 44 00 00 f4 5d c3 0f 1f 40 00 Jan 2 13:24:08 mail kernel: [3531872.467874] Call Trace: Jan 2 13:24:08 mail kernel: [3531872.467874] [8101b8a3] default_idle+0x53/0x1d0 Jan 2 13:24:08 mail kernel: [3531872.467874] [81012236] cpu_idle+0xd6/0x120 Jan 2 13:24:08 mail kernel: [3531872.467874] [8161ac2e] rest_init+0x72/0x74 Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9c03] start_kernel+0x3b0/0x3bd Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9388] x86_64_start_reservations+0x132/0x136 Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9140] ? early_idt_handlers+0x140/0x140 Jan 2 13:24:08 mail kernel: [3531872.467874] [81cf9459] x86_64_start_kernel+0xcd/0xdc -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7()
from dmesg on a vanilla 3.6.7 # uname -a Linux mail2.charite.de 3.6.7 #1 SMP Sun Nov 18 19:49:09 CET 2012 i686 GNU/Linux Nov 19 10:54:16 mail2 kernel: [52464.940539] [ cut here ] Nov 19 10:54:16 mail2 kernel: [52464.940566] WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7() Nov 19 10:54:16 mail2 kernel: [52464.940570] Hardware name: ProLiant DL360 G4 Nov 19 10:54:16 mail2 kernel: [52464.940573] empty IPI mask Nov 19 10:54:16 mail2 kernel: [52464.940576] Modules linked in: nfnetlink_log nfnetlink ipv6 microcode psmouse container hpwdt tg3 thermal rng_core i6300esb button processor Nov 19 10:54:16 mail2 kernel: [52464.940603] Pid: 27794, comm: clamd Not tainted 3.6.7 #1 Nov 19 10:54:16 mail2 kernel: [52464.940606] Call Trace: Nov 19 10:54:16 mail2 kernel: [52464.940620] [] warn_slowpath_common+0x67/0x8e Nov 19 10:54:16 mail2 kernel: [52464.940627] [] ? default_send_IPI_mask_logical+0x97/0xc7 Nov 19 10:54:16 mail2 kernel: [52464.940631] [] ? default_send_IPI_mask_logical+0x97/0xc7 Nov 19 10:54:16 mail2 kernel: [52464.940636] [] warn_slowpath_fmt+0x2e/0x30 Nov 19 10:54:16 mail2 kernel: [52464.940641] [] default_send_IPI_mask_logical+0x97/0xc7 Nov 19 10:54:16 mail2 kernel: [52464.940650] [] native_send_call_func_ipi+0x42/0x54 Nov 19 10:54:16 mail2 kernel: [52464.940657] [] smp_call_function_many+0x160/0x1dd Nov 19 10:54:16 mail2 kernel: [52464.940663] [] native_flush_tlb_others+0x26/0x28 Nov 19 10:54:16 mail2 kernel: [52464.940667] [] flush_tlb_mm_range+0x4f/0x18e Nov 19 10:54:16 mail2 kernel: [52464.940676] [] tlb_flush_mmu+0x7a/0x7c Nov 19 10:54:16 mail2 kernel: [52464.940681] [] tlb_finish_mmu+0x12/0x33 Nov 19 10:54:16 mail2 kernel: [52464.940686] [] unmap_region+0x88/0x9e Nov 19 10:54:16 mail2 kernel: [52464.940691] [] do_munmap+0x1bb/0x2aa Nov 19 10:54:16 mail2 kernel: [52464.940696] [] vm_munmap+0x32/0x45 Nov 19 10:54:16 mail2 kernel: [52464.940700] [] sys_munmap+0xe/0x10 Nov 19 10:54:16 mail2 kernel: [52464.940710] [] sysenter_do_call+0x12/0x26 Nov 19 10:54:16 mail2 kernel: [52464.940713] ---[ end trace a5fffac357fb1c34 ]--- -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7()
from dmesg on a vanilla 3.6.7 # uname -a Linux mail2.charite.de 3.6.7 #1 SMP Sun Nov 18 19:49:09 CET 2012 i686 GNU/Linux Nov 19 10:54:16 mail2 kernel: [52464.940539] [ cut here ] Nov 19 10:54:16 mail2 kernel: [52464.940566] WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7() Nov 19 10:54:16 mail2 kernel: [52464.940570] Hardware name: ProLiant DL360 G4 Nov 19 10:54:16 mail2 kernel: [52464.940573] empty IPI mask Nov 19 10:54:16 mail2 kernel: [52464.940576] Modules linked in: nfnetlink_log nfnetlink ipv6 microcode psmouse container hpwdt tg3 thermal rng_core i6300esb button processor Nov 19 10:54:16 mail2 kernel: [52464.940603] Pid: 27794, comm: clamd Not tainted 3.6.7 #1 Nov 19 10:54:16 mail2 kernel: [52464.940606] Call Trace: Nov 19 10:54:16 mail2 kernel: [52464.940620] [c1027f84] warn_slowpath_common+0x67/0x8e Nov 19 10:54:16 mail2 kernel: [52464.940627] [c101beef] ? default_send_IPI_mask_logical+0x97/0xc7 Nov 19 10:54:16 mail2 kernel: [52464.940631] [c101beef] ? default_send_IPI_mask_logical+0x97/0xc7 Nov 19 10:54:16 mail2 kernel: [52464.940636] [c1028027] warn_slowpath_fmt+0x2e/0x30 Nov 19 10:54:16 mail2 kernel: [52464.940641] [c101beef] default_send_IPI_mask_logical+0x97/0xc7 Nov 19 10:54:16 mail2 kernel: [52464.940650] [c101aac4] native_send_call_func_ipi+0x42/0x54 Nov 19 10:54:16 mail2 kernel: [52464.940657] [c105c5fa] smp_call_function_many+0x160/0x1dd Nov 19 10:54:16 mail2 kernel: [52464.940663] [c1024fe7] native_flush_tlb_others+0x26/0x28 Nov 19 10:54:16 mail2 kernel: [52464.940667] [c1025087] flush_tlb_mm_range+0x4f/0x18e Nov 19 10:54:16 mail2 kernel: [52464.940676] [c108f706] tlb_flush_mmu+0x7a/0x7c Nov 19 10:54:16 mail2 kernel: [52464.940681] [c108f71a] tlb_finish_mmu+0x12/0x33 Nov 19 10:54:16 mail2 kernel: [52464.940686] [c109473f] unmap_region+0x88/0x9e Nov 19 10:54:16 mail2 kernel: [52464.940691] [c1095bb9] do_munmap+0x1bb/0x2aa Nov 19 10:54:16 mail2 kernel: [52464.940696] [c1095cda] vm_munmap+0x32/0x45 Nov 19 10:54:16 mail2 kernel: [52464.940700] [c10967e6] sys_munmap+0xe/0x10 Nov 19 10:54:16 mail2 kernel: [52464.940710] [c129ff17] sysenter_do_call+0x12/0x26 Nov 19 10:54:16 mail2 kernel: [52464.940713] ---[ end trace a5fffac357fb1c34 ]--- -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
3.6.0: WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7()
Oct 2 10:49:33 mail2 kernel: [62773.643261] [ cut here ] Oct 2 10:49:33 mail2 kernel: [62773.643289] WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7() Oct 2 10:49:33 mail2 kernel: [62773.643296] Hardware name: ProLiant DL360 G4 Oct 2 10:49:33 mail2 kernel: [62773.643301] empty IPI mask Oct 2 10:49:33 mail2 kernel: [62773.643306] Modules linked in: nfnetlink_log nfnetlink ipv6 tg3 microcode rng_core psmouse hpwdt container thermal button processor i6300esb Oct 2 10:49:33 mail2 kernel: [62773.643349] Pid: 22582, comm: clamd Not tainted 3.6.0 #1 Oct 2 10:49:33 mail2 kernel: [62773.643352] Call Trace: Oct 2 10:49:33 mail2 kernel: [62773.643362] [] warn_slowpath_common+0x67/0x8e Oct 2 10:49:33 mail2 kernel: [62773.643368] [] ? default_send_IPI_mask_logical+0x97/0xc7 Oct 2 10:49:33 mail2 kernel: [62773.643373] [] ? default_send_IPI_mask_logical+0x97/0xc7 Oct 2 10:49:33 mail2 kernel: [62773.643378] [] warn_slowpath_fmt+0x2e/0x30 Oct 2 10:49:33 mail2 kernel: [62773.643383] [] default_send_IPI_mask_logical+0x97/0xc7 Oct 2 10:49:33 mail2 kernel: [62773.643391] [] native_send_call_func_ipi+0x42/0x54 Oct 2 10:49:33 mail2 kernel: [62773.643398] [] smp_call_function_many+0x160/0x1dd Oct 2 10:49:33 mail2 kernel: [62773.643403] [] native_flush_tlb_others+0x26/0x28 Oct 2 10:49:33 mail2 kernel: [62773.643408] [] flush_tlb_page+0x49/0x73 Oct 2 10:49:33 mail2 kernel: [62773.643416] [] ptep_clear_flush+0x18/0x20 Oct 2 10:49:33 mail2 kernel: [62773.643427] [] do_wp_page+0x1f4/0x72f Oct 2 10:49:33 mail2 kernel: [62773.643438] [] ? __enqueue_entity+0x6b/0x73 Oct 2 10:49:33 mail2 kernel: [62773.643447] [] handle_pte_fault+0x47a/0x8d8 Oct 2 10:49:33 mail2 kernel: [62773.643452] [] ? generic_smp_call_function_interrupt+0x6c/0x150 Oct 2 10:49:33 mail2 kernel: [62773.643457] [] ? generic_smp_call_function_interrupt+0xc3/0x150 Oct 2 10:49:33 mail2 kernel: [62773.643462] [] handle_mm_fault+0x19c/0x211 Oct 2 10:49:33 mail2 kernel: [62773.643471] [] ? vmalloc_sync_all+0x5/0x5 Oct 2 10:49:33 mail2 kernel: [62773.643476] [] do_page_fault+0xf3/0x3ab Oct 2 10:49:33 mail2 kernel: [62773.643483] [] ? generic_smp_call_function_interrupt+0xc3/0x150 Oct 2 10:49:33 mail2 kernel: [62773.643494] [] ? radix_tree_lookup_slot+0xd/0xf Oct 2 10:49:33 mail2 kernel: [62773.643502] [] ? find_get_page+0x1b/0x70 Oct 2 10:49:33 mail2 kernel: [62773.643511] [] ? vmalloc_sync_all+0x5/0x5 Oct 2 10:49:33 mail2 kernel: [62773.643523] [] error_code+0x67/0x6c Oct 2 10:49:33 mail2 kernel: [62773.643531] [] ? file_read_actor+0x25/0xb8 Oct 2 10:49:33 mail2 kernel: [62773.643540] [] shmem_file_aio_read+0xf1/0x2bb Oct 2 10:49:33 mail2 kernel: [62773.643552] [] do_sync_read+0x8f/0xbf Oct 2 10:49:33 mail2 kernel: [62773.643558] [] ? do_sync_write+0xbf/0xbf Oct 2 10:49:33 mail2 kernel: [62773.643563] [] vfs_read+0x80/0x13e Oct 2 10:49:33 mail2 kernel: [62773.643568] [] ? do_sync_write+0xbf/0xbf Oct 2 10:49:33 mail2 kernel: [62773.643573] [] sys_pread64+0x4e/0x7c Oct 2 10:49:33 mail2 kernel: [62773.643578] [] sysenter_do_call+0x12/0x26 Oct 2 10:49:33 mail2 kernel: [62773.643582] ---[ end trace 5b941cf88518b699 ]--- -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
3.6.0: WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7()
Oct 2 10:49:33 mail2 kernel: [62773.643261] [ cut here ] Oct 2 10:49:33 mail2 kernel: [62773.643289] WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x97/0xc7() Oct 2 10:49:33 mail2 kernel: [62773.643296] Hardware name: ProLiant DL360 G4 Oct 2 10:49:33 mail2 kernel: [62773.643301] empty IPI mask Oct 2 10:49:33 mail2 kernel: [62773.643306] Modules linked in: nfnetlink_log nfnetlink ipv6 tg3 microcode rng_core psmouse hpwdt container thermal button processor i6300esb Oct 2 10:49:33 mail2 kernel: [62773.643349] Pid: 22582, comm: clamd Not tainted 3.6.0 #1 Oct 2 10:49:33 mail2 kernel: [62773.643352] Call Trace: Oct 2 10:49:33 mail2 kernel: [62773.643362] [c1027f94] warn_slowpath_common+0x67/0x8e Oct 2 10:49:33 mail2 kernel: [62773.643368] [c101beef] ? default_send_IPI_mask_logical+0x97/0xc7 Oct 2 10:49:33 mail2 kernel: [62773.643373] [c101beef] ? default_send_IPI_mask_logical+0x97/0xc7 Oct 2 10:49:33 mail2 kernel: [62773.643378] [c1028037] warn_slowpath_fmt+0x2e/0x30 Oct 2 10:49:33 mail2 kernel: [62773.643383] [c101beef] default_send_IPI_mask_logical+0x97/0xc7 Oct 2 10:49:33 mail2 kernel: [62773.643391] [c101aac4] native_send_call_func_ipi+0x42/0x54 Oct 2 10:49:33 mail2 kernel: [62773.643398] [c105c56a] smp_call_function_many+0x160/0x1dd Oct 2 10:49:33 mail2 kernel: [62773.643403] [c1024fe7] native_flush_tlb_others+0x26/0x28 Oct 2 10:49:33 mail2 kernel: [62773.643408] [c1025218] flush_tlb_page+0x49/0x73 Oct 2 10:49:33 mail2 kernel: [62773.643416] [c109c420] ptep_clear_flush+0x18/0x20 Oct 2 10:49:33 mail2 kernel: [62773.643427] [c108fe26] do_wp_page+0x1f4/0x72f Oct 2 10:49:33 mail2 kernel: [62773.643438] [c104ab0c] ? __enqueue_entity+0x6b/0x73 Oct 2 10:49:33 mail2 kernel: [62773.643447] [c10917c4] handle_pte_fault+0x47a/0x8d8 Oct 2 10:49:33 mail2 kernel: [62773.643452] [c105c7eb] ? generic_smp_call_function_interrupt+0x6c/0x150 Oct 2 10:49:33 mail2 kernel: [62773.643457] [c105c842] ? generic_smp_call_function_interrupt+0xc3/0x150 Oct 2 10:49:33 mail2 kernel: [62773.643462] [c10928e1] handle_mm_fault+0x19c/0x211 Oct 2 10:49:33 mail2 kernel: [62773.643471] [c1020fe5] ? vmalloc_sync_all+0x5/0x5 Oct 2 10:49:33 mail2 kernel: [62773.643476] [c10210d8] do_page_fault+0xf3/0x3ab Oct 2 10:49:33 mail2 kernel: [62773.643483] [c105c842] ? generic_smp_call_function_interrupt+0xc3/0x150 Oct 2 10:49:33 mail2 kernel: [62773.643494] [c116a593] ? radix_tree_lookup_slot+0xd/0xf Oct 2 10:49:33 mail2 kernel: [62773.643502] [c10793fd] ? find_get_page+0x1b/0x70 Oct 2 10:49:33 mail2 kernel: [62773.643511] [c1020fe5] ? vmalloc_sync_all+0x5/0x5 Oct 2 10:49:33 mail2 kernel: [62773.643523] [c129f7a3] error_code+0x67/0x6c Oct 2 10:49:33 mail2 kernel: [62773.643531] [c107914e] ? file_read_actor+0x25/0xb8 Oct 2 10:49:33 mail2 kernel: [62773.643540] [c1088e4b] shmem_file_aio_read+0xf1/0x2bb Oct 2 10:49:33 mail2 kernel: [62773.643552] [c10abb31] do_sync_read+0x8f/0xbf Oct 2 10:49:33 mail2 kernel: [62773.643558] [c10abaa2] ? do_sync_write+0xbf/0xbf Oct 2 10:49:33 mail2 kernel: [62773.643563] [c10ac450] vfs_read+0x80/0x13e Oct 2 10:49:33 mail2 kernel: [62773.643568] [c10abaa2] ? do_sync_write+0xbf/0xbf Oct 2 10:49:33 mail2 kernel: [62773.643573] [c10ac636] sys_pread64+0x4e/0x7c Oct 2 10:49:33 mail2 kernel: [62773.643578] [c129fa17] sysenter_do_call+0x12/0x26 Oct 2 10:49:33 mail2 kernel: [62773.643582] ---[ end trace 5b941cf88518b699 ]--- -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: soft lockup detected on CPU#0!
pp: Detected unknown logitech mouse model 1 PM: Writing back config space on device :01:02.0 at offset b (was 164714e4, writing cb0e11) PM: Writing back config space on device :01:02.0 at offset 3 (was 4000, writing 4010) PM: Writing back config space on device :01:02.0 at offset 2 (was 200, writing 202) PM: Writing back config space on device :01:02.0 at offset 1 (was 2b0, writing 2b00146) PM: Writing back config space on device :01:02.0 at offset 0 (was 164714e4, writing 16a714e4) input: ImExPS/2 Logitech Explorer Mouse as /class/input/input1 NET: Registered protocol family 10 ADDRCONF(NETDEV_UP): eth0: link is not ready tg3: eth0: Link is up at 1000 Mbps, full duplex. tg3: eth0: Flow control is on for TX and on for RX. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 Clocksource tsc unstable (delta = 4686825172 ns) NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 BUG: soft lockup detected on CPU#0! [] softlockup_tick+0x90/0xb5 [] update_process_times+0x28/0x5e [] tick_sched_timer+0x48/0x9a [] hrtimer_interrupt+0x13f/0x1c5 [] smp_apic_timer_interrupt+0x55/0x85 [] __wake_up_common+0x39/0x59 [] apic_timer_interrupt+0x28/0x30 [] rt_check_expire+0xf8/0x160 [] rt_check_expire+0x0/0x160 [] run_timer_softirq+0x11e/0x17a [] it_real_fn+0x0/0x17 [] it_real_fn+0x12/0x17 [] __do_softirq+0x74/0xd9 [] ksoftirqd+0x0/0xba [] do_softirq+0x5f/0xa8 [] ksoftirqd+0x73/0xba [] kthread+0xae/0xd3 [] kthread+0x0/0xd3 [] kernel_thread_helper+0x7/0x14 === NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: soft lockup detected on CPU#0!
on device :01:02.0 at offset b (was 164714e4, writing cb0e11) PM: Writing back config space on device :01:02.0 at offset 3 (was 4000, writing 4010) PM: Writing back config space on device :01:02.0 at offset 2 (was 200, writing 202) PM: Writing back config space on device :01:02.0 at offset 1 (was 2b0, writing 2b00146) PM: Writing back config space on device :01:02.0 at offset 0 (was 164714e4, writing 16a714e4) input: ImExPS/2 Logitech Explorer Mouse as /class/input/input1 NET: Registered protocol family 10 ADDRCONF(NETDEV_UP): eth0: link is not ready tg3: eth0: Link is up at 1000 Mbps, full duplex. tg3: eth0: Flow control is on for TX and on for RX. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 Clocksource tsc unstable (delta = 4686825172 ns) NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 NOHZ: local_softirq_pending 08 BUG: soft lockup detected on CPU#0! [c013c69a] softlockup_tick+0x90/0xb5 [c0123564] update_process_times+0x28/0x5e [c01328fe] tick_sched_timer+0x48/0x9a [c012eff1] hrtimer_interrupt+0x13f/0x1c5 [c010e75d] smp_apic_timer_interrupt+0x55/0x85 [c011461c] __wake_up_common+0x39/0x59 [c01048d0] apic_timer_interrupt+0x28/0x30 [c02db6d0] rt_check_expire+0xf8/0x160 [c02db5d8] rt_check_expire+0x0/0x160 [c01227b7] run_timer_softirq+0x11e/0x17a [c011ece9] it_real_fn+0x0/0x17 [c011ecfb] it_real_fn+0x12/0x17 [c011f8c2] __do_softirq+0x74/0xd9 [c011f794] ksoftirqd+0x0/0xba [c0106624] do_softirq+0x5f/0xa8 [c011f807] ksoftirqd+0x73/0xba [c012bd02] kthread+0xae/0xd3 [c012bc54] kthread+0x0/0xd3 [c0104a53] kernel_thread_helper+0x7/0x14 === NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 22 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 NOHZ: local_softirq_pending 02 -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > * Ralf Hildebrandt <[EMAIL PROTECTED]>: > > > The one message strinking me as odd during the boot-process is: > > Jul 21 19:50:01 kasbah kernel: AC'97 warm reset still in progress? > > [0x] > > More details: If I unload the sounddriver: > > # rmmod snd_intel8x0 > > and the reload it: > > # modprobe snd_intel8x0 > > I get: > > ACPI: PCI Interrupt :00:06.0[A] -> Link [LACI] -> GSI 22 (level, low) -> > IRQ 19 > PCI: Setting latency timer of device :00:06.0 to 64 > AC'97 warm reset still in progress? [0x] > Intel ICH: probe of :00:06.0 failed with error -5 Fixed with 2.6.3-git3 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Ralf Hildebrandt [EMAIL PROTECTED]: * Ralf Hildebrandt [EMAIL PROTECTED]: The one message strinking me as odd during the boot-process is: Jul 21 19:50:01 kasbah kernel: AC'97 warm reset still in progress? [0x] More details: If I unload the sounddriver: # rmmod snd_intel8x0 and the reload it: # modprobe snd_intel8x0 I get: ACPI: PCI Interrupt :00:06.0[A] - Link [LACI] - GSI 22 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:06.0 to 64 AC'97 warm reset still in progress? [0x] Intel ICH: probe of :00:06.0 failed with error -5 Fixed with 2.6.3-git3 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > * Chase Venters <[EMAIL PROTECTED]>: > > > > CONFIG_MPENTIUM4, CONFIG_SMP and CONFIG_SCHED_SMT enabled? > > > > Yes in all three regards. > > Same here. Dual-Xeon 2.8Ghz, only 2 CPUs are being displayed. After activating ACPI and power Management, HT works again. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13
* Chase Venters <[EMAIL PROTECTED]>: > > CONFIG_MPENTIUM4, CONFIG_SMP and CONFIG_SCHED_SMT enabled? > > Yes in all three regards. Same here. Dual-Xeon 2.8Ghz, only 2 CPUs are being displayed. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Second CPU of 1-core HyperThreading CPU not found in 2.6.13
* Chase Venters [EMAIL PROTECTED]: CONFIG_MPENTIUM4, CONFIG_SMP and CONFIG_SCHED_SMT enabled? Yes in all three regards. Same here. Dual-Xeon 2.8Ghz, only 2 CPUs are being displayed. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Second CPU of 1-core HyperThreading CPU not found in 2.6.13
* Ralf Hildebrandt [EMAIL PROTECTED]: * Chase Venters [EMAIL PROTECTED]: CONFIG_MPENTIUM4, CONFIG_SMP and CONFIG_SCHED_SMT enabled? Yes in all three regards. Same here. Dual-Xeon 2.8Ghz, only 2 CPUs are being displayed. After activating ACPI and power Management, HT works again. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: util-linux: cryptsetup support
* Christoph Hellwig <[EMAIL PROTECTED]>: > > It's the place where you can found util-linux patch that adds full > > cryptsetup-luks support to mount, umount, swapon and swapoff. The patch > > supports classic cryptsetup and LUKS extension too. > > What is LUKS? LUKS - Linux Unified Key Setup http://luks.endorphin.org/ -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: util-linux: cryptsetup support
* Christoph Hellwig [EMAIL PROTECTED]: It's the place where you can found util-linux patch that adds full cryptsetup-luks support to mount, umount, swapon and swapoff. The patch supports classic cryptsetup and LUKS extension too. What is LUKS? LUKS - Linux Unified Key Setup http://luks.endorphin.org/ -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Lee Revell <[EMAIL PROTECTED]>:
> > 2.6.12 didn't have kexec (unless it's a -mm kernel)
> > So how could you boot using kexec then?
> >
>
> Is kexec supposed to be transparent to all the subsystems, or does ALSA
> have to know how to stop all DMA in order for kexec to work?
The way I used it was to replace the "reboot" call in
/etc/init.d/reboot. So at that time, ALSA was already "stopped"
(/etc/init.d/also stop ran) -- shouldn't that suffice?
Kconfig says:
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot but it
is indepedent of the system firmware. And like a reboot you can start
any kernel with it, not just Linux.
The name comes from the similiarity to the exec system call.
It is an ongoing process to be certain the hardware in a machine is
properly shutdown, so do not be surprised if this code does not initially
work for you. It may help to enable device hotplugging support. As of
this writing the exact hardware interface is strongly in flux, so no good
recommendation can be made.
--
Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED]
Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962
IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Denis Vlasenko <[EMAIL PROTECTED]>: > Not happening here on 2.6.12: 2.6.12 didn't have kexec (unless it's a -mm kernel) So how could you boot using kexec then? > Dunno what to do next. Shots in the dark: > > Did it wok with 2.6.12 for you? > > Maybe start adding printks in snd_intel8x0_create(), > where snd_intel8x0_chip_init() is eventually called. > You want to find out what is the difference in hw behaviour > bebween good and bad boot. > > Maybe do a superfluous pci_disable_device/pci_enable_device pair there. I can try that. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > The one message strinking me as odd during the boot-process is: > Jul 21 19:50:01 kasbah kernel: AC'97 warm reset still in progress? > [0x] More details: If I unload the sounddriver: # rmmod snd_intel8x0 and the reload it: # modprobe snd_intel8x0 I get: ACPI: PCI Interrupt :00:06.0[A] -> Link [LACI] -> GSI 22 (level, low) -> IRQ 19 PCI: Setting latency timer of device :00:06.0 to 64 AC'97 warm reset still in progress? [0x] Intel ICH: probe of :00:06.0 failed with error -5 -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Ralf Hildebrandt [EMAIL PROTECTED]: The one message strinking me as odd during the boot-process is: Jul 21 19:50:01 kasbah kernel: AC'97 warm reset still in progress? [0x] More details: If I unload the sounddriver: # rmmod snd_intel8x0 and the reload it: # modprobe snd_intel8x0 I get: ACPI: PCI Interrupt :00:06.0[A] - Link [LACI] - GSI 22 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:06.0 to 64 AC'97 warm reset still in progress? [0x] Intel ICH: probe of :00:06.0 failed with error -5 -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Denis Vlasenko [EMAIL PROTECTED]: Not happening here on 2.6.12: 2.6.12 didn't have kexec (unless it's a -mm kernel) So how could you boot using kexec then? Dunno what to do next. Shots in the dark: Did it wok with 2.6.12 for you? Maybe start adding printks in snd_intel8x0_create(), where snd_intel8x0_chip_init() is eventually called. You want to find out what is the difference in hw behaviour bebween good and bad boot. Maybe do a superfluous pci_disable_device/pci_enable_device pair there. I can try that. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
* Lee Revell [EMAIL PROTECTED]: 2.6.12 didn't have kexec (unless it's a -mm kernel) So how could you boot using kexec then? Is kexec supposed to be transparent to all the subsystems, or does ALSA have to know how to stop all DMA in order for kexec to work? The way I used it was to replace the reboot call in /etc/init.d/reboot. So at that time, ALSA was already stopped (/etc/init.d/also stop ran) -- shouldn't that suffice? Kconfig says: kexec is a system call that implements the ability to shutdown your current kernel, and to start another kernel. It is like a reboot but it is indepedent of the system firmware. And like a reboot you can start any kernel with it, not just Linux. The name comes from the similiarity to the exec system call. It is an ongoing process to be certain the hardware in a machine is properly shutdown, so do not be surprised if this code does not initially work for you. It may help to enable device hotplugging support. As of this writing the exact hardware interface is strongly in flux, so no good recommendation can be made. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
Jul 21 19:50:01 kasbah kernel: AC'97 warm reset still in progress? [0x] Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt Link [LMCI] enabled at IRQ 21 Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt :00:06.1[B] -> Link [LMCI] -> GSI 21 (level, low) -> IRQ 20 Jul 21 19:50:01 kasbah kernel: PCI: Setting latency timer of device :00:06.1 to 64 Jul 21 19:50:01 kasbah kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt :02:04.0[A] -> Link [LNK1] -> GSI 19 (level, low) -> IRQ 16 Jul 21 19:50:01 kasbah kernel: Yenta: CardBus bridge found at :02:04.0 [103c:006d] Jul 21 19:50:01 kasbah kernel: Yenta: Using CSCINT to route CSC interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta: Routing CardBus interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta TI: socket :02:04.0, mfunc 0x0d22, devctl 0x64 Jul 21 19:50:01 kasbah kernel: Yenta: ISA IRQ mask 0x0c78, PCI irq 16 Jul 21 19:50:01 kasbah kernel: Socket status: 3086 Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff Jul 21 19:50:01 kasbah kernel: cs: IO port probe 0x3000-0x7fff: clean. Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0xe810 - 0xe97f Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0x2000 - 0x23ff Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt :02:04.1[B] -> Link [LNK2] -> GSI 18 (level, low) -> IRQ 17 Jul 21 19:50:01 kasbah kernel: Yenta: CardBus bridge found at :02:04.1 [103c:006d] Jul 21 19:50:01 kasbah kernel: Yenta: Using CSCINT to route CSC interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta: Routing CardBus interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta TI: socket :02:04.1, mfunc 0x0d22, devctl 0x64 Jul 21 19:50:01 kasbah kernel: Yenta: ISA IRQ mask 0x0c78, PCI irq 17 Jul 21 19:50:01 kasbah kernel: Socket status: 3086 Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff Jul 21 19:50:01 kasbah kernel: cs: IO port probe 0x3000-0x7fff: clean. Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0xe810 - 0xe97f Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0x2000 - 0x23ff Jul 21 19:50:01 kasbah kernel: Real Time Clock Driver v1.12 Jul 21 19:50:01 kasbah kernel: alps.c: Enabling hardware tapping Jul 21 19:50:01 kasbah kernel: input: PS/2 Mouse on isa0060/serio4 Jul 21 19:50:01 kasbah kernel: input: AlpsPS/2 ALPS GlidePoint on isa0060/serio4 Jul 21 19:50:01 kasbah kernel: ts: Compaq touchscreen protocol output Jul 21 19:50:01 kasbah kernel: mice: PS/2 mouse device common for all mice Jul 21 19:50:01 kasbah kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Jul 21 19:50:01 kasbah kernel: ACPI: Battery Slot [BAT1] (battery present) Jul 21 19:50:01 kasbah kernel: ACPI: AC Adapter [ACAD] (on-line) Jul 21 19:50:01 kasbah kernel: ACPI: Power Button (FF) [PWRF] Jul 21 19:50:01 kasbah kernel: ACPI: Power Button (CM) [PWRB] Jul 21 19:50:01 kasbah kernel: ACPI: Lid Switch [LID] Jul 21 19:50:02 kasbah kernel: ACPI: Thermal Zone [THRM] (53 C) Jul 21 19:50:03 kasbah kernel: lp0: ECP mode Jul 21 19:50:06 kasbah /usr/sbin/gpm[4783]: Detected EXPS/2 protocol mouse. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
Link [LMCI] enabled at IRQ 21 Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt :00:06.1[B] - Link [LMCI] - GSI 21 (level, low) - IRQ 20 Jul 21 19:50:01 kasbah kernel: PCI: Setting latency timer of device :00:06.1 to 64 Jul 21 19:50:01 kasbah kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt :02:04.0[A] - Link [LNK1] - GSI 19 (level, low) - IRQ 16 Jul 21 19:50:01 kasbah kernel: Yenta: CardBus bridge found at :02:04.0 [103c:006d] Jul 21 19:50:01 kasbah kernel: Yenta: Using CSCINT to route CSC interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta: Routing CardBus interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta TI: socket :02:04.0, mfunc 0x0d22, devctl 0x64 Jul 21 19:50:01 kasbah kernel: Yenta: ISA IRQ mask 0x0c78, PCI irq 16 Jul 21 19:50:01 kasbah kernel: Socket status: 3086 Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff Jul 21 19:50:01 kasbah kernel: cs: IO port probe 0x3000-0x7fff: clean. Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0xe810 - 0xe97f Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0x2000 - 0x23ff Jul 21 19:50:01 kasbah kernel: ACPI: PCI Interrupt :02:04.1[B] - Link [LNK2] - GSI 18 (level, low) - IRQ 17 Jul 21 19:50:01 kasbah kernel: Yenta: CardBus bridge found at :02:04.1 [103c:006d] Jul 21 19:50:01 kasbah kernel: Yenta: Using CSCINT to route CSC interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta: Routing CardBus interrupts to PCI Jul 21 19:50:01 kasbah kernel: Yenta TI: socket :02:04.1, mfunc 0x0d22, devctl 0x64 Jul 21 19:50:01 kasbah kernel: Yenta: ISA IRQ mask 0x0c78, PCI irq 17 Jul 21 19:50:01 kasbah kernel: Socket status: 3086 Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff Jul 21 19:50:01 kasbah kernel: cs: IO port probe 0x3000-0x7fff: clean. Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0xe810 - 0xe97f Jul 21 19:50:01 kasbah kernel: pcmcia: parent PCI bridge Memory window: 0x2000 - 0x23ff Jul 21 19:50:01 kasbah kernel: Real Time Clock Driver v1.12 Jul 21 19:50:01 kasbah kernel: alps.c: Enabling hardware tapping Jul 21 19:50:01 kasbah kernel: input: PS/2 Mouse on isa0060/serio4 Jul 21 19:50:01 kasbah kernel: input: AlpsPS/2 ALPS GlidePoint on isa0060/serio4 Jul 21 19:50:01 kasbah kernel: ts: Compaq touchscreen protocol output Jul 21 19:50:01 kasbah kernel: mice: PS/2 mouse device common for all mice Jul 21 19:50:01 kasbah kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Jul 21 19:50:01 kasbah kernel: ACPI: Battery Slot [BAT1] (battery present) Jul 21 19:50:01 kasbah kernel: ACPI: AC Adapter [ACAD] (on-line) Jul 21 19:50:01 kasbah kernel: ACPI: Power Button (FF) [PWRF] Jul 21 19:50:01 kasbah kernel: ACPI: Power Button (CM) [PWRB] Jul 21 19:50:01 kasbah kernel: ACPI: Lid Switch [LID] Jul 21 19:50:02 kasbah kernel: ACPI: Thermal Zone [THRM] (53 C) Jul 21 19:50:03 kasbah kernel: lp0: ECP mode Jul 21 19:50:06 kasbah /usr/sbin/gpm[4783]: Detected EXPS/2 protocol mouse. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13.3 flooding my logs
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > 2.6.13.2 didn't do this, now I'm getting (from dmesg): > > PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=56 S=0x00 I=40463 F=0x4000 T=64 > ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING > skb: pf=2 (unowned) dev=lo len=56 > PROTO=17 127.0.0.1:56872 127.0.0.1:53 L=56 S=0x00 I=12024 F=0x4000 T=64 > ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING > skb: pf=2 (unowned) dev=lo len=89 > PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=89 S=0x00 I=40464 F=0x4000 T=64 > ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING > skb: pf=2 (unowned) dev=lo len=124 > PROTO=17 127.0.0.1:53 127.0.0.1:56729 L=124 S=0x00 I=40465 F=0x4000 T=64 > ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING > skb: pf=2 (unowned) dev=lo len=152 > PROTO=1 127.0.0.1:0 127.0.0.1:0 L=152 S=0xC0 I=41998 F=0x T=64 > > What is it? Looks like debug output, but I haven't turned any of that > on. This must be related to this change: [PATCH] revert nf_reset change [NETFILTER]: Revert nf_reset change Revert the nf_reset change that caused so much trouble, drop conntrack references manually before packets are queued to packet sockets. Adapted for 2.6.12 by Daniel Drake <[EMAIL PROTECTED]> Signed-off-by: Phil Oester <[EMAIL PROTECTED]> Signed-off-by: Patrick McHardy <[EMAIL PROTECTED]> Signed-off-by: Chris Wright <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13.3 flooding my logs
* Ralf Hildebrandt [EMAIL PROTECTED]: 2.6.13.2 didn't do this, now I'm getting (from dmesg): PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=56 S=0x00 I=40463 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=56 PROTO=17 127.0.0.1:56872 127.0.0.1:53 L=56 S=0x00 I=12024 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=89 PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=89 S=0x00 I=40464 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=124 PROTO=17 127.0.0.1:53 127.0.0.1:56729 L=124 S=0x00 I=40465 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=152 PROTO=1 127.0.0.1:0 127.0.0.1:0 L=152 S=0xC0 I=41998 F=0x T=64 What is it? Looks like debug output, but I haven't turned any of that on. This must be related to this change: [PATCH] revert nf_reset change [NETFILTER]: Revert nf_reset change Revert the nf_reset change that caused so much trouble, drop conntrack references manually before packets are queued to packet sockets. Adapted for 2.6.12 by Daniel Drake [EMAIL PROTECTED] Signed-off-by: Phil Oester [EMAIL PROTECTED] Signed-off-by: Patrick McHardy [EMAIL PROTECTED] Signed-off-by: Chris Wright [EMAIL PROTECTED] Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED] -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.13.3 flooding my logs
2.6.13.2 didn't do this, now I'm getting (from dmesg): PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=56 S=0x00 I=40463 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=56 PROTO=17 127.0.0.1:56872 127.0.0.1:53 L=56 S=0x00 I=12024 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=89 PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=89 S=0x00 I=40464 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=124 PROTO=17 127.0.0.1:53 127.0.0.1:56729 L=124 S=0x00 I=40465 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=152 PROTO=1 127.0.0.1:0 127.0.0.1:0 L=152 S=0xC0 I=41998 F=0x T=64 What is it? Looks like debug output, but I haven't turned any of that on. -- _ Charité - Universitätsmedizin Berlin _ Ralf Hildebrandt i.A. Geschäftsbereich Informationsmanagement Campus Benjamin Franklin Hindenburgdamm 30 | Berlin Tel. +49 30 450 570155 | Fax +49 30 450 570962 [EMAIL PROTECTED] http://www.charite.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.13.3 flooding my logs
2.6.13.2 didn't do this, now I'm getting (from dmesg): PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=56 S=0x00 I=40463 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=56 PROTO=17 127.0.0.1:56872 127.0.0.1:53 L=56 S=0x00 I=12024 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=89 PROTO=17 127.0.0.1:53 127.0.0.1:56872 L=89 S=0x00 I=40464 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=124 PROTO=17 127.0.0.1:53 127.0.0.1:56729 L=124 S=0x00 I=40465 F=0x4000 T=64 ip_local_deliver: bad skb: PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING skb: pf=2 (unowned) dev=lo len=152 PROTO=1 127.0.0.1:0 127.0.0.1:0 L=152 S=0xC0 I=41998 F=0x T=64 What is it? Looks like debug output, but I haven't turned any of that on. -- _ Charité - Universitätsmedizin Berlin _ Ralf Hildebrandt i.A. Geschäftsbereich Informationsmanagement Campus Benjamin Franklin Hindenburgdamm 30 | Berlin Tel. +49 30 450 570155 | Fax +49 30 450 570962 [EMAIL PROTECTED] http://www.charite.de - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Current kexec status?
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > Nope, no booting. I get one line of output which I don't remember; > I'll have to retry. Retried: "Starting new kernel" -- and that's it! -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Current kexec status?
* Vivek Goyal <[EMAIL PROTECTED]>: > Can you give more details like > - Which distro release you are running. Debian unstable; since it has no kexec-tools, I built those from source. > - Exactly what changes did you do to /etc/init.d/reboot and what steps > did you follow to load the kernel (command line options). /etc/init.d/reboot: === echo -n "Rebooting... " #reboot -d -f -i /usr/local/sbin/kexec -f --exec --debug Loading the Kernel in /etc/init.d/umountfs, before umount'ing /boot: echo -n "Loading kernel for kexec()..." /usr/local/sbin/kexec --load /vmlinuz echo "done." > - What do you see on screen? Did the new kernel start booting at all. Nope, no booting. I get one line of output which I don't remember; I'll have to retry. > - Would be nice if I can get serial console output. Sorry, no serial port here. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Current kexec status?
I want to experiment with kexec and my 2.6.13-rc3 kernel. I'm able to --load the kernel, but on --exec in /etc/init.d/reboot (I replaced the reboot command in there), the machine freezes. I'm using kexec-tools-1.101, are there any more patches needed? -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Current kexec status?
I want to experiment with kexec and my 2.6.13-rc3 kernel. I'm able to --load the kernel, but on --exec in /etc/init.d/reboot (I replaced the reboot command in there), the machine freezes. I'm using kexec-tools-1.101, are there any more patches needed? -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Current kexec status?
* Vivek Goyal [EMAIL PROTECTED]: Can you give more details like - Which distro release you are running. Debian unstable; since it has no kexec-tools, I built those from source. - Exactly what changes did you do to /etc/init.d/reboot and what steps did you follow to load the kernel (command line options). /etc/init.d/reboot: === echo -n Rebooting... #reboot -d -f -i /usr/local/sbin/kexec -f --exec --debug Loading the Kernel in /etc/init.d/umountfs, before umount'ing /boot: echo -n Loading kernel for kexec()... /usr/local/sbin/kexec --load /vmlinuz echo done. - What do you see on screen? Did the new kernel start booting at all. Nope, no booting. I get one line of output which I don't remember; I'll have to retry. - Would be nice if I can get serial console output. Sorry, no serial port here. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Current kexec status?
* Ralf Hildebrandt [EMAIL PROTECTED]: Nope, no booting. I get one line of output which I don't remember; I'll have to retry. Retried: Starting new kernel -- and that's it! -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.12-rc3
> It's available both as a patch (against 2.6.11) and as a tar-ball, and Where IS the tarball? Not on www.kernel.org, that's for sure. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.12-rc3
It's available both as a patch (against 2.6.11) and as a tar-ball, and Where IS the tarball? Not on www.kernel.org, that's for sure. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Coredump when program run as root?
I found this while trying to find out why squid doesn't produce a core file: http://lists.samba.org/archive/samba-technical/2002-August/023576.html Most UNIX variants disable core dumps in programs that have changed their uid or euid during operation. This includes Solaris and Linux. Well, squid does exactly that. How can I still get a coredump? I really need one. Kernel 2.6.11.7 -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Coredump when program run as root?
I found this while trying to find out why squid doesn't produce a core file: http://lists.samba.org/archive/samba-technical/2002-August/023576.html Most UNIX variants disable core dumps in programs that have changed their uid or euid during operation. This includes Solaris and Linux. Well, squid does exactly that. How can I still get a coredump? I really need one. Kernel 2.6.11.7 -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10 (EIP is at hid_init_reports+0x151/0x1d0 [usbhid])
* Andrew Morton <[EMAIL PROTECTED]>: > > Could you please test 2.6.11 or, even better, 2.6.12-rc1? I will do that, once Debian has such a kernel :| -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10 (EIP is at hid_init_reports+0x151/0x1d0 [usbhid])
* Andrew Morton [EMAIL PROTECTED]: Could you please test 2.6.11 or, even better, 2.6.12-rc1? I will do that, once Debian has such a kernel :| -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Oops in 2.6.10 (EIP is at hid_init_reports+0x151/0x1d0 [usbhid])
Mar 18 14:56:35 newserver kernel: usb 2-2: new low speed USB device using uhci_hcd and address 7 Mar 18 14:56:36 newserver usb.agent[17991]: usbhid: already loaded Mar 18 14:56:37 newserver kernel: hiddev96: USB HID v1.00 Device [American Power Conversion Back-UPS 500 FW: 6.4.I USB FW: c1 ] on usb-:00:1d.1-2 Mar 18 14:56:37 newserver udev[18027]: configured rule in '/etc/udev/rules.d/udev.rules[38]' applied, 'hiddev0' becomes 'usb/%k' Mar 18 14:56:37 newserver udev[18027]: creating device node '/dev/usb/hiddev0' Mar 18 14:57:18 newserver hidups[18038]: Startup successful Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: ctrl urb status -84 received Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: ctrl urb status -71 received Mar 18 14:57:19 newserver kernel: usb 2-2: USB disconnect, address 7 Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: input irq status -84 received Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: can't resubmit intr, :00:1d.1-2/input0, status -19 Mar 18 14:57:19 newserver kernel: Unable to handle kernel NULL pointer dereference at virtual address 0008 Mar 18 14:57:19 newserver kernel: printing eip: Mar 18 14:57:19 newserver kernel: d0a361b1 Mar 18 14:57:19 newserver kernel: *pde = Mar 18 14:57:19 newserver kernel: Oops: [#1] Mar 18 14:57:19 newserver kernel: PREEMPT Mar 18 14:57:19 newserver kernel: Modules linked in: usbhid pppoe pppox ppp_generic slhc af_packet lp autofs4 ipt_TCPMSS ipt_MASQUERADE ipt_state iptable_filter iptable_nat ipv6 ip_conntrack ip_tables ide_cd cdrom parport_pc parport tsdev mousedev psmouse floppy evdev rtc pcspkr 3c59x snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd snd_page_alloc i810_audio ac97_codec soundcore i2c_i801 i2c_core pci_hotplug usblp uhci_hcd intel_agp agpgart dm_mod capability commoncap usbkbd usbcore ext3 jbd mbcache ide_generic atiixp pdc202xx_old cmd64x hpt366 ide_disk generic amd74xx serverworks cs5530 ns87415 sc1200 sis5513 piix alim15x3 hpt34x cs5520 opti621 slc90e66 cy82c693 trm290 pdc202xx_new rz1000 via82cxxx siimage aec62xx triflex ide_core unix fbcon font bitblit vesafb cfbcopyarea cfbimgblt cfbfillrect Mar 18 14:57:19 newserver kernel: CPU:0 Mar 18 14:57:19 newserver kernel: EIP:0060:[pg0+275272113/1069863936] Not tainted VLI Mar 18 14:57:19 newserver kernel: EFLAGS: 00010286 (2.6.10-1-686) Mar 18 14:57:19 newserver kernel: EIP is at hid_init_reports+0x151/0x1d0 [usbhid] Mar 18 14:57:19 newserver kernel: eax: ebx: ecx: cb15e000 edx: be333c00 Mar 18 14:57:19 newserver kernel: esi: c4f3e024 edi: c4f3e000 ebp: esp: c8679eb0 Mar 18 14:57:19 newserver kernel: ds: 007b es: 007b ss: 0068 Mar 18 14:57:19 newserver kernel: Process hidups (pid: 18038, threadinfo=c8678000 task=ce837590) Mar 18 14:57:19 newserver kernel: Stack: c4f3e000 cb15e200 0080 0021 0100 Mar 18 14:57:19 newserver kernel:1388 c4f3e020 4805 cb15e000 c4f3e000 d0a3785f c4f3e000 Mar 18 14:57:19 newserver kernel:0005 c8678000 c01253b4 ce837590 00040004 c8678000 c8679f20 Mar 18 14:57:19 newserver kernel: Call Trace: Mar 18 14:57:19 newserver kernel: [pg0+275277919/1069863936] hiddev_ioctl+0x1cf/0x9d0 [usbhid] Mar 18 14:57:19 newserver kernel: [ptrace_stop+132/192] ptrace_stop+0x84/0xc0 Mar 18 14:57:19 newserver kernel: [ptrace_notify+103/144] ptrace_notify+0x67/0x90 Mar 18 14:57:19 newserver kernel: [sys_ioctl+234/592] sys_ioctl+0xea/0x250 Mar 18 14:57:19 newserver kernel: [do_syscall_trace+71/144] do_syscall_trace+0x47/0x90 Mar 18 14:57:19 newserver kernel: [syscall_call+7/11] syscall_call+0x7/0xb Mar 18 14:57:19 newserver kernel: Code: b8 88 13 00 00 31 ed 8b 11 89 44 24 20 31 c0 c1 e2 08 89 44 24 1c 81 ca 00 00 00 80 89 6c 24 18 0f b7 87 4c 0c 00 00 89 44 24 14 <0f> b7 43 08 89 54 24 04 89 0c 24 89 44 24 10 b8 21 00 00 00 89 Mar 18 14:57:19 newserver udev[18047]: removing device node '/dev/usb/hiddev0' -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Oops in 2.6.10 (EIP is at hid_init_reports+0x151/0x1d0 [usbhid])
Mar 18 14:56:35 newserver kernel: usb 2-2: new low speed USB device using uhci_hcd and address 7 Mar 18 14:56:36 newserver usb.agent[17991]: usbhid: already loaded Mar 18 14:56:37 newserver kernel: hiddev96: USB HID v1.00 Device [American Power Conversion Back-UPS 500 FW: 6.4.I USB FW: c1 ] on usb-:00:1d.1-2 Mar 18 14:56:37 newserver udev[18027]: configured rule in '/etc/udev/rules.d/udev.rules[38]' applied, 'hiddev0' becomes 'usb/%k' Mar 18 14:56:37 newserver udev[18027]: creating device node '/dev/usb/hiddev0' Mar 18 14:57:18 newserver hidups[18038]: Startup successful Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: ctrl urb status -84 received Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: ctrl urb status -71 received Mar 18 14:57:19 newserver kernel: usb 2-2: USB disconnect, address 7 Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: input irq status -84 received Mar 18 14:57:19 newserver kernel: drivers/usb/input/hid-core.c: can't resubmit intr, :00:1d.1-2/input0, status -19 Mar 18 14:57:19 newserver kernel: Unable to handle kernel NULL pointer dereference at virtual address 0008 Mar 18 14:57:19 newserver kernel: printing eip: Mar 18 14:57:19 newserver kernel: d0a361b1 Mar 18 14:57:19 newserver kernel: *pde = Mar 18 14:57:19 newserver kernel: Oops: [#1] Mar 18 14:57:19 newserver kernel: PREEMPT Mar 18 14:57:19 newserver kernel: Modules linked in: usbhid pppoe pppox ppp_generic slhc af_packet lp autofs4 ipt_TCPMSS ipt_MASQUERADE ipt_state iptable_filter iptable_nat ipv6 ip_conntrack ip_tables ide_cd cdrom parport_pc parport tsdev mousedev psmouse floppy evdev rtc pcspkr 3c59x snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd snd_page_alloc i810_audio ac97_codec soundcore i2c_i801 i2c_core pci_hotplug usblp uhci_hcd intel_agp agpgart dm_mod capability commoncap usbkbd usbcore ext3 jbd mbcache ide_generic atiixp pdc202xx_old cmd64x hpt366 ide_disk generic amd74xx serverworks cs5530 ns87415 sc1200 sis5513 piix alim15x3 hpt34x cs5520 opti621 slc90e66 cy82c693 trm290 pdc202xx_new rz1000 via82cxxx siimage aec62xx triflex ide_core unix fbcon font bitblit vesafb cfbcopyarea cfbimgblt cfbfillrect Mar 18 14:57:19 newserver kernel: CPU:0 Mar 18 14:57:19 newserver kernel: EIP:0060:[pg0+275272113/1069863936] Not tainted VLI Mar 18 14:57:19 newserver kernel: EFLAGS: 00010286 (2.6.10-1-686) Mar 18 14:57:19 newserver kernel: EIP is at hid_init_reports+0x151/0x1d0 [usbhid] Mar 18 14:57:19 newserver kernel: eax: ebx: ecx: cb15e000 edx: be333c00 Mar 18 14:57:19 newserver kernel: esi: c4f3e024 edi: c4f3e000 ebp: esp: c8679eb0 Mar 18 14:57:19 newserver kernel: ds: 007b es: 007b ss: 0068 Mar 18 14:57:19 newserver kernel: Process hidups (pid: 18038, threadinfo=c8678000 task=ce837590) Mar 18 14:57:19 newserver kernel: Stack: c4f3e000 cb15e200 0080 0021 0100 Mar 18 14:57:19 newserver kernel:1388 c4f3e020 4805 cb15e000 c4f3e000 d0a3785f c4f3e000 Mar 18 14:57:19 newserver kernel:0005 c8678000 c01253b4 ce837590 00040004 c8678000 c8679f20 Mar 18 14:57:19 newserver kernel: Call Trace: Mar 18 14:57:19 newserver kernel: [pg0+275277919/1069863936] hiddev_ioctl+0x1cf/0x9d0 [usbhid] Mar 18 14:57:19 newserver kernel: [ptrace_stop+132/192] ptrace_stop+0x84/0xc0 Mar 18 14:57:19 newserver kernel: [ptrace_notify+103/144] ptrace_notify+0x67/0x90 Mar 18 14:57:19 newserver kernel: [sys_ioctl+234/592] sys_ioctl+0xea/0x250 Mar 18 14:57:19 newserver kernel: [do_syscall_trace+71/144] do_syscall_trace+0x47/0x90 Mar 18 14:57:19 newserver kernel: [syscall_call+7/11] syscall_call+0x7/0xb Mar 18 14:57:19 newserver kernel: Code: b8 88 13 00 00 31 ed 8b 11 89 44 24 20 31 c0 c1 e2 08 89 44 24 1c 81 ca 00 00 00 80 89 6c 24 18 0f b7 87 4c 0c 00 00 89 44 24 14 0f b7 43 08 89 54 24 04 89 0c 24 89 44 24 10 b8 21 00 00 00 89 Mar 18 14:57:19 newserver udev[18047]: removing device node '/dev/usb/hiddev0' -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Randy.Dunlap <[EMAIL PROTECTED]>: > >Is it normal that the kernel with debugging enabled is not larger than > >the normal kernel? > >- > > No, it should be much larger. Recheck the .config file > for CONFIG_DEBUG_INFO=y. Maybe you need to do 'make clean' > first. CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_HIGHMEM is not set CONFIG_DEBUG_INFO=y # CONFIG_FRAME_POINTER is not set CONFIG_EARLY_PRINTK=y I built that using "make-kpkg" make-kpkg clean CONCURRENCY_LEVEL=4 MAKEFLAGS="CC=gcc-3.4" make-kpkg --revision=20050217 kernel_image -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > > The best way to do that is to ensure that the kernel was built with > > CONFIG_DEBUG_INFO, note the offending EIP value, then do > > > > # gdb vmlinux > > (gdb) l *0xc0 > > I'm rebuilding the ac12 kernel which crashed on me after just one day > and will reboot it today. Is it normal that the kernel with debugging enabled is not larger than the normal kernel? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Andrew Morton <[EMAIL PROTECTED]>: > There have been a handful of reports - there's surely a race in there. > > Unfortunately I've yet to see a report from which we can identify the > offending line in the very large journal_commit_transaction() function. :( > > The best way to do that is to ensure that the kernel was built with > CONFIG_DEBUG_INFO, note the offending EIP value, then do > > # gdb vmlinux > (gdb) l *0xc0 I'm rebuilding the ac12 kernel which crashed on me after just one day and will reboot it today. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Andrew Morton [EMAIL PROTECTED]: There have been a handful of reports - there's surely a race in there. Unfortunately I've yet to see a report from which we can identify the offending line in the very large journal_commit_transaction() function. :( The best way to do that is to ensure that the kernel was built with CONFIG_DEBUG_INFO, note the offending EIP value, then do # gdb vmlinux (gdb) l *0xc0whatever I'm rebuilding the ac12 kernel which crashed on me after just one day and will reboot it today. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Ralf Hildebrandt [EMAIL PROTECTED]: The best way to do that is to ensure that the kernel was built with CONFIG_DEBUG_INFO, note the offending EIP value, then do # gdb vmlinux (gdb) l *0xc0whatever I'm rebuilding the ac12 kernel which crashed on me after just one day and will reboot it today. Is it normal that the kernel with debugging enabled is not larger than the normal kernel? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Randy.Dunlap [EMAIL PROTECTED]: Is it normal that the kernel with debugging enabled is not larger than the normal kernel? - No, it should be much larger. Recheck the .config file for CONFIG_DEBUG_INFO=y. Maybe you need to do 'make clean' first. CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_HIGHMEM is not set CONFIG_DEBUG_INFO=y # CONFIG_FRAME_POINTER is not set CONFIG_EARLY_PRINTK=y I built that using make-kpkg make-kpkg clean CONCURRENCY_LEVEL=4 MAKEFLAGS=CC=gcc-3.4 make-kpkg --revision=20050217 kernel_image -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Dale Blount <[EMAIL PROTECTED]>: > This looks very similar (at least to me) to an OOPS I posted with 2.6.9 > on 12/03/2004. > http://marc.theaimsgroup.com/?l=linux-kernel=110210705504716=2 Could be. > My system is also a dual Xeon using SMP and Hyperthreading > (/proc/cpuinfo shows 4 cpus). Same system here. > Mine, like Ralf's, is also a mail server running postfix using ext3 for > the spool directory. Same here. > I've actually hit this bug (assuming it's the same) with 2.6.10 also. I > had to power cycle remotely and unfortunately didn't have the serial > console logging enabled when it happened with 2.6.10. I upgraded from > 2.4.23 to 2.6.8.1 and crashed within a week, and continued to crash at > least monthly after that. It had been running 2.4.23 for 200+ days with > no problems. > > Hope this helps trace it back. Me too -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Jan Kara <[EMAIL PROTECTED]>: > I guess the system is SMP... Indeed it is. Dual Xeon with SMP. > Sadly a few lines in the beginning of the > report are missing (probably scrolled off the screen) Yes, this sucks. I rebooted with vesafb active, no I do have 50 lines :) > but it seems similar like a several other oopses I've seen reported > recently. Is this the first time you hit this bug? It's actually the second time. The first time it hit the SAME box but with kernel-2.6.10 (vanilla) after 30 days of uptime. Nobody had a camera at hand, so I couldn't take a photo. Any suggestions? I'm open to suggestions. One difference between the 2.6.10 and 2.6.10-ac12 was that 2.6.10 has no in-kernel irq balancing, while in 2.6.10-ac12 I acivated that. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Jan Kara [EMAIL PROTECTED]: I guess the system is SMP... Indeed it is. Dual Xeon with SMP. Sadly a few lines in the beginning of the report are missing (probably scrolled off the screen) Yes, this sucks. I rebooted with vesafb active, no I do have 50 lines :) but it seems similar like a several other oopses I've seen reported recently. Is this the first time you hit this bug? It's actually the second time. The first time it hit the SAME box but with kernel-2.6.10 (vanilla) after 30 days of uptime. Nobody had a camera at hand, so I couldn't take a photo. Any suggestions? I'm open to suggestions. One difference between the 2.6.10 and 2.6.10-ac12 was that 2.6.10 has no in-kernel irq balancing, while in 2.6.10-ac12 I acivated that. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
* Dale Blount [EMAIL PROTECTED]: This looks very similar (at least to me) to an OOPS I posted with 2.6.9 on 12/03/2004. http://marc.theaimsgroup.com/?l=linux-kernelm=110210705504716w=2 Could be. My system is also a dual Xeon using SMP and Hyperthreading (/proc/cpuinfo shows 4 cpus). Same system here. Mine, like Ralf's, is also a mail server running postfix using ext3 for the spool directory. Same here. I've actually hit this bug (assuming it's the same) with 2.6.10 also. I had to power cycle remotely and unfortunately didn't have the serial console logging enabled when it happened with 2.6.10. I upgraded from 2.4.23 to 2.6.8.1 and crashed within a week, and continued to crash at least monthly after that. It had been running 2.4.23 for 200+ days with no problems. Hope this helps trace it back. Me too -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Today our mailserver froze after just one day of uptime. I was able to capture the Oops on the screen using my digital camera: http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/ Keywords: EIP is at journal_commit_transaction, process kjournald # mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/cciss/c0d0p5 on /boot type ext3 (rw) /dev/shm on /var/amavis type tmpfs (rw,noatime,size=200m,mode=770,uid=104,gid=108) -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Today our mailserver froze after just one day of uptime. I was able to capture the Oops on the screen using my digital camera: http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/ Keywords: EIP is at journal_commit_transaction, process kjournald # mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/cciss/c0d0p5 on /boot type ext3 (rw) /dev/shm on /var/amavis type tmpfs (rw,noatime,size=200m,mode=770,uid=104,gid=108) -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.10-ac11 announcement?
Where is the 2.6.10-ac11 announcement? -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.10-ac11 announcement?
Where is the 2.6.10-ac11 announcement? -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Re:parport disabled?
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > > Try disabling acpi. > > Didn't help. Same symptom I was able to make it work by going to the BIOS and set the IO & IRQ there. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Re:parport disabled?
* Ralf Hildebrandt [EMAIL PROTECTED]: Try disabling acpi. Didn't help. Same symptom I was able to make it work by going to the BIOS and set the IO IRQ there. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Re:parport disabled?
* [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > Whenever I "modprobe parport_pc", I get this message: > > > > Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b activated. > > Jan 27 10:55:47 hummus kernel: parport: PnPBIOS parport detected. > > Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b disabled. > > > > and the parallel port is unusable ever after. > > This is with Kernel 2.6.10-ac10 and 2.6.10-ac11 > > > > How can I make my parallel port usable again? > Try disabling acpi. Didn't help. Same symptom -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
parport disabled?
Whenever I "modprobe parport_pc", I get this message: Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b activated. Jan 27 10:55:47 hummus kernel: parport: PnPBIOS parport detected. Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b disabled. and the parallel port is unusable ever after. This is with Kernel 2.6.10-ac10 and 2.6.10-ac11 How can I make my parallel port usable again? -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
parport disabled?
Whenever I modprobe parport_pc, I get this message: Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b activated. Jan 27 10:55:47 hummus kernel: parport: PnPBIOS parport detected. Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b disabled. and the parallel port is unusable ever after. This is with Kernel 2.6.10-ac10 and 2.6.10-ac11 How can I make my parallel port usable again? -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Re:parport disabled?
* [EMAIL PROTECTED] [EMAIL PROTECTED]: Whenever I modprobe parport_pc, I get this message: Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b activated. Jan 27 10:55:47 hummus kernel: parport: PnPBIOS parport detected. Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b disabled. and the parallel port is unusable ever after. This is with Kernel 2.6.10-ac10 and 2.6.10-ac11 How can I make my parallel port usable again? Try disabling acpi. Didn't help. Same symptom -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.10-ac9
* Alan Cox <[EMAIL PROTECTED]>: > 2.6.10-ac9 I tried building it with gcc-4.0 -- while the build went fine, it just wouldn't boot (which doesn't suprise me a bit). Why is that? -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.10-ac9
* Alan Cox [EMAIL PROTECTED]: 2.6.10-ac9 I tried building it with gcc-4.0 -- while the build went fine, it just wouldn't boot (which doesn't suprise me a bit). Why is that? -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
