* Kernel Question
@ 2000-08-09 2:35 Assem Salama
0 siblings, 0 replies; 4+ messages in thread
From: Assem Salama @ 2000-08-09 2:35 UTC (permalink / raw)
To: linux-mm
I am runing RedHat 6.2, kernel version: 2.2.14-5.0
I have a couple of questions:
When I try to use ioremap, it gives me an undefined refernce. So, I
ended up using __ioremap. Is this the right way? Am I missing something?
same thing happened with memcpy, and virt_to_phys.
Also, I have a PCI board with 16MB of onboard memory. I got the
driver to probe the device and everything. I used __ioremap to remap the
PCI memory into virtual memory and I can read and write to it in kernel
space. Now, I want to be able to do that through user space. So, I
implemented mmap into my driver. I use remap_page_range with the
following arguments:
in init_mdoule()
myri_phys = (unsigned long) dev->base_address[0] &
PCI_BASE_ADDRESS_MEM_MASK;
...
in mydrv_mmap()
remap_page_range(vmP->vm_start, myri_phys,16*1024*1024 /* 16MB */,
vmP->vm_page_prot)
however, when I call mmap from user space, the machine either hangs or
completely reboots.
Any help would be greatly appreciated.
Sincerely,
Assem Salama
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
^ permalink raw reply [flat|nested] 4+ messages in thread
* kernel question
@ 2002-12-13 17:29 Joe Gofton
2002-12-13 19:16 ` Steve Brueggeman
0 siblings, 1 reply; 4+ messages in thread
From: Joe Gofton @ 2002-12-13 17:29 UTC (permalink / raw)
To: linux-kernel
I get this after I install a new kernel. 2.4.19 or 2.4.20. This doesn't
happen with 2.4.18. Is this bad?
Dec 1 11:10:32 ns1 kernel: SCSI subsystem driver Revision: 1.00
Dec 1 11:10:32 ns1 kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
DRIVER, Rev 6.2.8
Dec 1 11:10:32 ns1 kernel: <Adaptec 2940 Ultra2 SCSI adapter>
Dec 1 11:10:32 ns1 kernel: aic7890/91: Ultra2 Wide Channel A,
SCSI Id=7, 32/253 SCBs
Dec 1 11:10:32 ns1 kernel:
Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
Rev: 0230
Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
ANSI SCSI revision: 03
Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
Rev: 0230
Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
ANSI SCSI revision: 03
Dec 1 11:10:32 ns1 kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 253
Dec 1 11:10:32 ns1 kernel: scsi0:A:1:0: Tagged Queuing enabled. Depth 253
Dec 1 11:10:32 ns1 kernel: scsi: <fdomain> Detection failed (no card)
Dec 1 11:10:32 ns1 kernel: PCI: Enabling device 00:09.0 (0006 -> 0007)
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: agpgart: Detected Via Apollo Pro chipset
Dec 1 11:10:32 ns1 kernel: agpgart: AGP aperture is 64M @ 0xd0000000
Dec 1 11:10:32 ns1 kernel: Highpoint HPT370 Softwareraid driver for linux
version 0.01
Dec 1 11:10:32 ns1 kernel: No raid array found
Dec 1 11:10:32 ns1 kernel: SCSI subsystem driver Revision: 1.00
Dec 1 11:10:32 ns1 kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
DRIVER, Rev 6.2.8
Dec 1 11:10:32 ns1 kernel: <Adaptec 2940 Ultra2 SCSI adapter>
Dec 1 11:10:32 ns1 kernel: aic7890/91: Ultra2 Wide Channel A,
SCSI Id=7, 32/253 SCBs
Dec 1 11:10:32 ns1 kernel:
Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
Rev: 0230
Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
ANSI SCSI revision: 03
Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
Rev: 0230
Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
ANSI SCSI revision: 03
Dec 1 11:10:32 ns1 kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 253
Dec 1 11:10:32 ns1 kernel: scsi0:A:1:0: Tagged Queuing enabled. Depth 253
Dec 1 11:10:32 ns1 kernel: scsi: <fdomain> Detection failed (no card)
Dec 1 11:10:32 ns1 kernel: PCI: Enabling device 00:09.0 (0006 -> 0007)
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
Dec 1 11:10:32 ns1 kernel: Attached scsi disk sda at scsi0, channel 0, id
0, lun 0
Dec 1 11:10:32 ns1 kernel: Attached scsi disk sdb at scsi0, channel 0, id
1, lun 0
Dec 1 11:10:32 ns1 kernel: (scsi0:A:0): 80.000MB/s transfers (40.000MHz,
offset 63, 16bit)
Dec 1 11:10:32 ns1 kernel: SCSI device sda: 35861388 512-byte hdwr
sectors (18361 MB)
Dec 1 11:10:32 ns1 kernel: Partition check:
Dec 1 11:10:32 ns1 kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
Dec 1 11:10:32 ns1 kernel: (scsi0:A:1): 80.000MB/s transfers (40.000MHz,
offset 63, 16bit)
Dec 1 11:10:32 ns1 kernel: SCSI device sdb: 35861388 512-byte hdwr
sectors (18361 MB)
Dec 1 11:10:32 ns1 kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: kernel question
2002-12-13 17:29 kernel question Joe Gofton
@ 2002-12-13 19:16 ` Steve Brueggeman
0 siblings, 0 replies; 4+ messages in thread
From: Steve Brueggeman @ 2002-12-13 19:16 UTC (permalink / raw)
To: jgofton; +Cc: linux-kernel
You didn't include the beginning of the dmesg.
Is this by chance a VIA KT-400 based motherboard???
If so, disable the APIC in the BIOS, and 2.4.19+ should boot OK
Just a thought.
Steve Brueggeman
On Fri, 13 Dec 2002 13:29:12 -0400 (AST), you wrote:
>I get this after I install a new kernel. 2.4.19 or 2.4.20. This doesn't
>happen with 2.4.18. Is this bad?
>
>
>Dec 1 11:10:32 ns1 kernel: SCSI subsystem driver Revision: 1.00
>Dec 1 11:10:32 ns1 kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
>DRIVER, Rev 6.2.8
>Dec 1 11:10:32 ns1 kernel: <Adaptec 2940 Ultra2 SCSI adapter>
>Dec 1 11:10:32 ns1 kernel: aic7890/91: Ultra2 Wide Channel A,
>SCSI Id=7, 32/253 SCBs
>Dec 1 11:10:32 ns1 kernel:
>Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
>Rev: 0230
>Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
>ANSI SCSI revision: 03
>Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
>Rev: 0230
>Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
>ANSI SCSI revision: 03
>Dec 1 11:10:32 ns1 kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 253
>Dec 1 11:10:32 ns1 kernel: scsi0:A:1:0: Tagged Queuing enabled. Depth 253
>Dec 1 11:10:32 ns1 kernel: scsi: <fdomain> Detection failed (no card)
>Dec 1 11:10:32 ns1 kernel: PCI: Enabling device 00:09.0 (0006 -> 0007)
>Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
>Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
>Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
>Dec 1 11:10:32 ns1 kernel: agpgart: Detected Via Apollo Pro chipset
>Dec 1 11:10:32 ns1 kernel: agpgart: AGP aperture is 64M @ 0xd0000000
>Dec 1 11:10:32 ns1 kernel: Highpoint HPT370 Softwareraid driver for linux
>version 0.01
>Dec 1 11:10:32 ns1 kernel: No raid array found
>Dec 1 11:10:32 ns1 kernel: SCSI subsystem driver Revision: 1.00
>Dec 1 11:10:32 ns1 kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
>DRIVER, Rev 6.2.8
>Dec 1 11:10:32 ns1 kernel: <Adaptec 2940 Ultra2 SCSI adapter>
>Dec 1 11:10:32 ns1 kernel: aic7890/91: Ultra2 Wide Channel A,
>SCSI Id=7, 32/253 SCBs
>Dec 1 11:10:32 ns1 kernel:
>Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
>Rev: 0230
>Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
>ANSI SCSI revision: 03
>Dec 1 11:10:32 ns1 kernel: Vendor: QUANTUM Model: ATLAS_V_18_WLS
>Rev: 0230
>Dec 1 11:10:32 ns1 kernel: Type: Direct-Access
>ANSI SCSI revision: 03
>Dec 1 11:10:32 ns1 kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 253
>Dec 1 11:10:32 ns1 kernel: scsi0:A:1:0: Tagged Queuing enabled. Depth 253
>Dec 1 11:10:32 ns1 kernel: scsi: <fdomain> Detection failed (no card)
>Dec 1 11:10:32 ns1 kernel: PCI: Enabling device 00:09.0 (0006 -> 0007)
>Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
<DELETED>
>Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
>Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
>Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
>Dec 1 11:10:32 ns1 kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
>Dec 1 11:10:32 ns1 kernel: scsi0: Signaled a Target Abort
>Dec 1 11:10:32 ns1 kernel: Attached scsi disk sda at scsi0, channel 0, id
>0, lun 0
>Dec 1 11:10:32 ns1 kernel: Attached scsi disk sdb at scsi0, channel 0, id
>1, lun 0
>Dec 1 11:10:32 ns1 kernel: (scsi0:A:0): 80.000MB/s transfers (40.000MHz,
>offset 63, 16bit)
>Dec 1 11:10:32 ns1 kernel: SCSI device sda: 35861388 512-byte hdwr
>sectors (18361 MB)
>Dec 1 11:10:32 ns1 kernel: Partition check:
>Dec 1 11:10:32 ns1 kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
>Dec 1 11:10:32 ns1 kernel: (scsi0:A:1): 80.000MB/s transfers (40.000MHz,
>offset 63, 16bit)
>Dec 1 11:10:32 ns1 kernel: SCSI device sdb: 35861388 512-byte hdwr
>sectors (18361 MB)
>Dec 1 11:10:32 ns1 kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Kernel Question
@ 2011-03-18 20:00 Boswell, Patrick
0 siblings, 0 replies; 4+ messages in thread
From: Boswell, Patrick @ 2011-03-18 20:00 UTC (permalink / raw)
To: linux-omap
When in the boot process of the kernel do block devices get major and
minor devices added?
I can't get a Major/Minor number for /dev/mmcblk0p2 with
blk_lookup_devt(), but the klist iterator
sees ram0:15 and loop0:7, but nothing for mmc.
Thanks.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-03-18 20:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-08-09 2:35 Kernel Question Assem Salama
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 17:29 kernel question Joe Gofton
2002-12-13 19:16 ` Steve Brueggeman
2011-03-18 20:00 Kernel Question Boswell, Patrick
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.