kernel panic
Hi,
I am a kgdb newbie, so please be patient.
I suspect (just based on the fact that this is the 4th time I edit text files
on my NTFS partition through ntfs-3g, using Emacs, and getting frequent I/O
error messages inside Emacs, and then a kernel panic) that this is a ntfs-3g
related problem.
If you ask me exactly how to reproduce it, I sorry, I can tell you exactly (but
see the kgdb output below).
Anyway, the kernel seems to panic at /usr/src/sys/kern/vfs_bio.c:1530
Just a suggestion for a patch (without knowing the functionality of
/usr/src/sys/kern/vfs_bio.c):
The line where the kernel panics:
/usr/src/sys/kern/vfs_bio.c:
--
VM_OBJECT_LOCK(bp->b_bufobj->bo_object);
...
--
Comparing to another file, which does error checking before calling
VM_OBJECT_LOCK:
/usr/src/sys/kern/vfs_aio.c:
--
if (vp->v_object != NULL) {
VM_OBJECT_LOCK(vp->v_object);
...
--
Perhaps the kernel panic could be avoided with the following patch?
/usr/src/sys/kern/vfs_bio.c (suggested patch):
--
if ((bp->b_bufobj != NULL) && (bp->b_bufobj->bo_object != NULL)) {
VM_OBJECT_LOCK(bp->b_bufobj->bo_object);
...
--
Please let me know if you need more information.
Regards,
Johan Kuuse
---
kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x34
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc07b6de4
stack pointer = 0x28:0xe79de7c8
frame pointer = 0x28:0xe79de7e8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1214 (opera)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 5h20m30s
Physical memory: 2035 MB
Dumping 218 MB: 203 187 171 155 139 123 107 91 75 59 43 27 11
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc07b6de4
0xc07b6de4 is in vfs_vmio_release (/usr/src/sys/kern/vfs_bio.c:1530).
1525vfs_vmio_release(struct buf *bp)
1526{
1527int i;
1528vm_page_t m;
1529
1530VM_OBJECT_LOCK(bp->b_bufobj->bo_object);
1531vm_page_lock_queues();
1532for (i = 0; i < bp->b_npages; i++) {
1533m = bp->b_pages[i];
1534bp->b_pages[i] = NULL;
(kgdb) bt
#0 doadump () at pcpu.h:195
#1 0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc0754719 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc0a4905c in trap_fatal (frame=0xe79de788, eva=52) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0a492e0 in trap_pfault (frame=0xe79de788, usermode=0, eva=52) at
/usr/src/sys/i386/i386/trap.c:812
#5 0xc0a49c8c in trap (frame=0xe79de788) at /usr/src/sys/i386/i386/trap.c:490
#6 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc07b6de4 in vfs_vmio_release (bp=0xd927e33c) at
/usr/src/sys/kern/vfs_bio.c:1530
#8 0xc07b8a81 in getnewbuf (slpflag=0, slptimeo=0, size=Variable "size" is not
available.
) at /usr/src/sys/kern/vfs_bio.c:1847
#9 0xc07ba118 in getblk (vp=0xc8891bb0, blkno=0, size=2048, slpflag=0,
slptimeo=0, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/vfs_bio.c:2602
#10 0xc0932815 in ffs_balloc_ufs2 (vp=0xc8891bb0, startoffset=Variable
"startoffset" is not available.
) at /usr/src/sys/ufs/ffs/ffs_balloc.c:699
#11 0xc0952a85 in ffs_write (ap=0xe79debc4) at
/usr/src/sys/ufs/ffs/ffs_vnops.c:720
#12 0xc0a5efc6 in VOP_WRITE_APV (vop=0xc0b93c60, a=0xe79debc4) at vnode_if.c:691
#13 0xc07dbf37 in vn_write (fp=0xc85f3168, uio=0xe79dec60,
active_cred=0xc61c6300, flags=0, td=0xc583fc60) at vnode_if.h:373
#14 0xc07875e7 in dofilewrite (td=0xc583fc60, fd=17, fp=0xc85f3168,
auio=0xe79dec60, offset=-1, flags=0) at file.h:254
#15 0xc07878c8 in kern_writev (td=0xc583fc60, fd=17, auio=0xe79dec60) at
/usr/src/sys/kern/sys_generic.c:401
#16 0xc078793f in write (td=0xc583fc60, uap=0xe79decfc) at
/usr/src/sys/kern/sys_gen
Re: i386 vs amd64?
On Thu, 7 Aug 2008 11:34:41 +0200, Milan Obuch <[EMAIL PROTECTED]> said: > Funny observation: "r" is on LEFT keyboard side, "l" is on RIGHT keyboard > side. I for one have problem at times precisely for this reason, but I know > this is an important step and one need to act with great care. I use a different mnemonic: r)eplace and l)eave untouched (I read it in this ML a long time ago). Regards, -- Yoshiaki Kasahara Research Institute for Information Technology, Kyushu University [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ICRC's
On Sun, 10 Aug 2008, Jeremy Chadwick wrote: On Sun, Aug 10, 2008 at 06:01:34PM -0500, Larry Rosenman wrote: You have one or more of the following: 1. Faulty ATA cable 2. Faulty ATA port 3. Faulty ATA controller (doubtful, unless the errors are specific to one role (e.g. master or slave)) 4. A 2nd disk which is equally as bad (came from the same manufacturing batch, which is very likely if the drive is of the same vendor and model type, and manufacturing date (within a month or two)) We have a winner. I replaced the cable, and we get a clean scrub: pool: vault state: ONLINE scrub: scrub completed with 0 errors on Sun Aug 10 20:46:37 2008 config: NAMESTATE READ WRITE CKSUM vault ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ad4s1fONLINE 0 0 0 ad4s1eONLINE 0 0 0 ad4s1dONLINE 0 0 0 errors: No known data errors Much nicer. Thanks, Jeremy! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Groff in FreeBSD
I am trying to refresh my old groff skills, playing with it for the
first time on FreeBSD -- and getting very confused with understanding
groff's place and organization here. (I am writing this on FreeBSD 7.0
but I could start an 8.0 system if somebody suggested to take a look
there).
Let's start with the practical end of it: I wanted to find a good
macro package, good by modern standards. In the past, I've tried 'mm',
'ms', 'me' -- and could never decide which one was the most practical
one (well, 'mm', perhaps). These days, it seems like 'mom' is a
popular package, worth a serious attention.
So, I am trying to see if 'mom' is available on my system, and it is
not.
I do various online searches, and the only thing that comes up is:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2003-11/0407.html
groff macro package 'mom' not installed
Date: 11/24/03
(and similar entries)
'mom' is, of course, in the source tree:
ls -ld /usr/src/contrib/groff/contrib/mom
drwxr-xr-x 4 root wheel 512 Mar 26 19:30
/usr/src/contrib/groff/contrib/mom/
as is 'mm':
ls -ld /usr/src/contrib/groff/contrib/mm
drwxr-xr-x 4 root wheel 512 Mar 26 19:29 /usr/src/contrib/groff/contrib/mm/
But while the latter has "tmac" files installed:
ls /usr/share/tmac/mm*
0.MT 4.MT 5.MT locale mm.tmacmmse.tmac ms.cov
se_locale se_ms.cov
the former does not:
ls /usr/share/tmac/mom*
ls: /usr/share/tmac/mom*: No such file or directory
So, I try to build something relevant by hand, and nothing good comes
out of it. But I notice that the '/usr/src/contrib/groff/contrib/mm'
directory is not the only place for 'mm' -- there is also
ls -ld /usr/src/gnu/usr.bin/groff/contrib/mm
drwxr-xr-x 2 root wheel 512 Aug 10 17:48
/usr/src/gnu/usr.bin/groff/contrib/mm/
which is a built entity.
At this point, I begin not care about having 'mom' -- I just want to
understand the groff organization in FreeBSD.
Things that puzzle me:
1. Under '/usr/obj', there is a 'tmp/legacy' directory, which has an
empty 'mm' directory deep down:
find tmp/legacy/usr/share/tmac/mm -ls
5184624 drwxr-xr-x2 root wheel 512
Aug 9 23:05 tmp/legacy/usr/share/tmac/mm
What is this 'tmp/legacy'?
2. There is an odd relationship between "tmac" files under '/usr/src'
and '/usr/obj':
for cmd in "ls -l" "diff -q"; do for f in pic.tmac doc.tmac; do $cmd
/usr/src/contrib/groff/tmac/$f /usr/obj//usr/src/tmp/legacy/usr/share/tmac/$f;
done; done
-rwxr-xr-x 1 root wheel 117 Apr 17 2001
/usr/obj/i386/x01/freebsd/7.0/usr/src/tmp/legacy/usr/share/tmac/pic.tmac
-rw-r--r-- 1 root wheel 117 Apr 17 2001 /usr/src/contrib/groff/tmac/pic.tmac
-rwxr-xr-x 1 root wheel 73079 Aug 9 23:05
/usr/obj/i386/x01/freebsd/7.0/usr/src/tmp/legacy/usr/share/tmac/doc.tmac
-rw-r--r-- 1 root wheel 148585 Oct 20 2005
/usr/src/contrib/groff/tmac/doc.tmac
Files /usr/src/contrib/groff/tmac/doc.tmac and
/usr/obj/i386/x01/freebsd/7.0/usr/src/tmp/legacy/usr/share/tmac/doc.tmac differ
I.e. some files under '/usr/obj' are regenerated (see "Aug 9" for
'doc.tmac'), and others are not ('pic.mac'). Some files are
identical in both places, and others are not.
What is the logic and mechanics here?
Can anybody shed some light on this?
And also, if somebody had a recommendation on the most practical
choice of the macro package, it would be highly appreciated.
Thank you,
-- Alex -- [EMAIL PROTECTED] --
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ICRC's
On Sun, Aug 10, 2008 at 06:01:34PM -0500, Larry Rosenman wrote: > I'm getting the following on a zpool scrub: > > ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=54817587 > > I replaced the drive at ad8 because the original one would get an ICRC and > then hang the bus. > > Model Family: Seagate Barracuda 7200.10 family > Device Model: ST3500630AS > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED > WHEN_FAILED RAW_VALUE > 1 Raw_Read_Error_Rate 0x000f 105 100 006Pre-fail Always > - 9366477 > 7 Seek_Error_Rate 0x000f 063 060 030Pre-fail Always > - 2364626 > 9 Power_On_Hours 0x0032 100 100 000Old_age Always > - 41 > 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always > - 7 > 190 Airflow_Temperature_Cel 0x0022 064 061 045Old_age Always > - 36 (Lifetime Min/Max 35/39) > 194 Temperature_Celsius 0x0022 036 040 000Old_age Always > - 36 (0 32 0 0) > 195 Hardware_ECC_Recovered 0x001a 068 064 000Old_age Always > - 207627383 > 199 UDMA_CRC_Error_Count0x003e 200 200 000Old_age Always > - 94 > > Error 110 occurred at disk power-on lifetime: 41 hours (1 days + 17 hours) > When the command that caused the error occurred, the device was active or > idle. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 84 51 0f fe e7 36 49 Error: ICRC, ABRT 15 sectors at LBA = 0x0936e7fe = > 154593278 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- > c8 00 00 0d e7 36 49 00 01:23:46.872 READ DMA > c8 00 00 0d e6 36 49 00 01:23:46.871 READ DMA > c8 00 00 0d e5 36 49 00 01:23:46.871 READ DMA > c8 00 00 0d e4 36 49 00 01:23:46.870 READ DMA > c8 00 00 0d e3 36 49 00 01:23:46.853 READ DMA > > Ideas? > > This is on a SuperMicro SYS-7045-TR+ You have one or more of the following: 1. Faulty ATA cable 2. Faulty ATA port 3. Faulty ATA controller (doubtful, unless the errors are specific to one role (e.g. master or slave)) 4. A 2nd disk which is equally as bad (came from the same manufacturing batch, which is very likely if the drive is of the same vendor and model type, and manufacturing date (within a month or two)) The disk's SMART error log even confirms the DMA errors, which proves there is in fact a problem with one of the above. In this particular case, it's not FreeBSD. :-) My recommendation: * Try another disk from a different manufacturer (not Seagate) * If similar errors appear using that disk, the problem is either item 1, 2, or 3. * If no errors appear, it's item 4, in which case send the disk to Seagate for RMA; their SeaTools utility, on a full scan, should definitely return an error code which you can give to Support when filing for the RMA. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ICRC's
I'm getting the following on a zpool scrub: ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=54817587 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=187521229 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=187522189 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=109095258 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=101327859 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=172911744 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=65393370 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=64741875 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=262496999 ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=154593293 pool: vault state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: scrub completed with 0 errors on Sun Aug 10 16:20:30 2008 config: NAMESTATE READ WRITE CKSUM vault ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 017 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ad4s1fONLINE 0 0 0 ad4s1eONLINE 0 0 0 ad4s1dONLINE 0 0 0 errors: No known data errors I replaced the drive at ad8 because the original one would get an ICRC and then hang the bus. Smart info: smartctl version 5.38 [amd64-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3500630AS Serial Number:9QG19C2Q Firmware Version: 3.AAE User Capacity:500,107,862,016 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Sun Aug 10 18:01:07 2008 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 430) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time:( 163) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 105 100 006Pre-fail Always - 9366477 3 Spin_Up_Time0x0003 095 095 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030Pre-fail Always - 2364626 9 Power_On_Hours 0x0032 100 100 000Old_age Always - 41 10 Spin_Retry_Count0x0013 1
Re: IMPORTANT! Network is unreachable
09.08.08, 22:37, "Clifton Royston" <[EMAIL PROTECTED]>: > On Sat, Aug 09, 2008 at 05:23:32PM +0400, KES wrote: > > 09.08.08, 16:22, "Matthew Seaman" <[EMAIL PROTECTED]>: > > > Andrew Snow wrote: > > > > Usually if there is more than IP in a given subnet on an interface, you > > > > give it a /32 netmask. Only the first IP in a subnet should have the > > > > full netmask. > > > > > > > > So your example should look like this: > > > > > > > > inet 10.11.16.14 netmask 0xff00 broadcast 10.11.16.255 > > > > inet 10.11.16.9 netmask 0x broadcast 10.11.16.9 > > > /32 netmasks for 2nd and subsequent IP alias addresses used to be > > > mandatory and are arguably more correct, but nowadays you can use > > > the actual netmask for the network instead. Was fixed a year or > > > two ago. It's a wetware compatibility thing -- other unixoid OSes > > > never had the /32 netmask requirement, and it kept tripping people up > > > when swapping between OSes. > > > Unfortunately I can't say exactly what the problem the OP is experiencing > > > is due to, but the way routes are appearing and disappearing on a 5 > > > minute timescale does suggest dynamic routing problems to me. As a > > > work-around, if the OP wanted to override the information routed gets > > > from the network, then he could use /etc/gateways to have the local > > > routed append some static routes to the routing table -- see routed(8) > > > for the gory details. Losing a route for a directly attached network > > > looks like a bug to me though. > ... > > > > > > inet 10.11.16.14 netmask 0xff00 broadcast 10.11.16.255 > > > > inet 10.11.16.9 netmask 0x broadcast 10.11.16.9 > > /24 mask on each IPs on same interfaces is working fine on FreeBSD 6.3 > > So I do not think that problem is with the network mask. Because of even > > ping 10.11.16.14 > > returns network is unreachable! > > Now when I upgraded to v7 I see trouble described earlier. > > So this is must be counted as BUG of v7 > I happened to see recently a report of a similar problem with 7.0 on > a private mailing list. Again, there were multiple IP addresses > configured within the main subnet of the interface (this time > configured as /32s on other physical interfaces) and again, after a > while the system lost connectivity to its main subnet and "forgot" how > to ARP for addresses on the interface. An important similarity - the > routing info like yours showed the attached network with the G flag, as > being reachable via the gateway address within the same subnet. > I can't troubleshoot this, no access to the system in question, but I > thought it might help to know that others have run into the same > problem. > > The thing which is very interesting is: > > Why period is 5 min? > Might be something to do with ARP? Not sure. > -- Clifton >I can't troubleshoot this, no access to the system in question You mean you can try to resolve trouble if you get access to machine? I also have tryed /32, but this do not help: gorodok# ifconfig rl0 rl0: flags=8843 metric 0 mtu 1500 options=8 ether 00:0e:2e:db:4f:d4 inet 10.11.16.14 netmask 0xff00 broadcast 10.11.16.255 inet 10.11.16.9 netmask 0x broadcast 10.11.16.9 media: Ethernet autoselect (100baseTX ) status: active gorodok# ifconfig rl0 add 10.10.16.3/28 gorodok# ping 10.10.16.3 PING 10.10.16.3 (10.10.16.3): 56 data bytes ping: sendto: Network is unreachable ping: sendto: Network is unreachable ^C --- 10.10.16.3 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss gorodok# netstat -nr Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default10.11.16.1 UGS 032727rl0 10.0.0.0/1610.11.16.2 UG 00rl0 10.10.16.0/28 10.10.16.3 UGC 02rl0 10.11.15.0/24 link#2 UC 00rl1 10.11.16.0/24 link#1 UC 00rl0 10.11.16.1 00:e0:4c:59:50:7e UHLW20rl0 1193 10.11.16.2 00:03:79:01:9b:d0 UHLW20rl0 1126 10.11.16.9 10.11.16.9 UH 00rl0 => 10.11.16.9/32 link#1 UC 00rl0 10.11.16.1200:0c:6e:ff:0b:35 UHLW1 2472rl0 1127 10.11.16.1400:0e:2e:db:4f:d4 UHLW1 31lo0 127.0.0.1 127.0.0.1 UH 0 314lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 ff01:4::/32 fe80::1%lo0
Re: IMPORTANT! Network is unreachable
09.08.08, 18:30, "Kurt Jaeger" <[EMAIL PROTECTED]>: > Hi! > > So I do not think that problem is with the network mask. Because of even > > ping 10.11.16.14 > > returns network is unreachable! > > Now when I upgraded to v7 I see trouble described earlier. > > So this is must be counted as BUG of v7 > It might be some issue with ARP timeouts ? 10.11.16.14 is local address tcpdump on the interface with this address shows nothing >The system learns > the other IPs using some indirect way and forgets it as soon > as the arp address times out ? I do not think so. Because of when I ping local address 10.11.16.14 for an our without breaking this ping. So mac address can not die because of timeout. It dissappears from kernel routing table by some other cause. I do not know which cause > > 5min period is seen without routed. > > With routed I get next picture: > > start routed: network is unreachable > > stop routed: network still unreacheable > > start routed: network is reachable > > stop routed: network is reacheable > > start routed: network is unreachable again > > > > The thing which is very interesting is: > > Why period is 5 min? > Why do you run routed ? I want to use RIP > Why don't you just statically assign the routes ? Because of I have two links to same place router1 --- LAN1 --- router2 | / LAN2 LAN3 |/ router3 -/ router1: 10.0.16.1/24, 10.10.16.8/24 router2: 10.11.16.1/24, 10.0.16.3/24 router3: 10.11.16.14/24, 10.10.16.3/24 LAN1: 10.0.16.0 LAN2: 10.10.16.0 LAN3: 10.11.16.0 router3: rl0: flags=8843 metric 0 mtu 1500 options=8 ether 00:0e:2e:db:4f:d4 inet 10.11.16.14 netmask 0xff00 broadcast 10.11.16.255 inet 10.11.16.9 netmask 0xff00 broadcast 10.11.16.255 inet 10.10.16.3 netmask 0xfff0 broadcast 10.10.16.15 media: Ethernet autoselect (100baseTX ) status: active I add 10.10.16.3 address to rl0 by mistake. It must be on rl1 interface. But when I added it I lose connection to my LAN. I think this behavior is bug so I describe problem in letters earlier ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Sun, 10 Aug 2008, David Duchscher wrote: On Aug 10, 2008, at 10:22 AM, Larry Rosenman wrote: I don't have that IPMI card but I can say we have other cards of theirs working. I would make sure the card is at the latest version of firmware. The AOC-SIMSO(+) card was not detected correctly until we upgraded. I don't know why the card is going away when freebsd boots since I assume you are on the dedicated LAN interface with its own IP address. Yes. It's not going away, just doesn't see the key strokes. Looking through your dmesg file, I don't see a USB keyboard being attached. On my system, the virtual keyboard is a USB keyboard. ukbd0: on uhub3 kbd2 at ukbd0 Good catch. When I set it to disable USB Mass Storage when no image is loaded, the ukbd came alive, and I'm typing this on the IPMI Console. Thanks! -- DaveD -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Aug 10, 2008, at 10:22 AM, Larry Rosenman wrote: I don't have that IPMI card but I can say we have other cards of theirs working. I would make sure the card is at the latest version of firmware. The AOC-SIMSO(+) card was not detected correctly until we upgraded. I don't know why the card is going away when freebsd boots since I assume you are on the dedicated LAN interface with its own IP address. Yes. It's not going away, just doesn't see the key strokes. Looking through your dmesg file, I don't see a USB keyboard being attached. On my system, the virtual keyboard is a USB keyboard. ukbd0: on uhub3 kbd2 at ukbd0 -- DaveD
Re: IPMI Console: No luck once OS is booted
On Sun, 10 Aug 2008, Daryl Richards wrote: What NIC does your server use? I'm currently trying to figure out a similar issue with my server, which use bge(4) em(4), and the IPMI card has it's own NIC. I have a Sun Fire X2200. I can access the LOM no problem once Linux or Solaris is booted. But, once FreeBSD boots, it's no longer accessible from the NIC. Serial still works fine, it's just access via web or ssh. This happens from a fresh install, and also I've rebuild to -STABLE, and no joy either. These two cases might be related. Hrm. That's interesting. On 10-Aug-08, at 9:24 AM, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Aug 10, 2008, at 8:24 AM, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? I don't have that IPMI card but I can say we have other cards of theirs working. I would make sure the card is at the latest version of firmware. The AOC-SIMSO(+) card was not detected correctly until we upgraded. I don't know why the card is going away when freebsd boots since I assume you are on the dedicated LAN interface with its own IP address. We do have a few issues with Supermiro IPMI and FreeBSD that share the Intel NIC (em) with the OS. Once the NIC is detected, you can't talk to the IPMI card until the NIC is configured with ifconfig. Even just an ifconfig up will wake things back up. We ended up removing the em driver from the kernel and loading it as a module to reduce this window. The other issue is with bridging since the IPMI packets get gobbled up and never make it too the bridge. I do need to file PRs for these one of these days... -- DaveD
Re: IPMI Console: No luck once OS is booted
On Sun, 10 Aug 2008, David Duchscher wrote: On Aug 10, 2008, at 8:24 AM, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? I don't have that IPMI card but I can say we have other cards of theirs working. I would make sure the card is at the latest version of firmware. The AOC-SIMSO(+) card was not detected correctly until we upgraded. I don't know why the card is going away when freebsd boots since I assume you are on the dedicated LAN interface with its own IP address. Yes. It's not going away, just doesn't see the key strokes. We do have a few issues with Supermiro IPMI and FreeBSD that share the Intel NIC (em) with the OS. Once the NIC is detected, you can't talk to the IPMI card until the NIC is configured with ifconfig. Even just an ifconfig up will wake things back up. We ended up removing the em driver from the kernel and loading it as a module to reduce this window. The other issue is with bridging since the IPMI packets get gobbled up and never make it too the bridge. I do need to file PRs for these one of these days... -- DaveD -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
What NIC does your server use? I'm currently trying to figure out a similar issue with my server, which use bge(4) I have a Sun Fire X2200. I can access the LOM no problem once Linux or Solaris is booted. But, once FreeBSD boots, it's no longer accessible from the NIC. Serial still works fine, it's just access via web or ssh. This happens from a fresh install, and also I've rebuild to -STABLE, and no joy either. These two cases might be related. On 10-Aug-08, at 9:24 AM, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED] " ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
Larry Rosenman wrote: There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? In the IPMI card's web interface, I remember having to fiddle with the "Keyboard/Mouse emulation" option to solve this problem. Try changing to the alternative settings. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with /boot/loader [A new patch]
On Sat, Aug 09, 2008 at 05:17:31PM -0400, John Baldwin wrote: > > Sigh, it does not fix my problem described here: > > http://groups.google.ru/group/muc.lists.freebsd.stable/browse_thread/thread > >/538039f40b469e2a > > I've just updated my 7.0-STABLE to latest sources, applied your patch > > using "cd /usr/src; patch -p6 < ~/btx_hang.patch", it has applied cleanly. > > Then I've rebuilt and reinstalled kernel and world and rebooted. > > My problem persists as it was. > > In addition to my earlier message, it would probably be good to narrow down > what breaks the loader for you. For example, does it work ok over serial and > only break on vidconsole? I've established serial console, switched back to 7.0-STABLE sources plus your patch and found that while vidconsole hangs, serial console is not affected and command prompt works without a problem with it. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
