On Thu, Mar 18, 2010 at 04:53:13PM +0100, Claudio Prono wrote:

C ha scritto:

...

On Thu, Mar 18, 2010 at 13:51, Claudio Prono wrote:

...

Anyone have experienced any problem with the last kernel upgrade on OpenSuSE 11.0 x64? After that upgrade, i don't know if is just a random case or what, i have two servers with random, and frequently, die. I don't know the cause of the death, because i have nothing relevant on the log, simply the machine randomly freezes and becomes totally unresponsive. It accours after 10-20 mins from the boot sequence, but i don't know what can be the cause. When this problem occours i have to hard reset the machine, and reboots normally, until the next crash.

Any hint of what is happening? The new kernel is only a supposition, is the most relevant change before that situation....

Yes... i've had exactly the same problem on one of my computers (an Asus Eee with 11.2 fully updated). Oddly it's not happening on my main computer which is running on the same kernel. I experience the exact same symptoms you've described - I posted a question (about a possible kernel panic) to the list here about 12 hours ago... no answers, only an off list comment from someone else experiencing the same symptoms.

It's really annoying.. nothing in the logs anywhere... no clues as to what's going wrong... just sold hard lockup that only a full reset can recover from.

C.

OMG, i am not the only.... SuSE support, any solution? Is a real bad situation..... and now i start to think there is something wrong with the actual kernel...

Can you just downgrad to the previous released kernel and see if it persists. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

C ha scritto:

On Thu, Mar 18, 2010 at 16:56, Marcus Meissner wrote:

...

Can you just downgrad to the previous released kernel and see if it persists.

I've moved from 2.6.31.12 to 2.6.31.8. I'll leave it running and see if the lockup happens.. it's entirely random so.. really hard to trigger :-P

C.

Downgraded me too to a previous kernel release. But now the problem is another...the machine is very very slow! But with top, no processes consuming cpu or ram or swap, nothing wrong...but is seems more slow than ever... What can be? Claudio Prono. -- -------------------------------------------------------------------------------- Claudio Prono OPST System Developer Gsm: +39-349-54.33.258 @PSS Srl Tel: +39-011-32.72.100 Via San Bernardino, 17 Fax: +39-011-32.46.497 10141 Torino - ITALY http://atpss.net/disclaimer -------------------------------------------------------------------------------- PGP Key - http://keys.atpss.net/c_prono.asc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Adam Tauno Williams said the following on 03/18/2010 02:41 PM:

On Thu, 2010-03-18 at 17:09 +0100, C wrote:

...

On Thu, Mar 18, 2010 at 16:56, Marcus Meissner wrote:

...

Can you just downgrad to the previous released kernel and see if it persists.

I've moved from 2.6.31.12 to 2.6.31.8. I'll leave it running and see if the lockup happens.. it's entirely random so.. really hard to trigger :-P

I'm on 2.6.31.12-0.1-desktop and it is working perfectly. No crashes.

2.6.31.12-0.1-desktop #1 SMP PREEMPT 2010-01-27 08:20:11 +0100 i686 -- "Realizing the importance of the case, my men are rounding up twice the number of usual suspects" - Cpt Renault to Major Strasser, Cassablanaca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

C ha scritto:

On Thu, Mar 18, 2010 at 19:41, Adam Tauno Williams wrote:

...

On Thu, 2010-03-18 at 17:09 +0100, C wrote:

...

On Thu, Mar 18, 2010 at 16:56, Marcus Meissner wrote:

...

Can you just downgrad to the previous released kernel and see if it persists.

I've moved from 2.6.31.12 to 2.6.31.8. I'll leave it running and see if the lockup happens.. it's entirely random so.. really hard to trigger :-P

I'm on 2.6.31.12-0.1-desktop and it is working perfectly. No crashes.

Same here... on my desktop machine... but on the netbook it's def locking up. Other people are reporting it locking on various machines.. not all machines running 2.6.31.12.. just some.

It's really hard to diagnose though... there's absolutely nothing in the error or message logs... the machine is 100% dead when this happens.. I can't ssh to it etc. The only indication that it's actually "running" other than the frozen display is the flashing caps lock LED. If all the machines I'm using with 2.6.31.12 were showing the same behavior, it'd be a lot easier to nail down... but.. it's only some... which makes me wonder if it's down to a CPU type... or a very specific chipset combination... or a sound card... or something along those line.s

C.

After the downgrade of the kernel you have resolved the situation? I have got some problems anyway after the kernel downgrade... Claudio. -- -------------------------------------------------------------------------------- Claudio Prono OPST System Developer Gsm: +39-349-54.33.258 @PSS Srl Tel: +39-011-32.72.100 Via San Bernardino, 17 Fax: +39-011-32.46.497 10141 Torino - ITALY http://atpss.net/disclaimer -------------------------------------------------------------------------------- PGP Key - http://keys.atpss.net/c_prono.asc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2010-03-18 at 20:00 -0400, Brian K. White wrote:

...

...

After the downgrade of the kernel you have resolved the situation? I have got some problems anyway after the kernel downgrade...

Claudio.

I don't think I've seen anyone say they have the problem on kernel-default yet, all kernel-desktop so far. So as an alternative to downgrading, you might try kernel-default.

Or as someone else said, kernel of the day, though I don't know exactly what they mean by that. Some particular buildservce repo? rolling your own from kernel.org? opensuse-factory?

--

Rolling my own from kernel.org is something i didn't have to do for a very long time.... Just using the one's that came from SuSE. These can be found at (atleast) two places: The very official: http://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/ And one of the mirrors: http://ftp5.gwdg.de/pub/opensuse/repositories/Kernel:/openSUSE-11.2/openSUSE... ps, btw i tried to downgrade aswell (without any improvement), first the i tried, but forgot to mention it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

C wrote:

On Thu, Mar 18, 2010 at 21:39, Claudio Prono wrote:

...

...

...

...

...

Can you just downgrad to the previous released kernel and see if it persists.

I've moved from 2.6.31.12 to 2.6.31.8. I'll leave it running and see if the lockup happens.. it's entirely random so.. really hard to trigger :-P

I'm on 2.6.31.12-0.1-desktop and it is working perfectly. No crashes. Same here... on my desktop machine... but on the netbook it's def locking up. Other people are reporting it locking on various machines.. not all machines running 2.6.31.12.. just some.

After the downgrade of the kernel you have resolved the situation? I have got some problems anyway after the kernel downgrade...

OK, after the downgrade, no more lockups, but then I started having WiFi issues... the same I had before.. soemthing in the older kernel and my WiFi don't get along.

Anyway, moved back to the latest kernel, and within an hour or so.. lockup. WiFi works well though :-)

This is the default kernel, 32 bit. On my main system, also running the default kernel, it's 64 bit though, and never locks up. Maybe thats' the diff... the key here? The only 32 bit kernel I'm using is the one on the netbook.. that's the one that locks up. All other systems (quite a few if I include all the ones I've installed and support etc) are 64 bit kernels.

For the others experiencing lockups... is that on a 32 bit kernel?

C.

What do you mean "the default" ? The kernel that is installed BY default, is "kernel-desktop". However there is another kernel that is not installed by default, which is "kernel-default". Before 11.2 there was no kernel-desktop, just kernel-default and the various special ones like kernel-xen. That's why it's called -default, because it _was_ the default originally. This kernel had all features enabled and was tuned more for throughput than latency and favored reliability over speed. So it's good for servers. In 11.2 they added kernel-desktop, which removes several features they believe that desktop users do not need, sets some kernel config options to favor latency over throughput, and increase the the gcc optimization (favor speed over reliability). And, they made this new desktop-tuned kernel the one that is installed by default, because they believe that most of their users are desktop users. That is how the backwards-seeming naming came about. That is what I meant by saying "try installing kernel-default" But in any event, kotd sounds like the better answer for a desktop user as then you get to still have a desktop-tuned kernel. The advantage to trying kernel-default is just that you can try it now without adding any other repos, and it would be informative to find out if my hunch is correct that only kernel-desktop has the problem. But if it's already fixed in kotd, that last really doesn't matter much. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Mar 19, 2010 at 14:00, Adam Tauno Williams wrote:

Or, even more likely, you have a driver issue specific to the system you are using.  When you have an oops is it almost always a device driver.

Is it an oops? The thing that baffled me is the absolute lack of logging info. I've had problems with kernels in the past, where the Kernel died for whatever reason, and the caps lock, num lock and scroll lock LEDs would flash... as far as I remember there was some kind of dump to the messages log that at least gave some hint where the problem was... this time nothing.

Are your main system and secondary system really *identical* hardware? If not your comparison of the stability of the two doesn't mean much.

Definitely not. The unstable system is an Asus Eee... my "stable" system is a home built system on an AMD dual core. The comparison of the stability wasn't to say if one was stable why not the other since they are identical... it was just as a point of reference... nothing more. Anyway, I think the problem with whatever was spazzing out the 2.6.31.12 kernel-desktop has been resolved in a newer kernel. I pulled down the KOTD from the factory kernel repository (2.6.33), and it seems to be humming along fine now - I've had the laptop running for a few days now and put it through some testing, and haven't had a single lockup. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu March 18 2010 19:41:41 Adam Tauno Williams wrote:

On Thu, 2010-03-18 at 17:09 +0100, C wrote:

...

On Thu, Mar 18, 2010 at 16:56, Marcus Meissner wrote:

...

Can you just downgrad to the previous released kernel and see if it persists.

I've moved from 2.6.31.12 to 2.6.31.8. I'll leave it running and see if the lockup happens.. it's entirely random so.. really hard to trigger :-P

I'm on 2.6.31.12-0.1-desktop and it is working perfectly. No crashes.

Me, too. All's well here with 2.6.31.12-0.1-desktop. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2010-03-18 at 14:24 -0400, Anton Aylward wrote:

Claudio Prono said the following on 03/18/2010 11:53 AM:

...

...

It's really annoying.. nothing in the logs anywhere... no clues as to what's going wrong... just sold hard lockup that only a full reset can recover from.

+1

Have you tried seeing is SysRq still works after the oops? Possible to hook up another computer a dumb terminal (serial console)? http://www.mulix.org/lectures/kernel_oopsing/kernel_oopsing.pdf -- Adam Tauno Williams LPIC-1, Novell CLA http://www.whitemiceconsulting.com OpenGroupware, Cyrus IMAPd, Postfix, OpenLDAP, Samba -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Adam Tauno Williams said the following on 03/18/2010 02:39 PM:

On Thu, 2010-03-18 at 14:24 -0400, Anton Aylward wrote:

...

Claudio Prono said the following on 03/18/2010 11:53 AM:

...

...

It's really annoying.. nothing in the logs anywhere... no clues as to what's going wrong... just sold hard lockup that only a full reset can recover from.

+1

Have you tried seeing is SysRq still works after the oops?

Maybe its these odd key combinations on the laptop but no, I haven't been able to get sysrq to work alt+[fn]+end,h 'end' is also labelled [sysrq] laptop, remember, so a dozen and a half keys have that additional labelling. And yes, I have tried alt+[fn]+home,h 'cos "home" is labelled [prtsc] That doesn't work either. And yes I checked that /proc/sys/kernel/sysrq was set to "1" What do you suggest now? -- "If you have only one layer of protection you are only as safe as the next bug-de-jour" - Brad M Powell, Snr Network Security Architect, Sun Microsystems -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans Witvliet ha scritto:

On Thu, 2010-03-18 at 16:53 +0100, Claudio Prono wrote:

...

OMG, i am not the only.... SuSE support, any solution? Is a real bad situation..... and now i start to think there is something wrong with the actual kernel...

After a kernel upgrade on a 11.0 system, it failed completely to come up again, (first idea was HW-problem, apperently cciss-driver problem)

Thought all was lost, so booted 11.2 tried a system-upgrade, no show, still dead. Someone suggested to use the kernel-of-the-day...

No problems any more

Sorry, what is the kernel of the day? Claudio. -- -------------------------------------------------------------------------------- Claudio Prono OPST System Developer Gsm: +39-349-54.33.258 @PSS Srl Tel: +39-011-32.72.100 Via San Bernardino, 17 Fax: +39-011-32.46.497 10141 Torino - ITALY http://atpss.net/disclaimer -------------------------------------------------------------------------------- PGP Key - http://keys.atpss.net/c_prono.asc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org