Mailinglist Archive: opensuse-amd64 (274 mails)

[Darrell Shively <sused@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Santiago:

You don't have a lot of info to work with there, do you?
May I ask: did anything else change other than that scsi cable?  
Anything at all?

If not then there is one easy thing you can try: replace that new cable.  
Unlike you, I *have* had cables fail.  (I know it's weird - one would expect 
a working cable to keep working.  Still, it happens.)

If that doesn't help, then start looking at things in the path of the cable 
that could have been bumped when it was replaced.  (BTW: The cable might not 
even be related.  If some component was on the verge of failing then just 
power cycling the system may have finished it.)

If none of the above helps then listen to the better ideas someone else on 
this list will certainly have.  :-)

As a last resort use the divide-and-conquer strategy.  Start eliminating 
parts from the system until it becomes reliable.  Don't overlook the power 
supply - P/S line noise has brought more than one system to its knees.

Oh, one last thing: testing your RAM might not be a bad idea.

   Good luck dude!
	- Darrell


On Thursday 08 April 2004 12:33, Santiago Flores wrote:
> Hello all. I've been enjoying the opteron board preference discussion!
> Thanks.
>
> On to buisness -
> We had a SCSI cable fail (1st time I've ever had the cable fail) and we
> had to take down the machine to swap the cable. Now when I bring the
> machine up, it comes up fine. Just like normal. However, after an
> indeterminate amount of time it hangs. Not a hard hang though. I can
> type in any shells I have open, so long as I don't do anything
> interactive. As soon as I tab or press 'enter' then that shell is hosed
> too. I cannot open any new ones. The only info I am getting is this from
> /var/log/messages:
>
> just before hang
> Apr  8 11:11:51 linux sshd[1533]: error: fork: Cannot allocate memory
>
> interesting(?)
> Apr  8 11:25:18 linux kernel: Error seeking in /dev/kmem
> Apr  8 11:25:18 linux kernel: Error adding kernel module table entry.
>
>
> just before hang
> Apr  8 12:11:18 linux sshd[1533]: error: fork: Cannot allocate memory
> Apr  8 12:11:19 linux kernel: Unable to handle kernel paging request at
> virtual address 0000007f804540e0
> Apr  8 12:11:19 linux kernel:  printing rip:
> Apr  8 12:11:19 linux kernel: ffffffff80149627
> Apr  8 12:11:19 linux kernel: PML4 107bcc067 PGD 107bd4067 PMD 0
>
> Any ideas? I just rebooted with apic=no to try that and see if I can get
> it to hang.
>
> TIA,
>
> Santiago

- -- 
sused@xxxxxxxxx      "Perfect! ....what am I doing?"
                      -- Washu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFAdfQveo6c0kw6mZ0RAq8jAJ0f7/mCV99ljIMDiYgFWaYKvrk+lQCgzfnF
c2TGh/q9ELc1IMOoLwPK1+c=
=x5Zm
-----END PGP SIGNATURE-----