intent of my deceased
client.
If you accept please forward your full names, current address and
your
direct cell for the court documentations and so that we can
obtain the
probate division of court papers required for you to claim the
funds
from the holding bank.
Thanks,
Steven Walter
intent of my deceased
client.
If you accept please forward your full names, current address and
your
direct cell for the court documentations and so that we can
obtain the
probate division of court papers required for you to claim the
funds
from the holding bank.
Thanks,
Steven Walter
intent of my deceased
client.
If you accept please forward your full names, current address and
your
direct cell for the court documentations and so that we can
obtain the
probate division of court papers required for you to claim the
funds
from the holding bank.
Thanks,
Steven Walter
intent of my deceased
client.
If you accept please forward your full names, current address and
your
direct cell for the court documentations and so that we can
obtain the
probate division of court papers required for you to claim the
funds
from the holding bank.
Thanks,
Steven Walter
On Thu, Nov 20, 2014 at 10:51 AM, Steven Walter wrote:
>> > I think Marcel was after just providing a clarifying code comment in
>> > both places - having two branches of an if-statement doing exactly the
>> > same thing looks a bit weird to me. To make thins comple
The bluetooth spec states that automatically flushable packets may not
be sent over a LE-U link.
Signed-off-by: Steven Walter
---
net/bluetooth/l2cap_core.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
The bluetooth spec states that automatically flushable packets may not
be sent over a LE-U link.
Signed-off-by: Steven Walter
---
net/bluetooth/l2cap_core.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
index
The bluetooth spec states that automatically flushable packets may not
be sent to a LE-only controller. The code already supports
non-automatically-flushable packets, but uses a bit in the controller
feature field to determine whether to use them. That bit is always zero
for LE-only devices, so w
case VIDIOC_G_CTRL:
+ case VIDIOC_S_CTRL:
case VIDIOC_S_CTRL32:
+ case VIDIOC_S_FREQUENCY:
+ case VIDIOC_G_FREQUENCY:
case VIDIOC_QUERYCTRL:
case VIDIOC_G_INPUT32:
case VIDIOC_S_INPUT32:
--
1.5.3.rc2
--
-Steven Walter <[EMAIL PROTECTED]>
&qu
This patch adds a board definition for the Encore ENL-TV card, and
adds its PCI subdevice to the ID table. Patch is output from
git-format-patch against Linus' git tree.
Please let me know if there are any deficiencies in this submission.
--
-Steven Walter <[EMAIL PROTECTE
On Thu, Jul 19, 2001 at 03:24:09PM -0400, Ryan C. Bonham wrote:
> I get the following messages, I will paste dmesg.log at the bottom if you
> want to see it..
> mtrr: your CPUs had inconsistent fixed MTRR settings
> mtrr: probably your BIOS does not setup all CPUs
>
>From what i gather that messa
Great, glad to here it. Who (if anyone) is still attempting to unravel
the puzzle of the Via southbridge bug? You, Andy, should try and get in
touch with them and help debug this thing, if you're up to it.
On Mon, Jun 25, 2001 at 01:17:57AM -0500, Andy Ward wrote:
> Well, I have tried your sugg
On Mon, Jun 25, 2001 at 12:30:02AM +0200, J . A . Magallon wrote:
> Take a programmer comming from other system to linux. If he wants multi-
> threading and protable code, he will choose pthreads. And you say to him:
> do it with 'clone', it is better. Answer: non protable. Again: do it
> with for
On Sun, Jun 24, 2001 at 01:51:09PM -0500, Daniel Fraley wrote:
> Hi, everyone.. I'm borrowing my roommate's email, so please send replies to
> [EMAIL PROTECTED] Thanks!
>
> Here's my problem... when I boot anything 2.4, I get several oopsen in a
> row, all of which are either (most commonly) k
I too have been experiencing this on a gateway for a DSL modem. The
backtrace is almost exactly the same. On this machine, the bug results
in an "Aieee: Killing Interrupt Handler". I have to manually copy the
oops, and as such I copied only the backtrace, and parts of it may be
incorrect. I'v
On Tue, Jun 19, 2001 at 04:55:10PM -0400, Tom Diehl wrote:
> What is the best way to install the modules? Is there a directory _all_ of
> the modules exist in b4 you do "make modules_install". I usually end up
> setting EXTRAVERSION to something unique and doing a make modules_install.
> That way
It does appear that the documentation regarding this is out of date.
However, you can still install modules to a given location by:
INSTALL_MOD_PATH="/path/to/modules" make modules_install
Had to dig through the Makefile for that, though it may actually be
documented somewhere.
On Mon, Jun 18,
Probably what happens is that your BIOS stores some data in the top
megabyte of RAM, but doesn't set up the memory map to reflect this.
Therefore, Linux overwrites whatevers up there, causing problems.
On Sun, Jun 17, 2001 at 09:26:50PM +0200, Ronald Bultje wrote:
> P6b has three mem-slots. I wou
On Sat, Jun 16, 2001 at 02:59:34PM -0500, Josh Myer wrote:
> It might be better to add a default case to the switch statement below, so
> this symbol doesn't just eat up another 4(8 on some platforms, and i'm
> sure others) bytes of memory unneccesarily.
I'm not quite sure I follow you. The defa
This patch is obviously correct. It doesn't appear that tdfxfb has a
maintainer, so I'm sending this patch to the list. Nothing
earth-shattering, it just removes a warning during build.
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-
What kernel are you using?? I used to get it after I switced from a
Linux-supported winmodem to a hardware modem, but the messages are now
mysteriously absent from me logs. If you're running something prior to
2.4.5, I'd say it was fixed there. Also, it could've been fixed in
Alan's tree; I'm r
Here's a patch I wrote to allow ftape to compile against 2.4.something.
It still works with 2.4.5. I'm not sure if it works entirely (it seems
to), but it compiles and seems to work. Enjoy!
On Thu, Jun 07, 2001 at 05:12:31PM +0200, Friedrich Lobenstock wrote:
> Hi!
>
> As the linux-ftape maili
Just got this oops in 2.4.5-ac2. Can't reproduce it as of yet; if I
find a way, I'll give notice.
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
ksymoops 2.3.4 on i586 2.4.5-ac2. Options used
-V (default)
-
On Mon, May 21, 2001 at 08:16:18AM -0700, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:"Martin.Knoblauch" <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> >
> > Hi,
> >
> > while trying to enhance a small hardware inventory script, I found that
> > cpuinfo is m
On Sat, May 19, 2001 at 09:38:03PM +0200, Erik Mouw wrote:
> > But /dev/sda/offset=234234,limit=626737537 isn't a file! ls it and see
> > if it's there. writing to files that aren't shown in directory listings
> > is plain evil. I really don't want to explain why. It's extremely
> > messy and unin
Just a "me, too" here. I see this when using the in-kernel driver. I'm
now using... 4.12, I think. At any rate, the error doesn't occur, or at
least occurs to rarely as to escape notice, with this driver. Might I
suggest the kernel's version be upgraded? The updated driver was posted
here on
On Sun, Apr 29, 2001 at 04:52:15PM +0200, root wrote:
> Steven Walter wrote:
>
> > I'm running esound 0.2.17 from Debian 2.2. Can someone who's having no
> > problems with sound on 2.4.4 give a little info about their setup?
>
> esd works for me with any 2
On Sun, Apr 29, 2001 at 03:16:24PM +0100, Lee Mitchell wrote:
> >
> > It would appear that something in the kernel broke esd.
> >
>
> I can confirm that on my system also, the problem only appears when using
> esd for output.
There must be some for whom esd/sound is still working, or else I'd
ex
I'm also seeing what would appear to be exactly this.
The problem, for me, doesn't occur when I write directly to /dev/dsp
(i.e., use the OSS output plugin for xmms). The problem only occurs
with esd.
It would appear that something in the kernel broke esd.
On Sat, Apr 28, 2001 at 10:50:01AM +0
Just a heads up: works great for me
On Thu, Apr 26, 2001 at 07:51:08AM -0400, Jeff Garzik wrote:
> The attached patch, against 2.4.4-pre7, cleans up the huge pci_board
> list in serial.c to remove PCI id information. In the process, it (a)
> demonstrates more complex new-style PCI probing, and
This patch modifies serial.c to detect the ActionTec PCI modem. This
particular device has a class of PCI_CLASS_COMMUNICATION_OTHER, so it
isn't detected by the current catch-all rule that detects devices of
"PCI_CLASS_COMMUNICATION_SERIAL".
Patch is against kernel 2.4.3. Tested to compiled and
On Tue, Apr 24, 2001 at 05:18:36PM -0400, Brian Gerst wrote:
> Steven Walter wrote:
> >
> > This patch allows the serial driver to properly detect and set up the
> > ActionTec PCI modem. This modem has a PCI class of COMMUNICATION_OTHER,
> > which is why this mode
This patch allows the serial driver to properly detect and set up the
ActionTec PCI modem. This modem has a PCI class of COMMUNICATION_OTHER,
which is why this modem is not otherwise detected.
Any suggestions on the patch are welcome. Thanks
--
-Steven
In a time of universal deceit, telling th
It would seem that I have a modem (hardware based, not winmodem) of
PCI_CLASS_COMMUNICATION_OTHER. This, unfortunately, prevents it from
being automagically detected by the serial driver, which only looks for
devices of PCI_CLASS_COMMUNICATION_SERIAL.
I've fixed this here merely by adding an ent
On Sun, Apr 22, 2001 at 01:53:59PM +0200, [EMAIL PROTECTED] wrote:
> Hi!
>
> why doesnt the dma for ide disks show up in /proc/dma?
>
> heineken:~# hdparm -d /dev/discs/disc0/disc
> /dev/discs/disc0/disc:
> using_dma= 1 (on)
>
> heineken:~# cat /proc/dma
> 4: cascade
I suspect this is
On Wed, Apr 11, 2001 at 04:50:21PM -0400, Jeff Garzik wrote:
> Steven Walter wrote:
> >
> > When I try to start "agetty" on my serial line, agetty hangs in an
> > ioctl; according to strace, this ioctl is "SNDCTL_TMR_STOP". This
> > doesn't
When I try to start "agetty" on my serial line, agetty hangs in an
ioctl; according to strace, this ioctl is "SNDCTL_TMR_STOP". This
doesn't sound right, but that ioctl is defined as _IO('T', 3) if that
makes any more sense.
The reason that this must be a kernel bug is because agetty works
flawl
Earlier today, I tried to unlock xscreensaver on my desktop. After
typing in the password, it said "Checking..." and then hung. In
response, I hit Ctrl+Alt+Bksp, which killed X. However, gdm did not
restart X. I tried logging in on the console, but none of them were
responsive; characters woul
Right after a boot, I got 5 oopsen within about 8 minutes. There are
only two unique ones, which are attached. Each one occured at least
twice. Someone know what's going on?
--
-Steven
Freedom is the freedom to say that two plus two equals four.
ksymoops 2.3.4 on i586 2.4.3. Options used
I'm getting some interesting behavior with the 2.4.3 serial driver and
agetty.
This system uses the onboard serial port (ttyS0) for a serial console
(console=ttyS0,38400) along with the VGA port. If I try to start an
agetty on this line (agetty -L ttyS0 38400), it gets as far as
outputting "Debi
On Wed, Apr 04, 2001 at 04:52:32PM -0300, Sarda?ons, Eliel wrote:
> switch (prev->state) {
> case TASK_INTERRUPTIBLE:
> if (signal_pending(prev)) {
> prev->state = TASK_RUNNING;
> break;
>
On Mon, Apr 02, 2001 at 06:26:45AM +0100, Richard Russon wrote:
> On 01 Apr 2001 18:21:29 -0500, Jeff Garzik wrote:
> > Let's hope it's not a flamewar, but here goes :)
> >
> > We -need- .config, but /proc/config seems like pure bloat.
>
> Don't ask me for sample code, but...
>
> The init code
On Tue, Mar 27, 2001 at 01:42:39PM +0200, Thomas Pfaff wrote:
> Hi all,
>
> i decided to make a test for the 2.4 kernel on my old hardware (Gigabyte
> EISA/VLB with an AMD 486 DX4 133). The kernel boots fine but there is one
> strange thing: The system clock slows down under load, after a make
>
On Tue, Mar 27, 2001 at 06:05:05PM +1000, Keith Owens wrote:
> On Mon, 26 Mar 2001 23:16:27 -0600,
> Steven Walter <[EMAIL PROTECTED]> wrote:
> >This has happened twice, now, though I don't believe its completely
> >reproduceable. What happens is an Oops, which dro
This has happened twice, now, though I don't believe its completely
reproduceable. What happens is an Oops, which drops me into kdb. I've
been in X both times, however, which makes kdb rather useless. I
blindly type "go", and interrupts get reenabled, at least (I know
because my mp3 stops loopi
I'm having a similar problem with the onboard network card of a Sony
Vaio Laptop. I haven't tracked it down as far as you can; how can I
confirm its the same problem as yours?
On Fri, Mar 23, 2001 at 09:34:36AM -0800, Jun Sun wrote:
> christophe barbe wrote:
> >
> > Which kernel are you using.
Got the following oops while starting quake2 (one time) and running
mpg123 (another time). It seems pretty reproduceable. Kernel version
2.4.2-ac17, motherboard is a i810 chipset eMachines
Caveat emptor, this was typed by hand, but the two oopsen, after being
entered, where identical, so unless
I'm getting some interesting behavior while writing an ip_conntrack
helper module. The primary problem is if I specify a destination port
for the struct ip_conntrack_helper, my help routine is never called.
If I specify a source port, rather than a destination port, the routine
gets called for th
On Mon, Mar 12, 2001 at 08:50:23AM +0100, Martin Diehl wrote:
>
> On Sun, 11 Mar 2001, Steven Walter wrote:
> > I have this exact same chip on my board (a PCChips M599-LMR or something
> > like that) which works flawlessly on 2.4.2, even with UDMA66.
>
> Do you have CO
On Sun, Mar 11, 2001 at 10:03:48PM +0100, Martin Diehl wrote:
> On Fri, 9 Mar 2001, Lawrence MacIntyre wrote:
>
> > Uniform MultiPlatform E-IDE driver Revision 6.31
> > ide: assuminmg 33 MHz system bus speed for PIO modes: override with
> > idebus=xx
> > SIS5513: IDE controller on PCI bus 00 dev
After upgrading to 2.4.2, gcd or any audio CD player will work. The
attached chunk of dmesg is the messages produced by attempting to play
them. The player just loops through all tracks, playing nothing.
Ripping CD's a la cdparanoia still works.
If its any consequence, my CD-ROM is now detected
This message pops up in my logs countless times, often accompanied by
temporarily freezes of the system, and pops in the sound. It seems to
occur more often when under load, i.e. playing a DVD. In fact, they
degrade the performance so badly as to make DVDs unwatchable.
I would chock this up to
Problem in a nutshell: The module for my soundcard (cs4232.o) won't
load until after a "cat /proc/isapnp" has been run. I'm guessing
(though not sure) that this isn't the intended behavior. ISAPnP is
compiled into the kernel, and detects the card correctly during boot, as
evidenced by the boot
Ok, this sounds weird, and it is. After running 2.4.0 for... 1 day, 18
hours straight, I've run into some strange behavior. Most noticeable is
that, whem playing sounds, XMMS squeaks. However, the squeaks show up
on the graphic equalizer, which means to me that it is getting bad math
results.
While playing mp3's on XMMS, I get squeaks at random intervals. It
seems to correlate slightly with disk usage, but other than that it
seems random. These squeaks did not occur with 2.4.0-prerelease, and no
changes to the cmpci driver have occurred between -prerelease and
-final. Was there an i
On Fri, Jan 05, 2001 at 11:31:23AM -0500, Chris Kloiber wrote:
>
> Possibly related symptoms:
>
> kernel 2.4.0-ac1 compiled with gcc version 2.96 2731 (Red Hat Linux
> 7.0)
>
> last 2 lines in dmesg output:
> mtrr: 0xd800,0x200 overlaps existing 0xd800,0x100
> mtrr: 0xd8
On Wed, Jan 03, 2001 at 04:54:38PM -0500, Alexander Viro wrote:
> On Wed, 3 Jan 2001, Dan Aloni wrote:
>
> > It is known that most remote exploits use the fact that stacks are
> > executable (in i386, at least).
> >
> > On Linux, they use INT 80 system calls to execute functions in the kernel
>
On Wed, Jan 03, 2001 at 03:10:39PM -0600, Jim Studt wrote:
> The sis5513 has for quite a while had fatal problems with udma on some
> machines. (At least the thelinuxstore PIAs with the P6SET-ML
> motherboard, I have heard other people with the same problem).
>
> The sis5513 driver deliberatly o
This oops occurred just a few minutes ago under no particular load.
There were actually two oopsen, but I've included only the first as I've
heard that successive oops really aren't helpful. Nonetheless, if
anyone's interested in seeing it, I have it captured.
These oops were processed by
On Tue, Jan 02, 2001 at 09:45:03AM -0500, dep wrote:
> if it has anything to do with this, then it's reduced but not gone:
>
> Jan 2 09:42:35 depoffice kernel: hda: dma_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Jan 2 09:42:35 depoffice kernel: hda: dma_intr: error=0x84 {
> Drive
This oops occurred while I was on the internet. modemlights_applet, the
process that caused the oops, died, and upon being restarted, is hung in
the "D" state. kill -9 won't even rid me of it. The internet
connection is still alive, though, as I can ping sites. The system is
an AMD-K6/2, the k
On Sun, Dec 10, 2000 at 06:20:31PM +, David Wragg wrote:
> If I understood why the MTRR driver was doing something on the K6-2,
> then model-specific differences might make some sense. But currently,
> I don't see why there would be any difference between "MTRR disabled"
> and "MTRR enabled,
On Sun, Dec 10, 2000 at 01:35:26AM -0500, Victor J. Orlikowski wrote:
> Steven,
>
> One question:
> Do you have MTRR enabled?
> If so, a temporary workaround is to re-compile the kernel with
> it disabled.
To confirm, yes, I do have MTRR's enabled. I'll see if that fixes it...
Several times now, at seemingly random intervals, my computer has frozen
solid. The computer was not under high load--XMMS playing and my typing
an email in mutt. X was frozen, the soundcard played the same sound
repeatedly, and ctrl+alt+del did nothing. SysRq, however, caused the
computer to r
On Sun, Nov 19, 2000 at 08:20:33PM +0100, Martin Mares wrote:
> > During boot, I get the message:
> >
> > PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
> > using pci=biosirq.
>
> Can you send me 'lspci -vvx' output, please?
>
Here you go:
00:00.0 Host bridge: Silicon Int
During boot, I get the message:
PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
using pci=biosirq.
If I boot with pci=biosirq, as the error message suggests, I get the
same error, save the part about trying with pci=biosirq. This is with
version 2.4.0-test11-pre7 and as far
If my understanding is correct, you need to include version.h without
"#define __NO_VERSION__" in one and only one of your module's .c files.
More than one, and you get redefinition errors; less than one, and its
undefined.
On Tue, Nov 14, 2000 at 03:58:38PM -0600, Timur Tabi wrote:
> I'm at a lo
> Check your logs and see if their is a speed setting
> block issued, only if
> you are using patched 2.2x or 2.4.0x kernels will
> this report be
> generated.
I haven't been able to recover anything from the root
fs as of yet. If I do; I will check the logs.
> > Before, on a 40-conductor cable
Recently, when trying to use UDMA/66 on my SiS 530 and
WD84AA, I got some data corruption. At first, I tried
with "UDMA Enabled" set to off in the BIOS, because I
had known this to previously cause problems. However,
like this, I couldn't set the harddrive to use UDMA
mode4 (-X68). I would set
Casually browsing through my system logs, I came upon this two oopses
that happened together (logged as same second). I don't really remember
what situation was surrounding, or even if any interruption was
experienced. The system did totally freeze just under 30 minutes later,
however, with no
I posted a few days ago reporting that under normal load on 2.2.17final
would crash under non-strenuous loads. One of the symptoms I reported
was that the system speaker would beep. In fact, the beeps are coming
from the speakers. My soundcard is a CM8738, and so uses the cmpci
driver. Perhap
On Thu, Sep 14, 2000 at 10:56:20AM +0100, Alan Cox wrote:
> > Twice now I have experienced this crash, but I do not know how to
> > replicate it. The system was under normal load (netscape, xmms, and few
> > other minor programs) First, xmms stopped playing. Then, the screen
> > went black and
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other insecure places, or upgrade your util-linux to a newer
version; I'm not sur
Is the same behavior exhibited in 2.2.x w/Andre's IDE
patch?
Dewet Diener <[EMAIL PROTECTED]> wrote:
> I am experiencing problems with UDMA on my system on
> 2.4 kernels. It's an
> ASUS socket-7 MB, over 2 years old. Below follows a
> boot log on
> 2.4.0-test7:
>
> ide: Assuming 33MHz system b
74 matches
Mail list logo
