Bug 35857 - reboot into Windows ME results in ME halting immediately
Summary: reboot into Windows ME results in ME halting immediately
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-04-13 04:48 UTC by James Manning
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-04-13 04:48:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description James Manning 2001-04-13 04:48:48 UTC
laptop that did an up2date off of ftp.beta up2date servers to 7.1

only entries in lilo.conf are linux for 2.4.2-2 and winME other=/dev/hda1

if I init 6 and select ME from lilo graphical screen, it starts booting, I 
see the splash screen, and it immediately halts and powers down.  if a 
power cycle is involved, there's no problem.

This would seem to be something about the state the Linux kernel leaves 
some of the devices (maybe the PCMCIA controller? not sure) matching 
winME's check for "in shutdown state".

Yes, this is arguably a bug in Windows ME, and I'm usually the last person 
to want to request a kernel change (or any change for that matter) based 
on existing Microsoft behavior, but...

If there's any chance whatsoever that this could get changed so that those 
of us forced to dual boot wouldn't have to remember to power cycling when 
booting back to Microsoft, it'd be a great help for the usability of 7.1 
in multi-boot environments.

This bug report makes me feel dirty.

Comment 1 Arjan van de Ven 2001-04-13 19:06:48 UTC
This is 100% sure a ME bug....
It's humorous though, as the common case is that Windows does things to hardware
that Linux has trouble recovering :)

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