Hi, Chris wrote:

Hello,the last few days I have sometimes a kernel panic and I cannot do anything in order to reboot unless unplug the laptop.Is there any way to reboot or exit from that situation?Is there any way to keep these messages from the screen for debugging? Did you do try this: http://en.opensuse.org/Bugs/Kernel ? If nothing helps, make pictures and please file a Bug at http://bugzilla.novell.com with this pictures attached.

Regards, -- Patrick Kirsch - Quality Assurance Department SUSE Linux Products GmbH GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Did you do try this: http://en.opensuse.org/Bugs/Kernel ?

I am trying to open the link but it doesn't load...for now. ___________________________________________________________ Χρησιμοποιείτε Yahoo!; Βαρεθήκατε τα ενοχλητικά μηνύματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://login.yahoo.com/config/mail?.intl=gr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 03 January 2008 10:21, Chris wrote:

Yes I think that the matter is a joystick:Microsoft Sidewinder Presicion 2 which is a little old.

...

   Then, reconfigure (and test for a while) each peripheral.... one by one... until you find the one that is causing the problem.

How to configure the joystick;; You might be interested in trying the classic joystick from Saitek (Aviator AV8R) fully programmable, 8 toggle switch, 1 rotor switch, dual throttles, stick has thumb trim, three buttons, and firing button.

USB, works well with Linux (my son uses it to play GL-117 and others) and is reasonably priced. YMMV -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 03 January 2008 13:10, Carlos E. R. wrote:

If the joystick driver is part of the kernel, then the culprit remains being the kernel. Yes, I disagree.

Pluggable modules extent the kernel but are not THE kernel. (1) kernel runs without module (2) kernel panics with module plugged in (3) kernel runs when module unplugged The culprit is the module... not the kernel. And all the rhetoric and flapdoodle about pluggable kernel extensions is just that. Yes, the module provides services (kernel services) through a standard kernel interface, and yes, typically only kernel developers write modules, and yes, the kernel "team" determines which modules get "into" the kernel... but all of that flap is semantics when it comes time to debug a problem. Which module is it? If I come along and write a module replacement (unsanctioned) for what-ever-device (tainting the kernel) and the silly thing runs fine its my work as a module writer and nobody knows or cares, but if the silly thing causes the kernel to panic do you think anybody in kernel land wants a bug report for it?? No way. There would be nothing wrong with THE kernel except for the simple fact that MY module caused it to panic. On the other hand if a sanctioned module is causing the kernel to panic, then I think it would be helpful to be able to isolate the failing module BEFORE giving a report to the kernel team. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

If the module comes with the kernel supplied by suse, then it is an integral part of the kernel supplied by suse, and the kernel is this the culprit. It is not a third party module installed by the user. I think you might be missing my point | question. Ok, we report the bug to

On Thursday 03 January 2008 20:23, Carlos E. R. wrote: the suse kernel people (third party, since they don't own the kernel) and they fix their module, or the module owner fixes the module), and then the "suse kernel" is fixed. OK, don't the suse kernel people want to know which module is failing before a bug report is submitted as a "kernel" problem? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-01-03 at 20:35 -0600, M Harris wrote:

...

If the module comes with the kernel supplied by suse, then it is an integral part of the kernel supplied by suse, and the kernel is this the culprit. It is not a third party module installed by the user. I think you might be missing my point | question. Ok, we report the bug to

On Thursday 03 January 2008 20:23, Carlos E. R. wrote: the suse kernel people (third party, since they don't own the kernel) and they fix their module, or the module owner fixes the module), and then the "suse kernel" is fixed. OK, don't the suse kernel people want to know which module is failing before a bug report is submitted as a "kernel" problem?

If you have the expertise, do so. If not, simply report the Oops or panic to suse people and they can help the reporter get the data needed, and then perhaps they can solve it or report upstream. As to suse being third party... not completely. They have a good number of kernel developer/contributors on their staff. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHgB24tTMYHG2NR9URAmKUAKCVA02JqZW6ldlUO5PTEodh6CdZywCeLPJE gWDjK2HKR2rS8O45DG1G2GA= =/sN6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-01-07 at 01:05 -0600, M Harris wrote: El 2008-01-07 a las 01:05 -0600, M Harris escribió:

Date: Mon, 7 Jan 2008 01:05:53 -0600 From: M Harris Reply-To: OS-en To: opensuse@opensuse.org Subject: Re: [opensuse] Kernel panic exit

...

If you have the expertise, do so. If not, simply report the Oops or panic to suse people and they can help the reporter get the data needed, and then perhaps they can solve it or report upstream. ok. so, they have first line folks involved to isolate the module and then

On Saturday 05 January 2008 18:15, Carlos E. R. wrote: the kernel developers get involved? That makes reporting bugs easier... I suspect it takes a little longer on the suse side then. When I was doing that work for IBM the second level developers (primary OS developers) would not even get involved until the first level had isolated the correct module... and heaven help them if they isolated the wrong one. :-))

:-) Of course, they would love the user filling the bugzilla with all the info pointing to the culprit module, down to the line of code if possible. But there are all kinds of users: some may be kernel gurus, and some may be first time users, which will need a lot of help to produce the needed info. And if the bugzilla people are too busy, the latter kind will suffer long delays, I guess. And I think they are prety busy. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHghBqtTMYHG2NR9URAo7vAJ4rQMGg501cz96idRaztAesfPb4LACfQ+7E sDBiEciG0kmsptIBLfPw2BI= =dJjR -----END PGP SIGNATURE-----