Re: cannot boot 2.6.18-1 on sunblade 100
On Sun, Oct 08, 2006 at 12:56:47PM +1000, Jim Watson wrote: > Hi, > > I just installed linux-image-2.6.18-1-sparc64 which I think is the > latest available on debian/unstable. > > But booting linux-image-2.6.18-1-sparc64 on sunblade100 fails: > > Booting Linux... > NVRAM: Low Battery Voltage! > CLOCK: Clock was stopped. Kick start Hi, Can you please send the output of the 'prtconf -p -v' command to the bug 392078? Thanks, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apache 2.2 broken on sparc-unstable?
Since a few days (probably the last apt-get update), I get this
in my error_log:
[Thu Oct 12 22:51:29 2006] [notice] child pid 20359 exit signal
Segmentation fault (11)
[Thu Oct 12 22:51:29 2006] [notice] child pid 20358 exit signal
Segmentation fault (11)
[Thu Oct 12 22:51:29 2006] [notice] child pid 20357 exit signal
Segmentation fault (11)
I tried removing (--purge) all apache and php-related modules,
but even with the default config the result is the same:
u1:~# dpkg -l|grep apache
ii apache2 2.2.3-2Next generation, scalable, extendable web se
ii apache2-mpm-prefork 2.2.3-2
ii apache2-utils 2.2.3-2
ii apache2.2-common2.2.3-2
any idea? :)
regards,
Olivier
PS: strace:
u1:~# strace /usr/sbin/apache2 -k start -X
[...]
open("/etc/group", O_RDONLY)= 8
fcntl64(8, F_GETFD) = 0
fcntl64(8, F_SETFD, FD_CLOEXEC) = 0
_llseek(8, 0, [0], SEEK_CUR)= 0
fstat64(8, {st_mode=S_IFREG|0644, st_size=689, ...}) = 0
mmap2(NULL, 689, PROT_READ, MAP_SHARED, 8, 0) = 0x7001c000
_llseek(8, 689, [689], SEEK_SET)= 0
fstat64(8, {st_mode=S_IFREG|0644, st_size=689, ...}) = 0
munmap(0x7001c000, 689) = 0
close(8)= 0
setgroups32(1, [0]) = 0
geteuid32() = 0
setuid32(33)= 0
getpid()= 20470
epoll_create(1) = -1 ENOSYS (Function not
implemented)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 20470 detached
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fast data access MMU miss
[EMAIL PROTECTED] wrote: Hello I have a fast data access MMU miss since this morning when I am trying to boot with the cdrom of my U60. Searching the net , it seems the motherboard is defective, Is someone can confirm me the this state of fact ? This is most often caused by a faulty CDROM or drive. The OBP has minimal intelligence, so it reads the initial boot sector and executes it without checking for corruption. This inevitably leads to an illegal memory reference and thus to the message that you see. Try using a known good Sun pressed CD, not a CDR. If this fails your drive has probably expired, if you do not have a spare try booting from the network. The older drives in the U60 will probably have problems reading CDRs written at high speed and will almost certainly not read a CDRW. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fast data access MMU miss
Have you tried this on the OBP?: setenv diag-level max setenv diag-switch? true Please note that diag-device could be different from boot-device. Cheers, Daniel On Thu, 2006-10-12 at 09:25 +0200, [EMAIL PROTECTED] wrote: > Hello > > I have a fast data access MMU miss > since this morning when I am trying to > boot with the cdrom of my U60. > Searching the net , it seems the motherboard > is defective, Is someone can confirm me the this > state of fact ? > > best regards > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fast data access MMU miss
Daniel van Eeden wrote: > Have you tried this on the OBP?: > setenv diag-level max > setenv diag-switch? true > > Please note that diag-device could be different from boot-device. > > Well I just did that but I find the same error message -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
fast data access MMU miss
Hello I have a fast data access MMU miss since this morning when I am trying to boot with the cdrom of my U60. Searching the net , it seems the motherboard is defective, Is someone can confirm me the this state of fact ? best regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sunlance broken in current sparc32 installer
On Thursday 12 October 2006 08:57, Robert Waldner wrote: > Yesterday I needed to netboot one of my SS10s, so I grabbed the current > boot.img[0]. Unfortunately, the kernel's broken somewhat, as there are > unresolved symbols in (at least) sunlance. Which therefore doesn't > load and makes netbooting Sarge de facto impossible on machines with > LANCE ethernet. This is a known issue listed in the errata [1] for the installer released with Sarge r3. We are working to correct this for the r4 release. Cheers, FJP [1]http://www.debian.org/releases/sarge/debian-installer/index.en.html#errata pgpoGuho0s8lq.pgp Description: PGP signature
