Re: pf firewall and ftp
On 16/04/2012 03:31, Fbsd8 wrote: > > > OK I have uncovered what the problem is. > The pf version running on Freebsd 9.0 matches the version running on > openbsd 4.5. Found it on man pf at the end. > > The documentation on the Openbsd website for pf is for Openbsd 5.0 and > it has warning saying "NOTE: This information is for OpenBSD 4.7. NAT > configuration was significantly different in earlier versions." > http://pf4freebsd.love2party.net/ has more info about how back dated > the 9.0 Freebsd production version of pf is. > > The Freebsd handbook had a detailed section on pf including rules > examples matching the version of pf included with 9.0 But someone > allowed it to be removed in the current version of the handbook. > > So here we are with an outdated version of pf in the current > production 9.0 version of Freebsd and there is no documentation > available on nat rule syntax in the handbook or at openbsd/pf. > > Going to dig through the 9.0 pf man pages for the info > http://ftp.nluug.nl/pub/OpenBSD/doc/pf-faq45.txt might be useful? there is a version of the faq for each version of openbsd from 3.3 - 4.7 Vince > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
SV: pf firewall and ftp
To solve the ftp pre 4.7 part, you can start reading here http://home.nuug.no/~peter/pf/en/long-firewall.html#FTPPROBLEM /Hasse -Oprindelig meddelelse- Fra: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] På vegne af Fbsd8 Sendt: den 16 april 2012 04:31 Til: FreeBSD Questions; FreeBSD Current; FreeBSD doc Emne: Re: pf firewall and ftp Fbsd8 wrote: > Running 9.0 as a gateway host with pf firewall enabled. > FTP is launched by inetd. > Both active and passive ftp works from lan pc's to the host ftp. > The lan ftp session can be initiated from the host or any lan pc and > things work because there are no rules on the lan interface except > single pass all rule. > > But I can not do host initiated or lan initiated ftp sessions to the > public internet. Get "operation not permitted" message. Tried to setup > ftp-proxy per openbsd pf manual without any joy. > > Looking for working rule set with nat and ftp services to study and > learn from. > > > OK I have uncovered what the problem is. The pf version running on Freebsd 9.0 matches the version running on openbsd 4.5. Found it on man pf at the end. The documentation on the Openbsd website for pf is for Openbsd 5.0 and it has warning saying "NOTE: This information is for OpenBSD 4.7. NAT configuration was significantly different in earlier versions." http://pf4freebsd.love2party.net/ has more info about how back dated the 9.0 Freebsd production version of pf is. The Freebsd handbook had a detailed section on pf including rules examples matching the version of pf included with 9.0 But someone allowed it to be removed in the current version of the handbook. So here we are with an outdated version of pf in the current production 9.0 version of Freebsd and there is no documentation available on nat rule syntax in the handbook or at openbsd/pf. Going to dig through the 9.0 pf man pages for the info ___ freebsd-questi...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On 04/15/12 12:30, Conrad J. Sabatier wrote: > Today I'm suddenly unable to boot a newly built kernel without crashing > right near the end of the device probes, just before the system is > about to actually come up: > > Fatal trap 18: integer divide fault while in kernel mode > > Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 > divl 0x50(%rcx),%eax > > Backtrace lists this chain of calls: > g_label_ufs_taste_common > g_label_taste > g_new_provider_event > g_run_events > g_event_procbody > fork_exit > fork_trampoline > > Whether built with clang or gcc, CUSTOM config or GENERIC, same results > on rebooting. No idea why this suddenly started happening, haven't > changed anything at all in my setup. My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are attached to a Dell UltraSharp U2711 screen which does have a built-in USB/MMC hub. I realized that it was possible to log into my lab's box from remote when I'm not in the lab and that is usually coincidentally with a switched off screen. This morning I loged in from home, loged out and got to the office, switched on the screen - and reboot! I wasn't able to get the system running again, it always got stuck in a Fatal trap 18: integer divide fault while in kernel mode Unplugging the screen's USB hub makes the system booting again! Following is one of the last logged messages from the kernel, I don not know whether this is usefull looking for the problem. Regards, Oliver Apr 12 15:32:33 telesto kernel: hwpmc: SOFT/16/64/0x67 TSC/1/64/0x20 IAP/4/48/0x3ff IAF/3/48/0x61 UCP/8/48/0x3f8 UCF/1/48/0x60 Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self powered Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self powered Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 Apr 12 15:32:33 telesto kernel: uhub4: on usbus3 Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 Apr 12 15:32:33 telesto kernel: uhub5: on usbus0 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self powered Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 Apr 12 15:32:33 telesto kernel: ukbd0: on usbus3 Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 Apr 12 15:32:33 telesto kernel: uhid0: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 Apr 12 15:32:33 telesto kernel: uhub6: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 Apr 12 15:32:33 telesto kernel: uhub7: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 Apr 12 15:32:33 telesto kernel: umass0: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Apr 12 15:32:33 telesto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 lun 0 Apr 12 15:32:33 telesto kernel: da0: Removable Direct Access SCSI-0 device Apr 12 15:32:33 telesto kernel: da0: 40.000MB/s transfers Apr 12 15:32:33 telesto kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Apr 12 15:32:33 telesto kernel: ugen3.7: at usbus3 Apr 12 15:32:33 telesto kernel: ums0: on usbus3 Apr 12 15:32:33 telesto kernel: ums0: 8 buttons and [XYZT] coordinates ID=0 Apr 12 15:32:33 telesto kernel: Trying to mount root from ufs:/dev/gpt/root [rw]... Apr 12 15:32:33 telesto kernel: nvidia0: on vgapci0 Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested pci_enable_io Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested pci_enable_io Apr 12 15:32:33 telesto kernel: vboxdrv: fAsync=0 offMin=0x2d8 offMax=0x603c Apr 12 15:32:33 telesto kernel: module_register: module ng_ether already exists! Apr 12 15:32:33 telesto kernel: Module ng_ether failed to register: 17 signature.asc Description: OpenPGP digital signature
Re: SV: pf firewall and ftp
On Mon, Apr 16, 2012 at 09:39:38AM +0200, Hasse Hansson wrote: > To solve the ftp pre 4.7 part, you can start reading here > http://home.nuug.no/~peter/pf/en/long-firewall.html#FTPPROBLEM > > /Hasse > -Oprindelig meddelelse- > Fra: owner-freebsd-questi...@freebsd.org > [mailto:owner-freebsd-questi...@freebsd.org] På vegne af Fbsd8 > Sendt: den 16 april 2012 04:31 > Til: FreeBSD Questions; FreeBSD Current; FreeBSD doc > Emne: Re: pf firewall and ftp > > Fbsd8 wrote: > > Running 9.0 as a gateway host with pf firewall enabled. > > FTP is launched by inetd. > > Both active and passive ftp works from lan pc's to the host ftp. > > The lan ftp session can be initiated from the host or any lan pc and > > things work because there are no rules on the lan interface except > > single pass all rule. > > > > But I can not do host initiated or lan initiated ftp sessions to the > > public internet. Get "operation not permitted" message. Tried to setup > > ftp-proxy per openbsd pf manual without any joy. > > > > Looking for working rule set with nat and ftp services to study and > > learn from. > > > > > > > > OK I have uncovered what the problem is. > The pf version running on Freebsd 9.0 matches the version running on openbsd > 4.5. Found it on man pf at the end. > > The documentation on the Openbsd website for pf is for Openbsd 5.0 and it > has warning saying "NOTE: This information is for OpenBSD 4.7. NAT > configuration was significantly different in earlier versions." > http://pf4freebsd.love2party.net/ has more info about how back dated the > 9.0 Freebsd production version of pf is. > > The Freebsd handbook had a detailed section on pf including rules examples > matching the version of pf included with 9.0 But someone allowed it to be > removed in the current version of the handbook. > > So here we are with an outdated version of pf in the current production > 9.0 version of Freebsd and there is no documentation available on nat rule > syntax in the handbook or at openbsd/pf. The version of PF in FreeBSD is corresponds to the one in OpenBSD 4.5. There are old versions of the OpenBSD PF FAQ on mirrors: http://ftp2.eu.openbsd.org/pub/OpenBSD/doc/history/pf-faq45.pdf http://ftp2.eu.openbsd.org/pub/OpenBSD/doc/history/pf-faq45.txt > Going to dig through the 9.0 pf man pages for the info The rules should also be documented in the man pages. -- Denny Lin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
da0 takes a long time to appear
Hi, I recently had to replace the enclosure of an external USB harddisk (WD E1U1E Elements). With the new one (Trekstor DataStation maxi n.u 3,5"), it now takes over one minute between the detection of umass0 and da0. After that it works fine. Is this delay due to the hardware or is the kernel at fault? Any debug information I should provide? I'm running head r234133. Apr 16 14:43:35 mole kernel: ugen7.2: at usbus7 Apr 16 14:43:35 mole kernel: umass0: on usbus7 Apr 16 14:44:49 mole kernel: da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 Apr 16 14:44:49 mole kernel: da0: Fixed Direct Access SCSI-2 device Apr 16 14:44:49 mole kernel: da0: 40.000MB/s transfers Apr 16 14:44:49 mole kernel: da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) Stefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On 04/16/12 01:57, O. Hartmann wrote: > On 04/15/12 12:30, Conrad J. Sabatier wrote: >> Today I'm suddenly unable to boot a newly built kernel without crashing >> right near the end of the device probes, just before the system is >> about to actually come up: >> >> Fatal trap 18: integer divide fault while in kernel mode >> >> Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 >> divl 0x50(%rcx),%eax >> >> Backtrace lists this chain of calls: >> g_label_ufs_taste_common >> g_label_taste >> g_new_provider_event >> g_run_events >> g_event_procbody >> fork_exit >> fork_trampoline >> >> Whether built with clang or gcc, CUSTOM config or GENERIC, same results >> on rebooting. No idea why this suddenly started happening, haven't >> changed anything at all in my setup. > My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: > Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are > attached to a Dell UltraSharp U2711 screen which does have a built-in > USB/MMC hub. I realized that it was possible to log into my lab's box > from remote when I'm not in the lab and that is usually coincidentally > with a switched off screen. > This morning I loged in from home, loged out and got to the office, > switched on the screen - and reboot! I wasn't able to get the system > running again, it always got stuck in a > > Fatal trap 18: integer divide fault while in kernel mode > > Unplugging the screen's USB hub makes the system booting again! > > Following is one of the last logged messages from the kernel, I don not > know whether this is usefull looking for the problem. > > Regards, > Oliver > > Apr 12 15:32:33 telesto kernel: hwpmc: > SOFT/16/64/0x67 TSC/1/64/0x20 > IAP/4/48/0x3ff > IAF/3/48/0x61 UCP/8/48/0x3f8 > UCF/1/48/0x60 > Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self > powered > Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self > powered > Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self > powered > Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self > powered > Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 > Apr 12 15:32:33 telesto kernel: uhub4: class 9/0, rev 2.00/0.00, addr 2> on usbus3 > Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 > Apr 12 15:32:33 telesto kernel: uhub5: class 9/0, rev 2.00/0.00, addr 2> on usbus0 > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 > Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self > powered > Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self > powered > Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 > Apr 12 15:32:33 telesto kernel: ukbd0: class 0/0, rev 2.00/1.11, addr 3> on usbus3 > Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 > Apr 12 15:32:33 telesto kernel: uhid0: class 0/0, rev 2.00/1.11, addr 3> on usbus3 > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 > Apr 12 15:32:33 telesto kernel: uhub6: class 9/0, rev 2.00/0.00, addr 4> on usbus3 > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self > powered > Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 > Apr 12 15:32:33 telesto kernel: uhub7: class 9/0, rev 2.00/0.00, addr 5> on usbus3 > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self > powered > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 > Apr 12 15:32:33 telesto kernel: umass0: Reader, class 0/0, rev 2.00/1.91, addr 6> on usbus3 > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT > READY. CDB: 0 0 0 0 0 0 > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: > SCSI Status Error > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: > Check Condition > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI sense: > NOT READY asc:3a,0 (Medium not present) > Apr 12 15:32:33 telesto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 > lun 0 > Apr 12 15:32:33 telesto kernel: da0: > Removable Direct Access SCSI-0 device > Apr 12 15:32:33 telesto kernel: da0: 40.000MB/s transfers > Apr 12 15:32:33 telesto kernel: da0: Attempt to query device size > failed: NOT READY, Medium not present > Apr 12 15:32:33 telesto kernel: ugen3.7: at usbus3 > Apr 12 15:32:33 telesto kernel: ums0: 0/0, rev 2.00/56.01, addr 7> on usbus3 > Apr 12 15:32:33 telesto kernel: ums0: 8 buttons and [XYZT] coordinates ID=0 > Apr 12 15:32:33 telesto kernel: Trying to mount root from > ufs:/dev/gpt/root [rw]... > Apr 12 15:32:33 telesto kernel: nvidia0: on vgapci0 > Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested > pci_enable_io > Apr 12 15:32
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On Mon, Apr 16, 2012 at 07:35:23AM -0700, matt wrote: > On 04/16/12 01:57, O. Hartmann wrote: > > On 04/15/12 12:30, Conrad J. Sabatier wrote: > >> Today I'm suddenly unable to boot a newly built kernel without crashing > >> right near the end of the device probes, just before the system is > >> about to actually come up: > >> > >> Fatal trap 18: integer divide fault while in kernel mode > >> > >> Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 > >> divl 0x50(%rcx),%eax > >> > >> Backtrace lists this chain of calls: > >> g_label_ufs_taste_common > >> g_label_taste > >> g_new_provider_event > >> g_run_events > >> g_event_procbody > >> fork_exit > >> fork_trampoline > >> > >> Whether built with clang or gcc, CUSTOM config or GENERIC, same results > >> on rebooting. No idea why this suddenly started happening, haven't > >> changed anything at all in my setup. > > My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: > > Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are > > attached to a Dell UltraSharp U2711 screen which does have a built-in > > USB/MMC hub. I realized that it was possible to log into my lab's box > > from remote when I'm not in the lab and that is usually coincidentally > > with a switched off screen. > > This morning I loged in from home, loged out and got to the office, > > switched on the screen - and reboot! I wasn't able to get the system > > running again, it always got stuck in a > > > > Fatal trap 18: integer divide fault while in kernel mode > > > > Unplugging the screen's USB hub makes the system booting again! > > > > Following is one of the last logged messages from the kernel, I don not > > know whether this is usefull looking for the problem. > > > > Regards, > > Oliver > > > > Apr 12 15:32:33 telesto kernel: hwpmc: > > SOFT/16/64/0x67 TSC/1/64/0x20 > > IAP/4/48/0x3ff > > IAF/3/48/0x61 UCP/8/48/0x3f8 > > UCF/1/48/0x60 > > Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 > > Apr 12 15:32:33 telesto kernel: uhub4: > class 9/0, rev 2.00/0.00, addr 2> on usbus3 > > Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 > > Apr 12 15:32:33 telesto kernel: uhub5: > class 9/0, rev 2.00/0.00, addr 2> on usbus0 > > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 > > Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 > > Apr 12 15:32:33 telesto kernel: ukbd0: > class 0/0, rev 2.00/1.11, addr 3> on usbus3 > > Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 > > Apr 12 15:32:33 telesto kernel: uhid0: > class 0/0, rev 2.00/1.11, addr 3> on usbus3 > > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > > Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 > > Apr 12 15:32:33 telesto kernel: uhub6: > class 9/0, rev 2.00/0.00, addr 4> on usbus3 > > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > > Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 > > Apr 12 15:32:33 telesto kernel: uhub7: > class 9/0, rev 2.00/0.00, addr 5> on usbus3 > > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > > Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self > > powered > > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > > Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 > > Apr 12 15:32:33 telesto kernel: umass0: > Reader, class 0/0, rev 2.00/1.91, addr 6> on usbus3 > > Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT > > READY. CDB: 0 0 0 0 0 0 > > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: > > SCSI Status Error > > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: > > Check Condition > > Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI sense: > > NOT READY asc:3a,0 (Medium not present) > > Apr 12 15:32:33 telesto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 > > lun 0 > > Apr 12 15:32:33 telesto kernel: da0: > > Removable Direct Access SCSI-0 device > > Apr 12 15:32:33 telesto kernel: da0: 40.000MB/s transfers > > Apr 12 15:32:33 telesto kernel: da0: Attempt to query device size > > failed: NOT READY, Medium not present > > Apr 12 15:32:33 telesto kernel: ugen3.7: at usbus3 > > Apr 12 15:32:33 telesto kernel: ums0: > 0/0, rev 2.00/56.01, addr 7> on usbus3 > > Apr 12 15:32:33 telesto kernel: ums0: 8 bu
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On 16.04.2012 16:55 (UTC+1), Konstantin Belousov wrote: On Mon, Apr 16, 2012 at 07:35:23AM -0700, matt wrote: On 04/16/12 01:57, O. Hartmann wrote: On 04/15/12 12:30, Conrad J. Sabatier wrote: Today I'm suddenly unable to boot a newly built kernel without crashing right near the end of the device probes, just before the system is about to actually come up: Fatal trap 18: integer divide fault while in kernel mode Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 divl 0x50(%rcx),%eax Backtrace lists this chain of calls: g_label_ufs_taste_common g_label_taste g_new_provider_event g_run_events g_event_procbody fork_exit fork_trampoline Whether built with clang or gcc, CUSTOM config or GENERIC, same results on rebooting. No idea why this suddenly started happening, haven't changed anything at all in my setup. My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are attached to a Dell UltraSharp U2711 screen which does have a built-in USB/MMC hub. I realized that it was possible to log into my lab's box from remote when I'm not in the lab and that is usually coincidentally with a switched off screen. This morning I loged in from home, loged out and got to the office, switched on the screen - and reboot! I wasn't able to get the system running again, it always got stuck in a Fatal trap 18: integer divide fault while in kernel mode Unplugging the screen's USB hub makes the system booting again! Following is one of the last logged messages from the kernel, I don not know whether this is usefull looking for the problem. Regards, Oliver Apr 12 15:32:33 telesto kernel: hwpmc: SOFT/16/64/0x67 TSC/1/64/0x20 IAP/4/48/0x3ff IAF/3/48/0x61 UCP/8/48/0x3f8 UCF/1/48/0x60 Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self powered Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self powered Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 Apr 12 15:32:33 telesto kernel: uhub4: on usbus3 Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 Apr 12 15:32:33 telesto kernel: uhub5: on usbus0 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self powered Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 Apr 12 15:32:33 telesto kernel: ukbd0: on usbus3 Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 Apr 12 15:32:33 telesto kernel: uhid0: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 Apr 12 15:32:33 telesto kernel: uhub6: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 Apr 12 15:32:33 telesto kernel: uhub7: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 Apr 12 15:32:33 telesto kernel: umass0: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Apr 12 15:32:33 telesto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 lun 0 Apr 12 15:32:33 telesto kernel: da0: Removable Direct Access SCSI-0 device Apr 12 15:32:33 telesto kernel: da0: 40.000MB/s transfers Apr 12 15:32:33 telesto kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Apr 12 15:32:33 telesto kernel: ugen3.7: at usbus3 Apr 12 15:32:33 telesto kernel: ums0: on usbus3 Apr 12 15:32:33 telesto kernel: ums0: 8 buttons and [XYZT] coordinates ID=0 Apr 12 15:32:33 telesto kernel: Trying to mount root from ufs:/dev/gpt/root [rw]... Apr 12 15:32:33 telesto kernel: nvidia0: on vgapci0 Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested pci_enable_io Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested pci_enable_io Apr 12 15:32:33 telesto kernel: vboxdrv: fAsync=0 offMin=0x2d8 offMax=0x603c Apr 12 15:32:33 telesto kernel: module_register: module ng_ether already exists! Apr 12 15:32:33 telesto kernel: Module ng_ether failed to register: 17 Disconnect "Generic Ultra HS-SD/MMC" device which is presenting da0...same problem her
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On Mon, Apr 16, 2012 at 06:15:32PM +0200, Rainer Hurling wrote: > On 16.04.2012 16:55 (UTC+1), Konstantin Belousov wrote: > >On Mon, Apr 16, 2012 at 07:35:23AM -0700, matt wrote: > >>On 04/16/12 01:57, O. Hartmann wrote: > >>>On 04/15/12 12:30, Conrad J. Sabatier wrote: > Today I'm suddenly unable to boot a newly built kernel without crashing > right near the end of the device probes, just before the system is > about to actually come up: > > Fatal trap 18: integer divide fault while in kernel mode > > Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 > divl 0x50(%rcx),%eax > > Backtrace lists this chain of calls: > g_label_ufs_taste_common > g_label_taste > g_new_provider_event > g_run_events > g_event_procbody > fork_exit > fork_trampoline > > Whether built with clang or gcc, CUSTOM config or GENERIC, same results > on rebooting. No idea why this suddenly started happening, haven't > changed anything at all in my setup. > >>>My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: > >>>Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are > >>>attached to a Dell UltraSharp U2711 screen which does have a built-in > >>>USB/MMC hub. I realized that it was possible to log into my lab's box > >>>from remote when I'm not in the lab and that is usually coincidentally > >>>with a switched off screen. > >>>This morning I loged in from home, loged out and got to the office, > >>>switched on the screen - and reboot! I wasn't able to get the system > >>>running again, it always got stuck in a > >>> > >>>Fatal trap 18: integer divide fault while in kernel mode > >>> > >>>Unplugging the screen's USB hub makes the system booting again! > >>> > >>>Following is one of the last logged messages from the kernel, I don not > >>>know whether this is usefull looking for the problem. > >>> > >>>Regards, > >>>Oliver > >>> > >>>Apr 12 15:32:33 telesto kernel: hwpmc: > >>>SOFT/16/64/0x67 TSC/1/64/0x20 > >>>IAP/4/48/0x3ff > >>>IAF/3/48/0x61 UCP/8/48/0x3f8 > >>>UCF/1/48/0x60 > >>>Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 > >>>Apr 12 15:32:33 telesto kernel: uhub4: >>>class 9/0, rev 2.00/0.00, addr 2> on usbus3 > >>>Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 > >>>Apr 12 15:32:33 telesto kernel: uhub5: >>>class 9/0, rev 2.00/0.00, addr 2> on usbus0 > >>>Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 > >>>Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 > >>>Apr 12 15:32:33 telesto kernel: ukbd0: >>>class 0/0, rev 2.00/1.11, addr 3> on usbus3 > >>>Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 > >>>Apr 12 15:32:33 telesto kernel: uhid0: >>>class 0/0, rev 2.00/1.11, addr 3> on usbus3 > >>>Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >>>Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 > >>>Apr 12 15:32:33 telesto kernel: uhub6: >>>class 9/0, rev 2.00/0.00, addr 4> on usbus3 > >>>Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >>>Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 > >>>Apr 12 15:32:33 telesto kernel: uhub7: >>>class 9/0, rev 2.00/0.00, addr 5> on usbus3 > >>>Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >>>Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self > >>>powered > >>>Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >>>Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 > >>>Apr 12 15:32:33 telesto kernel: umass0: >>>Reader, class 0/0, rev 2.00/1.91, addr 6> on usbus3 > >>>Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >>>Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT > >>>READY. CDB: 0 0 0 0 0 0 > >>>Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: > >>>SCSI Status Error > >>>Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: > >>>Check Condition > >>>Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI sense: > >>>NOT READY asc:3a,0 (Medium not present) > >>>Apr 12 15:32:33 telesto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 > >>>lun 0 > >>>Apr 12 15:32:33 telesto kernel: da0: > >>>Removable Direct Access SCSI-0 device > >>>Apr 12 15:32:33 telesto kernel: da0: 40.000MB/s transfers > >>>Apr 12 15:32:33 telesto kernel: da0: Attempt to query
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On 16.04.2012 19:31 (UTC+1), Konstantin Belousov wrote: On Mon, Apr 16, 2012 at 06:15:32PM +0200, Rainer Hurling wrote: On 16.04.2012 16:55 (UTC+1), Konstantin Belousov wrote: On Mon, Apr 16, 2012 at 07:35:23AM -0700, matt wrote: On 04/16/12 01:57, O. Hartmann wrote: On 04/15/12 12:30, Conrad J. Sabatier wrote: Today I'm suddenly unable to boot a newly built kernel without crashing right near the end of the device probes, just before the system is about to actually come up: Fatal trap 18: integer divide fault while in kernel mode Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 divl 0x50(%rcx),%eax Backtrace lists this chain of calls: g_label_ufs_taste_common g_label_taste g_new_provider_event g_run_events g_event_procbody fork_exit fork_trampoline Whether built with clang or gcc, CUSTOM config or GENERIC, same results on rebooting. No idea why this suddenly started happening, haven't changed anything at all in my setup. My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are attached to a Dell UltraSharp U2711 screen which does have a built-in USB/MMC hub. I realized that it was possible to log into my lab's box >from remote when I'm not in the lab and that is usually coincidentally with a switched off screen. This morning I loged in from home, loged out and got to the office, switched on the screen - and reboot! I wasn't able to get the system running again, it always got stuck in a Fatal trap 18: integer divide fault while in kernel mode Unplugging the screen's USB hub makes the system booting again! Following is one of the last logged messages from the kernel, I don not know whether this is usefull looking for the problem. Regards, Oliver Apr 12 15:32:33 telesto kernel: hwpmc: SOFT/16/64/0x67 TSC/1/64/0x20 IAP/4/48/0x3ff IAF/3/48/0x61 UCP/8/48/0x3f8 UCF/1/48/0x60 Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self powered Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self powered Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 Apr 12 15:32:33 telesto kernel: uhub4: on usbus3 Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 Apr 12 15:32:33 telesto kernel: uhub5: on usbus0 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self powered Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 Apr 12 15:32:33 telesto kernel: ukbd0: on usbus3 Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 Apr 12 15:32:33 telesto kernel: uhid0: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 Apr 12 15:32:33 telesto kernel: uhub6: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 Apr 12 15:32:33 telesto kernel: uhub7: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self powered Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 Apr 12 15:32:33 telesto kernel: umass0: on usbus3 Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Apr 12 15:32:33 telesto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 lun 0 Apr 12 15:32:33 telesto kernel: da0: Removable Direct Access SCSI-0 device Apr 12 15:32:33 telesto kernel: da0: 40.000MB/s transfers Apr 12 15:32:33 telesto kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Apr 12 15:32:33 telesto kernel: ugen3.7: at usbus3 Apr 12 15:32:33 telesto kernel: ums0: on usbus3 Apr 12 15:32:33 telesto kernel: ums0: 8 buttons and [XYZT] coordinates ID=0 Apr 12 15:32:33 telesto kernel: Trying to mount root from ufs:/dev/gpt/root [rw]... Apr 12 15:32:33 telesto kernel: nvidia0: on vgapci0 Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested pci_enable_io Apr 12 15:32:33 telesto kernel: vgapci0: child nvidia0 requested pci_enable_io Apr 12 15:32:33 telesto kernel: vboxdrv: fAsync=0 offMin=0x2d8 offMax=0x603c Apr 12 15:32:33 telesto kernel: module_register: module ng_ether already exists! Apr 12 15:32:33
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On Mon, Apr 16, 2012 at 07:58:57PM +0200, Rainer Hurling wrote: > On 16.04.2012 19:31 (UTC+1), Konstantin Belousov wrote: > >On Mon, Apr 16, 2012 at 06:15:32PM +0200, Rainer Hurling wrote: > >>On 16.04.2012 16:55 (UTC+1), Konstantin Belousov wrote: > >>>On Mon, Apr 16, 2012 at 07:35:23AM -0700, matt wrote: > On 04/16/12 01:57, O. Hartmann wrote: > >On 04/15/12 12:30, Conrad J. Sabatier wrote: > >>Today I'm suddenly unable to boot a newly built kernel without > >>crashing > >>right near the end of the device probes, just before the system is > >>about to actually come up: > >> > >>Fatal trap 18: integer divide fault while in kernel mode > >> > >>Stopped at 0x803b2646 = g_label_ufs_taste_common+0x36 > >>divl 0x50(%rcx),%eax > >> > >>Backtrace lists this chain of calls: > >>g_label_ufs_taste_common > >>g_label_taste > >>g_new_provider_event > >>g_run_events > >>g_event_procbody > >>fork_exit > >>fork_trampoline > >> > >>Whether built with clang or gcc, CUSTOM config or GENERIC, same > >>results > >>on rebooting. No idea why this suddenly started happening, haven't > >>changed anything at all in my setup. > >My recent kernel does the same on two "FreeBSD 10.0-CURRENT #1 r234309: > >Sun Apr 15 14:14:11 CEST 2012" boxes. Both boxes in common is they are > >attached to a Dell UltraSharp U2711 screen which does have a built-in > >USB/MMC hub. I realized that it was possible to log into my lab's box > >from remote when I'm not in the lab and that is usually coincidentally > >with a switched off screen. > >This morning I loged in from home, loged out and got to the office, > >switched on the screen - and reboot! I wasn't able to get the system > >running again, it always got stuck in a > > > >Fatal trap 18: integer divide fault while in kernel mode > > > >Unplugging the screen's USB hub makes the system booting again! > > > >Following is one of the last logged messages from the kernel, I don not > >know whether this is usefull looking for the problem. > > > >Regards, > >Oliver > > > >Apr 12 15:32:33 telesto kernel: hwpmc: > >SOFT/16/64/0x67 TSC/1/64/0x20 > >IAP/4/48/0x3ff > >IAF/3/48/0x61 > >UCP/8/48/0x3f8 > >UCF/1/48/0x60 > >Apr 12 15:32:33 telesto kernel: uhub1: 4 ports with 4 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: uhub2: 4 ports with 4 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: uhub3: 2 ports with 2 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: uhub0: 2 ports with 2 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: ugen3.2: at usbus3 > >Apr 12 15:32:33 telesto kernel: uhub4: >class 9/0, rev 2.00/0.00, addr 2> on usbus3 > >Apr 12 15:32:33 telesto kernel: ugen0.2: at usbus0 > >Apr 12 15:32:33 telesto kernel: uhub5: >class 9/0, rev 2.00/0.00, addr 2> on usbus0 > >Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 usbus0 > >Apr 12 15:32:33 telesto kernel: uhub5: 6 ports with 6 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: uhub4: 8 ports with 8 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: ugen3.3: at usbus3 > >Apr 12 15:32:33 telesto kernel: ukbd0: >class 0/0, rev 2.00/1.11, addr 3> on usbus3 > >Apr 12 15:32:33 telesto kernel: kbd2 at ukbd0 > >Apr 12 15:32:33 telesto kernel: uhid0: >class 0/0, rev 2.00/1.11, addr 3> on usbus3 > >Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >Apr 12 15:32:33 telesto kernel: ugen3.4: at usbus3 > >Apr 12 15:32:33 telesto kernel: uhub6: >class 9/0, rev 2.00/0.00, addr 4> on usbus3 > >Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >Apr 12 15:32:33 telesto kernel: uhub6: 3 ports with 2 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: ugen3.5: at usbus3 > >Apr 12 15:32:33 telesto kernel: uhub7: >class 9/0, rev 2.00/0.00, addr 5> on usbus3 > >Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >Apr 12 15:32:33 telesto kernel: uhub7: 3 ports with 2 removable, self > >powered > >Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >Apr 12 15:32:33 telesto kernel: ugen3.6: at usbus3 > >Apr 12 15:32:33 telesto kernel: umass0: >Reader, class 0/0, rev 2.00/1.91, addr 6> on usbus3 > >Apr 12 15:32:33 telesto kernel: Root mount waiting for: usbus3 > >Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): TEST UNIT > >READY. CDB: 0 0 0 0 0 0 > >Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): CAM status: > >SCSI Status Error > >Apr 12 15:32:33 telesto kernel: (probe0:umass-sim0:0:0:0): SCSI status: > >Check Condition > >Apr 12 15:32:33 telesto kernel: (probe0:umass
Re: New FreeBSD SVN seed snapshot
On 2012-Apr-13 23:27:03 +1000, Darren Reed wrote: >On 24/08/2010 4:56 AM, Simon L. B. Nielsen wrote: >> I have made a new snapshot of the svn repo which can be used to start new >> FreeBSD svn mirrors. Note that now there's a CTM feed of the svn repo, there are regular svn repo seeds available at ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/svn-cur the latest is like svn-cur.00300xEmpty.xz This can be unpacked with: # ctm -b /where/you/want/svn .../svn-cur.00300xEmpty.xz which will create /where/you/want/svn/base etc You can update the resultant repo with either SVN or CTM (see http://www.freebsd.org/doc/handbook/ctm.html for the latter). Note that not all mirrors carry the CTM subdirectories. -- Peter Jeremy pgp4aRZBU7WeO.pgp Description: PGP signature
Re: Complete hang on 9.0-RELEASE
Hi, [for the record...] On Tue, Feb 14, 2012 at 11:41 AM, Arnaud Lacombe wrote: > Hi folks, > > For the records, I was running some tests yesterday on top of a > 9.0-RELEASE, amd64, kernel when the box hanged. At the time of the > hang, the box was running a process with about 2800 threads with heavy > IPC between 1400 writers and 1400 readers. The box was in single user > mode (/bin/sh coming from FreeBSD 7.4-STABLE). Here is the beginning > of the 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 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 > r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.70-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x106ca Family = 6 Model = 1c Stepping = 10 > Features=0xbfebfbff > Features2=0x40e31d > AMD Features=0x2800 > AMD Features2=0x1 > TSC: P-state invariant, performance statistics > real memory = 2137587712 (2038 MB) > avail memory = 2037841920 (1943 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: <070611 APIC1125> > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP/HT): APIC ID: 3 > > I will restart the test and see if this happens again. > I reproduced the previous problem on 10-CURRENT from r233917, on the following platform (here running 8.2-RELEASE): FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1800.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106ca Family = 6 Model = 1c Stepping = 10 Features=0xbfebfbff Features2=0x40e31d AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 2136539136 (2037 MB) avail memory = 2043772928 (1949 MB) ACPI APIC Table: <010312 APIC0947> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP/HT): APIC ID: 3 Complete system freeze while running about 2400 threads. I had to power cycle the system to get it back alive. I discussed a way to debug this with attilio@ on freebsd-stable@, but still did not had time to implement it. regards, - Arnaud ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: "/sys/conf/kmod.mk", line 111: Malformed conditional (${MK_CLANG_IS_CC}
On Mon, Apr 16, 2012 at 2:45 AM, Dimitry Andric wrote:
> On 2012-04-16 03:03, Chris wrote:
>>
>> I recently updated my system from 8.2-STABLE to 9.0-STABLE and I'm
>> seeing a similar error when trying to build the VirtualBox kernel
>> module:
>>
>> *** Building 'vboxdrv' module ***
>> "/usr/share/mk/bsd.own.mk", line 476: MK_CLANG_IS_CC can't be set by a
>> user.
>> *** Error code 1
>>
>> I tried the tips from all the previous posters with no luck. Any
>> suggestions would greatly be appreciated!
>
>
> It looks like this was caused by Maxim Sobolev's workaround here:
>
> http://lists.freebsd.org/pipermail/cvs-ports/2012-April/24.html
>
> He attempts to set MK_ variables by hand, but that is obviously not
> allowed.
>
> As has been said before, it is indeed possible to put a workaround for
> compiling with the wrong source directory in bsd.own.mk, but that would
> really help people to shoot themselves in the foot.
>
> It looks like the virtualbox-ose-kmod port sets a SRC_BASE variable to
> the appropriate source directory, but it should probably also set the
> MAKESYSPATH environment variable to ${SRC_BASE}/share/mk before invoking
> make.
>
> Note this is still not 100% safe, as you would really need to build
> using a toolchain corresponding to your kernel sources, but it's better
> than nothing.
As a quick-n-dirty workaround, I deleted the three patch files
mentioned in Maxim Sobolev's posting and the port compiles with no
problems. It may be that the version of bsd.own.mk that I have fixes
any compilation issues with clang.
Thanks for the help!
Chris
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: "/sys/conf/kmod.mk", line 111: Malformed conditional (${MK_CLANG_IS_CC}
On Mon, Apr 16, 2012 at 06:41:44PM -0400, Chris wrote:
> On Mon, Apr 16, 2012 at 2:45 AM, Dimitry Andric wrote:
> > On 2012-04-16 03:03, Chris wrote:
> >>
> >> I recently updated my system from 8.2-STABLE to 9.0-STABLE and I'm
> >> seeing a similar error when trying to build the VirtualBox kernel
> >> module:
> >>
> >> *** Building 'vboxdrv' module ***
> >> "/usr/share/mk/bsd.own.mk", line 476: MK_CLANG_IS_CC can't be set by a
> >> user.
> >> *** Error code 1
> >>
> >> I tried the tips from all the previous posters with no luck. Any
> >> suggestions would greatly be appreciated!
> >
> >
> > It looks like this was caused by Maxim Sobolev's workaround here:
> >
> > http://lists.freebsd.org/pipermail/cvs-ports/2012-April/24.html
> >
> > He attempts to set MK_ variables by hand, but that is obviously not
> > allowed.
> >
> > As has been said before, it is indeed possible to put a workaround for
> > compiling with the wrong source directory in bsd.own.mk, but that would
> > really help people to shoot themselves in the foot.
> >
> > It looks like the virtualbox-ose-kmod port sets a SRC_BASE variable to
> > the appropriate source directory, but it should probably also set the
> > MAKESYSPATH environment variable to ${SRC_BASE}/share/mk before invoking
> > make.
> >
> > Note this is still not 100% safe, as you would really need to build
> > using a toolchain corresponding to your kernel sources, but it's better
> > than nothing.
>
> As a quick-n-dirty workaround, I deleted the three patch files
> mentioned in Maxim Sobolev's posting and the port compiles with no
> problems. It may be that the version of bsd.own.mk that I have fixes
> any compilation issues with clang.
>
> Thanks for the help!
>
> Chris
Just to say that I stumbled upon this issue as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2012-April/074409.html
Subject: net/bwi-firmware-kmod "/sys/conf/kmod.mk", line 111: Malformed
conditional (${MK_CLANG_IS_CC} == "no" && ${CC:T:Mclang} != "clang")
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
Wiadomość napisana przez Rainer Hurling w dniu 16 kwi 2012, o godz. 19:58: > On 16.04.2012 19:31 (UTC+1), Konstantin Belousov wrote: >> On Mon, Apr 16, 2012 at 06:15:32PM +0200, Rainer Hurling wrote: >>> >>> I just updated my system to r234342, only downgraded >>> /usr/src/sys/cam/scsi/scsi_da.c to r233746, and now the system is >>> booting again. So obviously there is something wrong with the newest >>> patch to scsi_da.c. >> It is too broad, try to revert exactly one patch and see whether it works. > > Sorry for my bad english. I wanted to say, that I only reverted exactly one > patch (file scsi_da.c from 234177 back to 233746 manually). The rest is up to > r234342. Could you try the patch below? Index: sys/cam/scsi/scsi_da.c === --- sys/cam/scsi/scsi_da.c (revision 234314) +++ sys/cam/scsi/scsi_da.c (working copy) @@ -938,7 +938,9 @@ daopen(struct disk *dp) if (error != 0) xpt_print(periph->path, "unable to retrieve capacity data"); - if (periph->flags & CAM_PERIPH_INVALID) + if (periph->flags & CAM_PERIPH_INVALID || + softc->disk->d_sectorsize == 0 || + softc->disk->d_mediasize == 0) error = ENXIO; if (error == 0 && (softc->flags & DA_FLAG_PACK_REMOVABLE) != 0 && -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel builds, but crashes at boot (amd64, Revision: 234306)
On Tue, Apr 17, 2012 at 03:53:27AM +0200, Edward Tomasz Napieraa wrote: > Wiadomo?? napisana przez Rainer Hurling w dniu 16 kwi 2012, o godz. 19:58: > > On 16.04.2012 19:31 (UTC+1), Konstantin Belousov wrote: > >> On Mon, Apr 16, 2012 at 06:15:32PM +0200, Rainer Hurling wrote: > >>> > >>> I just updated my system to r234342, only downgraded > >>> /usr/src/sys/cam/scsi/scsi_da.c to r233746, and now the system is > >>> booting again. So obviously there is something wrong with the newest > >>> patch to scsi_da.c. > >> It is too broad, try to revert exactly one patch and see whether it works. > > > > Sorry for my bad english. I wanted to say, that I only reverted exactly one > > patch (file scsi_da.c from 234177 back to 233746 manually). The rest is up > > to r234342. > > Could you try the patch below? > > Index: sys/cam/scsi/scsi_da.c > === > --- sys/cam/scsi/scsi_da.c(revision 234314) > +++ sys/cam/scsi/scsi_da.c(working copy) > @@ -938,7 +938,9 @@ daopen(struct disk *dp) > if (error != 0) > xpt_print(periph->path, "unable to retrieve capacity data"); > > - if (periph->flags & CAM_PERIPH_INVALID) > + if (periph->flags & CAM_PERIPH_INVALID || > + softc->disk->d_sectorsize == 0 || > + softc->disk->d_mediasize == 0) > error = ENXIO; > > if (error == 0 && (softc->flags & DA_FLAG_PACK_REMOVABLE) != 0 && > > This patch fixed the problem for me. Thank you! -- Conrad J. Sabatier conr...@cox.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
