[Bug 223157] New: Kernel doesn't boot on Tyan Tiger K8SSA
https://bugzilla.novell.com/show_bug.cgi?id=223157 Summary: Kernel doesn't boot on Tyan Tiger K8SSA Product: openSUSE 10.2 Version: Beta 2 plus Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Blocker Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: hare@novell.com QAContact: qa@suse.de CC: stefan.fent@novell.com, aosthof@novell.com, bwalle@novell.com The Beta2+ kernel does not boot on my Tyan Tiger board. I get the nice pop-up 'loading linux kernel' during installation startup, but then the screen blanks and stays that way. Any hints on debugging this? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |ak@novell.com |maintainers@forge.provo.nove| |ll.com | ------- Comment #1 from hare@novell.com 2006-11-22 01:54 MST ------- SLES10 runs fine on this board. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #3 from hare@novell.com 2006-11-23 08:09 MST ------- FYI, the last messages printed are: TCP reno registered audit: initializing netlink socket (disabled) audit(1164294787.972:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) The next messages would be the PCI setup. Maybe something is going wrong here? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |hare@novell.com ------- Comment #4 from ak@novell.com 2006-11-23 08:10 MST ------- Can you boot with initcall_debug ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|hare@novell.com | ------- Comment #6 from hare@novell.com 2006-11-24 01:50 MST ------- Hmm. Doesn't really work. And according to initcall_debug we're indeed stuck in pci_init(). But please note that this is not a new error, AFAICR no 10.2 kernel ever booted on this beast. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #7 from hare@novell.com 2006-11-24 02:58 MST ------- Vanilla 2.6.17 doesn't boot, 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |hare@novell.com ------- Comment #8 from ak@novell.com 2006-11-24 03:01 MST ------- Can you try pci=nomsi and/or pci=nommconf ? Or alternatively git bisect between .16 and .17 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|hare@novell.com | ------- Comment #9 from hare@novell.com 2006-11-24 04:08 MST ------- pci=nomsi pci=nommconf doesn't make a difference. Starting bisect. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157
------- Comment #10 from hare@novell.com 2006-11-27 02:42 MST -------
bisect stops here:
commit 680cbbbb0e336b04b74be48b8ddd870537f1e226
Author: Dave Peterson
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #11 from hare@novell.com 2006-11-27 02:51 MST ------- But this was a false alarm. Compiling from git directly at this points boots. Oh well. Redo from start. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #12 from ak@novell.com 2006-11-27 03:32 MST ------- You can possibly avoid some work by restarting in the middle of the bisect log, not from scatch. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157
------- Comment #13 from bwalle@novell.com 2006-11-27 12:42 MST -------
I now did the bisect with start
good: [680cbbbb0e336b04b74be48b8ddd870537f1e226] EDAC: name cleanup
bad: [8ba130df4b67fa40878ccf80d54615132d24bc68] Linux v2.6.17
and finally ended in
d2d7cdcf6e6d2a3db9885316d075940f12324413 is first bad commit
diff-tree d2d7cdcf6e6d2a3db9885316d075940f12324413 (from
4c5aea053d64bee7a776a4b874e1b417e9f316fe)
Author: Akinobu Mita
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #18 from bwalle@novell.com 2006-11-29 03:50 MST ------- Found an interesting information at http://www.tyan.com/support/html/b_s3870.html: 05/12/06: * Fixed a compatiblity issue with RedHat 4 64-bit where it would hang after booting the kernel Looks like this is our board, isn't it? Can we try a BIOS update? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #20 from bwalle@novell.com 2006-11-29 05:11 MST ------- 2.6.19-rc6 with default config from 10.2 works fine on that board. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical ------- Comment #21 from aj@novell.com 2006-11-29 05:12 MST ------- This is a rather unfortunate regression but not a shipment blocker. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ------- Comment #22 from bwalle@novell.com 2006-11-30 05:02 MST ------- The behaviour isn't reproducable 100 % at all, I had kernels that sometimes boot and sometimes not. However, the process hangs at "pci_fixup_device() called from pci_init() in /drivers/pci/pci.c for the device vendor=0x1166, device=0x223 which is a Broadcom "HT1000 USB Controller". Disabling "Leagacy USB support" in the BIOS works reliably with our current 10.2 kernel. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223157 ak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Comment #24 from ak@novell.com 2007-02-15 06:31 MST ------- Closed because it's probably a bios bug. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com