Bug 3676 - Rebooting or halting system fails on an iMac
Summary: Rebooting or halting system fails on an iMac
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard: MGA2TOO MGA1TOO
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2011-12-09 14:07 CET by Olivier RONCALI Olivier
Modified: 2015-04-18 20:51 CEST (History)
2 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments
File "/var/log/messages" filtered (begins when I reboot and ends when the system has restarted) (72.79 KB, text/plain)
2012-01-31 14:32 CET, Olivier RONCALI Olivier
Details
File "dmesg" of Mageia 2 beta 3 (live CD KDE = x86_64) (68.46 KB, application/octet-stream)
2012-04-23 13:01 CEST, Olivier RONCALI Olivier
Details

Description Olivier RONCALI Olivier 2011-12-09 14:07:40 CET
Configuration : 
    iMac 10,1 (2010) - 21,5"
    INTEL Core 2 Duo 3,33 GHz

    Mageia 1 (32 bits)
    Kernel 2.6.38.8-desktop586-8



When I stop or reboot my computer, the system freeze near the end of the process.

For exazmple, if I try to reboot, the process runs without problem until it says "Please stand by while rebooting the system..." and "Rebooting system.". After that, the system freeze and I have to force the extinction by pressing the button a long time.
Comment 1 Manuel Hiebel 2011-12-09 19:03:28 CET
thomas any ideas ?

personally I don't really know :S

CC: (none) => tmb
Source RPM: (none) => kernel ?

Comment 2 Olivier RONCALI Olivier 2011-12-14 17:35:30 CET
The problem is still here in the Mageia 2 alpha 1. Tested with the live CD KDE 32 bits.
Comment 3 Marja Van Waes 2012-01-30 20:58:36 CET
(In reply to comment #2)
> The problem is still here in the Mageia 2 alpha 1. Tested with the live CD KDE
> 32 bits.

You mean with a liveCD KDE, without installing it?

When you reported this problem on the 9th of december, was that with Mageia installed? If so, how did you install it?

If you still have the problem with a Mageia install, could you please attach the part of /var/log/messages from when you decide to reboot till when the system is frozen?

CC: (none) => marja11

Comment 4 Olivier RONCALI Olivier 2012-01-31 14:32:09 CET
Created attachment 1473 [details]
File "/var/log/messages" filtered (begins when I reboot and ends when the system has restarted)
Comment 5 Olivier RONCALI Olivier 2012-01-31 14:35:39 CET
When I first show this problem, I used a Mandriva 2010 updated to Mageia 1. Since that, I reinstalled a mageia 1 from scratch. The problem remains.

I tried with Mageia 2 (alpha 1) 32 bits, with the live CD KDE, withput installing it. Same thing.
Olivier RONCALI Olivier 2012-01-31 14:36:00 CET

Attachment 1473 description: File "/var/log/messages" filtered (begons when I reboot and ends when the system has restarted) => File "/var/log/messages" filtered (begins when I reboot and ends when the system has restarted)

Marja Van Waes 2012-01-31 17:47:20 CET

Attachment 1473 mime type: application/octet-stream => text/plain

Comment 6 Marja Van Waes 2012-01-31 17:59:07 CET
@ Olivier

Thanks for the feedback

@ Thomas

Assigning to you, because I think this is a kernel issue. Please assign back to bugsquad and explain if I'm wrong

Assignee: bugsquad => tmb
Source RPM: kernel ? => kernel

Comment 7 Olivier RONCALI Olivier 2012-04-20 14:39:33 CEST
The problem is still here in the Mageia 2 beta 3. Tested with the live CD KDE
64 bits.
Comment 8 Thomas Backlund 2012-04-20 19:39:35 CEST
Can you attach /var/log/dmesg fron system running Mageia 2 beta 3 ?
Marja Van Waes 2012-04-20 21:10:20 CEST

Keywords: (none) => NEEDINFO

Comment 9 Olivier RONCALI Olivier 2012-04-23 13:01:30 CEST
Created attachment 2076 [details]
File "dmesg" of Mageia 2 beta 3 (live CD KDE = x86_64)
Marja Van Waes 2012-05-09 15:09:51 CEST

Keywords: NEEDINFO => (none)

Comment 10 Marja Van Waes 2012-07-06 15:03:47 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 11 Olivier RONCALI Olivier 2012-07-07 19:45:14 CEST
This problem exists since Mageia 1 and is also present on most popular distributions that use a kernel 3.x (I have not made any test on previous versions).

So the problem does not seem specific to Mageia but rather come from the kernel itself.
Comment 12 Marja Van Waes 2012-07-07 20:24:18 CEST
(In reply to comment #11)
> This problem exists since Mageia 1 and is also present on most popular
> distributions that use a kernel 3.x (I have not made any test on previous
> versions).
> 
> So the problem does not seem specific to Mageia but rather come from the kernel
> itself.

anyone who knows a link to an upstream bug report: please give it

Keywords: (none) => UPSTREAM
Version: 1 => Cauldron
Whiteboard: (none) => MGA2TOO MGA1TOO

Comment 13 Marja Van Waes 2015-04-18 20:51:46 CEST
Sorry, but this bug saw no action since over 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

Status: NEW => RESOLVED
Resolution: (none) => OLD


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