Re: Netra X1 strange lock up Debian 3.1, kernel 2.6.12.3

[Luigi Gangitano]

Il giorno 05/set/05, alle ore 22:25, William Herrin ha scritto:

I'm getting a wierd partial-lockup under Debian 3.1 (sarge) on a  
Netra X1

with a 2.6.11.3 kernel compiled fresh from the sources.


I had the same problem on my Sun Blade 100. Never got to catch lock- 
up while still logged in, so I could not debug this issue.


This happened with kernels from 2.6.9 to 2.6.11. It appears to have  
been fixed in 2.6.12, no lockup in the last 20 days (before it was 6  
days between each freeze).


Regards,

Luigi Gangitano


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Netra X1 strange lock up Debian 3.1, kernel 2.6.12.3

[William Herrin]

> > I'm getting a wierd partial-lockup under Debian 3.1 (sarge) on a  
> > Netra X1
> > with a 2.6.11.3 kernel compiled fresh from the sources.
> 
> This happened with kernels from 2.6.9 to 2.6.11. It appears to have  
> been fixed in 2.6.12, no lockup in the last 20 days (before it was 6  
> days between each freeze).

I'm sorry, that was a typo on my part. Its a 2.6.12.3 kernel, not 2.6.11.3.
I used 2.6.11.7 and when that failed I tried 2.6.12.3. The latter also failed.

Did you have good results with 2.6.8? Are there any serious bugs I need to
watch out for if I drop back to that version?

Thanks,
Bill

-- 
William D. Herrin  [EMAIL PROTECTED]  [EMAIL PROTECTED]
3005 Crane Dr.Web: 
Falls Church, VA 22042-3004


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Netra X1 strange lock up Debian 3.1, kernel 2.6.12.3

[William Herrin]

> The box is up for weeks on end you say? But you have no swap added. 
> Could it be linux's 2.6 MM refusing to spawn a new shell due to low mem?

I disabled the swap after the second time it happened on the theory that it
might be thrashing (the machine is remotely located so I can't just listen
for the drive). It dies the same way with or without swap.

Anyway, I tested a program which allocated and initialized memory until there
was none left. The kernel killed it like its supposed to and the system date
didn't change. So, it doesn't seem to be an out of memory condition.

/* malloc memory until I croak */

#include 
#include 
#include 
#include 

int main (int argc, char **argv)
{
  char *p;

  while (1) {
p = (char*) malloc (sizeof(char) * 1);
if (!p) {
  printf ("Out of memory hit; waiting.\n");
  fflush (stdout);
  sleep (300);
  return 1;
}
bzero (p,sizeof(char)*1);
  }
  return 0;
}

{lily:herrin:/home/h/herrin:!} ./a.out
Killed
{lily:herrin:/home/h/herrin:!}


I have observed that if I have more running it dies sooner. For example, when
I had sendmail and apache running too it would die after a week or ten days.
Now it only dies every few weeks.

-Bill


-- 
William D. Herrin  [EMAIL PROTECTED]  [EMAIL PROTECTED]
3005 Crane Dr.Web: 
Falls Church, VA 22042-3004


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Netra X1 strange lock up Debian 3.1, kernel 2.6.12.3

[Scott Walker]

The box is up for weeks on end you say? But you have no swap added. 
Could it be linux's 2.6 MM refusing to spawn a new shell due to low mem?


William Herrin wrote:

I'm getting a wierd partial-lockup under Debian 3.1 (sarge) on a Netra X1
with a 2.6.11.3 kernel compiled fresh from the sources.

The system will run fine for several weeks. Then it will refuse to run new
shells. Running daemons will continue to run but an attempt to start a new
shell will fail. I put some echos in /etc/profile to see where it stops.
The login stops responding when running the "id -u" command in /etc/profile.
When I remove that command it makes it to the end of /etc/profile but never
starts $HOME/.profile.

The other symptom is that the system clock jumps forward by 3 days, 6 hours,
11 minutes and 15 seconds. Every time. NTP is not running, nor is anything
else that should modify the date.

Examples from the /var/log/messages:

Jul 27 21:03:19 lily -- MARK --
Jul 27 21:04:19 lily -- MARK --
Jul 27 21:05:19 lily -- MARK --
Jul 31 03:17:34 lily -- MARK --
Jul 31 03:18:34 lily -- MARK --
Jul 31 03:19:34 lily -- MARK --

Sep  2 10:27:32 lily -- MARK --
Sep  2 10:28:32 lily -- MARK --
Sep  2 10:29:32 lily -- MARK --
Sep  5 16:41:47 lily -- MARK --
Sep  5 16:42:47 lily -- MARK --
Sep  5 16:43:47 lily -- MARK --

So, the hard drive is still writing. The Bind daemon (named) continues to run
and respond to queries. That and ssh are the only network services I have
running on the box. The kernel continues to output log messages from
iptables (with the wrong date) but outputs no other messages. Ssh will
connect, but it may or may not get past public key authentication. The
console will accept a login and make it past /etc/profile, but never
makes it to a prompt.

uname -a
Linux lily 2.6.12.3-lily #1 Mon Aug 1 18:40:53 EDT 2005 sparc64 GNU/Linux

cat /proc/cpuinfo
cpu : TI UltraSparc IIe (Hummingbird)
fpu : UltraSparc IIe integrated FPU
promlib : Version 3 Revision 0
prom: 4.0.6
type: sun4u
ncpus probed: 1
ncpus active: 1
Cpu0Bogo: 794.62
Cpu0ClkTck  : 17d78400
MMU Type: Spitfire

free
 total   used   free sharedbuffers cached
Mem:512496  49408 463088  0   8400  24976
-/+ buffers/cache:  16032 496464
Swap:0  0  0


I had the same problem with a 2.6.11.7 kernel, also compiled fresh from the
source on kernel.org. I havn't tried the stock Sarge kernel; that's next on my
list.

Has anyone seen anything like this before? Any suggestions for what to try to
track down the problem?

Thanks in advance,
Bill Herrin





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RE: D-I update for Sparc (daily builds)

[Jared Valentine]

Are there also tftpboot images with 2.6.12?  Where are these images located?


Thanks,

Jared Valentine
[EMAIL PROTECTED]

-Original Message-
From: Frans Pop [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 05, 2005 3:57 PM
To: debian-sparc@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: D-I update for Sparc (daily builds)

Hi,

The default kernel for sparc64 installations is now 2.6.12, with 2.4.27 as 
alternative.
For sparc32 support for 2.6 based installations has been dropped as there 
is no 2.6.12 kernel available (yet?); the 2.4.27 kernel will be supported 
as long as no decision is made to drop it.

NOTE: As the changes for building CDs still have to be implemented, the
  switch may mean that CD installations may be broken the next days.

If you boot a mini.iso or CD image, you can select the following options:
- install : default installation
- expert  : installation with debconf/priority=low
- rescue  : use the installer for rescue

For sparc64 CD images these options will boot the 2.6.12 kernel, to boot 
the alternative 2.4.27 kernel, use install24, expert24 or rescue24.

The official images for Sarge are of course not affected by this, only the 
daily builds are.

Cheers,
FJP



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: D-I update for Sparc (daily builds)

[Tyler]

Frans Pop wrote:


Hi,

The default kernel for sparc64 installations is now 2.6.12, with 2.4.27 as 
alternative.
For sparc32 support for 2.6 based installations has been dropped as there 
is no 2.6.12 kernel available (yet?); the 2.4.27 kernel will be supported 
as long as no decision is made to drop it.


NOTE: As the changes for building CDs still have to be implemented, the
 switch may mean that CD installations may be broken the next days.

If you boot a mini.iso or CD image, you can select the following options:
- install : default installation
- expert  : installation with debconf/priority=low
- rescue  : use the installer for rescue

For sparc64 CD images these options will boot the 2.6.12 kernel, to boot 
the alternative 2.4.27 kernel, use install24, expert24 or rescue24.


The official images for Sarge are of course not affected by this, only the 
daily builds are.


Cheers,
FJP
 

What is the address where the daily builds are available?  Also, does 
this imply that there is a *working* bootable image for people having 
the Fast MMU Access error with any/all CD's they've tried thus far?  If 
it doesn't fix this problem, when can we expect a working image?  Also, 
is there a direct link to an image that *does* work... the only one I've 
found to be reported as working around this bug, was a daily image from 
a few months ago, that is no longer on any archives/sites/mirrors that I 
can find.


Thanks,
Tyler.


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.18/89 - Release Date: 9/2/2005


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

D-I update for Sparc (daily builds)

[Frans Pop]

Hi,

The default kernel for sparc64 installations is now 2.6.12, with 2.4.27 as 
alternative.
For sparc32 support for 2.6 based installations has been dropped as there 
is no 2.6.12 kernel available (yet?); the 2.4.27 kernel will be supported 
as long as no decision is made to drop it.

NOTE: As the changes for building CDs still have to be implemented, the
  switch may mean that CD installations may be broken the next days.

If you boot a mini.iso or CD image, you can select the following options:
- install : default installation
- expert  : installation with debconf/priority=low
- rescue  : use the installer for rescue

For sparc64 CD images these options will boot the 2.6.12 kernel, to boot 
the alternative 2.4.27 kernel, use install24, expert24 or rescue24.

The official images for Sarge are of course not affected by this, only the 
daily builds are.

Cheers,
FJP


pgpxQAm0jHvB4.pgp
Description: PGP signature

Invitation to the Oldenburg Linux Developers Meeting

[Martin Schulze]

Dear developers,

there will be another Linux developers meeting taking place in
Oldenburg at the last weekend in September this year.  Like last year,
we will be able to start on Wednesday and work until Sunday.  So
diligent people can work up to four days in Oldenburg.


Executive summary:

URL:   http://meeting.ffis.de/Oldenburg2005/
What:  Oldenburg Linux Developers Meeting #A
Who:   Every developer interested in Linux on non-i386 platforms
   Every developer interested in developing the debian-installer
   Every developer interested in Debian-Java
When:  September, 21st to 25th (Wednesday noon to Sunday afternoon)
Where: University of Oldenburg, science building in Oldenburg Wechloy
Orga:  ffis e.V., Martin 'Joey' Schulze
Bonus: Regular rooms again, at least partially


The goal of this developers meeting is to provide developers a means
to work in common on the non-i386 Linux ports and related topics and
to further the exchange of ideas and discussion about these ports.
However, Debian developers and Debian Java people have asked whether
they can piggy-back a meeting at the same location as well.

We will have dedicated working and sleeping rooms in the university.
We are allowed to use the shower facility of the sports department
nearby where we can sleep as well this year.

We will have dinner together in a restaurant in the evening.  I'll put
a plan will be on the web soon.  If you prefer to stay at the
university and not go out having a dinner, please let me know in time
as this affects restaurant space requirements.

We will have a never-ending breakfast in one of the working rooms.
I'll get rolls each morning and try to ensure that there will be
enough butter, cheese, sausages, jam, Nutella and stuff.  I will also
take care of non-alcoholic fluids.

Beside machines, equipment and documentation you'll need to take with
you a sleeping bag, maybe a camping mat or cot, towels, shower stuff,
personal toilett accessories, maybe medicine, clothes.  A mug, plate
and cutlery are optional but helpful.  Don't forget enough power
chords, extenders and network cables.

You'll find routing information on the website mentioned above.

If you would like to attend the meeting, please send back the
following form, so that I can calculate space, power and food.

8<8<8<8<8<8<8<
Name :

Date of arrival .: ( ) Wednesday, Sep, 21st
   ( ) Thursday, Sep, 22nd
   ( ) Friday, Sep, 23rd 
   ( ) Saturday, Sep, 24th

Date of departure ...: ( ) Friday, Sep. 23rd
   ( ) Saturday, Sep. 24th
   ( ) Sunday, Sep. 25th

___ usable seats in my car, once arrived (only if you come by car)
(four usable seets --> one driver, three guests)

Special requirements for food: __
(Vegetarian should be covered with 10% of all, vegan people will need
special attention)
8<8<8<8<8<8<8<

If you have any further questions, please don't hesitate to ask me.

Kind regards,

Joey

-- 
Whenever you meet yourself you're in a time loop or in front of a mirror.

Please always Cc to me when replying to me on the lists.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Netra X1 strange lock up Debian 3.1, kernel 2.6.12.3

[Admar Schoonen]

On Mon, Sep 05, 2005 at 04:25:34PM -0400, William Herrin wrote:
> I'm getting a wierd partial-lockup under Debian 3.1 (sarge) on a Netra X1
> with a 2.6.11.3 kernel compiled fresh from the sources.



> Has anyone seen anything like this before? Any suggestions for what to try to
> track down the problem?

I have exactly the same problems on my blade 100 (same cpu, but at 500 MHz, 640
MB ram), running custom kernel 2.6.9 (from kernel.org sources I believe).
Unfortunately, I have no clue what is causing the problem, nor do I know any
workaround.

As this is my workstation, and usually I'm the only user, I just power cycle the
box, but it can be very inconvenient.

Admar


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Netra X1 strange lock up Debian 3.1, kernel 2.6.12.3

[William Herrin]

I'm getting a wierd partial-lockup under Debian 3.1 (sarge) on a Netra X1
with a 2.6.11.3 kernel compiled fresh from the sources.

The system will run fine for several weeks. Then it will refuse to run new
shells. Running daemons will continue to run but an attempt to start a new
shell will fail. I put some echos in /etc/profile to see where it stops.
The login stops responding when running the "id -u" command in /etc/profile.
When I remove that command it makes it to the end of /etc/profile but never
starts $HOME/.profile.

The other symptom is that the system clock jumps forward by 3 days, 6 hours,
11 minutes and 15 seconds. Every time. NTP is not running, nor is anything
else that should modify the date.

Examples from the /var/log/messages:

Jul 27 21:03:19 lily -- MARK --
Jul 27 21:04:19 lily -- MARK --
Jul 27 21:05:19 lily -- MARK --
Jul 31 03:17:34 lily -- MARK --
Jul 31 03:18:34 lily -- MARK --
Jul 31 03:19:34 lily -- MARK --

Sep  2 10:27:32 lily -- MARK --
Sep  2 10:28:32 lily -- MARK --
Sep  2 10:29:32 lily -- MARK --
Sep  5 16:41:47 lily -- MARK --
Sep  5 16:42:47 lily -- MARK --
Sep  5 16:43:47 lily -- MARK --

So, the hard drive is still writing. The Bind daemon (named) continues to run
and respond to queries. That and ssh are the only network services I have
running on the box. The kernel continues to output log messages from
iptables (with the wrong date) but outputs no other messages. Ssh will
connect, but it may or may not get past public key authentication. The
console will accept a login and make it past /etc/profile, but never
makes it to a prompt.

uname -a
Linux lily 2.6.12.3-lily #1 Mon Aug 1 18:40:53 EDT 2005 sparc64 GNU/Linux

cat /proc/cpuinfo
cpu : TI UltraSparc IIe (Hummingbird)
fpu : UltraSparc IIe integrated FPU
promlib : Version 3 Revision 0
prom: 4.0.6
type: sun4u
ncpus probed: 1
ncpus active: 1
Cpu0Bogo: 794.62
Cpu0ClkTck  : 17d78400
MMU Type: Spitfire

free
 total   used   free sharedbuffers cached
Mem:512496  49408 463088  0   8400  24976
-/+ buffers/cache:  16032 496464
Swap:0  0  0


I had the same problem with a 2.6.11.7 kernel, also compiled fresh from the
source on kernel.org. I havn't tried the stock Sarge kernel; that's next on my
list.

Has anyone seen anything like this before? Any suggestions for what to try to
track down the problem?

Thanks in advance,
Bill Herrin


-- 
William D. Herrin  [EMAIL PROTECTED]  [EMAIL PROTECTED]
3005 Crane Dr.Web: 
Falls Church, VA 22042-3004


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian CD won't boot on SunBlade2000

[Frans Pop]

On Monday 05 September 2005 13:40, wolf wolf wrote:
> How do I set up a netboot? (I understand that I need to configure a
> server). Can I netboot from a non sparc machine, for instance, Debian
> on HP?

Try the installation guide for instructions...
http://www.debian.org/releases/sarge/installmanual


pgpZIksdf7E8Q.pgp
Description: PGP signature

Re: Debian CD won't boot on SunBlade2000

[wolf wolf]

How do I set up a netboot? (I understand that I need to configure a
server). Can I netboot from a non sparc machine, for instance, Debian
on HP?On 9/4/05, Jon Biddell <[EMAIL PROTECTED]> wrote:
>> I am trying to install debian (3.01a) on a SynBlade2000 server.> when I type at the OK prompt "boot cdrom" I get this anoying error:> Fast Data Access MMU Miss.> I googled this error, found out that it has to do with the boot
> loader, or somthing, but didn't find a solution. Dose any one how> to fix this?>Welcome to my nightmare !!!I have the same problem on a SunBlade 1000, and had to resort to anetboot to get it working.
It's as known bug in the installer, but I don't believe there hasbeen a solution posted yet.Jon> Thanks.