OpenBSD current i386 hangs on boot in lm0.
Hi, I updated from OpenBSD current i386, built from CVS 24th March 2011, to one built from CVS on 2nd July 2011. The bsd.rd booted, and was used to upgrade, on reboot this hung. I noted lm0 was the last line, rebooting with the older kernel version the next dmesg line was lm1 detached, and the boot completed. The line in the /var/log/messages for old kernel are:- /bsd: lm1 at iic0 addr 0x2d: W83781D /bsd: lm0 at isa0 port 0x290/8: W83781D /bsd: lm1 detached Using boot -c with latest bsd, I disabled lm, this booted as normal with lm disabled. dmesg is below. I downloaded the latest snapshot bsd 29th June 2011, booted from this an hit the same problem at lm0. I booted from the bsd built from cvs, using boot -c and disabled just lm0, this booted as normal. Updated from CVS today, and rebuilt the kernel, booted from the new bsd, this hung at the same point lm0. Two other i386 systems are fine, but these don't have the lm device. Please contact me if anymore information is required, or anything you would me to try out. Regards Nigel Taylor OpenBSD 4.9-current (GENERIC) #6: Sat Jul 2 13:30:07 BST 2011 r...@lorien.asterisk.me.uk:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Celeron (GenuineIntel 686-class, 128KB L2 cache) 335 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PSE36,MMX,FXSR real mem = 267964416 (255MB) avail mem = 253394944 (241MB) User Kernel Config UKC disable lm 305 lm0 disabled 306 lm* disabled 307 lm* disabled UKC exit Continuing... mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/01/02, BIOS32 rev. 0 @ 0xf0520 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 2.1 @ 0xf/0xdb2 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/160 (8 entries) pcibios0: PCI Interrupt Router at 000:04:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xb000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x03 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xe400, size 0x400 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Rage Magnum rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) piixpcib0 at pci0 dev 4 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 4 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: MAXTOR STM380215A wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVD-ROM GDR8163B, 0L23 ATAPI 5/cdrom removable cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 4 function 2 Intel 82371AB USB rev 0x01: irq 5 piixpm0 at pci0 dev 4 function 3 Intel 82371AB Power rev 0x02: SMI iic0 at piixpm0 w83781d at iic0 addr 0x2d not configured iic0: addr 0x2d 20=7c 21=5d 22=d8 23=b9 24=ca 25=d5 26=d9 27=22 29=54 2b=89 2c=70 2d=89 2e=70 2f=ed 30=b0 31=75 32=c5 33=48 34=0a 35=8c 36=4b 37=63 38=4a 39=c2 3a=33 3b=c4 3c=92 3d=03 3e=00 3f=00 40=01 41=5a 42=0f 44=7f 45=00 46=40 47=a0 48=2d 49=00 4a=01 4b=40 4c=01 4d=95 4e=80 4f=5c 50=00 51=7f 52=00 56=00 57=80 58=11 60=7c 61=5d 62=d8 63=b8 64=ca 65=d5 66=d8 67=22 69=54 6b=89 6c=70 6d=89 6e=70 6f=ed 70=b0 71=75 72=c5 73=48 74=0a 75=8c 76=4b 77=63 78=4a 79=c2 7a=33 7b=c4 7c=92 7d=03 7e=00 7f=00 a0=7c a1=5d a2=d8 a3=bc a4=ca a5=d5 a6=da a7=22 a9=54 ab=89 ac=70 ad=89 ae=70 af=ed b0=b0 b1=75 b2=c5 b3=48 b4=0a b5=8c b6=4b b7=63 b8=4a b9=c2 ba=33 bb=c4 bc=92 bd=03 be=00 bf=00 c0=01 c1=5a c2=0f c4=7f c5=00 c6=40 c7=a0 c8=2d c9=00 ca=01 cb=40 cc=01 cd=95 ce=80 cf=5c d0=00 d1=7f d2=00 d6=00 d7=80 d8=11 e0=7c e1=5d e2=d8 e3=b8 e4=ca e5=d5 e6=d9 e7=22 e9=53 eb=89 ec=70 ed=89 ee=70 ef=ed f0=b0 f1=75 f2=c5 f3=48 f4=0a f5=8c f6=4b f7=63 f8=4a f9=c2 fa=33 fb=c4 fc=92 fd=03 fe=00 ff=00 words 00= 01= 02= 03= 04= 05= 06= 07=: w83781d iic0: addr 0x48 01=00 02=4b 03=50 05=00 06=4b 07=50 09=00 0a=4b 0b=50 0d=00 0e=4b 0f=50 11=00 12=4b 13=50 15=00 16=4b 17=50 19=00 1a=4b 1b=50 1d=00 1e=4b 1f=50 21=00 22=4b 23=50 25=00 26=4b 27=50 29=00 2a=4b 2b=50 2d=00 2e=4b 2f=50 31=00 32=4b 33=50 35=00 36=4b 37=50 39=00 3a=4b 3b=50 3d=00 3e=4b 3f=50 41=00 42=4b 43=50 45=00 46=4b 47=50 49=00 4a=4b 4b=50 4d=00 4e=4b 4f=50 51=00 52=4b 53=50 55=00 56=4b 57=50 59=00 5a=4b 5b=50 5d=00 5e=4b 5f=50 61=00 62=4b 63=50 65=00 66=4b 67=50 69=00 6a=4b 6b=50 6d=00 6e=4b 6f=50 71=00 72=4b 73=50 75=00 76=4b 77=50 79=00 7a=4b 7b=50 7d=00 7e=4b 7f=50 81=00 82=4b 83=50 85=00 86=4b 87=50 89=00 8a=4b 8b=50 8d=00 8e=4b 8f=50 91=00 92=4b 93=50 95=00 96=4b 97=50 99=00 9a=4b 9b=50 9d=00 9e=4b 9f=50 a1=00 a2=4b a3=50 a5=00 a6=4b
Re: OpenBSD current i386 hangs on boot in lm0.
On 07/06/11 07:47, Nigel Taylor wrote: Hi, I updated from OpenBSD current i386, built from CVS 24th March 2011, to one built from CVS on 2nd July 2011. The bsd.rd booted, and was used to upgrade, on reboot this hung. I noted lm0 was the last line, rebooting with the older kernel version the next dmesg line was lm1 detached, and the boot completed. The line in the /var/log/messages for old kernel are:- /bsd: lm1 at iic0 addr 0x2d: W83781D /bsd: lm0 at isa0 port 0x290/8: W83781D /bsd: lm1 detached Using boot -c with latest bsd, I disabled lm, this booted as normal with lm disabled. dmesg is below. I downloaded the latest snapshot bsd 29th June 2011, booted from this an hit the same problem at lm0. I booted from the bsd built from cvs, using boot -c and disabled just lm0, this booted as normal. Updated from CVS today, and rebuilt the kernel, booted from the new bsd, this hung at the same point lm0. Two other i386 systems are fine, but these don't have the lm device. Please contact me if anymore information is required, or anything you would me to try out. I reported the same thing in these two messages: http://marc.info/?l=openbsd-miscm=130755536116000w=2 http://marc.info/?l=openbsd-miscm=130764492616339w=2 This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. However, when I tried building kernels for that range of days I ran into other problems and haven't been able to get back to it since. Jeff
Re: OpenBSD current i386 hangs on boot in lm0.
Hi all, Medion computers, supermicro (many cheap models) motherboards are known as 'not free *unix* compatible'. Therefore most of supermicro other motherboards just seem to work well with *linux *BSD. Madion are hardware coded to be able only to boot a real windows OS, (even reactOS often fail to boot correctly), Then you need to boot other OS to have a windows installed in first partition(s) to use a multiboot, but even that can fail From: Jeff Ross jr...@openvistas.net Sent: Wed Jul 06 17:07:40 CEST 2011 To: Nigel Taylor njtay...@asterisk.demon.co.uk, OpenBSD misc@openbsd.org Subject: Re: OpenBSD current i386 hangs on boot in lm0. On 07/06/11 07:47, Nigel Taylor wrote: Hi, I updated from OpenBSD current i386, built from CVS 24th March 2011, to one built from CVS on 2nd July 2011. The bsd.rd booted, and was used to upgrade, on reboot this hung. I noted lm0 was the last line, rebooting with the older kernel version the next dmesg line was lm1 detached, and the boot completed. The line in the /var/log/messages for old kernel are:- /bsd: lm1 at iic0 addr 0x2d: W83781D /bsd: lm0 at isa0 port 0x290/8: W83781D /bsd: lm1 detached Using boot -c with latest bsd, I disabled lm, this booted as normal with lm disabled. dmesg is below. I downloaded the latest snapshot bsd 29th June 2011, booted from this an hit the same problem at lm0. I booted from the bsd built from cvs, using boot -c and disabled just lm0, this booted as normal. Updated from CVS today, and rebuilt the kernel, booted from the new bsd, this hung at the same point lm0. Two other i386 systems are fine, but these don't have the lm device. Please contact me if anymore information is required, or anything you would me to try out. I reported the same thing in these two messages: http://marc.info/?l=openbsd-miscm=130755536116000w=2 http://marc.info/?l=openbsd-miscm=130764492616339w=2 This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. However, when I tried building kernels for that range of days I ran into other problems and haven't been able to get back to it since. Jeff Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 ToulouseB FranceB +33 6 17 230 820 B +33 5 34 365 269 fpussa...@contactoffice.fr
Re: OpenBSD current i386 hangs on boot in lm0.
On 07/06/11 09:22, Francois Pussault wrote: Hi all, Medion computers, supermicro (many cheap models) motherboards are known as 'not free *unix* compatible'. Therefore most of supermicro other motherboards just seem to work well with *linux *BSD. Madion are hardware coded to be able only to boot a real windows OS, (even reactOS often fail to boot correctly), Then you need to boot other OS to have a windows installed in first partition(s) to use a multiboot, but even that can fail This is not my experience with SuperMicro motherboards, in fact, my experience is exactly the opposite. They all work and work well. Jeff From: Jeff Rossjr...@openvistas.net Sent: Wed Jul 06 17:07:40 CEST 2011 To: Nigel Taylornjtay...@asterisk.demon.co.uk, OpenBSD misc@openbsd.org Subject: Re: OpenBSD current i386 hangs on boot in lm0. On 07/06/11 07:47, Nigel Taylor wrote: Hi, I updated from OpenBSD current i386, built from CVS 24th March 2011, to one built from CVS on 2nd July 2011. The bsd.rd booted, and was used to upgrade, on reboot this hung. I noted lm0 was the last line, rebooting with the older kernel version the next dmesg line was lm1 detached, and the boot completed. The line in the /var/log/messages for old kernel are:- /bsd: lm1 at iic0 addr 0x2d: W83781D /bsd: lm0 at isa0 port 0x290/8: W83781D /bsd: lm1 detached Using boot -c with latest bsd, I disabled lm, this booted as normal with lm disabled. dmesg is below. I downloaded the latest snapshot bsd 29th June 2011, booted from this an hit the same problem at lm0. I booted from the bsd built from cvs, using boot -c and disabled just lm0, this booted as normal. Updated from CVS today, and rebuilt the kernel, booted from the new bsd, this hung at the same point lm0. Two other i386 systems are fine, but these don't have the lm device. Please contact me if anymore information is required, or anything you would me to try out. I reported the same thing in these two messages: http://marc.info/?l=openbsd-miscm=130755536116000w=2 http://marc.info/?l=openbsd-miscm=130764492616339w=2 This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. However, when I tried building kernels for that range of days I ran into other problems and haven't been able to get back to it since. Jeff Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 ToulouseB FranceB +33 6 17 230 820 B +33 5 34 365 269 fpussa...@contactoffice.fr !DSPAM:4e147f8448271610687006!
Re: OpenBSD current i386 hangs on boot in lm0.
Jeff Ross [jr...@openvistas.net] wrote: This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. Yet, a kernel compiled again Jun 6th sources does not display this behvaior Therefore, it is caused by a change that was in the snapshots--but not committed until later I was out of town for a week, but will now narrow down when the offending code was committed since it affects my X7SBL, PDSML, and probably other supermicro boards that I use in qty...
Re: OpenBSD current i386 hangs on boot in lm0.
On 07/06/11 10:04, Chris Cappuccio wrote: Jeff Ross [jr...@openvistas.net] wrote: This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. Yet, a kernel compiled again Jun 6th sources does not display this behvaior Well, that explains the problem I was having. None of the kernels I built would hang so I thought I was doing something wrong. Jeff Therefore, it is caused by a change that was in the snapshots--but not committed until later I was out of town for a week, but will now narrow down when the offending code was committed since it affects my X7SBL, PDSML, and probably other supermicro boards that I use in qty... !DSPAM:4e148bfa98349598613850!
Re: OpenBSD current i386 hangs on boot in lm0.
This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. Yet, a kernel compiled again Jun 6th sources does not display this behvaior Well, that explains the problem I was having. None of the kernels I built would hang so I thought I was doing something wrong. Well, you should know the snapshot behaviour by now if you are running OpenBSD so long. :-) Therefore, it is caused by a change that was in the snapshots--but not committed until later I was out of town for a week, but will now narrow down when the offending code was committed since it affects my X7SBL, PDSML, and probably other supermicro boards that I use in qty...
Re: OpenBSD current i386 hangs on boot in lm0.
On Wed, 6 Jul 2011 17:23:08 +0200 (CEST), Francois Pussault wrote Hi all, Medion computers, supermicro (many cheap models) motherboards are known as 'not free *unix* compatible'. Therefore most of supermicro other motherboards just seem to work well with *linux *BSD. Madion are hardware coded to be able only to boot a real windows OS, (even reactOS often fail to boot correctly), Then you need to boot other OS to have a windows installed in first partition(s) to use a multiboot, but even that can fail I have to disagree about Supermicro. I have been using their motherboards since the mid-2000s, and they are neither cheap nor unfriendly to free unices. The biggest problem is that their support people are generally not unix people. I never had any trouble running OpenBSD on their products until 4.8, when it started hanging on boot, which I reported to this list previously. ~~~
Re: OpenBSD current i386 hangs on boot in lm0.
Hi, I am using a ASUS P2B motherboard, this has been running OpenBSD since 2005 could be a few years longer. With no issues other than a hard disk failure. There is no multiboot in use, it's not a Medion computer, or using a supermicro motherboard. The common issue is with the lm device hanging during boot with OpenBSD current. Regards Nigel Taylor On 07/06/11 16:23, Francois Pussault wrote: Hi all, Medion computers, supermicro (many cheap models) motherboards are known as 'not free *unix* compatible'. Therefore most of supermicro other motherboards just seem to work well with *linux *BSD. Madion are hardware coded to be able only to boot a real windows OS, (even reactOS often fail to boot correctly), Then you need to boot other OS to have a windows installed in first partition(s) to use a multiboot, but even that can fail From: Jeff Rossjr...@openvistas.net Sent: Wed Jul 06 17:07:40 CEST 2011 To: Nigel Taylornjtay...@asterisk.demon.co.uk, OpenBSD misc@openbsd.org Subject: Re: OpenBSD current i386 hangs on boot in lm0. On 07/06/11 07:47, Nigel Taylor wrote: Hi, I updated from OpenBSD current i386, built from CVS 24th March 2011, to one built from CVS on 2nd July 2011. The bsd.rd booted, and was used to upgrade, on reboot this hung. I noted lm0 was the last line, rebooting with the older kernel version the next dmesg line was lm1 detached, and the boot completed. The line in the /var/log/messages for old kernel are:- /bsd: lm1 at iic0 addr 0x2d: W83781D /bsd: lm0 at isa0 port 0x290/8: W83781D /bsd: lm1 detached Using boot -c with latest bsd, I disabled lm, this booted as normal with lm disabled. dmesg is below. I downloaded the latest snapshot bsd 29th June 2011, booted from this an hit the same problem at lm0. I booted from the bsd built from cvs, using boot -c and disabled just lm0, this booted as normal. Updated from CVS today, and rebuilt the kernel, booted from the new bsd, this hung at the same point lm0. Two other i386 systems are fine, but these don't have the lm device. Please contact me if anymore information is required, or anything you would me to try out. I reported the same thing in these two messages: http://marc.info/?l=openbsd-miscm=130755536116000w=2 http://marc.info/?l=openbsd-miscm=130764492616339w=2 This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. However, when I tried building kernels for that range of days I ran into other problems and haven't been able to get back to it since. Jeff Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 ToulouseB FranceB +33 6 17 230 820 B +33 5 34 365 269 fpussa...@contactoffice.fr
Re: OpenBSD current i386 hangs on boot in lm0.
On 07/06/11 17:04, Chris Cappuccio wrote: Jeff Ross [jr...@openvistas.net] wrote: This hang happens with the 4 different SuperMicro based motherboards I have that have the lm chipset. In the second message referenced above I noted that a snapshot dated May 25 booted normally and I first ran into the problem on June 6 so the window is fairly small. Yet, a kernel compiled again Jun 6th sources does not display this behvaior Therefore, it is caused by a change that was in the snapshots--but not committed until later I was out of town for a week, but will now narrow down when the offending code was committed since it affects my X7SBL, PDSML, and probably other supermicro boards that I use in qty... Hi, This might be a different fault to the previous one reported. I tried a kernel built from CVS using the follwoing dates 6th June Ok. 15th June Ok. 22nd June Hangs. 19th June Ok. 20th June Ok. 21st June Hangs. The changed between the two dates are :- cvs -R -q diff -uNp -D 2011/06/20 -D 2011/06/21 | grep Index: Index: arch/amd64/conf/GENERIC Index: arch/i386/conf/GENERIC Index: dev/softraid.c Index: dev/vnd.c Index: dev/ata/wd.c Index: dev/isa/if_lc_isa.c Index: dev/isa/if_we.c Index: dev/isa/mcd.c Index: dev/isa/radiotrack2.c Index: dev/isa/sf16fmr2.c Index: dev/isa/wdc_isa.c Index: dev/microcode/Makefile Index: dev/pci/if_myx.c Index: dev/pci/if_myxreg.h Index: kern/subr_autoconf.c Index: net/if_pflog.c Index: net/pf.c Index: net/pf_norm.c Index: net/pfvar.h I think I narrowed this down to kern/subr_autoconf.c, build a kernel extract from CVS with a date of 21st June, with kern/subr_autoconf.c kept at version 1.64. This booted without hanging. 1.65 log serialize attach and detach of device sub-trees -- only one device sub-tree may attach or detach at a time. attach and detach will sleep against each other. this is fixing (working around?) some bizzare corner cases that have been seen (but not fully diagnosed) where the device trees, disk registration subsystem, and other things could get messed up. one could argue though that this serialization is a very good thing; it is easier than adding piles of locks in various other places. ok matthew jsing In the case of lm from dmesg we have, lm1 at iic0 addr 0x2d: W83781D lm0 at isa0 port 0x290/8: W83781D lm1 detached Regards Nigel Taylor
