Date: Mon, 29 Mar 2010 12:02:16 -0400 From: John Baldwin <jhb@freebsd.org> To: agh@coolrhaug.com Cc: kochetkov.andrew@gmail.com, Randy Chou <randychou@yahoo.com>, freebsd-hardware@freebsd.org Subject: Re: Intel DP45SG motherboard problem (amd64) Message-ID: <201003291202.16104.jhb@freebsd.org> In-Reply-To: <201003280826.19914.agh@coolrhaug.com> References: <201002212231.12018.agh@coolrhaug.com> <201003171123.03817.jhb@freebsd.org> <201003280826.19914.agh@coolrhaug.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 27 March 2010 8:26:19 pm Alastair Hogge wrote: > On Wed March 17 2010 23:23:03 John Baldwin wrote: > > On Tuesday 16 March 2010 9:22:28 am Alastair Hogge wrote: > > > On Tue March 2 2010 00:54:00 John Baldwin wrote: > > > > This would not change acpidump output, just the kernel. Are you able > > > > to capture the boot messages with this kernel? > > > > > > Full log: > > > http://codepad.org/96PT5OO8 > > > > Oh! ACPI is working, but the MADT is not so it's trying to mix and match > > mptable (for SMP) with ACPI. Odd that you didn't get a warning message > > about the checksum failing from boot -v. Try this patch: > > > > Index: amd64/acpica/acpi_machdep.c > > =================================================================== > > --- amd64/acpica/acpi_machdep.c (revision 205249) > > +++ amd64/acpica/acpi_machdep.c (working copy) > > @@ -627,8 +627,10 @@ > > if (ACPI_FAILURE(AcpiTbChecksum(table, length))) { > > if (bootverbose) > > printf("ACPI: Failed checksum for table %s\n", sig); > > +#if (ACPI_CHECKSUM_ABORT) > > table_unmap(table, length); > > return (NULL); > > +#endif > > } > > return (table); > > } > > Index: i386/acpica/acpi_machdep.c > > =================================================================== > > --- i386/acpica/acpi_machdep.c (revision 205249) > > +++ i386/acpica/acpi_machdep.c (working copy) > > @@ -641,8 +641,10 @@ > > if (ACPI_FAILURE(AcpiTbChecksum(table, length))) { > > if (bootverbose) > > printf("ACPI: Failed checksum for table %s\n", sig); > > +#if (ACPI_CHECKSUM_ABORT) > > table_unmap(table, length); > > return (NULL); > > +#endif > > } > > return (table); > > } > > > OK, I've applied the patch to my i386 system & there doesn't appear to be > problems so far. > > I also created an amd64 bootonly CD with the patch & was able to boot into > sysinstall :-) > > [dcons connected] > lapic: Divisor 2, Frequency 166664803 Hz > ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 59 > Timecounter "TSC" frequency 2833301532 Hz quality -100 > Timecounters tick every 1.000 msec > vlan: initialized, using hash tables with chaining > lo0: bpf attached > hptrr: no controller detected. > ata2: Identifying devices: 00000001 > ata2: New devices: 00000001 > firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1) (me) > firewire0: bus manager 1 > md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xffffffff8104f9f8 > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > usbus2: 12Mbps Full Speed USB v1.0 > usbus3: 480Mbps High Speed USB v2.0 > usbus4: 12Mbps Full Speed USB v1.0 > usbus5: 12Mbps Full Speed USB v1.0 > usbus6: 12Mbps Full Speed USB v1.0 > usbus7: 480Mbps High Speed USB v2.0 > ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad4: setting UDMA100 > ad4: 286188MB <Maxtor 6V300F0 VA111630> at ata2-master UDMA100 SATA 3Gb/s > ad4: 586114704 sectors [581463C/16H/63S] 16 sectors/interrupt 1 depth queue > GEOM: new disk ad4 > ugen0.1: <Intel> at usbus0 > uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 > ugen1.1: <Intel> at usbus1 > uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1 > ugen2.1: <Intel> at usbus2 > uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2 > ugen3.1: <Intel> at usbus3 > uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3 > ugen4.1: <Intel> at usbus4 > uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4 > ugen5.1: <Intel> at usbus5 > uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5 > ugen6.1: <Intel> at usbus6 > uhub6: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6 > ugen7.1: <Intel> at usbus7 > uhub7: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7 > ad4: Intel check1 failed > ad4: Adaptec check1 failed > ad4: LSI (v3) check1 failed > ad4: LSI (v2) check1 failed > ad4: FreeBSD check1 failed > ata3: Identifying devices: 00000001 > ata3: New devices: 00000001 > ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad6: setting UDMA100 > ad6: 476940MB <SAMSUNG HD502HJ 1AJ100E4> at ata3-master UDMA100 SATA 3Gb/s > ad6: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue > ad6: Intel check1 failed > ad6: Adaptec check1 failed > ad6: LSI (v3) check1 failed > ad6: LSI (v2) check1 failed > ad6: FreeBSD check1 failed > ata4: Identifying devices: 00000001 > ata4: New devices: 00000001 > ata4-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad8: setting UDMA100 > ad8: 114473MB <Seagate ST3120026AS 3.05> at ata4-master UDMA100 SATA 1.5Gb/s > ad8: 234441648 sectors [232581C/16H/63S] 16 sectors/interrupt 1 depth queue > ad8: Intel check1 failed > ad8: Adaptec check1 failed > ad8: LSI (v3) check1 failed > ad8: LSI (v2) check1 failed > ad8: FreeBSD check1 failed > ata5: Identifying devices: 00000000 > ata5: New devices: 00000000 > ata6: Identifying devices: 00000001 > ata6: New devices: 00000001 > ata6-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire > ad12: setting UDMA100 > ad12: 476940MB <SAMSUNG HD502HJ 1AJ100E4> at ata6-master UDMA100 SATA 3Gb/s > ad12: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue > ad12: Intel check1 failed > ad12: Adaptec check1 failed > ad12: LSI (v3) check1 failed > ad12: LSI (v2) check1 failed > ad12: FreeBSD check1 failed > ata7: Identifying devices: 00010000 > ata7: New devices: 00010000 > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire > acd0: setting UDMA100 > ata7: device_reset timeout=230us > acd0: <ASUS DRW-20B1LT/1.00> DVDR drive at ata7 as master > acd0: read 8269KB/s (8269KB/s) write 8269KB/s (8269KB/s), 2048KB buffer, > UDMA100 SATA 1.5Gb/s > acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet > acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray, unlocked > acd0: Medium: CD-ROM 120mm data disc > GEOM: new disk ad6 > GEOM: new disk ad8 > GEOM: new disk ad12 > firewire0: New S400 device ID:00902700022b34b9 > uhub0: 2 ports with 2 removable, self powered > uhub1: 2 ports with 2 removable, self powered > uhub2: 2 ports with 2 removable, self powered > uhub4: 2 ports with 2 removable, self powered > uhub5: 2 ports with 2 removable, self powered > uhub6: 2 ports with 2 removable, self powered > uhub3: 6 ports with 6 removable, self powered > uhub7: 6 ports with 6 removable, self powered > ugen0.2: <ALCOR> at usbus0 > uhub8: <ALCOR Generic USB Hub, class 9/0, rev 1.10/3.12, addr 2> on usbus0 > (probe1:sbp0:0:1:0): Error 22, Unretryable error > (probe2:sbp0:0:2:0): Error 22, Unretryable error > (probe3:sbp0:0:3:0): Error 22, Unretryable error > (probe0:sbp0:0:0:0): Error 22, Unretryable error > (probe4:sbp0:0:4:0): Error 22, Unretryable error > (probe5:sbp0:0:5:0): Error 22, Unretryable error > (probe6:sbp0:0:6:0): Error 22, Unretryable error > ATA PseudoRAID loaded > SMP: AP CPU #1 Launched! > cpu1 AP: > ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 > SMP: AP CPU #3 Launched! > cpu3 AP: > ID: 0x03000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 > SMP: AP CPU #2 Launched! > cpu2 AP: > ID: 0x02000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 > ioapic0: routing intpin 3 (ISA fIlRoQw t3a)b lteo cllaepaince r1 > svteacrttoerd 4 > 8 > ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 2 vector 48 > ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 3 vector 48 > ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 1 vector 49 > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 2 vector 49 > ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 3 vector 49 > ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 1 vector 50 > ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 2 vector 50 > msi: Assigning MSI IRQ 256 to local APIC 3 vector 50 > WARNING: WITNESS option enabled, expect reduced performance. > ugen1.2: <DATACOMP> at usbus1 > ukbd0: <DATACOMP SteelSDATA, class 0/0, rev 1.10/0.01, addr 2> on usbus1 > kbd2 at ukbd0 > kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000 > ums0: <DATACOMP SteelSDATA, class 0/0, rev 1.10/0.01, addr 2> on usbus1 > uhub8: 4 ports with 4 removable, self powered > ugen0.3: <SteelSeries ApS> at usbus0 > ums1: <SteelSeries ApS Ikari Laser, class 0/0, rev 2.00/1.00, addr 3> on > usbus0 > ums1: 7 buttons and [XYZ] coordinates ID=2 > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05 > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05 > Trying to mount root from ufs:/dev/md0 > ct_to_ts([2010-03-28 08:05:57]) = 1269763557.000000000 > start_init: trying /sbin/init > start_init: trying /sbin/oinit > start_init: trying /sbin/init.bak > start_init: trying /rescue/init > start_init: trying /stand/sysinstall > > Thanks for the help John & *, any chance this will get committed? It is already in the tree and merged to 7 and 8. It should be present in 7.4 and 8.1. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003291202.16104.jhb>