Slackware 12.0 crashes

At about 00:00 GMT (about an hour ago) all of my Slackware 12.0 boxes crashed 
with a kernel panic of some sort. No problems with boxes with earlier or later 
versions of Slackware.

There was a leap second in the ntp time system at 00:00 GMT. I am suspecting 
that this was the trigger, but I'm not really sure.

Anyone else notice something similar?

Steve

--

-- 
--------------------------------------------------------------------------
Steven Saner <ssaner <at> pantheranet.com>

Re: Slackware 12.0 crashes

On Wed, 31 Dec 2008 19:10:56 -0600
Steven Saner <ssaner <at> pantheranet.com> wrote:

> At about 00:00 GMT (about an hour ago) all of my Slackware 12.0 boxes
> crashed with a kernel panic of some sort. No problems with boxes with
> earlier or later versions of Slackware.
> 
> There was a leap second in the ntp time system at 00:00 GMT. I am
> suspecting that this was the trigger, but I'm not really sure.
> 
> Anyone else notice something similar?

Well, I was about to say that this was a good joke, but then it hit me
that my firewall had crashed a bit ago.  This was about 6:00PM
localtime, so I didn't think anything about the new year.  However,
guess what 1800 CDT is...  Guess what Slackware version my firewall is
running...  :/

-RW

_______________________________________________
slackware mailing list
slackware <at> mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/slackware

Re: Slackware 12.0 crashes

On Wed, 31 Dec 2008, Robby Workman wrote:

> Well, I was about to say that this was a good joke, but then it hit me
> that my firewall had crashed a bit ago.  This was about 6:00PM localtime,
> so I didn't think anything about the new year.  However, guess what 1800
> CDT is...  Guess what Slackware version my firewall is running...  :/

   What's the solution? Reboot?

Happy New Year in any case,

Rich

--

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: Slackware 12.0 crashes

On Dec 31, 2008, at 19:31, Robby Workman <rw <at> rlworkman.net> wrote:

> On Wed, 31 Dec 2008 19:10:56 -0600
> Steven Saner <ssaner <at> pantheranet.com> wrote:
>
>> At about 00:00 GMT (about an hour ago) all of my Slackware 12.0 boxes
>> crashed with a kernel panic of some sort. No problems with boxes with
>> earlier or later versions of Slackware.
>>
>> There was a leap second in the ntp time system at 00:00 GMT. I am
>> suspecting that this was the trigger, but I'm not really sure.
>>
>> Anyone else notice something similar?
>
>
> Well, I was about to say that this was a good joke, but then it hit me
> that my firewall had crashed a bit ago.  This was about 6:00PM
> localtime, so I didn't think anything about the new year.  However,
> guess what 1800 CDT is...  Guess what Slackware version my firewall is
> running...  :/

Well I guess I'm glad it wasn't just me.  I guess it about has to be a  
kernel issue as the ntpd version is the same as 12.1.

Steve

>
>
> -RW
> _______________________________________________

Re: KDE Bluetooth

On Mon, 22 Dec 2008 21:29:06 +0100
Morten Juhl-Johansen Zölde-Fejér <mjjzf <at> syntaktisk.dk> wrote:

> Any of you have experience with KDE Bluetooth? I have installed the
> new Slackbuild on Slack 12.2, but it keeps crashing.
> This is what I get:
> ~ $ kbluetooth 
> kbluetooth: [KBluetooth::DBusSignal::DBusSignal(const QString&, const
> QString&, const QString&, DBusConnection*)] : org.bluez
> path: /org/bluez interface: org.bluez.Manager conn: 0x80da748
> kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const
> QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager
> method: ListAdapters kbluetooth: libkbluetooth: getStringList(): A
> security policy in place prevents this sender from sending this
> message to this recipient, see message bus configuration file
> (rejected message had interface "org.bluez.Manager" member
> "ListAdapters" error name "(unset)" destination "org.bluez")
> kbluetooth: [QValueList<QString> KBluetooth::Manager::listAdapters()]
> 0 kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const
> QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager
> method: ListAdapters kbluetooth: libkbluetooth: getStringList(): A
> security policy in place prevents this sender from sending this
> message to this recipient, see message bus configuration file
> (rejected message had interface "org.bluez.Manager" member
> "ListAdapters" error name "(unset)" destination "org.bluez")
> kbluetooth: [KBluetooth::DBusSignal::DBusSignal(const QString&, const
> QString&, const QString&, DBusConnection*)] : org.bluez
> path: /org/bluez interface: org.bluez.Security conn: 0x80da748
> kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const
> QString&)] : org.bluez path: /org/bluez mInterfacE:

Re: Slackware 12.0 crashes

On Wed, 31 Dec 2008 17:36:08 -0800 (PST)
Rich Shepard <rshepard <at> appl-ecosys.com> wrote:

> On Wed, 31 Dec 2008, Robby Workman wrote:
> 
> > Well, I was about to say that this was a good joke, but then it hit
> > me that my firewall had crashed a bit ago.  This was about 6:00PM
> > localtime, so I didn't think anything about the new year.  However,
> > guess what 1800 CDT is...  Guess what Slackware version my firewall
> > is running...  :/
> 
>    What's the solution? Reboot?

In my case, the "solution" was to do a hard shutdown and then bring the
machine back up.  It was still powered on, but unresponsive to ping and
all other network activity.  That almost certainly means "kernel panic"
- unfortunately, it's in a closet with no keyboard or monitor, so I
  didn't see any messages.  

If I'd made the connection sooner, then I would have hooked up a
monitor before I "fixed" it.  Oh well.  I wonder if I can reproduce it
in a vm...

> Happy New Year in any case,

Thanks; same to you and everyone else here.

-RW

Re: Slackware 12.0 crashes

On Wed, 31 Dec 2008 20:45:40 -0600
Robby Workman <rw <at> rlworkman.net> wrote:

> If I'd made the connection sooner, then I would have hooked up a
> monitor before I "fixed" it.  Oh well.  I wonder if I can reproduce it
> in a vm...

Let's find out 

root <at> test12:~# cat /etc/slackware-version ; uname -a ; date -u
Slackware 12.0.0
Linux test12 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686 AMD
Athlon(tm) 64 X2 Dual Core Processor 6000+ AuthenticAMD GNU/Linux Wed
Dec 31 22:19:29 UTC 2008

_______________________________________________
slackware mailing list
slackware <at> mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/slackware

Re: KDE Bluetooth

---- 8< ---- Robby Workman ---- 8< ----
> I've not, and I don't have any bluetooth gadgets to play with, but...
> I might have some clue what's happening, but it's not trivial to find
> out on your end.  Are you game for building a new version of dbus?
>
> -RW
---- 8< ---- Robby Workman ---- 8< ----

I would be, but as it happens, I was suggested a solution that worked:
http://www.linuxquestions.org/questions/slackware-14/kde-bluetooth-dies-693167/

Yours,
Morten
__
http://www.syntaktisk.dk

Re: Slackware 12.0 crashes

Hi,

2009/1/1 Robby Workman <rw <at> rlworkman.net>:

> Let's find out 

What was the outcome of this test?

I have two slack12.0 boxes that went offline at exactly 2am SAST,
which would be 00:00 GMT (or UTC). This coincides with the additional
leap second that was added - both boxes were synchronized using ntpd.

I have other slack12.0 boxes that did not go down, the only difference
being that the ones that went down carried the stock kernel, the ones
that stayed up had newer hand-compiled kernels.

-Tiaan.

Re: Slackware 12.0 crashes

On Thu, 1 Jan 2009 18:37:26 +0200
"Tiaan van Aardt" <tiaanv <at> gmail.com> wrote:

> 2009/1/1 Robby Workman <rw <at> rlworkman.net>:
> 
> > Let's find out 
> 
> What was the outcome of this test?

No repro, which in hindsight, is exactly as expected.  0000 UTC didn't
occur again, so there was no leap second added again to screw with
things.  

-RW

_______________________________________________
slackware mailing list
slackware <at> mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/slackware