|
Bugzilla – Full Text Bug Listing |
| Summary: | Update crashes when including Add-on media (not enough free memory) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Patrick TenHoopen <ptenhoopen> |
| Component: | Update Problems | Assignee: | Lukas Ocilka <locilka> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2logs | ||
|
Description
Patrick TenHoopen
2006-11-28 03:53:58 UTC
Can you please attach y2logs. If you are in doubt please follow http://en.opensuse.org/Bugs/YaST. Thanks! Created attachment 107327 [details]
y2logs
Here are the y2logs. I hope they include the needed information. They are from my system after the successful update that I was able to do by not selecting to include the Add-on media. I tried to grab fresh ones by running another update but the system hung-up after it reads the Add-on CD and I couldn't press Shift-F8 to save them nor could I get to a shell prompt.
I'm sorry but if you are reporting an error you should obviously add YaST logs from situation when YaST is buggy. You have attached a non-erroneous logs. That's why I cannot tell what was the problem. Of course, there are some other possibilities to catch the problem... YaST Remote Logging in Installation -> log the installation process to the remote NFS server. http://en.opensuse.org/YaST_Remote_Logging_in_Installation If you encounter the "Error with installation", try to switch to the console by pressing Ctrl+Alt+F2 immediately. If it didn't work, you cold try another thing. Press Ctrl+Alt+Shift+x _before_ you select to add an Add-On product. This will open an xterm. So now, you have an installation process and xterm. Use Alt+Tab to switch between them. If it hangs, you might try to do something in that xterm. You could also start 'top' in that xterm and see what happens. Anyway, I think that the problem is something else then error in using add-on product. You just have less than recommended amount of RAM which is at least 256 MB :( Please, try this: http://en.opensuse.org/Installation_with_Little_Memory This could also help you: http://en.opensuse.org/Linuxrc parameter 'AddSwap' (to use a swap partition during update) I've checked your startup log and it says: MemFree="175696" This is about 171 MB and, to be honest, I wonder how it was possible to finish the update :) Of course, Add-On always takes some other memory (because it initializes another installation source). We are permanently working on lowering the memory requirements. Actually your computer is the proof that an update can work on computer with about 77% of recommended RAM size :) And that's a great success. Closing as enhancement-later. Maybe a check for free memory can be implemented. For instance before user tries to use an add-on media and maybe on other places. The solution would be also to turn the swap-on just after "update" method is selected. mass reopening all 10.2 LATER+REMIND bugs. close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it. |