45748 – vmware-workstation-4.0.5.6030-r1 crash after kernel upgrade

Bug 45748 - vmware-workstation-4.0.5.6030-r1 crash after kernel upgrade

Summary: vmware-workstation-4.0.5.6030-r1 crash after kernel upgrade

Status:	RESOLVED NEEDINFO

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Chris Gianelloni (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-03-25 16:02 UTC by erik poupaert
Modified:	2004-04-28 18:46 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description erik poupaert 2004-03-25 16:02:51 UTC

The original situation, which I have restored, works fine:
bzImage-2.4.20-gentoo-r5-gcc3.2.3 CC=(no flags) CHOST="i686-pc-linux-gnu"
vmware complains about it though; because my current system compiler is gcc3.3.2. It even says that it *will* crash, but it doesn't.

The buggy situation, which crashes randomly, is the current kernel/current gcc, with a few optimization flags:
bzImage-2.4.22-gentoo-r7-gcc3.3.2 CC=="-march=pentium4 -mcpu=pentium4 -pipe -O2 -fomit-frame-pointer -frename-registers -fforce-addr" CHOST="i686-pc-linux-gnu"

So, I'm now forced to use an old, ugly and unoptimized kernel in order to keep M$Windows running. What can I do to upgrade the kernel anyway, without crashing vmware?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Chris Gianelloni (RETIRED) gentoo-dev

2004-03-29 10:27:46 UTC

Have you tried the newest VMWare version in portage?

Comment 2 Chris Gianelloni (RETIRED) gentoo-dev

2004-04-28 18:46:50 UTC

1 month + no response == resolved-needinfo