Re: smbfs (Re: BUG: soft lockup detected on CPU#0! (2.6.18.2))
Andrew Morton <[EMAIL PROTECTED]> writes: > On Thu, 16 Nov 2006 10:30:41 + (UTC) > Oleg Verych <[EMAIL PROTECTED]> wrote: > >> [ Adding e-mail of Andrew Morton, he may have clue about who to ping ;] >> [ MAINTAINERS.smbfs seems to be emply ] > > smbfs is unmaintained and we'd like to kill it off. Please use cifs. Oh, I wasn't aware that CIFS had become stable enough and smbfs was deprecated. I will begin migration to cifs. Thanks. Regards /Rasmus -- Rasmus Bøg Hansen MSC Aps Bøgesvinget 8 2740 Skovlunde 44 53 93 66 - 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: smbfs (Re: BUG: soft lockup detected on CPU#0! (2.6.18.2))
Oleg Verych <[EMAIL PROTECTED]> writes: > [ Adding e-mail of Andrew Morton, he may have clue about who to ping ;] > [ MAINTAINERS.smbfs seems to be emply ] > > On 2006-11-14, Rasmus BЬg Hansen wrote: > [] >> [1.] One line summary of the problem: >> >> Kernel BUG's and freezes after a soft lockup. >> >> [2.] Full description of the problem/report: >> >> The night before sunday, my server froze. It was entirely dead and had >> to be power cycled. There was no seriel console connected but it >> managed to log a short BUG before, which seems related to smbfs. >> >> As it happened in the night, I am unsure what triggered the bug, but >> it was during the nightly backup routines, which includes running >> rsync over ssh (over ADSL so pretty slow) and writing some large >> .tar.bz2 to a smbfs drive. I assume (but do no know for sure) that it >> was the last one that triggered the bug. > > Nobody seems to picked this up. So. > Why don't you try debian's kernel 2.6.18 from unstable? I haven't tried that, partially to get rid of the initrd and have drivers for the controllers/disks in-kernel, partially because I like having built my own kernel. That might be silly, of course - I can try the Debian kernel, if you think it would make a difference. > I see, you've build it yourself, then try to enable some more locking > debuging in the "kernel hacking" section. I am now running with all lock debugging turned on. "Unfortunately" the machine has been running stable since the crash last weekend - perhaps the extra-large backup rourines at sunday may trigger it again... > (gitweb down, i can't check history of smbfs, and i have amd64 arch, anyway) >> Nov 12 03:54:57 gere kernel: BUG: soft lockup detected on CPU#0! >> Nov 12 03:54:57 gere kernel: [softlockup_tick+170/195] >> softlockup_tick+0xaa/0xc3 >> Nov 12 03:54:57 gere kernel: [update_process_times+56/137] >> update_process_times+0x38/0x89 >> Nov 12 03:54:57 gere kernel: [smp_apic_timer_interrupt+105/117] >> smp_apic_timer_interrupt+0x69/0x75 >> Nov 12 03:54:57 gere kernel: [smbiod+238/348] smbiod+0xee/0x15c > this > >> Nov 12 03:54:57 gere kernel: [apic_timer_interrupt+31/36] >> apic_timer_interrupt+0x1f/0x24 >> Nov 12 03:54:57 gere kernel: [journal_init_revoke+49/678] >> journal_init_revoke+0x31/0x2a6 >> Nov 12 03:54:57 gere kernel: [smbiod+238/348] smbiod+0xee/0x15c > and this *may be* double (un)lock. Hopefully lock debugging will tell. Regards /Rasmus -- Rasmus Bøg Hansen MSC Aps Bøgesvinget 8 2740 Skovlunde 44 53 93 66 - 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: [PATCH] Re: [MINOR PROBLEM] RTL8139C: transmit timed out
On Sat, 14 Jul 2001, Masaru Kawashima wrote: > > Jul 12 20:36:43 wiibroe kernel: NETDEV WATCHDOG: eth0: transmit timed out > > I had the same problem with linux-2.4.6-ac2, and I found a bug > in the function rtl8139_start_xmit() of 8139too.c. > > Attached patch will fix this bug. Now the box has been running for nearly a week without any trace of problems, so the patch seems to be fine. Rasmus -- -- [ Rasmus 'Møffe' Bøg Hansen ] --- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who - [ moffe at amagerkollegiet dot dk ] -- - 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: [2.4.5 and all ac-Patches] massive file corruption with reiseror NFS
On Sat, 2 Jun 2001, Andreas Hartmann wrote: > I got massive file corruptions with the kernels mentioned in the subject. I > can reproduce it every time. You cannot use NFS on reiserfs unless you apply the knfsd patch. Look at www.namesys.com. Rasmus -- -- [ Rasmus 'Møffe' Bøg Hansen ] -- If you only have a hammer everything looks like a nail [ moffe at amagerkollegiet dot dk ] --0 - 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: >2G Files
On Wed, 2 May 2001, Bill Wendling wrote: > Question: Does Linux support >2G files and, if so, how do I implement > this? With kernel 2.4 it does. You will probably need to compile userspace programs against 2.4 headers to get this functionality in userspace programs too. Rasmus -- -- [ Rasmus 'Møffe' Bøg Hansen ] -- I think the sum of intelligence on the internet is constant. Only the number of users grows. - Uwe Ohse in the monastery - [ moffe at amagerkollegiet dot dk ] - - 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: [PATCH] Single user linux
On Thu, 26 Apr 2001 [EMAIL PROTECTED] wrote: > > On Thu, 26 Apr 2001, [iso-8859-1] Rasmus Bøg Hansen wrote: > > > i'd be happy to accept proof that multi-user is a solution for > > > clueless user, not because it's proven on servers. but because it is > > > a solution by definition. > > > > Let's turn the question the other way. It's you trying to convince > > us, that everyone needs root access. What does a clueless user need root > > access for? > > what work around what? right now it's the kernel who thinks that root > is special, and applications work around that because there's a > division of super-user and plain user. is that a must? Basically yes. But if you do not want _any_ security - you can drop it. I started using Linux (and unix in general) in '96 (thanks Linus). And now - feelin like an experienced linux (unix) user I feel more like ever, I do _not_ want to be root You do not understand the unix security aspects. You do not want unix security and do not want unix. Then stop using it. People from redmond allow you to trash your system without any special effort. Stop bugging us. Have you noticed you never got response from Linus? He is probably still laughing (or feeling pissed off) - Stop trashing his (good) work, I know he is not the only one (I thank every Linux developer)... Did you ever realize, that the unix security model hasn't changed radically for 30 years? Beacause what? It is (opposite your patch) mostly good. > it's trivial to say that in multi-user system, one user shall not mess > with other user. in multi-process, a process shall not mess with other > process. Ok. If you want to fuck up other people's processes, do it. Kill init and get strange panics. If you want to crash other people's work, do it. But begone from _my_ box Go to a bar and get drunk (as you do not seem to have anything better to use your time for),. > but when it comes to a computer which only has one user, why would > it stop a user. because the kernel thinks it isn't right? if he > felt like killing random process, which is owned by other than the > user, is it a wrong thing to do? he owns the computer, he may do > anything he wants. Yeah. If he wants to do that he logs in as root. 'killall -1'? 'dd if=/dev/zero of=/dev/kcore'. Yeah, crash your computer if you want. But the 'clueless user does not want to'! > and i'm not even trying to convince anyone. communicating is > closer. Who are you not trying to convince? You propose a patch - you try to convince us to drop the unix secuity model... > > And if you really want everybody to have access to all files, you can > > just do a 'chmod 777 /'. Perhaps set it up as a cronjob to run daily? > > > Besides you write, that a distro shipping single-user is evil. So you > > want the clueless user to recompile his own kernel to enable single-user > > iff that distro starts up daemons. Or the user starts up daemons. He has root privileges after all. > > mode (why do at all call it 'single-user' when you still have different > > i wrote somewhere that it was my mistake to call it single-user when i > mean all user has the same root cap, and reduce "user" (account) to > "profile". Ok. My mistake. You want to use 'user profiles' but not use the advantages... You don't have to. You can use Windows if you want to. You can just use root. As long as you do not hack /sbin/login or xdm, you will still have to type login/password - no win, no gain. If it wasn't for the nips, being so good at bulding ships the yards would still be open in the clyde get out to a war and get shot! Rasmus -- -- [ Rasmus 'Møffe' Bøg Hansen ] -- I don't suffer from insanity, i enjoy every minute of it! - [ moffe at amagerkollegiet dot dk ] - - 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: [PATCH] Single user linux
> taking place as a clueless user, i think i should be able to do anything.
Yeah, I thought so when I started using Linux. I stopped thinking so,
when I accidentally blew up the FS on my datadrive and lost
nearly _everything_ I had written for 2 years...
> i'd be happy to accept proof that multi-user is a solution for
> clueless user, not because it's proven on servers. but because it is
> a solution by definition.
Let's turn the question the other way. It's you trying to convince
us, that everyone needs root access. What does a clueless user need root
access for?
Programming - no.
Writing documents - no.
Surfing the web - no.
Reading email - no.
Installing kernels - yes (but a clueless user won't do this).
Running viruses, that blow up the entire system - yes.
Installing software - yes. But how often do you do that? And is the 'su'
really so hard to remember?
If you really want to have different uids, why not hack xdm/login to
autologin. And when it autologins to a specific user, why do you want
different id's?
And if you really want everybody to have access to all files, you can
just do a 'chmod 777 /'. Perhaps set it up as a cronjob to run daily?
Besides you write, that a distro shipping single-user is evil. So you
want the clueless user to recompile his own kernel to enable single-user
mode (why do at all call it 'single-user' when you still have different
ID's?)... The clueless user probably does not even know what the kernel
is - and then have to recompile it...
Rasmus
--
-- [ Rasmus 'Møffe' Bøg Hansen ] --
if (getenv(EDITOR) == "vim") {karma++};
- [ moffe at amagerkollegiet dot dk ] -
-
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: A question about MMX.
On Sat, 21 Apr 2001 [EMAIL PROTECTED] wrote: > I have a Intel Pentium MMX machine and it acts as a mailserver, webserver, > ftp and I use X on it. I would like to know if the MMX instructions are > used by the kernel in this operations or not (networking, X etc.). I _think_ some MMX is used if you configure the kernel for an MMX-enabled CPU type, but not sure. But as MMX is mainly an extended floating point instruction set, you will not have much use for it on a server as you describe. Rasmus -- -- [ Rasmus 'Møffe' Bøg Hansen ] -- [ Cancel Cancelled ] - Pine - [ moffe at amagerkollegiet dot dk ] - - 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/
PROBLEM: Kernel oops in kmalloc (network?) - 2.4.3-ac7
Hi I just got an oops with 2.4.3-ac7: [1.] Kernel oops'es and KDE hangs. [2.] While compiling gcc, suddenly KDE hangs. I was able to change to a console to investigate the problem. It appears that the dying process was kwin as X and other parts of KDE still is responsive. The kernel seems to run happily on after the oops. [3.] Keywords: kmalloc, unix sockets, oops [4.] Kernel version (from /proc/version): Linux version 2.4.3-ac7 (root@grignard) (gcc version 2.95.3 20010315 (release)) #2 man apr 16 15:03:36 CEST 2001 [5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) ksymoops 2.3.7 on i586 2.4.3-ac7. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.3-ac7/ (default) -m /boot/System.map (specified) Reading Oops report from the terminal CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010086 eax: 001b ebx: c1227768 ecx: c01fcca0 edx: 18ef esi: c1a5a000 edi: 1000 ebp: 0246 esp: c4611e9c ds: 0018 es: 0018 ss: 0018 Process kdeinit (pid: 10521, stackpage=c4611000) Stack: c01d1c8f 04dc c2d3f97c c024b020 0007 0002 1000 c1a5a000 c0193ac6 083c 0007 c4b943e0 c461 c01932cc 0800 0007 c4611f4c 07e8 c4b940b4 c22fca9c c01c357f c4b943e0 07e8 Call Trace: [] [] [] [] [] [] [] Code: 0f 0b 83 c4 08 f6 43 11 04 74 55 b8 a5 c2 0f 17 87 46 00 3d >>EIP; c0124953<= Trace; c0193ac6 Trace; c01932cc Trace; c01c357f Trace; c0191234 Trace; c019143f Trace; c012cb1a Trace; c0106a63 Code; c0124953 <_EIP>: Code; c0124953<= 0: 0f 0b ud2a <= Code; c0124955 2: 83 c4 08 add$0x8,%esp Code; c0124958 5: f6 43 11 04 testb $0x4,0x11(%ebx) Code; c012495c 9: 74 55 je 60 <_EIP+0x60> c01249b3 Code; c012495e b: b8 a5 c2 0f 17mov$0x170fc2a5,%eax Code; c0124963 10: 87 46 00 xchg %eax,0x0(%esi) Code; c0124966 13: 3d 00 00 00 00cmp$0x0,%eax [6.] A small shell script or example program which triggers the problem (if possible) none. [7.] Environment [7.1.] Software (add the output of the ver_linux script here) Linux grignard 2.4.3-ac7 #2 man apr 16 15:03:36 CEST 2001 i586 unknown Gnu C 2.96 Gnu make 3.79.1 binutils 2.10.91.0.2 util-linux 2.11a modutils 2.4.2 e2fsprogs 1.19 reiserfsprogs 3.x.0j Linux C Library2.2.2 Dynamic linker (ldd) 2.2.2 Procps 2.0.7 Net-tools 1.56 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded nfsd lockd sunrpc autofs4 af_packet 3c59x ntfs nls_iso8859-15 nls_cp865 vfat fat [7.2.] Processor information (from /proc/cpuinfo): processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 9 model name : AMD-K6(tm) 3D+ Processor stepping: 1 cpu MHz : 451.035 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr bogomips: 897.84 [7.3.] Module information (from /proc/modules): Module Size Used by es1370 24400 0 (autoclean) (unused) soundcore 3728 4 (autoclean) [es1370] nfsd 65872 8 (autoclean) lockd 50096 1 (autoclean) [nfsd] sunrpc 57696 1 (autoclean) [nfsd lockd] autofs4 9472 2 (autoclean) af_packet 11136 1 (autoclean) 3c59x 23776 1 (autoclean) ntfs 35984 1 (autoclean) nls_iso8859-15 3392 3 (autoclean) nls_cp865 4352 2 (autoclean) vfat8656 2 (autoclean) fat30048 0 (autoclean) [vfat] [7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) /proc/ioports: -001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 0376-0376 : ide1 03c0-03df : vga+ 03f6-03f6 : ide0 0cf8-0cff : PCI conf1 c000-cfff : PCI Bus #01 d000-d00f : VIA Technologies, Inc. Bus Master IDE d000-d007 : ide0 d008-d00f : ide1 d800-d87f : 3Com Corporation 3c905B 100BaseTX [Cyclone] d800-d87f : eth0 dc00-dcff : Advanced System Products, Inc ABP940-U / ABP960-U e000-e03f : Ensoniq ES1370 [AudioPCI] e000-e03f : es1370 /proc/iomem: -0009fbff : System RAM 0009fc00-0009 : reserved 000a-000b : Video RAM area 00
Divide error 2.4.3
Hi
This morning I tried to restart networking on our server. However,
networking did not come up again. It showed out, that ifconfig had
triggered an oops. The box is running vanilla 2.4.3 with reiserfs 3.6.x
fs format.
The box is running iptables and squid - and not more than this. It has
got a via rhine based NIC (D-link DFE-530TX), eth0, and a Wisecom
(RTL8139too) card, eth1. eth1 has proxy arp enabled.
I have included what I think is necessary - don't hope, I have forgotten
anything.
Rasmus
moffe@wiibroe:~# ksymoops -m /boot/System.map < /tmp/oops.txt
ksymoops 2.3.4 on i586 2.4.3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.3/ (default)
-m /boot/System.map (specified)
CPU:0
EIP:0010:[kfree+69/188]
EFLAGS: 00010046
eax: 0b7ce4e0 ebx: c116a840 ecx: c020f360 edx:
esi: 0b7ce4e0 edi: 0286 ebp: esp: cf389e08
ds: 0018 es: 0018 ss: 0018
Process ifconfig (pid: 25860, stackpage=cf389000)
Stack: cc2275c0 cc22761c 0282 000c9e80 c019a14b
cc9e8000
c019a2ca cc2275c0 cc2275c0 cc2275c0 c01d4974 cc2275c0
cc2275c0
c0215de0 0001 0049 c01a0500 c15f5040 cc2275c0
0001
Call Trace: [kfree_skbmem+35/108] [__kfree_skb+310/316]
[netlink_broadcast+504/512] [rtmsg_ifinfo+108/116]
Code: f7 73 0c 89 c5 8b 41 14 89 44 a9 18 89 69 14 8b 53 14 8b 41
Using defaults from ksymoops -t elf32-i386 -a i386
Code; Before first symbol
<_EIP>:
Code; Before first symbol
0: f7 73 0c div0xc(%ebx),%eax
Code; 0003 Before first symbol
3: 89 c5 mov%eax,%ebp
Code; 0005 Before first symbol
5: 8b 41 14 mov0x14(%ecx),%eax
Code; 0008 Before first symbol
8: 89 44 a9 18 mov%eax,0x18(%ecx,%ebp,4)
Code; 000c Before first symbol
c: 89 69 14 mov%ebp,0x14(%ecx)
Code; 000f Before first symbol
f: 8b 53 14 mov0x14(%ebx),%edx
Code; 0012 Before first symbol
12: 8b 41 00 mov0x0(%ecx),%eax
moffe@wiibroe:~# cat /var/log/dmesg
Linux version 2.4.3 (root@wiibroe) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #2 fre mar 30 10:20:16 CEST 2001
BIOS-provided physical RAM map:
BIOS-e820: - 0009fc00 (usable)
BIOS-e820: 0009fc00 - 000a (usable)
BIOS-e820: 000f - 0010 (reserved)
BIOS-e820: - 0001 (reserved)
BIOS-e820: 0010 - 1000 (usable)
On node 0 totalpages: 65536
zone(0): 4096 pages.
zone(1): 61440 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=linux rw root=306
BOOT_FILE=/boot/vmlinuz
Initializing CPU#0
Detected 299.752 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 598.01 BogoMIPS
Memory: 255876k/262144k available (866k kernel code, 5880k reserved,
262k data, 172k init, 0k highmem)
Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
CPU: Before vendor init, caps: 008021bf 808029bf , vendor = 2
Enabling new style K6 write allocation for 256 Mb
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: After vendor init, caps: 008021bf 808029bf 0002
CPU: After generic, caps: 008021bf 808029bf 0002
CPU: Common caps: 008021bf 808029bf 0002
CPU: AMD-K6(tm) 3D processor stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb120, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Disabled enhanced CPU to PCI posting #2
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd v1.8
pty: 256 Unix98 ptys configured
block: queued sectors max/low 170026kB/56675kB, 512 slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: VIA vt82c586b (rev 41) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:pio, hdd:pio
hda: SAMSUNG VG34323A (4.32GB), ATA DISK drive
hdc: IBM-DTLA-307030, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 8446032 sectors (4324 MB)
Re: 2.4.3 irq routing conflict (VIA chipset)
On Tue, 3 Apr 2001, Tim Pepper wrote: > I know there was a thread on this previously and I was thinking it had been > resolved (or was that only for a specific mobo mfg?). When I finally got my > VIA chipset machine up to date with a 2.4.3 kernel I noticed the following on > boot up: I get a like error (apparently plugged in the same slot) > PCI: Found IRQ 11 for device 00:0a.0 > IRQ routing conflict in pirq table for device 00:0a.0 Mar 30 10:32:07 wiibroe kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb120, last bus=1 Mar 30 10:32:07 wiibroe kernel: PCI: Using configuration type 1 Mar 30 10:32:07 wiibroe kernel: PCI: Probing PCI hardware Mar 30 10:32:07 wiibroe kernel: PCI: Disabled enhanced CPU to PCI posting #2 Mar 30 10:32:07 wiibroe kernel: PCI: Using IRQ router VIA [1106/0586] at 00:07.0Mar 30 10:32:07 wiibroe kernel: Activating ISA DMA hang workarounds. [...] Mar 30 10:32:10 wiibroe kernel: 8139too Fast Ethernet driver 0.9.15c loaded Mar 30 10:32:10 wiibroe kernel: PCI: Found IRQ 11 for device 00:0a.0 Mar 30 10:32:10 wiibroe kernel: IRQ routing conflict in pirq table for device 00:0a.0 > The only device on irq 11 is an agp voodoo3 card. I don't seem to see any > negative effects (unless what I believe is an unrelated scsi error is tied to > this somehow). The box has two NIC's (a via rhine at IRQ 10 and the RTL8139). The strange things is that the RTL8139 card is detected at IRQ 11 but runs at IRQ 12 (11 is used by an ATI AGP card): Bus 0, device 9, function 0: Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine 10/100] (rev 6). IRQ 10. Master Capable. Latency=64. Min Gnt=118.Max Lat=152. I/O at 0xe800 [0xe87f]. Non-prefetchable 32 bit memory at 0xe800 [0xe87f]. Bus 0, device 10, function 0: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16). IRQ 12. Master Capable. Latency=64. Min Gnt=32.Max Lat=64. I/O at 0xec00 [0xecff]. Non-prefetchable 32 bit memory at 0xe8001000 [0xe80010ff]. Bus 1, device 0, function 0: VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP (rev 58). IRQ 11. Master Capable. Latency=64. Min Gnt=8. Prefetchable 32 bit memory at 0xe600 [0xe6ff]. I/O at 0xd000 [0xd0ff]. Non-prefetchable 32 bit memory at 0xe500 [0xe5000fff]. Rasmus -- -- [ Rasmus 'Møffe' Bøg Hansen ] -- There are three kinds of lies: lies, politics and statistics. - [ moffe at amagerkollegiet dot dk ] - - 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: ReiserFS - corrupted files (2.4.3)
Hello
I am getting musch the same types of corruption. I am on a K6-2 with a
30Gb IBM HD and 256Mb RAM running vanilla 2.4.3 with iptables and squid
caching proxy. The problems arise on the cache part of the FS (i.e. with
many file operations).
I am considering using reiserfsck (3.x.0j) to fix it, but it has to wait
until the morning - so in the meantime perhaps somebody can use the info
about the corruptions? I have nowhere to back up my rather large (in
comparison to other space on the box) cache, but if it goes lost in the
process of rebuilding it, it does not matter so much.
What should I do to help? I will try to debug the problem if necessary -
should I turb on internal checks?
On Mon, 2 Apr 2001, Robert NEDBAL wrote:
> Hello,
> I'm using ReiserFS on my primary filesystem and yesterday, I have found
> that some files are corrupted. Yesterday I had to reset computer becase
> X Window freezed. Maybe it caused this problem.
>
> This comes from log:
[SNIP]
My log goes much the same (although I have fewer errors - it seems to
affect only few files):
Mar 30 10:32:09 wiibroe kernel: reiserfs: checking transaction log
(device 16:01) ...
Mar 30 10:32:09 wiibroe kernel: Using r5 hash to sort names
Mar 30 10:32:09 wiibroe kernel: ReiserFS version 3.6.25
[...]
Apr 2 14:36:10 wiibroe kernel: is_leaf: item location seems wrong:
*OLD*[1214 319934 0x8f1 DIRECT], item_len 0, item_location 0,
free_space(entry_count) 2289
Apr 2 14:36:10 wiibroe kernel: vs-5150: search_by_key: invalid format
found in block 132193. Fsck?
Apr 2 14:36:10 wiibroe kernel: is_leaf: item location seems wrong:
*OLD*[1214 319934 0x8f1 DIRECT], item_len 0, item_location 0,
free_space(entry_count) 2289
Apr 2 14:36:10 wiibroe kernel: vs-5150: search_by_key: invalid format
found in block 132193. Fsck?
Apr 2 14:36:10 wiibroe kernel: vs-13050: reiserfs_update_sd: i/o
failure occurred trying to update [1214 319936 0x0 SD] stat datais_leaf:
item location seems wrong: *OLD*[1214 319934 0x8f1 DIRECT], item_len 0,
item_location 0, free_space(entry_count) 2289
Apr 2 14:36:10 wiibroe kernel: vs-5150: search_by_key: invalid format
found in block 132193. Fsck?
Apr 2 14:36:10 wiibroe kernel: vs-: reiserfs_delete_solid_item: i/o
failure occurred trying to delete [1214 319936 0x0 SD]
[...]
Apr 2 18:36:25 wiibroe kernel: vs-13042: reiserfs_read_inode2: [1020
271248 0x0 SD] not found
Apr 2 18:36:25 wiibroe kernel: vs-13048: reiserfs_iget: bad_inode. Stat
data of (1020 271248) not found
Apr 2 18:36:50 wiibroe kernel: is_leaf: item location seems wrong:
*OLD*[1214 319934 0x8f1 DIRECT], item_len 0, item_location 0,
free_space(entry_count) 2289
Apr 2 18:36:50 wiibroe kernel: vs-5150: search_by_key: invalid format
found in block 132193. Fsck?
Apr 2 18:36:50 wiibroe kernel: vs-13070: reiserfs_read_inode2: i/o
failure occurred trying to find stat data of [1214 319935 0x0 SD]
Apr 2 18:36:50 wiibroe kernel: vs-13048: reiserfs_iget: bad_inode. Stat
data of (1214 319935) not found
> When I want to list corrupted directory, I get this:
What I get is:
root@wiibroe:/var/spool/squid# find /var/spool/squid/ -type f | xargs ls
> /dev/null
find: /var/spool/squid/01/C5/0001C5DA: Ingen sådan fil eller filkatalog
find: /var/spool/squid/01/C5/0001C5E6: Ingen sådan fil eller filkatalog
find: /var/spool/squid/03/F5/0003F5E9: Adgang nægtet
find: /var/spool/squid/04/B6/0004B6E0: Adgang nægtet
(Ingen sådan fil eller filkatalog = No such file or directory
Adgang nægtet = Access denied)
Rasmus Bøg Hansen
--
-- [ Rasmus 'Møffe' Bøg Hansen ] --
if (getenv(EDITOR) == "vim") {karma++};
- [ moffe at amagerkollegiet dot dk ] -
-
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/
