[Bug 436895] New: Samsung R510 boot only Acpi=off
https://bugzilla.novell.com/show_bug.cgi?id=436895 Summary: Samsung R510 boot only Acpi=off Product: openSUSE 11.0 Version: Final Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Blocker Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: rossif8@gmail.com QAContact: jsrain@novell.com Found By: Community User I have installed Opensuse 11.0 x86_64 on Samsung R510. It boot normally only if acpi=off. My configuration is : Intel Core 2 Duo P7350 Chipset Intel PM45 + ICH9M Ram 4Gb Sk Video nVIDIA GeForce Go 9200M GS Hd 320 GB (5400 rpm S-ATA) Without acpi=off, the boot sequence rerun from the Bios welcome screen continuously. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c1
--- Comment #1 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
Jiri Srain
https://bugzilla.novell.com/show_bug.cgi?id=436895
User aorlovskyy@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c2
Alexander Orlovskyy
https://bugzilla.novell.com/show_bug.cgi?id=436895
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=436895
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c3
--- Comment #3 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c4
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c5
--- Comment #5 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c6
--- Comment #6 from Thomas Renninger
Without acpi=off, the boot sequence rerun from the Bios welcome screen continuously. With this info and the boot log from above, is this correct: Everything boots fine until runlevel X is reached and while booting the machine starts to shutdown again, I mean: starts to reboot?
If you pass 1 as a boot parameter, does it work (prompt for login instead of shutting down/rebooting?). If not, does it work with init=/bin/bash boot param? If yes, can you switch to runlevel 2,3 and 5 then (init 2... init 3...)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c7
--- Comment #7 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c8
--- Comment #8 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c9
--- Comment #9 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c10
--- Comment #10 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c11
--- Comment #11 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c12
--- Comment #12 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c13
--- Comment #13 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c14
Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c15
--- Comment #15 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c16
--- Comment #16 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c17
--- Comment #17 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c18
--- Comment #18 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c19
--- Comment #19 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c20
--- Comment #20 from Thomas Renninger
I boot without acpi parameter for activate acpi. Yep. You can boot an x86_64 kernel on a i386 installed system (not the other way around).
How to install x86_64 kernel on an i386 installation ==================================================== Best you take the -default and -default-base kernels from here: ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64 This is the latest kernel and if we find it you can get a fixed kernel from there before a update kernel is published. Download them and additionally install the kernel like this: rpm -ivh --ignorearch /mounts/dist/kerneltest/HEAD/x86_64/kernel-default{-base,}.rpm I separately post how you might be able to boot it without the reboot issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c21
--- Comment #21 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c22
--- Comment #22 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c23
--- Comment #23 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c24
--- Comment #24 from Thomas Renninger
From above I'd say pci=noacpi does not affect the reboot problem, so it's unrelated?
Then, I booted with 1 acpi_debug_level=0x1f pci=noacpi This worked, but I could not insert the modules, because it rebooted. What means it worked? If it rebooted it did not work and it is the same as with booting without pci=noacpi?!?
I installed the current kernel and booted with 1 acpi_debug_level=0x1f Booting was only possible for runlevel "s", else the reboot problem was there. That's great. Now we can debug a bit there... Did this only work with processor, fan and thermal blacklisted? I very much expect that a kernel driver is causing the reboot. If processor, fan and thermal had been blacklisted, I'd try to load them manually. The first task now is to find out which driver/module causes the reboot.
There is no output in /tmp/dmesg If it's too early for dmesg you could try to do: cat /proc/kmsg >/tmp/kmsg
Hmm, maybe this is related to something else. If pci=noacpi changes the reboot behaviour it could be related to something else. Can you separately try to boot (without additional boot params, only these): pcie_aspm=off noaer the command will block and /proc/kmsg will be empty afterwards, but that should not matter. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c25
--- Comment #25 from Tobias Lippert
Why do you need pci=noacpi? If I do not use pci=noacpi, the machine reboots during the boot procedure. I have it from a ACPI faq page.
Then, I booted with 1 acpi_debug_level=0x1f pci=noacpi This worked, but I could not insert the modules, because it rebooted. What means it worked? If it rebooted it did not work and it is the same as with booting without pci=noacpi?!? I can only get to a shell if I use that parameter. Else the system reboots during initialization.
I installed the current kernel and booted with 1 acpi_debug_level=0x1f Booting was only possible for runlevel "s", else the reboot problem was there. That's great. Now we can debug a bit there... Did this only work with processor, fan and thermal blacklisted? I very much expect that a kernel driver is causing the reboot. If processor, fan and thermal had been blacklisted, I'd try to load them manually. The first task now is to find out which driver/module causes the reboot. If I modprobe these modules, the system reboots. I cannot get any dmesg output with modprobe fan; modprobe processor; modprobe thermal; dmesg >/tmp/dmesg
Hmm, maybe this is related to something else. If pci=noacpi changes the reboot behaviour it could be related to something else. Can you separately try to boot (without additional boot params, only these): pcie_aspm=off noaer
There is no output in /tmp/dmesg If it's too early for dmesg you could try to do: cat /proc/kmsg >/tmp/kmsg the command will block and /proc/kmsg will be empty afterwards, but that should not matter.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c26
--- Comment #26 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c27
--- Comment #27 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c28
--- Comment #28 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c29
--- Comment #29 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c30
--- Comment #30 from Tobias Lippert
The boot parameter should make the machine fully work without any further problems. Oh, I am sorry I was not clear enough in my last post. I can get to bootlevel s. If I want to go to 3 or 5, the system reboots. (I will try 1 in a second)
I videotaped it and the last line of the boot process before rebooting is: ACPI: Processor [CPU1] (supports 8 throttling states) I do not know what part of the initialization follows, but that seems to cause the reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c31
--- Comment #31 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c32
--- Comment #32 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c33
--- Comment #33 from Tobias Lippert
Does the machine immediately (hard) reboot or is the ordinary, software controlled reboot process happening (runlevel services are stopped, etc.)? No, the computer does a hard reboot
So: acpi_root_table=rsdt does not help at all? It helps. Without the option I cannot get to runlevel s.
If it is a hard reboot, maybe C2 is causing this. Then processor.max_cstate=1 or idle=poll boot params may help?
No, this did not help. I get till runlevel s. If I type init 1 the system reboots
If the machine ordinary shuts down (services are stopped, etc.), then it's probably the thermal module causing this by a wrongly read temperature (OS things a critical temperature is reached and shuts down the machine).
dmesg shows a temperature of 48 degrees. So this does not seem to be the problem. I compared the dmesg output with that of the 32bit livecd which works. After the ACPI, the sound is initialized, perhaps this causes problems? After all, I can modprobe acpi without problems... this follows the acpi init in 32-bit livecd. HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 HDA Intel 0000:00:1b.0: setting latency timer to 64 hda_codec: Unknown model for ALC262, trying auto-probe from BIOS... I'll send you a full dmesg later. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User rossif8@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c34
--- Comment #34 from franco rossi
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c35
--- Comment #35 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c36
--- Comment #36 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c37
--- Comment #37 from Tobias Lippert
I have some trouble with acpi. Without special boot parameters, Intrepid will not boot. With acpi=off it boots. I also found that it boots with ACPI using the flag "mem=4096M" (don't understand why, but it works...). But when I use this flag, the OS recognizes only 3 GB of my 4 GB RAM:
I can confirmt this. with mem=4096MB I am able to boot and ACPI works. (unplugging my power cord caused a hard reboot before, now kde recognizes this) My machine shows only 3GB RAM too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c38
--- Comment #38 from Tobias Lippert
From dmesg:
https://bugzilla.novell.com/show_bug.cgi?id=436895
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c39
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436895
User herrmarder@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c40
--- Comment #40 from Tobias Lippert
https://bugzilla.novell.com/show_bug.cgi?id=436895
User gregkh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c41
--- Comment #41 from Greg Kroah-Hartman
participants (1)
-
bugzilla_noreply@novell.com