linux-kernel - Re: 2.6.25-rc3-git3: Reported regressions from 2.6.24

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 6 Mar 2008 15:24:15 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	mingo@...e.hu, g.liakhovetski@....de, rjw@...k.pl,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	bunk@...nel.org, gregkh@...e.de
Subject: Re: 2.6.25-rc3-git3: Reported regressions from 2.6.24

On Thu, 6 Mar 2008 15:13:31 -0800
Suresh Siddha <suresh.b.siddha@...el.com> wrote:

> > sd 1:0:0:0: [sdb] Stopping disk
> > sd 0:0:0:0: [sda] Synchronizing SCSI cache
> > sd 0:0:0:0: [sda] Stopping disk
> > ACPI: PCI interrupt for device 0000:05:00.1 disabled
> > ACPI: PCI interrupt for device 0000:05:00.0 disabled
> > ACPI: Preparing to enter system sleep state S5
> > Disabling non-boot CPUs ...
> > CPU 1 is now offline
> > SysRq : Show State
> >   task                        PC stack   pid father
> 
> I have been looking into a similar issue, which stops my system going into
> standy.

OK.

> > 
> > So CPU 1 is offline.  But the comatose watchdog thread is pinned to CPU 1. 
> > Could this be related to the problem?  By what means is a task which is
> > pinned to a going-away CPU handled?  How is this guy supposed to ever run
> > again?
> 
> move_task_off_dead_cpu() should move that thread to another online cpu. But
> for some reason it isn't running.

hm.  What guarantees that kernel/sched.c:migration_call(CPU_DEAD) is called
before kernel/softlockup.c:cpu_callback(CPU_DEAD)?  Just the ordering in
do_pre_smp_initcalls(), and notifier-chain behaviour, I guess.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/