cause of reboot
Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org smime.p7s Description: S/MIME cryptographic signature
Re: cause of reboot
On Mon, 30 Sep 2013 17:24:18 +0300 Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ That's likely something in the daily run going wrong, try disabling items in there one by one (by editing /etc/periodic.conf - which probably doesn't yet exist so create it and look in /etc/defaults/periodic.conf for details) until you get through a night without a reboot. Then the next step is to figure out why whatever is crashing the system does so, but first let's find out what. -- Steve O'Hara-Smith st...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
And /etc/ ? And /var/cron ? On Sep 30, 2013, at 11:00, Emre Çamalan mail...@yandex.com wrote: Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org smime.p7s Description: S/MIME cryptographic signature
Re: cause of reboot
Also . . . grep -ri . . . On Sep 30, 2013, at 11:06, Jason Hellenthal jhellent...@dataix.net wrote: And /etc/ ? And /var/cron ? On Sep 30, 2013, at 11:00, Emre Çamalan mail...@yandex.com wrote: Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org smime.p7s Description: S/MIME cryptographic signature
Re: cause of reboot
On 9/30/13 11:08 PM, Jason Hellenthal wrote: Also . . . grep -ri . . . On Sep 30, 2013, at 11:06, Jason Hellenthal jhellent...@dataix.net wrote: And /etc/ ? And /var/cron ? On Sep 30, 2013, at 11:00, Emre Çamalan mail...@yandex.com wrote: Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org Firstly, does this machine have the kernel debugger installed? if not then a kernel page fault will look like a reboot. if you know when this is going to occur, then I suggest that you set up some logging of every new process run, to a second machine, or possibly you might just ssh int the machine and leave 'top' running when it reboots you shoud get a snapshot of what's going on. you could just rename 'reboot' and see if it still happens. If not, then replace reboot (and friends) with a script that reports who called it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Le Mon, 30 Sep 2013 17:24:18 +0300, Emre Çamalan mail...@yandex.com a écrit : Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ The last time It happened (one month ago) to me it was the hard disk (periodic scripts read a large part of the disk). If the disk is smart capable try a full test with smartctl (sysutils/smartmontools) HTH, regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Patrick Lamaiziere wrote: [snip] I looked last command, reboot ~ ~ AM 03.15 ~ The last time It happened (one month ago) to me it was the hard disk (periodic scripts read a large part of the disk). If the disk is smart capable try a full test with smartctl (sysutils/smartmontools) My gateway/firewall/mail/ids router box at home has 2 GB RAM in it, so normally it has enough extra room that nothing ever pushes over into swap with one exception: the periodic run at 0300. It is generally never more than just a few kilobytes, but I find it slightly surprising nonetheless. If a sector (or more) on the drive that is backing the swap partition has gone bad it might not even be noticeable until something pages out to swap (like my 0300 periodic run). If the drive is a WD the 'Quick' test using the manufacturers' wddiags utility should spot it, and is non-destructive. I have occasionally seen the full test not destroy data - but I wouldn't count on it being non- destructive. However, as long as the remap area isn't full the long test will repair the drive by relocating and mapping out the bad spot. When this silent fading away of magnetic media occurs wrt to higher-end RAID controllers the scrub function in the controller BIOS is where you would want to go. The other problem relative to this that I've run into is the apple before the cart syndrome around backups. I have seen dump fail to allow for backing up data prior to using the full wddiags to repair a drive so you kinda get stuck. If the full test is going to wipe the drive and you can't generate a fresh current backup you're stuck only being able to restore whatever is the last good backup you have on hand. Wouldn't surpise me at all if this were to turn out to be the drive just recently grew one or more bad spots. A bad spot or few on an old drive that gets repaired I might continue to use the drive for a while, maybe even for like a year time-frame wise. If 2 months later it starts growing more bad spots the drive goes in the rubbish bin. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
kpn...@pobox.com wrote: [snip] While we're throwing ideas onto the table let me mention power supplies. Power supplies and hard drives are in a race to see which one will fail first. It may be that the power supply is marginal and added load from the drives being hit hard may send it over the edge. How heavily loaded is the machine in question? Absolute and total agreement with this. As they age and the filter caps leak and dry out more it will eventually become apparent. But in the meantime the output DC can just about meet spec up until really loaded. Then the ripple becomes so excessive it's not quite DC any longer. You can clearly see it using an oscilloscope. The 0300 AM periodic does hammer a machine enough to possibly push a marginal power supply over the edge. I once had a box where the RAM chips would sing with a high-pitched whistle only during the 0300 periodic run. It sounded just like the horizontal output on a television right before destruction. :-) [snip] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
On Mon, 30 Sep 2013 20:32:39 -0400, Michael Powell wrote: kpn...@pobox.com wrote: [snip] While we're throwing ideas onto the table let me mention power supplies. Power supplies and hard drives are in a race to see which one will fail first. It may be that the power supply is marginal and added load from the drives being hit hard may send it over the edge. How heavily loaded is the machine in question? Absolute and total agreement with this. The idea of a hardware problem looks more and more obvious here. A software configuration problem could be located by diff'ing the currently used files against stock files, or by checking the logs of a versioning system (if you use one to track your local configuration file changes, for example in a CVS reposi- tory). It could be a matter of power (by more than usual drain when the machine is heavily loaded), but also a file system inconsis- tency is possible. In case the machine is using a background fsck that silently fails to deal with a specific damage, using background_fsck=NO in /etc/rc.conf to _definitely_ bring the file systems up _clean_ prior to multi-user mode booting would probably be a good idea. Using smartctl to check the hard disks SMART data would make sure the disk is not dying (and the reboot is an effect of that). Monitoring the server when (or while) it reboots would surely be interesting. Maybe open some sessions to have a close look at programs like top, systat -v and mbmon (to check for temperatures and voltages) - and when run at 1 second intervals, it should be possible to obtain a good system status diagram of the last state before reboot, when the connection drops. I once had a box where the RAM chips would sing with a high-pitched whistle only during the 0300 periodic run. It sounded just like the horizontal output on a television right before destruction. :-) I have heared something comparable from a graphics card when developing some OpenGL demo stuff. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re-add lost device entries without a reboot; troubleshoot RAID card
On Sun, Jul 14, 2013 at 9:38 PM, Jason Birch jbi...@jbirch.net wrote: I have several hard drives running through an M1015 flashed to think it's an LSI 9211-8i IT. I've been running them successfully for the last three months through mps(4) as part of a raidz pool, but had the pool drop to a degraded state when /dev/da0 (and associated gpt device) disappeared after some apparent errors. After a reboot, I noticed that the disk that disappeared - da0 - was successfully probed and resilvered back in to the existing pool. I ran a short SMART self test and everything was fine. I ran a long SMART self test and the drive disappeared again towards the end of the scan (I didn't get a chance to view the results) I'd like to know if there's a way to suggest to 're-probe' connections to see if there are any devices that can be reconnected. It's clear that the drive is still around and at least partially responsive - is there a way I can online this disk, as just a device in its own right, such that I can finishing running the SMART diagnostics? I've read some old mentions of mps not being the most stable thing under load, but the mentions are over a year old. The initial failure happened right at the time the daily periodic was running (Which includes a check for negative permissions on the zfs partition) and the second failure was during a SMART long test, so I guess there's potential for load there. How might I go about diagnosing whether this is just the drive or possibly the card itself? I suppose the obvious Move it off the raid card is probably a good first start... $ uname -a FreeBSD blackfyre 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 dmesg output when things started going south the first time: Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 5a ca e4 98 0 0 8 0 length 4096 SMID 563 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec 58 0 0 8 0 length 4096 SMID 557 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 5a d7 a7 f8 0 0 8 0 length 4096 SMID 889 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec 60 0 0 8 0 length 4096 SMID 61 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec 60 0 0 8 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec a0 0 0 8 0 Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Device picked up again on restart: Jul 14 15:04:15 blackfyre kernel: da0 at mps0 bus 0 scbus0 target 0 lun 0 Jul 14 15:04:15 blackfyre kernel: da0: ATA ST3000DM001-9YN1 CC4H Fixed Direct Access SCSI-6 device Jul 14 15:04:15 blackfyre kernel: da0: 600.000MB/s transfers Jul 14 15:04:15 blackfyre kernel: da0: Command Queueing enabled Jul 14 15:04:15 blackfyre kernel: da0: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C) Device going south a second time: Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): READ(10). CDB: 28 0 d 7d 76 10 0 0 38 0 Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected) Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): READ(10). CDB: 28 0 d 94 b8 20 0 0 38 0 Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected) Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Culminating in the device being removed from /dev/: Jul 14 18:39:17 blackfyre kernel
Re: Re-add lost device entries without a reboot; troubleshoot RAID card
On Mon, Jul 15, 2013 at 7:18 PM, Jason Birch jbi...@jbirch.net wrote: I should note that `camcontrol rescan 0` (Or `camcontrol rescan all`) won't find da0. For those who stumble upon this thread later looking for answers, I'm almost certain the problem I'm seeing is the same as described in http://forums.freebsd.org/showthread.php?t=28252. I'm going to work through some of that to see if I can fix my problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re-add lost device entries without a reboot; troubleshoot RAID card
I have several hard drives running through an M1015 flashed to think it's an LSI 9211-8i IT. I've been running them successfully for the last three months through mps(4) as part of a raidz pool, but had the pool drop to a degraded state when /dev/da0 (and associated gpt device) disappeared after some apparent errors. After a reboot, I noticed that the disk that disappeared - da0 - was successfully probed and resilvered back in to the existing pool. I ran a short SMART self test and everything was fine. I ran a long SMART self test and the drive disappeared again towards the end of the scan (I didn't get a chance to view the results) I'd like to know if there's a way to suggest to 're-probe' connections to see if there are any devices that can be reconnected. It's clear that the drive is still around and at least partially responsive - is there a way I can online this disk, as just a device in its own right, such that I can finishing running the SMART diagnostics? I've read some old mentions of mps not being the most stable thing under load, but the mentions are over a year old. The initial failure happened right at the time the daily periodic was running (Which includes a check for negative permissions on the zfs partition) and the second failure was during a SMART long test, so I guess there's potential for load there. How might I go about diagnosing whether this is just the drive or possibly the card itself? I suppose the obvious Move it off the raid card is probably a good first start... $ uname -a FreeBSD blackfyre 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 dmesg output when things started going south the first time: Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 5a ca e4 98 0 0 8 0 length 4096 SMID 563 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec 58 0 0 8 0 length 4096 SMID 557 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 5a d7 a7 f8 0 0 8 0 length 4096 SMID 889 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec 60 0 0 8 0 length 4096 SMID 61 terminated ioc 804b scsi 0 state c xfer 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec 60 0 0 8 0 Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) Jul 11 03:07:20 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): WRITE(10). CDB: 2a 0 23 55 ec a0 0 0 8 0 Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) Jul 11 03:07:25 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Device picked up again on restart: Jul 14 15:04:15 blackfyre kernel: da0 at mps0 bus 0 scbus0 target 0 lun 0 Jul 14 15:04:15 blackfyre kernel: da0: ATA ST3000DM001-9YN1 CC4H Fixed Direct Access SCSI-6 device Jul 14 15:04:15 blackfyre kernel: da0: 600.000MB/s transfers Jul 14 15:04:15 blackfyre kernel: da0: Command Queueing enabled Jul 14 15:04:15 blackfyre kernel: da0: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C) Device going south a second time: Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): READ(10). CDB: 28 0 d 7d 76 10 0 0 38 0 Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected) Jul 14 18:36:56 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): READ(10). CDB: 28 0 d 94 b8 20 0 0 38 0 Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): CAM status: SCSI Status Error Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): SCSI status: Check Condition Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected) Jul 14 18:37:02 blackfyre kernel: (da0:mps0:0:0:0): Retrying command (per sense data) Culminating in the device being removed from /dev/: Jul 14 18:39:17 blackfyre kernel: (noperiph:mps0:0:0:0): SMID 3 finished recovery after aborting TaskMID 667 Jul 14 18:39:17 blackfyre kernel: mps0: mpssas_free_tm releasing simq Jul 14 18:39:22
Re: Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote: Just guessing from what I see - The panic is No usable event timer found! . Hi Shane, Thanks much for the hints you sent me. Since I'm pretty swamped with work it took me a couple of days before I could go on with my tests. Can you boot into single user mode? Nope - freezes at the exact same point during boot. what does sysctl kern.eventtimer.choice show? Well - nothing to be honest: variable 'kern.eventtimer.choice' not found Have you tried kern.eventtimer.periodic=0 or other values for kern.eventtimer.timer? With kern.eventtimer.periodic=0 - same result. What other values would be valid for kern.eventtimer.timer? Is the panic the same without the loader adjustments? Yes, absolutely the same. Does it boot 8.3 ? Haven't tried this, since I need to go to 9.1 on this system anyway. Besides that the server is in a remote DC so changing disks is not an easy thing to do. -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
On 14/06/2013 23:33, Ewald Jenisch wrote: On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote: Just guessing from what I see - The panic is No usable event timer found! I did say just guessing and thought someone more knowledgeable may have spoken by now. One thing I did find - there is a freebsd-proliant mailing list that may be more helpful than here. Thanks much for the hints you sent me. Since I'm pretty swamped with work it took me a couple of days before I could go on with my tests. Can you boot into single user mode? Nope - freezes at the exact same point during boot. what does sysctl kern.eventtimer.choice show? Well - nothing to be honest: variable 'kern.eventtimer.choice' not found Wondering if the system needs to be running to see that. Have you tried kern.eventtimer.periodic=0 or other values for kern.eventtimer.timer? With kern.eventtimer.periodic=0 - same result. What other values would be valid for kern.eventtimer.timer? That's where the eventtimer.choice comes in. As an example on my asus mb I get kern.eventtimer.choice: LAPIC(600) HPET(550) HPET1(440) HPET2(440) HPET3(440) HPET4(440) i8254(100) RTC(0) I thought in single user mode you could see your list of available options. Is the panic the same without the loader adjustments? Yes, absolutely the same. Does it boot 8.3 ? Haven't tried this, since I need to go to 9.1 on this system anyway. Besides that the server is in a remote DC so changing disks is not an easy thing to do. If 8.3 boots it then you can patch and compile your own kernel that supports your hardware. Being remote it may not be helpful unless you can have some indication that it will boot 8.3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
Hi, Several days ago I got a HP Proliant DL580 G5 that I wanted to install FreeBSD 9.1 (64bit) on - till now without any success :-(. Symptoms: Upon booting off the installation DVD the system freezes (when running the installation non-verbose) or installation stops with a panic followed by an automatic reboot. Here's what I tried so far: o) Updating BIOS, array-controller, iLO to the latest version o) Booting the installation DVD in safe-mode o) Booting the installatino DVD verbose mode o) Escaping to the loader prompt, entering kern.eventtimer.periodic=1 kern.eventtimer.timer=LAPIC and booting the install-DVD with these settings (I once could boot and older HP-server using these settings, so I tried them here too) Nothing of this helped - the system just freezes/crashes in an early stage even before the actual installer starts. I uploaded screenshots to a server so you can see what's happening: http://www.jenisch.at/HP-Proliant-DL580-G5-Installation-Crash/FreeBSD-install-crash-HP-Proliant-DL580-G5-01.jpg http://www.jenisch.at/HP-Proliant-DL580-G5-Installation-Crash/FreeBSD-install-crash-HP-Proliant-DL580-G5-02.jpg http://www.jenisch.at/HP-Proliant-DL580-G5-Installation-Crash/FreeBSD-install-crash-HP-Proliant-DL580-G5-03.jpg http://www.jenisch.at/HP-Proliant-DL580-G5-Installation-Crash/FreeBSD-install-crash-HP-Proliant-DL580-G5-04.jpg (FreeBSD-install-crash-HP-Proliant-DL580-G5-04.jpg shows the actual panic/stacktrace) Anybody seen this before? Any known cure against this problem? Thanks much in advance for any clue, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
On 06/06/2013 23:41, Ewald Jenisch wrote: Here's what I tried so far: o) Updating BIOS, array-controller, iLO to the latest version o) Booting the installation DVD in safe-mode o) Booting the installatino DVD verbose mode o) Escaping to the loader prompt, entering kern.eventtimer.periodic=1 kern.eventtimer.timer=LAPIC and booting the install-DVD with these settings (I once could boot and older HP-server using these settings, so I tried them here too) (FreeBSD-install-crash-HP-Proliant-DL580-G5-04.jpg shows the actual panic/stacktrace) Just guessing from what I see - The panic is No usable event timer found! Have you tried kern.eventtimer.periodic=0 or other values for kern.eventtimer.timer? Is the panic the same without the loader adjustments? Can you boot into single user mode? what does sysctl kern.eventtimer.choice show? Does it boot 8.3 ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hang on reboot with ZIL on SSD
Hi, I have a quite big server that I am tuning with FreeNAS running on It. It is based on an Intel Server and uses an Adaptec Controler ASR-6805 for a potential 12 disks pool (only 6 deployed for the moment). I have two more SSD disks intended for the ZIL cache. Connected directly on the mother board. It comes equipped with 32Gb of memory ECC. The system is installed on a specific dongle on the mother board (4Gb SLC dongle). The system is happy (= reboots without stopping at the real end of the reboot) as long as there is no SSD involved for the ZIL. As soon as the SSD are running, system freezes (or at least can't proceed with the reboot). It really freezes at the real end of the reboot after : Syncing disks, vnodes remaining…*0 0 0 0 done All buffers synced. Uptime: 3d4h12min I have to manually Power-Cycle the unit for It to complete the reboot. Here is the output of the dmesg : [root@freenas] ~# dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.3-RELEASE-p5 #2 r244158M: Wed Dec 12 10:04:42 PST 2012 r...@build.ixsystems.com:/home/jpaetzel/8.3.0/os-base/amd64/usr/home/jpaetzel/8.3.0/FreeBSD/src/sys/FREENAS.amd64 amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz (2394.25-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206d7 Family = 6 Model = 2d Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x17bee3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,AVX AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 34359738368 (32768 MB) avail memory = 33071357952 (31539 MB) ACPI APIC Table: INTEL S2600GZ FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 WARNING: VIMAGE (virtualized network stack) is a highly experimental feature. ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20101013/tbfadt-707) ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard kbd1 at kbdmux0 hpt27xx: RocketRAID 27xx controller driver v1.0 (Dec 12 2012 10:04:31) cryptosoft0: software crypto on motherboard aesni0: AES-CBC,AES-XTS on motherboard acpi0: INTEL S2600GZ on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, 9d000 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 47 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 47 at device 1.1 on pci0 pci2: ACPI PCI bus on pcib2 igb0: Intel(R) PRO/1000 Network Connection version - 2.3.1 port 0x1060-0x107f mem 0xd216-0xd217,0xd21b-0xd21b3fff irq 27 at device 0.0 on pci2 igb0: Using MSIX interrupts with 5 vectors igb0: Ethernet address: 00:1e:67:54:9f:cd igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb1: Intel(R) PRO/1000 Network Connection version - 2.3.1 port 0x1040-0x105f mem 0xd214-0xd215,0xd21a-0xd21a3fff irq 30 at device 0.1 on pci2 igb1: Using MSIX interrupts with 5 vectors igb1: Ethernet address: 00:1e:67:54:9f:ce igb1: [ITHREAD] igb1: [ITHREAD] igb1: [ITHREAD] igb1: [ITHREAD] igb1: [ITHREAD] igb2: Intel(R) PRO/1000 Network Connection version - 2.3.1 port 0x1020-0x103f mem 0xd212-0xd213,0xd219-0xd2193fff irq 28 at device 0.2 on pci2 igb2: Using MSIX interrupts with 5 vectors igb2: Ethernet address: 00:1e:67:54:9f:cf igb2: [ITHREAD] igb2: [ITHREAD] igb2: [ITHREAD] igb2: [ITHREAD] igb2: [ITHREAD] igb3: Intel(R) PRO/1000 Network Connection version - 2.3.1 port 0x1000-0x101f mem 0xd210-0xd211,0xd218-0xd2183fff irq 29 at device 0.3 on pci2 igb3: Using MSIX interrupts with 5 vectors igb3: Ethernet address: 00:1e:67:54:9f:d0 igb3: [ITHREAD] igb3: [ITHREAD] igb3: [ITHREAD] igb3: [ITHREAD] igb3: [ITHREAD] pcib3: ACPI PCI-PCI bridge irq 47 at device 2.0 on pci0 pci4: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge irq 47 at device 2.2 on pci0 pci5: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 3.0 on pci0 pci6: ACPI PCI bus on pcib5 aacu0: Adaptec RAID Controller mem
Does your 9.1-STABLE still hang on reboot?
Hi. I am talking about this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=172952cat=%20jb It should be fixed in STABLE, but I want to make sure it's safe to upgrade my 9.0 systems to 9.1-STABLE now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
reboot after removing ipv6 ?
Hello Do I have to reboot a server after unvalidating IPv6 in /etc/rc.conf ? I seems to use /etc/rc.d/netif restart is not suffisant Thank you ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reboot after removing ipv6 ?
Frank Bonnet f.bonnet at esiee.fr writes: Hello Do I have to reboot a server after unvalidating IPv6 in /etc/rc.conf ? I seems to use /etc/rc.d/netif restart is not suffisant Use 'netstat' to see what service(s) listen for ipv6 traffic and restart them. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
lagg interface not created at reboot ( 9.0 )
hello I use the lagg feature on a server and it seems the lagg pseudo interface is not created when the machine reboots , the server runs 9.0-p3 here is the incriminated part of the /etc/rc.conf file ifconfig_bce2=up ifconfig_bce3=up cloned_interface=lagg0 ifconfig_lagg0= laggproto lacp laggport bce2 laggport bce3 ipv4_addrs_lagg0= xxx.xxx.xxx.xxx/24 defaultrouter=xxx.xxx.xxx.xxx Note : if I create manually the lagg0 interface everything starts well ... thanks for any info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: lagg interface not created at reboot ( 9.0 )
On 2 Nov 2012, at 10:56, Frank Bonnet f.bon...@esiee.fr wrote: hello I use the lagg feature on a server and it seems the lagg pseudo interface is not created when the machine reboots , the server runs 9.0-p3 here is the incriminated part of the /etc/rc.conf file ifconfig_bce2=up ifconfig_bce3=up cloned_interface=lagg0 ifconfig_lagg0= laggproto lacp laggport bce2 laggport bce3 ipv4_addrs_lagg0= xxx.xxx.xxx.xxx/24 defaultrouter=xxx.xxx.xxx.xxx Note : if I create manually the lagg0 interface everything starts well ... thanks for any info cloned_interfaces , notice the plural. You're using cloned_interface, you're missing the S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ppp connection goes down - requires reboot
Lately I have a problem where the ppp connection goes down. Watching the log I see the following; Jul 12 09:54:58 3s1 ppp[30841]: tun0: Phase: deflink: Connected! Jul 12 09:54:58 3s1 ppp[30841]: tun0: Phase: deflink: opening - dial Jul 12 09:54:58 3s1 ppp[30841]: tun0: Phase: deflink: dial - carrier Jul 12 09:55:12 3s1 ppp[31114]: Phase: Using interface: tun0 Jul 12 09:55:12 3s1 ppp[31114]: Phase: deflink: Created in closed state Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: disable ipv6cp Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set dial Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set login Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 209.161.205.12 206.221.248.4 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.2/0 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: add default HISADDR Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: nat enable yes Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set device PPPoE:fxp0 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set mru 1492 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set mtu 1492 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set authname [login was here] Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set authkey Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set log Phase tun command Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: disable ipv6cp Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set dial Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set login Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 209.161.205.12 206.221.248.4 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.2/0 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: add default HISADDR Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: nat enable yes Jul 12 09:55:12 3s1 ppp[31115]: tun0: Phase: PPP Started (ddial mode). Jul 12 09:55:12 3s1 ppp[31115]: tun0: Phase: bundle: Establish Jul 12 09:55:12 3s1 ppp[31115]: tun0: Phase: deflink: closed - opening Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: Connected! Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: opening - dial Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: dial - carrier Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Disconnected! Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: carrier - hangup Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: 0 packets in, 0 packets out Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Thu Jul 12 09:55:13 2012 Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: hangup - opening Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Enter pause (30) for redialing. I shutdown ppp and restart it with no luck. I shutoff modem and reboot it and wait for connection light to go solid - still no go. I called ISP and they say there is no problem. I try to login to the ISP with a windows box and am successful. Having no luck connecting with my server, I reboot, and all is fine. What could it be about rebooting the server that allows connection where otherwise it is not possible? Any ideas where I can look for answers? my ppp.conf follows; default: # or name_of_service_provider set device PPPoE:fxp0 # replace xl1 with your ethernet device set mru 1492 set mtu 1492 set authname *** set authkey *** set log Phase tun command # you can add more detailed logging if you wish disable ipv6cp set dial set login set ifaddr 209.161.205.12 206.221.248.4 set ifaddr 10.0.0.1/0 10.0.0.2/0 add default HISADDR nat enable yes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ppp connection goes down - requires reboot
On 7/12/2012 10:18 AM, David Banning wrote: Lately I have a problem where the ppp connection goes down. Watching the log I see the following; Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: opening - dial Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: dial - carrier Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Disconnected! Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: carrier - hangup Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out 5 seconds seems like a pretty tight for it to give up. Do you have any other defaults in your ppp.conf not shown below ? also add enable echo disable vjcomp set lqrperiod 10 set cd 10 and when its not working, try tcpdump -nei fxp0 You should see responses to your PADI requests from the remote BAS. Also get rid of the 209.161.205.12 line. Typically your ISP will assign you the static IP out of RADIUS and you dont need to specify it. ---Mike I shutdown ppp and restart it with no luck. I shutoff modem and reboot it and wait for connection light to go solid - still no go. my ppp.conf follows; default: # or name_of_service_provider set device PPPoE:fxp0 # replace xl1 with your ethernet device set mru 1492 set mtu 1492 set authname *** set authkey *** set log Phase tun command # you can add more detailed logging if you wish disable ipv6cp set dial set login set ifaddr 209.161.205.12 206.221.248.4 set ifaddr 10.0.0.1/0 10.0.0.2/0 add default HISADDR nat enable yes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
system reboot yielding no coredump
Hi all. Has anyone else seen this: Feb 9 14:41:33 beeb kernel: interrupt total Feb 9 14:41:33 beeb kernel: irq18: ehci0 uhci5+ 325 Feb 9 14:41:33 beeb kernel: irq19: uhci2 uhci4 5180 Feb 9 14:41:33 beeb kernel: irq23: uhci3 ehci1 78296 Feb 9 14:41:33 beeb kernel: cpu0:timer 87480961 Feb 9 14:41:33 beeb kernel: irq256: igb0:que 0 4233015 Feb 9 14:41:33 beeb kernel: irq257: igb0:que 1 3164805 Feb 9 14:41:33 beeb kernel: irq258: igb0:que 2 3230196 Feb 9 14:41:33 beeb kernel: irq259: igb0:que 3 3149873 Feb 9 14:41:33 beeb kernel: irq260: igb0:que 4 3120911 Feb 9 14:41:33 beeb kernel: irq261: igb0:que 5 3207821 Feb 9 14:41:33 beeb kernel: irq262: igb0:que 6 3135338 Feb 9 14:41:33 beeb kernel: irq263: igb0:que 7 3237378 Feb 9 14:41:33 beeb kernel: irq264: igb0:link 2 Feb 9 14:41:33 beeb kernel: irq274: mpt034436250 Feb 9 14:41:33 beeb kernel: cpu1:timer 8585682 Feb 9 14:41:33 beeb kernel: cpu12:timer 10785198 Feb 9 14:41:33 beeb kernel: cpu6:timer 6794891 Feb 9 14:41:33 beeb kernel: cpu13:timer 6626277 Feb 9 14:41:33 beeb kernel: cpu7:timer 13703957 Feb 9 14:41:33 beeb kernel: cpu11:timer 8628910 Feb 9 14:41:33 beeb kernel: cpu5:timer 7938263 Feb 9 14:41:33 beeb kernel: cpu14:timer 6264729 Feb 9 14:41:33 beeb kernel: cpu4:timer 14017666 Feb 9 14:41:33 beeb kernel: cpu10:timer 18995834 Feb 9 14:41:33 beeb kernel: cpu9:timer 9905748 Feb 9 14:41:33 beeb kernel: cpu2:timer 23572337 Feb 9 14:41:33 beeb kernel: cpu8:timer 29507301 Feb 9 14:41:33 beeb kernel: cpu3:timer 9653985 Feb 9 14:41:33 beeb kernel: cpu15:timer 5084039 Feb 9 14:41:33 beeb kernel: Total 328545171 Feb 9 14:41:33 beeb kernel: KDB: stack backtrace: Feb 9 14:41:33 beeb kernel: #0 0x8038d458 at kdb_backtrace+0x58 Feb 9 14:41:33 beeb kernel: #1 0x80315b4b at watchdog_fire+0x8b Feb 9 14:41:33 beeb kernel: #2 0x80315e10 at hardclock_anycpu+0x2a0 Feb 9 14:41:33 beeb kernel: #3 0x80583278 at handleevents+0xd8 Feb 9 14:41:33 beeb kernel: #4 0x80583e36 at timercb+0x2d6 Feb 9 14:41:33 beeb kernel: #5 0x805aec46 at lapic_handle_timer+0xb6 Feb 9 14:41:33 beeb kernel: #6 0x80557f2c at Xtimerint+0x8c Feb 9 14:41:33 beeb kernel: #7 0x80dc8e53 at kcs_wait_for_obf+0x83 Feb 9 14:41:33 beeb kernel: #8 0x80dc935d at kcs_read_byte+0x2d Feb 9 14:41:33 beeb kernel: #9 0x80dc91ce at kcs_loop+0x34e Feb 9 14:41:33 beeb kernel: #10 0x80331d36 at fork_exit+0x76 Feb 9 14:41:33 beeb kernel: #11 0x8055790e at fork_trampoline+0xe I can't get a full dump for some reason unknown. This happens on RELENG_9_0. Feb 9 14:46:56 beeb kernel: CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2394.05-MHz K8-class CPU) Feb 9 14:46:56 beeb kernel: Origin = GenuineIntel Id = 0x206c2 Family = 6 Model = 2c Stepping = 2 Feb 9 14:46:56 beeb kernel: Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH ,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Feb 9 14:46:56 beeb kernel: Features2=0x29ee3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA, SSE4.1,SSE4.2,POPCNT,AESNI Feb 9 14:46:56 beeb kernel: AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM Feb 9 14:46:56 beeb kernel: AMD Features2=0x1LAHF Feb 9 14:46:56 beeb kernel: TSC: P-state invariant, performance statistics What can I do in such case? How can I create a goot dump to inspect it? -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
On Sat, 16 Jul 2011 22:40:19 -0400, Aryeh Friedman wrote: Is there any way to force a complete power down and then reset of a i386 without physically being present? I'm not fully sure what you mean by reset in terms that it happens _after_ powering down. When a machine is powered down (i. e. switched off), it's implicitely a reset - compare to pressing the RESET button which will keep the system powered on, but will perform a (very hard) reset. Allow me to point you to the following manpages: man shutdown man reboot man init A problem will be: How to power a machine back on that has been powered off? I assume you don't want the hard reset, you want to perform a clean shutdown first, followed by a powering down, and THEN power the machine back up. That's quite easy, although you need something more than just onboard means. I may introduce a (quite stupid) solution I invented many years ago: Prior to performing the shutdown -p time command, you access one of the parallel port's lines in order to start a timer (a quite basic transistor + relay is sufficient). This timer runs at least as long as the shutdown needs in average. Let's assume the shutdown needs (including all timeouts and wait states) 5 minutes. After those 5 minutes, the timer generates a pressing of the machine's power button, which means it will power on again. It's comparable to C. E. Shannon's Ultimate Machine in some regards. :-) Of couse, this approach can be used even to switch on AT systems which (unlike ATX) have a real power switch. This switch is then replaced by a self-supporting relay system that can be externally triggered (as those systems can't reflect the -p option of shutdown, just -h is possible). I hope this is a little inspiration about what's possible if you're willing to get your hands dirty. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
In the last episode (Jul 16), Aryeh Friedman said: Is there any way to force a complete power down and then reset of a i386 without physically being present? You haven't said what about an ordinary shutdown -r isn't satisfactory, but we have an iboot gizmo http://dataprobe.com/remote-reboot.html that we use on a (non-FreeBSD) server that hangs from time to time. WOL also works. Daniel Feenberg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
I'd feel better about the company if they used English correctly and didn't have a bunch of HTML bombs. On Jul 17, 2011, at 6:11 AM, Daniel Feenberg wrote: In the last episode (Jul 16), Aryeh Friedman said: Is there any way to force a complete power down and then reset of a i386 without physically being present? You haven't said what about an ordinary shutdown -r isn't satisfactory, but we have an iboot gizmo http://dataprobe.com/remote-reboot.html that we use on a (non-FreeBSD) server that hangs from time to time. WOL also works. Daniel Feenberg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to force a hard reboot remotely
Is there any way to force a complete power down and then reset of a i386 without physically being present? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
On Sun, Jul 17, 2011 at 2:40 AM, Aryeh Friedman aryeh.fried...@gmail.com wrote: Is there any way to force a complete power down and then reset of a i386 without physically being present? ___ Sure! If I understand your question correctly, reboot yes, shutdown then powerup by itself *Don't know :( * You can setup a crontab (as root user or with setuid ), something like 30 09 * * * /sbin/init 6 /dev/null; would reboot the machine at 9:30 am. But if you mean shut it down and then restart it automatically, I don't know for sure if it can be done? Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
From owner-freebsd-questi...@freebsd.org Sat Jul 16 21:40:19 2011 Date: Sat, 16 Jul 2011 22:40:19 -0400 From: Aryeh Friedman aryeh.fried...@gmail.com To: FreeBSD Mailing List freebsd-questions@freebsd.org Subject: how to force a hard reboot remotely Is there any way to force a complete power down and then reset of a i386 without physically being present? Powerdown: 'man shutdown' see the -p option. Hardware dependant. Reset after powerdown: Hardware dependant. requires remomte 'console' access of some sort, e.g. 'lights out' managment console. _Just_ force a hard reboot', per Subject line: 'man reboot'. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
Won't -p power it down and leave it powered down? On Jul 16, 2011, at 10:08 PM, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Sat Jul 16 21:40:19 2011 Date: Sat, 16 Jul 2011 22:40:19 -0400 From: Aryeh Friedman aryeh.fried...@gmail.com To: FreeBSD Mailing List freebsd-questions@freebsd.org Subject: how to force a hard reboot remotely Is there any way to force a complete power down and then reset of a i386 without physically being present? Powerdown: 'man shutdown' see the -p option. Hardware dependant. Reset after powerdown: Hardware dependant. requires remomte 'console' access of some sort, e.g. 'lights out' managment console. _Just_ force a hard reboot', per Subject line: 'man reboot'. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
From: Aryeh Friedman aryeh.fried...@gmail.com To: FreeBSD Mailing List freebsd-questions@freebsd.org Sent: Sat, July 16, 2011 10:40:19 PM Subject: how to force a hard reboot remotely Is there any way to force a complete power down and then reset of a i386 without physically being present? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org WOW! That's a tall order. A reboot from remote is simple, but a cold bootI don't think that's possible unless you have some kind of Wake-On-Lan capable NIC which could detect a connection attempt while the machine is off. I can't say that for sure because what you've got to remember is that with a cold boot, the machine will no longer remember what OS it was running until it reboots. My advice would be to get to the console if you absolutely have to cold boot it. Or call someone nearby the console and have the actually turn the machine off, wait the obligatory 30 seconds and then restart it. Someone else may have a better idea. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
When bottom replying, please clear the header and signature - thanks. You can set up a BIOS boot time, if you can get onsite... that would allow you to power it down at, say, 11:59PM and have it power back on at Midnight. Or a UPS that's controlled by another machine. Or the magic packet WOL option... but those require another machine. Maybe a switch or router than can send WOL packets would be a possibility? -- Ryan On Jul 16, 2011, at 10:31 PM, Bill Tillman wrote: WOW! That's a tall order. A reboot from remote is simple, but a cold bootI don't think that's possible unless you have some kind of Wake-On-Lan capable NIC which could detect a connection attempt while the machine is off. I can't say that for sure because what you've got to remember is that with a cold boot, the machine will no longer remember what OS it was running until it reboots. My advice would be to get to the console if you absolutely have to cold boot it. Or call someone nearby the console and have the actually turn the machine off, wait the obligatory 30 seconds and then restart it. Someone else may have a better idea. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
In the last episode (Jul 16), Aryeh Friedman said: Is there any way to force a complete power down and then reset of a i386 without physically being present? If you have a server motherboard with IPMI (or a high-end server with a service processor module), you can use that to power cycle the system remotely even if the OS is hung. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
On 7/16/2011 9:40 PM, Aryeh Friedman wrote: Is there any way to force a complete power down and then reset of a i386 without physically being present? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Odds are this would be a little bit of a hardware mod. Get a microcontroller and a relay, and tell the microcontroller to kill power to the system. Make sure in the BIOS you're set to restart when the power comes back on. If that fails you'll need another relay to short the on button. I don't know of anything in the computer that could be easily used instead of a microcontroller. You might be able to find something that'll work related to home automation. But the only guarantee of a power down is physically killing power, even if you're a thousand miles away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
On Jul 16, 2011, at 11:01 PM, Joshua Isom wrote: On 7/16/2011 9:40 PM, Aryeh Friedman wrote: Is there any way to force a complete power down and then reset of a i386 without physically being present? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Odds are this would be a little bit of a hardware mod. Get a microcontroller and a relay, and tell the microcontroller to kill power to the system. Make sure in the BIOS you're set to restart when the power comes back on. If that fails you'll need another relay to short the on button. I don't know of anything in the computer that could be easily used instead of a microcontroller. I think I kinda covered that with the UPS remote control thing... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to force a hard reboot remotely
On Sat, Jul 16, 2011 at 10:39:06PM -0500, Ryan Coleman wrote: Date: Sat, 16 Jul 2011 22:39:06 -0500 From: Ryan Coleman edi...@d3photography.com Subject: Re: how to force a hard reboot remotely To: Bill Tillman btillma...@yahoo.com Cc: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1084) When bottom replying, please clear the header and signature - thanks. You can set up a BIOS boot time, if you can get onsite... that would allow you to power it down at, say, 11:59PM and have it power back on at Midnight. Or a UPS that's controlled by another machine. Or the magic packet WOL option... but those require another machine. Maybe a switch or router than can send WOL packets would be a possibility? -- Ryan I had something like this in late 1995. Remotely shutdown -h [time] got my box powered down, then a remote timer cycled the power. Problems were: that the timer was hard to set exacrly. [There may have ben two timers; it was a bear of a problem. ] gary On Jul 16, 2011, at 10:31 PM, Bill Tillman wrote: WOW! That's a tall order. A reboot from remote is simple, but a cold bootI don't think that's possible unless you have some kind of Wake-On-Lan capable NIC which could detect a connection attempt while the machine is off. I can't say that for sure because what you've got to remember is that with a cold boot, the machine will no longer remember what OS it was running until it reboots. My advice would be to get to the console if you absolutely have to cold boot it. Or call someone nearby the console and have the actually turn the machine off, wait the obligatory 30 seconds and then restart it. Someone else may have a better idea. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bluetooth mouse does not work after reboot
On 18/01/2011 09:31, David Demelier wrote:
Hello,
I bought a Logitech V470 bluetooth mouse for my laptop. I followed this
website to configure mine :
http://astralblue.livejournal.com/357664.html
It had worked correctly yesterday (when I setup everything) now nothing
happens, after the reboot if I put the mouse in the association state it
does not associate with my laptop (the mouse led is blinking all the time).
There is no messages at all and bthidd, hcsecd are running too.
in my /etc/bluetooth/hosts I have :
00:1f:20:0f:62:31 mouse
in my /etc/bluetooth/hcsecd.conf I have :
[..snip..]
device {
bdaddr 00:1f:20:0f:62:31;
name Logitech V470;
key nokey;
pin ;
}
in my /etc/bluetooth/bthidd.conf I have :
device {
bdaddr 00:1f:20:0f:62:31;
control_psm 0x11;
interrupt_psm 0x13;
reconnect_initiate true;
battery_power true;
normally_connectable false;
hid_descriptor {
0x05 0x01 0x09 0x02 0xa1 0x01 0x85 0x02
0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01
0x29 0x08 0x15 0x00 0x25 0x01 0x75 0x01
0x95 0x08 0x81 0x02 0x05 0x01 0x09 0x30
0x09 0x31 0x16 0x01 0xf8 0x26 0xff 0x07
0x75 0x0c 0x95 0x02 0x81 0x06 0x09 0x38
0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x01
0x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x75
0x08 0x95 0x01 0x81 0x06 0xc0 0xc0 0x06
0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10
0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff
0x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91
0x00 0xc0
};
}
So what is the problem now? If you have any clue, thanks.
Kind regards,
It works if I remove the /var/db/bthidd.hids. Why this behavior?
Cheers,
--
David Demelier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Bluetooth mouse does not work after reboot
Hello,
I bought a Logitech V470 bluetooth mouse for my laptop. I followed this
website to configure mine :
http://astralblue.livejournal.com/357664.html
It had worked correctly yesterday (when I setup everything) now nothing
happens, after the reboot if I put the mouse in the association state it
does not associate with my laptop (the mouse led is blinking all the time).
There is no messages at all and bthidd, hcsecd are running too.
in my /etc/bluetooth/hosts I have :
00:1f:20:0f:62:31 mouse
in my /etc/bluetooth/hcsecd.conf I have :
[..snip..]
device {
bdaddr 00:1f:20:0f:62:31;
nameLogitech V470;
key nokey;
pin ;
}
in my /etc/bluetooth/bthidd.conf I have :
device {
bdaddr 00:1f:20:0f:62:31;
control_psm 0x11;
interrupt_psm 0x13;
reconnect_initiate true;
battery_power true;
normally_connectablefalse;
hid_descriptor {
0x05 0x01 0x09 0x02 0xa1 0x01 0x85 0x02
0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01
0x29 0x08 0x15 0x00 0x25 0x01 0x75 0x01
0x95 0x08 0x81 0x02 0x05 0x01 0x09 0x30
0x09 0x31 0x16 0x01 0xf8 0x26 0xff 0x07
0x75 0x0c 0x95 0x02 0x81 0x06 0x09 0x38
0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x01
0x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x75
0x08 0x95 0x01 0x81 0x06 0xc0 0xc0 0x06
0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10
0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff
0x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91
0x00 0xc0
};
}
So what is the problem now? If you have any clue, thanks.
Kind regards,
--
David Demelier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Switch ppp.conf with tun w/o reboot
Can I switch ppp configurations for ppp on demand using tunneling without rebooting? -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Switch ppp.conf with tun w/o reboot
On Dec 2, 2010, at 4:13 PM, Lars Eighner wrote: Can I switch ppp configurations for ppp on demand using tunneling without rebooting? If you're asking about the userland ppp using tunXX interfaces, yes. You can kill ppp, then re-run ppp -auto config2 and it will bring up ppp using a second config instead. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.1-RELEASE hangs on reboot
On Tuesday, November 30, 2010 8:23:19 pm Ondřej Majerech wrote: Hello, my 8.1-R system has just started hanging on reboot. Specifically after I svn up'd my source and updated from 8.1-R-p1 to -p2. Some kind of hang occurs on every reboot attempt. Usually it hangs at the Rebooting... message, but sometimes the thing just locks up before it even syncs disks. shutdown -p now seems to shutdown the system successfully each time. So I booted into single-user mode, executed reboot and during the Syncing disks I pressed Ctrl-Alt-Escape to break into the debugger. There I single-stepped with the s command until the thing simply stopped doing anything. (Even if I pressed NumLock, the LED on the keyboard wouldn't turn off.) The screen content at the moment of hang is (dutifully typed over as the thing is dead and I don't have a serial cable): [thread pid 12 tid 100017 ] Stopped at sckbdevent+0x5f: call _mtx_unlock_flags db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags: pushq %rbp db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x1: movq %rsp,%rbp db [thread pid 12 tid 100017 ] Stopped at _mtx_unloock_flags+0x4: subq $0x20,%rsp db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x8: movq %rbx,(%rsp) db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0xc: movq %r12,0x8(%rsp) db [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x11: movq %rdi,%rbx db [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x14: movq %r13,0x10(%rsp) db E Including that E at the end. No good ideas here, though I think we just turned off PSL_T by accident so it ran for a while before hanging after this. 'E' must be the start of a message on the console. As I said, it's 8.1-RELEASE-p2; it's on AMD64. I'm using custom kernel which only differs from GENERIC by addition of the debugging options: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC I tried rebooting with ACPI disabled, but the thing paniced on boot with panic: Duplicate free of item 0xff00025e from zone 0xff00bfdcc2a0(1024) cpuid = 0 KDB: enter: panic [thread pid 0 tid 10 ] Stopped at kdb_enter+0x3d: movq $0, 0x6b2d20(%rip) db bt Tracing pid 0 tid 10 td 0x80c63fc0 kdb_enter() at kdb_enter+0x3d panic() at panic+0x17b uma_dbg_free() at uma_dbg_free+0x171 uma_zfree_arg() at uma_zfree_arg+0x68 free() at free+0xcd device_set_driver() at device_set_driver+0x7c device_attach() at device_attach+0x19b bus_generic_attach() at bus_generic_attach+0x1a pci_attach() at pci_attach+0xf1 The free() should be the free to free the softc but that implies it had a previous driver and softc. Maybe add some debug info to devclass_set_driver() to print out the previous driver's name (and maybe the value of the pointer) before free'ing the softc. You could use gdb on the kernel.debug and the pointer value to figure out exactly which driver was the previous one and look to see if it's probe routine does something funky with the softc pointer. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.1-RELEASE hangs on reboot
On 1 Dec, Ondřej Majerech wrote: Hello, my 8.1-R system has just started hanging on reboot. Specifically after I svn up'd my source and updated from 8.1-R-p1 to -p2. Some kind of hang occurs on every reboot attempt. Usually it hangs at the Rebooting... message, but sometimes the thing just locks up before it even syncs disks. shutdown -p now seems to shutdown the system successfully each time. One of my systems running 8.1-STABLE started reliably(?) hanging at the Rebooting... step whenever try to reboot it. It's been doing this for the last month or so. I haven't seen the earlier hang. 9.0-CURRENT on the same hardware doesn't experience this problem. I haven't had time to try to debug this, so I've just been using the reset switch when it hangs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.1-RELEASE hangs on reboot
Hello, my 8.1-R system has just started hanging on reboot. Specifically after I svn up'd my source and updated from 8.1-R-p1 to -p2. Some kind of hang occurs on every reboot attempt. Usually it hangs at the Rebooting... message, but sometimes the thing just locks up before it even syncs disks. shutdown -p now seems to shutdown the system successfully each time. So I booted into single-user mode, executed reboot and during the Syncing disks I pressed Ctrl-Alt-Escape to break into the debugger. There I single-stepped with the s command until the thing simply stopped doing anything. (Even if I pressed NumLock, the LED on the keyboard wouldn't turn off.) The screen content at the moment of hang is (dutifully typed over as the thing is dead and I don't have a serial cable): [thread pid 12 tid 100017 ] Stopped at sckbdevent+0x5f: call _mtx_unlock_flags db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags: pushq %rbp db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x1: movq %rsp,%rbp db [thread pid 12 tid 100017 ] Stopped at _mtx_unloock_flags+0x4: subq $0x20,%rsp db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x8: movq %rbx,(%rsp) db [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0xc: movq %r12,0x8(%rsp) db [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x11: movq %rdi,%rbx db [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x14: movq %r13,0x10(%rsp) db E Including that E at the end. As I said, it's 8.1-RELEASE-p2; it's on AMD64. I'm using custom kernel which only differs from GENERIC by addition of the debugging options: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC I tried rebooting with ACPI disabled, but the thing paniced on boot with panic: Duplicate free of item 0xff00025e from zone 0xff00bfdcc2a0(1024) cpuid = 0 KDB: enter: panic [thread pid 0 tid 10 ] Stopped at kdb_enter+0x3d: movq $0, 0x6b2d20(%rip) db bt Tracing pid 0 tid 10 td 0x80c63fc0 kdb_enter() at kdb_enter+0x3d panic() at panic+0x17b uma_dbg_free() at uma_dbg_free+0x171 uma_zfree_arg() at uma_zfree_arg+0x68 free() at free+0xcd device_set_driver() at device_set_driver+0x7c device_attach() at device_attach+0x19b bus_generic_attach() at bus_generic_attach+0x1a pci_attach() at pci_attach+0xf1 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a legacy_pcib_attach() at legacy_pcib_attach+0x70 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a legacy_attach() at legacy_attach+0x19 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a nexus_attach() at nexus_attach+0x68 device_attach() at device_attach+0x69 bus_generic_new_pass() at bus_generic_new_pass+0xd6 bus_set_pass() at bus_set_pass+0x7a configure() at configure+0xa mi_startup() at mi_startup+0x59 btext() at btext+0x2c db reboot That panic is 100% repeatable -- every time I try booting with ACPI disabled, I get exactly the same panic. So -- what can I do about it? I'll gladly provide more information of course. Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010 17:11:30 -0400 (EDT), d...@safeport.com wrote: I have had two systems die with bad disks. Personally, I never had trouble with bad disks, but with defective file systems (origin unknown), and follow-up trouble caused by background fsck that prevented me many years from accessing my data. Going the old fashioned way brought everything back. Long story short: A present .snapshot from the 1st background fsck (which was introduced as default in 5.0, as far as I remember) caused fsck from working as expected; after removing this file, I got all the missing data back. Luckily, the problem didn't seem to be related to actual disk failure, as SMART data didn't give a hint about that. I did work with a 1:1 dd copy anyway. Modern disks die silently which I think is too bad. You usally see messages in dmesg / console that indicate disk trouble. In mos cases, those messages say that the disk is already dying - it's too late for repair. So time for backup and replacement. Seems that this is the result of continuing bigger and cheaper disks... If this is happening and you have data you want to recover you might try booting in single user move and using fsck manually on each slice. The fsck program operates on partitions, not on slices. Terminology, dear Watson. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to prevent system to launch interactive fsck after improper shutdown and reboot?
Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Thanks remko p.s. This was found within 5 seconds in /etc/defaults/rc.conf. -- /\ Best regards, | re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
El día Wednesday, September 15, 2010 a las 09:41:54AM +0300, Yuri escribió: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yes, just do: $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc $ man rc.conf | col -b | fgrep fsck_ In general one should avoid unclean shutdowns. I even after such event go into single user mode and run fsck(8) by hand. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 1:59 AM, Peter Boosten pe...@boosten.org wrote: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) Depends on the shell, I guess he's a bash user. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
El día Wednesday, September 15, 2010 a las 08:59:07AM +0200, Peter Boosten escribió: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) no, $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 15-9-2010 9:07, Matthias Apitz wrote: $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? zsh. Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 2:07 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, September 15, 2010 a las 08:59:07AM +0200, Peter Boosten escribió: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) no, $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? it doesn't work in zsh, csh, tcsh, I didn't try sh, it didn't even occur to me since I so rarely use it as an interactive shell. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010 08:47:38 +0200, Remko Lodder re...@elvandar.org wrote: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Very important point. As an addition, allow me to mention background_fsck=YES as an entry in /etc/rc.conf. This will let the system boot up and perform fsck checks while the system is running - running on a maybe defective or inconsistent file system. This is dangerous, but possible. It utilizes a snapshot mechanism which can cause further trouble (lost / emptyinodes and disappearing subtrees of files). Personally, if fsck requires YOUR attention, there's usually a reason for this. The reason is possible data loss or file system corruption where YOU take the responsibility of decision, not fsck. By default, fsck does not do damaging, but under strange circumstances, it can happen. For example, if you want to do a special kind of data recovery or forensic analysis on a file system, you potentially DO NOT WANT fsck to assume y for all the questions because that can make your job harder. A common additional y flag is -f (means fsck -yf) to force all operations suggested by fsck and confirming them. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 09/15/10 09:47, Remko Lodder wrote: I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Thanks remko p.s. This was found within 5 seconds in /etc/defaults/rc.conf. Thanks Remko! I never had spare 5 secs for this :-), and now when I left my computer to friends (not computer savvy) they got into this trap. There is no database... I think installer better asks this question during installation since many users just run a desktop and -y is pretty much ok for them. Thank you again, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 12:00 AM, Yuri y...@rawbw.com wrote: Thanks Remko! I never had spare 5 secs for this :-), and now when I left my computer to friends (not computer savvy) they got into this trap. There is no database... I think installer better asks this question during installation since many users just run a desktop and -y is pretty much ok for them. Train your friends to shut the machine down by pressing (not holding down!) the power button. On any modern machine ACPI should trigger a clean shutdown/poweroff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010, Polytropon wrote: On Wed, 15 Sep 2010 08:47:38 +0200, Remko Lodder re...@elvandar.org wrote: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Very important point. As an addition, allow me to mention background_fsck=YES as an entry in /etc/rc.conf. This will let the system boot up and perform fsck checks while the system is running - running on a maybe defective or inconsistent file system. This is dangerous, but possible. It utilizes a snapshot mechanism which can cause further trouble (lost / emptyinodes and disappearing subtrees of files). Personally, if fsck requires YOUR attention, there's usually a reason for this. The reason is possible data loss or file system corruption where YOU take the responsibility of decision, not fsck. By default, fsck does not do damaging, but under strange circumstances, it can happen. For example, if you want to do a special kind of data recovery or forensic analysis on a file system, you potentially DO NOT WANT fsck to assume y for all the questions because that can make your job harder. A common additional y flag is -f (means fsck -yf) to force all operations suggested by fsck and confirming them. I have had two systems die with bad disks. This email contains great information and spot-on advice from my experience. When I was ready to give up on my last system I did a -yf in single user mode and was able to get most of my data because the bad sectors were in /usr/local which had many missing files and directories. Modern disks die silently which I think is too bad. If this is happening and you have data you want to recover you might try booting in single user move and using fsck manually on each slice. If you are lucky, your errors will be in /tmp or /var. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reboot options
2010/8/30 Daniel Bye freebsd-questi...@slightlystrange.org: On Mon, Aug 30, 2010 at 11:43:33AM -0700, Chip Camden wrote: Is there a way to specify which boot option to choose on the next reboot? I often find that I'll start a reboot and then get distracted by something else and miss my chance to specify which way to boot before the beastie screen times out. A nit, I know -- but bothersome to a nitwit such as I. A nit by which others have obviously been irritated - nextboot(8) is probably what you're looking for! Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ If you don't remember a command, and knows the subject and what the command is supposed to do try the command apropos. $ apropos boot Shows many intersting things :-). -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
reboot options
Is there a way to specify which boot option to choose on the next reboot? I often find that I'll start a reboot and then get distracted by something else and miss my chance to specify which way to boot before the beastie screen times out. A nit, I know -- but bothersome to a nitwit such as I. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpNeLCYroXsI.pgp Description: PGP signature
Re: reboot options
On Mon, Aug 30, 2010 at 11:43:33AM -0700, Chip Camden wrote: Is there a way to specify which boot option to choose on the next reboot? I often find that I'll start a reboot and then get distracted by something else and miss my chance to specify which way to boot before the beastie screen times out. A nit, I know -- but bothersome to a nitwit such as I. A nit by which others have obviously been irritated - nextboot(8) is probably what you're looking for! Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpUS15D2loGH.pgp Description: PGP signature
Re: reboot options
Quoth Daniel Bye on Monday, 30 August 2010: On Mon, Aug 30, 2010 at 11:43:33AM -0700, Chip Camden wrote: Is there a way to specify which boot option to choose on the next reboot? I often find that I'll start a reboot and then get distracted by something else and miss my chance to specify which way to boot before the beastie screen times out. A nit, I know -- but bothersome to a nitwit such as I. A nit by which others have obviously been irritated - nextboot(8) is probably what you're looking for! Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ That's precisely what I was seeking -- thanks! -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpPR6VTAz5bb.pgp Description: PGP signature
box reboot after hdd write error
Hello fellas, My system is a 8.0-RELEASE with 6 hdd's. 2 days ago I had some power failures and 2 disks were affected. These 2 hdd;s are connected to atapci0: SiI 3512 SATA150 controller port 0xd000-0xd007,0xd100-0xd103,0xd200-0xd207,0xd300-0xd303,0xd400-0xd40f mem 0xfa4a-0xfa4a01ff irq 12 at device 4.0 on pci2 s-ata controller. Before the power surge, the disks were operating normally. I use them for storage, therefore no system data is kept on them. The issue here is that after the write failure, the box reboots. Up to this point I cannot figure out why it reboots, since the disks contain no relevant data (from a OS point of view). Do you think it's normal for an OS to reboot if 2 disks have write errors ? even more so, if the disks have no OS files on them ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: box reboot after hdd write error
On 8/17/2010 11:37 PM, claudiu vasadi wrote: Hello fellas, My system is a 8.0-RELEASE with 6 hdd's. 2 days ago I had some power failures and 2 disks were affected. These 2 hdd;s are connected to atapci0: SiI 3512 SATA150 controller port 0xd000-0xd007,0xd100-0xd103,0xd200-0xd207,0xd300-0xd303,0xd400-0xd40f mem 0xfa4a-0xfa4a01ff irq 12 at device 4.0 on pci2 s-ata controller. Before the power surge, the disks were operating normally. I use them for storage, therefore no system data is kept on them. The issue here is that after the write failure, the box reboots. Up to this point I cannot figure out why it reboots, since the disks contain no relevant data (from a OS point of view). Do you think it's normal for an OS to reboot if 2 disks have write errors ? even more so, if the disks have no OS files on them How often is it rebooting? And it's not saying or doing anything it just randomly reboots? That seems more like a hardware issue than something OS related since the OS isn't even on those disks. If it's just data disks you could unplug them to see if the machine still reboots. That would let you know for sure if they really are the problem or if it's something else. Are you sure the power surge didn't affect the power supply? Also did you do anything to the system after the power surge (like open it up for any reason where there may be a loose wire not plugged in all the way). The last thing I would mention is this could all be a coincidence and it might be related to heat, make sure all your fans are working and that there isn't any big dust buildup inside (gogo compressed air). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: box reboot after hdd write error
How often is it rebooting? Only after the write failure. If I do read from the disks, everything is fine If it's just data disks you could unplug them to see if the machine still reboots. That would let you know for sure if they really are the problem or if it's something else. I could try that but it will take some time since I am only administering the box and I have no access to it (fizicaly) Are you sure the power surge didn't affect the power supply? Yes I am. The other 4 disks are ok and the system has no other symptoms of any kind Also did you do anything to the system after the power surge (like open it up for any reason where there may be a loose wire not plugged in all the way). Nope. The last thing I would mention is this could all be a coincidence and it might be related to heat, make sure all your fans are working and that there isn't any big dust buildup inside (gogo compressed air). Crossed my mind too. I ran long and short smart test on it and it came up ok. Temp is ~37 degrees celsius. Like I said, the disks were ok before the power surge. All the fans are working fine. Sorry, I forgot to put the list in CC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
cpu_reset: stopping other CPUs - machine stalls at halt or reboot
Hello fellas, I have a vmware FreeBSD guest with 8 CPU's and 2GB RAM. I am a bit puzzled of the behaviour the system has when I issue reboot and/or halt -p now. It shows cpu_reset: stopping other CPUs and stalls for ~2 minutes. I have a custom SMP kernel and at the moment I was unable to reveal any problems with the guest or the host (win 7). FreeBSD has all ports up to date and at the moment of reboot or shutdown, no heavy is running. Did any of you experience something similar ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cpu_reset: stopping other CPUs - machine stalls at halt or reboot
On Sun, Jul 25, 2010 at 1:24 PM, claudiu vasadi claudiu.vas...@gmail.com wrote: Hello fellas, I have a vmware FreeBSD guest with 8 CPU's and 2GB RAM. I am a bit puzzled of the behaviour the system has when I issue reboot and/or halt -p now. It shows cpu_reset: stopping other CPUs and stalls for ~2 minutes. I have a custom SMP kernel and at the moment I was unable to reveal any problems with the guest or the host (win 7). FreeBSD has all ports up to date and at the moment of reboot or shutdown, no heavy is running. Did any of you experience something similar ? Yeah - I've seen the same thing when rebooting - the cpu_reset message appears and there is a long delay before a reboot happens. I have no problems powering off though (shutdown -p). I've got a -current vm under 6.5.4 with 2 CPUs, host OS is Windows 7, that can take a while to reboot. I haven't timed it but 90 seconds from the message appearing is a good estimate. Since the disks should already be synced by that point, there doesn't seem to be any harm in just resetting the VM - I've done it a number of times and never had any issues. However, even on a real computer, there is a bit of a delay here - my Thinkpad T61 will sit there for around 20 seconds before actually rebooting. I have no idea how to even start debugging this kind of thing and it isn't a really big deal to me (I don't reboot too often and just use the workaround when I do), so I never reported it. -- Rob Farmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cpu_reset: stopping other CPUs - machine stalls at halt or reboot
Rob, In the meantime I installed a real freebsd on my work T400 and I am experiencing the same thing. I believe that at this point I can rule out a vmware problem. PS: I also tried hard rebooting after I consider the sync done and I did not experience any weird behavior. Still is it intended to stall so long ? I hope not, because I don't like it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ownership of /var/named Changes on Reboot.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/06/2010 04:21:34, Peter Boosten wrote: On 17-6-2010 4:58, Robert Huff wrote: Martin McCormick writes: Is there a way to keep /var/named owned by bind across reboots? Yes. I had this happen for a long time. The bad news is it had been years since I fixed it, and I no longer remember exactly what I did. I will keep trying. Permissions are set using the mtree files: /etc/mtree/ Furthermore, the default setup *is* for named to run as an unprivileged process. The setup is very carefully designed so that named doesn't have write permission on the directory where its configuration files are stored, or on directories that contain static zone files, but it does have write permission on directories it uses for zone files AXFR'd from a master, or zone files maintained using dynamic DNS. This used to generate a warning from bind about not having a writable current working directory -- which was basically harmless and could be ignored. However recent changes mean bind needs a writable working directory, so the latest layouts include /var/named/etc/namedb/working Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwZ0w4ACgkQ8Mjk52CukIyWEACfdgSPyaDaLVXp/ugxYPCZIGSf KygAn2bsa27UF+O7BpZwmUMBGRIRvYeI =LaxU -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ownership of /var/named Changes on Reboot.
On 17 June 2010 08:47, Matthew Seaman m.sea...@infracaninophile.co.ukwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/06/2010 04:21:34, Peter Boosten wrote: On 17-6-2010 4:58, Robert Huff wrote: Martin McCormick writes: Is there a way to keep /var/named owned by bind across reboots? Yes. I had this happen for a long time. The bad news is it had been years since I fixed it, and I no longer remember exactly what I did. I will keep trying. Permissions are set using the mtree files: /etc/mtree/ Furthermore, the default setup *is* for named to run as an unprivileged process. The setup is very carefully designed so that named doesn't have write permission on the directory where its configuration files are stored, or on directories that contain static zone files, but it does have write permission on directories it uses for zone files AXFR'd from a master, or zone files maintained using dynamic DNS. This used to generate a warning from bind about not having a writable current working directory -- which was basically harmless and could be ignored. However recent changes mean bind needs a writable working directory, so the latest layouts include /var/named/etc/namedb/working Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwZ0w4ACgkQ8Mjk52CukIyWEACfdgSPyaDaLVXp/ugxYPCZIGSf KygAn2bsa27UF+O7BpZwmUMBGRIRvYeI =LaxU -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org so the logical extension to this is by changing the ownership of the directory to bind, you are making the configuration directory writeable, and therefore you are actually lowering security. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ownership of /var/named Changes on Reboot.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/06/2010 09:37:03, krad wrote: so the logical extension to this is by changing the ownership of the directory to bind, you are making the configuration directory writeable, and therefore you are actually lowering security. Correct. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwZ9iEACgkQ8Mjk52CukIxlOQCfZXV2D+ps0uQITQ6b05sXsmjC r3IAnjQyzVtfBhJ0XwxO8O+Gsct8wb9j =Kj7A -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ownership of /var/named Changes on Reboot.
Matthew Seaman writes: Furthermore, the default setup *is* for named to run as an unprivileged process. The setup is very carefully designed so that named doesn't have write permission on the directory where its configuration files are stored, or on directories that contain static zone files, but it does have write permission on directories it uses for zone files AXFR'd from a master, or zone files maintained using dynamic DNS. This used to generate a warning from bind about not having a writable current working directory -- which was basically harmless and could be ignored. However recent changes mean bind needs a writable working directory, so the latest layouts include /var/named/etc/namedb/working That turned out to be the issue. I reset the permissions to match the way they are when one first installs bind. Root owns /var/named but bind owns directories that should be writable so the trick is to set one's named.conf file to reference writable directories for all the zones, logs and named.pid. It is now starting automatically on reboot just like it should. While bind owns all the writable subdirectories, they all still have wheel as their GID. That appears to be okay since they are all only writable by owner. Thanks for explaining this annoying little mystery that has dogged me at a minor level for years. I have been running bind for Oklahoma State University for close to 18 years and one tends to stick with configurations that work. It is just time to modernize and at least configure bind in the recommended way so as to take full advantage of the clever design. It does still give the message that the working directory is not writable. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ownership of /var/named Changes on Reboot.
I run named chrooted to bind but not in a jail. When the system reboots, something changes ownership of /var/named back to root:wheel. I have thought several times I figured out how to prevent this from happening, but to no avail. The most promising lead was the following directives in /etc/rc.conf.local: named_uid=bind# User to run named as named_chrootdir= # Chroot directory (or not to auto-chroot it) named_chroot_autoupdate=YES # Automatically install/update chrooted Is there a way to keep /var/named owned by bind across reboots? Our production FreeBSD systems are up for years at a time so we don't see this problem often, but we have just been lucky that I am usually the one to reboot and know that named will come up broken and exit because named can not write in to /var/named when it is owned by root. It would be really nice to be able to count on /var/named staying put so named can just start automatically after a reboot. I prefer for named to run as a low-priority UID rather than as root so if I am doing something wrong, tell me that, also. We have been running named with a high-numbered UID for probably ten years and the force back to root ownership has always been a factor when the system is rebooted. Thank you. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ownership of /var/named Changes on Reboot.
Martin McCormick writes: Is there a way to keep /var/named owned by bind across reboots? Yes. I had this happen for a long time. The bad news is it had been years since I fixed it, and I no longer remember exactly what I did. I will keep trying. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Ownership of /var/named Changes on Reboot.
On 17-6-2010 4:58, Robert Huff wrote: Martin McCormick writes: Is there a way to keep /var/named owned by bind across reboots? Yes. I had this happen for a long time. The bad news is it had been years since I fixed it, and I no longer remember exactly what I did. I will keep trying. Permissions are set using the mtree files: /etc/mtree/ Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iwi0 and spontaneous reboot on /etc/rc.d/netif restart
Hello, I just upgraded to 8.0-RELEASE-p2 from 7.2 and I'm also seeing kernel crashes and reboots after running /etc/rc.d/netif restart, which didn't occur with 7.2. This is reproducible on demand. After writing this email I found the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/144755 % /etc/rc.d/netif restart Apr 30 08:57:04 met wpa_supplicant[1785]: CTRL-EVENT-SCAN-RESULTS Apr 30 08:57:04 met wpa_supplicant[1719]: CTRL-EVENT-SCAN-RESULTS Apr 30 08:57:04 met wpa_supplicant[1719]: Trying to associate with 0:xxx:aa (SSID='blah' freq=2447 MHz) Apr 30 08:57:04 met wpa_supplicant[1785]: Trying to associate with 00:xx:aa (SSID='blah' freq=2447 MHz) Apr 30 08:57:04 met wpa_supplicant[1785]: Associated with 00:xx:aa Apr 30 08:57:04 met kernel: wlan0: link state changed to UP Apr 30 08:57:05 met kernel: iwi0: firmware error Apr 30 08:57:04 met wpa_supplicant[1719]: Associated with 00:xx:aa Apr 30 08:57:05 met kernel: iwi0: need multicast update callback Apr 30 08:57:10 met kernel: iwi0: device timeout Apr 30 08:57:15 met wpa_supplicant[1719]: Authentication with 00:xx:aa timed out. Apr 30 08:57:15 met wpa_supplicant[1785]: Authentication with 00:xx:aa timed out. Apr 30 08:57:15 met kernel: wlan0: link state changed to DOWN Apr 30 08:57:15 met wpa_supplicant[1719]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Apr 30 08:57:15 met wpa_supplicant[1785]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Apr 30 08:57:24 met dhclient[1876]: send_packet: Network is down Apr 30 08:58:01 met last message repeated 2 times ...crash and reboot... % kgdb kernel /var/crash/vmcore.0 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. ... This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: wlan0: ieee80211_new_state_locked: pending SCAN - AUTH transition lost Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc49331d5 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0ad5b0c stack pointer = 0x28:0xc43bbb7c frame pointer = 0x28:0xc43bbc34 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (iwi0 taskq) trap number = 12 panic: page fault Uptime: 1m42s Physical memory: 1518 MB Dumping 69 MB: 54 38 22 6 % kldstat Id Refs AddressSize Name 1 95 0xc040 656394 kernel 21 0xc0a57000 b69c if_fxp.ko 32 0xc0a63000 2698cmiibus.ko 41 0xc0a8a000 f528 if_iwi.ko 56 0xc0a9a000 3fc40wlan.ko 61 0xc0ada000 7194 snd_ich.ko 72 0xc0ae2000 567b0sound.ko 81 0xc0b39000 87d8 atapicd.ko 91 0xc0b42000 4f6c atapicam.ko 101 0xc0b47000 d87c cpufreq.ko 111 0xc0b55000 30228iwi_bss.ko 121 0xc0b86000 2f2b0iwi_ibss.ko 131 0xc0bb6000 2f578iwi_monitor.ko 141 0xc0be6000 2ee0 wlan_acl.ko 151 0xc4858000 8000 linprocfs.ko 161 0xc4895000 26000linux.ko 171 0xc48f6000 3000 wlan_wep.ko 181 0xc48f9000 4000 wlan_tkip.ko 191 0xc48fe000 7000 wlan_ccmp.ko 201 0xc4cae000 9000 i915.ko % less /boot/loader.conf hw.ata.ata_dma=1 hw.ata.atapi_dma=1 kern.maxdsiz=734003200 kern.ipc.semmni=256 kern.ipc.semmns=512 kern.ipc.semmnu=256 sem_load=YES atapicd_load=YES atapicam_load=YES cpufreq_load=YES if_fxp_load=YES snd_ich_load=YES # stuff for wireless legal.intel_iwi.license_ack=1 if_iwi_load=YES iwi_bss_load=YES iwi_ibss_load=YES iwi_monitor_load=YES wlan_acl_load=YES Here are the relevant parts from /etc/rc.conf wlans_iwi0=wlan0 ifconfig_wlan0=WPA DHCP % cat /usr/src/sys/i386/conf/MY_KERNEL_CONFIG cpu I686_CPU ident MET_ATH_CX_2010-04-29 options SCHED_ULE options PREEMPTION #Enable kernel thread preemption options INET #InterNETworking options INET6 #IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options NFSLOCKD #Network Lock Manager options NFS_ROOT #NFS usable as /, requires NFSCLIENT options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7
iwi0 and spontaneous reboot on /etc/rc.d/netif restart
Hi, over the last 6 months or so, I have been so unfortunate to experience spontaneous reboots when I restart netif. Most of the time it leaves no trace in logs, but this time I was fortunate enough to be able to scrible down something while in console. I hope someone can shed some light on this - and I will be happy to provide a config files if necessary - it's basicly a standard setup with iwi0, wpa_supplicant connecting via wpa. It is a T42 with a Intel 2200BG. There is no issues in other OSes, so I figure this to be a driver specific problem. This is from handwritten notes, so there may be some inaccuracies. It is FreeBSD 8.0-release. wlan0: ieee80211_new_state_locked: pending SCAN - AUTH transition lost Fata trap 12: page fault while in kernel mode cpuid=0; apic id=00 fault virtual adress = 0xc4bd71b4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0f78867 stack pointer = 0x28:0xc439ab7c frame pointer = 0x28:0xc439ac34 code seqment= base 0x0, limit 0xf, type 0x16 = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (iwi0 taskq) trap number = 12 panic: page fault cpuid = 0 Uptime 13m9s Cannot dump. Device not defined or unavailable Automatic reboot in 15 seconds - press a key on the console to abort. Best Regards, Torgeir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Force reboot after kernel panic.
How can I enforce this? Presently the system just hangs. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Force reboot after kernel panic.
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Halliday Sent: Tuesday, April 13, 2010 3:17 PM To: questi...@freebsd.org Subject: Force reboot after kernel panic. How can I enforce this? Presently the system just hangs. Add to kernconf: options KDB_UNATTENDED -- Regards, T. Koeman, MTh/BSc/BPsy; Technical Monk MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence. smime.p7s Description: S/MIME cryptographic signature
FreeBSD 8.0 reboot hangs at welcome screen
I have a server with VMware ESXi4 with two FreeBSD-amd64 virtual machines (one 7.2, one 8.0). I wanted to do a shutdown -r of the 8.0 machine. The system when down, started 'Rebooting ..', showed the FBSD Welcome screen, counted down 10 seconds, .. then nothing happened, waited about 5 minutes nothing happened. I had do power-off the Virtual Machine, then power-on and it rebooted. After that I saw the time (date command) on that machine was 5 minutes behind ... Why is that? And can the 5 minutes behind in time be caused by that 5 minute 'hang' period? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Clarification w.r.t MDLv2 reports send at reboot in FreeBSD 8.0 Release
Hi, FreeBSD 8.0 Release send two MLDv2 Reports at reboot before performing DAD for its Link Local address, One for the IPv6 Solicited-node multicase address(i.e FF02::1:FFDB:ACD5) and other is unknown (i.e FF02::2:21d:d024 ). Could anyone please clarify me, why FreeBSD is send MLDv2 Report for FF02::2:21d:d024 multicast address? Please fine the attached ifconfig output and tcpdump trace captures and reboot time. Let me know if your need more info Thanks in advance Sitaramaraju Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/ tcpDump_atReboot.dump Description: Binary data bge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:13:21:d3:a1:dd media: Ethernet autoselect (none) status: no carrier fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=2009RXCSUM,VLAN_MTU,WOL_MAGIC ether 00:d0:b7:bd:ac:b5 inet6 fe80::2d0:b7ff:febd:acb5%fxp0 prefixlen 64 scopeid 0x2 inet6 3ffe:501::100:2d0:b7ff:febd:acb5 prefixlen 64 autoconf media: Ethernet autoselect (100baseTX) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST metric 0 mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: named needs restart after a reboot
On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wbl...@wonkity.com wrote: On Tue, 8 Dec 2009, Derrick Ryalls wrote: uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO amd64 I have most things working, but I have noticed that every time I reboot the machine, I need to manually restart named to get it listening on the proper interfaces as by default it is listening on 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it which seems like it would be configured correctly, but I have had to do this on a install before. Anyone have a guess as to what could be wrong? Only a guess: network interface comes up too late. If you're using DHCP to configure that interface, you could try SYNCDHCP. Or if it's an re(4) interface, there are patches in 8-STABLE that make it come up faster. -Warren Block * Rapid City, South Dakota USA ifconfig_nfe0=SYNCDHCP Was the fix, thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: named needs restart after a reboot
On Wed, Dec 9, 2009 at 3:39 PM, Derrick Ryalls ryal...@gmail.com wrote: On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wbl...@wonkity.com wrote: On Tue, 8 Dec 2009, Derrick Ryalls wrote: uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO amd64 I have most things working, but I have noticed that every time I reboot the machine, I need to manually restart named to get it listening on the proper interfaces as by default it is listening on 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it which seems like it would be configured correctly, but I have had to do this on a install before. Anyone have a guess as to what could be wrong? Only a guess: network interface comes up too late. If you're using DHCP to configure that interface, you could try SYNCDHCP. Or if it's an re(4) interface, there are patches in 8-STABLE that make it come up faster. -Warren Block * Rapid City, South Dakota USA ifconfig_nfe0=SYNCDHCP Was the fix, thanks! Spoke too soon. On one reboot, the interface couldn't talk to DHCP until I set it down then back up. I have gone to statically setting the IP. Not ideal, but seems to be working (based on one clean reboot). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
named needs restart after a reboot
Greetings, uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO amd64 I have most things working, but I have noticed that every time I reboot the machine, I need to manually restart named to get it listening on the proper interfaces as by default it is listening on 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it which seems like it would be configured correctly, but I have had to do this on a install before. Anyone have a guess as to what could be wrong? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: named needs restart after a reboot
On Tue, 8 Dec 2009, Derrick Ryalls wrote: uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@example.com:/usr/obj/usr/src/sys/FRODO amd64 I have most things working, but I have noticed that every time I reboot the machine, I need to manually restart named to get it listening on the proper interfaces as by default it is listening on 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it which seems like it would be configured correctly, but I have had to do this on a install before. Anyone have a guess as to what could be wrong? Only a guess: network interface comes up too late. If you're using DHCP to configure that interface, you could try SYNCDHCP. Or if it's an re(4) interface, there are patches in 8-STABLE that make it come up faster. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8-RC2 USB HDD and gjournal wiped partitions on reboot.
Gjournaled USB drive partitions wiped upon reboot. After repartitioning, again the partitions erased on reboot. For now, repartitioned to reclaim data and disabled gjournal. Anybody have the same problem and how to resolve? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
Sounds like you are narrowing down the culprit(s). Also note that it could possibly be a timing issue related to the order things start up. If the NATD is attempting to start before the interface has come up it will die. /etc/rc.d/natd has no REQUIRE section, so it is indeed possible for it to activate right at the very start. It also has a 'precmd' that checks for dhcp interfaces and sets up the -dynamic flag. Might be related. I have no way of knowing though, unless I add some debug messages and figure out to log them. I added REQUIRE: NETWORKING and now I'm waiting to see if the issue appears again. It's a tedious procedure... and the fact that sometimes, this causes named to not work isn't helping either. You can use something like natd_flags=-l in /etc/rc.conf. I have tried this, and the only thing it logs are nat rules that get set up at startup time. I could not find anything that would turn on actual status messages for this process... PS: Is there a way to turn on logging on the entire rc startup procedure? There are a lot of messages that get printed onto the physical screen, but none of them actually end up in /var/log/messages. None of the three 'rc_debug', 'rc_info' or 'rc_startmsgs' do it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
On 9. 11. 2009 1:27, umage wrote: When the connection goes down and comes back up it will take 5 minutes before my FreeBSD gateway box checks the lease and decides if a renewal is in order. This is automatic. If I am sitting in front of my computer and I want to speed this up I issue /etc/rc.d/netif restart on the gateway and it will come up and be happy in about 10 seconds, rather than waiting out the 5 minute time out. In my case the router does get the renewed ip, as I described earlier. However, even after waiting 8+ hours, the system will not recover from the outage properly (reason unknown). That's what this thread is all about. When I started the system today, I found that again it had no connectivity. I did some checks and then found that 'natd' was not running. But this is not happening that frequently, and seems to only have started after the last system update. Could be some sort of race condition. Is there a logfile that natd writes to, so that I may investigate the reason why it is exiting? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
umage wrote: [snip] In my case the router does get the renewed ip, as I described earlier. However, even after waiting 8+ hours, the system will not recover from the outage properly (reason unknown). That's what this thread is all about. When I started the system today, I found that again it had no connectivity. I did some checks and then found that 'natd' was not running. But this is not happening that frequently, and seems to only have started after the last system update. Could be some sort of race condition. Is there a logfile that natd writes to, so that I may investigate the reason why it is exiting? My first gut instinct about your problem was to blame dhclient first. But no NATD would definitely be a problem. I am assuming we are talking about IPFW and NATD here, and it has been many years since I've used it. I migrated to IPFILTER and then on to PF quite some time ago. Most logging related to IPFW is already present, but IIRC to log NATD you need to turn it on, and possibly configure it in syslog.conf should you desire the output somewhere other than /var/log/alias.log. Keep in mind there are two ways to pass options. You can use something like natd_flags=-l in /etc/rc.conf. Man natd will provide a list. The second method is to place the options in a file such as natd.conf and pull them in like natd_flags=-f /etc/natd.conf. I looked in my notes and here is a snippet from an old /etc/rc.conf: natd_enable=YES natd_interface=ppp0 natd_flags=-f /etc/natd.conf My /etc/natd.conf: interface ppp0 use_sockets yes same_ports yes dynamic yes You could add a 'log yes' line here; it does the same as the -l described above. Note that you might need the 'dynamic yes' switch for an interface that changes. In my case I was using it for a ppp dial-up connection, change interface as needed. Sounds like you are narrowing down the culprit(s). Also note that it could possibly be a timing issue related to the order things start up. If the NATD is attempting to start before the interface has come up it will die. Shouldn't happen, but... YMMV -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
When the connection goes down and comes back up it will take 5 minutes before my FreeBSD gateway box checks the lease and decides if a renewal is in order. This is automatic. If I am sitting in front of my computer and I want to speed this up I issue /etc/rc.d/netif restart on the gateway and it will come up and be happy in about 10 seconds, rather than waiting out the 5 minute time out. In my case the router does get the renewed ip, as I described earlier. However, even after waiting 8+ hours, the system will not recover from the outage properly (reason unknown). That's what this thread is all about. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
networking won't come back up until reboot after ISP outage
Hello. I have had 3 network outages this week, and everytime it happened, I found that my freebsd8rc1 machine/router was unable to communicate over the WAN interface even after the outages ended. A reboot helps, but that's not an acceptable solution. The symptoms are very weird: even though dhclient successfully receives a dhcp lease and sets up the interface, I am unable to ping the gateway. The ifconfig utility says the interface is up and configured correctly; netstat -arn says routes are set up as they should be; and tcpdump reports random network traffic arriving on the interface (so the network itself is up and running). Taking the interface down and back up doesn't help, reloading ipfw rules doesn't help. I have some more things to test - whether tcpdump reports any attempts at outgoing traffic, and whether disconnecting/reconnecting the network cable will do anything. And maybe reverting ipfw rules to what I've been using before. Other than this, I have no idea what else to do... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
Have you tried restarting routing? /etc/rc.d/routing restart I have found the same symptoms with other outages and not performing the above. I have done /etc/rc.d/netif restart and /etc/rc.d/routing restart. Wtih using these commands, I have found this to be successful in restoring network interfaces communication, without having to reboot. Hope this helps. On Sat, Nov 07, 2009 at 03:05:40PM +0100, umage thus spake: Hello. I have had 3 network outages this week, and everytime it happened, I found that my freebsd8rc1 machine/router was unable to communicate over the WAN interface even after the outages ended. A reboot helps, but that's not an acceptable solution. The symptoms are very weird: even though dhclient successfully receives a dhcp lease and sets up the interface, I am unable to ping the gateway. The ifconfig utility says the interface is up and configured correctly; netstat -arn says routes are set up as they should be; and tcpdump reports random network traffic arriving on the interface (so the network itself is up and running). Taking the interface down and back up doesn't help, reloading ipfw rules doesn't help. I have some more things to test - whether tcpdump reports any attempts at outgoing traffic, and whether disconnecting/reconnecting the network cable will do anything. And maybe reverting ipfw rules to what I've been using before. Other than this, I have no idea what else to do... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
On 7. 11. 2009 19:07, Jason wrote: Have you tried restarting routing? /etc/rc.d/routing restart I have found the same symptoms with other outages and not performing the above. I have done /etc/rc.d/netif restart and /etc/rc.d/routing restart. Wtih using these commands, I have found this to be successful in restoring network interfaces communication, without having to reboot. Hope this helps. On Sat, Nov 07, 2009 at 03:05:40PM +0100, umage thus spake: Hello. I have had 3 network outages this week, and everytime it happened, I found that my freebsd8rc1 machine/router was unable to communicate over the WAN interface even after the outages ended. A reboot helps, but that's not an acceptable solution. The symptoms are very weird: even though dhclient successfully receives a dhcp lease and sets up the interface, I am unable to ping the gateway. The ifconfig utility says the interface is up and configured correctly; netstat -arn says routes are set up as they should be; and tcpdump reports random network traffic arriving on the interface (so the network itself is up and running). Taking the interface down and back up doesn't help, reloading ipfw rules doesn't help. I have some more things to test - whether tcpdump reports any attempts at outgoing traffic, and whether disconnecting/reconnecting the network cable will do anything. And maybe reverting ipfw rules to what I've been using before. Other than this, I have no idea what else to do... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Thank you for the hint, I will try it when this happens again. Note: the output of netstat -r was identical to what it is currently... FYI: I've been using freebsd 6.2 - 7.2 until now, and I never had to intervene - the system resumed networking as usual. It might have something to do with migrating to 8rc1 (most likely not), or that I'm now using DHCP and there's a glitch somewhere (maybe). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: networking won't come back up until reboot after ISP outage
umage wrote: On 7. 11. 2009 19:07, Jason wrote: Have you tried restarting routing? /etc/rc.d/routing restart I have found the same symptoms with other outages and not performing the above. I have done /etc/rc.d/netif restart and /etc/rc.d/routing restart. [snip] Thank you for the hint, I will try it when this happens again. Note: the output of netstat -r was identical to what it is currently... FYI: I've been using freebsd 6.2 - 7.2 until now, and I never had to intervene - the system resumed networking as usual. It might have something to do with migrating to 8rc1 (most likely not), or that I'm now using DHCP and there's a glitch somewhere (maybe). My configuration is most likely different from yours in that my DSL modem- router is configured for split-bridge. This allows the DSL modem to handle the PPPoE connection and login but passes the WAN IP to my FreeBSD gateway box via DHCP. So the NIC on my gateway is getting it's lease from the DSL modem instead of directly from Verizon. Your DHCP lease is probably coming directly from the ISP I would presume. When the connection goes down and comes back up it will take 5 minutes before my FreeBSD gateway box checks the lease and decides if a renewal is in order. This is automatic. If I am sitting in front of my computer and I want to speed this up I issue /etc/rc.d/netif restart on the gateway and it will come up and be happy in about 10 seconds, rather than waiting out the 5 minute time out. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
DL360 G6 Reboot
On a HP DL360 G6 freebsd 6.4-RELEASE installs but reboots right before login prompt. 7.2 installs and works fine but unfortunately I can not use 7.2 due to some restrictions. Any hints? -- Best regards. Hooman Fazaeli ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
wpi0 went away, though a reboot cures it.
Today, after leaving my Lenovo T61 on overnight to do some compiles, I lost my wireless. I tried a few other things that what I've listed below, but none of it worked. This is a dual boot machine - I also run Windows XP, and don't have any issues with wireless on that OS. Any clues would be appreciated. # uname -a FreeBSD grimsqueaker.pigfarm.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 First, in /var/log/messages, I found the following: Sep 13 15:09:23 grimsqueaker kernel: wpi0: device timeout Sep 13 15:09:23 grimsqueaker kernel: wpi0: link state changed to DOWN Sep 13 15:09:24 grimsqueaker kernel: wpi0: could not set power mode Sep 13 15:09:24 grimsqueaker kernel: wpi0: device config failed So I tried stopping and starting netif: # /etc/rc.d/netif stop Stopping network:wpa_supplicant not running? (check /var/run/wpa_supplicant/wpi0.pid). lo0 em0 wpi0 fwe0 fwip0. # /etc/rc.d/netif start em0: no link .. giving up Starting wpa_supplicant. wpi0: no link .. giving up lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:1c:25:80:db:87 media: Ethernet autoselect status: no carrier wpi0: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:1f:3c:4d:e2:55 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid channel 11 (2462 Mhz 11g) authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 50 bmiss 7 scanvalid 60 protmode CTS roaming MANUAL Then, I let the compile get as far as it could, and rebooted. While rebooting, I noticed this on the console, and found these traces in /var/log/messages: Sep 13 16:05:44 grimsqueaker kernel: interrupt storm detected on irq16:; throttling interrupt source Sep 13 16:05:48 grimsqueaker last message repeated 4 times Sep 13 16:05:49 grimsqueaker syslogd: exiting on signal 15 Sep 13 16:07:38 grimsqueaker syslogd: kernel boot file is /boot/kernel/kernel Sep 13 16:07:38 grimsqueaker kernel: interrupt storm detected on irq16:; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: interrupt storm detected on irq16:; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done Sep 13 16:07:38 grimsqueaker kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...interrupt storm detected on irq16:; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: done Sep 13 16:07:38 grimsqueaker kernel: Waiting (max 60 seconds) for system process `syncer' to stop...interrupt storm detected on irq16:; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: Sep 13 16:07:38 grimsqueaker kernel: Syncing disks, vnodes remaining...0 interrupt storm detected on irq16:; throttling interrupt source Sep 13 16:07:38 grimsqueaker kernel: 0 done Sep 13 16:07:38 grimsqueaker kernel: All buffers synced. Sep 13 16:07:38 grimsqueaker kernel: Uptime: 6h53m12s Sep 13 16:07:38 grimsqueaker kernel: interrupt storm detected on irq16:; throttling interrupt source Thanks, Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
geli disk marked as dirty on normal shutdown/reboot
Hi List, # uname -a FreeBSD the.palaceofretention.ca 7.1-RELEASE-p6 FreeBSD 7.1-RELEASE-p6 #0: Tue Jun 9 16:26:47 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have a geli backed ufs file system: ===fstab=== # ad14.eli esata /dev/ufs/E1TB /edisks/esata0 ufs rw,noauto2 2 I use a passphrase to attach it: # geli attach ad14 Enter passphrase: ** The provider shows up as ad14.eli as expected. The file system on it has a label of E1TB (as seen above). The command: # mount /dev/ufs/E1TB usually works fine. The problem is that if I restart the system normally, the file system on the provider ad14.eli, when reattached, is marked as dirty and I get the usual operation not permitted error. I have to run: # fsck -t ufs /dev/ad14.eli before I can mount it again. This is repeatable and occurs for more than just the one geli provider I use in this example. Am I missing something with respect to properly attaching a geli device? Do I need the '-d' option to detach at last close? Thanks for any help. Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: geli disk marked as dirty on normal shutdown/reboot
On Mon, Aug 31, 2009 at 8:05 PM, Vinny vinny-mail-01+f.questions20090...@palaceofretention.cavinny-mail-01%2bf.questions20090...@palaceofretention.ca wrote: Hi List, # uname -a FreeBSD the.palaceofretention.ca 7.1-RELEASE-p6 FreeBSD 7.1-RELEASE-p6 #0: Tue Jun 9 16:26:47 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have a geli backed ufs file system: ===fstab=== # ad14.eli esata /dev/ufs/E1TB /edisks/esata0 ufs rw,noauto2 2 I use a passphrase to attach it: # geli attach ad14 Enter passphrase: ** The provider shows up as ad14.eli as expected. The file system on it has a label of E1TB (as seen above). The command: # mount /dev/ufs/E1TB usually works fine. The problem is that if I restart the system normally, the file system on the provider ad14.eli, when reattached, is marked as dirty and I get the usual operation not permitted error. I have to run: # fsck -t ufs /dev/ad14.eli before I can mount it again. This is repeatable and occurs for more than just the one geli provider I use in this example. Am I missing something with respect to properly attaching a geli device? Do I need the '-d' option to detach at last close? Thanks for any help. Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Usually I just umount before close. I don't get the need to fsck then. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
