Opened 10 years ago

Closed 10 years ago

#5859 closed bug (fixed)

"shutdown -q" fails in terminal

Reported by: Disreali Owned by: nobody
Priority: normal Milestone: R1
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Running hrev36434-Trunk on real hw.

Steps to reproduce: Open terminal and issue 'shutdown -q'. 'Shutdown failed!' is returned.

Expected behavior is that the system will shutdown.

Attachments (2)

haiku-r36434_shutdown-q_failed.png (90.3 KB ) - added by Disreali 10 years ago.
listdev_acer_am5620.txt (3.5 KB ) - added by Disreali 10 years ago.

Download all attachments as: .zip

Change History (9)

by Disreali, 10 years ago

comment:1 by anevilyak, 10 years ago

Any hardware specifics / syslog for that machine? shutdown -q behaves as expected here (instant power-off).

by Disreali, 10 years ago

Attachment: listdev_acer_am5620.txt added

comment:2 by axeld, 10 years ago

Generally, powering off can only work if APM or ACPI has been enabled - did you do that? It's not enabled by default in that revision yet (only after hrev36474).

in reply to:  2 ; comment:3 by Disreali, 10 years ago

Replying to axeld:

Generally, powering off can only work if APM or ACPI has been enabled - did you do that? It's not enabled by default in that revision yet (only after hrev36474).

One of the first things I do after any install is to enable ACPI. Though, I do not enable APM. Is that needed also?

I tried to upload my syslog, but it was to big. I don't know what I should be looking for in the syslog. If someone could give me an idea, I could then upload that section.

Also, I just found out that if I enter 'shutdown' without any switch, it will shutdown the system. This is not expected behavior. Entering 'shutdown' without a switch should print out the same as 'shutdown -h'.

comment:4 by Disreali, 10 years ago

Just installed hrev36511-alpha-rc and entering 'shutdown -q' in terminal freezes the system. System does not respond to keyboard or mouse input, and I have to do a hard reset.

Would you prefer I enter a new ticket for this?

in reply to:  3 comment:5 by bonefish, 10 years ago

Replying to Disreali:

Replying to axeld:

Generally, powering off can only work if APM or ACPI has been enabled - did you do that? It's not enabled by default in that revision yet (only after hrev36474).

One of the first things I do after any install is to enable ACPI. Though, I do not enable APM. Is that needed also?

No, enabling both is calling for trouble.

I tried to upload my syslog, but it was to big. I don't know what I should be looking for in the syslog. If someone could give me an idea, I could then upload that section.

Please note that the syslog can contain output of several sessions. One is fully sufficient. You can e.g. search for a line "Welcome to the Haiku boot loader!". The output for the session starts about 20 lines above that with a line "options = 0". Normally the output for a single session shouldn't hit the attachment size limit. If it still does, please zip it (gzip, bzip2, zip,...).

Also, I just found out that if I enter 'shutdown' without any switch, it will shutdown the system. This is not expected behavior. Entering 'shutdown' without a switch should print out the same as 'shutdown -h'.

The current behavior is definitely the expected one. All commands that don't need arguments should have a reasonable default behavior when invoked without any. And it is kind of obvious what the default behavior of the shutdown command would be.

Replying to Disreali:

Just installed hrev36511-alpha-rc and entering 'shutdown -q' in terminal freezes the system. System does not respond to keyboard or mouse input, and I have to do a hard reset.

Would you prefer I enter a new ticket for this?

Yes please. Also check whether you can still enter the kernel debugger (Alt-Sysreq-D).

comment:6 by Disreali, 10 years ago

This issue no longer occurs in hrev36635-trunk.

comment:7 by korli, 10 years ago

Resolution: fixed
Status: newclosed

Reopen if needed.

Note: See TracTickets for help on using tickets.