| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 13 Mar 2008 15:35:28 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: "Torsten Kaiser" <just.for.lkml@...glemail.com> Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pbadari@...il.com Subject: Re: 2.6.25-rc5-mm1 On Thu, 13 Mar 2008 23:05:11 +0100 "Torsten Kaiser" <just.for.lkml@...glemail.com> wrote: > On Wed, Mar 12, 2008 at 9:01 PM, Torsten Kaiser > <just.for.lkml@...glemail.com> wrote: > > On Wed, Mar 12, 2008 at 8:44 PM, Andrew Morton > > <akpm@...ux-foundation.org> wrote: > > > OK, so it looks like it died during networking initialisation. > > > > > > Could you please add initcall_debug to the boot command line so we can see > > > which function it is getting stuck in? > > > > Yes, here is the result: > > [ 2.573979] PCI-DMA: Disabling AGP. > > [ 2.577639] PCI-DMA: aperture base @ 8000000 size 65536 KB > > [ 2.589504] PCI-DMA: using GART IOMMU. > > [ 2.593258] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture > > [ 2.600132] initcall pci_iommu_init+0x0/0x20() returned 0 after 19 msecs > > [ 2.622146] calling hpet_late_init+0x0/0x140() > > [ 2.626689] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31 > > [ 2.633022] hpet0: 3 32-bit timers, 25000000 Hz > > [ 2.638562] initcall hpet_late_init+0x0/0x140() returned 0 after 9 msecs > > [ 2.654545] calling clocksource_done_booting+0x0/0x20() > > [ 2.659855] initcall clocksource_done_booting+0x0/0x20()<6>Time: > > > > hpet clocksource has been installed. > > [ 2.662185] returned 0 after 0 msecs > > [ 2.688448] calling init_pipe_fs+0x0/0x60() > > [ 2.695423] initcall init_pipe_fs+0x0/0x60() returned 0 after 0 msecs > > [ 2.705784] calling init_mnt_writers+0x0/0x70() > > [ 2.711681] initcall init_mnt_writers+0x0/0x70() returned 0 after 0 msecs > > [ 2.721678] calling eventpoll_init+0x0/0x90() > > [ 2.731644] initcall eventpoll_init+0x0/0x90() returned 0 after 0 msecs > > [ 2.738295] calling anon_inode_init+0x0/0x130() > > [ 2.751614] initcall anon_inode_init+0x0/0x130() returned 0 after 0 msecs > > [ 2.771585] calling pcie_aspm_init+0x0/0x30() > > [ 2.779297] initcall pcie_aspm_init+0x0/0x30() returned 0 after 2 msecs > > [ 2.793911] calling acpi_event_init+0x0/0x52() > > > > -> it looked like the system this time already hung here. But just > > pressing the 'Alt' key let the system continue until the network hang. > > (I tried this a second time, again it paused here until I pressed a key) > > > > [ 94.857929] initcall acpi_event_init+0x0/0x52() returned 0 after 29276 msecs > > [ 94.865002] calling pnp_system_init+0x0/0x20() > > [ 94.877935] system 00:06: ioport range 0x4d0-0x4d1 has been reserved > > [ 94.884286] system 00:06: ioport range 0x7b0-0x7df has been reserved > > [ 94.897886] system 00:06: ioport range 0x800-0x80f has been reserved > > [ 94.907886] system 00:06: ioport range 0xbb0-0xbdf has been reserved > > [ 94.917855] system 00:06: ioport range 0x2000-0x207f has been reserved > > [ 94.937827] system 00:06: ioport range 0x2080-0x20ff has been reserved > > [ 94.947827] system 00:06: ioport range 0x2400-0x247f has been reserved > > [ 94.957793] system 00:06: ioport range 0x2480-0x24ff has been reserved > > [ 94.977766] system 00:06: ioport range 0x2800-0x287f has been reserved > > [ 94.987766] system 00:06: ioport range 0x2880-0x28ff has been reserved > > [ 94.997734] system 00:06: ioport range 0x2c00-0x2c7f has been reserved > > [ 95.017708] system 00:06: ioport range 0x2c80-0x2cff has been reserved > > [ 95.024234] system 00:06: iomem range 0x0-0x0 could not be reserved > > [ 95.037678] system 00:06: iomem range 0xfee01000-0xfeefffff could > > not be reserved > > [ 95.060158] system 00:06: iomem range 0xefa80000-0xefabffff has been reserved > > [ 95.070158] system 00:06: iomem range 0xffb00000-0xffbfffff could > > not be reserved > > [ 95.077633] system 00:06: iomem range 0xfff00000-0xffffffff could > > not be reserved > > [ 95.097590] system 00:08: iomem range 0xfec00000-0xfec00fff could > > not be reserved > > [ 95.120064] system 00:08: iomem range 0xfee00000-0xfee00fff could > > not be reserved > > [ 95.130070] system 00:0c: ioport range 0x290-0x297 has been reserved > > [ 95.137523] system 00:0d: iomem range 0x0-0x9ffff could not be reserved > > [ 95.157495] system 00:0d: iomem range 0xc0000-0xcffff has been reserved > > [ 95.167495] system 00:0d: iomem range 0xe0000-0xfffff could not be reserved > > [ 95.177463] system 00:0d: iomem range 0x100000-0xdfffffff could not > > be reserved > > [ 95.197437] system 00:0d: iomem range 0xfec00000-0xffffffff could > > not be reserved > > [ 95.219983] initcall pnp_system_init+0x0/0x20() returned 0 after 162 msecs > > [ 95.226887] calling chr_dev_init+0x0/0xd0() > > [ 95.237813] initcall chr_dev_init+0x0/0xd0() returned 0 after 0 msecs > > [ 95.247378] calling firmware_class_init+0x0/0x90() > > [ 95.257320] initcall firmware_class_init+0x0/0x90() returned 0 after 0 msecs > > [ 95.276031] calling loopback_init+0x0/0x20() > > [ 95.288590] initcall loopback_init+0x0/0x20() returned 0 after 0 msecs > > [ 95.296837] calling cpufreq_gov_performance_init+0x0/0x20() > > [ 95.309084] initcall cpufreq_gov_performance_init+0x0/0x20() > > returned 0 after 0 msecs > > [ 95.317734] calling cpufreq_gov_dbs_init+0x0/0x50() > > [ 95.338090] initcall cpufreq_gov_dbs_init+0x0/0x50() returned 0 after 0 msecs > > [ 95.345254] calling init_acpi_pm_clocksource+0x0/0xc0() > > [ 95.355293] initcall init_acpi_pm_clocksource+0x0/0xc0() returned 0 > > after 0 msecs > > [ 95.374115] calling pcibios_assign_resources+0x0/0x90() > > [ 95.379618] PCI: Bridge: 0000:00:06.0 > > [ 95.394087] IO window: disabled. > > [ 95.397502] MEM window: 0xeff00000-0xefffffff > > [ 95.402032] PREFETCH window: 0x00000000eef00000-0x00000000eeffffff > > [ 95.415189] PCI: Bridge: 0000:00:0b.0 > > [ 95.418860] IO window: e000-efff > > [ 95.438075] MEM window: 0xefe00000-0xefefffff > > [ 95.442610] PREFETCH window: disabled. > > [ 95.455526] PCI: Bridge: 0000:00:0c.0 > > [ 95.459197] IO window: disabled. > > [ 95.462604] MEM window: 0xefd00000-0xefdfffff > > [ 95.475513] PREFETCH window: disabled. > > [ 95.479443] PCI: Bridge: 0000:00:0d.0 > > [ 95.485512] IO window: disabled. > > [ 95.495480] MEM window: 0xefc00000-0xefcfffff > > [ 95.500010] PREFETCH window: disabled. > > [ 95.515455] PCI: Bridge: 0000:00:0f.0 > > [ 95.519124] IO window: d000-dfff > > [ 95.522533] MEM window: 0xefb00000-0xefbfffff > > [ 95.535423] PREFETCH window: 0x00000000e0000000-0x00000000e7ffffff > > [ 95.545456] initcall pcibios_assign_resources+0x0/0x90() returned 0 > > after 79 msecs > > [ 95.557830] calling fill_mp_bus_to_cpumask+0x0/0x100() > > [ 95.575408] initcall fill_mp_bus_to_cpumask+0x0/0x100() returned 0 > > after 0 msecs > > [ 95.593777] calling inet_init+0x0/0x380() > > [ 95.597890] NET: Registered protocol family 2 > > > > -> same hang, no reaction to SysRq. > > > > What looks suspicious: The call to pcie_aspm_init is just before the > > temporary hang. When I used make oldconfig to upgrade the .config from > > 2.6.25-rc3-mm1 to -rc5-mm1 I activated the new option CONFIG_PCIEASPM. > > > > I will try with CONFIG_PCIEASPM_DEBUG added and completely without this option. > > CONFIG_PCIEASPM does not change anything. > Also testing the range of ipc patches you suggested to Badari did not fix it. > > I did a bisect, these patches are currently remaining, but I dod not > have the time for more bisect steps until tomorrow: OK, thanks for persisting. > git-scsi-misc > git-sh > execute-tasklets-in-the-same-order-they-were-queued > git-sched > sched: work around hrtick related lockup > sched: make sure jiffies is up to date before calling __update_rq_clock() > sched: fix rq->clock overflows detection with CONFIG_NO_HZ > sched: make cpu_clock() globally synchronous > sched: remove isolcpus > ftrace: make the task state char-string visible to all > sched: add latency tracer callbacks to the scheduler the sched patches, perhaps.. > latencytop: optimize LT_BACKTRACEDEPTH loops a bit > sched: cleanup old and rarely used 'debug' features. > [SCSI] zfcp: convert zfcp to use target reset and device reset handler > [SCSI] qla4xxx: Add target reset functionality > [SCSI] scsi_error: add target reset handler > [SCSI] ps3rom: Simplify fill_from_dev_buffer() > [SCSI] scsi_debug: use shost_priv macro > [SCSI] scsi_debug: remove unnecessary checking > [SCSI] scsi_debug: remove scsi_debug.h > [SCSI] scsi_debug: stop including drivers/scsi/scsi.h > [SCSI] Remove random noop unchecked_isa_dma users > [SCSI] aacraid: READ_CAPACITY_16 shouldn't trust allocation length in cdb > [SCSI] st: show options currently set in sysfs > [SCSI] st: add option to use SILI in variable block reads > [SCSI] gdth: remove command accessors > [SCSI] aic94xx: Use sas_request_addr() to provide SAS WWN if the > adapter lacks one > [SCSI] libsas: Provide a transport-level facility to request SAS addrs > [SCSI] ips: sg chaining support to the path to non I/O commands > [SCSI] gdth: convert to PCI hotplug API > [SCSI] gdth: PCI probe cleanups, prep for PCI hotplug API conversion > rtc: rtc-sh: Add support for periodic IRQs. > sh: SuperH KEYSC keypad data for Solution Engine 7722 > sh: SuperH KEYSC keypad data for MigoR > sh: SuperH KEYSC platform driver > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists