On Tue, Jun 16, 2009 at 2:03 AM, <w...@xoono.net> wrote: > > Hello, > > I ran "pcidump -vv" as instructed and it also rebooted the machine, but it > produced some output before that (which I have attached), and this output > stops in the "Chips and Technologies 65550" section, the last few lines of > the section are missing. >
Can you try pcidump -vv bus:dev:func for each bus:dev:func tuple found in pcidump -v, just to confirm which device is causing the reboot ? > I went back to Xorg and ran it in gdb, and as far as I could tell the reboot > happens in the "pci_system_openbsd_create" function in the libpciaccess > library. > > I hope this helps to narrow it down. > > Thanks a lot again for your help. > > ======== pcidump --v ================== > Domain /dev/pci0: > 0:0:0: Acer Labs M1523 PCI > 0x0000: Vendor ID: 10b9 Product ID: 1521 > 0x0004: Command: 0006 Status ID: 2400 > 0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 1c > 0x000c: BIST: 00 Header Type: 00 Latency Timer: 20 Cache Line Size: > 00 > 0x0010: BAR empty (00000000) > 0x0014: BAR empty (00000000) > 0x0018: BAR empty (00000000) > 0x001c: BAR empty (00000000) > 0x0020: BAR empty (00000000) > 0x0024: BAR empty (00000000) > 0x0028: Cardbus CIS: 00000000 > 0x002c: Subsystem Vendor ID: 10b9 Product ID: 1521 > 0x0030: Expansion ROM Base Address: 00000000 > 0x0038: 00000000 > 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00 > 0:2:0: Acer Labs M1523 ISA > 0x0000: Vendor ID: 10b9 Product ID: 1523 > 0x0004: Command: 000f Status ID: 3200 > 0x0008: Class: 06 Subclass: 01 Interface: 00 Revision: 07 > 0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: > 00 > 0x0010: BAR empty (00000000) > 0x0014: BAR empty (00000000) > 0x0018: BAR empty (00000000) > 0x001c: BAR empty (00000000) > 0x0020: BAR empty (00000000) > 0x0024: BAR empty (00000000) > 0x0028: Cardbus CIS: 00000000 > 0x002c: Subsystem Vendor ID: 10b9 Product ID: 1523 > 0x0030: Expansion ROM Base Address: 00000000 > 0x0038: 00000000 > 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00 > 0:2:1: Acer Labs M5219 UDMA IDE > 0x0000: Vendor ID: 10b9 Product ID: 5219 > 0x0004: Command: 0005 Status ID: 0280 > 0x0008: Class: 01 Subclass: 01 Interface: fa Revision: 20 > 0x000c: BIST: 00 Header Type: 80 Latency Timer: 40 Cache Line Size: > 00 > 0x0010: BAR empty (00000000) > 0x0014: BAR empty (00000000) > 0x0018: BAR empty (00000000) > 0x001c: BAR empty (00000000) > 0x0020: BAR io addr: 0x0000fcf0 > 0x0024: BAR empty (00000000) > 0x0028: Cardbus CIS: 00000000 > 0x002c: Subsystem Vendor ID: 0000 Product ID: 0000 > 0x0030: Expansion ROM Base Address: 00000000 > 0x0038: 00000000 > 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 02 Max Lat: 04 > 0:4:0: TI PCI1130 CardBus > 0x0000: Vendor ID: 104c Product ID: ac12 > 0x0004: Command: 0007 Status ID: 0200 > 0x0008: Class: 06 Subclass: 07 Interface: 00 Revision: 04 > 0x000c: BIST: 00 Header Type: 82 Latency Timer: 40 Cache Line Size: > 04 > 0x0010: Cardbus Control Registers Base Address: 02800000 > 0x0018: Primary Bus: 0 Cardbus Bus: 1 Subordinate Bus: 5 > Cardbus Latency Timer: 00 > 0x001c: Memory Base 0: 00000000 > 0x0020: Memory Limit 0: 00000000 > 0x0024: Memory Base 1: 00000000 > 0x0028: Memory Limit 1: 00000000 > 0x002c: I/O Base 0: 00000000 > 0x0030: I/O Limit 0: 00000000 > 0x0034: I/O Base 1: 00000000 > 0x0038: I/O Limit 1: 00000000 > 0x003c: Interrupt Pin: 01 Line: ff Bridge Control: 0340 > 0x0040: Subsystem Vendor ID: 0000 Product ID: 0000 > 0x0044: 16-bit Legacy Mode Base Address: 000003e1 > 0:4:1: TI PCI1130 CardBus > 0x0000: Vendor ID: 104c Product ID: ac12 > 0x0004: Command: 0007 Status ID: 0200 > 0x0008: Class: 06 Subclass: 07 Interface: 00 Revision: 04 > 0x000c: BIST: 00 Header Type: 82 Latency Timer: 40 Cache Line Size: > 04 > 0x0010: Cardbus Control Registers Base Address: 02801000 > 0x0018: Primary Bus: 0 Cardbus Bus: 6 Subordinate Bus: 10 > Cardbus Latency Timer: 00 > 0x001c: Memory Base 0: 00000000 > 0x0020: Memory Limit 0: 00000000 > 0x0024: Memory Base 1: 00000000 > 0x0028: Memory Limit 1: 00000000 > 0x002c: I/O Base 0: 00000000 > 0x0030: I/O Limit 0: 00000000 > 0x0034: I/O Base 1: 00000000 > 0x0038: I/O Limit 1: 00000000 > 0x003c: Interrupt Pin: 02 Line: ff Bridge Control: 0340 > 0x0040: Subsystem Vendor ID: 0000 Product ID: 0000 > 0x0044: 16-bit Legacy Mode Base Address: 000003e1 > 0:6:0: Chips and Technologies 65550 > 0x0000: Vendor ID: 102c Product ID: 00e0 > 0x0004: Command: 0083 Status ID: 0280 > 0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 05 > 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: > 00 > 0x0010: BAR mem 32bit addr: 0xfd000000 > 0x0014: BAR empty (00000000) > 0x0018: BAR empty (00000000) > 0x001c: BAR empty (00000000) > 0x0020: BAR empty (00000000) > 0x0024: BAR empty (00000000) > 0x0028: Cardbus CIS: 00000000 > 0x002c: Subsystem Vendor ID: 0000 Product ID: 0000 > 0x0030: Expansion ROM Base Address: 00000000 > 0x0038: 00000000 > 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00 > > ================ Xorg -verbose 1000 ========================== > X.Org X Server 1.5.3 > Release Date: 5 November 2008 > X Protocol Version 11, Revision 0 > Build Operating System: OpenBSD 4.5 i386 > Current Operating System: OpenBSD tensa.lan 4.5 GENERIC#1749 i386 > Build Date: 27 February 2009 05:01:11PM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 15 21:43:49 2009 > (++) Using config file: "/etc/X11/xorg.conf" > (==) ServerLayout "X.org Configured" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "Monitor0" > (**) | |-->Device "Card0" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (==) Not automatically adding devices > (==) Not automatically enabling devices > (==) Including the default font path > /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X 11/fonts/OTF,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/100dpi/ ,/usr/X11R6/lib/X11/fonts/75dpi/. > (**) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/, > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > (**) ModulePath set to "/usr/X11R6/lib/modules" > (II) Loader magic: 0x3c01e2e0 > (II) Module ABI versions: > X.Org ANSI C Emulation: 0.4 > X.Org Video Driver: 4.1 > X.Org XInput driver : 2.1 > X.Org Server Extension : 1.1 > X.Org Font Renderer : 0.6 > (II) Loader running on openbsd > (--) Using wscons driver on /dev/ttyC1 in pcvt compatibility mode (version > 3.32) > > > > On Sun, 14 Jun 2009, Matthieu Herrb wrote: > >> On Sat, Jun 13, 2009 at 9:46 PM, <w...@xoono.net> wrote: >>> >>> Hello, >>> >>> I just installed version 4.5 on a very old laptop (Texas Instruments >>> Extensa >>> 605CD), it was happily running 4.2 before. All the hardware seems to be >>> recognised correctly on both versions but I am having a strange problem >>> when >>> trying to configure Xorg, the command "X -configure" reboots the machine, >>> in >>> fact, running X with any parameter reboots the machine. I created a >>> xorg.conf file to test and trying to start X with it produces the same >>> result. >>> >>> I haven't used OpenBSD for very long, I only started with version 4.2 so >>> I >>> am thinking that I am probably missing something simple or something new >>> on >>> 4.5? (I have the machdep.allowaperture=2 in sysctl.conf). >>> >>> I am attaching my sysctl params and my dmesg, I hope someone can give me >>> a >>> hand with this. >>> >>> Thanks very much in advance. >> >> Please also include pcidump -vv output >> >> Can you look if you get something in /var/log/Xorg.0.log after the reboot? >> >> if not, can you set up a serial console, log in as root through it and >> run "script Xorg -verbose 4" >> and send the typescript here ? >> >> Also, try using the "Vesa" driver xorg.conf. It should work, as I >> suspect the breakage is in the xf86-video-chips driver. >> -- >> Matthieu Herrb >> > -- Matthieu Herrb
