Switch to DuckDuckGo Search
   April 18, 2019  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | >

Toggle Join/Part | bottom
[00:33:58] *** andy_js <andy_js!~andy@94.6.62.238> has quit IRC (Quit: andy_js)
[00:34:03] *** clapont <clapont!~clapont@unaffiliated/clapont> has quit IRC (Ping timeout: 255 seconds)
[00:35:51] *** clapont <clapont!~clapont@unaffiliated/clapont> has joined #illumos
[00:47:33] *** jubal <jubal!~jubal@24.237.158.24> has quit IRC (Max SendQ exceeded)
[00:57:55] *** polishdub <polishdub!~polishdub@207.86.38.254> has quit IRC (Quit: leaving)
[01:09:56] *** aszeszo_ <aszeszo_!~aszeszo@unaffiliated/aszeszo> has quit IRC (Ping timeout: 250 seconds)
[01:27:08] *** sarvet <sarvet!~sarvet@dslb-188-101-012-171.188.101.pools.vodafone-ip.de> has quit IRC (Quit: sarvet)
[01:52:14] *** amrfrsh <amrfrsh!~Thunderbi@134.19.177.18> has quit IRC (Ping timeout: 268 seconds)
[01:52:30] *** merzo <merzo!~merzo@216-27-133-95.pool.ukrtel.net> has quit IRC (Ping timeout: 246 seconds)
[01:55:25] *** serapheim <serapheim!~serapheim@DELPHIX-COR.ear2.SanJose1.Level3.net> has quit IRC (Ping timeout: 246 seconds)
[01:57:07] *** lewellyn <lewellyn!~lewellyn@about/windows/lewellyn> has quit IRC (Ping timeout: 240 seconds)
[02:13:23] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has quit IRC (Ping timeout: 245 seconds)
[02:20:44] *** aszeszo <aszeszo!~aszeszo@unaffiliated/aszeszo> has joined #illumos
[02:25:27] *** Kurlon <Kurlon!~Kurlon@98.13.72.207> has joined #illumos
[02:37:57] *** lewellyn <lewellyn!~lewellyn@about/windows/lewellyn> has joined #illumos
[02:37:57] *** ChanServ sets mode: +o lewellyn
[02:38:00] *** lewellyn <lewellyn!~lewellyn@about/windows/lewellyn> has quit IRC (Client Quit)
[02:45:26] *** aszeszo <aszeszo!~aszeszo@unaffiliated/aszeszo> has quit IRC (Quit: aszeszo)
[02:50:52] *** aszeszo <aszeszo!~aszeszo@unaffiliated/aszeszo> has joined #illumos
[02:55:01] *** poige_ <poige_!sid250374@gateway/web/irccloud.com/x-cfzelmoblnastolp> has joined #illumos
[02:56:31] *** fireglow- <fireglow-!~fireglow@fireglow.su> has joined #illumos
[02:57:01] *** glasspelican_ <glasspelican_!~quassel@2607:5300:201:3100::325> has joined #illumos
[02:57:25] *** jeffpc_ <jeffpc_!~jeffpc@josefsipek.net> has joined #illumos
[02:58:03] *** Weedstock <Weedstock!~grumpf@beiss.dessnourst.de> has joined #illumos
[02:58:04] *** pcd_ <pcd_!~pcd@openzfs/developer/pcd> has joined #illumos
[03:00:05] *** Sulako <Sulako!~LV-223@pool-71-248-160-109.bstnma.fios.verizon.net> has joined #illumos
[03:00:12] *** Mer|inDMC <Mer|inDMC!~merlin@163.172.186.44> has joined #illumos
[03:02:40] *** eau <eau!~eau@unaffiliated/eau> has quit IRC (*.net *.split)
[03:02:40] *** wiedi <wiedi!~wiedi@ip5b4096a6.dynamic.kabel-deutschland.de> has quit IRC (*.net *.split)
[03:02:40] *** _Tenchi_ <_Tenchi_!~phil@d-207-255-80-203.paw.cpe.atlanticbb.net> has quit IRC (*.net *.split)
[03:02:40] *** poige <poige!sid250374@gateway/web/irccloud.com/x-yvazhunjznvmfrmn> has quit IRC (*.net *.split)
[03:02:40] *** pcd <pcd!~pcd@openzfs/developer/pcd> has quit IRC (*.net *.split)
[03:02:40] *** MerlinDMC <MerlinDMC!~merlin@2001:bc8:4400:2700::1711> has quit IRC (*.net *.split)
[03:02:40] *** glasspelican <glasspelican!~quassel@2607:5300:201:3100::325> has quit IRC (*.net *.split)
[03:02:40] *** Woodstock <Woodstock!~grumpf@beiss.dessnourst.de> has quit IRC (*.net *.split)
[03:02:40] *** fireglow <fireglow!~fireglow@fireglow.su> has quit IRC (*.net *.split)
[03:02:40] *** jeffpc <jeffpc!~jeffpc@josefsipek.net> has quit IRC (*.net *.split)
[03:02:44] *** fireglow- is now known as fireglow
[03:02:44] *** poige_ is now known as poige
[03:04:03] *** Sulako <Sulako!~LV-223@pool-71-248-160-109.bstnma.fios.verizon.net> has quit IRC (Quit: Leaving)
[03:04:19] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has joined #illumos
[03:06:00] *** ed209 <ed209!~ed209@165.225.128.67> has quit IRC (Ping timeout: 246 seconds)
[03:09:16] *** eau <eau!~eau@unaffiliated/eau> has joined #illumos
[03:10:38] *** newuser482 <newuser482!4a69c138@gateway/web/freenode/ip.74.105.193.56> has joined #illumos
[03:20:08] *** ed209 <ed209!~ed209@165.225.128.67> has joined #illumos
[03:30:46] *** baojg <baojg!~baojg@162.243.44.213> has joined #illumos
[03:56:15] *** _Tenchi_ <_Tenchi_!~phil@d-207-255-80-203.paw.cpe.atlanticbb.net> has joined #illumos
[04:10:37] *** jeffpc_ is now known as jeffpc
[04:20:14] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has quit IRC (Ping timeout: 268 seconds)
[04:55:05] *** jubal <jubal!~jubal@178-0-237-24.gci.net> has joined #illumos
[05:09:41] *** serapheim <serapheim!~serapheim@172.92.5.112> has joined #illumos
[05:30:53] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has joined #illumos
[06:09:03] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has quit IRC (Ping timeout: 246 seconds)
[06:21:18] *** freakazoid0223 <freakazoid0223!~matt@pool-108-52-159-210.phlapa.fios.verizon.net> has quit IRC (Remote host closed the connection)
[06:23:16] *** hemi770_ <hemi770_!~hemi666@unaffiliated/hemi770> has joined #illumos
[06:26:19] *** hemi770 <hemi770!~hemi666@unaffiliated/hemi770> has quit IRC (Ping timeout: 246 seconds)
[06:29:44] *** clapont <clapont!~clapont@unaffiliated/clapont> has quit IRC (Ping timeout: 250 seconds)
[06:31:58] *** clapont <clapont!~clapont@unaffiliated/clapont> has joined #illumos
[06:48:49] *** jimklimov <jimklimov!~jimklimov@31.7.243.238> has joined #illumos
[07:17:55] *** papertigers <papertigers!~papertige@pool-108-55-27-43.bflony.fios.verizon.net> has quit IRC (Ping timeout: 264 seconds)
[07:18:20] <gitomat> [illumos-gate] 10706 gen_drv: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:21:23] <gitomat> [illumos-gate] 10707 tclient: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:24:12] <gitomat> [illumos-gate] 10708 pmcs: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:26:54] <gitomat> [illumos-gate] 10709 ses: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:27:22] *** papertigers <papertigers!~papertige@pool-108-55-27-43.bflony.fios.verizon.net> has joined #illumos
[07:28:12] *** newuser482 <newuser482!4a69c138@gateway/web/freenode/ip.74.105.193.56> has left #illumos
[07:29:12] *** serapheim <serapheim!~serapheim@172.92.5.112> has quit IRC (Ping timeout: 246 seconds)
[07:29:29] <gitomat> [illumos-gate] 10714 usbser: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:32:13] <gitomat> [illumos-gate] 10732 hsfs: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:34:54] <gitomat> [illumos-gate] 10733 specfs: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:35:41] <jimklimov> This nice stream from gitomat matches well a commit message a colleague posted in another project just today:
[07:35:41] <jimklimov> It's the same old bug // On poor old deploy // I so need a hug // Before I go rogue // Pushing on master // 'Cause I got madder
[07:36:28] <tsoome> :D
[07:37:02] <jimklimov> Just couln't pass by this gem without spreading it
[07:37:45] <gitomat> [illumos-gate] 10739 namefs: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:37:51] <jimklimov> And congrats TSoome for the hard work RTIing stuff finally paying off with a steady streamof improvements, thanks! :)
[07:38:08] *** serapheim <serapheim!~serapheim@172.92.5.112> has joined #illumos
[07:39:16] <tsoome> it is not just me, it is all the people doing reviews and helping with suggestions.
[07:40:17] <tsoome> it really is team effort:)
[07:40:38] <jimklimov> but you're the poster boy :)
[07:40:45] <jimklimov> you posted the commits :)
[07:41:28] <tsoome> thats true of course:D
[07:43:00] <gitomat> [illumos-gate] 10736 nfs: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:52:09] <gitomat> [illumos-gate] 10751 emlxs: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:54:25] <gitomat> [illumos-gate] 10760 cmlb: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[07:56:42] <gitomat> [illumos-gate] 10761 dls: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[08:17:53] *** idodeclare <idodeclare!~textual@cpe-76-185-177-63.satx.res.rr.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
[08:18:33] *** idodeclare <idodeclare!~textual@cpe-76-185-177-63.satx.res.rr.com> has joined #illumos
[08:21:42] *** tsoome <tsoome!~tsoome@148-52-235-80.sta.estpak.ee> has quit IRC (Quit: tsoome)
[08:28:28] *** serapheim <serapheim!~serapheim@172.92.5.112> has quit IRC (Ping timeout: 250 seconds)
[08:28:35] *** nikolam <nikolam!~nikolam@unaffiliated/nikolam> has joined #illumos
[08:30:37] <nikolam> illumos takes almost forever to boot inside VirtualBox 6.0.4 , (x)Ubuntu LTS 18.04 as host OS
[08:31:03] <nikolam> Xeon E5420
[08:33:21] *** nikolam <nikolam!~nikolam@unaffiliated/nikolam> has left #illumos ("Leaving")
[08:37:39] *** wiedi <wiedi!~wiedi@ip5b4096a6.dynamic.kabel-deutschland.de> has joined #illumos
[08:38:10] *** idodeclare <idodeclare!~textual@cpe-76-185-177-63.satx.res.rr.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
[08:59:25] *** neuroserve <neuroserve!~toens@195.71.113.124> has joined #illumos
[09:03:35] *** tsoome <tsoome!~tsoome@148-52-235-80.sta.estpak.ee> has joined #illumos
[09:04:55] *** _joes_ <_joes_!~Thunderbi@81.134.255.170> has joined #illumos
[09:05:58] *** jimklimov1 <jimklimov1!~jimklimov@31.7.243.238> has joined #illumos
[09:06:36] *** jimklimov <jimklimov!~jimklimov@31.7.243.238> has quit IRC (Ping timeout: 255 seconds)
[09:23:05] *** BH23 <BH23!~BH23@81.134.255.170> has joined #illumos
[10:18:04] *** merzo <merzo!~merzo@195.20.130.10> has joined #illumos
[10:22:02] *** igork1 <igork1!~igork@178.162.50.254> has joined #illumos
[10:23:37] *** igork <igork!~igork@91.204.56.74> has quit IRC (Ping timeout: 246 seconds)
[10:24:16] *** man_u <man_u!~manu@manu2.gandi.net> has joined #illumos
[10:38:23] *** _joes_ <_joes_!~Thunderbi@81.134.255.170> has quit IRC (Ping timeout: 245 seconds)
[10:38:27] *** BH23 <BH23!~BH23@81.134.255.170> has quit IRC (Ping timeout: 244 seconds)
[10:59:12] *** jimklimov1 <jimklimov1!~jimklimov@31.7.243.238> has quit IRC (Read error: Connection reset by peer)
[10:59:52] *** jimklimov <jimklimov!~jimklimov@31.7.243.238> has joined #illumos
[11:00:44] *** igork1 is now known as igork
[12:10:54] *** leoric <leoric!~alp@pyhalov.cc.rsu.ru> has quit IRC (Remote host closed the connection)
[12:11:53] *** _joes_ <_joes_!~Thunderbi@81.134.255.170> has joined #illumos
[12:12:01] *** BH23 <BH23!~BH23@81.134.255.170> has joined #illumos
[12:13:03] *** leoric <leoric!~alp@pyhalov.cc.rsu.ru> has joined #illumos
[12:20:00] *** ed209 <ed209!~ed209@165.225.128.67> has quit IRC (Remote host closed the connection)
[12:20:07] *** ed209 <ed209!~ed209@165.225.128.67> has joined #illumos
[13:11:01] *** baojg <baojg!~baojg@162.243.44.213> has quit IRC (Remote host closed the connection)
[13:15:00] *** baojg <baojg!~baojg@162.243.44.213> has joined #illumos
[13:21:02] *** Weedstock is now known as Woodstock
[13:23:33] *** baojg <baojg!~baojg@162.243.44.213> has quit IRC (Remote host closed the connection)
[13:41:15] *** _joes_ <_joes_!~Thunderbi@81.134.255.170> has quit IRC (Ping timeout: 246 seconds)
[13:42:01] *** BH23 <BH23!~BH23@81.134.255.170> has quit IRC (Ping timeout: 268 seconds)
[13:56:14] *** hemi770_ is now known as hemi770
[13:57:07] *** _joes_ <_joes_!~Thunderbi@81.134.255.170> has joined #illumos
[13:57:15] *** BH23 <BH23!~BH23@81.134.255.170> has joined #illumos
[14:28:08] *** baojg <baojg!~baojg@162.243.44.213> has joined #illumos
[14:30:43] *** tsoome <tsoome!~tsoome@148-52-235-80.sta.estpak.ee> has quit IRC (Ping timeout: 246 seconds)
[15:09:47] *** baojg <baojg!~baojg@162.243.44.213> has quit IRC (Remote host closed the connection)
[15:12:54] *** Kurlon <Kurlon!~Kurlon@98.13.72.207> has quit IRC (Ping timeout: 255 seconds)
[15:15:34] *** baojg <baojg!~baojg@162.243.44.213> has joined #illumos
[15:16:32] *** baojg <baojg!~baojg@162.243.44.213> has quit IRC (Remote host closed the connection)
[15:17:13] *** tsoome <tsoome!~tsoome@148-52-235-80.sta.estpak.ee> has joined #illumos
[15:21:23] *** baojg <baojg!~baojg@162.243.44.213> has joined #illumos
[15:27:18] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has joined #illumos
[15:28:23] <tsoome> does anyone else want to look on https://www.illumos.org/rb/r/1226/ and https://www.illumos.org/rb/r/1572/ (they will be pushed together)?
[15:29:43] *** baojg <baojg!~baojg@162.243.44.213> has quit IRC (Remote host closed the connection)
[15:33:07] *** baojg <baojg!~baojg@162.243.44.213> has joined #illumos
[15:35:51] *** aszeszo_ <aszeszo_!~aszeszo@unaffiliated/aszeszo> has joined #illumos
[15:37:28] *** aszeszo <aszeszo!~aszeszo@unaffiliated/aszeszo> has quit IRC (Ping timeout: 250 seconds)
[15:44:27] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has joined #illumos
[15:49:21] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has quit IRC (Ping timeout: 255 seconds)
[15:51:26] *** baojg <baojg!~baojg@162.243.44.213> has quit IRC (Remote host closed the connection)
[15:52:04] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has joined #illumos
[16:00:36] *** fanta1 <fanta1!~fanta1@p200300F76BC63B0019E63CC0A71DCF9B.dip0.t-ipconnect.de> has joined #illumos
[16:01:01] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has quit IRC (Ping timeout: 246 seconds)
[16:07:10] <gitomat> [illumos-gate] 10755 pset: NULL pointer errors -- Toomas Soome <tsoome at me dot com>
[16:15:29] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has joined #illumos
[16:16:48] *** merzo <merzo!~merzo@195.20.130.10> has quit IRC (Ping timeout: 255 seconds)
[16:19:17] *** amrfrsh <amrfrsh!~Thunderbi@134.19.177.23> has joined #illumos
[16:36:16] *** fanta1 <fanta1!~fanta1@p200300F76BC63B0019E63CC0A71DCF9B.dip0.t-ipconnect.de> has quit IRC (Quit: fanta1)
[16:38:17] *** squigley <squigley!602e22de@gateway/web/freenode/ip.96.46.34.222> has joined #illumos
[16:39:25] *** freakazoid0223 <freakazoid0223!~matt@pool-108-52-159-210.phlapa.fios.verizon.net> has joined #illumos
[16:40:24] <squigley> hello, I am trying to ipxe boot dilos, and while it loads the unix kernel and boot_archive files over tftp, when it tries to boot, it is saying "krtls: failed to open tftp://[myip]/path/to/unix", "krtload: bind primary() no relocation information found for module.."
[16:40:46] <squigley> I am pretty sure I am doing something wrong in the ipxe script
[16:41:17] <squigley> I have "kernel pxelinux/images/dilos/unix /platform/i86pc/kernel/amd64/unix -B prom_debug=1,kbm_debug=1 -kvd" "initrd pxelinux/images/dilos/boot_archive" "boot"
[16:43:56] *** serapheim <serapheim!~serapheim@DELPHIX-COR.ear2.SanJose1.Level3.net> has joined #illumos
[16:47:18] <igork> squigley: what is your release ?
[16:47:45] <igork> 2.0.1.63 ?
[16:48:19] <squigley> heh, hi igork, I saw your name in some logs from this channel with a similar problem. latest dilos ipxe image, downloaded it yesterday
[16:48:52] <squigley> dilos-2.0.1.63-pxe.tar.gz
[16:48:57] <igork> well - it's ok
[16:49:11] <igork> i can paste example what i'm using, one moment
[16:50:21] <squigley> I untarred it, and moved the unix and boot_archive files under my tftpboot directory, and ipxe is able to load both of them. I think it's something funny with the way the path to the unix kernel file is being passed to the kernel which it has already loaded into mem, which it's trying to find in the boot_archive
[16:51:24] *** merzo <merzo!~merzo@195.20.130.10> has joined #illumos
[16:52:29] <igork> squigley: https://paste.dilos.org/?a3aaaab44ebac213#wK4DXs0SaUgpkMpYxXmY4xIh+bPMr8lvUHtL5/i5wiQ=
[16:52:40] <squigley> I did not maintain the directory structure from the tar, moved the 2 files into the same directory under my tftpboot dir, could this have any effect? I don't think it should, since both files are in local mem
[16:53:14] <igork> it is example with loading files over http - faster
[16:53:34] <igork> you have to decompress files in tar archive
[16:53:51] <igork> but you have to correct provide locations of files
[16:54:30] <igork> :dilos-pxe label contain example how to provide network setup
[16:54:31] <squigley> so the directory structure from the tar file is important/rquired?
[16:54:36] <igork> yes
[16:54:43] <squigley> ah, ok
[16:55:08] <igork> and files names
[16:56:47] <igork> squigley: welcome to #dilos with questions
[16:57:10] <squigley> thanks :-)
[16:57:34] <squigley> hmm, ok, I see you have "initrd ${root-pxe}/dilos/pxe/platform/i86pc/amd64/boot_archive.pxe". the tar contains "dilos-2.0.1.63-pxe/platform/i86pc/amd64/boot_archive"
[16:57:53] <igork> update to name from tar archive
[16:57:59] <squigley> ok
[17:05:37] <squigley> also, when the kernel fails to boot, and says "press any key to reboot", the system is hard locked and I have to power cycle it. Not sure if that's a known issue..
[17:07:04] <squigley> it could be that there's an issue with the keyboard being connected though, as I am accessing the system through an ILOM remote console, as it is a Sun blade
[17:12:45] <igork> squigley: interest. i have tested pxe boot on supermicro servers by access to ipmi
[17:13:43] <igork> squigley: if you can prepare picture with loads in can be interest to look
[17:14:06] <igork> also, you can try to load smartos for testing
[17:14:36] <squigley> woo! success! "Welcome to kmdb, loaded modules, [0]>"
[17:14:47] <igork> if smartos works, i'll try to fix it
[17:15:09] <igork> well - you no need add '-kvd' to kernel line
[17:15:32] <squigley> ok, I'll see if I can setup a broken smartos and if the keyboard works to reboot there or not :-)
[17:15:55] <squigley> ah, right, I put that on in case it didn't work, and I could provide possibly useful info
[17:16:13] <squigley> also yeah, http loading was only about 100x faster than tftp
[17:16:26] <igork> squigley: it is not latest dilos - we are working on 2.0.2 update and will be released soon with many updates where tsoome fexed keyboard :)
[17:16:34] <igork> *fixed
[17:16:42] *** merzo <merzo!~merzo@195.20.130.10> has quit IRC (Ping timeout: 250 seconds)
[17:18:54] <tsoome> he did?
[17:18:56] *** amrfrsh <amrfrsh!~Thunderbi@134.19.177.23> has quit IRC (Read error: Connection reset by peer)
[17:19:02] <tsoome> :P
[17:19:05] <igork> hehe :)
[17:19:21] <igork> he did a lot of updates :)
[17:19:53] <tsoome> which one you are referring to?
[17:20:01] <igork> kbd
[17:20:24] <igork> right now your updates fixed out issue with apt ;)
[17:20:48] <tsoome> huh:D
[17:21:04] <igork> it was present a long time
[17:21:24] *** amrfrsh <amrfrsh!~Thunderbi@pptp-194-95-3-76.pptp.padnet.de> has joined #illumos
[17:39:01] *** BH23 <BH23!~BH23@81.134.255.170> has quit IRC (Ping timeout: 244 seconds)
[17:39:09] *** _joes_ <_joes_!~Thunderbi@81.134.255.170> has quit IRC (Ping timeout: 255 seconds)
[17:39:12] *** polishdub <polishdub!~polishdub@207.86.38.254> has joined #illumos
[17:45:02] *** merzo <merzo!~merzo@195.20.130.10> has joined #illumos
[18:04:18] <squigley> so I used your menu and got it all up and working, logged in and running the install now. I presume this is necessary in order to get other kernel modules to be available, such as the hxge 10gb eth driver?
[18:05:18] <igork> squigley: this driver should be on image
[18:05:20] <squigley> heh, as I sent that I just saw "prepare to unpack driver-network.." go up the screen. Probably answered my own question
[18:05:31] <igork> :)
[18:06:11] <igork> right now we are installing all drives, but in future dilos version i want install only detected list of drives
[18:06:12] <squigley> I'm hoping it is, I guess the environment that pxe boots to run the installer doesn't have everything available though?
[18:06:33] <igork> it is just installer
[18:06:54] <igork> also, you can use it for recovery if needed
[18:07:25] <igork> it is why we have login prompt and manual installer execution option
[18:07:52] <squigley> right. I've spent days trying to get linux up and running with support for the 10gbe NEM, but cannot access the driver without an Oracle support contract.. googling for the hxge driver is what found the illumos code repository :-)
[18:08:21] <igork> you need minimal install for next step where you can install what you need :)
[18:08:38] <squigley> right. install is finished and I am rebooting now
[18:09:16] <igork> if you want upgrade to testing/unstable version - let me know
[18:09:17] <squigley> "press any key to reboot" apparently doesn't include the enter key on the keypad. I got some weird control characters printed
[18:09:39] <igork> it is just installation process :)
[18:09:50] <squigley> but this may be fixed in the keyboard update you mentioned earlier
[18:09:54] <igork> we have minimal steps and honts just for loads
[18:10:16] <igork> s/honts/hints
[18:10:35] <squigley> right, makes sense, it's just that the keypad enter wasn't accepted as "any key" to cause a reboot, it just printed ctrl characters and sat there
[18:10:54] <igork> if you want - you can fix installer :) but for me - it should just setup new env
[18:11:32] <igork> if you can see last message about reboot - you can do it just restart host or vm
[18:11:46] <squigley> normal enter key worked, or I presume most other keys would work. I'm not complaining, just making observations :-)
[18:12:11] <igork> "enter" should work
[18:13:21] *** jimklimov <jimklimov!~jimklimov@31.7.243.238> has quit IRC (Ping timeout: 268 seconds)
[18:15:25] *** neuroserve <neuroserve!~toens@195.71.113.124> has quit IRC (Ping timeout: 246 seconds)
[18:16:23] <squigley> ok, so the hxge driver is there now, and I modloaded it, but dmesg doesn't report anything, and ifconfig -a doesn't show any new interfaces. Is there something else I need to do?
[18:18:27] <rmustacc> Do you see anything in dladm show-phys?
[18:19:41] <igork> dpkg -l | grep hxge
[18:19:50] <squigley> just the 2 onboard/passthrough igbX interfaces
[18:20:06] <igork> try take a look if we have installed driver
[18:20:20] <squigley> modinfo shows it loaded
[18:20:34] <igork> ok. prtconf -dD
[18:20:46] <igork> and check if it assigned to some device
[18:25:02] <squigley> I don't see it, but the NEM is also a weird interface that connects via the RAID controller..
[18:25:25] <igork> well, have to identify card address
[18:25:34] <igork> try take a look 'lspci -v'
[18:25:59] <igork> if no card, try to 'prtconf -v'
[18:26:14] <squigley> I see the raid controller.. " pci1000,9262 (pciex1000,79) [LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator]], instance #0 (driver name: mr_sas) sd, instance #0 (driver name: sd)"
[18:26:41] <igork> it is not network device
[18:27:22] <igork> we have to identify pci address
[18:27:26] <igork> for your device
[18:27:58] <squigley> "01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05)"
[18:28:11] <igork> well, it is HBA
[18:28:34] <igork> we can see only hba?
[18:28:36] *** amrfrsh <amrfrsh!~Thunderbi@pptp-194-95-3-76.pptp.padnet.de> has quit IRC (Ping timeout: 246 seconds)
[18:29:02] <squigley> right, sun does some weird thing of making the 10gbe ports appear as an enclosure connected to the raid controller
[18:29:47] <igork> well, will be interest how other os see it, like linux/bsd
[18:30:44] <squigley> under linux, using megacli, I see " Inquiry data : Vendor Identification : SUN Product Identification : NEMHydra_C10 Product Revision Level : 0403 Vendor Specific : x36-5.4.3.0 "
[18:31:19] <igork> what is driverID and vendorID?
[18:32:56] <squigley> Sun's documentation has ""/pci@7c,0/pci10de,5d@e/pci108e,aaaa@0" 0 "hxge""
[18:33:03] <squigley> https://docs.oracle.com/cd/E19677-01/820-6561-13/chapter3.html
[18:33:21] <squigley> that page may help to understand the weirdness
[18:33:22] <igork> https://paste.dilos.org/?c33953e2c541be5e#rS4CiXUyZtICsJ+2t75DFWmG7vu/YHg5OXHsSWKNPkI=
[18:33:32] <igork> it is driver info from manifest
[18:33:46] <igork> pciex108e,aaaa
[18:34:15] <igork> based on this info - driver should be attached
[18:34:23] <igork> have to investigate on your env
[18:34:33] <igork> modinfo - did you see driver?
[18:36:06] <igork> also, try to check logs - did you see messages about attach/detach?
[18:36:16] <squigley> https://paste.dilos.org/?28c7a812ca29335b#OEy+kTfBXND96KfMCYAL3Gtb/omcfjTC1prhugbg06Y=
[18:36:24] <squigley> my prtconf -v
[18:36:54] <squigley> modinfo |grep hxge 273 fffffffff7b91000 27358 60 1 hxge (HXGE 10Gb Ethernet Driver)
[18:37:55] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has quit IRC (Ping timeout: 244 seconds)
[18:38:09] <igork> pci108e,4347 (driver not attached)
[18:38:12] <squigley> I think it may be a hardware issue, rather than software.. I see the Sun docs making reference to the 10gbe if showing up in the BIOS as a boot device.. and these blades don't have that
[18:39:19] <squigley> the 4347 is one of the onboard Intel 1GB NICs
[18:39:31] *** man_u <man_u!~manu@manu2.gandi.net> has quit IRC (Quit: man_u)
[18:39:48] <igork> if you can see device on another OS - we can try identify it too. what driver on linux attached to your card ? did you try to test it on linux?
[18:40:15] <squigley> The only way I ever see it is via the RAID controller tools
[18:40:51] <igork> it is strange, but probably you can try setup it on other OS first and test
[18:40:52] <squigley> I can't test it on linux as the antique drivers for RHEL 5 or 6 are locked behind Oracle's paywall
[18:41:02] *** pcd_ is now known as pcd
[18:41:11] <igork> ah. what about debian/ubuntu?
[18:41:22] <squigley> I can't get drivers for any OS, that's why I ended up here :-)
[18:41:39] <squigley> Sun never released any .deb drivers
[18:41:43] <igork> well, we have no ideas is it is working
[18:41:58] <igork> if it's work
[18:42:08] <squigley> exactly. I have 4 of them though..
[18:42:46] <squigley> it shows up in the ILOM, and you can "manage" it, but there's pretty much nothing to configure in it
[18:43:08] <igork> can you try to use it for pxe?
[18:43:34] <squigley> no, that's where I'm seeing their screenshots showing it as a boot device, which I don't have
[18:44:01] <squigley> I'm beginning to wonder if it either doesn't work with these blades, or there's a FEM or something required for it to connect properly
[18:44:30] <squigley> I haven't worked with this hardware before, (Sun Blade 6000 chassis), so I'm, having to learn a lot of stuff the hard way
[18:44:56] <igork> well, in first , i'd like try to know - is it working device or not, can it work on other platform. based on your info - you can't check it
[18:47:17] <squigley> exactly, that's my difficulty. I'm supposed to be implementing a ceph cluster on this hardware, with 10G interconnect. Can't get any drivers for it, then found the illumos driver. Thought that perhaps if I could get that working, then I would try to get ceph working on DilOS
[18:47:46] <igork> based on your prtconf - i have no found reference to pci108,aaaa
[18:48:19] <igork> no ceph on DilOS :)
[18:48:21] <squigley> Sun's docs refer to it being there with PCI addresses too, like "/pci@7c0/pci@0/pci@8/network@0" (although this is SPARC doc)
[18:48:58] <igork> $(i386_ONLY)driver name=hxge alias=pci108e,aaaa perms="* 0600 root sys"
[18:49:03] <squigley> no ceph yet.. :-) seems like getting ceph working on DilOS is going to be easier than getting these bloody 10GbE cards working :-)
[18:50:07] <squigley> yeah, I really think these NEMs either don't work with these blades, or they need a FEM to connect them
[18:50:12] <igork> well, i have no ideas right now. maybe someone else have ideas. problem is: we don't know is it working device or noe
[18:50:16] <igork> *not
[18:51:33] <igork> and based on prtconf - no address found like: pci108e,aaaa
[18:51:42] <igork> you can have another device
[18:55:15] <rmustacc> squigley: At least from the OS perspective, we're not seeing a PCI device that refers to it or anything there. I suspect that there's some means that you'll have to poke firmware to make it appear.
[18:55:37] <squigley> yeah, I think it really needs to show up on the PCI bus. The docs say "Verify that the NEM is available to the system (that is, it is actively on the PCIe I/O bus)." "lspci" "85:00.0 Ethernet controller: Sun Microsystems Computer Corp. Unknown device aaaa (rev 01)" "Device code 0xAAAA (Unknown device aaaa (rev 01) output) is the Virtualized NEM Device; presence of this line indicates the NEM is visible and available to the system."
[18:56:21] <squigley> then they modprobe the driver, so it can't have done anything to make it appear
[18:56:46] <rmustacc> Right, the driver itself just looks for PCI devices to attach to. That's why it is loaded, but there are no instances of it.
[19:08:36] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has joined #illumos
[19:08:51] *** merzo <merzo!~merzo@195.20.130.10> has quit IRC (Ping timeout: 246 seconds)
[19:15:32] <squigley> OK, it looks like I need a different RAID controller, and or a "Pass-Thru PCIe 2.0 Fabric Expansion Module "
[19:16:55] <rmustacc> A different raid controller for driver reasons?
[19:17:27] <squigley> and finally, I find "For server modules to access the 10 GbE functionality of the Virtualized Multi-Fabric 10GbE NEM, they must have a fabric express module (FEM) installed in the server module. "
[19:18:09] <squigley> https://docs.oracle.com/cd/E19530-01/html/821-0874/gkako.html#NH2PNgkako
[19:19:07] <squigley> it's ambiguous. "The following table lists the supported server modules and associated FEMs and REMs that are supported for use with the Virtualized NEM M2", but it doesn't specify if that is an and or an or
[19:21:07] <squigley> but I guess when it says "they must have a fabric express module (FEM) installed", then it means I need the FEMs, which I don't have
[19:22:21] <squigley> but thanks very much will all your assistance in getting DilOS up and running :-) I have a bunch more of these chassis and blades, and I may run it on some of them :-)
[19:22:51] <igork> you are welcome
[19:23:47] <tsoome> does anyone want to look on https://www.illumos.org/rb/r/1664/ while I do RTI build?:P
[19:41:10] *** alanc <alanc!~alanc@129.157.69.37> has quit IRC (Remote host closed the connection)
[19:41:37] *** alanc <alanc!~alanc@129.157.69.37> has joined #illumos
[19:41:55] *** PMT <PMT!~PMT@pool-100-33-69-155.nycmny.fios.verizon.net> has quit IRC (Ping timeout: 250 seconds)
[19:42:19] *** ptribble <ptribble!~ptribble@cpc92716-cmbg20-2-0-cust138.5-4.cable.virginm.net> has joined #illumos
[20:06:37] *** merzo <merzo!~merzo@30-50-133-95.pool.ukrtel.net> has joined #illumos
[20:20:36] *** jubal <jubal!~jubal@178-0-237-24.gci.net> has quit IRC (Ping timeout: 246 seconds)
[20:23:15] *** jubal <jubal!~jubal@226-5-237-24.gci.net> has joined #illumos
[20:37:52] *** amrfrsh <amrfrsh!~Thunderbi@pptp-194-95-3-76.pptp.padnet.de> has joined #illumos
[20:41:47] *** amrmesh <amrmesh!~Thunderbi@134.19.177.23> has joined #illumos
[20:43:24] *** amrfrsh <amrfrsh!~Thunderbi@pptp-194-95-3-76.pptp.padnet.de> has quit IRC (Ping timeout: 250 seconds)
[20:43:25] *** amrmesh is now known as amrfrsh
[20:49:25] <squigley> I just did an upgrade, and got an error with the bootadm; "bootadm: unknown format specified: -F -R", "Error: /tmp/1492/sbin/bootadm update-archive -F -R /tmp/1492"
[20:50:55] <igork> squigley: what do you try to do?
[20:51:49] <squigley> I did a dist-upgrade, which updated dilos-upgrade
[20:51:56] <igork> if you want upgrade dilos, you need:
[20:51:56] <igork> update /etc/apt/sources.list - change 'dilos2' to 'dilos2-unstable'
[20:51:56] <igork> apt update
[20:51:56] <igork> apt install os-upgrade
[20:51:56] <igork> os-upgrade
[20:52:25] <igork> it will upgrade to to newBE for next boot
[20:52:30] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has joined #illumos
[20:52:54] <squigley> ah ok, I guess I'm just used to doing distupgrades on ubuntu/debian to update everything
[20:53:26] <igork> we are using ZFS
[20:53:52] <igork> and use 'beadm' for manage boot checkpoint
[20:54:34] <squigley> as opposed to bootadm? so that error is expected?
[20:54:54] <igork> beadm is using bootadm for update bootarchive
[20:55:10] <igork> in 'beadm activate newBE'
[20:57:01] <squigley> here's what I did, if it helps: https://paste.dilos.org/?c6b8ff5034bb7d38#HopV35DnUzP+WPL9E23fLi1cAjeWwl0oYTqdhCYIbJQ=
[20:57:55] <igork> squigley: you missed one step:
[20:57:55] <igork> update /etc/apt/sources.list - change 'dilos2' to 'dilos2-unstable'
[21:01:12] <igork> dilos-upgrade script was updated to os-upgrade, but not removed from repo. os-upgrade contain new upgrade procedure
[21:03:11] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has quit IRC (Remote host closed the connection)
[21:03:15] <sjorge> tsoome are those 2 for the fsater resilver thingy?
[21:04:01] <tsoome> um, which ones?:)
[21:04:02] <squigley> ok. perhaps there should be some sort of sanity check that the sources.list has been changed when attempting to do an upgrade.. aha, there's a new procedure, nvm then :-)
[21:04:10] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has joined #illumos
[21:06:12] <igork> squigley: have to block dist-upgrade and show message about os-upgrade, but i always forgot to do it
[21:07:19] <igork> i forgot about linux users who know how to use 'apt dist-upgrade' instead of just os-upgrade on dilos
[21:08:36] <squigley> fair enough. just patch apt to catch dist-upgrade and tell us to use os-upgrade instead
[21:08:48] <sjorge> tsoome
[21:08:48] <sjorge> does anyone else want to look on https://www.illumos.org/rb/r/1226/ and https://www.illumos.org/rb/r/1572/ (they will be pushed together)?
[21:09:05] <tsoome> yes it is.
[21:13:02] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has quit IRC (Remote host closed the connection)
[21:19:20] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has joined #illumos
[21:22:53] *** freakazoid0223 <freakazoid0223!~matt@pool-108-52-159-210.phlapa.fios.verizon.net> has quit IRC (Remote host closed the connection)
[21:23:33] *** freakazoid0223 <freakazoid0223!~matt@pool-108-52-159-210.phlapa.fios.verizon.net> has joined #illumos
[21:52:53] *** rsully <rsully!~rsully@unaffiliated/rsully> has joined #illumos
[22:10:45] *** PMT <PMT!~PMT@pool-100-33-69-155.nycmny.fios.verizon.net> has joined #illumos
[22:20:01] *** ed209 <ed209!~ed209@165.225.128.67> has quit IRC (Remote host closed the connection)
[22:20:08] *** ed209 <ed209!~ed209@165.225.128.67> has joined #illumos
[22:22:25] <tsoome> does mdb have any tools to help to find and analyze deadlocks?
[22:30:44] <igork> tsoome: i think only try dump threads time to time and analyze it
[22:31:02] <igork> or inject code helpers
[22:33:54] *** merzo <merzo!~merzo@30-50-133-95.pool.ukrtel.net> has quit IRC (Ping timeout: 250 seconds)
[22:36:07] <rmustacc> tsoome: I don't think there's a built-in deadlock finder, but there are dcmds that can easily inspect the locks and other things.
[22:36:15] <rmustacc> I'm happy to walk you through how to use them if you're not familiar with them.
[22:37:49] *** merzo <merzo!~merzo@30-50-133-95.pool.ukrtel.net> has joined #illumos
[22:37:55] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has quit IRC (Ping timeout: 246 seconds)
[22:38:03] <tsoome> like ::findlocks ?
[22:40:51] *** ptribble <ptribble!~ptribble@cpc92716-cmbg20-2-0-cust138.5-4.cable.virginm.net> has quit IRC (Quit: Leaving)
[22:44:33] <rmustacc> tsoome: No, there's nothing like a ::findlocks.
[22:44:59] <tsoome> yea, I found it out hard way:D
[22:45:01] <rmustacc> However, there are dcmds like ::mutex and ::rwlock which will tell you who's holding the lock you're trying to get.
[22:47:02] <richlowe> there literally is a findlocks?
[22:49:39] <richlowe> the wchan column in ::threadlist and a bit of awk is handy, too
[22:50:06] <richlowe> and wchaninfo -v
[22:50:38] <tsoome> ou thats neat
[22:50:50] <rmustacc> Huh, so there is as part of typegraph.
[22:50:53] <richlowe> ::thread -b
[22:50:54] <richlowe> too
[22:51:11] <richlowe> none of them are exactly a complete solution, but they give you at least moderate stone tools
[22:52:02] <tsoome> ya, well I roughly have idea what to look for, just need to get a bit more background information
[22:52:10] <rmustacc> OK, if you need a hand, let me know.
[22:52:54] *** aszeszo <aszeszo!~aszeszo@unaffiliated/aszeszo> has joined #illumos
[22:53:32] <tsoome> anything like mutex for kcondvar_t?
[22:54:13] *** aszeszo_ <aszeszo_!~aszeszo@unaffiliated/aszeszo> has quit IRC (Ping timeout: 245 seconds)
[22:57:26] <richlowe> wchaninfo I think
[23:00:39] *** aszeszo_ <aszeszo_!~aszeszo@unaffiliated/aszeszo> has joined #illumos
[23:00:53] <tsoome> yep, got it, thanks:D
[23:02:11] *** rsully <rsully!~rsully@unaffiliated/rsully> has quit IRC (Quit: rsully)
[23:03:48] *** aszeszo <aszeszo!~aszeszo@unaffiliated/aszeszo> has quit IRC (Ping timeout: 268 seconds)
[23:05:04] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has joined #illumos
[23:05:15] <richlowe> tsoome: if it's repeatable, debug builds (and maybe a tunable?) will get you the cycle in blocking chain panic for simple errors, too.
[23:05:44] <tsoome> I’ll see soon if it is:D
[23:09:25] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has quit IRC (Ping timeout: 246 seconds)
[23:21:40] *** clapont <clapont!~clapont@unaffiliated/clapont> has quit IRC (Ping timeout: 246 seconds)
[23:23:49] *** clapont <clapont!~clapont@unaffiliated/clapont> has joined #illumos
[23:49:27] <tsoome> or not that soon. so far no lockup
[23:51:32] <tsoome> i still do not like zfstest is pulling in pools from “other” disks.
[23:52:10] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has quit IRC (Quit: WeeChat 2.1)
[23:53:34] *** Kurlon <Kurlon!~Kurlon@98.13.72.207> has joined #illumos
[23:56:11] *** freakazoid0223 <freakazoid0223!~matt@pool-108-52-159-210.phlapa.fios.verizon.net> has quit IRC (Ping timeout: 244 seconds)
[23:56:53] *** polishdub <polishdub!~polishdub@207.86.38.254> has quit IRC (Remote host closed the connection)
top

   April 18, 2019  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | >