Hi,
Ingo Oeser wrote:
The only thing that looks responsible for this is the FXSR stuff,
that changed.
Like to try again backing this out?
Just to make sure it wasn't a gcc thing, I've recompiled the original
setup with egcs-1.1.2 (previously had used 2.95.2) and that did not
fix a thing.
Linus Torvalds wrote:
Mind trying it with the "HAVE_FXSR" and "HAVE_XMM" macros in
linux/include/asm-i386/processor.h
fixed? They _should_ be just
#define HAVE_FXSR (cpu_has_fxsr)
#define HAVE_XMM(cpu_has_xmm)
That doesn't help either.
-Udo.
-
Andi Kleen wrote:
Did you have CONFIG_X86_FXSR or CONFIG_X86_RUNTIME_FXSR enabled when it
worked?
If not it probably means that the XServer is testing OSFXSR and the branch
that handles it doesn't work.
--- linux-2.4.0/.config Thu Jan 11 11:22:11 2001
+++ linux-2.4.1/.config Thu Jan 11
Alan Cox wrote:
2.4.0-ac6
o Fix athlon crash on boot with local apic/nmi(Ingo Molnar)
Still crashes here with -ac6 on my Athlon. I'll have to write down the
oops by hand later on or set up a serial console, but once that's done
I'll post the trace - unless someone already knows
"Udo A. Steinberg" wrote:
Alan Cox wrote:
2.4.0-ac6
o Fix athlon crash on boot with local apic/nmi(Ingo Molnar)
Still crashes here with -ac6 on my Athlon. I'll have to write down the
oops by hand later on or set up a serial console, but once that's done
I'll post
As previously reported by someone, there are occasional
problems when shutting down with unmounting partitions,
that are reported as busy for strange reasons.
Keith Owens said it was supposedly a Redhat shutdown
script issue and I since I'm not using Redhat, it's
most likely not that.
Upon
/dev/hdb1: Inode 522901, i_blocks is 64, should be 8. FIXED
Ok, culprit identified: /var/spool/lpd/lpd.lock
On another partition I had the same problem with httpd's
error_log.
Since both of those seem to be log- and lock-files, maybe
there's something wrong with file locking?
Anyway,
Alexander Viro wrote:
umount: none busy - remounted read-only
The "none" bit puzzles me the most. /etc/fstab and /etc/mtab
look perfectly ok.
Has anyone got an idea? Everything worked well with 2.4.0 and
Alan's tree up to -ac4, didn't try ac5, and ac6 is what messes
up now.
"Udo A. Steinberg" wrote:
The very strange stuff is umount at reboot:
umount: none busy - remounted read-only
umount: /: device is busy
Remounting root-filesystem read-only
mount: / is busy
Rebooting.
I just noticed another strange effect:
ps uxa misses a couple dozen
[EMAIL PROTECTED] wrote:
These days umount is done by directory, not by device,
since a device may be mounted multiple times, so
I expect the silly message is gone.
(Is your umount recent?)
[But this is only about the "none". I don't know what is
wrong in your situation.]
My umount is
Hello,
I've got a sendmail 8.1.11 process hanging in D state with 2.2.18.
ps -eo fname,tty,pid,stat,pcpu,nwchan,wchan reveals the following:
PID STAT %CPU WCHAN WIDE-WCHAN-COLUMN COMMAND
16176 D 0.0 1f4c28 down_failed sendmail: startup with ...
Is this likely a bug in the
Hello,
Below is a decoded oops from a standard 2.2.18 kernel.
If you need any additional info, please let me know.
Regards,
Udo.
ksymoops 2.3.5 on i686 2.2.18. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.18/ (default)
Sergey Kubushin wrote:
The older chips (e.g. 82557) work fine. The problem arises when you have the
newer 82559's. They do work, however, if the power management for eepro100
is enabled in kernel config. It definitely means that those chips are
underinitialized (or overinitialized :)) when
Christopher Neufeld wrote:
The only patch
which has to be applied to make Linux run stably on these systems is to
increase that limit. Would it be possible to bump it up to 128, or even
256, in later 2.4.* kernel releases? That would allow this customer to
work with an unpatched kernel,
Hi all,
With all the latest kernels (at least since 2.4.0-test12)
I have had occasional problems with a PS/2 keyboard when
switching back and forth between X and text consoles.
In most cases the problem occurs when switching from X to
a text console, which renders the keyboard totally
Hi,
Alan Cox wrote:
2.4.4-ac10
With 2.4.4-ac10 and binutils 2.11 I get the following warnings:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.4-ac/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686 -malign-functions=4
Gerhard Mack wrote:
Its what I would describe as lack of enforcement by trading standards bodies,
and I suspect what the US would call 'insufficient class action lawsuits'
What we need is a web page for listing crap hardware so less people buy
it.
Not just crap hardware, but also
Tim Waugh wrote:
The end of my inbox has turned to zeroes (everything from a few k off
the beginning to the end), while running test8-pre2. :-(
(I've restored it from backup, but I thought someone ought to know.)
Similar things happen on test7 as well - content of files being garbled
and
Hello,
I'm still experiencing ext2 corruption even with the newest patch
test8-pre5. I'm not using bugtraq, mutt or pine and I'm fairly sure
it's not caused by a badly written application or strange input.
Right now Linux oopsed and badly broke the whole FS.
Hopefully this will help tracking
Alexander Viro wrote:
Urgh. Look for BUG in syslog (right before the oops). AFAICS it should be
line 711, i.e.
if (!buffer_mapped(bh))
BUG();
Yes, I saw that.
I've applied the patch you posted and it appears to work well.
The same procedures that formerly broke it
Steffen Luitz wrote:
2.4.0-test8's kupdate just crashed with a BUG at ll_rw_blk.c:711 when I
was trying to save a file from StarOffice. The system is a Dual PII-300
(with SMP ...)
Al Viro posted a patch to fix this problem earlier today on this list.
Udo.
-
To unsubscribe from this list:
Jes Sorensen wrote:
Pavel Umount (and mount on next line too) report "/: device is busy"
Pavel and the root filesystem stay not correctly unmounted.
2.2.13 and gcc-2.95.2 are not compatible, try with the correct
compiler first.
Whatever the problem is, it's probably not a compiler
Linus Torvalds wrote:
VM balacing fixes, sound should work again, and a lot of small details.
Linus
- pre7:
- official Compaq CISS driver.
There's a little annoying bug with printing partitions upon bootup.
Specifically my dmesg now looks like:
Partition check:
[EMAIL PROTECTED] wrote:
8. Fix Exists But Isnt Merged
* 2.4.0-test8 has a BUG at ll_rw_blk:711. (Johnny Accot, Steffen
Luitz) (Al Viro has a patch)
Said patch has already been merged in the test9-pre and -final series
and the bug can be considered fixed.
-Udo.
-
To
Hi Linus Alexander
It seems that we were all wrong in assuming that ext2 was fixed
wrt. filesystem corruption. test10pre3 once again has the potential
to eat files (not sure about earlier versions).
I finally managed to capture an oops (by hand), so bear with me that
I didn't typo anywhere.
Alexander Viro wrote:
See another posting. More or less the same analysis. I don't see
where it came from and it smells funny - looks like a loss of -b_count
_or_ an active page returned by alloc_page() (to grow_buffers()). I
wouldn't exclude the latter, BTW, but then I'm still
Hi,
With -ac21 I'm getting occasional long delays in video output with xawtv
or the picture totally freezes until I click with the mouse in the xawtv
window. dmesg shows:
bttv0: PLL: 28636363 = 35468950 ... ok
bttv0: irq: OCERR risc_count=0fb54810
bttv0: irq: OCERR risc_count=0fb54810
bttv0:
Alan Cox wrote:
With -ac21 I'm getting occasional long delays in video output with xawtv
or the picture totally freezes until I click with the mouse in the xawtv
window. dmesg shows:
You have a VIA chipset ?
Yes. Via KT133.
lspci output under -ac20:
00:00.0 Host bridge: VIA
Andrey Savochkin wrote:
eth0: card reports no RX buffers.
eth0: card reports no resources.
It's a known issue.
I've been promised that this issue would be looked up in Intel's errata by
people who had the access to it, but I haven't got the results yet.
I just figured out something
Andrey Savochkin wrote:
I've updated eepro100 driver for 2.4 kernel branch.
So far, the most annoying initialization problem (expressing itself in "card
reports no resources" messages) hasn't been fixed.
Hi Andrey,
I've been using an older EEPro100/B card until now and it's been working
Ion Badulescu wrote:
Do you know if only one specific chip revision exhibits this problem? It
would really help track down the problem. If I remember correctly, 82557
doesn't have flow control at all, and 82558/9 have different
implementations -- one is proprietary (82558) and one is
Skip Collins wrote:
I have a 900MHz Athlon/Asus A7V mobo system with an onboard ata100
promise controller. I have only had problems when my ata100/udma5
harddrive is connected to the promise controller. Using the ATA66 ide
bus eliminates the problem. I typically see the corruption when
Hi,
Following the discussion in another thread where someone
reported fs corruption when enabling DMA with hdparm, I've
played around with hdparm and found that even the rather
harmless hdparm operations are capable of trashing an ext2
filesystem quite nicely.
hdparm version is 3.9
hdparm -tT
Hi,
Andre Hedrick wrote:
No way that this could cause corruption it is a read-only test.
As others pointed out, it's probably something related to shared
memory, but it's definitely hdparm that triggers it. I haven't
got the hdparm sources here to look at what exactly it's doing,
but there
Jan Niehusmann wrote:
The following patch actually prevents the corruption I described.
I'd like to hear from the people having problems with hdparm, if it helps
them, too.
Yes, it prevents the issue.
Please note that the patch circumvents the problem more than it fixes it.
The true
Ion Badulescu wrote:
The fact that apparently only the people using 82559 chips are seeing this
seems to confirm my analysis above.
If you could try the attached patch (and maybe pass it onto the other
people who are experiencing this problem), that would be great.
+ /*
Ion Badulescu wrote:
Ok. Can you send me the entire dump? Also, it would be helpful if you
could try to determine when exactly it happens (upon insmod, upon ifconfig
up, or upon receiving some packets later).
I have the eepro driver compiled into a monolithic kernel. After rebooting
a
Hi,
Anton Altaparmakov wrote:
Just to say that the patch (including added 4) fixed the "card reports no
resources" messages for me. - Looking at my logs the messages appeared once
every 10-40 minutes. - Now the box is up for more than 5 hours with the
patch and test12-pre7 and not a single
Ion Badulescu wrote:
This is an i82559 C-step. What kind of switch is it attached to?
It's a 3Com FDDI/Ethernet Linkswitch 2200 Rev 2.8
Also, if you feel like experimenting, edit speedo_interrupt() and change
outw(status 0xfc00, ioaddr + SCBStatus);
to
outw(status
Hi Linus,
The Makefile changes broke compiling drivers/media, such as bttv,
as kernel modules. Below is the patch against test13-pre3 to fix it.
Please apply.
-Udo.
--- /sources/linux/drivers/media/Makefile Thu Dec 21 08:17:17 2000
+++ /usr/src/linux/drivers/media/Makefile Thu
Hi all,
After enabling the option "EEPRO100_PM" and upgrading to test13-pre4
my problems with the eepro100 driver mysteriously ceased to exist.
I no longer see any "Card reports no RX buffers" or "Card reports no
resources" messages.
Since I don't think -pre4 changed anything from -pre3 that
Hi all,
When mounting a 700 MB CD-RW in my Plextor CD-ROM, my machine
reliably oopses. Below is the first oops decoded.
Can someone explain to me what all those ksymoops warnings are
about?
-Udo.
ksymoops 2.3.5 on i686 2.4.0-test13-pre4. Options used
-V (default)
-k /proc/ksyms
Hi Linus et. all
While under massive disk and cpu load, 2.4.0-prerelease produced
the following oops (decode see below)
Keith, I've read the FAQ about having been bitten by Makefile bugs
with certain symbols and such, yet I still get these symbol warnings
even after a mrproper rebuild. Any
Hi,
Linus Torvalds wrote:
The strange thing is that 0x0100 value, which almost certainly should
just be NULL. A one-bit error.
Now, I assume this machine has been historically stable, with no history
of memory corruption problems.. It's entirely possible (and likely) that
the
Dan Aloni wrote:
After a bit of few code reviewing, it looks like the only code that
assigns stuff to -d_op in a nonstandard way is in fs/vfat/namei.c.
Udo, are you using vfat?
Yes.
-Udo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Hi,
Alexander Viro wrote:
In principle, it might be that d_find_alias() is broken. I don't see where
it could happen, but then I'm half-asleep right now... While we are at it,
do you have
* autofs
Yes.
* knfsd
* ncpfs
No, neither of these two.
-Udo.
-
To
Hi,
I just got another oops with test10pre6. Decoded output follows.
Hopefully this helps to hunt a bug down.
-Udo
Unable to handle kernel NULL pointer dereference at virtual address 0010
c0130512
*pde =
Oops:
CPU:0
EIP:0010:[c0130512]
Using defaults from ksymoops
Vitali Lieder wrote:
Hallo.
Ich have test new NVdriver 0.95 with new kernel 2.4.0test10, but
have the output:
***unresolved symbols in /lib/modules/2.4.0-test10/video/NVdriver
Just add the following lines somewhere on top of nv.c and recompile
the nvidia module.
#define
Linus Torvalds wrote:
I sure as hell hope this isn't an Athlon issue. Can other people try
the test-program and see if we have a pattern (ie "it happens only on
Athlons", or "Linus is on drugs and it happens for everybody else").
I've tried both variants (fesetenv and inline-asm) with
Linus Torvalds wrote:
Compiler specific ?
There's almost certainly more than that. I'd love to have a report on my
asm-only version, but even so I suspect it also requires the 3dnow stuff,
because I'm not able to trigger anything like this on any machines I have
access to (none of them
Markus Schoder wrote:
My test program caused the exception (and the freeze)
unintendedly in the return statement since the
division was optimized away as Brian pointed out.
It's quite strange that I cannot seem to trigger the
problem here on my machine.
I know of another guy with the exact
Alan Cox wrote:
Just built 2.4.3-ac10 and got an oops when booting. It tries to detect
the CD and gives the oops.
I'm getting a similar oops with -ac10. I initially thought this might be
a result of switching to gcc-2.95.3, because -ac9 runs fine when built
with gcc-2.95.2, but if others
Hi all,
I have an USB hub built into my monitor (Eizo T761) which disconnects
and powers down the hub when the monitor gets switched off. After
switching it back on, a problem occurs with reenabling the ports on
that USB hub. The kernel output follows.
Comments anyone?
Regards,
Udo.
[Detect
Pete Zaitcev wrote:
switching it back on, a problem occurs with reenabling the ports on
that USB hub. The kernel output follows.
Comments anyone?
Next time, post your /proc/version.
I thought this was unnecessary in this case, because my mail headers
nicely reveal which version it
Hello,
Attached is the trace of an oops which seems to be caused by the
tvmixer code. Tvmixer is compiled monolithically into the kernel,
the rest of bttv is compiled as modules.
Kernel is 2.4.5-ac17, compiled with gcc-3.0.
Regards,
Udo.
ksymoops 2.4.1 on i686 2.4.5-ac17. Options used
Hi,
Gerd Knorr wrote:
On Mon, Jun 25, 2001 at 12:56:03PM +0200, Udo A. Steinberg wrote:
Attached is the trace of an oops which seems to be caused by the
tvmixer code. Tvmixer is compiled monolithically into the kernel,
the rest of bttv is compiled as modules.
Any hints on how
Gerd Knorr wrote:
On Mon, Jun 25, 2001 at 12:56:03PM +0200, Udo A. Steinberg wrote:
Hello,
Attached is the trace of an oops which seems to be caused by the
tvmixer code. Tvmixer is compiled monolithically into the kernel,
the rest of bttv is compiled as modules.
Any hints on how
Peter Horton wrote:
I've found the cause of silent disk corruption on my A7V motherboard,
and it might affect all boards with the same North bridge (KT133 etc).
For some reason the IDE controller(s) was sometimes picking up stale
data during bus master DMA to the drive. Assuming that
Peter Horton wrote:
The patch doesn't work for me. Maybe I need to disable some more of
those North bridge features :-(
Oh bum. Back to testing with "normal" ...
FWIW, here's the output of my lspci for A7V with working 1003 BIOS
and still no corruption (after 2 hours stresstest).
00:00.0
"Udo A. Steinberg" wrote:
FWIW, here's the output of my lspci for A7V with working 1003 BIOS
and still no corruption (after 2 hours stresstest).
Bugger, forgot the end bit. Here's it again:
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
Subsyste
Petr Vandrovec wrote:
On 5 Feb 01 at 23:08, Udo A. Steinberg wrote:
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 8033
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr
Dale Farnsworth wrote:
However, if I enable the BIOS parameter "I/O Recovery Time", I can still
enable read caching without seeing any data corruption.
The lastest BIOS revision (1005C) enables "I/O Recovery Time" by default
where the previous revision I had (1004D) did not.
Interesting
"Udo A. Steinberg" wrote:
I'm not sure whether this is related to the ominous ps/2 mouse bug
you have been chasing, but this problem is 100% reproducible and
very annoying.
After upgrading my Asus A7V Bios from 1003 to 1005D, gpm no longer
receives any mouse events and the mou
Hi,
Alan Cox wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.1-ac9
o Merge with Linus 2.4.2pre2
I've noticed that -ac9 comes with the "Disable PCI-Master-Read-Caching
on VIA" patch that Peter Horton posted a while back. I don't know
whether it was applied
Hi all,
After modifying some bios settings and assigning the parallel port
IRQ5 instead of the IRQ7 it formerly had, I'm now getting kernel
messages like this:
spurious 8259A interrupt: IRQ7
IRQ7 is not in use by any device, but interrupts occur.
Can someone tell me what's up with that?
Alan Cox wrote:
2.4.2-ac24
2.4.2-ac23
o Back out problem via bridge change (me)
That fixed the bttv problems I had. I've noticed that there are
four VIA vt8363 PCI fixups by now. Are these experimental to see if
some people's problems go away or have VIA confirmed that
On Fri, 04 Jan 2008 17:22:57 +0100 Andi Kleen (AK) wrote:
AK [EMAIL PROTECTED] writes:
AK
AK I recently put 4 GB of memory in my Acer Travelmate 8210 series
AK notebook. The BIOS only detects 3 GB.
AK
AK Actually it will detect 4GB, but put the PCI hole over the last GB.
AK One way to get
AM 3fe6c0016fd863b233097a8219a0d8577c2fd503 is first bad commit
AM commit 3fe6c0016fd863b233097a8219a0d8577c2fd503
AM Author: Udo A. Steinberg ...
AM hpet-force-enable-on-ich34
AM
AM Guess the comments about thin ice and testing were justified :-)
AM
AM lspci and a 2.6.23-rc6 dmesg
On Sun, 30 Sep 2007 23:50:29 +0200 Frans Pop (FP) wrote:
FP I'm not sure what you mean. I fetched the branch I think you referred to
FP [1], but when I did a merge of that on top of v2.6.23-rc8-mm2 I
FP got Already up-to-date, so AFAICT that branch is fully merged into mm
FP and I'm already
On Mon, 1 Oct 2007 02:07:33 +0200 Frans Pop (FP) wrote:
FP On Monday 01 October 2007, you wrote:
FP I was suggesting to download 2.6.23-rc8 and applying the -hrt patchset
FP at
FP http://www.kernel.org/pub/linux/kernel/people/tglx/hrtimers/2.6.23-rc8/
FP on top of it.
FP
FP Ah, OK. I'm
On Mon, 06 Aug 2007 23:39:30 +0200 Rafał Bilski (RB) wrote:
RB VT8235 does *NOT* have a HPET(*). Only part which has HPET is VT8237. It
RB is device 00:17.0 too, but only 1106:3227 has HPET enable and memory
RB base registers. VT8235 one and only feature which doesn't have driver
RB yet seems to
On Mon, 6 Aug 2007 23:57:52 +0200 Udo A. Steinberg (UAS) wrote:
UAS My guess is that newer revisions of VT8235 have HPET whereas older
UAS revisions do not. I'll get an lspci dump from our box tomorrow.
Here is the lspci dump from our K7VT4A+ board, where HPET works.
00:00.0 Host bridge: VIA
Hello,
With 2.6.21 I am getting the following errors from the ACPI interpreter on an
Intel S5000PSL board:
Allocate Port Service[:02:02.0:pcie20]
Allocate Port Service[:02:02.0:pcie21]
Evaluate _OSC Set fails. Status = 0x0005
Evaluate _OSC Set fails. Status = 0x0005
aer_init: AER service
.
---
Calculate correct EBDA address for ACPI RSDP scan. The word at BIOS Data Area
40:0E is the segment address of the EBDA.
Signed-off-by: Udo A. Steinberg [EMAIL PROTECTED]
--- linux-2.6.12/arch/i386/kernel/acpi/boot.c.old 2005-07-20
17:28:32.0 +0200
+++ linux-2.6.12/arch/i386/kernel/acpi
Alan Cox wrote:
This is the initial merge with 2.4.6pre - treat this one with care, it may
not be the most reliable 2.4.5ac release ever made
make[3]: Entering directory `/usr/src/linux-2.4.5-ac/drivers/pnp'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.5-ac/include -Wall -Wstrict-prototypes
On Fri, 21 Jan 2005 18:13:55 -0800 (PST) Linus Torvalds (LT) wrote:
LT Ok, trying to calm things down again for a 2.6.11 release.
Connection tracking does not compile...
CC net/ipv4/netfilter/ip_conntrack_standalone.o
In file included from net/ipv4/netfilter/ip_conntrack_standalone.c:34:
On Sat, 22 Jan 2005 15:04:29 +0100 Martin Josefsson (MJ) wrote:
MJ On Fri, 2005-01-21 at 22:32 -0800, Udo A. Steinberg wrote:
MJ
MJ Connection tracking does not compile...
MJ The problem is when compiling without NAT...
MJ The patch below should fix it, I can compile both with and without NAT
On Wed, 29 Nov 2006 14:21:21 -0800 (PST) Linus Torvalds (LT) wrote:
LT So go get it. It's one of those rare perfect kernels. So if it doesn't
LT happen to compile with your config (or it does compile, but then does
LT unspeakable acts of perversion with your pet dachshund), you can rest easy
On Fri, 01 Dec 2006 08:15:12 +1100 Herbert Xu (HX) wrote:
HX Udo A. Steinberg [EMAIL PROTECTED] wrote:
HX
HX Ok, so 2.6.18 used to get along fine with cryptoloop and 2.6.19 refuses to
HX cooperate. An strace of losetup -e aes /dev/loop0 /dev/hda7 without all
HX the terminal interaction shows
On Fri, 8 Jun 2007 22:43:25 +0200 Ingo Molnar (IM) wrote:
IM
IM * Bj?rn Steinbrink [EMAIL PROTECTED] wrote:
IM
IM Anyway, both are bugs and should be fixed. Maybe we're even lucky and
IM it fixes your hang. *fingers crossed*
IM
IM just to make it clear: the NMI watchdog was working
On Fri, 8 Jun 2007 13:57:27 -0700 Andrew Morton (AM) wrote:
AM On Fri, 8 Jun 2007 22:49:11 +0200
AM Udo A. Steinberg [EMAIL PROTECTED] wrote:
AM
AM On Fri, 8 Jun 2007 22:43:25 +0200 Ingo Molnar (IM) wrote:
AM
AM IM
AM IM * Bj?rn Steinbrink [EMAIL PROTECTED] wrote:
AM IM
AM IM Anyway
Hi,
After switching an older machine over from the PDC20265 PATA driver to the
libata driver pata_pdc202xx_old my HDDs are now limited to UDMA/33. With the
old driver they were happily running with UDMA/100.
I'm including the relevant kernel output for both cases below.
Cheers,
- Udo
On Sun, 10 Jun 2007 17:12:59 +0100 Alan Cox (AC) wrote:
AC Doh logic was backwards when moved from the old to new driver as the old
AC driver was so messy.
AC
AC Try this and if you can confirm it works and results match the cable you
AC have.
AC
AC --- drivers/ata/pata_pdc202xx_old.c~
On Tue, 29 May 2007 14:52:53 +0200 Michal Piotrowski (MP) wrote:
MP Here is a list of some known regressions in 2.6.22-rc3.
MP
MP Feel free to add new regressions/remove fixed etc.
MP http://kernelnewbies.org/known_regressions
Here's another 2.6.22-rc3 regression. It was ok on 2.6.21. I believe
patch only enables HPET on ICH6 and beyond? HPET can
be enabled on earlier ICH by setting bit 17 in GEN_CNTL on PCI dev 31, func 0,
offset d0. This seems to work for ICH3/4/5. Are there any errata affecting
these ICHs?
Cheers,
- Udo
--
Dipl.-Inf. Udo Steinberg
show that HPET exists on these chipsets as well and can be enabled the
same way as described in the ICH5 datasheet.
Cheers,
- Udo
--
Dipl.-Inf. Udo Steinberg
Technische Universität Dresden http://os.inf.tu-dresden.de/~us15
Institute for System
Hi,
Alan Cox wrote:
>
> 2.4.4-ac10
With 2.4.4-ac10 and binutils 2.11 I get the following warnings:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.4-ac/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686 -malign-functions=4
Gerhard Mack wrote:
>
> > Its what I would describe as lack of enforcement by trading standards bodies,
> > and I suspect what the US would call 'insufficient class action lawsuits'
>
> What we need is a web page for listing crap hardware so less people buy
> it.
Not just crap hardware, but
Hi,
Ingo Oeser wrote:
>
> The only thing that looks responsible for this is the FXSR stuff,
> that changed.
>
> Like to try again backing this out?
Just to make sure it wasn't a gcc thing, I've recompiled the original
setup with egcs-1.1.2 (previously had used 2.95.2) and that did not
fix a
Linus Torvalds wrote:
>
> Mind trying it with the "HAVE_FXSR" and "HAVE_XMM" macros in
>
> linux/include/asm-i386/processor.h
>
> fixed? They _should_ be just
>
> #define HAVE_FXSR (cpu_has_fxsr)
> #define HAVE_XMM(cpu_has_xmm)
That doesn't help either.
Andi Kleen wrote:
>
> Did you have CONFIG_X86_FXSR or CONFIG_X86_RUNTIME_FXSR enabled when it
> worked?
>
> If not it probably means that the XServer is testing OSFXSR and the branch
> that handles it doesn't work.
--- linux-2.4.0/.config Thu Jan 11 11:22:11 2001
+++ linux-2.4.1/.config Thu
Alan Cox wrote:
>
> 2.4.0-ac6
> o Fix athlon crash on boot with local apic/nmi(Ingo Molnar)
Still crashes here with -ac6 on my Athlon. I'll have to write down the
oops by hand later on or set up a serial console, but once that's done
I'll post the trace - unless someone already knows
"Udo A. Steinberg" wrote:
>
> Alan Cox wrote:
> >
> > 2.4.0-ac6
> > o Fix athlon crash on boot with local apic/nmi(Ingo Molnar)
>
> Still crashes here with -ac6 on my Athlon. I'll have to write down the
> oops by hand later on or set up a
As previously reported by someone, there are occasional
problems when shutting down with unmounting partitions,
that are reported as busy for strange reasons.
Keith Owens said it was supposedly a Redhat shutdown
script issue and I since I'm not using Redhat, it's
most likely not that.
Upon
> /dev/hdb1: Inode 522901, i_blocks is 64, should be 8. FIXED
Ok, culprit identified: /var/spool/lpd/lpd.lock
On another partition I had the same problem with httpd's
error_log.
Since both of those seem to be log- and lock-files, maybe
there's something wrong with file locking?
Anyway,
Alexander Viro wrote:
> > umount: none busy - remounted read-only
>
> > The "none" bit puzzles me the most. /etc/fstab and /etc/mtab
> > look perfectly ok.
> >
> > Has anyone got an idea? Everything worked well with 2.4.0 and
> > Alan's tree up to -ac4, didn't try ac5, and ac6 is what messes
>
"Udo A. Steinberg" wrote:
>
> The very strange stuff is umount at reboot:
>
> umount: none busy - remounted read-only
> umount: /: device is busy
> Remounting root-filesystem read-only
> mount: / is busy
> Rebooting.
I just noticed another strange eff
[EMAIL PROTECTED] wrote:
>
> These days umount is done by directory, not by device,
> since a device may be mounted multiple times, so
> I expect the silly message is gone.
> (Is your umount recent?)
>
> [But this is only about the "none". I don't know what is
> wrong in your situation.]
My
Linus Torvalds wrote:
>
> Could people with Athlons please verify that pre3 works for them?
It works very well wrt. fxsr.
-Udo.
-
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
Hello,
I've got a sendmail 8.1.11 process hanging in D state with 2.2.18.
ps -eo fname,tty,pid,stat,pcpu,nwchan,wchan reveals the following:
PID STAT %CPU WCHAN WIDE-WCHAN-COLUMN COMMAND
16176 D 0.0 1f4c28 down_failed sendmail: startup with ...
Is this likely a bug in the
1 - 100 of 179 matches
Mail list logo
