Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Martin C. Barlow" <mips@martin.barlow.name>
To: "'Thiemo Seufer'" <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: <linux-mips@linux-mips.org>
Subject: RE: hwclock and df seg fault
Date: Sun, 21 Mar 2004 03:16:14 +1100	[thread overview]
Message-ID: <000001c40e96$adbdb1f0$6500a8c0@colombia> (raw)
In-Reply-To: <20040320122225.GK25832@rembrandt.csv.ica.uni-stuttgart.de>

Thiemo

With PREEMP turned off, the hwclock command works again. Looks like the
new scheduler may have a little problem.
The df problem is still there. This may be just a user space
mis-configuration error. I'll see if I can find the problem.
Let me know if you need any dumps.

marty

-----Original Message-----
From: Thiemo Seufer [mailto:ica2_ts@csv.ica.uni-stuttgart.de] 
Sent: Saturday, 20 March 2004 11:22 PM
To: Martin C. Barlow
Cc: linux-mips@linux-mips.org
Subject: Re: hwclock and df seg fault


Martin C. Barlow wrote:
[snip]
> Barcelona:/var/log# hwclock
> Mar 21 19:11:20 Barcelona kernel: bad: scheduling while atomic!
[snip]
> Mar 21 19:11:20 Barcelona kernel: note: hwclock[369] exited with 
> preempt_count 2

So this was with CONFIG_PREEMPT, I guess. Does it happen also without
that?


Thiemo

WARNING: multiple messages have this Message-ID (diff)
From: "Martin C. Barlow" <mips@martin.barlow.name>
To: 'Thiemo Seufer' <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org
Subject: RE: hwclock and df seg fault
Date: Sun, 21 Mar 2004 03:16:14 +1100	[thread overview]
Message-ID: <000001c40e96$adbdb1f0$6500a8c0@colombia> (raw)
Message-ID: <20040320161614.zRDQjFpXSoPZKl2JVG7i1VKJH244LUsOVNr64kAM4-Q@z> (raw)
In-Reply-To: <20040320122225.GK25832@rembrandt.csv.ica.uni-stuttgart.de>

Thiemo

With PREEMP turned off, the hwclock command works again. Looks like the
new scheduler may have a little problem.
The df problem is still there. This may be just a user space
mis-configuration error. I'll see if I can find the problem.
Let me know if you need any dumps.

marty

-----Original Message-----
From: Thiemo Seufer [mailto:ica2_ts@csv.ica.uni-stuttgart.de] 
Sent: Saturday, 20 March 2004 11:22 PM
To: Martin C. Barlow
Cc: linux-mips@linux-mips.org
Subject: Re: hwclock and df seg fault


Martin C. Barlow wrote:
[snip]
> Barcelona:/var/log# hwclock
> Mar 21 19:11:20 Barcelona kernel: bad: scheduling while atomic!
[snip]
> Mar 21 19:11:20 Barcelona kernel: note: hwclock[369] exited with 
> preempt_count 2

So this was with CONFIG_PREEMPT, I guess. Does it happen also without
that?


Thiemo

  reply	other threads:[~2004-03-20 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20 10:05 hwclock and df seg fault Martin C. Barlow
2004-03-20 10:05 ` Martin C. Barlow
2004-03-20 12:22 ` Ralf Baechle
2004-03-20 12:57   ` Martin C. Barlow
2004-03-20 12:57     ` Martin C. Barlow
2004-03-20 16:47   ` Martin C. Barlow
2004-03-20 16:47     ` Martin C. Barlow
2004-03-20 17:13     ` Ralf Baechle
2004-03-20 12:22 ` Thiemo Seufer
2004-03-20 16:16   ` Martin C. Barlow [this message]
2004-03-20 16:16     ` Martin C. Barlow
2004-03-20 19:54     ` Ralf Baechle
2004-03-22 18:00     ` Jun Sun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001c40e96$adbdb1f0$6500a8c0@colombia' \
    --to=mips@martin.barlow.name \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox