Re: 3c509 + sb16 bug
Alan Cox writes: > I think the problem here thought isnt the 3c509 and SB card, its the kernel > plug and play code. You might want to try building kernels with no PnP support > at all and see how they behave I agree. I have been having problems with isapnp reliably finding my ALS100 since 2.4.1 (I think). I have just modularised isapnp which means you can at least reload it when it fails to id the card. Since doing that, I've noticed that the use count for isapnp in lsmod continues rising eachtime the sb driver is removed. I am hoping to get some more time this weekend to look at it. Mark - 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/
2.4.0 kernel paging error
Hi, I am running 2.4.0 final. I got the following failed paging request which produced a complete freeze. As you can see it was precipitated by cron starting to run some housekeeping stuff overnight. Has anyone else had prblems? Mark Jan 10 02:25:01 hindleyhome /USR/SBIN/CRON[3823]: (root) CMD (test -e /usr/sbin/anacron || run-parts --report /etc/cron.daily) Jan 10 02:30:01 hindleyhome /USR/SBIN/CRON[3827]: (root) CMD (/sbin/rmmod -a) Jan 10 02:30:01 hindleyhome /USR/SBIN/CRON[3828]: (root) CMD (test -x /usr/sbin/anacron && /usr/sbin/anacron -s) Jan 10 02:30:01 hindleyhome anacron[3830]: Anacron 2.1 started on 2001-01-10 Jan 10 02:30:01 hindleyhome anacron[3830]: Will run job `cron.daily' in 5 min. Jan 10 02:30:01 hindleyhome anacron[3830]: Jobs will be executed sequentially Jan 10 02:35:01 hindleyhome /USR/SBIN/CRON[3832]: (root) CMD (/sbin/rmmod -a) Jan 10 02:35:01 hindleyhome anacron[3830]: Job `cron.daily' started Jan 10 02:35:01 hindleyhome anacron[3836]: Updated timestamp for job `cron.daily' to 2001-01-10 Jan 10 02:35:53 hindleyhome kernel: Unable to handle kernel paging request at virtual address c4870840 Jan 10 02:35:53 hindleyhome kernel: printing eip: Jan 10 02:35:53 hindleyhome kernel: c013d747 Jan 10 02:35:53 hindleyhome kernel: *pde = 03d61063 Jan 10 02:35:53 hindleyhome kernel: *pte = Jan 10 02:35:53 hindleyhome kernel: Oops: Jan 10 02:35:53 hindleyhome kernel: CPU:0 Jan 10 02:35:53 hindleyhome kernel: EIP:0010:[clear_inode+159/216] Jan 10 02:35:53 hindleyhome kernel: EFLAGS: 00010282 Jan 10 02:35:53 hindleyhome kernel: eax: c4870820 ebx: c338f4a0 ecx: c338f4a8 edx: c1169fa4 Jan 10 02:35:53 hindleyhome kernel: esi: c1169fa4 edi: c1dccde8 ebp: c1169fac esp: c1169f78 Jan 10 02:35:53 hindleyhome kernel: ds: 0018 es: 0018 ss: 0018 Jan 10 02:35:53 hindleyhome kernel: Process kswapd (pid: 3, stackpage=c1169000) Jan 10 02:35:53 hindleyhome kernel: Stack: c338f4a0 c013d7bf c338f4a0 c1dccc08 c1dccc00 c013d9c2 c1169fa4 00ee Jan 10 02:35:53 hindleyhome kernel:0004 03b3 c2c8fde8 c3e38bc8 c013d9f1 Jan 10 02:35:53 hindleyhome kernel:c0126453 0006 0004 0006 0004 00010f00 c01d32d7 c1168239 Jan 10 02:35:53 hindleyhome kernel: Call Trace: [dispose_list+63/88] [prune_icache+234/248] [shrink_icache_memory+33/48] [do_try_to_free_pages+91/128] [kswapd+116/272] [kernel_thread+40/56] Jan 10 02:35:53 hindleyhome kernel: Jan 10 02:35:53 hindleyhome kernel: Code: 8b 40 20 85 c0 74 06 53 ff d0 83 c4 04 8b 83 e0 00 00 00 85 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0 kernel paging error
Philipp Rumpf writes: > On Wed, Jan 10, 2001 at 05:55:05PM +0100, Daniel Phillips wrote: > > Mark Hindley wrote: > > > I am running 2.4.0 final. I got the following failed paging request which > > > produced a complete freeze. > > > > > > As you can see it was precipitated by cron starting to run some > > > housekeeping stuff overnight. > > > > > > Has anyone else had prblems? > > > > It looks real. It was executing this line of clear_inode in fs/inode.c: > > > > 380 if (inode->i_sb && inode->i_sb->s_op && inode->i_sb->s_op->clear_inode) > > ^ > >and it blew up here -> > > > Unable to handle kernel paging request at virtual address c4870840 > > I'm pretty sure this is a vmalloc/module address, which would mean ->s_op > points to a module that has been unloaded. This sounds consistent with the > "cron starting to run some housekeeping stuff" above. > > Mark, which file systems are you using ? I have ext2 (builtin) and autoload [v]fat, msdos, hfs, iso9660 and occasionally (but not recently) udf as modules for removable media. vfat is loaded all the time as I have a couple of partitions from another OS I used to use permantently mounted RO. As far as I can remember hfs and iso9660 were the only other ones I had used just before this happened. As I use the kernel module autoloader I also have a cron entry for rmmod -a which runs every so often to clear out the unused modules. Although the logs record rmmod running, they don't say what if any modules were removed. Mark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[PATCH] ALS-110 opl3 and mpu401 under 2.4.0-test10
Please consider this patch which fixes some problems I have been having
with mu ALS-110 card under 2.4 kernels.
There are 2 fixes:
1) pnp info in sb_card.c does not match what the card reports, so isapnp
doesn't identify the opl3 device
2) The other relates to the uart401 detection. If you build the sb driver
into the kernel and then pass the commandline uart401=1 this is interpreted
as the io parameter for the uart401 module not a command for the sb driver.
I have renamed the uart401 detection command to uart401probe. Obviously it
isn't a problem with a modular driver, but the change shouldn't matter.
Mark
--- drivers/sound/sb_card.c Fri Nov 17 10:22:36 2000
+++ drivers/sound/sb_card.c Fri Nov 17 10:12:37 2000
@@ -50,6 +50,10 @@
*
* 21-09-2000 Got rid of attach_sbmpu
* Arnaldo Carvalho de Melo <[EMAIL PROTECTED]>
+ *
+ * 17-11-2000 Renamed parameter uart401 to uart401probe to avoid conflict
with uart401 module
+ * Bugfix ALS-110 pnp info
+ * Mark Hindley <[EMAIL PROTECTED]>
*/
#include
@@ -195,7 +199,7 @@
static int isapnpjump = 0;
static int multiple= 1;
static int reverse = 0;
-static int uart401 = 0;
+static int uart401probe= 0;
static int audio_activated[SB_CARDS_MAX] = {0};
static int mpu_activated[SB_CARDS_MAX] = {0};
@@ -222,12 +226,12 @@
MODULE_PARM(isapnpjump,"i");
MODULE_PARM(multiple, "i");
MODULE_PARM(reverse, "i");
-MODULE_PARM(uart401, "i");
+MODULE_PARM(uart401probe, "i");
MODULE_PARM_DESC(isapnp, "When set to 0, Plug & Play support will be
disabled");
MODULE_PARM_DESC(isapnpjump, "Jumps to a specific slot in the driver's
PnP table. Use the source, Luke.");
MODULE_PARM_DESC(multiple, "When set to 0, will not search for
multiple cards");
MODULE_PARM_DESC(reverse, "When set to 1, will reverse ISAPnP search
order");
-MODULE_PARM_DESC(uart401, "When set to 1, will attempt to detect and
enable the mpu on some clones");
+MODULE_PARM_DESC(uart401probe, "When set to 1, will attempt to detect and
enable the mpu on some clones");
#endif
MODULE_PARM_DESC(io, "Soundblaster i/o base address
(0x220,0x240,0x260,0x280)");
@@ -454,8 +458,8 @@
ISAPNP_VENDOR('A','L','S'), ISAPNP_DEVICE(0x0110),
ISAPNP_VENDOR('@','@','@'), ISAPNP_FUNCTION(0x1001),
ISAPNP_VENDOR('@','X','@'), ISAPNP_FUNCTION(0x1001),
- ISAPNP_VENDOR('@','H','@'), ISAPNP_FUNCTION(0x0001),
- 1,0,0,0},
+ ISAPNP_VENDOR('@','H','@'), ISAPNP_FUNCTION(0x1001),
+ 1,0,0,0},
{"ALS120",
ISAPNP_VENDOR('A','L','S'), ISAPNP_DEVICE(0x0120),
ISAPNP_VENDOR('@','@','@'), ISAPNP_FUNCTION(0x2001),
@@ -557,7 +561,7 @@
}
/* Cards with separate MPU device (ALS, CMI, etc.) */
- if(!uart401)
+ if(!uart401probe)
return(sb_dev[card]);
if((mpu_dev[card] = isapnp_find_dev(bus,
sb_isapnp_list[slot].mpu_vendor, sb_isapnp_list[slot].mpu_function, NULL)))
{
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] ALS-110 opl3 and mpu401 under 2.4.0-test10
>It changes the command line properties people already use. It also cannot be >neccessary since 'uart401' is static. So why does the kernel command-line uart401=1 make a builtin uart401 driver look for the mpu at 0x1 rather than persuade the sb driver to to do a pnp lookup for it? Mark Hindley Director of the Music Centre University of St Andrews 01334 462226/7 http://www.st-andrews.ac.uk/services/music - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] ALS-110 opl3 and mpu401 under 2.4.0-test10
I conceed. The opl3 pnp patch still stands. I will have to look again at why the sb driver wasn't finding the mpu. Sigh Mark Mark Hindley Director of the Music Centre University of St Andrews 01334 462226/7 http://www.st-andrews.ac.uk/services/music - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[BUG] ? ide-scsi 2.4.0-test11. Can't mount iso9660 cd
I can not mount an cd in either my cdrom or cdrw drives. Both are ide drives using scsi-ide emulation. During the mount the logs show: Nov 23 10:03:27 hindleyhome kernel: VFS: Disk change detected on device sr(11,0) Nov 23 10:03:29 hindleyhome kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Nov 23 10:03:29 hindleyhome kernel: ISO 9660 Extensions: RRIP_1991A Nov 23 10:05:38 hindleyhome kernel: I/O error: dev 0b:00, sector 0 Nov 23 10:05:38 hindleyhome kernel: I/O error: dev 0b:00, sector 0 Nov 23 10:05:38 hindleyhome kernel: MSDOS: Hardware sector size is 2048 Nov 23 10:05:38 hindleyhome kernel: I/O error: dev 0b:00, sector 0 Nov 23 10:05:38 hindleyhome kernel: FAT bread failed Nov 23 10:05:38 hindleyhome kernel: MSDOS: Hardware sector size is 2048 Nov 23 10:05:38 hindleyhome kernel: I/O error: dev 0b:00, sector 0 Nov 23 10:05:38 hindleyhome kernel: FAT bread failed The boot logs are: Nov 23 09:00:48 hindleyhome kernel: Linux version 2.4.0-test11 (root@HindleyHome) (gcc version 2.95.2 2220 (Debian GNU/Linux)) #59 Thu Nov 23 08:54:15 GMT 2000 (...) Nov 23 09:00:48 hindleyhome kernel: ide-cd: passing drive hdc to ide-scsi emulation. Nov 23 09:00:48 hindleyhome kernel: ide-cd: passing drive hdd to ide-scsi emulation. (...) Nov 23 09:00:48 hindleyhome kernel: SCSI subsystem driver Revision: 1.00 Nov 23 09:00:48 hindleyhome kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices Nov 23 09:00:48 hindleyhome kernel: Vendor: YAMAHAModel: CRW4416E Rev: 1.0h Nov 23 09:00:48 hindleyhome kernel: Type: CD-ROM ANSI SCSI revision: 02 Nov 23 09:00:48 hindleyhome kernel: Vendor: PIONEER Model: CD-ROM DR-A24XRev: 1.04 Nov 23 09:00:48 hindleyhome kernel: Type: CD-ROM ANSI SCSI revision: 02 Nov 23 09:00:48 hindleyhome kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 Nov 23 09:00:48 hindleyhome kernel: Detected scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0 Nov 23 09:00:48 hindleyhome kernel: sr0: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray Nov 23 09:00:48 hindleyhome kernel: Uniform CD-ROM driver Revision: 3.11 Nov 23 09:00:48 hindleyhome kernel: sr1: scsi3-mmc drive: 20x/20x xa/form2 cdda tray I have now reverted to test10 with the same setup and all works fine. Hope that is useful Mark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
kernel 2.2.17 build reboots
I have just spent a frustrating day trying to rebuild the 2.2.17 kernel for my new Debian potato installation. It configures and builds fine. I am using 'make bzdisk' and then booting from the resulting floppy. When the new kernel boots it just reboots itself. The screen flash is so brief that I can't see exactly how far it gets. ? about one full screen. The same result no matter how I configure the build except that i get a hang if I enable apm. I don't know how to gp about sorting this out. I am unsure if is a compilation problem (gcc 2.95.2), hardware fault or kernel bug. 430TX motherboard, AMD K6 200, 2 HDs, CDROM, CDRW, S3 Video, ALS100 sound, ISA modem. The stock 2.2.17 in potato runs beautifully. I love linux! I need to rebuild it to sort out my sound card and remove some of the excess bagagge. Any suggestions about where to go? How can I be sure the hardware is okay? How can I isolate what is causing the reboot? Thanks for any help Mark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: kernel 2.2.17 build rebootsy
>> When the new kernel boots it just reboots itself. The screen flash is so >> brief that I can't see exactly how far it gets. ? about one full screen. > >try configuring it for a lower processor (say, 486 to be conservative). Same, even for a 386, albeit a bit slower > >> The same result no matter how I configure the build except that i get a >> hang if I enable apm. > >do you mean that it boots fine without apm? > No, with apm it hangs at the IDE allocation after it has identified the PIIX4. I assume it doesn't get far enough to reboot. >> Any suggestions about where to go? How can I be sure the hardware is okay? >> How can I isolate what is causing the reboot? > >serial console, for one. I only have one machine, so I think that is out, although I am getting out of my depth here. What would I need? Mark Mark Hindley Director of the Music Centre University of St Andrews 01334 462226/7 http://www.st-andrews.ac.uk/services/music - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Kernel 2.2.17 reboots
No joy with specifying the memory size. I have 64MB. I have tried mem=64M and 32/16/8. Still just reboots. Any other suggestions? Mark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
kernel 2.2.17 and 2.4.0-test8 reboots
I was having trouble booting new builds of both 2.2.17 and 2.4.0-test8. They both boot as far as loop: registered device at major 7 PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio before spontaneously rebooting. Specifying ide or mem parameters made no difference. It was made stranger by the fact that the stock Debian 'potato' 2.2.17 image boots and runs fine. I have just managed to sort out a way of getting the new built kernels to boot. It confuses me even more, but I hope it make sense to someone out there. I was testing the builds by booting from a floppy (made with make bzdisk). My normal boot is from DOS with a config.sys/autoexec.bat boot menu and loadlin. If I copy the built vmlinuz images to DOS and boot them with loadlin automatically from autoexec.bat they go fine. However, if I enter the loadlin command line manually in DOS I get a reboot at the same point. I cannot see why entering the loadlin command manually is different from using autoexec.bat. I also can't really see why booting from a floppy should be that different from using loadlin/lilo. Does this make any sense at all? TIA for any thoughts Mark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
opl3 under 2.4.0-test10
I am trying to setup my ALS 110 soundcard under my build of kernel 2.4.0-test10. I have built in isapnp support and also the sb and opl3 drivers. The sb driver works fine other than complaining about a missing 16 bit DMA (which I understand is missing from the card anyway). I can play and record wav with no problems. I am still missing MIDI. However, even though I pass opl3=0x388 on the Kernel command line all I get is an isapnp panic. Am I doing something silly or is there a bug? Is it a sound driver or isapnp or kernel problem? While trying to locate the problem I could not get any response from /dev/sndstat. % cat /dev/sndstat cat: /dev/sndstat: No such device Is it not supported in 2.4.0? I can't find the same info in the /proc filesystem. The full dmesg extract that seems relevant is Linux version 2.4.0-test10 (root@HindleyHome) (gcc version 2.95.2 2220 (Debian GNU/Linux)) #26 Fri Nov 3 18:08:00 GMT 2000 YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft 1993-1996 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 sb: PnP Sound Chip detected sb: ALS110 isapnp panic: opl3 device not found sb: ISAPnP reports 'PnP Sound Chip' at i/o 0x220, irq 5, dma 3, 1 SB16: Bad or missing 16 bit DMA channel at 0x220 irq 5 dma 3,1 sb: 1 Soundblaster PnP card(s) found. Thanks for the help Mark - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: opl3 under 2.4.0-test10
>On Sat, 11 Nov 2000, Stephen Thomas wrote: > >> Mark Hindley wrote: >> > I am trying to setup my ALS 110 soundcard under my build of kernel >> > 2.4.0-test10. >> > >> > I have built in isapnp support and also the sb and opl3 drivers. >> > >> > However, even though I pass opl3=0x388 on the Kernel command line all >> > I get is an isapnp panic. >> >> CONFIG_SOUND_YM3812=y >> >> and I'm passing "opl3=0x388" to the driver. However, if I query >> what synth devices the driver supports, it only reports an >> AWE32-0.4.4 (RAM512k) sample device. I expect it report an FM synth >> device, too. I get the same (lack of) effect if I go via the >> adlib_card code, by saying "adlib=0x388". My investigations so >> far have shown that when opl3_detect() first tries to get the >> signature of the OPL3 device, it gets 0xff from the inb() (line >> 195 of drivers/sound/opl3.c in test11pre1), while the corresponding >> code in 2.2.18pre19 gets 0x00. > >Can you try resetting CONFIG_SOUND_YM3812 to m rather than y. I had a >similar problem and that is the workaround I came up with. I haven't >gone back and tried to see why it happened; maybe I need to. How does this relate to ALS 110? I have tried building the relevant drivers both as modules and built-in to the kernel. It seems to make no difference. Mark Hindley Director of the Music Centre University of St Andrews 01334 462226/7 http://www.st-andrews.ac.uk/services/music - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[PATCH] 3c59x, check return of pci_enable_device()
commit 36d139ccebba6a1082b743fbedb53c5a5097987c
Author: Mark Hindley <[EMAIL PROTECTED]>
Date: Sat Jul 21 22:56:08 2007 +0100
Check return of pci_enable_device in vortex_up().
Signed-off-by: Mark Hindley <[EMAIL PROTECTED]>
diff --git a/drivers/net/3c59x.c b/drivers/net/3c59x.c
index f26ca33..192e74b 100644
--- a/drivers/net/3c59x.c
+++ b/drivers/net/3c59x.c
@@ -1490,13 +1490,17 @@ vortex_up(struct net_device *dev)
struct vortex_private *vp = netdev_priv(dev);
void __iomem *ioaddr = vp->ioaddr;
unsigned int config;
- int i, mii_reg1, mii_reg5;
+ int i, mii_reg1, mii_reg5, err;
if (VORTEX_PCI(vp)) {
pci_set_power_state(VORTEX_PCI(vp), PCI_D0);/* Go active */
if (vp->pm_state_valid)
pci_restore_state(VORTEX_PCI(vp));
- pci_enable_device(VORTEX_PCI(vp));
+ err = pci_enable_device(VORTEX_PCI(vp));
+ if (err) {
+ printk(KERN_WARNING "%s: Could not enable device \n",
+ dev->name);
+ }
}
/* Before initializing select the active media port. */
-
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/
hang with CONFIG_MCYRIXIII
Hi,
I recently been trying 2.6.2{2,3} kernels on a box with a Via C3
processor. It was previously running 2.6.18 without problems. I have
been getting random hangs, sysrq unresponsive, nothing in logs or on
serial console. Require power cycle to reset. Take between a few minutes
and days to occur.
I have been trying to get to the bottom of it and have discovered that
it seems down to compiling these later kernels with CONFIG_MCYRIXIII. I
have now reverted to CONFIG_M586 and the kernels seem stable again.
I could do with some pointers on sorting out if this is a compiler or
kernel bug.
Thanks,
Mark
cat /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 7
model name : VIA Ezra
stepping: 10
cpu MHz : 399.000
cache size : 64 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 de tsc msr cx8 mtrr pge mmx 3dnow
bogomips: 800.58
clflush size: 32
gcc --version
gcc (GCC) 4.1.3 20070601 (prerelease) (Debian 4.1.2-12)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
ld -v
GNU ld (GNU Binutils for Debian) 2.17.50.20070426
Copyright 2007 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.23-rc5-c3
# Sat Sep 1 12:00:28 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
# CONFIG_HIGH_RES_TIMERS is not set
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_PARAVIRT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MCORE2 is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
CONFIG_MCYRIXIII=y
# CONFIG_MVIAC
[OOPS] 2.6.23-rc5 ? network/via-rhine [was: hang with CONFIG_MCYRIXIII]
I have now got an oops trace out of this box, which I presume has been
the cause of the previously observed hangs.
To my inexperienced eye it looks like it is related to via-rhine.
Thanks
Mark
BUG: unable to handle kernel NULL pointer dereference at virtual address
0025
printing eip:
c0259a57
*pde =
Oops: [#1]
PREEMPT
Modules linked in: nfs cpufreq_userspace nfsd exportfs lockd sunrpc ppdev lp ac
battery ipv6 sd_mod cpufreq_ondemand cpufreq_powersave longhaul af_packet
tcp_diag inetv
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010246 (2.6.23-rc5 #1)
EIP is at tcp_rto_min+0x8/0x12
eax: 00c8 ebx: c7ab1080 ecx: ffee edx:
esi: c7ab1080 edi: ebp: c9a24b20 esp: c0341dec
ds: 007b es: 007b fs: gs: 0033 ss: 0068
Process ssh (pid: 4928, ti=c0341000 task=c963cf90 task.ti=c35b9000)
Stack: c0259b1b c7ab1080 c7ab1080 c025a2e8 c030c8a0 c025b906 0080 0080
c022f433 cacde032 0001 28419aa8 731a8024 28419b18
c011ebc5 28419b18 0282 028b585b 0004 cceb3540
Call Trace:
[] tcp_rtt_estimator+0xba/0x100
[] tcp_ack_saw_tstamp+0x14/0x43
[] tcp_ack+0x6aa/0x1726
[] skb_checksum+0x49/0x289
[] local_bh_enable+0x5/0x8c
[] tcp_rcv_established+0x344/0x5ed
[] ip_route_input+0x3a/0xcdc
[] tcp_v4_do_rcv+0x27/0x31d
[] tcp_v4_rcv+0x71a/0x765
[] ip_local_deliver+0x159/0x1bf
[] ip_rcv+0x44e/0x47b
[] rb_insert_color+0x4c/0xad
[] ip_rcv+0x44e/0x47b
[] enqueue_entity+0x1d2/0x1f3
[] ip_rcv+0x0/0x47b
[] netif_receive_skb+0x30d/0x38e
[] rhine_napipoll+0x2a7/0x46d [via_rhine]
[] net_rx_action+0x85/0x171
[] __do_softirq+0x35/0x75
[] do_softirq+0x3e/0x8d
[] handle_level_irq+0x0/0xd0
[] irq_exit+0x29/0x62
[] do_IRQ+0x94/0xad
[] common_interrupt+0x23/0x30
===
Code: 00 8b 14 24 8b 82 8c 02 00 00 89 82 10 04 00 00 a1 e0 6e 2f c0 89 82 14
04 00 00 83 c4 0c 5b 5e 5f 5d c3 8b 50 44 b8 c8 00 00 00 42 25 20 74 03 8b
42 54 c3
EIP: [] tcp_rto_min+0x8/0x12 SS:ESP 0068:c0341dec
Kernel panic - not syncing: Fatal exception in interrupt
-
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 -mm 1/2] 3c59x: Fix uninitialized variable bug
On Tue, Sep 04, 2007 at 02:09:47PM +0530, Satyam Sharma wrote: > Hi Steffen, > > > On Tue, 4 Sep 2007, Steffen Klassert wrote: > > > On Tue, Sep 04, 2007 at 03:45:55AM +0530, Satyam Sharma wrote: > > > > > > drivers/net/3c59x.c: In function 'vortex_up': > > > drivers/net/3c59x.c:1495: warning: 'err' may be used uninitialized in > > > this function > > > > This came in with the recently applied > > 3c59x-check-return-of-pci_enable_device patch > > from Mark Hindley. I just compiled it on a PCI only machine so far, > > therefore I did > > not notice the warning yet. > > Hmm, the .config I built with had PCI=y as well. Probably a compiler > version difference -- Jeff also mentioned yesterday that some newer > GCC versions fail to warn about uninitialized variables cases. > Sorry, this is my bad. I have just checked: there is no warning with gcc 4.2 or 4.1, but 3.3 emits the warning. > > > > is a genuine bug. The function returns an uninitialized value of 'err' > > > back to the caller, which expects it to be 0 for success cases. Let's > > > fix this by explicitly initializing 'err' to zero. > > > > > > Signed-off-by: Satyam Sharma <[EMAIL PROTECTED]> > > Acked-by: Steffen Klassert <[EMAIL PROTECTED]> Acked-by: Mark Hindley <[EMAIL PROTECTED]> - 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 -mm 1/2] 3c59x: Fix uninitialized variable bug
On Tue, Sep 04, 2007 at 11:17:57AM +0200, Steffen Klassert wrote: > The only warning that I was able to trigger with gcc 4.2 is in the case of a > .config > without PCI support. In this case I get > > drivers/net/3c59x.c: In function 'vortex_up': > drivers/net/3c59x.c:1672: warning: 'err' is used uninitialized in this > function That should be fixed by Satyam's patch too. Mark - 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: hang with CONFIG_MCYRIXIII
Having established that the oops was not the cause of the hangs I have been observing with MCYRIXIII, could anyone suggest ways to track down if this is a compiler or kernel bug? I have just complied latest git (with tcp_input.c oops fix) With CONFIG_MCYRIXIII I got a hang with empty logs and nothing on the serial line, sysrq unresponsive after about 2 hours CONFIG_M586MMX has been solid gcc (GCC) 4.1.3 20070812 (prerelease) (Debian 4.1.2-15) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. GNU ld (GNU Binutils for Debian) 2.17.90.20070812 Copyright 2007 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) a later version. This program has absolutely no warranty. Mark Hindley Thanks, Mark - 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 -mm 1/2] 3c59x: Fix uninitialized variable bug
On Thu, Sep 06, 2007 at 03:25:55PM +0530, Satyam Sharma wrote:
> This is a GCC bug (regression, actually, as you've found out) -- no two
> ways about it. Although different from the kind Jeff mentioned couple days
> back -- that was about wising GCC up to false positives and /not/ emitting
> warnings. But here a genuine problem was not complained about, so this is
> more serious. Do you plan to open up a bug at gcc.gnu.org/bugzilla/ ?
>
Yes, I have just narrowed down a test case, which is remarkably simple!
int
main(int i)
{
int err;
if (i) {
err = 1;
}
return err;
}
Mark
-
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: [Linux-usb-users] [REGRESSION] 2.6.23-rc1: uhci_hcd. irq 4: nobody cared
On Sun, Jul 29, 2007 at 11:19:47AM -0400, Alan Stern wrote: > On Sun, 29 Jul 2007, Mark Hindley wrote: > > > Hi, > > > > I have just tried 2.6.23-rc1 on my Acer Aspire 1350. > > > > On boot I get the following error as the uhci_hcd module is loaded: > > > > Jul 28 18:23:20 mercury kernel: ACPI: PCI Interrupt :00:10.0[A] -> Link > > [LNKA] -> GSI 4 (level, low) -> IRQ 4 > > Jul 28 18:23:20 mercury kernel: uhci_hcd :00:10.0: UHCI Host Controller > > Jul 28 18:23:20 mercury kernel: uhci_hcd :00:10.0: new USB bus > > registered, assigned bus number 2 > > Jul 28 18:23:20 mercury kernel: irq 4: nobody cared (try booting with the > > "irqpoll" option) > > Did it work okay with older kernels? What does /proc/interrupts say in > both 2.6.23-rc1 and in a working kernel? No boot error with 2.6.22.1. On 2.6.22.1: CPU0 0: 12312XT-PIC-XTtimer 1:286XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 4:434XT-PIC-XTuhci_hcd:usb2, [EMAIL PROTECTED]::01:00.0 5: 2000XT-PIC-XTyenta, uhci_hcd:usb3, wifi0 6: 3XT-PIC-XTfloppy 7: 3XT-PIC-XTparport0 8: 4XT-PIC-XTrtc 9: 0XT-PIC-XTuhci_hcd:usb4, VIA82XX-MODEM, VIA8233 10:843XT-PIC-XTacpi 11: 0XT-PIC-XTehci_hcd:usb1 12:123XT-PIC-XTi8042 14: 10951XT-PIC-XTide0 15: 53XT-PIC-XTide1 NMI:770 LOC: 120091 ERR: 0 MIS: 0 On 2.6.23-rc1: CPU0 0: 8616XT-PIC-XTtimer 1:183XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 4: 8233XT-PIC-XTuhci_hcd:usb1, [EMAIL PROTECTED]::01:00.0 5: 4948XT-PIC-XTuhci_hcd:usb2, yenta, wifi0 6: 3XT-PIC-XTfloppy 7: 22XT-PIC-XTparport0 8: 4XT-PIC-XTrtc 9: 0XT-PIC-XTuhci_hcd:usb3, VIA82XX-MODEM, VIA8233 10:854XT-PIC-XTacpi 11: 0XT-PIC-XTehci_hcd:usb4 12:123XT-PIC-XTi8042 14: 12202XT-PIC-XTide0 15: 53XT-PIC-XTide1 NMI:809 LOC: 150284 ERR: 1 MIS: 0 Mark - 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/
[OOPS] 2.6.23.1 in ext2/pdflush (tainted)
I have just upgraded an old K6 200 box to 2.6.23.1. It has oopsed overnight. Unfortunately the kernel is tainted by madwifi modules. As it is used headless as a wireless router, I can't remove them, but the trace looks to be in the pdflush/ext2 code. Config attached. Let me know if you want more info. Thanks, Mark Oct 21 04:41:59 titan kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 0007 Oct 21 04:41:59 titan kernel: printing eip: Oct 21 04:41:59 titan kernel: c0177115 Oct 21 04:41:59 titan kernel: *pde = Oct 21 04:41:59 titan kernel: Oops: [#1] Oct 21 04:41:59 titan kernel: PREEMPT Oct 21 04:41:59 titan kernel: Modules linked in: apm nfs softdog nfsd exportfs lockd sunrpc autofs4 ipv6 act_police sch_ingress cls_u32 sch_sfq sch_cbq via_rhine bitrev crc32 af_packet 3c59x mii bridge llc wlan_wep wlan_scan_ap ath_rate_sample ath_pci wlan ath_hal(P) floppy uhci_hcd ohci_hcd ehci_hcd usbcore ipt_owner ipt_REDIRECT xt_ limit ipt_recent xt_state ipt_REJECT ipt_LOG xt_tcpudp ipt_MASQUERADE iptable_filter iptable_nat ip_tables nf_nat x_tables nf_conntrack_ftp nf_conntrack_ipv4 nf_conntra ck nls_iso8859_1 nls_cp437 vfat fat tcp_diag inet_diag genrtc Oct 21 04:41:59 titan kernel: CPU:0 Oct 21 04:41:59 titan kernel: EIP:0060:[bio_get_nr_vecs+26/50] Tainted: P VLI Oct 21 04:41:59 titan kernel: EFLAGS: 00010a03 (2.6.23.1-mk6 #1) Oct 21 04:41:59 titan kernel: EIP is at bio_get_nr_vecs+0x1a/0x32 Oct 21 04:41:59 titan kernel: eax: c3eeb681 ebx: c110 ecx: 0003 edx: 0cfe Oct 21 04:41:59 titan kernel: esi: c1045320 edi: ebp: 0001 esp: c1100dc4 Oct 21 04:41:59 titan kernel: ds: 007b es: 007b fs: gs: ss: 0068 Oct 21 04:41:59 titan kernel: Process pdflush (pid: 83, ti=c110 task=c10fe530 task.ti=c110) Oct 21 04:41:59 titan kernel: Stack: c1100f7c 000c c1100ee4 c1e9af10 c1e9ae7c 0001 c1100dfc Oct 21 04:41:59 titan kernel:c3eeb680 0302 c1113b00 c1100e90 Oct 21 04:41:59 titan kernel: 0001 09ec c1100ea0 0001 Oct 21 04:41:59 titan kernel: Call Trace: Oct 21 04:41:59 titan kernel: [write_cache_pages+348/613] write_cache_pages+0x15c/0x265 Oct 21 04:41:59 titan kernel: [__mpage_writepage+0/1174] __mpage_writepage+0x0/0x496 Oct 21 04:41:59 titan kernel: [ext2_writepages+0/10] ext2_writepages+0x0/0xa Oct 21 04:41:59 titan kernel: [mpage_writepages+66/93] mpage_writepages+0x42/0x5d Oct 21 04:41:59 titan kernel: [ext2_get_block+0/1274] ext2_get_block+0x0/0x4fa Oct 21 04:41:59 titan kernel: [do_writepages+32/48] do_writepages+0x20/0x30 Oct 21 04:41:59 titan kernel: [__writeback_single_inode+455/835] __writeback_single_inode+0x1c7/0x343 Oct 21 04:41:59 titan kernel: [update_curr+288/330] update_curr+0x120/0x14a Oct 21 04:41:59 titan kernel: [sync_sb_inodes+340/517] sync_sb_inodes+0x154/0x205 Oct 21 04:41:59 titan kernel: [writeback_inodes+103/206] writeback_inodes+0x67/0xce Oct 21 04:41:59 titan kernel: [pdflush+0/449] pdflush+0x0/0x1c1 Oct 21 04:41:59 titan kernel: [wb_kupdate+110/206] wb_kupdate+0x6e/0xce Oct 21 04:41:59 titan kernel: [pdflush+285/449] pdflush+0x11d/0x1c1 Oct 21 04:41:59 titan kernel: [wb_kupdate+0/206] wb_kupdate+0x0/0xce Oct 21 04:41:59 titan kernel: [kthread+54/92] kthread+0x36/0x5c Oct 21 04:41:59 titan kernel: [kthread+0/92] kthread+0x0/0x5c Oct 21 04:41:59 titan kernel: [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10 Oct 21 04:41:59 titan kernel: === Oct 21 04:41:59 titan kernel: Code: e9 46 ff ff ff 8b 44 24 10 83 c4 1c 5b 5e 5f 5d c3 8b 40 54 8b 50 38 8b 82 0c 01 00 00 0f b7 8a 14 01 00 00 0f b7 92 16 01 00 00 e0 09 05 ff 0f 00 00 c1 e8 0c 39 d1 7e 02 89 d1 39 c8 7e 02 Oct 21 04:41:59 titan kernel: EIP: [bio_get_nr_vecs+26/50] bio_get_nr_vecs+0x1a/0x32 SS:ESP 0068:c1100dc4 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23.1-mk6 # Sat Oct 20 09:21:34 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y # CONFIG_POSIX_MQUEUE is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set #
[OOPS] 2.6.23-rc5 in tcp/net/nfsd
This oops appeared over night on a box running 2.6.23-rc5 (recent with the tcp_input.c fix). I can't find a similar one reported. Mark BUG: unable to handle kernel NULL pointer dereference at virtual address 007e printing eip: c02625bf *pde = Oops: 0002 [#1] PREEMPT Modules linked in: softdog nfs cpufreq_userspace nfsd exportfs lockd sunrpc ppdev lp ac battery ipv6 cpufreq_ondemand cpufreq_powersave longhaul af_packet tcp_diag inev CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00010246 (2.6.23-rc5-2-mcyrixiii #1) EIP is at ip_fragment+0x7f/0x680 eax: c3c09c00 ebx: ecx: b524d006 edx: 007b esi: c1f77810 edi: c1f77e00 ebp: esp: ccb48b3c ds: 007b es: 007b fs: gs: ss: 0068 Process nfsd (pid: 2942, ti=ccb48000 task=cf78c530 task.ti=ccb48000) Stack: 0060 0060 c0262dd0 c3c09c00 c0382600 0158 05c8 0014 cbbc5424 0158 8b80 c1134a40 c3c09c00 cee8b780 c0382600 c0264115 0282 ceabbe40 0158 c026306c Call Trace: [] ip_finish_output2+0x0/0x1c0 [] ip_output+0xd5/0x290 [] ip_generic_getfrag+0x4c/0xa0 [] __ip_select_ident+0x58/0xc0 [] ip_push_pending_frames+0x2df/0x3a0 [] ip_generic_getfrag+0x0/0xa0 [] udp_push_pending_frames+0x2ab/0x2d0 [] udp_sendmsg+0x469/0x590 [] __ip_route_output_key+0x6f0/0x710 [] ip_append_data+0x4df/0x970 [] irq_exit+0x40/0x70 [] inet_sendmsg+0x3b/0x50 [] sock_sendmsg+0xbb/0xe0 [] autoremove_wake_function+0x0/0x40 [] inet_sendmsg+0x3b/0x50 [] kernel_sendmsg+0x27/0x40 [] sock_no_sendpage+0x5a/0x70 [] udp_sendpage+0xd6/0x130 [] nfsd_acceptable+0x0/0xd0 [nfsd] [] udp_sendpage+0x0/0x130 [] inet_sendpage+0x55/0x90 [] inet_sendpage+0x0/0x90 [] kernel_sendpage+0x3f/0x50 [] svc_sendto+0x1b3/0x280 [sunrpc] [] encode_post_op_attr+0x4a/0x60 [nfsd] [] __slab_free+0x55/0x280 [] svc_udp_sendto+0x11/0x30 [sunrpc] [] svc_send+0xb7/0x100 [sunrpc] [] svcauth_unix_release+0x3b/0x50 [sunrpc] [] nfs3svc_release_fhandle+0x0/0x10 [nfsd] [] svc_process+0x418/0x690 [sunrpc] [] svc_recv+0x35a/0x3d0 [sunrpc] [] nfsd+0x185/0x2a0 [nfsd] [] nfsd+0x0/0x2a0 [nfsd] [] kernel_thread_helper+0x7/0x10 === Code: 01 00 00 03 75 0e 8b 42 18 8b 40 0c 8b 80 c4 00 00 00 eb 0a 8b 4c 24 08 8b 41 18 8b 40 28 0f c8 89 04 24 8b 44 24 08 b9 04 00 00 <00> ba 03 00 00 00 bf a6 ff ff EIP: [] ip_fragment+0x7f/0x680 SS:ESP 0068:ccb48b3c - 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/
