Ok,
the naming should be familiar - it's the same deal as with 2.4.0.
One difference is that while 2.4.0 took about 7 months from the pre1 to
the final release, I hope (and believe) that we have fewer issues facing
us in the current 2.6.0. But very obviously there are going to be a
few test-releases before the real thing.
The point of the test versions is to make more people realize that they
need testing and get some straggling developers realizing that it's too
late to worry about the next big feature. I'm hoping that Linux vendors
will start offering the test kernels as installation alternatives, and
do things like make upgrade internal machines, so that when the real
2.6.0 does happen, we're all set.
Linus
---
Summary of changes from v2.5.75 to v2.6.0-test1
============================================
<jcchen:icplus.com.tw>:
o [netdrvr sundance] increase eeprom read timeout
<taowenhwa:intel.com>:
o [e100] cu_start: timeout waiting for cu
o [e100] misc
Alan Cox:
o genrtc sets owner fields so
o Remove bogus printk in microcode.c
o clean up floppy98 a bit
o dtlk comment fix
o isurf compile fix
o axnet can unload with timers live
o ibmtr can unload with timers live
o fix up nmclan locking and hang on eject at wrong moment
o fix further timer in pcmcia stuff
o Fix remaining g_NCR5380 use of check_region
o not sure what the author was on
o AC97 updates from 2.4
o Add the au1000 driver
o demo plugin for switching ad1980 ports Dell style
o Fix security leaks in btaudio
o Add the ALI5455 driver from 2.4
o fix security leaks in cmpci
o Update cs46xx in 2.5 to the newer 2.4 release
o fix the security leak in dmasound
o Switch the SB Live! to the new ac97 api
o fix security leaks and a crash in es1370
o bring es1371 in line with 2.4
o fix security leak and crash in esssolo
o Add Forte Media OSS driver
o update ITE audio
o update the i810 audio driver
o switch maestro3 to new ac97
o fix security leak in maestro.c
o fix security leak in msnd_pinnacle.c
o Add swarm driver for broadcom boards
o update nec driver to new ac97
o update trident driver for new ac97 etc
o fix wrong printk in nm256 audio
o update via audio driver, make it work on esd add new chips
o more wrong strlcpy's
o update ymfpci for new ac97
o Merge AD1889 driver from 2.4
Alan Stern:
o USB: Small correction to usb-skeleton.c
o USB: Updates for unusual_devs.h
Andi Kleen:
o Deprecate numerical sysctl
o x86-64 fixes for 2.5.75
Andrew Morton:
o fix return of compat_sys_sched_getaffinity
o remove proc_mknod()
o reiserfs dirty memory accounting fix
o fix reiserfs for 64bit arches
o wall_to_monotonic initialization fixes for
o i_size atomic access: infrastructure
o i_size atomic access
o kmap() -> kmap_atomic() in fs/exec.c
o make CONFIG_KALLSYMS default to "on"
o misc fixes
o Set umask correctly for nfsd kernel threads
o Bug fix in AIO initialization
o Fix race condition between aio_complete and
o separate locking for vfsmounts
o fix for CPU scheduler load distribution
o NBD: cosmetic cleanups
o nbd: enhanced diagnostics support
o nbd: remove unneeded blksize_bits field
o nbd: initialise the embedded kobject
o nbd: cleanup PARANOIA usage & code
o NBD documentation update
o nbd: remove unneeded nbd_open/nbd_release and refcnt
o nbd: make nbd and block layer agree about device and
o JBD: checkpointing optimisations
o JBD: transaction buffer accounting fix
o ext3: sync_fs() fix
o oom killer fixes
o yenta-socket initialisation fix
o Fix yenta-socket oops
o devfs oops fix
o devfs deadlock fix
o epoll-per-fd fix
Andries E. Brouwer:
o cryptoloop
Bernardo Innocenti:
o asm-generic/div64.h breakage
Brian Gerst:
o c99 initializers for init/version.c
Daniel Ritz:
o more net driver timer fixes
o net/pcmcia fix fast_poll timers (HZ > 100)
Dave Jones:
o [AGPGART] Remove unneeded assignment
o [AGPGART] Use defines for register bits in AMD K8 GART driver
o [AGPGART] K8 GART driver doesn't need masks
o [AGPGART] Ignore multiple K8 GARTS on UP
o [AGPGART] Optimise PCI searching in K8 GART driver
o [AGPGART] K8 Device 0x1103 is always at PCI_FUNC 3
o [AGPGART] K8 North bridge bus position is no longer relevant
o [AGPGART] HP AGP update
o [AGPGART] Sort SiS device IDs
o [AGPGART] SiS 746 support This (and a few other SiS chipsets) are
AGP 3 compliant. AFAIK, none of these have been tested in AGP3
mode, but they should work just fine in AGP2.x mode at least.
o [AGPGART] SiS 648 support
o [AGPGART] Make frontend sparse clean
David Brownell:
o USB: usb_get_string(), don't use bogus ids
o USB: usbnet, don't NET_XMIT_DROP
David S. Miller:
o [SPARC]: SEMTIMEDOP for both Sparc ports
o [SPARC64]: Port over IPC msg{snd,rcv} compat32 fixes from ia64
o [TCP]: When in SYN-SENT, initialize metrics after move to
established state
o [NET]: Ok, sunhme is VLAN challenged after all
o [IPV6]: Build and send redirect packet using "buff" not "skb",
fixes OOPS
o [IPV6]: Fix dst reference counting in ndisc_send_redirect()
o [NET,COMPAT]: Delete bogus icmpv6 filter translation code
o [IPV6]: Fix leaks of ndisc DST entries
o [SPARC64]: Ditch local KALLSYMS from Kconfig, update defconfig
o [SPARC64]: Implement force_successful_syscall()
o [SPARC64]: Use mm->free_area_cache
o [IPV4]: Do not redefine config macros in net/ip_vs.h
o [IPV4]: Always use Jenkins hash in ipvs conn table, use
get_random_bytes() to init key
o [IPV4]: Kill slow timers from IPVS, they are superfluous and
inefficient these days
David Stevens:
o [IPV4]: Do not sent IGMP leave messages unless IFF_UP
Dominik Brodowski:
o [PCMCIA] don't hide calls to socket drivers
o [PCMCIA] rename ss_entry to ops
Fran?ois Romieu:
o Fix AD1889 driver 2.4 merge
o Fix error path in AD1889 driver
Greg Kroah-Hartman:
o USB: fix up my USB Bluetooth entry to help prevent confusion in the
future
o USB: remove pointless warning about using usbdevfs
Herbert Xu:
o [IPSEC]: Missing reqid check in xfrm_state_ok
Hideaki Yoshifuji:
o [IPV6]: Fix offset of payload with extension header
Ian Abbott:
o USB: ftdi_sio update
James Morris:
o [NETLINK]: Just drop packets for kernel netlink socket with no
data_ready handler
Jean Tourrilhes:
o [IrDA] include cleanup
o [IrDA] struct check
o [IrDA] irtty leaks
o [IrDA] irnet cast
o [IrDA] IrCOMM devfs
o [IrDA] setup dma fix
o [IrDA] irda-usb endian
o [IrDA] nsc 39x support
Jeff Garzik:
o [netdrvr tg3] more ULL suffixes to make gcc 3.3 happy
o [netdrvr] fix compiler warnings in 3c359, proteon, skisa tokenring
drivers.
o [netdrvr wavelan] remove check_region usage
o [netdrvr atmel_cs] kill compiler warning (jumping to "empty" label)
Jens Axboe:
o disk stats accounting fix
o Fix IDE-CD command failure re-play
o fs accounting, part 2
Kay Sievers:
o usblp: usb_buffer_free() not called Here is the blind flight :-)
=== drivers/usb/class/usblp.c usblp->dev was set to NULL to
indicate a device disconnect but we need this value for
usb_buffer_free() when device is still opened and cleanup is
delayed until usblp_release().
Linus Torvalds:
o Avoid mmap() overflow case if TASK_SIZE is the full range of an
"unsigned long" (sparc64).
o Merge comment updates from DRI CVS tree
o Update i810 DRI driver from CVS to add page flipping
o Update r128 driver from DRI CVS: add support for ycbcr textures
o Update radeon driver from DRI CVS: add more commands
o Merge from DRI CVS tree: avoid zero DRI "handles"
o Merge with DRI CVS tree - which added a reminder to the DRI people
not to remove the HAVE_KERNEL_CTX_SWITCH support that the sparc
drivers require.
o Fix signedness tests in vsnprintf by making it explicit
o Mark Bartlomiej as the IDE maintainer, about 3 months late ;)
o Disable TI cardbus PCI IRQ routing code that was forward-ported
from 2.4-ac - it seems to cause hangs for people.
Matthew Dharm:
o USB: fix usb-storage initializers
o USB: fix datafab and freecom to use I/O buffer
Matthew Wilcox:
o parisc updates
o Makefile update for parisc
o eisa Kconfig update for parisc
o Add two sysctls for PA-RISC
o Remove warning from binfmt_elf.c for upwards growing stack
o gsc-ps2 update
Miles Bader:
o Use <asm-generic/statsfs.h> on v850
o More irqreturn_t changes for v850
o show_stack changes for v850
Nivedita Singhvi:
o [NET]: Fix typo in net-sysfs.c copyright
Pete Zaitcev:
o [SPARC]: Clean secondary System.map
o [SPARC]: defconfig for willy's scsi
o [SPARC]: hch's cond_syscall() for PCI syscalls, Alpha/PPC/etc. can
use this too
o [SPARC]: Redo show_stack()
o [SPARC]: Trap table alignment for Hyperspace (Keith Weselowsky)
Petr Sebor:
o via-agp.c - agp_try_unsupported typo
Petr Vandrovec:
o new sysctl checking accesses userspace directly
Ralf B?chle:
o mkiss
Richard Henderson:
o [ALPHA] Add tgkill syscall
o [ALPHA] Set correct CLOCK_TICK_RATE for the RTC
o [ALPHA] Remove SBUS & MCA from alpha Kconfig
Robert Zwerus:
o Documentation/CodingStyle spelling fixes
Russell King:
o [PCMCIA] Prevent PCMCIA oops during socket driver initialisation
o [PCMCIA] Fix hangs when PCMCIA modules loaded
Samuel Thibault:
o [2.5] maestro volume tuning
Stephen Hemminger:
o convert plip to alloc_netdev
o [netdrvr dgrs] convert to using alloc_etherdev
Steve French:
o NTLMv2 password support and NTLMSSP signing part 1
o ntlmssp signing
o More NTLMv2
o Open / Create lookup intents part one
o Add mknod support
o fix cifs distributed caching - send oplock release immediately
after flush of writebehind data on oplock break from server
Thomas Graf:
o [NET]: Return EDESTADDRREQ as appropriate in sendmsg
implementations
Ulrich Drepper:
o Re: utimes/futimes/lutimes syscalls
Wensong Zhang:
o [NET]: Merge in IPVS layer
On Sun, Jul 13, 2003 at 08:59:07PM -0700, Linus Torvalds wrote:
> The point of the test versions is to make more people realize that they
> need testing and get some straggling developers realizing that it's too
> late to worry about the next big feature. I'm hoping that Linux vendors
> will start offering the test kernels as installation alternatives, and
> do things like make upgrade internal machines, so that when the real
> 2.6.0 does happen, we're all set.
Just tried to build this for powerpc, needs at least the following trivial
patch to compile:
--- linux-2.5-ppc/arch/ppc/kernel/time.c~ 2003-07-14 13:15:17.000000000 +0200
+++ linux-2.5-ppc/arch/ppc/kernel/time.c 2003-07-14 13:18:02.000000000 +0200
@@ -244,7 +244,7 @@
time_t wtm_sec, new_sec = tv->tv_sec;
long wtm_nsec, new_nsec = tv->tv_nsec;
unsigned long flags;
- int tb_delta, new_nsec, new_sec;
+ int tb_delta;
if ((unsigned long)tv->tv_nsec >= NSEC_PER_SEC)
return -EINVAL;
Regards,
--
Jasper Spaans http://jsp.vs19.net/contact/
<== The only intuitive interface ever created was a ==>
<== nipple. ==>
On Sun, Jul 13, 2003 at 08:59:07PM -0700, Linus Torvalds wrote:
>
> Ok,
> the naming should be familiar - it's the same deal as with 2.4.0.
>
> One difference is that while 2.4.0 took about 7 months from the pre1 to
> the final release, I hope (and believe) that we have fewer issues facing
> us in the current 2.6.0. But very obviously there are going to be a
> few test-releases before the real thing.
>
> The point of the test versions is to make more people realize that they
> need testing and get some straggling developers realizing that it's too
> late to worry about the next big feature. I'm hoping that Linux vendors
> will start offering the test kernels as installation alternatives, and
> do things like make upgrade internal machines, so that when the real
> 2.6.0 does happen, we're all set.
In the meantime, what about a "running 2.6.0-test HOWTO"?
ie:
1. base distro you using right now for testing
2. which updates are needed for said distro (I assume modutils, any others?)
3. compiler to use
4. parts which should be abused without fears for data loss
5. parts which could eat disks, for those with separate desktop/test machines
6. whatever else you can think about
on a related note, from reading lkml I can see that in-tree ext3
is in good shape, what about reiser3 or reiser4?
>
> Linus
>
> [ BIIIIIIG SNIP ]
>
Greets, Antonio.
--
In fact, this is all you need to know to be
a Caveman Database Programmer:
A relational database is a big spreadsheet
that several people can update simultaneously.
Compile statistics: 2.6.0-test1
Compiler: gcc 3.2.2
Script: http://developer.osdl.org/~cherry/compile/compregress.sh
bzImage bzImage modules
(defconfig) (allmodconfig) (allmodconfig)
2.6.0-test1 0 warnings 8 warnings 1296 warnings
0 errors 9 errors 39 errors
2.5.75 0 warnings 8 warnings 1296 warnings
0 errors 9 errors 39 errors
Compile statistics have been for kernel releases from 2.5.46 to
2.6.0-test1 at: http://developer.osdl.org/~cherry/compile/
Failure summary:
drivers/block: 2 warnings, 1 errors
drivers/char: 226 warnings, 4 errors
drivers/isdn: 216 warnings, 5 errors
drivers/media: 102 warnings, 5 errors
drivers/mtd: 42 warnings, 1 errors
drivers/net: 293 warnings, 6 errors
drivers/net: 29 warnings, 6 errors
drivers/scsi: 109 warnings, 10 errors
drivers/scsi/aic7xxx: 0 warnings, 1 errors
drivers/video: 101 warnings, 3 errors
sound: 5 warnings, 3 errors
sound/oss: 55 warnings, 3 errors
Warning summary:
drivers/atm: 36 warnings, 0 errors
drivers/cdrom: 25 warnings, 0 errors
drivers/i2c: 3 warnings, 0 errors
drivers/ide: 28 warnings, 0 errors
drivers/md: 2 warnings, 0 errors
drivers/message: 1 warnings, 0 errors
drivers/pci: 1 warnings, 0 errors
drivers/pcmcia: 3 warnings, 0 errors
drivers/scsi/aacraid: 1 warnings, 0 errors
drivers/scsi/pcmcia: 5 warnings, 0 errors
drivers/scsi/sym53c8xx_2: 1 warnings, 0 errors
drivers/serial: 1 warnings, 0 errors
drivers/telephony: 9 warnings, 0 errors
drivers/video/aty: 3 warnings, 0 errors
drivers/video/matrox: 5 warnings, 0 errors
drivers/video/sis: 1 warnings, 0 errors
fs/afs: 1 warnings, 0 errors
fs/intermezzo: 1 warnings, 0 errors
fs/jffs: 1 warnings, 0 errors
fs/lockd: 4 warnings, 0 errors
fs/nfsd: 2 warnings, 0 errors
fs/smbfs: 2 warnings, 0 errors
net: 39 warnings, 0 errors
sound/isa: 3 warnings, 0 errors
John
I need this to build on powerpc (plus the patch by Jasper Spaans already posted).
Matt
diff -NruX /home/arashi/kdontdiff linux-2.6.0-test1-orig/drivers/cpufreq/proc_intf.c linux-2.6.0-test1/drivers/cpufreq/proc_intf.c
--- linux-2.6.0-test1-orig/drivers/cpufreq/proc_intf.c 2003-07-13 23:30:48.000000000 -0400
+++ linux-2.6.0-test1/drivers/cpufreq/proc_intf.c 2003-07-14 23:41:49.000000000 -0400
@@ -13,7 +13,6 @@
#include <asm/uaccess.h>
-#define CPUFREQ_ALL_CPUS ((NR_CPUS))
/**
* cpufreq_parse_policy - parse a policy string
diff -NruX /home/arashi/kdontdiff linux-2.6.0-test1-orig/include/linux/notifier.h linux-2.6.0-test1/include/linux/notifier.h
--- linux-2.6.0-test1-orig/include/linux/notifier.h 2003-07-13 23:30:36.000000000 -0400
+++ linux-2.6.0-test1/include/linux/notifier.h 2003-07-14 23:41:56.000000000 -0400
@@ -65,6 +65,7 @@
#define CPU_UP_CANCELED 0x0004 /* CPU (unsigned)v NOT coming up */
#define CPU_OFFLINE 0x0005 /* CPU (unsigned)v offline (still scheduling) */
#define CPU_DEAD 0x0006 /* CPU (unsigned)v dead */
+#define CPUFREQ_ALL_CPUS ((NR_CPUS))
#endif /* __KERNEL__ */
#endif /* _LINUX_NOTIFIER_H */
On Tue, Jul 15, 2003 at 12:11:32AM -0400, Matt Reppert wrote:
> I need this to build on powerpc (plus the patch by Jasper Spaans already posted).
> * cpufreq_parse_policy - parse a policy string
> diff -NruX /home/arashi/kdontdiff linux-2.6.0-test1-orig/include/linux/notifier.h linux-2.6.0-test1/include/linux/notifier.h
> --- linux-2.6.0-test1-orig/include/linux/notifier.h 2003-07-13 23:30:36.000000000 -0400
> +++ linux-2.6.0-test1/include/linux/notifier.h 2003-07-14 23:41:56.000000000 -0400
> @@ -65,6 +65,7 @@
> #define CPU_UP_CANCELED 0x0004 /* CPU (unsigned)v NOT coming up */
> #define CPU_OFFLINE 0x0005 /* CPU (unsigned)v offline (still scheduling) */
> #define CPU_DEAD 0x0006 /* CPU (unsigned)v dead */
> +#define CPUFREQ_ALL_CPUS ((NR_CPUS))
>
> #endif /* __KERNEL__ */
> #endif /* _LINUX_NOTIFIER_H */
include/linux/cpufreq.h seems a more natural place to put this.
Can you confirm that works ok on PPC? I lack hardware to test.
Otherwise, looks good.
Dave
On Tue, Jul 15, 2003 at 11:56:57AM +0100, Dave Jones wrote:
> On Tue, Jul 15, 2003 at 12:11:32AM -0400, Matt Reppert wrote:
> > I need this to build on powerpc (plus the patch by Jasper Spaans already posted).
>
> > * cpufreq_parse_policy - parse a policy string
> > diff -NruX /home/arashi/kdontdiff linux-2.6.0-test1-orig/include/linux/notifier.h linux-2.6.0-test1/include/linux/notifier.h
> > --- linux-2.6.0-test1-orig/include/linux/notifier.h 2003-07-13 23:30:36.000000000 -0400
> > +++ linux-2.6.0-test1/include/linux/notifier.h 2003-07-14 23:41:56.000000000 -0400
> > @@ -65,6 +65,7 @@
> > #define CPU_UP_CANCELED 0x0004 /* CPU (unsigned)v NOT coming up */
> > #define CPU_OFFLINE 0x0005 /* CPU (unsigned)v offline (still scheduling) */
> > #define CPU_DEAD 0x0006 /* CPU (unsigned)v dead */
> > +#define CPUFREQ_ALL_CPUS ((NR_CPUS))
> >
> > #endif /* __KERNEL__ */
> > #endif /* _LINUX_NOTIFIER_H */
>
> include/linux/cpufreq.h seems a more natural place to put this.
> Can you confirm that works ok on PPC? I lack hardware to test.
No, please don't do this. There is no function at all in the cpufreq core
which may be called with CPUFREQ_ALL_CPUS as arguments. Well, there had
been, many months ago. But it really shall not be defined or used anywhere
outside the 2.4. proc-intf any more.
Now, wrt the ppc-cpufreq driver: benh's 2.5. tree includes a much more
updated version than plain 2.6.0-test1 -- Ben, can you push that to Linus,
please? Also, please change the line
freqs.cpu = CPUFREQ_ALL_CPUS;
in do_set_cpu_speed() to
freqs.cpu = 0;
which is the way it should be done now.
Dominik
On Tue, Jul 15, 2003 at 07:38:44PM +0200, Dominik Brodowski wrote:
> No, please don't do this. There is no function at all in the cpufreq core
> which may be called with CPUFREQ_ALL_CPUS as arguments. Well, there had
> been, many months ago. But it really shall not be defined or used anywhere
> outside the 2.4. proc-intf any more.
ick, you're right of course.
> Now, wrt the ppc-cpufreq driver: benh's 2.5. tree includes a much more
> updated version than plain 2.6.0-test1 -- Ben, can you push that to Linus,
> please? Also, please change the line
> freqs.cpu = CPUFREQ_ALL_CPUS;
> in do_set_cpu_speed() to
> freqs.cpu = 0;
> which is the way it should be done now.
Ok, CPUFREQ_ALL_CPUS is no more in my pending tree.
Documentation/cpu-freq/core.txt is also out of date and could use
an update, but I'm not sure if its just that define thats out of date.
Care to give it a read through?
Dave
Here's a nice oops for you guys.
Hotplug is the trigger. I can't reproduce without hotplug.
hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
oopses for each driver with hotplug, but if I try without hotplug ('apt-get
remove hotplug' before rebooting), I can load all three usb drivers with no
oops.
I saw this on 2.5.70 also, but this is the first time I tried SAK after the
console hung during boot. After SAK, it continued booting, and I saved the
oops.
I can supply more info as needed, and test patches.
I'm running smp+preempt on a UP pII 450.
input: Logitech USB Mouse on usb-0000:00:07.2-2
drivers/usb/core/usb.c: registered new driver hiddev
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
Adding 262136k swap on /usr/swap_file. Priority:2 extents:38
Unable to handle kernel paging request at virtual address d493885c
printing eip:
c01d3bdd
*pde = 040ce067
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[<c01d3bdd>] Not tainted
EFLAGS: 00010292
EIP is at kobject_add+0x79/0xf4
eax: c03d2280 ebx: d49550c4 ecx: d493885c edx: d49550dc
esi: c03d2288 edi: c03d2224 ebp: d3731f34 esp: d3731f28
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 209, threadinfo=d3730000 task=c4216080)
Stack: d49550c4 d49550c4 00000000 d3731f4c c01d3c70 d49550c4 d49550c4 d49550c4
c03d2220 d3731f70 c0238d6f d49550c4 d49550c4 d4953a8a 00000014 d4955080
00000000 d4955120 d3731f7c c023912a d49550a8 d3731f94 c01d9ba0 d49550a8
Call Trace:
[<c01d3c70>] kobject_register+0x18/0x48
[<c0238d6f>] bus_add_driver+0x3f/0x8c
[<c023912a>] driver_register+0x36/0x3c
[<c01d9ba0>] pci_register_driver+0x74/0x9c
[<d48e401e>] init+0x1e/0x4c [ehci_hcd]
[<c01381c8>] sys_init_module+0x118/0x240
[<c0109af7>] syscall_call+0x7/0xb
Code: 89 11 8b 43 24 8b 38 8d 4f 44 89 c8 ba ff ff 00 00 f0 0f c1
<7>ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
SysRq : HELP : loglevel0-8 reBoot tErm kIll saK showMem powerOff showPc unRaw Sync showTasks Unmount
SysRq : SAK
SAK: killed process 13 (init): p->session==tty->session
SAK: killed process 14 (rcS): p->session==tty->session
SAK: killed process 205 (S36hotplug): p->session==tty->session
SAK: killed process 207 (usb.rc): p->session==tty->session
SAK: killed process 210 (modprobe): p->session==tty->session
Installing knfsd (copyright (C) 1996 [email protected]).
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
process `snmpd' is using obsolete setsockopt SO_BSDCOMPAT
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)
00:0e.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02)
00:10.0 VGA compatible controller: Number 9 Computer Company Imagine 128 T2R [Ticket to Ride]
On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> Here's a nice oops for you guys.
>
> Hotplug is the trigger. I can't reproduce without hotplug.
>
> hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> remove hotplug' before rebooting), I can load all three usb drivers with no
> oops.
If you just load these drivers by hand, does the oops happen?
Can you enable debugging in the kobject code, or the driver base code to
try to get some better debug messages of what is going on?
thanks,
greg k-h
On Tue, Jul 15, 2003 at 06:37:43PM -0700, Greg KH wrote:
> On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> > Here's a nice oops for you guys.
> >
> > Hotplug is the trigger. I can't reproduce without hotplug.
> >
> > hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> > oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> > remove hotplug' before rebooting), I can load all three usb drivers with no
> > oops.
>
> If you just load these drivers by hand, does the oops happen?
>
I didn't look into the hotplug scripts to see which hotplug modules (and
they are modules for me) were being loaded and in which order.
I did load the usb drivers by hand with no oops though.
> Can you enable debugging in the kobject code, or the driver base code to
> try to get some better debug messages of what is going on?
>
Please tell me which file that's in, and what I need to change, or give a
patch.
Thanks.
On Tue, Jul 15, 2003 at 06:46:50PM -0700, Mike Fedyk wrote:
> On Tue, Jul 15, 2003 at 06:37:43PM -0700, Greg KH wrote:
> > On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> > > Here's a nice oops for you guys.
> > >
> > > Hotplug is the trigger. I can't reproduce without hotplug.
> > >
> > > hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> > > oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> > > remove hotplug' before rebooting), I can load all three usb drivers with no
> > > oops.
> >
> > If you just load these drivers by hand, does the oops happen?
> >
>
> I didn't look into the hotplug scripts to see which hotplug modules (and
> they are modules for me) were being loaded and in which order.
It should just do:
modprobe -q ehci-hcd >/dev/null 2>&1
modprobe -q ohci-hcd >/dev/null 2>&1
modprobe -q uhci-hcd >/dev/null 2>&1
That's what the latest hotplug package has in it. I don't know what
Debian has lately...
> I did load the usb drivers by hand with no oops though.
That's really strange.
> > Can you enable debugging in the kobject code, or the driver base code to
> > try to get some better debug messages of what is going on?
> >
>
> Please tell me which file that's in, and what I need to change, or give a
> patch.
Here's a patch that I always run with. It is pretty verbose, but helps
me out a lot in debugging and development.
Let us know if it shows anything interesting.
thanks,
greg k-h
diff -Nru a/drivers/base/bus.c b/drivers/base/bus.c
--- a/drivers/base/bus.c Tue Jul 15 19:23:44 2003
+++ b/drivers/base/bus.c Tue Jul 15 19:23:44 2003
@@ -8,7 +8,7 @@
*
*/
-#undef DEBUG
+#define DEBUG 1
#include <linux/device.h>
#include <linux/module.h>
diff -Nru a/drivers/base/class.c b/drivers/base/class.c
--- a/drivers/base/class.c Tue Jul 15 19:24:11 2003
+++ b/drivers/base/class.c Tue Jul 15 19:24:11 2003
@@ -10,7 +10,7 @@
*
*/
-#undef DEBUG
+#define DEBUG 1
#include <linux/device.h>
#include <linux/module.h>
diff -Nru a/drivers/base/core.c b/drivers/base/core.c
--- a/drivers/base/core.c Tue Jul 15 19:23:45 2003
+++ b/drivers/base/core.c Tue Jul 15 19:23:45 2003
@@ -8,7 +8,7 @@
*
*/
-#undef DEBUG
+#define DEBUG 1
#include <linux/device.h>
#include <linux/err.h>
diff -Nru a/drivers/base/driver.c b/drivers/base/driver.c
--- a/drivers/base/driver.c Tue Jul 15 19:24:11 2003
+++ b/drivers/base/driver.c Tue Jul 15 19:24:11 2003
@@ -8,7 +8,7 @@
*
*/
-#undef DEBUG
+#define DEBUG 1
#include <linux/device.h>
#include <linux/module.h>
diff -Nru a/include/linux/usb.h b/include/linux/usb.h
diff -Nru a/lib/kobject.c b/lib/kobject.c
--- a/lib/kobject.c Tue Jul 15 19:23:44 2003
+++ b/lib/kobject.c Tue Jul 15 19:23:44 2003
@@ -10,7 +10,7 @@
* about using the kobject interface.
*/
-#undef DEBUG
+#define DEBUG
#include <linux/kobject.h>
#include <linux/string.h>
@@ -213,6 +213,7 @@
void kobject_init(struct kobject * kobj)
{
+ WARN_ON(atomic_read(&kobj->refcount));
atomic_set(&kobj->refcount,1);
INIT_LIST_HEAD(&kobj->entry);
kobj->kset = kset_get(kobj->kset);
@@ -379,6 +380,7 @@
atomic_inc(&kobj->refcount);
} else
ret = NULL;
+ WARN_ON((kobj != NULL) && (ret==NULL));
return ret;
}
On Tue, Jul 15, 2003 at 07:31:50PM -0700, Greg KH wrote:
> On Tue, Jul 15, 2003 at 06:46:50PM -0700, Mike Fedyk wrote:
> > On Tue, Jul 15, 2003 at 06:37:43PM -0700, Greg KH wrote:
> > > On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> > > > Here's a nice oops for you guys.
> > > >
> > > > Hotplug is the trigger. I can't reproduce without hotplug.
> > > >
> > > > hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> > > > oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> > > > remove hotplug' before rebooting), I can load all three usb drivers with no
> > > > oops.
> > >
> > > If you just load these drivers by hand, does the oops happen?
> > >
> >
> > I didn't look into the hotplug scripts to see which hotplug modules (and
> > they are modules for me) were being loaded and in which order.
>
> It should just do:
> modprobe -q ehci-hcd >/dev/null 2>&1
> modprobe -q ohci-hcd >/dev/null 2>&1
> modprobe -q uhci-hcd >/dev/null 2>&1
>
> That's what the latest hotplug package has in it. I don't know what
> Debian has lately...
>
> > I did load the usb drivers by hand with no oops though.
>
> That's really strange.
>
> > > Can you enable debugging in the kobject code, or the driver base code to
> > > try to get some better debug messages of what is going on?
> > >
> >
> > Please tell me which file that's in, and what I need to change, or give a
> > patch.
>
> Here's a patch that I always run with. It is pretty verbose, but helps
> me out a lot in debugging and development.
>
> Let us know if it shows anything interesting.
>
Ok, I only see it when the system is booting, and after looking at the
hotplug script in init.d there is different behaviour on boot, and on later
invocations.
I'm including dmesg output, and the hotplug script (hotplug has an exit at
the top so I can boot without uninstalling the package).
What else can I do?
Mike
On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> On Tue, Jul 15, 2003 at 07:31:50PM -0700, Greg KH wrote:
> > On Tue, Jul 15, 2003 at 06:46:50PM -0700, Mike Fedyk wrote:
> > > On Tue, Jul 15, 2003 at 06:37:43PM -0700, Greg KH wrote:
> > > > On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> > > > > Here's a nice oops for you guys.
> > > > >
> > > > > Hotplug is the trigger. I can't reproduce without hotplug.
> > > > >
> > > > > hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> > > > > oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> > > > > remove hotplug' before rebooting), I can load all three usb drivers with no
> > > > > oops.
> > > >
> > > > If you just load these drivers by hand, does the oops happen?
> > > >
> > >
> > > I didn't look into the hotplug scripts to see which hotplug modules (and
> > > they are modules for me) were being loaded and in which order.
> >
> > It should just do:
> > modprobe -q ehci-hcd >/dev/null 2>&1
> > modprobe -q ohci-hcd >/dev/null 2>&1
> > modprobe -q uhci-hcd >/dev/null 2>&1
> >
> > That's what the latest hotplug package has in it. I don't know what
> > Debian has lately...
> >
> > > I did load the usb drivers by hand with no oops though.
> >
> > That's really strange.
> >
> > > > Can you enable debugging in the kobject code, or the driver base code to
> > > > try to get some better debug messages of what is going on?
> > > >
> > >
> > > Please tell me which file that's in, and what I need to change, or give a
> > > patch.
> >
> > Here's a patch that I always run with. It is pretty verbose, but helps
> > me out a lot in debugging and development.
> >
> > Let us know if it shows anything interesting.
> >
> Ok, I only see it when the system is booting, and after looking at the
> hotplug script in init.d there is different behaviour on boot, and on later
> invocations.
Ok, here are some more files it is referencing to:
On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> Ok, I only see it when the system is booting, and after looking at the
> hotplug script in init.d there is different behaviour on boot, and on later
> invocations.
This is really wierd. I can't see anything strange in your logs, until
the oops :)
I also can't duplicate it here myself, sorry, I don't really have any
ideas.
greg k-h
On Thu, Jul 17, 2003 at 07:31:41PM -0700, Greg KH wrote:
> On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> > Ok, I only see it when the system is booting, and after looking at the
> > hotplug script in init.d there is different behaviour on boot, and on later
> > invocations.
>
> This is really wierd. I can't see anything strange in your logs, until
> the oops :)
It looks like it's a bug in the core code because when I was testing 2.5.70,
it was on a athlon XP pr2600, and the via-rhine module oopsed (because it
was started before the usb modules), and then it would hang.
I didn't report it because I wasn't able to capture the oops. :(
I'll do more to try to reproduce manually without the hotplug scripts.
(I'll bet it has something to do with one of the hotplug modules being
loaded).
Mike
On Thu, Jul 17, 2003 at 07:31:41PM -0700, Greg KH wrote:
> On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> > Ok, I only see it when the system is booting, and after looking at the
> > hotplug script in init.d there is different behaviour on boot, and on later
> > invocations.
>
> This is really wierd. I can't see anything strange in your logs, until
> the oops :)
>
> I also can't duplicate it here myself, sorry, I don't really have any
> ideas.
Ok, I was going through some of my logs, and I came across this one, which
is a little different.
Maybe it will help some...
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
Unable to handle kernel paging request at virtual address d492e85c
printing eip:
c01d3bdd
*pde = 040ce067
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[kobject_add+121/244] Not tainted
EFLAGS: 00010292
EIP is at kobject_add+0x79/0xf4
eax: c03d2280 ebx: d4970184 ecx: d492e85c edx: d497019c
esi: c03d2288 edi: c03d2224 ebp: d2e13f34 esp: d2e13f28
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 253, threadinfo=d2e12000 task=d3e28080)
Stack: d4970184 d4970184 00000000 d2e13f4c c01d3c70 d4970184 d4970184 d4970184
c03d2220 d2e13f70 c0238d6f d4970184 d4970184 d496ea1a 00000014 d4970140
00000000 d49701e0 d2e13f7c c023912a d4970168 d2e13f94 c01d9ba0 d4970168
Call Trace:
[kobject_register+24/72] kobject_register+0x18/0x48
[bus_add_driver+63/140] bus_add_driver+0x3f/0x8c
[driver_register+54/60] driver_register+0x36/0x3c
[pci_register_driver+116/156] pci_register_driver+0x74/0x9c
[_end+340077356/1068944012] uhci_hcd_init+0xa0/0x10b [uhci_hcd]
[sys_init_module+280/576] sys_init_module+0x118/0x240
[syscall_call+7/11] syscall_call+0x7/0xb
Code: 89 11 8b 43 24 8b 38 8d 4f 44 89 c8 ba ff ff 00 00 f0 0f c1
<7>ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
SysRq : Emergency Sync
Emergency Sync complete
SysRq : Emergency Remount R/O
Unable to handle kernel paging request at virtual address d493885c
printing eip:
c01d3bdd
*pde = 040ce067
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[kobject_add+121/244] Not tainted
EFLAGS: 00010292
EIP is at kobject_add+0x79/0xf4
eax: c03d2280 ebx: d49550c4 ecx: d493885c edx: d49550dc
esi: c03d2288 edi: c03d2224 ebp: d3731f34 esp: d3731f28
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 209, threadinfo=d3730000 task=c4216080)
Stack: d49550c4 d49550c4 00000000 d3731f4c c01d3c70 d49550c4 d49550c4 d49550c4
c03d2220 d3731f70 c0238d6f d49550c4 d49550c4 d4953a8a 00000014 d4955080
00000000 d4955120 d3731f7c c023912a d49550a8 d3731f94 c01d9ba0 d49550a8
Call Trace:
[kobject_register+24/72] kobject_register+0x18/0x48
[bus_add_driver+63/140] bus_add_driver+0x3f/0x8c
[driver_register+54/60] driver_register+0x36/0x3c
[pci_register_driver+116/156] pci_register_driver+0x74/0x9c
[_end+340077226/1068944012] init+0x1e/0x4c [ehci_hcd]
[sys_init_module+280/576] sys_init_module+0x118/0x240
[syscall_call+7/11] syscall_call+0x7/0xb
Code: 89 11 8b 43 24 8b 38 8d 4f 44 89 c8 ba ff ff 00 00 f0 0f c1
<7>ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
SysRq : HELP : loglevel0-8 reBoot tErm kIll saK showMem powerOff showPc unRaw Sync showTasks Unmount
SysRq : SAK
SAK: killed process 13 (init): p->session==tty->session
SAK: killed process 14 (rcS): p->session==tty->session
SAK: killed process 205 (S36hotplug): p->session==tty->session
SAK: killed process 207 (usb.rc): p->session==tty->session
SAK: killed process 210 (modprobe): p->session==tty->session
Installing knfsd (copyright (C) 1996 [email protected]).
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
RPC: sendmsg returned error 101
kobject ehci_hcd: registering. parent: <NULL>, set: drivers
Unable to handle kernel paging request at virtual address d493885c
printing eip:
c01d3cb7
*pde = 040ce067
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[kobject_add+163/292] Not tainted
EFLAGS: 00010292
EIP is at kobject_add+0xa3/0x124
eax: c03d2980 ebx: d49550c4 ecx: d493885c edx: d49550dc
esi: c03d2988 edi: c03d2924 ebp: d3ae3f28 esp: d3ae3f1c
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 209, threadinfo=d3ae2000 task=d39612e0)
Stack: d49550c4 d49550c4 00000000 d3ae3f40 c01d3d50 d49550c4 d49550c4 d49550c4
c03d2920 d3ae3f70 c0238f2e d49550c4 d49550c4 d4953a8a 00000014 c036001c
c0341452 d4953a8a d4955080 00000000 d4955120 d3ae3f7c c023931a d49550a8
Call Trace:
[kobject_register+24/72] kobject_register+0x18/0x48
[bus_add_driver+82/160] bus_add_driver+0x52/0xa0
[driver_register+54/60] driver_register+0x36/0x3c
[pci_register_driver+116/156] pci_register_driver+0x74/0x9c
[_end+340077226/1068944012] init+0x1e/0x4c [ehci_hcd]
[sys_init_module+280/576] sys_init_module+0x118/0x240
[syscall_call+7/11] syscall_call+0x7/0xb
Code: 89 11 8b 43 24 8b 38 8d 4f 44 89 c8 ba ff ff 00 00 f0 0f c1
<7>ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
bus pci: add driver ohci-hcd
kobject ohci-hcd: registering. parent: <NULL>, set: drivers
SysRq : HELP : loglevel0-8 reBoot tErm kIll saK showMem powerOff showPc unRaw Sync showTasks Unmount
SysRq : SAK
SAK: killed process 13 (init): p->session==tty->session
SAK: killed process 14 (rcS): p->session==tty->session
SAK: killed process 205 (S36hotplug): p->session==tty->session
SAK: killed process 207 (usb.rc): p->session==tty->session
SAK: killed process 210 (modprobe): p->session==tty->session
Installing knfsd (copyright (C) 1996 [email protected]).
On Tue, Jul 29, 2003 at 11:02:09AM -0700, Mike Fedyk wrote:
> On Thu, Jul 17, 2003 at 07:31:41PM -0700, Greg KH wrote:
> > On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> > > Ok, I only see it when the system is booting, and after looking at the
> > > hotplug script in init.d there is different behaviour on boot, and on later
> > > invocations.
> >
> > This is really wierd. I can't see anything strange in your logs, until
> > the oops :)
> >
> > I also can't duplicate it here myself, sorry, I don't really have any
> > ideas.
>
> Ok, I was going through some of my logs, and I came across this one, which
> is a little different.
>
> Maybe it will help some...
I have added "set -x" to the init scripts, and here is the output.
I'm not sure if it'll help, since it looks pretty normal to me (just a bunch
of variable changes and etc, nothing special).
/etc/init.d/hotplug:
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ test -x /sbin/hotplug
+ echo -n 'Starting hotplug subsystem:'
Starting hotplug subsystem:+ '[' S = S ']'
+ touch /etc/nohotplug
+ echo /sbin/hotplug
+ '[' S '!=' S ']'
+ basename=usb.rc
+ name=usb
+ echo -n ' usb'
usb+ /etc/hotplug/usb.rc start
/etc/hotplug/usb.rc:
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ unset I_WANT_A_BROKEN_PS
+ PS_PERSONALITY=linux
+ STATIC_MODULE_LIST=
+ X11_USBMICE_HACK=false
+ '[' -f /etc/default/hotplug ']'
+ . /etc/default/hotplug
++ USBD_ENABLE=true
++ STATIC_MODULE_LIST=
++ X11_USBMICE_HACK=false
+ MOUSE_MODULES=mousedev input
+ '[' false = true ']'
+ maybe_start_usb
+ local COUNT SYNTHESIZE
+ COUNT=0
+ SYNTHESIZE=true
+ '[' '!' -d /proc/bus/usb ']'
+ modprobe -q usbcore
+ '[' -d /proc/bus/usb ']'
+ '[' '!' -f /proc/bus/usb/devices ']'
+ modprobe -q ehci-hcd
/etc/hotplug/usb.rc: line 382: 260 Segmentation fault modprobe -q ehci-hcd >/dev/null 2>&1
+ modprobe -q ohci-hcd
Here is the kksymoops output:
Unable to handle kernel paging request at virtual address d494989c
printing eip:
c01d7f7d
*pde = 040d0067
Oops: 0002 [#1]
PREEMPT SMP
CPU: 0
EIP: 0060:[kobject_add+121/244] Not tainted VLI
EFLAGS: 00010296
EIP is at kobject_add+0x79/0xf4
eax: c039b2c0 ebx: d495e144 ecx: d494989c edx: d495e15c
esi: c039b2c8 edi: c039b264 ebp: d35c3f34 esp: d35c3f28
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 260, threadinfo=d35c2000 task=d35c5940)
Stack: d495e144 d495e144 00000000 d35c3f4c c01d8010 d495e144 d495e144 d495e144
c039b260 d35c3f70 c022574f d495e144 d495e144 d495cb0a 00000014 d495e100
00000000 d495e1a0 d35c3f7c c0225b0a d495e128 d35c3f94 c01de234 d495e128
Call Trace:
[kobject_register+24/72] kobject_register+0x18/0x48
[bus_add_driver+63/140] bus_add_driver+0x3f/0x8c
[driver_register+54/60] driver_register+0x36/0x3c
[pci_register_driver+116/152] pci_register_driver+0x74/0x98
[_end+340150886/1069206088] init+0x1e/0x4c [ehci_hcd]
[sys_init_module+288/584] sys_init_module+0x120/0x248
[syscall_call+7/11] syscall_call+0x7/0xb
Code: 00 85 f6 75 11 8b 43 24 83 c0 10 50 e8 81 01 00 00 89 c6 83 c4 04 8b 43 24 83 c0 08 8d 53 18 8b 48 04 89 50 04 89 43 18 89 4a 04 <89> 11 8b 43 24 8b 38 8d 4f 44 89 c8 ba ff ff 00 00 f0 0f c1 10
<7>ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci-hcd: block sizes: ed 64 td 64
SysRq : HELP : loglevel0-8 reBoot tErm kIll saK showMem powerOff showPc unRaw Sync showTasks Unmount
SysRq : Kill All Tasks
Is ksymoops reliable with 2.6 kernels? Its output is different...
ksymoops 2.4.8 on i686 2.6.0-test2-mm1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.0-test2-mm1/ (default)
-m /boot/System.map-2.6.0-test2-mm1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address d494989c
c01d7f7d
*pde = 040d0067
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[kobject_add+121/244] Not tainted VLI
EFLAGS: 00010296
eax: c039b2c0 ebx: d495e144 ecx: d494989c edx: d495e15c
esi: c039b2c8 edi: c039b264 ebp: d35c3f34 esp: d35c3f28
ds: 007b es: 007b ss: 0068
Stack: d495e144 d495e144 00000000 d35c3f4c c01d8010 d495e144 d495e144 d495e144
c039b260 d35c3f70 c022574f d495e144 d495e144 d495cb0a 00000014 d495e100
00000000 d495e1a0 d35c3f7c c0225b0a d495e128 d35c3f94 c01de234 d495e128
Call Trace:
Warning (Oops_read): Code line not seen, dumping what data is available
>>eax; c039b2c0 <pci_bus_type+60/ec>
>>ebx; d495e144 <_end+1450cb8c/3fbaca48>
>>ecx; d494989c <_end+144f82e4/3fbaca48>
>>edx; d495e15c <_end+1450cba4/3fbaca48>
>>esi; c039b2c8 <pci_bus_type+68/ec>
>>edi; c039b264 <pci_bus_type+4/ec>
>>ebp; d35c3f34 <_end+1317297c/3fbaca48>
>>esp; d35c3f28 <_end+13172970/3fbaca48>
Code: 00 85 f6 75 11 8b 43 24 83 c0 10 50 e8 81 01 00 00 89 c6 83 c4 04 8b 43 24 83 c0 08 8d 53 18 8b 48 04 89 50 04 89 43 18 89 4a 04 <89> 11 8b 43 24 8b 38 8d 4f 44 89 c8 ba ff ff 00 00 f0 0f c1 10
Using defaults from ksymoops -t elf32-i386 -a i386
Code; ffffffd5 <__kernel_rt_sigreturn+1b95/????>
00000000 <_EIP>:
Code; ffffffd5 <__kernel_rt_sigreturn+1b95/????>
0: 00 85 f6 75 11 8b add %al,0x8b1175f6(%ebp)
Code; ffffffdb <__kernel_rt_sigreturn+1b9b/????>
6: 43 inc %ebx
Code; ffffffdc <__kernel_rt_sigreturn+1b9c/????>
7: 24 83 and $0x83,%al
Code; ffffffde <__kernel_rt_sigreturn+1b9e/????>
9: c0 10 50 rclb $0x50,(%eax)
Code; ffffffe1 <__kernel_rt_sigreturn+1ba1/????>
c: e8 81 01 00 00 call 192 <_EIP+0x192>
Code; ffffffe6 <__kernel_rt_sigreturn+1ba6/????>
11: 89 c6 mov %eax,%esi
Code; ffffffe8 <__kernel_rt_sigreturn+1ba8/????>
13: 83 c4 04 add $0x4,%esp
Code; ffffffeb <__kernel_rt_sigreturn+1bab/????>
16: 8b 43 24 mov 0x24(%ebx),%eax
Code; ffffffee <__kernel_rt_sigreturn+1bae/????>
19: 83 c0 08 add $0x8,%eax
Code; fffffff1 <__kernel_rt_sigreturn+1bb1/????>
1c: 8d 53 18 lea 0x18(%ebx),%edx
Code; fffffff4 <__kernel_rt_sigreturn+1bb4/????>
1f: 8b 48 04 mov 0x4(%eax),%ecx
Code; fffffff7 <__kernel_rt_sigreturn+1bb7/????>
22: 89 50 04 mov %edx,0x4(%eax)
Code; fffffffa <__kernel_rt_sigreturn+1bba/????>
25: 89 43 18 mov %eax,0x18(%ebx)
Code; fffffffd <__kernel_rt_sigreturn+1bbd/????>
28: 89 4a 04 mov %ecx,0x4(%edx)
Code; 00000000 Before first symbol
2b: 89 11 mov %edx,(%ecx)
Code; 00000002 Before first symbol
2d: 8b 43 24 mov 0x24(%ebx),%eax
Code; 00000005 Before first symbol
30: 8b 38 mov (%eax),%edi
Code; 00000007 Before first symbol
32: 8d 4f 44 lea 0x44(%edi),%ecx
Code; 0000000a Before first symbol
35: 89 c8 mov %ecx,%eax
Code; 0000000c Before first symbol
37: ba ff ff 00 00 mov $0xffff,%edx
Code; 00000011 Before first symbol
3c: f0 0f c1 10 lock xadd %edx,(%eax)
2 warnings and 1 error issued. Results may not be reliable.