On Wed, 2007-12-19 at 09:58 +0200, Dotan Shavit wrote:
On Tuesday 18 December 2007, Oded Arbel wrote:
I can see that a lot of time is spent in the hard-IRQ region - sometimes
more then all other regions together.
Lets look for more hints...
- Anything interesting in the logs (during
On Wed, 2007-12-19 at 10:34 +0200, Aviv Greenberg wrote:
Can you send an output of cat /proc/interrupts ? Is there any device
sharing the IRQ line with the network interface?
On Tue, 2007-12-18 at 22:14 +0200, Oron Peled wrote:
6. Why guess?
watch -n10 -d cat /proc/interrupts
I have a strange problem. When I try to login with any user, except
for root, I get an error message saying that the userś home directory
doesn´t exist. I verified that this is NOT true. All home directories
seem to be intact. I GOOGLED and found a suggestion that /etc/passwd
could, for some
It seems as if for some reason the /home partition was not mounted when you
tried to log it.
--
Ori Idan
On Dec 20, 2007 9:52 PM, shlomo solomon [EMAIL PROTECTED] wrote:
I have a strange problem. When I try to login with any user, except
for root, I get an error message saying that the
Check the permissions on /home and /home/user. The user must have +x on
/home and +rx on /home/user. Try to su to the user and check if you can
access its home directory.
On 12/20/07, shlomo solomon [EMAIL PROTECTED] wrote:
I have a strange problem. When I try to login with any user, except
No, as I already wrote, all the home directories are OK. I should have
specifically written that when I login as root, I can cd to them all.
I also tried creating a new user and after verifying that the new user
AND home directory were created, I couldn login as the new user
either.
I have some
On Dec 20, 2007 10:36 PM, Alon Altman [EMAIL PROTECTED] wrote:
Check the permissions on /home and /home/user. The user must have +x on
/home and +rx on /home/user. Try to su to the user and check if you can
access its home directory.
Already tried that - permissons are correct.
As far as su,
Even if you can cd to the directories as root does not mean that you can
read/write there as user. Please supply the output of ls -la /home (as
root).
Alon
On 12/20/07, shlomo solomon [EMAIL PROTECTED] wrote:
No, as I already wrote, all the home directories are OK. I should have
On Thursday, 20 בDecember 2007, Oded Arbel wrote:
I haven't calculated diffs exactly yet, but on first glance it looks
like eth0 interrupts are happening at about 150 a second while cciss0
interrupts are happening at about 20 per second.
Well, ~150 interrupts/seconds is very low interrupt rate
On Dec 20, 2007 11:01 PM, Alon Altman [EMAIL PROTECTED] wrote:
Even if you can cd to the directories as root does not mean that you can
read/write there as user. Please supply the output of ls -la /home (as
root).
Alon
At the moment, I´m using a rescue partition on the same box. So I
Hi all!
Well, this is also a way to make sites compatible with Firefox and other
Mozilla-based browsers. :-)
If you are job hunting and want to use http://www.yjobs.co.il/ and would
prefer to use Firefox, then look no further than:
Another reason kde could fail to write is lack of disk space. Is /home full
or close to full?
Alon
On 12/20/07, shlomo solomon [EMAIL PROTECTED] wrote:
On Dec 20, 2007 11:01 PM, Alon Altman [EMAIL PROTECTED] wrote:
Even if you can cd to the directories as root does not mean that you can
On 12/20/07, shlomo solomon [EMAIL PROTECTED] wrote:
On Dec 20, 2007 11:01 PM, Alon Altman [EMAIL PROTECTED] wrote:
Even if you can cd to the directories as root does not mean that you can
read/write there as user. Please supply the output of ls -la /home (as
root).
Alon
At the
On 20/12/2007, Shlomi Fish [EMAIL PROTECTED] wrote:
Hi all!
Well, this is also a way to make sites compatible with Firefox and other
Mozilla-based browsers. :-)
If you are job hunting and want to use http://www.yjobs.co.il/ and would
prefer to use Firefox, then look no further than:
And my word to this never ending story:
You may use get_cycles
(http://lxr.linux.no/linux/include/asm-i386/tsc.h#L19) to measure time
(cycles) in interrupts.
Read more here: http://www.linuxdriver.co.il/ldd3/linuxdrive3-CHP-7-SECT-1.html
--
Constantine Shulyupin
Freelance Embedded Linux
On Dec 20, 2007 11:36 PM, Alon Altman [EMAIL PROTECTED] wrote:
Another reason kde could fail to write is lack of disk space. Is /home full
or close to full?
No - over 20 Gb free on /home.
BTW - itś not a KDE problem. I can login from a console (Ctl-Alt-1) either.
On Dec 20, 2007 11:50 PM, shlomo solomon [EMAIL PROTECTED] wrote:
On Dec 20, 2007 11:36 PM, Alon Altman [EMAIL PROTECTED] wrote:
Another reason kde could fail to write is lack of disk space. Is /home full
or close to full?
No - over 20 Gb free on /home.
BTW - itś not a KDE problem. I can
When checking for free disk space, check also inodes (by df -i).
According to past experience, when a partition runs out of inodes,
sometimes the system manages to continue to work and erratically fail
(when processes need to create new files without deleting others
beforehand).
Another shot in
When I boot, I see hundreds of messages flying off the screen faster
than I can read them - some of them error messages. Alot, BUT NOT ALL,
of the messages can be seen with dmesg, but there are many messages
that I can´t see there or in the logs (unless, of course there are
additional logs I
19 matches
Mail list logo
