On Fri, Apr 11, 2008 at 04:37:12PM +0200, Bernhard Walle wrote:

Hi YaST hackers,

I observe a kernel bug that happens only in YaST partitioning code. Probably the partitioner does some "weird" thing (load modules, etc.) that triggers the bug.

How to debug this? Is it possible to trigger the same hardware detection code in a running system?

'yast2 disk' in the running system does mainly the same detection but loading of modules and activating of lvm, md etc. likely happened already.

Or do I need to rebuild the kernel (easy) and the installation initrd (because of modules)?

Any suggestions appreciated.

With YaST logs I might say what yast2-storage was doing. Might be difficult to get if the kernel crashed but IIRC y2logs can be redirected to syslog and thus to network. ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org