On Wed, Jan 21, 2009 at 6:08 AM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2009-01-19, Bryan <bra...@gmail.com> wrote: >> Greetings, >> >> >> I am still having issues with the re(4) interface on my server. I >> mentioned this on the list, and was told that the re(4) fix was in. I >> am running the 13 Jan 2009 snapshot, and I can still reproduce the >> error on a regular basis. It goes like this... >> >> 1. push the power button >> 2. boot openbsd >> 3. panic >> >> panic: config_detach: forced detach of re0 failed (45) >> Stopped at Debugger+0x4: leave > > This is not what is shown in your pictures. >
In noticed that too... I think that I failed to upload that pic. I'll look for it if you really need it. I typed it as I saw it. complete with whitespace... > After enabling javascript to see them (*grumble*) I see the ones > you have look like this: > unfortunately, at work, imageshack, and other pic sharing sites are blocked. So I use what is available to me. > uvm_fault(0xd080c660, 0x12e52000, 0, 3_) -> e > kernel: page fault trap, code=0 > Stopped at apic_vectorset+0x50: movl %esi,apic_maxlevel(,%eax,4) > apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 > ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f > cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42 > main(0,0,0,0,0) at main+0x3a7 > > only process in the table is the swapper. > > >> 4. issue "boot sync" >> 5. system restarts >> 6. re(4) starts with no issues >> <snipped...> >> If someone has any other ideas, please let me know. The dmesg below is >> when the server will come up after a "boot sync" and a warm restart. >> >> I do intend on updating to the latest snapshot (jan 18th) in the next >> few minutes. > > Did that change anything? > > Sometime between the 13th and the 18th, something was fixed and I've not had an issue with the re(4) interface. was going to post a "it got fixed, sorry about the noise, but you beat me to it...
