[Bug 228195] New: Installation failure on MSI K8T Neo2 (VIA K8T800 Pro)
https://bugzilla.novell.com/show_bug.cgi?id=228195 Summary: Installation failure on MSI K8T Neo2 (VIA K8T800 Pro) Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dulus@budweiser.com QAContact: jsrain@novell.com After i try to install with 10.2 64bit DVD, it detects sata_promise correctly, continues on motheboard VIA chipset detections and stuck there on via82_cxxx module. I used brokenmodules command to disable that module and stuck then on pata_via, generic. Finaly i added all three to brokenmodules, and get frozen on USB detection. I unplugged all usb devices, used PS2 mouse and keyboard, no luck... Diabled USB in bios and ran on same problem with firewire. Also tryied to disable all that APIC and ACPI stuff, didn't helped. After watching install status i discovered that problem is probably with insmod command, which is unable to load ANY module to installation kernel. After killing insmod processes they stay zombie and yast is skipping to text mode with red message of failure. There is nothing much to do because no ata or sata drives are accessible. Seems that 2.6.18 installation kernel has problem with this motherboard. I tried different BIOSes, older, newer, but same result. DVD chcecksum is correct, I sucesfully installed suse in VMware with this media. Suse 10.1 installation on this computer is without problems. -- 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=228195 dulus@budweiser.com changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- 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=228195 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dulus@budweiser.com ------- Comment #1 from mhorvath@novell.com 2006-12-13 06:04 MST ------- Please attach the /var/log/messages, the boot.log and the boot.msg. Thank you. -- 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=228195 kendy@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kendy@novell.com Status|NEEDINFO |ASSIGNED Info Provider|dulus@budweiser.com | ------- Comment #2 from kendy@novell.com 2006-12-13 08:48 MST ------- I have the same problem - oops very short after the installation kernel starts booting. No /var/log/messages at that time, etc. I'll attach hwinfo output of that machine and the output I get from serial console (including RAlt+SysRq+t). -- 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=228195 ------- Comment #3 from kendy@novell.com 2006-12-13 08:50 MST ------- Created an attachment (id=109567) --> (https://bugzilla.novell.com/attachment.cgi?id=109567&action=view) The oops. -- 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=228195 ------- Comment #4 from kendy@novell.com 2006-12-13 08:51 MST ------- Created an attachment (id=109568) --> (https://bugzilla.novell.com/attachment.cgi?id=109568&action=view) hwinfo output. (10.1 works OK on that machine.) -- 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=228195 ------- Comment #5 from dulus@budweiser.com 2006-12-14 02:42 MST ------- I think I found where bug is. It is sata_promise module. When I unplugged all sata drives, disabled sata chipset and used pata harddrive on via chipset installation of SuSE 10.2 was successfull. So I think this bug is duplicate of other sata_promise bugs. When kernel loads this module, it fails, module is going killed but it doesn't work somehow and all other modules which are loaded after that buggy sata_promise are unable to load into kernel. With sata_promise added to brokenmodules is installation possible (but ofcourse without sata drives). Here is part of boot.msg: <7>libata version 2.00 loaded. <7>sata_promise 0000:00:0d.0: version 1.04 <6>GSI 16 sharing vector 0xA9 and IRQ 16 <6>ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 17 (level, low) -> IRQ 169 <6>sata_promise PATA port found <6>ata1: SATA max UDMA/133 cmd 0xFFFFC20000036200 ctl 0xFFFFC20000036238 bmdma 0x0 irq 169 <6>ata2: SATA max UDMA/133 cmd 0xFFFFC20000036280 ctl 0xFFFFC200000362B8 bmdma 0x0 irq 169 <6>ata3: SATA max UDMA/133 cmd 0xFFFFC20000036300 ctl 0xFFFFC20000036338 bmdma 0x0 irq 169 <6>scsi0 : sata_promise <6>ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) <6>ata1.00: ATA-7, max UDMA/133, 240121728 sectors: LBA <6>ata1.00: ata1: dev 0 multi count 0 <6>ata1.00: configured for UDMA/133 <6>scsi1 : sata_promise <6>ata2: SATA link down (SStatus 0 SControl 300) <1>Unable to handle kernel NULL pointer dereference at 0000000000000008 RIP: <1> [<ffffffff8823c5ab>] :sata_promise:pdc_sata_scr_read+0x18/0x1b <4>PGD 3db5e067 PUD 3d718067 PMD 0 <0>Oops: 0000 [1] SMP <0>last sysfs file: /firmware/edd/int13_dev81/extensions <4>CPU 0 <4>Modules linked in: sata_promise libata ppa parport_pc parport cpufreq_ondemand freq_table fan thermal processor loop floppy ide_disk nfs nfs_acl lockd sunrpc cramfs vfat fat nls_iso8859_1 nls_cp437 af_packet edd sg st sd_mod sr_mod scsi_mod ide_cd cdrom ide_core <4>Pid: 1215, comm: insmod Not tainted 2.6.18.2-34-default #1 <4>RIP: 0010:[<ffffffff8823c5ab>] [<ffffffff8823c5ab>] :sata_promise:pdc_sata_scr_read+0x18/0x1b <4>RSP: 0018:ffff81003dc31c30 EFLAGS: 00010202 <4>RAX: 0000000000000008 RBX: ffff81003dc31c8c RCX: 0000000000000000 <4>RDX: ffff81003dc31c8c RSI: 0000000000000002 RDI: ffff81003d65c4f0 <4>RBP: ffff81003d65c4f0 R08: ffffffff80544a60 R09: 0000000000000020 <4>R10: 00000000ffffffff R11: 0000000000000000 R12: 0000000000000003 <4>R13: ffff81003e0a8000 R14: ffff81003ef94dc0 R15: ffff81003ff39070 <4>FS: 00002b2eb74d86f0(0000) GS:ffffffff805b7000(0000) knlGS:0000000000000000 <4>CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>CR2: 0000000000000008 CR3: 000000003f24c000 CR4: 00000000000006e0 <4>Process insmod (pid: 1215, threadinfo ffff81003dc30000, task ffff81003f45e080) <4>Stack: ffffffff8821763a ffffc20000036300 ffffffff8821cd38 0000000000000000 <4> ffffffff000000a9 00000000fffee54d 0000000000000000 000000a900000000 <4> 0000000000000002 0000000000000003 ffffffff8028a0ae 000000003f45e080 <4>Call Trace: <4> [<ffffffff8821763a>] :libata:sata_scr_read+0x1f/0x2c <4> [<ffffffff8821cd38>] :libata:ata_device_add+0x342/0x4ca <4> [<ffffffff8028a0ae>] process_timeout+0x0/0x5 <4> [<ffffffff8823cb71>] :sata_promise:pdc_ata_init_one+0x399/0x3e0 <4> [<ffffffff80319c73>] pci_device_probe+0xf7/0x165 <4> [<ffffffff8036fb83>] really_probe+0x47/0xa9 <4> [<ffffffff8036fd4f>] __driver_attach+0x65/0xb7 <4> [<ffffffff8036fcea>] __driver_attach+0x0/0xb7 <4> [<ffffffff8036f5ca>] bus_for_each_dev+0x43/0x6e <4> [<ffffffff8036f210>] bus_add_driver+0x7e/0x130 <4> [<ffffffff80319e6c>] __pci_register_driver+0x71/0x98 <4> [<ffffffff80299bcc>] sys_init_module+0x172f/0x18e5 <4> [<ffffffff8025800e>] system_call+0x7e/0x83 <4> <4> <4>Code: 8b 00 c3 48 8b 87 10 2b 00 00 48 8b 40 20 8b 40 40 c3 83 fe <1>RIP [<ffffffff8823c5ab>] :sata_promise:pdc_sata_scr_read+0x18/0x1b <4> RSP <ffff81003dc31c30> <0>CR2: 0000000000000008 <4> -- 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=228195 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | Status|ASSIGNED |NEW -- 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=228195 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |hare@novell.com |maintainers@forge.provo.nove| |ll.com | -- 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=228195 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hare@novell.com |htejun@gmail.com -- 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=228195 htejun@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|htejun@gmail.com |teheo@novell.com -- 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=228195 ------- Comment #6 from teheo@novell.com 2006-12-17 22:19 MST ------- Created an attachment (id=110051) --> (https://bugzilla.novell.com/attachment.cgi?id=110051&action=view) sata_promise board-2057x oops fix In your dmesg, the last port should be detected as PATA not SATA. This patch should fix it. This bug slipped testing because only 2037x series controllers are used for testing. -- 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=228195 ------- Comment #7 from teheo@novell.com 2006-12-17 22:20 MST ------- (From update of attachment 110051) diff --git a/drivers/ata/sata_promise.c b/drivers/ata/sata_promise.c index c94cf9c..8abc273 100644 --- a/drivers/ata/sata_promise.c +++ b/drivers/ata/sata_promise.c @@ -215,7 +215,7 @@ static const struct ata_port_info pdc_port_info[] = { /* board_2057x */ { .sht = &pdc_ata_sht, - .flags = PDC_COMMON_FLAGS | ATA_FLAG_SATA, + .flags = PDC_COMMON_FLAGS /* | ATA_FLAG_SATA */, .pio_mask = 0x1f, /* pio0-4 */ .mwdma_mask = 0x07, /* mwdma0-2 */ .udma_mask = 0x7f, /* udma0-6 ; FIXME */ -- 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=228195 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #110051|0 |1 is obsolete| | ------- Comment #8 from teheo@novell.com 2006-12-17 22:24 MST ------- Created an attachment (id=110052) --> (https://bugzilla.novell.com/attachment.cgi?id=110052&action=view) sata_promise board-2057x oops fix Sorry, -WRNGFILE. This is the correct one. Closing the 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.
https://bugzilla.novell.com/show_bug.cgi?id=228195 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #9 from teheo@novell.com 2006-12-17 22:27 MST ------- Closing, the patch in #8 fixes the problem. I'll forward the fix. -- 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=228195 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wstephenson@novell.com ------- Comment #10 from teheo@novell.com 2006-12-17 22:39 MST ------- *** Bug 221600 has been marked as a duplicate of this 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