linux-kernel - Re: [Ops] 2.6.18

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Oct 2006 16:47:36 +0200
From:	Andi Kleen <ak@....de>
To:	"S.??a??lar Onur" <caglar@...dus.org.tr>
Cc:	john stultz <johnstul@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [Ops] 2.6.18

On Wed, Oct 04, 2006 at 04:38:25PM +0300, S.??a??lar Onur wrote:
> 02 Eki 2006 Pts 20:36 tarihinde, john stultz ??unlar?? yazm????t??: 
> > On Sun, 2006-10-01 at 03:32 +0300, S.??a??lar Onur wrote:
> > > Hi;
> > >
> > > Here [1] are the two different panics with 2.6.18 on vmware, its
> > > reproducable on every 4-5 reboot [same config/kernel in "2.6.18 Nasty
> > > Lockup" thread, so i CC'd to that thread's posters also]
> > >
> > > [1] http://cekirdek.pardus.org.tr/~caglar/2.6.18/
> >
> > Hmmm.. That first oops looks interesting to me.
> >
> > When you say they're reproducible every 4-5 reboots, which one do you
> > mean?
> 
> For every 10 reboots first one occurs at least 6 times, 3 times second one 
> occurs and for last it boots :)

I assume it must be something specific to your configuration
or setup.

If plain 2.6.18 was that unstable we would be flooded in reports.
But that's not the case.  I also definitely don't see it on any of my systems
(except that if you use PIT time source on a multi core system 
things break on i386) 

Perhaps you list your setup and your configuration and a boot log
for the working case? I also I would really recommend to do the make 
distclean ; recompile step I mentioned earlier.

-Andi
-
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/