On May 19, 2009, at 1:44 AM, SAITOH Masanobu wrote:
Hello.The bug had been fixed by if_wm.c rev. 1.173 on -current. It's not pulled up yet. I'm now working other bugs and will be pulled up all of them in nearfuture.
Hi there. I see that this was pulled up into netbsd-5 approximately Mar-21, but it looks like it has not been pulled to netbsd-5-0, even though other things pulled to netbsd-5 more recently have also been pulled to netbsd-5-0.
Does there need to be a specific request for this bug-fix to if_wm to be pulled into netbsd-5-0? I think that should be done.
I'm running off of bouyer's patch now, and it's working just fine, I'll rebuild a netbsd-5 kernel in the next few days and verify that that works, but I don't anticipate any issues...
Thanks.
- Chris
Okay. I was able to compile a GENERIC netbsd-5-0 kernel, and it fails in the same way. The addresses are slightly different than mentioned in my earlier post, but the same error clearly in the same place occurs. As there have been no changes in the netbsd-5-0 branch in the wm driver since netbsd-5-0-RELEASE, this should apply to that release as well.Please, someone let me know if there's any more information I can provide. I am anxious to get this problem located and resolved so that I can update this machine, as the first of many 4.0 machines I plan to upgrade.Thank you. - Chris On May 17, 2009, at 23:07, Chris Ross wrote:From sources updated today, I built the world on an earlier NetBSD 5.0_STABLE i386 system, for i386. I built a custom kernel for my i386 (MP) router, and it doesn't boot successfully.In further testing, it appears that it's the act of simply bringing "up" the wm0 interface[...] I can bring online all of the filesystems, and then simply executing:ifconfig wm0 up causes a panic. Handwritten/copied here it is: uvm_fault(0xcadffd40, 0, 1) -> 0xe fatal page fault in supervisor mode trap type 6 code 0 eip c061788b cs 8 eflags 10286 cr2 0 ilevel 6 kernel: supervisor trap page fault, code=0Stopped in pid 29.1 (ifconfig) at netbsd:wm_tbi_mediachange+0xb: movl 0(%eax),%esi db{0}>I know there have been changes singe 5.0 release that affect wm, but I don't know if 5.0 release works either. I'm going to build a netbsd-5-0 kernel next, but that will take some time to fetch that source tree.NetBSD 4.0_STABLE reports my wm as:wm0 at pci0 dev 13 function 0: Intel i82543GC 1000BASE-X Ethernet, rev. 2wm0: interrupting at ioapic0 pin 17 (irq 11) wm0: 32-bit 33MHz PCI bus wm0: 64 word (6 address bits) MicroWire EEPROM wm0: Ethernet address 00:03:47:0d:eb:86 wm0: 1000baseSX, 1000baseSX-FDX, auto ..and the pcictl dump for this device is attached. Anyone have any idea? Thanks.---------------------------------------------------------- SAITOH Masanobu (masanobu%iij.ad.jp@localhost msaitoh%netbsd.org@localhost)