Re: 4.0 Lockup [Was: 3.9 Lockup]
STeve Andre' wrote: On Tuesday 07 November 2006 22:20, Melameth, Daniel D. wrote: STeve Andre' wrote: On Monday 06 November 2006 22:10, Melameth, Daniel D. wrote: I'm having the same issue with 4.0 -stable--well, a bastardized copy of -stable that also contains ral, cardbus and related changes from -current. I've used more than one fxp card as well as more than one ral card and the issue stays the same--fxp0: warnings and timeouts and, eventually under load or after a few days, the box locks up with no apparent panic and ddb.console=1 provides no help. If I recall correctly, the issue also exists if I replace fxp with xl. It would appear so long as there are two Cardbus cards in this box, this issue occurs--as fxp plus wi is rock solid. How do I troubleshoot this further? [snip] Ugh. This brings back some memories. I'm pretty sure it was a sat pro that I had some cardbus problems with some time ago. I believe I did a bios update, which changed things; better but not perfect. So try that, and look in the bios settings for anything that can tweak the cardbus slots. Given my experiences with this, I'm thinking there is a good chance that your problem lies in the laptop itself. Good luck. Yea, I figured as much/was afraid of that. Thanks for sharing. Thinking on this a little more, you might, just might see a difference between booting up with the cards, and inserting the cards after booting, or some combination of one card in and one card inserted post boot. I dimly remember doing that and wondering what was going on, so that might affect your results. Also change the speed of the system if you can to see what that does. I think you are likely out of luck here, but something truly screwy might help you. Ah, and you mention backporting some of the ral code--have you tried running -current on it? Can't hurt... I'm not interested in having it work if it requires an eclectic combination of add/removing hardware after booting or whatnot. What do you mean by changing the speed of the system? I can try running -current, but I doubt there'll be much change from my -stable--though, yea, it can't hurt. At the end of the day, I might just get another laptop with on-board Ethernet instead and, therefore, drop this routing over Cardbus bus stuff. Thanks, D
Re: 4.0 Lockup [Was: 3.9 Lockup]
On Tuesday 07 November 2006 22:20, Melameth, Daniel D. wrote: STeve Andre' wrote: On Monday 06 November 2006 22:10, Melameth, Daniel D. wrote: I'm having the same issue with 4.0 -stable--well, a bastardized copy of -stable that also contains ral, cardbus and related changes from -current. I've used more than one fxp card as well as more than one ral card and the issue stays the same--fxp0: warnings and timeouts and, eventually under load or after a few days, the box locks up with no apparent panic and ddb.console=1 provides no help. If I recall correctly, the issue also exists if I replace fxp with xl. It would appear so long as there are two Cardbus cards in this box, this issue occurs--as fxp plus wi is rock solid. How do I troubleshoot this further? [snip] Ugh. This brings back some memories. I'm pretty sure it was a sat pro that I had some cardbus problems with some time ago. I believe I did a bios update, which changed things; better but not perfect. So try that, and look in the bios settings for anything that can tweak the cardbus slots. Given my experiences with this, I'm thinking there is a good chance that your problem lies in the laptop itself. Good luck. Yea, I figured as much/was afraid of that. Thanks for sharing. Thinking on this a little more, you might, just might see a difference between booting up with the cards, and inserting the cards after booting, or some combination of one card in and one card inserted post boot. I dimly remember doing that and wondering what was going on, so that might affect your results. Also change the speed of the system if you can to see what that does. I think you are likely out of luck here, but something truly screwy might help you. Ah, and you mention backporting some of the ral code--have you tried running -current on it? Can't hurt... --STeve Andre'
Re: 4.0 Lockup [Was: 3.9 Lockup]
STeve Andre' wrote: On Monday 06 November 2006 22:10, Melameth, Daniel D. wrote: I'm having the same issue with 4.0 -stable--well, a bastardized copy of -stable that also contains ral, cardbus and related changes from -current. I've used more than one fxp card as well as more than one ral card and the issue stays the same--fxp0: warnings and timeouts and, eventually under load or after a few days, the box locks up with no apparent panic and ddb.console=1 provides no help. If I recall correctly, the issue also exists if I replace fxp with xl. It would appear so long as there are two Cardbus cards in this box, this issue occurs--as fxp plus wi is rock solid. How do I troubleshoot this further? [snip] Ugh. This brings back some memories. I'm pretty sure it was a sat pro that I had some cardbus problems with some time ago. I believe I did a bios update, which changed things; better but not perfect. So try that, and look in the bios settings for anything that can tweak the cardbus slots. Given my experiences with this, I'm thinking there is a good chance that your problem lies in the laptop itself. Good luck. Yea, I figured as much/was afraid of that. Thanks for sharing.
4.0 Lockup [Was: 3.9 Lockup]
I'm having the same issue with 4.0 -stable--well, a bastardized copy of -stable that also contains ral, cardbus and related changes from -current. I've used more than one fxp card as well as more than one ral card and the issue stays the same--fxp0: warnings and timeouts and, eventually under load or after a few days, the box locks up with no apparent panic and ddb.console=1 provides no help. If I recall correctly, the issue also exists if I replace fxp with xl. It would appear so long as there are two Cardbus cards in this box, this issue occurs--as fxp plus wi is rock solid. How do I troubleshoot this further? $ dmesg OpenBSD 4.0-stable (GENERIC) #0: Thu Nov 2 21:41:33 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 647 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE real mem = 133656576 (130524K) avail mem = 114528256 (111844K) using 1657 buffers containing 6787072 bytes (6628K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(63) BIOS, date 12/30/99, SMBIOS rev. 2.3 @ 0x7ff (45 entries) bios0: TOSHIBA SATELLITE PRO 4340XDVD apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 100% apm0: AC on, battery charge high, estimated 1:39 hours apm0: flags 20102 dobusy 0 doidle 1 pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xc/0xc000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 S3 Savage/IX-MV rev 0x11 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 5 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 5 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: SAMSUNG MP0402H wd0: 16-sector PIO, LBA48, 38204MB, 78242976 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TOSHIBA, DVD-ROM SD-C2402, 1317 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 5 function 2 Intel 82371AB USB rev 0x01: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered piixpm0 at pci0 dev 5 function 3 Intel 82371AB Power rev 0x03: SMI iic0 at piixpm0 admtemp0 at iic0 addr 0x4e: adm1021 ATT/Lucent LTMODEM rev 0x01 at pci0 dev 7 function 0 not configured vendor Toshiba, unknown product 0x0d01 (class wireless subclass IrDA, rev 0x00) at pci0 dev 9 function 0 not configured cbb0 at pci0 dev 11 function 0 Toshiba ToPIC95B CardBus rev 0x07: irq 11 cbb1 at pci0 dev 11 function 1 Toshiba ToPIC95B CardBus rev 0x07: irq 11 yds0 at pci0 dev 12 function 0 Yamaha 744 rev 0x02: irq 11 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns8250, no fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 20 device 0 cacheline 0x0, lattimer 0x0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 21 device 0 cacheline 0x0, lattimer 0x0 pcmcia1 at cardslot1 biomask ef65 netmask ef65 ttymask ffe7 pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support fxp0 at cardbus0 dev 0 function 0 INTEL(R), PRO/100 CARDBUS II, MBLA3300: INTEL(R) PRO/100 CARDBUS II: irq 11, address 00:a0:c9:bc:ad:ad inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 ral0 at cardbus1 dev 0 function 0 Ralink Technology, Inc., RT2500, 802.11 CardBus Reference Card: irq 11, address 00:0e:3b:07:a2:13 ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 WARNING: / was not properly unmounted ac97: codec id 0x414b4d02 (Asahi Kasei AK4543) ac97: codec features headphone, 18 bit DAC, 18 bit ADC, AKM 3D audio0 at yds0 opl0 at yds0: model OPL3 midi1 at opl0: DS-1 integrated Yamaha OPL3 mpu at yds0 not configured mpu at yds0 not configured mpu at yds0 not configured mpu at yds0 not configured Melameth, Daniel D. wrote: I recently upgraded (via clean install) a machine that was previously running 3.8 and wi in hostap, without incident for the last
Re: 4.0 Lockup [Was: 3.9 Lockup]
On Monday 06 November 2006 22:10, Melameth, Daniel D. wrote: I'm having the same issue with 4.0 -stable--well, a bastardized copy of -stable that also contains ral, cardbus and related changes from -current. I've used more than one fxp card as well as more than one ral card and the issue stays the same--fxp0: warnings and timeouts and, eventually under load or after a few days, the box locks up with no apparent panic and ddb.console=1 provides no help. If I recall correctly, the issue also exists if I replace fxp with xl. It would appear so long as there are two Cardbus cards in this box, this issue occurs--as fxp plus wi is rock solid. How do I troubleshoot this further? [snip] Ugh. This brings back some memories. I'm pretty sure it was a sat pro that I had some cardbus problems with some time ago. I believe I did a bios update, which changed things; better but not perfect. So try that, and look in the bios settings for anything that can tweak the cardbus slots. Given my experiences with this, I'm thinking there is a good chance that your problem lies in the laptop itself. Good luck. --STeve Andre'
