DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2008-01-20 07:58:10

ChrisOwens
Member
Registered: 2007-12-07
Posts: 31

Anyone seein TWSI errors in log?

My DNS323 runs chroot Debian.  The box really isn't very busy; it runs a very lightly loaded Kerberos KDC and an OpenLDAP server (both redundant backups of another machine).

After it has been up for a few days, I'll start getting pages and pages of the text below  in my log file (BlackHole is the hostname).

All I've been able to find out from  a little Google searching is that TWSI is the Two-Wire-Serial-Interface on the Marvell board.

I haven't a clue what this means.  The only thing that looks amiss when it's in that state if I look at the "status" page of the web interface, it shows the unit's temperature as 0.

Code:

Jan 19 21:05:20 BlackHole kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
Jan 19 21:05:20 BlackHole kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
Jan 19 21:05:20 BlackHole kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
Jan 19 21:05:20 BlackHole kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
Jan 19 21:05:20 BlackHole kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
Jan 19 21:05:20 BlackHole kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .

Last edited by ChrisOwens (2008-01-20 08:01:59)

Offline

 

#2 2008-01-23 21:50:43

Paul
Member
From: Landshut, Germany
Registered: 2007-01-19
Posts: 35
Website

Re: Anyone seein TWSI errors in log?

Yes I have :-(
And not only that the temperature shows 0° - you can't change the fanspeed anymore (in case you're using some sort of custom fanctrl script)...

I'm running a customized Kernel with reboot.ko and already tried using newer twsi-drivers (can't remember where I've found them)... The Problem still exists, though :-(
All my hope is in the mainline series kernel, but I didn't had a chance to compile and try it yet...

Offline

 

#3 2008-01-23 23:50:51

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: Anyone seein TWSI errors in log?

I have plenty of these, too. But with firmware kernels only. I haven't seen any such messages with orion git kernels.

Offline

 

#4 2008-01-24 21:29:12

Paul
Member
From: Landshut, Germany
Registered: 2007-01-19
Posts: 35
Website

Re: Anyone seein TWSI errors in log?

@fonz

as I understood your message, you're running an orion kernel? Is it possible to post your kernel config somewhere??
With my configurations the compiled kernel won't even boot (it just freezes after loading reload.ko)....

Offline

 

#5 2008-01-25 00:19:40

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: Anyone seein TWSI errors in log?

Paul wrote:

@fonz

as I understood your message, you're running an orion kernel? Is it possible to post your kernel config somewhere??
With my configurations the compiled kernel won't even boot (it just freezes after loading reload.ko)....

yes, orion git kernel with patches from hvr. config attached. patches are here: http://wwwhephy.oeaw.ac.at/u3w/r/riedel/www/dns323/

Code:

Linux darkstar 2.6.24-rc5 #1 Fri Jan 18 12:50:43 CET 2008 armv5tel unknown

I'm not booting into the dlink firmware, though.


Attachments:
Attachment Icon linux-2.6.config, Size: 32,217 bytes, Downloads: 747

Offline

 

#6 2008-01-25 12:06:19

Paul
Member
From: Landshut, Germany
Registered: 2007-01-19
Posts: 35
Website

Re: Anyone seein TWSI errors in log?

fonz wrote:

yes, orion git kernel with patches from hvr. config attached. patches are here: http://wwwhephy.oeaw.ac.at/u3w/r/riedel/www/dns323/

yes, I was using that one... but still no luck :-( If I compile the kernel using the dlink's cross-compile toolchain I always end up having a "dirty" kernel (vmlinux-2.6.24-rc5-g4d249b70-dirty). When compiling on the Dlink using "gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)" it compiles perfectly, but freezes when using reload.ko at the end where it says "Reloading...." :-(
How did you compile the kernel?

fonz wrote:

I'm not booting into the dlink firmware, though.

So you're saying you have flashed a customized kernel into the bootloader? that's great news! I'm soo excited right now ;-) Any details?

Offline

 

#7 2008-01-25 15:30:21

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: Anyone seein TWSI errors in log?

Paul wrote:

How did you compile the kernel?

i'm using a gcc-4.2 cross compiler on a i686 host.

Paul wrote:

fonz wrote:

I'm not booting into the dlink firmware, though.

So you're saying you have flashed a customized kernel into the bootloader? that's great news! I'm soo excited right now ;-) Any details?

i've flashed another 2.6.12.6 kernel to boot the dlink firmware with kernel-nfs support.
with the orion kernel, i'm booting from disk - nothing flashed here.

Offline

 

#8 2008-05-22 23:58:57

saltisol
Member
Registered: 2007-07-22
Posts: 22

Re: Anyone seein TWSI errors in log?

After a few days uptime, I today discovered that I get 2x7 messages to my syslog once per minute:

May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:50:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:51:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
May 22 22:52:57 DNS-323 user.warn kernel: TWSI: mvTwsiStopBitSet ERROR - Stop bit TimeOut .

Is this something bad or harmless?
Regardless, I want to get rid of this spam because my syslog is useless if it only contains the last 30 minutes of the above...

has anyone found a solution to get rid of this message?
thanks

Offline

 

#9 2008-05-23 00:02:29

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: Anyone seein TWSI errors in log?

i've seen this, too. often enough, and i think it's a kernel bug. the only 'fix' seems to be a new kernel.

Offline

 

#10 2008-09-15 13:43:44

kreuters
Member
Registered: 2007-04-13
Posts: 13

Re: Anyone seein TWSI errors in log?

i used to get this a lot, but changing the firmware to the CH3NAS (1.04rc6) seems to have fixed it,,

Offline

 

#11 2010-01-03 18:30:31

Opperpanter
Member
From: Eindhoven, Netherlands.
Registered: 2008-08-11
Posts: 89

Re: Anyone seein TWSI errors in log?

Sorry to revive this old thread, but the solution is in disabling the ntpd deamon, and run ntp syncing as a crontab.

From http://nas-tweaks.net/CH3SNAS:Tutorials/ntp :

Step 1 - Disable ntpd on startup, and shut it down right away:

Code:

chmod a-x /ffp/start/ntpd.sh
sh /ffp/start/ntpd.sh stop

Step 2 - Add crontab.

Code:

# This removes firmware cronjobs that interfere with ntpd.
crontab -l | grep -vw '/usr/sbin/daylight' | grep -vw '/usr/sbin/rtc' | crontab -
#Now start the ntp every hour
echo "1 * * * * /usr/sbin/sntp -r -P no de.pool.ntp.org" >> /var/spool/cron/crontabs/root
# force a cronjob update
echo "root" >> /var/spool/cron/crontabs/cron.update

Add the lines of Step2 to /ffp/etc/funplug.local to make the changes persistent over reboots.

Last edited by Opperpanter (2010-01-03 18:31:05)

Offline

 

#12 2010-01-05 05:13:13

atx32
Member
Registered: 2009-01-04
Posts: 20

Re: Anyone seein TWSI errors in log?

You don't need to disable ntpd, just add the -x option. This forces ntpd to always slew the clock to make corrections, instead of stepping for larger offsets. This change alone has eliminated TWSI errors for me. I also made some other changes to /ffp/start/ntpd.sh to write the drift file to /etc (preventing unneeded disk spin-up) and copying it to /ffp/etc upon shutdown.

Code:

#!/ffp/bin/sh

# PROVIDE: ntpd
# REQUIRE: SERVERS
# BEFORE: LOGIN

. /ffp/etc/ffp.subr

name="ntpd"
command="/ffp/bin/ntpd"
ntpd_flags="-x -g -f /etc/ntp.drift"
required_files="/ffp/etc/ntp.conf"
start_cmd="ntpd_start"
stop_cmd="ntpd_stop"

ntpd_start()
{
        # fix /etc/services
        if ! grep -w ntp /etc/services >/dev/null; then
                echo "ntp 123/udp" >>/etc/services
        fi

        # remove rtc and daylight cron jobs
        crontab -l | grep -vw '/usr/sbin/daylight' | grep -vw '/usr/sbin/rtc' | crontab -

        # copy drift file to /etc
        cp /ffp/etc/ntp.drift /etc 2>/dev/null
 
        proc_start $command
}

ntpd_stop()                
{                          
        # copy drift file to /ffp/etc
        cp /etc/ntp.drift /ffp/etc 2>/dev/null
        
        proc_stop $command
}

run_rc_command "$1"

I also changed funplug.local to set the time with ntpdate on boot. This steps the clock so that ntpd can manage better when restricted to only slewing the clock.

Code:

# USA/Central Time
echo 'CST6CDT' >/etc/TZ
# fix /etc/services
if ! grep -w ntp /etc/services >/dev/null; then
        echo "ntp 123/udp" >>/etc/services
fi
ntpdate -b us.pool.ntp.org

With this setup I never have any TWSI issues.

Bill

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB