* Re: Fast HDLC driver [not found] <200211191615.gAJGFVw09351@hofr.at> @ 2002-11-19 19:01 ` Owen Green 2002-11-20 11:55 ` linuxppc_2_4_devel, rc1 and rc2 problem Joakim Tjernlund 0 siblings, 1 reply; 12+ messages in thread From: Owen Green @ 2002-11-19 19:01 UTC (permalink / raw) To: Der Herr Hofrat; +Cc: linuxppc-embedded You can find it on: http://www.qslinux.com/ I`ve posted the .c file in the list too... Owen. --- Der Herr Hofrat <der.herr@mail.hofr.at> wrote: > > > > Hi all, > > > > I`ve started working on a new project were a high > > performace hdlc channel is needed (at least 4Mbps > on > > MPC8xx-50Mhz). > > I found several drivers for hdlc, but some are not > > very fast (copies memory,... ), most of them calls > > netif_rx from inside interrupt_handler (I don`t > think > > this is the best place for doing that, watchdog > may > > expire if the interface gets very busy..). > > The only driver I found that seems to be really > fast > > and doesnt do all this stuff in interrupt context > is > > for kernel-2.2 (QSLINUX). > > do you have a URL to that driver ?? > > thx ! > hofrat ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-19 19:01 ` Fast HDLC driver Owen Green @ 2002-11-20 11:55 ` Joakim Tjernlund 2002-11-20 15:23 ` Tom Rini 0 siblings, 1 reply; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-20 11:55 UTC (permalink / raw) To: linuxppc-dev I upgraded my linuxppc_2_4_devel from pre8(1.1130) to rc1(1.1157) and noticed that may syslog had problems to start: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (jffs2 filesystem). Freeing unused kernel memory: 64k init INIT: version 2.78 booting Fast boot, no file system check none on /dev/shm type shm (rw) ramfs on /tmp type ramfs (rw) ramfs on /var/run type ramfs (rw) ramfs on /tftpboot/log type ramfs (rw) Cleaning: /etc/network/ifstate. Enabling packet forwarding: done. Disable TCP/IP Explicit Congestion Notification: done. Configuring network interfaces: done. Cleaning: /tmp /var/lock /var/run. INIT: Entering runlevel: 2 Starting system log daemon: syslogd/etc/rc.d/rc2.d/S10syslog: line 53: 50 Ter minated start-stop-daemon -v --start --quiet --exec /sbin/syslogd - - $SYSLOGD klogd. Starting internet superserver: inetd. I then tried rc2(BK curr) and got the same problem. I am running a custom mpc860 board. Anyone else noticed this? Jocke ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 11:55 ` linuxppc_2_4_devel, rc1 and rc2 problem Joakim Tjernlund @ 2002-11-20 15:23 ` Tom Rini 2002-11-20 15:46 ` Joakim Tjernlund 0 siblings, 1 reply; 12+ messages in thread From: Tom Rini @ 2002-11-20 15:23 UTC (permalink / raw) To: Joakim Tjernlund; +Cc: linuxppc-dev On Wed, Nov 20, 2002 at 12:55:01PM +0100, Joakim Tjernlund wrote: > > I upgraded my linuxppc_2_4_devel from pre8(1.1130) to rc1(1.1157) and noticed that > may syslog had problems to start: > [snip] > I then tried rc2(BK curr) and got the same problem. I am running a custom mpc860 board. > > Anyone else noticed this? I haven't tried yet. Have you tried 'porting' your custom board to vanilla 2.4.x, which would make it easier to see which, if any of these upsteram revisions introduced a problem? The only 8xx-specific changes in that time have been your i2c changes and a serial fixup. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 15:23 ` Tom Rini @ 2002-11-20 15:46 ` Joakim Tjernlund 2002-11-20 16:01 ` Tom Rini 0 siblings, 1 reply; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-20 15:46 UTC (permalink / raw) To: Tom Rini; +Cc: linuxppc-dev > > On Wed, Nov 20, 2002 at 12:55:01PM +0100, Joakim Tjernlund wrote: > > > > > I upgraded my linuxppc_2_4_devel from pre8(1.1130) to rc1(1.1157) and noticed that > > may syslog had problems to start: > > > [snip] > > > I then tried rc2(BK curr) and got the same problem. I am running a custom mpc860 board. > > > > Anyone else noticed this? > > I haven't tried yet. Have you tried 'porting' your custom board to > vanilla 2.4.x, which would make it easier to see which, if any of these > upsteram revisions introduced a problem? The only 8xx-specific changes > in that time have been your i2c changes and a serial fixup. hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. Jocke > > -- > Tom Rini (TR1265) > http://gate.crashing.org/~trini/ > ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 15:46 ` Joakim Tjernlund @ 2002-11-20 16:01 ` Tom Rini 2002-11-20 18:55 ` Joakim Tjernlund 0 siblings, 1 reply; 12+ messages in thread From: Tom Rini @ 2002-11-20 16:01 UTC (permalink / raw) To: Joakim Tjernlund; +Cc: linuxppc-dev On Wed, Nov 20, 2002 at 04:46:05PM +0100, Joakim Tjernlund wrote: > > > > > On Wed, Nov 20, 2002 at 12:55:01PM +0100, Joakim Tjernlund wrote: > > > > > > > > I upgraded my linuxppc_2_4_devel from pre8(1.1130) to rc1(1.1157) and noticed that > > > may syslog had problems to start: > > > > > [snip] > > > > > I then tried rc2(BK curr) and got the same problem. I am running a custom mpc860 board. > > > > > > Anyone else noticed this? > > > > I haven't tried yet. Have you tried 'porting' your custom board to > > vanilla 2.4.x, which would make it easier to see which, if any of these > > upsteram revisions introduced a problem? The only 8xx-specific changes > > in that time have been your i2c changes and a serial fixup. > > hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. > No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. They both made it in post rc1 I think, yes. Try going back carefully via bk changes and bk export -tr1.xxxxx (find when /home/.../linuxppc_2_4 was merged into /home/.../linuxppc_2_4_devel). -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 16:01 ` Tom Rini @ 2002-11-20 18:55 ` Joakim Tjernlund 2002-11-20 19:14 ` Tom Rini 0 siblings, 1 reply; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-20 18:55 UTC (permalink / raw) To: Tom Rini; +Cc: linuxppc-dev > > > > hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. > > No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. > > They both made it in post rc1 I think, yes. Try going back carefully > via bk changes and bk export -tr1.xxxxx (find when > /home/.../linuxppc_2_4 was merged into /home/.../linuxppc_2_4_devel). The error ocurres between changeset 1.1130 - 1.1137. I forgot to mention that the error only happens on a 862,100Mhz, 16KB icache, 8KB dcache. My 860,80Mz does not show the problem. Idea's ? Jocke ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 18:55 ` Joakim Tjernlund @ 2002-11-20 19:14 ` Tom Rini 2002-11-21 13:30 ` Joakim Tjernlund 2002-11-21 15:27 ` Joakim Tjernlund 0 siblings, 2 replies; 12+ messages in thread From: Tom Rini @ 2002-11-20 19:14 UTC (permalink / raw) To: Joakim Tjernlund; +Cc: linuxppc-dev On Wed, Nov 20, 2002 at 07:55:35PM +0100, Joakim Tjernlund wrote: > > > > > > > hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. > > > No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. > > > > They both made it in post rc1 I think, yes. Try going back carefully > > via bk changes and bk export -tr1.xxxxx (find when > > /home/.../linuxppc_2_4 was merged into /home/.../linuxppc_2_4_devel). > > The error ocurres between changeset 1.1130 - 1.1137. > I forgot to mention that the error only happens on a 862,100Mhz, 16KB icache, 8KB dcache. > My 860,80Mz does not show the problem. > > Idea's ? Can you narrow down the ChangeSet it occured at a bit? -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 19:14 ` Tom Rini @ 2002-11-21 13:30 ` Joakim Tjernlund 2002-11-21 15:27 ` Joakim Tjernlund 1 sibling, 0 replies; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-21 13:30 UTC (permalink / raw) To: Tom Rini; +Cc: linuxppc-dev > On Wed, Nov 20, 2002 at 07:55:35PM +0100, Joakim Tjernlund wrote: > > > > > > > > > > hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. > > > > No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. > > > > > > They both made it in post rc1 I think, yes. Try going back carefully > > > via bk changes and bk export -tr1.xxxxx (find when > > > /home/.../linuxppc_2_4 was merged into /home/.../linuxppc_2_4_devel). > > > > The error ocurres between changeset 1.1130 - 1.1137. > > I forgot to mention that the error only happens on a 862,100Mhz, 16KB icache, 8KB dcache. > > My 860,80Mz does not show the problem. > > > > Idea's ? > > Can you narrow down the ChangeSet it occured at a bit? Aaargh, now I am getting it in pre8 as well. However I have made some progress: I have 2 custom boards one mpc862(100Mhz, 16KB icache, 8KB dcache) and a mpc860(80Mz,4KB icache, 4KB dcache). If I overclock the mpc860 to 100MHz I get the same problem. If I set the clock on both boards to 95MHz all is well. If I overclock the mpc862 to 105 MHz it works fine. It turns out that syslog is actually running after the error. If I stop syslog and start it again it works fine. If adjust my script so klogd is started before syslogd all is well to. This looks like a race somewhere to me, but i have no clue as to where. Anyone? Jocke ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-20 19:14 ` Tom Rini 2002-11-21 13:30 ` Joakim Tjernlund @ 2002-11-21 15:27 ` Joakim Tjernlund 2002-11-22 8:28 ` Joakim Tjernlund 1 sibling, 1 reply; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-21 15:27 UTC (permalink / raw) To: linuxppc-embedded Sending this to the embedded list as well. Jocke > On Wed, Nov 20, 2002 at 07:55:35PM +0100, Joakim Tjernlund wrote: > > > > > > > > > > hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. > > > > No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. > > > > > > They both made it in post rc1 I think, yes. Try going back carefully > > > via bk changes and bk export -tr1.xxxxx (find when > > > /home/.../linuxppc_2_4 was merged into /home/.../linuxppc_2_4_devel). > > > > The error ocurres between changeset 1.1130 - 1.1137. > > I forgot to mention that the error only happens on a 862,100Mhz, 16KB icache, 8KB dcache. > > My 860,80Mz does not show the problem. > > > > Idea's ? > > Can you narrow down the ChangeSet it occured at a bit? Aaargh, now I am getting it in pre8 as well. However I have made some progress: I have 2 custom boards one mpc862(100Mhz, 16KB icache, 8KB dcache) and a mpc860(80Mz,4KB icache, 4KB dcache). If I overclock the mpc860 to 100MHz I get the same problem. If I set the clock on both boards to 95MHz all is well. If I overclock the mpc862 to 105 MHz it works fine. It turns out that syslog is actually running after the error. If I stop syslog and start it again it works fine. If adjust my script so klogd is started before syslogd all is well to. This looks like a race somewhere to me, but i have no clue as to where. Anyone? Jocke ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-21 15:27 ` Joakim Tjernlund @ 2002-11-22 8:28 ` Joakim Tjernlund 2002-11-22 9:31 ` David Woodhouse 0 siblings, 1 reply; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-22 8:28 UTC (permalink / raw) To: linuxppc-embedded, dwmw2 > > Sending this to the embedded list as well. > > Jocke > > On Wed, Nov 20, 2002 at 07:55:35PM +0100, Joakim Tjernlund wrote: > > > > > > > > > > > > > hmm, my i2c stuff got into rc2 (and uart too?). I see this on rc2 AND rc1, but NOT in pre8. > > > > > No, I have not tried to port it to vanilla 2.4.x. It requires some work to do that. > > > > > > > > They both made it in post rc1 I think, yes. Try going back carefully > > > > via bk changes and bk export -tr1.xxxxx (find when > > > > /home/.../linuxppc_2_4 was merged into /home/.../linuxppc_2_4_devel). > > > > > > The error ocurres between changeset 1.1130 - 1.1137. > > > I forgot to mention that the error only happens on a 862,100Mhz, 16KB icache, 8KB dcache. > > > My 860,80Mz does not show the problem. > > > > > > Idea's ? > > > > Can you narrow down the ChangeSet it occured at a bit? > > Aaargh, now I am getting it in pre8 as well. However I have made > some progress: > > I have 2 custom boards one mpc862(100Mhz, 16KB icache, 8KB dcache) and a > mpc860(80Mz,4KB icache, 4KB dcache). If I overclock the mpc860 to 100MHz I get > the same problem. If I set the clock on both boards to 95MHz all is well. If I overclock > the mpc862 to 105 MHz it works fine. > > It turns out that syslog is actually running after the error. If I stop syslog and > start it again it works fine. If adjust my script so klogd is started before > syslogd all is well to. > > This looks like a race somewhere to me, but i have no clue as to where. > > Anyone? > > Jocke hmm, if I upgrade the JFFS2 filesystem to CVS HEAD, the problem goes away. Jocke ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-22 8:28 ` Joakim Tjernlund @ 2002-11-22 9:31 ` David Woodhouse 2002-11-22 10:14 ` Joakim Tjernlund 0 siblings, 1 reply; 12+ messages in thread From: David Woodhouse @ 2002-11-22 9:31 UTC (permalink / raw) To: joakim.tjernlund; +Cc: linuxppc-embedded joakim.tjernlund@lumentis.se said: > Sending this to the embedded list as well. -ENOCONTEXT. -- dwmw2 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: linuxppc_2_4_devel, rc1 and rc2 problem. 2002-11-22 9:31 ` David Woodhouse @ 2002-11-22 10:14 ` Joakim Tjernlund 0 siblings, 0 replies; 12+ messages in thread From: Joakim Tjernlund @ 2002-11-22 10:14 UTC (permalink / raw) To: David Woodhouse; +Cc: linuxppc-embedded > > -ENOCONTEXT. :-), sorry the context was lost due to me beeing a moron. Anyway here is the problem again: I upgraded my linuxppc_2_4_devel from pre8(1.1130) to rc1(1.1157) and noticed that my syslog had problems to start: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (jffs2 filesystem). Freeing unused kernel memory: 64k init INIT: version 2.78 booting Fast boot, no file system check none on /dev/shm type shm (rw) ramfs on /tmp type ramfs (rw) ramfs on /var/run type ramfs (rw) ramfs on /tftpboot/log type ramfs (rw) Cleaning: /etc/network/ifstate. Enabling packet forwarding: done. Disable TCP/IP Explicit Congestion Notification: done. Configuring network interfaces: done. Cleaning: /tmp /var/lock /var/run. INIT: Entering runlevel: 2 Starting system log daemon: syslogd/etc/rc.d/rc2.d/S10syslog: line 53: 50 Ter minated start-stop-daemon -v --start --quiet --exec /sbin/syslogd - - $SYSLOGD klogd. Starting internet superserver: inetd. I then started to backout the changes between pre8 and rc1 to see where the problem was. That gave me: >> Aaargh, now I am getting it in pre8 as well. However I have made >> some progress: >> >> I have 2 custom boards one mpc862(100Mhz, 16KB icache, 8KB dcache) and a >> mpc860(80Mz,4KB icache, 4KB dcache). If I overclock the mpc860 to 100MHz I get >> the same problem. If I set the clock on both boards to 95MHz all is well. If I overclock >> the mpc862 to 105 MHz it works fine. >> >> It turns out that syslog is actually running after the error. If I stop syslog and >> start it again it works fine. If adjust my script so klogd is started before >> syslogd all is well to. >> >> This looks like a race somewhere to me, but i have no clue as to where. >> >> Anyone? >> >> Jocke > >hmm, if I upgrade the JFFS2 filesystem to CVS HEAD, the problem goes away. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2002-11-22 10:14 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200211191615.gAJGFVw09351@hofr.at>
2002-11-19 19:01 ` Fast HDLC driver Owen Green
2002-11-20 11:55 ` linuxppc_2_4_devel, rc1 and rc2 problem Joakim Tjernlund
2002-11-20 15:23 ` Tom Rini
2002-11-20 15:46 ` Joakim Tjernlund
2002-11-20 16:01 ` Tom Rini
2002-11-20 18:55 ` Joakim Tjernlund
2002-11-20 19:14 ` Tom Rini
2002-11-21 13:30 ` Joakim Tjernlund
2002-11-21 15:27 ` Joakim Tjernlund
2002-11-22 8:28 ` Joakim Tjernlund
2002-11-22 9:31 ` David Woodhouse
2002-11-22 10:14 ` Joakim Tjernlund
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.