Re: uvm fault booting
It's running again. I ran Seagate Diagnostics, the long version, like 2 hours. When it was about 97% done it hadn't given any messages, and I went to dinner. When I came back I found I'd knocked the power plug out, the battery had run down, so I booted it up cold. Took longer than usual but it came up. So maybe the Seagate stuff remapped some sectors, maybe not. So do I dare scan my SD card or not? I think I'll try it from Windows, that's more expendable. Over half the drive is OpenBSD, the rest is Windows and Linux. On 2/29/16, Alan Corey wrote: > I forgot, wd0a and e aren't the only OpenBSD partitions, the biggie is > wd0m, about 500 gigs. There's 4 gigs of RAM and I never had a problem > with it before, but I can reproduce the uvm fault by trying to fsck it > in single user mode. I don't remember whether swap is on at that > point or not. Maybe it's time to download Seagate's drive diagnostics > and run them, but the drive's less than 1 year old. Maybe it needs to > remap a sector. > > The acpi and USB messages appear every time I open the lid on the > laptop, I don't pay much attention to them. It was running badblocks > on an SD card plugged into a USB reader that started all this, but I > don't see how a USB problem would persist through reboots. I've seen > some nasty crashes dealing with SD and USB memory sticks, it's almost > like they need their own utilities since they aren't really hard > drives. > > OpenBSD 5.7 (GENERIC.MP) #767: Sun Mar 8 11:04:48 MDT 2015 > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP > cpu0: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz ("GenuineIntel" > 686-class) 2 GHz > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF > real mem = 3747885056 (3574MB) > avail mem = 3674271744 (3504MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: date 07/16/13, BIOS32 rev. 0 @ 0xffa10, SMBIOS rev. > 2.4 @ 0xf6bd0 (62 entries) > bios0: vendor Dell Inc. version "A12" date 07/16/2013 > bios0: Dell Inc. Latitude D530 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP HPET APIC ASF! MCFG TCPA SLIC SSDT > acpi0: wakeup devices PCI0(S5) PCIE(S4) USB1(S0) USB2(S0) USB3(S0) > USB4(S0) USB5(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S3) RP02(S4) > RP03(S3) RP04(S3) RP05(S3) RP06(S5) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 199MHz > cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz ("GenuineIntel" > 686-class) 2 GHz > cpu1: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > ioapic0: misconfigured as apic 0, remapped to apid 2 > acpimcfg0 at acpi0 addr 0xf800, bus 0-63 > acpiprt0 at acpi0: bus 3 (PCIE) > acpiprt1 at acpi0: bus -1 (AGP_) > acpiprt2 at acpi0: bus 11 (RP01) > acpiprt3 at acpi0: bus 12 (RP02) > acpiprt4 at acpi0: bus -1 (RP03) > acpiprt5 at acpi0: bus -1 (RP04) > acpiprt6 at acpi0: bus -1 (RP05) > acpiprt7 at acpi0: bus 9 (RP06) > acpiprt8 at acpi0: bus 0 (PCI0) > acpicpu0 at acpi0: C3, C2, C1, PSS > acpicpu1 at acpi0: C3, C2, C1, PSS > acpitz0 at acpi0: critical temperature is 99 degC > acpibtn0 at acpi0: LID_ > acpibtn1 at acpi0: PBTN > acpibtn2 at acpi0: SBTN > acpiac0 at acpi0: AC unit online > acpibat0 at acpi0: BAT0 model "DELL" serial 1 type LION oem "Panasonic" > acpibat1 at acpi0: BAT1 not present > acpidock0 at acpi0: GDCK not docked (0) > acpivideo0 at acpi0: VID_ > acpivideo1 at acpi0: VID_ > acpivout0 at acpivideo1: LCD_ > acpivideo2 at acpi0: VID2 > bios0: ROM list: 0xc/0xf000! 0xcf000/0x1000 > cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2001, 2000, 1600, 1200, 800 MHz > pci0 at mainbus0 bus 0: configuration mode 1 (bios) > pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x0c > vga1 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x0c > intagp0 at vga1 > agp0 at intagp0: aperture at 0xe000, size 0x1000 > inteldrm0 at vga1 > drm0 at inteldrm0 > composite sync not supported > composite sync not supported > inteldrm0: 1024x768 > wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) > wsdisplay0: screen 1-5 added (std, vt100 emulation) > "Intel GM965 Video" rev 0x0c at pci0 dev 2 function 1 not configured > uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x02: apic 2 int 20 > uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x02: apic 2
Re: ASUS Zenbook UX305FA graphics issue
On Mon, Feb 29, 2016 at 11:14:09PM +0100, ni...@posteo.de wrote: > Hello, > > I'm running -current on my Zenbook UX305FA everything except the > graphic works great. It's running a Braodwell CPU and Intel Graphics. > > During the boot process as soon as inteldrm loads the screen turns > black. The backlight is still on and the laptop boots fine so I can ssh > into it. > Disabling inteldrm lets me boot up without any problem and start X. > I also tried booting straight to X with xdm enabled but that does not > work. > > Here are some hardware specification (I'm not sure what's relevant, > maybe the high screen resolution is a problem for the frambuffer?): > > CPU: Intel Core M-5Y71 > Graphics: Intel Graphics 5300 (tried different memory allocations in > BIOS 32MB-512MB) > Display: 3200x1800 > > and dmesg: http://pastebin.com/jfV7R3aN > > Any help to get this working would be greatly appreciated. > There is no support for MST displayport, it isn't clear if your panel can do that resolution with SST. If you can build a kernel with the following it should give some more information in dmesg: Index: sys/arch/amd64/conf/GENERIC === RCS file: /cvs/src/sys/arch/amd64/conf/GENERIC,v retrieving revision 1.414 diff -u -p -r1.414 GENERIC --- sys/arch/amd64/conf/GENERIC 20 Jan 2016 01:26:00 - 1.414 +++ sys/arch/amd64/conf/GENERIC 1 Mar 2016 01:43:47 - @@ -24,6 +24,7 @@ optionMTRR# CPU memory range attribu option NTFS# NTFS support option HIBERNATE # Hibernate support +option DRMDEBUG config bsd swap generic
Como Llenar su Restaurante de Gente
Aumente radicalmente el flujo de caja, las ganancias y la clientela de su restaurante! Ãnica Fecha, ¡No deje pasar esta oportunidad! 22 de Abril / Guadalajara Más información>> Como Organizar y Dirigir un Restaurante, 22 de Abril en Guadalajara. Unica Fecha en Guadalajara Pregunte por este Seminario Intensivo: Cómo Organizar y Dirigir un Restaurante Aprenda las mejores ideas y estrategias usadas en los mejores y más rentables restaurantes del mundo para atraer y fidelizar clientes, ganando imagen y recomendación. Este evento le ayudará a repotenciar todo un restaurante haciéndolo más rentable, atractivo y exitoso. Llámenos al 01 800 333 7726. Presione aqui para solicitar la informacion completa, NO olvide proporcionar su Nombre y Telefono O si lo prefiere, responda este correo con la palabra Restaurante junto con su Nombre y Teléfono. m...@cvs.openbsd.org¿Considera que recibe demasiados correos?, solamente responda con la palabra OCW932 en el asunto y su e-mail seré retirado de nuestro listado en las próximas 48 hrs. [demime 1.01d removed an attachment of type image/jpeg which had a name of img1.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of b.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of s.jpg]
ASUS Zenbook UX305FA graphics issue
Hello, I'm running -current on my Zenbook UX305FA everything except the graphic works great. It's running a Braodwell CPU and Intel Graphics. During the boot process as soon as inteldrm loads the screen turns black. The backlight is still on and the laptop boots fine so I can ssh into it. Disabling inteldrm lets me boot up without any problem and start X. I also tried booting straight to X with xdm enabled but that does not work. Here are some hardware specification (I'm not sure what's relevant, maybe the high screen resolution is a problem for the frambuffer?): CPU: Intel Core M-5Y71 Graphics: Intel Graphics 5300 (tried different memory allocations in BIOS 32MB-512MB) Display: 3200x1800 and dmesg: http://pastebin.com/jfV7R3aN Any help to get this working would be greatly appreciated.
Re: uvm fault booting
On Mon, Feb 29, 2016 at 11:24:23AM -0500, Alan Corey wrote: > Everything's been stable for months. Then I was running badblocks on an SD > card plugged into a USB card reader. The screen went white, I couldn't > ssh to it, so I killed the power. It boots to just past the file system > checks and hangs, disk access light on. Did that before so I went away for > an hour, came back to find the uvm fault message. 5.7 i386 > Upgrade to -current, as a ton of changes went into i386 pmap since 5.7. -ml > Sent from my Motorola XT1505
Re: uvm fault booting
I forgot, wd0a and e aren't the only OpenBSD partitions, the biggie is wd0m, about 500 gigs. There's 4 gigs of RAM and I never had a problem with it before, but I can reproduce the uvm fault by trying to fsck it in single user mode. I don't remember whether swap is on at that point or not. Maybe it's time to download Seagate's drive diagnostics and run them, but the drive's less than 1 year old. Maybe it needs to remap a sector. The acpi and USB messages appear every time I open the lid on the laptop, I don't pay much attention to them. It was running badblocks on an SD card plugged into a USB reader that started all this, but I don't see how a USB problem would persist through reboots. I've seen some nasty crashes dealing with SD and USB memory sticks, it's almost like they need their own utilities since they aren't really hard drives. OpenBSD 5.7 (GENERIC.MP) #767: Sun Mar 8 11:04:48 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF real mem = 3747885056 (3574MB) avail mem = 3674271744 (3504MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 07/16/13, BIOS32 rev. 0 @ 0xffa10, SMBIOS rev. 2.4 @ 0xf6bd0 (62 entries) bios0: vendor Dell Inc. version "A12" date 07/16/2013 bios0: Dell Inc. Latitude D530 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC ASF! MCFG TCPA SLIC SSDT acpi0: wakeup devices PCI0(S5) PCIE(S4) USB1(S0) USB2(S0) USB3(S0) USB4(S0) USB5(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S3) RP02(S4) RP03(S3) RP04(S3) RP05(S3) RP06(S5) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 3 (PCIE) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 11 (RP01) acpiprt3 at acpi0: bus 12 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus 9 (RP06) acpiprt8 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "DELL" serial 1 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 not present acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivideo1 at acpi0: VID_ acpivout0 at acpivideo1: LCD_ acpivideo2 at acpi0: VID2 bios0: ROM list: 0xc/0xf000! 0xcf000/0x1000 cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2001, 2000, 1600, 1200, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x0c vga1 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x0c intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 composite sync not supported composite sync not supported inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM965 Video" rev 0x0c at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x02: apic 2 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x02: apic 2 int 21 ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x02: apic 2 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" rev 0x02: msi azalia0: codecs: Sigmatel STAC9205X, Conexant/0x2c06, using Sigmatel STAC9205X audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x02: apic 2 int 16 pci1 at ppb0 bus 11 ppb1 at pci0 dev 28 function 1 "Intel 82801H PCIE" rev 0x02: apic 2 int 17 pci2 at ppb1 bus 12 athn0 at pci2 dev 0 function 0 "Atheros AR5418" rev 0x01: apic 2 int 17 athn0: MAC AR5418 rev 2, RF AR5133 (2T3R), ROM rev 8, address 00:21:63:30:0e:4c ppb2 at pci0 dev 28 function 5 "Intel 82801H PCIE" rev 0x02:
Re: uvm fault booting
Transcribing from a cell phone picture of the screen on another machine later: /dev/rwd0a fscked OK /dev/rwd0e fscked OK (both of my OpenBSD partitions) acpivideo1 unknown event 0x00 uhubs 0-6 detached uhubs 0-6 at usb0-6 "Intel UHCI (and EHCI) root hub" rev 1.00 (2.0 on the EHCI) uvm_fault (0xdaa7a1b0, 0xcfe08000,0,1) -> e kernel: page fault trap code = 0 Stopped at pmap_extract+0x3f: mov1 [camera lat/lon stamp on top of this] -- Credit is the root of all evil. - AB1JX
uvm fault booting
Everything's been stable for months. Then I was running badblocks on an SD card plugged into a USB card reader. The screen went white, I couldn't ssh to it, so I killed the power. It boots to just past the file system checks and hangs, disk access light on. Did that before so I went away for an hour, came back to find the uvm fault message. 5.7 i386 Sent from my Motorola XT1505
Dualbooting with GRUB in a UEFI environment
Hi misc@, I just cracked this and it doesn't seem to be well documented so I thought I'd stick it here. My setup is a VAIO laptop dualbooting Ubuntu 16.04 and OpenBSD -CURRENT. I've got sd0a setup as a cryptoraid partition, so I needed a way to chainload into the OBSD bootloader to get a prompt to decrypt the partition. The following syntax in grub2 (say in /etc/grub.d/40_custom on the linux side) works: menuentry 'OpenBSD/amd64 normal kernel' { insmod part_gpt insmod search_fs_uuid insmod chain chainloader (hd0,gpt1)/EFI/boot/BSD.BOOTX64.EFI } menuentry 'OpenBSD/amd64 ramdisk kernel' --class os { set root='(hd0,gpt3)' kopenbsd /bsd.rd } Don't forget to run update-grub after editing 40_custom. The gpt1 partition corresponds to the EFI one that any OS using UEFI creates. You can name the BSD bootloader whatever you want with this, and put it in it's own dir if necessary. I have shimx64.efi renamed to bootx64.efi as my grub "preloader". The second menu entry is for a bsd.rd placed in the ext2 /boot partition Linux uses to access it's kernel upon boot from grub. Many thanks to oldlaptop on Freenode for working out the grub2 syntax. Cheers, Noth P.S: Don't CC me, I'm subscribed to the mailing list.
Re: sndiod fallback trouble
> ... but i see no simple & obvious solution that doesn't break current common > use-cases Maybe I'm wrong, but hotplugd comes to my mind. Isn't it possible to run some script(s) at plug/unplug events associated with that USB DAC in order to reconfigure sndiod. Again, I never used hotplugd, but someone my know better ...