John Baldwin wrote:
In kgdb, do 'proc 783', and then 'where' to get a stack trace of the thread
that did the wrong thing. (The thread that panics is just an innocent
victim that bumped into the miscreant.)
(kgdb) proc 783
(kgdb) where
#0 0xc065f2c7 in sched_switch (td=0xc283e900, newtd=0xc2
On Tuesday 01 August 2006 11:58, José M. Fandiño wrote:
> Hello,
>
> I get a panic each time I try to create an access point
> with the ural driver.
>
> only by running this commands the machine panic:
> kldload bridge
> sysctl net.link.ether.bridge.enable=1
> net.link.ether.bridge_cfg="rl0,ural0
2 matches
Mail list logo
