|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST Hardware Information Module crash | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Forgotten User QtBI7gWTIh <forgotten_QtBI7gWTIh> |
| Component: | YaST2 | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_QtBI7gWTIh, mschauler, snwint |
| Version: | Milestone 7 | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
The YasT2 Logs
the mdt trace Log I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 3 I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 4 I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 5 I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 6 Console log from yast2 |
||
Please attach y2logs.If you're in doubt follow:http://en.opensuse.org/Bugs/YaST Thanks. The YaST2 Logs are attach ? I mean the Problem is in hwinfo --framebuffer. I have also a problem to create a initrd ? Well, if yast really crashes, I don't see why this would be related to hwinfo hanging. I can look into the hwinfo thing but if there's a yast issue as well you'd probably have to open a separate bug for it. Does hwinfo hang indefinitely? Please go to software.opensuse.org and install the 'mdt' package. Does 'mdt --modes' also hang? The only difference between M7 and RC1 I can think of is bug 590242. Does MALLOC_PERTURB_=0 vs. MALLOC_PERTURB_=1 make a difference? I can't found on factory or on software.opensuse.org the 'mdt' package ? Can you tell me the place to download ? I have found now the 'mdt' on your repository but mdt hang also the output is after 3 min ? techz:/home/gjn # mdt --modes version = 3.0, oem version = 12.19 memory = 16384k oem name [0xc01f0] = "ATI ATOMBIOS" vendor name [0xc0128] = "(C) 1988-2005, ATI Technologies Inc. " product name [0xc00b7] = "JUNIPER" product revision [0xc4d8a] = "01.00" 53 video modes: Ok, what about, e.g. 'mdt --mode 0x101'? It should return after some seconds. With 'mdt --mode 0x101 --show trace,dump >log' it writes a full instruction trace. As that file is probably quite large, can you attach at least the last, say, 100000 lines? the output from 'mdt --mode 0x101' 0x0101[bb]: 640x480+640, 8 bpp, max. 400 MHz, fb: 0xe0000000, a0000.7: 64k Ok I attache a looooong output I hope this is correct but my disk is full ;) Created attachment 371844 [details]
the mdt trace Log
I hope this is correct, but the first Log was 15 GB ??? I hope I remember correct on my system M6 was the first 11.3 that I can install, all other have the Problem with hwinfo? Update to M7 have small Problems with 'mkinitrd' (/boot/grub/menu.lst) Update to RC1, it is not possible to run mkinitrd (hwinfo) I tested this again with 11.2, 'hwinfo --framebuffer' is starting and ending correct? Steffen in comment#8 is attached requested info. Could you check it please? Question: can this Problem also break a new installaion ? On my system Intel DX58SO with a Raid1 (intel) the system hang by searching for linix Partition, or is this a ather Problem ? On this system are no Linux Partitions, a fresh installed Win7 64 Bit is installed, all other are clean? I kmow the Problem with the second SATA Chip (marvel ESATA) on this Board ? I have to disable this chip in the Bios. Hm, the log (comment 8) says the call completed in 3ms. So, does it mean it sometimes works and sometimes not? All i can say the first run of the command I have a full disk ~15GB the next run after 15 Sec I stop this run. I have now installed a fresh RC2 on my system, the installation is running correct, but afterward it isnot possibleeee to run 'mkinitrd' also it is not possible to run YaST2 Hardware Information it blocks by the framebuffer?, and I can't stop YaST2, I have to do a killall YaST2. OK I can install it but afterward it is not possible to update a kernel or... I create a new log and attache it, I hope this is uploaded? It is probably your BIOS running in an endless loop. I don't know why, so I need to look at a non-working log (at least the end of it). The log you sent shows no problems at all and the call was completed in 3ms. To get yast/mkinitrd going you can always turn off the code with hwprobe=-bios.vesa either at the boot prompt or as shell environment setting. Created attachment 373494 [details]
I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace
File 1
Created attachment 373495 [details]
I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace
File 2
Created attachment 373499 [details]
I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 3
Created attachment 373503 [details]
I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 4
Created attachment 373505 [details]
I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 5
Created attachment 373507 [details]
I split this file mdt_log.txt.bz2 in 6 Files, 7 Sec Trace File 6
Thanks! I'll look into it. Hm, the log is a bit of a mystery. How exactly did you create it? Did you abort the run somehow? Does it always that the same time? Is there a difference running it on the linux console? Yes after hang on framebuffer divice i abort yast. I can send a yast Log from console, also hang on framebuffrer device? The same problem on console and in KDE. on console I have to do a killall yast to end yast :(. Created attachment 374618 [details]
Console log from yast2
In the moment I have installed all packages from repository:base note you can always use the workaround from comment 15 (In reply to comment #28) > note you can always use the workaround from comment 15 same problem exists with 11.3 final (64bit). Adding workaround #15 to the kernel command line helps. But why all of the Problem's is not in a 11.2 or SLES 11 SP1 !!! on my site it is not possible to run a 11.3 (kernel Probs ...) only on a very old system 11.3 is running??? I mean the greatest problem is the testing (VMware) and NOT on a real Computer!!! I looked at it again and I've still no idea. Sorry, I have to leave this unsolved. |
Created attachment 369802 [details] The YasT2 Logs User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.3 (like Gecko) SUSE Hello, I install (update) from M7 to RC1. When I like to start the YaST2 Module Hardware Information YaST2 crash ? By checking the Framebuffer this is the end of life ;). I have a ATI 5770 PCIe Card. Reproducible: Always Steps to Reproduce: 1.Start YaST2 2.Star Hardware Information 3. Actual Results: Crash