It occurs to me that this is likely related to the new interrupt code. that tends to imply that the fix is "wait a few days and re-cvsup", but I thought folks here would be interested in seeing Sparc64 feedback. -T -- [It] contains "vegetable stabilizer" which sounds ominous. How unstable are vegetables? - A.S.R. quote (Jeff Zahn)
attached mail follows:
The serial console shows this: atapci0: <CMD 646 WDMA2 controller> port 0xc00020-0xc0002f,0xc00018-0xc0001b,0xc00010-0xc00017,0xc00008-0xc0000b,0xc00000-0xc00007 at device 3.0 on pci1 atapci0: [MPSAFE] ata2: at 0xc00000 on atapci0 ata2: [MPSAFE] ata3: at 0xc00010 on atapci0 ata3: [MPSAFE] pcib2: <APB PCI-PCI bridge> at device 1.0 on pci0 pci2: <OFW PCI bus> on pcib2 pcib3: <OFW PCI-PCI bridge> at device 3.0 on pci2 pci3: <OFW PCI bus> on pcib3 pci3: <bridge, PCI-unknown> at device 0.0 (no driver attached) hme1: <Sun HME 10/100 Ethernet> mem 0x2800000-0x2807fff at device 0.1 on pci3 pcib3: slot 0 INTB is routed to irq 25 hme1: Ethernet address: 08:00:20:c6:7f:c7 miibus1: <MII bus> on hme1 ukphy0: <Generic IEEE 802.3u media interface> on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci3: <bridge, PCI-unknown> at device 1.0 (no driver attached) hme2: <Sun HME 10/100 Ethernet> mem 0x4800000-0x4807fff at device 1.1 on pci3 pcib3: slot 1 INTB is routed to irq 26 hme2: Ethernet address: 08:00:20:c6:7f:c7 miibus2: <MII bus> on hme2 ukphy1: <Generic IEEE 802.3u media interface> on miibus2 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci3: <bridge, PCI-unknown> at device 2.0 (no driver attached) hme3: <Sun HME 10/100 Ethernet> mem 0x6800000-0x6807fff at device 2.1 on pci3 pcib3: slot 2 INTB is routed to irq 27 hme3: Ethernet address: 08:00:20:c6:7f:c7 miibus3: <MII bus> on hme3 ukphy2: <Generic IEEE 802.3u media interface> on miibus3 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci3: <bridge, PCI-unknown> at device 3.0 (no driver attached) hme4: <Sun HME 10/100 Ethernet> mem 0x8800000-0x8807fff at device 3.1 on pci3 pcib3: slot 3 INTB is routed to irq 24 hme4: Ethernet address: 08:00:20:c6:7f:c7 miibus4: <MII bus> on hme4 ukphy3: <Generic IEEE 802.3u media interface> on miibus4 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Timecounters tick every 0.976 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled ad0: WARNING - SETFEATURES recovered from missing interrupt ad0: WARNING - SETFEATURES recovered from missing interrupt ad0: WARNING - SET_MULTI recovered from missing interrupt ad0: WARNING - SETFEATURES recovered from missing interrupt GEOM: create disk ad0 dp=0xfffff8001087a6c0 ad0: 8223MB <ST38410A> [16708/16/63] at ata2-master WDMA2 acd0: WARNING - MODE_SENSE_BIG recovered from missing interrupt ata3: resetting devices .. It's an Ultra 5 with an IDE drive. I was previously running -current from after the 09/23 entry in UPDATING. Entries since then don't show anything particularly relevent. I ran cvsup before beginning the compile about 8:00am CST. Are there any known issues like this? Are there known solutions? Even a "wait until foo is committed then re-cvsp" would be great to hear ;-) I've tried "load /boot/kernel.old/kernel" from the boot loader to recover at least a booting system. This worked, though naturally my userland no longer matches my kernel. Should I be able to re-install a new kernel & userland from this point safely? -T -- "I'm getting a new desk soon! Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Lunch. Productivity is in the eyes of the beholder." - A.S.R. quote (Lars Balker Rasmussen) _______________________________________________ freebsd-sparc64_at_freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe_at_freebsd.org"Received on Tue Nov 04 2003 - 08:33:04 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:27 UTC