| Summary: | 6-STABLE crashes when being online via modem (Fujitsu Siemens Amilo A notebook) | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Hans-Michael Gerhards <hm-gerhards> |
| Component: | i386 | Assignee: | freebsd-i386 (Nobody) <i386> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 6.1-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Hans-Michael Gerhards
2006-05-30 15:50:19 UTC
I appear to be experiencing the same problem as reported in this bug report. I've posted what I could starting at: http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/140919.html Hi, Put debug.mpsafenet=0 into your /boot/loader.conf. I believe it is for workaround. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ Well, I've set the tunable as suggested, configured KPPP and am using it now. So far, no problem, but I haven't been online for long either, so time will tell if thats the problem. I came across this which states that if you are using pppd, then you need to set the tunable to 0, if I read it correctly. http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-08/2745.html This all makes me wonder, what is the advantage to having the debug.mpsafenet set to 1 as default, anyway, if the computer only has a single processor? Shouldn't the installer be smart enough to detect if the computer is single or multiprocessor, and set the tunable accordingly, at least until ALL of the network features are made MPSAFE so that it is no longer an issue? And, when installing FreeBSD 6.2, the kernel that booted from the install CD was GENERIC, but after the installation, the bootup showed that the kernel being used was SMP. Being that my computer is a single processor, shouldn't it default to the GENERIC kernel after installation, unless I request otherwise? Thanks, Joe Well, I'm sorry to say that this suggested workaround didn't fix the spontaneous reboot issue for me, although I was able to spend several hours connected while using KPPP before problems. In the dialup session in which the problem had occurred, I'd been online for about an hour which was spent downloading latest ports snapshot via portsnap. I left the computer after about an hour of downloading, and when I returned a while later, there it sat staring at me with a login prompt. It had spontaneously rebooted! I was using KPPP when this happened, so also using pppd. Joe State Changed From-To: open->feedback Hello is this still a problem on recent versions of FreeBSD? State Changed From-To: feedback->closed Feedback timeout |