(In reply to comment #0)
> Description of problem:
> Computer doesn't start any more after BIOS-Upgrade to BIOS-Version 07HL on
> Samsung NP-900X3A Ultrabook.
> 
> Version-Release number of selected component (if applicable):
> 3.2.9-2.fc16.x86_64
> 
> How reproducible:
> Upgrade BIOS. Boot.
> 
> Actual results:
> Computer doesn't start up unless kernel parameter "acpi=off" is set.
> 
> Expected results:
> Computer starts with ACPI support.
> 
> Additional info (kernel boot parameter):
> linux   /vmlinuz-3.2.9-2.fc16.x86_64
> root=UUID=3da94559-874b-4ee9-9863-f5d37365338e ro rd.md=0 rd.lvm=0 rd.dm=0
> quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=de_DE.UTF-8 
> KEYTABLE=sg-latin1 elevator=deadline i915.i915_enable_rc6=1
> i915.i915_enable_fbc=1 i915.lvds_downclock=1
> 
> 
> Boot Log:
> 
> [    0.306842] Disabled fast string operations
> [    0.326928] NMI watchdog enabled, takes one hw-pmu counter.
> [    0.327694]  #3
> [    0.398764] Disabled fast string operations
> [    0.418882] NMI watchdog enabled, takes one hw-pmu counter.
> [    0.419082] Brought up 4 CPUs
> [    0.419162] Total of 4 processors activated (12769.03 BogoMIPS).
> [    0.423899] devtmpfs: initialized
> [    0.424134] PM: Registering ACPI NVS region at aaeef000 (720896 bytes)
> [    0.425154] atomic64 test passed for x86-64 platform with CX8 and with SSE
> [    0.425332] RTC time: 18:35:12, date: 03/15/12
> [    0.425448] NET: Registered protocol family 16
> [    0.425695] ACPI: bus type pci registered
> [    0.425868] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem
> 0xf8000000-0xfbffffff] (base 0xf8000000)
> [    0.425991] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff) reserved in E820
> [    0.440218] PCI: Using configuration type 1 for base access
> [    0.441302] bio: create slab <bio-0> at 0
> [    0.441450] ACPI: Added _OSI(Module Device)
> [    0.441540] ACPI: Added _OSI(Processor Device)
> [    0.441621] ACPI: Added _OSI(3.0 _SCP Extensions)
> [    0.441703] ACPI: Added _OSI(Processor Aggregator Device)
> [    0.445099] ACPI: Executed 1 blocks of module-level executable AML code
> [    0.452708] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

This is the last line you see when booting without acpi=off?  Normally that _OSI(Linux) query message is meaningless.  I'm not sure why we print it out at all to be honest, but it's normally not a fatal condition.

Can you attach the output of 'acpidump'?

Yes, this is the last line. I didn't switch the computer off for about 20min, but this was the very last line to be printed out.

I attached the acpidump output - but that's of course while booted with acpi=off; does that matter?

Created attachment 570445 [details]
acpidump output

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

The problem still occurs and the output is also still the same as before.

Problem still occurs after upgrading to Fedora 17 Beta, Kernel 3.3.4-4.fc17.x86_64

When booting from a Ubuntu 12.04 usb live-image; the problem does not occur.

I compared the acpidump output from the previously attached acpidump (above) with the one acpidump printed out in Ubuntu, and the only difference appears on one of the very last lines;

RSD PTR @ 0xaaffe014 (Ubuntu)
instead of
RSD PTR @ 0xf00e0 (Fedora).

I also noticed that the IASL prints out some warnings on this DSDT table;
might fixing these help solving the problem?

can you boot (don't disable acpi) with initcall_debug as a boot parameter, and note the last line that gets printed.

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.