[S.u.S.E. Linux] Yast freezes
Hi all, Whenever I start yast (Suse 5.2), the computer starts to load the program and then the window freezes. Then I get the following processes (among others): 3168 p2 S 0:00 yast 3173 p2 S 0:00 /bin/sh -c fdisk -l >/tmp/stp3168_1_S 2>/tmp/stp3168_1_E 3174 p2 D 0:00 fdisk -l I can kill the first two. But the last one won't die! How can I kill the fdisk process (or anything else with status "D" for that matter)? I had heard of similar problems with fdisk when a removable disk was mounted or inserted. But the freeze in my case occures even without any removables. Is there a fix to this bug? Thanks Ramin - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
"RS" == Ramin Sina <sina@glue.umd.edu> writes:
RS> Hi all, RS> Whenever I start yast (Suse 5.2), the computer starts to load the RS> program and then the window freezes. Then I get the following processes RS> (among others): RS> 3168 p2 S 0:00 yast RS> 3173 p2 S 0:00 /bin/sh -c fdisk -l >/tmp/stp3168_1_S 2> /tmp/stp3168_1_E RS> 3174 p2 D 0:00 fdisk -l RS> I can kill the first two. But the last one won't die! How can I kill the RS> fdisk process (or anything else with status "D" for that matter)? man ps: STAT Information about the status of the process. The first field is R for runnable, S for sleeping, D for uninterruptible sleep, It means what it says. [...] RS> I had heard of similar problems with fdisk when a removable disk was RS> mounted or inserted. But the freeze in my case occures even without any RS> removables. RS> Is there a fix to this bug? Wait a moment! /bin/sh -c fdisk -l >/tmp/stp3168_1_S 2> /tmp/stp3168_1_E Did you ever have a look at these files: /tmp/stp3168_1_S /tmp/stp3168_1_E They might give you interesting information, that's why fdisk's stdout and stderr get redirected to those files. But instead of looking at them now, try to run `fdisk -l' yourself on the command line. And I almost forgot this: you mentioned a removable disk, so try to do your test in a situation identical to when your yast crash happened. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
/bin/sh -c fdisk -l >/tmp/stp3168_1_S 2> /tmp/stp3168_1_E
Did you ever have a look at these files:
/tmp/stp3168_1_S /tmp/stp3168_1_E
They might give you interesting information, that's why fdisk's stdout and stderr get redirected to those files.
-
Thanks for yor response. The error output states that: The number of cylinders for this disk is set to 16383. This is larger than 1024, and may cause problems with: 1) software that runs at boot time (e.g.m LILO) 2) booting and partitioning software from other OSs (e.g.), DOS FDISK, OS/2 FDISK) But I have no problems with LILO and the fdisk I use is within linux.
But instead of looking at them now, try to run `fdisk -l' yourself on the command line.
And I almost forgot this: you mentioned a removable disk, so try to do your test in a situation identical to when your yast crash happened.
fdisk -l spits out the output and then hangs again (Uninterruptable Sleep). The last few times these happened was when I had no removable drives at all. Ramin - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Thu, 13 Aug 1998, Ramin Sina wrote:
/bin/sh -c fdisk -l >/tmp/stp3168_1_S 2> /tmp/stp3168_1_E
Did you ever have a look at these files:
/tmp/stp3168_1_S /tmp/stp3168_1_E
They might give you interesting information, that's why fdisk's stdout and stderr get redirected to those files.
-
Thanks for yor response. The error output states that:
The number of cylinders for this disk is set to 16383. This is larger than 1024, and may cause problems with: 1) software that runs at boot time (e.g.m LILO) 2) booting and partitioning software from other OSs (e.g.), DOS FDISK, OS/2 FDISK)
But I have no problems with LILO and the fdisk I use is within linux.
It's just a warning. What you see is just the start of fdisk's output. After that I assume it hits some CD-ROM drive and hangs.
But instead of looking at them now, try to run `fdisk -l' yourself on the command line.
And I almost forgot this: you mentioned a removable disk, so try to do your test in a situation identical to when your yast crash happened.
fdisk -l spits out the output and then hangs again (Uninterruptable Sleep). The last few times these happened was when I had no removable drives at all.
But you do have an EIDE CDROM drive, do you? Please check if the behaviour is different depending on if there is a disk in the drive or not.
Ramin -o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
fdisk -l spits out the output and then hangs again (Uninterruptable Sleep). The last few times these happened was when I had no removable drives at all.
But you do have an EIDE CDROM drive, do you? Please check if the behaviour is different depending on if there is a disk in the drive or not.
Ramin -o) Hubert /\\ _\_v
Hi Hubert, thanks for your reply. It doesn't matter if there is a CD (mounted or not) in my Toshiba IDE CD-ROM. YAST still freezes with an un-interrupatable fdisk -l. Ramin - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Wed, 12 Aug 1998, Ramin Sina wrote:
Whenever I start yast (Suse 5.2), the computer starts to load the program and then the window freezes. Then I get the following processes (among others):
3168 p2 S 0:00 yast 3173 p2 S 0:00 /bin/sh -c fdisk -l >/tmp/stp3168_1_S 2>/tmp/stp3168_1_E 3174 p2 D 0:00 fdisk -l
I can kill the first two. But the last one won't die! How can I kill the fdisk process (or anything else with status "D" for that matter)?
Unfortunately, not at all ;-(
I had heard of similar problems with fdisk when a removable disk was mounted or inserted. But the freeze in my case occures even without any removables. Is there a fix to this bug?
I think not. fdisk just hangs on some EIDE CD-ROM drives. Try if the behaviour changes when there is a disk in the drive. The only "workaround" is to let YaST only call "fdisk" when it is really needed (I'm not quite sure whether Thomas already changed this).
Thanks Ramin -o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
Jochen_Hayek＠ACM.org -
mantel＠suse.de -
sina＠Glue.umd.edu -
sina＠glue.umd.edu