8139too.c and 2.4.4-pre1 kernel burp

2001-04-08 Thread Frank Jacobberger

Jeff,

I noticed the following on boot with 2.4.4-pre1:

kernel: eth0: Too much work at interrupt, IntrStatus=0x0001.

What is this saying to me :)

Thanks,

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: 8139too.c and 2.4.4-pre1 kernel burp

2001-04-08 Thread Frank Jacobberger

Jeff Garzik wrote:

> Frank Jacobberger wrote:
> 
>> Jeff,
>> 
>> I noticed the following on boot with 2.4.4-pre1:
>> 
>> kernel: eth0: Too much work at interrupt, IntrStatus=0x0001.
>> 
>> What is this saying to me :)
> 
> 
> How often does this occur?  A lot, or just once or twice?
> 
Every time I boot the kernel... very last statement.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



loop races broke big time in 2.4.2-pre3

2001-02-15 Thread Frank Jacobberger

So I assume we wait on baited breathe for 2.4.2-pre4 or
branch off soon to 2.5 blah?

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



exit.c -prerelease-diff - Jan 4

2001-01-04 Thread Frank Jacobberger

+  current->state = TASK_ZOMBIE;

Why the update on exit.c to include TASK_ZOMBIE?

Thanks,

Frank -

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



lcalls ???

2000-12-05 Thread Frank Jacobberger

Would someone be so kind and inform where I might go ferret out why I'm
getting these multiple lcalls from pci-pc.o?

Would I look real hard at General Setup in make menuconfig??

The kernels I have maked all work, but this little area puzzles me

___
kgcc -D_KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686  -c -o
pci-pc.o pci-pc.c
{standard input}: Assembler messages:
{standard input} 829: Warning: indirect lcall without `*'
{standard input}:911: Warning: indirect lcall without `*'
{standard input}:1006: Warning: indirect lcall without `*'
{standard input}:1046: Warning: indirect lcall without `*'
{standard input}:1076: Warning: indirect lcall without `*'
{standard input}:1106: Warning: indirect lcall without `*'
{standard input}:1137: Warning: indirect lcall without `*'
{standard input}:1166: Warning: indirect lcall without `*'
{standard input}:1195: Warning: indirect lcall without `*'
{standard input}:1497: Warning: indirect lcall without `*'
{standard input}:1592: Warning: indirect lcall without `*'
kgcc -D_KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686  -c -o
pci-irq.o pci-irq.c


Any pointers here would be appreciated.

Thanks again,

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



RH 7 update of 2.96 gcc and make

2000-12-23 Thread Frank Jacobberger

Seems stable enough... the following are excerpts of some of the
warnings on make bzImage:

-

-boundary=2 -march=i686-c -o tcp_input.o tcp_input.c
tcp_input.c:1944:78: warning: pasting would not give a valid
preprocessing token
tcp_input.c:2478:76: warning: pasting would not give a valid
preprocessing token
tcp_input.c:2485:52: warning: pasting would not give a valid
preprocessing token
tcp_input.c:2591:52: warning: pasting would not give a valid
preprocessing token
tcp_input.c:2604:79: warning: pasting would not give a valid
preprocessing token
tcp_input.c:2733:61: warning: pasting would not give a valid
preprocessing token

-

make[3]: Entering directory `/usr/src/linux-2.4.0-test12/fs/smbfs'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686  -DSMBFS_PARANOIA  -c -o proc.o
proc.c
In file included from proc.c:27:
smb_debug.h:14:56: warning: nothing can be pasted after this token
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686  -DSMBFS_PARANOIA  -c -o dir.o
dir.c
In file included from dir.c:20:
smb_debug.h:14:56: warning: nothing can be pasted after this token
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686  -DSMBFS_PARANOIA  -c -o
cache.o cache.c
In file included from cache.c:23:
smb_debug.h:14:56: warning: nothing can be pasted after this token
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686  -DSMBFS_PARANOIA  -c -o sock.o
sock.c
In file included from sock.c:29:
smb_debug.h:14:56: warning: nothing can be pasted after this token
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686  -DSMBFS_PARANOIA  -c -o
inode.o inode.c
In file included from inode.c:33:
smb_debug.h:14:56: warning: nothing can be pasted after this token
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686  -DSMBFS_PARANOIA  -c -o file.o
file.c
In file included from file.c:26:
smb_debug.h:14:56: warning: nothing can be pasted after this token

---

-boundary=2 -march=i686-c -o pci-pc.o pci-pc.c
{standard input}: Assembler messages:
{standard input}:802: Warning: indirect lcall without `*'
{standard input}:887: Warning: indirect lcall without `*'
{standard input}:973: Warning: indirect lcall without `*'
{standard input}:1011: Warning: indirect lcall without `*'
{standard input}:1043: Warning: indirect lcall without `*'
{standard input}:1075: Warning: indirect lcall without `*'
{standard input}:1106: Warning: indirect lcall without `*'
{standard input}:1135: Warning: indirect lcall without `*'
{standard input}:1164: Warning: indirect lcall without `*'
{standard input}:1451: Warning: indirect lcall without `*'
{standard input}:1547: Warning: indirect lcall without `*'


There! It still compiled alright and life moves on

Frank :) Merry Christmas

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



test13-pre4... udf problem with dvd access vs test12

2000-12-25 Thread Frank Jacobberger

Odd happening here. Been running good as gold through test12 with
accessing my dvd to using oms. Now updating to test13-pre4
I get a complete lock up of my whole system when executing oms.

I can access the drive via mounting it... with no trouble what ever.

Here is a snip from my message file No clue what to test for here...

Perhaps udf.c is the problem?

Any ideas?

Merry Christmas

Frank





Dec 25 02:02:13 f1j kernel: hdf: packet command error: status=0x51 {
DriveReady SeekComplete Error }
Dec 25 02:02:13 f1j kernel: hdf: packet command error: error=0x00
Dec 25 02:02:13 f1j kernel: ATAPI device hdf:
Dec 25 02:02:13 f1j kernel:   Error: No sense data -- (Sense key=0x00)
Dec 25 02:02:13 f1j kernel:   No additional sense information --
(asc=0x00, ascq=0x00)
Dec 25 02:02:13 f1j kernel:   The failed "Report Key" packet command
was:
Dec 25 02:02:13 f1j kernel:   "a4 00 00 00 00 00 00 00 00 0c c4 00 "
Dec 25 02:02:14 f1j kernel: hdf: command error: status=0x51 { DriveReady
SeekComplete Error }
Dec 25 02:02:14 f1j kernel: hdf: command error: error=0x50
Dec 25 02:02:14 f1j kernel: end_request: I/O error, dev 21:40 (hdf),
sector 1148
Dec 25 02:02:14 f1j kernel: ATAPI device hdf:
Dec 25 02:02:14 f1j kernel:   Error: Illegal request -- (Sense key=0x05)

Dec 25 02:02:14 f1j kernel:   Read of scrambled sector without
authentication -- (asc=0x6f, ascq=0x03)
Dec 25 02:02:14 f1j kernel: hdf: command error: status=0x51 { DriveReady
SeekComplete Error }
Dec 25 02:02:14 f1j kernel: hdf: command error: error=0x50
Dec 25 02:02:14 f1j kernel: ATAPI device hdf:
Dec 25 02:02:14 f1j kernel:   Error: Illegal request -- (Sense key=0x05)

Dec 25 02:02:14 f1j kernel:   Read of scrambled sector without
authentication -- (asc=0x6f, ascq=0x03)
Dec 25 02:02:14 f1j kernel: hdf: command error: status=0x51 { DriveReady
SeekComplete Error }
Dec 25 02:02:14 f1j kernel: hdf: command error: error=0x50
Dec 25 02:02:14 f1j kernel: end_request: I/O error, dev 21:40 (hdf),
sector 1152
Dec 25 02:02:14 f1j kernel: ATAPI device hdf:
Dec 25 02:02:14 f1j kernel:   Error: Illegal request -- (Sense key=0x05)

Dec 25 02:02:14 f1j kernel:   Read of scrambled sector without
authentication -- (asc=0x6f, ascq=0x03)
Dec 25 02:02:14 f1j kernel: hdf: command error: status=0x51 { DriveReady
SeekComplete Error }
Dec 25 02:02:14 f1j kernel: hdf: command error: error=0x50
Dec 25 02:02:14 f1j kernel: end_request: I/O error, dev 21:40 (hdf),
sector 1153
Dec 25 02:02:14 f1j kernel: ATAPI device hdf:
Dec 25 02:02:14 f1j kernel:   Error: Illegal request -- (Sense key=0x05)

Dec 25 02:02:14 f1j kernel:   Read of scrambled sector without
authentication -- (asc=0x6f, ascq=0x03)
Dec 25 02:02:14 f1j kernel: hdf: command error: status=0x51 { DriveReady
SeekComplete Error }
Dec 25 02:02:14 f1j kernel: hdf: command error: error=0x50
Dec 25 02:02:14 f1j kernel: end_request: I/O error, dev 21:40 (hdf),
sector 1154
Dec 25 02:02:14 f1j kernel: ATAPI device hdf:
Dec 25 02:02:14 f1j kernel:   Error: Illegal request -- (Sense key=0x05)

Dec 25 02:02:14 f1j kernel:   Read of scrambled sector without
authentication -- (asc=0x6f, ascq=0x03)
Dec 25 02:02:14 f1j kernel: hdf: command error: status=0x51 { DriveReady
SeekComplete Error }
Dec 25 02:02:14 f1j kernel: hdf: command error: error=0x50
Dec 25 02:02:14 f1j kernel: end_request: I/O error, dev 21:40 (hdf),
sector 1155
Dec 25 02:02:14 f1j kernel: ATAPI device hdf:
Dec 25 02:02:14 f1j kernel:   Error: Illegal request -- (Sense key=0x05)

Dec 25 02:02:14 f1j kernel:   Read of scrambled sector without
authentication -- (asc=0x6f, ascq=0x03)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



test13-pre5 + char-major-145??

2000-12-29 Thread Frank Jacobberger

Please help me explain why I'm getting the following
modprobe reply on boot up after kernel test13-pre5
loads:

modprobe: Can't locate module char-major-145

>From /usr/src/linux/Documentation/devices.txt

10 charNon-serial mice, misc features
145 = /dev/hfmodem  Soundcard shortwave modem control {2.6}

My modules.conf:
---
alias eth0 rtl8139
alias eth1 rtl8139
alias parport_lowlevel parport_pc
alias sound-slot-0 emu10k1
alias usb-controller usb-uhci
---

What may be calling this? Any advice where to go ferreting?

Thanks,

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



test13-pre6 weird with tdfx.o

2000-12-30 Thread Frank Jacobberger

This is a first for tdfx.o not loading with XFree 4.01.

All prior kernel build through test13-pre5 would load just fine...

Strange...

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



modutils 2.3.23 fails with tdfx.o with test13-pre6

2000-12-30 Thread Frank Jacobberger

I can't get the latest modutils to work with loading
tdfx.o... Even went to the directory where tdfx.o resides
and did a insmod -S tdfx.o and got the following :

BTW - test13-pre6 here

tdfx.o: unresolved symbol remap_page_range
tdfx.o: unresolved symbol __wake_up
tdfx.o: unresolved symbol mtrr_add
tdfx.o: unresolved symbol __generic_copy_from_user
tdfx.o: unresolved symbol schedule
tdfx.o: unresolved symbol kmalloc
tdfx.o: unresolved symbol si_meminfo
tdfx.o: unresolved symbol create_proc_entry
tdfx.o: unresolved symbol inter_module_put
tdfx.o: unresolved symbol __get_free_pages
tdfx.o: unresolved symbol boot_cpu_data
tdfx.o: unresolved symbol inter_module_get
tdfx.o: unresolved symbol remove_wait_queue
tdfx.o: unresolved symbol high_memory
tdfx.o: unresolved symbol iounmap
tdfx.o: unresolved symbol free_pages
tdfx.o: unresolved symbol __ioremap
tdfx.o: unresolved symbol del_timer
tdfx.o: unresolved symbol interruptible_sleep_on
tdfx.o: unresolved symbol __pollwait
tdfx.o: unresolved symbol kfree
tdfx.o: unresolved symbol remove_proc_entry
tdfx.o: unresolved symbol pci_find_slot
tdfx.o: unresolved symbol kill_fasync
tdfx.o: unresolved symbol fasync_helper
tdfx.o: unresolved symbol add_wait_queue
tdfx.o: unresolved symbol do_mmap_pgoff
tdfx.o: unresolved symbol mem_map
tdfx.o: unresolved symbol sprintf
tdfx.o: unresolved symbol jiffies
tdfx.o: unresolved symbol printk
tdfx.o: unresolved symbol add_timer
tdfx.o: unresolved symbol __generic_copy_to_user

So what gives here?

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: test13-pre6 weird with tdfx.o

2000-12-30 Thread Frank Jacobberger

J Sloan wrote:

> Frank Jacobberger wrote:
>
> > This is a first for tdfx.o not loading with XFree 4.01.
> >
> > All prior kernel build through test13-pre5 would load just fine...
> >
> > Strange...
>
> Very strange - others on this list, self included,
> have reported something a bit different:
>
> tdfx.o has not loaded in any kernel since -test12.
>
> The makefile changes have broken it.
>
> Are you certain tdfx.o loads for you in prior -test13
> versions? If so, that would be a most disturbing
> development...
>
> jjs

Yes your right... I just haven't noticed... Why doesn't someone fix it?

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: tdfx.o and -test13

2000-12-30 Thread Frank Jacobberger

Alan Cox wrote:

> > >  +#include 
> > >   #include 
> > >   #include 
> > >   #include 
> >
> > I just want to confirm that this small fix solves my drm
> > problems as well - currently running -test13-pre7
> >
> > Er, has anybody sent a patch to the maintainers?
>
> Wrong patch. Modversions.h should be getting automatically included. That
> is what needs fixing. You've nicely located the problem and fixed the symptoms
> for the module versioned case

This "patch" apparently has been around since test13-pre1. I guess the
maintainers are on vacation.

Frank


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: tdfx.o and -test13

2000-12-31 Thread Frank Jacobberger

Tony Hoyle wrote:

> Alan Cox wrote:
> >
> > I see modversions.h being included properly on the command line
>
> Me too..
>
> make[3]: Entering directory `/usr/src/linux/drivers/char/drm'
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -fno-strict-aliasing -pipe
> -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include
> /usr/src/linux/include/linux/modversions.h   -c -o agpsupport.o
> agpsupport.c
> In file included from agpsupport.c:1:
> /usr/src/linux/include/linux/modversions.h:3: warning: ignoring pragma:
> "Modversions included
>
> Modversions *is* being included... putting a message into the header
> file shows it to be correctly included at compile time.  However by the
> time the C file is processed it the symbols it has defined appear to no
> longer exist.  When you put the patch into drmP.h it never re-includes
> modversions (the pragma is not hit, because _LINUX_MODVERSIONS_H is
> already defined) *but* the macros within it suddenly become active.
>
> I'm confused!
>
> Preprocessor bug?  Demon possessed compiler?

No, the pre-y2k+1 bug of course.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: Happy new year^H^H^H^Hkernel..

2001-01-01 Thread Frank Jacobberger

Linus Torvalds wrote:

> On 1 Jan 2001, Adam Sampson wrote:
> >
> > It appears to work (even with the reiserfs patch with the obvious
> > Makefile tweak), but the drm modules have unresolved symbols:
>
> Does this fix it for you (do a "make clean" before re-building your tree)?
>
> Linus
>
> 
> --- v2.4.0-prerelease/linux/drivers/char/drm/Makefile   Mon Jan  1 09:38:35 2001
> +++ linux/drivers/char/drm/Makefile Mon Jan  1 09:38:04 2001
> @@ -44,22 +44,22 @@
>  mga-objs   := mga_drv.o   mga_dma.o mga_context.o  mga_bufs.o  mga_state.o
>  i810-objs  := i810_drv.o  i810_dma.oi810_context.o i810_bufs.o
>
> -obj-$(CONFIG_DRM_GAMMA) += gamma.o
> -obj-$(CONFIG_DRM_TDFX)  += tdfx.o
> -obj-$(CONFIG_DRM_R128)  += r128.o
> -obj-$(CONFIG_DRM_FFB)   += ffb.o
> -obj-$(CONFIG_DRM_MGA)   += mga.o
> -obj-$(CONFIG_DRM_I810)  += i810.o
> -
> -
>  # When linking into the kernel, link the library just once.
>  # If making modules, we include the library into each module
>
>  ifdef MAKING_MODULES
>lib = drmlib.a
>  else
> -  obj-y += drmlib.a
> +  extra-obj = drmlib.a
>  endif
> +
> +obj-$(CONFIG_DRM_GAMMA) += gamma.o $(extra-obj)
> +obj-$(CONFIG_DRM_TDFX)  += tdfx.o $(extra-obj)
> +obj-$(CONFIG_DRM_R128)  += r128.o $(extra-obj)
> +obj-$(CONFIG_DRM_FFB)   += ffb.o $(extra-obj)
> +obj-$(CONFIG_DRM_MGA)   += mga.o $(extra-obj)
> +obj-$(CONFIG_DRM_I810)  += i810.o $(extra-obj)
> +
>
>  include $(TOPDIR)/Rules.make

Works like a charm here fix added drmlib.a with tdfx.o to
/lib/modules/2.4.0-prerelease/kernel/drivers/char/drm


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



2.4.3-pre8 problem with 8139too - failure to load

2001-03-26 Thread Frank Jacobberger

Something has changed regarding the 8139too driver in pre8.

I worked on it all morning long trying to resolve why the sucker
failed to load. There are new configuration options that need to
be addressed. As you recall there were zippo options in the pre7.

There are now:

RealTek RTL-8139 PCI Fast Ethernet Adapter support  [M]  
  Use PIO instead of MMIO   
  [*]
  Support for automatic channel equalization (EXPERIMENTAL)   [ ]
  Support for older RTL-8129/8130 boards[*]

Doing any combination of the above netted no positive result here.

I have run every kernel patch since 2.4.0 blah and
have never seen this driver fail to load or perform to some degree.

Trying to do insmod 8139too.o from the :
/lib/modules/2.4.3-pre8/kernel/drivers/net directory show these
unresolved symbols:

8139too.o: unresolved symbol alloc_etherdev
8139too.o: unresolved symbol unregister_netdev
8139too.o: unresolved symbol register_netdev

Maybe Jeff can shed more light on these changes

Thanks,

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



8139too and 2.4.5-pre3

2001-05-17 Thread Frank Jacobberger

Jeff Garzik:

On kernel boot from messages I'm getting a different report from my 
RealTek 8139:

May 17 06:33:32 f1j kernel: eth0: RealTek RTL8139 Fast Ethernet at 
0xd0862000, 00:50:ba:d8:2c:35, IRQ 5
May 17 06:33:32 f1j kernel: eth0: media is unconnected, link down, or 
incompatible connection

Used to report on the second line: "half duplex or full duplex mode 
detected"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/