[04:03] <fabbione> hey tmarble 
[04:03] <tmarble> fabbione: ciao
[04:04] <tmarble> so are you, or David, lacking hardware to find this bug?
[04:04] <tmarble> not that I can do anything about it... but I thought i'd ask
[04:06] <fabbione> what bug?
[04:07] <fabbione> it's not like we have just one :)
[04:07] <fabbione> let me rephrase that
[04:07] <fabbione> we have no bugs.. 
[04:07] <fabbione> the hw just doesn't work
[04:07] <fabbione> :P
[04:12] <tmarble> ah. so you're saying it's my problem ;-)
[04:13] <fabbione> eheh
[04:13] <fabbione> no seriously.. i have been hacking like mad today
[04:13] <fabbione> what bug are you talking about?
[04:14] <tmarble> BUG: soft lockup detected on CPU#2!
[04:15] <fabbione> i already fixed that
[04:15] <fabbione> it's pushed in git but it will take a few days to be uploaded
[04:15] <fabbione> and i found another bug in the reboot code for the kernel that get trapped by the HV and generate a poweroff error
[04:16] <tmarble> hmmm yes.. having both those fixes will be nice
[04:18] <fabbione> i thought that the latter was caused by the former, but i have been proven wrong
[04:44] <tmarble> for the purpose of debugging, would it make sense to package up linux-image-2.6.17-10-sparc64-smp with these fixes such that I can try them?
[04:44] <tmarble> i.e. before it becomes a 2.6.17.n release?
[04:51] <fabbione> i already tested it, but i can upload an image if you want
[04:52] <tmarble> as I only have this box for little over a week I'd like to get going with it -- if it's not too much trouble
[04:53] <tmarble> there also would be enormous value in confirming the effectiveness of the fix
[04:53] <tmarble> if, for some reason, the fix(es) are not sufficient I assume it is better to know that early, right?
[04:54] <tmarble> So, for example, I don't know if it's possible for me to take the recent boot.img from yesterday at http://archive.ubuntu.com/ubuntu/dists/edgy/main/installer-sparc/current/images/sparc64/netboot/2.6/
[04:54] <tmarble> and then point at a non-production mirror (if you prefer) 
[04:55] <tmarble> then we wouldn't have to wait the 6 hours for ubuntu dinstall, right?
[04:55] <fabbione> halt..
[04:55] <fabbione> you are confusing 2 things here
[04:55] <fabbione> one is the d-i error you saw
[04:56] <fabbione> that has been addressed yesterday
[04:56] <tmarble> k
[04:56] <fabbione> the new image will work just fine
[04:56] <fabbione> but there might be instability in the mirrors soon
[04:56] <fabbione> new image will be default in a couple of hours
[04:56] <tmarble> will it, indeed, be  linux-image-2.6.17-10-sparc64-smp ?
[04:57] <fabbione> yes, but that image doesn't contain the fix for the CPU lockups yet
[04:57] <fabbione> so what i suggest to do is:
[04:57] <tmarble> right -- I confirm the d-i bug is fixed -- install completed nicely
[04:57] <fabbione> wait tomorrow or thursday for the new image
[04:57] <fabbione> install
[04:58] <fabbione> you will see also a login prompt on the console (that was broken when you did the first install)
[04:58] <fabbione> and then we can install the new kernel with the fix
[04:58] <fabbione> if the fix will not hit archive before that
[04:58] <tmarble> ah, so you are saying that  linux-image-2.6.17-11-sparc64-smp *will* include the CPU lockup fix?
[04:58] <fabbione> it can also be -10- with a version bump
[04:59] <tmarble> ah - ok
[04:59] <fabbione> -10- or -9- indicates the ABI version of the kernel
[04:59] <tmarble> right, my bad
[04:59] <fabbione> nah that's ok
[04:59] <fabbione> a lot of people don't grok that easily
[04:59] <tmarble> I actually do understand upstream vs. debian versions -- just not facile with these package names yet
[05:00] <fabbione> yeah
[05:00] <fabbione> kernel is special in this regard
[05:00] <tmarble> but, your point is, by tomorrow or thursday we will have a kernel with the CPU lockup fix, right?
[05:03] <fabbione> no, my point is that by tomorrow or thursday you will get an image that will install and take you to a console
[05:03] <fabbione> the reason why you didn't get a console was because of a bug in the installer that was fixed today
[05:03] <tmarble> ok
[05:04] <fabbione> the kernel with the CPU lock fixed is on my niagara and i can give you a copy
[05:04] <tmarble> but am I  still going to trip over CPU lockup?
[05:04] <fabbione> yes right
[05:04] <fabbione> that's not a big deal
[05:04] <tmarble> ah - -then I install manually from the console?
[05:04] <fabbione> exactly
[05:04] <fabbione> i can also explain to you how to fix your actual install
[05:04] <tmarble> are you going to give me a .deb
[05:04] <fabbione> and get a console
[05:04] <fabbione> yes i will give you a deb
[05:04] <tmarble> easy enough
[05:04] <fabbione> if you are bored.. netboot the machine with the installer
[05:05] <fabbione> get to the partitioner and <go back>
[05:05] <fabbione> get to the main menu
[05:05] <tmarble> choose ash
[05:05] <tmarble> ?
[05:05] <fabbione> "exit to a shell" or something similar
[05:05] <fabbione> mount your root somewhere
[05:05] <tmarble> it's already on /target isn't it?
[05:05] <fabbione> it's on target if you install
[05:06] <fabbione> but since you already installed, might as well fix the install
[05:06] <tmarble> ah -- ok
[05:06] <fabbione> so if you get to the partitioner, before reformatting anything
[05:06] <fabbione> get to the shell as i told you
[05:06] <fabbione> mount / somewhere
[05:06] <fabbione> in /etc/events.d
[05:06] <fabbione> add a file called ttyS0
[05:06] <fabbione> and slam this in it:
[05:07] <fabbione> start on runlevel-2
[05:07] <fabbione> start on runlevel-3
[05:07] <fabbione> start on runlevel-4
[05:07] <fabbione> start on runlevel-5
[05:07] <fabbione> stop on shutdown
[05:07] <fabbione> respawn /sbin/getty -L ttyS0 9600 vt102
[05:07] <fabbione> (actually it's /etc/event.d)
[05:07] <fabbione> reboot from there
[05:07] <tmarble> I assume this is under my mount -- not the installer real / , correct?
[05:07] <fabbione> yes right
[05:07] <fabbione> under the mount
[05:07] <tmarble> k
[05:07] <fabbione> that will give you console access
[05:07] <tmarble> ah.. good
[05:07] <fabbione> now i need to finish a couple of silo fixes
[05:07] <tmarble> then I can install your deb from that
[05:07] <tmarble> ok
[05:08] <tmarble> one more, different question please
[05:08] <fabbione> and i will upload the image on people.ubuntu.com/~fabbione/tmarble
[05:08] <tmarble> k
[05:08] <tmarble> my colleage wants to boot (from OBP) to a given partition (in his case, parition 4)
[05:08] <tmarble> I asked him to try this:
[05:09] <tmarble> ok boot /pci@780/pci@0/pci@9/scsi@0/disk@0,0:d
[05:09] <tmarble> BUT, it said "file is not executable" 
[05:09] <tmarble> is there some other way to do this?
[05:09] <fabbione> did he install silo in the partition? or in the MBR?
[05:10] <tmarble> i'll ask, hold please
[05:11] <fabbione> the installer by default uses the MBR iirc
[05:11] <tmarble> ok... 
[05:11] <fabbione> to install on the partition you need to do it manually
[05:11] <fabbione> IIRC with silo -f -t
[05:11] <fabbione> but he needs to check on the manpage
[05:11] <fabbione> i really don't remember
[05:11] <tmarble> I have to read more on silo, but is there any reason I can't add an entry in silo to jump to a partition (that happens to be running Solaris)?
[05:11] <tmarble> k
[05:11] <fabbione> yes you can add an entry to silo
[05:12] <tmarble> any thoughts about supporting grub?
[05:12] <fabbione> there are some people working on grub2
[05:12] <tmarble> supposedly grub understands Sun VTOC
[05:12] <fabbione> but i have no idea about the status
[05:12] <tmarble> k
[05:13] <tmarble> nikolay is not responding... please go ahead to work on your silo fixes...
[05:13] <tmarble> thanks for your help!  let me know when you have a deb for me
[05:14] <fabbione> it won't take long for the deb
[05:14] <fabbione> i need to build the kernrel but it takes only a few minutes on Niagara :)
[05:14] <tmarble> ok... i'll try to get the console thing fixed now
[05:15] <fabbione> btw.. tell Nikolay that i didn't forget about his gcc/linking issue
[05:15] <fabbione> i just had no time to work on it
[05:15] <fabbione> silo booting is beta blocker
[05:15] <tmarble> yeah -- I have promised to file a bug on that (and he has another kernel NFS bug I need to file too)
[05:46] <fabbione> /usr/bin/make -j512 EXTRAVERSION=-10-sparc64-smp  ARCH=sparc64 \
[05:46] <fabbione>                              image
[05:46] <fabbione> almost there :)
[05:46] <fabbione> that -j512 makes things go *slightly* faster :)
[06:01] <tmarble> I had trouble on install components -- skipping to detect disks
[06:03] <fabbione> they are changing the kernel bits in the archive as we speak
[06:03] <tmarble> i figured that... jumped to ash too early .. /dev/sdb was not known
[06:03] <fabbione> eheh
[06:04] <tmarble> mounted
[06:05] <fabbione> nice
[06:05] <fabbione> kernel is almost ready
[06:05] <fabbione> testing one more fix
[06:05] <tmarble> don't have /etc/event.d
[06:05] <tmarble> shall i mkdir
[06:07] <fabbione> it has to be there
[06:07] <fabbione> are you chrooted in /target or using real /etc ?
[06:07] <tmarble> does this look right (sorry for the flood):
[06:07] <tmarble> /mnt/event.d # pwd                                                             
[06:07] <tmarble> /mnt/etc/event.d
[06:07] <tmarble> /mnt/event.d # cat ttyS0
[06:07] <tmarble> start on runlevel-2
[06:07] <tmarble> start on runlevel-3
[06:08] <tmarble> start on runlevel-4
[06:08] <tmarble> start on runlevel-5
[06:08] <tmarble> stop on shutdown
[06:08] <tmarble> respawn /sbin/getty -L ttyS0 9600 vt102
[06:08] <tmarble> /mnt/event.d # 
[06:08] <tmarble> /mnt/event.d # mount
[06:08] <tmarble> none on /proc type proc (rw)
[06:08] <tmarble> tmpfs on /dev type tmpfs (rw)
[06:08] <tmarble> sysfs on /sys type sysfs (rw)
[06:08] <tmarble> tmpfs on /.dev type tmpfs (rw)
[06:08] <tmarble> /dev/sdb on /mnt type ext3 (rw,data=ordered)
[06:08] <fabbione>  /mnt/event.d ??
[06:08] <tmarble> /mnt/event.d # 
[06:08] <fabbione>  /etc/event.d ?
[06:08] <tmarble> that's ash that is confused -- hence the pwd
[06:08] <fabbione>  /mnt/etc/event.d
[06:09] <fabbione> that directory has to be there
[06:09] <fabbione> what's in there?
[06:09] <fabbione> is it empty?
[06:09] <tmarble> no, I just added ttyS0
[06:09] <tmarble> /mnt/event.d # ls -al
[06:09] <tmarble> drwxr-xr-x    2 root     root         1024 Sep 26 16:04 .
[06:09] <tmarble> drwxr-xr-x    4 root     root         1024 Sep 26 16:04 ..
[06:09] <tmarble> -rw-r--r--    1 root     root          138 Sep 26 16:06 ttyS0
[06:09] <tmarble> /mnt/event.d # cat ttyS0
[06:09] <tmarble> start on runlevel-2
[06:09] <tmarble> start on runlevel-3
[06:09] <fabbione> no
[06:09] <tmarble> start on runlevel-4
[06:09] <tmarble> start on runlevel-5
[06:09] <tmarble> stop on shutdown
[06:09] <fabbione> there is something wrong here
[06:09] <tmarble> respawn /sbin/getty -L ttyS0 9600 vt102
[06:09] <tmarble> /mnt/event.d # 
[06:09] <fabbione> that dir is full of stuff
[06:10] <fabbione> ls
[06:10] <fabbione> control-alt-delete  rc0       rc0-poweroff  rc2  rc4  rc6         rcS          sulogin  tty2  tty4  tty6
[06:10] <fabbione> logd                rc0-halt  rc1           rc3  rc5  rc-default  rcS-sulogin  tty1     tty3  tty5  ttyS0
[06:10] <fabbione> do you have /mnt/etc/inittab ?
[06:10] <tmarble> /mnt/event.d # ls -l /mnt/etc/inittab
[06:10] <tmarble> ls: /mnt/etc/inittab: No such file or directory
[06:12] <tmarble> something is weird
[06:12] <fabbione> no
[06:12] <fabbione> it's all wrong
[06:12] <fabbione> do you have /etc ?
[06:12] <fabbione> or did you mount /boot by mistake?
[06:13] <tmarble> perhaps.. let me try again
[06:17] <tmarble> my bad
[06:17] <tmarble> /tmp/5/etc/event.d # mount | grep /dev/sdb5
[06:17] <tmarble> /dev/sdb5 on /tmp/5 type ext3 (rw,data=ordered)
[06:17] <tmarble> /tmp/5/etc/event.d # ls
[06:17] <tmarble> control-alt-delete  rc2                 sulogin
[06:17] <tmarble> logd                rc3                 tty1
[06:17] <tmarble> rc-default          rc4                 tty2
[06:17] <tmarble> rc0                 rc5                 tty3
[06:17] <tmarble> rc0-halt            rc6                 tty4
[06:17] <tmarble> rc0-poweroff        rcS                 tty5
[06:17] <tmarble> rc1                 rcS-sulogin         tty6
[06:17] <tmarble> /tmp/5/etc/event.d # 
[06:18] <tmarble> /tmp/5/etc/event.d # cat ttyS0                                                 
[06:18] <tmarble> start on runlevel-2
[06:18] <tmarble> start on runlevel-3
[06:18] <tmarble> start on runlevel-4
[06:18] <tmarble> start on runlevel-5
[06:18] <tmarble> stop on shutdown
[06:18] <tmarble> respawn /sbin/getty -L ttyS0 9600 vt102
[06:18] <tmarble> /tmp/5/etc/event.d # 
[06:18] <tmarble> Correct?
[06:20] <fabbione> looks much better now :)
[06:20] <tmarble> ok
[06:20] <tmarble> now umount and reboot?
[06:20] <fabbione> yeps
[06:20] <tmarble> k
[06:21] <fabbione> i am booting the test kernel for you
[06:37] <fabbione> tmarble: you eat too fast
[06:38] <tmarble> no.. i just got the food -- will eat during the ConCall :-(
[06:38] <fabbione> oh
[06:38] <fabbione> i am reliefed i am not the only one :)
[06:40] <tmarble> i'm booting into solaris on sysdisk0 on reboots ....
[06:40] <tmarble> i thought I could set this in OBP:
[06:40] <tmarble> setenv auto-boot false
[06:40] <tmarble> but it doesn't like that/
[06:43] <tmarble> {7} ok setenv auto-boot? false
[06:43] <tmarble> auto-boot? =            false
[06:45] <tmarble> there is already one there now?
[06:45] <fabbione> i didn't notice
[06:45] <fabbione> yeah but i am testing one with an extra fix
[06:45] <tmarble> ah
[06:45] <fabbione> that one is useable
[06:47] <tmarble> OK ...last time it stopped here, I pressed <return> and it continued...... is it normal to stop here?
[06:47] <tmarble> Rebooting with command: boot disk1
[06:47] <tmarble> Boot device: /pci@780/pci@0/pci@9/scsi@0/disk@1  File and args: 
[06:47] <tmarble> SILO Version 1.4.12
[06:47] <tmarble> boot: boot: 
[06:48] <fabbione> it's normal.. but there is a timeout
[06:48] <tmarble> just press return now, then?
[06:48] <fabbione> it gives you time to chose the kernel or otherwise it will go by itself
[06:48] <fabbione> yeah
[06:50] <tmarble> Ubuntu edgy (development branch) blade220 ttyS0     
[06:51] <tmarble> Linux blade220 2.6.17-9-sparc64-smp #2 SMP Fri Sep 22 04:57:24 UTC 2006 sparc64 
[06:51] <tmarble> root@blade220:~# 
[06:51] <tmarble> I'm ready
[06:51] <fabbione> yeah i am doing the last boot.. only a few minutes (hopefully)
[06:52] <fabbione> but you can start using that one to avoid CPU lockups
[06:52] <tmarble> no worries -- now I can at least repair this system
[06:52] <tmarble> i'll wait
[07:01] <fabbione> uploading the new version now
[07:01] <tmarble> cool
[07:10] <fabbione> tmarble: can you please get somebody to look at https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/62485 ?
[07:10] <fabbione> it would be enough to know what the hell that message from the HV means
[07:10] <tmarble> hold on
[07:11] <fabbione> note that it doesn't happen with the old dapper kernel
[07:11] <fabbione> only on edgy
[07:11] <fabbione> and the kernel is on people
[07:26] <tmarble> So, I added the deb....
[07:26] <tmarble> it looks like silo is set for 
[07:26] <tmarble> image=/vmlinuz
[07:27] <tmarble> and the link was updated
[07:27] <tmarble>  vmlinuz -> boot/vmlinuz-2.6.17-10-sparc64-smp
[07:27] <tmarble> so, just reboot, right?
[07:28] <fabbione> yes but make sure you have vmlinux.old pointing to the old kernel
[07:28] <fabbione> just in case
[07:29] <fabbione> after that.. reboot
[07:29] <tmarble> it does
[07:29] <tmarble> so , in case of trouble do.... boot: vmlinux.old
[07:29] <fabbione> LinuxOLD
[07:29] <fabbione> there is an alias set in silo.conf
[07:29] <tmarble> right.. just saw that in silo.conf
[07:29] <fabbione> at silo: you can tab
[07:29] <fabbione> and see what images are available
[07:30] <tmarble> ok
[07:31] <fabbione> last reboot and i am off for today
[07:31] <tmarble> ok
[07:31] <fabbione> 15 hours in the day.. i am dead tired
[07:31] <tmarble> i can't understand???
[07:32] <fabbione> 15 hours of work today.. i am dead tired
[07:32] <tmarble> thanks so much -- I'm rebooting now
[07:32] <fabbione> no problem at all
[07:32] <fabbione> you might get that HV error
[07:32] <fabbione> as i did show you in the bug
[07:32] <fabbione> the machine might poweroff
[07:32] <fabbione> i should also get some new OBP for my T2000
[07:33] <fabbione> but that can wait tomorrow
[07:33] <tmarble> yes you should
[07:33] <fabbione> tmarble: can you send me a link with the latest crack?
[07:33] <tmarble> what should i do about the HV bug?
[07:33] <tmarble> sure
[07:33] <fabbione> i need to know what that error means
[07:33] <tmarble> it was in an e-mail i sent you
[07:33] <tmarble> ok
[07:34] <fabbione> checking in the emails
[07:34] <fabbione> ah no
[07:34] <fabbione> you gave it to me here on IRC
[07:34] <fabbione> and i did install that update
[07:34] <fabbione> i need to check fi there are new ones
[07:35] <tmarble> 123482-02
[07:36] <fabbione> hmm
[07:36] <fabbione> noi can't find it
[07:36] <fabbione> in my url list i mean
[07:37] <tmarble> ok hold on
[07:37] <fabbione> i have it now
[07:38] <fabbione> it's years i don't do sysadm on solaris, but i still remember how to search on sun.com :)
[07:38] <fabbione> http://sunsolve.sun.com/search/document.do?assetkey=1-21-123482-02-1
[07:38] <tmarble> right
[07:38] <fabbione> Wed Sep 13 12:26:54 MDT 2006
[07:40] <fabbione> 6437802 JBI Fatal HV error should not happen when I/O protection is on
[07:40] <fabbione> that smells like it
[07:41] <tmarble> had to powercycle my box... still waiting 
[07:41] <fabbione> yeah i told you
[07:41] <fabbione> it's annoying
[07:41] <fabbione> anyway i am off
[07:41] <fabbione> the kernel will boot fine
[07:41] <fabbione> thanks for the help
[07:41] <tmarble> I did init 0 from the older kernel
[07:41] <tmarble> no worries... take care... have a good rest
[07:41] <fabbione> cya tomorrow
[07:41] <tmarble> k